PK46854: QMF DOES NOT ALWAYS DELETE DSQCBST FROM MEMORY WHEN INITIALIZATION ERRORS CAUSE QMF TO TERMINATE.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Abend S0C4 at offset X'6A' in DSQCDBG1, eyecatcher V8R1.00
  03/03/21 11:48 WIM7388, in the following case:
  1) start QMF 7.2 for a DB2 subsystem that does not exist, get
  message "DSQ10297 Invalid subsystem id SID DB2 in the current
  operating system".
  2) start QMF 8.1 for a DB2 subsystem that does exist, you get
  the S0C4 above ( abends0c4 0c4 abend0c4 )
  This is because module DSQCBST doesn't get DELETEd in all error
  situations, causing DSQCBST V7.2 to remain in storage (linked
  RN, RU) for the invocation of QMF 8.1 and the LOAD for DSQCBST
  that is issued.
  

Local fix

• log off and log on TSO should fix this.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All QMF for TSO/CICS users invoking multiple *
  *                 releases of QMF within one ISPF session.     *
  ****************************************************************
  * PROBLEM DESCRIPTION: A user invoked QMF V7.2 and received    *
  *                      error MSGDSQ10297 'Invalid subsystem id *
  *                      xxx in the current operating system.'.  *
  *                      The user then tried to invoke QMF V8.1  *
  *                      within the same ISPF session and        *
  *                      received an ABEND0C4 and was unable to  *
  *                      invoke QMF V8.1. While diagnosing the   *
  *                      abend, it was determined that a V7.2    *
  *                      version of module DSQCBST was still in  *
  *                      storage during the QMF V8.1 invocation. *
  *                      This module should have been deleted    *
  *                      from storage during the QMF V7.2        *
  *                      termination. The user was not           *
  *                      allocating mixed release libraries for  *
  *                      their QMF V8.1 allocations.             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  If an error during QMF initialization prevents QMF from fully
  starting, QMF may not delete module DSQCBST during termination.
  If within the same ISPF session, a different release of QMF is
  invoked, unpredictable results can occur (ABEND0C4or any abend)
  due to a mixture of QMF release modules.  Both invocations of
  QMF must be attempted within the same ISPF session. The first
  attempt must end in an initialization error such as MSGDSQ10297,
  MSGDSQ10289, MSGDSQ10298, MSGDSQI0014 or any initialization
  error. The second invocation must be within the same ISPF
  session.
  

Problem conclusion

• QMF module DSQCBST has been modified to detect if an
  initialization error has occured so that flag DSQ_CBST_INIT will
  be properly set to DSQ_ISPF_CBST_LOADED to trigger the deletion
  of module DSQCBST upon termination.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UK26082 UK26083 UK26084

Modules/Macros

• DSQCBST
  

Fix information

• Fixed component name

  QMF-QUERY MGMT

• Fixed component ID

  566872101

Applicable component levels

• R720 PSY UK26082

     UP07/06/15 P F706

• R810 PSY UK26083

     UP07/06/15 P F706

• R910 PSY UK26084

     UP07/06/15 P F706

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.