Job Management Manager DCL Commands › SCHEDULE> › RUN › Examples

Examples

1. In this example, the hyphen at the end of the DCL command line extends the command to a second command line. The manager runs your job WKLY-RNM immediately. For this run only, the manager puts the job’s output in the file MYDISK:[MYDIR]TEST.LOG.

   SCHEDULE>  RUN WKLY-RNM/OUTPUT=MYDISK:[MYDIR]TEST.LOG-  _
   SCHEDULE> /CLUSTER_NODE=NODE1 
   %NSCHED-I-FLAGSET, Job  WKLY-RNM - Run Requested 
   Workload Scheduler Job 56  (Name: WKLY-RNM Started on node 	NODE1)
    Workload Scheduler Job 56  (Name: WKLY-RNM Completed on node 	NODE1)
   

   The job is run on node NODE1.

   When the job completes, the manager replaces the values for /OUTPUT and /CLUSTER_NODE with the original values for these qualifiers.

2. This example is the same as the first example, but specifies /CONFIRM on the command line. As a result, the manager requests confirmation before running the job.

   SCHEDULE>  RUN WKLY-RNM/CONFIRM/OUTPUT=MYDISK:[MYDIR]TEST.LOG-  
   _SCHEDULE>/CLUSTER_NODE=NODE1 
   Job WKLY-RNM (56, RUN? [No]) YES 
   %NSCHED-I-FLAGSET, Job  WKLY-RNM - Run Requested 
   Workload Scheduler Job 56  (Name: WKLY-RNM Started on node NODE1)
    Workload Scheduler Job 56  (Name: WKLY-RNM Completed on node NODE1)
   

3. This command specifies that the manager run the job on node NODE1. However, the manager is not running on that node, so the software issues a warning message. If the manager was running on NODE1, it would have run the job immediately.

   SCHEDULE>  RUN WKLY-RNM/CLUSTER_NODE=NODE1 
   %NSCHED-I-FLAGSET, Job       WKLY-RNM - Run Requested 
   %NSCHED-W-NOSCHED, No scheduler available to service request