Troubleshooting and FAQs › Frequently Asked Questions › Setting Up Jobs

Setting Up Jobs

How can I specify a job to run on all nodes in a cluster at the same time?

First, use the SCHEDULE CREATE command to create a new job to run on one node. Then use the SCHEDULE COPY command to create additional clones of that job for each CPU. If you specify a /GROUP qualifier when you create the job, you can copy the group and run all jobs in the group at the same time. For example:

SCHEDULE> CREATE /GROUP=group-name /CLUSTER_NODE=node1/PROMPT
  (You will be prompted for additional information)

SCHEDULE> COPY job-number /CLUSTER_NODE=node2
SCHEDULE> COPY job-number /CLUSTER_NODE=node3
SCHEDULE> COPY job-number /CLUSTER_NODE=node4
    :
    :
SCHEDULE> RUN /GROUP=multijob
SCHEDULE> SHOW JOB/GROUP=multijob

How do I set up a job to run every six hours, Monday through Friday?

Use the following command to create the job:

SCHEDULE> CREATE "vms-command"/INTERVAL="+0 6"/DAYS=(ALL,NOSAT,NOSUN)

If you are running in an OpenVMS Cluster, you can add the /CLUSTER qualifier to control on which OpenVMS Cluster node the command executes.

I have scheduled a job that requires mail notification. The job runs okay, but no mail is received. What is the problem?

Ensure that the ENQLM quota of the account that the manager runs on is at least 300.

How do I stop a continuous job?

Enter the following command:

SCHEDULE> MOD job-name/NEXT=NEVER/NOINT

        or

SCHEDULE> HOLD job-name

What happens when daylight savings time ends? Will a job that runs at 23:00 run again when the time falls back an hour?

Setting the clock back an hour should not affect scheduled jobs that have an interval greater than or equal to HOURLY. The reason is that the manager calculates the next time a job will run as soon as the job is ready to run. Moving the clocks ahead an hour also has no effect on jobs, because a job will run if its scheduled time is earlier than the current time.

Examples

• A job is scheduled to run every night at 23:00. At 23:00 tonight, just before it starts running, the job sets its next time to run for 23:00 tomorrow night.
• Assume you set back the clock one hour at 23:00. This will not affect the job, because its scheduled time is 23:00 tomorrow night. It will not run twice in the same night.
• At 2:00 A.M. you set your clock ahead to 4:00 A.M. Jobs scheduled to run at 3:00 A.M. start running immediately, because 3:00 A.M. is earlier than 4:00 A.M.

I have a job that must run on Wednesday of the third week of the fiscal month, except when the fiscal month has five weeks. In that case, the job should run on the Wednesday of the fourth week. How do I specify this?

Use the following interval:

/INTERVAL="F M -D11 HH:MM"/DAYS=(WED,NONE)  

This interval specifies the last day of the fiscal month minus 11 days, which is the second-to-last Wednesday of the fiscal month. When you need to specify this type of interval, use your fiscal calendar to calculate the number of days to specify.

I have a complex job that needs to restart if the system fails or if the job fails because of an error at the step last marked with SCHEDULE SET RESTART_VALUE STEP_NAME. How do I restart at this step if the job fails because of an error?

Start every job with the following line:

$ IF P1 .NES. "" THEN GOTO P1

When you need to restart, use the following command:

$ SCHEDULE RUN my_job/PARAM=step_01 

Step_01 is the step where the job should restart.

What should I do when jobs do not start at their scheduled time?

Stop the manager. Turn on DEBUG on the manager and view the log. (DEBUG can be enabled in the manager startup procedure, or by the SCHEDULE SET DEBUG ON command.)

DEBUG creates a file named NSCHED$:nodename.LOG. The log file contains useful information about what is happening with the manager. Also, use the SCHEDULE SHOW STATUS to view other useful information.