Control-M for z/OS - How to force a job from a mainframe CONTROL-M on a remote CONTROL-M (mainframe or distributed) - INCLUDES VIDEO
Knowledge Article
Control-M for z/OS - How to force a job from a mainframe CONTROL-M on a remote CONTROL-M (mainframe or distributed) - INCLUDES VIDEO
Control-M for z/OS - How to force a job from a mainframe CONTROL-M on a remote CONTROL-M (mainframe or distributed)
Control-M for z/OS
Control-M for z/OS
CONTROL-M for z/OS version 9.0.00 and above
Control-M for z/OS
Control-M for z/OS
CONTROL-M for z/OS version 9.0.00 and above
Control-M for z/OS
Control-M for z/OS
CONTROL-M for z/OS version 9.0.00 and above
It is possible to order on any CONTROL-M mainframe or any CONTROL-M distributed a predefined JOB from a CONTROL-M mainframe (CONTROL-M for z/OS) under condition?
Starting with CONTROL-M for z/OS version 9.0.00 (mainframe) there is a postprocessing action DO REMFORCE command that allow to order a job on another CONTROL-M through a CONTROL-M/Enterprise Manager 900. This feature is mentioned in page 5 of the INCONTROL for z/OS 9.0.00 Release Notes (July 2015) http://documents.bmc.com/supportu/documents/06/61/450661/450661.pdf QM0AAT86992 Dynamic job ordering on a remote Control-M Server: Ability to order jobs on remote Control-M/Servers by setting an on/do action in a job to trigger another job, and pass variables as a part of the order operation.
PREREQUISITE: - All the CONTROL-M involved AND the CONTROL-M/Enterprise Manager must be at level 900 or higher. - All the CONTROL-M for z/OS involved must be compatibility mode 900. &ILPREFA.PARM(IOAPARM) section CMODE and parameter MODECTx=900
NOTES ON IMPLEMENTATION: - The OWNER field of the SCHEDULE definition that will run the DO REMFORCE must specify a known/authorized account on the CONTROL-M/Enterprise Manager. If the account emuser is being used, set it in upper case in the schedule definition: EMUSER - The CONTROL-M name field set in the DO REMFORCE parameters must be identical to the CONTROL-M server name defined in the CONTROL-M/Enterprise Manager. Respect the lower/upper case! Example :em900test is not the same as EM900TEST! - If necessary, to allow entering lower cases in SCHEDULE definition, set the following variable in the PROFILE : SZUMLCM =Y