GeoStan - geostan_1

Note: To run the installation verification program for a CICS-enabled system, log into CICS and run transaction G1GI. Type the address and last line. Verify that a standardized name and address are returned.

To run the GeoStan installation verification job:

Edit the JCL in yourprefix.GEOSTAN.CNTL(GSIVPJOB).

The following is an example of the JCL:

// yourjob JOB ... <=== Fill in the jobcard
//****************************************************************
//*
//* Job to run sample application
//*
//* Lines marked with <=== must be tailored to your installation.
//*
//***************************************************************
// MVSTEST PROC GEOSPFX=yourprefix.GEOSTAN<=== GeoStan
//* data set prefix
//*

Substitute the items in bold with the appropriate values, as follows:

yourjob	The job name and rest of the job card per your installation standards.
yourprefix	The correct prefix for your z/OS product target data set names.

Note: If you installed VSAM data sets, you must modify the JCL to reflect the correct data set names.

Optionally, edit the JCL in yourprefix.GEOSTAN.CNTL(PNTIVPCK) to verify the point-level data installation. For information on editing the JCL, see the preceding step.
Submit and run the applicable jobs.
When the jobs complete, you should receive a condition code of "0000". If any other code is returned, investigate the job's output listing and correct the error.

Use Case	Output
If you do NOT have point-level data, and are not matching to an auxiliary (GAX) file, the output from the GSIVPJOB job should be:	PRECISELY SOFTWARE INC 1700 District Ave Ste 300 Burlington, MA 01803-5231 USA longitude: -105.239771 latitude: 40.018912 location code: AS0 match code: S80
If you have point-level data, the output from the PNTIVPCK job should be:	PRECISELY SOFTWARE INC 1700 District Ave Ste 300 Burlington, MA 01803-5231 USA longitude: -105.240976 latitude: 40.018301 location code: AP02 match code: S80
If you are using an auxiliary (GAX) file, the test JCL (GSIVPJOB) first runs MVSTEST without using an auxiliary file. It then reruns MVSTEST using an auxiliary file. The output from the job when rerun using the auxiliary file should be:	PRECISELY SOFTWARE INC 1700 District Ave Ste 300 Burlington, MA 01803-5231 USA longitude: -105.240976 latitude: 40.018912 location code: AG0 match code: G00

Use Case

Output

If you do NOT have point-level data, and are not matching to an auxiliary (GAX) file, the output from the GSIVPJOB job should be:

PRECISELY SOFTWARE INC

1700 District Ave Ste 300

Burlington, MA 01803-5231 USA

longitude: -105.239771

latitude: 40.018912

location code: AS0

match code: S80

If you have point-level data, the output from the PNTIVPCK job should be:

PRECISELY SOFTWARE INC

1700 District Ave Ste 300

Burlington, MA 01803-5231 USA

longitude: -105.240976

latitude: 40.018301

location code: AP02

match code: S80

If you are using an auxiliary (GAX) file, the test JCL (GSIVPJOB) first runs MVSTEST without using an auxiliary file. It then reruns MVSTEST using an auxiliary file. The output from the job when rerun using the auxiliary file should be:

PRECISELY SOFTWARE INC

1700 District Ave Ste 300

Burlington, MA 01803-5231 USA

longitude: -105.240976

latitude: 40.018912

location code: AG0

match code: G00

GeoStan - geostan_1 - 2024.01

GeoStan Geocoding Suite Installation for z/OS