I think that JES2 z/OS V2.2 is starting to include some basic job scheduling functions.
Configuring and activating job groups There is a new JES2 initialization statement and command, GRPDEF, that controls job group processing. Keywords on GRPDEF control the number of data areas available for group processing and the number of jobs that can run concurrently. Data for job groups is stored in a data area called a ZJC. The number of data areas needed to represent a group is dictated by the complexity of the group. One data area is needed for the group, one for each job in the group, and one for each dependency. The 4 job group described earlier would require 1 ZJC for the group, 4 for jobs in the group, and 4 for each of the dependencies, for a total of 9 data areas. The number of ZJCs (ZJCNUM=) is defaulted to 1000, allowing limited usage of the function. The value can be configured from 6 (only useful for basic testing) to 500,000. The other configuration keyword on GRPDEF is the number of concurrent jobs that can be configured in a single job group. This is the CONCURRENT_MAX= keyword. By default, the limit is set to zero, disabling the function. To allow users to use concurrent execution, this needs to be configured to a higher value. Valid range is 0 to 200. All the functions of job groups are only available when JES2 is in the z22 $ACTIVATE mode. The current $ACTIVATE mode can be displayed using the $D ACTIVATE command. The command also list any reasons why you cannot activate to z22, if you are in z11 mode. There is also a health check that reports if you are not in z22 mode and what is needed to activate to z22 mode. In general, all members must be running z/OS 2.2 or later. SPOOLDEF CYL_MANAGED=ALLOWED must be set, and the checkpoint data sets have to be large enough to hold the larger data areas. Doing a $ACTIVATE to z22 mode also enables a number of other functions in JES2 2.2, such as increased limits for checkpoint data, dynamic changes to the checkpoint size, and a large cache for spool space allocations. JES2 can be retroactivated to z11 mode by the $ACTIVATE command, but to do this, there can be no job groups defined in the system Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Jesse 1 Robinson > Sent: Friday, September 15, 2017 12:14 PM > To: [email protected] > Subject: Re: Can you run multiple jobs with the same job name at the same > time on JES2? > > I do sympathize with shops that cannot afford a highfalutin job scheduling > package. I've heard of fairly cheap alternatives although I have no > recommendations. WLM should help with managing batch load. > > The most promising new mechanism is the one (being) built into JES2 itself. > It's designed to handle the serialization function--even fairly complex > relationships--not just overall system load. You have to get current to > implement it, but once there the price is attractive. ;-) > > . > . > J.O.Skip Robinson > Southern California Edison Company > Electric Dragon Team Paddler > SHARE MVS Program Co-Manager > 323-715-0595 Mobile > 626-543-6132 Office ⇐=== NEW > [email protected] > > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Tom Marchant > Sent: Friday, September 15, 2017 11:11 AM > To: [email protected] > Subject: (External):Re: Can you run multiple jobs with the same job name at > the same time on JES2? > > On Fri, 15 Sep 2017 11:26:53 -0500, David G. Yeager wrote: > > >If there is one thing I've learned from following these threads is > >that every shop is different. If we ran (could afford) Thru-Put > >manager , we wouldn't rely on single threading same name jobs, but we > >do it , not for order , so much as to limit "thruput", because we need > >a poor man's solution being poor men. > > Have you considered WLM managed Initiators? > > -- > Tom Marchant > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
