Define agent jobs to CA WA CA 7 Edition using top line commands DB.11 or AGJOB or FUNCTION ‘A’ from the DB menu. Another option is to convert XPJOB jobs using the conversion utility.
Note: For more information, see the CA WA CA 7 Edition Database Maintenance Guide and the CA WA CA 7 Edition Interface Reference Guide.
Create the CA WA CA 7 Edition agent job PARMLIB member. Each job type has its own set of parameters that can be coded. For example, an FTP job indicates the options to perform the FTP data transmission: what is the server, upload/download options, files, and so on. A monitor job indicates what to monitor and the thresholds to use. A DB Stored Procedure (DBSP) job indicates the stored procedure to execute. The conversion utility creates PARMLIB members for converted UNIX and NT jobs.
Note: For more information, see the CA Integrated Agent Services User Guide.
After the job definition and its parameters are defined, execute the LJCK command against the job defined to help ensure that no syntax errors are encountered. This command validates the parameters. With the LIST=DEBUG option on the LJCK command, you can display a simulated AFM message. The passwords on this output always show SIMULATE, and the user ID is the user ID with which the CA WA CA 7 Edition logon occurred. This user ID can be changed when the actual job is sent to the agent based on the SECURITY AGUSER parameter.
Note: For more information about LJCK, see the CA WA CA 7 Edition Command Reference Guide.
Use normal functions for defining schedules, triggers, and requirements for the agent jobs. In CA WA CA 7 Edition, a job is a job and the relationship of this job is defined the same way as any other job. ARF and VRM resource definitions can apply to the job.
The conversion utility maintains this information for converted UNIX and NT jobs.
Create the CA WA CA 7 Edition agent user ID and password through the AGPSWD command. CA Workload Automation agents typically require that a user ID and password are passed with the job that the agent is to execute.
Although you can refine when to apply a password to the user ID based on agent and job type, we recommend that you try and apply the “keep it simple” principle. The user ID has a four-level lookup that is used to resolve which password is used. The basic lookup involves merely a user ID and a password. In addition to a user ID, you can optionally specify the specific agent, job type, or both. For example, you can have AGENTA and AGENTB, and on these agents, the same user ID, IDZ, is used. On AGENTA, IDZ has password IDA, and on AGENTB, the password is IDB. You can define through AGPSWD command two entries: IDZ going to AGENTA uses password IDA and IDZ going to AGENTB uses password IDB. You can then further qualify that if an FTP job is defined going to AGENTA, make its password IDF. The AGPSWD field completes (user id) IDZ, (agent) AGENTA, (job type) FTP_JOB, and (password) IDF. This process can get complicated, which is why the “keep it simple” rule is suggested!
Also, through security PANEL rule L2DBAPSW, you can secure the AGPSWD command to only those users requiring the access to define or change passwords. Another difference is that to update the password, enter the old password (this requirement differs from XPSWD command). You can enter the AGPSWD through a CA WA CA 7 Edition batch interface, which can make it easier when you have restricted this access to personnel who are not familiar with the CA WA CA 7 Edition interface.
The conversion utility creates agent user ID and passwords for existing UJMA user IDs and passwords.
Note: For more information, see the CA WA CA 7 Edition Database Maintenance Guide.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|