CTB Step

Adds Control‑M/Analyzer steps as the first and/or last step of the job’s execution.

Additional information	Description

Usage	Optional
Availability	This parameter is accessed from the Control‑M for z/OS interface only.
Format	CTB Step is composed of the AT, NAME, TYPE, and ARGUMENTS sub-parameters, described below.
Invalid Characters	Non-English characters
Variable Support	None
Alternate names	Control‑M/EM Utilities: (none) Control-M Report: (none) Control‑M/Server Utilities: (none) Control‑M for z/OS: (none) Control‑M/EM API: ctb_step
Sub-parameters
AT	Indicates where to place the Control‑M/Analyzer step in the job. Mandatory. Valid values: S (Start) – The indicated Control‑M/Analyzer step must become the first step of the job. E (End) – The indicated Control‑M/Analyzer step must become the last step of the job.
NAME	Name of the Control‑M/Analyzer entity. Must be a valid name of a Control‑M/Analyzer rule or mission. Mandatory.
	Length	1 through 8 characters
	Case Sensitive	Yes
	Invalid Characters	Blanks; non-English characters
TYPE	Type of Control‑M/Analyzer entity. Mandatory. Valid values: R (Rule) – Entity is a Control‑M/Analyzer rule. M (Mission) – Entity is a Control‑M/Analyzer mission.
ARGUMENTS	Arguments to be passed to the Control‑M/Analyzer step. Optional.
	Length	0 through 60 characters
	Case Sensitive	Yes
	Invalid Characters	Non-English characters

A maximum of two CTB STEP statements (that is, one START statement and one END statement) can be specified.

Multiple arguments must be separated by a comma without a space because they are automatically passed to the Control‑M/Analyzer step as a PARM=<arguments> parameter in the step’s JCL.

Control-M uses the status returned by Control‑M/Analyzer as it would use the return status of any job step.

If Control‑M/Analyzer returns a status of OK or TOLER (within accepted tolerances), Control-M considers the step as having ended OK.
If Control‑M/Analyzer returns a status of NOTOK or ABEND, Control-M considers the job step as having ended NOTOK.
NOTE: The Auto-Archive parameter is relevant only for jobs to be run in z/OS environments or OpenVMS computers. The parameter is displayed only if Control-R is selected.

EXAMPLE: Check results and set a condition

After successfully performing salary calculations, job SACALC01 invokes rule CHKCALC to ensure that the results are reasonable, and then sets OUT condition SALARY-OK.

JOB: SACALC01 LIB CTM.PROD.SCHEDULE FOLDER: SALARY

COMMAND ===> SCROLL===> CRSR

+--------------------------------------------------------------------------+

MEMNAME SACALC01 MEMLIB GENERAL

RUN AS SYS1 TASKTYPE JOB PREVENT-NCT2 DFLT N

APPL SAL SUB APPLICATION SALARY

DESC SALARY CALCULATIONS

OVERRIDE PATH

SCHENV SYSTEM ID NJE NODE

SET VAR

CTB STEP AT END NAME CHKCALC TYPE RULE

ARGUMENTS %%ODATE

CTB STEP AT NAME TYPE

DOCMEM SACALC01 DOCLIB CTM.PROD.DOC

===========================================================================

DAYS 01,15 DCAL

AND/OR

WDAYS WCAL

MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12- Y

DATES

CONFCAL SHIFT RETRO Y KEEP ACTIVE FOR 00 D-CAT

MINIMUM PDS

DEFINITION ACTIVE FROM UNTIL

===========================================================================

CONTROL

RESOURCE

PIPE

TIME: FROM UNTIL PRIORITY DUE OUT SAC CONFIRM

TIME ZONE:

===========================================================================

OUT SALARY-OK ODAT +

COMMANDS: EDIT, DOC, PLAN, JOBSTAT 11.17.00

Parent Topic

Actions parameters