Description:
Just upgraded OPS/MVS. Receiving OPS0037E PROCESS BLOCK POOL CREATE ERROR RC=4.
Solution:
Problem:
Just installed CA OPS/MVS new release. When I start my z/OS system with the new release it fails with a series of messages:
From OPSLOG:
OPS3144W MESSAGE QUEUE GETSTOR FAILED, RC=X'08', REASON CODE=1241522464 OPS3141E AOF MESSAGE QUEUE ALLOCATE FAILED, RC=X'04', DETECTED AT
OPSMMG+X'00004A9C' OPS0037E PROCESS BLOCK POOL CREATE ERROR RC=4 OPS0018W storage not released - ECSA X'00004FD8' bytes IEF196I OPS0018W storage not released - ECSA X'00004FD8' bytes OPS0017I OPS/MVS-JES2 subsystem OPSS termination complete IEF196I OPS0017I OPS/MVS-JES2 subsystem OPSS termination complete CDSYM0001I OPSMVS 1 IEFPROC OPINMA -------- R0000 IEF170I 1 OPSMVS CDSYM0001I OPSMVS 1 IEFPROC OPINMA -------- IEF404I OPSMVS - ENDED - TIME=14.36.04 CDSYM0001I OPSMVS -------- EOJ IEF170I 1 OPSMVS CDSYM0001I OPSMVS --------
Need to add the parameter MEMLIMIT=4G to the EXEC statement of the OPSMAIN JCL.
If use of above the bar 64-bit storage is automatically restricted by your installation using SMFPRMxx parmlib members or theSMF exit IEFUSI, then you may have to add the parameter 'MEMLIMIT=4G' to the OPSMAIN EXEC JCL statement or insure that CA OPS/MVS is not subject to any MEMLIMIT restrictions.