Previous Topic: Running Requests That Depend on Other Requests (RELEASE)Next Topic: Running Requests in Classes (CLASS)


Examples

You keep your department’s master schedule up to date. Each employee has a data file for his or her own schedule. When someone’s schedule changes, that person notifies you, and you run an EXEC called NEWSCHED to create a new master schedule. You can automate this procedure by writing an EXEC called CHKDATA to check the data files and then run NEWSCHED if any employees changed their data files since the last check. Set up a job called NEWSCHED to run as a dependent or release request:

vmsched schedule newsched newsched (release louisa

This command schedules a request called NEWSCHED to run on your user ID (GREGK) when released by user ID LOUISA. The first newsched is the name you give the request; the second is the command line for your NEWSCHED EXEC.

Have the CHKDATA EXEC execute a command if any employees updated their files. This command runs the request NEWSCHED that you scheduled to be released by user ID LOUISA on user ID GREGK. This command must be entered by the user ID specified after the release option on the SCHEDULE command above (LOUISA):

vmsched release gregk newsched

Finally, schedule a request called CHKDATA to run the CHKDATA EXEC at 6:00 a.m. every day:

vmsched schedule chkdata chkdata (at 06:00:00 again daily