CTCB

The CTCB (CTC) service provides the ability to abnormally terminate any task in any address space.

Optionally, you can specify

the ABEND and reason code
that a dump be taken
that the task be allowed to retry

You can also indicate that the job step is to be abnormally terminated if the task does not recover.

You can use the TCB service to display the tasks in an address space and create a symbolic name for each TCB.

CTCB,@TCB4,S0C4,RETRY

Syntax

The parameters are defined as follows:

Parameters	Description
tcbadrs	is a symbolic name that resolves to a TCB address in some address space (see examples) or the hexadecimal address of a TCB If you specify a hexadecimal address, you must also specify the address space name as the second operand.
asi	defines the target address space asi is an abbreviation for address space instance; see Identifying-address-spaces for more information. If the first parameter is a symbol and its address space attribute defines the desired target address space, you do not need to provide the asi parameter. If you do provide a value for the asi parameter, the value overrides the address space attribute of the symbol. If the first parameter is a TCB address, you must specify a value for asi (the second parameter).
Unnnn	(optional) can be entered in any position except the first The letters nnnn must be replaced with a four-digit decimal user ABEND code with a value of 1-4095. The task will be abnormally terminated with this code. The default code is U0086.
Sxxx	(optional) can be entered in any parameter position except the first The letters xxx must be replaced with a three hexadecimal character system code. The task will be abnormally terminated with this ABEND code. If you specify both Unnnn and Sxxx, the one entered last will take precedence.
RSNnnnn	(optional) can be entered in any parameter position except the first The letters nnnn must be replaced by one to nine decimal digits. The decimal value is used as the reason code.
DUMP	(optional ) indicates that a dump is requested Warning Note A dump will not be produced unless SYSUDUMP, SYSABEND, or SYSMDUMP has been preallocated. A dump will not be produced if suppressed by a recovery routine established by the task being terminated. Your installation can also suppress dumps.
RETRY	(optional) indicates that the task's recovery routines should be allowed to retry; retry will not be allowed if RETRY is not specified
STEP	(optional) indicates that the jobstep should also be terminated if the task fails to recover

Example 1

After using the TCB service to display information for the TCBs in an address space, you decide that you want to abnormally terminate the TCB labeled @TCB4. You do not care what abnormal termination code is used, so you accept the default of U0086. You also do not want the task's recovery routine to be able to retry, you do not want a dump, and you do not want to terminate the jobstep task; you only need to specify the symbolic name for the TCB.

CTCB,@TCB4

Example 2

You want to cause an abnormal termination in a task to test the recovery routine. Therefore, you want to specify a specific ABEND code, and you want to allow the task to retry:

CTCB,@TCB004,S0C4,RETRY

Example 3

You want to abnormally terminate a task with a user ABEND code, and you also want to provide a reason code:

CTCB,@TCB4,U2000,RSN30

Example 4

You want to abnormally terminate a task. You know the TCB address, and you know that the ASID for the address space is decimal 31. You can also enter the ASID as a hexadecimal value (X1F):

CTCB,160FF8,(31)