Certain abends can occur at initialization time. You might need to use native z/OS®, TSO, or CICS® diagnostic facilities to help you diagnose an abend.
For more information about common abends at initialization, see one of the following sections:
If you experience an 0C1 abend, the problem could be that the QMF initialization process is using load modules from one or more prior releases instead of the current release. See Problems that can occur when QMF is not using current load modules to determine whether this is situation is the problem.
- Check to ensure that you ran the DSQ1nPNL installation job, where n is a 1-character national language identifier. This job populates the VSAM panel library, DSQPNLn, with the product panels and help panels from QMF Version 13.1. For more information about this job, see Populating the VSAM panel library or the QMF program directory. Be sure that you are using the correct program directory for your QMF release and national language.
- If you are still experiencing the problem after the DSQ1nPNL
job ran successfully, check file allocations on the following DD statements:
- QMF for TSO:
Check your allocation for DD statement ADMGGMAP to make sure that it points to QMF1310.SDSQMAPn.
- QMF for CICS:
Check that the ADMF DD statement in the startup JCL for the CICS region in which QMF resides correctly points to the GDDM ADMF data set. The DSQ1nADM installation job writes the QMF Version 13.1 GDDM maps to this data set.
- QMF for TSO:
- If the file allocations are correct, see Problems that can occur when QMF is not using current load modules for more troubleshooting suggestions. Abends can occur at various times when QMF Version 13.1 is mistakenly initializing with modules from one or more prior releases.
If you experience an 0C7 abend, the problem could be that the QMF initialization process is using load modules from one or more prior releases instead of the current release. See Problems that can occur when QMF is not using current load modules to determine whether this situation is the problem.
ASRA abends can occur if you are running QMF for CICS. If you receive this error, check the following possible areas for the problem:
- On QMF startup:
- Make sure that all GDDM link-edits ran successfully.
- Make sure that the GDDM IVPs ran successfully in the CICS region.
- Verify that the QMF SMP/E APPLY steps that are documented in the QMF program directory completed successfully. These steps link the QMF load modules with the CICS load modules. Be sure that you are using the correct program directory for your QMF release and national language.
- Make sure that the region allocates the QMF Version 13 Release 1 load libraries and map groups. For more information about these steps of the installation and customization process, see one of the following topics:
- In module DSQQMFE, CSECT ADM:
The problem is probably a GDDM failure. Verify that GDDM is correctly installed and customized for CICS. Verify that GDDM is in the same CSI zone as CICS.
- In module DSQQMFE, CSECT DSQEGINT:
Verify that GDDM is customized for CICS and that a CSD entry exists for the GDDM module ADMASPLC.
- In module DSQQMFE, CSECT DSQIELI:
Verify that a CSD entry exists for the Db2® for z/OS interface module DSQIELI.
- In module DSQCBST, CSECT DSQCMCVP:
After QMF service is applied, verify that a z/OS LLA REFRESH was done in case QMF code is in the Library Lookaside.
- On exit of QMF:
Check that the governor is linked correctly. Review job DSQ1EGLK.
- With ABEND0C4 and DFHSM0102:
This error occurs when you run a query or when you press the Help function key. Make sure that the CSD file entry for DSQPNLn has RECFM=V (where n is a 1-character national language identifier.
- On issuing HELP or RUN commands:QMF data set DSQPNLn, which contains help and other screen text, was either not installed correctly or it was not allocated to the job that started the CICS region. To correct the problem:
- Verify that the CSD entry is defined correctly.
- Verify that a DD statement for DSQPNLn exists in the job stream that starts the CICS region. DD statements are described in Updating the CICS startup job stream.
Also, look for console error messages that are related to the DSQPNLn data set.
Replace n with the 1-character language identifier that represents the NLF you are using.
The Db2 for z/OS attachment facility is not active in the CICS region. Start the attachment facility by using the DSNC transaction.
Make sure that GDDM is running with IOSYNCH=YES.
Verify that the release level of GDDM that you customized for CICS matches the release level of GDDM that you are using in the job stream to start the CICS region.