0(0) |
PUTGET completed successfully. The line was obtained
from either: the REXX data stack, a command procedure DATA-ENDDATA
group, or the terminal. |
4(4) |
PUTGET completed successfully. The line was obtained
from an in-storage list or command procedure. (MODE messages only.) |
8(8) |
The PUTGET service routine did not complete.
An attention interruption occurred during the execution of PUTGET,
and the attention handler turned on the completion bit in the communications
ECB. |
12(C) |
One of the following situations occurred: - No prompting was allowed on a PROMPT request. Either the user
at the terminal requested no prompting with the PROFILE command, or
the current source of input is an in-storage list other than an EXEC
command procedure.
- A line could not be obtained after a MODE request. Second-level
messages exist, and the current stack element is not a terminal, but
the terminal user did not request PAUSE processing with the PROFILE
command. The messages are, therefore, not available to him.
|
16(10) |
One of the following situations occurred: - The NOWAIT option was specified for PUT processing and no line
was put out.
- A barrier element is on top of the stack, the current source of
input is a data set, and SUBSTACK=NO was specified or defaulted. No
command buffer is passed back.
|
20(14) |
The NOWAIT option was specified for GET processing
and no line was received. |
24(18) |
Incorrect parameters were supplied to the PUTGET
service routine. |
28(1C) |
PUTGET was unable to obtain sufficient storage
to satisfy the request for output buffers. |
32(20) |
The terminal has been disconnected. |
40(28) |
A barrier element is on the top of the stack and
SUBSTACK=YES was specified. No command buffer is passed back. |