Legacy ID:KA345802
When a job completes its execution on a remote host in Agentless mode, the job’s output (Sysout) is moved by default to the Control-M/Agent host that submitted the job. Alternatively, the Sysout transfer from the remote host to BMC Control-M/Agent can be disabled in case Sysout analysis is not required.
If the job’s Sysout is very large, and Sysout analysis is required, consider using a conventional Control-M/Agent instead to avoid increasing network traffic. The decision on whether to use the Agentless technology or a conventional agent should be taken in this case based on the network bandwidth capacity and load.
The system paramaters for Agentless to configure the method for handling the sysout include:
1. BMC Control-M/Agent can be configured not to copy Sysout files from Agentless remote hosts to the Control-M/Agent computer when those jobs completed.
- Configure the "RJX_DOWNLOAD_SYSOUT" parameter value to N in the BMC Control-M Configuration Manager. (CCM)
- When this mode is configured, the view Sysout action is not available for the agentless jobs managed by this BMC Control-M/Agent and ON statement defined in the jobs are ignored.
2. BMC Control-M/Agent can configured to keep Sysout files on Agentless remote hosts when those jobs completed.
- Configure the "RJX_KEEP_SYSOUT" parameter value to Y in the BMC Control-M Configuration Manager.
3. BMC Control-M Agent can also performed Sysout handling post processing actions, such as copy or move Sysout, on remote hosts.
- By default, Sysout handling post processing actions are performed on the BMC Control-M/Agent that submit and track the jobs.
- Configure "RJX_COPY_SYSOUT_REMOTE" parameter value to Y in the BMC Control-M Configuration Manager.
Related Products:
- Control-M/Agent for UNIX and Microsoft Windows