Cisco Cisco Workload Automation 6.3 Betriebsanweisung
26
Working with OS/400 Jobs
File Dependencies
—
*CURRENT
– Specifies that the current value be used by the submitting job.
—
*JOBD
– Specifies that the same value in the job description be used by the submitted job.
—
*SYSVAL
– Specifies that the system value for the spooled file action (QSPLFACN) be used by the submitted job.
—
*KEEP
– Specifies that when the job ends, the spooled files are kept with the job and that the status of the job
is updated to indicate that the job has completed.
—
*DETACH
– Specifies that when the job ends, the spooled files are detached from the job and the job is
removed from the system.
File Dependencies
The file dependency function for OS/400 agents supports all conditions (
EXISTS
,
SIZE
, etc...) for files under the
Integrated File System and File Type Objects in the library (QSYS File System).
The following are examples of the format required for each file system:
Integrated File System
/dir1/dir2/file1
QSYS File System
/QSYS.LIB/<library>.LIB/<file>.FILE/<member>.MBR
where
<library>, <file> and <member> are replaced with the appropriate values.
Monitoring Job Activity
The parameters of OS/400 jobs are defined within the OS/400 environment but the scheduling of these jobs is controlled
by CWA. Jobs are launched on a concurrent request by concurrent request basis. CWA watches for the completion of
each concurrent request and any other change in the status of the concurrent request. Once the process completes,
CWA determines the completion status and can return the output and log of the process. The status of a CWA OS/400
job with multiple concurrent requests is determined by the concurrent request that completed last.
by CWA. Jobs are launched on a concurrent request by concurrent request basis. CWA watches for the completion of
each concurrent request and any other change in the status of the concurrent request. Once the process completes,
CWA determines the completion status and can return the output and log of the process. The status of a CWA OS/400
job with multiple concurrent requests is determined by the concurrent request that completed last.
Controlling Adapter and Agent Jobs
Scheduler provides the following job control capabilities for either the process currently running or the job as a whole:
—Hold a job waiting to run.
—Abort an active job.
—Rerun a job that completed.
—Make last minute changes to a job.
—Delete a job instance before it has run.
Holding a Job
Adapter/agent jobs are held in the same way as any other Scheduler jobs.
Adapter/agent jobs can only be held before they are launched. Once a job reaches the Adapter/Agent system, it cannot
be held or suspended.
be held or suspended.