You can use the Send Event dialog to schedule an event for the selected CA Workload Automation AE job or jobs.
This dialog contains the following fields:
Displays the selected jobs or box jobs on which you can act. This field is read-only.
Specifies the event to send for the selected jobs or box jobs. Depending on your selection here, the appropriate associated fields are displayed in the dialog.
The following options are available:
Sends a STARTJOB event to start the selected job, but only if its other starting conditions are satisfied and it is not already running. This action ignores date and time starting conditions.
Sends a FORCE_START_JOB event to start the selected job regardless of whether any of its starting conditions have been met.
Sends a JOB_ON_HOLD event to change the selected job's status to ON_HOLD. A job that is on hold cannot be started. You cannot place a job on hold if it has a STARTING or RUNNING status.
Sends a JOB_OFF_HOLD event to take the selected job off hold. If the selected job's starting conditions have been met, the job will be started.
Sends a JOB_ON_ICE event to put the selected job on ice, which is the functional equivalent of deactivating the job definition. You cannot put a job on ice if it has a STARTING or RUNNING status.
Sends a JOB_OFF_ICE event to take the selected job off ice, which is the functional equivalent of reactivating the job definition. When you take a job off ice, it will start the next time its starting conditions are met.
Sends an ON_NOEXEC event that instructs the scheduling manager to bypass the job during the scheduled run, which means the job is not executed. Any downstream dependent jobs are executed as scheduled.
Sends an OFF_NOEXEC event instructing the scheduling manager to allow the job to be executed during the next scheduled run.
Sends a KILLJOB event to terminate the selected job. The action taken by the KILLJOB event depends on the job type and the type of server (UNIX or Windows) on which the job is running.
Sends a RELEASE_RESOURCE event to release the resources that are being held by a terminated job. This event is applicable only for jobs with a dependency on renewable resources that have been defined with the FREE=N attribute. This command is not available for box jobs.
Sends a response to an i5/OS agent notification requesting information required for the i5/OS job run to continue. If a job goes into a state where it is waiting for a response, the i5/OS agent sends a notification requesting a reply. The job will not resume running until the reply has been sent. When you select this option, you must also complete the Reply field.
Sends a SEND_SIGNAL event to send the value specified in the Signal field to the selected job running on a UNIX server. When you select this option, you must also complete the Signal field. This event is ignored if the job is running on a Windows server.
Note: The character limit is determined by the agent and platform.
Sends a CHANGE_PRIORITY event to change the selected job to the priority specified in the associated field. The priority you specify represents the selected job's priority relative to all jobs in the queue. The lower the number, the higher the priority. This command is a one-time priority override. If a job has started, the priority only changes for the next run. If a job has started and is in a queue, the priority changes immediately. When you select this option, you must also complete the Priority field.
Limits: 0-99, where 0 indicates to run the job immediately
Sends a CHANGE_STATUS event to change the status of the selected job to the status selected from the associated list. When you select this option, you must also complete the Status field. You should not typically use this option because the scheduling manager handles job state changes internally. If you use this option, you must send another CHANGE_STATUS event to revert the status to its original setting.
Sends a COMMENT event to attach the text you enter in the Comment field to the selected job.
Default: Start
Indicates the priority for sending the event.
Changes to display one or more fields relevant to the Event Type selected. For example, if a Send Signal event type is selected, this field displays as Signal and accepts a UNIX signal to send to the UNIX server. If a Change Status event type is selected, this field displays as Status and accepts a status type.
Specifies text to associate in the database with the COMMENT event you are sending. This field is for documentation purposes only. For example, you may want to provide an explanation of why an action was necessary.
(Optional) Defines the date at which to send the specified event. Clicking 
opens the Date Picker, so you can select a date to populate the Date field.
Limits: Varies depending on the selection for Format Locale in the My Profile dialog
Example: 7/16/09
Default: The current date
(Optional) Defines the time at which to send the specified event.
Limits: 24 hour format
Example: 05:15
This dialog contains the following buttons:
Sends the event and closes the dialog.
Discards your settings and closes the dialog.
|
Copyright © 2013 CA.
All rights reserved.
|
|