The CTMBLT utility can create tables in memory (instead of in a scheduling library) and order or force them.
This functionality enables users to order or force jobs to the Active Jobs file without saving Control-M job scheduling definitions in a scheduling library.
To create tables in memory and then order or force them, specify the same parameters as when creating tables in a library.
However, note the following point about the syntax:
|
The MEM-OVERWRITE statement must be specified in this syntax. An order or force action must be specified, followed, optionally, by one of the following date references (in parentheses):
You can also specify a future date. The date may be optionally followed by the /WAIT option, for example, MEM-OVERWRITE=ORDER(yymmdd/WAIT). This causes the job execution to be delayed until the date yymmdd specified, even if all other required run-time criteria (conditions, resources, and so on) are available.
Users who want to save the resultant Control-M job scheduling definitions in a scheduling library can do so by coding OPTION=S. For detail, see Table 95 in CTMBLT General Parameters.
Note: When building a SMART Table containing a SMART Table Entity only, without any job definitions, the EMPTYTBL parameter in the CTMPARM member of the IOA PARM library must be set to Y to be able to ORDER or FORCE the SMART Table.
Note: All error and informational messages produced by the job ordering component (CTMJOB) are written to the same message file (DAPRINT by default) which CTMBLT uses instead of the SYSPRINT DD.
This capability is provided only when invoking CTMBLT services in conversational (BAPI) mode, either
Parent Topic |