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

Products

• OPS/MVS Event Management & Automation

Issue/Introduction

We have a REXX code which uses function OPSUBMIT()  to submit a job from the queue populated by  OPSCLEDQ() .

The code has not changed since 2016. It is failing today with below error:

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

We have multiple jobs in production which uses the same REXX code to submit automation jobs. They might fail as well.

 

Here is the code:

var = OPSCLEDQ()                                                       
queue "//AOSEMAIL JOB   (BBI-BBI,OVHD),"rid",MSGCLASS=T,CLASS=B  "     
queue "/*LOGONID AOSBTCH                                         "     
queue "/*JOBPARM SYSAFF="sysid"                                  "     
queue "//JSTY0010 EXEC  PGM=IKJEFT1B                             "     
queue "//SYSEXEC  DD    DISP=SHR,DSN="hlq"TOOLS.XMITIP.EXEC      "     
queue "//SYSPRINT DD    SYSOUT=*                                 "     
queue "//SYSTSPRT DD    SYSOUT=*                                 "     
queue "//SYSTSIN  DD    *                                        "     
queue "%XMITIP *                                  -"                   
queue "FROM [email protected]          -"                     
queue "REPLYTO [email protected]      -"                   
queue "MSGDS '"hlq"ops.apps.card(null)'           -"                   
queue addfi_var                                                        
do j = 1 to i                                                          
  queue newsub.j                                                       
end j                                                                  
                                                                       
count = OPSUBMIT()                   <======== Job is failing on this line. It is not submitting job AOSEMAIL.                                  
return count                                                           

 

Environment

Release : 13.5

Component : OPS/MVS

Resolution

In this particular case, the error was caused by a lack of authority for the issuing task.

If unable to determine the problem, provide the following to Broadcom's CA Mainframe Support:

- Archived OPSLOG showing the timer period where the problem occurred.  (NOTE: the OPSLOGS must be archived and tersed, and transmitted binary).

- All REXX code involved, from all systems.