If this is a "normal" event in your shop and it is causing serious delays, you might look at running JES3 rather than JES2. JES3 has a process called High Watermark Setup which prevents this problem and JES3 also requires all volumes to go through fetch before the JOB can be scheduled. The switch is traumatic to the JES programmer and to operations. No question about that since nothing is the same. I can tell you that once you have two images (based on very old data) that the overhead is a break even. For more than two images JES3 has less overhead. The JES complex runs as one master (GLOBAL) and the rest are slaves (LOCAL).
I know this will start a logical argument in this discussion group. I offer this not as advice but as an additional piece of information. Nothing more. Regards, Rob Weiss z/SWITA and z/Series I/T Security and Privacy Consultant IBM Software Group Sales IBM Mainframe Discussion List <[email protected]> wrote on 06/01/2006 10:49:53 AM: > Hi Ituriel, > > Did you find a way to know how deep the allocation queue is? > > Regards, > Carles Aris > La Caixa > Spain ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
