Edward,
Sorry, I'm not trying to make excuses, but I have a production issue which has taken my attention until today. Even though it was requested that my access to mirror the previous DBA, I still encountering access problems.
I found the job to execute the IDMS CV program already has REGION=0M (see below). I attempted to recreate and capture more information on the abend, but once again I've encountered another access issue. It should be resolved soon.
Please advise, is it appropriate to keep this thread open until I get the abend recreated?
//PEXBCV95 JOB DBAPADP1,'EXB.DBA',MSGCLASS=R,PRTY=10,REGION=0M
//STARTING EXEC CV95
//CV95 PROC
//IDMSDC95 EXEC PGM=IDMSDC95,TIME=1440,
// PARM='S=95 S '
//STEPLIB DD DISP=SHR,DSN=DBAPRD.SYS.IDMS.LOAD.STARTUP
//CDMSLIB DD DISP=SHR,DSN=DBATST.DBA.IDMS.SIGNON.R160
// DD DSN=DBATST.DBA.IDMS.CV95.LOAD,DISP=SHR
// DD DSN=DBATST.SYS.IDMS.LOAD.R160,DISP=SHR
// DD DISP=SHR,DSN=DBATST.DBA.DBOL150.AUTH.LOADLIB
// DD DISP=SHR,DSN=DBATST.DBA.DBOL151.LOADLIB
// DD DSN=SYS1.SCEERUN,DISP=SHR
//SYSCTL DD DSN=DBATST.DBA.IDMS.CV95.SYSCTL,DISP=SHR
//ABNLIGNR DD DUMMY,BLKSIZE=80
//SYSUDUMP DD SYSOUT=*
//SYSJRNL DD DUMMY
//J1JRNL DD DSN=DBATST.DBA.IDMS.CV95.J1JRNL,DISP=SHR
//J2JRNL DD DSN=DBATST.DBA.IDMS.CV95.J2JRNL,DISP=SHR
//J3JRNL DD DSN=DBATST.DBA.IDMS.CV95.J3JRNL,DISP=SH
//J4JRNL DD DSN=DBATST.DBA.IDMS.CV95.J4JRNL,DISP=SH
//PLOGJOB DD DISP=SHR,DSN=SYS1.JES.PROCLIB(PEXB95LG)
//AJNLJOB DD DISP=SHR,DSN=SYS1.JES.PROCLIB(PEXB95JN)
//JESRDR DD SYSOUT=(1,INTRDR),DCB=(RECFM=F,LRECL=80,BLKSIZE=80)
//OLQRDR DD SYSOUT=(1,INTRDR),DCB=(RECFM=F,LRECL=80,BLKSIZE=80)