With this release, CA Workload Automation SE supports a variety of job types that can be submitted to CA Workload Automation Agents. These job types include several platforms such as UNIX (LINUX, Sun, and HP) and business applications, such as Data Base, SAP, PeopleSoft, and Oracle. Because each job type requires different information, you must define the job type in the job definition. These new job types are known as AGJOBs. To permit the definition and submission of these job types, specify the keyword AGENTJOB=YES on the initialization file XPDEF statement (the default is NO).
Note: For more information about system initialization and options, see the Systems Programming Guide. For more information about setting up the agent interface, see the Interface Reference Guide.
Working with CA Integrated Agent Services (CA IAS), CA Workload Automation SE invokes CA IAS to build and send the appropriate communication message to execute the job at the agent. CA IAS has several new files in the CA Workload Automation SE JCL procedure to define agent information. Also, you must define a new VSAM file, CA7AGNT, which contains agent job feedback information.
Note: For more information about the new CA IAS files and setup, see the CA IAS Implementation Guide.
The Database Menu panels are updated to let a user select the job type to define. An advanced user can go directly to the job definition panel by entering DB.11 or AGJOB and entering the job type. Here, information about the job's job type and destination is entered. The actual data to send to the destination is defined in a required PARMLIB member, using a control language (C-LANG). C-LANG indicates what to execute and any additional parameters and options to use during the job's execution.
Note: For more information about C-LANG, see the CA Integrated Agent Services User Guide. For more information about agent job and agent password definitions, see the Database Maintenance Guide.
Agent jobs are scheduled and have their requirements and triggers set up like any other CA Workload Automation SE job. You can forecast and manipulate agent jobs like other jobs. When looking at agent jobs in the CA Workload Automation SE panels, the job has its job type denoted in the MAINID or CPU SPEC column as a four-character job type (such as WIN for Windows job type and FTP for an FTP job).
When the agent job is submitted (attached) to the request queue, the agent job stays in that queue until all requirements are met (MCNT=0). Next, the agent job moves into the ready queue until submission occurs. This process is no different from regular jobs. If CA IAS is not available when the job is selected, the job remains in the ready queue with an N-IAS job status. If CA IAS is available, the job is submitted to CA IAS for transmission to the agent. If the agent is not immediately available, CA IAS queues the message until the agent is available. The job shows the status W-AGENT until the agent has received the job.
When the job starts execution at the agent, CA Workload Automation SE receives a job initiation message (through CA IAS) and creates a pseudo-SMF job initialization record. When CA Workload Automation SE processes this record, the agent job is then moved to the active queue. The job stays in the active queue until a job termination record is received, whereby the agent job moves back to the request queue, either in a job failure or job complete status. If the job is successfully completed, CA Workload Automation SE examines any requirements, triggers, or both and takes appropriate action before moving the job to the prior run queue. If the job fails, the job stays in the request queue until the job is restarted or is forced complete.
The CA Workload Automation Agent determines job success or failure. Agent jobs have no CA WA Restart Option restart abilities, and all agent jobs have only one step. The C-LANG statement, EXITCODE, can set the success or failure for agent jobs. Agent jobs have no job definition CONDCODE/RO (condition code/relational operator). Again, the CA Workload Automation Agent determines the success or failure of an agent job execution.
Several commands, such as CANCEL, HOLD, and RELEASE, are updated to interact with CA IAS and the CA Workload Automation Agents. If you enter a CANCEL command for an agent job, CA Workload Automation SE determines where the job is in the queues. If the job is already submitted to CA IAS or to the CA Workload Automation Agent, the CANCEL command builds an appropriate message to cancel the job from the IAS queue or from the CA Workload Automation Agent. A few job types let you enter a HOLD action while the job is executing on the CA Workload Automation Agent (as reflected in the active queue). The RELEASE command removes the hold action.
Also, the LJCK command is updated to verify an agent job to verify that the C-LANG data specified in the PARMLIB can build an appropriate message for the CA Workload Automation Agent. As with XPJOBs, we highly recommend using the LJCK command before sending a job to an agent to verify its correctness.
A number of new commands perform actions to CA IAS or to the CA Workload Automation Agent. The /IAS command performs actions to the CA IAS interface like reconfiguring the agent definition or starting and stopping the CA IAS TCP/IP communications interface.
The /AGENT command communicates with the agents. With this command, for example, you can clear agent log files or shut down the agent. The LAGENT command (List Agents) inquires CA IAS for a list of defined agents and their status. The /DELAGNT command removes data from the CA Workload Automation SE Agent VSAM file based on a specified number of days. All these commands have a new security interface. Secure these commands to the appropriate group.
Note: Because the CA WA Agent is not active on the target platform, CA Workload Automation SE cannot start an agent. If an agent should be started, the operator must start the CA WA Agent on the platform itself.
With agent jobs, you can retrieve the spool files generated by the execution of the job back to CA Workload Automation SE using the AGFILE command. Not all job types have spool file data. This command also lets you see the job feedback data stored in the new CA7AGNT VSAM file.
Note: For more information about commands, see the Command Reference Guide.
Various utilities and reports are updated to support the new agent jobs. For example, the SASSHR11 report now shows the data that was sent to the CA WA Agent, just as it shows the data sent to a Unicenter Agent for XPJOBs.
Note: For more information about reports, see the Report Reference Guide.
A conversion utility can move XPJOBs to AGJOBs for Windows and UNIX job types. This utility is designed to facilitate upgrading a CA universal agent to the new CA WA Agent for UNIX, Linux, or Windows. The conversion utility uses the LJOB command to find all XPJOB jobs defined in the database. With additional input, the utility converts the XPJOB database definition to an AGJOB database definition and builds the appropriate PARMLIB member.
Note: For more information about the conversion process, see the Interface Reference Guide.
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|