🚀 go-pugleaf

This article probably constitutes misuse of this news group (apologies)
but it is the only forum of IBM systems programmers that I have access to.
Is there a more appropriate news group that perhaps I am not getting in
my feed?

On to the subject at hand.  I am a systems programmer responsible for a
4381 running MVS/SP and JES2 1.3.6 . For a long time we have been
experiencing a problem with JES2 that no one has been able to explain or
solve. 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".

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?

Here are some details that may aid the diagnosis:

We run the following OEM products; ACF2, TLMS and FDR/ABR (being replaced
by DFHSM!).

The JES2 proc is;

//JES2    PROC MEMBER=JES2PARM,ALTMEM=JES2PARM
//IEFPROC EXEC PGM=HASJES20,DPRTY=(15,15),TIME=1440,PERFORM=9
//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
//HASPPARM DD  DSN=SYS1.JESPARMS(&MEMBER),DISP=SHR,FREE=CLOSE
//ALTPARM  DD  DSN=SYS1.PARMLIB(&ALTMEM),DISP=SHR,FREE=CLOSE
//HASPLIST DD  DDNAME=IEFRDER

All of the proclibs are PRIMARY allocation only. Their blocksizes are (in
order) 3120, 3120, 3120, 3120, 6160, 6160.

Any help in this matter would be appreciated.

Trevor Cook
attcan!bdofed!cook
(416) 394-7181