|
|
|
|
SNAP-IX uses this data indication to route an NMVT received from a remote node to an NMVT-level application that has registered to receive NMVTs. For information about how SNAP-IX determines which MS application receives an incoming NMVT, see NMVT Routing.
This indication is returned using the callback routine that the application supplied on the REGISTER_NMVT_APPLICATION verb. For more information about the requirements for this callback routine, see The Callback Routine Specified on the ms_async Entry Point.
typedef struct nmvt_received
{
AP_UINT16 opcode; /* Verb operation code */
unsigned char reserv2; /* reserved */
unsigned char format; /* reserved */
AP_UINT16 primary_rc; /* Primary return code */
AP_UINT32 secondary_rc; /* Secondary return code */
unsigned char pu_name[8]; /* Physical unit name */
unsigned char reserv3[6]; /* reserved */
AP_UINT16 nmvt_length; /* Length of incoming NMVT */
unsigned char *nmvt; /* NMVT data */
} NMVT_RECEIVED;
SNAP-IX includes the following parameters when it sends the NMVT_RECEIVED indication to the MS application:
AP_NMVT_RECEIVED
Name of the physical unit from which the NMVT originated. This is an 8-byte EBCDIC type-A string, padded on the right with EBCDIC spaces if the name is shorter than 8 bytes.
If the incoming NMVT requires a response, the application must send the response using TRANSFER_MS_DATA and must set the pu_name parameter of TRANSFER_MS_DATA to the pu_name returned here.
Length of NMVT data, which can be up to 512 bytes.
Full NMVT, containing MS major vector of the type or types specified on the REGISTER_NMVT_APPLICATION.
|
|
|
 |
|