During CA OPS startup messages OPS3144W, OPS3141E, OPS0037E, OPS3033E may appear and the product does not complete activation.

Document ID : KB000006018
Last Modified Date : 14/02/2018
Show Technical Document Details
Issue:

When starting OPSMAIN the messages below may appear:

IEF196I OPS3141E GLV MESSAGE QUEUE ALLOCATE FAILED, RC=X'04',                    

IEF196I AT OPSMMG+X'00004E2E'                                

OPS3141E GLV MESSAGE QUEUE ALLOCATE FAILED, RC=X'04',        

IEF196I OPS0037E PROCESS BLOCK POOL CREATE ERROR RC=4        

OPS0037E PROCESS BLOCK POOL CREATE ERROR RC=4                

OPS0070H MSF terminating                                     

IEF196I OPS3033E STORAGE POOL NOT IN USE (1  )               

OPS3033E STORAGE POOL NOT IN USE (1  )                       

IEF196I OPS0071E MSF - FREE OF MSF STORAGE POOL FAILED, RC=8 

OPS0071E MSF - FREE OF MSF STORAGE POOL FAILED, RC=8         

OPS0070H MSF terminated                                    

 

Environment:
A supported release of CA OPS/MVS and z/OS
Cause:

CA OPS/MVS 64-bit storage, that is, storage above the bar (2Gb limit) is not enough to complete OPSMAIN initialization.

The MEMLIMIT JCL parameter specifies the limit on the total size of usable virtual storage above the bar in a single address  space.

From CA OPS/MVS documentation:

If use of above the bar 64-bit storage is automatically restricted by your installation using SMFPRMxx parmlib members or the SMF 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.

 

 

Resolution:

To resolve this problem include the keyword MEMLIMIT=4G in the EXEC statement of the OPSMAIN JCL.

For example:

//IEFPROC EXEC PGM=OPINMA,REGION=4M,TIME=1440,DYNAMNBR=100, 
// PARM='&SSID.&MEMBER,&MAINPRM',MEMLIMIT=4G <----- here 

 

Additional Information: