1.

CECI REL PROG(programname) will do the trick.

2.
CICS: How to purge a transaction in CICS Let us say you are Xpediting a program in a CICS region and while in XPED you pressed PF12 key, but you are not getting any response from the region and you wanted to come out of the XPED session. You can follow the below instructions to forcibly come out of the transaction by purging it. Open another session to that CICS region. Assume that the transaction associated with your program is TX01. Now issue command CEMT I TA TRAN(TX01) in the blank in the new session. You will see a screen something like below. I TA TRA(TX01) STATUS: RESULTS - OVERTYPE TO MODIFY

Tas(0004889) Tra(TX01) Fac(BG9Z) Sus Ter Pri( 001 ) Sta(TO) Use(TXUXVXH ) Uow(C8DD6E4749B5A7AE) Hty(ZCIOWAIT) Now type PU as shown below to purge the task and press ENTER key I TA TRA(TX01) STATUS: RESULTS - OVERTYPE TO MODIFY

Tas(0004889) Tra(TX01) Fac(BG9Z) Sus Ter Pri( 001 ) PU Sta(TO) Use(TXUXVXH ) Uow(C8DD6E4749B5A7AE) Hty(ZCIOWAIT) Wait for couple of seconds and press ENTER key again to see if the task is purged. If it is not purged, type FO as shown below to forcibly purge the transaction

I TA TRA(TX01) STATUS: RESULTS - OVERTYPE TO MODIFY

Tas(0004889) Tra(TX01) Fac(BG9Z) Sus Ter Pri( 001 ) FO Sta(TO) Use(TXUXVXH ) Uow(C8DD6E4749B5A7AE) Hty(ZCIOWAIT)

3.
CEMT INQ/SET TASK To inquire upon and set runtime task attributes. Syntax CEMT INQ TASK[(taskNumber)] [CURRENTPROG(progName)] [TCLASS() | ALL] [TRANID(transId)] [FACILITY(facilityId)] [RUNNING | DISPATCHABLE | SUSPENDED] [INFLIGHT | INDOUBT | WAITFORGET] [TASK | TERM | DEST] [USERID(userId)] [PROCESSID(processId)] CEMT SET TASK[(taskNumber)] [CURRENTPROG(progName)] {PURGE | FORCEPURGE} Options taskNumber The CICS-generated task number. You cannot use an asterisk (*) or a plus sign (+). If you do not specify a task number, the command applies to all tasks. You cannot display or change system task attributes. System tasks are those tasks that are started (and used internally) by CICS, not as a result of a user transaction. CURRENTPROG(progName) The eight-character name of the program that is being run in this task. DEST The task has been initiated by a transient data queue trigger level. DISPATCHABLE The task is ready to run.

FACILITY(facilityId) Returns a four-character string that represents the name of the facility that is associated with the named task. If the task was initiated from a terminal (FACILITYTYPE of TERM), FACILITY returns the name of the terminal. If the task was initiated by a destination trigger level as defined in the Transient Data Definitions (TDD) (FACILITYTYPE of DEST), FACILITY returns the name of the associated transient data queue. Otherwise, a null value (blanks) is returned. INDOUBT The task is in the in doubt state during syncpoint processing. INFLIGHT CICS has initiated the task, but no attempt has yet been made to commit any changes that might have been made to recoverable resources during the current unit of work. PROCESSID(processId) The process ID of the process that is running the transaction that is associated with the task. PURGE | FORCEPURGE CICS abnormally terminates the task: PURGE Specifies that the task is to be abnormally terminated, but only when CICS can maintain system and data integrity. A task is not purged if its associated Transaction Definitions (TD) entry has the notpurgeable. FORCEPURGE Specifies that the task is to be abnormally terminated immediately. If a task has already been marked for FORCEPURGE, a further FORCEPURGE request for the task is rejected. After a forcepurge, the application server terminates. If the application server has done any recoverable work, within a short period, a new CICS application server is started with the same app_server_ID. This application server performs the necessary recovery work, such as releasing database locks and backing out any work since the last syncpoint was taken.

When a task is marked for PURGE or FORCEPURGE, CICS checks for this during processing of EXEC CICS commands on behalf of the user program. When the check indicates that the task is to be purged or forcepurged, abnormal task termination is triggered. Resources such as terminals, queues, and files that are locked for use by the task are released; outstanding Logical Unit of Work are backed out; and, recoverable ATI requests are requeued. If the user program keeps control without issuing any EXEC CICS commands, for example, if the program is looping, the check for PURGE cannot be made and the PURGE request has no effect. Similarly, if the user program is waiting for a resource within the execution of an EXEC CICS command, the check for PURGE does not occur until the resource is released. If this does not occur, the PURGE request has no effect. If FORCEPURGE was requested, CICS forces abnormal termination of the task. CICS might be able to terminate the application server tidily, or might cause abnormal termination of the region, depending on what the task was doing at the time of the request. Attention: Because FORCEPURGE can lead to unpredictable results, it must only be used in exceptional conditions. The use of FORCEPURGE is not recommended because it can cause the region to terminate, rather than the task, depending upon what the chosen task is doing. RUNNING The task is running. SUSPENDED Included only for consistency with other CICS family members. If you specify INQ TASK SUSPENDED, CICS displays a zero length list. TASK The task has been initiated from another task. TCLASS(classId) Identifies the task class to which the task belongs. TERM The task has been initiated from a terminal.

TRANID(transId) The transaction name of the task. USERID(userId) The name of the user who initiated the task. WAITFORGET The task is in the wait forget state during syncpoint processing. Examples To inquire upon all INDOUBT tasks: CEMT INQUIRE TASK INDOUBT See the TXSeries for Multiplatforms Intercommunication Guide for related information. Parent topic: CEMT (Runtime Resource Management)