PI84698: ENHANCEMENT FOR MQLISTENER FOR RECONNECTING DB2

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• Enhancement for MQListener for reconnecting DB2
  
  In the reported case, the DB2 subsystem shutdown
  while MQListener was active resulting in MQListener
  shutting down each time messages were placed on the queue.
  
  
  Additional keywords and symptoms:
  ************************************
  SQLCODE924 -924 DSNQ075I
  SQLSTATE58006 58006
  

Local fix

• no local fix or workaround
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All DB2 11 and DB2 12 for z/OS users of                      *
  * the MQListener application.                                  *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * This apar addresses the following two                        *
  * problems.                                                    *
  *                                                              *
  * First Problem.                                               *
  *                                                              *
  * Currently, MQListener connects to DB2                        *
  * at start up time and reuses the                              *
  * connection. If the connection is                             *
  * bad, the user needs to shutdown                              *
  * and restart MQListener.                                      *
  *                                                              *
  * Second Problem.                                              *
  *                                                              *
  * If there is some issue which causes                          *
  * the shutdown of MQListener, MQListener                       *
  * writes messages to the MQListener log                        *
  * but not to the z/OS console or log.                          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply corrective PTF when available                          *
  ****************************************************************
  This apar addresses the following two
  problems.
  
  First Problem.
  
  Currently, MQListener connects to DB2
  at start up time and reuses the
  connection. If the connection is
  bad, the user needs to shutdown
  and restart MQListener.
  
  Second Problem.
  
  If there is some issue which causes the
  shutdown of MQListener, MQListener
  writes messages to the MQListener log
  but not to the z/OS console or log.
  

Problem conclusion

Temporary fix

Comments

• This apar will provide the following new
  support for MQListener.
  
  1-- A new option 'restartDB2' is being
  added to the MQListener run command
  so the "listener" will reconnect DB2 after
  a DB2 outage or recycle.
  MQListener only reconnects to DB2 if the
  value of 'restartDB2' is 'Y' or 'y'.
  The default value of 'restartDB2' is 'N'.
  
  Please note that without this option,
  'restartDB2', MQListener will run with
  the old behavior (prior to this apar).
  
  Example:
  
    db2mqln2 run -ssID DB2A -config ACFG1
    -adminQueue ADMIN_Q
    -adminQMgr CSQ1 -restartDB2 Y
  
  
  2-- MQListener will write a message to
  the console log of z/OS when it is
  shutdown.
  
  Example of the message written to
  the console log:
  
    DSNQ084I MQListeners associated
    with configuration 'ABCD',
    DB2 subsystem 'DB2A' are shutdown.
  
  
  Please note:
  
  The 'Programming for DB2 for z/OS' publication, the 'MQListener
  in DB2 for z/OS' section, 'Configuring MQListener tasks'
  subsection, will be updated to include the above information
  as needed.
  
  After this apar/ptf is applied, users will need to rerun
  DSNTIJML for the 'BINDBRM' step to rebind MQListener and rebind
  the MQListener's applications
  

APAR Information

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

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

  UI52370 UI52371

Modules/Macros

• DSN@MQRN DSN@MQCF DSNAMQLN
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RC10 PSY UI52370

     UP17/12/19 P F712  

• RB10 PSY UI52371

     UP17/12/19 P F712  

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.