Path: utzoo!utgpu!watmath!att!tut.cis.ohio-state.edu!brutus.cs.uiuc.edu!wuarchive!swbatl!texbell!sugar!splut!jay
From: jay@splut.conmicro.com (Jay "you ignorant splut!" Maynard)
Newsgroups: comp.protocols.ibm
Subject: Re: Problem with JES2 proclibs
Keywords: IBM JES2 proclibs help
Message-ID: <2792@splut.conmicro.com>
Date: 28 Jul 89 13:59:53 GMT
References: <129@bdofed.UUCP>
Reply-To: jay@splut.conmicro.com (Jay "you ignorant splut!" Maynard)
Organization: Confederate Microsystems, League City, TX
Lines: 40

In article <129@bdofed.UUCP> cook@bdofed.UUCP (b) writes:
>Occasionally when a proc has been updated in or added to one of the 
>proclibs, batch jobs encounter problems accessing the proc. The job either 
>gets the old copy of the proc, or, in the case of a new proc, gets the error
>message "I/O ERROR READING PROCLIB". 

This looks like an extent being added to the library in the middle...
except that your primary allocation only rules that out.

>The only way we know of to straighten this problem out is to stop JES2 and 
>hot start it. This is not a great thing to be doing in the middle of the
>day!! ISC have carried this problem all the way to the JES2 development team
>without any success. Does anyone have any ideas or suggestions?

Actually, issuing $PJES2,ABEND and then restarting it, isn't that
disruptive if your JES2 starts up reasonably quickly. The only effect
that users will notice is that their SUBMITs and LOGONswill take a bit
longer.

>//PROC00   DD  DSN=SYS1.EBE.PROCLIB,DISP=SHR,DCB=BLKSIZE=20000          
>//         DD  DSN=SYS1.PROCLIB,DISP=SHR                                
>//         DD  DSN=OKPROD.PROC,DISP=SHR,UNIT=SYSDA,VOL=SER=EBE013       
>//         DD  DSN=OKPROD.MSPROC,DISP=SHR,UNIT=SYSDA,VOL=SER=EBE013     
>//         DD  DSN=PROD.PROCLIB,DISP=SHR,UNIT=SYSDA,VOL=SER=EBE007      
>//         DD  DSN=TEST.PROCLIB,DISP=SHR,UNIT=SYSDA,VOL=SER=EBE005      
>All of the proclibs are PRIMARY allocation only. Their blocksizes are (in
>order) 3120, 3120, 3120, 3120, 6160, 6160.

Looks like you've done everything right here...what's in
SYS1.EBE.PROCLIB? Hopefully, not much. You might run the BLKSIZE
parameter on the first card up to 20480, just to take better advantage
of the pages allocated to the buffers, but that's a nit.

Good question. Has me stumped. I guess you've APARed it...

-- 
Jay Maynard, EMT-P, K5ZC, PP-ASEL   | Never ascribe to malice that which can
uucp:        uunet!nuchat!   (eieio)| adequately be explained by stupidity.
{attctc,bellcore}!texbell!splut!jay +----------------------------------------
internet: jay@splut.conmicro.com    | "He's T*d, Jim."-Richard "Bones" Sexton