How to resolve CICS units of work manually

If the CICS-WebSphere MQ adapter ends abnormally, CICS® and WebSphere® MQ build indoubt lists either dynamically or during restart, depending on which subsystem caused the abend. When CICS connects to WebSphere MQ, one or more units of work might not have been resolved. Any units of work that CICS cannot resolve must be resolved manually using WebSphere MQ commands.

About this task

If some units of work have not been resolved, one of the following messages is sent to the console:
  • DFHMQ0404E
  • DFHMQ0405E
  • DFHMQ0406E
  • DFHMQ0407E
  • DFHMQ0408I
  • DFHMQ2064
  • DFHMQ2065
  • DFHMQ2066

CICS retains details of units of work that were not resolved during connection startup. An entry is purged when it no longer appears on the list presented by WebSphere MQ.

Any units of work that CICS cannot resolve must be resolved manually using WebSphere MQ commands. This manual procedure is rarely used, because it is required only where operational errors or software problems have prevented automatic resolution. Any inconsistencies found during indoubt resolution must be investigated.

To resolve the units of work:

Procedure

  1. Obtain a list of the units of work from WebSphere MQ using the following command:
    +CSQ1 DISPLAY CONN(*) WHERE(UOWSTATE EQ UNRESOLVED)
    You receive the following message:
    CSQM201I +CSQ1 CSQMDRTC  DISPLAY CONN DETAILS 
    CONN(BC85772CBE3E0001)                       
    EXTCONN(C3E2D8C3C7D9F0F94040404040404040)    
    TYPE(CONN)                                   
    CONNOPTS(                                    
     MQCNO_STANDARD_BINDING                      
     )                                           
    UOWLOGDA(2005-02-04)                         
    UOWLOGTI(10.17.44)                           
    UOWSTDA(2005-02-04)                          
    UOWSTTI(10.17.44)                            
    UOWSTATE(UNRESOLVED)                         
    NID(IYRCSQ1 .BC8571519B60222D)               
    EXTURID(BC8571519B60222D)                    
    QMURID(0000002BDA50)                         
    URTYPE(CICS)                                 
    USERID(MQTEST)                               
    APPLTAG(IYRCSQ1)                             
    ASID(0000)                                   
    APPLTYPE(CICS)                               
    TRANSID(GP02)                                
    TASKNO(0000096)                              
     END CONN DETAILS                   

    For CICS connections, the NID (origin identifier) consists of the CICS applid and a unique number provided by CICS at the time the syncpoint log entries are written. This unique number is stored in records written to both the CICS system log and the WebSphere MQ log at syncpoint processing time. This value is referred to in CICS as the work token.

  2. Scan the CICS log for entries related to a particular unit of work:
    1. Look for a PREPARE record for the task-related installation where the work token field (JCSRMTKN) equals the value obtained from the network ID. The network ID is supplied by WebSphere MQ in the DISPLAY CONN command output.
    2. The PREPARE record in the CICS log for the units of work provides the CICS task number. All other entries on the log for this CICS task can be located using this number.
    3. You can use the CICS journal print utility DFHJUP when scanning the log. For details of using this program, see Reading log streams using batch jobs (for example, DFHJUP).
  3. Scan the WebSphere MQ log for records with the NID related to a particular unit of work. Then use the URID from this record to obtain the rest of the log records for this unit of work. You can use the WebSphere MQ print log records program (CSQ1LOGP) to scan the log. When scanning the WebSphere MQ log, note that the WebSphere MQ startup message CSQJ001I provides the start RBA for this session.
  4. If you need to, perform indoubt resolution in WebSphere MQ. WebSphere MQ can be directed to take the work action for a unit of work using a WebSphere MQ RESOLVE INDOUBT command. To recover all threads associated with a specific connection-name, use the NID(*) option. The command produces one of the following messages showing whether the thread is committed or backed out:
    CSQV414I +CSQ1 THREAD network-id COMMIT SCHEDULED
    CSQV415I +CSQ1 THREAD network-id ABORT SCHEDULED

Results

When performing indoubt resolution, CICS and the adapter are not aware of the commands to WebSphere MQ to commit or back out units of work, because only WebSphere MQ resources are affected. However, CICS keeps details about the indoubt threads that were not resolved by WebSphere MQ. This information is purged either when the list presented is empty or when the list does not include a unit of work of which CICS has details.



za12930_.html | Timestamp icon Last updated: Monday, 5 June 2017