HP CommonIO Products Manual do Utilizador descarregar pdf (Página 241)

Diagnostic Messages

Diagnostic Message Example

Appendix C 241

Diagnostic Message Example

An example diagnostic message generated by the network from a CLEAR

REQUEST packet is shown below:

Clear request

LCGN: 0 LCN : 32

Clearing Cause [0] : DTE originated.

Diagnostic [241] :

In the example above, LCGN is the Logical Channel Group Number and

LCN is the Logical Channel Number (the number denoting the logical

association between a DTE and DTE connected by a VC). Refer to the

discussion below for more information on cause codes.

Diagnostic codes are generated by the network and may appear in octet 5

of RESTART INDICATION, RESET INDICATION, or CLEAR

INDICATION packets. If a diagnostic field is not present in a CLEAR

INDICATION or RESET INDICATION packet, 0 is returned as the

diagnostic code.

A cause code and message is usually returned from the network with

each diagnostic. Diagnostic codes and messages are usually displayed

only when tracing or logging is on, the x25check utility is run, or cause

and diagnostic codes are printed in level 3 application programs. Refer to

the listing of diagnostic codes later in this appendix for more

information.

In the descriptions in the diagnostic listing, a REQUEST or ACCEPTED

packet refers to a packet generated by the local application and an

INDICATION or CONFIRM packet refers to a packet received from the

network. The requests in which a diagnostic code can be found are shown

after the numeric code of the diagnostic.

Once the application specifies CLEAR or RESET cause and diagnostic

codes, this code combination is used for all RESET REQUEST packets

generated by the application. This combination is also used for the

CLEAR REQUEST generated when the application calls close() or

shutdown() on a given socket.

1 2 ... 236 237 238 239 240 241 242 243 244 245 246 ... 260 261

Sem comentários

HP CommonIO Products Manual do Utilizador Página 241