REXX storage: Used RM31=decimal-K-bytesK, RM24=decimal-K-bytesK; Requests=request-count, Failed=request-count
Informational message issued by VNCINI00, the program that runs the OBEYFILE exec during agent initialization, and VNCCPR01, the program that runs all REXX execs after the agent has finished intializing.
This message is displayed after an exec has completed execution, following message VNC0411I, to show the maximum amount of rmode 31 and rmode 24 memory used by the exec.
The request-count is the total number of requests from REXX to obtain and free blocks of memory. Normally, this should be an even number. It may be an odd number if a request fails and REXX issues a request for a smaller amount of memory that is accepted.
Normally, the failed request-count will be zero. If it is not, message VNC0961E will have been previously issued to show which rmode memory limit was exceeded.
When UseREXXLoader is set to Yes, RM24 is typically OK. However, even when the VNAC REXX loader is used, you may see some exec tasks running and below-the-line storage being used. Typically, these will be the initial obeyfile task and any exec that runs automatically at startup.
Until the initial obeyfile has been processed, the agent will default to running without the use of the VNAC REXX loader. Thus, these early tasks will load their own exec locally and cause REXX to obtain below-the-line storage for the I/O buffer. When these execs have ended, the REXX environment will be deleted and the associated below-the-line storage will be released. As a result, these execs do not impact the address space below-the-line storage usage in any significant manner; any such usage is temporary.
Action: Assuming the exec does not have an error, the corrective action is to increase the memory limit for the corresponding rmode using the RexxEnvLimit global configuration statement.