PM53840: QMF BATCH JOBS END WITH SQLCODE -713 12/01/13 PTF PECHANGE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• QMF tracing shows QMF is immediately issuing a SET SCHEMA
  DEFAULT statement and getting a SQLCODE -713.
  
  For example, QMF reports the following:
  
  USERID: DBA&
  AUTHORIZATION-ID: DBA&
  MESSAGE NUMBER: DSQ10496
  MESSAGE TEXT:
  THE REPLACEMENT VALUE FOR CURRENT SCHEMA IS INVALID.
   &O1:  ..DSN00713
   &O2:  THE REPLACEMENT VALUE FOR CURRENT SCHEMA IS INVALID
   &O3:  0
   &O4:  FFFFFC49 00000000 00000000
   &O5:  FFFFFFFF 00000000 00000000
   &O6:  DSN10015
   &O9:  -713 (3F000)
  
  There is no workaround for this in QMF because it happens before
  one can execute a SET CURRENT SQLID or SET SCHEMA statement.
  
  SQLCODE-713  SQLCODE713  -713 713
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All QMF for TSO/CICS V10.1 users using QMF   *
  *                 with userids containing characters other     *
  *                 than uppercase A-Z, 0-9, #, $ or @.          *
  ****************************************************************
  * PROBLEM DESCRIPTION: Users that invoke QMF with a userid     *
  *                      that contains a character other than    *
  *                      A-Z, 0-9, #, $ or @, will receive a     *
  *                      DSQ10496 'THE REPLACEMENT VALUE FOR     *
  *                      CURRENT SCHEMA IS INVALID.'             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  During QMF initialization, QMF was issuing the 'SET SCHEMA
  DEFAULT' statement to synchronize the CURRENT SQLID and CURRENT
  SCHEMA special registers.  This caused no harm until DB2 for
  z/OS APAR PM50448 began enforcing rules on valid CURRENT SCHEMA
  values.  CURRENT SCHEMA is an ordinary SQL identifier which may
  be any combination of uppercase A-Z, 0-9, # (X'7B'), $ (X'5B')
  or @ (X'7C').  When a userid (CURRENT SQLID) is a value such as
  'DBA&', SET SCHEMA DEFAULT will fail with a SQL code -713.
  Additionally, if a user were to issue a SET CURRENT SQLID to a
  value such as 'DBA&' and then CONNECT to a valid userid, the
  user will receive error DSQ14441 'Internal error detected in
  module DSQISRM.' It is also possible to receive the QMF Lost
  Connection prompt panel if the CURRENT SQLID has been previously
  set to an invalid SCHEMA value.
  

Problem conclusion

• QMF has removed the statement SET SCHEMA DEFAULT from internal
  DB2 for z/OS server initialization. QMF will no longer issue a
  SET SCHEMA statement when the CONNECT command is encountered and
  will let DB2 for z/OS initialize the SCHEMA special register.
  

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:

  UK75437

Modules/Macros

• DSQGSDB2 DSQIDOPT DSQISDB2
  

Fix information

• Fixed component name

  QMF-QUERY MGMT

• Fixed component ID

  566872101

Applicable component levels

• RA10 PSY UK75437

     UP12/01/17 P F201

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.