Re: IEF289E - WAITING FOR VOLUME(S) OR UNIT(S)

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:

Re: IEF289E - WAITING FOR VOLUME(S) OR UNIT(S)

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

RES: IEF289E - WAITING FOR VOLUME(S) OR UNIT(S)

Neto Tel: 55 11 4197-2021 Fax: 55 11 4197-2814 -Mensagem original- De: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] Em nome de Carles Ari­s Enviada em: quinta-feira, 01 de junho de 2006 13:50 Para: IBM-MAIN@BAMA.UA.EDU Assunto: Re: IEF289E - WAITING FOR VOLUME(S) OR UNIT(S

Re: JES vs JES (Was: IEF289E - WAITING FOR VOLUME(S) OR UNIT(S))

I know this will start a logical argument in this discussion group. I worked at a JES3/JES2 shop many aeons ago. Two sites were JES2 and one was JES3. They were connected by NJE/NJP with many complications if jobs were submitted on one node and had to execute on a node with a different JES.

Re: RES: IEF289E - WAITING FOR VOLUME(S) OR UNIT(S)

Hi Ituriel, Qname SYSIEFSD Rname Q4 is used to serialise changes to the UCB by allocation of vary processing. From my recollection it is of best use when you are going through allocation recovery and wish to see how deep the queue is. Feel free to email me direct Regards, James James Benson

Re: IEF289E - WAITING FOR VOLUME(S) OR UNIT(S)

Hi, You could try the MVS command D GRS,RES=(SYSIEFSD,*) RESPONSE=ISYS ISG343I 08.19.00 GRS STATUS 578 S=SYSTEM SYSIEFSD Q4 SYSNAMEJOBNAME ASID TCBADDR EXC/SHRSTATUS LSYS DFHSM 0FA4 00892968 SHARE OWN Regards, James James Benson

Re: IEF289E - WAITING FOR VOLUME(S) OR UNIT(S)

ITURIEL DO NASCIMENTO NETO [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED]... Hi all, We have implemented ALLOCxx with : VOLUME_ENQ POLICY(WTOR) VOLUME_MNT POLICY(WTOR) SPEC_WAIT POLICY(WAITNOH) MAXNWAIT(255) POLICYNW(WTOR)

IEF289E - WAITING FOR VOLUME(S) OR UNIT(S)

Hi all, We have implemented ALLOCxx with : VOLUME_ENQ POLICY(WTOR) VOLUME_MNT POLICY(WTOR) SPEC_WAIT POLICY(WAITNOH) MAXNWAIT(255) POLICYNW(WTOR) ALLC_OFFLN POLICY(WAITNOH) MAXNWAIT(255) POLICYNW(WTOR) This