Applying service updates

Maintenance or service updates might need to be applied to QMF periodically. These updates are in the form of a Program Temporary Fix (PTF) tape from IBM. All QMF tapes are shipped in MSHP format for easy installation and tracking. For more information on how to apply PTFs using MSHP, see the VSE/ESA Installation and Service manual.

Detailed instructions for installing that specific fix accompany the PTF tape from IBM. Like most IBM products, QMF consists of phases. But, unlike most IBM products, it also consists of objects such as panels, GDDM maps, and SQL packages.

Replacing text decks or phases

This is the most common type of replacement. Apply the PTF that contains the new text deck (object) or phase. The PTF specifies to MSHP which link book to use, if necessary.

There are however, QMF objects that require your handling, as they cannot be handled automatically. The MSHP process does keep track of these changes and restores the objects to the QMF sublibrary. The PTF documentation provides details if one of the following steps is to be performed after the PTF installation.

Updating the QMF panel file

If changes are necessary to the QMF Panel file (DSQPNLn), the entire file does not have to be replaced. Instead, single panels are shipped using the following naming convention:

DXYnname.N where n is the NLID

DXYnname is the complete name of the panel.

1. Install the PTF; the panel (or panels) are restored in the QMF sublibrary.
2. Close the existing panel file using the CICS transaction, CEMT:

   CEMT SET DA(DSQPNLn) CLOSE

3. Load the panels to the VSAM panel file DSQPNLn. Use the following sample job to load the panel DSYnname to file DSQPNLn.

   * $$ JOB JNM=REPPANEL,DISP=D,CLASS=0
   // JOB REPPANEL  Replace panel in the QMF panel file
   // DLBL DSQPNLn,'QMF720.DSQPNLn',,VSAM.CAT=VSESPUC
   // LIBDEF *,SEARCH=(qmflib.sublib)
   // EXEC DSQCVS80,SIZE=AUTO
   * $$ SLI MEM=DXYnname.n s=qmflib.sublib
            ............
   /*
   /&
   * $$ EOJ 

   Check and modify, if necessary, the following values:

   • n NLID. The single character that represents the language of the panel.
   • VSESPUC VSAM catalog name where the panel file was originally defined during QMF installation.
   • qmflib.sublib Library and sublibrary for QMF.
   • DXYnname Name of the panel to be replaced. This information is provided with the PTF.
   • .........Repeat, if necessary, the last statement for every panel being replaced by the PTF.
4. Reopen the panel file with:

   CEMT SET DA(DSQPNLn) OPEN

Updating QMF GDDM maps

QMF GDDM maps can also be affected by a PTF. As with the panels, those objects are restored to the QMF sublibrary when the PTF is applied.

1. Install the PTF.
2. Modify the SETPARM statements in the QMF installation job, DSQ3EINS.

   // SETPARM STEP1=NO     *-- DEFINE CLUSTER DSQPNLE
   // SETPARM STEP2=NO     *-- LOAD DSQPNLE
   // SETPARM STEP3=NO     *-- LOAD QMF CHARTS
   // SETPARM STEP4=YES    *-- LOAD QMF MAPS 

3. File and run the job. The first three job steps are skipped, and execution begins with loading the QMF maps.

NLF maps: Because GDDM maps are language dependent, your PTF might require you to change those objects as well.

1. Rerun the job DSQ3nINS, with the following SETPARM settings:

   // SETPARM STEP1=NO     *-- DEFINE CLUSTER DSQPNLP
   // SETPARM STEP2=NO     *-- LOAD DSQPNLP
   // SETPARM STEP3=YES    *-- LOAD QMF MAP GROUPS TO ADMF

2. File and run the job.

Updating QMF SQL packages

If QMF SQL packages are changed with a PTF, then the packages must be loaded into each database where QMF is installed. Use the original installation job, DSQ3EDBI, to update the packages.

1. Modify the SETPARMS in the QMF installation job DSQ3EDBI, as follows:

   // SETPARM STEP1=NO     *-- CREATE QMF CONTROL TABLES INSQLDB
   // SETPARM STEP2=YES    *-- LOAD QMF PACKAGES INTO SQL DB
   // SETPARM STEP3=NO     *-- LOAD QMF SAMPLES INTO SQL D B

2. Locate the // SETPARM DBNAME=SQLDS parameter and verify or change SQLDS to the name of the database that you are using.
3. File and run the job.
4. Repeat the procedure to load the packages into every database.