SAS 9.1.3 Intelligence Platform: System Administration Guide

Using an Operating System Scheduling Server R Canceling a Scheduled Flow on a z/OS Operating System Scheduling Server 217
3 If the specified start date does not comply with the recurrence criteria, then the
initial execution occurs on the first date following the start date that does comply
with the recurrence criteria.
For example, suppose you create a schedule on Friday, April 1, for a recurring
job that is to run only on weekdays, and you specify a start date of Sunday, April
3. The initial execution will occur on Monday, April 4.
How Operating System Scheduling Works on z/OS Systems
When you schedule a flow, Schedule Manager creates the following files:
3 a Restructured Extended Executer (REXX) program called
RunFlow_yyymmddhhmmsssss.rex, which submits each batch job to run on the
requested schedule.
3 a file called jobname.status, which contains information about the status of the
job.
3 the following files, each of which invokes the REXX program to log the job status:
3 logstart_jobname, which is executed as the first step of each job.
3 logend_jobname, which is executed as the last step of the job if all previous
steps have a return code of 0.
3 logfail_jobname, which is executed as the last step of the job if any of the
previous steps has a return code other than 0.
3 flowname.cmd, which contains the statements that execute the program for the
flow. This file is passed to the at command when the time event trigger occurs.
3 flowname.log, which contains the log information for the flow.
3 flowname.status, which contains the current status of the flow.
The files are written to a subdirectory called username.flowdefname in the Control
Directory that was specified in the operating system scheduling server definition.
Manually Submitting a Flow for Execution on a z/OS Operating System
Scheduling Server
Note: On z/OS, unexpected results can occur if you manually submit a flow without
having selected Manually Schedule when you scheduled the flow. R
If you need to manually submit a flow that has been scheduled on a z/OS operating
system scheduling server, follow these steps:
1 Change to the directory where the flow’s files are located (/outdir/username/
flowdefname), where outdir is the value of the Control Directory attribute in the
operating system scheduling server definition.
2 At the USS prompt, type a command with the following syntax:
RunFlow_yyymmddhhmmsssss.rex runonce|start
Specify runonce if you want to run the flow just once, or specify start if you want
to resume a recurrence that was specified for the flow.
Canceling a Scheduled Flow on a z/OS Operating System Scheduling
Server
If you need to cancel a flow that has been scheduled on a z/OS operating system
scheduling server, follow these steps: