How are Job Sysout's managed on Control-M Agentless Remote Hosts connected through WMI on Microsoft Windows?
Knowledge Article
How are Job Sysout's managed on Control-M Agentless Remote Hosts connected through WMI on Microsoft Windows?
How are Job Sysout's managed on Control-M Agentless Remote Hosts connected through WMI on Microsoft Windows?
Control-M/Agent for UNIX and Microsoft Windows
Control-M/Agent for UNIX and Microsoft Windows
Control-M/Agent for UNIX and Microsoft Windows
Agentless Remote Host
Control-M/Agent for UNIX and Microsoft Windows
Control-M/Agent for UNIX and Microsoft Windows
Control-M/Agent for UNIX and Microsoft Windows
Agentless Remote Host
How are Job Sysout's managed on Control-M Agentless Remote Hosts connected through WMI on Microsoft Windows?
- Control-M manages job sysouts on Agentless Remote Hosts running Microsoft Windows using Windows Management Instrumentation (WMI) through a shared directory. - When defining the Remote Host from the Control-M Configuration Manager, or when defining the Remote Host from the Control-M/Server command line ctmhostmap, the sysout directory paramater is required. - The sysout directory on the remote agent is used to temporarily store the sysout on the remote machine. - The sysout is created as one of the temp files ( .log) on the Remote Host. It's then sent to the Control-M/Agent upon job completion, where it is processed (extracting the job's exit return code). - If there are many large sysouts, consideration should be given to using a Control-M/Agent instead of Agentless technology as there is a impact to network bandwidth when moving the sysout from the Remote Host to the Control-M/Agent.
Additional Information: Customers viewing this solution may find value in the following self-help Connect with Control-M video.
Legacy ID:KA317769
Control-M/Agent for UNIX and Microsoft Windows
Control-M/Agent for UNIX and Microsoft Windows
Control-M/Agent for UNIX and Microsoft Windows
Agentless Remote Host