Update Parameters (CTMTBUPD)

Update parameters generally correspond to the parameters of the Control-M Job Scheduling Definition screen. Not all fields in the Job Scheduling Definition screen can be updated using the utility. Fields that can be updated are listed and described below. For a detailed description of each parameter, see the Job Production parameters chapter in the Control-M for z/OS User Guide.

Note: To update fields that are not supported by the CTMTBUPD utility, such as ONPGM or SHOUT, BMC recommends using a combination of the CTMBLT and CTMTLB utilities described in CTMBLT – Create Tables and CTMTLB – Produce XML and CTMBLT Utility Files, respectively. Once the CTMTLB utility has produced statements in the format suitable as input to the CTMBLT utility, these can be edited or updated with any editor, such as ISPF edit, and then run through the CTMBLT utility to recreate the tables with the desired changes.

Fields to be updated can fall into either of two categories:

fields easily updated by simple specification of the new value
fields that require complex value specifications

Fields Easily Updated

You can update the fields shown in Table 151a by specifying the new desired values in the following format:

parm_name=new_value

where

parm_name is the name of the parameter in the job scheduling definition.
new_value is the new value for the parameter.

Note: In Table 151a, an asterisk in column * indicates that character masking can be specified for the parameter as follows:

If an asterisk is specified following a character string, the character string is treated as a prefix (meaning, only the first n characters of the parameter, corresponding to the number of characters preceding the *, participate in the modification).

If the character string begins with one or more asterisks, the number of characters at the start of the parameter value corresponding to the number of asterisks specified do not participate in the modification.

Table 151a CTMTBUPD Parameters

