QJZARK and VISION:Report maintenance

Document ID : KB000046088
Last Modified Date : 14/02/2018
Show Technical Document Details

  SUMMARY:

VISION:Report maintenance is unlike any other CA product.

Both the configuration and tracking mechanisms are unique.

  BACKGROUND:

The product was acquired from Sterling Software which was acquired from Dylakor which was acquired from Goal systems.

Each company kept the initial maintenance configuration of the product.

   ENVIRONMENT:

z/OS

   INSTRUCTIONS:

 A) Configuration

The recommended loadlib configuration consists of a base loadlib, preceded by a patch loadlib, preceded by a PCP (custom) loadlib if any.

The patch loadlib is created by copying any modules to be corrected from the base to a new loadlib, then modifying those.

The base is never touched.

Similarly, if there are any customizing patches, a 3rd loadlib would be created in the same manner.

This is documented on page 1-18 of the r16.1 Installation Guide.

The history to this is that a cumulative fix file was delivered to customers and we are happy to provide one as well.

 

B) Tracking

To determine what maintenance is applied, use the QJZARK utility that is provided with the system.

There is a VISION:Report program in the member called QJZARK in the SAMPLIB delivered with the installation.

Hence you can run a job like this to see what you have applied to your system:

//    JOB  

//STEP1 EXEC PGM=QUIKJOB

//STEPLIB  DD DISP=SHR,DSN=your.visionreport.pcpload

//         DD DISP=SHR,DSN=your.visionreport.patchload

//         DD DISP=SHR,DSN=your.visionreport.baseload

//SYSIN    DD DISP=SHR,DSN=your.visionreport.SAMPLIB(QJZARK)

//SYSOUT   DD SYSOUT=*

//SYSPRINT DD SYSOUT=*

//SYSUT1   DD DUMMY

//