You can define a Remote Execution (PROXY_JOB) job to run commands to a remote UNIX, HP Integrity NonStop, or OpenVMS computer through Telnet or Secure Shell (SSH2).
To run these jobs, your system requires CA WA Agent for UNIX, Linux, or Windows and CA WA Agent for Remote Execution. The CA WA Agent for Remote Execution supports only remote target environments of UNIX, HP Integrity NonStop, and OpenVMS.
Required Statements
To define a Remote Execution job, you must specify the following statements:
Optional Statements
You can specify the following optional statements for a Remote Execution job:
We recommend that you set up a job class and possibly a job class map for Remote Execution jobs (Verb: RUN, Subverb: PROXY) in the agentparm.txt file with the number of initiators set to match the proxy.maxSubmitConnections value (default of 4). This method causes the waiting jobs to have a status of ‘Waiting for Initiator’. Without the job class, the waiting jobs appear as hanging in the ready queue.
Note: For more information, see the CA Workload Automation Agent for Remote Execution Implementation Guide and the CA Workload Automation Agent for UNIX, Linux, or Windows Implementation Guide.
Example: Run Commands to Get a List of Files and Store the List
This example runs query commands against a particular directory, /tmp/spool1/, to retrieve a list of the files present, the user name running the commands, and the current date. This data is stored in the non-default spoolfile location of /tmp/spool2.
AGENT PROXYAGENT REMOTE_TARGET UNIXEndpoint REMOTE_COMMAND 'ls' REMOTE_COMMAND 'whoami' REMOTE_COMMAND 'date' SUBMIT_MODIFIER 'cd /tmp/spool1/' SPOOLFILE '/tmp/spool2'
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|