S106 SVC Dump in OPS/MVS Main task following OPM3202W OR OPS3202W messages

Products

• OPS/MVS Event Management & Automation

Issue/Introduction

S106 SVC Dump in OPS/MVS Main task following OPM3202W OR OPS3202W messages.  Several other dumps for CICS issues preceded these in the log.

Resolution

Check to see if the OPSLOG shows the OPSMAIN address space was running out of storage with messages similar to: 

(Note that the offset may vary, depending on the release of OPS/MVS being run) 
=======

09:50:38 8008 OPM3202W GET OF 1048608 BYTES IN SUBPOOL X'E6' ERROR RC=X'00000004' REQUESTED BY   OPRXAO+X'0030B2' 
09:50:38 8048 OPM4301S GETMAIN - RXIN FAILED, RC=4        

Eventually a dump follows: 

09:51:50 IEW4000I FETCH FOR MODULE OPSAEX   FROM DDNAME -LNKLST- FAILED BECAUSE INSUFFICIENT STORAGE WAS AVAILABLE.    
09:51:50 IEF196I IEW4000I FETCH FOR MODULE OPSAEX   FROM DDNAME -LNKLST- FAILED                                        
09:51:50 IEF196I BECAUSE INSUFFICIENT STORAGE WAS AVAILABLE.  
09:51:50 CSV031I LIBRARY ACCESS FAILED FOR MODULE OPSAEX  , RETURN CODE 14, REASON CODE 26110021, DDNAME *LNKLST*      
09:51:50 IEF196I CSV031I LIBRARY ACCESS FAILED FOR MODULE OPSAEX  , RETURN CODE                                        
09:51:50 IEF196I 14, REASON CODE 26110021, DDNAME *LNKLST*                                                             
09:51:50 CSV028I ABEND106-14  JOBNAME=AOPOMAIN  STEPNAME=AOPOMAIN                                                      
09:51:50 IEF196I CSV028I ABEND106-14  JOBNAME=AOPOMAIN  STEPNAME=AOPOMAIN                                              
09:51:50 IEA045I AN SVC DUMP HAS STARTED AT TIME=09.51.50 DATE=10/29/2020
09:51:50 FOR ASID (0024)                                  
09:51:50 ERROR ID = SEQ37077 CPU00 ASID0024 TIME09.51.50.4
09:51:50 QUIESCE = NO                                     
==========

While it requested more than available according to the message at 09:50:38; also the size of OPSAEX 1866880 bytes is also bigger than available. 

If you have allocated OPSEXEC for your TSO section,  you can go to OPSV =4.1.6 to simulate how your parameter setting will affect your storage usage.  The parameters: PROCESS, AOFMAXQUEUE, and AOFSIZE heavily affect the total storage used.

You may consider to reduce the number of process blocks, or the storage that is allocated by all the process blocks. The number of process blocks you specify may use so much virtual storage that OPS/MVS fails to function correctly. You can reference this link : Process Blocks

 
The AOFSIZE parameter determines the size of the AOF workspace (used to store REXX variables).
Using several new OPS/MVS parameters (AOFWSHIGHUSED, AOFWSHIGHUSEDPGM, AOFWSHIGHUSEDRULE, AOFWSHIGHUSEDDATE, and AOFWSHIGHUSEDTIME), you can trace the maximum amount of workspace that rules have used since OPS/MVS was last started. After tracing the levels of workspace use, you may wish to decrease the value of the AOFSIZE parameter if it is set larger than the value of the AOFWSHIGHUSED parameter. You can reference this link : AOFMAXQUEUE Parameter