DIS07 DISPLAY UNABLE TO EXECUTE with Roscoe

Products

Roscoe

Issue/Introduction

How to Tune the Roscoe DISBUF ROSGBL Parameter to resolve DIS07 DISPLAY UNABLE TO EXECUTE and DIS07 DISPLAY UNABLE TO EXECUTE INSUFFICIENT MEMORY IN SUBPOOL 239.

Environment

Release:
Component: ROSCOE

Resolution

Whenever a user issues a DISplay command, Roscoe acquires a buffer in SQA. Roscoe keeps statistics of this usage and writes them out during termination. Sites can control the use of this storage by tuning the DISBUF parameter.

For best practices, users should specify use a wildcard when specifying DISplay, such as DIS ROSCOE+ to minimize the amount of buffer space required for the DIS command.

There are two variations of the DIS07 message:

DIS07 DISPLAY UNABLE TO EXECUTE

If SUBPOOL 239 is NOT specified, the problem has to do with CSA storage. When no subpool is specified in the message, there isn't enough space in SUBPOOL 239 and tuning DISBUF is not going to resolve the problem. The solution is to increase CSA, or possibly storage is fragmented and an IPL might help.

NOTE:

The SUBPOOL Roscoe is using cannot be changed.
DIS07 DISPLAY UNABLE TO EXECUTE INSUFFICIENT MEMORY IN SUBPOOL 239

If SUBPOOL 239 is specified, then increasing the DISBUF parameter would make a difference. Roscoe calls SUBPOOL 239 within the CSA to obtain the required work area for every DISPLAY command. The ROSGBL parameter DISBUF allows you to specify the size of the buffer used for each DISplay command. For JES2, DISBUF is specified in KB (1024 bytes) and the default value for DISBUF is 8 (KB).

NOTE:

For JES3 Local, the block size of the IATUX30 data set is used; DISBUF is not used.
For JES3 Global, the size of the buffer determines the maximum number of jobs the terminal user can display at any one time.
The formula is: (disbuf * 1024 - 28) / 34 = jobcnt

Instructions:

During termination, global messages are written to the log indicating the number of requests for storage for DISPLAY and the number of times that the request was unsuccessful.

Look for message: ROS137I TOTAL ROSGBL SRB'S ISSUED = num. This tells you how many times a buffer for DISplay was requested. Then look for ROS138I TOTAL ROSGBL SRB'S RETRIED = num. This tells you how many times a buffer for DISplay was requested and was unsuccessful and had to be rescheduled. If the number of times the request had to be rescheduled is excessive, you should increase DISBUF=.

You can increase the DISBUF parameter in the ROSGBL and reassemble it. You might start with the current value and double it. Increasing DISBUF has an impact on CSA. Continue to monitor the messages.