DFHMQ2064    date time applid Resynchronization outstanding for queue manager qmgr1 after CICS-MQ group attach has connected to queue manager qmgr2.

Explanation

CICS indicates that resynchronization is outstanding for queue manager qmgr1 after CICS-MQ group attach has connected to queue manager qmgr2.

System action

The CICS is connected to WebSphere MQ queue manager qmgr2 but UOWs remain outstanding for WebSphere MQ queue manager qmgr1.

User response

The MQCONN definition either has RESYNCMEMBER(NO) specified, or RESYNCMEMBER(YES) is specified but CICS detected that all the UOWs outstanding are shunted indoubt meaning that resynchronization with WebSphere MQ cannot take place immediately. Both these situations allow group attach to proceed, and the result is CICS has connected to a different WebSphere MQ queue manager than previously. The user must manually reconnect to the original WebSphere MQ queue manager, which automatically resynchronizes the outstanding (non shunted) units of work. Shunted units of work wait to be unshunted at which point resynchronization takes place if CICS is connected to the original WebSphere MQ queue manager.

Module

DFHMQCON

XMEOUT parameters/Message inserts

  1. date
  2. time
  3. applid
  4. qmgr1
  5. qmgr2

Destination

CMQM and Console



DFHMQ2064.html | Timestamp icon Last updated: Sunday, 4 June 2017