Purging a transaction that is using DBCTL

You can query and purge tasks that use DBCTL using the CICS® CEMT transaction as for any CICS task. However, if a transaction has "hung" in DBCTL, and you need to purge it, you must use the DBCTL command /STOP THREAD.

To find out what is happening to a task:

  1. Issue CEMT INQ TASK to find out what tasks are active.
  2. Expand the information on individual tasks by typing a ? to the left of the task you want to see. You will get a display like the one in Figure 23.
    Figure 23. CEMT INQ TASK (expanded)
      I TA
      SYNTAX OF SET COMMAND
       Tas(0000110) Tra(DLID) Fac(D2D3) Sus Ter Iso Pri( 001 )
          Hty(DBCTL   ) Hva(DLSUSPND) Hti(000007) Sta(TO)
          Use(CICSUSER) Rec(X'9EDA1F61E11CFA02')
       CEMT  Set TAsk() | < All >
        < PRiority() >
        < PUrge | FOrcepurge >
     
     
     
     
     
     
     
     
     
     
     
     
     
                                                          SYSID=CIC1 APPLID=DBDCCICS
     
     PF 1 HELP       3 END                    7 SBH 8 SFH 9 MSG 10 SB 11 SF
    Figure 23 includes the following useful information:
  3. Issue CEMT INQ TASK again.

To do this:

  1. From the CEMT INQ TASK display, make a note of the CICS APPLID and the 16-digit recovery token. (You can use a recovery token to find the thread number of a CICS task in DBCTL. For a fuller definition, see CICS DBCTL recovery tokens.)
  2. At the DBCTL console, enter /DISPLAY CCTL cctlname, where cctlname is the CICS APPLID (in this example, it is DBDCCICS). This causes the current status of DL/I activity to be displayed, as shown in Figure 24.
    Figure 24. Output from /DISPLAY CCTL cctlname
    0080  /DIS CCTL DBDCCICS
    0080  DFS000I MESSAGE(S) FROM ID=SYS1 047
    0080      CCTL     PSEUDO-RTKN  RECOVERY-TOKEN   REGID  PSBNAME   STATUS
    0080      DBDCCICS                                                 ATTACHED
    0080                            9EDA1F61E11CFA02     6  PC3COCHD  ACTIVE
    0080                            9EDA1F4E9B571B02     5  PC3COCHD  ACTIVE
    0080      *88204/101241*
  3. Find the recovery token (9EDA1F61E11CFA02 in this example) that matches the one you noted from the CEMT INQ TASK display, and then note the thread number that is next to it in the REGID column (6 in this example).
  4. Issue the command:
    /STOP THREAD n ABDUMP
    where n is the thread number.

    This causes the thread and transaction to terminate when it has finished processing the current request, and causes a dump to be taken.

    If the thread does not stop, use:

    /STOP THREAD n CANCEL

    Do not use /STOP THREAD CANCEL if you do not need to, because it may cause DBCTL to terminate with a U113 abend.

Related concepts
Back to full list of operator communications
Operator communication with DBCTL -- overview
Other related concepts
Operations with DBCTL
Connecting to DBCTL: overview
Dealing with messages from DBCTL and CICS
[[ Contents Previous Page | Next Page Index ]]