DYNAMIC ALLOCATION of INTERNAL READER failed, RC=4, detected at OPSUBMIT+X'0000031E'
search cancel

DYNAMIC ALLOCATION of INTERNAL READER failed, RC=4, detected at OPSUBMIT+X'0000031E'

book

Article ID: 204264

calendar_today

Updated On:

Products

OPS/MVS Event Management & Automation

Issue/Introduction

We're experiencing issues with execs that submit jobs via OPSUBMIT on one of our LPARs.  If an exec that does an OPSUBMIT is called from a CMD or MSG rule (and probably other rule types), an error allocating the Internal Reader is produced, and the job does not get submitted.      

OPM3092H DYNAMIC ALLOCATION of INTERNAL READER failed, RC=4, detected at OPSUBMIT+X'0000031E' 
OPM3092H ERROR 48 RUNNING OPSUBTST, LINE 11: FAILURE IN SYSTEM SERVICE    

Line 11 in this example is simply "xx = opsubmit(jfdata.)"  

If the same exec with the OPSUBMIT is called directly via an OSFOI command on this system however, we do not get the Internal Reader failure, and the job submits successfully.  Issuing the command that calls the exec on another LPAR also does not get an error with the internal reader, and submits the job successfully.    

 

 

                   


 

                   

 

Environment

Release : 13.5 14.0

Component : OPS/MVS

Resolution

There is maintenance to address this problem:

OPS 13.5 - PTF LU00068

https://support.broadcom.com/download-center/solution-detail.html?aparNo=LU00068&os=z%2FOS

OPS 14.0 - PTF LU00067

https://support.broadcom.com/download-center/solution-detail.html?aparNo=LU00067&os=z%2FOS