exec-name(task-name) ALR3 buffer is missing/invalid
Error message issued by functions ALERTRTN (VNCRXF31) and ALERTRSL (VNCRXF32).
If the ALR3 alert buffer is “missing,” then the exec that called the function was not called from an alert rule, so there is no alert buffer to process. This is a user error.
If the ALR3 alert buffer is invalid, the storage class ID in the buffer is not the expected ALR3.
This is an internal logic error.
exec-name received an invalid MDB prefix/header; ID=eyecatcher, VER=mdb-version, TYPE=MDB-type; no variables created
Error message issued by VNCRXM03, the REXX EXEC exit that creates variables for execs called from alert and message rules. The address of the MDB buffer is passed to the exec in the CPB.
The error occurs when the MDB buffer fails validation of the eyecatchers in the prefix or header sections, identified in the message by eyecatcher.
For the MDB prefix section, ID should equal MDBP, VER should equal 1, and TYPE should = 0 (zero).
For the MDB header, ID should equal MDB, VER should equal 1, and TYPE should equal 1.
This message probably indicates an internal logic error.
program-name: exec-name(task-name), MDB(buffer-address), CPB(buffer-address)
Debug message issued by VNCRXM03, the REXX EXEC exit that creates variables for execs called from alert and message rules. The exit acts before the exec begins processing the MDB message buffer. The address of the MDB buffer is passed to the exec in the CPB.
exec-name received an invalid ALR3 buffer; ID=buffer-id; LEN=buffer-length; no variables created
Error message issued by VNCRXM03, the REXX EXEC exit that creates variables for execs called from alert and message rules. The address of the ALR3 alert buffer is passed from the alert rule to the exec in the CPB.
The error occurs when the ALR3 alert buffer fails validation of its storage class, identified in the message by buffer-id.
The ID should be “ALR3” and the length should be 0x00001000 (4,096).
program-name: exec-name(task-name), ALERT=vip-alert-id, AGENT=vip-agent-name, ALR3(buffer-address), CPB(buffer-address)
Debug message issued by VNCRXM03, the REXX EXEC exit that creates variables for execs called from alert and message rules. The exit acts before the exec begins processing the ALR3 alert buffer. The address of the ALR3 alert buffer is passed to the exec in the CPB.
exec-name request for decimal-K-bytesK bytes exceeds RMODE 24 or 31 memory limit of decimal-K-bytesK
Error message issued by VNCRXR02, the program that services REXX requests to obtain and free blocks of memory, when the total allocation for the specified rmode, including the latest request, would exceed the limit set for the rmode, either by default, or with the global configuration statement “RexxEnvLimit.”
The first decimal-K-bytes in the message is the total amount of memory that would be allocated, if the current request was processed.
The second decimal-K-bytes is the maximum amount of memory allowed for the rmode shown in the message.
The storage request is rejected and the number of failed storage requests for the exec is increased by 1.
REXX always retries failed storage requests once. Sometimes REXX will request a smaller amount on the second request. If the second request keeps the total allocation below the limit for the rmode, the exec may continue execution and complete normally.
If REXX cannot obtain enough memory, it will free all the memory is has obtained so far and terminate the exec with various error messages, depending on what the exec was doing at the time of the failed storage request.
Action: Increase the memory limit for the rmode, using the “RexxEnvLimit” global configuration statement, and re-run the exec.
program-name: exec-name REXX-storage-request ADR=pool-address, ACTSZ=actual-size, MINSZ=requested-size, SP=storage-subpool; CPB=cpb-address
Debug message issued by VNCRXR02, the program that services REXX requests to obtain and free blocks of memory, to show the parameters passed by REXX every time REXX makes a storage request.
The REXX-storage-request may be “GET” for an rmode 31 storage request, “GETLOW” for an rmode 24 storage request. Or “FREE” for a request to free storage of either rmode.
ADR and ACTSZ only have meaningful data for “FREE” requests, in which case pool-address is the address of the data section of a previously allocated buffer, and actual-size is the size of the data section of the buffer.
MINSZ only has meaningful data for “GET” and “GETLOW” requests.
The requested-size is the minimum length of the memory block REXX is requesting.
The storage-subpool is always zero. All storage allocations for REXX are in subpool zero.
VNC0959D program-name: exec-name RSM action an storage-class@ buffer-address, length=buffer-length; totals RM31=decimal-K-bytesK, RM24=decimal-K-bytesK
Debug message issued by VNCRXM00, the program that controls REXX execution, and VNCRXR02, the program that services REXX requests to obtain and free blocks of memory, to show the disposition of a block of memory.
RSM refers to the REXX Storage Management component of VNAC.
The action may be either “allocated” or “freed.”
The storage-class refers to the name of the buffer type being processed. Requests for 64KB or less use storage-class RXL0-RXL4 for rmode 24 buffers, and RXH0-RXH4 for rmode 31 buffers. storage-class is SMTS for memory blocks larger than 64KB for both rmodes.
The buffer-address is the buffer’s hexadecimal memory address. The buffer-length is the decimal length of the buffer, including its 32 byte header.
The totals show the current memory allocation for each rmode. They include the amount for the latest request.
program-name: exec-name PUTALR created AFR buffer buffer sequence number at buffer-address; Agent=vip-agent-name, alert=vip-alert-id
Debug message issued by VNCRXF28, the program that saves alert rules processed by the OBEYFILE exec, to show the sequence-number, buffer-address, filter vip-alert-id, and vip-agent-name values of each new alert filter that gets stored in an AFR buffer.
program-name: exec-name set or cancel check-for-cancel timer; RTC=hex-return-code; CPB=cpb-address
Error message issued by VNCRXM00, the program that initiates and terminates REXX execs, if it receives a non-zero hex-return-code when it sets or cancels the the STIMERM exit. STIMERM periodically checks if a request was issued to cancel the exec. This will not affect the execution of the exec. However, if a set request fails, it may prevent a user from canceling the exec. If a cancel request fails, it may result in other abends.
Action: For help resolving this problem, contact SDS Technical Support.
