Action parameters for CTMTLB

The following parameters are used to perform actions:

• Multiple sets of SCHEDULE-LIB/TABLE statements are permitted. SCHEDULE-LIB/TABLE statements point to the library and member names of the job scheduling library and tables on which the utility operates. At least one TABLE statement per SCHEDULE-LIB statement is required.

  Masking (? and * wildcards) in the TABLE name parameter is permitted.

• Comment statements begin with an asterisk in column 1.
• The optional parameter CONVERT-TAGS=Y causes a subsequent execution of the CTMBLT utility to convert regular schedule tags (in SMART table entity) to external (CTM-LEVEL) RBCs. Setting CONVERT-TAGS=N cancels the affect of CONVERT-TAGS=Y.
• The utility control statement RUN_AS_DUMMY=Y causes all jobs to be treated as Dummy jobs. When this statement is used, job statuses of all jobs change to ENDED OK immediately when the pre-submission criteria of the jobs are satisfied.

  The RUN_AS_DUMMY=Y statement has the following impact on job definitions in Control-M/EM:

  • For jobs in all datacenters (both distributed and mainframe) the Run as dummy check box is selected.
  • For distributed jobs, the command or script defined in the What area is bypassed.

  Note that if you subsequently choose to clear the Run as dummy check box, all jobs are restored to their original job type. Mainframe jobs are also restored to their original Override Path (overlib) and UseInstreamJCL values.

  To use the RUN_AS_DUMMY option, the following statements must be defined in all jobs, either as input for the CTMBLT utility or manually through the Job Scheduling Definition Screen in Control-M (Screen 2):

  SETVAR %%$BMCWAIORIGTYPE=original-overlib-value

  SETVAR %%$BMCWAIORIGUSEISJCL="Y"

  OVERLIB="DUMMY"

  If you are converting from the CA ESP scheduling product and want to use the Run as dummy functionality, see the description of the RUNDUMMY parameter in the Control-M for z/OS for CA-ESP Conversion Guide.

• If CTMTLB processes multiple scheduling libraries, you can use APPEND_LIB_SUFFIX_TO_FOLDER=x to ensure the uniqueness of non-mainframe table names. APPEND_LIB_SUFFIX_TO_FOLDER=x appends a suffix with a length of x to each non-mainframe table name. The suffix is derived from the scheduling library name.