30.01.2013 Views

DCP Series Telcon Message Manual - Public Support Login - Unisys

DCP Series Telcon Message Manual - Public Support Login - Unisys

DCP Series Telcon Message Manual - Public Support Login - Unisys

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Event 5 EVENT/ERROR DETECTED AT L5 (SESSION)<br />

Event 5 EVENT/ERROR DETECTED AT L5 (SESSION)<br />

EVENT/ERROR DETECTED AT L5 (SESSION)<br />

Description: A significant event has taken place, or an error has been discovered in<br />

the DCA protocol stack layer 5, Session Layer.<br />

Action: Dependent on supplementary message (or procedure name) as follows.<br />

Supplementary <strong>Message</strong>s for Class 13, Event 05<br />

ATTACH TO DTP<br />

DTPX<br />

Description: DTPX has received an error in response to the registration with DTP on<br />

behalf of an SSU registering with DTPX. <strong>Telcon</strong> generates this CENLOG.<br />

Description: A bad HIC has been received from the session service user or from the<br />

peer session services.<br />

R8: DTPX error status (shown in hexadecimal):<br />

0 OK status.<br />

1 Missing parameter.<br />

2 No end of packet.<br />

3 Error AU HIC.<br />

4 Error AU label length.<br />

6 No AS$SPEX.<br />

8 Error in DTPX header.<br />

9 Error in EUAFO.<br />

A Error VER HIC.<br />

B Error IDENT length.<br />

C Past FTXT offset.<br />

F Unexpected table type from DSRV.<br />

10 Zero AU label.<br />

12 Access authority error.<br />

13 Directory information base access error.<br />

14 Invalid interface message type.<br />

15 Invalid transport type.<br />

16 Transport service not available.<br />

R9: CENLOG code = CE$ICR = 45<br />

R10: The address of the procedure in DTPX in which the error occurred.<br />

R11: First HIC of message if a control message, otherwise zero.<br />

7436 0728–303 13–81

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!