

Scheduling Work › Work Scheduling › On-Request Scheduling › RUN Command
RUN Command
The RUN command is used to request a job without verifying the availability of input requirements or performing the updates that normally follow successful job completion.
Use of the RUN or RUNH command causes a job to be brought into the request queue for scheduling. If workload balancing is being used, the job runs in CA WA CA 7 Edition class 9.
The following normal scheduling activities of CA WA CA 7 Edition are bypassed:
- Verification of input requirement availability.
- Construction of postprocessing workstation networks.
- Database index entry updates for newly created output data sets.
- Prior-run queue updates.
- Scheduling of job or data set triggered jobs.
- Requirements are not satisfied for normally scheduled jobs.
- Updating of database "last run" value.
The following normal scheduling activities occur:
- The appropriate LTERM is prompted if the job becomes late.
- The appropriate LTERM is notified when the job completes.
- The RUNLOG is updated.
Copyright © 2015 CA Technologies.
All rights reserved.
 
|
|