Appendix B. Supported SNA Request Units

This appendix lists all request units (RUs) that can be sent or received by a transaction program that uses IRIS SNA LU 0-3. The RUs can be sent as requests, positive responses, or negative responses.

In most cases, the value assigned to the constants represent the corresponding SNA-defined request code. The following constants were assigned different values so that each constant has a unique value: P_NSPE, P_INTSLF, P_TRMSLF, P_RECFMS, P_REQMS.

Sending RUs

When sending request RUs, use the sndru verb and if a positive or negative response is sent, use the accru or rejru verb, respectively. Table B-1 shows the ru_cmd parameter and whether RU is a request or response. The ru parameter is specified as being Required, Not Required, or Optional.

Table B-1. ru_cmd and ru Parameters for Sending RUs

ru_cmd

 

ru

P_BID

Response

Not Required

P_BIND

Response

Optional

P_CANCEL

Request

Not Required

P_CHASE

Request

Not Required

P_CHASE

Response

Not Required

P_DAT

Response

Not Required

P_DAT

Request

Optional (ru_len=0)

P_ECHTST

Response

Not Required

P_INTSLF

Request

Required

P_LUSTAT

Request

Required

P_NMVT

Request

Required

P_NMVT

Response

Not Required

P_NOTIFY

Request

Required

P_QC

Request

Not Required

P_QEC

Request

Not Required

P_RECFMS

Request

Required

P_RELQ

Request

Not Required

P_REQECH

Request

Required

P_REQMS

Response

Not Required

P_RQR

Request

Not Required

P_RSHUTD

Request

Not Required

P_RTR

Request

Not Required

P_SHUTC

Request

Not Required

P_SIGNAL

Request

Required

P_SIGNAL

Response

Not Required

P_TRMSLF

Request

Required

P_UNBIND

Request

Not Required


Receiving RUs

The receiving RUs can be requests or responses. The type is indicated in the ru_cmd and wht_rcv parameters. Respond to the wht_rcv types of P_FMH, FMH, P_DATA, and P_SNA by using the accru or rejru verb. The layout of the wht_rcv type P_NOTIF is found in Appendix C, "Notification Events."
Table B-2 shows the receiving RU parameters.

Table B-2. The ru_comd and wht_rcv Parameters for Sending RUs

ru_cmd

 

wht_rcv

P_ACTLU

Request

P_NOTIF

P_ACTPU

Request

P_NOTIF

P_BID

Request

P_SNA

P_BIND

Request

P_SNA

P_CANCEL

Request

P_NOTIF

P_CANCEL

Response

P_NRSP/P_PRSP

P_CHASE

Request

P_SNA

P_CHASE

Response

P_NRSP/P_PRSP

P_CLEAR

Request

P_NOTIF

P_DACTLU

Request

P_NOTIF

P_DACTPU

Request

P_NOTIF

P_DAT

Request

P_DATA/P_FMH

P_DAT

Response

P_NRSP/P_PRSP

P_ECHTST

Request

P_SNA

P_INTSLF

Response

P_NRSP/P_PRSP

P_LUSTAT

Request

P_NOTIF

P_LUSTAT

Response

P_NRSP/P_PRSP

P_NMVT

Request

P_SNA

P_NMVT

Response

P_NRSP/P_PRSP

P_NOTIFY

Request

P_NOTIF

P_NOTIFY

Response

P_NRSP/P_PRSP

P_NSPE

Request

P_NOTIF

P_QC

Request

P_NOTIF

P_QC

Response

P_NRSP/P_PRSP

P_QEC

Request

P_NOTIF

P_QEC

Response

P_NRSP/P_PRSP

P_RECFMS

Response

P_NRSP/P_PRSP

P_RELQ

Request

P_NOTIF

P_RELQ

Response

P_NRSP/P_PRSP

P_REQECH

Response

P_NRSP/P_PRSP

P_REQMS

Request

P_SNA

P_RQR

Response

P_NRSP/P_PRSP

P_RSHUTD

Response

P_NRSP/P_PRSP

P_RTR

Response

P_NRSP/P_PRSP

P_SDT

Request

P_NOTIF

P_SHUTC

Response

P_NRSP/P_PRSP

P_SHUTD

Request

P_NOTIF

P_SIGNAL

Request

P_SNA

P_SIGNAL

Response

P_NRSP/P_PRSP

P_STSN

Request

P_NOTIF

P_TRMSLF

Response

P_NRSP/P_PRSP

P_UNBIND

Request

P_NOTIF

P_UNBIND

Response

P_NRSP/P_PRSP