For most situations you can choose a trigger type of File close, Job termination, or Job initiation. However, there may be times when the triggering event you want to define is not a system‑initiated even and a logical event may be more suitable. The trigger type of CA Event lets you create these user‑initiated logical events.
Using the executable caevent (provided with CA NSM), you can generate a logical event by executing the caevent command and supplying two command line arguments--the first is the logical event name, and the second optional parameter is an event status code. By running the caevent executable in scripts or using it interactively, the system alerts the CA NSM JM Option to events as they take place.
In addition, since the event name and status code are user‑specified, they can describe any trigger event. For example, the following caevent command sends an event of type caevent, with an event name of bkupnow (a previously defined trigger profile), and a status code of 10 to the CA NSM JM Option:
caevent bkupnow 10
If a defined trigger profile matches these criteria, the trigger trips and the associated message action profile is processed. The message action profile may demand a jobset into the workload automatically or execute a cautil backup command. Message action profiles are flexible enough to meet your needs. For additional information about the caevent command, see the online CA Reference.
Often, events not related to a job need to be tied directly to a job or jobset, such as creation or deletion of a file, completion of a job that ran on another server, or occurrence of an IPL event. These events can be detected by the trigger mechanism in the CA NSM JM Option and can be used to satisfy a job dependency.
For instance, you may not want a payroll job to start until the data file has transferred from another system. You can define a trigger to watch for the creation of the data file and define the payroll job with a predecessor to wait for the trigger.
In another scenario, CA NSM JM Option server SERVA runs a job on system SYSA. CA NSM JM Option server SERVB cannot run a job until the job submitted by SERVA completes. Define a trigger on SERVB to watch for the completion (JOBTERMU) of the job submitted by SERVA, and define this trigger as a predecessor to the job on SERVB.
Note: For additional information about keywords that let you use trigger profiles as predecessors, see the Control Statements for JOBSETPRED and JOBPRED objects in the online CA Reference.
For procedures to schedule using triggers, see Defining Trigger Profiles in the online CA Procedures.
|
Copyright © 2010 CA.
All rights reserved.
|
|