Cisco Cisco Workload Automation 6.3 User Guide
172
Jobs and Job Groups
Defining Jobs Interface
FTP User – Specify a user from those defined to CWA that has an associated password to log on to the DataMover
server. A user account may not be necessary if the DataMover server offers Anonymous login.
server. A user account may not be necessary if the DataMover server offers Anonymous login.
Anonymous – Select this option if you know that the remote DataMover server has been configured to accept this
option. Using anonymous as a DataMover login does not normally require a user account and password. You must
supply a CWA user with an email account before using this option.
option. Using anonymous as a DataMover login does not normally require a user account and password. You must
supply a CWA user with an email account before using this option.
Tracking Section
In the Tracking section, select a method to determine that a job has completed. Four options are available:
External – This option requires an external application or user to signal that the DataMover task completed.
Exit code – This option bases the status of the job on the success or failure of the DataMover operation.
Scan Output: Normal String – If you select this option, type a text string in the field below that signals a job
completed normally if the text string appears in the job’s output.
completed normally if the text string appears in the job’s output.
Scan Output: Abnormal String – If you select this option, type a text string in the field below that signals a job
completed abnormally if the text string appears in the job’s output.
completed abnormally if the text string appears in the job’s output.
Duration Section
In the Duration section, specify the time parameters for job completion. These parameters are used to send an alert to
the console if a job is not completing as expected.
the console if a job is not completing as expected.
Estimated – This value configures the forecast next to the Job Activity pane.
Minimum – If the job completes before the specified number of minutes, an alert can be created to notify the
operator.
operator.
Maximum – If the job completes after the specified number of minutes, an alert can be created to notify the operator.
Effective Date Dialog
The Effective Date dialog appears after either modifying the parameters of a job or job group contained in one of the
compiled schedules or modifying a calendar used by one of the jobs contained in the compiled schedules. From this
dialog, you specify the date when the changes should apply. The Effective Date
compiled schedules or modifying a calendar used by one of the jobs contained in the compiled schedules. From this
dialog, you specify the date when the changes should apply. The Effective Date
dialog only appears if you are connected
to the master.
This dialog contains the following elements:
Scheduled Dates – Displays all dates in the compiled production schedule. Those dates in the compiled schedule
that coincide with the dates associated with the modified job or calendar are displayed in bold type. If there are no
bolded dates than the job or calendar is not used on any of the dates that have already been compiled. Select one
of the listed dates to be the Effective Date.
that coincide with the dates associated with the modified job or calendar are displayed in bold type. If there are no
bolded dates than the job or calendar is not used on any of the dates that have already been compiled. Select one
of the listed dates to be the Effective Date.
Effective Date (Web client only) – Displays the date you selected from the
Scheduled Dates list.
If the job is already in the schedule and has just been modified, all instances of the job that have not yet run before
the effective date will not reflect the change. All existing schedules going forward from the selected effective date,
will be recompiled to account for the modifications to the job or calendar. The default effective date is the first date
listed in the Scheduled Dates
the effective date will not reflect the change. All existing schedules going forward from the selected effective date,
will be recompiled to account for the modifications to the job or calendar. The default effective date is the first date
listed in the Scheduled Dates
list that the job will run on.
Start today’s repeating job(s) now – Displayed when the job or group has a designated number of times to repeat.
Normally, a job or group will begin repeating at midnight if no time window is specified. By selecting this option, you
can start the first repeating instance as soon as the job or group is added to the production schedule; otherwise, it
is possible that no instances of the repeating job will be added for today if the number of repeats completed between
midnight and the current time configured.
Normally, a job or group will begin repeating at midnight if no time window is specified. By selecting this option, you
can start the first repeating instance as soon as the job or group is added to the production schedule; otherwise, it
is possible that no instances of the repeating job will be added for today if the number of repeats completed between
midnight and the current time configured.
Note: Any instances of a job that has not yet run will be replaced.