|
|
|
|
|
WRN0002 message reports a function in TWS that is not available with Control-M.
EXAMPLE: NDA_CNR_VIP#QTAB_NON_DEQ
AT 0000
EVERY 0100
UNTIL 2359
ONUNTIL SUPPR
ONUNTIL SUPPR: The SUPPRess statements set any job(s) with the SUPPR condition to a state of success once the ONUNTIL time is passed, even though they have not yet started. Control-M handles this condition by following the same rules as ONUNTIL CANC.
suppr: The final job stream state is HOLD if the job stream contains at least one every job. Otherwise the final state is calculated using the normal rules and the jobs with the optiononuntil suppr are considered in SUCC state when the until time occurs, even if their dependencies have actually not been released.
ONUNTIL CANC: The CANCEL command is effective for a job or job stream and is related to jobs that have not yet dispatched. The job or job stream is canceled when the until time specified expires. Any job or job stream that was dependent on the completion of a job or job stream that was canceled runs because the dependency no longer exists in TWS. To handle this with Control-M, it requires a combination to use CTMPSM parameters.
EXAMPLE: With a script on the Control-M Server or Control-M Agent machine with a content of:
Windows: “ctmpsm_script_location”\ctmpsm -UPDATEAJF %2 SETTOOK
UNIX: “ctmpsm_script_location”\ctmpsm -UPDATEAJF $2 SETTOOK
This is an alert mechanism that allows the job to continue. The job or job stream runs when all necessary conditions are met and a notification message is written to the log when the until time elapses. This can be simply addressed using the Control-M Shout options.
Parent Topic |