DCP Series Telcon Message Manual - Public Support Login - Unisys

Title 

DCP Series Telcon Message Manual 7436 0728–303 

o New Release o Revision • Update o New Mail Code 

IMPORTANT 

This hardcopy version of the document (–303) replaces all earlier versions and includes updates that are not 

contained on the CD6R2B CD-ROM. 

If you have a support contract, you can view an online version of this document on the Product Support Web 

Site at http://www.support.unisys.com/. 

This manual is an update, with changes to Sections 3 and 6. 

The DCP Series Telcon Message Manual contains: 

• Critical Event Notification and Logging (CENLOG) messages that appear on NMS consoles 

• Corrective actions for Network Management Services (NMS) 

• Error conditions 

• Status messages 

• Directory Service Agent (DSA) messages 

• Remote File Services (RFS) messages 

The appendixes consist of acronyms and abbreviations and diagnostic codes and initialization error codes for: 

• X.25 PSCS program product 

• IBM� and Unisys Sense Data 

This manual is intended for Telcon system network analysts and operators who are responsible for troubleshooting. 

To order paper copies of this document 

• Unisys customers, order through the electronic Book Store at http://www.bookstore.unisys.com. 

• Customers outside the United States, contact your Unisys sales office. 

Product Information 

Announcement 

• Unisys personnel, order through the electronic Book Store at http://iwww.bookstore.unisys.com. 

Comments about documentation can be sent through e-mail to doc@unisys.com. 

Announcement only: Announcement and attachments: System: DCP Series 

Release: Level 10R3A 

Date: October 1999 

Part number: 7436 0728–303

DCP SERIES 

Telcon 

Message 

Manual 

CD 6R2B October 1999 

Printed in USA 

Priced Item 7436 0728–303

Format these characters as “white” to force printing of blank page.

DCP SERIES 


Message 

Manual 

Copyright � 1999 Unisys Corporation. 

All rights reserved. 

Unisys is a registered trademark of Unisys Corporation. 

This revision includes: –303. 

CD 6R2B October 1999 

Printed in USA 

Priced Item 7436 0728–303 

Unisys

NO WARRANTIES OF ANY NATURE ARE EXTENDED BY THIS DOCUMENT. Any product or related information 

described herein is only furnished pursuant and subject to the terms and conditions of a duly executed agreement to 

purchase or lease equipment or to license software. The only warranties made by Unisys, if any, with respect to the 

products described in this document are set forth in such agreement. Unisys cannot accept any financial or other 

responsibility that may be the result of your use of the information in this document or software material, including 

direct, special, or consequential damages. 

You should be very careful to ensure that the use of this information and/or software material complies with the laws, 

rules, and regulations of the jurisdictions with respect to which it is used. 

The information contained herein is subject to change without notice. Revisions may be issued to advise of such 

changes and/or additions. 

Notice to Government End Users: The software and accompanying documentation are delivered and licensed as 

“commercial computer software” and “commercial computer software documentation” as those terms are used in 48 

C.F.R. § 12.212 and 48 C.F.R. § 227.7202-1 through 227.7202-4, as applicable. The Government shall receive only those 

rights provided in the standard commercial software license, or where applicable, the restricted and limited rights 

provisions of the contract FAR or DFARS (or equivalent agency) clause. 

Correspondence regarding this publication can be e-mailed to doc@unisys.com. 

Unisys is a registered trademark of Unisys Corporation. 

All other terms mentioned in this document that are known to be trademarks or service marks have been appropriately 

capitalized. Unisys Corporation cannot attest to the accuracy of this information. Use of a term in this document should 

not be regarded as affecting the validity of any trademark or service mark.

DCP Series 


Message Manual 

CD 6R2B 

DCP Series 


Message Manual 

CD 6R2B 

7436 0728–303 7436 0728–303 

Bend here, peel upwards and apply to spine.

Format these characters as “white” to force printing of 

blank page.

Contents 

About This Manual .................................................................................... xiii 

Section 1. Introduction 

CENLOG Class Types ............................................................. 1–1 

CENLOG Class Attributes ......................................... 1–2 

CENLOG Display Formats ...................................................... 1–3 

Mini Format Without Central Display .......................... 1–3 

Mini Format With Central Display ............................... 1–4 

Brief Format ............................................................ 1–4 

Long Format ........................................................... 1–5 

Analyzing CENLOG Files ........................................................ 1–6 

NMS Operator Actions for CENLOG Events .......................... 1–8 

Detailed CENLOG Event Descriptions .................................... 1–8 

UNILPH CENLOG Entry Descriptions ..................................... 1–9 

Class 1 CENLOG Messages ................................................... 1–10 

Section 2. Class 2 CENLOG Messages 

Event 1 DEBUG EVENT ......................................................... 2–1 

Events 2–16 Not Defined ....................................................... 2–2 


Event 1 PROGRAM PRODUCT NOT PRESENT ...................... 3–1 

Event 2 X.25 GATEWAY EVENT ............................................ 3–6 

Event 3 *** X.21 ERR *** R14, R15 = PORT ID ............... 3–7 

Event 4 SNA/net Event ......................................................... 3–8 

Event 5 DCPOSITP EVENT .................................................... 3–9 

Event 6 DCPX25-PNCS EVENT ............................................. 3–11 

Event 7 DCPX25-PNCS EVENT ............................................. 3–12 

Event 8 VIDEOTEX EVENT .................................................... 3–13 


Event 12 TCP–IP GATEWAY EVENT ...................................... 3–18 

Event 13 P1X24 HIGH PRIORITY EVENT .............................. 3–73 

Event 14 TNAS END USER EVENT ........................................ 3–74 

Event 15 SNA GATEWAY EVENT LOG .................................. 3–75 

Event 16 CENLOG Messages ............................................... 3–76 

Supplementary Messages for Class 03, Event 16 ....... 3–76 

7436 0728–303 iii

Contents 


Event 1 *** X.21 MSG *** R14, R15 = PORT, ID R8: 

4XXX=CPS# 5,6=ID MSG ................................................. 4–1 


Event 12 AX25 EVENT ........................................................... 4–3 

Event 13 ALC GATEWAY EVENT ............................................ 4–4 

Event 14 P1X24 LOW PRIORITY EVENT ................................ 4–5 

Event 15 LOW SPEED BAUDOT EVENT AIR/net LSB ............. 4–6 

Event 16 CENLOG Messages ................................................. 4–7 



Event 1 ‘CALL’ INTERFACE RETURNED ERROR 

(ABNORMAL) ...................................................................... 5–1 

Event 2 UNABLE TO RESTART PORT PROCESSOR ............... 5–2 

Event 3 CP QUEUE FULL CONDITION .................................... 5–3 

Event 4 QUEUE ITEM UNAVAILABLE / ACCESS ERROR ........ 5–6 

Event 5 DYNAMIC SYSTEM SEGMENT ERROR ...................... 5–7 

Event 6 INVALID COMMAND / CONTROL / HIC RECEIVED ... 5–11 

Event 7 QUEUE OR LINK AREA ERROR ................................. 5–23 

Event 8 QUEUE ACCESS / ADDITION ERROR ........................ 5–25 

Event 9 INVALID RUN TIME TABLE ACCESS .......................... 5–27 

Event 10 INVALID RUN TIME INDEX VALUE ........................... 5–33 

Event 11 INVALID / UNRECOGNIZABLE INPUT PARAMETER 

FOR PROCEDURE .............................................................. 5–35 

Event 12 MESSAGE PROCESSING ERROR DETECTED .......... 5–44 


Event 13 PROCEDURE PROCESSING ERROR (INTERNAL) .... 5–57 

Event 14 CONFIGURATION FILE ACCESS / REQUEST 

ERROR ............................................................................... 5–71 

Event 15 CONFIGURATION ERROR DETECTED / 

UNDEFINED ........................................................................ 5–75 





Event 1 TERMINAL SIGN-ON .................................................. 6–1 

Event 2 TERMINAL SIGN-OFF ................................................ 6–2 

Event 3 TERMINAL SIGN-ON (AUTO ALLOCATED) ................. 6–3 

Event 4 TERMINAL SIGN-OFF (TIME-OUT) ............................. 6–4 

Event 5 SESSION ESTABLISHMENT COMPLETED ................. 6–5 

Event 6 SESSION TERMINATION COMPLETED ...................... 6–6 

Event 7 LINE CONNECTION COMPLETED ............................. 6–15 

Event 8 LINE DISCONNECTION COMPLETED ........................ 6–17 

Event 9 IPM EVENT ................................................................ 6–19 

Event 10 SESSION CONNECTION FAILED ............................. 6–21 

iv 7436 0728–303

Contents 

Event 11 ILM EVENT .............................................................. 6–22 

Events 12–15 Not Defined .................................................... 6–104 

Event 16 CENLOG Messages ................................................ 6–105 



Event 1 NETWORK STATISTICS COLLECTED ........................ 7–1 

Event 2 PN1 SPECIFICATION ERROR .................................... 7–4 

Event 3 NETWORK RESPONSE-TIME HI/LO GAUGE 

CROSSING ......................................................................... 7–5 

Event 4 PORT PROCESSOR (PP) SPECIFICATION 

EXCEPTION ....................................................................... 7–6 

Event 5 PP HARDWARE ERROR STATISTICS LOGGED .......... 7–9 

Supplementary Message for Class 07, Event 05 ........ 7–9 

Event 6 IPP/IOP HARDWARE EVENT ..................................... 7–10 


Event 7 COMMUNICATIONS LINE ERROR ............................. 7–11 

Events 8-9 Not Defined ......................................................... 7–12 

Event 10 LINE/TERMINAL STATISTICS ................................. 7–13 

Event 11 LOCAL STORAGE SINGLE BIT ERROR .................... 7–14 

Event 12 LINE/TERMINAL STATISTICS ................................. 7–15 

Event 13 Not Defined ............................................................ 7–16 

Event 14 PROCESSOR UTILIZATION STATISTICS .................. 7–17 

Event 15 SINGLE NODE LOG OF DNS TRACE DATA ............. 7–18 

Event 16 Not Defined ............................................................ 7–19 


Event 1 INVALID TERMINAL SIGN-ON .................................. 8–1 

Event 2 NMS PASSWORD/AUTHORITY ACCESSED FOR 

CHANGE ............................................................................ 8–2 

Event 3 ATTEMPT TO EXECUTE UNAUTHORIZED NMS 

COMMAND ........................................................................ 8–3 

Event 4 ATTEMPT TO CONNECT TO INVALID END USER .... 8–4 







EVENT 8 CENLOG Messages ................................................ 8–8 


EVENT 9 CENLOG Messages ................................................. 8–9 


EVENT 10 NMS SECURITY EVENT ....................................... 8–10 

EVENT 11 DCPOS SECURITY EVENT ..................................... 8–11 

EVENTS 12-15 Not Defined ................................................... 8–12 

EVENT 16 CENLOG Messages ............................................. 8–13 


7436 0728–303 v

Contents 


Event 1 ‘UP’ OF FACILITIES COMMAND ................................ 9–1 

Event 2 ‘DOWN’ OF FACILITIES COMMAND .......................... 9–5 

Event 3 ‘START’ OF FACILITIES COMMAND ......................... 9–10 

Event 4 ‘STOP’ OF FACILITIES COMMAND ........................... 9–11 

Event 5 NMS MOVE OF FACILITIES ...................................... 9–12 

Event 6 ‘SWITCH’ COMMAND ISSUED .................................. 9–13 

Event 7 ONLINE CONFIG LOG ENTRY .................................. 9–14 

Event 8 NMS COMMAND COMPLETION STATUS ................. 9–15 





Event 1 DISCARDED MESSAGE (LOST MESSAGE) ............... 10–1 


Event 2 NDL MESSAGE UNDELIVERABLE ............................. 10–6 

Event 3 UDM MESSAGE UNDELIVERABLE ............................ 10–7 

Event 4 TIME / DATE EVENT ................................................ 10–8 




Event 1 MODIFICATION IN NODE ROUTING STATUS ............ 11–1 

Supplementary Messages For Class 11, Event 01 ...... 11–1 

Event 2 MODIFICATION IN NODE NETWORK CONNECTION 11–3 


Event 3 CHANGE IN THE INTER-NODE TRUNK STATUS ....... 11–4 

Event 4 RESILIENT NODE IS NOW ........................................ 11–5 

Event 5 ALTERNATE NODE IS NOW ...................................... 11–6 

Event 6 RESILIENCY AUDIT FILE PROBLEM ......................... 11–7 


Event 7 SWITCH NOTIFICATION ........................................... 11–8 


Event 8 RESILIENT MOVE COMPLETION .............................. 11–12 

Event 9 CENLOG Messages .................................................. 11–13 

Supplementary Messages ......................................... 11–13 

Event 10 RESILIENCY EVENT NOTIFICATION ....................... 11–14 


Events 11–13 Not Defined ..................................................... 11–15 

Event 14 CENLOG FILE AUTORETV XFER COMMAND 

INVOKED ............................................................................ 11–16 

Event 15 CENLOG FILE FULL SWITCHING 

ACTIVE LOG FILE FROM: .................................................. 11–17 



vi 7436 0728–303


Contents 

Event 1 Not Defined .............................................................. 12–2 

Event 2 LOGW COMMAND ................................................... 12–3 

Events 3-5 Not Defined ......................................................... 12–4 

Event 6 OPEN/CLOSE ERROR REPORTED FROM FILE 

MANAGER .......................................................................... 12–5 

Event 7 MASS STORAGE ACCESS ERROR ........................... 12–6 

Event 8 SYSTEM SERVICE CALL EXCEPTION STATUS ........ 12–8 

Event 9 INSUFFICIENT SYSTEM RESOURCES (STORAGE) .. 12–12 

Event 10 INSUFFICIENT MASS STORAGE (DISK) ................. 12–17 

Supplementary Messages For Class 12 Event 10 ....... 12–17 

Event 11 MAXIMUM TABLE-SIZE LIMIT REACHED ............... 12–18 


Event 16 CENLOG Messages ............................................... 12–21 



Event 1 EVENT/ERROR DETECTED AT L1 (PHYSICAL) ......... 13–1 

Event 2 EVENT/ERROR DETECTED AT L2 (LINK) ................. 13–3 

Event 3 EVENT/ERROR DETECTED AT L3 (NETWORK) ........ 13–11 


IP Router Messages ......................................... 13–15 

Open Shortest Path First (OSPF) 

Messages .......................................... 13–28 

Event 4 EVENT/ERROR DETECTED AT L4 (TRANSPORT) ..... 13–72 

Event 5 EVENT/ERROR DETECTED AT L5 (SESSION) ........... 13–81 


Event 6 EVENT/ERROR DETECTED AT L6 

(PRESENTATION) ............................................................... 13–84 

Supplementary Messages for Class 13 Event 06 ........ 13–84 

Event 7 EVENT/ERROR DETECTED AT L7 (APPLICATION) ... 13–85 


Event 8 TERMINATION SYSTEM IS UP .................................. 13–87 

Event 9 PATH TO THE TS IS BLOCKED ................................. 13–88 


7436 0728–303 vii

Contents 


Event 1 LINE CONNECTION (UNSUCCESSFUL) .................... 14–1 

Event 2 LINE DISCONNECTION (ABNORMAL) ...................... 14–3 

Event 3 AUTO-DIAL FAILURE ................................................ 14–11 

Event 4 ADRD FAILURE ......................................................... 14–12 

Event 5 NO POLL GROUP FOUND ......................................... 14–13 

Events 6–7 Not Defined ......................................................... 14–14 

Event 8 ABNORMAL LINE TERMINATION FUNCTION ........... 14–15 

Event 9 Not Defined ............................................................... 14–18 

Event 10 UNRECOVERABLE TERMINAL/DEVICE ERROR ..... 14–19 

Events 11–15 Not Defined ..................................................... 14–20 


Supplementary Messages for Class, 14, Event 16 ...... 14–21 


Event 1 HARDWARE LINE ERROR (NOT A PP STATE ITEM) . 15–1 

Supplementary Message For Class 15, Event 01 ........ 15–3 

Event 2 COMMUNICATIONS LINE PROTOCOL ERROR 

DETECTED ......................................................................... 15–5 


Event 3 INPUT ERROR FROM DEVICE/TERMINAL ................ 15–13 

Supplementary Messages for CLASS 15, EVENT 03 ... 15–14 

Event 4 OUTPUT ERROR TO DEVICE/TERMINAL .................. 15–18 

Event 5 POLL GROUP STATUS .............................................. 15–21 


Event 6 Not Defined .............................................................. 15–22 

Event 7 TERMINAL/DEVICE PROTOCOL ERROR 

DETECTED ......................................................................... 15–23 





Events 1-15 Not Defined ........................................................ 16–2 



Section 17. NMS and DSA Messages 

Introduction ............................................................................ 17–1 

NMS Messages ...................................................................... 17–2 

Directory Services Agent (DSA) Messages ............................ 17–42 

Section 18. Remote File System (RFS) Messages 

Error Messages Generated from RFS Consoles .................... 18–2 

viii 7436 0728–303

Contents 

Messages Defined by DDP .................................................... 18–3 

Warning Messages ................................................................ 18–6 

Error Messages ..................................................................... 18–7 

IPC Status Codes ................................................................... 18–8 

Appendix A. X.25 PSCS Diagnostic Codes 

DCE Network Feature Diagnostic Codes ............................... A–1 

Appendix B. X.25 PSCS Initialization Error Codes 

Appendix C. X.25 PSCS Cause Codes 

Appendix D. Sense Data 

Clear Packets ........................................................................ C–2 

Reset Packets ........................................................................ C–3 

Restart Packets ..................................................................... C–4 

Sense Data Conditions .......................................................... D–2 

Sense Data Categories .......................................................... D–2 

Unisys Internal Sense Data .................................................... D–3 

Request Reject (Category X'01') ................................ D–7 

IBM/Unisys Request Reject (Category X'08') .............. D–9 

IBM/Unisys Request Error (Category X'10') ................ D–21 

IBM/Unisys State Error (Category X'20') .................... D–23 

IBM/Unisys RH Usage Error (Category X'40') ............. D–25 

IBM/Unisys Path Error (Category X'80') ..................... D–27 

Appendix E. Acronyms and Abbreviations 

Glossary 

Bibliography 

Index 

7436 0728–303 ix

Contents 

x 7436 0728–303

Tables 

1–1. CENLOG Class Types ............................................................................ 1–1 

7–1. Virtual Circuit Connection – Buffer Format ............................................... 7–2 

13–1. Example of Long Format ....................................................................... 13–89 

13–1. Example of Long Format (continued) ....................................................... 13–90 

13–2. Input Logging Items .............................................................................. 13–91 

13–3. Output Logging Items ............................................................................ 13–92 

17–1. Message Types Table ........................................................................... 17–2 

18–1. Error Messages from RFS Consoles ....................................................... 18–2 

18–2. Messages Defined by DDP ..................................................................... 18–3 

18–3. Warning Messages ................................................................................ 18–6 

18–4. Error Messages .................................................................................... 18–7 

18–5. IPC Class 3 Error Codes ........................................................................ 18–8 

18–6. IPC Class 4 Error Codes ........................................................................ 18–9 

18–7. IPC Class 10 Error Codes ...................................................................... 18–9 

18–8. IPC Class 128 ...................................................................................... 18–10 

18–9. IPC Class 129 Error Codes .................................................................... 18–10 




A–1. X.25 Diagnostic Codes .......................................................................... A–2 

B–1. X.25 PSCS Initialization Error Codes ..................................................... B–1 

C–1. Clear Packet Cause Codes .................................................................... C–2 

C–2. Resetting Cause Codes ......................................................................... C–3 

C–3. Restarting Cause Field Coding ............................................................. C–4 

D–1. Sense Data Format ............................................................................... D–1 

D–2. Sense Data Categories .......................................................................... D–2 

D–3. Supplemental Event Code Categories ..................................................... D–3 

D–4. Supplemental Codes ............................................................................. D–3 

7436 0728–303 xi

Tables 

xii 7436 0728–303

About This Manual 

Purpose 

Scope 

The DCP Series Telcon Message Manual lists status messages, error conditions, and 

corrective actions for network management services (NMS) and critical event notification 

and logging (CENLOG) messages that appear on NMS consoles. 

This manual also includes directory service agent (DSA), remote file services (RFS), and 

instrumentation messages. The appendixes consist of diagnostic codes and initialization 

error codes for the X.25 PSCS program and IBM® Sense Data information. 

The CENLOG messages are arranged in sections by class and event. Classes 2 through 16 

are in Sections 2 through 16. 

This manual includes NMS and CENLOG messages from the following products: 

• Telcon 

• SNA/net 

• Packet Switched Communications Software (X.25 PSCS) 

• TCP–IP Stack, the Transmission Control Protocol/Internet Protocol (TCP/IP) program 

product 

• Open Systems Interconnection Transport Services (OSITS) program product 

• Intelligent Line Module (ILM) product (part of the ENS program product) 

• Enterprise Network Services (ENS) program product 

7436 0728–303 xiii


Audience 

This manual is for Telcon system network analysts and operators who are responsible for 

troubleshooting. 

Notation Conventions 

Prerequisites 

Notation Convention 

CENLOG messages Appear in bold before the description and action. 

Telcon detailed CENLOG procedure 

names 

Appear in bold before the description and action. 

Commands Appear in ITALIC CAPITAL letters. 

Screen displays Appear in ��. 

Optional items Appear in square brackets ([ ]). 

This manual assumes expertise in understanding Telcon systems and program products. 

Organization 

Section 1. Introduction 

Provides an overview of the parts and types of messages and what to do when a message 

appears. It also describes CENLOG display formats. 


Provides descriptions and actions for Class 2 CENLOG messages. 







xiv 7436 0728–303
























7436 0728–303 xv


Section 17. NMS and DSA Messages 

Provides descriptions and actions for NMS and DSA messages. 

Section 18. Remote File System (RFS) Messages 

Provides descriptions and actions for RFS messages. 

Appendix A. X.25 PSCS Diagnostic Codes 

Provides information on X.25 PSCS diagnostic codes. 

Appendix B. X.25 PSCS Initialization Error Codes 

Lists X.25 PSCS initialization codes and explains what each means. 

Appendix C. X.25 PSCS Cause Codes 

Provides X.25 cause code information from Recommendation X.25. 

Appendix D. Sense Data 

Provides IBM Sense Code information. 

Appendix E. Acronyms and Abbreviations 

Includes a list of relevant acronyms and abbreviations. 

xvi 7436 0728–303

Related Product Information 

The following Unisys documents contain helpful product information. 

Document Name/Number Description 

Buyer’s Guide to DCP Communication 

Products (7436 9828) 

DCP Series DCP/OS Operations 

Reference Manual (7831 5702) 

DCP Series Intelligent Line Module (ILM) 

Programming Reference Manual 

(7831 8569) 


This guide provides marketing personnel and clients 

with detailed information about DCP hardware, 

software, networking connectivity, and product 

migration. It fills the gap between marketing brochures 

and technical manuals. 

This manual provides information on how to: 

• Boot and dump the DCP 

• Build, debug, and edit programs 

• Enter and use DCP commands and utilities 

• Use system tuning and memory management 

• Identify error codes 

• Interpret system messages 

This manual describes the ILM and communications 

processor (CP) environment and the manner in which 

services are selected by programmers. For the ILM 

platform architecture, this manual includes 

descriptions of the following: 

• Formats 

• Conventions 

• Requirements 

Refer to the ENS Installation, Configuration and 

Operations Guide for updated ILM information for 

CD6R2 and CD6R2A releases. 

7436 0728–303 xvii



DCP Series Enterprise Network Services 

Installation, Configuration and Operations 

Guide (7441 2065) 

DCP Series Communications Processor 

Architecture Programming Reference 

Manual (7431 5805) 

DCP Series SNA/net Configuration Guide 

(7831 5629) 

DCP Series TCP–IP Stack Configuration 

and Operations Guide (7831 5546) 

This guide provides the following: 

• Detailed information on configuring and operating 

the Telcon program product that enables Telcon 

to communicate over 802.3, FDDI, and Token 

Ring LANs 

• Alphabetically arranged configuration and 

operation reference information for each Telcon 

configuration statement and NMS command ENS 

uses 

• IP Router, IPX Router and SNMP Agent 

configuration statements 

• Information on installing the ENS program product 

on a DCP 

• Information on operating the IP Router, IPX Router 

and SNMP Agent using the ENS menu 

Use this guide with the base Telcon product operations 

and configuration library. 

This manual describes the DCP family instruction 

repertoire and architecture. 

This guide describes how to configure the SNA/net 

program product. This guide includes descriptions of 

the following: 

• SNA/net features 

• SNA/net software 

• Telcon configuration statements 

• Sample network configurations 

This guide describes how to configure TCP–IP Stack 

software on a DCP. This guide includes the following: 

• An overview of the product 

• Descriptions of the required configuration 

statements 

• Examples of typical configurations 

• Operations procedures unique to TCP–IP Stack 

Refer to the Telcon Configuration Reference Manual, 

the Telcon Configuration Guide and the ENS 

Installation, Configuration and Operations Guide for 

updated TCP/IP information for CD6R2 and CD6R2A 

releases. 

xviii 7436 0728–303


DCP Series Telcon Configuration Guide 

(7831 5678) 

DCP Series Telcon Configuration 

Reference Manual (7831 5686) 

DCP Series Telcon Installation Guide 

(7831 5645) 

DCP Series Telcon Network Load Utility 

Installation Guide (7436 1601) 


This guide explains how to configure Telcon to enable 

communication in a DCP communication network. This 

guide explains how to configure: 

• Network protocols 

• Terminals 

• Applications 

• DSF 

This guide also provides an overview of Telcon and the 

software components Telcon works with, including the 

following: 

• DCP/OS 

• NMS 

• Telcon program products 

Use this guide with the Telcon Configuration Reference 

Manual (7831 5686). 

This manual provides: 

• Detailed, alphabetically arranged reference 

information for each Telcon configuration 

statement used to configure the base Telcon 

communication product, which includes TCP/IP 

and OSI communication capabilities. 

• An extensive set of Telcon source configuration 

files, covering the major areas of Telcon 

configuration. 

Use this manual with the DCP Series Telcon 

Configuration Guide (7831 5678). 

This guide provides information on how to 

• Install and generate Communications Delivery (CD) 

software and related program products on an OS 

2200 host 

• Load the generated software to Distributed 

Communications Processors (DCPs) 

• Verify the loaded software 

This guide describes how to install, configure, and 

operate the NLU product. NLU loads a DCP with 

Telcon when a bootloader is not available. NLU 

• Supports a wide set of networks 

• Provides the means to use various transport 

protocols between DCPs or between a DCP and 

an OS 2200 host 

7436 0728–303 xix



DCP Series Telcon Operations Guide 

(7831 5785) 

DCP Series Telcon Operations Reference 

Manual (7831 5728) 

DCP Series X.25 Packet Switched 

Communications Software (PSCS) 

Configuration and Operations Guide 

(7831 5470) 

This guide explains how to 

• Organize DCP networks using NMS consoles and 

commands 

• Transfer files in a DCP environment 

• Interpret messages 

• Enable instrumentation 

• Control console and logged messages 

This manual contains information on the following 

Network Management Services (NMS) commands and 

parameters: 

• Telcon NMS 

• ILM Platform NMS 

• LAN LM NMS 

• OSITS NMS 

• TCP–IP Stack NMS 

• Remote File System (RFS) 

This manual also contains information about the 

following: 

• Instrumentation commands and messages 

• Software support procedures 

This guide describes how to configure X.25 PSCS 

software on a DCP. This guide includes the following: 

• An overview of the product 

• Hardware and software compatibility 

• Descriptions of required configuration statements 

• Examples of typical configurations 

This guide also includes information on the following: 

• PSCS operations, including troubleshooting 

• Descriptions of X.25 related NMS commands 

xx 7436 0728–303

Section 1 

Introduction 

The DCP Series Telcon Message Manual is one of several documents that comprise the 

Communications Delivery (CD) library. 

CENLOG Class Types 

This subsection explains critical event notification and logging (CENLOG) class types. 

CENLOG messages are divided into 16 classes. Each class contains 16 events, for a total 

of 256 event types. The following table describes the kind of events and errors assigned to 

CENLOG classes. For information on how to log CENLOG messages, control displays, 

and automatically catalog CENLOG files, refer to the Telcon Operations Guide (7831 

5785). For information on how to use NMS commands associated with CENLOG 

messages, refer to the Telcon Operations Reference Manual (7831 5728). 

Table 1–1. CENLOG Class Types 

Class Events/Errors 

1 There are no CENLOGs defined for this class. 

2 Contains CENLOGs that result from debug tools that may be disabled with a 

special NMS TRON command. 

3 Contains CENLOGs assigned by program products. 

4 Contains CENLOGs assigned by program products. 

5 Contains errors and status information associated with the software and 


6 Contains normal connection/disconnection and sign-on/sign-off events. 

7 Contains hardware errors, statistics, and utilization events. 

8 Contains security-related events, including access attempts. 

9 These CENLOGs result when an administrator alters a facility by issuing an NMS 

command that controls the facility. The change in the operational mode of the 

specific facility specified in the command is reported in the CENLOG. 

10 Contains traffic messages the system is unable to deliver (UDMs) and time/date 

changes. 

11 These CENLOGs result from automatic facility control alterations made by the 

software control modules. 

7436 0728–303 1–1

Introduction 

Table 1–1. CENLOG Class Types 

Class Events/Errors 

12 These CENLOGs result from interface errors related to the system’s resources. 

The DCP/OS usually returns these errors in response to requests from Telcon for 

architecture table changes such as queues and segments. The cause is typically 

related to insufficient memory to expand the architecture tables. 

13 Contains network architecture (DCA layers 1 through 7) events and errors. 

14 Contains unrecoverable communication line errors. 

15 Contains recoverable communication line errors. 

16 Contains port processor errors. 

CENLOG Class Attributes 

CENLOG is a Telcon event log mechanism that records significant events such as errors, 

statistics, and other events. These events can be individually recorded in any combination 

of the following ways: 

• LOGL – Logged into a mass storage binary log file on the local DCP. 

• LOGC – Logged centrally into a mass storage binary log file on a central CENLOG 

node. 

• DSPL – Displayed on various NMS consoles of the local DCP. 

• DSPC – Displayed on various NMS consoles on a central CENLOG node. 

You can enable or disable each of these methods before the event occurs. 

1–2 7436 0728–303

CENLOG Display Formats 

Introduction 

This subsection explains CENLOG display formats. There are four display formats, as 

follows: 

• Mini format without central display. Provides an overall picture of the network, 

without central display, and allows you to examine network activity over a range of 

time. 

• Mini format with central display. Provides an overall picture of the network, with 

central display, and allows you to examine network activity over a range of time. 

• Brief format. Provides an overall picture of the network, with central display, and 

allows you to examine network activity over a range of time. Provides more detail 

than the mini format, but quickly scrolls off the screen. 

• Long format. Provides an overall picture of the network, with central display, and 

allows you to examine network activity over a range of time. The long format 

provides detailed information, including the register contents, 

Select the format based on the type of information you want from the CENLOG. 

A primary CENLOG message is displayed for each defined class and event. One or more 

supplementary messages may accompany the primary message. 

Mini Format Without Central Display 

Enter the TROF TYPE=CNLB command or specify OPTN=MINI on the LOGI command to 

display this format. CENLOGs fit on a single line so you see a column effect and can 

observe more history and trend information. 

The mini format without central display appears as follows: 

�� 

7436 0728–303 1–3

Introduction 

Mini Format With Central Display 

Brief Format 

This format is displayed when your local DCP receives CENLOGs from other DCPs. Enter 

the TROF TYPE=CNLB command or specify OPTN=MINI parameter on the LOGI 

command to display this format. CENLOGs fit on a single line so you see a column effect 

and can observe more history and trend information. 

The mini format with central display appears as follows: 

�� 

�� 

Brief format is the default display format. You can also enter TRON TYPE=CNLB and/or 

TROF TYPE=CNLL, or LOGI OPTN=Brief to select this format. 

The brief format appears as follows: 

�� 

�� 

�� 

�� 

where: 

�� is the processor symbolic name identifying the nodal processor from 

which the CENLOG event occurred. 

�� identifies the sequence number assigned to the corresponding entry in the 

logging mass storage file. The sequence numbers are unique by processor 

(DCP) only. 

�� is the hours:minutes:seconds of the incident occurrence from the DCP 

that generated the log entry. 

�� is the class number of the event (1–16). 

�� is the event number of the log entry (1–16). 

�� is the symbolic name that refers to the initial procedure of the task. 

1–4 7436 0728–303

Long Format 

Introduction 

�� 

is the symbolic name that refers to the current active Telcon procedure 

that generated the event. 

�� identifies the relative offset within the procedure that generated the 

CENLOG event. 

�� is a configured symbolic facility name of the serial communication line 

with which this event is generally (or specifically) associated. 

�� is a configured specific facility name of the batch device or serial 

communication terminal with which this event is associated (for example, 

a terminal). 

�� is the physical port processor number and, optionally, a multiline line 

number of that port on the declared DCP with which this event is 

associated. 

Enter the TROF TYPE=CNLL command or specify OPTN=LONG on the LOGI command 

to display CENLOGs in long format. 

The long format is the same as the brief format with the following additional information. 

�� 

�� 

�� 

Additional table or text information, variable in length, but in the following format: 

�� 

�� 

� � � � � � � � 

� � � � � � � � 

�� 

7436 0728–303 1–5

Introduction 

Analyzing CENLOG Files 

You can analyze CENLOG files on the OS 2200 host by using the CENLOG Analysis 

Program (CAP) included in the CO$UTIL file on the Communications Delivery (CD) 

release tape. 

To use CAP, your CENLOG file must reside on the OS 2200 host. If you central logged the 

host, your CENLOG file will be as follows: 

Format 

�� 

Parameters 

prcsr-name is the name of the processor (DCP), for example, TEL*CST-SLB. 

If the DCP used logging, use the NMS XFER command to transfer the file to the host. See 

the Telcon Operations Reference Manual (7831 5728) for information on using the XFER 

command. If you did not specify a �� parameter on the XFER command, the name of the 

file on the host defaults to the following: 

Format 

�� 

Parameters 

yy is PR for a primary (local) log file, AL for an alternate (local ) log file, or CL 

for a central log file. 

xx-number is the two-digit processor DCP sequence number in hexadecimal notation, or 

the two-character node ID if you specified a node ID on the Telcon 

runstream @TELCON statement. 

Note: Temporary hold files (HDSTATxx) do not contain a CENLOG header and 

cannot be analyzed by CAP. 

For example, the primary log file for the tenth DCP in a network defaults to 

TEL*PRSTAT0A. If your configuration specifies an XEU named DEMAND, enter the 

following: 

�� 

1–6 7436 0728–303

Introduction 

After the CENLOG file is transferred to the OS 2200 host, you can analyze the file by 

calling the CENLOG Analysis Program (CAP). CAP is an interactive program that you call 

from a demand run on a UNISCOPE type of terminal by entering the following: 

Format 

�� 

Parameters 

options or opts: 

H is the print help screen. 

spec-1. is the CENLOG file to be analyzed. 

spec-2. is the (optional) print file for a hard copy report. 

Note: If you request a hard copy and do not supply a print file name for spec-2, CAP 

prompts you for a print file name. 

When CAP begins executing, you are prompted to select the subset of CENLOG entries 

you want analyzed. The criteria of entries you can select are as follows: 

• CENLOG Type (class and event code) 

• Facility name 

• Sequence number 

• Time interval 

• Processor name or node number 

After you select the CENLOG subset you want, CAP prompts you to specify the fields you 

want within the subset. After selecting the subset and the fields, you can request CAP to 

produce the analysis to your terminal screen, in a print file, or both. 

7436 0728–303 1–7

Introduction 

NMS Operator Actions for CENLOG Events 

Sections 2 through 16 of this manual provide descriptions and suggested actions for events 

and errors that occur during system operation. The CENLOG messages that are displayed 

on various NMS consoles provide a system message, class number, and event number. 

Sometimes a CENLOG message suggests that you submit a User Communication Form 

(UCF). If a UCF is necessary, follow these suggestions: 

• Determine the frequency of the occurrence. 

• Determine how the CENLOG relates to problems you are experiencing. 

• Submit a long list of the CENLOGs that concern you (whether or not you are able to 

initiate a Telcon dump or a @@CONS SNAP Telcon dump). 

To submit a long list, enter the @@PRNT command on one of your network NMS consoles, 

or better yet, XFER the CENLOG files (PRSTATnn, ALSTATnn) to a 2200 host and 

execute the @CAP Telcon utility to print them. 

For more information on handling problems and support procedures, see the Telcon 

Operations Guide (7831 5785) and the Telcon Operations Reference Manual (7831 5728). 

Detailed CENLOG Event Descriptions 

Detailed CENLOGs help network analysts isolate and resolve system problems. You can 

locate the description you need by system procedure name, CENLOG class, and event 

numbers displayed at NMS consoles. The procedure appears in bold type. The majority of 

detailed CENLOGs are in class 5 (Section 5 of this manual). Procedure names do not 

contain messages, but rather abbreviations and acronyms such as DTP, NTRLPH, TAF, 

and BVOUTPUT. 

You should be familiar with the Telcon networking system and system-level nomenclature 

to use these CENLOGs. 

To obtain further information about each CENLOG, refer to the assembly listing of the 

procedure at the address where the CENLOG occurs. The address displays on the NMS 

console when you select the long format. These addresses are not listed in this manual 

because they may change with each software generation level. 

1–8 7436 0728–303

Detailed CENLOGs may show more than one identical procedure name. You can 

differentiate between them by doing one or more of the following: 

Introduction 

• Matching the description with the comments in the assembly listing at the CENLOG 

call. 

• Matching a supplementary message displayed on the console with one of the 

supplementary messages or descriptions for that class/event and procedure. 

• Matching a particular register setting at the CENLOG call with a register setting. 

Supplementary messages are optional. If a supplementary message is designed for a 

CENLOG call, the message appears in the module near the point of the CENLOG call. 

UNILPH CENLOG Entry Descriptions 

UNILPH makes a CENLOG entry when a line protocol or hardware error is detected. Each 

entry consists of a supplementary message describing the error and the register contents 

at the time of the CENLOG call (registers are available only with the long form of the 

CENLOG display). Register R8 contains the error code or hardware status. Registers R9 

to R15 contain more information pertaining to the error, depending on the contents of R8. 

If the contents of R8 are of the form 00Ex, where x is a hexadecimal number ranging from 

0 to F, the line protocol handler (LPH) is reporting a line protocol error or hardware event 

not detectable by a hardware status. Otherwise, R8 contains hardware status bits passed 

to the LPH by the Input/Output Processor (IOP). In the error descriptions in this manual, 

the following register conventions hold true unless indicated otherwise. 

• R12 is the TCB address of terminal in error condition 

• R14 is the LINE-ID of line on which the error occurred 

• R15 is the RID/SID of terminal in error condition 

7436 0728–303 1–9

Introduction 

Class 1 CENLOG Messages 

No CENLOGS have been defined for events 1 through 16. 

1–10 7436 0728–303

Section 2 


Class 2 contains CENLOGs that result from debug tools. They are disabled with a 

special NMS TRON command. 

Event 1 DEBUG EVENT 

DEBUG EVENT 

Description: Trace/Debug features. See TRON/TROF commands for details. Telcon 

generates this CENLOG. 

Action: None. 

7436 0728–303 2–1

Events 2–16 Not Defined 


No CENLOGs have been defined for events 2 through 16. 

2–2 7436 0728–303

Section 3 


Telcon and the program products use Class 3 CENLOGs to define significant events. 

Event 1 PROGRAM PRODUCT NOT PRESENT 

PROGRAM PRODUCT NOT PRESENT 

Description: An attempt was made to use an uninstalled program product. Telcon 


Action: Install the program product or remove reference of the program product 

from the configuration. 

CORPNET NOT INSTALLED 

Description: The CORP/net program product layer 4 nonfunctional module (CRPL4) 

received a PCALL primitive from X.25 PSCS’s Layer 3/4 Platform interface. Because 

the CORP/net program product is not installed, it is unable to process the PCALL 

primitive. 

Attributes affected: Configuration event. The nonfunctional CRPL4 module in 

Telcon for the CORP/net program product generates this CENLOG. Procedure: 

CRPL4. 

Action: Install the CORP/net program product, or remove any X.25 PSCS DTE 

statements that are configured for the program product. 

PDN28I 

Description: The X.25 PSCS X.28 PAD terminal handler nonfunctional module 

(PDNX28) received an EU statement information table. Because X.25 PSCS is not 

installed, it is unable to process the EU statement information table. 

Attributes affected: Supplementary text message, configuration event. The 

nonfunctional PDNX28 module in Telcon for the X.25 PSCS program product 

generates this CENLOG. Procedure: PDN28I. 

Action: Install the X.25 PSCS program product or remove the EU statement with the 

TYPE=X28PAD parameter. 

7436 0728–303 3–1


PDNLPD 

Description: The X.25 PSCS NMS terminal processing nonfunctional module 

(PDNLPD) received an NMS command. Because X.25 PSCS is not installed, it is 

unable to process the NMS command. 

Attributes affected: Configuration event. The nonfunctional PDNLPD module in 

Telcon for the X.25 PSCS program product generates this CENLOG. Procedure: 

PDNLPD. 

Action: Install the X.25 PSCS program product, or remove the TERM statement 

associated with X.25 PSCS. 

PDNMAS 

Description: The X.25 PSCS NMS line processing nonfunctional module (PDNMS) 

received an NMS STAT or LIST LINE command. Because X.25 PSCS is not installed, 

it is unable to process the NMS command. 

Attributes affected: Configuration event. The nonfunctional PDNMS module in 


PDNMAS. 

Action: Install the X.25 PSCS program product, or modify the LINE statement 


PDNNET - EU NDS ENCOUNTERED 

Description: The X.25 PSCS DCE Network feature’s nonfunctional module 

(PDNNET) received an EU statement information table. Because X.25 PSCS is not 

installed, it is unable to process the EU statement information. 

Attributes affected: Supplementary text message. Error event. The nonfunctional 

PDNNET module in Telcon for the X.25 PSCS program product generates this 

CENLOG. Procedure: PDNETP. 

Action: Install the X.25 PSCS program product or modify the EU statement with the 

TYPE=DCPNET parameter. 

3–2 7436 0728–303

PDNNET–X25NET NDS ENCOUNTERED 


Description: The X.25 PSCS DCE Network feature’s nonfunctional module 

(PDNNET) received an X25NET statement information table. Because X.25 PSCS is 

not installed, it is unable to process the X25NET statement information. 

Attributes affected: Supplementary text message. Error event. The nonfunctional 

PDNNET module in Telcon for the X.25 PSCS program product generates this 


Action: Install the X.25 PSCS program product or remove the X25NET statement 

from the configuration. 

PDNPAD 

Description: The X.25 PSCS X.29 terminal handler nonfunctional module (PDNPAD) 

received unsolicited output related to a configured X.29 terminal. Because X.25 PSCS 

is not installed, it is unable to process the unsolicited output. 

Attributes affected: Configuration event. The nonfunctional PDNPAD module in 


PDNPAD. 

Action: Install the X.25 PSCS program product or modify the TERM statement 

associated with X.25 PSCS’s X.29 terminal handler. 

PDNSVS 

Description: The X.25 PSCS NMS line processing nonfunctional module (PDNSVS) 

received a line initialization indication from line services. Because X.25 PSCS is not 

installed, it is unable to process the indication. 

Attributes affected: Configuration event. The nonfunctional PDNSVS module in 


PDNSVS. 

Action: Install the X.25 PSCS program product or modify the LINE statement 


7436 0728–303 3–3


PDNTRNK 

Description: The X.25 PSCS DCP-to-DCP nonfunctional module (PDNTRK) received 

a UDLC line up notification. Because X.25 PSCS is not installed, it is unable to 

process the notification. 

Attributes affected: Configuration event. The nonfunctional PDNTRK module in 


PDNTRK. 

Action: Install the X.25 PSCS program product or modify the UDLC LINE and 

STATION statements, or the TRUNK statement associated with both UDLC and 

referenced by an X.25 PSCS DTE statement. 

PDNURS 

Description: The X.25 PSCS terminal processing nonfunctional module (PDNURS) 

received an unsolicited terminal processing command. Because X.25 PSCS is not 

installed, it is unable to process the command. 

Attributes affected: Configuration event. The nonfunctional PDNURS module in 


PDNURS. 

Action: Install the X.25 PSCS program product or remove the TERM statement 


PLSEUI 

Description: The X.25 PSCS packet layer services (PLS) feature’s nonfunctional 

module (PDNPLS) received an EU statement information table. Because X.25 PSCS is 

not installed, it is unable to process the EU statement information. This event 

includes a supplementary text message. 

Attributes affected: Configuration event. The nonfunctional PDNPLS module in 


PLSEUI. 

Action: Install the X.25 PSCS program product or modify the EU statement with the 

TYPE=PLSTSU parameter. 

3–4 7436 0728–303

PXCCONF 


Description: The X.25 PSCS X.25/DCATS Bridge feature nonfunctional module 

(PDNDXA) received a DCATS statement’s information table that is associated with a 

DTE statement. Because X.25 PSCS is not installed, it is unable to process the DCATS 

statement. 

Attributes affected: Configuration event. The nonfunctional PDNDXA module in 


PXCCONF. 

Action: Install the X.25 PSCS program product or modify the DCATS statement that 

references a DTE statement. 

SNA: 254 - SNA-CDRM feature not installed 

Description: This message occurs when PU type 4 is configured, but the SNA-CDRM 

feature is not installed. The probable cause is an installation problem. 

SNA: 255 - SNA-NPSI feature not installed 

Description: This message occurs when X.25 connections are configured for 

SNA/net but the SNA-NPSI feature is not installed. The probable cause is an 

installation problem. 

TCP–IP FEATURE NOT INSTALLED 

Description: Telcon detected an attempt to configure a TCP–IP Stack feature. 

TCP–IP Stack was not installed. TCP–IP Stack generates this CENLOG. 

Action: Either install TCP–IP Stack or remove reference to TCP–IP Stack from the 


X.25: PSCS is not installed 

Description: The X.25 PSCS layer 3 nonfunctional module (PDNL3) received a 

PCALL primitive from a program product that uses X.25 PSCS’s Layer 3/4 Platform 

interface (such as, OSITS or TCP–IP Stack). Because X.25 PSCS is not installed, it is 

unable to process the PCALL primitive. If the primitive is a call request, a clear 

indication is returned; otherwise, the primitive is discarded. 

Attributes affected: Supplementary text message, configuration event. The 

nonfunctional PDNL3 module in Telcon for the X.25 PSCS program product generates 

this CENLOG. Procedure: PDNL3. 

Action: Install the X.25 PSCS program product or modify the DCATS statement that 

references a DTE statement. 

7436 0728–303 3–5

Event 2 X.25 GATEWAY EVENT 

Event 2 X.25 GATEWAY EVENT 

X.25: GATEWAY EVENT 

DOWN AND UP THE LINE IF THE DTEs PDNGRP WAS CHANGED 

Description: The PDNGRP field on a DTE statement was changed using CNFG. If 

the layer four is PLS, you must DOWN and UP the facility. 

Action: DOWN and UP the line associated with the PDNGRP configuration statement 

that was changed. 

3–6 7436 0728–303

Event 3 *** X.21 ERR *** R14, R15 = PORT ID 

Event 3 *** X.21 ERR *** R14, R15 = PORT ID 

Currently there are no CENLOGs defined for this event. 

7436 0728–303 3–7

Event 4 SNA/net Event 

Event 4 SNA/net Event 

SNA: 652 – EUSERV returned error (reason code = %%%%) 

Description: This message occurs as a result of errors or events in the crossover 

application bridge (XAB). The XAB handles traffic between SNA resources and OS 

2200 hosts. The % represents a hexadecimal number. The probable cause is a 

software problem. 

SNA: 1236 - SNANPSI needs re-assembly with DCPX25-PSCS 

Description: COMUS was not used to build this system. 

Action: You need to re-assemble the SNANPSI module for the system to work. 

3–8 7436 0728–303

Event 5 DCPOSITP EVENT 

OSI INTERNET PROTOCOL INITIALIZED 


Description: Successful processing of at least one OSISN NDS. The OSIIP 

component of the OSITS program product generates this CENLOG. 

Reason: Installation verification notification. 

OSI TRANSPORT SERVICE INITIALIZED 

Description: Successful processing of the EU NDS by the transport services. The 

OSITS component of the OSITS program product generates this CENLOG. 


OSITB - CONFIGURATION ERROR 

Description: A TSAP configuration statement is not properly linked to an XEU 

configuration statement. The OSITB component of the OSITS program product 


Reason: Configuration error. 

OSITB - DCA MESSAGE DISCARDED 

Description: Input from DTP has been discarded. The OSITB component of the 

OSITS program product generates this CENLOG. 

Reason: A disconnect has occurred on the OSI half-connection. 

OSITB - DDP REJECTED CONNECTION 

Description: DDP–PPC has rejected a DCA transport connection request. The 

OSITB component of the OSITS program product generates this CENLOG. 

Reason: DDP–PPC is not active on the OS 2200 system. 

OSITB - INTERNAL SOFTWARE ERROR 

Description: Internal tables have been corrupted. The OSITB component of the 


Reason: Unknown. 

7436 0728–303 3–9


OSITB - OSI MESSAGE DISCARDED 

Description: Input from the OSI transport service has been discarded. The OSITB 


Reason: A disconnect has occurred on the DCA half-connection. 

OSITB - OSI TRANSPORT BRIDGE INITIALIZED 

Description: Successful processing of the EU NDS by the transport bridge. The 

OSITB component of the OSITS program product generates this CENLOG. 


3–10 7436 0728–303

Event 6 DCPX25-PNCS EVENT 



7436 0728–303 3–11




3–12 7436 0728–303

Event 8 VIDEOTEX EVENT 

VTXGTW program product 

R3 = Terminal Name 

R8 = Session State 

R14 = Get PPID 

R15 = LCN 

VTXG - X25 Connect Request 


Description: An attempt has been made to establish a session with a remote host. 

VTXG - X25 Disconnect Request 

Description: A request has been received to terminate a session. 

VTXG - Host Connect Reject 

Description: A remote host has rejected a request for a session. 

VTXG - Host UDM Received 

Description: The remote host temporarily cannot receive messages. 

Action: This condition is often temporary. If this persists, there may be a problem 

with sufficient host resources. 

VTXG - No Response From Application 

Description: The remote transaction program is not responding. It may be busy, or 

not functioning. 

VTXG - Host Disconnect Request 

Description: The remote host has requested a termination of the session. This could 

be caused by local or remote processing problems. 

VTXG - Appl Disconnect Request 

Description: The remote application program has requested that the session be 

terminated. 

7436 0728–303 3–13


VTXG - Host Frame Too Large 

Description: A very large frame has been encountered from the host that could not 

be processed. 

VTXG - User Timed Out 

Description: The local user has not been active, and the session timed out. 

VTXG - Call Rejected From Application 

Description: An attempt to establish a session has been rejected by the host program 

application. 

VTXG - Wrong msg type from X25L3 

Description: Invalid data has been received from layer 3. 

VTXG - Link Area Overflow 

Description: Internal Videotex error. 

Action: Contact your system administrator. 

VTXG - Output to X25L3 Discarded 

Description: A message has been discarded destined for X25L3. This may be due to 

session termination. 

VTXG - Unknown CTRL MSG from Telcon 

Description: VTXL4 received a control message from layer 3 that it could not 

interpret. 

VTXG - Unknown HICs from CMS 

Description: VTXL4 received a control message (HIC) that it could not interpret. 

VTXG - Application type out of range 

Description: Invalid request received from layer 3. 

3–14 7436 0728–303

VTXG - Data MSG not sent to Host 


Description: A data message was not successfully queued from VTXL4 to DTP. 


VTXPDN - Initialization not completed 

Description: VTXPDN failed to start. 


VTXPDN - Invalid Event for Current Connection State 

Description: A warning, but may not be fatal. 

VTXPDN - Error Event at VTX/PSCS Interface 

Description: R15 = error type, 1 through A. May not be fatal. 

VTXPDN - Error in VTXPDN TSU initialization 

Description: Failure of Videotex to initialize. 


VTXPAD - Terminal sign on 

Description: A VTXPAD terminal has signed on and the X25 call has been accepted. 

VTXPAD - Line Disconnection 

Description: PDNL3 has requested a disconnection and dismantling of the session. 

VTXPAD - Terminal sign off 

Description: Terminal session has been cleared as a result of a disconnect request, 

confirm, abort. 

Direct Connect: Terminal sign on 

Description: DSR has been received by VTXIOP and VTXLPH. LCB and TCB tables 

are built and a connect request sent to TIP. 

7436 0728–303 3–15


Direct Connect: Terminal sign off 

Description: Carrier has dropped due to a line disconnection or terminal timeout. 

Direct Connect: Host connect reject 

Description: The host (TIP) has rejected an attempt to establish a session. 

Direct Connect: Host UDM received 

Description: The host is temporarily not able to process messages. This is usually a 

temporary condition. 

Direct Connect: Host disconnect request 

Description: The host has initiated a disconnect request for the session. 

Direct Connect: Host frame too large 

Description: An output frame cannot be processed to its size. 


3–16 7436 0728–303


No CENLOGs have been defined for Events 9 through 11. 


7436 0728–303 3–17

Event 12 TCP–IP GATEWAY EVENT 


DEVICE=$ 

TELNET: ATTACH TO $ 

TERMINAL ID = $ IP ADDRESS = ! 

Description: A configured TELNET terminal is establishing a connection. This 

message is informational only. The TCP–IP Stack program product generates this 

CENLOG. 

Action: None. 

ETNDCA: INTERNAL ERROR DETECTED, DEGRADED 

Description: This message indicates a software error. You should report it to your 

Unisys representative, including the register contents. The TCP–IP Stack program 

product generates this CENLOG. 

ETNDCA: TS ABORTED, NOT LOCALLY RECOVERABLE! 

Description: This message is generated when the TCP–IP Stack detects that a 

DCATS application (IS–PC, IS–CS, or IS–6000) is no longer readable. It means that 

Telcon no longer attempts to read the application, and instead waits for the 

application to initiate the new connection. The TCP–IP Stack program product 


ETNMSP: CFACCS QUEUE FULL, MESSAGE LOST 

Description: TCP–IP Stack was unable to complete processing of an NMS command. 

This condition is usually recoverable. The TCP–IP Stack program product generates 

this CENLOG. 

Action: If the condition persists, contact your support center. 

ETNMSP: Internal Error Detected 

Description: TCP–IP Stack detected an internal error. This condition is usually 

recoverable. The TCP–IP Stack program product generates this CENLOG. 

Action: If the condition persist, contact your support center. 

3–18 7436 0728–303

ETNMSP: NMS Interface Error 


Description: TCP–IP Stack detected an internal error. TCP–IP Stack was unable to 

complete processing of an NMS command. This condition is usually recoverable. The 

TCP–IP Stack program product generates this CENLOG. 


ETNMSP: OUTPUT QUEUE IS FULL, MESSAGE LOST 

Description: TCP–IP Stack was unable to complete processing of an NMS command. 

This condition is usually recoverable. The TCP–IP Stack program product generates 

this CENLOG. 

Action: If the condition persist, contact your support center. 

ETNMSP: Pascal Runtime System Error Detected 

Description: TCP–IP Stack detected a system error. The TCP–IP Stack program 



ETNSMP: Internal Non-Fatal Error 

Description: TCP–IP Stack detected an internal error. This condition is normally 


Action: If this condition persists, contact your support center. 

ETNSMP: Send Failed (Queue Full) 




ETNSMP: Send Failed (Disconnected) 

Description: TCP–IP Stack lost communications with another software component. 

This condition is normally recoverable. The TCP–IP Stack program product generates 

this CENLOG. 

Action: Verify that all software components are running as needed. If this condition 

persists, contact your support center. 

7436 0728–303 3–19


ETNSMP: Set Table - Internal Error 




ETNSMP: Set Table - Interface Error 

Description: TCP–IP Stack detected an error in the interface to another software 

component. This condition is normally recoverable. The TCP–IP Stack program 



ETNSMP: MAU Parse _ Invalid Encoding Type 





ETNSMP: MAU Registration - - failed 


component. This condition is normally not recoverable. The TCP–IP Stack program 



ETNSMP: MAU Registration - - Not sent 





ETNSMP: MAU Registration - - Exception 





3–20 7436 0728–303

ETNSMP: MAU Connect Response - - Not sent 






ETNSMP: MAU Connect - - Duplicate 


component. TCP–IP Stack detected a possible configuration error in the 

configuration of the SNMP software component. Some configured functions may not 

be available. The 


Action: Verify the configuration of the SNMP software component. If this condition 


ETNSMP: MAU Connect - - Exception 





ETNSMP: ICS Input - Invalid Function 





ETNSMP: ICS Registration Complete 

Description: TCP–IP Stack is establishing communications with other software 

components. This message is informational only. The TCP–IP Stack program product 


Action: None. 

7436 0728–303 3–21


ETNSMP: ICS Registration Failed 





ETNSMP: Initialization - Fatal Error 





ETNSMP: Interface Table Overflow 

Description: TCP–IP Stack detected an internal error. This condition is normally not 



ETNSMP: Internal Non-Fatal Error 




ETNSMP: Invalid Channel for Data 





ETNSMP: Invalid Channel for IPM Connect 





3–22 7436 0728–303

ETNSMP: Invalid Channel for IPM Disconnect 






ETNSMP: Invalid Channel for IPM Free 





ETNSMP: Invalid Receive Status 





ETNSMP: IPM Connect - Complete 




Action: None. 

ETNSMP: IPM Connect - Exception 





ETNSMP: IPM Disconnect - Exception 





7436 0728–303 3–23


ETNSMP: IPM Free - Exception 





ETNSMP: Queues Cannot Be Registered (FATAL!) 


component. This condition is normally not recoverable. Some configured functions 

may not be available. The TCP–IP Stack program product generates this CENLOG. 


ETNSMP: SNMP Agent Available 


components. The SNMP subagent for TCP–IP Stack is now available. This message is 

informational only. The TCP–IP Stack program product generates this CENLOG. 

Action: None. 

ETNSMP: SNMP Agent NOT Available - - Disconnected 


The TCP–IP Stack SNMP subagent is not available. This condition is normally 


Action: Verify that software components are running as needed. If this condition 


ETNSMP: SNMP Agent NOT Available - - IPM Disconnect 


The TCP–IP Stack SNMP subagent is not available. This condition is normally 


Action: Verify that software components are running as needed. If this condition 


3–24 7436 0728–303

ETNSMP: SNMP Data Transfer Discarded 






ETNSP: Cache File not Catalogued 

Description: Domain Name System Resolver inoperable due to cache file error. 

Action: Contact your support center. 

ETNSP: Cache File ASSIGN Failed 



ETNSP: Cache File Open Failed 



ETNSP: Cache File UPDATE Failed 



ETNSP: CPA$RQL Failed 

Description: Domain Name System Resolver inoperable due to internal error. 


ETNSP: Domain Name Cache File Full 

Description: Domain Name System Resolver degraded due to insufficient resources. 


7436 0728–303 3–25


ETNSP: Duplicate cache filenames on NSS statement 



ETNSP: Fatal Error -- unable to open cache files 



ETNSP: Find_Free_QL_Entry: Svc call 1 failed 



ETNSP: Find_Free_QL_Entry: Svc call 2 failed 

Description: Domain Name System Resolver inoperable due to inoperable error. 


ETNSP: Invalid IT received from CFACCS 

Description: Domain Name System Resolver inoperable due to configuration error. 


ETNSP: Invalid Queue Selection 



ETNSP: Invalid Response Received 

Description: Domain Name System Resolver degraded due to network error. 


ETNSP: IPADR statement contains syntax error 

Description: Domain Name System Resolver degraded due to configuration error. 


3–26 7436 0728–303

ETNSP: MM Delete CB FAILED 




ETNSP: MMgetCB FAILED 



ETNSP: MMPoolDef OF CC FAILED 



ETNSP: MMPoolDef of ACT FAILED 



ETNSP: Multiple NSS statements received 



ETNSP: No local name server configured (No NSS statement) 



ETNSP: Non-NS type in NS Response 



ETNSP: NSM Statement contains syntax error 



7436 0728–303 3–27


ETNSP: Query/Response Mismatch 



ETNSP: Send of User Response Failed 

Description: Domain Name System Resolver degraded due to internal error. 


ETNSP: Timer Expiration with invalid State 

Description: Domain Name System Resolver degraded to internal error. 


ETNSP: Unable to Catalog Cache File 



ETNSP: Unexpected Function Code from CFACCS 



ETNUDP: Cannot Allocate Destination Address Table 

Description: Cannot allocate storage. Possible internal or system error. The TCP–IP 

Stack program product generates this CENLOG. 

ETNUDP: Cannot Reach ICS 



ETNUDP: CDS Dereg - Cannot Delete POT 

Description: Cannot release storage. Possible internal error. The TCP–IP Stack 

program product generates this CENLOG. 

3–28 7436 0728–303

ETNUDP: CDS Dereg - ICS POT not Found 


Description: Cannot find data. Possible internal or system error. The TCP–IP Stack 


ETNUDP: CDS Dereg - POT not Found 



ETNUDP: CDS Dereg - Socket Owned By Another 

Description: Application is trying to deregister UDP port owned by another 

application. Possible non-Telcon problem. Possible internal error. 

Action: Check non-Telcon UDP applications. 

ETNUDP: CDS Register - Duplicate Socket 

Description: System configuration problem. More than one application is trying to 

access the same UDP port. 

Action: Check CIM configuration. 

ETNUDP: CDS Register - ICS Connection not Found 



ETNUDP CDS Register - No Resources 



ETNUDP: CDS Reply - Can't Find Connection Table 



ETNUDP: FlushPOTs - Internal Error 

Description: Internal error. The TCP–IP Stack program product generates this 

CENLOG. 

7436 0728–303 3–29


ETNUDP ICS Connect - Allocate Table Failed 



ETNUDP: ICS Disconnect - Cannot Delete POT 



ETNUDP: ICS Disconnect from IML IP Router 



ETNUDP: ICS Registration Exception 


CENLOG. 

ETNUDP Initialization - Cannot Define DAT Table Pool 



ETNUDP Initialization - Cannot Define POT Pool 



ETNUDP: Initialization - Fatal Error 

Description: Fatal internal error. The TCP–IP Stack program product generates this 

CENLOG. 

ETNUDP: Invalid Socket Registration Response 

Description: ICS IPM connection to UDP is available. The TCP–IP Stack program 


ETNUDP: IPM Connect - Complete 


CENLOG. 

3–30 7436 0728–303

ETNUDP: IPM Connect - Exception 



CENLOG. 

ETNUDP: IPM Disconnecting 

Description: ICS IPM connection to UDP is not available. Possible ICS problem. 

ETNUDP: IPM Disconnect - Exception 


CENLOG. 

ETNUDP: IPM Free - Exception 


CENLOG. 

ETNUDP: LLP message unknown 

Description: An internal error was detected. This condition is normally recoverable. 

The TCP–IP Stack program product generates this CENLOG. 


ETNUDP: MMallocCB failed 


CENLOG. 

ETNUDP: MMdelCB failed 


CENLOG. 

ETNUDP: MMgetCB Failed 



ETNUDP: MMnextCB failed 

Description: Cannot find data. Possible internal or system error. 

ETNUDP: Output Discarded - ILM IP Router disconnected 

Description: Internal error. 

ETNUDP: Previous State is Illegal 


7436 0728–303 3–31


ETNUDP: Queues Cannot Be Registered 


CENLOG. 

ETNUDP: Send Failed 

Description: Internal interface disabled. Possible internal error. 

ETNUDP: Send Failed (Disconnected) 


ETNUDP: Send Failed (Queue Full) 


ETNUDP: Supervisor Call Failed 

Description: Cannot release storage. Possible internal error. 

ETNUDP: Svc call 1 failed 



ETNUDP: Svc call 2 failed 



ETNUDP: UDP_TLI_CLASS Service Discontinued 

Description: Service not supported. 

3–32 7436 0728–303

ETNUDP: Undeliverable Message 


Description: UDP cannot deliver some of its messages to their destination. Possible 

router down. Possible configuration problem in network nodes. 

Action: Check for CENL message “IP: ICMP RCVD DEST UNREACH MSG.” If 

message does not occur, check for interface down. Check for gateway configuration 

problems. Otherwise, check contents of ICMP message (CENL message display with 

OPTION=LONG) for source address or message to determine probable location of 

problem. 

ETNUDP: Unrecognizable message 





EU FOR TCP–IP NOT CONFIGURED 

Description: A configuration error was detected by TCP–IP Stack. No EU statement 

of TYPE=TCPIP was found. TCP–IP Stack features are not available. TCP–IP Stack 


Action: Add an EU statement with TYPE=TCPIP to the configuration. 

INITQUES: NO SYSTEM TRUNKS CONFIGURED 

Description: TCP–IP Stack cannot find the configured trunks. This may indicate an 

internal software fault or a configuration error. Check the configuration, and try 

restarting Telcon. The TCP–IP Stack program product generates this CENLOG. 

IP: BAD FUNCTION CODE FROM MIP 





IP: BUFFER SIZE TOO LARGE (R8) 




7436 0728–303 3–33


IP: CALL CLEARING, CAUSE = #, DIAG = # 

Description: Indicates receipt of a clear indication from PSCS, clearing an active 

connection. R8 contains the diagnostic code, giving the reason for the clear 

indication. The TCP–IP Stack program product generates this CENLOG. 

IP: CALL REJECTED, CAUSE - #, DIAG = # 

Description: Indicates receipt of a clear indication from PSCS, rejecting a call 

request. R8 contains the diagnostic code, giving the reason for the clear. The TCP–IP 


IP: CANNOT DISPLAY ALL TABLES 

Description: IP cannot fit all tables into the NMS response message. The TCP–IP 


IP: CANNOT DISPLAY IP STATUS RECORD 

Description: IP cannot fit the status into the NMS response message. The TCP–IP 


IP: CANNOT FIND NA FOR ADR = ! 

Description: There is no IPADDR configuration providing an NA for this IP address 

(R8, R9). The TCP–IP Stack program product generates this CENLOG. 

IP: CANNOT READ LINE, STE = # 

Description: IP cannot access the configuration for a LINE statement. The 

configuration database may be corrupted. The TCP–IP Stack program product 


IP: CANNOT ROUTE ICMP ECHO REQUEST 

Description: IP cannot find a route for an ICMP Echo Request. The request will be 

discarded. The TCP–IP Stack program product generates this CENLOG. 

IP: CFACCS ERROR: CODE = #, SPECIFIC ERROR = # 

Description: Indicates a problem when accessing the Telcon configuration. R8 gives 

the error type, and R9 gives a more specific diagnostic. For more information on 

these codes, refer to the Telcon Programming Reference Manual (7436 0710). The 


3–34 7436 0728–303

IP: CLEAR COLLISION: CAUSE = #, DIAG = # 


Description: IP received a clear indication on a virtual circuit that was expecting a 

clear confirmation. The TCP–IP program product generates this CENLOG. 

IP: CONFIG ACCESS ERR: DLCUNIT PROCESSING 

Description: IP cannot read a DLCUNIT configuration statement. IP detected an 

internal error. This may indicate a serious software fault. The TCP–IP Stack program 


IP: CONFIG ACCESS ERR IN SAP PROCESSING 

Description: IP cannot read a SAP configuration statement. IP detected an internal 

error. This may indicate a serious software fault. The TCP–IP Stack program product 


IP: CONFIG CONFLICT LOCAL ADDRESS = ! 

Description: A configuration error was detected. The IPADR statement specifying 

the indicated IP address may be in error. There is no matching IP address in the ENS 

IP Router configuration. Some configuration functions may not be available. The 


IP: CONFIGURATION ERROR, 

RESTART TELCON FOR ONLINE CONFIGURATION CHANGES 

Description: IP detected configuration errors. Internal tables do not match 

configuration information. This error can occur when online configuration changes 

are made. The 


IP: DGSIZE REDUCED FROM n TO n BYTES BY LINE linename 

Description: Possible configuration error. Compare datagram size in SUBNET 

statement with maximum datagram size permitted by line module. 

IP: DIFFERENT SUBNET TYPES W/SAME NET: ! 

Description: IP found more than one SUBNET configuration, each with a different 

TYPE parameter. The TCP–IP Stack program product generates this CENLOG. 

IP: DLCUNIT CONFIG ERROR: STE = # 

Description: DLCUNIT facility identifier is invalid. This error can occur when online 

configuration changes are made. The TCP–IP Stack program product generates this 

CENLOG. 

7436 0728–303 3–35


IP: DOWN PDTE CMD NOT IMPLEMENTED FOR 

INTERNET (DDN X.25) CONNECTIONS 

Description: A response to a DOWN PDTE command. IP does not process this 

command, so although the DTE is set DOWN (if configured), existing connections to 

this DTE are not cleared. The TCP–IP Stack program product generates this 

CENLOG. 

IP: DTEADR PARAMETER MISSING ON PDNGRP 

Description: IP requires the DTEADDR parameter on the PDNGRP statement when 

the SUBNET is of TYPE=DDN. The TCP–IP Stack program product generates this 

CENLOG. 

IP: DUPLICATE ADR MAP = ! 

Description: IP detected an internal error. This may indicate a serious software 

fault. The TCP–IP Stack program product generates this CENLOG. 

IP: DUPLICATE MESSAGE STILL PRESENT 



IP: DUPLICATE OPTION RECEIVED 

Description: IP received two identical IP options in the same datagram. The second 

option will be ignored. Another TCP/IP host may be having a problem. The TCP–IP 


IP: DUPLICATE SAP-S: LINE STE = # 

Description: TCP–IP Stack detected a configuration error. More than one SAP 

statement with the same type DLCUNIT point at the line. The TCP–IP Stack program 


Action: Verify that the DCLUNIT statements are correct. 

Note: TCP–IP Stack does not require the configuration of SAP and DLCUNIT 

statements. 

IP: ERROR IN SUBNET CONFIGURATION 

Description: IP received a message for which no corresponding SUBNET 

configuration exists. The TCP–IP Stack program product generates this CENLOG. 

3–36 7436 0728–303

IP: EXPEDITED DATA RESPONSE MISSING 


Description: An error was detected in the interface to ENS IP Router. This condition 

is normally recoverable. The TCP–IP Stack program product generates this CENLOG. 


IP: EXTERNAL INTERFACE ERROR 

Description: IP has detected an error in data received from a non-TCP–IP Stack 

component. This may be another program product (e.g. PSCS), a Telcon component 

(e.g. HLEMAN), or an external program (e.g. ICS). R13 indicates the location in IP 

where the error was detected. The TCP–IP Stack program product generates this 

CENLOG. 

IP: FRAGMENT REASSEMBLY ERROR, SRC ADR = ! 



IP: FRAGMENT REASSEMBLY NOT TIMED 

Description: An acute resource shortage forced IP to abandon timing fragment 

reassembly. This is not a serious problem if the message eventually does get 

assembled. Until it does, the incomplete message occupies buffer and link-area space. 


IP: HOST CHANNEL NOT FOUND, INPUT LOST 

Description: IP received a message for which no corresponding SUBNET 

configuration exists. The TCP–IP Stack program product generates this CENLOG. 

IP: HOST CHANNEL SUBNETS SHOULD SPECIFY CHANNELS 

Description: IP found a SUBNET configuration of TYPE=IPCHAN, which does not 

reference a CHANNEL. The TCP–IP Stack program product generates this CENLOG. 

IP: ICMP ECHO REPLY ID CORRUPTED 

Description: ICMP stores identifying information in echo requests. The returning 

echo reply held no recognizable identifying information. This echo reply was either 

unsolicited or corrupted in transit. The TCP–IP Stack program product generates this 

CENLOG. 

7436 0728–303 3–37


IP: ICMP NO CONNECTION FOR REDIRECT–IGNORED 

Description: IP is ignoring the redirect because it cannot find the route specified by 

the redirect. TCP–IP Stack may have a configuration error, or the network may be 

having a problem with a router or a line. The TCP–IP Stack program product 


IP: ICMP RECVD UNSOLICITED ECHO REPLY 

Description: ICMP received an echo reply and could not match it to an outstanding 

request. The outstanding request may have timed out. This error is similar to IP:ICMP 

RECEIVED UNRECOGNIZED INPUT. The TCP–IP Stack program product generates 

this CENLOG. 

IP: ICMP RCVD DEST UNREACH MSG FROM xxx.xxx.xxx.xxx 

DESTINATION = xxx.xxx.xxx.xxx UDM CODE = # 

Description: IP received a diagnostic message that originated on a datagram that 

could not be routed to its destination. TCP–IP Stack may have a configuration error, 

or the network may be having a problem with a router or a line. The TCP–IP Stack 


IP: ICMP RCVD PARAM PROBLEM MSG 

Description: IP is building messages with invalid headers. The TCP–IP Stack 


IP: ICMP RCVD REDIRECT MSG FROM xxx.xxx.xxx.xxx 

NEW GATEWAY = xxx.xxx.xxx.xxx 

DESTINATION = xxx.xxx.xxx.xxx 

Description: Another router is informing IP of a better route. The TCP–IP Stack 


IP: ICMP RCVD SOURCE QUENCH FROM xxx.xxx.xxx.xxx 

DESTINATION: xxx.xxx.xxx.xxx 

Description: A destination host is receiving too many messages from one of the local 

hosts. The TCP–IP Stack program product generates this CENLOG. 

IP: ICMP RCVD TIME EXCEEDED MSG FROM xxx.xxx.xxx.xxx 

DESTINATION xxx.xxx.xxx.xxx 

Description: An output message spent more time traversing the Internet than R8 

allowed. R8 indicates the specific event. The TCP–IP Stack program product 


3–38 7436 0728–303

IP: ICMP RCVD UNRECOGNIZED TYPE: # 


Description: ICMP does not recognize the input just received. There may be a 

software failure in either the peer ICMP program or in this IP/ICMP program. The 


IP: ICS CONNECTIONS DOWN 

Description: IP’s connection to ICS is not available. The TCP–IP Stack program 


IP: ICS CONNECTIONS ESTABLISHED 




IP: ICS CONNECTION FAILED 

Description: An attempt to connect to an ICL LAN line module failed. The TCP–IP 


IP: ICS CONNECTIONS LOST 

Description: TCP–IP Stack has lost communications with other software 

components. The TCP–IP Stack program product generates this CENLOG. 

Action: Verify that all software components are running as needed. If the condition 


IP: INPUT DISCARDED 

Description: An input message was discarded. This event has several causes, but 

does not indicate a serious condition. The TCP–IP Stack program product generates 

this CENLOG. 

IP: INPUT DISCARDED ON UNCONFIGURED INTERFACE 

Description: TCP–IP detected a configuration error. Input was received on an 

unconfigured interface. Some configuration functions may not be available. The 


Action: Verify that the correct LINE, CHANNEL, or PDNGRP parameters are 

specified on the SUBNET statements. 

7436 0728–303 3–39


IP: INPUT LOST -- CONFIGURATION ERROR 

Description: An input message was discarded. It could not be processed because it 

was received on an incorrectly configured interface. The TCP–IP Stack program 


IP: INPUT LOST, OUT OF RESOURCES 

Description: An input message could not be processed for lack of resources. If it 

occurs frequently, review your sizing requirements. Your configuration may be using 

more resources than necessary if it contains many normally unused facilities. The 


IP: INPUT LOST, TRANSMISSION ERROR 

Description: An input message was discarded because IP detected a transmission 

error. The TCP–IP Stack program product generates this CENLOG. 

IP: INTERFACE DOWN, NET = ! 

Description: IP received indication that there are no available connections to a 

subnetwork. Registers 8 and 9 contain the network address. The TCP–IP Stack 


IP: INTERFACE UP, NET = ! 

Description: IP received indication that there are connections available to a 

subnetwork. Registers 8 and 9 contain the network address. The TCP–IP Stack 


IP: INTERNAL ERROR, POSSIBLE RIP PROBLEM 



IP: INTERNAL ERROR, POSSIBLE SMP PROBLEM 



IP: INTERNAL INTERFACE ERROR 

Description: IP has detected an internal error. Another TCP–IP component is 

behaving in an unexpected manner. This may indicate a serious software fault. The 


3–40 7436 0728–303

IP: INTERNAL PROCESSING ERROR 


Description: TCP–IP Stack detected an internal error. This error is normally 



IP: INTERNAL TABLES CORRUPTED 

Description: A fatal error. The error may be generated in several areas, and usually 

means that IP detected unexpected values in its runtime tables. Dump; then restart 

Telcon. The TCP–IP Stack program product generates this CENLOG. 

IP: INVALID INPUT MESSAGE 

Description: IP received a message with an invalid IP header. Another TCP–IP host 

could be having problems. The TCP–IP Stack program product generates this 

CENLOG. 

IP: INVALID OPTION LENGTH RECEIVED 

Description: IP received an IP option with an invalid length field. Another TCP–IP 

host could be having problems. The TCP–IP Stack program product generates this 

CENLOG. 

IP: INVALID OPTION POINTER RECEIVED 

Description: IP received an IP option with an invalid pointer field. Another TCP–IP 

host could be having problems. The TCP–IP Stack program product generates this 

CENLOG. 

IP: INVALID SUBNET CLASS FOR LOGICAL HOSTS 

Description: IP can support DDN logical hosts on Class A or Class B subnetworks 

only. The TCP–IP Stack program product generates this CENLOG. 

7436 0728–303 3–41


IP: IPADR CONFIG ERR, IPADR IP ADDRESS = !, LINE STE = # 

LINE IP ADDRESS = !, MASK = ! 

Description: TCP–IP Stack detected a configuration error. The IP address specified 

on an IPADR statement does not match the IPNETID specified by the SUBNET 

statement that references the LINE, CHANNEL, or PDNGRP parameter referenced by 

the IPADR statement. Some configured functions may not be available. The TCP–IP 


Action: Verify that all IP addresses and masks are specified correctly. Verify that 

IPADR statements using the LINE, CHANNEL, or PDNGRP parameter refer to the 

correct statement. 

IP: IPADR CONFIGURATION ERROR, IP ADDR = !, LINE = # 

Description: TCP–IP Stack detected a configuration error. There is no SUBNET 

statement configured for the LINE, CHANNEL, or PDNGRP referenced by an IPADR 

statement. Some configured functions may not be available. The TCP–IP Stack 


Action: Verify that all IPADR statements using the LINE, CHANNEL, or PDNGRP 

refer to the correct statement. 

IP: IPADR nnn.nnn.nnn.nnn IN ERROR - BOTH LOCAL 

Description: Configuration error. IPADR statement should not be used to specify 

two local addresses at the same time. 

IP: IPM SERVICE ERROR, R8 = ERROR, R9 = IPM ID 

Description: TCP–IP Stack detected a system error. Some configured functions may 

not be available. The TCP–IP Stack program product generates this CENLOG. 

Action: If the problem persists, contact your support center. 

IP: LA ENTRY IN USE, SHOULDN'T BE 

Description: Fatal error. IP detected that its link area appeared to be corrupted. 

Dump; then restart Telcon. The TCP–IP Stack program product generates this 

CENLOG. 

IP: LA ENTRY NOT IN USE, SHOULD BE 

Description: A fatal error. IP detected that its link area appeared to be corrupted. 

Dump; then restart Telcon. The TCP–IP Stack program product generates this 

CENLOG. 

3–42 7436 0728–303

IP: LAN ATTACHMENTS INCOMPLETE (R8=STE) 


Description: IP detected a missing DLCUNIT or SAP statement. The TCP–IP Stack 


IP: LAN SUBNETS SHOULD SPECIFY LINES 

Description: IP found a SUBNET configuration of TYPE=LAN, LANLLC, IPTR, or 

FDDI, which does not reference a LINE. The TCP–IP Stack program product 


IP: LINK AREA IS FULL 

Description: IP has tried to save data for later processing. Because of an acute 

resource shortage, the data was not saved. The TCP–IP Stack program product 


IP: LINK AREA OVERFLOW 

Description: A moderately serious problem that could be caused by an acute 

problem. The link area has a large capacity, and link-area overflow means hundreds 

of messages and fragments of messages have not been processed. If the problem 

persists, dump and restart Telcon. The TCP–IP Stack program product generates this 

CENLOG. 

IP: LINK AREA WAS NOT EXPANDED 

Description: A shortage of memory resources. The link area space currently 

allocated is insufficient to meet message storage requirements, so the latest input will 

probably be discarded. This problem is likely to occur before link-area overflow 

occurs. The TCP–IP Stack program product generates this CENLOG. 

IP: LOGICAL HOST ENABLED: CAUSE = #, DIAG = # 

Description: A configured logical host has been enabled. The TCP–IP Stack 


IP: LOGICAL HOST NOT ENABLED: CAUSE = #, DIAG = # 

Description: A configured logical host could not be enabled. R8 contains a 

diagnostic code. The TCP–IP Stack program product generates this CENLOG. 

IP: MAP FOR IP ADDRESS ! DOESNT MATCH NETWORK ! 

Description: TCP–IP Stack detected a configuration error. The address mapping 

using the DTE, NA, or STA parameter on an IPADR statement does not match the 

7436 0728–303 3–43


TYPE parameter on the associated SUBNET statement. Some configured functions 


Action: Verify that all IP addresses and masks are specified correctly. Verify that the 

correct TYPE parameter is used on the SUBNET statements. 

IP: MASK nnn.nnn.nnn.nnn IN ERROR - MASK NOT CONTIGUOUS 

Description: Configuration error. CIDR (RFC 1519) requires IP address masks to be 

contiguous. This means that all “ones” must start at the most significant bit 

(canonical), and no ones may follow the first “zero” in the mask. 

Example: 

Correct: 255.255.192.0 

Incorrect: 255.255.3.0 

TCP–IP Stack automatically correct’s the problem by filling in the zeros with ones. 

This is done to allow TCP–IP Stack to execute correctly; it probably does not result in 

a correct configuration. 

IP: MESSAGE TOO LARGE, SRC ADR = ! 

Description: TCP–IP Stack discarded a received message that was too large. 

TCP–IP Stack cannot handle messages that assemble to larger than 12,287 bytes. 


IP: MESSAGE TRACING IS NOT ON 

Description: IP detected an internal error. This could indicate a serious software 


IP: MULTIPLE DNS SUBNETS FOUND 

Description: IP found more than one SUBNET configuration of TYPE=IPDNS. The 


IP: NEED TO FRAGMENT OUTPUT BUT CANNOT 

DESTINATION: ! 

MAX FRAGMENT SIZE: # 

Description: IP is trying to send a datagram that may not be fragmented on a 

network that requires this datagram to be fragmented. This could indicate a problem 

with the configured DGSIZE parameter on the SUBNET statement. The TCP–IP Stack 


3–44 7436 0728–303

IP: NMS COMMAND FACILITY NOT FOUND 


Description: IP received an NMS command referencing a configured facility that is 

not associated with IP SUBNETs. The TCP–IP Stack program product generates this 

CENLOG. 

IP: NO DTE ADDRESS FOR CALL TO NON-DDN DESTINATION - ADR = ! 

Description: There is no IPADR configuration providing a DTEADR for this IP 

address (R8, R9). The TCP–IP Stack program product generates this CENLOG. 

IP: NO LOCAL ADDRESSES CONFIGURED 

Description: TCP–IP Stack detected a configuration error. No IPADR statement was 

found to configure an IP address with the LOCAL flag. Some configured functions 


Action: Verify that all IP addresses and masks are specified correctly. Verify that IP 

addresses assigned to TCP–IP Stack are indicated by the LOCAL flag on the IPADDR1 

or IPADDR2 parameter. 

IP: NO MATCHING DLCI FOR FRLY SUBNET 

Description: IP cannot find a DLCI statement to match the DLCI parameter for this 

IP address (R8, R9). The TCP–IP Stack program product generates this CENLOG. 

IP: NO PDNGRP FOR PSCS LINE 

Description: TCP–IP Stack detected a configuration error. No PDNGRP statement 

was found for a LINE referenced by a SUBNET statement that had the TYPE 

parameter set to IPPDN or DDN. Some configured functions may not be available. 


Action: Verify that the SUBNET statement references the correct LINE statement. 

Verify that the Packet Switched Communications Software (PSCS) program product is 

configured correctly. 

IP: OPTION LIST TOO LONG, OPTION IGNORED 



IP: OUTPUT LOST, OUT OF RESOURCES 

Description: A lack of resources caused IP to abandon an output message. This 

problem is not serious. Check sizing requirements to avoid this problem. The TCP–IP 


7436 0728–303 3–45


IP: OUTPUT LOST, QUEUE FULL 

Description: DNS, host channel (HCC), LAN, or PSCS is not keeping up with IP or 

other users of DNS. IP detected an internal error. This could indicate a serious 

software fault. The TCP–IP Stack program product generates this CENLOG. 

IP: REJECT CALL, NO RESOURCES 

Description: A PSCS call was rejected because of a lack of resources. If this event 

occurs frequently, recheck your sizing requirements. The TCP–IP Stack program 


IP: SET TIMER FAILED 

Description: IP had to drop a heartbeat timer used to check on virtual activity, due 

to a lack of resources. This means that IP will no longer disconnect X.25 SVCs when 

they become inactive. This is not a serious problem unless hosts on the LAN change 

their addresses. The TCP–IP Stack program product generates this CENLOG. 

Action: Although this problem is not serious, the only recourse is to restart Telcon. 

If this event occurs frequently, recheck your sizing requirements. 

IP: SET TIMER FAILED FOR ADR - ! 




IP: STACK CORRUPTED 



IP: STRICT SOURCE ROUTE FAILED 

Description: TCP–IP could not forward a message with a strict source route option. 

The rules for processing a strict source route option do not permit forwarding this 

message. This condition is normally not recoverable. The TCP–IP Stack program 



IP: SUBNET/IPADR HAVE SAME ADR = nnn.nnn.nnn.nnn 

Description: Configuration error. Cannot specify a local IP address with the nonnetwork 

portion all zeros. 

3–46 7436 0728–303

IP: SUBNET MISSING LOCAL ADDRESS - ADR = ! 


Description: TCP–IP Stack detected a configuration error. No IPADR statement was 

found to configure an IP address associated with the indicated SUBNET statement 

with the LOCAL flag. Some configured functions may not be available. The TCP–IP 


Action: Verify that the IP addresses and masks are specified correctly. Verify that 

the IP address assigned to TCP–IP Stack for the indicated SUBNET statement is 

indicated by the LOCAL flag on the IPADDR1 or IPADDR2 parameter. 

IP: SUBNET STATEMENT ERROR 

Description: IP detected an error in a SUBNET configuration statement. The 


IP: TCP–IP NOT CONFIGURED – DISCARDING INPUT 

Description: IP is receiving messages, even though no IPADR or SUBNET 

statements were processed. The TCP–IP Stack program product generates this 

CENLOG. 

IP: TCP–IP STACK CONNECTED TO ILM IP ROUTER 




IP: TCP–IP STACK DISCONNECTED FROM ILM IP ROUTER 

Description: TCP–IP Stack has lost communications with other software 

components. The TCP–IP Stack program product generates this CENLOG. 

Action: Verify that all software components are running as needed. If the condition 


IP: TIMER RETRY COUNT EXHAUSTED 

Description: IP repeatedly attempted to set a timer and lack of resources prevented 

successful completion. This event usually precedes another timer-related event. If 

this event occurs frequently, recheck your sizing requirements. The TCP–IP Stack 


IP: TRACE - ARP CTL MSG 

Description: Informational only message. Usually indicates changes in interface 

state. 

7436 0728–303 3–47


IP: TRACE - HLEMAN CONFIRM 


state. 

IP: TRACE - IP CTL MSG 


state. 

IP: TRACE - ARP ATTACH CONFIRM 


state. 

IP: TRACE - IP ATTACH CONFIRM 


state. 

IP: TRACE - REATTACH REQUEST 


state. 

IP: TRACE FACILITY NOT FOUND 

Description: IP received an NMS command referencing a configured facility that is 

not associated with IP’s SUBNETs. The TCP–IP Stack program product generates this 

CENLOG. 

IP: ULP QUEUE FULL, DISCARDING UD45 




IP: ULP QUEUE FULL, IC45 DISCARDED 



IP: ULP QUEUE IS FULL, LOOP-BACK DATA DISCARDED 



3–48 7436 0728–303

IP: UNABLE TO SEND BROADCAST MSG OVER X.25 


Description: An upper layer attempted to send a broadcast message through a DDN 

or generic X.25 layer. The TCP–IP Stack program product generates this CENLOG. 

IP: UNRECOG SUBNET TYPE 

Description: IP found a SUBNET configuration of an unrecognized TYPE. The TCP– 

IP Stack program product generates this CENLOG. 

IP: UNRECOGNIZED CONFIG ITEM 

Description: IP was called for initialization and the configuration item passed was 

not recognized. This error indicates a software failure on the part of the initialization 

module. This is not a serious condition. The TCP–IP Stack program product 


IP: UNRECOGNIZED OPTION RECEIVED 

Description: IP received an IP option that was not implemented. Another host with 

TCP–IP could be having problems. The TCP–IP Stack program product generates this 

CENLOG. 

IP: UNSOLICITED PING REPLY 

Description: TCP–IP Stack received an unexpected message or too much time 

elapsed before receiving an expected message. This error is normally recoverable. 


Action: Increase the amount of time specified by the TIMEOUT parameter in the 

NMS command TCP PING. If the condition persists, contact your support center. 

IP: UNSUPPORTED OPTION RECEIVED 

Description: The security stream ID and timestamp options are not supported at this 

time. The TCP–IP Stack program product generates this CENLOG. 

IP: X.25 NETWORK CONNECTIONS DOWN (R8, R9) 

Description: PSCS informed IP that the link is not available for data. The TCP–IP 


IP: X.25 NETWORK CONNECTIONS UP (R8, R9) 

Description: PSCS informed IP that the link is available for data. The TCP–IP Stack 


7436 0728–303 3–49


IPSVS: PK$ ERROR FROM IP 

Description: TCP–IP stack detected an internal error. This could indicate a serious 


IPSVS: UNKNOWN IP MESSAGE TYPE 

Description: TCP–IP stack detected an internal error. This could indicate a serious 


RIP: Cannot init configured route 

Description: The interface configured on the SUBNET statement cannot be placed in 

the RIP’s routing table because of insufficient memory. The routing information 

protocol module for the TCP–IP Stack program product generates this CENLOG. 

RIP: Cannot init static route 

Description: RIP cannot place a static route into its routing table because of 

insufficient memory. The routing information protocol module for the TCP–IP Stack 


RIP: Invalid Subnet Mask on Subnet NDS 

Description: TCP–IP Stack detected a configuration error. The SUBNMASK 

parameter on a SUBNET statement is not correct. The TCP–IP Stack program 


Action: Verify the configuration to make sure all IP addresses are specified correctly. 

RIP: Maximum number of IPADDRs exceeded 

Description: TCP–IP Stack could not process all configuration statements 

completely. Some configured functions may not be available. The TCP–IP Stack 


RIP: Maximum number of RIPNBRs exceeded 

Description: TCP–IP Stack could not process all configuration statements 

completely. Some configured functions may not be available. The TCP–IP Stack 


3–50 7436 0728–303

RIP: No IPNETID found for net # of IPGATEWY 


Description: TCP–IP Stack detected a configuration error. The IPGATEWY 

parameter of a SUBNET statement specifies an IP address for which there is no 

configured interface. The TCP–IP Stack program product generates this CENLOG. 


RIP: No space for new route 

Description: TCP–IP Stack was not able to get needed memory resources. Some 

routes may not be available. The TCP–IP Stack program product generates this 

CENLOG. 

RIP: RIP on but no LINE specified 

Description: TCP–IP Stack detected a configuration error. A SUBNET statement 

specifies RIP=YES, but does not specify an interface. The TCP–IP Stack program 


Action: Either remove the RIP parameter, or add a LINE, CHANNEL, or PDNGRP 

parameter. 

RIP: RIP on but IP Routing is off 

Description: TCP–IP Stack detected a configuration error. A SUBNET statement 

specified RIP=YES, but does not specify IPROUTER=YES. Some configured 

functions may not be available. The TCP–IP Stack program product generates this 

CENLOG. 

Action: Either set RIP=SILENT or add IPROUTER=YES. 

RIP: RIP not supported on SUBNET TYPE 

Description: TCP–IP Stack detected a configuration error (DDN, IPCHAN, or 

IPPDN). A SUBNET statement specifies RIP=YES, but the TYPE parameter indicates 

an incompatible value. The TCP–IP Stack program product generates this CENLOG. 

Action: Remove the RIP parameter. Verify that the correct TYPE parameter was 

used. 

RIP: Route table allocation failure 

Description: RIP cannot acquire enough memory for its routing table. The routing 

information protocol module for the TCP–IP Stack program product generates this 

CENLOG. 

7436 0728–303 3–51


RIP: Strange SNMP Message 

Description: TCP–IP Stack detected an internal error condition. This condition 

usually is recoverable. The TCP–IP Stack program product generates this CENLOG. 

RIP: SUBNET NDS has no local IPADR configured 

Description: TCP–IP Stack detected a configuration error. An interface configured 

by a SUBNET statement has no corresponding IPADR statement that gives a local IP 

address to match the IPNETID. The TCP–IP Stack program product generates this 

CENLOG. 


Verify that an IPADR statement specifies the local address for that interface. 

RIP: Timer pool allocation failure 

Description: RIP cannot acquire enough memory to allocate its timer pool. The 

routing information protocol module for the TCP–IP Stack program product generates 

this CENLOG. 

TCPTB - DUPLICATE HIC FROM DTP 





TCPTB - INTERNAL FATAL ERROR 




TCPTB - MISSING/INVALID DTPX HEADER 





3–52 7436 0728–303

TCPTB - MISSING/INVALID XEU 


Description: TCP–IP Stack detected a configuration error. There is an error with an 

XEU statement. Some configured functions may not be available. The TCP–IP Stack 


Action: Verify that all XEU statements are specified correctly. 

TCPTB - MISSING REQUIRED HIC FROM DTP 





TCPTB - PARTIAL MESSAGE FROM TCPTS 





TCPTB - UNEXPECTED INPUT FROM DTP 





TCPTB - UNEXPECTED INPUT FROM ETNSMP 





TCPTB - UNEXPECTED INPUT FROM TCPTS 





7436 0728–303 3–53


TCPTS: ERROR TPDU RECEIVED - - CONNECTION CLOSED 





TCPTS: INVALID MESSAGE FROM TCP DISCARDED 





TCPTS: INVALID MESSAGE FROM TSU DISCARDED 





TCPTS: INVALID RFC1006 HEADER OR LENGTH 

Description: TCP–IP Stack received an invalid message. This condition is normally 

not recoverable. The TCP–IP Stack program product generates this CENLOG. 

TCPTS: NO CONNECTION RESOURCES AVAILABLE 

Description: TCP–IP Stack has insufficient resources. This condition is normally 



TCPTS: NO REGISTRATION RESOURCES AVAILABLE 

Description: TCP–IP Stack has insufficient resources. This condition is normally 



3–54 7436 0728–303

TCPTS: TCP TRANSPORT SERVICE FATAL ERROR 





TCPTS: UNEXPECTED INPUT FROM ETNMSP 





TCP 4000 NO ERROR SPECIFIED 

Description: No error was specified. The transmission control protocol module for 

the TCP–IP Stack program product generates this CENLOG. 

TCP 4001 INTERFACE PKT–UNKNOWN ERROR 

Description: The request primitive received from the ULP is invalid for the 

connection state. The transmission control protocol module for the TCP–IP Stack 


TCP 4002 NO CONNECTION EXISTS 

Description: The LLP connection ID returned from ULP is unknown to TCP. The 

transmission control protocol module for the TCP–IP Stack program product 


TCP 4003 DUPLICATE CONNECTION ATTEMPTED 

Description: A connection attempt is made with identical socket addresses to an 

existing connection. The transmission control protocol module for the TCP–IP Stack 


TCP 4004 NO RESOURCES FOR REQUEST 

Description: Architectural resources, such as buffers or queues, are temporarily 

unavailable. The transmission control protocol module for the TCP–IP Stack program 


7436 0728–303 3–55


TCP 4005 NO FOREIGN SOCKET SPECIFIED 

Description: The ULP failed to provide the foreign socket (destination) address to 

which the connection is to be made. The transmission control protocol module for 


TCP 4006 SECURITY/PRECEDENCE VIOLATION 

Description: A security or precedence conflict occurred during connection 

establishment. The transmission control protocol module for the TCP–IP Stack 


TCP 4007 NETWORK FAILURE 

Description: Attempt to route a message failed because of a gateway failure, or 

because there is no network connection to the destination. Check with your network 

administrator. The transmission control protocol module for the TCP–IP Stack 


TCP 4008 SERVICE FAILURE 

Description: The ULP service request primitive type passed by a ULP is unknown to 

TCP. The transmission control protocol module for the TCP–IP Stack program 


TCP 4009 ULP–REQUESTED ABORT OCCURRED 

Description: The local end user terminal or application closed or aborted the TCP 

session. Try again. The transmission control protocol module for the TCP–IP Stack 


TCP 4010 REMOTELY–REQUESTED ABORT OCCURRED 

Description: The peer TCP requested the connection to be aborted. The 



TCP 4011 CONNECTION CLOSING 

Description: TCP received an invalid service request primitive while the connection 

is being closed. The transmission control protocol module for the TCP–IP Stack 


3–56 7436 0728–303

TCP 4012 ULP–REQUESTED CLOSE OCCURRED 


Description: The local end user terminal or application closed or aborted the TCP 

session. Try again. The transmission control protocol module for the TCP–IP Stack 


TCP 4013 TIMEOUT OCCURRED 

Description: TCP encountered the maximum number of message timeout 

occurrences. The transmission control protocol module for the TCP–IP Stack 


TCP 4014 OPEN FAILURE 

Description: TCP is unable to complete a connection opened by a ULP. The 



TCP 4015 INTERNAL ERROR 

Description: Local TCP internal error. The transmission control protocol module for 


TCP 4016 DCPOS CANNOT ALLOCATE ANY MORE DSSNs 

Description: This message indicates a resource shortage. It usually is a sign of 

insufficient memory for the size of Telcon or the number of Telcon runs. The 



TCP 4017 NMS REQUEST ABORT 

Description: TCP–IP Stack is closing a TCP session in response to the NMS 

command TCP KILL TCP. This message is informational only. The TCP–IP Stack 


TCP 4018 RECEIVED UNRECOGNIZED NMS COMMAND 





7436 0728–303 3–57


TCP 4019 MAXIMUM NUMBER OF TCP PORTS EXCEEDED 

Description: TCP–IP Stack is running out of allocatable resources. This condition is 

normally recoverable. The TCP–IP Stack program product generates this CENLOG. 

TCP 4020 SNMP INTERFACE INTERNAL ERROR 





TCP 4021 SNMP INITIATED ABORT 

Description: TCP–IP Stack is closing a TCP session in response to an SNMP 

command. This message is informational only. The TCP–IP Stack program product 


Action: None. 

TCP 4022 DELETE SEGMENT FAILED 

Description: TCP–IP Stack detected a system error. This condition is normally 



TRK: TI$ TABLE CREATION FAILED 

Description: Internal data structure could not be set up, possibly due to limited 

resources. Some configured functions may not be available. The TCP–IP program 



TRK: MESSAGE PACKET ERROR - ID=#, TYPE=# 

Description: TCP–IP Stack detected an internal error condition. This condition is 

normally recoverable. The TCP–IP program product generates this CENLOG. 


3–58 7436 0728–303

TRK: UNKNOWN FUNCTION: CODE = # 



normally recoverable. The TCP–IP program product generates this CENLOG. 


TRK: IPADR STMT NOT CONFIGURED FOR TRUNK 

LOCAL ADDRESS: ! 

REMOTE ADDRESS: ! 

Description: TCP–IP Stack detected a configuration error. No IPADR statement 

referencing a trunk was found that matched the IP addresses specified on incoming 

data. The TCP–IP program product generates this CENLOG. 

Action: Verify that IP addresses on IPADR statements that reference trunks are 

correctly specified. 

TRK: TRUNK HAS BEEN DOWNED BY PEER 

LOCAL ADDRESS: ! 


Description: A DCP-to-DCP trunk is no longer available for data due to actions taken 

by the other DCP. The TCP–IP Stack program product generates this CENLOG. 

TRK: TRUNK IS NOW UP 

LOCAL ADDRESS: 1 


TRUNK STE INDEX: # 

Description: DCP-to-DCP trunk by means of IP has initialized on this side. The 


TRK: BOTH ADDRESSES ARE MARKED LOCAL 

ADDRESS 1: ! 

ADDRESS 2: ! 

Description: Configuration problem in IPADR configuration. The TCP–IP Stack 


TRK: NEITHER ADDRESS IS MARKED LOCAL 

ADDRESS 1: ! 

ADDRESS 2: ! 

Description: Configuration problem in IPADR configuration. The TCP–IP Stack 


7436 0728–303 3–59


TRK: NO TIMER ID OBTAINED 

Description: TCP–IP Stack detected an internal error. This may indicate a serious 


TRK: TI$ OR DF$ INITIALIZATION FAILED 



TRK: TI$ TABLE CREATION FAILED 




TRK: ERROR - LIMITED RESOURCES 



TRK: NO HCB FOR TRUNK ID=# WAS FOUND 



UTL: LAX IN USE, SHOULD NOT BE 


usually recoverable. The TCP–IP Stack program product generates this CENLOG. 


3–60 7436 0728–303

UTL: NO MORE LINK AREA ENTRIES AVAILABLE 


Description: TCP–IP Stack is running out of allocatable resources. This condition is 



UTL: TIMER CANT BE QUEUED 




UTL: TIMER ERROR, R12=QN, R13=ERROR CODE 




1001 HOSTSRV INVALID MESSAGE TYPE 

Description: The message type received from the LLP was either invalid or is not 

supported in this release. The host services module for the TCP–IP Stack program 


1002 HOSTSRV INVALID CONNECTION ID 

Description: The message received from the LLP referenced a nonexistent 

connection entry. Record the following information and give to the site analyst: 

R12: Current connection identifier (PK$ULP) 

R11: PK$MTYPE–message type from current message packet. Message types 

found in AADDNDEF 

The host services module for the TCP–IP Stack program product generates this 

CENLOG. 

7436 0728–303 3–61


1003 HOSTSRV ILLOGICAL MESSAGE 

Description: The message type received was invalid for the current connection. The 

following information should be recorded and given to the site analyst: 

R12: DCA connection state (8 bits)/DDN connection state (8 bits). Connection 

state codes found in DDNSVS 

R11: PK$MTYPE — message type from current message packet. Message types 

found in AADDNDEF 


CENLOG. 

1004 HOSTSRV INVALID DCA STATE FOUND 

Description: The message type received was invalid for the current DCA connection. 


CENLOG. 

1005 HOSTSRV INVALID LLP STATE FOUND 

Description: The message type received was invalid for the current DDN 

connection. The host services module for the TCP–IP Stack program product 


1006 HOSTSRV INPUT HIC ANALYSIS ERROR 

Description: An error was detected when translating the internal interface packet 

parameters into the HIC sequences for the (DDNG) DDNSVS header. The host 

services module for the TCP–IP Stack program product generates this CENLOG. 

1007 HOSTSRV NO MCT SPACE AVAILABLE 

Description: Contact your site administrator. The host services module for the 


1008 HOSTSRV REPEATED ABORT INDICATION RECEIVED 

Description: Contact your site administrator. The host services module for the 


1009 HOSTSRV INVALID LOCAL PORT 

Description: The message received from the LLP had a MEMBER FOUND invalid 

local passive open port number. (The valid local passive open port numbers are: 20, 

21, 23, 25, 256, 257, 258, or 275–299.) The host services module for the TCP–IP Stack 


3–62 7436 0728–303

1010 HOSTSRV OUTPUT HIC ANALYSIS ERROR 


Description: The header received had an invalid HIC sequence. An error message is 

created and sent to the ULP. The host services module for the TCP–IP Stack program 


1011 HOSTSRV ERROR CODE FROM INCOMING MESSAGE 

Description: A message was received from the LLP with the message type of 

ERROR. The host services module for the TCP–IP Stack program product generates 

this CENLOG. 

1012 HOSTSRV NO SOURCE IP ADDRESS CONFIGURED 

Description: The TSID/PROCID combination was not found in the source address 

table; the search is done to obtain the source IP address. (The source address table is 

built from the HOSTID entries on the EU card.) This error causes the current session 

to terminate. The host services module for the TCP–IP Stack program product 


1021 HOSTSRV UNEXPECTED DCA INPUT 

Description: A DCA control message was received that was not correct at this point 

of the processing sequence. The following information should be recorded and given 

to the site analyst: 

R12: Return address — contents of R7 before CENLOG call 


CENLOG. 

1022 HOSTSRV NO DCA$ ENTRY AVAILABLE 

Description: A new connection table entry could not be created either because the 

maximum number of TCP connections was reached or no segments were available for 

connection tables. The maximum number of TCP connections is a configurable value 

(TCPP). This condition is usually temporary. This error causes the current session to 

terminate. The host services module for the TCP–IP Stack program product generates 

this CENLOG. 

1023 HOSTSRV BAD DCA CC PACKET 

Description: A bad DCA connect confirm message was received. The host services 

module for the TCP–IP Stack program product generates this CENLOG. 

7436 0728–303 3–63


1024 HOSTSRV DCA UDM RECEIVED 

Description: A DCA UDM message was received. The host services module for the 


1025 HOSTSRV BAD CONNECTION ID FROM LLP 

Description: A message was received from the LLP with an SVS connection ID of 

zero. The host services module for the TCP–IP Stack program product generates this 

CENLOG. 

1026 HOSTSRV BAD DCA CI/CR POCKET 

Description: An error was detected when processing a DCA connect indication or 

connect request message (from DTPX). The host services module for the TCP–IP 


1027 HOSTSRV INTERNAL SOFTWARE ERROR 



Action: If this condition persists, contact your support center.An error was detected 

when processing a DCA connect indication or connect request message (from DTPX). 


CENLOG. 

1028 HOSTSRV INVALID DCA MSG 

Description: A DCA message had an invalid HIC sequence. The host services 

module for the TCP–IP Stack program product generates this CENLOG. 

1029 HOSTSRV CONFIG MISSING IPADR & SUBNET 

Description: TCP–IP Stack detected a configuration error. Expected IPADR or 

SUBNET statements were not found. Some configured functions may not be 

available. The TCP–IP Stack program product generates this CENLOG. 

Action: Verify that all needed IPADR and SUBNET statements are specified. 

1030 HOSTSRV DCA$ ENTRY IN ERROR 




3–64 7436 0728–303

2000 TELNET UNIDENTIFIED ERROR 





2001 TELNET NO DTPX HDR SENT ON FIRST DT:DDNP 





2002 TELNET CN76 RECEIVED – INVALID 

Description: An invalid message was received by TELNET. The TCP–IP Stack 


2003 TELNET CMD SVS I/F PKT SZ INCR TO 2 GRAN 

Description: The command services interface packet was increased in size by 

another granule. The TCP–IP Stack program product generates this CENLOG. 

2004 TELNET INVALID CONN TYPE FOR USER I/F CMD 

Description: An illegal condition occurred while processing a connection request 

(%%CONNECT ...). The TCP–IP Stack program product generates this CENLOG. 

2005 TELNET INVALID PORT SPECIFIED IN DTPX 





2006 TELNET SESSION NAME ILLEGAL THIS RELEASE 





7436 0728–303 3–65


2007 TELNET NO ULP ID GIVEN 

Description: A message was received from the LLP that did not specify a ULP 

connection ID. The TCP–IP Stack program product generates this CENLOG. 

2008 TELNET INVALID ULP ID GIVEN 

Description: A message was received from the LLP that specified an invalid ULP 


2009 TELNET INVALID LLP ID GIVEN 

Description: A message was received from the ULP that specified an invalid LLP 


2010 TELNET NO CONN TABLE EXISTS 

Description: A message was received that specified a nonexistent connection entry. 


2011 TELNET BAD PKT RECEIVED 

Description: An error was detected within the interface packet. The TCP–IP Stack 


2012 TELNET INVALID QUEUE ID RECEIVED 

Description: A message was received from a protocol module that is currently not 

supported by the TELNET module. The TCP–IP Stack program product generates this 

CENLOG. 

2013 TELNET BAD PACKET RETURNED 





2014 TELNET INVALID CONN ATTEMPT 

Description: Software error (warning). The data-link control manager service 

module that maintains the interfaces to the link providers generates this CENLOG. A 

host program (USER) did not supply a %%CONNECT command as the first data 

transfer to the DDN Gateway. The TELNET module generates this CENLOG. 

3–66 7436 0728–303

2015 TELNET DUPLICATE CONN ATTEMPT 






2016 TELNET MSG TYPE NOT IN PROGRAM TBL 

Description: Invalid message type received. The TCP–IP Stack program product 


2017 TELNET NO TABLE ENTRY FOR ATTACH 





2018 TELNET QCT INDEX INVALID FOR ATTACH 





2019 TELNET UNAUTHORIZED CALLER FOR ATTACH 





2020 TELNET ATTCH RECEIVED - INVALID 





7436 0728–303 3–67


2021 TELNET NSP NAME CONV W/O AO PENDING 

Description: A response was received from the name server protocol module, but a 

request was not sent. The TELNET module generates this CENLOG. 

2022 TELNET INVALID ERROR CODE ENCOUNTERED 





2023 TELNET DDNG ERROR CODE FROM ULP 

Description: An error code, destined for a host user, was received from an upper 

layer protocol. The TELNET module generates this CENLOG. 

2024 TELNET NO DTPX HDR ON 1ST DT (DDNP) 

Description: The first data transfer for a user pass-through connection did not 

contain a DTPX (connection establishment) header. The message was processed, but 

the connection is likely to fail. The TELNET module generates this CENLOG. 

2025 TELNET ERROR IN QUEUING ROUTINE 

Description: Insufficient resources for session support. The TELNET module 


2026 TELNET MSG DEQUEUED 

Description: Informational only message. The TCP–IP Stack program product 


Action: None. 

2027 TELNET MSG QUEUED 

Description: Informational only message. The TCP–IP Stack program product 


Action: None. 

3–68 7436 0728–303

2028 TELNET MISC ERROR IN TELNET VALIDATION 


Description: An error was detected while processing the message. The following 

information should be recorded and given to the site analyst: 

R13: Current connection states — inbound (upper 4 bits)/outbound (next 4 

bits)/(next 8 bits unused). Connection state codes found in TELNET. 

R14: PK$MTYPE/PK$ERROR — message type (8 bits)/error code (8 bits) from 

current message packet. Message types and error codes found in 

AADDNDEF. 

R15: Error code. Error codes found in AADDNDEF. 

The TELNET module generates this CENLOG. 

2200 TELNET INV FUNCTION CODE 

Description: An invalid parameter was passed to the protocol manager routine. The 

TELNET module generates this CENLOG. 

2201 TELNET UNSPEC ERROR: PMA PMAXEU10 





2202 TELNET INTERNAL PROT MGR ERROR 

Description: The presentation services routine rejected the calling parameters set up 

by the protocol manager routine. The TELNET module generates this CENLOG. 

2203 TELNET INV COMMAND : PMC 





2400 TELNET CASE LIMIT ERROR: CMS_SVS 

Description: An internal error was detected in the command services routine. The 


7436 0728–303 3–69


2401 TELNET INVALID STATE TABLE VALUE 

Description: An internal error was detected in the command services routine. The 


2500 TELNET INV FUNCTION CODE PRES_SVS 

Description: An invalid parameter was passed to the presentation services routine. 


2501 TELNET INV CONNECT. TYPE: PRES_SVS 

Description: An invalid parameter was passed to the presentation services routine. 


2700 TELNET MAX MSG SIZE EXCEEDED 

Description: Protocol transmission resulted in a message buffer size greater than 

allowed. The TELNET module generates this CENLOG. 

2701 TELNET PUTCHAR – MAX BFR SZ : CHAR BYPASSED 

Description: An out-of-bounds condition was detected in the CHAR BYPASSED 

PUTCHAR routine. No buffer space was available to add the character. The current 

character was bypassed. The TELNET module generates this CENLOG. 

2702 TELNET ADRSIMSG – MSG NOT IN PROGRAM TBL 

Description: An invalid message type parameter was passed. The TELNET module 


2703 TELNET PPUTHOLD NO QLx AVAILABLE 

Description: Insufficient resources for session. The TELNET module generates this 

CENLOG. 

2704 TELNET NO CONN TBL RESOURCES 

Description: No segments were available to create a new connection table entry. 


3–70 7436 0728–303

2705 TELNET DSSN ERROR IN CONN TEL SEG INIT 


Description: TCP–IP Stack detected a system error. This condition is normally 



2706 TELNET INV PTR IN FREE ENTRY ROUTINE 


CENLOG. 

2707 TELNET INV PST IN FREE ENTRY ROUTINE 

Description: An invalid return code was returned from the ROUTINE SUDPST 

supervisor routine. The TCP–IP Stack program product generates this CENLOG. 

2708 TELNET INTERNAL TABLE HANDLING 

Description: The PST in use bit mask table was corrupted. The TCP–IP Stack 


2709 TELNET INV ADDR IN CND MSG RTN 

Description: An invalid parameter was passed to the canned message routine. The 


2710 TELNET INVALID PROTOCOL ID 





2711 TELNET INVALID FUNCTION CODE 





7436 0728–303 3–71


2712 TELNET RECOVERY FAILED 




2713 TELNET QUEUE PRIMARY MSG RECOVERY 

Description: This message is informational only. The TCP–IP Stack program 


Action: None. 

2714 TELNET QUEUE ALT. MSG. RECOVERY 



Action: None. 

2715 TELNET GET QUEUE ITEM RECOVERY 



Action: None. 

2716 TELNET Q. NOT IN PROT-ID TBL: GET Q 





2717 TELNET QUEUE FULL 




3–72 7436 0728–303

Event 13 P1X24 HIGH PRIORITY EVENT 

Event 13 P1X24 HIGH PRIORITY EVENT 


7436 0728–303 3–73

Event 14 TNAS END USER EVENT 

Event 14 TNAS END USER EVENT 


3–74 7436 0728–303

Event 15 SNA GATEWAY EVENT LOG 


Event 15 SNA GATEWAY EVENT LOG 

7436 0728–303 3–75

Event 16 CENLOG Messages 


Supplementary Messages for Class 03, Event 16 

LAN: 1 - SET STATION FAILED 

Description: The LAN LM could not be initialized on the LAN. Either there is a 

previous station already on the LAN with the same station address that was specified 

in the LINE statement for this LM, or the LAN LM is not correctly attached physically 

to the LAN. The 802.3 LM Handler component of the ENS program product generates 

this CENLOG. 

LAN: 2 - LANMCA CFACCS ERROR 

Description: Error while accessing configuration. Software error. The 802.3 LM 

Handler component of the ENS program product generates this CENLOG. 

LAN: 3 - INVALID LINE TERMINATION 

Description: The LAN LM line was incorrectly terminated. Software error. The 

802.3 LM Handler component of the ENS program product generates this CENLOG. 

LAN: 4 - PP PROGRAM STOP 

Description: The ENS PP program failed. Software error. The 802.3 LM Handler 

component of the ENS program product generates this CENLOG. 

LAN: 5 - PP START FAILED 

Description: An ENS PP program was unable to be started. Software or hardware 

failure. The 802.3 LM Handler component of the ENS program product generates this 

CENLOG. 

LAN: 6 - INVALID CONTROL MESSAGE 

Description: An unexpected control message was received by the ENS program 

product. Software error. The 802.3 LM Handler component of the ENS program 


LAN: 7 - INVALID CONTROL MESSAGE 

Description: An unexpected control message was received by the ENS program 

product. Software error. The 802.3 LM Handler component of the ENS program 


3–76 7436 0728–303

LAN: 8 - INVALID AID 


Description: A message to the ILM was rejected because of an invalid ILM AID. 

Software error. The 802.3 LM Handler component of the ENS program product 


LAN: 9 - ATTACH FAILED 

Description: An attach request to the line module was returned in error. This is 

likely an invalid configuration parameter. The 802.3 LM Handler component of the 

ENS program product generates this CENLOG. 

LAN: 10 - DETACH FAILED 

Description: A detach request to the line module was returned in error. Software 

error. The 802.3 LM Handler component of the ENS program product generates this 

CENLOG. 

LAN: 11 - INVALID CALL 

Description: Indicates that the program was called with an invalid value. Software 


CENLOG. 

LAN: 12 - ATTACH REQUEST PPID INVALID 

Description: An attach request message was received from a user program with a 

PPID that was invalid for any LAN LMs. Software error. The 802.3 LM Handler 

component of the ENS program product generates this CENLOG. 

LAN: 13 - INVALID CMD HIC FROM NMS 

Description: An unexpected message was received from NMS. Software error. The 


LAN: 14 - INVALID FAC HIC FROM NMS 

Description: An unexpected message was received from NMS. Software error. The 


LAN: 15 - LINE CFACCS ERROR 



7436 0728–303 3–77


LAN: 16 - TOO MANY ATTACHES 

Description: A request for an attachment was received when the maximum number 

of attaches were already active. Probably too many SAP statements configured for 

the same LAN LM. The 802.3 LM Handler component of the ENS program product 


LAN: 17 - SAP CFACCS ERROR 



LAN: 18 - INVALID OUTPUT QUEUE 

Description: An output queue specified for an attachment was not valid. Software 


CENLOG. 

LAN: 19 - HLE CFACCS ERROR 



LAN: 20 - INVALID INPUT QUEUE 

Description: The input queue specified for an attachment was invalid. Software 


CENLOG. 

LAN: 21 - INVALID CMD FROM MAU 

Description: An unexpected message was received from the MAU. Software error. 

The 802.3 LM Handler component of the ENS program product generates this 

CENLOG. 

LAN: 22 - PP IS RESTARTED 

Description: The PP program stopped running, but was able to restart. The 802.3 LM 


LAN: 23 - NO USER TABLE 

Description: An error occurred while accessing the user table. Software error. The 


3–78 7436 0728–303

LAN: 24 - LINE INIT ERROR 


Description: An error occurred while trying to initialize the LAN line. Software 


CENLOG. 

LAN: 25 - LINE INIT FAIL - NO CONTIGUOUS MEMORY AVAILABLE 

Description: An error occurred while trying to initialize the LAN line because no 

contiguous memory was available. The 802.3 LM Handler component of the ENS 


LAN: 26 - UNABLE TO ADD QUEUE TO PP QUEUE LIST 

Description: An error occurred while trying to add a queue to the PP queue list. 



LAN: 27 - LINE INIT FAIL - UNABLE TO ADD IUT TO PST 

Description: An error occurred while trying to add the individual user table to the 

procedure segment table. Software error. The 802.3 LM Handler component of the 

ENS program product generates this CENLOG. 

LAN: 28 - INVALID MESSAGE 

Description: An unexpected message was received from the PP. Software error. 


CENLOG. 

LAN: 29 - INVALID IUTE ADDRESS 

Description: A message was returned from the PP, but an individual user table does 

not exist for that message. The 802.3 LM Handler component of the ENS program 


LAN: 30 - ATTACH CONFIRM 

Description: An attach request to the line module completed successfully. The 802.3 

LM Handler component of the ENS program product generates this CENLOG. 

LAN: 31 - DETACH INDICATION/CONFIRM 

Description: A detach indication or confirmation was received from the line module. 


CENLOG. 

7436 0728–303 3–79


LAN: 32 - UNABLE TO REMOVE QUEUE FROM PP QUEUE LIST 

Description: A queue was unable to be removed from the PP queue list. Software 


CENLOG. 

LAN: 33 - UNABLE TO RESTART PP 

Description: An error occurred while trying to restart the PP after a PP state item. 



LAN: 34 - UNABLE TO DOWN LINE 

Description: An error occurred while trying to restart the PP after a PP state item. 



LAN: 35 - UNABLE TO EXTEND IUT 

Description: An error occurred while trying to expand the individual user table. 



LAN: 36 - UNABLE TO ATTACH USER - HCB ENTRY NOT 

PRESENT/FOUND 

Description: The HLE entry could not be found. The 802.3 LM Handler component 

of the ENS program product generates this CENLOG. 

LAN: 37 - UNABLE TO ADD QUEUE TO QUEUE LIST 

Description: A queue could not be added to the queue list. Software error. The 


LAN: 38 - INVALID COMMAND FROM HLEMAN 

Description: ILMSVS received an unknown command from HLEMAN. Software 


CENLOG. 

3–80 7436 0728–303

LAN: 39 - HLE MESSAGE COULD NOT BE SENT 


Description: ILMSVS tried to queue a HLEMAN indication or confirmation message 

to the HLE. It could not because the queue number could not be found, or the queue 

could not be added to the ILMSVS queue list entry. Software error. The 802.3 LM 


LAN: 40 - DATA UDM 

Description: An output message was placed on the UDM queue, or thrown away if 

there is no UDM queue, because the line module could not send the message over the 

LAN. The 802.3 LM Handler component of the ENS program product generates this 

CENLOG. 

LAN: 41 - DUT TABLE IS FULL 

Description: The dynamic user table (DUT) has reached maximum size. If the line is 

down, only the HLE in the DUT will be notified when the line comes up. The 802.3 LM 


Action: You can fix this problem by using less dynamic attaches. Configure an attach 

(SAP) for each time this CENLOG occurs. 

LAN: 42 - ERROR CREATING THE DUT 

Description: An error occurred while trying to create a dynamic user table (DUT). 

Dynamic attaches do not work. The 802.3 LM Handler component of the ENS 


7436 0728–303 3–81


3–82 7436 0728–303

Section 4 


Event 1 *** X.21 MSG *** R14, R15 = PORT, ID 

R8: 4XXX=CPS# 5,6=ID MSG 

*** X.21 MSG *** R14, R15 = PORT, ID 

Action: None. 

7436 0728–303 4–1



There are no CENLOGs defined for events 2 through 11. 

4–2 7436 0728–303

Event 12 AX25 EVENT 

AX25 EVENT 

Program product. 

Event 12 AX25 EVENT 

7436 0728–303 4–3

Event 13 ALC GATEWAY EVENT 

Event 13 ALC GATEWAY EVENT 

ALC GATEWAY EVENT 


4–4 7436 0728–303

Event 14 P1X24 LOW PRIORITY EVENT 

P1X24 LOW PRIORITY EVENT 


Event 14 P1X24 LOW PRIORITY EVENT 

7436 0728–303 4–5

Event 15 LOW SPEED BAUDOT EVENT AIR/net LSB 

Event 15 LOW SPEED BAUDOT EVENT AIR/net LSB 

LOW SPEED BAUDOT EVENT AIR/net LSB 


4–6 7436 0728–303


TCPTS: CONNECT REQUEST RECEIVED 

TSAP=tipcsu TO IDENT=Application Name 

FROM IDENT=terminal ID IP ADDRESS=151.85.10.41 

R8-R15= 483D 5000 009A 0000 0010 02F7 0A4F 


Description: TCP–IP Stack is establishing communications with other equipment. 

This message is informational only. The TCP–IP Stack program product generates 

this CENLOG. 

Action: None. 


TELNET: ATTACH TO “XEU name” 

TERMINAL ID = “site” IP ADDRESS = “IPADR” 

Description: TCP–IP Stack is establishing communications with other equipment. 

This message is informational only. The TCP–IP Stack program product generates 

this CENLOG. 

Action: None. 

7436 0728–303 4–7


4–8 7436 0728–303

Section 5 


Errors and status information associated with the software and configuration process 

characterize Class 5 CENLOGs. 

Event 1 ‘CALL’ INTERFACE RETURNED ERROR 

(ABNORMAL) 

‘CALL’ INTERFACE RETURNED ERROR (ABNORMAL) 

Description: The CALL interface is the DCP internal programming way of one 

procedure giving control to another procedure to perform a particular task. The 

receipt of this CENLOG event signals that the status return to the first procedure was 

unacceptable, and corrective error recovery was initiated by the first procedure. 

Telcon generates this CENLOG. 

Action: If no apparent problem appears at an operational level, the corrective action 

by the CALLING procedure was probably successful and no further action is required. 

NMOPEN 

Description: NMOPEN is sending DTP a connect request/confirm/reject, and 

receives an error from EUSERV. 

R15: Reason code 


SNA: 260 - No session index available 

Description: This message occurs as a result of an internal software error. 

Action: Use the NMS DOWN/UP command on the PU. 

SNA: 1403 – EUSERV error return (type %%%%) 

Description: This message occurs as a result of errors in SNMS, the part of SNA/net 

that processes operator commands. The type is one of the DTPX and EUSERV error 

types and % represents a hexadecimal number. The probable cause is a software 

problem. 

7436 0728–303 5–1

Event 2 UNABLE TO RESTART PORT PROCESSOR 

Event 2 UNABLE TO RESTART PORT PROCESSOR 

UNABLE TO RESTART PORT PROCESSOR 

Description: The PORT PROCESSOR refers to one of the communication lines 

connected to the DCP. Refer to the port number associated with the CENLOG to 

isolate the inoperative line. The controlling CP procedure responsible for processing 

(due to an original error) caused the port to stop and caused the CENLOG. The 

original problem is visible through some other CENLOG display. Telcon generates 

this CENLOG. 

Action: Currently the port is not running. One action would be to DOWN and then 

UP the affected port using the appropriate NMS commands. If still not successful, 

notify someone knowledgeable about this communication line (problem may be 

hardware or software related). 

AGPPER 

Description: AGPPER was unable to restart the PP because of an error reported by 

LMLOAD. 

R8: Error bits returned from LMLOAD 

R9: IOPID 

R10: IOP table index 

R12: Microcode ID 

R13: Line module ID 


5–2 7436 0728–303

Event 3 CP QUEUE FULL CONDITION 

CP QUEUE FULL CONDITION 


Description: QUEUES are lists that contain system and user messages. The Telcon 

program procedure generating this CENLOG message has attempted to add a message 

to one of these lists (queues) and cannot because the list is full. The procedure 

attempts some corrective action which may, as a last resort, include throwing away 

the current message. Subsequent CENLOGs should provide additional information as 

to the cause of this CENLOG event. Telcon generates this CENLOG. 

Action: If the system appears to be operational, no action is necessary. However, if 

the system appears to be hung, take a system dump and present it to Unisys with a 

UCF or other appropriate procedural steps, as outlined by your Unisys representative. 

DUC 

Description: The link area is full. Telcon generates this CENLOG. 

LINK AREA FULL 

Description: Queue or link area is full. Appropriate recovery actions are attempted 

(which may include discarding the message). Telcon generates this CENLOG. 

Action: Refer to the CP QUEUE FULL CONDITION description for appropriate 

action to take. 

LMS 

Description: LMS unsuccessfully attempted to queue an item to its internal interface 

queue or internal hold queue. Telcon generates this CENLOG. 

NTRLPH 

Description: This event occurs if NTRLPH attempts to queue a message to the PP 

output queue (size = 62), but cannot because the queue is full. If this occurs, the 

entire NTRLPH process waits until it can queue the message, thus slowing down all 

other NTR sites. If this event happens, submit a UCF. This error is recoverable, but 

degrades system performance in the NTR area any time it occurs. Other information 

is logged in the registers, but is applicable only to debug. Telcon generates this 

CENLOG. 

7436 0728–303 5–3


RMLPH 

Description: The design of RMLPH makes the overflow of the queues from RMLPH 

to RMIOP impossible. 

R9: I/O state 

R10: Message address 

R11: LCB address 

R12: TCB address 

R14: PP ID 


SNA: 810 – msg not sent to tg; psa, pea, yea = %%%% %%%% 

%%%% 

Description: This message occurs as a result of errors in Path Control (ERVR), the 

network routing portion of SNA/net. The psa refers to partner subarea, pea refers to 

partner element address, yea refers to your element address, and % represents a 

hexadecimal number. The probable cause is a software problem. 

SNA: 1800 – Pascal Send Failed 

SRC 

SRC 

TAF 


that processes operator commands. The probable cause is a software problem. 

Description: SRC has received a TS down message from HCC through CENLOG. 

The TSID is saved on a dynamic queue so that a pause can be effected to allow the 

alternate DCP to send a host status command. The dynamic queue has overflowed. 

The message is discarded and no resilient switch is affected. Telcon generates this 

CENLOG. 

Description: SRC is attempting to send a message to the console in response to an 

NMS command. The NMS queue is full and the dynamic save queue is full. The 

response is discarded. Telcon generates this CENLOG. 

Description: A queue to which a caller must send an item is full, mandating a timed 

suspension. Telcon generates this CENLOG. 

5–4 7436 0728–303

TSM 


Description: TSM received input with no session or input on a secondary session 

from CSUAFI. TSM turns around and queues this input buffer to itself, but the queue 

instruction is not successful. The input buffer is discarded. Telcon generates this 

CENLOG. 

TSTN 

Description: Message received from Telcon interface modules are queued up waiting 

for an RR from the external TS. The queue is full. Telcon generates this CENLOG. 

TTYLP 

Description: This event occurs if TTYLP tries to requeue an output message to the 

front of the TCB queue, but it cannot, because the queue is full. Because the TCB 

queue is currently an MCT LIST type queue, occurrence of this event is extremely 

unlikely. If it does occur, the message TTYLP is attempting to requeue is discarded. 

Other information logged: 

R14: TTYLPH Q-list index of the TCB queue that is full 


7436 0728–303 5–5

Event 4 QUEUE ITEM UNAVAILABLE / ACCESS ERROR 

Event 4 QUEUE ITEM UNAVAILABLE / ACCESS 

ERROR 

QUEUE ITEM UNAVAILABLE / ACCESS ERROR 

Description: Queue item or link area item not available as expected. Telcon 


Action: None. 

PDN Trunk is not initialized 

Description: The DCP-to-DCP module (PDNTRK) was unable to successfully obtain 

a queued item from its queue. The item was either a primitive across the Layer 3/4 

Platform interface or some other item type. This could be a software error that has 

caused the PDNTRK module to become invoked from a CALL reference instead of a 

queued item. 

Attributes affected: Supplementary text message, configuration event. The X.25 

PSCS program product generates this CENLOG. Procedure: PDNTRK. 

SNA: 814 – (rh10 = %%%% %%%% %%%% %%%% %%%%) 

Description: This message occurs as a result of errors in ERVR, the network routing 

portion on SNA/net. The % represents a hexadecimal number. The probable cause is 

a software problem. 

SNA: 2014 – Pascal send of fdbsc traced message failed 

Description: This message occurs as a result of errors in establishing sessions 

between OS 2200 hosts and BSC terminals that are connected to an IBM ® 

network. 

The probable cause is a software problem. 

5–6 7436 0728–303

Event 5 DYNAMIC SYSTEM SEGMENT ERROR 


RMLPH 

Description: 15: Invalid call code. Telcon generates this CENLOG. 

PDN Trunk is not configured 

Description: The DCP-to-DCP module (PDNTRK) was unable to successfully 

process a primitive across the Layer 3/4 Platform interface or some other item 

received on its queue. he reason is because the PDNTRK initialization segment is not 

present. 


PSCS program product generates this CENLOG. 

Action: Review the X.25 PSCS’s configuration statements. If any DTE statements 

have DTETYPE statements whose Level 4 equals PDNTRUNK, then verify that the 

DTE statement references a valid TRUNK statement on its TRUNK parameter. Check 

to see if the X25ROUTE statement is inadvertently routing call packets to the 

PDNTRK module. Procedure: PDNTRK. 

SNA: 1036 – Pub/Lub segment creation error 

Description: This message occurs as a result of errors or events in terminals 

attached to SNA/net. The probable cause is a software problem. 

SNA: 1404 - Could not extend system segment 



SNA: 1405 – Maximum SCB segments created (err %%%%) 


that processes operator commands, where % represents a hexadecimal number. The 

probable cause is a software problem. 

SNA: 1406 – Could not extend system segment (err %%%%) 


that processes operator commands. The % represents a hexadecimal number. The 


7436 0728–303 5–7


SNA: 1407 – Could not enter segment into PST (err %%%%) 

SRC 




Description: SRC has encountered an invalid DSSN in AZ$LCKB while attempting to 

activate/deactivate a line during a resilient switch. Telcon generates this CENLOG. 

SYSTEM SEGMENT ERROR 

TRS 

Description: Various internal processes allocate space dynamically at runtime to 

contain various runtime tables. If an error is detected during the creation/usage of 

these segments, the calling procedure registers this statistic log entry. Telcon 


Action: Submit a UCF. 

Description: When TRS deallocates resources for the last terminal on a line, it calls 

the supervisor to delete the DSSN segment. If the use count is nonzero, it returns a 

status, indicating that the DSSN has not been deleted. TRS logs the error and gives up 

control. If this occurs, a process has most likely not cleared the PST entry. 

R11: LCB 


TSTN 

Description: At TS/TN initialization, the DSSN number is loaded and an invalid DSSN 

number is specified by this CENLOG. Telcon generates this CENLOG. 

5–8 7436 0728–303

X.25: No Resources 


Description: The layer 3 module (PDNL3) received an incoming call packet from the 

network or from a directly attached DTE. PDNL3 was unable to successfully process 

the call packet because a virtual circuit connection table (ZV$) entry could not be 

allocated. A clear packet was returned to the network/DTE. 

R11: Clear packet’s diagnostic code. See Appendix A of this manual for a 

description of the codes. 

Attributes affected: Supplementary text message. The X.25 PSCS program product 

generates this CENLOG. Procedure: PDNL3. 

Action: No action is necessary. However, repeated occurrences of this event may 

indicate an out-or-memory condition; submit a UCF along with a Telcon dump. 

X.25 SNMP: Received input from unknown/unexpected Queue 

("procedure name") 

Description: The X.25 PSCS SNMP interface module (PDNSMP) received a queued 

item on an unknown queue or a queue that was not expected for the current state of 

PDNSMP. This may adversely affect the operation of PDNSMP. 

R8: Address of queue on which item was received 

Attributes affected: Error event, supplementary text message. 

Action: This event indicates an internal software interface error. You must re-start 

your Telcon run if you notice that PDNSMP is not operating properly. If the error reoccurs, 

take a Telcon dump and submit a UCF. Procedure: The procedure name, 

which is internal to the X.25 PSCS PDNSMP module, is displayed as part of the 

supplementary text message. 

X.25 SNMP: ICS queue data error ("procedure name") 

Description: The X.25 PSCS SNMP interface module (PDNSMP) was unable to send 

a data message. The message was to the SNMP Agent’s manager-agent user interface. 

This adversely affects the ability of X.25-related MIB information from being retrieved 

by the SNMP management workstation. It may be a temporary condition. 

Attributes affected: Recoverable error event, supplementary text message. 

Action: PDNSMP automatically recovers from this event. If the error re-occurs, take 

a Telcon dump and submit a UCF. Procedure: The procedure name, which is internal 

to the X.25 PSCS PDNSMP module, is displayed as part of the supplementary text 

message. 

7436 0728–303 5–9


X.25 SNMP: General queue error ("procedure name") 

Description: The X.25 PSCS SNMP interface module (PDNSMP) was unable to send 

a message to a Telcon services interface. This error may cause PDNSMP to become 

dormant. In this case, no SNMP MIB information related to X.25 can be retrieved. 

Attributes affected: Error event, supplementary text message. 

Action: This event indicates an internal software interface error. You must re-start 

your Telcon run in order to recover from this error. If the error re-occurs, take a 

Telcon dump and submit a UCF. Procedure: This procedure name, which is internal 


message. 

X.25 UTS4000: No Resources 

Description: The X.25 PSCS UTS 4000 Cluster Controller interface module (PDNL4) 

received an incoming call. PDNL4 was unable to successfully process the call 

because a logical channel index table (ZL$) could not be allocated for the new virtual 

circuit. A clear packet was returned in response to the incoming call. 

R8: The nth minus 1 PDNGRP configuration statement that is associated with the 

line where the incoming call was received. 

R9: The logical channel number used by the incoming call packet. 

R11: The diagnostic code used in the returned clear packet. 

Attributes affected: Recoverable error. Supplementary text message. 

Procedure: PDNL4. 

Action: No action is necessary. However, repeated occurrences of this event may 

indicate an out-of-memory condition; take a Telcon dump and submit a UCF. 

5–10 7436 0728–303

Event 6 INVALID COMMAND / CONTROL / HIC RECEIVED 

Event 6 INVALID COMMAND / CONTROL / HIC 

RECEIVED 

BVINPUT 

Description: A $$COMMAND statement was discarded, usually because the 

command had no meaning at this point. For example, a $$RESUME statement was 

encountered, but there was no file to resume. 

R8: Value of R2 — Byte offset where error was detected 

R10: Address of output buffer 

R11: Address of LCB 

R12: Address of TCB 

R13: 03 


BVOUTPUT 

Description: Probable HIC format error. Possible error in length. Possible 

unrecognizable HIC type. Possible erroneous parameter within the HIC. 

R8: Previous contents of R0 





R13: Error code used by software development to determine the relative location 

within the program where the error was encountered. 

R13: 03–06,OP,013,–16–018,01A,01B,01D,023,027,029–02B,02F,035,036 

R14: Error code denoting the type of error encountered. 


CENLCOM 

Description: CENLCOM received an invalid command HIC. Telcon generates this 

CENLOG. 

7436 0728–303 5–11


DMOPEN 

DTP 

Description: When an ATTACH request is rejected by DMOPEN, an ATTACH reject 

is generated and returned to DTPX. DMOPEN sends the reject request to DTPX using 

a call to CSUAFI, which requires data on CSU class and CSU ID. This code is used 

when DMOPEN fails to find a valid CSU class or CSU and the ATTACH request is 

thrown away. 

R8: CSU ID 

R9: CSU ID 

R10: ATTACH request buffer address 


Description: DTP has received an unrecognizable control message. One of the 

following conditions has occurred: The byte count = 0. The control message 

identification HIC (first HIC) is not valid (is not recognized by DTP). A flow control 

HIC (X'03') has been received from the transport service user, but the variant is 

neither “start” nor “stop.” Telcon generates this CENLOG. 

DTVTR 

Description: The DCT 1000 VTR received an HIC that is unrecognizable and invalid. 


R14: PPID 

R15: RID/SID 


INVALID COMMAND / CONTROL/ HIC RECEIVED 

Description: This message indicates that a procedure received a control message 

that contains invalid data. Telcon generates this CENLOG. 


5–12 7436 0728–303

IPC 


Description: IPC has received an unrecognizable HIC in either the AC-1 or IT-1 

header. 

R8: AC-1 HIC 

R9: AC-1 HIC variant 

R11: IT-1 HIC 


MVTR 

Description: RB2 syntax or protocol error detected by REM1 VTR. 

R9: Stack pointer 

R10: Source message buffer header 

R11: Source message byte pointer 


R13: Current return address 

R14: Invalid HIC or parameter 

R15: Invalid HIC variant or parameter length 


NTRLPH 

Description: This event occurs if NTRLPH receives an unrecognizable HIC from 

NTRIOP in the communication BCW (# 15) of the MCT, or in a message from 

somewhere else in the Telcon system. If this event occurs, the MCT and message are 

discarded. A supplemental message distinguishes whether it was from the PP or from 

the rest of the system. Telcon generates this CENLOG. 

7436 0728–303 5–13


PDNL4(X.25) RECEIVED INVALID TCR NUMBER–MESSAGE 

DISCARDED 

Description: The UTS 4000 Cluster (PDNL4) module received a data packet from the 

network containing an invalid TCR number in the transport protocol header. A 

software error has caused either PDNL4 to send an invalid TCR number to the UTS 

4000 Cluster, or the UTS 4000 Cluster has corrupted the TCR number. 

R9: Identifies the line and logical channel number on which the message was 

received. The value contained in the upper 4 bits is the nth minus 1 PDNGRP 

statement specified in the configuration. The message was received on the 

line associated with this PDNGRP statement. The value contained in the 

lower 12 bits is the logical channel number. 

Attributes affected: Supplementary text message, error event. The X.25 PSCS 

program product generates this CENLOG. Procedure: PDNL44. 

PDNTRK: Received out-of-range primitive value 



received on its queue. The reason is because the function value in the primitive is 

outside of the range expected by PDNTRK. The unknown primitive/queued item is 

discarded. 

Attributes affected: Supplementary text message, error event. The X.25 PSCS 

program product generates this CENLOG. Procedure: PDNTRK. 

PDN Trunk is not initialized 



received on its queue. The reason is because the PDNTRK module has not been 

initialized. Either no statements have been configured for the PDNTRK module or a 

software error has prevented PDNTRK from receiving the initialization notification. 



Action: Review the X.25 PSCS configuration statements. If any DTE statements have 

DTETYPE statements whose Level 4 equals PDNTRUNK, then verify that the DTE 

statement references a valid TRUNK statement on its TRUNK parameter. Check if the 

X25ROUTE statement is inadvertently routing call packets to the PDNTRK module. 

Procedure: PDNTRK. 

SMRP 

Description: Error returned from a call to AGBYTLD/AGBYTST. Input is discarded. 


5–14 7436 0728–303


SNA: 614 – LU–LU Session status in ERROR 



2200 hosts. The probable cause is a configuration and/or software problem. 

SNA: 645 – No session active for this message transfer 



2200 hosts. It is informational only. 

SNA: 646 – Unexpected SNA Response received 



2200 hosts. The probable cause is a software problem. 

SNA: 647 – Oversized Request Unit received 




SNA: 651 – Invalid / duplicate SON literal (%%%% %%%%) 





SNA: 663 - SESS=&&&&-&&&&/&&&&, RQ Code=%%%% 

Unexpected 



2200 hosts. The & represents a decimal number and % represents a hexadecimal 

number. The probable cause is a software problem. 

SNA: 664 – Extended BIND RSP received - Protocol violation 



2200 hosts. The probable cause is a configuration problem. 

7436 0728–303 5–15


SNA: 666 – XAB not initialized - Message received 




SNA: 674 – Invalid data assurance response (XABCSCVT) 




SNA: 675 – Invalid RB-2 protocol 




SNA: 1001 – Invalid Link handler type %%%% , discard 


attached to SNA/net. The % represents a hexadecimal number. The probable cause is 


SNA: 1002 – Invalid Link handler control message = &&&& 


attached to SNA/net. The & represents a decimal number. The probable cause is a 


SNA: 1401 – Bad DTPX control msg received (type %%%%) 




SNA: 1402 – Invalid SNMS msg received (action %%%%) 



probable cause is a terminal operator error. 

SNA: 1803 – SNMS Parse Interface Packet Error 



5–16 7436 0728–303


SNA: 1806 – SNMS Display Interface Packet Error 



SNA: 1809 – SNMS Standby/OnLine Level Mismatch -- HALTING 

Description: This message occurs as a result of a mismatch between the levels of the 

online and standby systems. Ensure that the online and standby systems have the 

same level. 

SNA: 1812 – SNMS Reqms Interface Packet Error 



SNA: 1821 – SNMS Move – Interface packet error 



SNA: 2002 – Inv xab ru, yea= %%%%, rh= %% %% %%, ru= %% %% 

%% 


between OS 2200 hosts and BSC terminals that are connected to an IBM network. The 

ru is the request/response headers, yea is your element address, btu is a basic 

transmission unit, and % represents a hexadecimal number. The probable cause is a 


SNA: 2003 – Inv ervr btu, yea= %%%%, rh= %% %% %%, btu= %% 

%% 



btu is a basic transmission unit, yea is your element address, rh is the 

request/response header, and % represents a hexadecimal number. The probable 

cause is a software problem. 

SNA: 2008 – Inv req btu, st= %% %%, pea %%%% psa %%%%, 

btu= %% %% 



btu is a basic transmission unit, pea is partner element address, psa is partner 

subarea, and % represents a hexadecimal number. The probable cause is a software 

problem. 

7436 0728–303 5–17


SNA: 2009 – Inv rsp btu, st= %% %% pea %%%% psa %%%%, 

btu= %% %% 



btu is a basic transmission unit, pea is a partner element address, psa is a partner 

subarea, and % represents a hexadecimal number. The probable cause is a software 

problem. 

SNA: 2010 – Inv req ru, st= %% %%, yea= %%%%, ru= %% %% %% 



ru is a request/response unit, yea is your element address, and % represents a 


SNA: 2011 – Inv rsp ru, st= %% %%, yea= %%%%, ru= %% %% %% 



ru is a request/response unit, yea is your element address, and % represents a 


SNA: 2012 – Unkwn rsp status, st= %% %%, btu= %% %%, sta= %% 

%% 



btu is a basic transmission unit, and % represents a hexadecimal number. The 


SNA: 2207 – Invalid ru from ervr, psa = %%%%, ru = %%, 

state = %% 

Description: This message occurs as a result of errors in the trunk used to connect 

DCA traffic across an SNA network. The ru is a request/response unit, psa is a 

partner subarea, and % represents a hexadecimal number. The probable cause is a 


SNA: 2214 – Invalid control msg from DNS %% %% %% %% %% %% 

%% %% 


DCA traffic across an SNA network. The % represents a hexadecimal number. The 


5–18 7436 0728–303


SNA: 2215 – Vr msg, bad state (&&), rh= %% %% %%, ru= %% %% 

%% 

Description: This message occurs as a result of a response being received from the 

ERVR complex and the SNA trunk was not expecting it. The & represents a decimal 

number, the % represents a hexadecimal number. 

SNA: 2216 – Vr data received in bad state (&&) 

Description: This message occurs when a session control message is received from 

the ERVR complex while SNA trunk is not in the correct state. The & represents a 

decimal number. 

SNA: 2217 – Mparse err = %%%%, msg from vr, ru= %% %% %% 

Description: This message occurs in SNA trunk when a message received from the 

ERVR complex cannot be parsed correctly. The % represents a hexadecimal number 

identifying the “Mparse” error and the request unit that could not be successfully 

parsed. 

SNA: 2218 – Mparse err = %%%%, cinit from snass 

Description: This message occurs in SNA trunk when a CINIT is received from the 

SNASS complex and it could not be correctly parsed. The % represents a hexadecimal 

number identifying the “Mparse error.” 

SNA: 2219 – Mparse build @@@@@@@@, err = %%%% 

Description: This message occurs in SNA trunk when a message could not be built 

successfully by the parsing complex. The @ represents an ASCII character and the % 

represents a hexadecimal number. 

SNA: 2220 – Invalid snass msg, function code = %%%% 

Description: This message occurs in SNA trunk when an unknown message is 

received from the SNASS complex. The % represents a hexadecimal number and 

identifies the invalid message code. 

SNA: 2221 – No cb, snass msg, name = @@@@@@@@, fc = %%%% 

Description: This message occurs in SNA trunk when a message is received from the 

SNASS complex and no control block could be found using the name of the control 

block as the search key. The @ represents an ASCII character and the % represents a 

hexadecimal number. 

7436 0728–303 5–19


SNA: 2222 – No cb, snass msg, ea = %%%%, fc = %%%% 

Description: This message occurs in SNA trunk when a message is received from the 

SNASS complex and no control block could be found using the element address (EA) 

as the search key. The % represents a hexadecimal number. 

SNA: 2807 – Invalid ICS Function Rcvd 

Description: An ICS management message was received which contained an 

unknown function. May indicate an internal software error or a problem with the ICS 

run. 

SNMP 304 Received invalid message type xx from peer on port nn 

Description: The SNMP Agent reporting this event received a coordinating data 

message from another Agent using an ICS connection. The type of message was 

invalid either because the message was corrupted or a software error occurred. More 

than one SNMP Agent is loaded and configured within the same ICS domain. As each 

Agent initializes, it forms an ICS connection and passes coordination data messages 

with all other Agents so that all Agents can determine which one becomes active. 

Variables: 

xx The coordination message type received from another SNMP Agent 

nn The port of the SNMP Agent from which the coordination message was received 

Action: This event implies a possible memory corruption problem or a software 

error. Dump the ILM reporting this event in port nn. 

SNMP 401 Received unknown function type 

SRC 

Description: The sub-Agent received a message from the MIB manager containing an 

unknown MIB request type. The sub-Agent provides SNMP MIB information related to 

the SNMP itself. This includes system information and message statistics. The sub- 

Agent has a direct interface to the MIB manager; no ICS is involved. 

Action: This event implies a memory corruption or software problem. Dump the ILM 

or activate the ILM SNMP traces. 

Description: SRC has received an unrecognizable command from the alternate DCP. 

The message is discarded. Telcon generates this CENLOG. 

5–20 7436 0728–303

SRC 

TSM 

TSTN 

TSTN 


Description: SRC has received an unrecognizable control message on the 

EUSERV/DTP interface while managing the dynamic session to one of the alternate 

Telcon nodes. Telcon generates this CENLOG. 

Description: TSM received a control message that was missing a FROM IDENT in 

the packet. Telcon generates this CENLOG. 

Description: TSTN received an invalid HIC from other Telcon interface modules. 

The valid HICs are either UDM or UDM clear. The received HIC was neither. Telcon 


Description: Received a message from Telcon interface modules on the priority 

queue; the only valid HICs are RR/RNR. The received message was neither. Telcon 


TTYVTR 

Description: Invalid control HIC received. 



UDLCRS 

Description: R8: 0001. AE$UD601. (UDLC): NMS COMMAND/MESSAGE 

DISCARDED: HIC TRUNCATED. 

UDLC services was attempting to locate an HIC in an NMS message. The HIC was 

located, but the message buffer was too short to include all the HIC data. 


7436 0728–303 5–21


UDLCRS 

Description: R8: 0002. AE$UD600. (UDLC): NMS COMMAND/MESSAGE 

DISCARDED: HIC MISSING. 

UDLC services did not find a required HIC during the processing of a message from 

NMS. 

R9: The HIC being located in the message 


5–22 7436 0728–303

Event 7 QUEUE OR LINK AREA ERROR 

QUEUE OR LINK AREA ERROR 

IPC 


Description: Link area error — entry already in use. Telcon generates this CENLOG. 


Description: IPC could not obtain a message stored in its link area. The 

unobtainable message is either: (1) an activate request that was stored in the link area 

while establishing a transport connection or (2) a NITH (a part of a segmented 

message) that was stored in the link area while waiting for a LITH (the last part of a 

segmented message). Telcon generates this CENLOG. 

LMS 

Description: LMS unsuccessfully attempted to remove an item from its internal 

interface queue, or link/unlink an item from its link area. Telcon generates this 

CENLOG. 

REM1 LPH 

Description: The REM1 LPH attempts to link an output buffer when the link area is 

already in use. 

R8: TCB DSSN 

R9: LCB REM1 I/O flag word 

R10: PP ID 



R15: Normal dispatch call code 


SNA: 620 – Invalid XABDCASM queue item 




7436 0728–303 5–23


SNA: 621 – Invalid XABSNASM queue item 




SNA: 623 – Invalid NTNSC queue item Data Byte Offset 




SNA: 648 – CPEs for SCB Overflowed Limits 




SNA: 665 – Invalid link index = %%%%, Segmentation error 





SNA: 667 – Get Link Error (ERROR CODE = %%%%) 





SNA: 683 – Invalid Link Index = %%%%, Chaining Error 





SNA: 2622 – (PS) Cannot queue to application 

Description: This message indicates internal software exceptions. Useful for 

network analysts in determining status of environment. 

5–24 7436 0728–303

Event 8 QUEUE ACCESS / ADDITION ERROR 


QUEUE ACCESS / ADDITION ERROR 

Description: A procedure was not able to put a new message on a queue because the 

queue was already full. This event occurred partly because the procedure was not 

able to dynamically add a queue to the operational environment. Telcon generates 

this CENLOG. 

Action: No operator action is necessary. Program recovery paths were invoked 

automatically. 

NTRV2R 

Description: This event occurs if NTRV2R either cannot get an available Q-list index 

for an NTR site during sign-on processing, or if NTRV2R cannot delete a site’s console 

queue during sign-off processing. This error is fatal to NTRV2R, resulting in the 

procedure being blocked or in Telcon crashing. Other information is logged in the 

registers, but applicable to debug only. Telcon generates this CENLOG. 

RMVTR 

RTC 

Description: RMVTR detected an error in one of its queues. 





R13: Last subroutine call 

R14: Varies 

R15: Varies 


Description: A queue access violation occurred while the user was trying to register 

the priority trunk queues with route control. Telcon generates this CENLOG. 

SNA: 608 – Output queue selected by CQM (G,A) 




7436 0728–303 5–25


SNA: 679 – ‘CPA$AQL’ failed: Error code = %%%%, Queue Num = 

%%%% 

Description: This message occurs when the DCP/OS is unable to successfully add a 

que to the calling procedure’s queue list. The % represents a hexadecimal number. 

SNA: 1005 – Queue list manipulation error 

Description: This new boundary function (NBF) handles all of the management 

messages for 3270 connected devices, IBF connections to NCPs, and connections to 

NT 2.1 devices. The probable cause is a software problem. 

TSTN 

Description: SYSTSTRK or UDLC ask to put QCT indexes into TSTN’s queue list; 

however, TSTN’s queue list is full; not enough space reserved. Command disregarded; 

no queue added to queue list. Telcon generates this CENLOG. 

X.25: Memory Too Low For PDNTRK To Add Queues 

Description: The DCP-to-DCP module (PDNTRK) was unable to successfully expand 

its queue list in order to add DNS’s output queues. The reason is probably because of 

insufficient buffer space. The PDNTRK module pauses and attempts to expand its 

queue list again at three second intervals until successful. 

Attributes affected: Supplementary text message, recoverable error. The X.25 

PSCS program product generates this CENLOG. Procedure: PDNTRK. 

X.25: Up/Down Line Error in MLP Procedure 

Description: An error occurred in one of the following DCPOS service calls: 

CPA$AQL, CPA$DQUE, CPA$GQN, OR CPA$RQL. 

R8: The nth PDNGRP statement specified in the configuration 

R9: DCPOS error code 

R14: Port Processor Identifier (PPID) 

Attributes affected: line event, and configuration event. The X.25 PSCS program 

product generates this CENLOG. Procedure: PDNMLP. 

5–26 7436 0728–303

Event 9 INVALID RUN TIME TABLE ACCESS 


INVALID RUN TIME TABLE ACCESS 

BAD CENLOG HEADER: INVALID LENGTH (2 nd from R12) 

R8-R15= 80000 E000 C800 2EFB E010 0070 F000 0002 

DTP 

DTP 

IPC 

Description: A procedure detected an illegal or invalid reference to an operational 

table that may not exist. An example of this is the access of a terminal control block 

table that has been removed by normal sign-on/sign-off processing. These “timing 

windows” occur in large network operations. Telcon generates this CENLOG. 

Action: Depending on the frequency and the severity of the impact, submit a UCF 

with a system dump. 

Description: DTP is unable to load the TP$ (transport connection) table or the TN$ 

(network connection) table. R12 = TN$ table address (for example, X'B004') unless 

otherwise specified. Unable to load TP$ table: Input received with bad BH$ID1 and 

BH$ID2. The pace literal is invalid (R12 = 0). Unable to load TN$ table: Cannot find a 

suitable network connection (TN$) table for a CDATA (connectionless data) request. 


Description: The segment not loaded. The PST load (SUSPST) for the TN$ table 

failed (R12 = X'FFFF' or R12 = 4 ). The PST index is out of range for the TN$ table 

(R12 = 1). The TN$ entry number is out of range (R12 = 2). There is an insufficient 

number of slots for TN$ segments in DTP PST (R12 = 6). The analyst should check 

the configuration, especially for SESSN statements defined or defaulted by DTP. 


Description: An attempt was made to access an IPC context area that was not 

supporting any conversation. Telcon generates this CENLOG. 

LMS 

Description: LMS received an invalid DLU or MDL service access point across the 

LMS interface. Telcon generates this CENLOG. 

NO LCB TO INITIALIZE LINE STATISTICS TABLE 

Description: LCB is nonexistent, although it was requested by the LPH to count I/O 

statistics by way of the LOGSTAT procedure. An LPH could have passed an invalid 

PPID to the LOGSTAT procedure. Telcon generates this CENLOG. 

7436 0728–303 5–27


RCAS 

Description: RCAS could not locate the control table specified in a message. Telcon 


RFSYN 

Description: RFSYN could not locate the control table specified in a message. 


SNA: 1000 – Pub/Lub segment load error 



SNA: 2402 – MM search error, mmerr %%%% syserr %%%%, 

@@@@@@@@ 

Description: The new boundary function (NBF) handles all of the management 


NT 2.1 devices. The % represents a hexadecimal number and @ represents an ASCII 

character. The probable cause is a software problem. 

SNA: 2403 – MM chain error, mmerr %%%% syserr %%%%, 

@@@@@@@@ 



NT 2.1 devices. The % represents a hexadecimal number and @ represents an ASCII 

character. The probable cause is a software problem. 

SNA: 2425 – PUB tmr get err mmerr %%%% syserr %%%% id 

%%%% 



NT 2.1 devices. The % represents a hexadecimal number. The probable cause is a 


SNA: 2426 – LUB bmp chn err mmerr %%%% syserr %%%% id 

%%%% 





5–28 7436 0728–303

SNA: 2602 – PC delete dynamic queue error 




SNA: 2603 – SNAPATH appl eu init error 



SNA: 2617 – (PS) Invalid ACB 

Description: This message indicates internal software exceptions. Generally, a 

pointer value to the ACB has been lost/corrupted. Useful for network analysts in 

determining status of environment. 

SNA: 2618 – (PS) Invalid NRCB 

Description: This message indicates internal software exceptions. Generally, a 

pointer value to the NRCB has been lost/corrupted. Useful for network analysts in 

determining status of environment. 

SNA: 2621 – (PS) NRCB load failed 



SNA: 2805 – ICS Disconnect - Cannot Delete CCB 

Description: Internal software error in the SNA/net SNMP (Simple Network 

Management Protocol) Submanaged Program. Indicates that a connection control 

block could not be deleted when a disconnect was received from ICS. 

SNA: 2806 – ICS Disconnect - Connect CB Not Found 


Management Protocol) Submanaged Program. Indicates that no connection control 

block was found when a disconnect was received from ICS. 

7436 0728–303 5–29


SNMP 301 Duplication connection from peer on port nn 

Description: Reports a duplicate ICS connection attempt being made by another 

SNMP Agent loaded in port nn. The attempt is ignored by the Agent reporting this 

event. More than one SNMP Agent is loaded and configured within the ICS domain. 

As each Agent initializes, it forms an ICS connection with all other Agents so that all 

of the Agents can determine which one becomes active. 

Variable: nn is the port number of the SNMP Agent that initiated an ICS connection 

to the Agent reporting this event. 

Action: Normally, this is an error because only one ICS connection is formed 

between two SNMP Agents. Dump the ILM on port nn. If running in a dual-partition 

environment, this event can be reported when partitions are being switched. ICS is 

resynchronizing its connection to each Agent in the ILMs. This event should be 

ignored. 

SNMP 305 Received disconnect from unknown peer on port nn 

TRS 

Description: The SNMP Agent reporting this event received an ICS disconnect from 

another Agent in port nn, but this Agent has no run-time table entry for maintaining 

this ICS connection with the other Agent. More than one SNMP Agent is loaded and 

configured within the same ICS domain. As each Agent initializes, it forms an ICS 

connection and passes coordination data messages to all other Agents so that all of 

the Agents can determine which one becomes active. Once one of the Agents 

becomes active, all ICS connections are maintained and are not disconnected. This is 

done in order to determine if and when another Agent (whether active or not) 

becomes unloaded and thus unable to participate in any future coordination activities 

for determining which Agent becomes active. 

Variable: nn is the port of the SNMP Agent initiating the ICS disconnect. 

Action: This event implies a memory or software problem in the ILM port reporting 

this event, or an ICS problem. Dump the ILM reporting this event, unless other events 

are reported implying the ICS. 

Description: TRS attempted to allocate resources for a terminal. TRS rejects the 

request due to configuration, terminal already active, proxy terminal not signed on, no 

buffer space available, or operator error. 

R11: LCB 

R12: TCB 


5–30 7436 0728–303

TSM 


Description: When TSM receives a secondary session command, the user application 

specified in the command’s parameter table entry is not found in TSM’s list of defined 

applications. The secondary session command is not processed. Check TSM’s list of 

defined applications and the parameter table entry for the specified command. Telcon 


TSTN 

Description: Received a message from external TS through UDLC/HCC with an 

invalid TS ID#. Message discarded. Telcon generates this CENLOG. 

TTYLPH 

Description: This event occurs if TTYLPH can not get visibility to either the LCB or 

the TCB. If it does occur, the MCT/message (if any) that initiated processing is 

discarded. Other information is logged in the registers, but applicable to debug only. 


UDLCRS 

Description: R8: 0003. AE$UD030. (UDLC). BAD CONTROL MESSAGE PRDM IOP 

MP$FX INVALID. The contents of the MP$FX field in the MPA are invalid. The MPA 

is built by a port processor in an MCT. Telcon generates this CENLOG. 

UDLCRS 

Description: R8: 0004. AE$UD030: (UDLC). BAD CONTROL MESSAGE PRDM IOP 

MP$SE6 INVALID. 

The contents of the MCT parameter area (MPA) are invalid. The MP$ equates are 

defined in AAHARDEF. The MPA is built in an MCT by a port processor. 

R9: Contents of the MP$CF and MP$DF fields of the MPA 

R14: LINE-ID 


UDLCRS 

Description: R8: 0005. AE$UD620: (UDLC). CONFIG READ ERROR ON LINE 

TABLE FOR NMS COMMAND. The NMS message being processed by UDLC services 

contained the line facility HIC. An error occurred in attempting to read the line 

information table (LIT). The function requested by the NMS message was not 

performed. 


7436 0728–303 5–31


UDLCRS 

Description: R8: 0006. AE$UD032: (UDLC). BAD CONTROL MESSAGE FROM IOP: 

MP$GF/MP$DF INVALID. 

The contents of the MP$GF field or the MP$DF field of the MPA are invalid. The MPA 

is built by a port processor in an MCT. The function indicated by the MP$FX field is 

performed by the procedure identified by the MP$SEG field. Telcon generates this 

CENLOG. 

X.25 SNMP: Unable to load PDNSVS init. segment ("procedure 

name") 

Description: The X.25 PSCS SNMP interface module (PDNSMP) encountered an 

unexpected processing error. PDNSMP was unable to access a run-time table central 

to accessing X.25 MIB information. This adversely affects the ability of X.25-related 

MIB information from being retrieved by the SNMP management workstation. 

R8: Run-time address of the PDNSVS initialization segment 


Action: This event indicates an internal software interface error. You may have to 

re-start your Telcon run in order to recover from this error. If the error re-occurs, take 



message. 

5–32 7436 0728–303

Event 10 INVALID RUN TIME INDEX VALUE 


INVALID RUN TIME INDEX VALUE 

Description: Invalid runtime index value - bad control block IDs, and so on. Telcon 


Action: None. Internal statistic log entry. 

DTVTR 

IPC 

Description: The DCT 1000 VTR was sent an output canned message HIC with an 

invalid canned message number. 

R12: TCB Address. 

R15: RID/SID of terminal 


Description: An attempt was made to access a nonexistent IPC context area. Telcon 


LMS 

Description: LMS received an invalid function code across the LMS interface. The 

probable cause is a configuration error. Telcon generates this CENLOG. 

LPHTRS 

Description: TRS is unable to queue an attach (fixed session) to CSU (DTPX). The 

probable cause is a configuration error. Telcon generates this CENLOG. 

7436 0728–303 5–33


NTRLPH 

Description: This event occurs if one of the counts of active input devices, active 

output devices, or of all active devices is already zero, but should be decremented 

because of device termination processing. The device count in error is left at zero if 

this occurs, and the count is correct again when all devices of that type go inactive. 

This is an information-only logged event, and could serve as a clue in trying to solve 

an NTR problem. Wrong counts could cause a premature sign off if a COMPLETE 

QUEUE AND TERM remote-site operator keyin is in effect. Other information logged: 

R13: Active device counts work (NS$ADC) from SCT (see AANTRDEF) 

R14: PP-ID 

R15: Device number of the device being terminated 


SNA: 1400 – SNMS SCB not found (id1= %%%%, id2= %%%%) 


that processes operator commands. The id1 is BH$ID1, id2 is BH$ID2, and % 

represents a hexadecimal number. The probable cause is a software problem. 

TTYLPH 

Description: This event occurs if TTYLPH gets zero for the TC$IPACE pace index 

when it is trying to increment it for an input message. This is an information-only, 

debug event. If it occurs, the input message the pace index was to be incremented for 

is discarded. The most likely cause of this is that the input message came in during 

$$SOFF or DOWN processing, resulting in probable discarding of the input message. 

Other information is logged in the registers, but is useful for debug only. Telcon 


5–34 7436 0728–303

Event 11 INVALID / UNRECOGNIZABLE INPUT PARAMETER FOR PROCEDURE 

Event 11 INVALID / UNRECOGNIZABLE INPUT 

PARAMETER FOR PROCEDURE 

INVALID / UNRECOGNIZABLE INPUT PARAMETER FOR PROCEDURE 

DISPATCH OR CALL 

DTP 

Description: A program received a message from another program that could not be 

deciphered. Telcon generates this CENLOG. 

Action: Submit a UCF with a system dump and a console hard copy. 

Description: An error occurs that is of a catastrophic nature to the transport 

connection after DTP has sent a close immediate to the peer to terminate the 

connection properly. The following conditions may occur: TS times out and DTP has 

still not received the close confirm. DTP received an invalid protocol message that 

caused the execution of procedure K. In all cases, DTP abnormally terminates the 

transport connection. Telcon generates this CENLOG. 

Illegal/unknown event code was received while in PLS data state 

Description: R11: 01002 

R12: State and event code 

R15: Location event was generated in PPLS 

Attributes affected: Display event. The X.25 PSCS program product generates this 

CENLOG. Procedure: PPLS. 

Illegal/unknown input or output for the DTP/DTE interface table 

Description: R11: 01002 

R12: DP state and event code 

R15: Location event was generated in PPLS 

Attributes affected: Display event. The X.25 PSCS program product generates this 

CENLOG. Procedure: PPLS. 

7436 0728–303 5–35


NTRLPH 

Description: This event occurs if NTRLPH is called by some procedure with an 

illegal call index or an illegal function index within a legal function. If it occurs, 

NTRLPH merely returns to the caller without performing any processing. This is an 

information-only logged event that may serve as a clue in investigating an NTR 

problem. Other information logged: 

R13: Illegal call index if R14 = X'FFFF' 

R14: Illegal function index or X'FFFF’. Other information is logged in the registers, 

but is useful for debug only 


PU100 

Description: A dispatch is detected and the code in R1 is not valid. Valid codes are: 

0 – Normal dispatch 

02000 – Call from LPHTRS 

03000 – State item processing 

08000 – Initialization 


SNA: 609 – Invalid function code (%%%%) received by XABLUSVC 


application bridge (XAB). The % represents a hexadecimal error. The XAB handles 

traffic between SNA resources and OS 2200 hosts. The probable cause is a software 

problem. 

SNA: 615 – Error in finding SCB Pointer (BH$ID2) 




SNA: 618 – Invalid function code (%%%%) from XABLUSVC 



2200 hosts. The % represents a hexadecimal error. The probable cause is a software 

problem. 

5–36 7436 0728–303


SNA: 622 – Invalid XABLUSVC request to XABRIDGE 




SNA: 624 – Invalid NTNSC queue - item function 




SNA: 635 – Invalid BH$ID - not SCB pointer 




SNA: 639 – Invalid NTNSC Start Type Code 




SNA: 649 – SSCP-LU on P-P has Unsupported NSH 




SNA: 656 – SESS=&&&&-&&&&/&&&&, FM %%%%, TS %%%% Not 

supported 





SNA: 657 – Bad SCB Pointer = %%%%, Called from %%%% 





7436 0728–303 5–37


SNA: 658 – Invalid DCA Sess IDs, Function=%%%%,ID1=%%%%, 

ID2=%%%% 





SNA: 659 – SESS=&&&&-&&&&/&&&&, LU Type %%%% Not 

supported 




number. The probable cause is a configuration problem. 

SNA: 662 – Illogical DTP Message FUNC=%%%%,ID1=%%%%, 

ID2=%%%% 




configuration problem. 

SNA: 668 – Invalid function code (%%%%) received by XABRIDGE 

TAF 





Description: Line type not recognized, or LPH not registered. Telcon generates this 

CENLOG. 

UDLCRS 

Description: R8 = 0007.AE$UD001. (UDLC): UDLCSUS CALLED WITH FUNCTION 

CODE IN R1. Telcon generates this CENLOG. 

5–38 7436 0728–303


XPLS: DATA NOT ALLOWED 

Description: The Packet Layer Services (PLS) feature (module PDNPLS) received a 

disconnect confirm HIC from the host interface that included additional data. The 

extra data are ignored. R15: Virtual address event occurred in procedure PPLS. 


generates this CENLOG. Procedure: PPLS. 

XPLS: ID FROM HOST DOES NOT MATCH 

Description: The Packet Layer Services (PLS) feature (module PDNPLS) is unable to 

obtain one of its connection table entries from the identifier received in a message 

from DTP. The DTP message is discarded. This event includes a copy of PLS’s 

DTE/DTP interface table entry. 

R12: Upper byte: May contain the event received 

R12: Lower byte: May contain the PLS state 

R15: Virtual address event occurred in procedure PPLS 



XPLS: INPUT DISCARDED DUE TO RNR 

Description: The Packet Layer Services (PLS) feature (module PDNPLS) received a 

message data transfer primitive across the Layer 3/4 Platform interface, but PLS is in a 

“receive not ready” state. The primitive and data are discarded. This event includes a 

copy of PLS’s DTE/DTP interface table entry. 




7436 0728–303 5–39


XPLS: INVALID FUNC54 HIC FOUND 

Description: The Packet Layer Services feature (module PDNPLS) was unable to 

successfully process an HIC string message received from the host PLS interface. 

This event includes a copy of the PLSs DTP/DTE interface table entry. 

R9: PLS message type 

R10: Host identifier 

R12: DCP identifier 

R13: Reset/Close diagnostic code 




XPLS: ILLEGAL INPUT FROM L3 

Description: The Packet Layer Services (PLS) feature (module PDNPLS) received an 

invalid primitive function across the Layer 3/4 Platform interface for the state 

perceived by PLS. Primitive is discarded. This event may include a copy of PLS’s 

DTE/DTP interface table entry. 

R9: Primitive function code received 

R12: Upper byte: May contain the primitive received 

R12: Lower byte: May contain the PLS state 




5–40 7436 0728–303


XPLS: ILLEGAL OUTPUT FROM DTP 

Description: The Packet Layer Services (PLS) feature (module PDNPLS) received an 

unknown/invalid message-type code from DTP, or the message type is valid, but not 

for the connection state perceived by PLS. The message is discarded. Invalid codes 

include the message buffers BH$ID2 being zero. This event may include a copy of the 

PLSs DTE/DTP interface table entry. 

R12: Upper byte. May contain the event received 

R12: Lower byte. May contain the PLS state 




X.25 SNMP: Received Unknown/Unexpected ICS packet ("procedure 

name") 

Description: The X.25 PSCS SNMP interface module (PDNSMP) received an 

unrecognizable ICS packet or an ICS packet type that was not expected for the 

current state of PDNSMP. 

R8 - R15: The first eight words of the received ICS packet 

Attributes affected: Recoverable error event, supplementary text message, and a 

table of the received ICS packet. Procedure: The procedure name, which is internal 


message. 

X.25 SNMP: MAU Registration Response returned error status 


Description: The X.25 PSCS SNMP interface module (PDNSMP) was unable to 

successfully initialize with the SNMP Management-Agent user (MAU) interface. The 

MAU returned an error status in response to the PDNSMP’s Registration Request. 

This error causes PDNSMP to dismantle all connections with the MAU interface and 

to become dormant. No SNMP MIB information related to X.25 can be retrieved. 

R8: Error code returned by MAU interface 

Attributes affected: Error event, supplementary text message, and a table of the 

MAU interface Registration Response packet. Procedure: The procedure name, 

internal to the X.25 PSCS PDNSMP module, is displayed as part of the supplementary 

text message. 

7436 0728–303 5–41


X.25 SNMP: Received unknown/unexpected message from MAU 


Description: The X.25 PSCS SNMP interface module (PDNSMP) received an 

unrecognizable message from the SNMP Management-Agent user (MAU) interface or 

an MAU interface packet type that was not expected for the current state of PDNSMP. 

This error can cause PDNSMP to dismantle all connections with the MAU interface 

and to become dormant. In this case, no SNMP MIB information related to X.25 can 

be retrieved. 

R8: MAU interface packet type 


table of the MAU interface packet. Procedure: The procedure name, which is internal 

to the X.25 PSCS PDNSMP module, is displayed as part of the supplementary message. 

X.25 SNMP: Received non-data ICS message ("procedure name") 

Description: The X.25 PSCS SNMP interface module (PDNSMP) received a non-data 

or control message from ICS. The message was not any of the anticipated 

contingency messages. The ICS message is ignored. 

R8 - R15: First eight words of the received ICS packet 


table of the received ICS packet. Procedure: The procedure name, which is internal 


message. 

X.25 SNMP: Unexpected event message from PSCS ("procedure 

name") 

Description: The X.25 PSCS SNMP interface module (PDNSMP) received from one 

of the X.25 PSCS modules either an unrecognizable event packet, or an unexpected 

event packet for the current state. PDNSMP. These event packets are used to 

accumulate statistics related to X.25 protocol events such as Clear, Reset, Restart 

packets, and line errors. The received packet is ignored. 

R8: Event packet type. 


table of the received packet. Procedure: The procedure name which is internal to the 

X.25 PSCS PDNSMP module, is displayed as part of the supplementary text message. 

5–42 7436 0728–303


X.25 SNMP: Unexpected response message from CFACCS 


Description: The X.25 PSCS SNMP interface module (PDNSMP) received from the 

Telcon CFACCS interface either an unknown response message, or an unexpected 

response message for the current state of PDNSMP. The CFACCS response message 

is ignored. This could adversely affect access to information available in the SNMP 

MIB for X.25 protocols. 

R8 - R15: First eight words of the CFACCS response message. 


table of the first sixty-four words of the CFACCS response message. Procedure: The 

procedure name, which is internal to the X.25 PSCS PDNSMP module, is displayed as 

part of the supplementary text message. 

X.25 SNMP: Unexpected timer expiration from AGTIME ("procedure 

name") 


Telcon timer services interface (AGTIME), an unexpected timer expiration message 

for the current state of PDNSMP. The AGTIME message is ignored. 

R8 - R15: First eight words of the AGTIME message. 


table of the first sixty-four words of the AGTIME message. Procedure: The procedure 

name, which is internal to the X.25 PSCS PDNSMP module, is displayed as part of the 

supplementary text message. 

X.25 SNMP: Unexpected timer response from AGTIME ("procedure 

name") 


Telcon timer services interface (AGTIME) an unexpected timer response message for 

the current state of PDNSMP. The AGTIME response is ignored. 

R8 - R15: First eight words of the AGTIME response message. 


table of the first sixty-four words of the AGTIME response message. Procedure: The 

procedure name, which is internal to the X.25 PSCS PDNSMP module, is displayed as 

part of the supplementary text message. 

7436 0728–303 5–43

Event 12 MESSAGE PROCESSING ERROR DETECTED 


MESSAGE PROCESSING ERROR DETECTED 

Description: A program received a message that could not be processed because an 

error was detected. Telcon generates this CENLOG. 

Action: This CENLOG may appear under normal conditions from DTP. If you are 

experiencing session problems or if this CENLOG is generated by a module other than 

DTP, submit a UCF with a system dump and a console hard copy. 


ATTEMPTED TO REGISTER DUPLICATE COMMAND 

Description: An attempt by a program product to dynamically register with NMS a 

previously registered command name. Telcon generates this CENLOG. 

Action: Submit a User Communication Form (UCF) with a system dump. 

BVINPUT 

Description: A syntax error has been detected within the input data. 

R8: Previous contents of register 2. The offset value into the previous contents of 

register 2. The offset value into the input data where the syntax error 

occurred 

R13: 01 or 02 

R14: Error code for this error condition 


5–44 7436 0728–303

BVOUTPUT 


Description: An error occurred during a terminate command. Possible incorrect 

device code. 

R8: Previous contents of register 0 





R13: Error code from which the relative location in the program where the error 

occurred may be located 

R14: Error code 


BVOUTPUT 

Description: All the characters within the record were processed, but an end-ofrecord 

indicator was not located. Possible HIC error. 






R13: 032. Error code where the relative location in the program that caused the 

error can be determined. 



BVOUTPUT 

Description: Error encountered during translation — probable protocol error. 

R8: Previous value found in R0 

R11: Previous value found in R3 

R12: Previous value found in R6. Data byte being translated. 

R13: 07, 034. Relative offset into the BV output program where the error was 

encountered. 



7436 0728–303 5–45


BVOUTPUT 

Description: The data byte count containing the number of bytes within the data 

block has been decremented to zero without an end-of-block character being 

encountered. 

R8: Contents of R0 





R13: Error code number used by software development to determine the relative 

program location where the error was encountered 

R13: 01, 02, 08, 0B, 0D, 010–012, 014, 015, 01C, 01E–022, 024–026, 028, 02A–02E 

R14: Error code that denotes the type of error encountered 


DSERV 

DTP 

Description: DSERV could not successfully process a message because a required 

HIC was not found in the message or the message contained syntax errors. Telcon 


Description: DTP has received an invalid DTP protocol message or is announcing 

data loss. Telcon generates this CENLOG. 

DTVTR 

Description: An attempt was made to pick up data from the source buffer, but no 

data was found, or all the data expected was not there. 

R12: TCB address. 


DYNAMIC COMMAND NAME NOT IN REGISTRATION PACKET 

Description: A registration packet with a command name missing was received by 

NMSIS from a program product. Telcon generates this CENLOG. 


5–46 7436 0728–303


DYNAMIC Q*UEUE NUMBER NOT IN REGISTRATION PACKET 

Description: A registration packet with a missing queue number was received by 

NMSIS from a program product. Telcon generates this CENLOG. 


NMSIS 

Description: NMSIS could not successfully process a dynamic command registration 

because of errors encountered during the processing of the registration packet. 


NMSISs DYNAMIC COMMAND TABLE FULL 

Description: The table NMSIS uses to hold dynamically registered commands is full. 



RCSA 

Description: RCAS could not successfully process a message because a required HIC 

was not found in the message or the message contained syntax errors. Telcon 


RFSYN 

Description: RFYSN could not successfully process a message because a required 

HIC was not found in the message or the message contained syntax errors. Telcon 


RMVTR 

Description: RMVTR discovered an error in its link management. 






R14: Varies 


7436 0728–303 5–47


SNA: 650 – SESS=&&&&-&&&&/&&&& S-CK RHRQ=%%%%%%/%% 

SENS=%%%%%%%% 



2200 hosts. The SESS = %% is a session ID, including the partner subarea, partner 

element address, and your element address; & represents a decimal number; and 

SENSE = % is an IBM sense code. For more information on IBM sense codes, refer to 

Appendix D of this manual. The probable cause is a software problem. 

SNA: 653 – LU-LU -RSP, SESS=&&&&-&&&&/&&&&, 

Sense=%%%%%%%% 



2200 hosts. The SESS = is a session ID including the partner subarea, partner element 

address, and your element address, & represents a decimal number, and SENSE = % is 

an IBM sense code. For more information on IBM sense codes, refer to Appendix D of 

this manual. The probable cause is a software problem. 

SNA: 654 – SESS=&&&&-&&&&/&&&&, SLU MAXRU %%%% Too 

Large 



2200 hosts. The SESS = is a session ID including the partner subarea, partner element 

address, and your element address; & represents a decimal number; and % represents 

a hexadecimal number. The probable cause is a configuration problem. 

SNA: 655 – SESS=&&&&-&&&&/&&&&, PLU MAXRU %%%% Too 

Large 



2200 hosts. The SESS = is a session ID, including the partner subarea, partner 

element address, and your element address; & represents a decimal number; and % 

represents a hexadecimal number. The probable cause is a configuration problem. 

SNA: 661 – No DTP Connection for FUNC=%%%%,ID1=%%%%, 

ID2=%%%% 





5–48 7436 0728–303


SNA: 671 – RBFTE - Negative response 




SNA: 684 – @@@@@@@@ Input Message Error - SESSION 





SNA: 685 – Input Message Discarded - ELU down/down pending 




SNA: 686 – ELU Configuration Error - PLU/SLU Mismatch 




SNA: 687 – Input Message Discarded - Segment boundary overflow 




SNA: 1004 – UDLC error - 'AH$SAICD' at wrong time 



SNA: 2211 – Snatrunk logon failed sense data = %%%% %%%% 


DCA traffic across an SNA network. The % represents a hexadecimal number. It is 

informational only. 

SNA: 2212 – Snatrunk config. duplicate destname @@@@@@@@ 


DCA traffic across an SNA network. The @ represents an ASCII character. The 

probable cause is a configuration problem. 

7436 0728–303 5–49


SNA: 2408 – No SCB (vr msg) err= %%%%, ea= %%%%, ru= %% 

%% %% 



NT 2.1 devices. The err represents the error, ea is the element address, ru is the 

request/response unit, and % represents a hexadecimal number. The probable cause is 


SNA: 2409 – No SCB (dev msg) err= %%%%, ea= %%%%, ru= %% 

%% %% 



NT 2.1 devices. The err represents the error, ea is the element address, ru is the 

request/response unit, and % represents a hexadecimal number. The probable cause is 


SNA: 2410 – No PUCB (dlc control msg) err= %%%%, 

mifmsg= %%%% 





SNA: 2411 – No PUCB (device msg) err= %%%%, ru= %% %% %% 



NT 2.1 devices. The ru is the request response unit, % represents a hexadecimal 


SNA: 2412 – No LUCB (device msg) err= %%%%, ru= %% %% %% 



NT 2.1 devices. The ru is the request response unit and % represents a hexadecimal 


SNA: 2414 – Inv sscp_pu dev msg, rh= %% %% %%, ru= %% %% 

%% 



NT 2.1 devices. The ru is the request/response unit, rh is the request/response header, 

and % represents a hexadecimal number. The probable cause is a software problem. 

5–50 7436 0728–303


SNA: 2415 – Inv sscp_lu dev msg, rh= %% %% %%, ru= %% %% %% 





SNA: 2416 – Inv lu_lu dev msg, rh= %% %% %%, ru= %% %% %% 





SNA: 2419 – Inv ru from vr, rh= %% %% %%, ru= %% %% %% 



NT 2.1 devices. The ru is a request/response unit, rh is a request/response header, and 

% represents a hexadecimal number. The probable cause is a software problem. 

SNA: 2420 – Inv msg from vr, rh= %% %% %%, ru= %% %% %% 





SNA: 2421 – Inv msg from dev, rh= %% %% %%, ru= %% %% %% 





SNA: 2601 – PCRCV detected error (Sense = %%%% %%%%) 

Description: A not supported/unrecognized message was received in PCRCV. A 

response is generated and sent to the SNA session partner. This could also be an 

indication that an attempt to send a response failed because of a ‘Send Check.’ The % 

represents a hexadecimal number. 

SNA: 2608 – (TC) RSP exceeds MAXRUSIZE - discarded 



7436 0728–303 5–51


SNA: 2609 – (TC) EUAFO rejected msg - discarded 



SNA: 2610 – (TC) Unexpected response received 



SNA: 2611 – (TC) EPU Send check (PCSEND) Sense = %%%% 


network analysts in determining status of environment. The Sense = %%%% refers to 


this manual. 

SNA: 2612 – CT-SEND-RQ-NORM overflow 



SNA: 2613 – CT-RCV-RQ-NORM overflow 



SNA: 2614 – CT-SEND-RQ-EXP overflow 



SNA: 2615 – CT-RCV-RQ-EXP overflow 



SNA: 2616 – (PS) Invalid message 



SNA: 2619 – (PS) EUSERV error 



5–52 7436 0728–303


SNA: 2620 – (PS) RQ already outstanding 



SNA: 2623 – (PS) PCSEND error EPU Send check, Sense = %%%% 




this manual. 

SNA: 2624 – (PS) %%%% %%%% -RSP received 


network analysts in determining status of environment. The % represents a 


SNA: 2627 – (PS) -RSP sent (Sense = %%%% 0000) 




this manual. 

SNA: 2629 – (PS) CONN CFRM rcvd while DISC ABRT sent 



SNA: 2630 – RECEIVE detected error 



SNA: 2631 – OPENTEL detected error 



SNA: 2632 – CLOSETEL detected error 



7436 0728–303 5–53


SNA: 2633 – (LS) LU INFO table processing (NRCB load failed) 



SNA: 2637 – (LS) Invalid RSP discarded (RU=%%%%) 


network analysts in determining status of environment. The RU refers to 

request/response unit and % represents a hexadecimal number. 

SNA: 2638 – (LS) EUAFO rejected msg - discarded 

Description: An indication that an attempt to queue a message using EUAFO failed. 

The message is lost. 

SNA: 2639 – SNA Send check, Sense = %%%% %%%% 




this manual. 

SNA: 2640 – EPU Send check, Sense = %%%% 


network analysts in determining status of environment. The Sense %%%% refers to an 

IBM sense code. For more information on IBM sense codes, refer to Appendix D of 

this manual. 

SNA: 2641 – SNA Receive check, Sense = %%%% %%%% 




this manual. 

SNA: 2642 – EPU Receive check, Sense = %%%% 




this manual. 

5–54 7436 0728–303


SNA: 2643 – %%%% -RSP received 




SNA: 2644 – SENDTEL error - DCA session not active 



SNA: 2645 – DCA control message error (%%%%) 




SNA: 2646 – Invalid data assurance response 



SNA: 2647 – Invalid DFC signal data (%%%%) 




SNA: 2648 – Received data was discarded 



SNA: 2649 – INT-1 data error 



SNA: 2650 – DCA non-connect msg – no session 



7436 0728–303 5–55


SNA: 2651 – Unsupported MUCB signal (%%%%) 




SNA: 2652 – Unsupported SC request (%%%%) 




SNA: 2653 – Unsupported DFC request (%%%%) 




SNA: 2654 – Unsupported RU category (%%%%) 




SNA: 2658 – Received device status - %%%% 




SNA: 2659 –Session Request - REJECTED - FROM=@@@@@@@@ 

TO=@@@@@@@@ 

Description: The POOL configured limit of dynamically allocated LUs - SESLIM - has 

been exceeded. The @ represents LU names. 

• Reconfigure another value higher on the specific POOL statement and reset the 

POOL using NMS DOWN/UP. 

• A PARTNER/terminal has attempted to connect to its configured static LU but the 

LU is marked as DOWN. The PARTNER/terminal connection using the EPU2 

POOL is not usable until the LU is set to an UP state. 

UNABLE TO ADD DYNAMIC QUEUE TO QUEUE LIST 

Description: The dynamic queue could not be added to the queue list of NMSIS as 

part of a command register. Telcon generates this CENLOG. 


5–56 7436 0728–303

Event 13 PROCEDURE PROCESSING ERROR (INTERNAL) 

Event 13 PROCEDURE PROCESSING ERROR 

(INTERNAL) 

PROCEDURE PROCESSING ERROR (INTERNAL) 

Description: Internal software errors. Conditions occur that should not. Telcon 


Action: If this problem occurs frequently, send a UCF with a hard copy of the 

console messages. 

AGSYSRTN 

DTP 

Description: A specification error occurred in a procedure for which contingency 

processing is implemented. The procedure’s contingency routine called the system 

service AGCONT to log the error, and performed error recovery to allow the system to 

continue with operation. Telcon generates this CENLOG. 

Description: DTP has detected an invalid event for the current state of the transport 

service machine or of the DTP protocol machine. Telcon generates this CENLOG. 

LMS 

Description: LMS detected an unresolvable error, and was unable to report it to the 

original requestor. Telcon generates this CENLOG. 

RMVTR 

Description: RMVTR detected a miscellaneous internal error. 






R14: Varies 

R15: Varies 


7436 0728–303 5–57


SNA: 257 - Could not delete PU CB 

Description: This error message is the result of trying to delete the control block of a 

physical unit and being unsuccessful. 

SNA: 443 – Correlation Table LAx Corruption: SNF=&&&&& 

Description: This message occurs as a result of errors or events in SNASS SNA/net. 

The & represents a decimal number. The probable cause is a software problem. 

SNA: 444 – Unable to delete CT entry: CBID = &&&&& 



SNA: 445 – QUEUE Table LAx corrupted: LAx=&&&&& 



SNA: 446 – Illegal DCF Return Code: code 

Description: This message occurs as a result of errors or events in session services 

(SNASS). SNASS performs SSCP services for SNA/net; such as, directory lookup and 

conversing with other SSCPs in the process of establishing and terminating sessions. 

This event records internal coding errors that should be reported. This event may 

cause lack of SNA session establishment. 

SNA: 447 – DomIDX Mismatch Session: DomIDX Message: DomIDX 




This event records internal coding errors that should be reported. This event may 

cause lack of SNA session establishment. Domain Indexes (DomIDX) are assigned in 

order from the Configuration File in a multiple DOMAIN SNA/net configuration. The 

DomIDX associated with a session procedure table entry does not agree with the 

DomIDX associated with the currently loaded SNASS message Workspace. 

SNA: 448 – Down/Up of resource required 

Description: An online configuration change has modified the parameters of a 

resource. An NMS DOWN and UP of the resource must be performed before the 

modification is effective. 

5–58 7436 0728–303


SNA: 605 – Parentgateway status of ELU -> INACTIVE 




SNA: 606 – Bit map correlation error (Error code = %%%%) 


application bridge (XAB). The XAB handles traffic between SNA resources and 

OS 2200 hosts. The probable cause is a software problem. 

Possible values for bit map correlation errors are as follows: 

0001 – Logical bit-map error between XC$ and XH$ bitmaps. 

0002 – Logical bit-map error between XC$ and SCB bitmaps. 

0003 – Logical bit-map error between XC$ and CPT timers. 

0004 – XAB timer ID bit-map errors. 

FFFF – Allocated bit-map is full. 

SNA: 607 – ELU chain error (count length) 




SNA: 610 – ELU Element Address = %%%% invalid 





SNA: 611 – EAX table ELU CB pointer = 0 




SNA: 613 – No queued Session found to match BIND Request 




7436 0728–303 5–59


SNA: 616 – ELU status = INACT with SCB status = ACTIVE 




SNA: 625 – Invalid PCID - No QSLE found 




SNA: 626 – Invalid Session Key - No QSLE/SLE 




SNA: 637 – SESS-KEY mismatch with CBs 




SNA: 638 – SESS-KEY not found 




SNA: 643 – No QSLE available for LOGON request 




SNA: 644 – No PCID value available for LOGON request 




SNA: 673 – 3770 - first SCB not CONSOLE 




5–60 7436 0728–303


SNA: 677 – SCB HASH TABLE ERROR (CODE = %%%%) 





SNA: 689 – Domain Index for this ELU not found 




SNA: 1006 – Invalid SSCP-PU state = %%%% , discard 




SNA: 1012 – Invalid LU-LU state = %%%% , discard 




SNA: 1013 – Invalid SSCP-LU state = %%%% , discard 




SNA: 1014 – Invalid rsp from SNABFO, RU code = %%%%, discard 




SNA: 1015 – Invalid req from SNABFO, RU code = %%%%, discard 




7436 0728–303 5–61


SNA: 1016 – Invalid func code from SNASS = %%%%, discard 




SNA: 1017 – Invalid timeout event type = %%%%, discard 




SNA: 1018 – Invalid NMS func code = %%%%, discard 




SNA: 1019 – Illegal IT type from NMS = %%%%, discard 




SNA: 1024 – Invalid message number passed = x%%%% 




SNA: 1025 – Invalid PU type in PUB = %%%% 




SNA: 1026 – Message too large, number = x%%%% 




SNA: 1027 – Invalid session type in message MPH area 



5–62 7436 0728–303


SNA: 1035 – SETTIM request failed 



SNA: 1037 – LU control block create error 



SNA: 1038 – BFNPSI - Invalid control message 

Description: This message occurs when an invalid control message is received by 

the boundary function (BF) from the program product PSCS or from SNA/net module 

NT21CP. 

SNA: 1039 – BFNPSI - Invalid PUCB state = %%%% 

Description: This message occurs when boundary function (BF) receives a PSCS 

“call accept” message and the physical unit (PU) calling “type” was found to be 

incorrectly configured. The % represents a hexadecimal number. 

SNA: 1040 – BFNPSI - No PU found for rcv’d IDBlk/Num 

(%%%%%%%%) 

Description: This message indicates that an XID was received with a given 

IDBLK/IDNUM and no PU was configured on the DTE with a matching 

IDBLK/IDNUM. A PU needs to be configured with a matching IDBLK/IDNUM value 

before it will connect. Optionally, only one PU with no IDBLK/IDNUM field can be 

configured per DTE where no validation is performed. The % represents a 


SNA: 1041 – BFNPSI - PU with IDBlk/Num(%%%%%%%%) already 

active 

Description: This message indicates that a PU with a given IDBLK/IDNUM is already 

active on the DTE and the new request is denied. This may be an inadvertent 

duplicate of an XID’s use of the IDBLK/IDNUM. Remote configurations should be 

investigated. The % represents a hexadecimal number. 

SNA: 1409 – Msg discarded - SNMS to NMS internal sess bad 


that processes operator commands. The probable cause is a configuration problem. 

7436 0728–303 5–63


SNA: 1410 – SNMS to NMS internal session failed 



SNA: 1411 – SNMS - registration as nms extension failed 



SNA: 1801 – SNMS Parse Exception Occurred 



SNA: 1802 – SNMS Parse Internal Error Detected 



SNA: 1804 – SNMS Display Exception Occurred 



SNA: 1805 – SNMS Display Internal Error Detected 



SNA: 1807 – SNMS Vary Exception Occurred 



SNA: 1808 – SNMS Vary Internal Error Detected 



SNA: 1810 – SNMS Reqms Exception Occurred 



5–64 7436 0728–303


SNA: 1811 – SNMS Reqm Internal Error Detected 



SNA: 1813 – SNMS Link Timer Exception Occurred 



SNA: 1814 – SNMS Link Timer Internal Error Detected 



SNA: 1817 – SNMS Move - Internal error 



SNA: 1818 – SNMS Move - Recovery file invalid 



SNA: 2000 – Invalid fdbsc cenl display attempted, number = &&&&& 

Description: This message occurs as a result of error in establishing sessions 


& represents a decimal number. The probable cause is a software problem. 

SNA: 2001 – Invalid son notification rcvd, w1= %%%%, w2= %%%% 




SNA: 2004 – No cbs xab, yea %%%% pea %%%% psa %%%%, 

ru= %% %% %% 



yea is your element address, pea is a partner element address, psa is a partner 

subarea, ru is a request/response unit, and % represents a hexadecimal number. The 


7436 0728–303 5–65


SNA: 2005 – No cbs ervr, yea %%%% pea %%%% psa %%%%, 

btu= %% %% 



yea is your element address, pea is a partner element address, psa is a partner 

subarea, btu is a basic transmission unit, and % represents a hexadecimal number. 


SNA: 2006 – State %% %% error, ervr msg, yea= %%%%, btu= %% 

%% 



yea is your element address, btu is a basic transmission unit, and % represents a 


SNA: 2007 – State %% %% error, xab msg, yea= %%%%, ru= %% 

%% %% 



yea is your element address, ru is a request/response unit, and % represents a 


SNA: 2200 – Invalid Snatrk cenl display attempted, #= &&&&& 


DCA traffic across an SNA network. The & represents a decimal number. The 


SNA: 2201 – MM cb creation error, mmerr %%%% syserr %%%% 




SNA: 2202 – MM search err, mmerr %%%%, yea %%%%, psa 

%%%% 


DCA traffic across an SNA network. The yea is your element address, psa is a partner 

subarea address, and % represents a hexadecimal number. The probable cause is a 


5–66 7436 0728–303


SNA: 2203 – Invalid isystem config item, name = @@@@@@@@ 


DCA traffic across an SNA network. The @ represents an ASCII character. The 


SNA: 2205 – Invalid timeout received, literal = %%%% %%%% 




SNA: 2206 – Timeout error, no cb %%%% %%%%, mmerr= %%%% 




SNA: 2400 – Invalid nt21 cenl display, number= &&&&& 



NT 2.1 devices. The & represents a decimal number. The probable cause is a 


SNA: 2407 – Invalid timeout received, literal = %%%% %%%% 





SNA: 2417 – Inv lu_lu state (&&), rh= %% %% %%, ru= %% %% %% 



NT 2.1 devices. The & represents a decimal number, rh is a request/response header, 

ru is a request response unit, and % represents a hexadecimal number. The probable 


SNA: 2418 – Inv snass msg, function code = %%%% 





7436 0728–303 5–67


SNA: 2422 – Mparse err = %%%%, msg from vr, ru= %% %% %% 



NT 2.1 devices. The ru is a request/response unit and % represents a hexadecimal 


SNA: 2423 – Mparse err = %%%%, msg from dev, ru= %% %% %% 





SNA: 2424 – Mparse err = %%%%, msg from lh, ru= %% %% %% 





SNA: 2438 – Mparse err = %%%%, xid from lh 





SNA: 2439 – Mparse err = %%%%, cinit from snass 





SNA: 2600 – R1 Dispatched to PC in ERROR 



SNA: 2606 – SNAPATH application detected error 



5–68 7436 0728–303


SNA: 2607 – PC NRCB services error (Service Request 

Code = %%%%) 




SNA: 2626 – (PS) Invalid procedure call (Caller id = %%%%) 




SNA: 2634 – BLDACB detected error (Load of NRCB failed) 



SNA: 2635 – (LS) An attempt to send a -RSP was rejected 

(EC = %%%%) 




SNA: 2636 – (LS) LU-LU Session no longer active 



SNA: 2656 – SVC error - %%%% 




SNA: 2801 – IPM Disconnect 

Description: This message occurs as a result of a disconnect of an IPM channel to 

ICS. The probable cause is that the ICS run has terminated. 

SNA: 2802 – IPM Disconnect - Exception 


Management Protocol) Submanaged Program. Caused by an exception condition 

during IPM channel disconnection. 

7436 0728–303 5–69


SNA: 2803 – ICS Registration Failed 


Management Protocol) Submanaged Program. Indicates the user registration with ICS 

failed. 

SNA: 2808 – Invalid Input Channel 


Management Protocol) Submanaged Program. An invalid receive channel was 

detected during input queue processing. 

SNA: 2809 – Invalid Receive Status 


Management Protocol) Submanaged Program. An unknown receive status was 

detected during input queue processing. 

X.25 SNMP: Software logic error ("procedure name") 

Description: The X.25 PSCS SNMP interface module (PDNSMP) encountered an 

unexpected processing error. This event may be preceded by another CENLOG entry 

indicating the type of error that occurred. This error may cause PDNSMP to become 

dormant. In this case, no SNMP MIB information related to X.25 can be retrieved. 

R8: PDNSMP status 

Attributes affected: Error event, supplementary text message, and the first 128 

bytes of a message buffer, if present. 

Action: This event indicates an internal software interface error. You should submit 

the contents of this entry to your Unisys representative for analysis. You may have to 

re-start your Telcon run in order to recover from this error. If the error re-occurs, take 



message. 

5–70 7436 0728–303

Event 14 CONFIGURATION FILE ACCESS / REQUEST ERROR 

Event 14 CONFIGURATION FILE ACCESS / REQUEST 

ERROR 

CONFIGURATION ACCESS ERROR 

Description: This error message is the result of trying to access the configuration file 

and being unsuccessful. 

CONFIGURATION FILE ACCESS / REQUEST ERROR 

Description: Configuration file access error - cannot access incarnation number. 


Action: If this event occurs frequently, retrieve the configuration file and start a 

batch run to activate the program. 

PDNMS 

Description: The X.25 PSCS NMS processing module (PDNMS) received an X.25 

PSCS specific NMS command, but X.25 PSCS is not initialized. 

Attributes affected: Configuration event. The X.25 PSCS program product 

generates this CENLOG. Procedure: PDNMS. 

Action: Verify that at least one of X.25 PSCS’s lines has been enabled on a valid line 

module using an NMS UP LINE command. If a line has already been enabled, then 

X.25 PSCS may currently be initializing, or an initialization error has occurred and has 

been recorded with a CENLOG class/event of 5/15 with a supplementary text message 

of: “PSCS initialization error.” 

PPID NOT FOUND 

RTC 

Description: During line termination (module PDNSVS) was unable to successfully 

access one of its link layer table (Z2$) entries. PDNSVS was unable to obtain a match 

based on the LINE STE index contained in the line control block (LCB). 

Attributes affected: Line event, Configuration event. The X.25 PSCS program 

product generates this CENLOG. Procedure: PDNSVS. 

Action: Online configuration changes to the LINE statement may require Telcon to 

be restarted. If this event occurs after Telcon is restarted, then a software error has 

either corrupted the LINE STE index in the PDNSVSs link- layer table or in the LCB. 

Description: A configuration error occurred while processing the ROUTE 

configuration statements. Telcon generates this CENLOG. 

7436 0728–303 5–71


SNA: 256 – Configuration access error 

Description: This message occurs as a result of not being able to access the 

configuration file. 

SNA: 1820 – SNMS Move –Cfaccs error move incomplete 



SNA: 2204 – Config access error, code= &&&&& 


DCA traffic across an SNA network. The & represents a decimal number. The 


SNA: 2406 – Config access error, code= &&&&& 




hardware problem. 

SNA: 2625 – (PS) CFACCS error 

SRC 

SRC 

SRC 



Description: SRC is processing a connect indication from DTP. The attempt to 

convert the from-name to a DCP ID by locating it in the configuration ID table is 

unsuccessful. Telcon generates this CENLOG. 

Description: SRC is processing an UPDATE TS STATUS command from the 

alternate DCP, or is trying to send one. The attempt to locate the appropriate DCATS 

configuration statement in the configuration is unsuccessful. Telcon generates this 

CENLOG. 

Description: When SRC receives the first resilient LINE configuration statement for 

a particular Telcon node, it cycles through the RCM configuration statements in the 

configuration looking for the one that corresponds to that Telcon node. This RCM 

configuration statement cannot be found. Telcon generates this CENLOG. 

5–72 7436 0728–303

SYSSESN 

TRS 


Description: A CFACCS call failed. 

R14: 03 = identifier 

R15: Error code from CFACCS call 


Description: TRS made a call to configuration access, and an error status was 

returned, indicating a no-find or disk-access error. 

R11: LCB 

R14: IOPID 

TSM 


Description: Control returns to TSM from a CFACCS call with a hardware or 

software error. Check the error field upon return. This may lead to conflicts within 

the configuration. Telcon generates this CENLOG. 

UTS4000 is not configured 

Description: UTS 4000 is not properly configured. 

R8: Logical link number 

R14: MCT address 



Action: Correct the DTE and/or CLSTR statements for the UTS 4000 cluster. 

X.25 SNMP: CFACCS returns error response ("procedure name") 

Description: The X.25 PSCS SNMP interface module (PDNSMP) received an error 

response from the Telcon configuration access (CFACCS) interface. This adversely 

affects the ability of X.25-related MIB information from being retrieved by the SNMP 

management workstation. It may be a temporary condition. 

R8: CFACCS error type 

Attributes affected: Configuration event, recoverable error event, supplementary 

text message, and a table of the first 128 bytes of the CFACCS response message 

7436 0728–303 5–73


buffer. Procedure: The procedure name, which is internal to the X.25 PSCS PDNSMP 

module, is displayed as part of the supplementary text message. 

Action: PDNSMP automatically recovers from this event. If the error re-occurs, take 

a Telcon dump and submit a UCF. 

X25 NDS ERROR: UTS 4000 MUST BE CONFIGURED ON FIRST 16 

X25 LINES 

Description: X.25 PSCS received an incoming call packet from the network that is 

configured for the UTS 4000 Cluster. The call packet was received on a line 

associated with a PDNGRP statement that is not one of the first 16 specified in the 


R8: The nth minus 1 PDNGRP statement specified in the configuration that is 

associated with the line where the incoming call was received 

R9: The logical channel number used by the incoming call packet 

R11: The diagnostic code used in the clear packet returned to the network 

Attributes affected: Supplementary text message, Configuration event. The X.25 

PSCS program product generates this CENLOG. Procedure: PDNL44. 

Action: The configuration must be modified so that DTE statements specified for the 

UTS 4000 Cluster must have one of the first 16 specified PDNGRP statements in the 

configuration as its parent. 

5–74 7436 0728–303

Event 15 CONFIGURATION ERROR DETECTED / UNDEFINED 

Event 15 CONFIGURATION ERROR DETECTED / 

UNDEFINED 

CONFIGURATION ERROR DETECTED/UNDEFINED 

Description: Configuration file error (undefined) - expected information not present. 


Actions: 

1. Notify the person responsible for creating and maintaining the Telcon 

configuration element. That person can then recheck the configuration 

statements for HCONFIG errors and for adherence to rules stated in the Telcon 

Configuration Guide (7831 5678). 

2. If this message has started appearing suddenly and frequently, transfer the 

configuration to a host (for example, XFER file = CONFIG) and process it there 

by entering @ADD TEL*LIBABS.TELCNFGR after the person responsible for 

installing the Telcon products catalogs a permanent TEL*LIBABS file and copies 

the LIBABS file from the original Telcon release tape. For more information, refer 

to the Telcon Installation Guide (7831 5645). 

3. As a last resort, take a dump and reload the Telcon from the host. Send a UCF 

with a dump and a console printer copy. 


ATTEMPT TO CREATE DUPLICATE NAME IN DIRECTORY NAME = 

name 

Description: The DSA has received a request to add an already existing name to the 

directory information base (DIB). Telcon generates this CENLOG. 

Action: None. 

Configuration error detected/undefined 

Description: An NMS command pertaining to X.25 facilities was entered. A disk-file 

configuration-access error occurred other than a name-not-found error. 

R10: May contain STE index of statement accessed 

R14: CFACCS error code 

Attributes affected: Configuration event, Display Event. The X.25 PSCS program 

product generates this CENLOG. Procedure: PDNMS. 

7436 0728–303 5–75


DMOPEN 

Description: After DMOPEN receives a valid ATTACH request from DTP, DMOPEN 

must determine the group ID for the terminal. This is accomplished by obtaining the 

information from the configuration file by providing CFACCS with the STE index. 

This code is used when CFACCS reports errors while attempting to read the 

configuration file. Telcon generates this CENLOG. 

R9: Configuration access buffer address (msg) 

R14: STE index 

DUPLICATE NODE DETECTED IN NETWORK, NA = node address 

Description: Duplicate node detected in network. This node has been kept from 

entering the network because it is considered to be a duplicate node, or a neighbor to 

this node was not allowed because it was considered to be a neighbor node. Telcon 

generates this CENLOG in the DNS modules. 

Action: The operator must determine which nodes have the same address specified 

in the supplementary message (NA = ) and correct the configuration. 

ILLEGAL UNKNOWN DTE ADDRESS 

Description: A call indication packet was received from a network that contained an 

unrecognizable DTE address. No user data was provided and no default layer 4 was 

configured. 

R9: Logical channel number 

R12 – 15: Calling remote DTE address 

Attributes affected: Supplementary text message, Display Event. The X.25 PSCS 

program product generates this CENLOG. Procedure: PCALL. 

ILLEGAL FACILITY CODE REQUESTED 

Description: A call indication packet with a facility field contains an illegal or 

unknown facility code. The call is cleared. 

R8: Illegal facility code 

R9: Clear packet’s diagnostic code 

Attributes affected: Supplementary text message, Display event. The X.25 PSCS 

program product generates this CENLOG. Procedure: PCALL. 

5–76 7436 0728–303


ILMX25 Waiting for Response From ILM Platform 

Description: The PDNILM module has not received a response from a request packet 

that it previously sent to the ILM Platform. 

Attributes affected: Line event includes the port number and supplementary text 

message. Procedure wait_receive of the X.25 PSCS program product generates this 

CENLOG. 

Action: If the line was not previously enabled then the ILM Platform may not be 

responding because required ILM load and configuration files are not present on the 

DCP mass storage. The ILM-20 HS omnibus load file element, ILMLOAD.ILMPLATA1, 

must be present. The ILM-20 HS source configuration file element, 

ILMCFG.PSCSHDLC, must also be present. The qualifier name for these files must 

match the project id of the DCP OS Run statement used to start the Telcon program. 

If the line was previously active then this event may indicate a (severe) looping or 

hanging condition in the ILM Platform or ILM IA. 

ILMX25 Line Already Down 

Description: PDNILM received an NMS DOWN LINE request from the ILM Platform, 

but the indicated line is already marked down in the configuration, or no line control 

block (LCB) is associated with the line. 


message. Procedure p_nms_dwn of the X.25 PSCS program product generates this 

CENLOG. 

Action: Check the Telcon configuration for duplicate port addresses on the LINE 

configuration statement’s ADR parameter. 

Initialization error (Error code = %%%%) 



2200 hosts. The probable cause is resource availability (out of memory, out of disk). 

SNA/net message number 600. 

Possible values for initialization errors are as follows: 

• Unable to load PST 

• SVC$CSEG unable to create SSN for common data segment 

• SVC$CSEG unable to create SSN for element address index table 

• SVC$CSEG unable to create SSN for host table 

LPHTRS 

Description: TRS was notified of a CFACCS error status software error report by file 

control. Telcon generates this CENLOG. 

7436 0728–303 5–77


LSUB #00nn IS NOT CONFIGURED FOR TS #00cc 

Description: This CENLOG refers to an error in DUC where it received an 

initialization message for a Logical Subchannel (SESSN statement) that is not 

configured for this DCP. The user may not be able to access a Termination System if 

this session that is in error is the only session to the Termination System. An Out of 

Order Reset is sent back to the sender. Telcon generates this CENLOG. 

Action: From the NMS console, determine what the TS is that is sending the 

message. This can be done by entering DISP TS = 00cc. Then either add a SESSN 

statement to the Telcon configuration to match the LSUB number or remove the 

configuration to match the LSUB number or remove the configuration from the TS 


NTRLPH 

Description: This event occurs if an NTR site attempts to sign on using a full-duplex 

site ID on a line that is configured as half-duplex. This sign-on attempt will not 

succeed, and repeated attempts of such a sign on are logged in the same manner. 

Other information is logged in the registers, but is applicable to debug only. Telcon 


Action: The configuration on either the remote NTR site or for the DCP line being 

used should be changed. 

NTRV2P 

Description: This event occurs if code in NTRV2R that has specifically been turned 

off by the customer (to reduce memory requirements) was actually required. This is a 

fatal error (to NTRV2R), resulting in the procedure being blocked or the Telcon 

crashing. Other information is logged in the registers, but is applicable to debug only. 


OSIIP–DUPLICATE DNS SUBNET 

Description: More than one OSISN configuration statement processed defining a 

DNS subnet. The OSIIP component of the OSITS program product generates this 

CENLOG. 


OSIIP–FWD PDU FAIL 

Description: A PDU could not be forwarded because the forwarding subnet is down. 

OSITS requested output of message with no segmentation allowed. The OSITS 


Reason: Network failure and invalid OSITS request, respectively. 

5–78 7436 0728–303


OSIIP–INVALID FULLY SPECIFIED 

Description: A fully specified output request has been discarded. The OSIIP 


Reason: Invalid output parameters in request. 

OSIIP–IP NOT ACTIVE; GENERIC NSAP REQUIRED 

OSIIP–MEMORY MANAGEMENT FAIL 

Description: An error was returned to OSIIP to a memory management module 

request. The OSIIP component of the OSITS program product generates this 

CENLOG. 

Reason: System failure. 

OSIIP–MAX LAN SUBNETS EXCEEDED 

Description: Maximum of 26 dynamically configured subnets exceeded. The OSIIP 



OSIIP–QUERY NO RESPONSE 

Description: A response has not been received to a query request. The OSIIP 


Reason: Destination of PDU not recognized by other systems on the network. 

OSIIP–RIB ERROR 

Description: An error PDU could not be returned to an error condition because the 

error PDU destination is not in the RIB. The OSIIP component of the OSITS program 


Reason: RIB error. 

OSIIP–SUBNET NSAP NOT DEFINED 

Description: Output requested on subnet for which no source NSAP is defined. The 

OSIIP component of the OSITS program product generates this CENLOG. 


7436 0728–303 5–79


OSIIP–SUBNET SPACE FULL 

Description: The maximum number of OSISN configuration statements has been 

exceeded. The OSIIP component of the OSITS program product generates this 

CENLOG. 


OSIIP–UNRECOGNIZED NDS 

Description: An attempt was made to process an NDS (configuration statement) 

type other than an NSAP, OSIROUTE, or OSISN. The OSIIP component of the OSITS 



OSIIP–UNRECOGNIZED PSCS FUNCTION CODE 

Description: An attempt was made to process a configuration statement type other 

than an NSAP, OSIROUTE, or OSISN. The OSIIP component of the OSITS program 


Reason: Program product mismatch. 

OSIIP–STATIC CIRCUIT IGNORED 

Description: Request to build static circuit subnet received after system has 

initialized. The OSIIP component of the OSITS program product generates this 

CENLOG. 

Reason: Configuration request in error. 

OSIIP–SPECIFIC NSAP CONFLICT 

Description: Multiple NSAP configuration statements reference the same 

subnetwork by way of an OSISN keyword. The OSIIP component of the OSITS 


Reason: Configuration request in error. 

5–80 7436 0728–303

PDNSVS 


Description: During line initialization (module PDNSVS) was unable to successfully 

access one of its link-layer table (Z2$) entries. PDNSVS was unable to obtain a match 

based on the LINE STE index contained in the line control block (LCB). This event 

includes the LINE name. 

R10: PDNGRP STE index 

Attributes affected: Line event, LCB is in Register R11, Configuration event. The 

X.25 PSCS program product generates this CENLOG. Procedure: PDNSVS. 

Action: Online configuration changes to the LINE statement may require Telcon to 

be restarted. If this event occurs after Telcon is restarted, then a software error has 

either corrupted the LINE STE index in PDNSVS’s link- layer table or in the LCB. 

RMVTR 

RTC 

Description: RMVTR detected an invalid configured value. 




Description: Route table could not be created/expanded properly for route control. 


SNA: 230 - TG=index#: Station address error, Rcv Adr x%%%% 

Description: This message occurs as a result of errors or events in the Transmission 

Group Control (TGC) that controls lines between SNA/net and IBM subareas. %%%% 

represents a hexadecimal number for the receiver address. The # is a TG index 


SNA: 248 – TG=index#: Could not add PU to transmission group 

Description: This message results from too many physical units in the transmission 

group or an incompatible parameter for the physical unit. The # is a TG index 

number. 

7436 0728–303 5–81


SNA: 420 – COS invalid or undefined: name 



conversing with other SSCPs in the process of establishing sessions. The COS name 

referenced was determined to be invalid. Without this COS being available SNA LU- 

LU session establishment may not occur. 

SNA: 451 – Multiple Pool CDRMs - CDRM ignored 




The CDRM referenced is defined as TYPE=POOLCDRM and a CDRM of that type is 

already active for the parent DOMAIN. This is ignored and marked as “configuration 

status down.” 

SNA: 603 – GW type = %%%% not supported (check configuration) 





SNA: 604 – Resource type = %%%% not supported (check config) 





SNA: 642 – Terminal type %%%% is not supported 



2200 hosts. The % represents a hexadecimal number. It is informational only. 

SNA: 672 – String Definition Error - Check Parameter &&&& 



2200 hosts. The & represents a decimal number. The probable cause is a 


5–82 7436 0728–303


SNA: 678 – Invalid RMT name received from RBFTE SETUP file 

Description: This message occurs when the length of the RBFT/E “user data” 

specified for use in the RBFT/E logon string exceeded eight characters. This 

information is specified in the RBFT/E “setup” file on the Unisys host. 

SNA: 680 – Configuration error - XAB EU not configured 

Description: This message occurs when the end user (EU) type on an SNA/net 

BATCH,SNAPPC,SNARJE or MCB outbound open EU, is not specified to be “XABEU.” 

“XABEU” identifies the EU as a provider of crossover support from one protocol to 

another. 

SNA: 1408 – Too many SNMS EUs configured 


that processes operator commands. The probable cause is a configuration problem. 

SNA: 1600 – Invalid link type = x%%%%, from CFACCS 

Description: This message occurs as a result of errors in DTPLNK, the part of 

SNA/net that enables SNA/net to communicate with other SNA/nets as if they are 

physically adjacent. The % represents a hexadecimal number. The probable cause is a 


SNA: 1601 – Could not create control block for LINK 



physically adjacent. The probable causes are resource availability (out of memory or 

out of disk storage) and configuration problems. 

SNA: 1822 – SNMS UP failed, duplicate logname: @@@@@@@@ 


that processes operator commands. The @ represents an ASCII character. The 

probable cause is a configuration problem. 

SNA: 2404 – Invalid isystem config item, name = @@@@@@@@ 



NT 2.1 devices. The @ represents an ASCII character. The probable cause is a 


7436 0728–303 5–83


SNA: 2405 – LUs directly chained from POOL ignored 



NT 2.1 devices. The probable cause is a configuration problem. 

SNA: 2413 – Xid negotiation error, dlcstate= &&&, code= &&& 





SNA: 2440 – Xid Rejected (Cntrl Vector 022 byte=&& bit=&) 

Description: This message indicates a mismatch of XID field values to configured 

values. The control vector indicates the byte and the bit offset from byte 0 of the XID 

indicating the offending field. The & represents a decimal number. 

SNA: 2443 – PU alloc reject, possible primary/secondary conflict 

Description: This message occurs as a result of errors or events in a Boundary 

Function within SNA/net attempting to configure secondary and primary PUs on the 

same line. The probable cause is a configuration problem. 

SNA: 2444 – Bad XID: Adr/ID Rcvd: %%/%%%%%%%% Cnfg’d: 

%%/%%%%%%%% 

Description: This message indicates that the configured Adr (Station Address) or 

IDBLK/IDNUM value for a given PU does not match the Address or IDBLK/IDNUM 

value on its received XID. Coordination of the Address or IDBLK/IDNUM values with 

the desired hardware should be confirmed. The % represents a hexadecimal number 

for the Address (2-digit) and IDBLK/IDNUM (8-digit) value. 

SNA: 2604 – PC lu list init detected error (Name=@@@@@@@@) 

Description: Allocation of memory space for an LU List failed during the 

initialization of a specified LU. This is a resource problem and sizing of the system 

should be considered. The @ represents an ASCII character. 

SNA: 2605 – PC pu list init detected error (Name=@@@@@@@@) 

Description: Allocation of memory space for a PU List failed during the initialization 

of a specific PU. This is a resource problem and sizing of the system should be 

considered. The @ represents an ASCII character. 

5–84 7436 0728–303


SNA: 2628 – (PS) No PARTNER Name 

Description: An indication that no PARTNER parameter is configured on an LU that 

is attempting an outbound open request (BIND) from the SNA session partner to a 

DCA defined terminal/end-user. 

SNA: 2655 – Received CONNECT REJECT 

SRC 

SRC 

SRC 

SRC 

Description: This message indicates that an LU attempted an open request to DTP 

which failed due to a non-configured PID in CMS. 

Description: Too many DCPs in resilient mode. R8 = STE index. Telcon generates 

this CENLOG. 

Description: INN configuration mismatch. CE$CED AE$RTPTK. Telcon generates 

this CENLOG. 

Description: SRC received an EXCHANGE TSIDs command from the alternate 

Telcon node, and couldn’t find the specified DCATS configuration statement in the 

configuration. supp msg = none. Telcon generates this CENLOG. 

Description: Backup DCP# same as local DCP. 

R8: STE index 


7436 0728–303 5–85


SYSSESN 

Description: Error on SESSN card — fatal. 

R14: Indicates type of error 

= 1 – Session length long, check TS1/TS2 

= 2 – Session length short, check TS1/TS2 

= 3 – CFACCS error return while building LX$ table 

= 4 – Bad Telcon node destination, check TS1/TS2 

= 7 – Duplicate logical subchannel 

R15: LS # 


Too many digits on the PDNGRP DTEADR parameter 

Description: During line initialization (module PDNSVS) obtained the PDNGRP 

statement associated with the LINE statement that was enabled. The number of DTE 

address digits configured on the PDNGRP’s DTEADR parameter is greater than 14. 

The DTE address specified is ignored. This event includes the LINE statement name. 


Attributes affected: Supplementary text message, Configuration event. The X.25 

PSCS program product generates this CENLOG. Procedure: PDNSVS. 

TOO MANY SESSIONS CONFIGURED–INCREASE AC$SESSS. 

Description: This CENLOG refers to an error in TS/TN where it received an 

initialization for a SESSN that was not put into the TS/TN SS$ table. This is because 

the number of SESSNs configured was greater than the maximum table space 

available. If none of the SESSNs to the termination system were able to get into the 

SS$ tables, the user may have a problem getting into the termination system. The 

default is currently 4000 SS$ entries. The system discards this message. Telcon 


Action: Increase the value for AC$SESSS in AACONFIG by using the NEWCON 

parameter. 

TSTN 

Description: Fast path protocol has been specified in Telcon, but the host does not 

support it. This problem could cause Telcon to run in a loop. Check the host system 

release to make sure the host supports fast path protocol. Telcon generates this 

CENLOG. 

5–86 7436 0728–303


XPLS: EU NDS HAS INVALID DTE/XEU NAME: "dte/xeu name" 


successfully process its EU statement because it either didn’t reference a DTE or an 

XEU statement. 

R15: Virtual address event occurred in procedure PLSEUI. 


generates this CENLOG. Procedure: PLSEUI. 

XPLS: INVALID DTE ON EU–R9 = STEX 


successfully obtain a response to DTE information request primitives across the Layer 

3/4 Platform interface. This event includes a copy of its DTP/DTE interface table 

entry. 

R9: DTE STE index 




XPLS: INPUT FOR DP$ THAT IS IN NOT-AVAIL STATE–R9 = DTE STEX 


successfully process a primitive received across the Layer 3/4 Platform because PLS 

perceives the connection is in a “DTE not available” state. This event includes a copy 

of its DTP/DTE interface table entry. 

R9: DTE STE index 




7436 0728–303 5–87


XPLS: SUPERFLUOUS ACK REC'D–DISCARDED 

Description: The Packet Layer Services feature (module PDNPLS) received an 

unexpected Data Acknowledgement primitive across the Layer 3/4 Platform interface. 

The primitive is ignored. This event includes a copy of its DTP/DTE interface table 

entry. 




Action: Online configures the PDNGRP DTEADR parameter to contain less than or 

equal to 14 digits (enter DTEADR = NONE to remove the DTE address). Then use the 

NMS ITLN command to reinitialize the line. Procedure: PPLS. 

X.25: Incoming Calls Barred (RIC), R9 = lcn 

Description: The layer 3 module (PDNL3) was unable to successfully process an 

incoming call packet received from the network or directly attached DTE. The packet 

was received on a logical channel number that is configured to reject incoming call 

packets (one-way only circuits). A clear packet is returned to the network/DAD. This 

event includes the line name. 

R9: Received packet’s logical channel number 



Action: Review the PDNGRP statement’s logical channel range type specified on the 

VCGRP parameter. Procedure: PDNL3. 

5–88 7436 0728–303


X.25: L4 Call Request Cleared, R11 = reason 

Description: The layer 3 module (PDNL3) was unable to successfully process a Call 

Request primitive received across the Layer 3/4 Platform interface. Instead of sending 

a call request packet to the network, PDNL3 returned a Clear Indication primitive to 

the layer 4 module. 

R11: Clear primitive’s diagnostic code. For a description of error codes, refer 

to Appendix B of this manual. 

R12-R15: May contain the called DTE address digits 



X.25 PSCS initialization error 

Description: While processing the X.25 PSCS portion of the configuration, an invalid 

condition occurred. Such conditions can include illegal statement or keyword 

referenced, required statement or missing out-of-range keyword values, internal table 

sizes exceed system segment size, or configuration access error. When an error 

condition occurs, X.25 PSCS remains uninitialized (exceptions noted). Either an 

online configuration change (restarting Telcon is not necessary) or a new, correct 

configuration file is required to correct the error condition. 

R8: Relative address offset in PDNIUS at which the error occurred 

R9: Error code. For error code explanation, refer to Appendix B of this manual. 

R10: Supplemental error information, if applicable. For error code explanation, 

refer to Appendix B of this manual 

R11: Line Control Block (LCB) 

R12: Supplemental error information, if applicable. For error code explanation, 

refer to Appendix B of this manual. 

Attributes affected: Configuration event, LCB address in R11, and Supplementary 

text message. The X.25 PSCS program product generates this CENLOG. Procedure: 

PDNIUS. 

7436 0728–303 5–89


X.25: Unassigned LCN, R9 = lcn 

Description: The layer 3 module (PDNL3) was unable to successfully process a 

packet received from the network or directly attached DTE. The packet was received 

on a logical channel number that is outside the range of configured logical channel 

ranges. This event includes the line name. 


Attributes affected: Line event, Configuration error event, Error event, 

Supplementary text message. The X.25 PSCS program product generates this 

CENLOG. 

Action: Review the PDNGRP statement’s logical channel ranges specified on the 


X.25: Virtual Circuit Assignments 

Description: The layer 3 module (PDNL3) was unable to successfully process a 

packet received from the network or directly attached DTE. The packet was received 

on a logical channel number of zero (and not configured to be by specifying the 

X25DEF statement’s L3OPT parameter value 3), or an invalid packet was received on 

a configured permanent virtual circuit (PVC). This event includes the line name. 




Action: Review the PDNGRP statement’s logical channel ranges specified on the 


X.29 SIGNON FAILED: NO TERMINAL CONFIGURED 

Description: The X.29 Terminal initialization module (PDNURS) was unable to 

successfully process a $$SON command from a terminal connected through an X.29 

PAD interface. The reason is because the TERM statement with which it is associated 

does not reference a valid PDNPAD statement. The supplementary text message is 

logged with this event. 



Action: Review X.25 PSCS’s NDSs (configuration statements). Verify all the TERM 

statements for X.29 PAD terminals reference valid PDNPAD statements. Procedure: 

PDNURS. 

5–90 7436 0728–303



SNA: 225 – PU control block not found 


Description: This message occurs as a result of errors or events in the transmission 

group control (TGC) that controls lines between SNA/net and IBM subareas. The 


SNA: 227 – TG=index# Requested function out of range 


Group Control (TGC) that controls lines between SNA/net and IBM subareas. The # is 

a TG index number. The probable cause is a software problem. 

SNA: 235 – TG=index#: No QL index available: x%%%% 


Group Control (TGC) that controls lines between SNA/net and IBM subareas. The % 

represents a hexadecimal number. The # is a TG index number. The probable cause 

is a software problem. 

SNA: 236 – TG=index#: Create queue error: x%%%% 



represents a hexadecimal number. The # is a TG index number. The probable cause 

is a software problem. 

SNA: 237 – TG=index#: Queue list entry not made 




SNA: 238 – TG=index#: Delete of a dynamic queue failed 




7436 0728–303 5–91


SNA: 239 – TG=index#: PIU queuing error 




SNA: 240 – TG=index#: Dynamic queuing error 




SNA: 243 – TG=index#: Link area full 




SNA: 244 – TG=index#: Link area error 




SNA: 245 – No PU control block created 




SNA: 247 – No TGCB created: Too many or no memory 




SNA: 263 - TG=index#: ILM port detached 

Description: This message occurs as a result of errors or events in the ILM. The # is 

a TG index number. Correct the ILM problem. 

SNA: 264 - TG=index#: Unsupported level of ILM microcode 

Description: This message occurs as a result of mismatched ILM microcode levels. 

The # is a TG index number. Correct the ILM microcode levels. 

5–92 7436 0728–303

SNA: 265 - TG=index#: TG sweep failure 





SNA: 403 – Insufficient SSCP resources 



conversing with other SSCPs in the process of establishing sessions. The probable 


SNA: 404 – No SSCP resources to continue sess establishment 





SNA: 405 – No SSCP resources to terminate session 





SNA: 406 – No SSCP resources to continue queued sess estab 





SNA: 414 – Correlation Table/Link Error 





SNA: 415 – Invalid NAU function code FC= %%%% EA= &&&& 



conversing with other SSCPs in the process of establishing sessions. The FC is the 

invalid function code, % presents a hexadecimal number, EA is the element address, 

and & represents a decimal number. The probable cause is a software problem. 

7436 0728–303 5–93


SNA: 416 – Invalid NAU STEX STEx=%%%% EA=&&&& 



conversing with other SSCPs in the process of establishing sessions. The STEX is the 

symbol table entry index, % represents a hexadecimal number, EA is the element 

address, and & represents a decimal number. The probable cause is a software 

problem. 

SNA: 417 – Invalid NAU Type Type=%%%% EA=&&&& 



conversing with other SSCPs in the process of establishing sessions. The type is the 

NAU type, % represents a hexadecimal number, EA is the element address, and & 

represents a decimal number. The probable cause is a software problem. 

SNA: 418 – NOTIFY Table Full EA=&&&& 



conversing with other SSCPs in the process of establishing sessions. The EA is the 

element address and & represents a decimal number. The probable cause is a 


SNA: 419 – CDRM Pacing queue full SA = &&&& 



conversing with other SSCPs in the process of establishing sessions. The & 


SNA: 421 – Unable to locate CDRMCB (&&&&&/&&&&) 




represents a decimal number. The probable cause is a configuration problem. 

SNA: 422 – Unable to allocate CDRM segment 





5–94 7436 0728–303

SNA: 423 – Invalid CDRM State (&&&&&/&&&&) 





represents a decimal number. The probable cause is a configuration problem. 

SNA: 424 – Unable to locate PCID: %%%%%%%%%%%%%%%% 



conversing with other SSCPs in the process of establishing sessions. The % represents 

a hexadecimal number. The probable cause is a configuration problem. 

SNA: 430 – Unable to locate Session Procedure 





SNA: 431 – Unable to Send Cross Domain Message (&&&&&/&&&&) 





SNA: 434 – No CT Entry Found SNF=&&&&& PSA=&&&&& 

PEA=&&&&& 



conversing with other SSCPs in the process of establishing sessions. The PSA is the 

partner subarea, PEA is the partner element address, and & represents a decimal 


SNA: 438 – Unable to locate queued session YEA = &&&&& 



conversing with other SSCPs in the process of establishing sessions. The YEA is your 

element address and & represents a decimal number. The probable cause is a 


7436 0728–303 5–95


SNA: 439 – Unable to locate queued session NAU=@@@@@@@@ 



conversing with other SSCPs in the process of establishing sessions. The @ 

represents an ASCII character. The probable cause is a software problem. 

SNA: 440 – Unable to Terminate Third Party Session 





SNA: 441 – Unable to Find Queued Sess–PCID: 

%%%%%%%%%%%%%%%% 




a hexadecimal number. The probable cause is a software problem. 

SNA: 449 – SNASS Cenlog number skipped n times 




The CENLOG number indicated has been skipped in the interest of brevity since no 

additional useful information is contained in them. This message is informational 

only. 

SNA: 1034 – BF debug %%%% %%%% %%%% %%%% %%%% 

%%%% %%%% %%%% 




SNA: 1200 – Initialization Incomplete 

Description: This message occurs as a result of errors in the network packetswitching 

interface (NPSI) that SNA/net uses to communicate with terminals and 

other subareas across X.25 networks. The probable cause is a software problem. 

5–96 7436 0728–303

SNA: 1203 – Input Message Lost 





SNA: 1204 – Output Message Lost 




SNA: 1223 – Data Received In Wrong State 




SNA: 1225 – No Resources Available 

Description: The following message occurs as a result of errors in the network 

packet-switching interface (NPSI) that SNA/net uses to communicate with terminals 

and other subareas across X.25 networks. The probable cause is a software problem. 

SNA: 1226 – Local Procedure Error 

Description: This message occurs as a result of errors in NPSI that SNA/net uses to 

communicate with terminals and other subareas across X.25 networks. 

SNA: 1602 – Unsupported DTPX control msg rcv, type = x%%%% 



physically adjacent. The type is a DTPX control message type and % represents a 

hexadecimal number. For more information refer to the Telcon Programming 

Reference Manual (7430 0710). The probable cause is a software problem. 

SNA: 1607 – Link state = &&, and rcv connect confirm 



physically adjacent. The & represents a decimal number. The probable cause is a 


7436 0728–303 5–97


SNA: 1608 – DTPLNK TG state = &&, and attempt to inact 



physically adjacent. The DTPLNK TG state is the current state of the TG. Possible 

values for the TG state are: 

0 – Down 

1 – Operational pending 

2 – Suspended 

3 – Operational 


SNA: 1609 – Link state = &&, and rcv connect reject 



physically adjacent. The link state is the current state of the link. Possible values for 

link state are: 

0 – Down 

1 – Activation pending 




6 – Inactive pending 


SNA: 1610 – Link state = &&, and rcv connect request 



physically adjacent. Possible values for link state are: 

0 – Down 







5–98 7436 0728–303


SNA: 1611 – Link state = &&, and rcv disconnect abort 




0 – Down 







SNA: 1612 – Link state = &&, and rcv disconnect confirm 




0 – Down 







SNA: 1613 – Error =x%%%% in sending request to EUSERV 



physically adjacent. The % represents a hexadecimal number. The probable cause is 


7436 0728–303 5–99


SNA: 1614 – Link state = &&, and rcv RNR 




0 – Down 







SNA: 1615 – Link state = &&, and rcv operational from TGC 




0 – Down 







SNA: 1616 – Link state = &&, and rcv message 




0 – Down 







5–100 7436 0728–303

SNA: 1617 – Link state = &&, and rcv RR 





0 – Down 







SNA: 1618 – DTPLNK TG state = &&, and msg to be sent 



physically adjacent. The DTPLNK TG state is the current state of the TG. Possible 

values for link state are: 

0 – Down 





SNA: 1619 – Link state = &&, and timer expired 




0 – Down 







7436 0728–303 5–101


SNA: 1620 – Link state = &&, and rcv UDM 




0 – Down 







SNA: 1621 – Error = x%%%% getting QL1 index 



physically adjacent. The % represents a hexadecimal number. The probable cause is 


SNA: 1622 – Link not found on DOWN of TG 



physically adjacent. The probable cause is a software problem. 

SNA: 1624 – Invalid internal name 




5–102 7436 0728–303

Section 6 


Normal connection/disconnection and sign-on/sign-off events characterize CENLOGS 

associated with class 6. 

Event 1 TERMINAL SIGN-ON 

TERMINAL SIGN-ON 

Description: This event is for accounting purposes only. A terminal has successfully 

signed on to the system. Telcon generates this CENLOG. 

LMS 

Action: None. 

Description: A terminal signed on using LMS. 


PDNURS 

TRS 

Description: The X.25 PSCS UTS 4000 Cluster and X.29 Terminal handler module 

(PDNURS) received a Telcon $$SON command for one of its terminals. This event 

includes both the LINE and TERM names. 

Attributes affected: The Terminal Control Block (TCB) address is in register R12. 

The Line Control Block (LCB) is in register R11. This CENLOG is generated by the 

X.25 PSCS program product. 

Procedure: PDNURS 

Description: TRS received a signed-off message from the PPS/VTR to deallocate 

terminal resources. 

R11: LCB 

R12: TCB 


7436 0728–303 6–1

Event 2 TERMINAL SIGN-OFF 

Event 2 TERMINAL SIGN-OFF 

TERMINAL SIGN-OFF 

Description: This event is for notification only and signifies that a valid logoff was 

received by the operating system and processed successfully. The resources for this 

terminal session have been released. The terminal should now be in a state to accept 

another logon command. Telcon generates this CENLOG. 

LMS 

Action: None. 

Description: A terminal signed off using LMS. 

PDNURS 

TRS 


(PDNURS) is in the process of signing-off one of its terminals. The reasons include a 

Telcon $$SOFF received from the terminal or some other event that has caused the 

virtual circuit connection to be cleared. This event includes both the LINE and TERM 

names. 


The Line Control Block (LCB) is in register R11. This CENLOG is generated by the 

X.25 PSCS program product. 


Description: TRS received a sign-off message from the PPS/VTR to deallocate 

terminal resources. 

R11: LCB 

R12: TCB 


6–2 7436 0728–303

Event 3 TERMINAL SIGN-ON (AUTO ALLOCATED) 

Event 3 TERMINAL SIGN-ON (AUTO ALLOCATED) 

TERMINAL SIGN-ON (AUTO ALLOCATED) 

Description: This event signifies that the terminal does not require a sign-on 

message from the terminal operator. The first user input will establish the resources 

for the terminal session and allow the user access to application. Telcon generates 

this CENLOG. 

LMS 

TRS 

Description: LMS auto-allocated a terminal. Telcon generates this CENLOG. 

Description: TRS processed an auto-sign-on terminal with the first input. Telcon 


7436 0728–303 6–3

Event 4 TERMINAL SIGN-OFF (TIME-OUT) 

Event 4 TERMINAL SIGN-OFF (TIME-OUT) 

PDNURS 


(PDNURS) is in the process of signing-off one of its terminals. The reason is because 

the terminal has timed out. This event includes both the LINE and TERM names. 


The Line Control Block (LCB) is in register R11. 


Action: No action necessary unless this was unexpected. Review the TIMEOUT 

parameter values specified on either the TERM or PRCSR statements. 

This CENLOG is generated by the X.25 PSCS program product. 

STATDCR 

TRS 

Description: Terminal sign-off (timeout). Telcon generates this CENLOG. 

Description: TRS processed a terminal timeout/deallocation request. Telcon 


6–4 7436 0728–303

Event 5 SESSION ESTABLISHMENT COMPLETED 

Event 5 SESSION ESTABLISHMENT COMPLETED 

SNA: 432 - OLU:name(Subarea/element) 

DLU:name(Subarea/element) 

Description: This messages occurs as a result of errors or events in SNASS. SNASS 

performs SSCP services for SNA/net; such as, directory lookup and conversing with 

other SSCPs in the process of establishing sessions. The OLU and DLU are the two 

SNA session partners involved in this Session Termination event. This message is 


SNA: 436 - 3rd Party Session Start LU2=@@@@@@@@ 

LU1=@@@@@@@@ 

Description: This messages occurs as a result of errors or events in SNASS. SNASS 


other SSCPs in the process of establishing sessions. The @ represents an ASCII 

character. 

7436 0728–303 6–5

Event 6 SESSION TERMINATION COMPLETED 


SNA: 433 - OLU:name(Subarea/element) 

DLU:name(Subarea/element) 



conversing with other SSCPs in the process of establishing sessions. Tthe OLU and 

DLU are the two SNA session partners involved in this Session Termination event. 

This message is informational only. 

SNA: 442 - FORCED NAU1:NA(&&&&&/&&&&) 

NAU2:NA=(&&&&/&&&&) 




represents a decimal character. This message is informational only. 

TRNG (000): HLE output buffer is formatted incorrectly 

Description: Buffer discarded. Internal error. 

Action: None. 

TRNG (001): Can’t insert Station into Ring - Hardware Error 

Description: Line cannot be initialized. Hardware error. 

Action: Fix MAU/LAN connection problem. 

TRNG (002): Station inserted into Token Ring 

Description: Line is initialized. 

Action: None. 

TRNG (003): Registration with DLCMAN complete 

Description: LPIA is ready for line initialization. 

Action: None. 

6–6 7436 0728–303

TRNG (004): Registration with DLCMAN failed 

Description: Line cannot be initialized. Internal error. 

Action: Submit a UCF with a dump of the ILM. 


TRNG (005): Unexpected output QLX on dispatch 



TRNG (006): Unsupported Set/Get attributes request 

Description: Request discarded. Internal error. 

Action: None. 

TRNG (007): Unsupported DLCMAN request (discarded) 

Description: Request discarded. Internal error. 

Action: None. 

TRNG (009): Input Frame has invalid RIF length 

Description: Message discarded. Message error. 

Action: None. 

TRNG (011): LLC input frame too short (discarded) 


Action: None. 

TRNG (012): Can’t queue UI frame to HLE 



TRNG (013): Discarding a too short LLC2 I-frame 


Action: None. 

7436 0728–303 6–7


TRNG (014): Can’t queue I-frame to HLE 



TRNG (015): Invalid LLC control field in input frame 


Action: None. 

TRNG (017): Can’t queue Control Frame to HLE 



TRNG (018): Can’t queue loopback input frame 



TRNG (019): Non-LLC input frame discarded 


Action: None. 

TRNG (020): Station detects ring fault - Recovering with beacon 

frame 

Description: Ring reinitializes. Hardware error. 

Action: None. 

TRNG (021): Station received beacon frame - Recovering from ring 

fault 

Description: Ring should reinitialize. Informational only. 

Action: None. 

6–8 7436 0728–303


TRNG (022): Station detects signal loss - Lobe cable fault or H/W err 

Description: Line not operational. Hardware error. 

Action: Correct lobe fault. 

TRNG (023): Ring/Hardware event (event code in supplemental msg) 

Description: Ring not operational. Hardware error. 

Action: Correct hardware fault. 

TRNG (024): Ring Input frame discarded - unexpected MTF 


Action: None. 

TRNG (025): No active Stn for Ring Input - frame discarded 

Description: Line is not operational. Internal error. 

Action: Down and then up the line. 

TRNG (026): Ring Input frame too large - frame discarded 


Action: None. 

TRNG (027): “ ) ; 


Action: None. 

TRNG (029): Can’t queue output to device driver 

Description: Message discarded. Internal error. 


TRNG (030): Tried to send output that was LLC1 but Non-addressing 


Action: Submit a UCF to HLE. 

7436 0728–303 6–9


TRNG (031): HLE output - no StationCB active (discarded) 

Description: Line is down. Internal error. 

Action: Submit a UCF to HLE. 

TRNG (033): UserIA sent invalid BH$ Control output 


Action: Submit a UCF to UserIA. 

TRNG (034): Loopback output frame too short 

Description: Buffer discarded. Internal error. Possible hardware error. 

Action: None. 

TRNG (035): Invalid ouput FUI/DUI RIF length 


Action: Submit a UCF with a type code of HLE. 

TRNG (036): Non-LLC HLE output (config error) 

Descripton: Message discarded. Configuration error. 

Action: Correct your HLE configuration. 

TRNG (043): Station inserted into Token Ring 

Description: Line is initialized. 

Action: None. 

TRNG (044): Can’t insert Station into Ring - Driver Init Error 

Description: Line is not initialized. Internal error. 


TRNG (045): Can’t insert Station in Ring - Two Stations have same Adr 

Descripton: Two or more stations on the ring have the same address. 

Action: Correct the station configurations. 

6–10 7436 0728–303


TRNG (046): Can’t insert Station into Ring - Driver List Size Error 



TRNG (047): Can’t insert Station into Ring - Driver Buffer Size Error 



TRNG (048): Can’t insert Station into Ring - Driver Xmit Buf’r Cnt Err 



TRNG (049): Can’t insert Station into Ring - Invalid Open Options 



TRNG (050): Can’t insert Station in Ring - Reason code in next Cenlog 



TRNG (051): Can’t Open Token Ring Driver - Line already in use 



TRNG (052): Token Ring Driver Open - Inserting Station into Ring 

Description: Station attempting to insert into ring. Informational only. 

Action: None. 

TRNG (053): Can’t Open Token Ring Driver - Line doesn’t exist 



7436 0728–303 6–11


TRNG (054): Can’t Open Token Ring Driver - Unknown problem 



TRNG (055): Cannot open another connection due to no table space 

Description: Connection is not opened. Internal error. 


TRNG (057): Can’t queue UDM to HLE’s UDM queue 

Description: Message discarded. Internal error. 


TRNG (058): Station removed from Ring - H/W lobe cable fault 

Description: Line is not operational. Hardware error. 

Action: Correct lobe error. 

TRNG (059): Station removed from Ring - Auto remove err-lobe wrap 

fail 

Description: Line will not be operational. Hardware error. 


TRNG (060): Station removed from Ring - Remove MAC frame 

received 

Description: Line is not operational. Informational only. 

Action: None. 

6–12 7436 0728–303

TRNG (061): Station removed from Ring - xxxx 

where xxxx is: 

Unknown H/W problem 

H/W invalid XOP 

H/W invalid E-int’rupt 

H/W invalid interrupt 


H/W ring underrun 

H/W RAM parity error 

H/W RAM data error 




H/W parity error 

H/W illegal Op-code 

H/W DMA write abort 

H/W DMA read abort 

H/W DIO parity error 


Description: Message discarded. Informational/Hardware. 

Action: If problem persists, submit a UCF with a dump of the ILM. 

TRNG (062): Can’t insert Station into Ring - H/W lobe cable 

Description: Line is not operational. Hardware error. 


TRNG (063): Can’t insert Station into Ring - Auto removal error 


Action: None. 

TRNG (064): Can’t insert Station into Ring - Remove MAC frame 

received 


Action: None. 

7436 0728–303 6–13


TRNG (065): Can’t insert Station into Ring - xxxx 

where xxxx is: 


H/W invalid XOP 

H/W invalid E-int’rupt 

H/W invalid interrupt 


H/W ring underrun 

H/W RAM parity error 

H/W RAM data error 




H/W parity error 

H/W illegal Op-code 

H/W DMA write abort 

H/W DMA read abort 

H/W DIO parity error 

Description: Message discarded. Informational/Hardware. 

Action: If problem persists, submit a UCF with a dump of the ILM. 

TRNG (066): SAI Up signal sent to HLE 

Description: Connection is going active. Informational only. 

Action: None. 

TRNG (067): SAI Down signal sent to HLE 

Description: Connection is going active. 

Action: None. 

TRNG (068): Set multicast address request received 

Description: Multicast address will be filtered by LPIA. 

Action: None. 

TRNG (069): Input frame has incorrect RIF length 


Action: None. 

6–14 7436 0728–303

Event 7 LINE CONNECTION COMPLETED 


LINE CONNECTION COMPLETED 

Description: This event records that a physical connection has been made for this 

line. In a dial-up line, or directly connected line, this event signifies that the DCP 

hardware detected a data-set-ready lead and that a log on can now be made from the 

terminal. Telcon generates this CENLOG. 

LMS 

Action: None. 

Description: LMS was notified by the link of a line connection. Telcon generates 

this CENLOG. 

PDNSVS 

TRS 

Description: The X.25 line initialization module has successfully completed the 

physical connection of the line. This event includes the LINE name. 

Attributes affected: Line event, Line Control Block (LCB) address in Register R11. 

This CENLOG is generated by the X.25 PSCS program product. 

Procedure: PDNSVS 

Description: Data set ready (line connection) was detected and processed by the 

LPHTRS. 

R11: LCB. 


7436 0728–303 6–15


UDLCRS 

Description: R8 = 0039. AE$UD100. (UDLC): The UDLC line is successfully 

connected for a dedicated line, or a switched line connected to the XID frame from 

the remote station identified a DCP or a TS. In a dial-out line, the call to the remote 

station completed successfully. The following categories of event codes specify line 

events. The line is a UDLC line, as defined by a Telcon line configuration statement. 

Necessary information tables and control tables are accessed to build the LCB and 

SCB within the PP fixed space (PPF) segment. 

132–136, 340, 341: Specify a logical line connection failure even though the 

line is physically connected. 

139, 140, 143–151, 386, 387: Specify line disconnection. 

152, 153, 403: Specify line errors that may be tried again (overrun, 

underrun, carrier off). 

R8: Contents of LC$TLF field in LCB. The LC$T equates are defined in 

AAHARDEF. 

R9: If the configuration error attribute attends the event, the configuration access 

(CFACCS) error code is placed in R9. 

R10: Contents of the SC$STM field in the first SCB in the LCB 


R12: Pseudo TCB address so that the STE index to the high-level information table 

can be supplied as though it were the STE index to the terminal information 

table. 

R13: If a line event due to a line hardware error, R13 contains the SDT chain 

completion status. R14:LINE-ID. 

R15: Number of connected lines in a line group. A line group can be (1) a trunk of 

one or more lines connecting two Telcon nodes, (2) a dedicated line or a 

switched backup line connecting a host, or (3) a single line connecting one or 

more terminals. 


6–16 7436 0728–303

Event 8 LINE DISCONNECTION COMPLETED 


LINE DISCONNECTION COMPLETED 

Description: The physical line has been disconnected from the DCP and the line 

resources deallocated. Telcon generates this CENLOG. 

Action: None. 

BSC LPH 

Description: Generated when the BSC LPH receives a status from the IOP indicating 

loss of data-set-ready. This causes the BSC site to be terminated. 

R8: The flag word for the BSC LPH. The exact meaning of each bit can be found 

in the assembly of AAHARDEF. It contains flags indicating message transfer 

state, I/O direction, site termination, and so on. 

R9: Contains the IOP status word. The exact definition can be found in the 

assembly of AAHARDEF. 

R11: The address of the LCB 

R12: The address of the TCB 

R14: The IOP ID 

LMS 


Description: LMS was notified by the link of a line disconnection. Telcon generates 

this CENLOG. 

PDNSVS 

Description: The Common Network Management Service (CNMS) X.25 interface 

module in PDNSVS received an NMS DOWN LINE indication. This event includes the 

LINE name. 


Attributes affected: Line event, Line Control Block (LCB) address may be in 

Register R11. The X.25 PSCS program product generates this CENLOG. 


7436 0728–303 6–17


TRS 

Description: TRS was called to deallocate a disconnected line. 

R11: LCB 

R14: IOPID 


UDLCRS 

Description: R8=0016. AE$UD133. (UDLC): LSM/RCM CONTROL LINE. The 

LSM/RCM control line has been disconnected. Telcon generates this CENLOG. 

UDLCRS 

Description: R8=0018. AE$UD132. (UDLC): RESILIENT LINE IS NOW STANDBY. A 

resilient UDLC line has been disconnected because system resiliency control has 

requested it to become dormant. Telcon generates this CENLOG. 

6–18 7436 0728–303

Event 9 IPM EVENT 

IPM EVENT 


Description: An event occurred concerning an interprogram message (IPM) queue 

and may have involved two independent Telcon runs. Telcon generates this CENLOG. 

Action: None. 

DTPIPM - INITIALIZATION ERROR 

Description: DTPIPM failed IPM registration because there is a duplicate IPM 

receiver name. This can occur when multiple Telcons are executed with the same 

node ID. Telcon generates this CENLOG. 

Action: Change the node ID on the Telcon execution statement. 

DUPLICATE NODEID DETECTED BY NMSOS 

Description: The DCP is running multiple Telcons. Your Telcon has a duplicate 

node ID specified on the Telcon execute statement, or no node ID specified. If no 

node ID was specified, your Telcon is running with the default node ID (N1) and 

another Telcon is also running with the default node ID. Telcon generates this 

CENLOG. 

Action: None, unless IPPs are configured. If IPPs are configured, restart Telcon and 

use a unique node ID on the Telcon execute statement. 

NMSOS 

Description: This event occurs when a duplicate node ID is detected (Telcon 

execute statement). Telcon generates this CENLOG. 

7436 0728–303 6–19


X.25 SNMP: Received non-connect IPM Contingency (“procedure 

name”) 

Description: The X.25 PSCS SNMP interface module (PDNSMP) received an interprogram 

message (IPM) contingency that is not related to the disconnection of a 

pending or existing ICS connection. This type of IPM contingency causes PDNSMP to 

re-initialize its connections with ICS and the SNMP Agent’s manager-agent user 

interface. 

R8: IPM contingency type 


Procedure: The procedure name, which is internal to the X.25 PSCS PDNSMP 


Action: PDNSMP should automatically recover from this event. However, 

subsequent occurances indicate an error with either DCP/OS, ICS, or PDNSMP. In 

this case, you should take a Telcon dump and submit a UCF. 

X.25 SNMP: IPM queue registration error (“procedure name”) 


register one of its inter-program message (IPM) queues. This error causes PDNSMP to 

become dormant. In this case, no SNMP MIB information related to X.25 can be 

retrieved. 


IPM Channel (queue) table. 



Action: You must re-start Telcon in order to recover from this error. Subsequent 

occurances indicate and error with either DCP/OS, ICS, or PDNSMP. In this case, you 

should take a Telcon dump and submit a UCF. 

6–20 7436 0728–303

Event 10 SESSION CONNECTION FAILED 

Event 10 SESSION CONNECTION FAILED 

SESSION CONNECTION FAILED 

Description: An event occurred concerning an interprogram message (IPM) queue 

and may have involved two independent Telcon runs. Telcon generates this CENLOG. 

Action: None. 

7436 0728–303 6–21

Event 11 ILM EVENT 


ASYNC (001): Error on getting queued message event 

Description: Potential software error. The asynchronous-to-UTS converter 

component of the ILM software generates this CENLOG. 

Action: Call the Unisys support representative. 

ASYNC (002): ILM management packet rejected 




ASYNC (003): ILM attach response not accepted 




ASYNC (004): ILM service request not accepted 




ASYNC (005): Invalid number of load elements 




ASYNC (006): Invalid ilmcfg data for line 

Description: Configuration error. The asynchronous-to-UTS converter component 

of the ILM software generates this CENLOG. 

Action: Correct the ILMCFG file element for the line. 

6–22 7436 0728–303

ASYNC (007): Incorrect imode in ilmcfg data 


Description: Configuration error. The asynchronous-to-UTS converter component 

of the ILM software generates this CENLOG. 

Action: Correct the IMODE parameter in the ILMCFG file element for the line. 

ASYNC (008): Output received without request code 




ASYNC (009): Output packet rejected 




ASYNC (010): Configuration packet rejected 




ASYNC (011): Output data not in expected format 




ASYNC (012): Message header not freed 




7436 0728–303 6–23


ASYNC (013): Buffer not freed 




ASYNC (014): Message not freed 




ASYNC (015): Message type error 




ASYNC (016): Get lcb error for line 




ASYNC (017): Link write request reject status = -x 




ASYNC (018): No packet header for CP input 




6–24 7436 0728–303

ASYNC (019): Input error - parity, etc. 


Description: Potential configuration error. The asynchronous-to-UTS converter 


Action: Verify that line configuration agrees with (for example, speed and parity) the 

operator setup for the terminal before calling the Unisys support representative. 

ASYNC (020): Maximum consecutive I/O errors 

Description: Potential configuration error. The asynchronous-to-UTS converter 


Action: Verify that line configuration for speed, parity, and so on agrees with the 

operator setup for the terminal before calling the Unisys support representative. 

ASYNC (021): Input accumulation error 




ASYNC (022): Output accumulation error 




ASYNC (023): Send to destination error 




ASYNC (024): Send output error 




7436 0728–303 6–25


ASYNC (025): Segment not allocated 




ASYNC (026): Segment not freed 




ASYNC (027): Source message not present 




“BLOK (001) SU 212 Channel Registered with Platform” 

Description: The BLOCK MUX IA registered itself with the ILM platform and with 

DLCMAN. This CENLOG is generated by the BLOK link provider interface application 

(LPIA) for the ILM software. 

“BLOK (002) SAI UP FAILED” 

Description: An error occurred that prevented the IA from sending a Link Active 

command to HLE. 

“BLOK (003) SAI Up Sent to HLE's” 

Description: The HLE data path is now available. 

“BLOK (005) SAI Down Sent to HLE's” 

Description: The HLE data path is now blocked. 

“BLOK (006) bmo2drv put failed” 

Description: An error occurred that prevented the LPIA from sending data to the 

host interface. 

6–26 7436 0728–303

“BLOK (007) Write DATA put Queue Failed” 


Description: An error occurred that prevented the LPIA from sending data to the 

HLE interface. 

“BLOK (008) No HLE Input QUEUE defined For a SNA Message” 

Description: There is no HLE interface defined for this data. 

“BLOK (009) No HLE Input STATION defined For a SNA Message” 

Description: There is no station defined for this data. 

“BLOK (010) I/O Open Failed” 

Description: An error occurred that prevented the IA from starting the host 

interface. 

“BLOK (011) Write XID put queue Failed” 

Description: An error occurred that prevented the LPIA from sending XID data to 

the HLE interface. 

“BLOK (013) No SNA Control Queue defined” 

Description: There is no control queue defined for SNA user IA. 

“BLOK (014) Connect Put Queue Failed” 


“BLOK (015) No SNA Control Queue Defined” 


“BLOK (100) FATAL ERROR-UNEXPECTED SERVICE IN RESPONSE 

INTERRUPT” 

Description: An illegal and unexpected event occurred on the channel interface. 

“BLOK (101) FATAL ERROR-UNEXPECTED PROCEED INTERRUPT” 

Description: An illegal and unexpected event occurred on the channel interface. 

7436 0728–303 6–27


“BLOK (102) FATAL ERROR-DMA2 ERROR” 

Description: The host read Direct Memory Access (DMA) channel was initialized 

incorrectly. 

“BLOK (103) FATAL ERROR-DMA3 ERROR” 

Description: The host write Direct Memory Access (DMA) channel was initialized 

incorrectly. 

“BLOK (104) FATAL ERROR-INVALID DMA STOP INTERRUPT” 

Description: The Direct Memory Access (DMA) controller malfunctioned. 

“BLOK (105) FATAL ERROR-INVALID RESET OCCURRED” 

Description: A channel reset occurred without proper interface sequencing. 

“BLOK (106) SYSTEM RESET OCCURRED” 

Description: The host presented a system reset to the line module. 

“BLOK (107) SELECTIVE RESET OCCURRED” 

Description: The host presented a selective reset to the line module. 

“BLOK (108) INTERFACE DISCONNECT OCCURRED” 

Description: The host disconnected the channel interface. 

“BLOK (109) FREE_MSG CALL UNSUCCESSFUL” 

Description: The driver attempted to free a platform message but was unsuccessful. 

“BLOK (110) GET_Q CALL UNSUCCESSFUL” 

Description: The driver attempted to get a message from a queue but was 

unsuccessful. 

“BLOK (111) GET_Q_COUNT CALL UNSUCCESSFUL” 

Description: The driver attempted to get a count of the messages on a queue but was 

unsuccessful. 

6–28 7436 0728–303

“BLOK (112) PUT_Q CALL UNSUCCESSFUL” 

Description: The driver attempted to put a message on a queue but was 

unsuccessful. 

“BLOK (113) DRIVER CRASHED” 


Description: The driver detected a fatal error and called the platform crash function. 

“BLOK (115) RESET COMPLETED” 

Description: The driver completed a reset command from the IA. 

“BLOK (116) OPEN FAILED - INVALID DEVICE ADDRESS” 

Description: The IA sent an open command with an invalid device address. 

“BLOK (117) OPEN FAILED - LINE MODULE OFFLINE” 

Description: The IA sent an open command but the line module bulkhead switch is 

offline. 

“BLOK (118) OPEN FAILED - QUEUE INDEX NOT SPECIFIED” 

Description: The IA sent an open command without a valid queue index. 

“BLOK (119) OPEN SUCCESSFUL” 

Description: The IA sent an open command which was successfully completed. 

“BLOK (120) CLOSE STARTED” 

Description: A close command from the IA has been started. 

“BLOK (122) CONTROL FAILED - COMMAND NOT SUPPORTED” 

Description: A control command was received from the IA with a command code 

that is not supported. 

“BLOK (130) OPEN FAILED, ANOTHER LINE ALREADY OPENED” 

Description: An open command was received from the IA but another line is already 

open. 

7436 0728–303 6–29


“BLOK (131) CLOSE SUCCESSFUL” 

Description: The driver successfully completed a close command from the IA. 

“BLOK (132) FREE_MSG NOT SUCCESSFUL, -INVALID-” 

Description: A free message call was unsuccessful because the message header 

address was invalid. 

“BLOK (133) FREE_MSG NOT SUCCESSFUL, -NOT OWNED-” 

Description: A free message call was unsuccessful because the message was not 

owned by the driver. 

“BLOK (134) DELETE_P CALL (LINE CLOSING) NOT SUCCESSFUL” 

Description: The delete_p (delete process) call during line closure was not 

successful. 

“BLOK (135) CREATE_APP CALL (LINE OPENING) NOT SUCCESSFUL” 

Description: The create_app call during line opening was unsuccessful. 

“BLOK (136) CREATE_P CALL (LINE OPENING) NOT SUCCESSFUL” 

Description: The create_p (create process) call during line opening was 

unsuccessful. 

“BLOK (137) CREATE_QL CALL (LINE OPENING) NOT SUCCESSFUL” 

Description: The create_ql (create queue list) call during line opening was 

unsuccessful. 

“BLOK (138) ADD_TO_LIST (LINE OPENING) NOT SUCCESSFUL” 

Description: The add_to_list call during line opening was unsuccessful. 

“BLOK (139) GET_Q_HANDLE (LINE OPENING) NOT SUCCESSFUL” 

Description: The get_q_handle call during line opening was unsuccessful. 

“BLOK (140) DELETE_APP_CALL (LINE OPENING) NOT SUCCESSFUL” 

Description: The delete_app call during line opening was unsuccessful. 

6–30 7436 0728–303


“BLOK (141) GET_Q_CALL (LINE OPENING) NOT SUCCESSFUL” 

Description: The get_q call during line opening was unsuccessful. 

“BLOK (142) ADD_TO_LIST CALL (LINE CLOSING) NOT SUCCESSFUL” 

Description: The add_to_list call during line closing was unsuccessful. 

“BLOK (143) **********MESSAGE FREED**********” 

Description: A message was freed during line closure. 

“BLOK (144) CONTACT COMMAND RECEIVED” 

Description: A contact command was received from the host. 

“BLOK (145) ********DISCONTACT COMMAND 

RECEIVED********” 

Description: A discontact command was received from the host. 

“BLOK (146) FREE_BUFFER NOT SUCCESSFUL, -INVALID-” 

Description: A free_buffer call was attempted with an invalid buffer address. 

“BLOK (147) FREE_BUFFER NOT SUCCESSFUL, -NOT OWNED-” 

Description: A free_buffer call was attempted for a buffer not owned by the driver. 

DLCMAN (001): Invalid packet on att/det queue 

Description: A packet type other than an Attach/Detach request was found on the 

Attach/Detach queue. This request packet is discarded. Software error (warning). 

The data link control manager service module that maintains the interfaces to the link 

providers generates this CENLOG. 

DLCMAN (002): ACL entry already in use 

Description: A duplicate attachment was requested. The request was rejected. 

Software error (warning). The data link control manager service module that 

maintains the interfaces to the link providers generates this CENLOG. 

7436 0728–303 6–31


DLCMAN (003): ILMATT recovery failed 

Description: The ILM platform rejected an ILMATT service call. The attachment 

failed. Software error (warning). The data link control manager service module that 


DLCMAN (004): Open Output queue failed 

Description: The allocation of an output queue failed. The attachment is rejected. 



DLCMAN (005): No LCB exists for output attachment 

Description: An LCB does not exist for the attachment. Informational (warning). 



DLCMAN (006): ILMATT call failed 




DLCMAN (007): ILMATT recovery attempt failed 

Description: The recovery attempt for the ILMATT call failed. The attachment 



DLCMAN (008): ACL entry already in use 

Description: A duplicate attachment was requested. The attachment was rejected. 



DLCMAN (009): ILMATT recovery failed 

Description: The recovery attempt on the ILMATT call failed. The attachment was 

rejected. Software error (warning). The data link control manager service module 

that maintains the interfaces to the link providers generates this CENLOG. 

6–32 7436 0728–303

DLCMAN (010): No buffer to send Set Station primitive 


Description: No buffer is available to send primitive to Link Provider. The primitive 

was not sent and the request was rejected. Resource shortage (warning). The data 

link control manager service module that maintains the interfaces to the link 


DLCMAN (011): ILMATT call failed 


was rejected. Software error (warning). The data link control manager service 

module that maintains the interfaces to the link providers generates this CENLOG. 

DLCMAN (012): ILMATT recovery attempt failed 

Description: The recovery attempt on ILMATT service call failed. The attachment 



DLCMAN (013): ACL entry not in use 

Description: A detach request was received for a non-existent attachment. 

Informational (warning). The data link control manager service module that 


DLCMAN (014): ILMATT detach call failed 

Description: The ILM platform rejected an ILMATT service call but the detach still 

completed. Software error (warning). The data link control manager service module 


DLCMAN (015): Wrong 'out_q handle' for close queue 

Description: Software error (warning). The data link control manager service 


DLCMAN (016): ILMATT rejected detach confirm 



DLCMAN (017): Wrong attach table entry 



7436 0728–303 6–33


DLCMAN (018): No valid packet found in NMS message 



DLCMAN (019): No packet found in message 



DLCMAN (020): Invalid Qlx received 



DLCMAN (021): Packet received on invalid qlx 



DLCMAN (022): Unrecognizable DLC packet 



DLCMAN (023): Unrecognizable DLC command 



DLCMAN (024): Invalid Packet Type received 



DLCMAN (025): Invalid message type received 



DLCMAN (026): Invalid User packet type on primitive queue 



6–34 7436 0728–303








DLCMAN (029): No STACB pointer in User packet 



DLCMAN (030): No Station CB pointer in User packet 



DLCMAN (031): LPIA failed to close station 



DLCMAN (032): LPIA rejected Set/Get attributes command 



DLCMAN (033): Set Station Attributes complete 



DLCMAN (034): No LSAP CB pointer in User packet 



DLCMAN (035): Link Provider failed to close LSAP 



7436 0728–303 6–35


DLCMAN (036): No Connect CB pointer in User packet 



DLCMAN (037): Link Provider failed to close connection 



DLCMAN (038): Unknown primitive received from LPIA 



DLCMAN (039): Invalid User packet primitive queue 



DLCMAN (040): Response text length exceeds maximum 



DLCMAN (041): NMS response rejected by ILM platform 



DLCMAN (042): No LPIA queue for output 



DLCMAN (043): Can't allocate Trunk Table 



DLCMAN (044): 'alloc_msg' failed 



6–36 7436 0728–303

DLCMAN (045): 'alloc_hdr' failed on user primitive 




DLCMAN (046): put_q failed on user primitive 



DLCMAN (047): IA registration error: Bad Q hdl 



DLCMAN (048): 'alloc_msg' failed on CPU indication 



DLCMAN (049): No Connection control block space 



DLCMAN (050): Cannot allocate message space 



DLCMAN (051): Restart Message w/o Station CB ptr 









7436 0728–303 6–37


DLCMAN (200): Link Provider IA rejected Open Line Request 



DLCMAN (201): OPEN Line complete 



DLCMAN (202): Requested Link Provider not registered 



DLCMAN (203): Requested line still in use. 



DLCMAN (204): Open of priority line queue failed 



DLCMAN (205): Allocate of LCB failed 



DLCMAN (206): Open of line's output queue failed 



DLCMAN (207): Add of output queue to QL failed 



DLCMAN (208): Link Provider IA rejected Open Line Request 



6–38 7436 0728–303

DLCMAN (209): OPEN Line complete 







DLCMAN (211): Invalid multi-line number in user request 

Description: A user or peer IA requested an operation to be performed on an illegal 

multi-line number. The data link control manager service module that maintains the 

interfaces to the link providers generates this CENLOG. 

DLCMAN (212): Requested line still in use 

Description: A request was made to open a line that is already in use. The data link 

control manager service module that maintains the interfaces to the link providers 



Description: DLCMAN requested the ILM Platform to allocate an LCB but no 

memory space was available. The data link control manager service module that 


DLCMAN (214): Unrecognized User Name on usrAllocStaReq 

Description: A user or peer IA requested a service without properly identifying itself. 



DLCMAN (215): Link Provider IA rejected Alloc Line Request 

Description: A link provider IA rejected a request to allocate a line. The data link 



DLCMAN (216): ALLOC Line complete 

Description: A link provider has successfully completed its allocated line 

requirements. The data link control manager service module that maintains the 


7436 0728–303 6–39


DLCMAN (217): Invalid multi-line number in request 

Description: A user or peer IA requested an operation to be performed on an illegal 

multi-line number. The data link control manager service module that maintains the 


DLCMAN (218): Requested LPIA not registered 

Description: A service was requested from a non-existent LPIA. The data link 



DLCMAN (219): Requested line still in use 

Description: A request was made to open a line that is already in use. The data link 



DLCMAN (220): Open of line's priority line queue failed 

Description: DLCMAN cannot open a queue to an LPIA. The data link control 

manager service module that maintains the interfaces to the link providers generates 

this CENLOG. 


Description: DLCMAN requested the ILM Platform to allocate an LCB but no 

memory space was available. The data link control manager service module that 


DLCMAN (222): Open of line's output queue failed 

Description: DLCMAN cannot open a queue to an LPIA. The data link control 


this CENLOG. 

DLCMAN (223): Add Output Queue to QL failed 

Description: DLCMAN cannot add a line queues to QL. The data link control 


this CENLOG. 

DLCMAN (224): Unable to open line's UDM queue 

Description: DLCMAN is unable to open lines on the UDM queue. Open line 

processing will not continue. The data link control manager service module that 


6–40 7436 0728–303

DLCMAN (225): Unable to open Loop Input queue 


Description: DLCMAN is unable to open queues for loop-back testing. Loop request 

is denied. The data link control manager service module that maintains the interfaces 

to the link providers generates this CENLOG. 

DLCMAN (226): CLOSE Line complete 

Description: DLCMAN indicated that the line facility close is complete. The data 



DLCMAN (227): Requested LPIA not registered 

Description: DLCMAN received a command for which there is no target IA. The 

command is rejected. The data link control manager service module that maintains 

the interfaces to the link providers generates this CENLOG. 

DLCMAN (228): CLOSE Line pending 

Description: DLCMAN forwarded a down line request to the appropriate LPIA. The 

data link control manager service module that maintains the interfaces to the link 



Description: DLCMAN received confirmation from an LPIA indicating line down 

processing is complete. The data link control manager service module that maintains 











Description: DLCMAN received confirmation from an LPIA indicating line down 

processing is complete. The data link control manager service module that maintains 


7436 0728–303 6–41










DLCMAN (236): CLOSE Line Ind w/o LCB pointer 

Description: DLCMAN received a close line indication from an LPIA that did not 

contain a proper control block pointer. The data link control manager service module 


DLCMAN (237): No CB pointer in SET Station Ind 

Description: DLCMAN received a set station attributes indication from an LPIA that 

did not contain a proper control block pointer. The data link control manager service 


DLCMAN (238): No Information buffer in SET Station Indication 

Description: DLCMAN received an incomplete set station attributes indication from 

an LPIA. The data link control manager service module that maintains the interfaces 


DLCMAN (239): Invalid Set Station Indication received 

Description: DLCMAN received an incomplete set station attributes indication from 



DLCMAN (240): Set MCA failed - invalid Line STEX 

Description: DLCMAN is unable to set a multicast address due to incorrect primitive 

information. The data link control manager service module that maintains the 


DLCMAN (241): Set MCA failed - no LCB allocated 

Description: DLCMAN is unable to set a multicast address because no line is active 

for multicast messages. The data link control manager service module that maintains 


6–42 7436 0728–303


DLCMAN (242): Set Repeating Message failed - invalid STEX 




DLCMAN (243): Set Repeating Message failed - no LCB 




DLCMAN (244): Set Repeating Message failed - no ConnCB 

Description: DLCMAN is unable to set repeating messages because the requested 

connection is not active. The data link control manager service module that maintains 


DLCMAN (245): Set Repeating Message failed - t/o < 2 seconds 

Description: DLCMAN is unable to honor a repeating message because the time is 

less than 2 seconds. The data link control manager service module that maintains the 


DLCMAN (246): Set Repeating Message failed - no table space 

Description: DLCMAN is unable to honor a request because no table space can be 

allocated. The data link control manager service module that maintains the interfaces 


DLCMAN (247): Set Repeating Message failed - Msg table full 

Description: DLCMAN is unable to honor a request because a maximum number of 

messages is already active. The data link control manager service module that 


DLCMAN (248): Set Repeating Message failed - no buffer space 

Description: DLCMAN is unable to honor a request because no table space can be 

allocated. The data link control manager service module that maintains the interfaces 


DLCMAN (249): Set Repeating Message Complete 

Description: DLCMAN successfully handled a repeating request. The data link 



7436 0728–303 6–43


DLCMAN (252): Cancel MCA failed - no MCA table 

Description: DLCMAN received a request to cancel an MCA. There was no MCA 

table allocated for the line to which the request was directed. 

DLCMAN (253): Set MCA failed - unable to allocate table 

Description: DLCMAN received a request to set an MCA. DLCMAN was not able to 

allocate an MCA table for MCA maintenance for the requested line. 

DLCMAN (254): Set MCA failed - no available entries 

Description: DLCMAN received a request to set an MCA. The MCA table is full. 

DLCMAN (255): LANMCA configuration access failed 

Description: DLCMAN was not able to access the Telcon configuration to read the 

LANMCA configuration statement for a line. 

DLCMAN (300): Requested line is not active 

Description: DLCMAN received a request for a facility that is not available. The data 



DLCMAN (301): No Input queue exists for LSAP 

Description: DLCMAN is unable to honor an open LSAP request because no input 

queue is established. The data link control manager service module that maintains the 


DLCMAN (302): No Station CB for Open LSAP Request 

Description: DLCMAN is unable to honor an open LSAP request because no station 

is currently open. The data link control manager service module that maintains the 



Description: DLCMAN is unable to honor an open LSAP request because the request 

LPIA is not registered. The data link control manager service module that maintains 


6–44 7436 0728–303

DLCMAN (304): Requested HLE STE is not valid 


Description: DLCMAN is unable to match an open LSAP request with its paired HLE. 



DLCMAN (305): No LSAP CB after requeue 

Description: DLCMAN errored when checking a pending request status. The data 



DLCMAN (306): LPIA rejected Open LSAP 

Description: LPIA rejected an open of an LSAP. The data link control manager 

service module that maintains the interfaces to the link providers generates this 

CENLOG. 

DLCMAN (307): OPEN LSAP complete 

Description: Requirements for LSAP open are complete. This includes a 

confirmation from LPIA and DLCMAN. The data link control manager service module 


DLCMAN (308): Max Connections already active on LSAP 

Description: DLCMAN is unable to establish a connection because the LPIA has a 

maximum number of connections active. The data link control manager service 


DLCMAN (309): No Connect CB after re_queue 




DLCMAN (310): Requested line is not initialized 




DLCMAN (311): Requested line does not support SAPs 

Description: DLCMAN received an open SAP request for a line that does not support 

SAPs. The data link control manager service module that maintains the interfaces to 

the link providers generates this CENLOG. 

7436 0728–303 6–45


DLCMAN (312): Requested line does not support STATIONs 


stations. The data link control manager service module that maintains the interfaces 


DLCMAN (313): Invalid LSAP type requested 

Description: DLCMAN received an invalid LSAP request. The data link control 


this CENLOG. 

DLCMAN (314): Unable to allocate LSAP Control Block 

Description: DLCMAN is unable to allocate an LSAP CB. The request is rejected. 




Description: DLCMAN is unable to make a connection because the LPIA has a 



DLCMAN (316): No Connect Control Block space can be allocated 

Description: DLCMAN is unable to honor a request because no control block space 

can be allocated. The data link control manager service module that maintains the 


DLCMAN (317): Unrecognized User Name on usrAllocSapReq 

Description: DLCMAN is unable to recognize the source of a request because the 

name in the packet is not the registered name. The data link control manager service 


DLCMAN (318): Requested multi-line number out of range 

Description: DLCMAN received a request for an illegal line number. The data link 



DLCMAN (319): Requested line is not initialized 




6–46 7436 0728–303









CENLOG. 

DLCMAN (322): User IA OPEN LSAP complete 

Description: DLCMAN opened an LSAP for a User IA. The data link control manager 


CENLOG. 

DLCMAN (323): Max Connections already active on User LSAP 

Description: DLCMAN is unable to make a connection because the LPIA has a 



DLCMAN (324): No Connect CB after re_queue 




DLCMAN (325): Requested line does not support STATIONs 


stations. The data link control manager service module that maintains the interfaces 


DLCMAN (326): Requested line does not support SAPs 




DLCMAN (327): Invalid LSAP type requested 

Description: DLCMAN received an invalid LSAP request. The data link control 


this CENLOG. 

7436 0728–303 6–47


DLCMAN (328): Unable to allocate LSAP Control Block 




DLCMAN (329): Unable to allocate User input queue 

Description: DLCMAN is unable to allocate an input queue for the user. The data 







DLCMAN (331): Unable to allocate Connect Control Block space 




DLCMAN (332): Invalid LSAP pointer LPIAs Indication packet 

Description: DLCMAN received an invalid LSAP indication from an LPIA. The data 



DLCMAN (333): Invalid Line in Users Indication packet 




DLCMAN (334): Close Connection Indication from link provider 

Description: DLCMAN received an indication from LPIA to close a connection. The 



DLCMAN (335): No LSAP Control Block after requeue 

Description: DLCMAN erred when checking a pending request status. The data link 



6–48 7436 0728–303

DLCMAN (400): Unknown User/Peer IA 





DLCMAN (401): Invalid Line number received 




DLCMAN (402): Unable to locate Station CB 

Description: DLCMAN received a primitive for which an LCB does not exist. The 



DLCMAN (403): Invalid User ID received 




DLCMAN (405): Invalid Facility ID received 

Description: DLCMAN received a primitive for which no facility exists. The data 










CENLOG. 

DLCMAN (408): No buffer to send AllocConnConf to Peer IA 

Description: DLCMAN is unable to confirm a request due to lack of memory 

resources. The data link control manager service module that maintains the 


7436 0728–303 6–49


DLCMAN (409): Connection allocated by link provider 

Description: DLCMAN received an open SAP request for a connection allocated by 



DLCMAN (410): Connection already allocated 

Description: DLCMAN received a second allocate request for the same connection. 



DLCMAN (411): Unknown User/Peer IA 











CENLOG. 

DLCMAN (415): Connection allocated by link provider 

Description: DLCMAN received an open SAP request for a connection allocated by 



DLCMAN (416): Connection already allocated 

Description: DLCMAN received a second allocate request for the same connection. 



DLCMAN (417): No CONNCB pointer in User packet 

Description: DLCMAN received a primitive from an LPIA without a proper 

connection control block pointer. The data link control manager service module that 


6–50 7436 0728–303






DLCMAN (420): Close LSAP Complete 

Description: DLCMAN completed all close LSAP requirements and LPIA. The data 



DLCMAN (421): Close CONN Complete - Close LSAP 

Description: DLCMAN received a close connection confirm from an LPIA for the last 

confection on an LSAP. DLCMAN will close the LSAP. The data link control manager 


CENLOG. 

DLCMAN (422): Close Connection Complete 

Description: DLCMAN received confirmation from an LPIA that a connection was 

closed. The data link control manager service module that maintains the interfaces to 


DLCMAN (423): Requesting User IA not registered 

Description: DLCMAN received a request from an unregistered user. The data link 







DLCMAN (425): Requested Line not active 




7436 0728–303 6–51


DLCMAN (426): Requested LSAP CB not active 

Description: DLCMAN received a primitive for a nonexistent LSAP CB. The data 



DLCMAN (428): Close Connection Complete 

Description: DLCMAN received confirmation from an LPIA that a connection was 

closed. The data link control manager service module that maintains the interfaces to 


DLCMAN (429): no CONNCB pointer in User packet 

Description: DLCMAN received a primitive from an LPIA without a proper 



DLCMAN (430): retry OpenConnReq 

Description: DLCMAN is attempting to reopen a failed connection. The data link 



DLCMAN (431): OPEN Connection complete 

Description: DLCMAN received notification from an LPIA that a connection has 

been established successfully. The data link control manager service module that 






DLCMAN (433): Invalid SAPIndex in Users Indication packet 

Description: DLCMAN is unable to identify an LSAP because the LPIAs primitive 

contained an invalid SAP Index. The data link control manager service module that 






6–52 7436 0728–303

DLCMAN (437): Invalid SAPIndex in Users Indication packet 


Description: DLCMAN is unable to identify an LSAP because the LPIAs primitive 

contained an invalid SAP Index. The data link control manager service module that 


DLCMAN (441): No Connect CB pointer Users Indication packet 

Description: DLCMAN received a primitive from lan LPIA without a proper 



DLCMAN (443): Close Connection Indication from LPIA 

Description: DLCMAN received an indication from an LPIA to close a connection. 



ENET (002): Registration with DLCMAN failed (FATAL!) 

Description: ILM software error. ILM is not usable. The Ethernet link provider 

interface application (LPIA) for the ILM software generates this CENLOG. 

Action: Contact your Unisys representative. 

ENET (003): Unsupported DLCMAN request (discarded) 

Description: Not supported DLCMAN primitive received. A long CENLOG shows the 

primitive. The Ethernet link provider interface application (LPIA) for the ILM 

software generates this CENLOG. 

ENET (004): Can't queue Ethernet frame to HLE (FATAL!) 



ENET (005): Can't queue LLC frame to HLE (FATAL!) 



ENET (015): Input bridge frame (XID not yet exchanged) 

Description: Input to the host on the HLB cannot be sent until the host is satisfied 

the 802.3 LAN is operational by means of a successful XID exchange. All inputs to the 

HLB are discarded. The Ethernet link provider interface application (LPIA) for the 

ILM software generates this CENLOG. 

7436 0728–303 6–53


ENET (016): Can't queue bridge MAC frame (discarded) 

Description: The host channel on the HLB is not operational after a successful XID 

exchange. All input frames to the HLB are discarded. The Ethernet link provider 


ENET (017): Can't queue loopback input frame (discarded) 

Description: ILM software error. ILM loop-back (LOOP command) test failed. The 

Ethernet link provider interface application (LPIA) for the ILM software generates this 

CENLOG. 

ENET (018): HLE output received - LCC disabled (discarded) 

Description: INTEL 825x6 LAN Chip Controller (LCC) hardware failure. ILM is not 

usable. The Ethernet link provider interface application (LPIA) for the ILM software 


ENET (019): SAI Down received from bridge 

Description: The host channel on the HLB is down. The Ethernet link provider 


ENET (020): SAI Up received from bridge 

Description: The host channel on the HLB is up. The Ethernet link provider 


ENET (022): Bridge output frame too short (discarded) 

Description: The length of an HLB output frame is less than the required packet 

header. The Ethernet link provider interface application (LPIA) for the ILM software 


ENET (023): Can't queue XID response to bridge 

Description: The input side of the HLB is not operational. All input frames to the 

HLB are discarded. The Ethernet link provider interface application (LPIA) for the 


ENET (024): XID response queued to bridge 

Description: The HLB is operational. A long CENLOG shows the XID. The Ethernet 

link provider interface application (LPIA) for the ILM software generates this 

CENLOG. 

6–54 7436 0728–303

ENET (025): Loopback output frame too short 


Description: The length of a diagnostic loopback (LOOP command) frame is less 

than the required addressing header. The loopback test failed. A long CENLOG 

shows the Telcon buffer header. The Ethernet link provider interface application 

(LPIA) for the ILM software generates this CENLOG. 

ENET (026): No LSAP for HLE/Facility ID 

Description: Configuration or software error. Output for this HLE/Facility ID is 

discarded. A long CENLOG shows the Telcon buffer header containing the offending 

HLE/Facility ID. The Ethernet link provider interface application (LPIA) for the ILM 


ENET (027): HLE output - not MAC or LLC (config error) 

Description: The SAP configuration ILMIF is not one of the permitted types: LLC 

Type 1, LLC Type 2, Transparent, or MAC. Output frames are discarded. A long 

CENLOG shows the output buffer. The Ethernet link provider interface application 


Action: Correct the configuration. 

ENET (028): Can't connect MAC station to LAN (FATAL!) 

Description: LCC hardware, bulkhead connector or transceiver problem. 

Subsequent CENLOG(s) indicate the precise failure cause. ILM is not usable. The 


CENLOG. 

ENET (029): LCC H/W passed diagnostic self tests 

Description: ILM is operational on the 802.3 LAN. The Ethernet link provider 


ENET (030): LCC H/W failed diagnostic self tests (FATAL!) 

Description: INTEL 825x6 internal failure. ILM is not usable. The Ethernet link 

provider interface application (LPIA) for the ILM software generates this CENLOG. 

ENET (031): LCC H/W failed internal loopback (FATAL!) 



7436 0728–303 6–55


ENET (032): LCC H/W failed transceiver loopback (FATAL!) 

Description: Transceiver failure or problem with transceiver cable connection. ILM 

is not usable. The Ethernet link provider interface application (LPIA) for the ILM 


Action: ILM TDR command may indicate location and cause of problem. 

ENET (033): LCC H/W failed 'set SCP address' (FATAL!) 

Description: INTEL 825x6 internal failure. Initialization of LCC hardware structures 

failed. ILM is not usable. The Ethernet link provider interface application (LPIA) for 

the ILM software generates this CENLOG. 

Action: An ILM DUMP might indicate the cause of the failure. 

ENET (034): LCC H/W failed external loopback (FATAL!) 

Description: INTEL 825x6 internal failure. The probable cause is a short or open on 

the LAN cable. ILM is not usable. The Ethernet link provider interface application 


Action: The ILM TDR command might indicate location and cause of the problem. 

ENET (036): Can't queue SAI signal to HLE (FATAL!) 



ENET (037): ISR - can't queue link input (FATAL!) 



ENET (039): Can't allocate LCC H/W SCB area (FATAL!) 



ENET (040): LCC H/W register dump taken (FATAL!) 



Action: An ILM DUMP may indicate the cause of the failure. 

6–56 7436 0728–303

ENET (041): LCC H/W deadlocked (warning) 


Description: INTEL 825x6 internal lock up. ILM is temporarily not usable. The 


CENLOG. 

Action: ILM software will attempt a H/W RESET to restart the 825x6. A long 

CENLOG shows the H/W System Control Block (SCB). 

ENET (042): ISR - can't configure LCC H/W (FATAL!) 



Action: A long CENLOG shows the H/W Command Block (CB). 

ENET (043): ISR - can't set LCC H/W MAC address (FATAL!) 

Description: INTEL 825x6 internal failure. Set local station MAC address command 




ENET (044): ISR - can't set LCC H/W M/C addresses (FATAL!) 

Description: INTEL 825x6 internal failure. Set multicast (M/C) address command 




ENET (045): LCC H/W deadlock - H/W reset failed (FATAL!) 

Description: INTEL 825x6 internal failure. Hardware RESET did not clear LCC 

internal lock up. ILM is not usable. The Ethernet link provider interface application 


Action: A long CENLOG shows the H/W System Control Block (SCB). 

ENET (046): SAI Up signal sent to HLE 

Description: HLE data path is available. The Ethernet link provider interface 

application (LPIA) for the ILM software generates this CENLOG. 

Action: None (informational). 

7436 0728–303 6–57


ENET (047): SAI Down signal sent to HLE 

Description: HLE data path is blocked. The Ethernet link provider interface 


Action: None. It might require a DOWN/UP if blockage persists. 

ENET (048): ISR - no RBD attached to FD (warning) 

Description: ILM software error. The Ethernet link provider interface application 



ENET (049): ISR - no RB attached to RBD (warning) 

Description: ILM software error. The Ethernet link provider interface application 



ENET (055): Oversize output UDU frame (discarded) 

Description: An output frame was received from a Telcon HLE that exceeds the 

maximum IEEE 802.3 frame size (1497 bytes). The Ethernet link provider interface 


Action: Correct the Telcon configuration for session maximum UDU size. For 

example, MAXNDU for TS/TN and RTC. 

ENET (056): Duplicate address check 

Description: This MAC station address is duplicated at another MAC station on the 

LAN. The Ethernet link provider interface application (LPIA) for the ILM software 


Action: Use a unique MAC station address for this MAC station (LINE STA 

parameter). 

FDDI (001): Can't create Link Input Q 

Description: The FDDI link provider interface application (LPIA) for the ILM 


6–58 7436 0728–303

FDDI (002): Can't create Conn hold Q 


Description: FDDI LPIA is unable to create required initialization queues. The FDDI 


CENLOG. 

FDDI (003): Can't create ConnHold hold Q 

Description: FDDI LPIA is unable to create required initialization queues. The FDDI 


CENLOG. 

FDDI (004): registration to DLCMAN failed 

Description: FDDI IA cannot complete initialization. The FDDI link provider 


FDDI (005): Unrecognized DLCMAN primitive received 

Description: FDDI IA does not recognize a received primitive. The primitive request 

did not complete. The FDDI link provider interface application (LPIA) for the ILM 


FDDI (006): Response text length exceeds maximum 

Description: FDDI IA created an NMS message which exceeds the memory space 

allocated for the message. The FDDI link provider interface application (LPIA) for the 


FDDI (007): NMS Response failed 

Description: Indicates that the NMS message was not received. The FDDI link 


FDDI (008): Open Station Req - failure 

Description: FDDI IA is unable to complete MAC station initialization. The FDDI 


CENLOG. 

FDDI (009): Create P failed for FDIIN 



CENLOG. 

7436 0728–303 6–59


FDDI (010): Create P failed for FDIOUT 



CENLOG. 

FDDI (011): Create P failed for FDIEVNT 



CENLOG. 

FDDI (012): Station initialization failed 



CENLOG. 

FDDI (013): SMT initialization failed 



CENLOG. 

FDDI (014): Ring Connection failed 



CENLOG. 

FDDI (015): Can't add In Q to QL 

Description: FDDI IA is unable to complete the SAP initialization. The FDDI link 


FDDI (016): Unknown 'Set Station Attributes Req' received 

Description: FDDI IA received an unrecognized set attributes request. FDDI IA 

cannot complete the request. The FDDI link provider interface application (LPIA) for 


FDDI (021): Oversized frame received 

Description: FDDI IA received an oversized frame from the link. The frame was 

discarded. The FDDI link provider interface application (LPIA) for the ILM software 


6–60 7436 0728–303

FDDI (024): 'alloc_msg' failed in Get Message 


Description: FDDI IA is unable to complete a pending request. The FDDI link 



Description: An NMS response message is too large. The FDDI link provider 



Description: An NMS response message is too large. The FDDI link provider 


FDDI (027): 'put_q' failed on SAI message to HLE 

Description: FDDI IA is unable to send input to an HLE. The FDDI link provider 


FDDI (028): Alloc Station Req - failure 

Description: FDDI IA is unable to allocate resources required to run a Loopback 

test. The FDDI link provider interface application (LPIA) for the ILM software 


FDDI (029): Open Station Req - Process init failed 




FDDI (030): Open Station Req - Process init failed 




FDDI (031): Station initialization failed during Allocate 




7436 0728–303 6–61


FDDI (032): Create P failed for fddi SMT timer 

Description: FDDI IA is unable to complete MAC initialization. The FDDI link 











FDDI (036): Request channel 0 initialization failed 



FDDI (037): Request channel 1 initialization failed 



FDDI (038): Indicate channel 0 initialization failed 









6–62 7436 0728–303

FDDI (041): Can't allocate QL for input process 


Description: FDDI IA is unable to initialize the SAP. The FDDI link provider 


FDDI (042): Can't add Link input Q to QL 



FDDI (043): Can't create QL for output process 



FDDI (044): Can't add Output Q to QL 



FDDI (045): Can't add hold Q to output QL 



FDDI (046): Can't add temp Q to output QL 



FDDI (047): Can't add UDM Q to output QL 



FDDI (048): Output message freed - no odud 

Description: FDDI IA is unable to allocate output message control space. The 

message was not delivered. The FDDI link provider interface application (LPIA) for 


FDDI (049): Maximum output retry exceeded 

Description: The retry count was exceeded and the connection closed. The FDDI 


CENLOG. 

7436 0728–303 6–63


FDDI (051): Send CNF error 

Description: FDDI IA transmit confirmation error on a send message. The message 

was not delivered. The FDDI link provider interface application (LPIA) for the ILM 


FDDI (052): No message header for input data 

Description: FDDI IA was unable to allocate message space for input. The FDDI 


CENLOG. 

FDDI (053): put_q to line's input queue failed 

Description: FDDI IA was unable to send input to an HLE. The FDDI link provider 


FDDI (055): Oversized User Data Unit 

Description: An HLE sent an oversized data unit to FDDI IA. The message was not 

delivered. The FDDI link provider interface application (LPIA) for the ILM software 


FDDI (056): No identifiable MODE on output 

Description: Output message processing cannot be continued. The FDDI link 


FDDI (057): No Station CB to receive input 

Description: Input message processing error. The message was discarded. The 

FDDI link provider interface application (LPIA) for the ILM software generates this 

CENLOG. 

FDDI (058): Ring Configuration Change = Isolated C_WRAP_A 

C_WRAP_B THRU 

Description: FDDI Station Management (SMT) has detected a ring topology change. 

CENLOGs FDDI (060) and FDDI (061) provide additional change information. This 

CENLOG is informational. FDDI Interface Application (FDDIIA) generates this 

CENLOG. 

Action: None, this message is informational only. 

6–64 7436 0728–303

FDDI (059): MAC neighbor change: New XXX reported 


Description: FDDI Station Management (SMT) has detected a ring topology change. 

CENLOGs FDDI (060) and FDDI (061) provide additional change information. XXX 

will be replaced by a new Upstream Neighbor Address (UNA) or a new Downstream 

Neighbor Address (DNA). This CENLOG is informational. FDDI Interface Application 

(FDDIIA) generates this CENLOG. 


FDDI (060): Old UNA:xx-xx-xx-xx-xx-xx New UNA:xx-xx-xx-xx-xx-xx 

Description: Refer to CENLOG FDDI (058). This CENLOG provides additional 

information for ring topology changes for old and new Upstream Neighbor Addresses 

(UNA). FDDI Interface Application (FDDIIA) generates this CENLOG. 


FDDI (061): Old DNA:xx-xx-xx-xx-xx-xx New DNA:xx-xx-xx-xx-xx-xx 

Description: Refer to CENLOG FDDI (058). This CENLOG provides additional 

information for ring topology changes for old and new Downstream Neighbor 

Addresses (DNA). FDDI Interface Application (FDDIIA) generates this CENLOG. 


FDDI (062): LSAP value already in use 

Description: A SAP configuration statement is being processed that conflicts with a 

previous SAP statement. FDDI Interface Application (FDDIIA) generates this 

CENLOG. 

Action: Check your configuration for conflicting LSAP configuration parameters. 

FDDI (063): LLC2 Disconnect Ind received from remote SAP 

Description: An LLC2 Disconnect Mode (DM) frame has been received by the FDDI 

Interface Application (FDDIIA). The FDDIIA closes the SAP. 


FDDI (064): Duplicate address detected on MAC–XXXX 

Description: FDDI Station Management (SMT) has detected a duplicate station 

address on the ring. XXXX is replaced with MY DUPLICATE or MY UNA 

DUPLICATE. 

Action: Update your configuration. 

7436 0728–303 6–65


FDDI (065): SMT Frame error detected on MAC–XXXX 

Description: XXXX is replaced by ACTIVE or NOT ACTIVE as required by the error 

type. This CENLOG is originated by the FDDI Interface Application (FDDIIA). 


FDDI (066): Closing Connection - Max Retry exceeded 

Description: The FDDI Interface Application (FDDIIA) has reached the maximum 

number of retries in its attempt to recover an LLC2 connection. The connection is 

closed and reopened. This CENLOG is originated by the FDDI Interface Application 

(FDDIIA). 


FRLY: PORT UP 

Description: This message indicates that the Frame Relay software has registered 

with the ILM platform. 

FRLY: PORT DOWN 

Description: This message indicates that the Frame Relay network connection is not 

operational. 

FRLY: PORT EXCEPTION 

Description: This message indicates that an exception indication has been received 

from the UDLC driver or that an LMI exception has occurred. 

FRLY: PORT RECOVERY 

Description: This message indicates that the Frame Relay network connection has 

recovered from an exception event. 

FRLY: DLCI n # NEW 

Description: This message indicates that the DLCI represented by DLCI name (n) 

and number (#) has been added as active to the Frame Relay network connection as 

given by the line name. 

FRLY: DLCI n # REMOVE 


and number (#) has been removed by the Frame Relay network connection as given 

by the line name. The destination of the DLCI is not operational. 

6–66 7436 0728–303

FRLY: DLCI n # ACTIVE 



and number (#) has been added as active to the Frame Relay network connection as 

given by the line name. 

FRLY: DLCI n # INACTIVE 


and number (#) has been changed to be inactive by the Frame Relay network 

connection as given by the line name. 

FRLY: DLCI n # VIOLATION 


and number (#) has had a violation by the Frame Relay network connection as given 

by the line name. A non-configured Frame Relay network DLCI may have been used 

on a frame. 

ILMLOOP (012) 

Description: The ILMLOOP Interface Application has received notification of link 

availability from DLCMAN. 


ILMX25 LCB Not Found During SAI Down Processing 

Description: After PDNILM receceived an SAI down facility control request from the 

ILM Platform (refer to the “ILMX25: Received SAI Down From ILM Platform” 

CENLOG). PDNILM was unable to obtain the line control block (LCB). A software 

error occurred between the PDNILM and the ILM PLatform interface. 


message. Procedure PDN8ILM of the X.25 PSCS program product generates this 

CENLOG. 

Action: Use the NMS DOWN and UP LINE commands to re-initialize the line. 

7436 0728–303 6–67


ILMX25 Line Already Up 

Description: PDNILM received a line initialization packet from the ILM Platform for 

a port that already has an enabled line (a line control block already exists). 

Attributes affected: Line event including port number and line name, 

supplementary text message. Procedure line_init_request of the X.25 PSCS program 


Action: Check the Telcon configuration for duplicate port addresses on the LINE 

configuration statement of the ADR parameter. 

ILMX25 Line Control Block Build/Initialization Failure 

Description: During X.25 line initialization, DCP OS buffer resource problems 

occurred while trying to reserve system segment numbers or allocate buffer space for 

the line control block. 

Attributes affected: Line event including the port number and line name, 



Action: Either the DCP itself has temporarily run out of memory (become throttled), 

or Telcon or the OS have reached configured buffer limits. Check to see if the 

configured buffer limits are too low. 

ILMX25 Line Initialization Failure 

Description: An error occured during X.25 line initialization. The specific reason is 

reported in one of the following related CENLOGs. 

• Class 5 Event 15 “X.25 PSCS Initialization error” may be reported indicating a 

probable configuration error. Refer to the CENLOG’s description for the specific 

initialization error. 

• A Configure Element Confirm packet was received from the ILM Platform 

containing a failure status. Another CENLOG should be reported by the ILM 

Platform or ILM IA indicating the reason for the failure. 

Attributes affected: Line event including the port number and line name, 



Action: Refer to any other “initialization error” CENLOGs related to this one for 

determining the reason for the error. If no other CENLOGs occurred, this may 

indicate a software error. Contact your Unisys support representative. 

6–68 7436 0728–303

ILMX25 Port Initialization Failure ILMX25 


Description: During X.25 initialization, PDNILM received an undeliverable message 

(UDM) attach confirm packet with a failure status from the ILM Platform. A related 

UDM attachment error CENLOG should be reported by the ILM Platform or ILM IA to 

indicate the specific reason for the failure. 

Attributes affected: Line event including port number and line name, 



Action: Refer to any other “UDM attachment error” CENLOGs related to this one for 

determining the reason for the error. If no other CENLOGs occurred, this may 

indicate a software error. Contact your Unisys support representative. 

ILMX25 Received SAI Down from the ILM Platform 

Description: PDNILM receceived an SAI down facility control request packet from 

the ILM Platform after the Platform was notified of a PP State Item. PDNILM 

proceeds to de-allocate resources (line control block) associated with the line. 

Attributes affected: Line event including port number, supplementary text message. 

Procedure line_init_request PDN8ILM of the X.25 PSCS program product generates 

this CENLOG. 

Action: The aborted port should automatically restart and the line should become 

reinitialized. No action needed. 

If the NMS ILM DUMP command was previously used to automatically retrieve the 

aborted port’s memory into a DCP file, contact your Unisys support representative to 

have the ILM DUMP analyzed. 

ILMX25 State Item Detach Request Confirm 

Description: The PDNILM module received an unsolicited detach request confirm 

packet from the ILM Platform after the Platform was notified of a PP State item. The 

ILM Platform uses this unsolicited packet method to indicate that a PP state item 

occured. PDNILM proceeds to detach queue resources associated with the line. 

Attributes affected: Line event includs the port number and supplementary text 

message. Procedure PDN5ILM of the X.25 PSCS program product generates this 

CENLOG. 

Action: The aborted port should automatically restart and the line should become 

reinitialized; no action necessary. 

If the NMS ILM DUMP command was previously used to automatically retrieve the 

aborted port’s memory into a DCP file, contact your Unisys support representative to 

have the ILM DUMP analyzed. 

7436 0728–303 6–69


LAPBHS (001): x.x.xx - Registered with ILM platform 

Description: LAPBHS IA initialized and is ready for command packets. 


LAPBHS (002): DEBUG - Management packet rejected 

Description: Software error. This CENLOG is found only in debug systems. 


LAPBHS (003): DEBUG - Output Attach Request 

Description: Normal during line/station initialization. This CENLOG is found only in 

debug systems. 


LAPBHS (004): DEBUG - Output Attach Request - REJECTED 

Description: The output queue attach request failed. This CENLOG is found only in 



LAPBHS (005): DEBUG - Input Attach Request - DATA 




LAPBHS (006): DEBUG - Input Attach Request REJECTED 

Description: An input queue attach request failed. This CENLOG is found only in 



LAPBHS (007): DEBUG - Detach Request 

Description: Normal during line/station tear down. This CENLOG is found only in 



6–70 7436 0728–303

LAPBHS (008): DEBUG - Detach Request REJECTED 


Description: The request for queue detach failed. This CENLOG is found only in 



LAPBHS (009): DEBUG - LINE_CONFIG_TBL 




LAPBHS (010): DEBUG - STATION_CONFIG_TBL 




LAPBHS (011): DEBUG - LINE_MODE_CHANGE 

Description: A change in mode was indicated. This CENLOG is found only in debug 

systems. 


LAPBHS (012): DEBUG - DOWN_LINE 

Description: This is a normal message that appears during line/station tear down. 

This CENLOG is found only in debug systems. 


LAPBHS (013): DEBUG - UP_STATION 

Description: This is a normal message that appears when a line/station is initialized. 

This CENLOG is found only in debug systems. 


LAPBHS (014): DEBUG - DOWN_STATION 

Description: This is a normal message that appears when a line/station is taken 

down. This CENLOG is found only in debug systems. 


7436 0728–303 6–71


LAPBHS (015): DEBUG - START_STATION 

Description: This is a normal message that appears when NMS starts a station. This 

CENLOG is found only in debug systems. 


LAPBHS (016): DEBUG - STOP_STATION 

Description: This is a normal message that appears when NMS stops a station. This 



LAPBHS (017): DEBUG - DORMANT_STATE_CHG 

Description: This is a normal message that appears when the dormant flag line 

changes. This CENLOG is found only in debug systems. 


LAPBHS (018): DEBUG - CONFIG_ELEMENT_REQUEST -- FAILED 

Description: A configuration packet failed or a request for a configuration element 

failed. This CENLOG is found only in debug systems. 


LAPBHS (019): LINE CONFIG ERROR, Must be FULL DUPLEX 

Description: The line is configured as half duplex. 

Action: Correct the configuration by configuring the Telcon line as full duplex. 

LAPBHS (020): LINE CONFIG ERROR, May NOT be a Switched Line 

Description: The line is configured as a switched line. 

Action: Correct the configuration by configuring the Telcon line as direct. 

LAPBHS (022): STATION CONFIG ERROR, Must be Two Way 

Simultaneous 

Description: The station is configured as two way alternate. 

Action: Correct the configuration by configuring the Telcon line as two way 

simultaneous. 

6–72 7436 0728–303


LAPBHS (023): STATION CONFIG ERROR, Must be Async Balanced 

Mode 

Description: The station is not configured in async balanced mode. 

Action: Correct the station configuration for async balanced mode. 

LAPBHS (024): STATION CONFIG ERROR, Local Station Must be ABM 

Description: The station is not configured as async balanced mode. 

Action: Correct the station configuration for async balanced mode. 

LAPBHS (025): Line UP 

Description: The data-set-ready signal was received. 


LAPBHS (026): Line DOWN 

Description: The data-set-ready signal was lost. 


LAPBHS (027): Station Entered Information Transfer State (ITS) 

Description: The SABM/UA exchange was successful. 


LAPBHS (028): Station Entered Logical Disconnect State (LDS) 

Description: DISC/UA was successful or fatal protocol error occurred. 

Action: Check the line error counter using the following ILM mode NMS command: 

DISP PORT pp LINE I TYPE ERRS. This command identifies error conditions that 

may have caused the disconnect. If the line continues to toggle between ITS and LDS, 

check the value of the T1 timer using the following ILM mode NMS commands: LIST 

LINE line_name or LIST LINE pp/l. If the T1 timer is not long enough, it may be 

lengthened in your TELCON configuration by adding or lengthening the response 

timer. 

7436 0728–303 6–73


(LPIA)LAPBHS (030): ilmsvc() rejected response to CONFIG_ELT_REQ 

Description: A software error occurred. 


LAPBHS (031): ilmsvc() rejected packet being returned in error 

Description: A software error occurred. 


LAPBHS (034): packet from ILM platform REJECTED, reason: x 

Description: A software error occurred. Reason codes for x are as follows: 

0 – packet type not known 

1 – bad line number 

2 – line not initialized 

3 – attachment already exists 

4 – invalid output priority 

5 – all UDM attachments full 

6 – all INPUT attachments full 

7 – attachment doesn’t exist 

8 – bad attachment type 


LAPBHS (035): START Station 

Description: An NMS START station command was received. The HDLC link 



LAPBHS (036): STOP Station 

Description: NMS STOP station command was received. 


LAPBHS (037): UP Line 

Description: NMS UP line command or line initialization. 


6–74 7436 0728–303

LAPBHS (038): DOWN Line 

Description: NMS DOWN line command. 


LAPBHS (039): UP Station 

Description: NMS UP station command or station initialization. 


LAPBHS (040): DOWN Station 

Description: NMS DOWN station command. 


LAPBHS (041): S/W ERROR - negative status received 

Description: This is a software error. 



LAPBHS (042): XPC H/W is not responding - modem clocks lost 

Description: Either a transmit or a receive clocks to the line is missing. 

Action: Check the cables and modems. If the line is not wired then configure the line 

down. 

LAPBHS (043): DLL - Down Line Load requested 

Description: A remote station is requesting a down line load. 


LAPBHS (044): Station Entered Initialization State (IS) 

Description: RIM/SIM exchange successful, down line load of remote station. 


7436 0728–303 6–75


LAPBHS (045): OLD station configuration OVER-WRITTEN by NEW 

Description: There is more than one station configured for a line. Only the last 

station configuration packet is honored. This CENLOG also can indicate a second 

attempt to bring up a station. 

Action: Check the Telcon configuration and correct if necessary. 

LAPBHS (046): Output message of invalid length Discarded 

Description: There was an output attempt of a message larger than the configured 

maximum I-frame size. The message was discarded. 

Action: Correct the Telcon configuration. 

LAPBHS (047): Up Station FAILED - no UDM queue 



LAPBHS (048): Up Station FAILED - no input data queue 



LAPBHS (049): Indication packet REJECTED by ILM platform 



LAPBHS (050): Return of ATTACH/DETACH packet rejected 



LAPBHS (051): XPC driver error - illegal command 

Description: This is a software error. The hardware driver issued an invalid 

command or a valid command at a time when that command is not allowed. 

Action: The software will attempt recovery. An ILM DUMP may indicate the cause 

of the failure. Contact your Unisys representative. 

6–76 7436 0728–303

LAPBHS (105): DEBUG - Input Attach Request - UDM 





LAPBHS (205): DEBUG - Input Attach Request - DLL 

Description: Normal during line/station initialization for down line load. This 



LMMGT (001): Lbus input error 

Description: An input exception error occurred on the LBUS input. The line 

module’s ILM Platform manager generates this CENLOG. 

LMMGT (002): Invalid packet type received from CP 

Description: Unrecognized packet received on management output attachment. The 

line module’s ILM Platform manager generates this CENLOG. 

LMMGT (003): Invalid packet type or no IA 

Description: Unrecognizable packet type or unknown target IA. The line module’s 

ILM Platform manager generates this CENLOG. 

LMMGT (004): 'Free_msg' failed 

Description: MTF message cannot be freed. The line module’s ILM Platform 

manager generates this CENLOG. 

LMMGT (005): Det_req for invalid att table entry 

Description: A detach request was received for an unknown attachment. The line 

module’s ILM Platform manager generates this CENLOG. 

LMMGT (006): First load block received 

Description: Program load in progress, first block received. The line module’s ILM 

Platform manager generates this CENLOG. 

7436 0728–303 6–77


LMMGT (007): Last load block received 

Description: Program load last block received. The line module’s ILM Platform 

manager generates this CENLOG. 

LMMGT (008): First (w/spawn) load block received 

Description: Program load in progress, first block received. The line module’s ILM 


LMMGT (009): Unrecognizable load code 

Description: An unrecognizable load code was received during the load process. 

The line module’s ILM Platform manager generates this CENLOG. 

LMMGT (010): Load complete 

Description: The program load completed. The line module’s ILM Platform manager 


LMMGT (011): Input detach request in OAT range 

Description: An invalid detach request was received. The line module’s ILM 


LMMGT (012): No IUT entry for requested AID for the ILM software. 

Description: The ILM Platform manager received a request for an attach ID for 

which there is no Interface User Table (IUT) entry. The request cannot be honored. 

(Software error.) This CENLOG is generated by the line module’s ILM Platform 

manager. 

LMMGT (013): 'AID' for output is greater min input ID 

Description: The ILM Platform manager received an invalid output attach request. 


manager. 

LMMGT (014): No IUT entry for detach 

Description: The ILM Platform manager received a request for an attach ID for 

which there is no Interface User Table (IUT) entry. The request cannot be honored. 


manager. 

6–78 7436 0728–303

LMMGT (015): Attach table entry not valid 


Description: The ILM Platform manager received an invalid output attach request. 


manager. 

LMMGT (016): Wrong 'call func' returned in 'det_conf' 

Description: The ILM Platform manager received a detach confirm from an IA with 

the wrong call function ID. The confirm is returned to the IA. (IA software error.) 

This CENLOG is generated by the line module’s ILM Platform manager. 

LMMGT (017): 'Close_q' failed on call func 

Description: The ILM Platform manager attempted to close a queue. The call 

returned a failure code. (IA software error.) This CENLOG is generated by the line 

module’s ILM Platform manager. 

LMMGT (018): Wrong 'queue' returned in 'det_conf' 

Description: The ILM Platform manager received a detach confirm from an IA with 

the wrong call function ID. (IA software error.) This CENLOG is generated by the 

line module’s ILM Platform manager. 

LMMGT (019): invalid packet type received from IA 

Description: An IA attempted to pass a packet to the ILM Platform by means of an 

ILMSVC call. The packet type was not recognized by the manager. (IA software 

error.) This CENLOG is generated by the line module’s ILM Platform manager. 

LMMGT (020): 'Att_req' is for wrong port 

Description: The ILM Platform manager received a request that was intended for 

another port. (Software error.) This CENLOG is generated by the line module’s ILM 

Platform manager. 

LMMGT (021): 'Att_req' is in IAT range 

Description: The ILM Platform manager received an output attach request with an 

erroneous attach ID. (Software error.) This CENLOG is generated by the line 


LMMGT (022): 'Att_req' out of OAT range 




7436 0728–303 6–79


LMMGT (023): Attach table entry already occupied 

Description: The ILM Platform manager received an invalid attach request. 


manager. 

LMMGT (024): Invalid 'att_conf' received from IA 



manager. 

LMMGT (025): 'Att_req' is for wrong port 



manager. 

LMMGT (026): 'Input_att_req' is in OAT range 




LMMGT (027): 'AID' greater than 252 



manager. 

LMMGT (028): Attach table entry already occupied 



manager. 

LMMGT (029): IA rejected 'attach input request' 

Description: The ILM Platform manager received an attach confirm which the IA 

rejected. (Software error.) This CENLOG is generated by the line module’s ILM 


LMMGT (030): Invalid 'att_conf' received from IA 



manager. 

6–80 7436 0728–303

LMMGT (031): Response text length exceeds maximum 


Description: An NMS response overran its buffer space. (Software error.) This 

CENLOG is generated by the line module’s ILM Platform manager. 

LMMGT (032): IA registration error: Bad Q hdl 

Description: An IA passed a registration packet to the ILM Platform manager that 

contained an invalid queue identifier. This CENLOG is generated by the line module’s 

ILM Platform manager. 

LMMGT (033): 'Alloc_msg' failed 

Description: The ILM Platform manager attempted to allocate a message. The failed 

attempt indicates a limited resource condition in the LM. This CENLOG is generated 

by the line module’s ILM Platform manager. 

LMMGT (034): 'Put_q' failed on management attachment 

Description: The ILM Platform manager is unable to send data to the CP. This 

CENLOG is generated by the line module’s ILM Platform manager. 

LMMGT (035): No IA queue for message 

Description: The ILM Platform manager is unable to pass a packet to its intended IA 

because the IA has not registered a proper queue. This CENLOG is generated by the 

line module’s ILM Platform manager. 

LMMGT (036): 'Free_seg' failed when deleting IUT entry 

Description: The ILM Platform manager is unable to deallocate space. (Software 


LMMGT (037): No buffer for reject - restart timer 

Description: The ILM Platform manager is unable to send a required response to the 

CP due to low resources. A timer started so the response can be sent at a later time. 

This CENLOG is generated by the line module’s ILM Platform manager. 

LMMGT (038): Attach request timed out 

Description: An IA took more than 5 seconds to respond to a request. The Platform 

takes the action to respond. This CENLOG is generated by the line module’s ILM 


7436 0728–303 6–81


LMMGT (039): Detach request timed out 

Description: An IA took more than 5 seconds to respond to a request. The Platform 

takes the action to respond. This CENLOG is generated by the line module’s ILM 


LMMGT (040): Invalid packet received from IA on ILMSVC call 

Description: An IA attempted to pass a packet to the ILM Platform by means of an 

ILMSVC call. The packet type was not recognized by the manager. (IA software 


LMMGT (041): All lines are already active 

Description: A build LCB call was made to the ILM Platform manager when all lines 

are already assigned. This CENLOG is generated by the line module’s ILM Platform 

manager. 

LMMGT (042): Requested line number out of range 

Description: A build LCB call was made to the ILM Platform manager with an invalid 

line number. This CENLOG is generated by the line module’s ILM Platform manager. 

LMMGT (043): LCB already allocated 

Description: A build LCB call was made to the ILM Platform manager for a line that 

is already busy. This CENLOG is generated by the line module’s ILM Platform 

manager. 

LMMGT (044): LCB offspring still linked to LCB 

Description: A call was made to the ILM Platform manager to delete an LCB. The 

LCB still has subordinate facilities linked to it. This CENLOG is generated by the line 


LMMGT (045): 'Alloc_msg' failed, trace buffer lost 

Description: The ILM Platform manager is unable to allocate a trace buffer. Traces 

are lost. This CENLOG is generated by the line module’s ILM Platform manager. 

PPP (nnn) Registration with DLCMAN complete 

Description: PPP has registered with DLCMAN (nnn is an indicator of the location of 

the CENLOG in the PPP software). 

Action: None. 

6–82 7436 0728–303

PPP (nnn) Starting LCP Protocol 


Description: PPP is starting Link Control Protocol for line (nnn is an indicator of the 

location of the CENLOG in the PPP software). 

Action: None. 

PPP (nnn) SAI Up signal sent to HLE 

Description: The user IA or High Level Entity (HLE) has been informed that the PPP 

Link is ready to use (nnn is an indicator of the location of the CENLOG in the PPP 

software). 

Action: None. 

PPP (nnn) SAI Down signal sent to HLE 

Description: The user IA or High Level Entity (HLE) has been informed that the PPP 

Link is no longer available to the user (nnn is an indicator of the location of the 

CENLOG in the PPP software). 

Action: This may be a normal action caused by management command. If this is 

caused by PPP link failure, an additional CENLOG identifies the failure. 

PPP (nnn) Received Protocol Reject 

Description: PPP received a protocol reject packet from its peer on the link (nnn is 

an indicator of the location of the CENLOG in the PPP software). 

Action: This indicates a PPP configuration error. Examine the PPP configuration for 

both ends of the PPP line and fix the PPP configuration. 

PPP (nnn) Received Code Reject 

Description: PPP received a code reject packet from its peer on the link (nnn is an 

indicator of the location of the CENLOG in the PPP software). 

Action: This indicates that the peer PPP software is not compatible. Contact your 

Unisys representitive. 

PPP (nnn) Received Unknown Code 

Description: PPP received an unknown code in a packet from its peer on the link 

(nnn is an indicator of the location of the CENLOG in the PPP software). 

Action: This indicates that the peer PPP software is not compatible. Contact your 

Unisys representitive. 

7436 0728–303 6–83


PPP (nnn) Input frame discarded due to line error 

Description: An input message was received in error and discarded (nnn is an 

indicator of the location of the CENLOG in the PPP software). 

Action: If this occurs, often the quality of the link should be upgraded. 

PPP (nnn) Unrecoverable line error 

Description: The line failed (nnn is an indicator of the location of the CENLOG in 

the PPP software). 

Action: PPP tries to connect to the peer on the link again. If this occurs, often the 

quality of the link should be upgraded. 

SDLC (000): Registered with platform 

Description: The SDLC IA registered itself with the ILM platform and with DLCMAN. 

This CENLOG is generated by the SDLC link provider interface application (LPIA) for 

the ILM software. 

Action: This is a normal occurrence that requires no user action. 

Supplementary Data: Management Extension Registration Packet. For more 

information, refer to the ILM Platform Programming Reference Manual (7431 8569). 

SDLC (001): ABM mode not supported in this release 

Description: An attempt was made to configure an ABM station. ABM is not 

supported in this release level. This CENLOG is generated by the SDLC link provider 

interface application (LPIA) for the ILM software. 


Supplementary Data: Connection Control Block. For more information, refer to the 

ILM Platform Programming Reference Manual (7431 8569). 

SDLC (003): Configuration ERROR - Incompatible stations 

Description: An attempt was made to configure incompatible stations on the line. 






6–84 7436 0728–303

SDLC (022): Stn config ERROR - Invalid Mode/Type Combo 


Description: An attempt was made to configure a station with an incompatible 

combination of Station Mode and Local Station Type. This CENLOG is generated by 

the SDLC link provider interface application (LPIA) for the ILM software. 




SDLC (023): Stn config ERROR - Can't mix NRM Sec with anything 

Description: An attempt was made to configure an NRM secondary station on the 

same line as another station type. This CENLOG is generated by the SDLC link 

provider interface application (LPIA) for the ILM software. 




SDLC (025): Data Set Ready (DSR) detected - LINE UP 

Description: Data Set Ready was detected on the line and the line was reported as 

up. This CENLOG is generated by the SDLC link provider interface application (LPIA) 

for the ILM software. 


Supplementary Data: Line Control Block. For more information, refer to the ILM 

Platform Programming Reference Manual (7431 8569). 

SDLC (026): Data Set Ready (DSR) lost - LINE DOWN 

Description: Data-Set-Ready (DSR) was lost due to a line error or disconnection. 



Action: Automatic recovery should occur when the line connection is restored. If 

automatic recovery does not occur, try a DOWN of the line followed by an UP of the 

line from the NMS console. 



7436 0728–303 6–85


SDLC (027): Station Entered Information Transfer State (ITS) 

Description: The station entered information transfer state. This CENLOG is 

generated by the SDLC link provider interface application (LPIA) for the ILM 

software. 


SDLC (028): Station Entered Logical Disconnect State (LDS) 

Description: The station entered logical disconnect state. This CENLOG is 

generated by the SDLC link provider interface application (LPIA) for the ILM 

software. 

Action: This occurs when the station on the other end of the line disconnects or 

stops responding. 

SDLC (030): START line 

Description: An NMS START LINE command was received and processed. This 

CENLOG is generated by the SDLC link provider interface application (LPIA) for the 

ILM software. 

Action: None. 

SDLC (031): STOP line 

Description: An NMS STOP LINE command was received and processed. This 


ILM software. 

Action: None. 

SDLC (035): START station 

Description: An NMS START STATION command was received and processed. This 


ILM software. 

Action: None. 

SDLC (036): STOP station 

Description: An NMS STOP STATION command was received and processed. This 


ILM software. 

Action: None. 

6–86 7436 0728–303

SDLC (037): UP line 


Description: An NMS UP LINE command was received and processed. This 


ILM software. 

Action: None. 

SDLC (038): DOWN line 

Description: An NMS DOWN LINE command was received and processed. This 


ILM software. 

Action: None. 



SDLC (039): UP station 

Description: An NMS UP STATION command was received and processed. This 


ILM software. 

Action: None. 

SDLC (040): DOWN station 

Description: An NMS DOWN STATION command was received and processed. This 


ILM software. 

Action: None. 



SDLC (042): Unrecoverable mgmt queue/queue list ERROR 

Description: An error occurred that prevented the IA from establishing a queue 

between it and the ILM platform. This CENLOG is generated by the SDLC link 

provider interface application (LPIA) for the ILM software. 

Action: None. 

7436 0728–303 6–87


SDLC (043): Max XID commands sent without valid response 

Description: The maximum number of XID commands was sent without receiving a 

valid reply. This CENLOG is generated by the SDLC link provider interface 

application (LPIA) for the ILM software. 

Action: Check the configuration and the connection. 

SDLC (050): FRMR sent,... 

Description: A frame reject response was sent. The control frame of the rejected 

command, the expected N(s) and N(r), and the reason code for the frame reject are 

also displayed. 

Action: None. 

SNAUIA0 (001): Snau_main: SNAUIA Registered with Platform 

Description: The SNA User Interface application registered itself with the data link 

controller manager (DLCMAN). 

SNAUIA0 (024): fwdSaiChg: Send to HLE failed 

Description: An error occurred which prevents the SNA User Interface application 

from sending control messages to the High Level Entity (HLE). 

SNAUIA0 (031): No free Connection 

Description: The SNA user interface application has exceeded the maximum 

number of PU(s). 

SNAUIA0 (032): No segment available for PU_alloc request 

Description: The SNA user interface application has no memory available for the 

PU. 

SNAUIA0 (047): SnaulnvState: Invalid state for message received 

Description: The SNA User Interface application received a message while the 

connection was not in receive mode. 

SNAUIA0 (066): PU role mismatch 

Description: The SNA user interface application has detected a configuration error. 

When LSTYP=NEG (negotiable) only one PU can be configured/active on the line. 

When configuring multiple PU(s) on a line, all the PU(s) must be configured with the 

same LSTYP parameter which can be either PRIM or SEC. 

6–88 7436 0728–303

SNMP Messages 

SNAUIA0 (072): Verify_msg: Input PIU not of Type 4 


Description: The SNA User Interface application received a message with an invalid 

format header. 

SNAUIA0 (073): Verify_msg: Input PIU Length Error 

Description: The SNA User Interface application received a message with an invalid 

length specification. 

Note: All SNMP CENLOG messages include a name in parentheses at the end of 

the message. This name is the name of the internal routine which produced 

the CENLOG. The exact message, including this name must be included 

with any report of a problem. 

SNMP 101 Alt response PDU is too big 

Description: An error response PDU was built to be sent to the SNMP management 

station, but the PDU was too big to fit in the output buffer. The response is discarded. 

Action: Single occurrences can be ignored. If this error occurs repeatedly, dump the 

ILM to determine the cause of the problem. 

Note: Some SNMP CENLOG messages have variable parts that may vary each 

time the CENLOG is generated. 

SNMP 102 ASN.1 construct not supported: ssssssss 

Description: The SNMP Agent encountered an ASN.1 construct in a PDU from a 

management station that it does not support. The message is discarded. 

Variable: ssssssss The type of ASN.1 construct that is not supported. 

Action: Single occurrences can be ignored. An SNMP trace with TYPE=M can be 

used to capture the offending management PDU. 

7436 0728–303 6–89


SNMP 103 Auth fail IP=xxxxxxxx, community=ssssssss 

Description: The community name in a PDU from a management station was either 

not found in the list of configured community names, or a SET Request was received 

and the community name was not configured to allow SETs. 

Variable: xxxxxxxx The IP address of the management station from which the PDU 

was received, in 32-bit hex format. 

Variable: ssssssss The community name received from that management station. 

Action: The SNMP Agent and the management station must be configured to use the 

same community names. These names are case sensitive. Check the community and 

communitySET configuration statements for the SNMP Agent. Refer to the ENS 

Installation, Configuration, and Operations Guide (7441 2065), for a detailed 

description and options for these statements. 

In some cases an unauthorized management station trys to gain access to the SNMP 

Agent. In this case the CENLOG indicates that an unauthorized access has been 

attempted, and the CENLOG can be ignored. 

SNMP 104 Auth failure and not enabled 

Description: Indicates that the SNMP Agent wanted to send an authentication failure 

trap PDU to a management station, but that the sending of these traps was not 

enabled in the SNMP Agent’s configuration. 

Action: Authentication failure traps are enabled by the snmpEnableAuthenTraps 

statement in the SNMP Agent’s configuration. If you enable authentication failure 

traps, this CENLOG does not occur. 

SNMP 105 Bad ASN.1 parse 

Description: The length of a PDU from a management station, that is contained 

within the PDU, is longer than the actual PDU received. The PDU is discarded. 

Action: Single occurrences can be ignored. This indicates an error in the PDU 

building code in the management station. An SNMP trace with TYPE=M can be used 

to capture the offending management PDU. 

SNMP 106 Bad authentication header 

Description: A message was received by the SNMP Agent which did not have the 

format of an SNMP PDU. The message is discarded. 

Action: If this CENLOG occurs repeatedly, an SNMP trace with TYPE=M can be used 

to capture the offending message. 

6–90 7436 0728–303

SNMP 107 ASN.1 NULL with non-zero length 


Description: While parsing a PDU, the SNMP Agent encountered an ASN.1 NULL 

item with a non-zero length. This construct is not supported by the SNMP Agent. The 

PDU was discarded. 

Action: Single occurrences can be ignored. If this CENLOG occurs repeatedly, an 

SNMP trace with TYPE=M can be used to capture the offending PDU. 

SNMP 108 Bad PDU build, field=ssssssss 

Description: The SNMP Agent encountered an error while attempting to build a PDU 

to send to a management station. The PDU was discarded. 

Variable: ssssssss The name of the SNMP PDU field which could not be built 

properly. 


SNMP trace with TYPE=M can be used to attempt to capture the offending 

circumstances. 

SNMP 109 Bad PDU parse, field=ssssssss 

Description: The SNMP Agent encountered an error while attempting to parse a 

PDU received from a management station. The PDU was discarded. 

Variable: ssssssss The name of the SNMP PDU field which could not be parsed 

properly. 



SNMP 110 Bad trap request 

Description: An internal error is keeping the SNMP Agent from being able to 

generate a Trap Request PDU to a management station. 

Action: Single occurrences can be ignored. If this CENLOG occurs repeatedly, dump 

the ILM as close as possible to an occurrence. 

SNMP 111 Clock param error 

Description: An internal error has occurred within the SNMP Agent when attempting 

to get or set the value of an internal clock object. 



7436 0728–303 6–91


SNMP 112 Duplicate CIM connection 

Description: The SNMP Agent has detected a duplicate ICS connection to CIM-ILM 

or CIM-FILE. This duplicate has been disconnected. 

Action: Could indicate problems elsewhere in the system. Look for other symptoms 

of improper operation. 

SNMP 113 Integer must be long 

Description: When parsing or building an ASN.1 integer type, the internal storage for 

the integer must be 32 bits. An internal error has occurred where this is not the case. 

The PDU being processed is discarded. 

Action: Could indicate problems elsewhere in the system. Look for other symptoms 

of improper operations. 

SNMP 114 ASN.1 length > 32 bits 

Description: When parsing a PDU from a management station, an ASN.1 object was 

found whose length would not fit within a 32-bit field (for example, the length value 

was >2 32 

). The PDU is discarded. 

Action: Single occurrences can be ignored. If the CENLOG occurs repeatedly, an 


SNMP 115 Length past end of buffer 

Description: When parsing a PDU from a management station, an ASN.1 object was 

found whose indicated length is longer than the PDU received. The PDU was 

discarded. 



SNMP 116 Out of node space 

Description: There are more [NODExx] statements in the ENS configuration 

specifying SNMP for this domain than the SNMP Agent can handle. The current limit 

is 8 nodes per SNMP domain. The node configuration (beyond 8) is ignored. 

Action: Verify that the SNMP configuration is correct. Refer to the ENS Installation, 

Configuration, and Operations Guide (7441 2065) for the description of configuring 

[NODExx] statements (Telcon runs) in an SNMP domain. If more than 8 are needed, 

submit a UCF, as this limit can be upped. 

6–92 7436 0728–303

SNMP 117 Msg before transport ready 


Description: The SNMP Agent has a PDU to send to a management station but there 

is no UDP transport path currently available to output it. The PDU is discarded. 

Action: Because the different components of ENS initialize asynchronously, this 

CENLOG may normally occur once when the ILM containing the SNMP Agent is 

initialized. If this CENLOG occurs at other times, it may indicate that the SNMP Agent 

has lost its previously available UDP transport path. Look for other symptoms of 

improper operation, such as the management station loosing contact with the SNMP 

Agent. 

SNMP 118 Couldn't get buffer for ssssssss 

Description: An ILM buffer could not be obtained to contain the structure indicated 

by ssssssss. 

Variable: ssssssss The type of internal structure which could not be allocated. 

Action: This CENLOG indicates a tight memory situation in the ILM. If the ILM is not 

currently under heavy load, then an internal error may have occurred which 

consumed a lot of memory, and the ILM needs to be dumped. 

SNMP 119 No room for CDS header 

Description: The SNMP Agent did not have enough room at the beginning of a buffer 

to put a header on a PDU to a management station. The PDU is discarded. 



SNMP 120 Not my CIM msg: ssssssss 

Description: An internal error has occurred between the SNMP Agent and CIM-ILM. 

Variable: ssssssss A more detailed description of the type of error. 

Action: An SNMP trace with TYPE=S can be used to capture the offending message. 

7436 0728–303 6–93


SNMP 121 No transport for trap 

Description: The SNMP Agent has a Trap PDU to send to a management station, but 

there is no UDP transport path currently available to output it. The Trap PDU is 

discarded. 

Action: Because the different components of ENS initialize asynchronously, this 

CENLOG may normally occur once when the ILM containing the SNMP Agent is 

initialized. If this CENLOG occurs at other times, it may indicate that the SNMP Agent 

has lost its previously available UDP transport path. Look for other symptoms of 

improper operation, such as the management station loosing contact with the SNMP 

Agent. 

SNMP 122 Not SNMPv1 msg 

Description: A PDU was received which is not SNMP version 1. The SNMP Agent 

does not support SNMPv2 PDUs. The PDU is discarded. 



SNMP 123 Too many subid's in OID 

Description: The SNMP Agent encountered an ASN.1 object identifier which either 

contained too many sub-identifiers, or a sub-identifier had too large a value. The 

current limits are up to 96 sub-identifiers in an object identifier up to 65535. The PDU 

is discarded. 

Action: An SNMP trace with TYPE=M can be used to capture the offending PDU. 

SNMP 124 Trap not OID 

Description: An internal error has been detected when attempting to build a Trap 

PDU where the supplemental information was not an object identifier. 


SNMP trace with TYPE=M can be used to capture the offending Request PDU. 

SNMP 127 Cannot truncate response 

Description: The SNMP Agent attempted to generate a Response PDU which 

exceeded the maximum PDU size. Under the rules of SNMP version 1, a truncated 

response is not allowed. The Response PDU is discarded. 


SNMP trace with TYPE=M can be used to capture the offending Response PDU. 

6–94 7436 0728–303

SNMP 128 Unable to fixup lengths 


Description: An internal error has occurred when building a PDU to a management 

station when the SNMP Agent was attempting to set lengths within some ASN.1 fields 

to match the actual length of the PDU. The PDU is discarded. 



SNMP 129 Unknown auth header type 

Description: A PDU was received which was not SNMP version 1. The SNMP Agent 

does not support SNMPv2 PDUs. The PDU is discarded. 



SNMP 130 Unrecognized CDS msg 

Description: An internal error has beendetected between the SNMP Agent and a 

UDP transport provider. The unrecognized message has been discarded. 



SNMP 131 Unknown CIM function 

Description: An internal error has been detected between the SNMP Agent and CIM- 

ILM. The unrecognized message has been discarded. 


SNMP trace with TYPE=M can be used to capture the offending message. 

SNMP 132 Unknown transport type 

Description: The SNMP Agent is connected to a transport provider of a type that is 

not supported. Only UDP transports are currently supported. If a message was being 

processed, it is discarded. 

Action: This error would probably result from an internal corruption of SNMP tables 

or code. If this CENLOG occurs repeatedly, dump the ILM as close as possible to an 

occurrence. 

7436 0728–303 6–95


SNMP 133 SNMPv1 not enabled 

Description: The SNMP Agent has received an SNMP version 1 PDU that it is not 

enabled to process. The PDU is discarded. 

Action: This error probably would result from an internal corruption of SNMP tables 


occurrence. 

SNMP 134 var_info chain ptr error 

Description: The internal linking of MIB variables for building a response message 

has been corrupted. The response message is discarded. 

Action: This error probably would result from an internal corruption of SNMP tables 


occurrence. 

SNMP 136 Bad file status xxxx 

Description: An error status has been received when processing the MIB subtree 

files. These DCP files are read during SNMP Agent initialization. An error processing 

any of these files results in part of the MIB not being built (although the part which is 

built is not in error). 

Variables: xxxx The hex error status value. Common values are: 

0016 File not cataloged. 

0075 File in exclusive use. 

0090 Element not found. 

0100 File I/O error. 

Action: Verify that the file ENS*ENSMIB exists on the DCP. (This filename can be 

changed using the MIBfile configuration statement.) The SNMP Agent expects to read 

the following elements from the file (unless skipped by the MIBskip configuration 

statement): CHRSTRM, DCPOS, FR, HOSTRES, IPX, PSCS, SNANET, UTS, 

X25DL, X25PL. 

SNMP 137 CIM_FILE interface problem xxxx 

Description: An internal error has been detected between the SNMP Agent and 

CIM-FILE. The reading of the MIB subtree files is aborted if this error occurs. 

Variable: xxxx Internal diagnostic value. 

Action: Dump the ILM as close as possible to an occurrence. 

6–96 7436 0728–303

SNMP 138 Unknown file function xxxx 


Description: An internal error has been detected between the SNMP Agent and CIM- 

FILE. The SNMP Agent has received an unsupported file function code. The message 

containing this function code is discarded. 

Variable: xxxx Unsupported file function code value. 

Action: An SNMP trace with TYPE=S can be used to capture the offending function. 

SNMP 139 MIBbuilder Error, File=ssssssss, Line=nnnn 

Description: An error in the content of one of the MIB subtree files has been 

detected. The part of the MIB built by this file is not built. 

Variables: ssssssss The name of the element (within the ENS*ENSMIB file) 

containing the error. 

nnnn The line number within the element where the error was 

detected. 

Action: Reinstall the ENS*ENSMIB file from the release tape. If this does not solve 

the problem, provide the ssssssss element, or a listing of it, with a UCF. 

SNMP 200 SNMP Agent Activating in Port xx 

Description: This CENLOG is a notification of which ILM (DCP port number) the 

SNMP Agent is running in. It should occur each time the system is initialized, 

whenever that ILM fails and the SNMP Agent for the same SNMP domain in another 

ILM takes over. 

Variable: xx The hex port number of the ILM. 

Action: None. If this CENLOG occurs at other than system initialization, then it 

indicates the ILM containing the previous SNMP Agent has failed. 

SNMP 201 put_q failed: Q-List Index=nn 

Description: This is an indication of an internal error wherein a message could not 

be added to an ILMOS queue. The message is discarded. 

Variable: nn The SNMP queue list index of the queue. 

Action: Dump the ILM as close to an occurrence as possible. 

7436 0728–303 6–97


SNMP 202 Invalid ICS class=xxxx 

Description: The SNMP Agent cannot determine the ICS class of one of its 

connections. If a message was being processed, it is discarded. 

Variable: xxxx The ICS value 


or code. Dump the ILM as close as possible to an occurrence. 

SNMP 207 L-Bus Failure Notification, bus#=n 

Description: The SNMP Agent has received notification of an L-bus failure from ICS. 

The notification is ignored. 

Variable: n The L-bus number. 

Action: None. 

SNMP 208 Inv exp ack, type=xx port=nn pid=yy 

Description: An ICS expedited data acknowledgement has been received by the 

SNMP Agent. The SNMP Agent should never get this, because it never sends 

expedited data. The acknowledgement is discarded. 

Variables: xx The ICS type code (CP or ILM) of the destination. 

nn The DCP port number of the destination. 

yy The ICS process ID of the destination. 

Action: Dump the ILM as close as possible to an occurrence. 

SNMP 209 Invalid CCB Error 

Description: An SNMP internal error has occurred wherein an address thought to be 

of a connection control block really is not a connection control block. If there is a 

message being processed with this control block, it is discarded. 



occurrence. 

6–98 7436 0728–303

SNMP 210 Bad ICS connect status xxxx 


Description: The SNMP Agent received a bad status trying to establish an ICS 

connection. The connection has not been made. 

Variable: xxxx The ICS status value. 

Action: If this CENLOG occurs repeatedly, dump the ILM as close as possible to an 

occurrence. 

SNMP 211 Bad ICS send status xxxx 

Description: The SNMP Agent received a bad status trying to send data on an ICS 

connection. The data message is discarded. 

Variable: xxxx The ICS status value. 

Action: If this CENLOG occurs repeatedly, dump the ILM as close as possible to an 

occurrence. 

SNMP 212 No memory for CCB 

Description: The SNMP Agent could not get ILM memory to build a connection 

control block. Although the connection exists, no control block is built to be able to 

use it. 


currently under heavy load, then an internal error could have occurred which 

consumed a lot of memory. Dump the ILM. 

SNMP 213 No config access. Using defaults. 

Description: During system initialization, the SNMP Agent waits to be contacted by 

CIM-ILM in order to read its configuration. If forty-five seconds (current value) has 

elapsed without this contact, the SNMP Agent continues initialization with the default 

configuration. The default configuration is equivalent to the following (where pp is 

the port number). 

[PORTpp] 

[SNMP] 

Action: Dump the ILM. 

7436 0728–303 6–99


SNMP 403 Unable to release ssssssss 

Description: The sub-Agent could not return message buffer space to the operating 

system for subsequent reuse. 

The sub-Agent provides SNMP MIB information related to the SNMP itself. This 

includes system information and message statistics. The sub-Agent has a direct 

interface to the MIB manager; no ICS is involved. 

Variable: ssssssss Text indicating the MIB manager message type and what 

portion of the message space. 

Action: This event indicates a memory corruption problem. Dump the ILM. 

SNMP 404 Received ssssssss containing out-of-range oid value 

Description: The sub-Agent received a request message from the MIB manager 

containing a valid MIB sub-tree, but the object value was out of range. 



interface to the MIB manager; no ICS connection is involved. 

Variable: ssssssss Request message type received from the MIB manager. 

Action: This event implies either a memory corruption or software problem. 

Activate ILM SNMP traces and/or take an ILM dump. 

SNMP 405 Received ssssssss containing unknown object id (oid) 

Description: The sub-Agent received a request message from the MIB manager 

containing an invalid object specifier (MIB sub-tree), or a valid one but not compatible 

with the type of request message received. 




Variable: ssssssss Request message type received from the MIB manager. 

Action: This event implies either a memory corruption or software problem. 

Activate ILM SNMP traces and/or take an ILM dump. 

SNMP 501 Same OID from the same SMP 

Description: If this CENLOG displays, there is a coding problem. 

Action: An SNMP trace with TYPE=LM can be used to capture the offending SMP. 

6–100 7436 0728–303


SNMP 502 Register packet received with an error status (xxxx) 


Variable: xxxx The status received in the SMP Register Packet. 


SNMP 503 Register packet received with a count of zero 



SNMP 504 Bad SMP REG received by MIBman 

Description: An error occurred while processing the SMP registration packet. This 

could be a coding error or an SMP is trying to register for a MIB branch that is not 

known by MIBman. 

Action: Check the DCP file ENS*ENSMIB, to make sure all the dynamic MIBs are 

listed. If all the MIB files are there, an SNMP trace with TYPE=LM can be used to 

capture the offending SMP. Dump the ILM after the traces have been turned off. 

SNMP 505 Bad index type (xx), used 

Description: The MIB definition received by the SNMP Agent from the manager does 

not match the SNMP Agent’s MIB definition. 

Variable: xx The MIB definition (instance encoding type) 

Action: Ensure that the MIB definition used by the manager matches the MIB 

definition used by the SNMP Agent. An SNMP trace with TYPE=M can be used to 

capture the offending message. 

SNMP 506 Bad Get Response or interface error message (xxxx) 

Description: A response from the SMP contained an error. There is a coding 

problem. 

Variable: xxxx An error code stating what was wrong with the response. 

Action: An SNMP trace with TYPE=LM can be used to determine the cause of the 

problem. 

7436 0728–303 6–101


SNMP 507 Encoding packet encoding type error (xxxx) 

Description: A response from the SMP contained an encoding type not known to 

MIBman. 

Variable: xxxx The encoding type that caused the error. 

Action: An SNMP trace with TYPE=LM can be used to capture the offending 

message. 

SNMP 508 No SMP Reg Command was received 

Description: A Get Response was received from the SMP before a SMP REG was 

done. 


message. 

SNMP 509 Unknown message (xxxx), received from the ssssssss 

Description: An unknown command was received from the SNMP manager or the 

SMP. If the message came from the SNMP manager, probably the command is not 

supported by the SNMP Agent. If the message came from the SMP, probably the 

command is not supported by the SMP. 

Variables: xxxx The message type 

ssssssss The name of the entity that sent the message, for example the 

manager or the SMP. 

Action: If the message came from the SNMP Manager, check the message type. 

Currently the DCP only supports SNMPv1 commands. In either case, an SNMP trace 

with TYPE=LM can be used to capture the offending message. 

SNMP 510 Couldn't get a buffer for ssssssss 

Description: An ILM buffer could not be obtained to contain the structure indicated 

by ssssssss. 

Variable: ssssssss The type of internal structure that could not be allocated. 


currently under heavy load, an internal error may have occurred which consumed a 

lot of memory. Dump the ILM. 

6–102 7436 0728–303

SNMP 511 MIB branch exist--Old definition will be used. 


Description: A dynamic MIB was being built for a branch that has already been 

defined. 

Action: Check the MIB definitions in the DCP file ENS*ENSMIB to ensure they are 

for the correct MIB branches. An SNMP trace with TYPE=LM can be used to capture 

the offending message to help find the MIB file that is causing the problem. 

SNMP 512 Bad OID received by MIBbuilder 

Description: A dynamic MIB OID sequence was received that its placement in the 

current MIB could not be found. 


messages to help find the MIB file causing the problem. 

7436 0728–303 6–103




6–104 7436 0728–303




SNA: 228 - TG=index# Line operational, Station address x%% 



represents a hexadecimal number. The # is a TG index number. This message is 


SNA: 249 - TG=index# TG operational 



a TG index number. 

SNA: 250 - TG=index# TG in-operative 



a TG index number. This message is informational only. 

SNA: 261 - TG=index#: PU operational 


Group Control (TGC) that controls lines between SNA/net and IBM subareas. The # 

is a TG index number. This message is informational only. 

SNA: 262 - TG=index#: PU in-operative 



a TG index number. This message is informational only. 

SNA: 400 - Cdrm Netname.sscpname Active (Subarea/Element) 



conversing with other SSCPs in the process of establishing sessions. The SSCP-SSCP 

session of the indicated resource is now active. This message is informational only. 

7436 0728–303 6–105


SNA: 401 - Cdrm Netname.sscpname Terminated 

(Subarea/Element) 




session of the indicated resource has been terminated by operator action and is now 

inactive. User SNA sessions cannot be established with this Domain if the SSCP-SSCP 

session is inactive. 

SNA: 402 - Cdrm Netname.sscpname Outage (Subarea/Element) 




session of the indicated resource is now inactive as a result of a network outage. User 

SNA sessions cannot be established with this Domain if the SSCP-SSCP session is 

inactive. 

SNA: 435 - Unable to send Local NAU message:FC %%%% YEA= 

&&&& 




a hexadecimal number, & represents a decimal number, and YEA is your element 

address. The probable cause is a software problem. 

SNA: 437 - 3rd Party Session Fail LU2=@@@@@@@@ 

LU1=@@@@@@@@ 



conversing with other SSCPs in the process of establishing sessions. The @ 

represents an ASCII character. This message is informational only. 

SNA: 450 - No COS for CDRM Activation 



conversing with other SSCPs in the process of establishing sessions. The COS 

statement referenced was required for SSCP-SSCP session activation and was not 

available or defined. The CDRM SSCP-SSCP session may have been activated anyway 

because of activation attempts from the peer CDRM. 

6–106 7436 0728–303


SNA: 669 - RBFTE - Host Connect reschedule (Reject = %%%%) 

Description: This message occurs as a result of errors or events in the Crossover 

Application Bridge (XAB). The XAB handles traffic between SNA resources and OS 

2200 hosts. The % represents a hexadecimal number. This message is informational. 

SNA: 670 - RBFTE - SNA Logon reschedule (Sense = %%%%%%%%) 


Application Bridge (XAB). The XAB handles traffic between SNA resources and 

OS2200 hosts. The % represents a hexadecimal number. This message is 

informational. For more information on sense codes, refer to Appendix D of this 

manual. 

SNA: 1010 - PU activated 


attached to SNA/net. This message is informational only. 

SNA: 1011 - LU activated 



SNA: 1031 - PU deactivated 



SNA: 1032 - LU deactivated 



SNA: 1033 - PU deactivated - BF link area overflow 



SNA: 1201 - Incoming Call Accepted 




7436 0728–303 6–107


SNA: 1202 - XID Match 




SNA: 1234 - NPSI Link Up 




SNA: 1235 - NPSI Link Down 




SNA: 2013 - Session aborted, yea %%%% pea %%%% psa %%%%, 

rsn= %% 

Description: The following message occurs as a result of errors in establishing 

sessions between OS 2200 hosts and BSC terminals that are connected to an IBM 

network. The yea is your element address, pea is the partner element address, psa is 

the partner subarea, and % represents a hexadecimal number. The probable cause is a 


SNA: 2208 - Snatrunk active 


DCA traffic across an SNA network. The probable cause is a configuration problem. 

SNA: 2209 - Snatrunk inactive 


DCA traffic across an SNA network. This message is informational only. 

6–108 7436 0728–303

SNA: 2431 - @@ active 


Description: The new boundary management messages for 3270 connected devices, 

IBF connections to NCPs, and connections to NT 2.1 devices. The @ represents an 

ASCII character. This message is informational only. 

SNA: 2432 - @@ inactive 



NT2.1 devices. The @ represents an ASCII character. This message is informational 

only. 

7436 0728–303 6–109


6–110 7436 0728–303

Section 7 


Hardware errors, statistics, and utilization events characterize Class 7. 

Event 1 NETWORK STATISTICS COLLECTED 

DCE FEATURE ACCOUNTING LOG 

Description: The NMS RECORD command for the DCE Feature has been invoked. 

This event records the formation or termination of any virtual circuit connection or an 

interval over which a specified number of data packets has occurred. This event 

includes the buffer containing the virtual circuit connection information. 

Attributes affected: Supplementary text message, Registers not included. The X.25 


Procedure: PDNETP 

The format of the included virtual circuit connection is shown in Table 7–1. 

7436 0728–303 7–1


Word Offset 

(hex) 

Table 7–1. Virtual Circuit Connection – Buffer Format 

0 Remote 

DTE 

length 

Bit Position 

F 8 7 0 

1 Remote DTE address (ASCII) 

9 Local DTE address (ASCII) 

11 No. of segments received 

13 No. of segments sent 

15 No. of bytes received 

17 No. of bytes sent 

19 Call Request time (real-time clock) 

1B No. of data packets received 

1D No. of data packets sent 

1F No. of interrupt packets received 

21 No. of interrupt packets sent 

23 No. of receive ready packets received 

25 No. of receive ready packets sent 

27 No. of receive not ready packets received 

29 No. of receive not ready packets sent 

2B Input packet size index 

2D Output packet size index 

2F Input window size 

31 Output window size 

33 No. of other packets received 

35 No. of other packets sent 

37 VC Type Logical channel number 

Local DTE length 

38 Clear cause code Clear diagnostic code 

39 CUG No. Flags 

3A Auxiliary flags 

3B No. of days No. of hours 

3C No. of minutes No. of seconds 

7–2 7436 0728–303


Notes: 

1. A segment is equal to 64 octets. 

2. Packets received and sent are in regard to the internal and external DTEs, not those 

between peers in other Telcon nodes. 

3. VC type: 0 equals switched virtual circuit, 1 equals permanent virtual circuit, 2 

equals reject incoming calls, 3 equals reject outgoing calls. 

4. Flags (by bit position). 

6,7: Priority number 

5: Transit delay facility 

4: Restricted response on fast select facility 

3: Fast select facility 

2: Rpoa facility 

1: Flow control negotiation facility 

0: Reverse charging facility 

5. Auxiliary flags are not currently used. 

6. Word offsets 3B and 3C contain the real-time clock stamp in binary where the call 

request occurred until the virtual circuit connection is cleared. Then these call 

duration fields are set in a binary coded decimal (BCD) format. 

7436 0728–303 7–3

Event 2 PN1 SPECIFICATION ERROR 

Event 2 PN1 SPECIFICATION ERROR 

PN1 SPECIFICATION ERROR 

Description: An internally recoverable event posted by an I/O processor. It could 

also result from bringing down a line or channel. Telcon generates this CENLOG. 

Action: No action is necessary. If the problem persists, down the line using NMS and 

contact the local customer engineer. 

7–4 7436 0728–303

Event 3 NETWORK RESPONSE-TIME HI/LO GAUGE CROSSING 

Event 3 NETWORK RESPONSE-TIME HI/LO GAUGE 

CROSSING 





7436 0728–303 7–5

Event 4 PORT PROCESSOR (PP) SPECIFICATION EXCEPTION 

Event 4 PORT PROCESSOR (PP) SPECIFICATION 

EXCEPTION 

PORT PROCESSOR (PP) SPECIFICATION EXCEPTION (PP STATE ITEM 

RECEIVED) 





AGPPST 

Description: Signifies that the LPH requested that a log be performed during PP 

state-item processing in AGSYSRTN. After a PP state-item occurs, the line or lines on 

that port are brought down. Use the NMS UP command to continue use of that line. 

R9: Output chain address 

R12: Error subtype 

R13: Supplementary status 1 

R14: PPID 

R15: LPH return status 

Telcon generates this CENLOG. The table space in the CENLOG contains the entire 

text of the state item. For detailed information on the state item, refer to the DCP 

CPA Program Reference Manual (7431 5805–100). 

BSC LPH 

Description: BSC port processor state-item event has occurred. 

R8: PAO address 

R9: State-item status 

R10: LC$AFLG 


R12: LC$B flag word 

R13: LC$FLGW flag word 

R14: Port processor ID 

R15: LC$SSTAT flag word 


7–6 7436 0728–303

HCC 


Description: HCC has received a state-item from a host channel port. If the stateitem 

was due to an NMS DOWN command, the port is freed and the facility is marked 

as down. If the state-item was due to a software or hardware error, an attempt is 

made to restart the port. 

R8: Current instruction offset in HCC 

R9: TSID 

R10: Port output chain address 

R11: Port input chain address 

R12: Op-code of instruction that errored: bits 15-8 

Type of error: bits 7-5 

R13: 

Subtype of error: bits 4-0 

Supplementary status 

R14: PPID 

R15: Input flags from AGSYSRTN 


NTRLPH 

Description: This event occurs whenever the PP hardware or the PP program 

detects a fatal hardware or software error. The line is brought down after occurrence 

of this event. If the error type and subtype (logged registers R9 & R10) do not indicate 

a hardware error, this information should be the basis for submission of a UCF. Other 

information logged: 

R9: Error type code 

R10: Error sub-type code 

R12: Output chain execution address 

R13: Input chain execution address 

R14: PP-D. Values in other registers may be useful for debug. The PP state-item 

buffer is logged in the first 64 (X'40') words. The LCB and SCT (site control 

table) are logged in the remaining words of the log entry. 


RMLPH 

Description: Port hung; Unable to force state-item by clearing the ‘C’ bit; but, the 

state-item was never received. This is a hardware or microcode problem. 

R15: Port number 


7436 0728–303 7–7


TTYLPH 

Description: This event occurs if a fatal hardware or software error occurs on the 

PP being used. This results in all lines configured on the PP being downed. Other 


R9: State-item error type 

R10: State-item error sub-type 

R12: Output chain execution address 

R13: Input chain execution address 

R14: PPID (no 4X1 line # present). The PP state-item buffer (64 words) structured, 

as stated in the preface of the DCP/40 System Description. The contents of 

the PP fixed-space for the PP program used (as defined in location counter 0 

of TTYIOP for 4X1 line modules, and location counter 0 of TTYLPH for 1X1 

line modules). 


7–8 7436 0728–303

Event 5 PP HARDWARE ERROR STATISTICS LOGGED 

Event 5 PP HARDWARE ERROR STATISTICS LOGGED 

Description: Logging/Notification of PP Error Statistics is exceedingly high. This 

CENLOG occurs when the ratio of PP error counts to I/O transmission counts exceeds 

the maximum percentage, as configured on the MAXERR parameter of the associated 

LCLASS statement. The default is five percent. This CENLOG will not appear if the 

PPE STATS parameter on the PRCSR statement does not specify YES (the default is 

NO). This CENLOG prints a formatted message (showing the error-rate percentage 

and the PPID) for each port that was excessive in error ratio. Telcon generates this 

CENLOG. 

Supplementary Message for Class 07, Event 05 

I/O TRANSMISSION ERROR RATE = N% ON PORT N(HEX) N(DECIMAL) 

Action: If operations seem acceptable to users, then increase the MAXERR 

parameter on the corresponding LCLASS configuration statement. If operations are 

not acceptable, try a different line module, modem, or DCM. Contact your Unisys 

representative if operation is still unacceptable. 

7436 0728–303 7–9

Event 6 IPP/IOP HARDWARE EVENT 

Event 6 IPP/IOP HARDWARE EVENT 

Description: R15 has code and status. This is a hardware event. Telcon generates 

this CENLOG. 


The following Class 7 Event 6 CENLOGs report hardware events that can occur on a 

DCP62X. 

CODE IN LOWER BYTE OF R15 

Description: If the lower byte of R15 contains event code 020, then the upper byte is 

the PPID. A port processor (PP) unexpected state-item occurred on a port not 

assigned to a DCP/OS run. This can occur when you issue an UP or DOWN line 

command. 


Description: If the lower byte of R15 contains event code 021, then the upper byte is 

the IOPID number and an unexpected background state-item has occurred. 


Description: If the lower byte of R15 contain an event code of 050, 052, or 053, a 

Control Station or MCF error has occurred. 

050 – The link between the Control Station and the DCP has gone through recovery 

because of an error detected by the MCF. The OS terminal(s) are recovered 

but any Telcon terminals active on the Control Station must be restarted. 

051 – The link between the Control Station and the DCP has gone through recovery 

because of an error detected by the DCP. The OS terminal(s) are recovered 

but any Telcon terminals active on the Control Station must be restarted. 

052 – The link between the MCF and the DCP has gone through recovery because of 

an error detected by the DCP. 

Action: No action is required unless these CENLOGs are repeatedly occurring, then 

call your Unisys representative. 

7–10 7436 0728–303

Event 7 COMMUNICATIONS LINE ERROR 

Event 7 COMMUNICATIONS LINE ERROR 

COMMUNICATIONS LINE ERROR 

Action: None. 

7436 0728–303 7–11

Events 8-9 Not Defined 


No CENLOGs have been defined for Events 8 and 9. 

7–12 7436 0728–303

Event 10 LINE/TERMINAL STATISTICS 

LINE–TERMINAL STATISTICS 


Description: With the NMS SETI command, statistics on a line or line/terminal basis 

can be collected. This event is not displayed at the NMS console and requires a log 

reduction program for analysis. Telcon generates this CENLOG. 

Action: None. 

All LPH modules, FCONTROL, and HCC 

Description: Line/terminal statistics (message I/O counts). This CENLOG does not 

display on the console (unless the LOGI command is used). One CENL entry is made 

for each port that has had at least one I/O message since the last CENL entry. The 

STATS parameter on the PRCSR statement controls whether these statistics should be 

gathered, and if so, how detailed and how often. The detail can include statistics for 

each active terminal per line. The configured time interval length (that is, frequency 

of this CENLOG) can range from 5 minutes to 12 hours, and defaults to 10 minutes. 

The default configuration specifies that no line/terminal statistics are to be gathered. 

The NMS SETI command can override the configuration. Data included in this 

CENLOG are: input message count, output message count, input character count, 

output character count, PPID, line/terminal name, and LPH type for each 

line/terminal. Telcon generates this CENLOG. 

STATDCR 

Description: Line/terminal statistics (MESSAGE I/O COUNT AND SIZE). Telcon 


7436 0728–303 7–13

Event 11 LOCAL STORAGE SINGLE BIT ERROR 

Event 11 LOCAL STORAGE SINGLE BIT ERROR 

LOCAL STORAGE SINGLE BIT ERROR 

Description: The DCP architecture provides a way of reading a memory-log table 

that records any single bit (correctable) errors that have been detected along with the 

error-code register for all four ports. Telcon generates this CENLOG. 

Action: None. 

7–14 7436 0728–303


LINE–TERMINAL STATISTICS 


Description: With the NMS SETI command, statistics on a line or line/terminal basis 

can be collected. This event is not displayed at the NMS console and requires a log 

reduction program for analysis. Telcon generates this CENLOG. 

Action: None. 














STATDCR 



7436 0728–303 7–15

Event 13 Not Defined 


No CENLOGs have been defined for Event 13. 

7–16 7436 0728–303

Event 14 PROCESSOR UTILIZATION STATISTICS 

Event 14 PROCESSOR UTILIZATION STATISTICS 

PROCESSOR UTILIZATION STATISTICS 

Description: Formats a supplementary console message as it displays to show the 

following statistics. These statistics show how well the primary hardware processor 

resources were used over the current statistics interval. 

Example: 

�� 

�� 

�� 

The PEAK CPU idle time is lower than the average to reflect a higher CPU busy 

percent. The 128-byte statistics are the most widely used type of memory buffers. 

They show percents and counts for the amount of available granules of memory. 

Statistics on each active IOP not processing PP related work are kept, calculated, 

collected, reported, and logged for DCP/50s and DCP/30s. These statistics are kept at 

the discretion of the customer’s configuration parameters. 

For example: 

�� 

� �� 

� �� 

�� 

Only the IOP statistics lines appear and are logged for each IOP that is running. 


Action: If the buffer statistics are averaging and peaking at or near zero over several 

hours you should either order more memory for the DCP, or move some users to 

another DCP. 

Note: The IOP statistics do not appear for the DCP/15 model. 

CPUTL 

Description: Network statistics collected. Telcon generates this CENLOG. 

7436 0728–303 7–17

Event 15 SINGLE NODE LOG OF DNS TRACE DATA 

Event 15 SINGLE NODE LOG OF DNS TRACE DATA 

SINGLE NODE LOG OF DNS TRACE DATA 

DNS 

Description: This CENLOG is logged when you take a DTRC. The NMS DTRC 

command traces the path between two points in a DNS network. The reports from the 

individual nodes along the path are logged if the LOGL or LOGC parameters are 

enabled. Use the NMS LOGI command to display this event. For further information 

on the DTRC report format, refer to the Telcon Operations Reference Manual (7831 

5728). Telcon generates this CENLOG. 

Action: None. 

Description: Single node log of DNS trace data. One CENLOG entry is made for 

each trace report that is received in response to the NMS DTRC command. Use the 

NMS LOGI command to display this event. For further information on the DTRC 

report format, refer to the Telcon Operations Reference Manual (7831 5728). Telcon 


7–18 7436 0728–303




7436 0728–303 7–19


7–20 7436 0728–303

Section 8 


Event 1 INVALID TERMINAL SIGN-ON 

INVALID TERMINAL SIGN-ON 

LMS 

Description: Security event. A terminal operator attempted to sign on to the 

network with an invalid $$SON call line. Telcon generates this CENLOG. 

Action: Operator action determined on a site-by-site basis. 

Description: LMS detected an invalid terminal sign-on attempt. Telcon generates 

this CENLOG. 

SNA: 660 - FBDSC not installed, Terminal %%%%-%%%% 

TRS 



2200 hosts. Where % represents a hexadecimal number. The probable cause is a 


Description: If an attempt is made to sign on a terminal that is not configured, or if a 

typing error is made while attempting any $$ message processed by TRS, the error is 

logged. 

R11: LCB 


7436 0728–303 8–1

Event 2 NMS PASSWORD/AUTHORITY ACCESSED FOR CHANGE 

Event 2 NMS PASSWORD/AUTHORITY ACCESSED 

FOR CHANGE 

NMS PASSWORD/AUTHORITY ACCESSED FOR CHANGE 

Description: Security event. A terminal operator attempted to change the NMS 

password or raise the console authority by using the NMS IDEN command. Telcon 


Action: Operator action determined on site-by-site basis. 

MLGEN 

Description: Using NMS IDEN command to change the NMS password, or to raise 

NMS console authority. Telcon generates this CENLOG. 

8–2 7436 0728–303

Event 3 ATTEMPT TO EXECUTE UNAUTHORIZED NMS COMMAND 

Event 3 ATTEMPT TO EXECUTE UNAUTHORIZED 

NMS COMMAND 

ATTEMPT TO EXECUTE UNAUTHORIZED NMS 


7436 0728–303 8–3

Event 4 ATTEMPT TO CONNECT TO INVALID END USER 

Event 4 ATTEMPT TO CONNECT TO INVALID END 

USER 

ATTEMPT TO CONNECT TO INVALID END USER 


8–4 7436 0728–303



INVALID PASSWORD 

Description: Password failed. 


Action: Re-enter password. If the password continues to fail, notify the system 

administrator. 

7436 0728–303 8–5




INVALID TICKET 

Description: Time has expired, attempts to gain access by intruding the system have 

occurred, or a configuration problem between the Security Management Information 

Base (SMIB) and the Telcon security file exists. 

Action: Contact the system administrator. 

8–6 7436 0728–303



INVALID SITE-ID 


Description: Input is coming from an invalid identification (ID) site. 


7436 0728–303 8–7

EVENT 8 CENLOG Messages 



SMIB NOT CATALOGUED 

Description: Security configuration file not initialized. 


8–8 7436 0728–303



SECURITY LOGIN 


Description: Displays terminal ID and user ID when a terminal logs in using NSAC. 

7436 0728–303 8–9

EVENT 10 NMS SECURITY EVENT 

EVENT 10 NMS SECURITY EVENT 

NMS SECURITY EVENT 

Description: Various NMS command executions are logged for security reasons, an 

appropriate supplementary message is appended to the standard CENLOG message. 

Action: None. 

8–10 7436 0728–303

EVENT 11 DCPOS SECURITY EVENT 

DCPOS SECURITY EVENT 

EVENT 11 DCPOS SECURITY EVENT 

Description: Various DCPOS events are logged for security reasons; an appropriate 

supplementary message is appended to the standard CENLOG message. 

Action: None. 

7436 0728–303 8–11

EVENTS 12-15 Not Defined 

EVENTS 12-15 Not Defined 


8–12 7436 0728–303




SNA: 407 - ACTCDRM received from nonconfigured CDRM 

Description: This message occurs as a result of errors or events in SNASS. SNASS 


other SSCPs in the process of establishing sessions. The probable cause is a 


SNA: 425 - Invalid IBM Network Address Received SA = &&&&& 



other SSCPs in the process of establishing sessions. Where & represents a decimal 


7436 0728–303 8–13


8–14 7436 0728–303

Section 9 


CENLOGs in this class result when an administrator alters a facility by issuing an NMS 

command that controls the facility. The change in the operational mode of the facility 

specified in the command is reported in the CENLOG. 

Event 1 ‘UP’ OF FACILITIES COMMAND 

‘UP’ OF FACILITIES COMMAND 

LMS 

LMS 

Description: Log trace event for NMS command. Telcon generates this CENLOG. 

Action: None. 

Description: LMS processed an NMS UP LINE command. Telcon generates this 

CENLOG. 

Description: LMS processed an NMS UP TERMINAL command. Telcon generates 

this CENLOG. 

SNA: 234 – PU config status --> UP 

Description: This standard message reports that a PU was brought up successfully. 

SNA: 259 - LINE config status --> UP 

Description: This standard message reports that a line was brought up successfully. 

SNA: 408 - CDRM configuration status -> UP 



other SSCPs in the process of establishing sessions. It is informational only. 

7436 0728–303 9–1


SNA: 410 - CDRSC configuration status -> UP 




SNA: 412 - DLM configuration status -> UP 




SNA: 426 - COS configuration status -> UP 





SNA: 601 - Max GW’s already configured, ‘Up GW’ ignored 




SNA: 602 - Max ELU/SLE CB’s configured, ‘Up ELU’ ignored 




SNA: 627 - GW configuration status -> UP 




SNA: 628 - ELU configuration status -> UP 




9–2 7436 0728–303

SNA: 630 - GW already has status -> ACTIVE 





SNA: 632 - ELU already has status -> ACTIVE 




SNA: 640 - GW status -> DOWN PENDING - Discarded activation 




SNA: 1029 - PU configuration status -> UP 



SNA: 1030 - LU configuration status -> UP 



SNA: 2429 - @@@@ config status --> UP 

Description: This message is from the New Boundary Function (NBF). In this 

message, @@@@ represents ASCII characters. The NBF handles all of the 

management messages for 3270 connected devices, IBF connection to NCPs, and 

connections to NT 2.1 devices. It is informational only. 

UP Terminal 


(PDNURS) received an NMS UP TERM command. This event indicates the initiation 

of a change in a facility’s status. This event includes the TERM name. 




7436 0728–303 9–3


X.25: UP PDTE 

Description: An NMS UP PDTE command was entered. This event indicates the 

initiation of a change in a facility’s status. 

Attributes affected: Supplementary Text Message, Display Event. The X.25 PSCS 


Procedure: PDNMS 

X.25: UP PTRK 

Description: An NMS UP PTRK command was entered. This event indicates the 

initiation of a change in a facility’s status. 

Attributes affected: Supplementary Text Message, Display Event. The X.25 PSCS 


Procedure: PDNMS. 

9–4 7436 0728–303

Event 2 ‘DOWN’ OF FACILITIES COMMAND 


‘DOWN’ OF FACILITIES COMMAND 

Description: Log trace event for NMS command. Telcon generates this CENLOG. 

Action: None. 

DOWN Terminal 


(PDNURS) received an NMS DOWN TERM command. This event indicates the 

initiation of a change in a facility’s status. This event includes the TERM name. 




Line config status -> DOWN 

LMS 

LMS 

Description: This standard status message reports that a line was brought down 

successfully. 

Description: LMS processed an NMS DOWN LINE command. Telcon generates this 

CENLOG. 

Description: LMS processed an NMS DOWN TERMINAL command. Telcon 


SNA: 233 – PU config status --> DOWN 

Description: This standard message reports that a PU was brought down 

successfully. 

SNA: 258 - LINE config status --> DOWN 

Description: This standard message reports that a line was brought down 

successfully. 

7436 0728–303 9–5


SNA: 409 - CDRM configuration status -> DOWN 




SNA: 411 - CDRSC configuration status -> DOWN 




SNA: 413 - DLM configuration status -> DOWN 




SNA: 427 - COS configuration status -> DOWN 





SNA: 612 - ELU configuration status -> DOWN 




SNA: 629 - GW configuration status -> DOWN 




SNA: 631 - GW already has status -> INACTIVE 




9–6 7436 0728–303

SNA: 633 - ELU already has status -> INACTIVE 





SNA: 641 – ELU status -> INACT, Configuration status -> UP 




SNA: 1021 - PU configuration status -> DOWN 


attached to SNA/net. It is informational only. 

SNA: 1022 - LU configuration status -> DOWN 



SNA: 2430 - @@@@ config status --> DN 

Description: This message is from the New Boundary Function (NBF). In this 

message, @@@@ represents ASCII characters. The NBF handles all of the 

management messages for 3270 connected devices, IBF connection to NCPs, and 

connections to NT 2.1 devices. It is informational only. 

SNA: 2445 – Bind’s LU type (&&) not equal to configured (&&) 

TRS 

Description: The configured LU type does not match the LU type in the BIND. 

Contact the person responsible for maintaining the SNA/net portion of the DCP 

configuration and update the LU type. This could be due to a mismatch in the IBM 


Description: TRS received from NMS using the LPH, an NMS HIC for processing HIC 

DOWN FACILITY command. 

R11: LCB 


7436 0728–303 9–7


TRS 

Description: TRS received an UP FACILITY command for processing. 

R11: LCB 

R14: IOPID 


TTYLPH 

Description: This event occurs following a PP state-item crash for each line 

configured (and not currently down) on the line module where the PP program 

crashed. This log entry indicates that down-facility processing is being initiated for 

this line. Other information logged: the line control block (LCB) of the line is being 

downed. Telcon generates this CENLOG. 

UDLCRS 

Description: R8=0017. AE$UD130. (UDLC): NMS LINE DOWN REQUEST. The line 

has been disconnected. Telcon generates this CENLOG. 

X.25: DOWN PDTE 

Description: The X.25 PSCS NMS module (PDNMS) received an NMS DOWN PDTE 

command. This event indicates the initiation of a change in a facility’s status. 




X.25: DOWN PTRK 

Description: The X.25 PSCS NMS module (PDNMS) received an NMS DOWN PTRK 

command. This event indicates the initiation of a change in a facility’s status. 




9–8 7436 0728–303

X.25: NMS DOWN Line command 


Description: The X.25 PSCS line termination module (PDNSVS) received an NMS 

DOWN LINE command. This event indicates the initiation of a change in a facility’s 

status and includes the LINE name. 

Attributes affected: Supplementary text message, Line event, Line Control Block 

(LCB) in register R11. The X.25 PSCS program product generates this CENLOG. 


7436 0728–303 9–9

Event 3 ‘START’ OF FACILITIES COMMAND 

Event 3 ‘START’ OF FACILITIES COMMAND 

‘START’ OF FACILITIES COMMAND 

LMS 

LMS 

Description: Logged event for NMS commands. Telcon generates this CENLOG. 

Action: None. 

Description: LMS processed an NMS START LINE command. Telcon generates this 

CENLOG. 

Description: LMS processed an NMS START TERMINAL command. Telcon 


STRT Terminal 


(PDNURS) received an NMS STRT TERM command. This event indicates the 

initiation of a change in a facility’s status and includes the TERM name. 




9–10 7436 0728–303

Event 4 ‘STOP’ OF FACILITIES COMMAND 

Event 4 ‘STOP’ OF FACILITIES COMMAND 

‘STOP’ OF FACILITIES COMMAND 

LMS 

LMS 

Description: Logged event for NMS commands. Telcon generates this CENLOG. 

Action: None. 

Description: LMS processed an NMS STOP LINE command. Telcon generates this 

CENLOG. 

Description: LMS processed an NMS STOP TERMINAL command. Telcon generates 

this CENLOG. 

STOP Terminal 


(PDNURS) received an NMS UP STOP command. This event indicates the initiation of 

a change in a facility’s status and includes the TERM name. 




7436 0728–303 9–11

Event 5 NMS MOVE OF FACILITIES 

Event 5 NMS MOVE OF FACILITIES 

NMS MOVE OF FACILITIES 

Description: Logged event for NMS command. Telcon generates this CENLOG. 

Action: None. 

MLMOVE 

Description: A configured facility has been moved, using the NMS MOVE command. 


9–12 7436 0728–303

Event 6 ‘SWITCH’ COMMAND ISSUED 

‘SWITCH’ COMMAND ISSUED 

Event 6 ‘SWITCH’ COMMAND ISSUED 

Description: Operator initiated an SWT command for resilient system. Telcon 


Action: None. 

7436 0728–303 9–13

Event 7 ONLINE CONFIG LOG ENTRY 

Event 7 ONLINE CONFIG LOG ENTRY 

ONLINE CONFIG LOG ENTRY 

Description: A supplementary message is appended to the standard message 

showing the change to the Telcon configuration. This CENLOG is logged but not 

automatically displayed. The NMS LOGI command can be used to display these 

CENLOGs. The first supplementary message contains the site-id and processor name 

of the inputting console. Subsequent supplementary messages contain the individual 

online changes. 

The CENLOG Analysis Program (CAP) can be used to collect the online CENLOG 

changes. 

Action: None. 

9–14 7436 0728–303

Event 8 NMS COMMAND COMPLETION STATUS 

Event 8 NMS COMMAND COMPLETION STATUS 

XFER 1-PRC1 from=CD6R2*PRSTATN1, 

to=xhost::PRC1*PRSTATN101. DCP file blocks transferred =800, DCP 

file EOF found. 

Description: Records each XFER command completion. The success or failure of 

each XFER is recorded. 

Action: None. 

7436 0728–303 9–15




9–16 7436 0728–303




SNA: 428 - DOMAIN UP ignored, PLEASE RESTART SNA/net 




SNA: 429 - Multiple Domain Cards Posted During ISYSTEM 





SNA: 1028 - Command ignored, PU not up/active 



SNA: 2210 - Snatrunk configuration status --> @@@@ 


DCA traffic across an SNA network. In this message, @ represents an ASCII 

character. It is informational only. 

SNA: 2213 - Down inv state, retry or down TG to force down 


DCA traffic across an SNA network. The probable cause is a software problem. 

SNA: 2433 - Cannot down LU while PU/POOL down in progress 

Description: This message is from the New Boundary Function (NBF). The NBF 

handles all of the management messages for 3270 connected devices, IBF connection 

to NCPs, and connections to NT 2.1 devices. It is informational only. 

SNA: 2434 - Cannot down PU while POOL down in progress 




7436 0728–303 9–17


SNA: 2435 - Down already in progress 




SNA: 2436 - Already @@@@ 

Description: This message is from the New Boundary Function (NBF). The @ 

represents an ASCII character. The NBF handles all of the management messages for 

3270 connected devices, IBF connection to NCPs, and connections to NT 2.1 devices. 

It is informational only. 

9–18 7436 0728–303

Section 10 


Traffic messages the system is unable to deliver (UDMs) and time/date changes 

characterize the CENLOGs in Class 10. 

Event 1 DISCARDED MESSAGE (LOST MESSAGE) 

DISCARDED MESSAGE (LOST MESSAGE) 

Description: Message discarded–no path. Telcon generates this CENLOG. 

Action: None. 

SNA: 682 – CANNED MESSAGE RECEIVED:FUNC=%%%% 

ID1=%%%% ID2=%%%% 

Description: This message occurs when a canned message is received by the 

crossover application bridge (XAB). The % represents a hexadecimal number. 

SNA: 2800 - Send Failed 

Description: Internal software error in the SNA/net SNMP submanaged Program. 

Unable to send a message, the message is discarded. 

7436 0728–303 10–1



DUC 

Description: DUC discarded the message for one of the following reasons: 

• Received data while IM pending (IM PENDING) 

• Received invalid NDU sequence number (SEQ NUMBER INVALID) 

• Time-out on a reassembling PDU (MESSAGE LOST, REMAINING PDU 

DISCARDED) 

• Timeout on a reassembling PDU (MESSAGE CONSIDERED LOST) 

• Invalid DUC command received (INVALID MESSAGE) 

• Duplicate NDU found (DUPLICATE MESSAGE) 

• Received invalid SN$ entry number (INVALID N/C ID RECEIVED) R12=SN$ 

address 


DUPLICATE MESSAGE 

Description: The DUC has received a duplicate NDU from the network. This 

message will be discarded. Telcon generates this CENLOG. 

Action: None. 

FRAME NOT SENT 


module in PDNSVS received a discarded message notification. The reason is the port 

processor was unable to successfully send the frame to the network. This event 


R8: CNMS unrecoverable line error reason code 


Attributes affected: Supplementary text message, Line event. The X.25 PSCS 

program product generates this CENLOG. Procedure: PDNSVS. 

INVALID MESSAGE 

Description: DUC received an invalid data message. The DUC header is invalid. 


Action: The long format shows the discarded message. 

10–2 7436 0728–303

INVALID N/C ID RECEIVED 


Description: DUC received an invalid network connection (N/C) ID number. 

Without a valid ID number, DUC cannot find the proper table entry, and has to discard 

the message. Telcon generates this CENLOG. 

Action: Register 15 of the long format has an invalid ID number. 

MESSAGE CONSIDERED LOST 

Description: After waiting for ten seconds, the expected NDU was not received and 

DUC now discards it. Telcon generates this CENLOG. 

Action: This usually indicates a problem with the physical lines. Check all trunk 

lines to ensure that they are functioning properly. The long format will display the 

session entry. 

MSG LOST. REMAINING PDU DISCARDED 

Description: Same as the previous message except the lost NDU was not a complete 

PDU. The rest of the PDU is discarded. The long format displays the session entry. 


Action: None. 

NO PRC TO PRC SESSION/TRUNKS CONFIGURED 

RTC 

RTC 

Description: This CENLOG refers to an error in Route Control where it receives a 

message to be processed, but its tables have not been built. The tables have not been 

built because the configuration does not contain any DCP-to-DCP SESSN statement 

for this processor, or the configuration does not contain any TRUNK statements for 

this processor. Both statements are required for Route Control to work. The system 

discards this message. Telcon generates this CENLOG. 

Action: Add SESSN and/or TRUNK statements to the configuration. 

Description: UDLC received a control message that was not a valid entry and the 

message is being discarded. Telcon generates this CENLOG. 

Description: A data message was received with an invalid routing header. Telcon 


7436 0728–303 10–3


RTC 

RTC 

Description: A message was received that did not have a valid route. Telcon 


Description: Route control got a message in, but no DCP-to-DCP sessions have been 

configured. The message is discarded. Telcon generates this CENLOG. 

SEQ NUMBER INVALID 

Description: DUC received a network data unit (NDU) with an invalid sequence 

number. The most common cause is UDLC sending a duplicate message. Telcon 


Action: The long format displays the session table. The operator should ensure that 

the session is recovered properly. 

SNA: 676 - Received data ignored (discarded) 

Description: This message occurs as a result of error or events in the Crossover 

Application Bridge (XAB), which handles traffic between SNA resources and OS 2200 

hosts. The probable cause is a software problem. 

SNA: 1623 - Message could not be sent 

Description: This message appears as a result of errors in the DTPLINK, the part of 

SNA/net that enables SNA/net to communicate with other SNA/nets as if they were 


Unacked Frame 


module in PDNSVS received a discarded message notification. The reason is the port 

processor never received an acknowledgment by the network for a frame that it had 

sent. This event includes the LINE name. 

R8: CNMS unrecoverable line error reason code 



program product generates this CENLOG. Procedure: PDNSVS. 

10–4 7436 0728–303

X.25: Undelivered, Non-Data Packet 


Description: The network layer module (PDNL3) received an undelivered packet 

notification from the link layer. The packet sent to the network is a non-data type 

packet. The undeliverable packet is discarded. This event includes the LINE name. 

R8: Undeliverable reason code 


Attributes affected: Line event, Supplementary text message. This CENLOG is 

generated by the X.25 PSCS program product. Procedure: PDNL3. 

7436 0728–303 10–5

Event 2 NDL MESSAGE UNDELIVERABLE 

Event 2 NDL MESSAGE UNDELIVERABLE 

CHANGE TO DCP NETWORK CONNECTION STATUS 

Description: Peer DUC has not responded after third retry. Telcon generates this 

CENLOG. The following supplementary messages may be generated: 

�� 

�� 

�� 

�� 

�� 

�� 

If these CENLOGS persist, the routing path to the peer DUC is blocked in at least one 

direction. 

Action: DOWN and UP the trunk lines leading to the peer Telcon. 

SNMP 303 Unable to send message type xx to peer on port nn 

Description: The SNMP Agent reporting this event is unable to send a coordinating 

message to another Agent using an ICS connection. This is probably a problem with 

ICS, especially if this event or other events are reported by other ICS programs in this 

or other ILMs. 

More than one SNMP Agent is loaded and configured within the same ICS domain. As 

each Agent initializes, it forms an ICS connection and passes coordination data 

messages with all other Agents so that all Agents can determine who becomes active. 

Variables: xx the coordination message type attempted to be sent 

nn the port of the SNMP Agent where the message coordinate was to 

be sent 

Action: This event implies a problem with ICS, examine the status of other ICS 

connections and perform any recovery and diagnostic actions recommended for ICS. 

This event could be reported by an SNMP Agent that has not become active; it could 

adversely impact the Agent that is intended to become active. 

If no SNMP Agent is currently active, either restart ICS or reload all ILMs containing a 

configured SNMP Agent to recover from the problem. 

10–6 7436 0728–303

Event 3 UDM MESSAGE UNDELIVERABLE 

Event 3 UDM MESSAGE UNDELIVERABLE 

UDM MESSAGE UNDELIVERABLE 

RTC 

Description: Net change cannot be sent. Telcon generates this CENLOG. 

Action: None. 

Description: A message has been lost in the network and cannot return to the 

originating Telcon node. The buffer is being discarded. Telcon generates this 

CENLOG. 

7436 0728–303 10–7

Event 4 TIME / DATE EVENT 


TIME / DATE EVENT 

Description: Time and date establishment (retrieval from an OS 2200 host or explicit 

setting) event. The event may result from system initialization (PRCSR statement 

SETTIME parameter) or SET command processing. Telcon generates this CENLOG. 

Action: Varies–Refer to supplementary messages that follow. 


TIME/DATE AUTO-SETTING FROM HOST COMPLETED 

Description: Successful completion of time and date retrieval from an OS 2200 host, 

the expected result of system initialization processing for a PRCSR statement 

SETTIME parameter. Telcon generates this CENLOG. 

Action: None. 

TIME/DATE COULD NOT BE AUTO-SET FROM HOST 

Description: The time and date source hosts specified by the PRCSR statement 

SETTIME parameter are unavailable. The hosts may be down, inaccessible through 

the specified name, or simply don’t exist. No automatic retry is attempted. Telcon 


Action: Enter a SET command with an alternate source HOST name or use a SET 

command with explicit TIME and DATE parameters to set the time and date on the 

DCP. 

TIME/DATE NMS EXPLICIT SETTING COMPLETED 

Description: Successful completion of explicit time and date establishment– the 

expected result of a SET command with TIME and DATE parameters. Telcon 


Action: None. 

TIME/DATE NMS SETTING FROM HOST COMPLETED 

Description: Successful completion of time and date retrieval from an OS 2200 host– 

the expected result of a SET command with a HOST parameter. Telcon generates this 

CENLOG. 

Action: None. 

10–8 7436 0728–303

TIME/DATE STILL RETRYING AUTO-SET FROM HOST 


Description: Indicates repeated failure to open a session to the time and date source 

hosts specified on the PRCSR statement SETTIME parameter. 

Open requests are automatically retried at 30-second intervals (this event repeats at 

10-minute intervals) until a request is successful or until the operator enters a SET 

command. Telcon generates this CENLOG. 


command with explicit TIME and DATE parameters to set the DCP time and date on 

the DCP. 

TIME/DATE UNCHANGED–HOST NAME INVALID 

Description: The time and date source host specified by the SETTIME parameter on 

a PRCSR statement is not the name of an ADDRESS, NETADR, or XEU statement in 

the configuration file. Telcon generates this CENLOG. 




TIME/DATE UNCHANGED–APPLICATION UNAVAILABLE 

Description: The time and date source host specified on a PRCSR statement 

SETTIME parameter is available, but does not respond to the time and date retrieval 

request within the response time limit – 30 seconds. 

The network or specified host is having problems or the host is not an OS 2200 host. 





7436 0728–303 10–9




10–10 7436 0728–303

Section 11 


CENLOGs in Class 11 result from automatic facility control alterations made by the 

software control modules. 

Event 1 MODIFICATION IN NODE ROUTING STATUS 

MODIFICATION IN DCP ROUTING STATUS 

Description: This CENLOG refers to statistic information for the network 

administrator. It lets the administrator determine if there are stability problems in the 

network with any of the trunks or DCPs. Every time a trunk goes up or down 

anywhere in the network, one of these CENLOGs appears on every DCP in the 

network. This allows the administrator to determine from a local DCP where linkages 

have gone up or down. Tracking of the CENLOG allows the administrator to 

determine if the problem is intermittent or continuous. This CENLOG does not 

display on the NMS console because initialization is a part of the normal operation of 

the system and would not be useful for the normal operator. Telcon generates this 

CENLOG. 

Action: None, unless there are an unusual number of routing updates from one DCP 

or trunk in the network. The DCP processor name is called out in the CENLOG. You 

can obtain a trunk ID name by entering a DISP TRNK=nn DCP=ccc from an NMS 

console. Analyze the DCP trunk to determine the cause of the instability. 

Supplementary Messages For Class 11, Event 01 

ROUTING UPDATE STARTED BY DCP cccc, TRUNK ID #0nn. 

Description: This CENLOG refers to statistic information for the network 

administrator. It lets the administrator determine if there are stability problems in the 

network with any of the trunks or DCPs. Every time a trunk goes up or down 

anywhere in the network, one of these CENLOGs appears on every DCP in the 

network. This allows the administrator to determine from a local DCP where linkages 

have gone up or down. Tracking of the CENLOG allows the administrator to 

determine if the problem is intermittent or continuous. This CENLOG does not 

display on the NMS console because initialization is a part of the normal operation of 

the system and would not be useful for the normal operator. Telcon generates this 

CENLOG. 

7436 0728–303 11–1

Event 1 MODIFICATION IN NODE ROUTING STATUS 

Action: None, unless there are an unusual number of routing updates from one DCP 

or trunk in the network. The DCP processor name is called out in the CENLOG. You 

can obtain the trunk ID name by doing a DISP TRNK=nn DCP=ccc from an NMS 

console. Analyze the DCP trunk to determine the cause of the instability. 

11–2 7436 0728–303

Event 2 MODIFICATION IN NODE NETWORK CONNECTION 

Event 2 MODIFICATION IN NODE NETWORK 

CONNECTION 

MODIFICATION IN DCP NETWORK CONNECTION 

Description: Network address in UDM state. Telcon generates this CENLOG. 

Action: Register 10 in the long format shows the Telcon node that is in a UDM state. 

Verify that this Telcon node is in fact down, and that it is not just a connection 

(TRUNK) problem. 


DUC 

Description: Invalid N/C name received no more DS$SEG. Telcon generates this 

CENLOG. 

INVALID N/C NAME RECEIVED 

Description: During the DUC initialization, a SESSN configuration statement name 

was received, but did not belong in the processor. Telcon generates this CENLOG. 

Action: The long format shows the buffer received with the SESSN statement 

configuration name. Check the configuration for errors. 

TOO MANY SESSIONS CONFIGURED•SEE AC$SESSN 

Description: The number of DUC-to-DUC sessions exceeds the maximum number 

allowed in the system. Telcon generates this CENLOG. 

Action: Increase the AC$SESSN value by using a NEWCON SGS and regenerate the 


7436 0728–303 11–3

Event 3 CHANGE IN THE INTER-NODE TRUNK STATUS 

Event 3 CHANGE IN THE INTER-NODE TRUNK 

STATUS 

CHANGE IN THE INTER-DCP TRUNK STATUS 

Description: Change in logical link (trunk) state. Telcon generates this CENLOG. 

Action: None. 

X.25 part of trunk is down 

Description: The DCP-to-DCP path count module (PDNUDLC) has received a trunk 

path disabled notification from the X.25 PSCS trunk module PDNTRK. All virtual 

circuits for a trunk connection have been disconnected (except in the case of an idle 

trunk state) over an X.25 network. This event includes the facility ID of the trunk. 

Attributes affected: Supplementary text message, Device event. Telcon generates 

this CENLOG for the X.25 PSCS program product. 

Procedure: PDNUDLC 

X.25 part of trunk is up 

Description: The DCP-to-DCP path count module (PDNUDLC) has received a trunk 

path enabled notification from the X.25 PSCS trunk module PDNTRK. A trunk 

connection now exists over an X.25 network. This event includes the facility ID of the 

trunk. 

Attributes affected: Supplementary text message, Device event. Telcon generates 

this CENLOG for the X.25 PSCS program product. 

Procedure: PDNUDLC 

11–4 7436 0728–303

Event 4 RESILIENT NODE IS NOW 

Event 4 RESILIENT NODE IS NOW 

RESILIENT DCP IS NOW {ONLINE FROM cccccccc TO 

cccccccc/STANDBY FROM cccccccc TO cccccccc/LOADSHARING 

WITH cccccccc/LIMBO} 

SRC 

Description: The Telcon node has affected a resilient switch into the state indicated. 


Action: Where cccccccc is a configured PRCSR named after initial program load or 

after the NMS ONLN or STBY command is processed, this message is informational 

only. During normal operation, it could indicate failure of the alternate Telcon node 

or a problem on the node-to-node session. 

Description: The DCP has brought a resilient switch into the indicated state. Telcon 


7436 0728–303 11–5

Event 5 ALTERNATE NODE IS NOW 

Event 5 ALTERNATE NODE IS NOW 

ALTERNATE DCP IS NOW {UP/DOWN/PROTECTING US/NOT 

PROTECTING US} 

SRC 

Description: Indicates a change in the status of the alternate Telcon node. Telcon 


Action: If the status of the alternate Telcon node is DOWN or NOT PROTECTING US 

(has gone online for a different Telcon node), you must restore the failed Telcon node. 

The �� and �� messages indicate a Telcon node that failed is back in 

operation. 

Description: This indicates a change in the status of the alternate Telcon node. 

11–6 7436 0728–303

Event 6 RESILIENCY AUDIT FILE PROBLEM 

Event 6 RESILIENCY AUDIT FILE PROBLEM 

RESILIENCY AUDIT FILE PROBLEM 

Description: The problem occurred while building the audit file. SRC is attempting 

to rebuild it. Telcon generates this CENLOG. 

Action: Ignore if the reinitialization is successful. If the reinitialization is not 

successful, take a dump and reload from the host. 


SRC AUDIT FILE PROBLEM: BAD CONFIRMATION 

Description: A bad confirmation was received from the alternate Telcon node after 

sending the audit file contents. Telcon generates this CENLOG. 

Action: Ignore if the reinitialization is successful. If the reinitialization is not 

successful, take a dump and reload from the host. 

SRC AUDIT FILE PROBLEM: FILE COMPROMISED 

Description: The audit file is compromised and can no longer be trusted. Telcon 


Action: Dump the Telcon node when convenient and reload from the host. 

SRC AUDIT FILE PROBLEM: AUDIT FILE FULL 

SRC 

Description: The audit file is now full and no more information will be saved. All 

subsequent online configuration and NMS changes will not be sent to the backup 

Telcon node when the path is restored. Telcon generates this CENLOG. 

Action: On the next generation, you can increase the audit file size by increasing the 

size of AC$SRCAF in the module AACONFIG. You should take immediate action to 

restore communication to the backup Telcon node. 

Description: The problem occurred while building the audit file. SRC is attempting 

to rebuild it. Telcon generates this CENLOG. 

7436 0728–303 11–7

Event 7 SWITCH NOTIFICATION 


SWITCH NOTIFICATION 

Description: An internal process issued a command to an LSM or RCM, but the 

requested hardware could not be accessed. Telcon generates this CENLOG. 

Action: The customer engineer and systems analyst need to examine the hardware 

and the Telcon configuration to determine the problem. 


A–B Switch responded with an I error 

Description: A command sent to the device has resulted in the device responding 

with an I (incomplete) status. The matrix switch handler generates this CENLOG. 

Action: Check hardware connections and configuration. 

Action for port ssss and dddd failed. Error: nnnn 

Description: Connection of ports ssss and dddd failed due to the error specified. 

The matrix switch handler generates this CENLOG. 

Action: Error nnnn is defined by the line switch. Contact your line switch 

representative. 

Bad A–B Switch line speed or timefill 

Description: An I (incomplete), S, or X status from the device could be a result of a 

bad configuration defining the line speed control line or a bad timefill value has been 

specified. The matrix switch handler generates this CENLOG. 

Action: Check the configuration for correct TTY device values with respect to line 

speed and/or number of timefill characters. 

Bad number of A–B Switch device ports configured 

Description: The number of ports entered on the IDENT parameter in your 

configuration is larger than the number of physical ports on the device. The matrix 

switch handler generates this CENLOG. 

Action: Correct the number of ports in your configuration. 

11–8 7436 0728–303

Connected with the device on port nnnn 


Description: The control line for the device has been successfully connected and is 

responding. The matrix switch handler generates this CENLOG. 

Action: None. 

Device not connected..full device table 

Description: The LSM software’s Line Switch Control Table size has been exceeded 

by attempting to connect too many line switch devices. The matrix switch handler 


Action: Disconnect an inactive line switch device if possible and then connect the 

one that caused this CENLOG message. Or reassemble other LSM software 

components with the PASCAL variable LSMTblSiz increased to the number of line 

switch devices plus one. 

H/W alarm aaaaaaaa type: nnnn Rack: nn Address: nnnn 

Description: The device has posted an error or recovery alarm message. The 

aaaaaaaa field contains the error or recovery indication. Significance of the type, 

rack, and address fields must be determined by a line switch engineer. The matrix 

switch handler generates this CENLOG. 

Action: These messages (alarms) can occur and no action is required; however, this 

must be determined by the user. If action is required, contact your Unisys 


HOST DOWN NO SWITCH 

Description: Neither Telcon node has a channel open to the host. It is assumed that 

the host is down and no resilient switch is affected. Telcon generates this CENLOG. 

Action: Bring the host back up. 

HOST UP SWITCH 

Description: A critical host channel has failed on the online Telcon node. The 

alternate Telcon node still has a channel open to the host, so a resilient switch is 

affected. Telcon generates this CENLOG. 

Action: Bring the failed host channel back into operation. 

7436 0728–303 11–9


LSM DID NOT SWITCH 

Description: The LSM did not successfully switch all of the lines. Telcon generates 

this CENLOG. 

Action: The customer engineer and systems analyst need to examine the 

hardware/Telcon configuration and the LSM hardware to determine the problem. 

Port ssss is connected to port dddd 

SRC 

SRC 

Description: Port ssss is connected to port dddd. This is an informational message. 

The matrix switch handler generates this CENLOG. 

Action: None. 

Description: SRC sent an LSM command to UDLC that could not be executed. 


Description: SRC received an unrecognizable error code from UDLC in response to 

an LSM/RCM command. 



S/W error: Msg ID nn (Caused by: nn) 

Description: A Line Switch software error occurred. Msg ID gives the procedure in 

the software that failed. The “Caused by: nn” number is only valid based on the “Msg 

ID nn” value. The matrix switch handler generates this CENLOG. 

Action: Contact your Unisys representative. Be prepared to submit the values that 

appear in the CENLOG message (Msg ID nn and Caused by: nn). 

11–10 7436 0728–303

Unable to Configure The Device 


Description: While attempting to initialize or reinitialize an A–B Switch device, the 

device returned an I (incomplete) error status. The matrix switch handler generates 

this CENLOG. 

Action: Check the physical connections. 

UNIDENTIFIED ERROR CODE 

Description: An internal process has received an unrecognizable error code after 

issuing a command to an LSM or RCM. Telcon generates this CENLOG. 


7436 0728–303 11–11

Event 8 RESILIENT MOVE COMPLETION 

Event 8 RESILIENT MOVE COMPLETION 

Resilient Move Completion: Good/Bad 

Description: This CENLOG provides information about the outcome of a resilient 

move from a line to a spare line. A resilient move can be initiated by either the SRC 

detecting a PP State Item or an operator performing an RMOV command on an NMS 

console. If the resilient move completion status is bad, the line will be inoperative. 

This could be caused by another line using the spare port, even though it is not 

configured to use the spare line. 

Action: In this case, check the configuration for port conflicts. Otherwise, check all 

applicable hardware and repair or replace as necessary. 

11–12 7436 0728–303


Supplementary Messages 


SNA: 681 – NETWK RECVRY IN PROGRESS:FUNC=%%%% 

ID1=%%%% ID2=%%%% 

Description: This message occurs when a resilient host network switches to its 

standby host. DTP sends the crossover application bridge (XAB) a control message 

equating to “Network Recovery in Progress; Possible Loss of Input.” The % represents 

a hexadecimal number. 

System Integrity Monitor Terminating Telcon 

Description: The system integrity monitor (SIMON) has sent a heartbeat message to 

itself in the DCP/600. If the heartbeat is not received back in the allotted amount of 

time, SIMON assumes that the system is hung and terminates Telcon. Telcon 


Action: When Telcon terminates, a system dump should be taken and analyzed to 

determine the cause of the system congestion. A UCF may be submitted. 

7436 0728–303 11–13

Event 10 RESILIENCY EVENT NOTIFICATION 

Event 10 RESILIENCY EVENT NOTIFICATION 

Resiliency Event Notification 

Description: This CENLOG provides information about a resilient SRC switch that 

has occurred. Telcon generates this CENLOG. 

Action: The following items should be investigated by the system analyst or 

customer engineer to determine the cause of the problem: 

• CENLOG supplementary message 

• Telcon configuration 

• DCP and related hardware 

• Telcon dump 


HB Receive Timer Timeout 

Description: SRC has sent a heartbeat to the alternate Telcon in a resilient 

environment. A heartbeat has not been returned in the allotted amount of time. 

Action: SRC issues a resume heartbeat command. If the resume fails, then the cause 

of the inability of the two Telcons to communicate needs to be determined. 

Switch/Status-Confirm Timer Timeout 

Description: A resilient SRC switch is in progress but the switch did not complete in 

the allotted amount of time. 

Action: The cause of the switch failure needs to be determined. 

11–14 7436 0728–303




7436 0728–303 11–15

Event 14 CENLOG FILE AUTORETV XFER COMMAND INVOKED 

Event 14 CENLOG FILE AUTORETV XFER COMMAND 

INVOKED 

XFER PRSTATN!,xhost::PRC1*PRSTATN101 

where: 

xhost The name of the host as defined in the configuration (PRCSR statement) for 

the AUTORETV parameter. 

N1 The 2-character Telcon Node0ID as specified on the Telcon execution 

statement in the Telcon runstream (which defaults to N1 if not specified). 

01 The Telcon PRCSR sequence number in decimal. 

PR AL if transferring the alternate (ALSTAT) CENLOG file, or PR if transferring 

the primary (PRSTAT) CENLOG file. 

Description: CENLOG has switched the logging files and the closed file is being 

autoretrieved to the host. 

Action: None. 

11–16 7436 0728–303

Event 15 CENLOG FILE FULL. SWITCHING ACTIVE LOG FILE FROM: 

Event 15 CENLOG FILE FULL. SWITCHING ACTIVE 

LOG FILE FROM: 

PRSTATN1 to file ALSTATN1 

Description: A CENLOG is written to the CENLOG file whenever a switch of local 

CENLOG occurs. N1 is the 2-character Telcon node-ID specified on the Telcon 

execution statement in the Telcon runstream (which defaults to N1 is not specified). 

This CENLOG is logged but not automatically displayed. The NMS LOGI command 

can be used to display this CENLOG. 

Action: Use the LOGI command to search for the last CENLOG switch message, to 

determine when the switch occurred and which local CENLOG file is currently being 

logged into. 

7436 0728–303 11–17




SNA: 1809 – SNMS Standby/Online Level Mismatch -- HALTING 

Description: This message occurs as a result of different levels on the online and 

standby systems. 

Action: Ensure that the same levels for the online and the standby systems are being 

used. 

11–18 7436 0728–303

Section 12 


CENLOGs in this class result from interface errors related to the system’s resources. The 

DCP/OS usually returns these errors in response to requests from Telcon for architecture 

table changes; such as, queues and segments. The cause is typically related to insufficient 

memory to expand the architecture tables. 

7436 0728–303 12–1




12–2 7436 0728–303

Event 2 LOGW COMMAND 

LOGW COMMAND 

Event 2 LOGW COMMAND 

Description: Forced switching of CENLOG files using the NMS LOGW command or 

automatically at midnight. An appropriate supplementary message is appended to the 

standard CENLOG message. 

Action: None. 

7436 0728–303 12–3




12–4 7436 0728–303

Event 6 OPEN/CLOSE ERROR REPORTED FROM FILE MANAGER 

Event 6 OPEN/CLOSE ERROR REPORTED FROM 

FILE MANAGER 

OPEN/CLOSE ERROR REPORTED FROM FILE MANAGER 

Description: An open or close mass storage file request (either from an operator at a 

system console or from a procedure) was not completed due to an error. Telcon 


Action: If you made the request from a system console, check for an illegal file name, 

unknown file name, unknown volume name, or unknown device type. Correct and 

retry as necessary. If the request was from a procedure, the procedure must handle 

the error. If the error continues or is not handled correctly, take a system dump of the 

Telcon node when the error is displayed. Give it to the appropriate Unisys 


7436 0728–303 12–5

Event 7 MASS STORAGE ACCESS ERROR 


MASS STORAGE ACCESS ERROR 

Description: A mass storage file request, such as a READ or WRITE, was made 

either from an operator at a system console or from a procedure. An error status was 

returned after the request. This could be due to either a physical hardware error or to 

operational conflicts. Telcon generates this CENLOG. 

Action: Attempt to use disk commands for the suspected disk volumes. If this error 

repeats itself and if operational conflicts are not suspected, then request that an 

engineer run some diagnostic testing on that volume. As a last resort, that volume can 

be reformatted or reprepped using DCP/OS commands. Refer to the DCP/OS 

Operations Reference Manual (7831 5702). 

CFACCS: FILE CATALOGUE ERROR: XXXXX 

Description: Configuration file could not be expanded because a scratch file could 

not be catalogued. The file manager error code has been translated to an error 

message and will be appended dynamically to the right of this message. 

SMRP 

Description: Error return from a call to file control. Input is discarded. Telcon 


SNA: 815 - Dyrd file read unsuccessful, info will be re-learned 

Description: This message is the result of an internal file access error by the SNA/net 

ERVR module. This message is informational only. 

SNA: 816 - Dyrd file initialization failed: file error = %%%% 


ERVR module. This message is informational only. The file access exception status is 

included in this message. 

SNA: 817 - Dyrd file recording turned off: file error = %%%% 


ERVR module. This message is informational only. The file access exception status is 

included in the message. 

12–6 7436 0728–303


SNA: 1819 - SNMS Move - I/O Error, move cancelled 

Description: This message occurs as a result of errors in SNMS Pascal, the part of 

SNA/net that processes operator commands. The probable cause is a hardware 

problem. 

7436 0728–303 12–7

Event 8 SYSTEM SERVICE CALL EXCEPTION STATUS 

Event 8 SYSTEM SERVICE CALL EXCEPTION 

STATUS 

SYSTEM SERVICE CALL EXCEPTION STATUS 

Description: A request was made to a system-service routine to perform some 

function, but the system service routine rejected the request and instead returned an 

error status. Examples of system-service routines are configuration file access and 

DCP/OS architecture services. Telcon generates this CENLOG. 

Action: If the system does not appear to be working, take a system dump. 

INSTDC 

Description: INSTDC failed to make catalog entry for the instrumentation/statistics 

file. The configured file size for the file may be too large or too many files have been 

cataloged. 

R0: File control error code 


Load Fail on Port XXX (not responding) 

Description: An attempt to load an ILM failed while attempting to initialize a line. 

The ILM is not responding. 

Action: Retry the line initialization or free the port and retry the line initialization. 

Load Fail on Port XXX (already owned) 

Description: The ILM Platform attempted to initialize a line on a port. The DCP/OS 

returned a status indicating the port was owned by another run. 

Action: If the DCP is dual partition, the port may be assigned to the other partition. 

The run on the partition in question must have the same ‘Application ID’ to assign the 

port. 

If the port is assigned to another run, the port is unavailable for use. Identify the run 

that has the port assigned and take the appropriate action to free the port from the 

other run. 

12–8 7436 0728–303


Load Fail on Port XXX (no file or elt) 

Description: The load element for an ILM has the hardware type appended to the 

load file name. In an attempt to initialize a line, the ILM Platform could not locate a 

loadfile for the appropriate hardware type. 

Action: Ensure the correct ILM load element exists in the ‘Run Qualifier’*ILMLOAD 

file. 

SNA: 1603 - Error =x%%%% in extending segment for PCB 

Description: This message appears as a result of errors in DTPLNK, the part of 


physically adjacent. The word error in the message represents a specification error in 

DCA. Where x%%%% represents a hexadecimal number. Refer to the Telcon 

Programming Reference Manual (7436 0710) for further information. The probable 


SNA: 1604 - Error =x%%%%, creating segment for PCB 




DCA. The x%%%% represents a hexadecimal number. Refer to the Telcon 

Programming Reference Manual (7436 0710) for further information. Probable 

causes include a resource availability (out of memory, out of disk storage) or software 

problem. 

SNA: 1605 - Error =x%%%% putting PCB segment in PST 







SNA: 1606 - Error =x%%%% getting send queue number 







7436 0728–303 12–9


Unable To Delete X.25 System Segment 

Description: The X.25 line termination module (PDNSVS) was unable to successfully 

complete the disabling of an X.25 line. One or more dynamic system segments 

chained from the Line Control Block (LCB) could not be deleted. This event includes 

the LINE name. 

Attributes affected: Line event, Recoverable error event, Line Control Block (LCB) 

address in register 

R11: The X.25 PSCS program product generates this CENLOG. 


UNABLE TO RE-INIT PORT AFTER STATE ITEM 

Description: The X.25 line services module (PDNSVS) was unable to successfully restart 

the port processor after receiving a port processor state- item notification. 

PDNSVS could not create and add queues for this port processor. This event includes 


Attributes affected: Supplementary text message, Line event, Error event. The 

X.25 PSCS program product generates this CENLOG. 


UDLCRS 

Description: The line is disconnected; however, because of an error in accessing the 

line information table, the line is hung until a network administrator brings it down 

R8: 0036. AE$UD160. (UDLC): LINE DISC FAILURE: CONFIG LINE READ ERR. 

DOWN/UP THE LINE 

R9: Most recent NAK-1 detail code 

R10: Active device counts word from SCT 

R11: LCB/SCT address 

R12: NS$STAT1 word from SCT (status flags) 

R13: NS$STAT2 word from SCT (more status flags) 

R14: LINE-ID 


12–10 7436 0728–303

UDLCRS 


Description: The line is disconnected as a result of a network administrator 

requesting to bring down the line; however, because of a configuration access error on 

the SB$UNUSE function, the line is hung until it is successfully brought down by a 

network administrator. Telcon generates this CENLOG. 

R8: 0037. AE$UD161. (UDLC): LINE DISC FAILURE: CONFIG SB$UNUSE ERR. 

DOWN/UP THE LINE 

UDLCRS 

Description: A UA response to an operational mode set command was received. 

The station required the extended control field; however, the pool of static modulo 

128-station queues was empty. An information transfer state could not be established. 


R8: 003F. AE$UD202. (UDLC): ENTER ITS FAIL: DCP/OS REJECTED A CREATE 

QUEUE CALL 

7436 0728–303 12–11

Event 9 INSUFFICIENT SYSTEM RESOURCES (STORAGE) 

Event 9 INSUFFICIENT SYSTEM RESOURCES 

(STORAGE) 

INSUFFICIENT SYSTEM RESOURCES (STORAGE) 

RTC 

RTC 

RTC 

Description: Insufficient system resources. Telcon generates this CENLOG. 

Action: At this point, the system is very low on free buffer space. The operator could 

slow traffic on the communication lines until the problem clears up. If this is not 

satisfactory or the problem does not clear up, take a system dump of the Telcon node 

and give it to the appropriate Unisys representative. 

Description: Could not obtain a DSSN for the RT$ routing table, or could not obtain 

a PST. Telcon generates this CENLOG. 

Description: An error occurred while building the route control trunk table (TD$). 


Description: DUC SN$ table was not available for route control to register. Telcon 


SNA: 617 - Not enough space (%%%%) for FID2 to SNAPPI 



2200 hosts. Where % represents a hexadecimal number. The probable cause is a 


SNA: 619 - SCB table is full 




SNA: 634 - Correlation Pool Table is full 




12–12 7436 0728–303


SNA: 636 - Requested LINK AREA is full 




SNA: 688 - Unable to create dynamic queue - Attempting to retry 




SNA: 803 - link area unexpandable, cursiz=%%%% 


network routing portion of SNA/net. Where % represents a hexadecimal number. The 


SNA: 1023 - Session closed, BF link area overflow 



SNA: 2401 - MM create error, mmerr %%%% syserr %%%%, 

@@@@@@@@ 

Description: This message is from the New Boundary Function (NBF). Where %%%% 

represents a hexadecimal number and @@@@ represents ASCII characters. The NBF 



SNA: 2804 - ICS Connect - Allocate CB failed 


management Protocol) Submanaged Program. Indicates a new control block could 

not be allocated due to a software error or insufficient system memory. 

SNA: 2810 - (NSMPMOA) Get Lookup CB - Allocate CB failed 


Management Protocol) Submanaged Program. Indicates a new control block could 

not be allocated for resource lookup, due to a software error or insufficient system 

memory. 

7436 0728–303 12–13


SNMP 402 Unable to allocate Get Response buffer 

TRS 

Description: The sub-Agent was unable to allocate enough message buffer space in 

order to return a response message to the MIB manager. 




Action: This event is related to memory requirements. Check the ILM port where the 

SNMP Agent is configured and choose an ILM with more memory. 

If other events are reported then this could be a memory corruption problem. Dump 

the ILM. 

Description: TRS issued an SB$UNUSE function to configuration access. The return 

status after the request indicates that the function was not completed due to such 

conditions as a file-control access error or a segment that was still assigned by 

another process. TRS performs this function as a result of an NMS command to bring 

down the line. This CENLOG indicates that the command to bring down the line did 

not take effect. 

R11: LCB 


X.25 SNMP: Alarm Event control block creation error (“procedure 

name”) 


allocate a control block for maintaining SNMP Clear, Reset, and Restart statistics that 

occur on a particular X.25 line. This adversely affects the information available for 

one of the X.25 lines related to the X.25 SNMP MIB branch. 

R8, R9: Memory manager result packet 


table of the event packet (ZR$ Pcall packet) received from the X.25 PSCS packet layer 

module, PDNL3. 



12–14 7436 0728–303


X.25 SNMP: mm pool definition for link events failed (“procedure 

name”) 

Description: The X.25 PSCS SNMP interface module (PDNSMP) was unable to set up 

resources for maintaining SNMP link layer statistics. This adversely affects the 

information available for all X.25 lines related to the laph SNMP MIB branch. 


Attributes affected: Recoverable error event, supplementary test message, and a 

talbe of the memory manager packet pool for link layer events. 



X.25 SNMP: mm pool definition for alarm events failed (“procedure 

name”) 

Description: The X.25 PSCS SNMP interface module (PDNSMP) was unable to set 

up resources for maintaining SNMP packet layer statistics. This adversely affect the 

information available for all X.25 lines related to the x25 SNMP MIB branch. 



table of the memory manager packet pool for packet layer events. 

Procedure: The procedure name, which is internal to X.25 PSCS PDNSMP module, is 

displayed as part of the supplementary text message. 

X.25 SNMP: mm pool definition for maintaining mau cmds failed 

(“procedure name”) 

Description: The X.25 PSCS SNMP interface module (PDNSMP) was unable to set 

up resources for maintaining requests for SNMP MIB information from the SNMP 

Agent interface to the ILM. This causes the X.25 PSCS SNMP interface to dismantle 

all connections with the SNMP Agent interface and to become dormant. No SNMP 

MIB information related to X.25 can be retrieved. 



memory manager pool definition packet for maintaining the SNMP Agent request 

messages. 



7436 0728–303 12–15


X.25 SNMP: Unable to allocated buffer (“procedure name”) 


allocate (new or additional) buffer space for sending a message. This causes the X.25 

PSCS SNMP interface to dismantle all connections with the SNMP Agent interface and 

to become dormant. No SNMP MIB information related to X.25 can be retrieved. 

R8-R15: First eight words of the message buffer header (BH$), if present 


first sixty-four words of the message buffer, if present. 

Procedure: This procedure name, which is internal to the X.25 PSCS PDNSMP 


X.25 SNMP: Memory Mgmt. control block Allocate error (“procedure 

name”) 


allocate a memory manager control block. This adversely affects either the 

maintenance of, or the access to, information available in the SNMP MIB for X.25 

protocols. 



Procedure. The procedure name, which is internal to the X.25 PSCS PDNSMP module, 

is displayed as part of the supplementary text message. 

X.25 SNMP: Memory Mgmt. control block Get error (“procedure 

name”) 


retrieve a previously allocated memory manager control block. This adversely affects 

the access to information available in the SNMP MIB for X.25 protocols. 



Procedure. The procedure name, which is internal to the X.25 PSCS PDNSMP module, 

is displayed as part of the supplementary text message. 

12–16 7436 0728–303

Event 10 INSUFFICIENT MASS STORAGE (DISK) 

Event 10 INSUFFICIENT MASS STORAGE (DISK) 

INSUFFICIENT MASS STORAGE (DISK FILES) 

Description: Insufficient space on a disk for a new file or insufficient space in a file 

for the requested operation. Telcon generates this CENLOG. 

Action: Delete unnecessary files or recatalog larger files, as per the following 

supplementary messages. 

Supplementary Messages For Class 12 Event 10 

DSA: DIB OVERFLOW–NAME ENTRY FOR name FAILED 

Description: The directory information base (DIB) file is too small for the requested 

configuration. Telcon generates this CENLOG. 

Action: Perform these tasks in the following order: (1) Terminate the Telcon and 

DSA runs; (2) Delete the existing DIB file; (3) Catalog a larger DIB file; (4) Start the 

DSA program; (5) Run the BLDDIB utility; (6) Start Telcon. 

DSA: DIB VERTEX TABLE OVERFLOW–name NOT INSTALLED 

Description: The DSA has received a request that requires a new entry in an already 

full vertex table within the directory information base (DIB). Telcon generates this 

CENLOG. 

Action: None. 

7436 0728–303 12–17

Event 11 MAXIMUM TABLE-SIZE LIMIT REACHED 


NTRLPH 

Description: This event occurs if the remote operator at an NTR site is attempting to 

start up an input device when the DCP is in a soft-throttle or hard-throttle situation, in 

which case the DCP does not have the resources to run the input device. In this case, 

the request for input device initialization is ignored, and the remote operator can retry 

the keyin later. This event is displayed so that the Telcon system operator can answer 

queries from the remote NTR operator as to why input cannot be started. If the 

system gets out of hard or soft throttle, input starts up normally. If this event happens 

frequently, changes should be made to the configuration to keep the system from 

running low on storage. Other information logged: 

R14: The PPID of the line the NTR site is on 

R15: The device number of the input device being denied initialization 


SNMP 302 Unable to allocate peer table entry for port nn 

Description: This event reports the inability of an SNMP Agent to coordinate with 

another Agent using an ICS connection. It indicates either a lack of sufficient 

memory, or possibly corrupted memory. 

More than one SNMP Agent is loaded and configured within the same ICS domain. As 

each Agent initializes, it forms an ICS connection and passes coordination data 

messages with all other Agents so that all Agents can determine which one becomes 

active. Either a run time table entry could not be obtained upon receiving the ICS 

connection indication, or the table entry could not be obtained upon receiving a 

subsequent coordination message from another Agent. 

Variable: nn The ILM port of the SNMP Agent that initiated the ICS connection or 

sent the coordination message. 

Action: This event is related to memory limitations. Check the ILM port where the 

SNMP Agent is configured and choose an ILM with more memory. 

This event could be reported by an SNMP Agent that will not become active; it could 

adversely impact the Agent that is intended to become active. If memory limitations 

have been considered and this event is reported, dump the ILM. 

If no SNMP Agent is currently active, either restart ICS or reload all ILMs containing a 

configured SNMP Agent to recover from the problem. 

12–18 7436 0728–303


STAT PDTE produced output > 16K bytes–excess truncated 

Description: The response message to an NMS STAT PDTE or STAT PTRK 

command has generated more that 16K bytes of data. The response message is 

truncated and displayed. 

Attributes affected: Supplementary text message, Recoverable error event. The 

X.25 PSCS program product generates this CENLOG. 


7436 0728–303 12–19




12–20 7436 0728–303



SNA: 226 - TG=index# Line LMID/MCID read error 


Description: This message occurs as a result of errors or events in the TGC that 

controls lines between SNA/net and IBM subareas. The # is a TG index number. The 

probable cause is a hardware problem. 

7436 0728–303 12–21


12–22 7436 0728–303

Section 13 


Network architecture (DCA layers 1 through 7) events and errors result in the CENLOGs 

associated with class 13. 


(PHYSICAL) 

EVENT/ERROR DETECTED AT L1 (PHYSICAL) 

Description: Line initialization was not completed correctly, or a problem exists with 

the physical line itself. Telcon generates this CENLOG. 

Action: Initialize (ITLN) the line in question (DOWN and UP), and verify that the 

hardware connections are accurate and complete. If the problem does not clear up, 

take a system dump of the Telcon node. 

UDLCRS 

Description: R8: 000B. AE$UD583. (UDLC): CARRIER OFF. Input chain completion 

status of carrier off on the start data transfer PP instruction. The CLC discards the 

input data. 


UDLCRS 

Description: R8: 001C. AE$UD555. (UDLC): PARITY ERROR (PCS). Chain 

completion status of FCS error on a start data transfer PP instruction. The input data 

is ignored. 


UDLCRS 

Description: R8: 001E. AE$UD552. (UDLC): INPUT MESSAGE TOO SHORT TO BE 

VALID. The input data is not of adequate length to contain the address field and 

control field of the frame header. The input data is ignored. Telcon generates this 

CENLOG. 

7436 0728–303 13–1

Event 1 EVENT/ERROR DETECTED AT L1 (PHYSICAL) 

UDLCRS 

Description: R8: 001F. AE$UD556. (UDLC): LINE MODULE REPORTS INPUT 

MESSAGE ABORT. Input chain completion status of abort on the start data transfer 

PP instruction. The CLC discards the input data. 


UDLCRS 

Description: R8: 0023. AE$UD580. (UDLC): OVERRUN: IOP UNABLE TO KEEP UP 

WITH INCOMING DATA RATE. The start data transfer (SDT) chain completion status 

includes overrun. 


UDLCRS 

Description: R8: 0026. AE$UD581. (UDLC): UNDERRUN. The start data transfer 

(SDT) chain completion status includes underrun. 


13–2 7436 0728–303

Event 2 EVENT/ERROR DETECTED AT L2 (LINK) 


EVENT/ERROR DETECTED AT L2 (LINK) 

Description: A procedure that transfers information across a physical link detected 

an error. Such errors may be either recoverable or fatal. For fatal errors, a system 

dump may be initiated or the procedure may be blocked. Telcon generates this 

CENLOG. 

Action: This may be a symptom of problems of a particular physical link the user 

encountered. This message may signal the operator to take a system dump when 

attempting to trap such a problem. Frequent occurrences of such errors/events may 

indicate that corrective action should be taken. 

ALPMCP 

Description: The ASYNCH link service has detected a software error. The error 

severity code is in R10, and the error code (6Fxx) is in R11. Severity codes are as 

follows: 0 = fatal, 1 = serious, 2, 3, 4 = trivial. Telcon generates this CENLOG. 

ASYNMLCP 

Description: The ASYNCH link service has detected an input error. 

R8 = 0024 

R9 = 8000 No buffer - the port processor could not obtain a buffer for message 

4000 Input limit - more input came in that there is buffer space 

0400 Message timeout - input came in without an end of message character 

0200 DSR off - data set ready has been dropped and the line will disconnect 

0100 Parity error - configured line speed, parity or character length does not 

match what the hardware or software in PC is set up to 

0040 Data overrun - the port processor cannot keep up with the rate at which 

the input is being received 

PDNSVS 

Description: The X.25 line initialization module (PDNSVS) was unable to successfully 

complete the connection of an enabled line. This event includes the LINE name. 

R15: Error reason code 

Attributes affected: Line event, Configuration event, Line Control Block (LCB) 

address in register R11. The X.25 PSCS program product generates this CENLOG. 

Procedure: PDNSVS. 

7436 0728–303 13–3


SNA: 210 - TG=index#: Length error 



a TG index number. It is informational only. 

SNA: 211 - TG=index#: DM frame received 




SNA: 212 - TG=index#: FRMR frame received 




SNA: 213 - TG=index#: Non-XID frame received 




SNA: 214 - TG=index#: Unexpected frame received: x%%%% 



a TG index number. The % is a hexadecimal number. The probable cause is a 


SNA: 231 - TG=index#: Line disconnected 




SNA: 241 - TG=index#: WRAP ACK error 




13–4 7436 0728–303


SNA: 242 - TG=index#: FID type is not 4 or F 



a TG index number. The probable cause is a configuration problem. 

SNA: 246 - Format 2 XID error; offset: &&& 


Group Control (TGC) that controls lines between SNA/net and IBM subareas. &&& is 

the offset within the XID where the error was detected. The probable cause is a 


SNA: 252 - TG=index#: BTU length error 




UDLCRS 

Description: R8: 0009. AE$UD570. (UDLC): OVERSIZED OUTPUT, OR 

UNDETECTED DATA CORRUPTION. The output data unit presented to the UDLC 

complex is larger than the maximum size specified by the MIFS keyword parameter to 

the station configuration statement. The output data unit is still sent. Telcon 


UDLCRS 

Description: R8: 0020. AE$UD554. (UDLC): INVALID OR UNIMPLEMENTED U 

FRAME FROM REMOTE STATION. A bad unnumbered command frame has been 

received in logical disconnect state (LDS) or initialization state (IS). Telcon generates 

this CENLOG. 

UDLCRS 

Description: R8: 0021. AE$UD557. (UDLC): N(S) SEQUENCE ERROR. The N(S) 

value in a received I-frame did not match the receive variable. The frame is ignored 

except for the P/F bit and the N(R) field. Telcon generates this CENLOG. 

UDLCRS 

Description: R8: 0022. AE$UD591. (UDLC): OUTPUT MESSAGE RETRANSMISSION. 

An output frame was retransmitted. Telcon generates this CENLOG. 

7436 0728–303 13–5


UDLCRS 

Description: R8: 0024. AE$UD590. (UDLC): REMOTE STATION NOT RESPONDING - 

TIMED OUT. A response timeout has been reported by a timer in the UDLC IOP 

output chain. Telcon generates this CENLOG. 

UDLCRS 

Description: R8: 0025. AE$UD551. (UDLC): S OR I FRAME RECEIVED IN LDS. An S 

or an I frame was received in LDS or IS. The frame was ignored. Telcon generates 

this CENLOG. 

UDLCRS 

Description: R8: 0027. AE$UD234. (UDLC): ITS--

UDLCRS 


Description: R8: 002D. AE$UD233. (UDLC): ITS--


UDLCRS 

Description: R8: 003C. AE$UD332. (UDLC): IS-->LDS. DM RECEIVED; LOGICAL 

DISCONNECT. The local station entered LDS from IS because it received a DM. 


UDLCRS 

Description: R8: 003D. AE$UD200. (UDLC): LDS-->ITS. UA RESP. TO A MODE SET; 

LOGICAL CONNECTION. The local station entered ITS from LDS or IS because it 

received a MODE SET command (combined or secondary station) or a UA response to 

a MODE SET command (primary station). The following categories of event codes 

specify device events: The device is a UDLC station as defined by a Telcon station 

configuration statement. 112–120: station state change between the logical 

disconnect state and the information transfer state. 167–170: station state change 

between the initialization state and either the logical disconnect state or the 

information transfer state. 100, 122–130, 192: a station-level event that does not affect 

the state of the station. 

R8: Contents of the SC$SW1 field in the SCB. The SC$ equates are defined in 

AAHARDEF. The contents of SC$SW1 are extracted prior to making any 

changes required by the event. 

R9: Contents of the SC$SW2 field in the SCB. The SC$ equates are defined in 

AAHARDEF. The contents of SC$SW2 are extracted prior to making any 

changes required by the event. 

R10: Contents of the SC$STM field in the SCB. The SC$ equates are defined in 

AAHARDEF. 

For FRMR related events 99, 117, 118, R10 contains the reason for the FRMR. 

These reasons are specified by one or more of the following bits being set in 

R10. 

Bit 0: Bit 0 is the least significant bit. The control field contained in R15 is 

invalid or not implemented. 

Bit 1: The control field contained in R15 was considered invalid because the 

frame contained an information field that is not permitted with this 

frame. 

Bit 2: The received information field exceeded the maximum established 

capacity of the secondary/combined station. 

Bit 3: The control field contained in R15 contained an invalid N(R) number. 

R11: LCB address. 

R12: Pseudo TCB address so that the STE index to the station information table 

can be supplied as though it were the STE index to the terminal information 

table. 

R13: Control field of the frame received by the local station at the time the event 

occurred. 

For FRMR related events 99,117,118, R13 contains the third and fourth bytes 

of the FRMR information field. 

13–8 7436 0728–303


R14: LINE-ID. 

R15: Address field of the frame received by the local station at the time the event 

occurred. 

For the FCS error (126) and input frame abort (127), R15 contains the start 

data transfer (SDT) chain completion status. 

For FRMR related events (99,117,118), R15 contains the first two bytes of the 

FRMR’s information field if the local station control field type is extended. 

Otherwise, R15 contains zero. Telcon generates this CENLOG. 

UDLCRS 

Description: R8: 0040. AE$UD550. (UDLC): INVALID STATION ADDRESS ON 

INPUT. A UDLC frame was received with an address that is not the global address, or 

is not the address configured for the station. The frame is discarded. Telcon 


X.25: Link Established 

Description: The link layer (layer 2) is initialized. This event includes the line name. 

R8: STE index of PDNGRP statement associated with line 

Attributes affected: Line event, Supplementary text message. The X.25 PSCS 


X.25: Link Reset/Downed 

Description: The link layer (layer 2) is disabled. This event includes the line name. 

R9: Reason code 



7436 0728–303 13–9


X.25 MLP: Link Established 

Description: The link layer (layer 2) is initialized. The initialization of the multi-link 

protocol begins on this line. 

R14: Port processor identifier (PPID) of line 


program product generates this CENLOG. Procedure: PDNMLP. 

X.25 MLP: Link Reset/Downed 

Description: One of the lines running the multi-link protocol is disabled. Other lines 

are still operational. 

R14: Port processor identifier (PPID) of line 


program product generates this CENLOG. Procedure: PDNMLP. 

13–10 7436 0728–303

Event 3 EVENT/ERROR DETECTED AT L3 (NETWORK) 


(NETWORK) 

Description: An event or error has been detected at the network layer. These 

CENLOG messages have been generated by Telcon DNS, X.25 PSCS program product, 

the IP Router component of the ENS program product, OSI TS, or the SNA/net 

program product. 

Action: See Supplementary Messages in this section. 


CANNOT RECOVER! 

Description: The PDNDXA module cannot find a DTE VC table entry because of a 

corrupted chain in the hash table. A software error has corrupted one of the chains in 

the hash table. 

Attributes affected: Fatal error event. The X.25 PSCS program product generates 

this CENLOG. Procedure: TPCDATA. 

CFACCS IO ERROR (R8,R9) 

Description: The PDNDXA module received an IO error from a CALL reference to 

CFACCS. 

R9: IO error code returned by CFACCS 

Attributes affected: Error event, Configuration event. The X.25 PSCS program 

product generates this CENLOG. Procedure: TPCDATA. 

CFACCS SOFT ERROR (R8,R9) 

Description: The PDNDXA module received a software error from a CALL reference 

to CFACCS. 

R9: Error code returned by CFACCS 



7436 0728–303 13–11


CFACCS WEIRD ERROR (R8) 

Description: The PDNDXA module received an unknown error from a CALL 

reference to CFACCS. 

R8: Error code returned by CFACCS 



DCA TERMINAL NOT CONFIGURED 

Description: The PDNDXA module cannot obtain one of its DTE TS table entries 

based upon the TSID passed in an output data message buffer. The software has 

either corrupted the routine in TSTN that puts the TSID into the message buffer or the 

routine in PDNDXA used to obtain the DTE TS table. 

Attributes affected: Error event. The X.25 PSCS program product generates this 

CENLOG. Procedure: TPCDATA. 

DCATS AND DTE DONT PAIR 

Description: The PDNDXA module obtained a DTE statement that contains an STE 

index of a DCATS statement, but the DCATS statement does not contain the 

corresponding STE index of the DTE statement. (Statements don’t point to each 

other.) This DCATS/DTE statements pair is ignored. 



DCATS NOT PAIRED WITH DTE 

Description: The PDNDXA module was unable to obtain a DTE STE using 

information from a DCATS statement. The DCATS statement does not point to a DTE 

type statement. The DCATS statement is ignored. 



DNS: NEIGHBOR NETWRK VERSN NAME MISMATCH, NA = node 

address 

Description: Neighbor node with the node address displayed in the supplementary 

message is using a configuration that contains a network version name that is 

different from the network version name contained in this node’s configuration. 


Action: None. This CENLOG is displayed to inform you that both nodes are using 

configurations created for different network levels. 

13–12 7436 0728–303

DTE VC WASNT LOADED 


Description: The PDNDXA module received an NMS DOWN PDTE indication 

primitive, but was unable to associate a DTE virtual circuit table based upon the DTE 

address passed by the primitive. A software error has corrupted the DTE address 

passed in the primitive. 



DTETS TBL NOT BUILT 

Description: The PDNDXA module was unable to successfully build a DTE TS table 

entry using information obtained from the DCATS statement. A software error has 

either corrupted the DCATS STE or the routine that builds DTE TS tables. 



DTEVC HAS NO LSCH LIST 

Description: The PDNDXA module cannot successfully associate one of its DTE 

virtual circuit tables with a logical subchannel table entry. A software error has 

corrupted the logical subchannel table entry addresses within the DTE virtual circuit 

tables. 



INVALID DTETS LOG ADR 

Description: The PDNDXA module was unable to associate one of its TSID table 

entries from an address obtained from its DTE virtual circuit table. A software error 

has corrupted the TSID address in the DTE virtual circuit table. 



INVALID DTEVC LOG ADR 

Description: The PDNDXA module cannot obtain the DTE VC table entry using an 

address from the logical subchannel table entry. A software error has corrupted one 

of the DTE VC table entry addresses in one of the logical subchannel table entries. 



7436 0728–303 13–13


INVALID LSCH ENTRY COUNT 

Description: The PDNDXA module cannot find a free, logical subchannel table entry 

even though the table segment header indicated there were free entries. A software 

error has corrupted one of the logical subchannel table segment headers. 



INVALID LSCH LIST LOG ADR 

Description: The PDNDXA module cannot successfully access its logical subchannel 

table entry. The table’s address is corrupted. A software error has corrupted the 

address. 



13–14 7436 0728–303

IP Router Messages 


The IP Router component of the ENS program product generates the following CENLOG 

messages. All IP Router supplementary messages begin with the prefix IP, a five digit 

event identifier, and an internal software component identifier, for example MIP (IP 

manager) or FLIP (IP interface). 

If you change the default logging or trace level (OFF) to LOW, MED, or HIGH on the 

LOG or TRACE statements in the ENS configuration then CENLOG events other than the 

ones documented below are reported by the IP Router. These additional events are 

typically used for diagnostic purposes. 

The following information is often displayed in IP Router supplementary messages: 

• if_id is the first ten characters of the name specified on the name statement under the 

interface’s IP section header. If no name statement is configured, if_id is 

port=%%/if=&, where %% is the hexadecimal port number specified on a [PORTxy] 

section header and & is the interface parameter value configured on an IP interface 

(see rtr=&) section header. 

• ilm=%%, where %% is the hexadecimal number of the physical port in which the IP 

manager is running. 

• rtr=&, where & is the router number specified on the router parameter on an 

[ip_router], [ip_telcon], or IP interface ([ip_ethernet], [ip_fddi], [ip_tr], [ip_fr], 

[ip_ppp], or [ip_interface]) section header. 

Most IP Router messages are either “informational only” or indicate internal software 

error conditions that are not amenable to local corrective action. The following standard 

action applies unless more specific action is described. 

Standard Action for IP Messages 

If IP Router messages persist and seem to be related to an operational problem you are 

having, restarting or reloading the line module that generates these messages may 

eliminate messages. If the messages continue to display, report the problem to your 

Unisys support representative. A long format CENLOG message listing and an ILM dump 

of the ILM in which the IP manager is executing are usually required to diagnose and 

resolve the problem. 

IP 04020: FLIP UNREC DLCMAN primitive % 

Description: The IP interface component has received an unrecognized message 

type from DLCMAN. % is a hexadecimal internal message type code. 

Action: Standard action. 

7436 0728–303 13–15


IP 04022: FLIP getIFEncap ERR01 - & 

Description: The IP interface component has received an unrecognized link 

encapsulation value during configuration processing. & is a decimal internal 

encapsulation code. 


IP 04030: FLIP FAILURE I/F init, rtr=& 

Description: The IP interface component has failed to complete configuration 

processing because of lack of memory resources. 


IP 04035: FLIP ics_flow_ctl ERR01 status=% 

Description: An IP interface component internal interface with another entity is 

restricted becaus of flow control. % is a hexadecimal internal status code. 


IP 04045: FLIP send_ICSConn_data ERR01 status=%,rtr=& 

Description: An IP interface component attempt to send message to another router 

& entity has failed. % is a hexadecimal internal status code. 


IP 04052: FLIP Unrecognized IPkt Type &1,rtr=& 

Description: The IP interface component has received an unrecognized request type 

from the router & IP manager component. Internal software error. &1 is a decimal 

internal request type code. 


IP 04060: FLIP set MCA fail - port=%%, if=& 

Description: The IP interface component received a fail indication in attempting to 

register a link layer multicast address. %% is the hexadecimal port number configured 

on a [PORTxy] section header and & is the interface parameter value configured on 

the [ip_ethernet], [ip_fr], or [ip_ppp] section headers. 


13–16 7436 0728–303


IP 04061: FLIP missing expedited ACK rtr=&, port=%% 

Description: The IP interface component has not received an acknowledgment for 

an expedited data message sent to another router & entity. The wait period for 

acknowledgment is one second. %% is the hexadecimal port number specified on a 

[PORTxy] section header. Information only. 

Action: None. 

IP 05000: MIP (ilm=%%)Router & is up 

Description: IP router & is active on the ILM %%. Informational only. 

Action: None. 

IP 05001: MIP (ilm=%%)Router & is down 

Description: IP router & is inactive on ILM %%. Informational only. 

Action: None. 

IP 05002: MIP (ilm=%%)interface is up. rtr=& if_id 

Description: Interface if_id on IP router & is now up. Informational only. 

Action: None. 

IP 05003: MIP (ilm=%%)interface is down. rtr=& if_id 

Description: Interface if_id on IP router & is now down. Informational only. 

Action: None. 

IP 05004: MIP (ilm=%%)no local address. rtr=& if_id 

Description: No local IP address (ip_address statement) is configured for interface 

if_id on IP router &. 

Action: Correct the ENS configuration and restart the IP interface or router. 

IP 05005: MIP (ilm=%%)invalid IF # configured, IF not initialized. 

rtr=& if_id 

Description: The interface parameter value specified for interface if_id on the IP 

router & is invalid. 

Action: Correct the ENS configuration and restart the IP interface or router. 

7436 0728–303 13–17


IP 05022: MIP (ilm=%%)UNEXPECTED CD DATA type=&1 

src=%%%%%%%% 

Description: The IP manager executing in ILM %% has received an unexpected 

internal message of type &1. %%%%%%%% is a hexadecimal internal ICS user 

identifier. 

Action: The supplementary data contained in the CENLOG provides additional 

information and should be submitted with a problem report. 

IP 05026: MIP (ilm=%%)*** ERROR @@@ *** 

Description: The IP manager executing in ILM %% has detected an internal error. 

@@@ is a descriptive text string. 

Action: The supplementary data contained in the CENLOG provides additional 

information and should be submitted with a trouble report. 

IP 05028: MIP (ilm=%%)LOW MEMORY! Router not initialized, rtr=& 

Description: IP router & has not initialized because of insufficient memory. 

Action: Submit a trouble report with a dump of the ILM %%. 

IP 05029: MIP (ilm=%%)LOW MEMORY! INTF not initialized 

(rtr=&/port=%1/if=&1) 

Description: Interface &1 on port %1 on IP router & has not initialized because of 

insufficient memory. %1 is the hexadecimal port number specified on a [PORTxy] 

section header and &1 is the interface parameter value configured on an IP interface 

section header. 

Action: Submit a trouble report with a dump of ILM %%. 

IP 05032: MIP (ilm=%%)cfg MTU exceeds allowed (&1>&2) line if_id 

Description: The MTU (mtu_size parameter) value specified for interface if_id 

exceeds the allowed value for the type of interface the port provides. &1 and &2 are 

the configured and allowed values, respectively. The allowed value is used. &1 and 

&2 are decimal numbers. 

Action: To eliminate the CENLOG, correct the configuration and restart the IP 

interface or router. 

13–18 7436 0728–303


IP 05033: MIP (ilm=%%)Router & preempted by port=%%1 

Description: The IP manager for IP router & running on PORT %% has been 

preempted by another IP manager running in PORT %%1. %% and %%1 are 

hexadecimal port numbers specified on [PORTxy] section headers. Informational 

only. 

Action: None. 

IP 05034: MIP (ilm=%%)Router & coming online 

Description: IP router & is now being managed by the IP manager residing in PORT 

%%. Informational only. 

Action: None. 

IP 05035: MIP (ilm=%%)LOW MEMORY! Line if_id not RESIL 

Description: Interface if_id has failed in a resilient configuration, but because of 

memory limitations the backup interface is not able to assume responsibility for the 

failed interface. 


IP 05036: MIP (ilm=%%)RESIL IP addresses from if_id are @@@ 

Description: All IP addresses assigned to interface if_id have been either placed in a 

resilient state (@@@ = RESIL) because of the failure of the interface, or are being 

reclaimed (@@@ = RECLAIMED) by the primary interface because the primary 

interface is now back on line. Informational only. 

Action: None. 

IP 05037: MIP (ilm=%%)RESIL IP addr @@@ => to if_id 

Description: The IP address @@@ is being reassigned to interface if_id because the 

interface which was originally responsible failed. @@@ is a dotted decimal IP 

address. Informational only. 

Action: None. 

7436 0728–303 13–19


IP 05038: MIP (ilm=%%)LOW ILM MEMORY!!, occurred after 

hh:mm:ss mm/dd/yy 

Description: A low memory situation has occurred on ILM %%. The time stamp 

hh:mm:ss mm/dd/yy indicates when this message was last generated and is all zeros 

for the first occurrence of this message. Additional information is available in the 

supplementary data contained in the CENLOG. 

Action: Submit a trouble report with the CENLOG supplementary data and possibly a 

dump of the ILM %%. 

IP 08001: RIP error: @@@ rtr=& 

Description: The IP RIP component has detected an internal error on IP router &. 

@@@ is a supplemental text string that reads: 

Unable to register UDP socket or Unable to deregister UDP socket. 


IP 08002: RIP error: Unknown router. rtr=& loc: &1 

Description: The IP RIP component was passed a router identifier for a router it 

does not recognize. & is the unknown IP router. &1 is a decimal internal instance 

code. This is could be a coding error. The impact of this error on system functionality 

depends on where the error is occuring. 


IP 08004: Unknown interface. id=%% loc: & 

Description: The IP RIP component has being passed an internal interface identifier 

for an interface it does not recognize. %% is the unknown interface identifier. & is a 

decimal internal instance code. This could be a coding error. The impact of this error 

on system functionality depends on where the error is occuring. 


IP 14002: SMP ICS Connectionless Data Received. 

src=%%%%%%%% 

Description: The IP SMP component has received an unexpected ICS message. 

%%%%%%%% is a hexadecimal internal ICS user identifier. 


13–20 7436 0728–303


IP 14003: SMP ICS Connectionless Flow Control Received. 

dest=%%%%%%%% 


%%%%%%%% is a hexadecimal internal ICS user identifier. 


IP 14005: SMP ICS Connect Indication rejected. Domain=& 

Description: The IP SMP component has received a connect indication from an 

unknown user identified by &, presumably an SNMP agent. & is the domain 

parameter value specified on an [SNMP] section header. 


IP 14007 SMP ICS Expedited Ack received. cid=%%%%%%%% 


%%%%%%%% is a hexadecimal internal connection identifier. 


IP 14008: SMP ICS Expedited Data received. cid=%%%%%%%% 




IP 14009: SMP ICS Flow Control received. cid=%%%%%%%% 




IP 14010: SMP ICS registration complete. 

Description: Informational only. 

Action: None. 

7436 0728–303 13–21


IP 14013: SMP initialization process started. 


Action: None. 

IP 14015: SMP started 


Action: None. 

IP 14016: SMP Unable to create IPSMP process 

Description: The IP SMP component will not function. 


IP 14021: SMP Invalid domain on deregistration. Domain=& 

Description: The IP manager has called the IP SMP component during down or 

delete router processing but provided an unknown domain (&) identifier. The impact 

of this error on system functionality may vary since the router is going down anyway. 

& is the domain parameter value specified on the [SNMP] section header. 


IP 17621: UDP appl dg dscd. rtr=& err=&1 

Description: The UDP component has discarded a UDP datagram it received from a 

UDP service user, but was unable to pass to the IP component. &1 is a decimal 

internal error code. You can use the NMS LOGI OPTN=LONG command to display 

the discarded datagram. Probable service user software error. 


IP 17622: UDP IP dg dscd. rtr=& err=&1 

Description: The UDP component has discarded an undeliverable UDP datagram it 

received from the IP component (UDP datagrams that result in an ICMP Destination 

Unreachable, Port Unreachable error message are not discarded and do not trigger 

this event). &1 is a decimal internal error code. You can use the NMS LOGI 

OPTN=LONG command to display the discarded datagram. Probable service user 

software error if this event occurs when UDP logging and tracing is disable (OFF); 

probable datagram checksum error if UDP tracing or logging level MED or HIGH is 

enabled. 


13–22 7436 0728–303


IP 17623: UDP ICMP dg dscd. rtr=& err=&1 (t&2/c&3) 

Description: The UDP component has discarded an undeliverable ICMP message it 

received from the IP component. &1 is a decimal internal error code, &2 and &3 are 

the ICMP message’s Type and Code value, respectively. You can use the NMS LOGI 

OPTN=LONG command to display the discarded message. Probable software error if 

this event occurs when UDP logging and tracing is disabled (OFF); probable 

application or network connectivity error if UDP tracing or logging level MED or 

HIGH is enabled. 


IP 17711: UDP ICS conn rej. rtr=& err=&1 

Description: The UDP component was unable to accept an internal connection with 

a UDP datagram service user. &1 is a decimal internal error code. Probable software 

error. 


IP 17712: UDP ICS disc rej. rtr=& cid=%%%%%%%% err=&1/&2 

Description: The UDP component has discarded an invalid internal disconnection 

indication for a UDP datagram service user. %%%%%%%% is a hexadecimal internal 

connection identifier, &1 and &2 are decimal internal error codes. Probable ICS 

software error. 


IP 17725: UDP ICS data dscd. rtr=& cid=%%%%%%%% 

Description: The UDP component has discarded a service request from an unknown 

UDP datagram service user. %%%%%%%% is a hexadecimal internal connection 

identifier. Probable service user software error. 


IP 17726: UDP unkn CDS func. rtr=& cid=%%%%%%%% fn=&1 

Description: The UDP component has received an unexpected service interface 

request from a UDP datagram service user. %%%%%%%% is a hexadecimal internal 

function identifier. Probable service user software error. 


7436 0728–303 13–23


IP 17727: UDP CDS UDP dg dscd. rtr=& cid=%%%%%%%% 

Description: The UDP component has discarded a UDP datagram for an unknown 

UDP datagram service user. %%%%%%%% is a hexadecimal internal connection 

identifier. Probable UDP software error. 


IP 17728: UDP CDS ICMP dg dscd. rtr=& cid=%%%%%%%% 

(t&1/c&2) 

Description: The UDP component has discarded an ICMP message addressed to a 

UDP datagram service user. The UDP datagram service interface does not support 

passing ICMP messages to applications outside the IP manager. %%%%%%%% is a 

hexadecimal internal connection identifier, &1 and &2 are the ICMP message’s Type 

and Code value, respectively. Probable UDP component software error if this event 

occurs when UDP logging and tracing is disabled (OFF); probable application or 

network connectivity error if UDP tracing or logging level is enabled. 


IP 17731: UDP ICS send fail. status=& 

Description: The UDP component was unable to communicate with a UDP datagram 

service user. A service interface request response or arriving UDP datagram has been 

discarded. & is a decimal internal error code. Probable software error. 


IP 17801: UDP add rtr fail. rtr=& err=&1 

Description: The UDP component has failed to initialize. &1 is a decimal internal 

error code. Probable memory shortage error. 

Action: Standard action. Router & must be restarted. 

IP 17802: UDP upd rtr fail. rtr=& 

Description: The UDP component has failed to restart. Probable software error. 

Action: Standard action. Router & must be restarted. 

IP 17803: UDP del rtr fail. rtr=& 

Description: The UDP component has failed to deactivate. Probable software error. 


13–24 7436 0728–303


IP 17821: UDP add socket fail. rtr=& port=&1 cid=%%%%%%%% 

err=&2 

Description: The UDP component has rejected a UDP service interface listening port 

registration request. &1 is a decimal UDP port number, %%%%%%%% is a hexadecimal 

internal connection identifier, and &2 is a decimal internal error code. You can use 

the NMS LOGI OPTN=LONG command to display the rejected listening port 

descriptor. Probable service user software error. 


IP 17822: UDP del socket fail. rtr=& port=&1 cid=%%%%%%%% 

err=&2 

Description: The UDP component has rejected a UDP service interface listening port 

deletion request. &1 is a decimal UDP port number, %%%%%%%% is a hexadecimal 

internal connection identifier, and & is a decimal internal error code. You can use the 

NMS LOGI OPTN=LONG command to display the rejected listening port descriptor. 

Probable service user software error. 


IP 17823: UDP get SRC fail. rtr=& 

Description: The UDP component has rejected a UDP service interface source 

address lookup request. Probable service user software error. 


IP 17824: UDP get MTU fail. rtr=& 

Description: The UDP component has rejected a UDP service interface maximum 

datagram send size and receive size lookup request. Probable service user software 

error. 


IP 17831: UDP read stats fail. rtr=& 

Description: The UDP component has rejected a UDP statistics access request from 

the Menu or SMP component. Probable software error. 


7436 0728–303 13–25


IP 17832: UDP clr stats fail. rtr=& 

Description: The UDP component has rejected a UDP statistics reset request from 

the Menu or SMP component. Probable software error. 


IP 17833: UDP open table fail. rtr=& 

Description: The UDP component has rejected a UDP listening port table access 

request from the Menu or SMP component. Probable software error. 


IP 17834: UDP read table fail. id=%%%%%%%% 


request from the Menu or SMP component. % is a hexadecimal internal table entry 

identifier. Probable software error. 


IP 17835: UDP cls table fail. id=%%%%%%%% 


request from the Menu or SMP component. % is a hexadecimal internal table entry 



IP 17836: UDP read single fail. rtr=& 


request from the Menu or SMP component. Probable software error. 


IP 17837: UDP unkn table func. rtr=& fn=&1 


request from the Menu or SMP component. &1 is a decimal internal function 



13–26 7436 0728–303


IP 17992: UDP ICS CLs Data rcvd. src=%%%%%%%% 

Description: The UDP component has discarded an unexpected ICS connectionless 

data message. %%%%%%%% is a hexadecimal internal ICS user identifier. Probable 



IP 17993: UDP ICS CLs Fl Ctl rcvd. dest=%%%%%%%% 

Description: The UDP component has received an unexpected ICS connectionless 

data flow control notification. %%%%%%%% is a hexadecimal internal ICS user 



IP 17994: UDP ICS Exp Data rcvd. cid=%%%%%%%% 

Description: The UDP component has discarded an unexpected ICS expedited data 

message. %%%%%%%% is a hexadecimal internal connection identifier. Probable 



IP 17995: UDP ICS Exp Ack rcvd. cid=%%%%%%%% 

Description: The UDP component has discarded an unexpected ICS expedited data 

acknowledgment message. %%%%%%%% is a hexadecimal internal connection 



IP 17996: UDP ICS Fl Ctl rcvd. cid=%%%%%%%% 

Description: The UDP component has received an unexpected ICS flow control 

notification. %%%%%%%% is a hexadecimal internal connection identifier. Probable 



7436 0728–303 13–27


IP 18002: ICMP dg


IP 31003: OSPF Event OSPF ERR_DD_NNOTSET src = xx.xxx.xxx.xxx 

Description: The data base description packet received has a mismatch in option bit 

N. The received packet has N bit clear indicating the area is not a NSSA (“not-sostubby”) 

area. This area is locally defined as NSSA area. src=xxx.xxx.xxx.xxx is 

the source address of input in the dotted decimal format. 

IP 31003: OSPF Event OSPF ERR_HELLO_MASK src = xx.xxx.xxx.xxx 

Description: The OSPF hello packet received contains a network mask that does 

not agree with the locally defined network mask. src=xxx.xxx.xxx.xxx is the 

source address of input in the dotted decimal format. 

IP 31003: OSPF Event OSPF ERR_HELLO_TIMER 

src =xxx.xxx.xxx.xxx 

Description: The OSPF packet received contains a hello interval that does not agree 

with the locally defined hello interval value. src=xxx.xxx.xxx.xxx is the source 

address of input in the dotted decimal format. 

IP 31003: OSPF Event OSPF ERR_HELLO_DEAD src = xxx.xxx.xxx.xxx 

Description: The OSPF hello packet received contains a router dead interval that 

does not agree with the locally defined router dead interval value. 

src=xxx.xxx.xxx.xxx is the source address of input in the dotted decimal format. 

IP 31003: OSPF Event OSPF ERR_HELLO_ESET src = xxx.xxx.xxx.xxx 

Description: The OSPF hello packet received has a mismatch in option bit E. The 

received packet has E bit set indicating the area is AS-external-LSA capable. The area 

is locally defined as not AS-external-LSA capable. src=xxx.xxx.xxx.xxx is the 


IP 31003: OSPF Event OSPF ERR_HELLO_ENOTSET 

src = xx.xxx.xxx.xxx 

Description: The OSPF hello packet received has a mismatch in option bit E. The 

received packet has E bit clear indicating the area is not AS-external-LSA capable. 

The area is locally defined as AS-external-LSA capable. src=xxx.xxx.xxx.xxx is the 


IP 31003: OSPF Event OSPF ERR_HELLO_NSET src = xxx.xxx.xxx.xxx 

Description: The OSPF hello packet received has a mismatch in option bit N. The 

received packet has N bit set indicating the area is NSSA capable. The area is locally 

defined as not a NSSA area. src=xxx.xxx.xxx.xxx is the source address of input in 

the dotted decimal format. 

7436 0728–303 13–29


IP 31003: OSPF Event OSPF ERR_HELLO_NNOTSET 

src = xxx.xxx.xxx.xxx 

Description: The OSPF hello packet received has a mismatch in option bit N. The 

received packet has N bit clear indicating the area is not a NSSA area. The area is 

locally defined as a NSSA area. src=xxx.xxx.xxx.xxx is the source address of input 

in the dotted decimal format. 

IP 31003: OSPF Event OSPF ERR_HELLO_ID src = xxx.xxx.xxx.xxx 

Description: The OSPF hello packet received has a router ID matching the local 

router ID. This is not an error condition if a router has multiple connections to the 

same broadcast network. src=xxx.xxx.xxx.xxx is the source address of input in the 

dotted decimal format. 

IP 31003: OSPF Event OSPF ERR_CHECKSUM src = xxx.xxx.xxx.xxx 

Description: The OSPF was received with a bad checksum. src=xxx.xxx.xxx.xxx 

is the source address of input in the dotted decimal format. 

IP 31003: OSPF Event OSPF NETWORK_MISMATCH 

src = xxx.xxx.xxx.xxx 

Description: The source network of the OSPF packet received is not the same as the 

network of the receiving interface. src=xxx.xxx.xxx.xxx is the source address of 

input in the dotted decimal format. 

IP 31003: OSPF Event OSPF AREA_ID_MISMATCH src = 

xxx.xxx.xxx.xxx 

Description: The area ID of the OSPF packet received does not match the area ID of 

the receiving interface. src=xxx.xxx.xxx.xxx is the source address of input in the 

dotted decimal format. 

IP 31003: OSPF Event OSPF ERR_AUTH_TYPE src = xxx.xxx.xxx.xxx 

Description: The authentication type of the OSPF packet received is different than 

the authentication type specified for the receiving interface. src=xxx.xxx.xxx.xxx 

is the source address of input in the dotted decimal format. 

IP 31003: OSPF Event OSPF ERR_AUTH_KEY src = xxx.xxx.xxx.xxx 

Description: The authentication key of the OSPF packet received is different than 

the authentication key specified for the receiving interface. src=xxx.xxx.xxx.xxx is 

the source address of input in the dotted decimal format. 

13–30 7436 0728–303


IP 31003: OSPF Event OSPF ERR_HDR_SHORT (rtr = xxxxx) 

Description: The OSPF header length field value of the OSPF packet received is less 

than the minimum OSPF header size. rtr=xxxxx identifies the local IP router. 

IP 31003: OSPF Event OSPF LEN_LONG (rtr = xxxxx) 

Description: The OSPF header length field value of the OSPF packet received is 

greater than the datagram length field value contained in the IP header. rtr=xxxxx 

identifies the local IP router. 

IP 31003: OSPF Event OSPF ERR_VERSION (rtr = xxxxx) 

Description: The OSPF packet with a version number not equal to 2. rtr=xxxxx 

identifies the local IP router. 

IP 31003: OSPF Event SPF scheduled (rtr = xxxxx) 

Description: The OSPF SPF algorithm scheduled for the specified local router. 

rtr=xxxxx identifies the local IP router. 

LAX IN USE, SHOULDN’T BE 

Description: The PDNDXA module was unable to save a data message in the link 

area. The data message has been discarded. A software error has either corrupted 

the link area or the link area indices in the DTE VC table. 



LAX NOT IN USE, SHOULD BE 

Description: The PDNDXA module cannot successfully obtain a data message from 

link area. A software error has either corrupted the index used to access the linked 

data message in the DTE virtual circuit table, or the link area itself has become 

corrupted. 



7436 0728–303 13–31


LEVEL 4 ROUTING ID IS UNKNOWN TO LEVEL 3 

Description: A layer 4 sent a call request primitive to layer 3 without including its 

routing id. 

R11: Diagnostic code. See Appendix A of this manual for more information. 


generates this CENLOG. Procedure: PCALL. 

LOADED WRONG DTETS TBL 

Description: The PDNDXA module cannot use one of its DTE TS table entries 

because the entry addresses do not match. A software error has either corrupted the 

entry address within the DTE TS table or the routine used to obtain a DTE TS table 

entry has become corrupted. 



LOADED WRONG DTEVC TBL 

Description: The PDNDXA module cannot use one of its DTE VC table entries 

because the entry addresses do not match. A software error has either corrupted the 

entry address within the DTE VC table or the routine used to obtain a DTE VC table 

entry has become corrupted. 



LOADED WRONG LSCH LIST 

Description: The PDNDXA module cannot successfully load one of its logical 

subchannel table segments. A software error has corrupted the procedure segment 

table. 



LSCH LIST CHAIN CORRUPTED 

Description: The PDNDXA module was unable to remove all chained logical 

subchannel table lists from one of its DTE VC table entries. A software error has 

corrupted one of the logical subchannel table list chains. 



13–32 7436 0728–303

LSCH LIST WASNT LOADED 


Description: The PDNDXA module cannot successfully load one of its logical 

subchannel table segments. A software error has corrupted the procedure segment 

table. 



MESSAGE SIZE ILLEGAL, TRUNCATED 

Description: The PDNDXA module was unable to successfully build an NMS 

response message. The response message is truncated. 



NOT ENOUGH RESOURCES FOR NEW TBL 

Description: The PDNDXA module cannot successfully allocate a new internal table. 

The reason could be not enough memory. 

R8: Internal error code 



7436 0728–303 13–33


OSIIP–DNS ATTACH FAIL 

Description: An attempt by OSIIP to attach to DNS as a user has failed. The OSIIP 



OSIIP–DNS MESSAGE RECEIVE FAIL 

Description: Unknown message type received through DNS. The OSIIP component 

of the OSITS program product generates this CENLOG. 

Reason: Data transfer state not yet established. 

OSIIP–DNS SUBNET NOT UP; SEND REQUEST DISCARDED 

Description: No indication of successful DNS attachment has been received. The 



OSIIP–ERROR PDU DISCARD 

Description: An error PDU has been discarded. The OSIIP component of the OSITS 


Reason: A PDU was corrupted in transit. 

OSIIP–HCC MESSAGE RECEIVE FAIL 

Description: An input message from the host channel was discarded. The OSIIP 


Reason: The message failed to meet HCC to OSIIP validation criteria. 

OSIIP–HCC SUBNET NOT UP; SEND REQUEST DISCARDED 

Description: No indication of host channel initialization has been received. The 


Reason: Configuration or hardware error. 

13–34 7436 0728–303

OSIIP–HCC UDM 


Description: An undeliverable message (UDM) indication was received from a host 

channel. The OSIIP component of the OSITS program product generates this 

CENLOG. 

Reason: Host channel failure. 

OSIIP–INVALID DNS INPUT 

Description: The DNS header on a PDU received on the DNS subnet is in error. The 


Reason: DNS header failed validation criteria. 

OSIIP–LAN ATTACH FAIL 

Description: Attempt to dynamically attach to LAN subnet failed. The OSIIP 



OSIIP–LAN MESSAGE RECEIVE FAIL 

Description: An input message from a LAN link has been discarded. The OSIIP 


Reason: The LAN link service reported an input error. 

OSIIP–LAN RECEIVE PROTOCOL FAILURE 

Description: An input message from a LAN link was discarded. The OSIIP 


Reason: The message failed to meet OSI protocol validation criteria. 

OSIIP–LAN SUBNET NOT UP; SEND REQUEST DISCARDED 

Description: No indication of LAN initialization has been received. The OSIIP 



7436 0728–303 13–35


OSIIP–LEVEL 4 MESSAGE DISCARDED; NO X.25 RESOURCES 

Description: All virtual circuit facilities allocated to the X.25 subnetwork are already 

in use. The OSIIP component of the OSITS program product generates this CENLOG. 

Reason: Message traffic load. 

OSIIP–LINK AREA FULL 

Description: OSIIP link table full. The OSIIP component of the OSITS program 



OSIIP–MULTICAST FAIL 

Description: Attempt to register multi-cast address failed. The OSIIP component of 

the OSITS program product generates this CENLOG. 


OSIIP–NO ADJACENCY RIB 

Description: Adjacency routing base referenced, but not present. The OSIIP 



OSIIP–NO ID RIB 

Description: In area routing base referenced, but not present. The OSIIP component 



OSIIP–NO OUT OF AREA RIB 

Description: Out of area routing base referenced, but not present. The OSIIP 



13–36 7436 0728–303

OSIIP–NULL PDU DISCARDED 


Description: An inactive subset (no protocol header) PDU has been received on 

subnet on which NULL PDU input is not enabled. The OSIIP component of the OSITS 



OSIIP–OUTPUT PDU LIFETIME EXPIRED 

Description: The lifetime of an output message expired while waiting for a 

subnetwork handler to clear a queue-full condition. The OSIIP program product 


Reason: The subnetwork handler is unable to accept input. 

OSIIP–PERIODIC MESSAGE FAIL 

Description: Attempt to register multi-cast repeating message failed. The OSIIP 



OSIIP–PSCS RECEIVE PROTOCOL FAILURE 

Description: An input message received from an X.25 subnetwork was discarded. 

The OSIIP component of the OSITS program product generates this CENLOG. 

Reason: The message content failed to meet OSI protocol validation criteria. 

OSIIP–RECEIVED PDU LIFETIME EXPIRED 

Description: An incomplete message has been discarded. The OSIIP component of 


Reason: The lifetime of a partial message expired. 

OSIIP–RIB ERROR; SEND REQUEST DISCARDED 

Description: A forward route was not found in the RIB (routing information base) 

when the DCP performs as an intermediate system (IS). The OSIIP component of the 


Reason: RIB incorrect. 

7436 0728–303 13–37


OSIIP–ROUTE NOT FOUND; SEND REQUEST DISCARDED 

Description: No direct, forward, or default route has been defined for the remote 

NSAP address. The OSIIP component of the OSITS program product generates this 

CENLOG. 


OSIIP–STATIC CIRCUIT NOT AVAILABLE; SEND DISCARDED 

Description: Static circuit specified for data output not in data transfer state. The 


Reason: Data transfer state not yet established. 

OSIIP–UNEXPECTED DNS MESSAGE RECEIVED 

Description: 

• A message was received from DNS when a DNS subnet was not defined, or 

• An invalid DNS message type was received on the DNS subnet. The OSIIP 



OSIIP–UNEXPECTED HCC MESSAGE RECEIVED 

Description: An input message was received from a host channel for which a subnet 

has not been created. The OSIIP component of the OSITS program product generates 

this CENLOG. 

Reason: System failure or hardware error. 

OSIIP–UNEXPECTED LAN MESSAGE RECEIVED 

Description: An input message was received from a LAN link for which an OSISN 

statement had not been defined. The OSIIP component of the OSITS program product 



OSIIP–UNEXPECTED POQ MESSAGE RECEIVED 

Description: A LAN initialization message received for which a LAN subnet is not 

defined. The OSIIP component of the OSITS program product generates this 

CENLOG. 

Reason: System or hardware failure. 

13–38 7436 0728–303


OSIIP–UNEXPECTED PSCS MESSAGE RECEIVED 

Description: An input message was received from an X.25 subnetwork for which an 

OSISN statement had not been defined. The OSIIP component of the OSITS program 



OSIIP–UNEXPECTED REDIRECT PDU RECEIVED 

Description: An ISO 9542 redirect PDU was received when the DCP is not an end 

system only (performs also as an intermediate system). The OSIIP component of the 


Reason: Unknown. 

OSIIP–UNEXPECTED STATION DOWN MESSAGE 

Description: A station down (subnet down) message was received on a LAN or host 

channel subnet when the subnet was already down. The OSIIP component of the 



OSIIP–UNEXPECTED STATION UP MESSAGE 

Description: A station up (subnet up) message was received on a LAN or host 

channel subnet when the subnet was already up. The OSIIP component of the OSITS 



OSISIS: UNRECOGNIZED HIC FROM NMS 

Description: A message was received from NMS with an unexpected HIC. The 

OSISIS component of the OSITS program product generates this CENLOG. 

Reason: Programming error. 

OSIIP–VIRTUAL CIRCUIT 

Description: An inactive virtual circuit has been cleared. The OSIIP component of 


Reason: The virtual circuit is no longer active. 

7436 0728–303 13–39


OSIIP–X.25 SUBNET NOT UP; SEND REQUEST DISCARDED 

Description: No indication of X.25 initialization has been received. The OSIIP 



OSISIS: ATTEMPT TO EXCEED MAXIMUM SEQUENCE NUMBER 

Description: Sequence number on an LSP overflowed. Disables the IS for 20 

minutes. The OSISIS component of the OSITS program product generates this 

CENLOG. 

Reason: This happens after a long period of time. 

OSISIS: ATTEMPT TO EXCEED MAXIMUM SEQUENCE NUMBER 

Description: An LSP needed to be sent, but could not increment the sequence 

number without causing overflow. This is normal after a long period of time. The 


Reason: A lot of nodes going up or down on the network. 

OSISIS: AUTHENTICATION FAILURE 

Description: An ISIS PDU was received with an incorrect password. The OSISIS 


Reason: There is an IS on the network that doesn’t belong. 

OSISIS: BAD ISIS PDU TYPE 

Description: Received an ISIS PDU with an invalid PDU type field. The OSISIS 


Reason: A node on the network is generating corrupt PDUs. 

OSISIS: BUMP CHAIN FAILED ON TENT 

Description: Could not follow the chain in the tentative paths memory management 

pool. The OSISIS component of the OSITS program product generates this CENLOG. 


13–40 7436 0728–303

OSISIS: CAN'T LINK A NIL MSG! 


Description: Tried to put an empty message in the link area. The OSISIS component 



OSISIS: CORRUPTED LSP RECEIVED 

Description: Received an LSP with a bad checksum. The OSISIS component of the 


Reason: Bit errors on the network or programming error. 

OSISIS: COULDN'T FIND TENT PATH IN ADJ TABLE 

Description: An entry in the tentative paths pool had no corresponding entry in the 

adjacency table. The OSISIS component of the OSITS program product generates this 

CENLOG. 


OSISIS: DATABASE OVERLOAD (RECOVERED) 

Description: The DCP is now able to route again. The OSISIS component of the 


Reason: Memory has become available. 

OSISIS: GPTS ERROR: BCAST TMR_DEREG FAILED 

Description: Could not stop the broadcast timer. The OSISIS component of the 


Reason: 

R8: Memory management error code 

R9: System error code 

R10: Gpts error code 

OSISIS: GPTS ERROR: BCAST TMR_REG FAILED 

Description: Could not start the broadcast timer. The OSISIS component of the 


Reason: 




7436 0728–303 13–41


OSISIS: GPTS ERROR: ELECT TMR_START FAILED 

Description: An error occurred trying to start the pseudonode election timer. The 


Reason: 




OSISIS: GPTS ERROR: ELECTION TMR_REG FAILED 

Description: Could not register the election timer. The OSISIS component of the 


Reason: 




OSISIS: GPTS ERROR: IIH tmr_reg failed 

Description: An error occurred trying to start the IIH timer. The OSISIS component 


Reason: 




OSISIS: GPTS ERROR: IIH TMR_REG FAILED 

Description: Could not register the IS–IS Hello Timer. The OSISIS component of the 


Reason: 




13–42 7436 0728–303


OSISIS: GPTS ERROR: IIH TMR_START FAILED 

Description: An error occurred trying to start the IIH timer. The OSISIS component 


Reason: 




OSISIS: GPTS ERROR: IIH TMR_START FAILED 

Description: Could not start the IS–IS Hello Timer. 

Reason: 




OSISIS: GPTS ERROR: ISH TMR_CANCEL FAILED 

Description: An error occurred trying to stop the ISH timer. The OSISIS component 


Reason: 




OSISIS: GPTS ERROR: ISH tmr_reg failed 

Description: An error occurred trying to start the ISH timer. The OSISIS component 


Reason: 




7436 0728–303 13–43


OSISIS: GPTS ERROR: ISH TMR_REG FAILED 

Description: Could not register the IS Hello Timer. The OSISIS component of the 


Reason: 




OSISIS: GPTS ERROR: ISH TMR_START FAILED 

Description: An error occurred trying to start the ISH timer. The OSISIS component 


Reason: 





Description: Could not start the polling IS–IS Hello Timer. The OSISIS component of 


Reason: 





Description: Could not start the IS Hello Timer. The OSISIS component of the OSITS 


Reason: 




13–44 7436 0728–303


OSISIS: GPTS ERROR: POLL TMR_START FAILED 

Description: An error occurred trying to start the ISH polling timer. The OSISIS 


Reason: 




OSISIS: GPTS ERROR: POLL TMR_START FAILED 

Description: Could not start the polling IS-IS Hello Timer. 

Reason: 




OSISIS: GPTS ERROR: SOLICIT TMR_REG FAILED 

Description: Could not register the IS Hello Timer used when soliciting the ES 

configuration. The OSISIS component of the OSITS program product generates this 

CENLOG. 

Reason: 




OSISIS: GPTS ERROR: tmr_dereg(IIH) 

Description: Error occurred trying to stop the IIH timer. The OSISIS component of 


Reason: 




7436 0728–303 13–45


OSISIS: GPTS ERROR: tmr_dereg(ISH) 

Description: An error occurred trying to stop the ISH timer. The OSISIS component 


Reason: 




OSISIS: ID FIELD LENGTH MISMATCH 

Description: Received an ISIS PDU with an ID length that does not match the 

SYSIDLEN configured on the NSAP configuration statement. The OSISIS component 


Reason: There is an IS on the network that is not configured correctly. 

OSISIS: IGNORING UNRECOGNIZED OPTION IN ISIS PDU 

Description: An ISIS PDU was received with an unknown option. The OSISIS 


Reason: There is an IS on the network sending invalid or experimental PDUs. 

OSISIS: INITIALIZATION FAILURE (AREA MISMATCH) 

Description: Received an IIH that had no area addresses in common. The OSISIS 


Reason: There is an IS on the network that is in a different Level 1 area or not 

configured correctly. 

OSISIS: INVALID ADJ IN TENT 

Description: The adjacency ID stored in the tentative paths pool could not be 

brought into visibility. The OSISIS component of the OSITS program product 



OSISIS: INVALID CIRCID IN ADJACENCY POOL 

Description: Could not bring circuit ID into visibility. The OSISIS component of the 



13–46 7436 0728–303

OSISIS: INVALID CIRCUIT FOR IIH 


Description: Received an IIH on a circuit that doesn’t exist. The OSISIS component 



OSISIS: INVALID CIRCUIT FOR LSP 

Description: Received an LSP on a circuit that doesn’t exist. The OSISIS component 



OSISIS: INVALID CIRCUIT FOR SNP 

Description: Received an SNP on a circuit that doesn’t exist. The OSISIS component 



OSISIS: INVALID CIRCUIT TYPE IN PT–PT IIH 

Description: A point to point IIH was received with an invalid circuit type. The 


Reason: An IS on the network is sending invalid PDUs. 

OSISIS: INVALID IN AREA RIB ACK FROM OSIIP 

Description: An RIB acknowledgment was out of range. The OSISIS component of 



OSISIS: INVALID INPUT MESSAGE FROM NMS 

Description: A message was received from NMS with an unexpected format. The 



7436 0728–303 13–47


OSISIS: INVALID LITERAL TYPE FROM OSIIP 

Description: Received an unrecognized literal from OSIIP. The OSISIS component of 



OSISIS: INVALID LAN IIH RECEIVED (NO AREAS) 

Description: Received an IIH that had no area option. The OSISIS component of the 


Reason: There is an IS on the LAN that is not configured correctly. 

OSISIS: INVALID LAN IIH RECEIVED (TOO MANY AREAS) 

Description: Received an IIH that had more than MAXAREA area options. The 


Reason: There is an IS on the LAN that is not configured correctly. 

OSISIS: INVALID LOWLANPRIID 

Description: Unable the get the IS adjacency that is the lowest priority into visibility. 

The OSISIS component of the OSITS program product generates this CENLOG. 


OSISIS: INVALID OUT OF AREA RIB ACK FROM OSIIP 

Description: A Routing Information Base (RIB) acknowledgment was out of range. 



OSISIS: INVALID PT–PT IIH RECEIVED (NO AREAS) 

Description: Received an IIH that had no area option. The OSISIS component of the 


Reason: The IS on the other end of the static X.25 circuit is not configured correctly. 

13–48 7436 0728–303


OSISIS: INVALID PT–PT IIH RECEIVED (TOO MANY AREAS) 

Description: Received an IIH that had more than MAXAREA area options. The 


Reason: The IS on other end of the static X.25 circuit is not configured correctly. 

OSISIS: INVALID SUBNET DISABLE 

Description: Received a subnet disable for a circuit that doesn’t exist. The OSISIS 



OSISIS: INVALID SUBNET ENABLE 

Description: Received a subnet enable for a circuit that doesn’t exist. The OSISIS 



OSISIS: INVALID SUBNET IN OUT OF AREA RIB 

Description: The RIB points to an invalid OSISN. The OSISIS component of the 



OSISIS: INVALID SUBNET INN AREA RIB 

Description: The RIB points to an invalid OSISN. The OSISIS component of the 



OSISIS: INVALID SUBNET TYPE 

Description: An unrecognized subnet type was received in an OSIIP subnet created 

message. The OSISIS component of the OSITS program product generates this 

CENLOG. 


7436 0728–303 13–49


OSISIS: IS IGNORING RD PDU 

Description: Received a Redirect PDU when configured as an IS. The OSISIS 



OSISIS: LSP DATABASE OVERLOAD 

Description: Could not store an LSP. The OSISIS component of the OSITS program 


Reason: Insufficient resources. 

OSISIS: MANUAL ADDRESS DROPPED FROM AREA 

Description: One of the configured L1AREAS on the NSAP configuration statement 

has been dropped. The OSISIS component of the OSITS program product generates 

this CENLOG. 

Reason: The number of manual addresses on the LAN exceeded MAXAREAS and only 

the numerically lowest addresses are kept. 

OSISIS: MAXIMUM AREA ADDRESSES MISMATCH 

Description: Received an ISIS PDU with a maximum number of areas that does not 

match the MAXAREAS configured on the NSAP configuration statement. The OSISIS 


Reason: There is an IS on the network that is not configured correctly. 

OSISIS: MMERROR: {function} {pool name} 

Description: An error occurred during a call to the Memory Manager. The OSISIS 


Reason: 

R8: Memory management error code. 

R9: System error code. 

R10: Control block address. 

R11: Control block ID. 

13–50 7436 0728–303


OSISIS: MULTIPLE TRANSMIT PASSWORDS 

Description: More than one transmit password was specified on an ISISPASS 

configuration statement. The OSISIS component of the OSITS program product 



OSISIS: NEW SUBNET FROM IP REJECTED–NO MEMORY 

Description: Could not create circuit (subnet). The OSISIS component of the OSITS 


Reason: Insufficient memory. 

OSISIS: OSISIS CFACCS ACCESS ERROR 

Description: Access error during a CFACCS request. The OSISIS component of the 


Reason: For information on R8 error codes, refer to the Telcon Programming 

Reference Manual (7436 0710). 

OSISIS: OSISIS CFACCS IO ERROR 

Description: I/O error during a CFACCS request. The OSISIS component of the 


Reason: For information on R8 error codes, refer to the DCP/OS Programming 

Reference Manual (7431 6894). 

OSISIS: RECEIVED ISH ON A NON STATIC CIRCUIT 

Description: Received an Intermediate System Hello on a circuit that is not an X.25 

Static Circuit. The OSISIS component of the OSITS program product generates this 

CENLOG. 


OSISIS: RECEIVED LEVEL 2 CSNP (NOT SUPPORTED) 

Description: Received a Level 2 Complete Sequence Numbers PDU. The OSISIS 



7436 0728–303 13–51


OSISIS: RECEIVED LEVEL 2 IIH (NOT SUPPORTED) 

Description: Received a Level 2 IS–IS Hello PDU. The OSISIS component of the 



OSISIS: RECEIVED LEVEL 2 LSP (NOT SUPPORTED) 

Description: Received a Level 2 link-state PDU. The OSISIS component of the OSITS 



OSISIS: RECEIVED LEVEL 2 PSNP (NOT SUPPORTED) 

Description: Received a Level 2 Partial Sequence Numbers PDU. The OSISIS 



OSISIS: REJECTED ADJACENCY 

Description: Unable to add a new adjacency. The OSISIS component of the OSITS 


Reason: Insufficient resources. 

OSISIS: REJECTING CONS NSAP–BAD HASH 

Description: Could not enter the NSAP into the CONS RIB due to hash key failure. 


Reason: Duplicate NSAP. 

OSISIS: REJECTING ISISPASS NDS–NO MEMORY 

Description: Could not save the password specified on an ISISPASS configuration 

statement. The OSISIS component of the OSITS program product generates this 

CENLOG. 


13–52 7436 0728–303


OSISIS: REJECTING NSAP–BAD HASH 

Description: Unable to add an Out of Area RIB entry due to a bad hash key. The 


Reason: Possibly a duplicate NSAP. 

OSISIS: REJECTING NSAP–MMOUT POOL IS FULL 

Description: Ran out of RIB entries. The OSISIS component of the OSITS program 


Reason: Too many static routes. 

OSISIS: REJECTING NSAP NDS 

Description: Only one NSAP may be specified unless the multi-homed ES feature is 

enabled or Insufficient memory. The OSISIS component of the OSITS program 


Reason: 

R8: Symbol Table Entry Index of the configuration statement 

R9: 1 Multiple NSAPs 

R9: Insufficient memory 

OSISIS: REJECTING OSIROUTE. MUST BE AFTER NSAP NDS. 

Description: An OSIROUTE configuration statement is being discarded. The OSISIS 


Reason: NSAP configuration statement must appear before any OSIROUTE 

configuration statements. 

OSISIS: SUBNET NOT FOUND FOR ESH 

Description: Received an End System Hello PDU on a circuit that does not exist. The 



OSISIS: SUBNET NOT FOUND FOR ISH 

Description: An Intermediate System Hello was received on circuit that does not 

exist. The OSISIS component of the OSITS program product generates this CENLOG. 


7436 0728–303 13–53


OSISIS: SUBNET NOT FOUND FOR RD 

Description: Received a Redirect PDU on a circuit that does not exist. The OSISIS 



OSISIS: UNABLE TO CREATE CSNP 

Description: Could not create an MCT for a complete sequence numbers PDU. The 



OSISIS: UNABLE TO CREATE LSP 

Description: Could not create an MCT for a link-state PDU. The OSISIS component 



OSISIS: UNABLE TO CREATE NEW IN AREA RIB 

Description: mmpooldef( ) failed. The OSISIS component of the OSITS program 


Reason: OSIIP stopped. 

OSISIS: UNABLE TO CREATE PSEUDONODE PATHS 




OSISIS: UNABLE TO CREATE PSNP 

Description: Could not create an mct for a partial sequence numbers PDU. The 



13–54 7436 0728–303


OSISIS: UNABLE TO CREATE TENTATIVE PATHS 




OSISIS: UNABLE TO FIND CIRCUIT FROM CFFACS 

Description: Could not find the OSISN name on an configuration statement card in 

the circuit pool. The OSISIS component of the OSITS program product generates this 

CENLOG. 


OSISIS: UNABLE TO FIND NDS PASSWD IN POOL 

Description: Could not find the ISISPASS configuration statement in the password 

pool. The OSISIS component of the OSITS program product generates this CENLOG. 

Reason: Programming error 

OSISIS: UNABLE TO GET MSG FROM THE LINK AREA 

Description: Could not retrieve a message from the link area. The OSISIS 



OSISIS: UNABLE TO GET TRANSMIT PASSWORD 

Description: The configured transmit password was not in the database. The OSISIS 


Reason: Programming error 

OSISIS: UNABLE TO HASH NAME ON ADDRESS NDS 

Description: NSAP to ASCII translation for this configuration statement is not 

possible due to hashing failure. 

Reason: R8: Symbol Table Entry Index of the configuration statement. 

7436 0728–303 13–55


OSISIS: UNABLE TO INFORM OSIIP OF AREA CHANGE 

Description: Could not create an MCT to queue to OSIIP. The OSISIS component of 



OSISIS: UNABLE TO LINK MSG 

Description: Could not store a message in the link area. The OSISIS component of 


Reason: Out of resources. 

OSISIS: UNABLE TO REGISTER WITH NMS 

Description: Could not create the message to register the ‘OSI’ prefix with NMS. The 



OSISIS: UNABLE TO REQUEST ALL ADDRESS NDSs 

Description: Could not queue the message to CFACCS. The OSISIS component of 


Reason: CFACCS queue is full. 

OSISIS: UNABLE TO SAVE ROUTE NAME ON NDS 

Description: NSAP to ASCII translation for this configuration statement is not 

possible due to memory constraints. The OSISIS component of the OSITS program 


Reason: 

R8: Symbol Table Entry Index of the configuration statement. 

OSISIS: UNABLE TO SEND TO CFACCS 

Description: Error in queuing a message to CFACCS. The OSISIS component of the 


Reason: 

R8: 1 ... Message could not be created. 

R8: 2 ... Message could not be queued. 

13–56 7436 0728–303


OSISIS: UNEXPECTED FUNCTION CODE FROM CFACCS 

Description: Received a response from CFACCS that was not expected. The OSISIS 



OSISIS: UNRECOGNIZED HIC FROM NMS 

Description: A message was received from NMS with an unexpected HIC. The 



OSISIS: UNRELEASED ADDRCB 

Description: An address control block is still in visibility at task termination. The 



OSISIS: UNRELEASED ADJCB 

Description: An adjacency control block is still in visibility at task termination. The 



OSISIS: UNRELEASED CIRCUITCB 

Description: A circuit control block is still in visibility at task termination. The 



OSISIS: UNRELEASED CONSCB 

Description: A CONS RIB control block is still in visibility at task termination. The 



7436 0728–303 13–57


OSISIS: UNSOLICITED ECHO REPLY 

Description: An Echo Reply was received without sending an Echo Request (PING) 

or it was received after the Echo Request timed out. The OSISIS component of the 


Reason: Too short of a lifetime on a PING. 

OSISIS: UNRELEASED ESCB 

Description: An End System ID control block is still in visibility at task termination. 



OSISIS: UNRELEASED LSPCB 

Description: A Link State PDU control block is still in visibility at task termination. 



OSISIS: UNRELEASED OUTCB 

Description: An Out of Area control block is still in visibility at task termination. The 



OSISIS: UNRELEASED PASSWDCB 

Description: A password control block is still in visibility at task termination. The 



OSISIS: UNRELEASED PATHSCB 

Description: An In Area RIB control block is still in visibility at task termination. The 



13–58 7436 0728–303


OSISIS: WRONG SYSTEM TYPE FOR PT–PT IIH 

Description: A point to point IIH was received from a Level 2 Only IS. The OSISIS 


Reason: The IS on the other end of the static X.25 circuit is a Level 2 only IS. 

OUTPUT MESSAGE LOST 

Description: The IS-PC software interface module (PDNDXA) has output message 

data but must discard it because the connection is down or the link area is full and 

can not be expanded. 

Attributes affected: Supplementary text message or error event. The X.25 PSCS 

program product generates this CENLOG. Procedure: TPCDATA. 

Action: This event is expected (normal) if the line over which the connection was 

active is downed. “Clear” CENLOG entries would be associated with this entry. If, 

however, the event occurs and the line is up then this indicates a memory resource 

problem. You should re-examine the sizing requirements for the products being used. 

PACKET LAYER CLEARING -- R8=DTE STEX 

Description: The X.25 to TSTN protocol module (PDNDXA) received a clear 

indication primitive from the Layer 3/4 Platform interface. 

R8: DTE STE index TSID 

R9: Packet’s diagnostic code. See Appendix A in this manual for a description of the 

diagnostic code. 

Attributes affected: Non-displayed event, supplementary text message, device event 

contains the DTE statement name. The X.25 PSCS program product generates this 


7436 0728–303 13–59


PDNL3 CALLED BUT X.25 IS NOT UP 

Description: The PDNL3 module was activated, but X.25 PSCS has not (yet) 

initialized. An item, such as a Call Request primitive from a layer 4 module, has been 

placed on the PDNL3 queue, but no X.25 PSCS tables have been built for processing 

the item. 



Action: Verify that at least one of the X.25 PSCS lines is enabled on a valid line 

module using an NMS UP LINE command. If a line has already been enabled, then 

X.25 PSCS may currently be initializing; or an initialization error has occurred and has 

been recorded with a CENLOG class/event of 5/15 with a supplementary text message 

of: “PSCS initialization error.” 

PDNURS - PSCS NOT INITIALIZED, MESSAGE DISCARDED 

Description: An NMS TERM command was entered and the TERM name is 

associated with either a UTS 4000 cluster controller workstation or an X.29 PAD 

terminal running over an X.25 network. Because the X.25 program product is not yet 

initialized the command cannot be processed. 


generates this CENLOG. Procedure: PDNURS. 

Action: No action required. Because X.25 PSCS is not initialized, no internal run-time 

terminal table exists for updating. 

SNA: 808 - no actid match for ACT/TEST REPLY 


network routing portion of SNA/net. The probable cause is a software problem. 

13–60 7436 0728–303


SNA: 809 - max piu too small, SA=%%%% size=&&& 

Description: This message occurs as a result of errors or events in ERVR. The 

possible causes are a configuration error or a software problem. The subarea sending 

the invalid PIU size is included for reference. The % represents a hexadecimal number 

and the & represents a decimal number. 

SNA: 811 - er send error, invalid tg number 



X.25 Clear by DCP–Cause, Diagnostic=hhh,hhhh 


module in PDNSVS received an alarm notification. (CNMS does not need to be 

operating for this CENLOG to be enabled.) The layer 3 module sent a Clear packet to 

the network for a particular virtual circuit. This event includes the LINE name and 

could include the DTE statement name or address information. 



R10: Packet’s cause code. See Appendix C of this manual for a description of the 

cause code 

R11: Packet’s diagnostic code. See Appendix A of this manual for a description of 

the diagnostic code 

R12: CNMS alarm code 

Attributes affected: Supplementary text message, Line event, Device event, (if the 

clear [reset] packet is associated with a configured DTE statement and CNMS is not 

active), can include CNMS interface packet. The X.25 PSCS program product 

generates this CENLOG. Procedure: PDNSVS. 

7436 0728–303 13–61


X.25 Clear by Network–Cause,Diagnostic=hhhh,hhhh 



operating for this CENLOG to be enabled.) The layer 3 module received Clear packet 

from the network for a particular virtual circuit. This event includes the LINE name 

and could include the DTE statement name or address information. 




cause code. 


the diagnostic code. 


R13: Layer 4 routing identifier 

Attributes affected: Supplementary text message, Line event, Device event (if the 

clear [reset] packet is associated with a configured DTE statement and CSNM is not 



X.25: DEFAULT LEVEL 4 NOT ALLOWED FOR LEVEL 4 TYPE 

Description: X.25 PSCS received an incoming call packet from the network. The 

X25ROUTE statement’s LEVEL4 parameter is used to configure a default layer 4, but 

X.25 PSCS does not support this layer 4 as a default. 

R9: Level 4 routing id (ZH$ Equate). 


generates this CENLOG. Procedure: PCALL. 

Action: Modify the X25ROUTE statement. 

13–62 7436 0728–303


X.25: L4 Message Discarded -- No Virtual Circuit Table R8=L4 to L3 

Message Type 

Description: The layer 3 module (PDNL3) received a message from a Layer 4 module 

but the layer 3 connection identifier did not match a currently active virtual circuit 

table. 

R8: Layer 3/4 Platform’s primitive type (ZR$xx43) 

R9,R10: Layer 3 connection identifier passed by the Layer 4 module 



Action: This indicates an unexpected software interface error. It is difficult to 

determine which layer 4 module is responsible because the virtual circuit table it 

identified is no longer associated with that connection, and the layer 4 module is not 

obligated to supply its routing id in most primitives except for call set-up primitives. If 

no user-written layer 4s are actively using the interface, you should contact your 

Unisys representative. 

X.25: Invalid Message Primitive from L2 R8=L2 to L3 Message 

Type,R9= PDNGRP Index 

Description: The layer 3 module (PDNL3) received an invalid message type from the 

layer 2 (data link layer) module or its interface module. 

R8: Message type (ZR$xx23) 

R9: STE index of the PDNGRP configuration statement associated with the line 



Action: This indicates an unexpected internal software interface error. You should 

contact your Unisys representative. 

7436 0728–303 13–63


X.25: L4 Call Request Cleared, R11=reason 

Description: The layer 3 module (PDNL3) was unable to successfully process a Call 

Request primitive received across the Layer 3/4 Platform interface. Instead of sending 

a call request packet to the network, PDNL3 returned a Clear Indication primitive to 

the layer 4 module. 

R11: Clear primitive’s diagnostic code. For a description of the codes, refer to 

Appendix A of this manual. 

R12–R15: May contain the called DTE address digits 



X.25 Link Area Full 

Description: The PDNL3 module was unable to save a data message for later 

transmission to the network or layer 4 for a particular virtual circuit. No link area 

indexes were available. PDNL3 clears the virtual circuit. 



X.25 Network Layer Event 


module in PDNSVS received an alarm notification. (CNMS does not need to be in 

operating for this CENLOG to be enabled.) The reason code is passed and displayed 

by register R12. This event includes the LINE name, and could include the DTE 

statement name or address information. 


R9: May contain the logical channel number 

R10: May contain a packet’s cause code. See Appendix C of this manual for a 

description of the cause code. 

R11: May contain a packet’s diagnostic code. See Appendix A of this manual for a 

description of the diagnostic code. 


Attributes affected: Supplementary text message, Line event, may include CNMS 

interface packet. The X.25 PSCS program product generates this CENLOG. 


X.25 - PCALL Trace File Error - No Space 

Description: The NMS TRAC SNAP=X25 command was used to enable tracing during 

establishment of a virtual circuit. An error occurred while cataloging the trace file 

used by the PDNCALL module. 

13–64 7436 0728–303


R8: DCP/OS FILE$ error code corresponding to equate FR$NS, “no space or no 

free DSL” 


generates this CENLOG. Procedure PCALL. 

Action: Delete some unused DCP mass storage files to free disk space. The disk 

space required must be contiguous. 

X.25: PDNCALL TRACE FILE CLOSING ERROR 

Description: The PDNL3 module was unable to successfully close PDNCALL’s trace 

file. The DCP OS FILE$ service returned an error. 

R8: DCP OS FILE$ error code 



X.25: PDNCALL TRACE FILE ERROR 

Description: The NMS TRAC SNAP=X25 command was used to enable tracing during 

establishment of a virtual circuit. An error occurred with the trace file used by the 

PDNCALL module. 

R8: Error code returned by the DCP/OS FILE$ service request. Consult the 

DCP/OS Operations Reference Manual (7831 5702) for a description of the 

error code. 



Action: Depends upon the error code. May indicate problems with the mass storage 

device. Procedure: PCALL. 

7436 0728–303 13–65


X.25: PDNL3 TRACE FILE ERROR 

Description: The PDNL3 module was unable to successfully write trace information 

into its trace file. An error was returned by the DCP OS FILE$ service. 




X.25 - PDNL3 Trace File Error - No Space 

Description: The NMS TRAC SNAP=X25 command was used to enable an X.25 

protocol packet and/or message data tracing on a virtual circuit. An error occurred 

while cataloging the trace file used by the PDNL3 module. 

R8: DCP/OS FILE$ error code corresponding to equate FR$NS, “no space or no 

free DSL” 


generates this CENLOG. Procedure PDNL3. 

Action: Delete some unused DCP mass storage files to free disk space. The disk 

space required must be contiguous. 

X.25 Reset by DCP–Cause, Diagnostic=hhhh,hhhh 



operating for this CENLOG to be enabled.) The layer 3 module sent a reset packet to 

the network for a particular virtual circuit. This event may include the DTE statement 

name or address information. 




cause code. 








13–66 7436 0728–303

X.25 Restart by DCP–“reason" 




operating for this CENLOG to be enabled.) The layer 3 module sent a Restart packet 

to the network on a particular network connection (line). This event includes the 

LINE name. 



cause code. 







X.25 Reset by Network–Cause,Diagnostic=hhhh,hhhh 



operating for this CENLOG to be enabled.) The layer 3 module received Reset packet 

from the network for a particular virtual circuit. This event includes the LINE name 

and may include the DTE statement name or address information. 




cause code. 




R13: Layer 4 routing identifier 





7436 0728–303 13–67


X.25 Restart by Network – Cause,Diagnostic=hhhh,hhhh 



operating for this CENLOG to be enabled.) The layer 3 module received a restart 

packet from the network on a particular network connection (line). This event 




cause code. 







X.25 SNMP: ICS Registration Failed (“procedure name”) 

Description: The X.25 PSCS SNMP interface module (PDNSMP) received an ICS 

Registration Response message with an error code. This error causes PDNSMP to 

become dormant. In this case, no SNMP MIB information related to X.25 can be 

retrieved. 

R8: ICS Registration Response error code 

Attributes affected: Error event, supplementary text message, and a table of the ICS 

response packet. 

Action: This event indicates an internal software interface error. Submit the contents 

of the entry to your Unisys representative for analysis. You must re-start your Telcon 

run, and you may need to re-start ICS, in order to recover from this error. If the error 

re-occurs, take a Telcon dump and submit a UCF. 



13–68 7436 0728–303


X.25 SNMP: MAU SNMP Component is active (“procedure name”) 

Description: The X.25 PSCS SNMP interface module (PDNSMP) successfully 

completed its initialization with ICS and the SNMP Management-Agent user (MAU) 

interface. This event indicates that you can access X.25-related information from the 

SNMP MIB using an SNMP manager workstation. If you cannot, refer to the ENS 

Installation, Configuration and Operations Guide (7441 2065) for verifying the 

SNMP Agent program. Also refer to the CD 6R2 Release Notes (7442 1207) X.25 PSCS 

Troubleshooting section for configuration and operational considerations. 

Attributes affected: Supplementary text message. 



X.25: SUB-ADDRESS NOT PERMITTED FOR LEVEL 4 TYPE 

Description: X.25 PSCS received an incoming call packet from the network. The 

X25ROUTE statement’s SUBADR parameter is used to configure a layer 4 based upon 

the called DTE address sub-address digits, but X.25 PSCS does not support the subaddress 

routing this layer 4. 

R9: Level 4 routing ID (ZH$ Equate) 



Action: Modify the X25ROUTE statement. Procedure: PCALL. 

X.25: TRACE CATALOG FILE SIZE RECEIVED 

Description: The PDNL3 module acknowledges the receipt of the trace file size data 

value specified in the DATA parameter of the NMS TRAC X25 command. The TYPE 

parameter included an “L.” 

R8: DATA parameter value received 



7436 0728–303 13–69


X.25: TRACE CONTENT DATA RECEIVED 

Description: The PDNL3 module acknowledges the receipt of the trace items data 


parameter included an “M.” 




X.25: TRACE FILE CLOSING ERROR 

Description: The PDNL3 module was unable to successfully close the PDNL3 trace 

file. The DCP OS FILE$ service returned an error. 




X.25: TRACE FILES CLOSED 

Description: The PDNL3 module acknowledges the receipt of a close trace file 

request by specifying a zero in the DATA parameter of the NMS TRAC X25 command. 

The TYPE parameter included an “L.” 



X.25: TRACE INTERFACE DATA RECEIVED 

Description: The PDNL3 module acknowledges the receipt of the trace interface data 


parameter included an “H.” 




THERE ARE DTES WITHOUT DTEID!! 

Description: The PDNDXA module was unable to obtain an internal DTE statement 

identifier from the DTE STE. A software error has corrupted the DTE STE or the 

initialization routine (PDNIUS) in X.25 PSCS. 


generates this CENLOG. Procedure: TPCDATA. 

13–70 7436 0728–303


TROUBLE LINK DETECTED–TRUNK: trunkname 

Description: Node not allowed to establish neighbor communications over the 

named trunk, because neighbor communications have been disrupted too often in the 

past few minutes. Telcon generates this CENLOG. 

The CENLOG registers contain the network address of the node in the following 

manner: 

R8: Node number 

R9: Simple cluster number 

R10: Super cluster number 

R11: Subdomain number 

Action: Determine and correct the causes of the disruptions (for example, links going 

up and down and rebooting nodes). 

TRUNK Overflow Condition Detected–TRUNK: trunkname 

TSTN 

Description: The subnetwork the named trunk is using is saturated. This occurs 

because the capacity of the subnetwork is insufficient for the amount of data being 

routed through it. You may experience delay-induced timeouts and resets of 

connections whose data traverses this trunk. Telcon generates this CENLOG. 

Action: The system administrator must re-engineer the subnetwork the trunk is using 

to accommodate the amount of data being routed through it, or readjust the network 

topology and routing to reduce the amount of data traversing the trunk. 

Description: Received ADD QCT INDEX TO QUEUE LIST command from 

SYSTSTRK after the system initialization process completed. The ADD QCT INDEX 

command should have been sent during system initialization, not after. The command 

was processed. Telcon generates this CENLOG. 

UNCONFIGURED NEIGHBOR REJECTED–TRUNK: trunkname 

Description: Node not allowed to establish neighbor communication over the named 

trunk because of the trunk’s boundary restrictions. Telcon generates this CENLOG. 

The CENLOG registers contain the network address of the node as follows: 

R8: Node number 

R9: Simple cluster number 

R10: Super cluster number 

R11: Subdomain number 

Action: To establish neighbor communications with the node over the trunk, add a 

BOUNDARY parameter in the TRUNK configuration statement. 

7436 0728–303 13–71

Event 4 EVENT/ERROR DETECTED AT L4 (TRANSPORT) 


(TRANSPORT) 

EVENT/ERROR DETECTED AT L4 (TRANSPORT) 

Description: An error has been discovered in a Layer 4 protocol packet that DTP 

received. Layer 4 is the Transport Layer of the DCA stack. DTP is the Transport 

Layer. DTP has received an invalid service primitive. R13 contains a JLR return 

address of the offset within the DTP module at which the error was discovered. IF R6 

was nonzero, the first 64 words of the source buffer in question is traced in the 

CENLOG. After that, the 16 words of the MCT trace history (MC$PROCNR) are also 

traced. If R6 is nonzero and R11 is nonzero, then R9 will show the TSU (EU) class 

from TP$TSUCL. R11 shows the address of the TP$ entry. 

Action: If this is occurring frequently, and/or if users are unable to make session 

connections for no other explainable reason, then take a SNAP dump. Submit the 

dump, with the configuration print-file from HCONFIG and the CENLOG files or hardcopy 

long-format printouts of these CENLOGs. If there are any program products 

installed that deal with network transports (such as OSITS, TCP–IP, PSCS, or X.25), 

submit the UCF to the most active program first. If there is any local code dealing 

with network transports, submit the dump information to the owners. Otherwise, 

submit the UCF to the Telcon product. 

13–72 7436 0728–303


DCE FEATURE–CONFIGURATION ERROR 

Description: The DCE Feature module (PDNNET) was unable to successfully 

process one of its configuration statements. 

R13: Virtual address in PDNNET module in which error occurred 

R15: Error codes: 

=7 An X25NET statement doesn’t reference an XEU statement. The 

offending statement’s STE and information table is included in this event. 

=8 An X25NET statement references a statement that isn’t an XEU. The 

offending statement’s STE and information table is included in this event. 

=9 PDNNET received a Call Request primitive from one of the layer 4 

modules, but the DTE address is invalid. That is, the format of the 

address doesn’t conform to any of the DNIC or DCE node addresses 

defined. The MCT containing the primitive received from layer 4 is 

included in this event. 

=10 A subsequent CFACCS access to the PDNNET EU statement has failed. 

This is a software error in either CFACCS or the PDNNET work area 

buffer has become corrupted. The STE and information table accessed is 


Attributes affected: Supplementary text message, Error event. The X.25 PSCS 

program product generates this CENLOG. Procedure: PDNETP. 

DCE FEATURE–DCA MESSAGE DISCARDED 

Description: The DCE Feature module (PDNNET) received an unknown or 

unexpected message type from DTP, or PDNNET was unable to successfully process 

the DTP HIC string. The first part of the message buffer received from DTP is 


R11: If unknown, contains message type code received 




7436 0728–303 13–73


DCE FEATURE–LAYER FOUR MESSAGE DISCARDED 

Description: The DCE feature module (PDNNET) received an unknown or 

unexpected primitive from one of the layer 4 modules. The MCT containing the 

PCALL packet received from layer 4 is included in this event. 




DCE FEATURE–NOT INITIALIZED 

Description: The DCE feature module (PDNNET) is unable to successfully complete 

initialization. Reasons include not being able to reroute items intended for layer 3’s 

(PDNL3 module’s) queue to PDNNET. 



DCE FEATURE–PDNL3 MESSAGE DISCARDED 


unrecognized primitive from layer 3 across the Layer 3/4 Platform. The MCT 

containing the PCALL packet received from layer 3 is included in this event. 

R13: Virtual address in PDNNET module in which error occurred. 



DCE FEATURE–PEER MESSAGE DISCARDED 


unexpected primitive from its peer module in another Telcon node. The first part of 

the message buffer received from its peer is included in this event. 




13–74 7436 0728–303


DCE FEATURE–STATE/PROTOCOL VIOLATION 

DTP 

Description: The DCE feature module (PDNNET) received an invalid primitive from 

layer 3 across the Layer 3/4 Platform, or from its peer because of the state that 

PDNNET perceives the connection. The MCT containing the PCALL packet received 

from layer 3, or the first part of the message buffer received from its peer is included 

in this event. 




Description: DTP has detected an error in a recognizable service primitive control 

message. Telcon generates this CENLOG. 

INSTDC 

Description: INSTDC received error status from EUSERV when it tried to open a 

session with a remote central logging Telcon node. May be caused by improper 

configuration of XEU that defines remote logging point. R1 contains the error code 

from EUSERV. Telcon generates this CENLOG. 

OSITS–IPM CONTINGENCY ERROR 

Description: An IPM contingency item was ignored. The OSITS component of the 


Reason: The IPM contingency item contained either an erroneous or an unrecognized 

function code. 

OSITS–IPM REGISTRATION ERROR 

Description: Unable to register as an IPM receiver. The OSITS component of the 


Reason: IPM receive registration failed. 

7436 0728–303 13–75


PDNNET–DCE FEATURE INITIALIZED 

Description: The DCE feature has been configured with an EU statement and 

PDNNET statements if needed. During Telcon initialization this event indicates that 

the DCE feature module (PDNNET) has received its EU statement information table 

or the first of any X25NET information tables. The PDNNET has not yet processed 

any of these information tables; subsequent CENLOG events may indicate an 

initialization error. 

Attributes affected: None. The X.25 PSCS program product generates this 


SNA: 800 - vrsnf rcv bad, psa,vrid,exp,act=%%%% %%%% %%%% 


network routing portion of SNA/net. Where psa refers to partner subarea and % 

represents a hexadecimal character. The probable cause is a software problem. 

SNA: 801 - invalid th 



SNA: 804 - vr receive no vrcb, psa=%%%%, pea=%%%%, 

vrid=%%%% 




SNA: 806 - Bad NC message from SA=%%%% EA=%%%% 

VR=%%%% 


network routing portion of SNA/net. Where % represents a hexadecimal character. 


SNA: 807 - no free vrn, cur_ern=%%%% 




SNA: 812 - bad RERN on actvr, psa=%%%%, rern=%%%% 




13–76 7436 0728–303


SNA: 813 - vrprs not rcvd on vractrsp, psa=%%%%, vrid=%%%% 




SNA: 818 - invalid domain index 

Description: An invalid domain index has been received by the SNA/net ERVR 

module. The probable cause is a software problem. 

SNA: 1205 - Clear - Link Down 




SNA: 1206 - Clear - Local Procedure Error 




SNA: 1207 - Clear - Remote Procedure Error 




SNA: 1208 - Clear - Out of Order 




SNA: 1209 - Clear - Network Congestion 




SNA: 1210 - Clear - DTE Originated 




7436 0728–303 13–77


SNA: 1211 - Clear - Invalid Cause Code 




SNA: 1212 - Reset - Local Procedure Error 




SNA: 1213 - Reset - Remote Procedure Error 




SNA: 1214 - Reset - DTE Originated 




SNA: 1215 - Reset - Network Congestion 




SNA: 1216 - Call Setup Improper 




SNA: 1217 - QLLC Error - Undefined C-field 




SNA: 1218 - QLLC Error - Unexpected C-field 




13–78 7436 0728–303


SNA: 1219 - QLLC Error - Missing I-field 




SNA: 1220 - QLLC Error - Undefined I-field 




SNA: 1221 - QLLC Error - I-field Too Long 




SNA: 1222 - QLLC Error - Frame Reject Received 




SNA: 1224 - Diagnostic Packet Received 




SNA: 1227 - Facility Not Supported 




SNA: 1228 - Unexpected Calling DTE 




SNA: 1229 - Unexpected XID 




7436 0728–303 13–79


SNA: 1230 - Reset Invalid For SVC 




SNA: 1231 - Invalid Protocol Identifier 




SNA: 1232 - Connection Identifier Mismatch 




SNA: 1233 - QDISC Command Received 




13–80 7436 0728–303

Event 5 EVENT/ERROR DETECTED AT L5 (SESSION) 


EVENT/ERROR DETECTED AT L5 (SESSION) 

Description: A significant event has taken place, or an error has been discovered in 

the DCA protocol stack layer 5, Session Layer. 

Action: Dependent on supplementary message (or procedure name) as follows. 


ATTACH TO DTP 

DTPX 

Description: DTPX has received an error in response to the registration with DTP on 

behalf of an SSU registering with DTPX. Telcon generates this CENLOG. 

Description: A bad HIC has been received from the session service user or from the 

peer session services. 

R8: DTPX error status (shown in hexadecimal): 

0 OK status. 

1 Missing parameter. 

2 No end of packet. 

3 Error AU HIC. 

4 Error AU label length. 

6 No AS$SPEX. 

8 Error in DTPX header. 

9 Error in EUAFO. 

A Error VER HIC. 

B Error IDENT length. 

C Past FTXT offset. 

F Unexpected table type from DSRV. 

10 Zero AU label. 

12 Access authority error. 

13 Directory information base access error. 

14 Invalid interface message type. 

15 Invalid transport type. 

16 Transport service not available. 

R9: CENLOG code = CE$ICR = 45 

R10: The address of the procedure in DTPX in which the error occurred. 

R11: First HIC of message if a control message, otherwise zero. 

7436 0728–303 13–81


R12: If reject or abort is sent out, R12: reason code, otherwise zero. 

R13: SSU ID1 if R8 = 9 

R14: SSU ID2 if R8 = 9 

R15: SSU Class if R8 = 9 


EUINIT 

Description: Occurs when the end user ATTACH confirm analysis routine is called 

and the ATTACH confirm appears bad. Telcon generates this CENLOG. 

INVALID IPM FREE CONTINGENCY FOR IPMID=nnnn REASON=nnnn 

Description: DTPX encountered an error (indicted by the REASON value) while 

processing the IPM FREE. Telcon generates this CENLOG. 

IPM CONNECT CONTINGENCY FOR IPMID=nnnn REPLY 

NAME=aaaaaaaa 

Description: DTPX has received an IPM connect. The connection was initiated by 

the user identified by the REPLY NAME value. Telcon generates this CENLOG. 

IPM CONNECT ERROR FOR IPMID=nnnn 

Description: DTPX detected an error when attempting to obtain an IPM status using 

the IPM ID from an IPM CONNECT. Telcon generates this CENLOG. 

IPM CONTINGENCY CODE ERROR–CODE=nnnn 

Description: DTPX has received an unrecognized IPM contingency code (indicated 

by the code value). Telcon generates this CENLOG. 

IPM DISCONNECT CONTINGENCY FOR IPMID=nnnn 

REPLY NAME=aaaaaaaa FREE STATUS=nnnn 

Description: DTPX received an IPM DISCONNECT. The DISCONNECT was for the 

user identified by the REPLY NAME value. Telcon generates this CENLOG. 

IPM DISCONNECT PERFORMED FOR IPMID=nnnn DISCONNECT 

STATUS=nnnn 

Description: DTPX disconnected the IPM attachment indicated by the IPMID value. 


13–82 7436 0728–303


IPM FREE CONTINGENCY FOR IPMID=nnnn 

REPLY NAME=aaaaaaaa TSU ID=xx 

Description: DTPX received an IPM FREE. The FREE was for the user identified by 

the REPLY NAME value. Telcon generates this CENLOG. 

ISYSTEM NOT COMPLETE 

Description: DTPX has received an SSU registration prior to the completion of 

system initialization. Telcon generates this CENLOG. 

NO SESSION TO ALTERNATE DCP CONFIGURED 

Description: The System Resiliency Control module (SRC) has received a sessionconnect-reject 

HIC (= 041), with reason-code (E7$RSNCV) = AH$CNFER (05), R10 = 

BH$ buffer pointer, and R14 = EUSERV (EUSTRAN) E&$ buffer pointer. 

Action: Verify that your configuration has a TSTN session configured to each backup 

DCP. (Your configuration is not currently setup to use DNS sessions to an alternate 

backup DCP). 

SNA: 802 - send vrcb not found, yea=%%%%, vrcbid=%%%% 




SNA: 805 - sesid bad, rucd,yea,sid,vrcbid=%%%% %%%% %%%% 

%%%% 




SNA: 2657 – SNA/TIF initial open reject 



7436 0728–303 13–83

Event 6 EVENT/ERROR DETECTED AT L6 (PRESENTATION) 


(PRESENTATION) 

EVENT/ERROR DETECTED AT L6 (PRESENTATION) 


the DCA protocol stack layer 6, the presentation layer. 

Action: Dependent on the supplementary (or procedure name) displayed. 

Supplementary Messages for Class 13 Event 06 

Reserved. 

13–84 7436 0728–303

Event 7 EVENT/ERROR DETECTED AT L7 (APPLICATION) 


(APPLICATION) 

EVENT/ERROR DETECTED AT L7 (APPLICATION) 


the DCA protocol stack layer 7, Application Layer. 

Action: Dependent on the supplementary (or procedure name) displayed. 


Reserved. 

Description: The EUAFO interface rejected an IPC message. 

R8, R9: Conversation identifier 

R11: AP class 


NTRLPH 

Description: This event occurs if an RB-2 protocol error is detected. A supplemental 

message specifies the protocol error. In most cases, this results in the affected device 

being immediately terminated. If it is an output device, the file is requeued. If it is an 

input device, its file is discarded. Other information logged: 

R14: The line’s PP ID 

R15: The device’s device-number. Other registers are applicable to debug use only 

and are different for each case. 


7436 0728–303 13–85

Event 7 EVENT/ERROR DETECTED AT L7 (APPLICATION) 

NTRV2R 

Description: This event occurs if an RB-2 protocol error is detected. A supplemental 

message specifies the side (host or DCP) that detected the error. In most cases, this 

event results in the affected device being immediately terminated. If it is an output 

device, the file is requeued. If it is an input device, its file is discarded. Other 

registers are applicable to debug use only, and are different for each case. Other 


R14: The line’s PP ID 

R15: The device’s device number 


13–86 7436 0728–303

Event 8 TERMINATION SYSTEM IS UP 

TERMINATION SYSTEM IS UP 

Event 8 TERMINATION SYSTEM IS UP 

Description: The Host channel Control procedure (HCC) has received an ‘SAI UP’ 

control message, for a channel (control block-HH$) that was previously blocked 

(HH$BLK set). 

R14 is the PPID 

R9 is the channel-type identifier (HH$ID) 

Action: None. This is an informational CENLOG to apprise you that the host (CMS 

1100) has gone down. Check on the status of CMS 1100 for the host connected to the 

channel PPID. 

7436 0728–303 13–87

Event 9 PATH TO THE TS IS BLOCKED 















STATDCR 



OR 

Description: The Host Channel Control procedure (HCC) has received an ‘SAI 

BLOCKED’ control message, for a channel (control block - HH$) that was previously 

UP. R14 is the PPID, and R9 is the channel-type identifier (HH$ID). 

Action: If this host channel disconnection was not intended and the cause was not 

clear, redisplay this CENLOG in long format (LOGI SEQ=n, OPTN=LONG) and take a 

CMS 1100 trace and log, then call your Unisys representative. A long format example 

follows: 

13–88 7436 0728–303

Oldest 

PPtrace 

Table 13–1. Example of Long Format 


0008= 0000 EB0E 0B00 0100 0000 0000 0000 0000 

0010= 1001 0002 029B 1E88 8708 0002 0008 0000 

-4 0018= 0000 0000 0000 0000 0000 0000 0000 0000 

0020= 1000 0000 029B 1F04 830F 0000 0000 0000 

-3 0028= 0000 0000 0000 0000 0000 0000 0000 0000 

0030= 1001 0002 029B 2E43 8707 0002 0008 0000 

-2 0038= 0000 0000 0000 0000 0000 0000 0000 0000 

0040= 1000 0000 029B 2EB3 830F 0000 0000 0000 

-1 0048= 0000 0000 0000 0000 0000 0000 0000 0000 

PP 

trace 

newest 

PPtrace 

0050= 1000 0000 029B 3E69 830F 0000 0000 0000 

0058= 0000 0000 0000 0000 0000 0000 0000 0000 

0060= 1000 0000 029A 6126 020A 0000 07EC 4000 

0068 4D0E 07E6 8AB0 F1FB 0660 0B77 0670 0017 

7436 0728–303 13–89


�� 

� 

�� 

�� 

� 

�� 

�� 

� 

�� 

�� 

� 

�� 

�� 

� 

�� 

�� 

� 

�� 

�� 

� 

�� 

�� 

� 

�� 

Table 13–1. Example of Long Format (continued) 

�� 

�� 

�� 

�� 

�� 

�� 

�� 

�� 

�� 

13–90 7436 0728–303

Table 13–2. Input Logging Items 


Input Status Items Channel Types 

(1) # of input data frame x 

(2) # of input super frame x 

(3) # of input error frame x 

SU057 FEPI 

(4) # of input time out x x 

(5) # of input NAK frame x x 

(6) # of input consecutive time out x x 

(7) # of input RTA frame x 

(8) NO-BUFFER during input processing x x 

(9) LM status input limit x 

(10) LM status response timer time out x 

(11) LM status off line x 

(12) LM status system reset x 

(13) LM status selective reset x 

(14) LM status terminate CMDs x 

(15) LM status H/W parity error x 

(16) LM status no command x 

(17) LM status lost data x 

(18) LM status illegal loop back x 

7436 0728–303 13–91


SRC 

Table 13–3. Output Logging Items 

Output Status Items Channel Types 

SU057 FEPI 

(1) # of output data frame x x 

(2) # of output super frame x x 

(3) # of output time out x x 

(4) # of output NAK frame x x 

(5) # of output consecutive time out x x 

(6) LM status response timer time out x 

(7) LM status off line 

(8) LM status system reset x 

(9) LM status selective reset x 

(10) LM status terminate CMDs x 

(11) LM status no command x 

(12) LM status lost data x 

(13) LM status illegal loop back x 

(14) LM status stop sequence x 

Description: This class and event code is used internally to inform the system that a 

critical host channel has logically disconnected. Telcon generates this CENLOG. 

13–92 7436 0728–303




7436 0728–303 13–93


13–94 7436 0728–303

Section 14 


CENLOGs in Class 14 result from unrecoverable communication line errors. 

Event 1 LINE CONNECTION (UNSUCCESSFUL) 

LINE CONNECTION (UNSUCCESSFUL) 

Description: An unsuccessful attempt was made to connect an external line. Telcon 


Action: Check all applicable hardware and repair or replace as necessary. If 

hardware is operational, check system configuration information for completeness 

and correctness; that is, UDLC station addresses, dial-out phone numbers, and dialer 

line module port IDs. 

UDLCRS 

Description: R8: 0010. AE$UD102. (UDLC): NO HCB. The line is connected 

physically and the remote station is known, but there is no HCB for the high-level 

entity with which the station is associated. Telcon generates this CENLOG. 

UDLCRS 

Description: R8: 0011. AE$UD103. (UDLC): CONFIG READ ERROR ON LINE 

TABLE - CHECK CONFIG/DISK. The line is connected physically, but an error 

occurred accessing the line information table. Telcon generates this CENLOG. 

UDLCRS 

Description: R8: 0012. AE$UD104. (UDLC): CONFIG READ ERROR ON GROUP 


occurred in accessing the group information table. Telcon generates this CENLOG. 

UDLCRS 

Description: R8: 0013. AE$UD1015. (UDLC): CONFIG READ ERROR ON STATION 


occurred in accessing the station information table. Telcon generates this CENLOG. 

7436 0728–303 14–1

Event 1 LINE CONNECTION (UNSUCCESSFUL) 

UDLCRS 

Description: R8: 0014. AE$UD106. (UDLC): CONFIG ERROR ON HLE TABLE - 

CHECK CONFIG/DISK. The line is connected physically, but an error occurred in 

accessing the high-level information table (HIT). The HIT table is the information 

table for a trunk or a TS. Telcon generates this CENLOG. 

UDLCRS 

Description: R8: 0015. AE$UD107. (UDLC): CONFIG ERROR ON PRCSR TABLE - 

CHECK CONFIG/DISK. The line is connected physically, but an error occurred in 

accessing the information table. Telcon generates this CENLOG. 

UDLCRS 

Description: R8: 0042. AE$UDX66. (UDLC): UNABLE TO ACCESS AN HCB TABLE. 


UDLCRS 

Description: R8: 0043 AE$UDX67. (UDLC): UNABLE TO ACCESS AN SCE TABLE. 


UDLCRS 

Description: R8: 0044 AE$UDX65. (UDLC). CONFIG READ ERROR ON DLCUNIT 

TABLE. CHECK CONFIG/DISK. The line is physically connected, but an error 

occurred in accessing the DLCUNIT information table. Telcon generates this 

CENLOG. 

14–2 7436 0728–303

Event 2 LINE DISCONNECTION (ABNORMAL) 


LINE DISCONNECTION (ABNORMAL) 

Description: An unexpected line disconnection has occurred. These abnormal line 

disconnections typically occur on direct connect lines that are not usually 

disconnected for any reason. Telcon generates this CENLOG. 

Action: Check applicable line hardware and repair or replace as necessary. These 

checks should include the line cable connection to the DCP, the line cable itself, the 

modem, direct connect module (DCM) or terminal (if the terminal is direct connect), 

and all other intermediate hardware between the DCP and the source of the data-setready 

(DSR) signal. 

FCS Error 


module in PDNSVS received an unrecoverable line-error notification. The line module 

could not validate the frame’s frame-check sequence (FCS). This event could include 


R8: CNMS unrecoverable line-error reason code 



(LCB) address may be in Register R11. The X.25 PSCS program product generates this 

CENLOG. 


Full Input Queue to Level 3 


module in PDNSVS received an unrecoverable line-error notification. The port 

processor is unable to send the frame received from the network to the layer 3 module 

(or the multi-link module). The module’s input queue is full. This event could include 






CENLOG. 


7436 0728–303 14–3


Input Limit 



processor has detected that the input limit has been reached. This event could include 






CENLOG. 


Invalid Chain Status (Output/Input) 



detected an invalid chain status after output or input. This event includes the LINE 

name. 





CENLOG. 


Loss of Carrier 



detected a loss of the carrier signal. This event could include the LINE name. 





CENLOG. 


14–4 7436 0728–303

Loss of DSR (Output/Input) 




detected a loss of the data-set-ready (DSR) signal. This event could include the LINE 

name. 





CENLOG. 


Maximum Underruns 



processor exceeded the maximum number of underruns. This event includes the 

LINE name. 





CENLOG. 


N2xT1 Retries 



processor sent a frame to the network “N2” times while waiting a period of “T1” 

milliseconds between resending the frame. The number of retries and the period of 

time are configured on the X25DEF statement’s N2 and T1 parameters, respectively. 

This event could include the LINE name. 





CENLOG. 


7436 0728–303 14–5


PDNSVS 


module in PDNSVS received an unrecoverable line-error notification. The reason code 

is unknown (not documented by CNMS). This event could include the LINE name. 

R8: Unrecoverable line-error reason code 




CENLOG. 


Received “frame type” in ITS 



processor received a particular frame type while in the information transfer state. In 

some cases, the frame type is a protocol violation; in other cases, the frame type 

causes a procedural termination of the information transfer state. The possible frame 

types include the following: FRMR, SABM, DM, DISC, and unsolicited UA, and any 

response frame containing an unsolicited F–bit. Also note that in some parameter 

definitions of the network type (see the X25DEF statement’s NETWORK parameter), 

one or more of these frame types does not cause an unrecoverable line-error 

notification. Network parameter definitions are configured by the X25DEF 

statement’s L2OPT parameter, or those values defined for a particular network type. 

This event could include the LINE name. 





CENLOG. 


14–6 7436 0728–303

Resilient Line is Standby 




processor detected the line as dormant. A resilient line is configured to be active or 

standby. If an active line fails, or is configured as standby, then it becomes dormant 

and its standby becomes active. This event could include the LINE name. 


R10 : PDNGRP STE index 



CENLOG. 


Sent FRMR in ITS 



processor sent a frame-reject frame while in the information transfer state. Note that 

in some parameter definitions of a network type (see the X25DEF statement’s 

NETWORK parameter), the FRMR frame does not cause an unrecoverable line-error 

notification. Network parameter definitions are configured by the X25DEF 

statement’s L2OPT parameter, or those values defined for a particular network 

identifier. This event could include the LINE name. 





CENLOG. 


7436 0728–303 14–7


Timeout, Idle Channel (T3) 



processor’s T3 timer expired. This timer value is configured on the X25DEF 

statement’s T3 parameter. This event could include the LINE name. 





CENLOG. 


Timeout, Message Timer (Output) 



processor’s message response timer expired. This event could include the LINE 

name. 





CENLOG. 


UDLCRS 

Description: R8: 0019. AE$UD144. (UDLC): OUTPUT RESPONSE TIMEOUT. The 

start data transfer chain completion status includes output response timer expiration. 

The PP chains are halted, and the line is disconnected. 


UDLCRS 

Description: R8: 001A. AE$UD146. (UDLC): MESSAGE TIMER TIMEOUT. The start 

data transfer chain completion status includes output message timer expiration. The 

line is disconnected. 


14–8 7436 0728–303

UDLCRS 


Description: R8: 000C. AE$UD140. (UDLC): LOSS OF DSR. The start data transfer 

chain completion status includes DSR off. The line is disconnected. 


UDLCRS 

Description: R8: 000D. AE$UD142. (UDLC): LOSS OF CARRIER. The start data 

transfer chain completion status includes carrier off. The line is disconnected. 


UDLCRS 

Description: R8: 001B. AE$UD148. (UDLC): INVALID CHAIN STATUS. The start 

data transfer chain completion status is invalid. The line is disconnected. 


UDLCRS 

Description: R8: 0031. AE$UD180. (UDLC): MAX OVERRUNS. The start data 

transfer (SDT) chain completion status includes overrun. This is the last allowed 

overrun for the port in a series of overruns. The line is disconnected. 


UDLCRS 

Description: R8: 0032. AE$UD181. (UDLC): MAX UNDERRUNS. The start data 

transfer (SDT) chain completion status includes underrun. This is the last allowed 

underrun for the port in a series of underruns. The line is disconnected. 


UDLCRS 

Description: R8: 0033. AE$UD131. (UDLC): BACKUP DROPPED. A dedicated line 

to a host TS connected while this switched backup line was active. The switched 

backup line was disconnected intentionally. 


7436 0728–303 14–9


UDLCRS 

Description: R8: 0034. AE$UD150. (UDLC): INPUT LIMIT. The start data transfer 

(SDT) chain completion status includes input limit. The line is disconnected. 


UDLCRS 

Description: R8: 0035. AE$UD158. (UDLC): PP SPECIFICATION ERROR. The PP is 

halted because of a PP specification error or a PP hardware error. The line is 

disconnected. 


UDLCSVS 

Description: RCM/LSM was multidropped off a trunk line. The trunk line was not 

active when an LSM/RCM command was issued. Telcon generates this CENLOG. 

14–10 7436 0728–303

Event 3 AUTO-DIAL FAILURE 

AUTO–DIAL FAILURE 

Event 3 AUTO-DIAL FAILURE 

Description: Auto dial-out attempt was unsuccessful. Telcon generates this 

CENLOG. 

Action: Check applicable hardware and all connecting hardware (cables) and repair 

or replace as necessary. If hardware is operational, check configuration information 

(such as the dial-out phone number) and verify that the line is configured for dial-out. 

7436 0728–303 14–11

Event 4 ADRD FAILURE 

Event 4 ADRD FAILURE 

ADRD FAILURE 

Description: An unsuccessful Auto Data Rate Detection (ADRD) attempt was made. 

This error is reported when a hardware error (indication of a failed ADRD attempt) is 

detected on a disconnected TTY line that is configured for ADRD. Telcon generates 

this CENLOG. 

Action: This CENLOG is informative only and can occur legitimately until the correct 

data rate has been detected. If the data rate can never be correctly identified, check 

and repair the applicable hardware (DCP line module or terminal). 

ALPMCP 

Description: This event occurs when the line module detects an error. The 

supplemental message indicates whether it occurred on input or output. The 

hardware status is shown in the DEVICE-ID field of the short-display, and in R15 of 

the long display. A high frequency of these events indicates a problem (hardware, 

configuration, operational, or device) that should be corrected. This event occurs 

only when the error is detected while ADRD is being performed. Telcon generates 

this CENLOG. 

TTYLPH 

Description: This event occurs when the line module detects an error during ADRD 

processing. The source of the error could be hardware, configuration, or operational 

procedure (wrong ADRD character typed). The status-flags should be examined to 

determine the error source, and the cause of the error should be corrected. This is 

considered a recoverable error. Other information logged: 

R7: MCT status bits from IOP 

R8: Transfer-count (from last SDT to/from this message) 

R14: Line ID 

R15: Status-flags (from SDT) 


14–12 7436 0728–303

Event 5 NO POLL GROUP FOUND 

NO POLL GROUP FOUND 

Event 5 NO POLL GROUP FOUND 

Description: Input has been received from a UNISCOPE ® 

terminal that has an invalid 

RID for this line. Telcon generates this CENLOG. 

Action: This error is caused by a terminal responding to a poll with a RID other than 

its own. Take the terminal offline for repairs. 

INVALID RID RECEIVED FROM UNISCOPE TERMINAL 

Description: Input has been received from a terminal that has an invalid RID (that is, 

belongs to a poll group that is invalid for this line). Because a valid poll group cannot 

be found, R12 does not contain a valid TCB address. R8 contains the value of 00E5. 

UNILPH generates this CENLOG. For more information on UNILPH CENLOG entry 

descriptions, refer to Section 1 of this manual. 

Action: This error is caused by a terminal responding to a poll with a RID other than 

its own. Take the terminal offline and repair it. If this error occurs often enough to 

create intolerable overhead to the system, you can issue an NMS STOP command for 

the line to which the terminal is connected. When the terminal has been taken offline, 

issue an NMS STRT command for the line to restore normal operation. 

7436 0728–303 14–13



No CENLOGs have been defined for Events 6 and 7. 

14–14 7436 0728–303

Event 8 ABNORMAL LINE TERMINATION FUNCTION 


ABNORMAL LINE TERMINATION FUNCTION 

Description: The line has been either brought down, reinitialized, terminated due to 

error conditions, or a state item has been posted unexpectedly. Telcon generates this 

CENLOG. 

Action: If this CENLOG display was generated as a result of previous NMS 

operations, it is informational only. Check and correct the hardware condition of the 

line. 

BSC LPH 

Description: Generated when the maximum retry count is exceeded for recoverable 

line errors. 

R8: Contains the flag word for the LPH. The meaning of each bit is in the 

AAHARDEF assembly. 

R11: Contains the LCB address 

R12: Contains the TCB address 

R14: Contains the IOP ID 

R15: Contains a code indicating the type of line error, as follows: 

0 Incorrect response to a line bid. 

1 The ACK response block count is incorrect. 

2 A NAK was received to an output text. 

3 A bad ACK block count was sent to the terminal, or text was distorted on 

the line. 

4 Bad input was received from the terminal. 

5 No response condition. 

011 Handler unable to queue an ack. 


7436 0728–303 14–15


NTRLPH 

Description: This event occurs if an NTR site is terminated abnormally. The 

supplemental message identifies the source of the abnormal termination. The NTR 

site is signed off, with any active output files being requeued. If any input device is 

active when this occurs, all of the input file is discarded. The LINE/SITE DOWNED, or 

RE-SIGNON case need not be investigated further. The FATAL INPUT/OUTPUT 

ERROR case should be investigated for a possible hardware problem, as should the 

MAX OUTPUT RETRY case. The NO RESPONSE or NAK-SEQ OVERFLOW cases 

indicate that the DCP cannot communicate with the remote site either because of a 

hardware problem, or because the remote site has crashed or has hardware problems 

of its own. The NAK-LOOP case indicates that the same message is being affected by 

NAK, but the recovery process is working without any hardware error. This is usually 

caused by a configuration error (wrong buffer sizes), or a protocol handling error in 

the software. Any preceding recoverable error CENLOGs should also be examined for 

any of these cases. Other information logged: 

R9: Nak-1 detail code 

01 Message too long 

02 Message too short 

03 Input message timeout 

04 Message-number sequence error 

05 Response time-out (idle-site handshake) 

07 Parity/LRC error 

08 First character not SON or S 

R10: 

0A Input overrun/output underrun 

0C No buffer for input 

0D Too many inputs without ACKing outstanding output 

0E Wrong FDX/HDX sign on for line configuration 

The active device counts word (NS$ADC) from the SCT 

R12: The NS$STAT1 flag word from the SCT 

R13: The NS$STAT2 flag word from the SCT. All NS$ equates are defined in 

AANTRDEF. 


14–16 7436 0728–303


PP STATE ITEM RECEIVED (UNISCOPE) 

Description: A PP state item has been posted for a serial UNISCOPE line. Other 

information is as follows: 

R8: PP instruction address where error occurred (PAO) 

R9: Error type 

R10: Error subtype 

R12–R13: Real-time clock value at the time of the CENLOG 

R14: Port ID of the port posting the state item 

The port is left in the same state as when the error occurred to allow further online 

investigation. A copy of the state item is saved (as a result of system state-item 

processing for further analysis when a system dump is taken, regardless of any online 

analysis). The state item and LCB are also shown if the long format of the CENLOG 

display is retrieved. 

The long format of the CENLOG for 4x1 lines displays part of the fixed space instead 

of the stated item. 

It should be noted that because the line is left in the state it was in when the error 

occurred, an NMS STAT command may indicate that the line is still up, but 

inoperative. This CENLOG is generated by UNILPH. For more information on 

UNILPH CENLOG entry descriptions, refer to Section 1 of this manual. 

Action: To reestablish an operational environment for the line, you will have to 

execute the NMS DOWN and UP commands for that line. See the DCP Series 

Communications Processor Architecture Programming Reference Manual (7431 

5805) for a description of the error type/error subtypes and their possible causes. 

TTYLPH 

Description: This event occurs after the maximum unsuccessful retries of a 

recoverable line-error. The supplementary message on the CENLOG tells whether it 

was an input or an output message. If this event occurs, the line is disconnected (and 

the terminals, if any) are signed off. The preceding CENLOGs for the recoverable 

errors should be examined to determine the source (hardware, configuration, or 

device) of the error so that corrective action can be taken. No additional information 

is logged. Telcon generates this CENLOG. 

7436 0728–303 14–17




14–18 7436 0728–303

Event 10 UNRECOVERABLE TERMINAL/DEVICE ERROR 

Event 10 UNRECOVERABLE TERMINAL/DEVICE 

ERROR 

UNRECOVERABLE TERMINAL/DEVICE ERROR 

Description: This CENLOG display is generated when the device error is so severe 

that recovery is impossible, or all reasonable attempts at recovery have failed. Telcon 


Action: Check the device hardware and repair or replace. 

BSC Output VTR 

Description: Failed to locate the proper TCB. 






R13: Error code from which the relative value within the program from which the 

error occurred may be located 

R13: 033 



PP Crash 


module in PDNSVS received a port processor (PP) crash indication. This event could 

include the LINE name. 

R8: Unrecoverable line-error reason code 




CENLOG. 


7436 0728–303 14–19




14–20 7436 0728–303


Supplementary Messages for Class, 14, Event 16 


SNA: 1008 - ACTPU failed, sense code = %%%% %%%% 


attached to SNA/net. Where sense code refers to IBM sense codes found in Appendix 

D of this manual and % represents a hexadecimal number. It is informational only. 

SNA: 1009 - ACTLU failed, sense code = %%%% %%%% 


attached to SNA/net. Where sense code refers to IBM sense codes found in Appendix 

D of this manual and % represents a hexadecimal number. It is informational only. 

SNA: 2427 - ACTLU failed, sense code=%%%% %%%% 



NT 2.1 devices. Where sense code refers to IBM sense codes found in Appendix D of 

this manual and % represents a hexadecimal number. It is informational only. 

SNA: 2428 - ACTPU failed, sense code=%%%% %%%% 



NT 2.1 devices. Where sense code refers to IBM sense codes found in Appendix D of 

this manual and % represents a hexadecimal number. It is informational only. 

7436 0728–303 14–21


14–22 7436 0728–303

Section 15 


CENLOGs in Class 15 result from recoverable communication line errors. 

Event 1 HARDWARE LINE ERROR (NOT A PP STATE 

ITEM) 

HARDWARE LINE ERROR (NOT A PP STATE ITEM) 

Description: A hardware error has been detected on the line indicated by the 

CENLOG display. Telcon generates this CENLOG. 

Action: If the errors are infrequent on a given line, this CENLOG display is 

informative only. If the errors on the line are occurring frequently, repair the line 

hardware. To determine the repair to the line hardware, you may need to retrieve the 

long form of the CENLOG display using the NMS LOGI command. 

ALPMCP 


supplemental message indicates whether it occurred on input or output. The 

hardware status is shown in the DEVICE–ID field of the short display, and in R15 of 

the long display. A high frequency of these events indicates a problem (hardware, 

configuration, operational, or device) that should be corrected. Telcon generates this 

CENLOG. 

CARRIER OFF (UNISCOPE) 

Description: This status bit is set when the carrier signal has dropped or is no longer 

received by the line module during input. R8 contains the value 0080 or 0081 (bit 7 

set). This CENLOG is generated by UNILPH. For more information on UNILPH 

CENLOG entry descriptions, refer to Section 1 of this manual. 

Action: Check modem, DCM, cluster controller, or terminal, and repair as necessary. 

The carrier-off condition is treated as an error only for synchronous lines. If logging 

this error should cause undue overhead to the system, you can issue an NMS STOP 

command for the line, poll group, or terminal, as applicable. When the source of the 

problem has been fixed or taken offline, issue an NMS STRT command to restore the 

normal operating environment. 

7436 0728–303 15–1

Event 1 HARDWARE LINE ERROR (NOT A PP STATE ITEM) 

NTRLPH 

Description: This event occurs when line module/CLC detects a hardware error. 

The supplemental message tells what type of error was detected. Except for the MAX 

OUTPUT RETRIES case, these errors are considered to be recoverable. If any of 

these errors start to occur quite often, the cause should be investigated and corrected. 

Other information logged: 

R8: Status flags (from SDT) 

R9: NAK–1 detail code 



03 Input message time-out 


05 Response-timeout (idle-site handshake) 


08 1st character not OSH or G 

R13: 



0D Too many inputs without acknowledging outstanding output 

0E Wrong FDX/HDX sign-on for line configuration 

Least significant byte of transfer count 44 

R14: PPID 

No other information is logged. Telcon generates this CENLOG. 

TTYLPH 


supplemental message with this logged event indicates whether the error was on 

output or input. A high frequency of these events indicates a problem (hardware, 

configuration, or device) that should be corrected. These are considered to be 

recoverable errors. Other information logged: 

R7: MCT status bits from IOP 

R8: Transfer-count (from last SDT to/from this message) 

R14: Line-ID 

R15: Status flags (from SDT). For more information about UNISCOPE line errors 

using Class 15, refer to Section 1 of this manual. 

15–2 7436 0728–303


Supplementary Message For Class 15, Event 01 

DATA OVERRUN (UNISCOPE) 

Description: This status bit is set when the communication line handler (CLC) is 

unable to keep up with the required input data rate. R8 contains the value of 0040 or 

0041 (bit 6 is set). Telcon generates this CENLOG. 

Action: Several actions can be considered for this error. First, determine if the line 

module being used is capable of operating at the baud rate of the line. If that appears 

to be in order, consider the priority of the port. The guideline is that the lower the 

port number within a CLC, the higher the priority that port is given by the CLC. Many 

times, you can solve the problem by rearranging the line modules so that UNISCOPE 

line modules reside in the higher priority ports. If that doesn’t work, the CLC may be 

overloaded and you should consider reducing the number of lines on the CLC. If this 

is not acceptable, reduce the line speed so that the CLC can keep up with the input 

data rate. For more information, refer to the DCP Series Communications Processor 

Architecture Programming Reference Manual (7431 5805). 

If logging this error causes undesirable overhead to the system, you can issue an NMS 

DOWN command for the line on which the error is occurring. When the source of the 

error has been found and corrected, you can issue an NMS UP command to restore 

the line to a normal operating state. 

MESSAGE TIMER EXPIRATION (UNISCOPE) 

Description: This status bit is set if the message timer expires. The message timer is 

started when the first character is successfully received from, or sent to, the terminal. 

If this timer expires, it indicates that the message did not complete and that the 

terminal is malfunctioning. R8 contains the value of 0400 or 0401 (bit 10 is set). 


Action: If this error occurs often, take the terminal in question offline and check and 

repair as necessary. If logging this error should cause intolerable overhead to the 

system, issue an NMS DOWN command for the terminal. When the terminal has been 

repaired and brought back online, you will have to issue an NMS UP command before 

the terminal can return to the network. 

7436 0728–303 15–3


UNISCOPE MESSAGE ERROR (PARITY ERROR) 

Description: VRC or LRC (parity check) error is detected. Can be caused by faulty 

line hardware, terminal hardware, or intolerable electrical noise on the line. R8 

contains 0100 or 0101 (bit 8 is set). UNILPH generates this CENLOG. For more 

information on UNILPH CENLOG entry descriptions, refer to Section 1 of this manual. 

Action: If this error occurs for many terminals on the same line, check and repair the 

line hardware and its electrical environment (including cables, modems, DCMs, and 

multiplexers). 

If this error occurs for only one terminal, or only for terminals connected to the same 

cluster controller, check and repair the terminal or cluster. 

If this error occurs often enough to cause undue overhead to the system, you can 

issue an NMS STOP command for the line, poll group, or terminal, as applicable. 

When the offending hardware has been fixed or taken offline, issue an NMS STRT 

command to restore a normal operating environment. 

UNISCOPE PORT PROCESSOR ERROR (HUNG PP) 

Description: Port processor error (hung IOP). This error is detected when the LPH 

has requested a response from the IOP and the IOP fails to respond within a 

reasonable amount of time. This condition generally occurs when the line module 

hangs or is faulty. When this condition is discovered, the LPH forces a state item to 

get to a known state on that port. At that point, system state processing is invoked 

(see PP STATE ITEM error description). R8 contains the value 00E8. Telcon 


Action: Wait for state-item processing to be completed and reported, and proceed 

accordingly (see description for PP STATE ITEM RECEIVED). 

15–4 7436 0728–303

Event 2 COMMUNICATIONS LINE PROTOCOL ERROR DETECTED 

Event 2 COMMUNICATIONS LINE PROTOCOL 

ERROR DETECTED 

COMMUNICATION LINE PROTOCOL ERROR DETECTED 

Description: A line protocol error has been detected on the line indicated by the 

CENL display. Telcon generates this CENLOG. 

Action: Information only. If errors occur frequently for a given line, you may need to 

correct the problem. 

BSC LPH 

Description: Indicates a first call for BSC line errors. 

R8: Contains the flag word for the LPH. The meaning of each bit can be found in 

the AAHARDEF assembly. 




R15: Contains a code indicating the type of line error as follows: 

0 Incorrect response to a line bid 

1 The ACK response block count is incorrect 

2 A NAK was received to an output text 

3 A bad ACK block count was sent to the terminal or a text was hit on the 

line 

4 Bad input was received from the terminal 


7436 0728–303 15–5


BSC LPH 

Description: Indicates an intermediate call for BSC line errors. 

R8: Contains the flag word for the LPH. The meaning of each bit can be found in 

the AAHARDEF assembly. 




R15: Contains a code indicating the type of line error 

0 An incorrect response to a line bid 

1 The ACK response block count is incorrect 

2 A NAK was received to an output text 

3 A bad ACK block count was sent to the terminal or a text was hit on the 

line 

4 Bad input was received from the terminal 

5 No response from remote terminal or DLC character not identified 


BVOUTPUT 

Description: An attempt was made to insert data into an output buffer, but the space 

was exhausted. Probable software error. 






R13: Error code denoting the relative position within the program in which the 

error occurred 


15–6 7436 0728–303

NTRLPH 


Description: This event occurs if the NTR PP program (NTRIOP) detects a line 

protocol error. A supplemental message specifies what type of error was detected. 

Recovery is initiated as per NTR/FDR protocol. This indicates a possible 

configuration, software, or hardware error. Other information logged: 

R8: status-flags (from SDT) 

R9: NAK–1 detail code 



03 Input message time-out 


05 Response-time-out (idle-site handshake) 


08 1st character not SOH or G 

R13: 



0D Too many inputs without acknowledging outstanding output 

0E Wrong FDX/HDX sign-on for line configuration 

Least significant byte of transfer count 

R14: PP ID 


NTRV2R 

Description: This event occurs if NTRV2R detects a line protocol error. A 

supplemental message specifies what type of error was detected. Recovery is 

initiated as per NTR/FDR protocol. This indicates a possible configuration, software, 

or hardware error. Other information logged (for BAD CONTROL case): 

R15: The device number the bad control message was for. 


7436 0728–303 15–7


REPLY REQUEST ERROR (UNISCOPE) 

Description: This is a recoverable line protocol error that is generally caused by 

faulty line or terminal hardware, or unacceptable electrical noise on the line. R8 

contains the value 00E6. UNILPH generates this CENLOG. For more information on 



line hardware and its electrical environment (including cables, modems, DCMs, 




If this error occurs often enough to cause undue overhead to the system, issue an 

NMS STOP command for the line, poll group, or terminal as applicable. When the 

malfunctioning hardware has been taken offline, issue an NMS STRT command to 

restore a normal operating environment. 

RMLPH 

Description: I/O failure due to hardware detected error. 

R15: IOP ID 


RMLPH 

Description: The terminal has sent a retransmit character and the data buffer should 

be retransmitted. 

R14: IOP ID 


UDLCRS 

Description: An F bit was received even though a P bit was not out. The input frame 

is ignored, R8 = 001D. Telcon generates this CENLOG. 

UDLCRS 

Description: A non-XID frame was received during the XID exchange phase of UDLC 

line connection. The frame is discarded–an XID frame is still expected, R8 = 003E. 


15–8 7436 0728–303



ABORTED FRAME 


module in PDNSVS received a recoverable line-error notification. The reason is 

because the line module received an aborted frame. This event includes the LINE 

name. 

R8: CNMS recoverable line-error reason code 





FCS ERROR 



because the line module could not validate the input frame’s frame-check sequence 

(FCS). This event includes the LINE name. 






INVALID HEADER RECEIVED 

Description: At terminal sign on an invalid header is received by UNILPH; input is 

discarded. 

R8: 00E1 

R15: RID/SID 



Action: Caused by invalid SID. Correct at the UTS control page. 

7436 0728–303 15–9


OVERRUN 



because an overrun chain status occurred during input. This event includes the LINE 

name. 






RESPONSE TIMER EXPIRATION (UNISCOPE) 

Description: This status bit is set if the response timer expires. The response timer 

is started as soon as the data transfer is initiated, and is terminated without error 

when the line module becomes synchronized with the line. If this timer expires, it 

indicates that the data transfer never got started and that the terminals are either 

malfunctioning or not connected to the UNISCOPE line. R8 contains the value 0800 or 

0801 (bit 11 will be set). This CENLOG is generated by UNILPH. For more 


Action: If these errors occur for many terminals on the same line, check and repair 

the line hardware and its electrical environment (including cables, modems, DCMs, 

and multiplexers). 

If these errors occur for only one terminal, or only for terminals connected to the 

same cluster controller, check and repair the terminal or cluster. 

If none of the above actions correct the problem, you must increase the response 

timer value to accommodate any onsite timing differences that may be occurring. 

This is done using the LCLASS RSPTIMER parameter at system generation time. 

If these errors occur often enough to cause undue overhead to the system, you can 

issue an NMS DOWN command for the line, poll group, or terminal as applicable. 

When the malfunctioning hardware has been taken offline, issue an NMS UP 


15–10 7436 0728–303


TIMEOUT, INPUT MESSAGE TIMER 



because the port processor’s input response timer expired. This event includes the 

LINE name. 






TIMEOUT, OUTPUT RESPONSE 



because the port processor’s output response timer expired. This event includes the 

LINE name. 






UNDERRUN 



because an underrun chain status occurred during output. This event includes the 

LINE name. 






7436 0728–303 15–11


UNISCOPE TERMINAL IS DATA STREAMING 

Description: Terminal is data streaming. This is a line protocol rule violation in 

which the terminal is sending input text in response to the acknowledgment of a 

previous input text. R8 contains the value of 00E4. UNILPH generates this CENLOG. 

For more information on UNILPH CENLOG entry descriptions, refer to Section 1 of 

this manual. 

Action: If the error occurs often, take the terminal offline and check and repair. If 

logging this error is creating intolerable overhead to the system and the terminal is 

signed on, you can issue an NMS STOP command for the offending terminal until it 

can be taken offline. When the terminal has been taken offline, issue an NMS STRT 

command to restore the normal operating environment of the line. 

UNRECOVERABLE LINE ERROR (UNISCOPE) 

Description: This error is logged when all error recovery attempts have failed and a 

general ACK is to be sent on the line in a final attempt to clear the error. This may 

result in the loss of data if the error sequence was initiated by input from a terminal. 



Action: Review the previous CENLOGs pertaining to this line and take the 

appropriate operator action according to the errors logged. 

15–12 7436 0728–303

Event 3 INPUT ERROR FROM DEVICE/TERMINAL 


INPUT ERROR FROM DEVICE/TERMINAL 

Description: An input error (such as bad input parity, invalid terminal response) has 

been detected. Telcon generates this CENLOG. 

Action: Information only, unless the frequency of errors on a given device indicate 

that you may need to repair or replace the device. 

ASYNC STATUS RECEIVED (UNISCOPE) 

Description: The async status bit is set if a break character (all zeroes with no stop 

bit) is detected, or when a space to mark transition is detected following a break 

character on async UNISCOPE lines. This status is treated as a recoverable error per 

UNISCOPE line protocol rules when the transfer of data is involved. R8 contains the 

value of 0020 or 0021 (bit 5 is set). UNILPH generates this CENLOG. For more 


Action: You must evaluate this status with respect to the hardware being used (both 

modems and terminals). In some cases, this status should never occur (for example, 

during data transfers) and repairs may be warranted. In other cases, this status may 

be a natural occurrence because of the hardware involved (for example, during line 

disconnection). 

If logging this error causes undesirable overhead to the system, you can issue an NMS 

STOP command for the line on which the error is occurring. When you have found 

and corrected the source of the error, issue an NMS STRT command to restore the 

line to a normal operating environment. 

PU100 

Description: A bad input has been received from the port processor. May be a 

hardware problem. 




7436 0728–303 15–13


RMLPH 

Description: Maximum retries on input buffer. 

R13: 0000—terminal sent a retransmit or an invalid control character. (See 

previous REM1 CENLOGs for which 8000—system is out of buffers.) 4000— 

terminal sent an invalid buffer of more than 331 characters. 0800—terminal 

did not respond within five seconds. 0400—terminal did not complete 

message within five seconds. 0100—A VRC or LRC error was detected. 

0040—line module unable to keep up with the required input message data 

rate. 

R14: PPID 

R15: Configuration STE of the terminal having the problem 


RMLPH 

Description: The control character received from the terminal was invalid. Request 

retransmission from terminal. 

R14: IOP ID 

R15: Terminal response 


Supplementary Messages for CLASS 15, EVENT 03 

INPUT LIMIT EXCEEDED (UNISCOPE) 

Description: The input limit status bit is set when more input is received than the 

input limit allows. The input limit is set at 4,096 bytes for terminals using the 

UNISCOPE line protocol and is sufficient for U100, U200, DCT1000, and all terminals 

of the UTS family. This error generally indicates that the terminal is streaming data. 

R8 contains the value of 4000 or 4001 (bit 14 will be set). UNILPH generates this 

CENLOG. For more information on UNILPH CENLOG entry descriptions, refer to 

Section 1 of this manual. 

Action: If this error occurs often enough to cause undue overhead to the system, you 

can issue an NMS STOP command for the terminal that is streaming data. When the 

malfunctioning hardware has been taken offline, issue an NMS STRT command to 

restore a normal operating environment. 

15–14 7436 0728–303


NO BUFFERS AVAILABLE FOR INPUT (UNISCOPE) 

Description: The no-buffer status bit is set when the CLC cannot allocate any zeroed 

input buffer space. This error indicates a system buffer pool problem. R8 contains 

the value of 8000 or 8001 (bit 15 will be set). UNILPH generates this CENLOG. 

UNILPH For more information on CENLOG entry descriptions, refer to Section 1 of 

this manual. 

Action: Review the system hardware and software configuration to determine what 

can be done to resolve the lack of buffer pool resources. 

SNA: 200 - TG=index#: DSR dropped 



a TG index number. The probable cause is a hardware problem. 

SNA: 201 - TG=index#: Carrier dropped 




SNA: 202 - TG=index#: Line idle 




SNA: 203 - TG=index#: Invalid chain status 




SNA: 204 - TG=index#: Response timer expired 




SNA: 205 - TG=index#: Message timer expired 




7436 0728–303 15–15


SNA: 206 - TG=index#: Over-run 




SNA: 207 - TG=index#: Message not used 

Description: This message is informational only. 

SNA: 208 - TG=index#: Frame checksum error 




SNA: 209 - TG=index#: Input limit 




SNA: 215 - TG=index#: Error threshold crossed 




SNA: 216 - TG=index#: Station permanently busy 




SNA: 217 - TG=index#: Output status = x%%%% 


Group Control (TGC) that controls lines between SNA/net and IBM subareas. Where 

X%%%% represents a hexadecimal number. The # is a TG index number. The probable 

cause is a hardware problem. 

SNA: 218 - TG=index#: Input status = x%%%% 


Group Control (TGC) that controls lines between SNA/net and IBM subareas. Where 

X%%%% represents a hexadecimal number. The # is a TG index number. The probable 

cause is a hardware problem. 

15–16 7436 0728–303

SNA: 219 - TG=index#: Station cleared 





SNA: 232 - TG=index#: Frame aborted 


Group Control (TGC) that controls lines between SNA/net and IBM subarea. The # is 


SNA: 251 - TG=index#: Unexpected XID received - Line cleared 




SNA: 1020 - Invalid TH on msg from device, discard 



7436 0728–303 15–17

Event 4 OUTPUT ERROR TO DEVICE/TERMINAL 


MISSING ACK ERROR (UNISCOPE) 

Description: This is a recoverable line protocol error that is generally caused by 

faulty line or terminal hardware or unacceptable electrical noise on the line. R8 

contains the value 00E7. UNILPH generates this CENLOG. For more information on 



line hardware and its electrical environment (including cables, modems, DCPs, and 




If this error occurs often enough to cause undue overhead to the system, you can 

issue an NMS STOP command for the line, poll group, or terminal, as applicable. 

When the malfunctioning hardware has been taken offline, issue an NMS STRT 


OUTPUT ERROR TO DEVICE/TERMINAL 

Description: An output error (such as invalid or no response to an output message) 

has been detected. Telcon generates this CENLOG. 

Action: Informational only, unless the frequency of the error for a given device 

implies that you may need to repair or replace the device. 

PDNPAD 

Description: The X.29 PAD handler in module PDNPAD was unable to successfully 

process a HIC received from the virtual terminal processor. This event includes the 

TERM name. 

R10: HIC received 

Attributes affected: Recoverable error event, Terminal Control Block (TCB) address 

is in register R12, Device event. The X.25 PSCS program product generates this 

CENLOG. 

Procedure: PDNPAD 

15–18 7436 0728–303

PU100 


Description: The maximum output retry count has been exceeded. Output is 

suspended until a successful input. 



R14: Queue service code 


RMLPH 

Description: Maximum retries on output buffer. 

R13: 0000–terminal sent a retransmit or an invalid control character. (See previous 

REM1 CENLOGs for which 0800–terminal did not respond within five 

seconds.) 0400–terminal did not complete message within five seconds. 

R14: PP ID 

R15: Configuration STE index of the terminal having the problem 


SNA: 220 TG=index#: DSR dropped 




SNA: 221 TG=index#: Invalid chain status 




SNA: 222 TG=index#: Response timer expired 




7436 0728–303 15–19


SNA: 223 TG=index#: Message timer expired 




SNA: 224 TG=index#: Under-run 




15–20 7436 0728–303

Event 5 POLL GROUP STATUS 

POLL GROUP STATUS 

Event 5 POLL GROUP STATUS 

Description: UNISCOPE poll group has entered slow poll. R15 contains the value of 

the RID for the poll group. Telcon generates this CENLOG. 

Action: Several actions are possible to correct the error. Check modem, cluster 

controller, or terminal, and repair as necessary. If the logging of the error should 

cause intolerable overhead to the system, an NMS DOWN PGRP command may be 

issued for the poll group. When the problem has been solved and the system brought 

back online, an NMS UP PGRP command will have to be issued. 


POLL GROUP IN SLOW POLL (UNISCOPE) 

Description: UNISCOPE poll group has entered slow poll. R15 contains the value of 

the RID for the poll group. Telcon generates this CENLOG. 

Action: See operator action under primary message. 

POLL GROUP IN FAST POLL (UNISCOPE) 

Description: UNISCOPE poll group has returned to fast poll. R15 contains the value 

of the RID of the poll group. Telcon generates this CENLOG. 

Action: See operator action under primary message. 

UNILPH 

Description: The poll group changes the state from FAST POLL to SLOW POLL or 

from SLOW POLL to FAST POLL. 

R11: LCB Address 

R15: RID for the poll group 


7436 0728–303 15–21




15–22 7436 0728–303

Event 7 TERMINAL/DEVICE PROTOCOL ERROR DETECTED 

Event 7 TERMINAL/DEVICE PROTOCOL ERROR 

DETECTED 

TERMINAL/DEVICE PROTOCOL ERROR DETECTED 

Description: A terminal or device has responded with an invalid response. Telcon 


Action: Informational only, unless this error occurs frequently enough for a specific 

terminal/device to warrant investigation for response. 

BVINPUT 

Description: This CENLOG is for transparency error traces. 

R0: Current characters moved in PDU 

R1: Count of PDU left 

R2: Offset into PDU buffer 

R6: Current character that BVINPUT receives transparent data and is not in 

transparent mode; or BVINPUT has not found the end-of-text character (R6 

not equal to 3) 


BVOUTPUT 

Description: A text message has an illegal RB2 HIC in it. This means that the 

BVOUTPUT cannot match the bad HIC with anything expected. 

R6: Bad RB2 HIC 

R13: 037: error code 

R14: Type of error encountered 


7436 0728–303 15–23


BVOUTPUT 

Description: The zone width is less than the record length. 






R13: Error code denoting the relative position within the program in which the 

error occurred. 

R13: 01, 0C, 0E 


DTVTR 

Description: The DCT 1000 VTR received a message from a device that has an 

invalid or unrecognizable DID. 


R14: PPID 

R15: RID/SID 


MISSING AUX DEVICE STATUS (UNISCOPE) 

Description: SNA/net message number 210. This error occurs when the terminal 

responds to a selection poll (specific DID) with something other than an auxiliary 

device status. The error may occur several times during a selection sequence. R8 

contains the value of 00E9. UNILPH generates this CENLOG. For more information 

on UNILPH CENLOG entry descriptions, refer to Section 1 of this manual. 

Action: If this error occurs often, check and repair the auxiliary interface in the 

terminal or cluster controller (if the terminal is a work station). If logging this error is 

creating intolerable overhead to the system and the terminal is signed on, you can 

issue an NMS STOP command for the malfunctioning terminal until it can be taken 

offline. When the terminal has been taken offline, issue an NMS STRT command for 

the terminal to restore the normal operating environment of the line. 

15–24 7436 0728–303

NTRLPH 


Description: This event occurs if the remote-site operator attempts to start up an 

input device when the line, device, or site has previously been stopped using an NMS 

command or from the host; that is, the session has stopped input. If this occurs, the 

remote operator’s initialize-device keyin/command is ignored. A supplemental 

message to the normal message explains this to the operator. Other information 

logged: 

R14: The PPID of the NTR line the site is using 

R15: The device number of the input device trying to start. All other registers are 

applicable to debug only. 


RMVTR 

Description: Either a deviation from the REM1 terminal protocol or an operator 

error was detected by the REM1 VTR. 






R14: The offending code or character 


RMVTR 

Description: RMVTR detected a deviation from Telcon interface requirements. 






R14: Varies 

R15: Varies 


SNA: 1007 Invalid msg from device 



7436 0728–303 15–25


TTYVTR 

Description: Used when an invalid DID is passed with the DID HIC to the TTYVTR. 



UDLCRS 

UVTR 

Description: A UA response to an operational mode-set command was received. 

The station required the extended control field; however, the pool of static modulo 

128-station queues was empty. Information transfer state could not be established, R8 

= 003F. Telcon generates this CENLOG. 

Description: UVTR detected an incomplete cursor or FCC sequence on an input 

from a terminal. 


R15: RID/SID of terminal 


15–26 7436 0728–303




7436 0728–303 15–27




SNA: 229 - Line cleared 


Group Control (TGC) that controls lines between SNA/net and IBM subareas. It is 


15–28 7436 0728–303

Section 16 


This section describes CENLOGs for Class 16. 

7436 0728–303 16–1



No CENLOGs have been defined for Events 1 through 15 

16–2 7436 0728–303




PPHNGMN= WARNING, LINE/PP LOOP OR HNG, STATE=000n 

Description: The PP may be looping or in a hung state for the input chain (when 

STATE=0001) or the output chain (when STATE=0002). 

Action: Enter the NMS DOWN command and then the NMS UP command for the 

port. If the status still persists, call your Unisys site administrator. 

SNA 1815: SNMS reserved 

Description: Reserved for future use. 

SNA 1816: SNMS reserved 

Description: Reserved for future use. 

7436 0728–303 16–3


16–4 7436 0728–303

Section 17 

NMS and DSA Messages 

This section describes: 

• Network management services (NMS) message types 

• How to obtain actions for messages displayed on an NMS console 

• What action to take when a message is displayed 

• Directory Services Agent (DSA) messages 

Introduction 

NMS uses console messages to keep you informed of errors, events, and other activities 

that may occur in the Telcon environment. These messages are particularly useful when 

you are using NMS commands. For information on NMS commands, refer to the Telcon 

Operations Reference Manual (7831 5728). 

This section defines console messages and command responses. Each message and 

response description contains the following components: 

• Description 

• Action, if applicable 

7436 0728–303 17–1


NMS Messages 

All the messages are alphabetized for easy reference. Table 17–1 classifies messages into 

particular message types. 

Table 17–1. Message Types Table 

Message Type Description 

Access Authority Messages relating to the types of console authority allowed 

in the network, passwords, and other security measures. 

CENLOG CENLOG messages report and record significant 

events/errors that occur in the Telcon environment. 

Communication Facility These messages are responses to NMS commands that 

affect various facilities in the network. Examples include the 

following: 

• Using the wrong RID 

• Bringing up a terminal when the cluster is down 

• Using the wrong facility name 

DCP Status Displays status information (messages) on the NMS console 

after you enter a STATUS command on a DCP. 

Dial-out Operation When a system session-open request is received from a 

host for a terminal that is attached to an inactive group, an 

attempt is made to establish the physical connection with 

the terminal through an auto or manual dial-out operation. 

An auto dial-out operation involves a second port processor, 

which is cabled to an automatic call unit connected to a 

local modem requiring a special line module to perform the 

dial function. This is performed through the hardware and 

software and requires no human intervention. For manual 

operation, you must perform the dial operation to the 

specified group of terminals from the local modem attached 

to the indicated port processor. The DCP always attempts 

to locate an auto-dial line first. If it fails to locate an autodial 

line, a manual dial-up operation is attempted. 

Disk These messages provide information relating to disk file 

manipulation; such as, cataloging or copying files. 

Facility Move A response message is displayed on the NMS console when 

an NMS MOVE command has been entered. 

Inspect/Change Response messages are displayed on the NMS console 

when an NMS INSP or CHNG command has been entered. 

Magnetic Tape Response messages relating to file manipulation on 

magnetic tape such as assigning, freeing, or canceling files, 

or reporting a file as empty. 

Miscellaneous Response messages displayed on the NMS console when 

various NMS commands are entered. 

17–2 7436 0728–303

Table 17–1. Message Types Table 

Message Type Description 


NMS Session These messages relate to the establishment and status of 

sessions in the network. 

Resiliency Messages acknowledging that a resiliency-type NMS 

command has been executed (solicited or automatic). 

Set Response messages are displayed on the NMS console 

when an NMS SET command has been entered. 

Statistics Statistics are collected by software and periodically written 

to disk. Two local mass storage disk files (PRSTAT and 

ALSTAT) are cataloged during system initialization phase. 

When local data collection has been configured, and either 

the primary or alternate file has been filled, a message 

appears signifying that the current statistics file is full. 

Storage Status Storage status information is displayed on the NMS console 

following the execution of the NMS command STOR. 

Syntax Analysis Error messages are displayed on the NMS console when an 

NMS command has been entered incorrectly. 

System Warning Warning messages are displayed on the NMS console when 

an abnormal status condition exists. 

Unsolicited Message Error Errors encountered in processing the USM result in the 

USMs being dropped and an error response being returned 

to the sending terminal. 

XFER Response messages are displayed on the NMS console 

when an NMS XFER command has been entered. 

When a message appears on your console, refer to the following alphabetical list to 

determine the action you should take. 

ALTERNATE DCP ID MUST BE SPECIFIED 

Description: Alternate Telcon node ID is not specified on ONLN or STBY command. 

Operator Action: Telcon is backed up by more than one Telcon. In this case, you 

must specify an alternate Telcon node ID indicating which pair is affected by the 

switch. 

* AUX DEVICE ERROR DETECTED * 

Description: An error occurred in accessing an auxiliary device. 

Operator Action: Check the auxiliary device conditions, such as paper out or unit 

offline. 

7436 0728–303 17–3


CATALOG COMPLETE 

Description: Execution of the CAT command has completed. 

CFIL SWITCH COMPLETE 

Description: The system is now using the new configuration file. 

CHANGE COMPLETE 

Description: The CHNG command has executed. 

CLASS=n LOGL=a LOGC=a DSPL=a DSPC=a 

Description: This is the response to the LOGD command. It displays the logging and 

display conditions. 

If... Then the condition indicates... 

LOGC is Y Central logging 

LOGL is Y Local logging 

DSPL is Y Display local logging 

DSPC is Y Display central logging 

CLUSTER(UP,DOWN),INPUT(STOPPED,ALLOWED) LINE GROUP: aaa 

TERMINAL(S): aaa aaa ... 

DEVICE(S): aaa aaa ... 

Description: The cluster is in the indicated state. 

COMMAND ACCEPTED 

Description: The command has been verified and accepted. Action to complete the 

execution of the command has been initiated. 

COMMAND COMPLETE 

Description: This is the response to the LOGC command. It indicates that the 

requested action is complete. 

COMMAND REJECTED: CRITICAL DEVICE FAILED 

Description: You are not able to perform a resilient command because a critical 

device has failed in this DCP. 

Action: Wait until DCP switch is completed. 

17–4 7436 0728–303

COMMAND REJECTED: SWITCH ALREADY IN PROGRESS 


Description: Previous SWT, ONLN, or STBY command has not been completed yet. 

Action: Wait for SWITCH COMPLETE message, and retry the command. 

DEVICE NAME... 

DEVICE NAME: aaa DEVICE TYPE: aaa 

DEVICE STATUS: aaa IOP NUMBER: a 

PPID NUMBER: n UNIT NUMBER: n 

VOLUME MOUNTED: n PAIRED DEVICE NAME: aaa 

Description: This is a STAT DEVICE command response. 

DIAL ON PORT XXX, DCP XXXXXXXX, PHONE # X...X 

Description: This is the manual dial-up message. 

Action: Perform a dial-out function on the port specified to the telephone number 

specified. 

Additional Information: When a system session open request is received from a 

host for a terminal that is attached to an inactive group, an attempt is made to 

establish the physical connection with the terminal using an auto or manual dial-out 

operation. An auto-dial operation involves a second port processor, which is cabled to 

an automatic call unit connected to a local modem. It requires a special line module 

to perform the dial function. The operation is performed with hardware and software 

and requires no human intervention. Manual dialing involves a Telcon node operator 

performing the dial operation to the specified group of terminals from the local 

modem attached to the indicated port processor. The Telcon node always attempts 

first to locate an auto-dial line; if it fails to locate one, it attempts a manual dial-up 

operation. 

This message and the one following are used to communicate with the Telcon node 

console operator during dial-out attempts. 

DIAL TIMEOUT ON PORT XXX, DCP XXXXXXXX. PLEASE PLACE 

PHONE ON HOOK 

Description: This is the manual dial-up message. 

Action: Place the phone on the hook to terminate the manual dial-out operation. 

7436 0728–303 17–5


DIRECTORY SERVICES NOT AVAILABLE 

Description: The DSA is down. 

Action: Start the DSA. 

DOWN DEVICE–COMPLETE 

Description: The DOWN command for a device has been executed. 

DOWN PDTE dte-id COMPLETED 

Description: The DOWN PDTE command was executed successfully. This is an X.25 

PSCS message. 

DOWN PDTE dte-id REJECTED 

Description: The DOWN PDTE command was rejected. This is an X.25 PSCS 

message. 

DOWN X.25 TRUNK trunk-id COMPLETED 

Description: The DOWN PTRK command was executed successfully. This is an X.25 

PSCS message. 

*** ERROR: ACCESS AUTHORITY REQUIRED *** 

Description: The command requires higher authority than the console possesses. 

Action: Verify the authority limit of the NMS console, and enter IDEN command if 

higher authority is required. 

*** ERROR: ADDRESS EXCEEDS FILE *** 

Description: An INSP or CHNG command address argument is too large. 

Action: Verify the address, and reenter the command. 

*** ERROR: ADDRESS EXCEEDS HIGHEST WRITTEN BLOCK *** 

Description: An INSP or CHNG command block argument is too large. 

Action: Verify the block number of the file, and reenter the command. 

17–6 7436 0728–303

*** ERROR: ADDRESS OUT OF BOUNDS *** 


Description: The address parameter value in the command statement is too large. 

Action: Verify the address, and reenter the command. If the problem persists, get 

assistance from a local Unisys systems analyst. 

*** ERROR: ALIGN VALUE INVALID *** 

Description: The CAT command ALGN parameter argument must be C or the 

statement unspecified. 

Action: Verify the ALGN parameter. 

*** ERROR: ATTEMPTING TO MOVE TO A SWITCHED LINE *** 

Description: The station facility move was requested. The TO parent is a switched 

line. The facility move was aborted. 

Action: Verify the TO port number, and reenter the MOVE command. 

*** ERROR: AUTHORITY VIOLATION *** 

Description: The console does not have enough authority to perform the command. 

Action: Verify the authority limit of the NMS console, and enter the IDEN command 

if higher authority is required. 

*** ERROR: BLOCK OUT OF FILE *** 

Description: An INSP or CHNG command block argument is too large. 

Action: Verify the block number of the file, and reenter the command. 

*** ERROR: CANNOT MOVE TO A RESTRICTED PORT *** 

Description: The TO port is the restricted port used by mass storage, parallel 

UNISCOPE, integrated flexible diskette controller, or host channel. 


7436 0728–303 17–7


*** ERROR: CANNOT MOVE TO AN INCOMPATIBLE LINE TYPE *** 

Description: The station facility move was requested. The line type of the TO parent 

(line or group) is a non-UDLC line. The facility move was aborted. 

Action: Verify the configuration for the TO port number, and reenter the MOVE 

command. 

*** ERROR: CATALOG ABORT, FATAL ERROR n *** 

Description: The CAT command was attempted, but aborted due to a fatal error. 

Action: Refer to the DCP/OS Operations Reference Manual (7831 5702) for an 

explanation. 

*** ERROR: CLUSTER IS DOWN *** 

Description: An UP terminal command is invalid if the terminal cluster is down. 

Action: Bring up the related cluster first, and reenter the command. 

*** ERROR: CLUSTER IS STOPPED *** 

Description: A STRT terminal command (input or output) is invalid if the 

corresponding state of the terminal cluster is stopped. 

Action: Use the STRT command to start the related cluster first, and reenter the 

command. 

*** ERROR: COMMAND NOT IMPLEMENTED *** 

Description: The command is defined, but not implemented. 

*** ERROR: COMMAND NOT SUPPORTED FOR THIS TERMINAL TYPE *** 

Description: This command is not applicable to this type of terminal. 

*** ERROR: CONFIGURATION ACCESS LOGICAL ERROR *** 

Description: The NMS software was unable to process a session look-up. 

Action: Check the TYPE parameter in NMS EU statement. 

17–8 7436 0728–303

*** ERROR: COPY ABORT, FATAL ERROR!-INPUT *** 

Description: A fatal disk error on a disk read has occurred. 


Action: See the DCP/OS Operations Reference Manual (7831 5702) for an 

explanation. 

*** ERROR: COPY ABORT, FATAL ERROR!-OUTPUT *** 

Description: A fatal disk error on a disk write has occurred. 

Action: See the DCP/OS Operations Reference Manual (7831 5702) for an 

explanation. 

*** ERROR: DCP VALUE NOT CONFIGURED *** 

Description: The desired Telcon node is not configured. 

Action: Verify the value. If the value is correct, seek configuration assistance. If the 

value is incorrect, enter the true value. 

*** ERROR: DELETE ABORT, FATAL ERROR n *** 

Description: The DEL command was attempted, but aborted due to a fatal error. If 

an error occurred while the user was attempting to delete the file’s data-set label, the 

catalog entry has been successfully deleted. 

Action: Refer to the DCP/OS Operations Reference Manual (7831 5702) for an 

explanation. 

*** ERROR: DESTINATION NOT CONFIGURED *** 

Description: The destination name requested cannot be found. 

Action: Check the configuration for EUs related to NMS. 

*** ERROR: DRIVE NOT READY OR WRITE PROTECTED *** 

Description: Ready the drive or remove the write protection. 

Action: Reenter the command. 

7436 0728–303 17–9


*** ERROR: DTYP VALUE INVALID *** 

Description: The parameter value can be only one of a few fixed-character strings 

(names). 

Action: Change the value, and reenter the command. 

*** ERROR: DUPLICATE FACILITY NAME *** 

Description: This is the response to the MOVE command when the facility being 

moved already exists on the destination Telcon node. 

Action: Verify the facility name, and reenter the MOVE command. 

*** ERROR: DUPLICATE FILE NAME *** 

Description: The specified file is already cataloged. 

Action: Change the file name, and reenter the command. 

*** ERROR: EXTERNAL COMMAND TEXT MISSING *** 

Description: The XCMD must be followed by a non-blank character string. 

Action: Verify the text, and reenter the command. 

*** ERROR: FACILITY NOT FOUND *** 

Description: The facility name is not defined according to the following: 

• Configuration 

• Directory services 

• Directory services is not available 

Action: 

• Verify the facility name. 

• If using directory services, verify that the DSA is running. 

*** ERROR: FACILITY MUST BE A TERM-LINE OR CLTR OR TERM *** 

Description: The LINE, CLTR, TERM, or STN facility specified on the MOVE 

command is not a terminal line, cluster, terminal, or station. 

Action: Verify the facility type and name, and reenter the MOVE command. 

17–10 7436 0728–303


*** ERROR: FACILITY/TO SPECIFICATION INCONSISTENT *** 

Description: The TO facility is not the correct type for the facility being moved. 

Action: Verify the TO facility name, and reenter the MOVE command. 

*** ERROR: FAILED TO ACCESS LCB/TCB *** 

Description: This message may appear during the execution of a LIST command. It 

indicates that the facility being referenced is down. 

*** ERROR: FILE NOT CATALOGED *** 

Description: The file name in the command statement is not cataloged. 

Action: Verify the name. If the name is correct, seek configuration assistance. If the 

name is incorrect, enter the true name. 

*** ERROR: FROM FACILITY NOT CONFIGURED *** 

Description: The FROM facility specified on the MOVE command is not configured. 


*** ERROR: FROM PARENT (LINE/GROUP) MUST BE IN DOWN STATE 

*** 

Description: A station facility move was requested. The station’s parent (line or 

group) is in the active state. The facility move was aborted. 

Action: Bring down the FROM line or group first, then reenter the MOVE command. 

$$ ERROR–ILLEGAL TYPE 

Description: This error message is generated when the USM receives a $$ command 

that is not recognized. 

Action: Verify the syntax, and reenter the $$ command. 

*** ERROR: INCORRECT FACILITY TYPE *** 

Description: The incorrect facility type was specified in the command statement. 

Action: Check the configuration for the correct facility name, and reenter the 

command. 

7436 0728–303 17–11


*** ERROR: INSPECT LENGTH EXCEEDED *** 

Description: The LENGTH parameter for the INSP command is too large. 

Action: Reenter it with a value of 128 or less. 

*** ERROR: INVALID PARAMETER ARGUMENT *** 

Description: The number used to specify a facility is out of range. This is an X.25 

PSCS message. 

*** ERROR: INVALID PARAMETER VALUE *** 

Description: The value associated with a parameter is not correct. 

Action: Check the command syntax, and reenter the command. 

*** ERROR: INVALID POLL GROUP NUMBER *** 

Description: The poll group remote identifier (RID) does not exist with the line 

specified in the command statement. 

Action: Check the configuration for the correct poll group RID, and reenter the 

command. 

*** ERROR: INVALID STANDBY DCP ID *** 

Description: The FOR parameter value in ONLN or STBY command should be a 

backup Telcon node. 

Action: Correct the value, and retry the command. 

*** ERROR: INVALID X.25 COMMAND *** 

Description: Input is not a valid X.25 command. This is an X.25 PSCS message. 

*** ERROR: IO VALUE INVALID *** 

Description: The I/O value is incorrect. 

Action: Change the appropriate value, and reenter the command. 

*** ERROR: KEYWORD NAME TOO LONG *** 

Description: The command keyword name is too long. 

Action: Make the appropriate change and reenter the command, or use HELP. 

17–12 7436 0728–303


*** ERROR: MODE REJECTED–ENTER END SENTINEL *** 

Description: Online communication mode cannot be entered. 

Action: Enter an end sentinel or a blank string to return to NMS mode. 

*** ERROR: MOVE ALREADY IN PROGRESS *** 

Description: A facility move is already in progress on the Telcon node. 

Action: Reenter the command later. 

*** ERROR: MOVE CANCEL ALREADY ACTIVE *** 

Description: This is the response to the CNCL command when the cancel move is 

already in progress on the Telcon node. 

Action: Wait for the active cancel to complete, and reenter the CNCL command. 

*** ERROR: MOVE FACILITY NOT CONFIGURED *** 

Description: The facility specified in the MOVE command is not configured. 


*** ERROR: MOVE FAILED–COULD NOT DOWN FACILITY *** 

Description: A facility move was aborted because of the inability to bring a resource 

down on the facility being moved. 

Action: If the problem persists, get help from a local Unisys systems analyst. 

*** ERROR: MOVE FAILED–FROM FACILITY CHAIN INVALID *** 

Description: The FROM facility resource chain is invalid and could not be corrected. 

The configuration is suspect. 

Action: Restore the configuration file from the host. 

*** ERROR: MOVE FAILED ON CONFIGURATION ACCESS *** 

Description: A facility move was aborted because of an error in accessing the 


Action: If the problem persists, restore the configuration file from the host. 

7436 0728–303 17–13


*** ERROR: MOVE FAILED ON RECOUP CHAIN *** 

Description: An unrecoverable error exists in the configuration of a facility being 

moved. The configuration is suspect. 


*** ERROR: MOVE FAILED ON SYSTEM ERROR *** 

Description: A facility move was aborted because of insufficient system resources to 

complete the move. 

Action: Reenter the MOVE command. 

*** ERROR: MOVE FAILED–TO FACILITY CHAIN INVALID *** 

Description: The TO facility resource chain is invalid and could not be corrected. 

The configuration is suspect. 


*** ERROR: NO CFIL ACTION TAKEN *** 

Description: The requested CFIL action cannot be performed. This problem has one 

of the following causes: 

• The specified file is not cataloged or is currently assigned to some other program 

in the DCP. 

• An active facility (such as a signed-on terminal, an LCLASS, a connected line) in 

the current configuration file has been deleted from the new configuration file, or 

does not exist by the same name in the new configuration file. 

Action: 

• Verify the file name and reenter the command. 

• Review the online configuration procedure and correct the problems. 

*** ERROR: NO FREE SPACE IN CONFIGURATION FILE–PACK AND 

EXPAND *** 

Description: No free space exists in the Telcon node configuration file for additional 

facility moves between Telcon nodes. 

Action: Pack and expand the configuration file to provide free space, offline. 

17–14 7436 0728–303

*** ERROR: NO GROUP ASSOCIATED WITH THE LINE *** 


Description: An attempt was made to bring up a poll group for a switched line. 

*** ERROR: NO HARDWARE LM AVAILABLE *** 

Description: The TO port hardware line module is not compatible with the line 

facility. 


*** ERROR: NO RECOVERY FILE. REENTER MOVE COMMAND *** 

Description: This is the response to the RCVR command when a system failure has 

occurred during a facility move, but a recovery file is not cataloged. 


*** ERROR: NO SESSION PATH AVAILABLE *** 

Description: No session path exists to the destination. 

Action: Configuration error. Notify systems analyst. 

*** ERROR: NO SPACE OR NO FREE DATA SET LABEL *** 

Description: No space or free data-set label is available on the volume or device 

type. 

Action: Change the volume, device type, or size, and reenter the command. 

*** ERROR: ON MULTIPLE DCP CONFIGURATION *** 

Description: A resilient command has taken place (solicited or automatic). 

*** ERROR: OUTPUT FILE SIZE TOO SMALL *** 

Description: The output file for a copy is too small. 

Action: Recatalog a larger output file, and retry. 

*** ERROR: PARAMETER VALUE MUST BE A NUMBER *** 

Description: An input parameter value is not a number. 

Action: Change the invalid parameter value, and reenter the command. Refer to the 

syntax definition of a number. 

7436 0728–303 17–15


*** ERROR: PARAMETER VALUE TOO LARGE *** 

Description: A parameter value is too large. 

Action: Decrease the parameter value, and reenter the command. If the problem 

persists, get help from a local Unisys systems analyst. 

*** ERROR: PARAMETER VALUE TOO LONG *** 

Description: A parameter value contains too many characters. 

Action: Correct its value and reenter the command, or use HELP. 

*** ERROR: PASSWORD INCORRECT *** 

Description: Privileged authority is not established. 

Action: Verify the password, and retry the command. 

*** ERROR: POLL GROUPS ONLY WITH UNISCOPE LINES *** 

Description: Poll groups are allocated only on UNISCOPE display terminal lines. 

Action: Check the configuration for the current line, and reenter the command. 

*** ERROR: PRIVILEGED AUTHORITY REQUIRED *** 

Description: The command requires privileged authority. 

Action: Use the IDEN command, if authorized. 

*** ERROR: READ ONLY FILE *** 

Description: The specified file is read-only and cannot be written to. 

*** ERROR: REQUIRED PARAMETERS MISSING *** 

Description: The required parameters are missing. 

Action: Include the missing parameter, and reenter the command, or use HELP. 

*** ERROR: SIZE NOT SPECIFIED *** 

Description: The SIZE parameter on a CAT command was omitted. 

Action: Reenter the CAT command, and specify the SIZE parameter. 

17–16 7436 0728–303

*** ERROR: STATION MUST BE IN DOWN STATE *** 


Description: A station facility move was requested on an active station. The facility 

move was aborted. 

Action: Bring the destination station down, and reenter the MOVE command. 

*** $$ ERROR–SYNTAX *** 

Description: This error occurs when there is an error in the syntax of the address of 

the receiving terminal and no address or message text follows the $$ command. 

Action: Check the syntax and reenter the $$MSG command. 

*** ERROR: SYNTAX ERROR *** 

Description: The syntax for one of the parameters is in error. 

Action: Correct and reenter the command, or use HELP. 

*** ERROR: TEXT COLOR MUST BE DIFFERENT FROM BACKGROUND 

COLOR *** 

Description: The TEXT command was used on the UTS 60, but the background color 

is the same as the color used for normal, error, warning, header, and CENLOGs. 

Action: Check the color attributes, and reenter the command. 

*** ERROR: TO FACILITY CURRENTLY HAS MAX NUM STATIONS *** 

Description: A station facility move was requested. The TO parent has the 

maximum number of stations attached to it. 

Action: Verify the TO facility name, and reenter the MOVE command. 

*** ERROR: TO FACILITY NOT CONFIGURED *** 

Description: The TO facility specified on the MOVE command is not configured. 


7436 0728–303 17–17


*** ERROR: UDLC LINE/STATION CANNOT BE MOVED BETWEEN 

DCPS *** 

Description: UDLC lines or stations can be moved within the same Telcon node 

only. 


*** ERROR: UNALLOWED PARAMETER FOUND *** 

Description: A parameter not defined for this command was entered. 

Action: Delete and reenter the command, or use HELP. 

*** ERROR: UNDEFINED COMMAND (USE HELP) *** 

Description: The command verb syntax is faulty. 

Action: Reenter the command correctly, or use HELP. 

*** ERROR: UNDEFINED COMMAND OR UNKNOWN FACILITY NAME 

*** 

Description: The command verb syntax is faulty or the facility name is not found. 

Action: Reenter the command name or facility name correctly. 

*** ERROR: UNDEFINED PARAMETER *** 

Description: The parameter name syntax is faulty. 

Action: Correct and reenter the command, or use HELP. 

*** ERROR: UNDEFINED TRACE TYPE *** 

Description: The TRON or TROF command argument is invalid. 

Action: Correct it, and retry the command. 

*** ERROR: UNKNOWN AUTHORITY *** 

Description: The AUTH parameter can only be GLOB, AREA, NODE, or REGN. 

Action: Check the AUTH parameter, and reenter the command. 

17–18 7436 0728–303

*** ERROR: UNKNOWN DEVICE NAME *** 


Description: An invalid device name was specified in the command statement. 

Action: Check the configuration for the correct device name, and reenter the 

command. 

*** ERROR: UNKNOWN FACILITY NAME *** 

Description: An invalid facility name was specified in the command statement. 

Action: Check the configuration for the correct facility name, and reenter the 

command. 

*** ERROR: UNKNOWN FILE NAME *** 

Description: The file is not cataloged. 

Action: Check the file name; correct and reenter the command. 

*** ERROR: UNKNOWN PROCEDURE/SEGMENT NAME *** 

Description: The procedure or segment name in the command statement is not in 

the PSEGTB# elements. 

Action: Verify the name, and retry the command. 

*** ERROR: UNKNOWN TERMINAL *** 

Description: The TERM parameter terminal name is not configured. 

Action: Check the terminal name, and retry the command. 

*** ERROR: LINE NAME IS REQUIRED FOR LINE ID *** 

Description: The UP LINE command using the line number is not allowed. 

Action: Check the configuration for the correct line name, and reenter the command. 

*** ERROR: VOL/DTYP PARAMETER MISSING *** 

Description: The volume or DTYP parameter must be supplied for this command. 

Action: Reenter the command, specifying the DTYP or DTYP parameter. 

7436 0728–303 17–19


*** ERROR: VOLUME NOT MOUNTED *** 

Description: The volume specified in a VOL statement argument is not mounted. 

Action: Mount the volume, and retry. 

*** ERROR: XTS VALUE NOT CONFIGURED *** 

Description: The external termination system specified is invalid. 

Action: Correct the value, and reenter the command. 

FACILITY MOVE (ACTIVE,FAILURE,CANCEL) 

FACILITY IS (LINE,CLUSTER,TERMINAL) 

MOVING FROM aaaaaaaa ON DCP # n 

MOVING TO aaaaaaaa ON DCP # n 

Description: A line, cluster, or terminal facility move is in the specified state. 

ACTIVE indicates that the move is in progress. FAILURE indicates a system failure 

during a facility move. CANCEL indicates that the facility move is being canceled 

(CNCL). 

Action: A recovery file is available and the facility move may be restarted by RCVR 

command or canceled by CNCL command. 

FACILITY MOVE CANCELLED–CONFIGURATION RESTORED 

Description: This is the response to the CNCL command when an active facility 

move has been canceled and the original state of the configuration has been restored. 

FACILITY MOVE COMPLETE 

Description: This is a response to the MOVE or RCVR command when a facility 

move has been successfully completed. 

FACILITY MOVE FAILURE–NO RECOVERY FILE 

Description: This is a response to the MOVS command when a system failure has 



17–20 7436 0728–303

FACILITY MOVE NOT ACTIVE 


Description: This is the response to the MOVS, RCVR, or CNCL commands when a 

facility move is not active. 


FILE ASSIGNED 

Description: The file name specified on a tape command exists. 

FILE CANCELLED 

Description: All tape requests for the file are aborted. 

FILE COPY COMPLETE 

Description: The COPY command has been successfully executed. 

FILE DELETION COMPLETE 

Description: The DEL command has executed. 

FILE EMPTY 

Description: The command could not be executed because the file is empty. 

Action: Verify the file name and retry. 

FILE EMPTY–NOTHING COPIED 

Description: The IFIL parameter argument of the copy command exists, but the file 

is empty. 

Action: Verify the file name and retry. 

FILE FREED 

Description: The file specified on a tape ASG command has been released. 

7436 0728–303 17–21


FILE NAME... 

FILE NAME: aaa , FILE SEQUENCE 

NUMBER: n NUMBER OF BLOCKS 

ALLOCATED n HIGHEST BLOCK 

WRITTEN n 

�� 

�� 

�� 

�� 

�� 

Description: This is a STAT file command response. 

FILE NOT FOUND 

Description: The file name specified on a tape command does not exist. 

Action: Verify the file name and retry the command. 

I/O ERROR ON aaa , FILE=aaa , CNCL or READY DRIVE 

Description: The tape drive is not ready. 

Action: Either cancel (CNCL) the previous tape ASG, or ready the tape drive. 

ILLEGAL USM TERMINAL TYPE 

Description: This error is generated when an attempt is made to send a USM to a 

terminal that is not a legal USM recipient. 

*** INPUT PARITY ERROR DETECTED *** 

Description: A parity error was detected while attempting to input a message on a 

device (such as a teletypewriter) that has no recovery procedure in its link protocol. 

Action: Check the line or terminal if this message displays frequently. 

VALID TAPE LABEL ON aaa , FILE= aaa , VOL=aaa 

Description: Mount an unlabeled tape. 

Action: Retry the command. 

17–22 7436 0728–303

*** LAST INPUT MESSAGE DISCARDED *** 


Description: This message informs the terminal operator that the system is unable to 

accept input because of resource conflicts; such as, buffer depletion. The input 

message is discarded, but may be reinitiated immediately. 

Action: Reenter the last input. 

LINE DOWN 

Description: The line is disabled and cannot be used. 

*** LINE xxxxxx INPUT STREAMING *** 

Description: This message informs the terminal operator that a hardware problem 

has been detected. A rapid flood of input over a UNISCOPE or teletypewriter (TTY) 

line alerts the handler of a problem. The TERMINAL STREAMING message appears 

when the terminal is known to CMS 1100 (that is, it is signed on and a device table 

exists for it); otherwise the more general LINE STREAMING message appears on the 

CMS 1100 host console. 

Action: When an input streaming condition is detected, the terminal handler attempts 

to synchronize input with another CMI$. If this is unsuccessful, the offending terminal 

should be brought down or powered off, and proper personnel notified. 

LINE LOGGING THRESHOLD CHANGE COMPLETE 

Description: This is a response to the STTH command. 

LINE UP... 

LINE UP, (DIS,____) CONNECTED,INPUT (STOPPED,ALLOWED), 

OUTPUT (STOPPED,ALLOWED), 

TYPE:(UNI,TTY,etc.), (n,NO)POLL GROUP(S), n TERMINAL(S) ACTIVE 

ERROR LOGGING THRESHOLD = (THRESHOLD VALUE) 

MODE = (ACTIVE,BACKUP) 

(This output appears only if line is resilient.) 

LINE (OPERATIVE, INOPERATIVE) 

Description: The line is enabled. 

7436 0728–303 17–23


LOCAL LOG FILE SWITCH: xxxxxx FROM xxxxxx 

Description: Two local mass storage disk files (PRSTAT and ALSTAT) are cataloged 

during the system initialization phase. When local data collection has been 

configured, and either the primary or alternate file has been filled, this error message 

appears. It signifies that the current statistics file is full. 

where: 

�� 

�� 

Action: If you want a copy of the line statistics, you should initiate a retrieve of the 

switched file to a host or turn on the auto-retrieve function. Otherwise, the collection 

of statistics continues to toggle between the two files, overwriting previously 

collected statistics. 

LSM NOT AVAILABLE 

Description: NMS is not able to queue the SWT command to the LSM/RCM. This is 

usually caused by UDLC being turned off in the configuration. 

Operator Action: Check the configuration for UDLC related statements. 

MEMORY NOT PRESENT 

Description: Storage at the specified address in the INSP or CHNG command does 

not exist. 

Action: Verify the ADR parameters, and retry the command. 

MOUNT aaa , FILE=aaa , REEL=aaa , VOL=aaa 

Description: Mount the requested tape. 

NO FILES CATALOGED 

Description: No files are cataloged. 

NO MESSAGES WAITING 

Description: This message is received by the user who transmits a $$SEND when no 

USMs are queued for them. 

17–24 7436 0728–303

NO RECOVERY FILE–CANNOT CANCEL FACILITY MOVE 


Description: This is the response to the CNCL command when a system failure has 



NON-CONFIGURED TERMINAL 

Description: This error message is generated when a user sends a USM to a terminal 

that does not exist. 

Action: Check the configuration for the terminal, and reenter the command. 

NOTE: NO X.25 TRUNKS CONFIGURED 

Description: An X.25 trunk command was invoked and no X.25 trunks are 

configured. This is an X.25 PSCS NMS message. 

NOTE: PDTE dte-id NOT ACTIVE 

Description: Part of the response to a DOWN PTRK command when the X.25 part of 

a trunk is already marked down in the configuration, but is still in the process of being 

brought to the down state. This is an X.25 PSCS NMS message. 

NOTE: X.25 TRUNK trunk-id ALREADY DISABLED 

Description: Part of the response to a DOWN PTRK command when the X.25 part of 

a trunk is already marked down in the configuration, but is still in the process of being 

brought to the down state. This is an X.25 PSCS NMS message. 

NOTE: X.25 TRUNK trunk-id ALREADY ENABLED 

Description: Part of a trunk is already marked up in the configuration, but is still in 

the process of being brought to the up state. This is an X.25 PSCS NMS message. 

PDTE dte-id NOT FOUND 

Description: A command specified a DTE that is not in configuration. This is an 

X.25 PSCS NMS message. 

POLL GROUP UP ... 

POLL GROUP UP, INPUT(STOPPED,ALLOWED), 

OUTPUT(STOPPED,ALLOWED),n TERMINAL(S) ACTIVE, 

(SPECIFIC,GENERAL,SLOW) POLLING 

Description: The poll group exists. 

7436 0728–303 17–25


*** RECEIVE NOT READY (RNR) EU=aaa 

Description: The NMS session to this end user is in an RNR condition. 

Action: Check the terminal status if the EU is an NMS console. 

*** RECEIVE READY (RR) EU=aaa 

Description: The NMS session to this end user is in an RR condition. 

RECORD is ON, LOG=freq 

Description: Displayed when the RECORD STAT=YES command is issued. This is 

an X.25 PSCS NMS message. 

REQUEST ASSIGN FOR TAPE FILE aaa 

Description: Enter the ASG command for the specified tape file name. 

Action: Enter the ASG command. 

REQUEST WRITE RING ON aaa , FILE=aaa 

Description: Place the write ring on the specified tape. 

RESOURCE LACK RESPONSE 

Description: Insufficient resources exist to execute the command. 

Action: Try again later. 

SEGMENT NOT PRESENT 

Description: The SEG parameter argument of the INSP or CHNG command is not a 

valid segment. 

Action: Verify the parameter and retry the command. 

*** SESSION DOWN (UDM) CONSOLE=aaa 

Description: The NMS session to this console is blocked. 

*** SESSION DOWN (UDM) DCP=aaa 

Description: The NMS session to this Telcon node is blocked. 

17–26 7436 0728–303

*** SESSION DOWN (UDM) TS=aaa 

Description: The session to this DCA TS is blocked. 


*** SESSION NOT AVAILABLE NOW. TRY AGAIN LATER *** 

Description: The session table in NMS is temporarily full. 

Action: Wait awhile, then retry. 

*** SESSION UP (UDM-C) CONSOLE=aaa 

Description: The NMS session to this console is open. 

*** SESSION UP (UDM-C) DCP=aaa 

Description: The NMS session to this Telcon node is open. 

*** SESSION UP (UDM-C) TS=aaa 

Description: The NMS session to this DCA TS is open. 

SITE NOT ACTIVE... 

SITE NOT ACTIVE, INPUT (STOPPED,ALLOWED), 

OUTPUT (STOPPED,ALLOWED) 

Description: The site is not signed on. 

SITE DOWN... 

Description: The site is disabled. 

7436 0728–303 17–27


SITE UP... 

SITE UP, INPUT (STOPPED,ALLOWED), 

OUTPUT (STOPPED,ALLOWED), TYPE: (BSC,NTR,etc.), 

n TERMINAL(S) ACTIVE n OUTPUT(S) QUEUED, 

n INPUT(S) QUEUED 

SITE (OPERATIVE, INOPERATIVE) 

Description: The site is enabled. 

STANDBY DCP VALUE NOT CONFIGURED 

Description: A resilient command has taken place (solicited or automatic). 

Action: If solicited, reenter with the correct Telcon node value. 

SUB-SEGMENTS NOT PRESENT 

Description: An invalid address in a noncontiguous segment was given in the INSP 

command. 

Action: Verify the address, and reenter the command. 

SWITCH COMPLETE 

Description: This message is a response to the normal completion of the SWT, 

ONLN, or STBY command. 

SWITCH REJECTED: ONLINE FOR OTHER STANDBY 

Description: The ONLN command was rejected because this Telcon node is already 

in an online state for another standby DCP pair. 

*** SYSTEM ERROR: CFIL DISK I/O ERROR = n *** 

Description: A hardware error occurred while the disk was being accessed. See the 

DCP/OS Operations Reference Manual (7831 5702) for an explanation. 

Action: If the error persists, call a local Unisys systems analyst. 

*** SYSTEM ERROR: UNABLE TO ACQUIRE TABLE VISIBILITY *** 

Description: The requested command could not be executed due to inaccessibility 

or corruption of system resources. 

Action: Call a local Unisys systems analyst. 

17–28 7436 0728–303

TERMINAL DOWN 

Description: Terminal is disabled. 

*** TERMINAL xxxxxx INPUT STREAMING *** 


Description: This message informs the terminal operator that a hardware problem 

has been detected. A rapid flood of input over a UNISCOPE or TTY line alerts the 

handler to a problem. The TERMINAL STREAMING message appears when the 

terminal is known to CMS 1100 (that is, it is signed on and a device table exists for it); 

otherwise, the more general LINE STREAMING message appears on the CMS 1100 

host console. 

Action: When an input streaming condition is detected, the terminal handler attempts 

to synchronize input with another CMI$. If this is unsuccessful, the offending terminal 

should be downed or powered off, and proper personnel notified. 

TERMINAL NOT ACTIVE... 

TERMINAL NOT ACTIVE, INPUT (STOPPED,ALLOWED), OUTPUT 

(STOPPED,ALLOWED) 

Description: The terminal is not signed on. 

TERMINAL/SESSION-ALREADY ACTIVE 

Description: This message is entered when the terminal is currently signed on and 

has an active session. 

TERMINAL UP... 

TERMINAL UP, IOP # n , PPID # n , 

INPUT (STOPPED,ALLOWED), OUTPUT (STOPPED,ALLOWED), 

TYPE:(U 100,TTY, etc.), n OUTPUT(S) QUEUED, 

n INPUT(S) QUEUED, SESSION PATH OUTPUT 

(BLOCKED,THROTTLED,ALLOWED) 

SESSION PATH INPUT (BLOCKED,THROTTLED,ALLOWED) 

SESSION PATH (OPEN,CLOSE)(COMPLETE,PENDING) TO:xeuname 

TERMINAL (OPERATIVE, INOPERATIVE) 

Description: The terminal is enabled. 

*** THE SESSION CONNECT-REQUEST HAS BEEN REJECTED *** 

Description: The session cannot be established. It may not be configured at the 

destination node. 

Action: Check the configuration for NMS SESSIONs and EUs. 

7436 0728–303 17–29


*** THE SESSION TO THE REQUESTED DCP/XTS DESTINATION IS 

DOWN (UDM)*** 

Description: The session required for the remote NMS command is blocked. 

Action: Check the reason for session blockage. 

TIME/DATE CHANGE IN PROGRESS–WAIT 

Description: Response to a SET command when time and date retrieval from an OS 

2200 host is already in progress. The retrieval in progress might be the result of 

system initialization or a previous SET command. 

Action: If retrieval in progress is successful, none. If retrieval in progress fails, retry 

SET command. 

TIME/DATE NMS EXPLICIT SETTING COMPLETED 

Description: Successful completion response to a SET command with explicit TIME 

and DATE parameters. 

Action: None. 

TIME/DATE NMS SETTING FROM HOST COMPLETED 

Description: Successful completion response to a SET command with a HOST 

parameter. 

Action: None. 

TIME/DATE UNCHANGED 

Description: Response to a SET command with no parameters. 

Action: None. 

TIME/DATE UNCHANGED–FORMAT OR VALUES INVALID 

Description: Response to a SET command with an invalid TIME or DATE parameter. 

Action: Retry the SET command with the correct TIME or DATE parameter. 

17–30 7436 0728–303

TIME/DATE UNCHANGED–HOST NAME INVALID 


Description: Response to a SET command with a HOST parameter when the 

parameter value is not the name of an ADDRESS, NETADR, or XEU statement in the 

configuration file or the DIB. 

Action: 1) Retry with an alternate source HOST name, or 2) use explicit TIME and 

DATE parameters to set the DCP’s time and date. 

TIME/DATE UNCHANGED–HOST UNAVAILABLE 

Description: Response to a SET command with a HOST parameter when the host 

name is valid, but a session cannot be opened to the time and date source host 

specified. The specified host is either down, inaccessible by means of the specified 

name, or doesn’t exist. 

Action: 

• Retry with an alternate source HOST name, or 

• Use explicit TIME and DATE parameters to set the time and date on the DCP. 

TIME/DATE UNCHANGED–APPLICATION UNAVAILABLE 

Description: Response to a SET command with a HOST parameter when a session 

can be opened to the time and date source host, but the host does not respond to the 

time and date retrieval request. The specified host is either having problems or is not 

an OS 2200 host. 

Action: 1) Retry with an alternate source HOST name or 2) use explicit TIME and 

DATE parameters to set the time and date on the DCP. 

TOO MANY USMS QUEUED 

Description: Too many messages are queued to the specified terminal ID. The 

maximum allowed is seven. 

Action: Wait and retry the command. 

TRACE TURNED OFF 

Description: The selected software debug tracing is turned off. 

TRACE TURNED ON 

Description: The selected software debug tracing is turned on. 

7436 0728–303 17–31


UP DEVICE-COMPLETE 

Description: The UP command for a device has been executed. 

UP PDTE dte-id COMPLETED 

Description: The UP PDTE command has been successfully completed. This is an 


UP PDTE dte-id REJECTED 

Description: The UP PDTE command was rejected. This is an X.25 PSCS NMS 

message. 

UP X.25 TRUNK trunk-id COMPLETED 

Description: The UP PTRK command has been successfully completed. This is an 


UP X.25 TRUNK trunk-id REJECTED 

Description: The UP PTRK command has been rejected. This is an X.25 PSCS NMS 

message. 

USM FILE ‘M@USMFnn’ NOT CATALOGED 

Description: A user attempting to send a USM when the ‘M@USMFnn’ file is not 

cataloged receives this error message. 

Action: The ‘M@USMFnn’ file must be cataloged. 

USM STORAGE FILE FULL 

Description: This error message is generated when the USM file ‘M@USMFnn’ has 

no free disk sectors in which to store USMs. 

Action: This problem may be corrected by expanding the ‘M@USMFnn’ file to a size 

of up to 1860 disk sectors. 

VOLUME ID... 

VOLUME ID: aaa USER ID: aaa 

DEVICE NAME: aaa DEVICE TYPE: aaa 

NUMBER OF FREE CATALOG ENTRY (SYSTEM) 

DATA SET LABEL: aaa 

Description: This is a STAT VOLUME command response. 

17–32 7436 0728–303


WARNING: LIST PROCESSING FOR THIS INFORMATION TABLE IS NOT 

IMPLEMENTED 

Description: The NMS LIST command is not supported for the table type. The 

command parameter specified a configuration statement name or STE index that 

correlates with a table type for which no processing is implemented. 

Action: If you specified the NMS LIST NAME command, you can use the NMS CFG’s 

@DISP command which displays the configuration statement name’s information 

table contents in hexadecimal format. You must be familiar with the information 

table’s field definitions and meanings in order to decode this format. 

*** WARNING: NO CFIL ACTION TAKEN - 

FACILITIES aaa ... ARE ACTIVE *** 

Description: No CFIL action was taken, as the indicated facilities are active. 

Action: Retry the command when the facilities are inactive. 

*** WARNING: NO CFIL ACTION TAKEN-FACILITIES ARE ACTIVE *** 

Description: Required processing for switching to the specified configuration names 

cannot be completed now because the indicated facilities are active. 

Action: Retry the configuration file switch when the facilities are inactive. 

*** WARNING: NO RESPONSE ON DCP–DCP FACILITY MOVE–CANCEL 

OR RECOVER? *** 

Description: This is the response to the MOVE command when a facility is being 

moved between DCPs and no acknowledgment is received within the allotted time. 

The warning is periodically repeated until it is answered. 

Action: Enter either cancel (CNCL) or restart (RCVR) as appropriate. 

WARNING: OPEN REJECT–aaa 

Description: The NMS session open request to this destination was rejected. 

Action: Reenter the command. If the problem persists, get help from a local Unisys 

systems analyst. 

WARNING: PDTE dte-id ALREADY DOWN 

Description: Displayed as part of an DOWN PDTE command when the PDTE is 

already marked down in configuration. This is an X.25 PSCS NMS message. 

7436 0728–303 17–33


WARNING: PDTE dte-id ALREADY UP 

Description: Displayed as part of an UP PDTE command when the DTE specified is 

already marked up in configuration. This is an X.25 PSCS NMS message. 

WARNING: X.25 TRUNK trunk-id ALREADY DOWN 

Description: Displayed as part of a response to a DOWN PTRK command when the 

trunk specified is already marked down in configuration. This is an X.25 PSCS NMS 

message. 

WARNING: X.25 TRUNK trunk-id ALREADY UP 

Description: Displayed as part of an UP PTRK command when the X.25 part of a 

trunk is already marked up in configuration. This is an X.25 PSCS NMS message. 

X.25 TRUNK trunk-id NOT FOUND 

Description: Command specified an X.25 trunk ID that is not in configuration. This 

is an X.25 PSCS NMS message. 

XFER–COMMAND RECEIVED 

Description: The end user program processing the transfer command has received 

an XFER command input, and is beginning to parse the command text. 

XFER ERROR–INVALID HOST FILE CYCLE 

Description: The host file cycle is invalid. 

Action: Correct and reenter the host file cycle. 

XFER ERROR–INVALID NMS COMMAND PARAMETER 

Description: An XFER STATUS or CNCL command was submitted with an invalid 

parameter. 

Action: Enter the correct parameter. 

XFER ERROR–NO DEFAULT HOSTID CONFIGURED 

Description: No default XFER destination is configured to allow an XFER FROM 

filename type of transfer. 

Action: For the TO= parameter, use an XEU that points to the desired destination 

host. 

17–34 7436 0728–303

XFER n-dcpname ABORT–DCP FILE IS EMPTY 


Description: The file transfer failed because the specified DCP file is empty. 

XFER n-dcpname ABORT–DCP FILE IS NOT A PROGRAM FILE 

Description: This DCP file is a data file only. It does not contain any elements. 

XFER n-dcpname ABORT–DCP FILE TOO SMALL 

Description: The specified DCP file is too small to accommodate the file transfer. 

Action: 

1. Delete and recatalog the file with sufficient size to accommodate the file being 

transferred. 

2. Catalog an alternate file with sufficient size to accommodate the file being 

transferred. 

XFER n-dcpname ABORT–DCP PHYSICAL I/O ERROR 

Description: The file transfer failed because of a DCP physical input or output error. 

XFER n-dcpname ABORT–HOST FILE TOO SMALL 

Description: The specified host file is too small to accommodate the file transfer. 

XFER n-dcpname ABORT–INTERNAL ERROR 

Description: A software error fatal to file transfer n-dcpname has occurred in the 

XFER software. 

XFER n-dcpname ABORT–SESSION CANNOT BE OPENED TO HOST 

Description: The transfer program (XFER) cannot open a session to the host 

specified by the XEU name input as a HOSTID on the transfer command (XFER). 

XFER n-dcpname ABORT–SESSION PATH DOWN 

Description: The XFER session to the host has been closed. 

XFER n-dcpname ABORT–USE (+1) RELATIVE FILE CYCLE 

Description: The host file specified as the transfer destination (using the XFER 

command) does not exist. Therefore, an absolute file cycle is invalid because the 

transfer command (XFER) cannot create an absolute cycle. 

7436 0728–303 17–35


XFER n-dcpname CANCELED 

Description: The file transfer referenced by n has been terminated with an NMS 

CNCL command. 

XFER n-dcpname COMPLETE–DCP FILE EOF FOUND 

Description: The end of a DCP file or element has been found during a transfer from 

a DCP to a host. 

XFER n-dcpname COMPLETE–HOST EOF FOUND 

Description: The end of a host file or element that is being transferred to a DCP has 

been found. 

XFER n-dcpname ERROR–ASSUMED QUALIFIER NOT ALLOWED FOR 

HOST 

Description: The *filename is not allowed for a host file parameter. 

Action: Remove the *filename and reenter input. 

XFER n-dcpname ERROR–DCP ELEMENT NOT IN FILE 

Description: The file cannot be transferred because the specified DCP element is not 

in the file. 

XFER n-dcpname ERROR–DCP FILE DISABLED 

Description: The file cannot be transferred because the specified DCP is disabled. 

XFER n-dcpname ERROR–DCP FILE I/O ERROR 

Description: The file cannot be transferred because of a DCP file input or output 

error. 

XFER n-dcpname ERROR–DCP FILE IN EXCLUSIVE USE 

Description: A DCP file involved in a transfer is already exclusively assigned by 

another run. 

17–36 7436 0728–303

XFER n-dcpname ERROR–DCP FILE IN USE 


Description: The file cannot be transferred because the specified DCP file is in use. 

Action: Reenter the command when the file is free. (Enter the STAT command to 

determine the status of the file.) 

XFER n-dcpname ERROR–DCP FILE NOT CATALOGED 

Description: The file cannot be transferred because the specified DCP file is not 

cataloged. 

Action: Catalog the DCP file and reenter the XFER command. 

XFER n-dcpname ERROR–DCP FILE READ ONLY 

Description: The file cannot be transferred because the specified DCP file cannot be 

written to. 

XFER n-dcpname ERROR–DCP MASS STORAGE ERROR 

Description: The file cannot be transferred because of a DCP mass storage error. 

XFER n-dcpname ERROR–DCP VOLUME NOT AVAILABLE 

Description: The file cannot be transferred because the requested DCP volume is too 

small. 

XFER n-dcpname ERROR–ELEMENT NAME NOT INPUT 

Description: This transfer (using the XFER command) requires an element name. 

Action: Enter the element name. 

XFER n-dcpname ERROR–FILE NAME ERROR 

Description: An incorrect filename has been entered. 

Action: Enter the correct filename. 

7436 0728–303 17–37


XFER n-dcpname ERROR–HOST FILE NOT AVAILABLE 

Description: An XFER destination or source file cannot be assigned for some reason. 

Two possible reasons are: 

• The file is an XFER destination and is not word-addressable, or 

• Someone else on the host has the file assigned. 

XFER n-dcpname ERROR–HOSTID NOT CONFIGURED 

Description: The specified HOSTID is not configured. 

XFER n-dcpname ERROR–HOSTID NOT INPUT 

Description: If both FROM and TO parameters are used, a HOSTID must also be 

input. 

Action: Enter a HOSTID. 

XFER n-dcpname ERROR–INSUFFICIENT HOST RESOURCES–TRY 

LATER 

Description: The host lacked sufficient resources to execute this command at this 

time. 

Action: Resubmit the command at a later time. 

XFER n-dcpname ERROR–INVALID DCP FILE NAME 

Description: The specified DCP filename is invalid. 

Action: Enter the valid DCP filename. 

XFER n-dcpname ERROR–INVALID HOST ELEMENT TYPE 

Description: The specified host element is invalid. 

Action: Enter the valid host element type. 

XFER n-dcpname ERROR–INVALID HOST FILE CYCLE 

Description: The host file cycle is invalid. 

17–38 7436 0728–303

XFER n-dcpname ERROR–INVALID HOST FILE NAME 

Description: The specified host file name is invalid. 

Action: Enter the valid host file name. 

XFER n-dcpname ERROR–INVALID PARAMETER 


Description: The syntax of an XFER parameter argument is incorrect. 

Action: Reenter the correct XFER parameter argument. 

XFER n-dcpname ERROR–INVALID TYPE PARAMETER 

Description: The entered TYPE parameter is invalid. 

Action: Enter the valid TYPE parameter. 

XFER n-dcpname ERROR–NO FILE NAME INPUT 

Description: A filename has not been entered. 

Action: Enter the filename. 

XFER n-dcpname ERROR–NO FROM PARAMETER INPUT 

Description: A transfer (using the XFER command) requires a FROM parameter. 

Action: Enter a FROM parameter. 

XFER n-dcpname ERROR–NO HOST FILE READ ACCESS 

Description: You do not have read access to the specified host file. 

XFER n-dcpname ERROR–PARAGRAPH LENGTH EXCEEDED 

Description: Too many characters have been entered for the XFER parameter. 

Action: Correct the incorrect XFER parameter and reenter the XFER parameters. 

XFER n-dcpname ERROR–REMOTE SYSTEM DOES NOT SUPPORT THIS 

XFER TYPE 

Description: The communication software paired with this Telcon does not support 

the transfer of an absolute element from the DCP to the host. 

7436 0728–303 17–39


XFER n-dcpname ERROR–TO PARAMETER NOT INPUT FOR XFER TO 

DCP 

Description: A transfer (using the XFER command) requires both a FROM and a TO 

parameter. 

Action: Enter a TO parameter. 

XFER n-dcpname ERROR–TYPE PARAMETER MISSING 

Description: This transfer (using the XFER command) requires a TYPE parameter. 

Action: Enter the TYPE parameter. 

XFER n-dcpname ERROR–UNRECOVERABLE HOST I/O ERROR 

Description: The transfer command (XFER) failed because of an unrecoverable host 

input or output error. 

XFER n-dcpname ERROR–XFER TO HOST ELEMENT NOT ALLOWED 

Description: A transfer (using the XFER command) from a DCP file element to a 

host file element is not allowed. 

XFER n-dcpname–FILE TRANSFER STARTED 

Description: A session has been opened to a host, the DCP file has been opened, the 

host file has been assigned, and a read from either the host or the DCP file has been 

initiated. 

XFER n-dcpname HOST FILE CREATED 

Description: A host file has been cataloged with a name derived from the name of 

the DCP file involved in the XFER n-dcpname. 

XFER n-dcpname–HOST FILE DOES NOT EXIST 

Description: An XFER destination or source file or element does not exist on the 

host designated by the XFER HOSTID specification. 

Action: Enter the correct destination or source file or element name. 

XFER n-dcpname HUNG–TRANSFER RESTART INDICATED 

Description: This file transfer has not recovered properly from a UDM on its session 

with the host. The transfer is being started over again from the beginning. 

17–40 7436 0728–303

XFER n-dcpname NOT ACTIVE 

Description: The file transfer referenced by n is not active. 

XFER n-dcpname–PATH TO HOST IS BLOCKED 


Description: A UDM has been received on the host session for this transfer 

command (XFER). 

XFER n-dcpname–PATH TO HOST IS OPEN 

Description: A UDM clear has been received on the host session for transfer (XFER) 

number n. 

XFER n-TOO MANY TRANSFERS ACTIVE–TRY LATER 

Description: The maximum number of transfers (using the XFER command) are 

active. 

Action: Enter the command later. 

XFER–NO FILE TRANSFERS ACTIVE 

Description: There are currently no active file transfers. 

7436 0728–303 17–41


Directory Services Agent (DSA) Messages 

The Directory Services Agent (DSA) function can be run in both demand and batch 

modes. The following messages log events within the DSA, and appear on your screen 

when you run DSA in demand mode. 

IPM CONNECTION UP. REMOTE ID=XXXX. REMOTE NAME=ipmQname. 

LOCAL ID=XXXX 

Description: The interprogram message queue is up. 

IPM CONNECTION DOWN. REMOTE NAME=ipmQname. 

Description: The interprogram message queue is down. 

SESSION# UP. 

Description: The peer DSA or DSA user session is connected. 

SESSION# DOWN. 

Description: The peer DSA or DSA user session is disconnected. 

17–42 7436 0728–303

Section 18 

Remote File System (RFS) Messages 

Remote file system error messages, text messages, and status codes are generated from 

the following: 

• RFS consoles (NMS consoles operating in the RFS command mode). These messages 

are generated by the local Telcon system from which the RFS command was entered. 

• Distributed Data Processing (DDP). These messages are generated by a target system 

specified in the RFS command. 

• Interprocess Communications (IPC) status codes. These messages are generated as a 

result of an error detected by an underlying service used by RFS. 

7436 0728–303 18–1


Error Messages Generated from RFS Consoles 

Table 18–1 lists the error messages that are generated by the RFS consoles (NMS consoles 

operating in the RFS command mode). These messages are generated by the local Telcon 

system from which the RFS command was entered. 

Table 18–1. Error Messages from RFS Consoles 

Message Explanation 

INVALID RFS COMMAND The command entered is not CREATE, PURGE, COPY, HELP, 

FORMAT, or EXIT. 

RFS SYNTAX ERROR The FILE or FROM keyword is not the first keyword specified 

in the command; the TO keyword is not the second keyword 

specified in the command; the command entered does have 

sufficient data to be parsed correctly; a file name contains 

more than 80 characters; one of the following special 

characters is used incorrectly, or a string containing one of 

the following special characters is not enclosed in single 

quotes: 

space 

, comma 

! exclamation point 

' single quote 

" double quote 

& ampersand 

= equal sign 

# pound sign 

: colon 

; semicolon 

INVALID RFS KEYWORD An invalid keyword was entered for a particular command. 

INVALID RFS KEYWORD 

VALUE 

WORK ORDER LOG IS 

FULL 

UNRECOGNIZABLE 

REPORTED CONDITION– 

VALUE = >n< 

UNABLE TO CREATE 

WORK ORDER LOG 

An invalid keyword value was entered for a particular 

keyword. 

The RFS system is temporarily out of resources. The 

command may be retried at a later time. 

A DDP status code that is not known to this Telcon system 

was returned. The value displayed may be used as a crossreference 

to a DDP status code used in the target system. 

Recognizable DDP status codes are listed in Table 18–2. 

An internal system error has occurred. 

18–2 7436 0728–303

Messages Defined by DDP 


Table 18–2 lists the messages defined by DDP. These messages are generated by a target 

system specified in an RFS command. The target system may be a Telcon system or a 

foreign system (a system other than Telcon). Although the messages have similar 

meanings in all DDP systems, the precise meaning may vary, depending on the target 

system that generated the message. 

The DDP status code is not displayed when the text of the message is displayed, but is 

provided as a cross-reference to DDP status codes in foreign systems. 

The explanation states the reason that a Telcon system would generate the message. This 

explanation may not apply if the message was generated by a foreign system. 

Table 18–2. Messages Defined by DDP 

DDP 

Status 

Code Message Explanation (for Telcon systems) 

1 PARAMETER ERROR A supplied parameter has an invalid value; a 

required parameter is missing; a supplied 

parameter is inconsistent with the request 

(for example, a tape file parameter is 

supplied for a disk file); or an unspecified file 

system error has occurred. 

2 TEMPORARILY UNABLE– 

PLEASE RETRY 

3 FUNCTION CODE NOT 

SUPPORTED 

4 WORK ORDER HEADER 

ERROR 

5 WORK ORDER CLASS NOT 

SUPPORTED 

6 CHECKPOINT NOT 

AVAILABLE 

Resources are temporarily unavailable; a 

device is busy; all tape drives are allocated; the 

file system volume table is not updated; the file 

system catalog is not updated; or the file 

system label is not updated. 

A request was received that was not CREATE, 

COPY, or PURGE. 

An internal system error occurred. 

An incompatible DDP system was accessed. 

An attempt was made to recover or restart a 

failed DDP operation (recovery is not supported 

by Telcon). 

8 REPORT TEXT Additional text was supplied describing the 

outcome of the command (if the command 

was entered from an RFS console, the 

additional text will be displayed). Tables 18–3 

and 18–4 list report text messages that Telcon 

may generate. 

10 COMPLETED The command completed successfully. 

7436 0728–303 18–3



DDP 

Status 


130 FILE NAME ALREADY EXISTS An attempt was made to create a file with a 

name that already exists (the file may exist on 

disk, or may be assigned as a tape file). 

131 VOLUME SPACE NOT 

AVAILABLE 

132 VOLUME NAME NOT 

AVAILABLE 

133 SOURCE VOLUME NOT 

AVAILABLE 

There is not enough space to create the file on 

the target system; there is not enough space 

to create the file on the requested device or 

volume; or the file catalog is full. 

The volume is not available; the volume is a 

system read-only volume; or the file resides on 

a volume that is not available. 

The file resides on a volume that is not 

available. 

134 FILE TYPE NOT SUPPORTED The file type is not SEQUENTIAL or 

UNDEFINED; or an element type parameter is 

specified. 

135 INVALID KEY SPECIFICATION A file key is specified. 

136 INVALID FILE SIZE 

SPECIFICATION 

140 DEVICE CLASS/TYPE NOT 

AVAILABLE 

141 DEVICE CLASS/TYPE NOT 

SUPPORTED 

The maximum size parameter is greater than 

65,535 blocks. 

The device class or device type is down; or 

there are no tape drives that are up. 

The device class is not DISK, DISKETTE, or 

TAPE; the device type is not FIXED, REMOVE, 

WINCH, or 8441W for device-class DISK; the 

device type is not FDDS, FDS, IFDC, or 8441D 

for device-class DISKETTE; or no tape drives 

are configured. 

142 FILE NAME SYNTAX ERROR The file name has an invalid length; the file 

qualifier has a invalid length; or the file system 

detected an invalid file name. 

160 SOURCE FILE NOT FOUND The file does not exist on the target system. 

161 SOURCE ELEMENT TYPE 

NOT SUPPORTED 

162 ELEMENT NAME NOT 

FOUND 

163 SOURCE FILE NOT 

AVAILABLE 

165 READ KEY INVALID OR 

MISSING 

Not applicable to Telcon. 


The file is in use, and the mode parameter is 

not WAIT. 


18–4 7436 0728–303



DDP 

Status 


170 ERROR IN SOURCE FILE 

PROCESSING 

180 DESTINATION FILE NOT 

FOUND 

181 DESTINATION ELEMENT 

TYPE NOT SUPPORTED 

183 DESTINATION FILE NOT 

AVAILABLE 

184 WRITE KEY INVALID OR 

MISSING 

185 DESTINATION FILE READ 

KEY INVALID 

186 DESTINATION FILE 

ENCODING NOT 

SUPPORTED 

189 FILE NOT COPIED, 

UNRECOVERABLE ERROR 

190 ERROR IN DESTINATION FILE 

PROCESSING 

200 HOST WITH DESTINATION 

FILE NOT AVAILABLE 

201 EXECUTION HOST NOT 

AVAILABLE 

An unspecified file system error has occurred. 

The file does not exist on the target system. 


The file is in use; or the file is in use, and the 

MODE parameter is not WAIT. 



The file translation is not ASCII, EBCDIC, or 

TRANSPARENT. 

An internal system error has occurred. 

An unspecified file-system error has occurred 

or an internal system error has occurred. 

A session could not be established from the 

source system to the destination system. 

A session could not be established to the 

source or target system. 

7436 0728–303 18–5


Warning Messages 

Table 18–3 lists the warning messages that may accompany a work order completion 

message. 

These messages are reported with the DDP status code 8, REPORT TEXT. If the command 

was entered from an RFS console, these messages will be displayed. If the command was 

entered from a foreign system, these messages may not be displayed. 

These messages indicate that the command was completed successfully, but some 

parameters given in the command may have been ignored or overridden. 

Table 18–3. Warning Messages 

Warning Message Explanation 

**WARNING** RECORD SIZE 

NOT SUPPORTED 

**WARNING** BLOCK SIZE 

NOT SUPPORTED 

**WARNING** INITIAL SIZE 

NOT SUPPORTED 

**WARNING** INCREMENT 

SIZE NOT SUPPORTED 

**WARNING** REGISTER 

ENTRY CAN ONLY BE 

‘CATALOG’ 

**WARNING** ACCESS CAN 

ONLY BE ‘PUBLIC’ 

**WARNING** RECORD 

FORMAT SUPPORTED 

**WARNING** MAXIMUM 

SIZE NOT SUPPORTED FOR 

TAPE FILES 

**WARNING** DEVICE 

PARITY CAN ONLY BE ‘ODD’ 

**WARNING** MAXIMUM 

SIZE DEFAULTED TO 10 

BLOCKS 

A record size parameter is specified, but is not supported 

by Telcon. 

A block size parameter is specified, but is not supported 


An initial size parameter is specified, but is not supported 


An increment size parameter is specified, but is not 

supported by Telcon. 

A register entry parameter other than CATALOG is 

specified, but only CATALOG is supported by Telcon. 

An access parameter other than PUBLIC is specified, but 

only PUBLIC is supported by Telcon. 

A record format parameter is specified, but is not 

supported by Telcon. 

A maximum size parameter is specified for a tape file, but 

is not supported by Telcon (the maximum size parameter 

only applies to disk files). 

A parity parameter other than ODD is specified, but only 

ODD is supported by Telcon. 

A maximum size parameter is not specified or the 

maximum size parameter is zero. Thus, a default value of 

10 blocks is used. 

18–6 7436 0728–303

Error Messages 


Table 18–4 lists error messages that may accompany a work-order rejection message. 

These messages are reported with the DDP status code 8, REPORT TEXT. If the command 

was entered from an RFS console, these messages are displayed. If the command was 

entered from a foreign system, these messages may not be displayed. 

These messages indicate the command was not completed due to the reason specified. 

Table 18–4. Error Messages 

Error Message Explanation 

PROTOCOL ERROR An internal system error has occurred. 

DESTINATION FILE NOT 

AVAILABLE, INDIRECT MODE NOT 

SUPPORTED 

The file is in use and the mode parameter is 

INDIRECT, but only DIRECT and WAIT are supported 


SOURCE FILE EMPTY The file does not contain any data to copy. 

ATTEMPTED TO WRITE PAST EOF 

IN DESTINATION FILE 

OPERATOR CANCELED TAPE FILE 

>tape file name< 

ATTEMPTED TO WRITE MORE 

THAN 2048 WORDS TO FILE 

BLOCK 

TIMEOUT WAITING FOR FILE >file 

name< 

The destination file is too small to contain the source 

file or the file-system detected a block number out of 

range. 

The tape file has been canceled by the operator. 

A file record was received with more than 2,048 

words. 

The file is in use, the mode parameter is WAIT, and 

the maximum amount of time allowed to wait for the 

file has elapsed. 

DESTINATION NAME UNKNOWN A remote target system is unknown; the RFS system 

is not configured properly; or an internal system 

error has occurred. 

IPC DETECTED ERROR, 

CLASS=>ipc error class< 

CODE=>ipc error code< 

An error is detected by the underlying IPC service 

used by RFS. IPC error classes and codes are listed 

in Tables 18–5 through 18–12. 

FILE TRANSFER SESSION IS DOWN The session used by RFS has been lost. 

AUTHORIZATION DENIED The UID parameter specified in the NMS RFS 

command (the NMS command used to enter the RFS 

mode) is not allowed to access a target DDP system 

or an internal system error has occurred. 

7436 0728–303 18–7


IPC Status Codes 

Tables 18–5 through 18–12 list status codes generated by IPC. These messages are generated 

as a result of an error detected by an underlying service used by RFS. 

Certain IPC status codes are translated by RFS so that a meaningful message is displayed on 

the RFS console. Those that are not translated are either not generated by Telcon systems, 

or indicate an unusual internal system error. 

Table 18–5 lists Class 3 IPC error codes, which indicate that the request was not accepted by 

IPC. 

Table 18–5. IPC Class 3 Error Codes 

Code Description Comments 

1 AP name not found in external 

directory. 

Not generated by Telcon. 

2 Destination name unknown. Translation provided by RFS. 

3 Authorization denied. Translation provided by RFS. 

4 Interface parameter unknown. Internal system error. 

5 Interface parameter missing. Internal system error. 

6 Conversation ID unknown. Not generated by Telcon. 

7 Context area unavailable. Translation provided by RFS. 

8 Exception reply pending. Not generated by Telcon. 

9 Abort pending. Translation provided by RFS. 

10 Command discipline violation. Internal system error. 

11 Unknown operation request. Internal system error. 

12 Solicited Response not arrived. Not generated by Telcon. 

13 No data. Translation provided by RFS. 

15 Conversation not terminated on 

close. 

Not generated by Telcon. 

18–8 7436 0728–303


Table 18–6 lists IPC Class 4 error codes, which indicate that the conversation was aborted 

locally by IPC. 



1 Timeout waiting for response. Internal system error. 

2 Error on underlying level. Translation provided by RFS. 

3 IPC logic error. Internal system error. 

4 IPC load error. Not generated by Telcon. 

Table 18–7 lists IPC Class 10 error codes, which indicate that the request was not accepted 

by image transformation services. 



1 Presentation format descriptor 

name unknown. 

Internal system error. 

2 Presentation error. Internal system error. 

7436 0728–303 18–9


Table 18–8 lists IPC Class 128 error codes, which indicate an IPC request error. 

Table 18–8. IPC Class 128 


1 Required header item missing. Internal system error. 

2 Header item not expected. Internal system error. 

3 Invalid function code. Internal system error. 

4 Invalid response type. Internal system error. 

5 Invalid user ID. Translation provided by RFS. 

6 Invalid external AP reference. Translation provided by RFS. 

7 Message sequence error. Internal system error. 

8 Invalid mode of operation. Internal system error. 

9 Invalid priority. Not generated by Telcon. 

10 IPC protocol procedure error. Internal system error. 

11 Invalid header item. Internal system error. 

12 Version not supported. Attempt to access incompatible DDP 

product. 

13 Class of procedure not 

supported. 

Internal system error. 

0 Others. Internal system error. 

Table 18–9 lists IPC Class 129 error codes, which indicate a system error. 



1 Load error. Not generated by Telcon. 

2 User program check. Not generated by Telcon. 

3 User program loop. Not generated by Telcon. 

4 User program exceeded timeout count. Internal system error. 

0 Others. Internal system error. 

18–10 7436 0728–303


Table 18–10 lists IPC Class 130 error codes, which indicate a recovery error. 



1 Recovery facility down. Not generated by Telcon. 

0 Others. Not generated by Telcon. 

Table 18–11 lists IPC Class 131 error codes, which indicate an access error. 



1 User program issued invalid data command. Internal system error. 

0 Others. Not generated by Telcon. 

Table 18–12 lists IPC Class 132 status code error messages, which indicate a program request 

error. 



1 Invalid successor ID. Not generated by Telcon. 

2 Invalid procedural request. Not generated by Telcon. 

3 Program issued abort. Internal system error. 

7436 0728–303 18–11


18–12 7436 0728–303

Appendix A 

X.25 PSCS Diagnostic Codes 

Information in this appendix originates from the following specifications: 

• Recommendation X.25, defined by the International Telecommunications 

Union/Telecommunications Standardization Sector (ITU/TSS), formerly the 

Consultative Committee for International Telegraph and Telephone (CCITT) 

• International Standards Organization (ISO) 8208 

• Public Data Networks Interfaces 

Diagnostic Codes are reported by: 

• The X.25 PSCS layer 3/4 platform interface (specific) 

PSCS diagnostic codes pertain to a layer 4 program that sends a call request primitive 

to layer 3 in PSCS. While the request is being processed, a call request reject can 

occur for a number of reasons. 

• The X.25 PSCS Packet Layer Services (PLS) Host interface (specific) 

• Directly attached X.25 DTE (DAD) devices 

• Packet Switched Public Data Networks (PDNs) 

• X.25 PSCS (general) 

• The DCE Network Feature 

Coding of X.25 network generated diagnostic fields in clear, reset, and restart indication 

packets are listed in the table below. In the description of the CENLOG, Register R11 will 

contain the code listed in this table. 

DCE Network Feature Diagnostic Codes 

Diagnostic codes that may be contained in clear or reset packets generated by the DCE 

Network feature when a virtual circuit connection is routed through the feature are listed 

below. The DCE Network feature still passes through diagnostic codes generated by 

another X.25 DTE device, PDN, or X.25 PSCS’s layer 3 module. 

7436 0728–303 A–1


Table A–1. X.25 Diagnostic Codes 

Code Diagnostic Source 

Dec Hex 

0 0 No additional information PDN, PSCS, DAD generated 

1 1 Invalid P (S) PDN, PSCS, DAD generated 

2 2 Invalid P (R) PDN, PSCS, DAD generated 

16 10 Packet type invalid PDN, PSCS, DAD generated 

17 11 Packet type invalid for state r1 PDN, PSCS, DAD generated 



20 14 Packet type invalid for state p1 PDN, PSCS, DAD generated 






26 1A Packet type invalid for state p7 PDN, PSCS, DAD generated 

27 1B Packet type invalid for state d1 PDN, PSCS, DAD generated 

28 1C Packet type invalid for state d2 PDN, PSCS, DAD generated 

29 1D Packet type invalid for state d3 PDN, PSCS, DAD generated 

32 20 Packet not allowed PDN, PSCS, DAD generated 

33 21 Unidentifiable packet PDN, PSCS, DAD generated 

34 22 Call on one-way logical channel PDN, PSCS, DAD generated 

34 22 Incoming call was received on a 

circuit configured for outgoing only. 

Check the VCGRP=(fchan,lchan,RIC) 

parameter on the PDNGRP statement. 

35 23 Invalid packet type on a permanent 

virtual circuit 

PSCS generated 

PDN, PSCS, DAD generated 

36 24 Packet on unassigned logical channel PDN, PSCS, DAD generated 

36 24 A packet was received on a logical 

channel number outside the 

configured range of circuits. Check 

the logical channel ranges configured 

on all of the VCGRP=(fchan,lchan) 

parameters. 


A–2 7436 0728–303




Dec Hex 

36 24 An incoming call packet was received 

for the X.25 UTS 4000 Cluster 

Controller layer 4 interface on a line 

that is not one of the 16 lines 

configured. 


37 25 Reject not subscribed to PDN, PSCS, DAD generated 

38 26 Packet too short PDN, PSCS, DAD generated 

38 26 An incoming call packet contains no 

DTE address field. 

38 26 A call connected packet contains a 

shorter facility field than the facility 

field length indicates. 



39 27 Packet too long PDN, PSCS, DAD generated 

39 27 A Call Request Primitive has specified 

too much call user data for the call 

request packet. 

39 27 A clear indication packet contains too 

much fast-select user data. 

39 27 A call connected packet contains 

user data or contains too much fastselect 

user data. 




40 28 Invalid general format identifier PDN, PSCS, DAD generated 

41 29 Restart or registration packet with 

nonzero in bits 1 to 4 of octet 1, or 

bits 1 to 8 of octet 2 

42 2A Packet type not compatible with 

facility 

42 2A A call connected packet was received 

in response to a call packet 

containing a restricted-response fast 

select facility. (This type of facility 

requires a clear indication response.) 




43 2B Unauthorized interrupt confirmation PDN, PSCS, DAD generated 

44 2C Unauthorized interrupt PDN, PSCS, DAD generated 

45 2D Unauthorized reject PDN, PSCS, DAD generated 

48 30 Time expired PDN, PSCS, DAD generated 

49 31 Time expired for incoming call PDN, PSCS, DAD generated 

50 32 Time expired for clear indication PDN, PSCS, DAD generated 

7436 0728–303 A–3




Dec Hex 

51 33 Time expired for reset indication PDN, PSCS, DAD generated 

52 34 Time expired for restart indication PDN, PSCS, DAD generated 

53 35 Time expired for call deflection PDN, PSCS, DAD generated 

64 40 Call set up, call clearing, or 

registration problem 


for the TCP–IP Stack, but didn’t 

contain the required protocol ID 

information in the call user data field. 

64 40 An incoming call packet contains a 

badly formatted facility field 

parameter. 

64 40 No available resources for handling a 

new virtual circuit connection. 


for the X.29 PAD handler, but didn’t 

contain the required protocol ID 

information in the call user data field. 

64 40 For the X.29 PAD handler, a $$SON 

error occurred. 


for the DCP-to-DCP Trunk handler, but 

the X.25 Trunk is not initialized or not 

configured. 

64 40 An incoming call was received for the 

following program products or 

features, but they are not installed, 

configured, or initialized: OSITS 

program product, TCP–IP Stack 

program product, DCE Networking 

Feature, or the user-written layer 4s 

for handling international, national, or 

user-defined protocol IDs. 


for the X.28 PAD Terminal handler. 

This interface is not designed to 

receive incoming call packets. 










65 41 Facility/registration code not allowed PDN, PSCS, DAD generated 

A–4 7436 0728–303




Dec Hex 


containing the priority facility, but the 

OPTIONS=HIPRI on the PDNGRP 

statement isn’t configured. 

65 41 An incoming call packet contains a 

facility code that is not allowed for 

incoming call packets. 



66 42 Facility parameter not allowed PDN, PSCS, DAD generated 


containing an out-of-range facility 

parameter value for the following 

facility codes: window size, packet 

size, fast select, reverse charging. 

Check the configured window, packet 

and frame sizes configured on the 

WINSIZ and PAKSIZ parameters of the 

DTETYPE statement and the N1 

parameter on the X25DEF statement, 

and the OPTIONS=(RVCHG,FASTSL) 

parameter options. 

66 42 A Call Accept Primitive was received 

containing out-of-range packet or 

window sizes. These values cannot 

be larger than the values specified in 

the Call Indication Primitive. 

66 42 A call connected packet was received 

containing out-of-range packet or 

window sizes. These values cannot 

be larger than the values specified in 

the call request packet. 




67 43 Invalid called DTE address PDN, PSCS, DAD generated 


and its called DTE address doesn’t 

match the DTE address configured on 

the DTEADR parameter of the 

PDNGRP statement. 


68 44 Invalid calling DTE address PDN, PSCS, DAD generated 


that is not configured to be accepted. 

Check the X25ROUTE statement and 

its parameters to verify the type and 

content of the incoming call packets 

that is allowed. 


7436 0728–303 A–5




Dec Hex 


from a directly attached X.25 DTE 

(DAD) device (OPTIONS=DAD on the 

PDNGRP statement) and calling 

address verification is enabled 

(L3OPT=11 on the X25DEF 

statement) and the incoming call 

packet’s calling DTE address doesn’t 

match the DTE address configured on 

the DTEADR parameter of the DTE 

statement. 


69 45 Invalid facility/registration length PDN, PSCS, DAD generated 

70 46 Incoming call barred PDN, PSCS, DAD generated 

71 47 No logical channel available PDN, PSCS, DAD generated 

72 48 Call collision PDN, PSCS, DAD generated 

73 49 Duplicate facility requested PDN, DAD generated 

74 4A Nonzero address length PDN, DAD generated 

75 4B Nonzero facility length PDN, DAD generated 

76 4C Facility not provided when expected PDN, DAD generated 

77 4D Invalid CCITT-specified DTE facility PDN, DAD generated 

78 4E Maximum number of call redirections 

or call deflections exceeded 

PDN, DAD generated 

80 50 Miscellaneous PDN, DAD generated 

81 51 Improper cause code from DTE PDN, DAD generated 

82 52 Not aligned octet PDN, DAD generated 

83 53 Inconsistent Q-bit setting PDN, PSCS, DAD generated 

84 54 NUI problem PDN, DAD generated 

96 60 Not assigned X.25 network generated 

112 70 International problem X.25 network generated 

113 71 Remote network problem X.25 network generated 

114 72 International protocol problem X.25 network generated 

115 73 International link out of order X.25 network generated 

116 74 International link busy X.25 network generated 

117 75 Transit network facility problem X.25 network generated 

118 76 Remote network facility problem X.25 network generated 

A–6 7436 0728–303




Dec Hex 

119 77 International routing problem X.25 network generated 

120 78 Temporary routing problem X.25 network generated 

121 79 Unknown called DNIC X.25 network generated 

122 7A Maintenance action (see Note 6) PDN, DAD generated 

128 80 Closed-user group (CUG) number is 

not valid 


129 81 CUG type does not allow call packets. PSCS generated 

129 81 Invalid EU statement identifier * DCE Network Feature generated 

130 82 EU statement already active * DCE Network Feature generated 

131 83 No available line * DCE Network Feature generated 

132 84 Dial out failed * DCE Network Feature generated 

133 85 Configuration error * DCE Network Feature generated 

134 86 EU statement marked down * DCE Network Feature generated 

135 87 No resources * DCE Network Feature generated 

136 88 Device console not active * DCE Network Feature generated 

136 88 X.25 trunk has become idle. This is 

the default diagnostic value and a 

different code value can be specified 

on the DTETYPE configuration 

statements. Refer to the DCP Series 

X.25 PSCS Configuration and 

Operations Guide. Section 6.3.1 

describes the use of the diag 

parameter option on the 

�� parameter. 


138 8A Close abort from EU/CSU * DCE Network Feature generated 

139 8B Improper protocol * DCE Network Feature generated 

140 8C Syntax error * DCE Network Feature generated 

141 8D Open reject from EU statement * DCE Network Feature generated 

142 8E Session is timed out * DCE Network Feature generated 

143 8F Session is lost * DCE Network Feature generated 

144 90 Abort requested * DCE Network Feature generated 

144 90 Timer expired or retransmission 

count surpassed 


7436 0728–303 A–7




Dec Hex 

145 91 Interrupt confirmation packet timeout 

occurred. The virtual circuit is in a 

data state and an interrupt packet is 

outstanding. 


count surpassed for INTERRUPT 



145 91 Invalid DTE identifier or address DCE Network Feature generated 


count surpassed for DATA packet 

transmission 


146 92 DTE statement marked down DCE Network Feature generated 


count surpassed for REJECT 


147 93 Unknown DTE (not found) DCE Network Feature generated 

148 94 DTE is for calling only DCE Network Feature generated 

149 95 Logic error (software problem) DCE Network Feature generated 

160 A0 DTE-Specific signals PDN, DAD generated 

161 A1 DTE operational PDN, PSCS, DAD generated 

162 A2 DTE not operational PDN, DAD generated 

163 A3 DTE resource constraint PDN, DAD generated 

164 A4 Fast select not subscribed PDN, DAD generated 

165 A5 Invalid paritally full DATA packet PDN, DAD generated 

166 A6 D-bit procedure not supported PDN, DAD generated 

167 A7 Registration/Cancellation confirmed PDN, DAD generated 

169 A9 Configured DTE statement has been 

marked as “down” by an NMS 

command. 

170 AA Configured DTE statement has been 

enabled by an NMS command. 

171 AB DTP connection to the host is 

blocked. Probable configuration error 

or transport connection error. 

172 AC Call packet is cleared because the 

resilient trunk is in standby or 

dormant state. 



PLS generated 


A–8 7436 0728–303




Dec Hex 

174 AE Due to congestion at the data link 

layer, a packet could not be sent out 

on the network. The virtual circuit 

connection is reset. 

175 AF A data packet could not be saved 

because the link area is full. The 

virtual circuit is cleared. 

176 

to 

223 

B0 

to 

D0 

(Not assigned) – – 

176 B0 Due to congestion at the packet 

layer, the virtual circuit connection is 

cleared. Too many packets for this 

circuit have been saved in the link 

area that are waiting to be sent on 

the network. 

177 B1 Out of resources. A call packet is 

cleared by the DCP-to-DCP layer 4 

(LEVEL4=PDNTRUNK) type. Either the 

maximum number of switched virtual 

circuits limit has been reached 

(LEVEL4=(PDNTRUNK,mxsvc)), or the 

layer 4 was unable to allocate a runtime 

table for the pending virtual 

circuit connection. 

199 C7 Invalid primitive type received from 

layer 4 program after a call indication 

primitive had been sent to it. 

208 D0 Data message size of the 

reassembled (M-bit) data packets 

exceeds 16,384 octets, a Telcon 

software limitation. 







224 E0 OSI Network Service problem PDN, DAD generated 

225 E1 Disconnection (transient condition) PDN, DAD generated 

226 E2 Disconnection (permanent condition) PDN, DAD generated 

227 E3 Connection rejection – reason 

unspecified (transient condition) 

228 E4 Connection rejection – reason 

unspecified (permanent condition) 



7436 0728–303 A–9




Dec Hex 

229 E5 Connection rejection – quality of 

service not available (transient 

condition) 

230 E6 Connection rejection – quality of 

service not available (permanent 

condition) 

231 E7 Connection rejection – NSAP 

unreachable (transient condition) 

232 E8 Connection rejection – NSAP 

unreachable (permanent condition) 





233 E9 Reset – reason unspecified PDN, DAD generated 

234 EA Reset – congestion PDN, DAD generated 

235 EB Connection rejection – NSAP address 

unknown (permanent condition) 


240 F0 Higher layer initiated PDN, DAD generated 

241 F1 Disconnection – normal PDN, DAD generated 

241 F1 Received an unknown/invalid HIC 

string from the host. 

PLS generated 

242 F2 Limited resources in the host. PLS generated 

242 F2 Disconnection – abnormal PDN, DAD generated 

243 F3 Disconnection – incompatible 

information in user data 

244 F4 Connection rejection – reason 

unspecified (transient condition) 

245 F5 Connection rejection – reason 

unspecified (permanent condition) 

246 F6 Connection rejection – quality of 

service not available (transient 

condition) 

247 F7 Connection rejection – quality of 

service not available (permanent 

condition) 

248 F8 Connection rejection – incompatible 

information in user data 

249 F9 Connection rejection – 

unrecognizable protocol identifier in 

user data 








A–10 7436 0728–303




Dec Hex 

250 FA Reset – user resynchronization PDN, DAD generated 

256 100 Closed - user group (CUG) specified 

with no group index (ZR$LNKI), LINE 

STE index (ZR$LSTEI), or PDNGRP 

STE index (ZR$PGRPX). 

258 102 No link, network, or abbreviated DTE 

address information is specified in a 

multi-network configuration. 

Layer 3/4 Platform generated 


259 103 Invalid layer 4 routing ID. Layer 3/4 Platform generated 

260 104 Invalid circuit type (permanent or 

switched). 


261 105 Requested DTE was not found. Layer 3/4 Platform generated 

262 106 Unknown group index, line, or 

PDNGRP STE index. 


263 107 No logical channels available. Layer 3/4 Platform generated 

264 108 No links available for use. Layer 3/4 Platform generated 

266 10A Invalid flow-control parameter. Layer 3/4 Platform generated 

267 10B No system resources available 

(buffers). 


268 10C Requested group is down, not ready. Layer 3/4 Platform generated 

269 10D The DTE is configured to not allow 

call requests (the parameter value, 

OPTIONS=CALLING, is configured). 


270 10E Invalid DTE identifier or address. Layer 3/4 Platform generated 

271 10F The configured DTE statement has 

been marked as “down” by an NMS 

command. 

272 110 Layer 3 received an invalid 

connection identifier (ZR$TLID) from 

Layer 4. The identifier has become 

obsolete because it has since been 

re-used for another virtual circuit 

connection. 



Legend 

* These diagnostic codes correspond to reasons given by the Telcon Data Transport Protocol (DTP) 

when a transport connection has been rejected or has failed. 

7436 0728–303 A–11


Notes: 

1. “Layer 3/4 Platform generated” implies that the values of the codes are greater 

in value (255 decimal) than what would be allowed to be sent across an X.25 

network. 

2. Diagnostic codes that PSCS generated defines, and will send out on the network. 

A DTE, attached either directly to the DCP (DAD) or across a network, may 

receive these diagnostic codes in clear packets. In some cases, the codes are 

passed up by the layer 3 to the layer 4 program. 

3. Not all diagnostic codes need apply to a specific network, but those used are as 

coded in the table. 

4. A given diagnostic need not apply to all packet types (for example, reset 

indication, clear indication, restart indication, registration confirmation, and 

diagnostic packets). 

5. The first diagnostic in each grouping is a generic diagnostic and can be used in 

place of the more specific diagnostics within the grouping. The decimal 0 

diagnostic code can be used in situations where no additional information is 

available. 

6. This diagnostic may also apply to a maintenance action within a national 

network. 

7. Diagnostics 224 through 255 support the OSI Network Service Definition. 

8. In certain situations, multiple diagnostic codes may apply. For example, if a 

timer has expired and a (RESTART, CLEAR, or RESET) REQUEST packet is to 

be retransmitted, then the DTE may use the diagnostic code associated with the 

original error or the corresponding “timer expired” diagnostic code. 

A–12 7436 0728–303

Appendix B 

X.25 PSCS Initialization Error Codes 

Table B–1 lists X.25 PSCS initialization codes and explains what each means. 

Code 

(Hex) 

Table B–1. X.25 PSCS Initialization Error Codes 

Explanation 

0002 X.25 PSCS is unable to register its extension name (X25) with Telcon’s NMS 

registration procedure. (Initialization is complete, however.) 

0004 X.25 PSCS is unable to obtain the DCA queue number associated with the X.25 

PSCS NMS queue. (Initialization is complete, however.) 

0005 X.25 PSCS was unable to obtain the DCE Networking Feature’s DCA queue 

(using DCP/OS service CPA$QL1X). Though initialization for X.25 PSCS is 

complete, the interface to DCE Networking software is not. R10 contains the 

DCP/OS error code. 

0008 The table type associated with a DTE statement was neither a trunk, cluster, or 

DCATS. 

0009 More than 15 DTE address digits are specified on the DTEADR parameter. R10 

contains the DTE STE index. 

0010 No remote DTE address (DTEADR parameter) is specified on a DTE statement. 

0020 No more dynamic system segments are available from DCP/OS. The 

configuration may be too large or the operating system may not have enough 

system segments to allocate (BUILD) directive SST). 

0040 The accumulated sizes of internal table structures exceed the system segment 

size (4K bytes). Possible causes include too many logical channels specified 

on the PDNGRP statements or too many DTE statements referencing a 


0041 Maximum number of PDNGRP statements is exceeded. 

0042 Maximum number of TRUNK statements associated with PDNs is exceeded. 

0200 The required VCGRP keyword is missing from a PDNGRP statement. 

2002 NDS type other than a LINE statement references a PDNGRP statement as its 

parent or not NDS references a PDNGRP. 

2003 The required DTETYPE keyword is missing from a DTE statement. 

7436 0728–303 B–1

X.25 PSCS Initialization Error Codes 

Code 

(Hex) 

Table B–1. X.25 PSCS Initialization Error Codes 

Explanation 

2005 An invalid logical channel number is specified for a VCGRP keyword on a 

PDNGRP statement. The last logical channel number must be greater than or 

equal to the first logical channel number. Initialization has been completed, but 

the VCGRP parameter was ignored. Register R10 contains the STE index of 

the PDNGRP statement on which the error occurred. 

2006 An unknown virtual circuit type is specified for a VCGRP keyword on a PDNGRP 

statement. Initialization has been completed, but the VCGRP parameter was 

ignored. Register R10 contains the STE index of the PDNGRP statement on 

which the error occurred. 

2007 A configuration access (CFACCS) read error has occurred. Register 10 (R10) 

contains the CFACCS error code (SB$CAERR). 

2008 A configuration access (CFACCS) write error occurred. Initialization is 

complete; however, register 10 (R10) contains the CFACCS error code 

(SB$CAERR). Register 12 (R12) contains the STE index of the table being 

updated. 

2009 Maximum number of DTE statements has been exceeded. 

200A The ABBRVADR option was specified on a DTE statement that references a 

DTETYPE statement defining a Level 4 parameter of PDNTRUNK, PDNDXA, 

PDNUNIX, PDNX28, or PLS. This is not a valid configuration. Initialization has 

been completed, but the ABBRVADR option was ignored on the DTE statement. 

200B A DTE statement references a TRUNK statement that is also being referenced 

by another compatible network service such as a LAN link (SAP statement). 

2100 The logical channel range specified on the DTE statement PERMVC parameter 

is not within the logical channel range specified on the VCGRP parameter on 

the PDNGRP statement that functions as the DTE statement’s parent. 

4000 There is no one-to-one correspondence between LINE and PDNGRP statements. 

Either no LINE statement or more than one LINE statement references a 


B–2 7436 0728–303

Appendix C 

X.25 PSCS Cause Codes 

X.25 cause codes information and tables in this appendix originate from the following 

specifications: 

• Recommendation X.25, defined by the International Telecommunications 

Union/Telecommunications Standardization Sector (ITU/TSS), formerly the 

Consultative Committee for International Telegraph and Telephone (CCITT) 

• International Standards Organization (ISO) 8208 

• Public Data Networks Interfaces 

Cause codes are reported by: 

• The layer 3/4 platform interface 

• The packet layer services (PLS) Host interface 

• Directly attached X.25 DTE (DAD) devices 

• Packet Switched Public Data Networks (PDNs) 

The following generate cause codes: 

• The PDN to which the DCP is attached 

• The DCE Network Feature 

• A DTE that is attached to the network either directly or across the network 

7436 0728–303 C–1


Clear Packets 

Table C–1 contains cause codes related to clear packets and should be referred to by all 

PSCS generated CENLOG events whose description is for clear packets. In the 

description of the CENLOG, Register R10 contains the code listed in Table C–1. 

DTE originated 

DTE originated * 

Table C–1. Clear Packet Cause Codes 

Cause Code 

Number busy 

Out of order 

Remote procedure error 

Reverse charging acceptance not subscribed † 

Incompatible destination 

Fast select acceptance not subscribed † 

Ship absent ‡ 

Invalid facility request 

Access barred 

Local procedure error 

Network congestion 

Not obtainable 

RPOA out of order † 

Gateway-detected Procedure Error 

Gateway congestion 

Decimal Hex 

0 

>128 & 

80 & 

Reset Packets 


Table C–2 contains cause codes related to reset packets and should be referred to by all 

PSCS generated CENLOG events whose description is for reset packets. In the 

description of the CENLOG, Register R10 contains the code listed in this table. 

DTE originated 

DTE originated * 

Out of order † 

Remote procedure error 

Local procedure error 


Remote DTE operational † 

Network operational † 

Incompatible destination 

Network out of order † 

Gateway-detected procedure error 

Gateway congestion 

Gateway operational † 

Table C–2. Resetting Cause Codes 

Cause Code 

Decimal Hex 

7436 0728–303 C–3 

0 

>128 

* When the most significant bit is set, the remaining bits are those indicated by the remote DTE in the 

resetting cause field (virtual calls and permanent virtual circuits) of the reset packet. 

† Applicable to permanent virtual circuits only. 

1 

3 

5 

7 

9 

15 

17 

29 

193 

195 

199 

0 

>80 

1 

3 

5 

7 

9 

F 

11 

1D 

C1 

C3 

C7


Restart Packets 

Table C–3 shows the coding of the restarting cause field in the restart indication packets. 

In the description of the CENLOG, Register R10 contains the code listed in the following 

table. 

Table C–3. Restarting Cause Field Coding 

Cause Code 

Decimal Hex 

Local procedure error 1 1 


Network operational 

Registration/cancellation confirmed * 

DTE originated 0 or 128 0 or 80 

C–4 7436 0728–303 

3 

7 

127 

* Can be received only if the optional online facility registration facility is used. 

3 

7 

7F

Appendix D 

Sense Data 

The IBM sense code descriptions in this section are used with the permission of 

International Business Machines Corporation. This section also provides information on 

sense data specific to Unisys. 

SNA sense data is a four-byte field consisting of two bytes of sense code and two bytes of 

sense code specific information (see Table D–1). The two-byte sense code consists of a 

one-byte category and a one-byte modifier. The information presented in this section is 

concerned only with the sense code. For sense code specific information, refer to the 

appropriate IBM documentation. 

Table D–1. Sense Data Format 

Byte 0 Byte 1 Byte 2 Byte 3 

Category Modifier Sense code 

specific 

Sense Code Sense Data 

7436 0728–303 D–1

Sense Data 

Sense Data Conditions 

D–2 

The following conditions create sense data: 

• Exception request 

• Negative response 

• UNBIND request 

• Sense data (X'7D') MS common subvector 

• Function management header type 7 (FMH-7) 

• Extended sense data control vector (X'35') 

• SNA report code 

Sense Data Categories 

Table D–2. Sense Data Categories 

Value Category 

X‘00’ User Sense Data Only (cannot be used on LU 6.2 sessions) 

X‘01’ Unisys Request Reject 

X‘08’ Request Reject 

X‘10’ Request Error 

X‘20’ State Error 

X‘40’ Request Header (RH) Usage Error 

X‘80’ Path Error 

7436 0728–303

Unisys Internal Sense Data 

Sense Data 

The SNA/net EPU2 utilizes the Telcon Critical Event Notification and Logging (CENLOG) 

mechanism to log critical events or errors detected by the Telcon or SNA/net systems. 

Register R8 contains the supplemental event code and Register R9 contains sense data. 

R8 and R9 are displayed via the “long” option. 

The following supplemental event code categories are assigned: 

Table D–3. Supplemental Event Code Categories 

Category Name Event Code 

Path control X'0000' to X'0FFF' 

Transmission control X'1000' to X'1FFF' 

Data flow control X'2000' to X'2FFF' 

PU services X'3000' to X'3FFF' 

LU services X'6000 to X'6FFF' 

Application X'8000' to X'8FFF' 

Pass-through X'9400' to X'94FF' 

The supplemental codes are as follows: 

Table D–4. Supplemental Codes 

Code Description 

0001 PC dispatch error 

0002 Input error to PC 

0003 PC emergency queue error 

0004 Path selector initialization error 

0005 LU list initialization error 

0006 LU list initialization error 

0007 Path selection error 

0008 NRCB services error 

1001 Oversize RU received and discarded 

1002 Telcon rejected and discarded message 

1003 Unexpected response received and discarded 

1004 PC rejected and discarded message 

2003 Normal send request overflow 

2004 Normal receive request overflow 

7436 0728–303 D–3

Sense Data 

D–4 



2005 Expedited send request overflow 

2006 Expedited receive request overflow 

3001 Output to Telcon no ACB (session) active 

3002 Invalid message 

3003 Invalid ACB 

3004 Invalid NRCB 

3005 Output to Telcon rejected 

3006 Request already outstanding 

3007 NRCB segment load failed 

3008 Application queue full 

3009 PC rejected message 

3010 Received -RSP to ACT PU/LU 

3011 Configuration access error 

3012 Invalid procedure call 

3013 Sent -RSP to request 

3014 No destination name on connect 

3100 Up PU/LU complete 

3101 Up PU/LU failed 

3102 Down PU/LU complete 

3103 Down PU/LU failed 

6001 Invalid message discarded 

6002 Invalid information field 

6003 Response rejected 

6004 Invalid request rejected 

6005 Invalid response rejected 

6006 LU-LU session inactive 

6007 PST usage error 

8001 Send check (SNA defined) 

8002 Send check (SNA Gateway defined) 

8003 Receive check (SNA defined) 

8004 Receive check (SNA Gateway defined) 

8005 Exception request 

7436 0728–303



8006 Received -RSP 

8007 Build ACB error 

8008 Delete ACB error 

8009 Error return on Telcon session connect 

800A Error return on Telcon session send 

800B Error return on Telcon session disconnection 

800C Error return on open SNA session 

800D Error return on close SNA session 

800E Error return on status SNA session 

8010 Error on Telcon control message 

8011 Invalid data assurance response 

8012 Invalid DFC signal 

8013 Received data discarded 

8014 Received SSCP-LU data when DCA session closed 

8015 Received UDM from DCA session 

8016 Received session outage abort on SNA session 

8017 INT-1 protocol violation 

Sense Data 

8018 Received Telcon message other than connect when no ACB exists 

8019 Invalid signal 

801A Invalid SNA session control request 

801B Invalid DFC request 

801C Unsupported RU category 

801D Received connect reject 

801E Bind rejected 

9401 Connect received, LU not active 

9402 Received SNA message without ACB 

9403 Telcon send check 

9404 Invalid signal 

9405 Cannot load NRCB 

9406 SNA send check 

9407 Sent RSP to request 

9408 Configuration error 

7436 0728–303 D–5

Sense Data 

Request Reject (Category X'01') 

D–6 

The following is a list of pseudo-SNA sense data for SNA/net components. 

Note: The following sense data may display in CENLOGs. 

Sense code category X'01' is not used in the current SNA definition, therefore it is used in 

the following Unisys SNA/net EPU2 component defined sense codes. In the event that 

sense code category X'01' is used by a future SNA definition, HU$SKDEF is to be set in 

conjunction with HY$SXSH$ whenever the sense code is an SX$ value. The sense code is 

in hexadecimal. The sense code modifier values are allocated as follows: 

MACRO INTERFACE (AP/SNA) X'00 thru X'0F' 

PATH CONTROL X'10' thru X'1F' 

TRANSMISSION CONTROL X'20' thru X'3F' 

DATA FLOW CONTROL X'40 thru X5F" 

LU SERVICES X'60 thru X'7F' 

0100 MACRO INTERFACE (AP/SNA) 

0100 INVALID VALUE IN SA$SNAOP 

0101 REQUEST ALREADY OUTSTANDING 

0102 INVALID NRCB-ID ON SENDSNA 

0110 PATH CONTROL 

0110 UNABLE TO QUEUE ITEM (NO NRCB) 

0120 TRANSMISSION CONTROL 

0120 UNABLE TO LOAD THE SECB SEGMENT (SUSPST FAIL - CALLER NOT 

AUTHORIZE) 

0121 UNABLE TO LOAD THE SECB SEGMENT ( SUSPST FAIL - INVALID DSSN) 

0122 SECB VALIDITY CHECK FAIL (CONTENTS OF SE$SECBV NE TO THE 

SE$SECBI VALUE) 

0123 INVALID SIGNAL 

7436 0728–303

Sense Data 

0140 DATA FLOW CONTROL 

0140 UNABLE TO LOAD THE SECB SEGMENT (SUSPST FAIL CALLER NOT 

AUTHORIZE) 

0141 UNABLE TO LOAD THE SECB SEGMENT ( SUSPST FAIL - INVALID 

DSSN) 




0144 UNABLE TO PUT AP'S INPUT QUEUE INTO DFC'S QL DURING 

DFQSAV LOGIC (SUSPST FAIL - CALLER NOT AUTHORIZED) 

0145 UNABLE TO PUT AP'S INPUT QUEUE INTO DFC'S QL DURING 

DFQSAV LOGIC (SUQPL FAIL - INVALID QCTX) 

0152 ENTRY NOT FOUND IN CT-RCV-RQ-NORM FOR THE NORM RSP BEING 

SENT 

0153 ENTRY NOT FOUND IN CT-RCV-RQ-NORM FOR THE EXP RSP BEING 

SENT 

0154 

0155 NOT ALLOWED TO SEND MORE THAN ONE RSP TO THE SAME CHAIN 

0156 NOT ALLOWED TO CHANGE THE SNC WHEN SENDING A NEG RSP 

0157 NOT ALLOWED TO SEND RESPONSES OUT OF ORDER WHEN IN 

IMMEDIATE RESPONSE MODE 

0158 NOT ALLOWED TO SEND A CHASE UNTIL RESPONSES TO ALL 

REQUESTS RECEIVED PRIOR TO THE CHASE HAVE BEEN SENT 

0159 UNABLE TO LOAD THE SECB SEGMENT (SUSPST FAIL-CALLER NOT 

AUTHORIZED) 

0160 LU SERVICES 

0160 UNABLE TO LOAD THE SECB SEGMENT (SUSPST FAIL-CALLER NOT 

AUTHORIZED) 

0161 UNABLE TO LOAD THE SECB SEGMENT (SUSPST FAIL-INVALID 

DSSN) 




0164 MSG NOT BIND REQUEST 

0165 MSG NOT SNA FORMAT 

0166 INVALID CALL PARAMETER 

0167 ACB DOES NOT EXIST 

7436 0728–303 D–7

Sense Data 

IBM/Unisys Request Reject (Category X'08') 

D–8 

Indicates that the request was delivered to the intended component and was understood 

and supported, but not executed. 

The sense code is in hexadecimal. 

0801 Resource Not Available. The LU, PU, station, or link specified in an RU is not 

available. 

0802 Intervention Required. Forms or cards are required at an output device, or a 

device is temporarily in local mode, or other conditions require intervention. 

0803 Missing Password. The required password was not supplied. 

0804 Invalid Password. Password was not valid. 

0805 Session Limit Exceeded. The requested session cannot be activated because 

one of the NAUs is at its session limit. For example, the LU–LU session limit or 

the (LU, mode) session limit. This sense code applies to ACTCDRM, INIT, 

BIND, and CINIT requests. 

0806 Resource Unknown. For example, the request contained a name or address not 

identifying a PU, LU, SSCP, link, or link station known to the receiver or the 

sender. 

In an interconnected network environment, this sense code may be set by an 

SSCP in whose subnetwork and domain the LU was expected to reside; it is not 

set by an SSCP that is only an intermediary on the session-setup path. A 

gateway SSCP examines the Resource Identifier control vector in a sessionsetup 

request (for example, CDINIT) to determine whether the LU is in the 

SSCP's subnetwork and domain. 

0807 Resource Not Available–LUSTAT Forthcoming. A subsidiary device will be 

unavailable for an indeterminate period of time. LUSTAT is sent when the 

device becomes available. 

0808 Invalid Contents ID. The contents contained on the ACTCDRM request was 

found to be invalid. 

0809 Mode Inconsistency. The requested function cannot be performed in the 

present state of the receiver. 

080A Permission Rejected. The receiver has denied an implicit or explicit request of 

the sender. 

When sent in response to BIND, it implies either that the secondary LU will not 

notify the SSCP when a BIND can be accepted or that the SSCP does not 

recognize the NOTIFY vector key X'0C'. (See the X'0845' sense code for a 

contrasting response.) 

7436 0728–303

Sense Data 

080B Bracket Race Error. Loss of contention within the bracket protocol. This error 

can arise when bracket initiation/termination by both NAUs is allowed. 

080C Procedure Not Supported. A procedure (Test, Trace, IPL, REQMS type, MS 

major vector key) specified in an RU is not supported by the receiver. 

080D NAU Contention. A request to activate a session was received while the 

receiving half-session was awaiting a response to a previously sent activation 

request for the same session. For example, the SSCP receives an ACTCDRM 

from the other SSCP before it receives the response for an ACTCDRM that is 

sent to the other SSCP and the SSCP ID in the received ACTCDRM was less 

than or equal to the SSCP ID in the ACTCDRM previously sent. 

080E NAU Not Authorized. The requesting NAU does not have access to that 

requested resource. 

080F End User Not Authorized. The requesting end user does not have access to the 

requested resource. 

0810 Missing Requester ID. The required requester ID was missing. 

0811 Break. Asks the receiver of this sense code to terminate the present chain with 

CANCEL or with an FMD request carrying EC. The half-session sending the 

Break sense code enters chain-purge state when Break is sent, the half-session 

receiving the Break sense code discards the terminated chain without 

retransmitting it. 

0812 Insufficient Resource. Receiver cannot act on the request because of a 

temporary lack of resources. 

0813 Bracket Bid Reject — No RTR Forthcoming. BID (or BB) was received while 

the first speaker was in the in-bracket state or while the first speaker was in the 

between-brackets state and the first speaker denied permission. RTR is not 

sent. 

0814 Bracket Bid Reject — RTR Forthcoming. BID (or BB) was received while the 

first speaker was in the in-bracket state or while the first speaker was in the 

between-brackets state and the first speaker denied permission. RTR will be 

sent. 

0815 Function Active. A request to activate a network element or procedure was 

received, but the element or procedure was already active. 

0816 Function Inactive. A request to deactivate a network element or procedure 

was received, but the element or procedure was not active. 

0817 Link or Link Resource Inactive. A request requires the use of a link or link 

resource that is not active. 

0818 Link Procedure in Process. CONTACT, DISCONTACT, IPL, or other link 

procedure in progress when a conflicting request was received. 

7436 0728–303 D–9

Sense Data 

D–10 

0819 RTR Not Required. Receiver of Ready to Receive has nothing to send. 

081A Request Sequence Error. Invalid sequence of requests. 

081B Receiver in Transmit Mode. A race condition exists: a normal-flow request was 

received while the half-duplex contention state was not-receive, (*S, ¬R), or 

while resources (such as buffers) necessary for handling normal-flow data 

were unavailable. (Contrast this sense code with X'2004', which signals a 

protocol violation.) 

081C Request Not Executable. The requested function cannot be executed because 

of a permanent error condition in the receiver. 

081D Invalid Station/SSCP ID. The station ID or SSCP ID in the request was found to 

be invalid. 

081E Session Reference Error. The request contained reference to a half-session 

that either could not be found or was not in the expected state (generally 

applies to network services requests). 

081F Reserved. 

0820 Control Vector Error. Invalid data for the control vector specified by the target 

network address and key. 

0821 Invalid Session Parameters. Session parameters were not valid or not 

supported by the half-session whose activation was requested. 

0822 Link Procedure Failure. A link-level procedure has failed due to link equipment 

failure, loss of contact with a link station, or an invalid response to a LINK 

command. (This is not a path error because the request being rejected was 

delivered to its destination.) 

0823 Unknown Control Vector. The control vector specified by a network address 

and key is not known to the receiver. 

0824 Logical Unit of Work Aborted. The current unit of work has been aborted; 

when sync point protocols are in use, both sync point managers are to revert to 

the previously committed sync point. 

0825 Component Not Available. The LU component (a device indicated by an FM 

header) is not available. 

0826 FM function not supported. A function requested in an FMD RU is not 

supported by the receiver. 

0827 Intermittent Error — Retry Requested. An error at the receiver caused an RU 

to be lost. The error is not permanent. Retry or the RU (or chain) is requested. 

0828 Reply Not Allowed. A request requires a normal-flow reply, but the outbound 

data flow for this half-session is quiesced or shut down. There is no delayed 

reply capability. 

7436 0728–303

Sense Data 

0829 Change Direction Required. A request requires a [00ff] 20 normal-flow reply, 

but the half-duplex flip-flop state (of the receiver of the request) is not-send, 

and CD was not set on the request. There is no delayed reply capability. 

082A Presentation Space Alteration. Presentation space altered by the end user 

while the half-duplex state was not-send, (¬S,*R); request executed. 

082B Presentation Space Integrity Lost. Presentation space integrity lost (for 

example, cleared or changed) because of a transient condition. For example, 

because of a transient hardware error or an end user action such as allowing 

presentation services to be used by the SSCP. 

Note: The end-user action described under X'082A' and X'084A' is 

excluded here. 

082C Resource-Sharing Limit Reached. The request received from an SSCP was to 

activate a half-session, a link, or a procedure when that resource was at its 

share limit. 

082D LU Busy. The ILU resources needed to process the request are being used; for 

example, the LU resources needed to process the request received from the 

SSCP are being used for the LU–LU session. 

082E Intervention Required at LU Subsidiary Device. A condition requiring 

intervention, such as out-of-paper, power-off, or cover interlock open exists at 

a subsidiary device. 

082F Request Not Executable because of LU Subsidiary Device. The requested 

function cannot be executed because of a permanent error condition in one or 

more of the receiver's subsidiary devices. 

0830 Sessions-Related Identifier Not Found. The receiver could not find a 

session-related identifier for a specified session. 

0831 LU Component Disconnected. An LU component is not available because of 

power-off or some other disconnecting condition. 

0832 Invalid Field Count. A count field contained in the request field indicates a 

value too long or too short to be interpreted by the receiver or the count field is 

inconsistent with the length of the remaining fields. 

0833 Invalid Parameter (with Pointer and Complemented Byte). One or more 

parameters contained in fixed- or variable-length fields of the request are 

invalid or not supported by the NAU that received the request. 

This sense code is not used for a BIND error because the displacement of fields 

within the BIND may not be the same at both ends of a session when the BIND 

was affected by name transformations; for example, after the BIND has passed 

through a gateway. Sense code X'0835' is used to specify a displacement for a 

BIND error. 

7436 0728–303 D–11

Sense Data 

D–12 

0834 RPO Not Initiated. A power-off procedure for the specified node was not 

initiated because one or more other SSCPs have contacted the node or because 

a CONTACT, DUMP, IPL, or DISCONTACT procedure is in progress for that 

node. 

0835 Invalid Parameter (with Pointer Only). The only request contained a fixed- or 

variable-length field whose contents are invalid or not supported by the NAU 

that received the request. 

This sense code is not used to report an invalid value in an MS major vector. If 

the invalid value occurs in a formatted MS subvector, sense code X'086B' is 

used. If it occurs in an unformatted subvector, sense code X'0870' is used. 

0836 PLU/SLU Specification Mismatch. For a specified LU–LU session, both the 

origin LU (OLU) and the destination LU (DLU) have only the primary capability 

or have only the secondary capability. 

0837 Queuing Limit Exceeded. For an LU–LU session initiation request (INIT, 

CDINIT, or INIT-OTHER-CD) specifying an initiate or queue (if initiate not 

possible) or a queue only, the queuing limit of either the OLU or the DLU, or 

both, was exceeded. 

0838 Request Not Executable Because of Resource or Component State 

Incompatibility. The request is not executable because it is not compatible 

with the state of a resource component in the receiver. 

One or more reported token strings are used to identify these changes when 

the report code is carried in an SNA condition report. 

0839 LU–LU Session Being Taken Down or LU being Deactivated. 

083A LU Not Enabled. At the time an LU–LU session initiation request is received at 

the SSCP, at least one of the two LUs although having an active session with its 

SSCP, is not ready to accept CINIT or BIND requests. 

083B Invalid PCID. The received PCID for a new session duplicated the PCID 

assigned to another session or the received PCID intended as an identifier for 

an existing session could not be associated with such an existing session. 

083C Domain Takedown Contention. While waiting for a response to a CDTAKED, a 

CDTAKED request is received by the SSCP containing the SSCP–SSCP primary 

half-session. Contention is resolved by giving preference to the CDTAKED sent 

by the primary half-session. 

083D Dequeue Retry Unsuccessful — Removed from Queue. The SSCP cannot 

successfully honor a CDINIT (Dequeue) request (which specifies “leave on 

queue if dequeue-retry is unsuccessful”) to dequeue and process a previously 

queued CDINIT request (for example, because the LU in its domain is still not 

available for the specified session), and removes the queued CDINIT request 

from its queue. 

083E Reserved. 

7436 0728–303

Sense Data 

083F Terminate Contention. While waiting for a response to a CDTERM, a CDTERM 

is received by the SSCP of the SLU. Contention is resolved by giving 

preference to the CDTERM sent by the SSCP of the SLU. 

0840 Procedure Invalid for Resource. The named RU is not supported in the 

receiver for this type of resource. For example, SETCV specifies boundary 

function support for a type 1 node, but the capability is not supported by the 

receiving node or the PU receiving an EXECTEST or TESTMODE is not the 

primary PU for the target link. 

0841 Duplicate Network Address. In an LU–LU session initiation request, one of the 

specified LUs has a duplicate network address already in use. 

0842 Session Not Active. 

0843 Required Synchronization Not Supplied. For example, a secondary LU (LU 

type 2 or 3) received a request with Write Control Code = Start Print, along 

with RQE and ¬CD. 

0844 Initiation Dequeue Contention. While waiting for a response to a CDINIT 

(Dequeue), a CDINIT (Dequeue) is received by the SSCP of the SLU. 

Contention is resolved by giving preference to the CDINIT (Dequeue) sent by 

the SSCP of the SLU. 

0845 Permission Rejected — SSCP Will Be Notified. The receiver has denied an 

implicit or explicit request of the sender. When sent in response to BIND, it 

implies that the secondary LU will notify the SSCP (via NOTIFY vector key X 

'OC') when a BIND can be accepted and the SSCP of the SLU supports the 

notification. (See the X'080A' sense code for a contrasting response.) 

0846 ERP Message Forthcoming. The received request was rejected for a reason to 

be specified in a forthcoming request. 

0847 Restart Mismatch. Sent in response to STSN, SDT, or BIND to indicate that the 

secondary half-session is trying to execute a resynchronizing restart, but has 

received insufficient or incorrect information. 

0848 Cryptography Function Inoperative. The receiver of a request was not able to 

decipher the request because of a malfunction in its cryptography facility. 

0849 User Names Lost. An exception condition has resulted in the loss of user 

names associated with the identified message unit. 

084A Presentation Space Alteration. The presentation space specified was altered by 

the end user while the half-duplex state was not-send, (¬S,*R); request not 

executed. 

084B Requested Resources Not Available. Resources named in the request, and 

required to honor it, are not currently available. It is not known when the 

resources will be made available. 

7436 0728–303 D–13

Sense Data 

D–14 

084C Permanent Insufficient Resource. Receiver cannot act on the request because 

resources required to honor the request are permanently unavailable. The 

sender should retry immediately because the situation is not transient. 

084D Retired. 

084E Invalid Session Parameters — PRI. A positive response to an activation request 

(for example, BIND) was received and was changed to a negative response 

because of invalid session parameters carried in response. The LU receiving 

the response will send a deactivation request for the corresponding session. 

084F Resource Not Available. A requested resource is not available to service the 

given request. 

0850 Link-Level Operation Cannot be Performed. An IPL, dump, or RPO cannot be 

performed through the addressed link station because the system definition or 

current state of the hardware configuration does not allow it. 

0851 Session Busy. Another session that is needed to complete the function being 

requested on this session is temporarily unavailable. 

0852 Duplicate Activation Request. Two session activation requests have been 

received with related identifiers. The relationship of the identifiers and the 

resultant action varies by request. 

0853 TERMINATE (Cleanup) Required. The SSCP cannot process the termination 

request because it requires cross-domain SSCP–SSCP services that are not 

available. (The corresponding SSCP–SSCP session is not active.) TERMINATE 

(Cleanup) is required. 

0854 Retired. 

0855 Reserved. 

0856 SSCP–SSCP Session Lost. Carried in the Sense Data field in a NOTIFY 

(Third-Party Notification vector, X'03') or -RSP(INIT_OTHER) sent to an ILU to 

indicate that the activation of the LU–LU session is uncertain because the 

SSCP(ILU)-SSCP(OLU) session has been lost. (Another sense code, X'0842', is 

used when it is known that the LU–LU session activation cannot be 

completed.) 

0857 SSCP–LU Session Not Active. The SSCP–LU session, required for the 

processing of a request, is not active. For example, in processing REQECHO, 

the SSCP did not have an active session with the target LU named in the 

REQECHO RU. 


0859 REQECHO Data Length Error. The specified length of data to be echoed (in 

REQECHO) violates the maximum RU size limit for the target LU. 

7436 0728–303

Sense Data 

085A Specific Server Exception. An architecturally defined or customer-defined 

server that is sensitive to data object contents has detected an exception. 

085B Unknown Resource Name. The identified resource, required to complete the 

requested unit-of-work, is not known to the SNA node. 

085C System Exception. The node experiences an exception condition within a 

resident system or subsystem that inhibits subsequent processing by the SNA 

component. 

085D The MU ID could not be accepted in the MU_ID registry. 

085E Operator Intervention. 


0860 Function Not Supported–Continue Session. The function requested is not 

supported; the function may have been specified by a request code or some 

other field, control character, or graphic character in an RU. 

0861 Invalid COS Name. The class of service (COS) name, either specified by the 

ILU or generated by the SSCP of the SLU from the mode table is not in the 

“COS name to VR identifier list” table used by the SSCP of the PLU. 

0862 Medium Presentation Space Recovery. An error has occurred on the current 

presentation space. Recovery consists of restarting at the top of the current 

presentation space. The sequence number returned is of the RU in effect at the 

top of the current presentation space. 

0863 Referenced Local Character Set Identifier (LCID) Not Found. A referenced 

character set does not exist. 

0864 Function Abort. The conservation was terminated abnormally. Other 

terminations may occur after repeated reexecutions; the request sender is 

responsible to detect such a loop. 

0865 Retired. 

0866 Retired. 

0867 Sync Event Response. Indicates a [00ff]20 required negative response to an 

(RQE,CD) synchronizing request. 

0868 No Panels Loaded. Referenced format not found because no panels are loaded 

for the display. 

0869 Panel Not Loaded. The referenced panel is not loaded for the display. 

086A Subfield Key Invalid. A subfield key in an MS subvector was not valid in the 

conditions under which it was processed. 

7436 0728–303 D–15

Sense Data 

D–16 

086B Subfield Value Invalid. A value in the subfield within an MS major vector was 

invalid for the receiver. 

See sense code X'0870' for the case in which the invalid value occurs in an 

unformatted subvector; that is, one not containing subfields with keys and 

lengths, or in the unformatted portion of a partially formatted subvector. 

086C Required Subvector Missing. One or more MS subvectors that are required by 

the receiver to perform some function are missing from the received list of 

subvectors or are not present in the required position. 

086D Required Subfield Missing. An MS subvector lacks one or more subfield keys 

that are required by the receiver to perform the function requested. 

086E Invalid Subvector Combination. Two or more subvectors, each permissible by 

itself, are present in a combination that is not allowed. 

086F Length Error. A length field within an MS major vector is invalid or two or 

more length fields are incompatible. 

0870 Unformatted Subvector Value Invalid. A value is an unformatted MS subvector 

or, in an unformatted portion of a partially formatted MS subvector, is invalid. 

See sense code X'086B' for the case in which the invalid value occurs in 

formatted MS subvector; that is, one containing subfields with keys and 

lengths, or in the formatted portion of a partially formatted subvector. 

0871 Read Partition State Error. A Read Partition structured field was received 

while the display was in the retry state. 

0872 Explicit or Implied Orderly Deactivation Refused. 

0873 Virtual Route Not Defined. No ERN designated to support this VRN. 

0874 ER Not in a Valid State. The ER supporting the requested VR is not in a state 

allowing VR activation. 

0875 Incorrect or Undefined Explicit Route Requested. The reverse ERNs specified 

in the NC-ACTVR do not contain the ERN defined to be used for the VR 

requested or the ERN designated to be used for the VR is not defined. 

0876 Nonreversible Explicit Route Requested. The ERN used by the NC-ACTVR 

does not use the same sequence of transmission groups (in the reverse order) 

as the ERN that should be used for the RSP (NC-ACTVR). 

0877 Resource Mismatch. The receiver of a request has detected a mismatch 

between two of the following: its definition of an affected resource, the actual 

configuration, or the definition of the resource as implied in the request. 

0878 Insufficient Storage. The storage resource required for a data format is not 

available. 

7436 0728–303

Sense Data 

0879 Storage Medium Exception. An exception has occurred involving a storage 

medium. 

087A Format Processing Error. A processing error has occurred during data 

formatting. 

087B Resource Unknown. The request contains a session key that does not identify 

a session known to some gateway node; for example, a session activation 

request arrives at a gateway node after it has released the address transform 

for the intended session. 

087C SSCP–PU Session Not Active. A gateway SSCP–PU session that is needed to 

establish an address transform for the intended cross-network LU–LU session 

was not active. 

087D Session Service Path Error. A session services request cannot be rerouted 

along a path of SSCP–SSCP sessions. This capability is required, for example, 

to set up a cross-network LU–LU session. 

087E SSCP Visit Count Exceeds Limit. The SSCP visit count specified in the session 

service request-CDINIT, INIT_OTHER_CD, or DSRLST- has been decremented 

to 0. The session services request has been routed through an excessive 

number of SSCPs. (The SSCPs are not necessarily distinct.) 



0881 ACTDRM Failure–REQACTCDRM Sent. An SSCP–SSCP session-activation 

request, ACTCDRM, cannot be rerouted to a gateway SSCP because, at some 

gateway PU, the necessary transform is not complete and the gateway PU has 

sent REQACTCDRM to the gateway SSCP. 



0884 ACTCDRM Failure–No REQACTCDRM Sent. An SSCP–SSCP session activation 

request, ACTCDRM, cannot be rerouted to the destination SSCP because, at 

some gateway node PU, the necessary transform is not complete and 

REQACTCDRM cannot be sent to the destination SSCP because the gateway 

SSCP–PU session is not active or the intended SSCP session partner does not 

provide gateway services. 


0886 Subnetwork Rerouting Not Supported. An SSCP received a session services 

request–CDINIT, INIT_OTHER_CD, NOTIFY (Vector Key=X'01'), or DSRLST 

from an SSCP in its subnetwork that, if rerouted, would not cross a subnetwork 

boundary. The SSCP does not support rerouting within a subnetwork. 

7436 0728–303 D–17

Sense Data 

D–18 

0887 Dequeue Retry Unsuccessful — Session Remains Queued. The SSCP cannot 

successfully honor CDINIT (Dequeue) request. The request specifies “leave on 

queue if dequeue-retry is unsuccessful.” The SSCP has left the queued session 

on its queue. 

0888 Name Conflict. A name specified in an RU is unknown, or is known and does 

not have the required capabilities, or is a duplicate resource for the specified 

resource type. When a name conflict is detected, further name checking 

ceases; multiple name conflicts are not reported or detected. 

0889 Transaction Program Error. The transaction program has detected an error. 

088A Resource Unavailable — NOTIFY Forthcoming. The SSCP cannot satisfy the 

request because a required resource is temporarily unavailable. When the 

required resource becomes available, NOTIFY NS(s) key X'07' or X'08' will be 

sent. 

088B BB Not Accepted — BIS Reply Requested. Sent in response to a BB (either an 

LUSTAT bid or an Attach) to indicate that the receiver has sent a BIS request 

and wishes to terminate the session without processing any more 

conversations, but without sending an UNBIND. A BIS reply is requested so 

that the negative response sender may send a normal UNBIND. This sense 

code is sent only by LUs not supporting change-number-of-session protocols. 

088C Missing Control Vector. The RU did not contain a control vector that was 

expected to appear. 

088D Duplicate Network Name. An SSCP has detected a violation of the requirement 

that the network names used across multiple domains be unique within the 

multiple-domain network. For example, the SSCP (DLU) has detected that the 

OLU received in CDINIT is currently also defined in the domain of the SSCP 

(DLU). 

088E Capability Mismatch. A network component detected a capability mismatch 

between different resources involved in the same network function. For 

example, an SSCP detects that an LU has been assigned a subarea address too 

large for one of the other resources involved in the session initiation to 

support. 

088F XRF Procedure Error. A request was received for an XRF-active or 

XRF-backup session and was not acted on. 


0891 Invalid Network ID (NETID). 

0892 Automatic network shutdown (ANS) has occurred. 

0893 Takeover Not Complete. 

7436 0728–303

Sense Data 

0894 Migration Support Error. The sender of the request is relying on migration 

support that is not available. Bytes 2 and 3 may contain the following sense 

code specific information. 

0895 Control Vector Error. The RU contained a control vector that was in error. 

0896 Control Vector Too Long. 

0897 System Definition Mismatch. The requested function is not supported by the 

receiver, or there is a mismatch between the sending and receiving system 

definitions. 

0898 Session Reset. The XRF session is being reset. 

0899 Invalid Address. An address modifying a control function is invalid or outside 

the range allowed by the receiver. 

089A Invalid File or File Not Found. The requested file was not found or was found 

to be an invalid file. 

089B Session Correlation Exception. The session correlation procedure detected an 

exceptional condition at the SLU. 

089C Reserved. 

089D Gateway Node Error Detected during Cross-Network Session Initiation. 

089E Identified Data Object Already Exists. 

08A0 Session Reset. An LU or PU is resetting an LU–LU session. 

08A2 Resource Active. The requested function must be performed on an inactive 

resource but the resource is active. 

08A4 Token-Match Exception. Partial name matching is unsuccessful during the 

required find or store operation. The canonical identifier involved in the 

exception is reported in the FS server report. 

08A6 Object Not Found. An exception has occurred when the general server 

attempted to process the server object, but the server object could not be 

found. 

08FF Entered resource name cannot be found within SNA/net's own domain. ADJSA 

has not been turned on. 

7436 0728–303 D–19

Sense Data 

IBM/Unisys Request Error (Category X'10') 

D–20 

Indicates that the RU was delivered to the intended NAU component, but could not be 

interpreted or processed. This condition represents a mismatch of NAU capabilities. 


1001 RU Data Error. Data in the request RU is not acceptable to the receiving 

component. For example, a character code is not in the set supported, a 

formatted data field is not acceptable to presentation services, or a value 

specified in the length field (LL) of a structured field is invalid. 

1002 RU Length Error. The request RU was too long or too short. 

1003 Function Not Supported. The requested function is not supported. The 

function may have been specified by a formatted request code, a field in an RU, 

or a control character. 


1005 Parameter Error. A parameter modifying a control function is invalid or 

outside the range allowed by the receiver. 

1006 Required Field or Parameter is Missing. 

1007 Category Not Supported. DFC, SC, NC, or FMD request was received by a 

half-session not supporting any requests in that category, an NS request byte 0 

was not set to a defined value, or byte 1 was not set to an NS category 

supported by the receiver. 

1008 Invalid FM Header. The FM header was not understood or translatable by the 

receiver or an FM header was expected but not present. For LU 6.2, this sense 

code is sent in FMH-7 or indicated in UNBIND. 

1009 Format Group Not Selected. No format group was selected before issuing a 

Present Absolute or Present Relative Format structured field to a display. 

100A Unknown User Name. 

100B Format Exception. 

100C Unrecognized Message Unit. 

100D Request Inconsistency. The control information provided for the request is not 

consistent with other information in the request. 

100E Directing Exception. A node is unable to perform the required directing or 

redirecting function for a request as a result of insufficient directory support or 

incompatibility between TP name and presence/absence of a user name. 

100F Improper SNA/DS Usage of LU 6.2. 

7436 0728–303

Sense Data 

1011 RNAA Request Error. The RNAA is rejected because there is a mismatch 

between the sending and receiving node's system definitions or capabilities. 

1012 SNA/DS Receiver Exception MU Format Exception. Parsing or building of the 

SNA/DS Receiver Exception MU Format was unsuccessful. 

1013 Unknown Server Parameters. The specified parameters are not recognized by 

the server. 

1018 MU Sequence Exception. An SNA/DS transaction program has detected an 

improper sequence of SNA/DS MUs. 

1019 Invalid Restart Byte Position. 

7436 0728–303 D–21

Sense Data 

IBM/Unisys State Error (Category X'20') 

D–22 

Indicates a sequence number error or an RH or RU that is not allowed for the receiver's 

current session control or data flow control state. These errors prevent delivery of the 

request to the intended component. 

For LU 6.2 this category will be indicated within UNBIND or on negative response to 

BIND. 


2001 Sequence Number. Sequence number received on normal-flow request was not 

1 greater than the last. 

2002 Chaining. Error in the sequence of the chain indicator settings (BCI, ECI), such 

as first, middle, first. 

2003 Bracket. Error resulting from failure of sender to enforce bracket rules for 

session. (This error does not apply to contention or race conditions.) 

2004 Direction. Error resulting from a normal-flow request received while the 

half-duplex flip-flop state was Not Receive. 

2005 Data Traffic Reset. An FMD or normal-flow DFC request received by a 

half-session whose session activation state was active, but whose data traffic 

state was not active. 

2006 Data Traffic Quiesced. An FMD or DFC request received from a half-session 

that has QUIESCE COMPLETE or SHUTDOWN COMPLETE and has not 

responded to RELEASE QUIESCE. 

2007 Data Traffic Not Reset. A session control request (for example, STSN) allowed 

only while the data traffic state is reset, was received while the data traffic 

state was not reset. 

2008 No Begin Bracket. An FMD request specifying BBI = BB was received after the 

receiver had previously received a BRACKET INITIATION STOPPED request. 

2009 Session Control Protocol Violation. An SC protocol has been violated. A 

request, allowed only after a successful exchange of an SC request and its 

associated positive response, has been received before such a successful 

exchange has occurred (for example, an FMD request has preceded a required 

CRYPTOGRAPHY VERIFICATION request). The request code of the particular 

SC request or response required, or X'00' if determined, appears in the fourth 

byte of the sense data. 

200A Immediate Request Mode Error. The immediate request mode protocol has 

been violated by the request. 

200B Queued Response Error. The Queued Response protocol has been violated by 

a request; for example, QRI = ¬QR when an outstanding request had QRI = QR. 

7436 0728–303

Sense Data 

200C ERP Sync Event Error. The ERP sync event protocol in DFC has been violated. 

That is, after receiving a negative response to a chain, a request other than a 

request soliciting a synchronization event response was sent to DFC_SEND and 

rejected. 

200D Response Owed Before Sending Request. An attempt has been made in 

half-duplex (flip-flop or contention) send/receive mode to send a normal-flow 

request when a response to a previously received request has not yet been sent. 

200E Response Correlation Error. A response was received that cannot be 

correlated to a previously sent request. 

200F Response Protocol Error. A violation has occurred in the response protocol; 

for example, a +RSP to an RQE chain was generated. 

2010 BIS Protocol Error. A BIS protocol error was detected; for example, a BIS 

request was received after a previous BIS was received and processed. 

2011 Pacing Protocol Error. 

2012 Invalid Sense Code Received. A negative response was received that contains 

an SNA defined sense code that cannot be used for the sent request. 

7436 0728–303 D–23

Sense Data 

IBM/Unisys RH Usage Error (Category X'40') 

D–24 

Indicates that the value of a field or combination of fields in the RH violates architectural 

rules or previously selected BIND options. These errors prevent delivery of the request to 

the intended component and are independent of the current states of the session. They 

may result from the failure of the sender to enforce session rules. Detection by the 

receiver of each of these errors is optional. 


4001 Invalid SC or NC RH. The RH of a session control (SC) or network control 

(NC) request was invalid. For example, an SC RH with pacing request 

indicator set to 1 is invalid. 


4003 BB Not Allowed. The Begin Bracket indicator (BBI) was specified incorrectly; 

for example, BBI = BB with BCI = BC. 

4004 CEB and EB Not Allowed. The Conditional End Bracket indicator (CEBI) or 

End Bracket indicator (EBI) was specified incorrectly; for example, CEBI = 

CEB when ECI = ¬EC or EBI = EB with BCI = ¬BC, or by the primary 

half-session when only the secondary may send EB, or by the secondary when 

only the primary may send EB. 

4005 Incomplete RH. Transmission shorter than full TH–RH. 

4006 Exception Response Not Allowed. Exception response was requested when 

not permitted. 

4007 Definite Response Not Allowed. Definite response was requested when not 

permitted. 

4008 Pacing Not Supported. The Pacing indicator was set on a request, but the 

receiving half-session or boundary function half-session does not support 

pacing for this session. 

4009 CD Not Allowed. The Change Direction indicator (CDI) was specified 

incorrectly; for example, CDI = CD with ECI = EC or CDI = CD with EBI = EB. 

400A No-Response Not Allowed. No-response was specified on a request when not 

permitted. (Used only on EXR.) 

400B Chaining Not Supported. The chaining indicators (BCI and ECI) were specified 

incorrectly. For example, chaining bits indicate other than (BC,EC), but 

multiple-request chains are not supported for the session or for the category 

specified in the request header. 

400C Brackets Not Supported. The bracket indicators (BBI, CEBI, and EBI) were 

specified incorrectly. For example, a bracket indicator was set (BBI = BB, 

CEBI = CEB, or EBI = EB), but brackets are not used for the session. 

7436 0728–303

400D CD Not Supported. The Change-Direction indicator was set, but is not 

supported. 

400E Reserved. 

Sense Data 

400F Incorrect Use of the Format Indicator. The Format indicator (FI) was specified 

incorrectly. For example, FI was set with BCI = BC or FI was not set on a DFC 

request. 

4010 Alternate Code Not Supported. The Code Selection indicator (CSI) was set 

when not supported for the session. 

4011 Incorrect Specification of RU Category. The RU Category indicator was 

specified incorrectly. For example, an expedited-flow request or response was 

specified with RU Category indicator = FMD. 

4012 Incorrect Specification of request Code. The request code on a response does 

not match the request code on its corresponding request. 

4013 Incorrect Specification of (SDI, RTI). The Sense Data Included indicator (SDI) 

and the Response Type indicator (RTI) were not specified properly on a 

response. The proper value pairs are (SDI = SD, RTI = negative) and (SDI = 

SD, RTI = positive). 

4014 Incorrect Use of (DR1I, DR2I, ERI). The Definite Response 1 indicator (DR1I), 

Definite Response 2 indicator (DR2I), and Exception Response indicator (ERI) 

were specified incorrectly. For example, a SIGNAL request was not specified 

with DR1I = DR1, DR2I = DR2, and ERI = ER. 

4015 Incorrect Use of QRI. The Queued Response indicator (QRI) was specified 

incorrectly. For example, QRI = QR on an expedited-flow request. 

4016 Incorrect Use of EDI. The Enciphered Data indicator (EDI) was specified 

incorrectly. For example, EDI = ED on a DFC request. 

4017 Incorrect Use of PDI. The Padded Data indicator (PDI) was specified 

incorrectly. For example, PDI = PD on a DFC request. 

4018 Incorrect Setting of QRI with Bidder's BB. The first speaker half-session 

received a BB chain requesting use of a session (via LUSTAT(X'0006')), but the 

QRI was specified incorrectly; that is, QRI = QR. 

4019 Incorrect indicators with Last-In-Chain Request. A last-in-chain request has 

specified incompatible RH settings; for example, RQE*, CEBI = CEB, and CDI = 

CD. 

401A Reserved. 

through 

4020 

4021 QRI Setting in Response Different From That in Request. The QRI setting in 

the response differs from the QRI setting in the corresponding request. 

7436 0728–303 D–25

Sense Data 

IBM/Unisys Path Error (Category X'80') 

D–26 

Indicates that the request could not be delivered to the intended receiver because of a 

path outage, an invalid sequence of activation requests, or one of the listed path 

information unit (PIU) errors. Some PIU errors fall into other categories. For example, 

sequence number errors are sense code category X'20'. A path error received while the 

session is active usually indicates that the path to the session partner was lost. 


8001 Intermediate Node Failure. Machine or program check in a node providing 

intermediate routing function. A response may or may not be possible. 

8002 Link Failure. Data link failure. 

8003 NAU Inoperative. The NAU is unable to process requests or responses. For 

example, the NAU has been disrupted by an abnormal termination. 

8004 Unrecognized Destination. A node in the path has no routing information for 

the destination specified either by the SLU name in a BIND request or by the 

TH. 

8005 No Session. No half-session is active in the receiving end node for the 

indicated origination-destination pair or no boundary function session 

connector is active for the origin-destination pair in a node providing the 

boundary function. A session activation request is needed. 

8006 Invalid FID. Invalid FID for the receiving node. 

Note: It is usually not possible to send a response for this exception 

condition because information (FID, addresses) required to 

generate a response is not available. It is logged as an error if this 

capability exists in the receiver. 

8007 Segmenting Error. First BIU segment had less than 10 bytes; mapping field 

sequencing error, such as first, last, middle; or segmenting not supported and 

mapping field not set to BBIU, EBIU. 

Note: If segmenting is not supported, a negative response is returned for 

the first segment only, since this contains the RH. Subsequent 

segments are discarded. 

8008 PU Not Active. The SSCP–PU secondary half-session in the receiving node has 

not been activated and the request was not ACTPU for this half-session. For 

example, the request was ACTLU from an SSCP that does not have an active 

SSCP–PU session with the PU associated with the addressed LU. 

8009 LU Not Active. The destination address specifies an LU for which the SSCP–LU 

secondary half-session has not been activated and the request was not ACTLU. 

7436 0728–303

Sense Data 

800A Too-Long PIU. Transmission was truncated by a receiving node because the 

PIU exceeded a maximum length or sufficient buffering was not available. 

800B Incomplete TH. Transmission received was shorter than a TH. 

Note: It is usually not possible to send a response for this exception 

condition because information (FID, addresses) required to 

generate a response is not available. It is logged as an error if this 

capability exists in the receiver. 

800C DFC Error. Data Count field inconsistent with transmission length. 

800D Lost Contact. Contact with the link station for which the transmission was 

intended has been lost, but the link has not failed. If the difference between 

link failure and loss of contact is not detectable, link failure (X'8002') is sent. 

800E Unrecognized Origin. The origin address specified in the TH was not 

recognized. 

800F The address combination is invalid. 

8010 Segmented RU Length Error. An RU was found to exceed a maximum length or 

required buffer allocation that might cause future buffer depletion. 

8011 ER Inoperative or Undefined. A PIU was received from subarea node that does 

not support ER and VR protocols and the explicit route to the destination is 

inoperative or undefined. 

8012 Subarea PU Not Active or Invalid Virtual Route. A session-activation request 

for a peripheral PU or LU cannot be satisfied because there is no active SSCP– 

PU session for the subarea node providing boundary function support, or the 

virtual route for the specified SSCP–PU (type1 or type 2 nodes) or SSCP–LU 

session is not the same as that used for the SSCP–PU session of the type 1 or 

type 2 node's PU or the LU's subarea PU. 

8013 COS Not Available. A session activation request cannot be satisfied because 

none of the virtual routes requested for the session is available. 


through 

8016 

8017 PIU from Adjacent Pre-ER-VR Subarea Node Rejected. A PIU that requires 

intermediate path-control routing was received by a subarea node from an 

adjacent subarea node that does not support ER–VR protocols, but the 

receiving subarea node does not support intermediate path-control routing for 

adjacent subarea nodes that do not support ER–VR protocols. 

8018 Management Services component is unable to find or recognize the name of the 

application transaction program specified in the request. 

7436 0728–303 D–27

Sense Data 

D–28 

8019 Routing Exception. A node is unable to perform the required routing function 

for a request. 

801C Hop Count Exhausted. 

8020 Session Reset. The LU–LU session identified in the UNBIND is being 

deactivated because of a reset condition. 

7436 0728–303

Appendix E 

Acronyms and Abbreviations 

The following is a list of acronyms and abbreviations that are used throughout this 

document. 

ABS absolute element 

ACF advanced communication function 

ACK acknowledge 

ADR address 

ADRD automatic data rate detection 

AE alternate environment list 

AET alternate environment table 

ALSM asynchronous-controlled line switch module 

ALT alternate 

AS/400 Application System/400 

ASCII American Standard Code for Information Interchange 

Async LM asynchronous line module 

AUX auxiliary 

BAL basic assembly language 

BCC block check character 

BDBI LM bi-direction byte interface line module 

BIOC LM byte I/O channel line module 

BMux block multiplexor 

BN block number 

bpi bits per inch 

7436 0728–303 E–1


bps bits per second 

BSC binary synchronous communications 

CAP Communications Access Processor 

CD Communications Delivery 

CDRM cross-domain resource manager 

CDRSC cross-domain resource 

CENLOG critical event notification and logging 

CICS Customer Information Control System 

CLC Communications Line Controller 

CMS 1100 Communications Management System 1100 

CNMS Common Network Management Services 

COMPOOL communications message pool 

CP communications processor 

CPA communications processor architecture 

CPADEF communications processor architecture definition 

CRC cyclic redundancy check 

CS control station 

CT count 

CTOS Convergent Technologies operating system 

CTS conversational time sharing, clear to send (RS-232 signal) 

CUBE Cooperating Users of Burroughs Equipment 

DCA Distributed Communications Architecture 

DCP Distributed Communications Processor 

DCP/OS DCP Operating System 

DCP OSG DCP Operating System Group 

DD dual disk 

E–2 7436 0728–303


DDP-PPC Distributed Data Processing Program-to-Program Communications 

DDN Defense Data Network 

DIA Document Interchange Architecture 

DIR directory services 

DNS Dynamic Network Services 

DPS 1100 Display Processing System 1100 

DSC datastream compatible 

DSL data set label 

DTR data terminal ready (RS-232 signal) 

DVS device status 

EBCDIC extended binary coded decimal interchange code 

ELO electronic literature ordering 

ENQ enquiry 

EOM end of message signal 

EOT end of transmission 

ER explicit route 

ERP error-recovery procedure 

ESA extended subarea address 

ES end system 

ETX end of text 

EWP early warning point 

FCB file control block 

FCC field control character 

FDDI fiber distributed data interface 

FDBSC foreign domain BSC 

FEP front end processor 

7436 0728–303 E–3


FEPI LM front end processor interface line module 

FDX full duplex mode 

FTAM file transfer access and management 

FTP file transfer protocol 

GID/DID general-ID/device-ID 

GPL gated procedure list 

HBW highest block written 

HCF Host Command Facility 

HID hardware ID 

HSLLM high speed loadable line module 

HVWS host virtual workstation 

IB interface control table 

IBF inverted boundary function 

IBM International Business Machines (Corporation) 

ICT interface control table 

ICTN interface control table number 

IDF integrated flexible diskette 

ILM intelligent line module 

IMS Information Management System 

IOM input/output module 

IOP input/output processor 

IP Internet Protocol 

IPF Interactive Processing Facility 

IPL initial program load 

IPM interpartition message 

IS Information Services 

E–4 7436 0728–303

IS Intermediate System 

ISO International Organization for Standardization 

ISPF Interactive System Productivity Facility 

JCL job control language 

JES job entry subsystem 

LAN local area network 

LEN low entry networking 

LLC logical link control 

LM line module 

LMS line module status 

LRC longitudinal redundancy check 

LSEG load segment 

LSM line switch module 

LU logical unit 

LUN logical unit number 

MAC media access control 

MASM Meta-Assembler 

MCB Message Control Bank 

MCT message control table 

MDLM multiple device line module 

MHS message handling system 

MLF module library file 

MLLM multi-line line module 

MLSLM multi-line synchronous line module 

MSLLM medium speed loadable line module 

NAK not acknowledged 


7436 0728–303 E–5


NCCF Network Communications Control Facility 

NCP Network Control Program 

NFS new feature suggestion 

NIF Network Installation Facility 

NLU Network Load Utility 

NMS network management services (Telcon application) 

NMVT Network Management Vector 

NPSI Network Packet Switching Interface 

NRZ non-return to zero 

NRZI non-return to zero inverted 

NT node type 

OMN omnibus element 

OS operating system 

OS 2200 Operating System 2200 

OSI Open Systems Interconnection 

OSN office support node 

PC personal computer 

PCT program control data 

PCR primus change document 

PDN public data network 

PDT peripheral device table, physical device table 

PID process ID 

PHYSIO physical I/O 

PL/1 Programming Language/1 

PLE problem list entry 

PLM programmable line module 

E–6 7436 0728–303

PLU primary logical unit 

PN procedure number 

POC power on confidence 

PP port processor 

PPID port processor ID 

PPPT port processor program table 

PP S.I. port processor state item 

PS/2 Personal System/2 

PSCS Packet Switched Communications Software 

PST procedure segment table 

PT procedure table 

PU physical unit 

PW 2 

Q queue 

Personal Workstation 2 

QIC quarter-inch cartridge tape 

QL queue list 

QN queue number 

QT queue table 

RAM random access memory 

RBFTE Remote Batch File Transfer Extended 

RBT remote batch terminal 

RCW run control word 

RIP Routing Information Protocol 

ROM read-only memory 

RTH Real Terminal Handler 

RTS request to send (RS-232 signal) 


7436 0728–303 E–7


RU request/response unit 

RVI reverse interrupt 

SAI software attention item 

SB system base 

SCSI small computer system interface 

SCT system counter table 

SD segment descriptor 

SDF system data format 

SDFI system data format input 

SDFO system data format output 

SDLC synchronous data link control 

SDR segment descriptor register 

SDT segment descriptor table 

SEG segment 

SMTP simple mail transfer protocol 

SNA Systems Network Architecture 

SNADS SNA Distribution Services 

SNAPPC SNA Program-to-Program Communications 

SNARJE SNA Remote Job Entry 

SNASS SNA Session Services 

SNMS SNA/net Network Management Services 

SOE start-of-entry (character) 

SPEC specification 

SPS supplementary status 

SQL system queue list 

SRA Software Release Announcement 

E–8 7436 0728–303

SRN source recipient node 

SSCP system services control point 

SST system status table 

SSTDEF system status table definition 

STEP Synchronous Terminal Emulation Package 

STX start of text 

SVC service call, supervisor call 

SYM symbolic element 

Sync LM synchronous line module 

SYSINF system information 

SU00057 SU00057 host (word) channel line module 

TAF Terminal Attach Facility 

TCP Transmission Control Protocol 

TCP-IP Transmission Control Protocol/Internet Protocol 

TG transmission group 

TIP transaction processing 

TL3 test level 3 

TM terminal message 

TOMF Terminal Operator Menu Facility 

TPLM twisted pair line module 

TSO time sharing option 

TTD temporary text delay 

TTY teletype 

UCF user communication form 

UDLC universal data link control 

USE, Inc. Unisys Users Group 


7436 0728–303 E–9


USR update service request 

UTS Universal Terminal System 

UUA Unisys Users Association (Europe) 

UVT Unisys Video Terminal 

VC virtual circuit 

Video 

Text LM video text line module 

VRC vertical redundancy check 

VS virtual storage 

VST volume space table 

VTAM Virtual Telecommunications Access Method 

WAN wide area network 

WACK wait before transmit positive acknowledge 

E–10 7436 0728–303

Glossary 

A 

absolute element 

A complete program suitable for execution by the Exec operating system. Absolute 

elements normally occur as output from a collection of relocatable elements. 

AGPPER 

PP state-item (abort of the line-module software) detection and reporting in AGSYSTRN. 

AGSYSRTN 

See global common system subroutines. 

ASCII 

Acronym for American Standard Code for Information Interchange (pronounced ASKEY), 

a 7-bit character code that defines 128 standard alphanumeric characters. ASCII is an 

industry standard that defines the codes for a character set to be used for information 

interchange between equipment of various manufacturers. It is the standard for digital 

communication over telephone lines. (This term is not spelled out in Unisys 

documentation.) 

Asynchronous Balanced Mode (ABM) 

An operational mode in which either of two stations can initiate transmission without 

receiving permission from the other station. 

Asynchronous Line Switch Module (ALSM) 

A line switching device attached to an asynchronous control line. 

Automatic Data Rate Detection (ADRD) 

A Telcon feature that detects the line speed of an asynchronous terminal by sampling the 

first input character. 

B 

Binary Synchronous Communication (BSC) 

A protocol developed by IBM for synchronous transmission of binary coded data. One of 

the first protocols for transparent text transmission. Same as bisync. 

BSC 

See IBM Binary Synchronous Communication protocol. 

7436 0728–303 Glossary–1

Glossary 

BSC Transaction Interface (BSCTIF) 

A BSC half-duplex, point-to-point protocol used for host-to-host communication. BSCTIF 

can be used to transmit data between foreign computers and TIP applications within 

Unisys hosts. 

BVINPUT 

IBM BSC protocol converter for remote batch sites using the IBM 2780/3780 protocol. 

Converts input messsages in the BSC protocol to the RB2 protocol for input messages to 

CMS 1100 RB2 CSU. 

BVOUTPUT 

IBM BSC protocol converter for remote batch sites using the IBM 2780/3780 protocol. 

Converts output messages to the BSC protocol from the RB2 protocol from input 

messages from CMS 1100 RB2 CSU. 

C 

CENL 

The command used to access CENLOGs. See also CENLOG. 

CENLCOM 

See CENLOG command processor. 

CENLOG 

See critical event notification and logging. 

CENLOG Analysis Program (CAP) 

The CENLOG complex of the Telcon system provides a means of reporting and recording 

significant system events and errors for the DCP family of processors. 

Circuit-Switched Communications Software (CSCS) 

See X.21 Circuit-Switched Communications Software. 

CMS 1100 

See Communications Management System. 

CMS 1100 network 

One or more interconnected CMS 1100 nodes. Node interconnections can be direct or 

indirect. If indirect, interconnections can be through an intermediate Telcon node or 

through a TCP/IP or OSI internetwork connection. 

CMS 1100 node 

A CMS 1100 program on an OS 2200 or Series 2200 host. Each host can contain more than 

one node; each node has a separate configuration file. 

Communications Management System (CMS 1100) 

The software that manages data communication to and from OS 2200 host computers. 

CMS 1100 provides an interface between the OS 2200 and the Telcon/DCP. 

Glossary–2 7436 0728–303

COMUS 

Glossary 

Acronym for Computerized Onsite Maintenance of User System. COMUS is an OS 2200 

processor that leads you interactively through the process of defining the configuration 

and parameters for the software products you want to install. For example, after you 

define a CMS 1100 configuration, COMUS calls the symbolic stream generator, which 

creates a runstream to generate a CMS 1100 configuration file. COMUS can also initiate 

generation of the Telcon software for DCPs in your network. 

Critical Event Notification and Logging (CENLOG) 

1) A proprietary system for Telcon that collects alarms, statistics, and significant events 

for displaying on NMS consoles on various DCPs in the network or for logging into 

mass storage log files on various DCPs. 

2) The facility that allows software processes to log system and error events. Logs are in 

a standard format and can be written to a disk file cataloged for that purpose. In 

addition, warning messages are sent to network administrator consoles for critical 

events. 

D 

Data Circuit-Terminating Equipment (DCE) 

1) A PDN device, usually a packet-switching communications processor, that functions 

as a gateway to the network. It interfaces with data terminal equipment (DTE) so the 

DTE can access a network. 

2) A network switch that communicates with customer equipment (a computer or 

terminal). X.25 defines how a DCE (network equipment) communicates with a DTE 

(subscriber equipment). 

Data Link Connection Identifier (DLCI) 

A 10 bit value stored in a Frame Relay frame that identifies the destination of the frame. 

This value is preconfigured in the network to identify a given destination. Telcon Frame 

Relay must match the assigned network value to reach a given destination. Because these 

connections are static, they can be called permanent virtual circuits (PVC). 

DCA 

See Distributed Communications Architecture or Defense Communications Agency. 

DCA Transport Protocol (DTP) 

The DCA Level II layer 4 protocol that defines the set of rules for creating and maintaining 

end-to-end communication paths between computing systems or transport service users. 

It connects and terminates connections, controls data flow, recovers errors, and segments 

and recombines messages. DTP replaced port flow control and the Device Management 

Facility (DMF), which are functions supported by DCA Level 1. Handles all DCA Layer 4 

traffic between DCA Layer 3 modules (such as DNS or TSTN) and DCA Layer 5 modules 

(such as DTPX). 

DCA Transport Protocol Extension (DTPX) 

The DCA Level II layer 5 protocol that establishes and controls interactive session, session 

layer addressing, and data assurance. Handles all DCA layer 5 traffic between the DCA 

Layer 4 modules (such as DTP) and a VTR (via TSM) or end-user module (via EUSERV). 

7436 0728–303 Glossary–3

Glossary 

DCT 1000 Virtualizer Protocol Converter (DTVTR) 

Interfaces between DTPX and UNILPH for DCT1000 terminals. 

Distributed Communications Architecture (DCA) 

A Unisys proprietary network architecture and set of communication protocols based on 

the seven-layer Reference Model for Open Systems Interconnection. DCA supports the 

protocols required for several different network environments to interoperate. The main 

differences between the DCA and OSI architecture are in protocol implementation. DCA 

software implementations allow integration and concurrent operation of appropriate 

protocol modules or protocol conversion software that provide functions required in OSI, 

TCP/IP, and other network environments. 

Distributed Data Processing (DDP) 

A computing environment in which processing and storage facilities are geographically 

dispersed, but loosely coupled by transmission media. These computers are capable of 

sharing, transferring, or distributing files and processing tasks associated with 

applications. 

DLCMAN 

The main ILM management platform manager element for the new ILM handlers. 

DMOPEN 

Handles outbound open connection requests to a terminal from a remote application. Also 

handles auto-dial requests to dial a phone number over an auto-dial port. 

DNS 

See dynamic network services or domain name system. 

domain name system 

The DCP provides a domain name system resolver for the pairing of host names with their 

IP addresses. 

DTP 

DTPX 

DTVTR 

DUC 

See DCA transport protocol. 

See DCA transport protocol extension. 

See DCT 1000 virtualizer protocol converter. 

See data unit control. 

Dynamic Network Services (DNS) Protocol 

A DCA Layer 3 transport protocol that is an alternate to TSTN. It provides connectionless 

network layer services between Unisys network nodes. (A network node is either a host 

or a DCP.) The ISO 8473 internetwork protocol (IP) is the basis for the DNS network layer 

protocol. Connectionless network layer services allow you to define logical routes 

between hardware units in a DCA network without using SESSN statements. 

Configuration time for DNS is reduced because it dynamically recognizes new node 

addresses in the network and creates session paths for them. Unlike TSTN, DNS does not 

require SESSN statements. 

Glossary–4 7436 0728–303

E 

End User Services (EUSERV or EUSTRAN) 

1) A system service that helps end user (EU) programs send and translate session 

control messages. 

ENET 

2) Assists EU programs such as NMS to receive session control messages from the 

network. A procedure in the EUSERV module. 

A display abbreviation for Ethernet. 

Glossary 

Enterprise Network Services (ENS) 

A program product that runs on Telcon and provides the LAN Platform services of 802.3, 

FDDI, and 802.5, IPX, and SNMP agent. 

Ethernet 

A high-speed cabling system, developed by Xerox Corporation, that carries data through 

local area networks (LANs). Ethernet provides a de facto standard for baseband 

CSMA/CD LANs and is included in IEEE 802.3 LAN standards. Ethernet is an alternative 

to an IEEE LAN. The physical and electrical properties of the two LAN types are identical, 

but protocols and associated data structures (such as frame size and header content) 

differ. 

Ethernet User Initialization module (EUINIT) 

Receives EU configuration statements from the configuration during Telcon system 

initialization. 

EUINIT 

EUSERV 

See Ethernet User Initialization module. 

See end user services. 

external end user (XEU) 

An individual program or physical device external to a particular network, which uses a 

bridge to that network to perform system operations. Nonhuman users include 

applications and termination equipment such as terminals. 

external user 

The operator or the software that uses the data transport network specifically to perform 

a task or application. Compare with internal user. 

F 

FDDI 

See Fiber Distributed Data Interface. 

Fiber Distributed Data Interface (FDDI) 

An ANSI defined interface that supports data exchange over a fiber optic media at a rate 

of 100M bps. 

7436 0728–303 Glossary–5

Glossary 

File Transfer Protocol (FTP) 

A method of transferring files between computers with different operating systems. 

Established by the TCP/IP internet community from original DDN standards, FTP is the 

fastest and most globally-accepted method of transferring or viewing files between 

computer systems. 

flow control 

A function that controls data flow within a layer or between adjacent layers. Flow control 

prevents queue and buffer overspill and data loss when the receiver is unable to accept 

data. 

Frame Relay 

A data communications protocol developed in 1990 based on Integrated Services Digital 

Network (ISDN) standards. Frame Relay is designed to accommodate bursty data 

applications by providing high transmission speeds, low network delay, high connectivity, 

and efficient bandwidth use. 

Frame Relay User Device 

A device attached to a Frame Relay network that is capable of using the Frame Relay 

protocol for exchanging of information between it and other Frame Relay user devices 

attached to the Frame Relay network. 

FTP 

G 

See file transfer protocol. 

global common system subroutines 

Contains two location counters: $1 for procedures that can be called by any other 

procedure through the CALL instruction; $2 for subroutines in virtual address SDR5 

(address 2800-2FFF) that can be called within any other procedure through the SCALL or 

JLR instructions. 

H 

hard throttle 

An extremely low memory state where normal processing is not possible and the DCP/OS 

must terminate runs to revive the system. 

HCC 

See host channel control (HCC) module. 

HCONFIG 

Configuration processor that converts configuration statements to omnibus elements that 

Telcon can read. 

Host Channel Control (HCC) module 

Controls the channel protocol with CMS 1100. 

Glossary–6 7436 0728–303

I 

Glossary 

IBM Binary Synchronous Communications protocol 

Generally applies to Telcon's 2780/3780 remote batch device handler. Related procedure 

names are BSCLPH, BVINPUT, and BVOUTPUT. 

ILM 

See intelligent line module. 

ILM-AUC 

See Intelligent Line Module Asynchronous to UTS Converter. 

INSTDC 

See instrumentation data collection module. 

Instrumentation Data Collection Module (IDCM, INSTDC) 

A module that enables you to store the instrumentation buffers produced by the hardware 

when instrumentation is turned on. Writes instrumentation data to disk if requested from 

the TRON command using the WRAP=N parameter if the TRON command specified 

instrumentation parameters rather than system debug trace parameters. See disk file 

INSTDAnn. This INSTDC module also writes CENLOG buffers to disk, in 4K segments. 

See file names PRSTATnn, ALSTATnn for local log files and HDSTATnn and 

CLSTATnn for central log files. Refer to the DCP Series Telcon Operations Guide (7831 

5785) for more information. 

Intelligent Line Module (ILM) 

A line module that contains an M68xxxx microprocessor and dedicated main memory, 

enabling an ILM to perform communications processing functions that previously required 

resources from both the communications processor (CP) and the input/output processor 

(IOP). The result is a lower processing load on the CP and IOP, allowing greater 

throughput for DCP users. 

Intelligent Line Module Asynchronous-to-UTS Converter (ILM AUC) 

An interface application that can execute on the ILM and ILM Platform. It provides the 

same functions as the predecessor Asynchronous to UTS product, but allows greater 

throughput, since it executes almost exclusively on the ILM, not the CP. ILM AUC allows 

users of asynchronous terminals (primarily Digital and Digital-compatible) to access 

applications on OS 2200 hosts as if they were using UTS terminals. 

Interprogram Message (IPM) 

A DCP/OS mechanism by which two separate programs can communicate with each other. 

One program defines an IPM Receiver (a queue) and the other program connects to this 

receiver for a one-way connection. 

International Standards Organization (ISO) 

The organization that promotes international computer standards. Includes 

representatives from major computer manufacturers in many countries. 

7436 0728–303 Glossary–7

Glossary 

Internet Protocol (IP) 

The routing protocol that resides at the internet (network) layer (layer 2) of the TCP/IP 

architectural model. The IP is a connectionless datagram protocol that routes data to host 

systems within a complex system of multiple network nodes and interconnected 

networks. The IP provides datagram service, delivery service, general network services, 

and error reporting services. 

internetwork 

A large physical network made up of many interconnecting packet-switching networks. 

Connections are made through gateways that implement appropriate subnetwork 

protocols. 

Interprocess Communication (IPC) 

1) A function that provides communication services for all system processes. 

2) A facility that provides communication services for all applications. IPC can be one or 

more software products or a logically identifiable part of a larger product, with the 

larger product also providing application-specific services. 

3) Communication for DDP file transfers. Activated by an NMS RFS command on this 

DCP or another DCP, or an @IPF or @DDPFJT command on an OS 2200 series host 

for a DCP node. Not related to the NMS XFER command. 

IP 

IPC 

IPM 

ISO 

L 

LAN 

See internet protocol or internetwork protocol. 

See interprocess communication or interprocess control. 

See interprogram message. 

See International Standards Organization. 

See local area network. 

Line Protocol Handler (LPH) 

The Telcon software module that controls a particular line protocol, such as UDLC or the 

UNISCOPE line handler. The LPH is responsible for all the logical functions that control a 

communication line and provides the interface between the devices attached to that line 

and the Telcon network. Examples are UNILPH, TTYLPH, and NTRLPH. See also 

LPHTRS module, which is a resource to the LPH modules. 

Line Protocol Handler Terminal Resource Services (LPHTRS) 

Handles terminal control block (TCB) allocation and deallocation when a terminal signs 

on ($$SON command) and signs off ($$SOFF command). 

Glossary–8 7436 0728–303

Glossary 

Line Switch Module (LSM) 

A switch that physically connects the lines that run from the operating and backup 

front-end processors (FEPs) to the terminals. If the operating FEP fails, the LSM switches 

the communications lines to the backup FEP so data transmission can continue. Used to 

switch lines from one DCP to another DCP, either under Software Resiliency Control 

(SRC) or operator control through an NMS command. 

Link Management Services (LMS) 

Link Management Services for the Telcon Terminal Handler Platform suite of modules. 

Called from a Display Protocol Handler through the Data Link Service Interface calls 

DLU$DO and DLP$DO. Called from the following Telcon asynchronous terminal handlers: 

ALPMCP, ASYNMLCP, GTDLU, and VTDLU. Also called from the Asynchronous-UTS- 

Converter (VTE) program product’s VTEXDLU module and the ILM-AUC Asynchronous- 

UTS-Converter program product’s ILMASYCP module. Refer to the Telcon Terminal 

Handler Platform Programming Reference Manual (UP-9255.8) for more information. 

LMS 

See Link Management Services. 

loadsharing 

Loadsharing allows as many as eight DCPs to be configured. Each DCP has a primary load 

and a secondary load assigned to it through the configuration. With loadsharing, when a 

DCP fails, its primary load is absorbed by one or more of the other DCPs, but its 

secondary load is not. 

Local Area Network (LAN) 

1) A computer system communication network that is confined within a specified 

geographical area (usually a floor or a small building) and whose resources and 

peripheral equipment are often shared. 

2) One of the program products from the Open Systems products available for Telcon. 

logging central node 

The node that centrally logs event messages in a network. Logging can be done locally or 

at a logging central node. 

LPH 

LPHTRS 

LSM 

M 

See line protocol handler. 

See Line Protocol Handler Terminal Resource Services. 

See line switch module. 

Maintenance Control Facility (MCF) 

Each power control module in the basic (main) DCP600 cabinet contains a maintenance 

control facility (MCF) which monitors and controls various DCP600 processes. The MCF 

reports faults which appear as error messages in the control station windows. Each 

partition on a DCP600 can contain an MCF. 

7436 0728–303 Glossary–9

Glossary 

Management Information Base (MIB) 

A collection of objects that can be accessed using a network management protocol such 

as the Simple Network Management Protocol (SNMP). 

matrix switch 

An assembly of switches that permits the routing of one or more lines between two or 

more ports in a physical network. A matrix switch may reroute communication lines to 

enhance system resiliency. 

MCF 

See maintenance control facility. 

Message Handling System (MHS) 

An electronic mail and message handling application layer service that enables individual 

users to transmit and receive messages within an OSI network environment. MHS is an 

OSI specific application service element (SASE). MHS incorporates a list of user 

addresses, a message database, and processing facilities to create messages and direct 

them to users on the local host or remote hosts in the network. 

MHS 

MIB 

MLF 

MLMOVE 

See OSI Message Handling System or message handling system. 

See Management Information Base. 

See module library file. 

An NMS local processing module. It processes any MOVE command issued by any NMS 

administrator in the network, applicable to this DCP. Element name is the same. 

Module Library File (MLF) 

A Telcon omnibus element created with the @BUILD command and executable in the 

DCP/OS environment. The Telcon absolute element is built from multiple MLF omnibus 

elements, some of which were compiled from a Pascal source element (by MONAPP), and 

most of which were created by the MAP and DCPAPP processors from MASM 

relocatables. 

N 

NAK 

See negative acknowledgment. 

Negative Acknowledgment (NAK) 

A system response, expressed as NAK, that indicates to the sender of a message that the 

message was not properly received or could not be received. Compare with 

acknowledgment (ACK). 

Glossary–10 7436 0728–303

Glossary 

Network Management Services (NMS) 

The group of network control and reporting functions that establishes, maintains, and 

modifies the operations of the Telcon communication network. NMS supports network 

administration through persons or programs that maintain the operational capabilities of 

the network. NMS commands are the Telcon equivalent of the CMS 1100 communication 

system administrator (CSA) commands. 

network resiliency 

A feature that maintains network integrity when hardware components or connections 

between components in the network fail. This is accomplished through one of two 

methods. In the first method, alternate paths through a network are established between 

two network users. If a component fails (breaking one of the paths) an alternate path is 

used. In the second method, redundant hardware components are installed. If a 

component fails, a backup component is used. 

Nine Thousand Remote (NTR) 

A program that controls communication between a Telcon network and any terminal using 

NTR batch communication protocol. 

Nine Thousand Remote Line Protocol Handler (NTRLPH) 

Services the line protocol for remote batch sites using the NTR protocol. 

Nine Thousand Remote Virtualizer Protocol Converter (NTRV2R) 

Converts the NTR protocol to the RB2 host protocol for remote batch sites using the NTR 

protocol. 

NMS 

NTRLPH 

NTRV2R 

O 

See Network Management Services. 

See Nine Thousand Remote Line Protocol Handler. 

See Nine Thousand Remote Virtualizer Protocol Converter. 

Open Systems Interconnection (OSI) 

An ISO communication standard network protocol. OSITS is one of the program products 

from the Open Systems products available for Telcon. Enables the computer systems of 

multiple vendors to communicate. OSI is based on standard protocols developed by ISO 

and defined in the ISO Reference Model (usually called the OSI model, as opposed to the 

TCP/IP model). OSI architecture has seven layers: physical layer (layer 1), data-link layer 

(layer 2), network layer (layer 3), transport layer (layer 4), session layer (layer 5), 

presentation layer (layer 6), and application layer (layer 7). Each layer has specific 

functions, communicates with peer entities (those in the same layer), performs services 

for the next higher layer, and requests services from the next lower layer. See also layers. 

OSI 

See Open Systems Interconnection. 

7436 0728–303 Glossary–11

Glossary 

OSI Reference Model 

The seven-layer architectural model, defined by the International Organization for 

Standardization (ISO), that provides the framework for building an open network. The 

seven layers include: application, presentation, session, transport, network, data link, and 

physical. 

P 

Packet Switched Communications Software (PSCS) 

PSCS is one of the program products from the Open Systems products available for 

Telcon. It enables communication between DCPs and other devices attached to packetswitched 

PDNs. It also enables point-to-point connections using the Recommendation 

X.25 protocol defined by the Consultative Committee on International Telephone and 

Telegraph (CCITT). See also X.25 Packet-Switched Communications Software. 

packet-switched network 

A network based on packet-switching technology in which data is transmitted in units 

called packets. Messages are split into packets, then routed independently on a 

store-and-forward basis and reassembled at the receiving end of the communication link. 

Packet-switched data transfer uses the communication link only during the time of actual 

transmission. 

PCALL 

PDCNMS 

PDN 

PDN28I 

PDNETP 

The X.25 call processing handler. This procedure is defined in X.25 PSCS element 

PDNCALL. It processes call packets received from the network or call primitives 

received from a level 4 program using the Layer 3/4 Platform. 

The X.25 Common Network Management Services (CNMS) interface handler. This 

procedure is defined in X.25 PSCS element PDNSVS. PDCNMS processes commands 

received from the CNMS manager through the Telcon Manager-Agent User (MAU) and 

collects attribute, alarm, or statistics information from other X.25 PSCS modules. This 

procedure collects CENLOGs of various events that occur in other X.25 PSCS modules. 

See public data network. 

The nonfunctional version of the X.28 PAD terminal handler interface. This procedure is 

defined in Telcon and is present only when X.25 PSCS is not installed. 

Implements the X.25 DCE Network feature, which allows one or more Telcon processors 

to be an X.25 network. This procedure is defined in both the nonfunctional Telcon 

element PDNPAD and in the X.25 PSCS element PDNNET. The nonfunctional procedure 

is present only when X.25 PSCS is not installed. This feature allows an X.25 DTE device to 

directly attach to a DCP and form a packet-level connection to any other attached X.25 

DTE device. Also provides “internal DTE” interfaces to some of the level 4 programs using 

the Layer 3/4 Platform in X.25 PSCS. 

Glossary–12 7436 0728–303

PDNIUS 

PDNL3 

PDNL44 

PDNLPD 

PDNMAS 

PDNMLP 

PDNMS 

PDNPAD 

PDNSVS 

Glossary 

The X.25 PSCS initialization procedure. This procedure is defined in X.25 PSCS element 

PDNIUS. When the first line configured for X.25 PSCS becomes enabled, this procedure 

examines all other configuration statements related to X.25 PSCS and builds internal data 

structures needed for the X.25 PSCS operation. 

Implements the X.25 packet-level protocol (level 3). This procedure is defined in both the 

nonfunctional Telcon element PDNL3 and in the X.25 PSCS element PDNL3. The 

nonfunctional procedure is present only when X.25 PSCS is not installed. This procedure 

provides an interface between the various level 4 programs using the Layer 3/4 Platform 

and the link level or multi link-level protocol. 

The transport protocol terminal interface for UTS 4000 Cluster Controllers running UTS 

X.25 PSCS software. This procedure is defined in X.25 PSCS element PDNL4. It provides 

an interface between the terminal interface in element PDNLPD and the X.25 packet-level 

protocol. 

The terminal virtualizer interface handler for UTS 4000 Cluster Controllers running UTS 

X.25 PSCS software. This procedure is defined in X.25 PSCS element PDNLPD. It 

provides an interface between the transport protocol in procedure PDNL44 and the Telcon 

UTS virtualizer. 

The nonfunctional version of the interface handler for processing NMS command 

parameters defined for X.25 PSCS. This procedure is defined in Telcon and is present only 

when X.25 PSCS is not installed. 

See Public Data Network Multi Link-Level Protocol. 

The Telcon NMS interface handler for processing NMS command parameters defined for 

X.25 PSCS. This procedure validates the NMS command and its parameter values, invokes 

functions to other modules in X.25 PSCS for performing the NMS command, and generates 

output response and information messages to the NMS console. 

The handler for asynchronous terminals connected to an X.29 network PAD across an X.25 

network. This procedure is defined in X.25 PSCS element PDNPAF. It provides an 

interface between Telcon’s INT-1 protocol and the X.25 packet level protocol. When a 

terminal makes a packet level connection, the terminal operator uses standard Telcon 

control commands, forming a session to an application. 

The X.25 line handler. This procedure is defined in both the nonfunctional Telcon element 

PDNSVS and the X.25 PSCS element PDNSVS. The nonfunctional procedure is present 

only if X.25 in not installed. This procedure processes line initialization and line 

termination commands. 

7436 0728–303 Glossary–13

Glossary 

PDNTRK 

The S.25 DCP-toDCP (Trunk) interface. This procedure is defined in the X.25 PSCS 

element PDNTRK. PDNTRK provides an interface between DNS and the X.25 packet-level 

protocol. It also controls the number of virtual circuit connections needed depending 

upon the amount of data, or lack of data, sent over the trunk. 

PDNTRNK 

The nonfunctional version of the X.25 DCP-toDCP (Trunk) interface. This procedure is 

defined in Telcon and is present only is X.25 PSCS is not installed. 

PDNURS 

PLSEUI 

The terminal resources services interface for UTS 4000 Cluster Controller terminals and 

asynchronous terminals defined to run over an X.25 network. This procedure is defined in 

X.25 PSCS. It provides an interface with the Telcon terminal control block resource 

routines and the data protocols recognized within X.25 PSCS. See also PDNPAD and 

PDNL44. 

The initialization handler for the packet layer services (PLS) host interface software. This 

procedure is defined in both the nonfunctional Telcon element PDNPLS and the X.25 

PSCS element PDNPLS. The nonfunctional procedure is present only if X.25 PSCS is not 

installed. This procedure processes end user (EU) configuration statements where the 

TYPE parameter is set to PLSTSU. 

Port Processor Identification Number (PPID) 

A number that identifies a port processor on a DCP. It is an 8-bit byte that combines the 

IOP number and the hardware line module address. The hardware engineer straps the IOP 

number when the IOP is installed. The most significant four bits describe the IOP number; 

the least significant four bits describe the line module address. 

PPID 

PPLS 

PSCS 

See port processor identification number. 

The packet layer services (PLS) host interface handler. This procedure is defined in X.25 

PSCS element PDNPLS. It provides an interface between the X.25 packet-level protocol 

and an application on an OS 2200 host that uses GASIF. 

See Packet Switched Communications Software and X.25 Packet Switched 

Communications Software. 

Public Data Network (PDN) 

A digital data network that provides communication service for customer hosts and 

terminals. Public data networks use either the X.25 packet-switched protocol (see PSCS) 

or the circuit-switched X.21 protocol. See also Packet Switched Communications 

Software. 

Public Data Network Multi Link Level Protocol (PDNMLP) 

Implements the X.25 multi link-level protocol. This procedure is defined in X.25 PSCS 

element PDNMLP. It provides an interface between the X.25 packet-level protocol and the 

X.25 link-level (level 2) protocol. 

Glossary–14 7436 0728–303

Glossary 

PXCCONF 

The nonfunctional version of the handler for IS–PC, IS–CS, or IS–6000 systems running 

DCA TSTN over X.25 software. This procedure is defined in Telcon and is present only if 

X.25 PSCS is not installed. 

R 

RCAS 

See Remote Command Application Software. 

REM1 Line Protocol Handler (PMLPH) 

Services the line protocol for remote batch sites using the REM1 protocol. 

REM1 Virtualizer Protocol Converter (RMVTR) 

Converts the REM1 protocol to the RB2 host protocol for remote batch sites using the 

REM1 protocol. 

Remote Command Application System (RCAS) 

Used for DDP file transfers. Interfaces with IPC and RFSYN. Activated by an NMS RFS 

command on this DCP or another DCP, or an @IPF or @DDPFJT command on an OS 

2200 Series host. Not related to the NMS XFER command. 

RFSYN 

RMLPH 

RMVTR 

Remote file server for DDP file transfers. Activated by an NMS RFS command on this 

DCP or another DCP, or an @IPF or @DDPFJT command on an OS 2200 host. Not 

related to the NMS XFER command. 

See REM1 line protocol handler. 

See REM1 virtualizer protocol converter. 

Route Control (RC, RTC) 

A TSTN (non-DNS) service between DCA Layer 3 and DCA Layer 2. See document 

number SH06655 or its follow-on documents for the design description of RTC within a 

DCA. 

RTC 

S 

See route control. 

Simple Network Management Protocol (SNMP) 

Defines a set of standards for network management, including a protocol, a databasestructure 

specification, and a set of data objects which are designed to run over TCP/IPbased 

network environments. 

SMRP 

See standard message repository procedure. 

7436 0728–303 Glossary–15

Glossary 

SNMP 

See simple network management protcol. 

soft throttle 

The low memory state that occurs when the unused portion of the buffer pool of a DCP 

has drained to 20 percent of the available total (default), or to the user-defined level set by 

using the @TUNER program. Users are warned to cut back on memory usage to prevent a 

hard throttle. 

SRC 

See system resiliency control module. 

Standard Message Repository Procedure (SMRP) 

Used for NMS broadcast messages created by a system administrator operator. See the 

ISDM, ADDM, CHAM, DELM, DISM, and SNDM commands in the Telcon Operations 

Reference Manual (7831 5728). (Not related to the Unsolicited Message Service feature or 

USM.) 

STATDCR 

Statistics (primarily CENLOG) data collection routines. 

SYSSESN 

System initialization module to initialize run-time session control tables for DTP for each 

TSTN session statement found in the configuration. 

System Resilience Control Module (SRC) 

Controls loadsharing or backup on online/standby-state changes among a set of DCPs or a 

set of lines in the network configured as resilient. For information on configuring network 

resiliency, refer to the DCP Series Telcon Configuration Guide (7831 5678). 

T 

TAF 

TCP/IP 

See terminal attach facility. 

See transmission control protocol/internet protocol. 

TCP/IP model 

The four layer architectural model for a communication protocol developed primarily for 

defense-related networks through research conducted by the U. S. Department of Defense. 

TCP/IP protocols are in the public domain and are used within a Defense Data Network 

(DDN), or Internet environment. The TCP/IP model provides the framework for building 

an open systems network. 

Glossary–16 7436 0728–303

Glossary 

TCP–IP Stack 

A Unisys DCP Series program product that provides added functions for Telcon software 

on a Unisys Distributed Communications Processor (DCP). TCP–IP Stack provides frontend 

communications for OS 2200 hosts running DDN 1100, which provides two TCP/IP 

applications-file transfer protocol (FTP) and simple mail transfer protocol (SNMP). 

TCP–IP Stack enables communication with peer devices running compatible TCP/IP 

software. 

Telenet 

Telnet 

A PDN packet-switching network developed by General Telephone and Electronics 

Corporation. Telenet can be accessed by many different communications devices. 

A DDN Internet terminal protocol that provides a standard interface between terminals 

and processes so sites can interact with remote timesharing systems. 

Teletype Line Protocol Handler (TLPH) 

Used for asynchronous terminals configured with an LCLASS type of TTYL. This is the 

oldest version of Telcon’s three versions of TTY asynchronous line handlers. 

Teletype Virtualizer Handler (TTYVTR) 

Converts the INT1 output protocol messages to UNISCOPE protocol for TTYLPH to 

handle. Also converts TTY protocol input messages to INT1 protocol messages for input 

to CMS 1100, for either RSDCSU applications or TIP applications such as MAPPER. R12 

typically points to the TCB (terminal control block). 

Terminal Attach Facility (TAF) 

(1) The module used for passing messages to terminal resource services (TRS) and the 

terminal session manager (TSM). It can also be sued for passing messages between a line 

protocol handler (LPH) and a virtualizer (VTR). 

(2) A small Telcon interface module between LPH modules and VTR modules. For an LPH 

to pass an input message to its corresponding VTR module, it must call TAF. For a VTR 

module to pass an output message to its corresponding LPH module, it must also call TAF. 

TAF is also the interface for passing special control messages to LPHTRS or to TSM. See 

the R14 function-code parameters for TAF in the AASYSDEF element. Examples are 

CS$TLPH, CS$TVTR, CS$THIC, CS$TDAL, amd CS$TTSM. 

Terminal Session Manager (TSM) 

The Telcon module that controls session establishment and disestablishment for terminals 

other than DCA. Processes or creates session open or session close request commands 

from (or in behalf of) a terminal. The AASYSDEF element contains the function codes to 

be passed to TSM. For examples, FN$MSG, FN$AUX, FN$ALTCB, FN$DSRON, FN$SON, 

or FN$SOFF. Usually called by LPHTRS for most terminal types. 

Termination System Transport Network (TSTN) 

The only DCA layer 3 transport protocol until the DNS protocol was created in Telcon 

8R1. Requires a static SESSN statement in the configuration file for every session pairing 

before a session can be opened between any two end points in the network. 

7436 0728–303 Glossary–17

Glossary 

TPCDATA 

The handler for PC or U Series systems running DCA TSTN over X.25 software. This 

procedure is in X.25 PSCS element PDNNXA and provides an interface between the X.25 

packet-level porotocl and TSTN. 

Transmission Control Protocol (TCP) 

A commonly used Internet protocol that provides end-to-end reliability control for 

protocols residing in the process/application layer of the OSI Reference Model. TCP is a 

connection-oriented (virtual circuit) data transport protocol. It verifies the integrity of 

data received from the network before passing it to the process/application layer. It 

interprets error messages returned by lower layer protocols or by the TCP entity on the 

peer end system and executes appropriate error recovery procedures. TCP isolates 

process/application layer protocols from the characteristics of lower layer protocols. 

Transmission Control Protocol/Internet Protocol (TCP/IP) 

A set of protocols developed to connect different kinds of networks and computers. The 

most common implementation of TCP/IP is UNIX systems, which use TCP/IP protocols to 

communicate over an IEEE LAN. TCP/IP protocols are based on a four-layer architecture 

model, as opposed to the OSI seven-layer model. The four layers in the TCP/IP model are: 

process/application (layer 4), host-to-host (layer 3), internet (layer 2), and network access 

(layer 1). The main differences between the TCP/IP model and the OSI model are the 

location of reliability control (error detection and recovery) within the protocol hierarchy 

and the application system structure defined by each model. TCP/IP is required for the 

Defense Data Network (DDN). 

TSM 

TSTN 

TTYLPH 

TTYVTR 

U 

UDLCRS 

UDM 

See terminal session manager. 

See Termination System Transport Network. 

See teletype line protocol handler. 

See teletype virtualizer handler. 

See universal data-link control handler for remote DCP load/dump services. 

See undeliverable message. 

Undeliverable Message (UDM) 

An input or output message may cause a UDM notification if the endpoint of the session at 

which the message was destined for became unavailable. This may cause the session to 

remain in a UDM condition until the endpoint either becomes available or is completely 

terminated. 

Glossary–18 7436 0728–303

UNILPH 

See UNISCOPE line protocol handler. 

Glossary 

UNISCOPE 

1) A Unisys interactive synchronous line protocol for display terminals. 

2) An early series of Unisys (Sperry Univac) nonintelligent interactive display terminals. 

UNISCOPE Line Protocol Handler (UNILPH) 

Controls each individual UNISCOPE compatible terminal in a terminal-by-terminal, lineby-line 

basis. R11 points to the LCB (line control block). R12 typically points to the TCB 

(terminal control block). 

UNISCOPE Virtualizer (UVTR) 

Converts the INT1 output protocol messages to UNISCOPE protocol for UNILPH to 

handle. Also converts UNISCOPE protocol input messages to INT1 protocol messages for 

input to CMS 1100, for either RSDCSU applications or TIP applications such as MAPPER. 

R12 typically points to the TCB (terminal control block). 

Universal Data-Link Control Handler for the Remote DCP Load/Dump Services (UDLCRS) 

Handles loading and dumping of remote termination systems (such as remote DCPs that 

do not have an 2200 channel connected, or UTS20L terminals) over a serial synchronous 

communication line. For more information on these services refer to the Telcon 

Installation Guide (7831 5645). 

Universal Terminal System (UTS) 

A family of Unisys interactive display terminals that uses the UNISCOPE line protocol. 

Unsolicited Message (USM) 

A message sent from one demand terminal to another demand terminal. No session path 

is required between the two terminals. USMs are typically short. 

USM 

See unsolicited message. 

USM/broadcast 

The unsolicited message/broadcast procedure enables an application or terminal to send a 

message up to five pages long to another terminal or group of terminals without 

establishing sessions with them. 

USM central node 

The DCP where network unsolicited messages (USMs) are stored and can be manipulated 

with NMS commands. 

UTS 

UVTR 

See Universal Terminal System. 

See UNISCOPE Virtualizer. 

7436 0728–303 Glossary–19

Glossary 

X 

XEU 

X.21 

See external end user. 

The CCITT Recommendation that defines a protocol for communication between user 

devices and a circuit-switched network. 

X.21 Circuit-Switched Communications Software (CSCS) 

A Unisys product that enables Telcon to communicate over an X.21 circuit-switched 

public data network (PDN). 

X.25 Packet-Switched Communications Software (PSCS) 

See Packet-Switched Communications Software. 

Glossary–20 7436 0728–303

Bibliography 

Buyer’s Guide to DCP Communications Processor Architecture (7436 9828). Unisys 

Corporation. 

DCP Series Communications Processor Architecture Programming Reference Manual 

(7431 5805). Unisys Corporation. 

DCP Series Intelligent Line Module Programming Reference Manual (7431 8569). Unisys 

Corporation. 

DCP Series Enterprise Network Services Installation, Configuration and Operations 

Guide (7441 2065). Unisys Corporation. 

DCP Series OSI Transport Services (OSITS) Configuration and Operations Guide 

(7831 5587). Unisys Corporation. 

DCP Series SNA/net Configuration Guide (7831 5629). Unisys Corporation. 

DCP Series TCP–IP Stack Configuration and Operations Guide (7831 5546). Unisys 

Corporation. 

DCP Series Telcon Configuration Guide (7831 5678). Unisys Corporation. 

DCP Series Telcon Configuration Reference Manual (7831 5686). Unisys Corporation. 

DCP Series Telcon Installation Guide (7831 5645). Unisys Corporation. 

DCP Series Telcon Network Load Utility Installation Guide (7436 1601). Unisys 

Corporation. 

DCP Series Telcon Operations Guide (7831 5785). Unisys Corporation. 

DCP Series Telcon Operations Reference Manual (7831 5728). Unisys Corporation. 

DCP Series X.25 Packet Switched Communications Software (PSCS) Configuration and 

Operations Guide (7831 5470). Unisys Corporation. 

7436 0728–303 Bibliography–1

Bibliography 

Bibliography–2 7436 0728–303

Index 

A 

auto-dial operation, 17-5 

C 

cause codes 

clear packet (table), C-2 

description, C-1 

resetting, C-3 

restarting, C-4 

CENLOG 

class 10 messages, event 1, 10-1 














































class 2 messages, 2-1 














class 6 messages, event 16, 6-105, 6-106 














7436 0728–303 Index–1

Index 























class types, description, 1-1 

detailed event descriptions, 1-8 

display format, description, 1-3 

event, description, 1-8 

Videotex, 3-13 

class types 

CENLOG, 1-1 

codes 

diagnostic (table), A-2 

console messages, 17-1 

D 

DDP 

error messages (table), 18-2 

diagnostic 

diagnostic codes (table), A-2 

dial-out operation, 17-5 

display formats 

CENLOG, 1-3 

DSA 

messages, listed, 17-42 

E 

event descriptions 

CENLOG, 1-8 

Index–2 7436 0728–303 

F 

format 

display, brief, 1-4 

display, long, 1-5 

display, long (table), 13-89 

display, mini with central, 1-4 

display, mini without central, 1-3 

IBM sense data (table), D-1 

I 

IPC 

status codes (table), 18-9 

items 

input logging (table), 13-91 

output logging (table), 13-92 

M 

manual dialing, 17-5 

message types, 17-2 

messages 

DDP-defined, 18-3 

DSA, listed, 17-42 

error, RFS, 18-2 

NMS, listed, 17-3, 17-41 

NMS, types, 17-2 

RFS console (table), 18-2 

RFS errors (table), 18-7 

N 

NMS 

messages, listed, 17-3, 17-41 

messages, types, 17-2 

P 

path error 

sense data, D-27

R 

request error 

sense data, D-21 

request reject 

sense data, D-7, D-9 

RFS 

messages from DDP, 18-3 

messages from RFS consoles (table), 18-2 

messages from work order rejection 

(table), 18-6, 18-7 

RH usage error 


S 

Sense code 

figure, D-1 

Sense data 

conditions that create, D-2 

defined, D-1 

format (table), D-1 

path error category, D-27 

PH usage error category, D-25 

request error category, D-21 

request reject, D-7, D-9 

state error category, D-23 

state error 

IPC codes for RFS, 18-11 


T 

types 

CENLOG classes, description, 1-1 

NMS messages, 17-2 

U 

UCF 

submitting, 1-8 

UNILPH 

entry descriptions, 1-9 

UNILPH entry descriptions, 1-9 

Index 

7436 0728–303 Index–3 

V 

VTXGTW 

CENLOGs, 3-13 

CENLOGs, Videotex, 3-13 

Class 3 Event 8, 3-13 

Videotex CENLOGs, 3-13 

W 

work order rejection 

RFS error messages (table), 18-7 

RFS warning messages (table), 18-6 

X 

X.25 PSCS 

clear packet cause codes (table), C-2 

diagnostic codes (table), A-2 

reset packet cause codes (table), C-3 

restart packet cause codes (table), C-4

Index 

Index–4 7436 0728–303

*74360728-303* 

74360728–303

DCP Series Telcon Message Manual - Public Support Login - Unisys

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?