OPS3092H DYNAMIC ALLOCATION of TSO EXECUTE QUEUE failed, RC=4

Products

• OPS/MVS Event Management & Automation

Issue/Introduction

When using dynamic allocation with ADDRES OSF or ADDRESS TSO in a REXX program processed in OPSMVS, the following error may occasionally occur depending on the usage status of VIO.

Is there any way to avoid this problem?

 

<Error messages>

OPS3092H DYNAMIC ALLOCATION of TSO EXECUTE QUEUE failed, RC=4, detected at OPRXTS+X'0000090E'  
OPS0997T *-* 43:   "ALLOC FI(INFILE1) DSN('prefix.USEREXEC(program_name)') SHR"          
OPS0997T +++     RC(4)                                                                         

OPS3092H The input or output file INFILE1 is not allocated. It cannot be opened for I/O.       
OPS3092H EXECIO error while trying to GET or PUT a record.                                     
OPS0997T *-* 45:   "EXECIO * DISKR INFILE1 (STEM INREC1. FINIS"                                
OPS0997T +++     RC(20)             

 

<Example of specified program code>

   ADDRESS OSF
   "ALLOC FI(INFILE1) DSN('"libname"("membname")') SHR"

or

   ADDRESS TSO
   "ALLOC FI(INFILE1) DSN('"libname"("membname")') SHR"

Environment

OS : z/OS

Product : OPS/MVS Event Management & Automation

Release : All

Component : OPSMVS

Resolution

ADDRESS TSO and ADDRESS OSF allocate temporary data sets via VIO, but if the allocation fails, the following error message is output.

 

DYNAMIC ALLOCATION of TSO EXECUTE QUEUE failed, RC=4, detected at OPRXTS+X『0000090E』

 

On the other hand, ADDRESS OPSDYNAM does not allocate temporary data sets, unlike ADDRESS TSO and OSF.  
Therefore, please change the ADDRESS TSO and ADDRESS OSF in the ALLOC command to ADDRESS OPSDYNAM.

On the other hand, ADDRESS OPSDYNAM does not allocate temporary data sets, unlike ADDRESS TSO and OSF.  
In such cases, it is recommended to change the ADDRESS TSO or ADDRESS OSF in the ALLOC command to ADDRESS OPSDYNAM.

<Sample Code>

  ADDRESS OPSDYNAM
   "ALLOC FI(INFILE1) DSN('"libname"("membname")') SHR"