 |
Purpose This macroinstruction receives
normal information that is immediately available from a specified
conversation. The conversation may be in continue-any or continue-specific
mode. VTAM® does not wait for
more data to be received before completing this macroinstruction.
Usage When this macroinstruction is issued, VTAM copies all data that is immediately
available into the supplied data area or control block that is specified
by the AREA parameter. The AREALEN parameter specifies the length
of the data area. VTAM does
not wait to receive any more data before completing the macroinstruction
request. If there is no information available, VTAM issues an RCPRI, RCSEC combination of X'0000', X'0008',
NO_IMMEDIATELY_AVAILABLE_INFORMATION.
When this macroinstruction
completes, the RECLEN field indicates how much data was written to
the data area. The WHATRCV field indicates what type of data was received.
If VTAM is processing APPCCMD CONTROL=RECEIVE,
QUALIFY=ANY|IANY for a conversation and the application program issues
APPCCMD CONTROL=RECEIVE, QUALIFY=ISPEC for the same conversation,
the QUALIFY=ISPEC request fails with an RCPRI, RCSEC combination of X'0000', X'0003',
RECEIVE_SPECIFIC_REJECTED. VTAM cannot
allow a specific-mode RECEIVE while an any-mode RECEIVE is being processed.
This
macroinstruction corresponds to the RECEIVE_IMMEDIATE verb described
in the LU 6.2 architecture.
Context For half-duplex conversations,
this macroinstruction can be issued from the following conversation
states: - RECEIVE
- PEND_END_CONV_LOG
- PEND_RCV_LOG
For full-duplex conversations, this macroinstruction
can be issued from the following conversation states: - SEND/RECEIVE
- RECEIVE_ONLY
- PENDING_SEND/RECEIVE_LOG
- PENDING_RECEIVE-ONLY_LOG
- PENDING_RESET_LOG
This macroinstruction is not allowed for conversations
pending deallocation for persistent LU-LU sessions.
Syntax 
(1)
>>-+---------+--APPCCMD-- --CONTROL--=--RECEIVE--,--QUALIFY--=--ISPEC------>
'-name-- -'
(2)
>--,--RPL--=--+-rpl_address_field----------+-------------------->
'-(--rpl_address_register--)-'
>--+-----------------------------------------------------------+-->
| (3) |
'-,--AAREA--=--+-rpl_extension_address_field----------+-----'
'-(--rpl_extension_address_register--)-'
>--+-----------------------------------------------+------------>
| (3) |
'-,--ACB--=--+-acb_address_field----------+-----'
'-(--acb_address_register--)-'
>--+------------------------------------------------------+----->
| (3) |
'-,--AREA--=--+-data_area_address_field----------+-----'
'-(--data_area_address_register--)-'
>--+--------------------------------------------------------+--->
| (3) |
'-,--AREALEN--=--+-data_area_length----------------+-----'
'-(--data_area_length_register--)-'
>--+---------------------------+--+-------------------------+--->
| (3) | | (1) |
'-,--BRANCH--=--+-NO--+-----' '-,--CD--=--+-DEFER-+-----'
'-YES-' '-IMMED-'
>--+-------------------------------+---------------------------->
| (1) |
'-,--CONMODE--=--+-BUFFCA-+-----'
+-CS-----+
+-LLCA---+
'-SAME---'
>--+---------------------------------------------------------+-->
| (1) |
'-,--CONVID--=--+-32-bit_resource_id_field----------+-----'
'-(--32-bit_resource_id_register--)-'
>--+-----------------------------+------------------------------>
| (1) |
'-,--CONXMOD--=--+-CA---+-----'
+-CS---+
'-SAME-'
>--+-------------------------------------------------------------+-->
| (4) (3) |
+-,--ECB--=--+-INTERNAL-------------------+-------------------+
| +-ecb_address_field----------+ |
| '-(--ecb_address_register--)-' |
| (5) (3) |
'-,--EXIT--=--+-exit_routine_address_field----------+---------'
'-(--exit_routine_address_register--)-'
>--+--------------------------+--------------------------------->
| (1) |
'-,--FILL--=--+-BUFF-+-----'
'-LL---'
>--+-------------------------------------------------+---------->
| (6) (3) |
'-,--OPTCD--=--(------+-+-ASY-----+----------+--)-'
| | (3) | |
| '-SYN-----' |
| (3) (7) |
+-+-KEEPSRB----------+-+
| | (3) (8) | |
| '-NKEEPSRB---------' |
| (3) |
'-+-NBUFFLST-----+-----'
| (3) |
'-XBUFLST------'
>--+------------------------------------------------------+----->
| (1) |
'-,--VTROUTA--=--+-vector_address_field----------+-----'
'-(--vector_address_register--)-'
>--+-----------------------------------------------------+-----><
| (1) |
'-,--VTROUTL--=--+-vector_length_field----------+-----'
'-(--vector_length_register--)-'
Notes: - Operand value might be placed in its RPL extension
field either by specification on an ISTRPL6 macroinstruction operand
or by explicitly setting the field using the ISTRPL6X DSECT.
- See Coding default values for
information on coding operands on the RPL or the APPCCMD macroinstruction.
- Operand value might be placed in its RPL field
either by specification on an RPL macroinstruction operand or by explicitly
setting the field using the IFGRPL DSECT.
- ECB is meaningful only for asynchronous operations.
- EXIT is meaningful only for asynchronous operations.
- You can code more than one suboperand on OPTCD,
but no more than one from each group.
- KEEPSRB is meaningful only for synchronous operations.
- NKEEPSRB is meaningful only for synchronous operations.
Input parameters The following information
shows descriptions of the input parameters: - AAREA=rpl_extension_address_field
- AAREA=(rpl_extension_address_register)
- Specifies
the address of the LU 6.2 RPL extension that will be associated with
this APPCCMD macroinstruction. This field is labeled RPLAAREA in the
RPL.
- ACB=acb_address_field
- ACB=(acb_address_register)
- Specifies
the address of an access method control block that identifies the
application program that is issuing the APPCCMD macroinstruction. VTAM associates conversations with
application programs using the conversation ID (CONVID). The application
program associates conversations with transaction programs. Application
programs cannot issue APPCCMD macroinstructions in address spaces
other than the ACB address space. This field is labeled RPLDACB in
the RPL.
- AREA=data_area_address_field
- AREA=(data_area_address_register)
- Specifies
the data area in which the application program is to receive the data.
When the application program receives information other than data,
as indicated by the WHATRCV field of the RPL extension, nothing is
placed in this data area. This field is labeled RPLAREA in the RPL.
When OPTCD=XBUFLST, AREA specifies an address in which VTAM is to build an extended buffer
list. The AREALEN field of the RPL specifies a length of this area
that is a nonzero multiple of 48 bytes. Each entry in the buffer list
points to a CSM buffer. For each list entry, VTAM provides the CSM token, data length and
information necessary for the application to address the storage (address
and data space ALET). Note that a large buffer list area can help
prevent excessive API crossings. The format of the extended buffer
list pointed to by the AREA parameter is mapped by the ISTBLXEN mapping
DSECT.
- AREALEN=data_area_length
- AREALEN=(data_area_length_register)
- Specifies
the length value that is the maximum amount of data the application
program is to receive.
If OPTCD=XBUFLST, AREALEN specifies the
length of the area in which VTAM builds
a buffer list. The buffer list in turn points to the data that has
been received. The AREALEN parameter specifies an area length that
is a nonzero multiple of 48 bytes.
This field is labeled RPLBUFL
in the RPL.
- BRANCH
- Specifies
whether authorized path processing is to be used for application programs
running in supervisor state under a TCB. Application programs running
in TCB-mode supervisor state can use BRANCH=YES to obtain authorized
path services. The indicator resides within the RPLEXTDS field of
the RPL.
- BRANCH=NO
- Authorized path processing is not to be used. For application
programs running in problem state (non-supervisor state) under a TCB,
BRANCH=NO is the only option.
- BRANCH=YES
- Authorized path processing is to be used. For application programs
running under an SRB rather than under a TCB, the macroinstruction
is processed in this manner automatically, regardless of the actual
setting of the BRANCH field.
- CD
- Specifies
whether the LU immediately goes to SEND or whether the LU defers the
SEND transition by going into PEND_SEND when a change of direction
is received with no data.
- CD=DEFER
- Specifies that the conversation state will be in PEND_SEND state
when the SEND indicator of the WHATRCV field is set and none of the
data indicators are set.
- CD=IMMED
- Specifies that the conversation state will be in SEND state when
the SEND indicator of the WHATRCV field is set and none of the data
indicators are set.
- CONMODE
- Specifies
the mode for receiving normal information upon completion of the APPCCMD.
This field is labeled RPL6CMOD in the RPL extension.
- CONMODE=BUFFCA
- Specifies that the conversation is to be placed in buffer-continue-any
mode. It indicates that APPCCMD CONTROL=RECEIVE, QUALIFY=ANY|IANY
can be used to receive data and that the application program is to
receive data independently of the logical-record format of the data.
BUFFCA corresponds to FILL=BUFFER on the APPCCMD CONTROL=RECEIVE,
QUALIFY=SPEC|ISPEC macroinstruction.
- CONMODE=CS
- Specifies that the conversation is to be placed in continue-specific
mode. It indicates that only APPCCMD CONTROL=RECEIVE, QUALIFY=SPEC|ISPEC
can be used to receive data on this conversation. When the application
program issues APPCCMD CONTROL=RECEIVE, QUALIFY=SPEC|ISPEC, it must
indicate whether the data is to be received in terms of the logical-record
format of the data or independently of the logical-record format of
the data.
- CONMODE=LLCA
- Specifies that the conversation is to be placed in logical-record-continue-any
mode. It indicates that APPCCMD CONTROL=RECEIVE, QUALIFY=ANY|IANY
can be used to receive data on this conversation and that the application
program is to receive data in terms of the logical-record format of
the data. LLCA corresponds to FILL=LL on the APPCCMD CONTROL=RECEIVE,
QUALIFY=SPEC|ISPEC macroinstruction.
- CONMODE=SAME
- Specifies that the continuation mode of the conversation is to
remain unchanged.
- CONVID=32-bit_resource_id_field
- CONVID=(32-bit_resource_id_register)
- Specifies
the resource ID of the conversation. This field is labeled RPL6CNVD
in the RPL extension.
- CONXMOD
- Specifies
the mode for receiving expedited information upon completion of the
APPCCMD. This field is labeled RPL6CXMD in the RPL extension.
- CONXMOD=CA
- Specifies that the mode for expedited information is to be put
in such a state that expedited information can be received by either
a specific-type macroinstruction or an any-type macroinstruction,
such as, APPCCMD CONTROL=RCVEXPD, QUALIFY=SPEC|ISPEC or APPCCMD CONTROL=RCVEXPD,
QUALIFY=ANY|IANY.
- CONXMOD=CS
- Specifies that the mode for expedited information is to be put
in such a state that expedited information can be received only by
a specific-type macroinstruction, such as, APPCCMD CONTROL=RCVEXPD,
QUALIFY=SPEC or ISPEC.
- CONXMOD=SAME
- Specifies that the conversation mode for expedited information
is to remain unchanged at the completion of this macroinstruction.
- ECB
- Valid
only if OPTCD=ASY. Specifies how the application program requests
to be informed of the completion of the APPCCMD macroinstruction.
You cannot specify both ECB and EXIT on a single APPCCMD macroinstruction.
The indicator resides within the RPLOPT1 field of the RPL.
- ECB=INTERNAL
- Specifies that VTAM is
to post an internal ECB when the APPPCCMD macroinstruction completes.
- ECB=ecb_address_field
- ECB=(ecb_address_register)
- Specifies that VTAM is
to post an event control block (ECB) when an asynchronous APPCCMD
completes. Event_control_block_address is
the location of the ECB to be posted. The ECB can be any fullword
of storage aligned on a fullword boundary.
- EXIT=exit_routine_address_field
- EXIT=(exit_routine_address_register)
- Valid
only if OPTCD=ASY. It indicates the address of a routine to be scheduled
when the APPCCMD completes. You cannot specify both ECB and EXIT on
a single APPCCMD macroinstruction. The indicator resides within the
RPLEXTDS field of the RPL.
- FILL
- Specifies
whether the application program is to receive data in terms of the
logical-record format of the data. This parameter corresponds to FILL=LL|BUFFER
described in the LU 6.2 architecture. This field is labeled RPL6FILL
in the RPL extension.
- FILL=BUFF
- Specifies the application program is to receive data independently
of its logical-record format, up to the length specified by the AREALEN
field of the RPL. FILL=BUFF corresponds to FILL=BUFFER on the RECEIVE_AND_WAIT
verb, as described in the LU 6.2 architecture.
- FILL=LL
- Specifies the application program is to receive one logical record,
or whatever portion of the logical record is available, up to the
length specified by the AREALEN field of the RPL. FILL=LL corresponds
to FILL=LL on the RECEIVE_AND_WAIT verb, as described in the LU 6.2
architecture.
- OPTCD
- Specifies
the following processing options that can be selected for the macroinstruction
request:
- OPTCD=SYN
- Specifies that control is to be returned synchronously to the
application program when the function of the APPCCMD has completed.
The indicator resides within the RPLOPT1 field of the RPL.
- OPTCD=ASY
- Specifies that control is to be returned to the application program
immediately and that the application program is to be informed later
of the completion of the macroinstruction by the posting of an ECB
or the scheduling of an exit. The indicator resides within the RPLOPT1
field of the RPL.
- OPTCD=KEEPSRB
- Specifies that for a synchronous request issued in SRB mode, VTAM returns to the application
under the same SRB in which VTAM was
invoked. The indicator resides within the RPLOPT11 field of the RPL.
- OPTCD=NKEEPSRB
- Specifies that for a synchronous request issued in SRB mode, VTAM does not return to the application
under the same SRB in which VTAM was
invoked. The indicator resides within the RPLOPT11 field of the RPL.
- OPTCD=NBUFFLST
- Specifies that the AREA field contains the address of the area
in which the application is to receive the data. The RECLEN field
specifies the length of the data area.
- OPTCD=XBUFLST
- Specifies that the HPDT interface is to be used. VTAM builds an extended buffer list in the address
specified by the AREA parameter. Each entry in the buffer list points
to a CSM buffer containing the data being received by the application.
The indicator is labeled RPLXBFL and resides within the RPLOPT6 field
of the RPL.
Note: Application programs running in TCB-mode supervisor
state must specify BRANCH=YES for HPDT requests.
- RPL=rpl_address_field
- RPL=(rpl_address_register)
- Specifies
the address of the request parameter list that contains information
to be used during the processing of the APPCCMD macroinstruction.
- VTROUTA=vector_address_field
- VTROUTA=(vector_address_register)
- Specifies the address of the area where the application places
vector list information for VTAM.
If OPTCD=XBUFLST is specified, this field must point to the XBUFLST-receive
vector (ISTAPC82), which is mapped by ISTAPCVL. (Refer to z/OS Communications Server: SNA Programmer's
LU 6.2 Guide for more information.)
This field is
labeled RPL6VAOA in the RPL extension.
- VTROUTL=vector_length_field
- VTROUTL=(vector_length_register)
- Specifies the length of the area where the application places
vector list information for VTAM.
This field is labeled RPL6VAOL in the RPL extension.
RPL and RPL extension fields modified by macroinstruction The
following information shows descriptions of RPL and RPL extension
fields: - CONSTATE
- The
field in the RPL6 extension that indicates the state of the conversation.
This field is labeled RPL6CCST in the RPL extension.
For half-duplex
conversations, this field can have t the following values: - X'01'
- SEND
- X'02'
- RECEIVE
- X'03'
- RECEIVE_CONFIRM
- X'04'
- RECEIVE_CONFIRM_SEND
- X'05'
- RECEIVE_CONFIRM_DEALLOCATE
- X'07'
- PENDING_END_CONVERSATION_LOG
- X'08'
- END_CONVERSATION
- X'09'
- PENDING_SEND
- X'0A'
- PENDING_RECEIVE_LOG
For full-duplex conversations, this field
can have the following values: - X'80'
- FDX_RESET
- X'81'
- SEND/RECEIVE
- X'82'
- SEND_ONLY
- X'83'
- RECEIVE_ONLY
- X'84'
- PENDING_SEND/RECEIVE_LOG
- X'85'
- PENDING_RECEIVE-ONLY_LOG
- X'86'
- PENDING_RESET_LOG
- EXPDLEN
- The
field in the RPL6 that shows the length of the expedited data waiting
to be received. This field has meaning only when EXPDRCV=YES. This
field is labeled RPL6EXDL in the RPL extension.
- EXPDRCV
- The
field in the RPL6 that indicates whether expedited data is waiting
to be received. This field is labeled RPL6EXDR in the RPL extension.
- FDB2
- The
field in the RPL in which a global VTAM secondary
return code is returned to the application program. It is labeled
RPLFDB2 in the RPL.
- FMH5LEN
- The
field in the RPL extension that returns the length of the FMH-5 waiting
to be received by the application program. If multiple FMH-5s are
waiting to be received, FMH5LEN specifies the length of the longest
FMH-5 to be received by the application program. This field has meaning
only when FMH5RCV=YES. This field is labeled RPL6MH5L in the RPL extension.
- FMH5RCV
- The
field in the RPL extension that returns an indication of whether an
FMH-5 has been received. The indication is either YES or NO (RPL6RMH5
set on or off). This field is labeled RPL6RMH5 in the RPL extension.
- YES (B'1')
- One or more FMH-5s have been received from partner application
programs. The FMH5RCV field continues to be set to YES as long as
an FMH-5 is waiting to be received by the application program. The
application program must issue APPCCMD CONTROL=RCVFMH5 in order to
receive an FMH-5.
- NO (B'0')
- No FMH-5s are waiting to be received by the application program.
- LOGRCV
- The
field in the RPL extension that returns an indication of whether error
log data is expected. The indication is either YES or NO (RPL6RLOG
set on or off). This field is labeled RPL6RLOG in the RPL extension.
- YES (B'1')
- An FMH-7 was received that specified that error log data follows.
The application program must issue APPCCMD CONTROL=RECEIVE, QUALIFY=SPEC|ISPEC
in order to retrieve the log data. It is the responsibility of the
application program to perform an optional receive check after issuing
APPCCMD CONTROL=RECEIVE, QUALIFY=SPEC|ISPEC to determine whether the
expected log data was sent by the partner LU. The data must be error
log data and it must be in the form of a GDS variable.
LOGRCV=YES
only if the RCPRI field of the RPL extension contains one of the following
values: - X'0004'
- ALLOCATION_ERROR
- X'0014'
- DEALLOCATE_ABEND_PROGRAM
- X'0018'
- DEALLOCATE_ABEND_SERVICE
- X'001C'
- DEALLOCATE_ABEND_TIMER
- X'0030'
- PROGRAM_ERROR_NO_TRUNC
- X'0034'
- PROGRAM_ERROR_PURGING
- X'0038'
- PROGRAM_ERROR_TRUNC
- X'003C'
- SERVICE_ERROR_NO_TRUNC
- X'0040'
- SERVICE_ERROR_PURGING
- X'0044'
- SERVICE_ERROR_TRUNC
- X'0048'
- RESOURCE_FAILURE,_NO_RETRY
- X'005C'
- USER_ERROR_CODE_RECEIVED
- NO (B'0')
- Either no error indicator was received or an error indicator was
received but indicated that no log data follows.
- RCPRI
- The
field in the RPL extension in which an APPCCMD-specific primary return
code is returned to the application program. This field has meaning
only when RTNCD=X'00' and FDB2=X'0B'. This field
is labeled RPL6RCPR in the RPL extension.
- RCSEC
- The
field in the RPL extension in which an APPCCMD-specific secondary
return code is returned to the application program. This field has
meaning only when RTNCD=X'00' and FDB2=X'0B'. This
field is labeled RPL6RCSC in the RPL extension. The combination of
the RCPRI and RCSEC fields indicates the result of the macroinstruction
processing.
- RECLEN
- The
field in the RPL that returns to the application program the actual
amount of data the application program received. If the application
program receives information other than data, this variable is set
to 0. When OPTCD=XBUFLST is specified, VTAM returns
the actual length of the extended buffer list that is built in the
buffer list area pointed to by the AREA operand. This field is labeled
RPLRLEN in the RPL.
- RTNCD
- The
field in the RPL in which a global VTAM primary
return code is returned to the application program. This field is
labeled RPLRTNCD in the RPL.
- SENSE
- The
field in the RPL extension that returns a 32-bit sense code. It is
labeled RPL6SNSI in the RPL extension. This field has meaning only
if the RCPRI field is set to a nonzero value. The sense code also
can be set when the return code is RESOURCE_FAILURE_NO_RETRY. This
code indicates why the session for the conversation was deactivated.
Not all RCPRI values have sense data associated with them. If the
RCPRI field indicates USER_ERROR_CODE_RECEIVED, the SENSE field contains
an FMH-7 sense code that was not interpreted by VTAM.
- SIGDATA
- The
field in the RPL extension in which the signal code and signal extension
fields of a received SIGNAL RU are returned to the application program.
This field has meaning only when SIGRCV=YES. This field is labeled
RPL6SGNL in the RPL extension.
- X'00010001' indicates a REQUEST_TO_SEND notification
has been received from the remote application program.
Note: The SIGDATA field is reserved if, on the macroinstruction
that initiated the conversation (APPCCMD CONTROL=ALLOC or APPCCMD
CONTROL=RCVFMH5), the application specified RTSRTRN=EXPD.
- SIGRCV
- The
field in the RPL extension that returns an indication of whether an
application program's partner has requested permission to send. This
field and the SIGDATA field correspond to the REQUEST_TO_SEND_RECEIVED
parameter described in the LU 6.2 architecture.
Note: The SIGRCV
field is reserved if, on the macroinstruction that initiated the conversation
(APPCCMD CONTROL=ALLOC or APPCCMD CONTROL=RCVFMH5), the application
specified RTSRTRN=EXPD.
The indication is either YES or
NO (RPL6RSIG bit set on or off). It is labeled RPL6RSIG in the RPL
extension. - YES (B'1')
- A SIGNAL RU has been received from the partner LU. The values
carried in the signal code and signal extension fields of the SIGNAL
RU are returned to the application program in the SIGDATA field.
- NO (B'0')
- No SIGNAL RU has been received from the partner LU. When SIGRCV=NO,
the SIGDATA field contains no meaningful information.
- USERFLD
- Specifies
4 bytes of user data that the application program requests be associated
with a conversation. Whenever an APPCCMD completes, VTAM places in the USERFLD field of the RPL
extension the 4 bytes that were supplied on the APPCCMD CONTROL=ALLOC
macroinstruction (if the conversation was initiated by the local application
program) or the APPCCMD CONTROL=RCVFMH5 macroinstruction (if the conversation
was initiated by a remote application program). This field is labeled
RPL6USR in the RPL extension.
- WHATRCV
- The
field in the RPL extension that indicates what the application program
received. It is labeled RPL6WHAT in the RPL extension. The application
program should examine the WHATRCV field only when RCPRI indicates X'0000'.
Otherwise, WHATRCV has no meaning.
When RCPRI indicates OK, one
or more bits in the mask can be turned on (contain a value
of B‘1’) to indicate the type of information that has been received.
For instance, if the application program is being passed both conversation
data and a request for confirmation, both the DATA and CONFIRM bits
will be set on; the other bits will be set off.
The
2-byte WHATRCV mask has the format shown in Table 1.
Table 1. Format of WHATRCV
mask| RPL6RCV1 |
RPL6RCV2 |
|---|
| Bit |
Meaning |
Bit |
Meaning |
|---|
| 0 |
DATA |
0 |
PARTIAL_PS_HEADER |
| 1 |
DATA_COMPLETE |
1–7 |
Reserved |
| 2 |
DATA_INCOMPLETE |
|
|
| 3 |
SEND |
|
|
| 4 |
CONFIRM |
|
|
| 5 |
DEALLOCATE |
|
|
| 6 |
LOG_DATA |
|
|
| 7 |
PS_HEADER |
|
|
For example, a WHATRCV value indicating that DATA
has been received would be represented by X'8000'. Refer
to z/OS Communications Server: SNA Programmer's
LU 6.2 Guide for a discussion of the meaning of this field.
State changes See the description of the
WHATRCV mask for state changes when RCPRI indicates OK.
See Return codes for state changes associated with
other return codes.
Return codes The following (RCPRI, RCSEC)
combinations can be returned to the application program when it issues
this APPCCMD macroinstruction. See Return codes for
a description of these return codes.
| RCPRI |
RCSEC |
Meaning |
|---|
| X'0000' |
X'0000' |
OK |
| X'0000' |
X'0003' |
RECEIVE_SPECIFIC_REJECTED |
| X'0000' |
X'0008' |
NO_IMMEDIATELY_AVAILABLE_INFORMATION |
| X'0004' |
X'0002' |
ALLOCATION_ERROR—CONVERSATION_TYPE_MISMATCH |
| X'0004' |
X'0003' |
ALLOCATION_ERROR—PIP_NOT_ALLOWED |
| X'0004' |
X'0004' |
ALLOCATION_ERROR—PIP_NOT_SPECIFIED_CORRECTLY |
| X'0004' |
X'0005' |
ALLOCATION_ERROR—SECURITY_NOT_VALID |
| X'0004' |
X'0007' |
ALLOCATION_ERROR—SYNC_LEVEL_NOT_SUPPORTED_ BY_PROGRAM |
| X'0004' |
X'0008' |
ALLOCATION_ERROR—TPN_NOT_RECOGNIZED |
| X'0004' |
X'0009' |
ALLOCATION_ERROR—TRANS_PGM_NOT_AVAIL_NO_ RETRY |
| X'0004' |
X'000A' |
ALLOCATION_ERROR—TRANS_PGM_NOT_AVAIL_RETRY |
| X'0004' |
X'000B' |
ALLOCATION_ERROR—CANNOT_RECONNECT_TRANS_ PGM_NO_RETRY |
| X'0004' |
X'000D' |
ALLOCATION_ERROR—RECONNECT_NOT_SUPPORTED_ BY_PGM |
| X'0014' |
X'0000' |
DEALLOCATE_ABEND_PROGRAM |
| X'0018' |
X'0000' |
DEALLOCATE_ABEND_SERVICE |
| X'001C' |
X'0000' |
DEALLOCATE_ABEND_TIMER |
| X'002C' |
X'0002' |
PARAMETER_ERROR_INVALID_CONVERSATION_ID |
| X'002C' |
X'0002' |
PARAMETER_ERROR—INVALID_CONVERSATION_ID |
| X'002C' |
X'0008' |
PARAMETER_ERROR—SUPPLIED_LENGTH_INSUFFICIENT |
| X'002C' |
X'000C' |
PARAMETER_ERROR—ZERO_EXIT_FIELD |
| X'002C' |
X'000D' |
PARAMETER_ERROR—ZERO_ECB_FIELD |
| X'002C' |
X'000E' |
PARAMETER_ERROR—REQUEST_INVALID_FOR_ADDRESS_ SPACE |
| X'002C' |
X'000F' |
PARAMETER_ERROR—CONTROL_BLOCK_INVALID |
| X'002C' |
X'0010' |
PARAMETER_ERROR—INVALID_DATA_ADDRESS_OR_ LENGTH |
| X'002C' |
X'0011' |
PARAMETER_ERROR—PREVIOUS_MACROINSTRUCTION_ OUTSTANDING |
| X'002C' |
X'001F' |
PARAMETER_ERROR—APPCCMD_ISSUED_FOR_NON-APPC |
| X'002C' |
X'0030' |
PARAMETER_ERROR— STORAGE_TYPE_NOT_VALID |
| X'002C' |
X'0032' |
PARAMETER_ERROR— UNEXPECTED_VECTOR_PROVIDED_ON_APPCCMD |
| X'002C' |
X'0033' |
PARAMETER_ERROR— A_REQUIRED_VECTOR_WAS_NOT_PROVIDED_ OR_SPECIFIED_INCORRECTLY |
| X'0030' |
X'0000' |
PROGRAM_ERROR_NO_TRUNC |
| X'0034' |
X'0000' |
PROGRAM_ERROR_PURGING |
| X'0038' |
X'0000' |
PROGRAM_ERROR_TRUNC |
| X'003C' |
X'0000' |
SERVICE_ERROR_NO_TRUNC |
| X'0040' |
X'0000' |
SERVICE_ERROR_PURGING |
| X'0044' |
X'0000' |
SERVICE_ERROR_TRUNC |
| X'0048' |
X'0000' |
RESOURCE_FAILURE_NO_RETRY |
| X'004C' |
X'0000' |
RESOURCE_FAILURE_RETRY |
| X'0050' |
X'0000' |
STATE_ERROR |
| X'005C' |
X'0000' |
USER_ERROR_CODE_RECEIVED—FOLLOWING_NEGATIVE_ RESPONSE |
| X'005C' |
X'0001' |
USER_ERROR_CODE_RECEIVED—WITHOUT_NEGATIVE_ RESPONSE |
| X'0070' |
X'0000' |
TEMPORARY_STORAGE_SHORTAGE |
| X'0078' |
X'0000' |
VTAM_INACTIVE_FOR_YOUR_ACB |
| X'007C' |
X'0000' |
REQUEST_ABORTED |
| X'0084' |
X'0000' |
STORAGE_SHORTAGE |
| X'0088' |
X'0000' |
CANCELLED_BY_REJECT_OR_DEALLOCATE_ABEND |
| X'008C' |
X'0000' |
PARTNER_COMMITTED_PROTOCOL_VIOLATION |
| X'0090' |
X'0000' |
APPLICATION_NOT_APPC_CAPABLE |
| X'00A0' |
X'0002' |
REQUEST_NOT_ALLOWED—REQUEST_BLOCKED |
| X'00A8' |
X'0000' |
ENVIRONMENT_ERROR_OS_LEVEL_DOES_NOT_SUPPORT_ REQUESTED_FUNCTION |
| X'00A8' |
X'0001' |
ENVIRONMENT_ERROR—SUSPEND_FAILURE |
| X'00A8' |
X'0002' |
ENVIRONMENT_ERROR—RESUME_FAILURE |
| X'00A0' |
X'0006' |
PROGRAM_NOT_AUTHORIZED_FOR_ REQUESTED_FUNCTION |
| X'00B4' |
X'0001' |
CSM_DETECTED_ERROR—NOT_SPECIFIED |
|
z/OS Communications Server: SNA Programmer's LU 6.2 Reference
Copyright IBM Corporation 1990, 2014