SDSF folks at Rocket... job groups need some love too. This feature could be very useful when used in ad-hoc job suites or workflows. Ones that are too infrequent to warrant going into the scheduler. Too frequent that submitting one job after another is a bore.
Kicking off a chain and letting jobs do their magic, parallel where parallel is needed, serial where serial is, etc. - KB ------- Original Message ------- On Wednesday, August 17th, 2022 at 6:54 AM, Peter Vels <[email protected]> wrote: > Roger is correct; you don't need both CONCURRENT statements. In fact, > you'll get an error with two. Note that the syntax is CONCURRENT NAME= > job. > > Also, what does $D GRPDEF show? > If you are seeing CONCURRENT_MAX=0 (which is the default) then change it to > 2 (or more if you like) with command: $T GRPDEF,CONCURRENT_MAX=2 > > > > This worked for me: > > > > //DRCPYFC JOBGROUP > > //DRCPYFC1 GJOB > > // CONCURRENT NAME=DRCPYFC2 > > //DRCPYFC2 GJOB > > //DRCPYFC ENDGROUP > > //* ------------------------------- > > //DRCPYFC1 JOB (ACCT#),'DR COPY ',CLASS=A, > > // MSGCLASS=X,REGION=800M > > // SCHEDULE JOBGROUP=DRCPYFC > > //STUFF1 EXEC PGM=IEFBR14 > > //DRCPYFC2 JOB (ACCT#),'DR COPY ',CLASS=A, > > // MSGCLASS=X,REGION=800M > > // SCHEDULE JOBGROUP=DRCPYFC > > //STUFF2 EXEC PGM=IEFBR14 > > > Regards, > > Peter > > > On Wed, 17 Aug 2022 at 06:52, Roger W Suhr [email protected] wrote: > > > Hi, > > > > Maybe you can try this: > > > > //DRCPYFC JOBGROUP > > //DRCPYFC1 GJOB > > // CONCURRENT NAME=DRCPYFC2 > > > > I'm not sure you need two CONCURRENT statement > > > > Roger W. Suhr > > > > [email protected] > > > > -----Original Message----- > > From: IBM Mainframe Discussion List [email protected] On Behalf > > Of Tom Longfellow > > Sent: Tuesday, August 16, 2022 16:40 > > To: [email protected] > > Subject: Simple JOBGROUP or Simple User > > > > My forehead is bruised from beating it against the wall. I am trying to > > set up a simple JOBGROUP with two simultaneous jobs. Here is my JCL > > (excerpted for brevity) > > //DRCPYFC JOBGROUP > > //DRCPYFC1 GJOB > > // CONCURRENT=DRCPYFC2 > > //DRCPYFC2 GJOB > > // CONCURRENT=DRCPYFC1 > > //DRCPYFC ENDGROUP > > //* ------------------------------- > > //DRCPYFC1 JOB (ACCT#),'DR COPY ',CLASS=A, > > // MSGCLASS=X,REGION=800M > > // SCHEDULE JOBGROUP=DRCPYFC > > //* stuff to do > > //DRCPYFC2 JOB (ACCT#),'DR COPY ',CLASS=A, > > // MSGCLASS=X,REGION=800M > > // SCHEDULE JOBGROUP=DRCPYFC > > //* more stuff to do > > > > Jes is rejecting this masterpiece with: > > > > $HASP100 DRCPYFC ON INTRDR FROM TSU17899 > > TECHXXX > > $HASP1110 DRCPYFC -- Illegal JOBGROUP card - card not > > valid within JOBGROUP > > $HASP1110 DRCPYFC -- Illegal JOBGROUP card - card not > > valid within JOBGROUP > > IRR010I USERID TECH905 IS ASSIGNED TO THIS JOB. > > $HASP1111 DRCPYFC -- ENDGROUP card - JOBGROUP DRCPYFC contains errors > > > > I tweak, I read the manual (many times). But must be missing something. > > It did run once, but sequentially - not concurrently. I added CONCURRENT > > cards and this is where I am. > > > > What funny little JES syntax did I miss? I modeled this on the sample in > > the book. > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, send email > > to [email protected] with the message: INFO IBM-MAIN > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to [email protected] with the message: INFO IBM-MAIN > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
