Tim,
You might like to look at Jol's Networking Facility. Jol is an English
like enhancement language for Z/OS. It also works on Windows, Linux and
OS/2.
The main Jol Website is here: www.Jol-Oscar.com
Re Jol Networking:
You can see the documentation here, with pictorial representations of
the Network :
http://www.members.iinet.net.au/~mitsu2/JolWebManuals/SHD_Frame.html
Creating a simple network, can be done with this simple code.
NETWORK ONE;
SUBMIT JOB1;
SUBMIT JOB2;
SUBMIT JOB3 AFTER JOB1 & JOB2 ENDED;
ENDNET;
Symbolic Parameters and Variables can be passed from Job to Job too.
More documentation for scheduling and networking can be found here:
http://start.oscar-jol.com/documentation/technical-how-to-use#Scheduling
Jol has full Symbolic Variable processing, just like PL/I or any other
high level language. See the Assign Statement here:
http://www.members.iinet.net.au/~mitsu2/JolWebManuals/Jol_Instructions_With_Frames.html
Here's an example of submitting JCL depending on the day.
Statement Number Jol Code
1 IF %DAY='FRIDAY'
THEN DO ; /* Weekly Processing */
2 SUBMIT '//JOB1 JOB etc......'
'//STEP1 EXEC WKPROC,'
'// SPACE=''(CYL,10)''' ;
3 END ;
4 ELSE DO ;
5 SUBMIT '//JOB1 JOB etc......'
'//STEP1 EXEC DAYPROC,'
'// SPACE=''(CYL,5)''' ;
6 END ;
Explanation:
Statement 1 Checks Jol's calendar to determine if the day is Friday. If
it is FRIDAY, it initiates the DO group (statement 2).
Statement 2 SUBMIT's the following JCL on Fridays:
//JOB1 JOB....etc
//STEP1 EXEC WKPROC,
// SPACE='(CYL,10)'
Statement 3 END's the DO group that was started by statement 1.
Statement 4 Initiates another *DO *group if today is not Friday.
Statement 5 SUBMIT's the following JCL on days /other than /Fridays:
//JOB1 JOB....etc
//STEP1 EXEC DAYPROC,
// SPACE='(CYL,5)'
Statement 6 END's the DO group started by statement 5.
You can see the power of the language, as well as the ease for networking.
Clem Clarke
Timothy Sipples wrote:
As some other examples, DB2 for z/OS has a task scheduler:
https://www.ibm.com/support/knowledgecenter/SSEPEK_12.0.0/admin/src/tpc/db2z_taskschedulerarchitecture.html
z/OS is UNIX(TM), and of course z/OS UNIX System Services includes cron.
Here's an article describing how to use it:
http://www.ibmsystemsmag.com/mainframe/administrator/systemsmanagement/cron_rexx/
Also, z/OS 2.2 and higher include the new SCHEDULE JCL statement, which is
quite convenient:
http://www.ibmsystemsmag.com/mainframe/tipstechniques/systemsmanagement/SCHEDULE-JCL-statement/
Paul Gilmartin wrote:
Should I assume the two are comparable in capabiity, and neither is
enterprise-worthy, hence the need for third-party products?
There's definitely an important, growing role for industrial strength
job/task scheduling.
--------------------------------------------------------------------------------------------------------
Timothy Sipples
IT Architect Executive, Industry Solutions, IBM z Systems, AP/GCG/MEA
E-Mail: sipp...@sg.ibm.com
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
