N_CONN_RES Primitive

AIXLink/X.25 1.1 for AIX: Guide and Reference

N_CONN_RES Primitive

Purpose

Allows the destination NPI application to accept an incoming connection request.

Structure

This primitive consists of one M_PROTO message block with the following structure:

typedef struct {
   ulong PRIM_type;
   ulong TOKEN_value;
   ulong RES_length;
   ulong RES_offset;
   ulong SEQ_number;
   ulong CONN_flags;
   ulong QOS_length;
   ulong QOS_offset;
} N_conn_res_t;

Note: QOS_length QOS_length should be 0 (zero) since QOS parameters are not supported.

Description

The format of this message is one M_PROTO message block followed by one or more M_DATA blocks. The M_DATA blocks contain user data which is optional. Any integral number of octets, up to the limit imposed by the underlying network, can be passed. Note that an odd-length CUD string is not allowed.

Parameters

PRIM_type

Specifies the N_CONN_RES primitive.

TOKEN_value

Identifies the stream on which the NS user wants to establish the network connection (NC). The value of this parameter can be one of the following:

>0	Indicates the NS user wants to establish the NC on a stream other than the stream on which the N_CONN_IND primitive arrived.
0	Indicates the NS user wants to establish the NC on the same stream on which the N_CONN_IND primitive arrived.

The NS user determines the stream's value by issuing an N_BIND_REQ primitive with the TOKEN_REQUEST flag set. The N_BIND_ACK primitive returns the token value.

RES_length

Specifies the length of the responding address parameter. The responding address parameter conveys the network address of the NS user to which the NC has been established. Under certain circumstances, such as call redirection or generic addressing, the parameter value may be different from the destination address parameter specified in the corresponding N_CONN_REQ primitive.

RES_offset

Indicates the offset of the responding address from the beginning of the M_PROTO message block.

SEQ_number

Indicates the sequence number of the N_CONN_RES primitive. The NS provider uses this number to associate the N_CONN_RES with an outstanding N_CONN_IND message. An invalid sequence number results in an NBADSEQ error.

CONN_flags

Matches the value of the CONN_flags parameter of the N_CONN_REQ primitive. The CONN_flags parameter can have the following value:

REC_CONF_OPT

Indicates the use and/or availability of the receipt confirmation service on the NC. The receipt confirmation service must be provided in the network service to be used on the NC. If this flag is set, it must match the value of the CONN_flags parameter of the N_CONN_REQ primitive. This uses the X.25 D bit.

QOS_length

This should be set 0 (zero) since QOS parameters are not supported.

QOS_offset

This should be set 0 (zero) since QOS parameters are not supported.

Acknowledgments

The NS provider generates one of the following acknowledgments upon receipt of the N_CONN_RES primitive:

Successful	The N_OK_ACK primitive indicates the N_CONN_RES primitive succeeded.
Unsuccessful	The N_ERROR_ACK primitive indicates that a non-fatal error occurred.

Error Codes

The applicable non-fatal errors are defined as follows:

NBADDATA	Indicates the amount of user data specified was outside the range supported by the NS provider.
NBADOPT	Indicates the options were either in an incorrect format or contained illegal information.
NBADSEQ	Indicates the sequence number specified in the primitive was incorrect or illegal.
NOUTSTATE	Indicates the primitive was issued from an invalid state.
NSYSERR	Indicates a system error. The error is indicated in the primitive.

Implementation Specifics

The N_CONN_RES primitive is part of X.25 Licensed Program.

[ Previous | Next | Contents | Search ]