Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

JES3: how to prevent concurrent //*NETs ?

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> JCL & VSAM
View previous topic :: :: View next topic  
Author Message
David Eisenberg

New User


Joined: 15 Nov 2007
Posts: 39
Location: New York

PostPosted: Fri May 01, 2009 10:16 pm    Post subject: JES3: how to prevent concurrent //*NETs ?
Reply with quote

Anyone,

If I want to prevent specific jobs from executing concurrently (assuming that they have different jobnames), I can add a DD statement for a catalogued dataset with DISP=OLD to the //JOBLIB concatenation. Any job that has that DD statement will wait for the previous job to complete. So far, so good.

Is there any equivalent protection in JES3 to prevent concurrent execution of //*NETs, even though the NETs may have different NET ids?

What I'm looking for (I guess) is a way to establish an enqueue at the beginning of a NET which won't be released until the entire NET is complete.

Thanks,

David
Back to top
View user's profile Send private message

Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 7995
Location: Bellevue, IA

PostPosted: Fri May 01, 2009 10:51 pm    Post subject:
Reply with quote

NETREL=(netid,jobname) is an option on //*NET -- put it on the last job of the network you want to run first. I do not know what happens, however, if the first network has a job abend.

One of the reasons I haven't used DJC networks for 25 years is that they are difficult to work with; one job abend and you're typically better off just flushing the whole network and resubmitting it. I'm not sure how much they have improved over the years but back then we had too many abends to be able to reliably use DJC networks.
Back to top
View user's profile Send private message
David Eisenberg

New User


Joined: 15 Nov 2007
Posts: 39
Location: New York

PostPosted: Fri May 01, 2009 11:42 pm    Post subject: Reply to: JES3: how to prevent concurrent //*NETs ?
Reply with quote

Robert,

If I understand the NETREL option correctly, it can be used to establish a sequence across DJC networks, but it requires that the names of those networks be explicitly provided. I guess I wasn't clear in what I'm looking for.

I'm not trying to force a particular DJC network to run before another particular one, I just don't want them running concurrently. We have dozens of these networks, all with different NET ids, but what they all have in common is that I don't care what order they run in, as long as only one runs at a time.

Hence my original non-DJC example with DISP=OLD. If I catalogue a dataset called 'FORCE.ENQUEUE.DAVID', and I create fifty different JCL members with that dataset in the JOBLIB concatenation with DISP=OLD, then while I won't have any guarantees about what order the jobs are executed, I can guarantee that only one of the jobs will run at a time. I'm trying to get the equivalent sort of protection, but amongst multiple DJC networks.

I hope this makes sense...

David
Back to top
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 7995
Location: Bellevue, IA

PostPosted: Sat May 02, 2009 12:46 am    Post subject:
Reply with quote

That makes sense and clarifies things. As far as I'm aware, there's no way to tell JES3 to run one DJC network at a time. You could probably enforce the rule by running them all in a class with one initiator open, but that would pretty much get rid of parallel processing for the networks.
Back to top
View user's profile Send private message
David Eisenberg

New User


Joined: 15 Nov 2007
Posts: 39
Location: New York

PostPosted: Sat May 02, 2009 1:02 am    Post subject: Reply to: JES3: how to prevent concurrent //*NETs ?
Reply with quote

>You could probably enforce the rule by running them all in a class with one initiator open, but that would pretty much get rid of parallel processing for the networks.<

Aha! In our situation, that might actually be workable. It's not that I don't want any DJC networks to run concurrently, I just want to ensure that particular ones don't run concurrently. So if I set up the JCL to run those specific ones in the same class, and only run one initator for that class, I'm safe.

Thank you!

David
Back to top
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 7995
Location: Bellevue, IA

PostPosted: Sat May 02, 2009 1:16 am    Post subject:
Reply with quote

LOL ... glad I could help, I think? icon_confused.gif Good luck with it!
Back to top
View user's profile Send private message
David Eisenberg

New User


Joined: 15 Nov 2007
Posts: 39
Location: New York

PostPosted: Sat May 02, 2009 1:19 am    Post subject: Reply to: JES3: how to prevent concurrent //*NETs ?
Reply with quote

Robert,

You did help!

David
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> JCL & VSAM All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts JES2 JEC: Use UNIX Pipes to Pass Data... Virendra Shambharkar JCL & VSAM 21 Tue Dec 20, 2016 6:55 pm
No new posts ADRDSSU Restore - How to prevent repl... Lipi.Prasannan JCL & VSAM 12 Fri Oct 02, 2015 12:13 am
No new posts Prevent rounding of COMP-2 when displ... sijayapal COBOL Programming 5 Wed Apr 08, 2015 10:07 pm
No new posts JES3 equivalents for... Pedro JCL & VSAM 2 Thu May 15, 2014 5:42 am
No new posts Concurrent VSAM Access for Batch and ... abhisingh CICS 5 Wed Sep 05, 2012 3:33 pm


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us