Why does a task remains active in the Datacom MUF after a CICS transaction is purged with the KILL command?

book

Article ID: 15742

calendar_today

Updated On:

Products

CA Datacom CA DATACOM - AD

Issue/Introduction



Why does a task remains active in the Datacom MUF after a CICS transaction is purged with the KILL command?

Environment

Release: DBCISF00200-15.1-Datacom-Database-Option for CICS Services
Component:

Resolution

When a CICS task is terminated with the CEMT SET TASK(number)KILL or CEKL SET TASK(number)KILL command or the KILL command from CA SYSVIEW,  CICS gets rid of the task but does not inform Datacom CICS Services.  The reason is the consequences of using the KILL transaction are unpredictable.

Please see the IBM documentation Consequences of using KILL and refer to the Data and System integrity in Table-1 on the KILL option. According to the documentation neither system nor data integrity is protected when using the KILL transaction to purge a task in CICS. 

In this situation our TRUEs do not get back control from CICS for notification of task termination and two-phase commit processing. As a result the transaction remains active in Datacom CICS Services control blocks and in the MUF.

To resolve the situation perform the following:

  • Find the number of the MUF in question by issuing a DBEC I,MUF(??),SYSID(*) 
  • Issue a DBEC PERFORM,IMMEDIATE,MUF(nn) this will terminate the connection to the MUF and then automatically reconnect.