Maintenance procedures

Fixes to the FDRPAS products are provided by BMC Compuware in the form of zaps. Before using FDRPAS, you should check to see if there is any new FDRPAS maintenance required since the FDRPAS installation package was created. FDRPAS maintenance is packaged in a ZIP file and is available in the FDRPAS Downloads section of the BMC Support Center.

Included in the ZIP file is a Table of Fixes PDF document that describes the necessary maintenance as well as the information on how to apply the maintenance. Please review this entire document.

These zaps can be applied by using the IBM SUPERZAP program (PGM=AMASPZAP or IMASPZAP) but BMC Compuware also provides a program for applying zaps that is an advantage.

FDRSPZAP Program

The FDRSPZAP program uses JCL almost identical to the IBM SUPERZAP program and accepts all SUPERZAP control statements. However, it has an advantage over SUPERZAP. The CHECKSUM statement, which BMC Compuware provides as part of all zaps, is used as a check that zaps have been entered correctly. It compares the value provides to a checksum of all hexadecimal digits on the preceding VER and REP statements; almost all typing errors result in a checksum mismatch and an error message. However, the IBM SUPERZAP program compares the checksum AFTER it has already applied the changes in the REP statements. Therefore, it tells you that you have just applied a bad zap and leaves it to you to back it off. FDRSPZAP reads all the control statements and verifies the CHECKSUM before invoking SUPERZAP to perform the actual zap.

FDRSPZAP JCL

The JCL for execution of FDRSPZAP looks like this (similar to SUPERZAP):

//FDRSPZAP EXEC PGM=FDRSPZAP,REGION=0M
//STEPLIB DD DISP=SHR,DSN=fdrpas.loadlib
//SYSLIB DD DISP=SHR,DSN=fdrpas.loadlib
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
.SUPERZAP control statements supplied by Compuware.
/*

FDRMVZAP Program

FDRMVZAP is used to apply zaps to the in-storage copies of the FDRMOVE Dynamic Allocation Intercept Exit (FDR0009I), if the exit is active and dynamically installed. If test exits are installed, fixes can be applied to either the test or production exits.

FDRMVZAP JCL

The JCL for execution of FDRMVZAP looks like this (similar to SUPERZAP):

//FDRMVZAP EXEC PGM=FDRMVZAP,REGION=0M,PARM=parm
//STEPLIB DD DISP=SHR,DSN=fdrpas.loadlib
//SYSLIB DD DISP=SHR,DSN=fdrpas.loadlib
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
.SUPERZAP control stmts supplied by Compuware.
/*

FDRMVZAP Parameters (PARM=)

FDRMVZAP accepts a PARM= value (“parm” in the example above). Possible values are:

null or PARM= omitted

FDRMVZAP applies the zap only to the library indicated by SYSLIB.

IGNIDRFULL

All BMC Compuware zaps include an IDRDATA statement, which stores a string with each module indicating which zaps are applied. If the space reserved for IDR data in a load module becomes full, IGNIDRFULL allows the zap to be applied anyway (although the IDRDATA is not saved).