OPS9506S DYNAMIC ALLOCATION OF TSO EXECUTE QUEUE FAILED, RC=4,DETECTED AT OPRXTS+X'000086C'

book

Article ID: 52929

calendar_today

Updated On:

Products

CA SOLVE:Operations Automation SOLVE:Access Session Management CA SOLVE:CA Mainframe Connector CA SOLVE:FTS CA OPS/MVS Event Management & Automation CA SOLVE

Issue/Introduction

Description:

The ADDRESS TSO command in a REXX ends with RC=4 and the message OPS9506S is displayed in the OPSOSF server.

Solution:

In most cases this error occurs because OPSMVS cannot allocate the TSO execute queue to a VIO device. By default the first VIO eligible unit from the Eligible Device Table is used to allocate this temporary dataset, which is used to trap the output from the TSO command.

If you don't have VIO devices defined In the IODEF you can set the VIO parameter in the OPSTART1 CLIST with the OPSPARM SET(VIO) VALUE(SYSDA) . If SYSDA is not a valid esoteric name than specify any other valid esoteric name. You can also define the value of VIO into the OPSSPAxx member with using the following statement:

T = OPSPRM_Set("VIO","SYSDA")

There are a few cases where a customer did have VIO devices and did not set the VIO parameter, but still got occasionally the OPS9506S message when executing a REXX with ADDRESS TSO commands.

This problem was caused by the SMS routine that allocated the temporary OPSOSF datasets. To bypass this problem customer took the OPOSF temporary dataset out of SMS control, until the problem in the SMS routines was corrected.

Environment

Release:
Component: SOPMVS