Commands › RUN, RUNH Command › RUN Usage Notes

RUN Usage Notes

The following normal scheduling activities of CA WA CA 7 Edition are bypassed:

• Verification of input requirement availability.
• The JCL-OVRD and VERIFY (from the JOB panel) are ignored.
• Scheduling of output workstation networks.
• Database index entry updates for newly created output data sets.
• Prior-run queue updates.
• Posting of job and data set dependencies. This posting includes mutually exclusive job dependencies.
• Scheduling of job or data set triggered (AUTO) jobs.
• #JCL statement in JCL. The statement is taken out, but the override indication is not done.

The following normal scheduling activities occur:

• If the job becomes late, the appropriate LTERM is prompted.
• The appropriate LTERM is notified when the job completes.
• Run log is updated when the job completes or is restarted after a failure.

If TYPE=RES is specified in the RUN command, the CA WA CA 7 Edition restart facilities, QM.4 panel, or RESTART command can be used to restart or rerun the job.

If workload balancing is used, the job is run under the default WLB class for RUN if the CLASS= keyword is not specified.

Note: For more information about the RUNCLASS parameter on the OPTIONS statement in the initialization file, see the Systems Programming Guide.

REF and FROMNODE are reserved keywords that are not considered valid input unless generated by CA WA CA 7 Edition internally. These keywords cannot be coded on online, batch, or trailer terminal transactions. They are reserved for special functions but are described here because they can occur in master station messages.

If REF is specified, the job does not wait for restart in the request queue following abnormal job completion.

All cross-platform jobs must be defined in the CA WA CA 7 Edition database, because selected information for each job is contained in the cross-platform job definition. As a result, cross-platform jobs cannot be added to the database through the RUN(H) command.