Parameter	*	Value	Description
ACTIVE-FROM		6 digits in format yymmdd	Schedule RBC Definition Active From date
ACTIVE-UNTL		6 digits in format yymmdd	Schedule RBC Definition Active Until date
ADJUST-CONDITION		Y (Yes), N (No), D (Dummy), or B (Bridge)	Adjust conditions indicator. For SMART Table Entities only
APPL	*	1 through 20 characters	Application name
AUTOARC		Y (Yes) or N (No)	Archive SYSDATA
CATEGORY		1 through 20 characters	Category for Control-D
CONFCAL		1 through 8 characters	Confirmation calendar name
CONFIRM		Y (Yes) or N (No)	Confirmation for schedule
CYCLIC-TYPE		C, S, V	Type of interval between cycles: C – constant; S – specified; V – varying
CYC-RUNTIME		hhmm,nnn	Enhanced cyclic specific run times in 24-hour format: hh (hour), mm (minutes) with an optional day-offset (nnn)
DATES		4 digit dates, separated by commas	DATES scheduling
DAYS		For information, see the Job Production parameters chapter of the Control-M for z/OS User Guide	Scheduling days
DAYSFROM		3 digits (0–120)	Time FROM days offset
DAYSKEEPNOK		2 digits (0–99)	The minimal number of days that the folder and its jobs are kept in the AJF after the folder is marked as "NOT-OK". 1-98 – Number of days to keep. 99 – Keep forever. The above two options are invalid when REMOVEATONCE is set to "No". 0 – Do not keep (Default). This is the only valid value when REMOVEATONCE is set to "No".
DAYSUNTIL		3 digits (0–120)	Time UNTIL days offset
DAYS-DUEOUT		3 digits (0–120)	Due-out time days offset
DCAL		1 through 8 characters or "*"	DAYS calendar name
DEL-RBC	*	1 through 20 characters	Name of RBC to delete from the SMART Table
DESC		1 through 50 characters	Description of job
DOCLIB	*	1 through 44 characters	Documentation library name
DOCMEM	*	1 through 8 characters	Documentation member name
DUE-OUT		[+/-]hhmm	Due out time
INSERT-RBC	*	1 through 20 characters	Name of RBC to insert into the SMART Table
INTERVAL		5 digits (0-64800)	Minutes between reruns
INTERVAL-TYP		1 character: S (Start), E (End), or T (Target)	Interval type
INTERVL-UNIT		M, H, D	The units in which INTERVAL is expressed (Minutes, Hours, or Days)
MAXDAYS		2 digits	Expiration period
MAXRERUN		4 digits	Maximum number of reruns
MAXRERUN - CYC		4 digits; 0 through 9999	Maximum number of cyclic runs. Effective only if TASKTYPE is set to CYC for job or TBC for cyclic SMART Table.
MAXRUNS		3 digits	Maximum number of runs
MAXWAIT		2 digits	Maximum days job is retained 0-98 (default is 0) 99 indicates "forever"
MEMLIB	*	1 through 44 characters	Library containing JCL member
MEMNAME	*	1 through 8 characters	JCL member name
NJE-NODE		1 through 8 characters	NJE node identifier
OVERLIB	*	1 through 44 characters	Overriding JCL library name
OWNER	*	1 through 8 characters	User-identification
PREVENT-NCT2		Y (Yes) or N (No) or F or L	Prevent ‘NOT CATLGD 2’ errors
PRIORITY		1 to 2 characters	Priority
RBC	*	1 through 20 characters	Schedule RBC name
RBC-LEVEL		CTM or TBL	Indicates whether this is a Control-M Rule-based Calendar or a Table Rule-based Calendar
RBC-RELATION		1 character (blank, O, A)	RBC And/Or relationship
RELATION		A or O	AND or OR relation
REMOVEATONCE		Y (Yes) or N (No - default)	Indicates that all the jobs will be removed together, when the folder is ready to be removed.
RETDAYS		3 digits	Maximum number of days to retain
RETGENS		2 digits	Maximum number of generations to retain
RETRO		Y (Yes) or N (No) - Y (Yes) is not valid in SMART Tables	Retroactive selection
SCHENV		1 through 16 characters	Workload management scheduling environment
SHIFT		1 character: >, <, @, blank	Shift on confirmation calendar
SHIFT-EXT		3 characters: ±nn, or blank	For a description, see the Control-M for z/OS User Guide
SAC		1 character (P, N, -, +, blank)	Schedule adjustment for conversion
SYSDB		Y (Yes) or N (No)	Archive to common data set
SYSTEM-ID		1 through 4 characters	SYSTEM-ID identifier
TABLE	*	1 through 20 characters	Table name
TASKTYPE		3 characters	Type of task (job, started task, and so on. For SMART Tables the valid values are: TBC - cyclic SMART Table and TBL - regular table)
TIMEFROM		[+/-]hhmm	Earliest time to submit job
TIMEUNTIL		[+/-]hhmm,>	Latest time to submit job, submit as soon as possible
TIME-ZONE		3 characters	Time zone designation
TOLERANCE		1 to 4 digits	Enhanced cyclic tolerance - the maximum number of minutes after the specified time permitted for a late submission.
VAR-INTERVAL		nnnnn,unit	Enhanced cyclic varying interval (nnnnn - interval length, unit = M (Minutes), H (Hours), D (Days)
WCAL		1 through 8 characters or "*"	WDAYS calendar name
WDAYS		For information, see the Control-M for z/OS User Guide	Weekly scheduling days

Note:

You can use a blank (‘ ’) as the value for any parameter in Table 151a, except for the MEMLIB, MEMNAME, and OWNER parameters.
Certain parameters cannot be specified with other parameters. For example, if you specify the DATES parameter, you cannot specify the MONTHS and RELATION parameters. For the rules governing valid parameter combinations, see Control-M for z/OS User Guide.
Multiple values for the DAYS and WDAYS parameters must be specified in a single statement separated by commas.
For SMART Tables, to update parameters defined in RBCs (DAYS, WDAYS, and so on.) or to change the Schedule RBC name, selection parameter RBC must be specified.
An RBC name of ‘*’ cannot be changed, and an RBC name cannot be changed to ‘*’. To delete a rule-based calendar and all of its corresponding job scheduling definitions from the SMART Table Entity, specify the name of the RBC to be deleted in the RBC selection parameter and specify a null RBC update parameter.

The RBC parameter cannot be used to add new rule-based calendars to SMART Table Entity definitions.
For parameters TIMEFROM, TIMEUNTIL and DUE-OUT, the hhmm value can be preceded by a + or -. This indicates that the specified hhmm value is to be added to or subtracted from the existing (non-blank) hhmm value in the FROM, UNTIL, DUE OUT parameter in the job scheduling definition.
If you want to run the CTMTBUPD utility through Control-M scheduling, and any of the utility control statements contains the string "%%" (such as SETVAR), you must specify the AutoEdit statements %%RESOLVE OFF and %%RESOLVE ON before and after the control statement, respectively.

Parent Topic

CTMTBUPD Parameters