PK51461: QMF MSGDSQ16805 AND SQLCODE -805 WHEN QMF FOR TSO TRIES TO CONNECT TO A NON-DB2 Z/OS SERVER.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• MSGDSQ16805 'Your command invoked a program not found in the
  current plan.' is unexpectedly received when invoking QMF.
  An SQL code -805 (SQLCODE805) is seen for package
  DSQESDB7 (QMF V8.1) or DSQFSDB7 (QMF V91.) as well as possible
  others.  The QMF bind package job DSQ1BPKG had been run.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All QMF for TSO/CICS V8.1 and V9.1 users.    *
  ****************************************************************
  * PROBLEM DESCRIPTION: MSGDSQ16805 'Your command invoked a     *
  *                      program not found in the current plan.' *
  *                      is unexpectedly received when invoking  *
  *                      QMF. An SQL code -805 (SQLCODE805) is   *
  *                      seen for package DSQESDB7 (QMF V8.1) or *
  *                      DSQFSDB7 (QMF V91.) and possibly for    *
  *                      other packages.  The QMF bind package   *
  *                      job DSQ1BPKG had been run.              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The user experiencing this problem had added the CURRENTSERVER
  option to the QMF runtime bind plan job (DSQ1BINR). The
  CURRENTSERVER location was a DB2 for Linux remote server.
  Because of this change to the bind plan job, QMF made the
  initial requester connect to the DB2 for Linux server, which
  caused QMF to react unpredictably.
  

Problem conclusion

• Users should never add or modify any options on any of the QMF
  bind packages or plan jobs unless instructed to d so within the
  job itself. In the case of this APAR situation, due to improper
  modification of the QMF runtime plan job, QMF was initially
  connected to a non-DB2 for z/OS database. QMF did not test for
  this possibility and ended in the error condition described.
  QMF is designed to operate only with a DB2 for z/OS requester
  database (on initial CONNECT via the DSQSSUBS or S parameter).
  QMF is able to do remote DRDA connects to non-DB2 for z/OS
  or remote DB2 for z/OS servers after making initial local
  connect to a DB2 for z/OS requester.
  If users want to go immediately to a remote DB2
  server from startup of QMF, the combination of DSQSSUBS (S parm)
  with the DSQSDBNM (D parm) can be used, or the user can issue
  the CONNECT command once in QMF. This APAR will amend QMF to
  detect initial startup in a non-DB2 for z/OS server and issue
  error message DSQ10341 "The database product (xxx) is not
  supported by QMF."  The value of 'xxx' will be replaced by the
  SQLERRP of the initial CONNECT and contains the database
  signature of the database. Note that MSGDSQ10341 can also be
  issued if invoking QMF in an unsupported DB2 for z/OS release.
  

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:

  UK28528 UK28530

Modules/Macros

• DSQIDOPT
  

Fix information

• Fixed component name

  QMF-QUERY MGMT

• Fixed component ID

  566872101

Applicable component levels

• R810 PSY UK28528

     UP07/08/25 P F708

• R910 PSY UK28530

     UP07/08/25 P F708

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.