DCP Series Telcon Operations Guide - Public Support Login - Unisys

Title: 

DCP Series Telcon Operations Guide 

Product Information 

Announcement 

New Release Revision Update New Mail Code 

This Product Information Announcement announces the release and availability of the DCP Series Telcon Operations 

Guide (7831 5785–200). The following changes have been incorporated into this release: 

• Reorganization and consolidation of Network Management Services (NMS) information 

• Removal of information that now appears in the Telcon Operations Reference Manual (7831 5686) 

• Illustrations of ILM help screens 

This guide is for network administrators, operators, end users, and systems analysts using Communications 

Delivery level 6R1 software within a Telcon network. This guide explains the following tasks: 

• Using NMS commands 

• Using the Intelligent Line Module (ILM) NMS commands 

• Using NMS commands that provide the diagnostic and management functions of TCP–IP Stack 

• Using NMS commands for diagnostic and management functions of OSI Transport Services (OSITS) 

This document is a full revision and should totally replace earlier revisions and updates. 

To order additional copies of this document: 

• United States customers, call Unisys Direct at 1-800-448-1424. 

• All other customers, contact your Unisys Sales Office. 

• Unisys personnel, use the Electronic Literature Ordering (ELO) system. 

Announcement only: 

MBWA, MBZ, MU59, MX3, 

MX5, MX6, MX7, MX8, MY5 

Announcement and attachments: 

AF01 

System: DCP Series 

Release: Level 10R1 

Part number: 7831 5785–200

DCP Series 

Telcon 

Operations 

Guide 

Copyright© 1994 Unisys Corporation. 

All rights reserved. 

Unisys is a registered trademark of Unisys Corporation. 

Release Level 6R1 December 1994 

Printed in U S America 

Priced Item 7831 5785–200

NO WARRANTIES OF ANY NATURE ARE EXTENDED BY THE DOCUMENT. Any product and related 

material disclosed herein are 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 Corporation, if any, with respect to the products described in this document are set 

forth in such agreement. Unisys Corporation 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, indirect, 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. 

Correspondence regarding this publication should be forwarded to Unisys Corporation by addressing 

remarks to Communication Systems Product Information, Salt Lake City Publications, MS B2B07, 322 

North 2200 West, Salt Lake City, UT 84116-2979, U.S.A. 

RESTRICTED - Use, reproduction, or disclosure is subject to the restrictions set forth in 

DFARS 252.227-7013 and 252.211-7015/FAR 52.227-14 and 52.227-19 for commercial computer 

software, as applicable. 

UNISCOPE is a registered trademark of Unisys Corporation.

About This Guide 

Purpose 

Scope 

——————————————————————————————————————— 

The Telcon Operations Guide (7831 5785) is part of the operations subset of the DCP 

Series Telcon library. This guide explains the functions of the Telcon system. 

A DCP Series network has three major software components 

• Telcon 

• Communications Management System (CMS 1100) 

• Distributed Communications Processor Operating System (DCP/OS) 

This guide covers Telcon operations only. 

——————————————————————————————————————— 

This guide contains information on the following basic Telcon network operations and 

subjects: 

• How to use operator commands and routines 

• How a Distributed Communications Processor (DCP) network is organized 

• How to use the Network Management Services (NMS) console and commands 

• How to use the Intelligent Line Module (ILM) 

• How to use the TCP–IP Stack NMS commands 

• How to use OSI Transport Services (OSITS) NMS commands 

• How to control critical event notification and logging (CENLOG) messages that 

appear on your console or that are logged to your disk or to the central logging 

DCP or host 

7831 5785–200 v


Audience 

Prerequisites 

This guide contains information about product functions including commands, 

parameter syntax, and status messages. It provides the procedural information you 

need to accomplish specific tasks. 

——————————————————————————————————————— 

This guide is for communication network administrators (NA), end users, and systems 

analysts (SA). 

——————————————————————————————————————— 

This guide assumes advanced computer and communications understanding. This guide 

also assumes you have a basic understanding of Telcon software and Distributed 

Communications Architecture (DCA). 

——————————————————————————————————————— 

How to Use This Guide 

vi 

Use this guide with the Telcon Operations Reference Manual (7831 5785). 

In this guide 

If you need information about... Go to... 

Using Network Management Services Section 2 of this guide 

Using the Intelligent Line Module Section 3 of this guide 

Operating the TCP–IP Stack Section 4 of this guide 

Operating OSI Transport Services Section 5 of this guide 

7831 5785–200

Organization 

Other Unisys documentation 

If you need information about... Go to the... 

Changing logging possibilities Telcon Configuration Guide (7831 5678) 


Handling system problems DCP/OS Operations Reference Manual (7831 5702) 

ILM configurations Telcon Configuration Guide (7831 5678) 

Telcon Configuration Reference Manual (7831 5686) 

ILM HDLC capabilities Telcon Installation Guide (7831 5645) 

ILM AUC Intelligent Line Module AUC Configuration and User Guide 

(7831 5601) 

Logging and displaying event 

classes 

NMS commands 

Using instrumentation 

Using remote file system (RFS) and 

transfer operations 

Using NMS XFER command 

Telcon Operations Reference Manual (7831 5728) 

Telcon Configuration Guide ((7831 5678) 

Telcon Operations Reference Manual (7831 5728) 

——————————————————————————————————————— 

This guide is organized as follows: 

Section 1. Introduction 

This section is a basic overview of Telcon and Telcon networks. 

Section 2. Using Network Management Services (NMS) 

This section provides an overview of Network Management Services (NMS) and NMS 

commands. This section describes central logging and displaying, restricting network 

access, opening NMS, and using auxiliary screen control commands. 

Section 3. Using the Intelligent Line Module (ILM) 

This section describes the operations environment and expanded features of the 

Intelligent Line Module (ILM). This section also contains information about using ILM 

mode and ILM NMS commands. 

7831 5785–200 vii


Section 4. Operating the TCP–IP Stack 

This section describes NMS commands that provide the diagnostic and management 

functions of the TCP–IP Stack. 

Section 5. Operating OSI Transport Services (OSITS) 

This section provides an overview of OSITS. This section also explains how to use 

NMS commands for diagnostic and management functions of OSITS. 

——————————————————————————————————————— 

Notation Conventions 

viii 

This document uses the following command notation conventions: 

Command names 

Parameters 

Examples 

Messages 

Screen displays 

File names 

Variables 

Notation Convention Example 

ITALIC CAPS The RES command resets all adjustable 

system parameters. 

Monofont SCREEN BYPASS SIGNED ON 

italic Specify TYPE=typename. 

$$ON terminal-id 

Keyboard keys BOLD CAPS Press the TAB key. 

User entry bold italic Enter the following: 

LOGON=HST1 

——————————————————————————————————————— 

7831 5785–200

Command Conventions 

This document uses the following command conventions: 

Convention Description Example 

Brackets [ ] Enclose optional parameters, 

parameter values, or variables. 

Braces { } Enclose required parameters, 

parameter values, or variables. 

You must select one. 

(Parameters not enclosed by 

braces are also required.) 

Braces within 

brackets [{ }] 

Enclose two or more optional 

parameters. You can specify only 

one of the optional parameters. 

Commas , Separate parameters from other 

parameters and multiple 

parameter values from one 

another. 

Parentheses ( ) Enclose a list of parameters. One 

parameter from the list is 

required; however, you can select 

more than one or all of the 

parameters. 

Pipes | Separate optional parameters. 

You can only choose one. 

Semicolons ; Used to continue a configuration 

statement on another line. 

OSI HELP [command] 


DEST= nn.nn.nn.nn 

adr1,adr2,adr3,adr4 

NODE= name 

[[[n/]n/]n/]n 

CHAD FROM=name,TO=name 

MOD= NODR=n 

LNKR=n, TRNK=name 

ENCAP=YES | NO 

LINE=line; 

DLCI=dlci 

Ellipses ... Indicate repeating parameters. ACCESS=(amask....amask) 

Asterisks * Used to enter comments in 

configuration files. The asterisk 

must appear in the first two 

columns of the file. 

**DNS XEU STATEMENTS 

——————————————————————————————————————— 

7831 5785–200 ix


Required Characters 

x 

You may need to use the following characters when entering a CMS 1100, Telcon, or 

DCP/OS command. 

Character Description 

Double colons :: Separate some Telcon commands. 

Semicolons ; Act as a continuation symbol when commands are continued on the 

next line. CMS 1100 commands usually require a space before the 

semicolon; Telcon commands do not. 

Spaces Represent the actual number of spaces you must enter as part of a 

command. 

——————————————————————————————————————— 

7831 5785–200

Related Product Information 

The following Unisys documents contain helpful product information. 

Document Name/Number Description 

DCP Series Telcon 

Configuration Reference 

Manual (7831 5686) 

DCP Series Telcon 

Configuration Guide 

(7831 5678) 

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 describes how to configure Telcon to enable 

communication in a DCP communication network. This guide 

tells the user 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). 

continued 

7831 5785–200 xi


xii 


DCP Series Telcon Installation 

Guide (7831 5645) 

DCP Series Telcon Operations 

Reference Manual 

(7831 5728) 

DCP Series Telcon End Use 


This guide provides information on how to 

• Install and generate Communications Delivery software and 

related program products on an OS 2200 host 

• Load the generated software to Distributed 

Communications Processors (DCPs) 

• Verify the loaded software 

This manual contains information on the following Network 

Management Services (NMS) commands and parameters: 

• Telcon 

• ILM NMS 

• 802.3 LAN platform 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 explains how to 

• Establish sessions through Telcon 

• Send and receive unsolicited messages in a Telcon network 

• Use the terminal operations menu facility (TOMF) 

• Open and close sessions 

• Use TCP–IP Stack TELNET 

continued 

7831 5785–200


DCP Series Telcon Message 

Manual (7436 0728) 

DCP/OS Programming 


(7431 6894) 

DCP/OS Operations 

Reference Manual (7831 

5702) 

This manual contains information on the following: 


• Status messages, error conditions, and corrective actions 

for NMS and CENLOG messages 

• Directory Service Agent (DSA) messages 

• Remote Files Services (RFS) messages 

• Instrumentation messages 

This manual describes how to write programs to run under the 

DCP/OS. This manual contains information on the following: 

• User programming 

• CPA module definitions 

• Contingency handling process 

• System service calls and functions 

• Common utility subroutines 

• System messages 

• Debug facilities 

• Meta-Assembler (MASM) utility procedures 

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 

continued 

7831 5785–200 xiii


xiv 


DCP Series Telcon Network 

Load Utility (NLU) Installation 


DCP Series Open Systems 

Communications Software 

Conceptual Overview 

(7831 5835) 

DCP Series Intelligent Line 

Module (ILM) Programming 


(7431 8577) 

DCP Series Implementation 

Reference Manual Volumes 1, 

2, & 3 (UP–12728) 

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. 

This overview introduces you to fundamental concepts of open 

systems communication. This overview describes the following: 

• Architectural structures 

• Communication functions 

• Standard protocols on which TCP/IP, OSI, and Unisys DCA 

networks are based 

• DCP and OS 2200 products for open systems 

This manual describes the formats, conventions, and 

requirements of the Intelligent Line Module (ILM) platform 

architecture required to implement ISO protocols and create 

ILM user applications. 

Unisys Distributed Communications Processors implement 

Communications Processor Architecture in a range of sizes and 

capacities and offer the same general selection of line modules. 

Volume 1 describes communications processor architecture and 

summarizes the processor hardware. 

Volume 2 contains information on the line module interfaces and 

protocols. 

Volume 3 contains procedural and reference information on DCP 

Series offline diagnostics. 

continued 

7831 5785–200


DCP Series TCP–IP Stack 

Configuration and Operations 


DCP Series OSITS 

Configuration and Operations 


DCP Series X.25 PSCS 

Programming Reference 

Manual (7831 5496) 

OS 1100 Exec Installation and 

Configuration Guide 

(7830 7915) 

OS 1100 IPF 1100 Functional 

Overview and Master Index 

(UP–9610) 

OS 1100 NPE Pascal 

Programming Reference 

Manual (7831 0547) 


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 

This guide describes how to configure OSITS 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 OSITS 

This manual provides the information needed to use the DCP 

X.25 PSCS layer 3/4 platform interface and packet layer 

services (PLS) interface to write programs that use PSCS 

services. 

This guide explains how to configure hardware features and 

specify software requirements for OS 2200 systems. It also 

illustrates how to set up and modify an OS 2200 system to 

keep up with the changing needs of your site. 

This document gives a general overview of IPF 1100 and shows 

what IPF 1100 can do for you. It also contains a master index 

of terms from the individual IPF 1100 operations guides, with a 

reference to the particular manual in which each term appears. 

This document is a detailed reference for the OS 2200 New 

Programming Environment pascal (NPE Pascal) implementation 

of the Pascal language as specified by the American National 

Standards Institute/Institute of Electrical and Electronic 

Engineers document 770 X3.97-1983. 

——————————————————————————————————————— 

7831 5785–200 xv

Contents 


Section 1. Introduction 

1.1. Overview of Telcon Networks ..................1–3 

1.1.1. What is Telcon? ...........................1–3 

1.1.2. What is a Telcon Network? ....................1–3 

1.1.3. What does a Telcon Network Consist Of? ..........1–3 

1.1.4. What does a Telcon Network Look Like? ...........1–5 

1.2. Types of Telcon Networks ....................1–7 

1.2.1. Single-node Networks .......................1–7 

1.2.2. Multiple-node Networks ......................1–7 

1.3. Telcon Users ..............................1–9 

1.3.1. End Users ...............................1–9 

1.3.2. Network Administrators ......................1–9 

Section 2. Using Network Management Services 

(NMS) 

2.1. Overview .................................2–2 

2.1.1. Description ..............................2–2 

2.1.2. What does NMS Provide? .....................2–2 

2.1.3. Logging and Displaying Functions ...............2–3 

2.2. Restricting Network Access ...................2–5 

2.3. Opening NMS .............................2–7 

2.4. Using Auxiliary Screen Control Commands .......2–11 

2.4.1. Printing Console Messages ...................2–11 

2.4.2. Customizing Screen Size by Using Insert 

Lines .................................2–13 

2.4.3. Using Response Numbers ...................2–15 

2.5. Creating Initial Unsolicited and Broadcast 

Message Files ............................2–16 

2.5.1. Manipulating Broadcast Messages ..............2–16 

2.5.2. Controlling USM Files .......................2–18 

7831 5785–200 xvii

Contents 

xviii 

2.6. Using the NMS HELP Command ...............2–20 

2.7. Understanding NMS Commands ..............2–21 

2.7.1. Rules for Entering NMS Commands .............2–23 

2.7.2. Characteristics of NMS Commands .............2–24 

Section 3. Using the Intelligent Line Module (ILM) 

3.1. Overview .................................3–2 

3.1.1. Description ..............................3–2 

3.1.2. Diagnostics and Troubleshooting ................3–2 

3.1.3. ILM Platform and Manager ....................3–3 

3.1.4. Interface Applications .......................3–3 

3.1.5. User Interface ............................3–4 

3.2. Using ILM Conversational Mode ................3–5 

3.2.1. Entering ILM Conversational Mode ...............3–5 

3.2.2. Exiting ILM Conversational Mode ................3–6 

3.3. Using ILM NMS Commands ...................3–7 

3.4. Using the DISP Help Facility ...................3–9 

3.5. Using the ILM Online Help Facility .............3–16 

3.6. Using the Trace Facility .....................3–18 

Section 4. Operating the TCP–IP Stack 

4.1. Overview .................................4–2 

4.2. Using NMS Commands for TCP–IP Stack .........4–3 

4.2.1. Monitoring Routes, Connections, and 

Addresses ...............................4–4 

4.2.2. Modifying Routing Tables .....................4–5 

4.2.3. Tracing TCP/IP Information ....................4–5 

4.3. Entering TCP–IP Stack NMS Commands ..........4–7 

4.4. Using the TCP–IP Stack Online Help 

Facility ..................................4–9 

7831 5785–200

Section 5. Operating OSI Transport Services (OSITS) 

Contents 

5.1. Overview .................................5–2 

5.2. Using OSITS NMS Commands ..................5–3 

5.3. Entering OSITS NMS Commands ...............5–6 

5.4. Using the OSITS Online Help Facility .............5–8 

5.5. Making Online Parameter Changes ............5–12 

5.5.1. Making changes using the help facility ...........5–12 

5.5.2. Making changes with the PARAMETER 

command ..............................5–13 

7831 5785–200 xix

Figures 

1–1. Basic Telcon Network ......................................1–5 

1–2. Multiple-Node Telcon Network .................................1–8 

2–1. Network Divisions of NMS Authority .............................2–6 

2–2. NMS Sign On Screen .......................................2–8 

2–3. NMS Screen Before Command Transmittal ........................2–9 

2–4. NMS Screen After Command Transmittal ..........................2–9 

2–5. NMS Command Format (Example) .............................2–21 

3–1. General DISP Command Help Screen ...........................3–10 

3–2. DISP Help Screen for Line Information ...........................3–12 

3–3. DISP Help Screen for Internal Table Information ....................3–13 

3–4. DISP Help Screen for MTF Information ...........................3–14 

3–5. DISP Help Screen for Memory Information ........................3–15 

7831 5785–200 xxi

Tables 

2–1. NMS Divisions and Authority ..................................2–5 

2–2. Broadcast Message Commands ...............................2–16 

2–3. Unsolicited Message Commands ..............................2–18 

3–1. ILM NMS Commands .......................................3–7 

3–2. Tracing Procedures .......................................3–18 

4–1. TCP–IP Stack NMS Commands ................................4–3 

4–2. Expanded NMS DISPLAY Commands .............................4–4 

4–3. NMS KILL and MODIFY Commands ..............................4–5 

4–4. TCP/IP TRACE Commands ...................................4–5 

5–1. OSITS NMS Commands .....................................5–3 

7831 5785–200 xxiii

Section 1 

Introduction 

In this section 

——————————————————————————————————————— 

The DCP Series Telcon Operations Guide is one of several documents in the Telcon 

library. This guide provides the network operator with how-to information and 

procedures for operating a Telcon network. This section contains the following 

information: 

Subsection Topic 

1.1 

1.1.1 

1.1.2 

1.1.3 

1.1.4 

1.2 

1.2.1 

1.2.3 

1.3 

1.3.1 

1.3.2 

Overview of Telcon Networks 

What is Telcon? 

What is a Telcon Network? 

What does a Telcon Network Consist of? 

What does a Typical Telcon Network Look Like? 

Types of Telcon Networks 

Single-node Networks 

Multiple-node Networks 

Telcon Users 

End Users 

Network Administrators 

——————————————————————————————————————— 

7831 5785–200 1–1

Introduction 

Terms you should know 

1–2 

Term Definition 

DNS Dynamic Network Services (DNS) provides connectionless networklayer 

services between Unisys network nodes. 

Network node A network node is either a host or a DCP. 

OSI protocol OSI is a packet-oriented protocol that sends information in 

Protocol Data Units (PDUs). 

TCP/IP Protocol Transmission Control Protocol/Internet Protocol (TCP/IP) is a set 

of protocols providing a uniform internetworking environment. The 

TCP protocol is responsible for error detection and end-to-end 

logical connections. The IP protocol is responsible for the 

connectionless routing of packets. 

X.25 packet-switched 

network 

An X.25 network based on packet switching technology in which 

data is transmitted in units called packets. 

——————————————————————————————————————— 

7831 5785–200

1.1. Overview of Telcon Networks 

Introduction 

——————————————————————————————————————— 

1.1.1. What is Telcon? 

Telcon is the core communications software product for the Distributed 

Communications Processor (DCP) and is an implementation of the Unisys DCA. Telcon 

provides network management functions and enables the DCP to connect to hosts, 

other DCPs, terminals, remote concentrators, and other communication devices. 

Although designed primarily to support OS 2200 host computers and terminal systems, 

Telcon also supports many terminals in other systems. 

Note: In this guide, DCP refers to DCP5/15/25/30/35/50/55, DCP200, or DCP600 

Series unless stated otherwise. 

——————————————————————————————————————— 

1.1.2. What is a Telcon Network? 

Networks provide the essential link through which all systems and peripheral devices 

are interconnected. A Telcon network is a stand-alone communication network based 

on the Unisys DCA. Multiple interconnected DCPs (controlled by Telcon software) 

form the backbone network service in a Telcon network. Telcon software enables the 

DCP to operate as a 

• Front-end processor (FEP) 

• Remote concentrator (RC) 

• Intermediate network node 

To ensure flexibility, Telcon networks normally support a wide variety of non-Telcon 

hardware. 

——————————————————————————————————————— 

1.1.3. What does a Telcon Network Consist of? 

Hardware 

The minimum Telcon network hardware requirements are a DCP, an OS 2200 host, and 

terminals. 

Software 

Telcon network software components consist of the basic Telcon software, and Telcon 

program products such as OSITS, TCP–IP Stack, and X.25 PSCS. This suite of 

software operates under DCA and supports open systems communication. 

7831 5785–200 1–3

Introduction 

The software specifically used to manage and maintain a Telcon network is referred to 

as Network Management Services (NMS). Section 2 of this guide contains detailed 

information about NMS. 

——————————————————————————————————————— 

1.1.4. What does a Telcon Network Look Like? 

1–4 

The following figure is a basic Telcon network. Your network could be more complex. 

CONSOLE Telcon 

Node 

TERMINAL 

CLUSTER 

OS 2200 

HOST 

TERMINAL 


Node 

CLUSTER 

Figure 1–1. Basic Telcon Network 

TERMINAL TERMINAL 

CONSOLE 

003TC200.CDR 

——————————————————————————————————————— 

7831 5785–200

1.2. Types of Telcon Networks 

Introduction 

A Telcon network can be controlled from a single control center (network 

administrators have access to the entire network in this case), or the network can be 

divided into two or more control centers (in this case, network administrators have 

access only to parts of the network). 

If you have a network with a wide geographical distribution—some nodes in Europe, 

others in the United States—you may want to have a control center in a United States 

node of the network and another in a European node. Then the United States control 

center only receives information about events in the U.S. node, while the European 

control center only receives information about events in the European node. 

——————————————————————————————————————— 

1.2.1. Single-node Networks 

In a single-node network, your console is logically connected to your DCP. Any 

UNISCOPE ® or DCA terminal can become an NMS console by opening NMS. This 

allows you to use the NMS functions (the functions you use depend on your NMS 

console authority). 

——————————————————————————————————————— 

1.2.2. Multiple-node Networks 

In a network with multiple nodes (more than one DCP, or multiple nodes in a single 

DCP), you can route NMS to a different node not logically connected to your console. 

NMS software is identical in each Telcon; therefore, network management functions 

are distributed over the network. NMS software establishes a connection between two 

nodes dynamically when an NMS command requires the connection. This allows you 

to access NMS functions for all nodes from a single location in a large network. 

Figure 1–2 is an example of a multiple-node Telcon network. 

7831 5785–200 1–5

Introduction 

1–6 

Figure 1–2. Multiple-Node Telcon Network 

——————————————————————————————————————— 

7831 5785–200

1.3. Telcon Users 

Introduction 

Telcon users are divided into two groups: end users and network administrators. End 

users use terminals to access the host applications. Network administrators use 

terminals configured as network consoles to control network functions and access 

applications in the DCP and the host. 

——————————————————————————————————————— 

1.3.1. End Users 

End users are only allowed access to applications contained in the host computers and 

to other network-provided facilities, such as unsolicited messages (USMs). They access 

the network by using sign on procedures and establishing sessions with specific 

application communication system users (CSUs). See the Telcon End Use Guide 

(7436 0736) for more information on standard procedures for these functions. 

——————————————————————————————————————— 

1.3.2. Network Administrators 

Network administrators are responsible for the day-to-day operations of the network 

and may assist with installing new software systems and network expansions, such as 

adding new lines or terminals. Network administrators may also operate as end users. 

The network administrator can use Telcon to 

• Ensure the various DCPs within the network are operating correctly 

• Monitor attached lines and terminals 

• Take corrective action when specific problems are detected. This may involve 

getting extra assistance, such as engineering support. 

——————————————————————————————————————— 

7831 5785–200 1–7

Section 2 

Using Network Management Services 

(NMS) 


——————————————————————————————————————— 

This section provides an overview of Network Management Services (NMS) and 

describes how to use NMS. 


2.1 

2.1.1 

2.1.2 

2.1.3 

Overview 

Description 

What does NMS provide? 

Logging and Displaying Functions 

Central logging and displaying 

Local logging and displaying 

2.2 Restricting Network Access 

2.3 Opening NMS 

2.4 

2.4.1 

2.4.2 

2.4.3 

2.5 

2.5.1 

2.5.2 

Using Auxiliary Screen Control Commands 

Printing Console Messages 

Customizing Screen Size by Using Insert Lines 

Using Response Numbers 

Creating Initial Unsolicited and Broadcast Message Files 

Manipulating Broadcast Messages 

Controlling USM Files 

2.6 Using the NMS HELP Command 

2.7 

2.7.1 

2.7.2 

Understanding NMS Commands 

Rules for Entering NMS Commands 

Characteristics of NMS Commands 

——————————————————————————————————————— 

7831 5785–200 2–1

Using Network Management Services (NMS) 

2.1. Overview 

——————————————————————————————————————— 

2.1.1. Description 

Network Management Services (NMS) is a feature of Telcon software. NMS allows 

you to control and monitor the operations of DCP networks. NMS cannot function 

without Telcon, just as Telcon cannot function without NMS. NMS is installed as 

part of Telcon. 

——————————————————————————————————————— 

2.1.2. What does NMS provide? 

2–2 

NMS offers services needed to successfully manage your network, including a network 

control language with English-like syntax for network administrators at NMS consoles. 

With NMS you are able to 

• Broadcast, catalogue, change, and delete unsolicited messages (USMs) 

• Catalogue, delete, and transfer files 

• Change Telcon configurations and run online diagnostics 

• Configure an INT1, UNISCOPE, or DCA terminal or equivalent to open a session to 

NMS 

• Display internal Telcon tables and the trace status of Dynamic Network Services 

(DNS) 

• Initiate file transfers to and from DCPs and 2200 hosts 

• Initialize DNS trunks 

• Inspect local or mass storage 

• Manipulate USMs and broadcast messages for INT1 users 

• Monitor logical and physical connections anywhere in the network 

• Monitor critical event notification messages (CENLOGs) 

• Obtain network status and list of facilities 

• Open a connection over open systems, TS/TN, and DNS transport types 

• Perform debug tracing 

• Restrict authority by subdividing your network into areas, nodes, and regions 

7831 5785–200

• Terminate, dump, and restart Telcon 

• Up, down, move, and reroute lines 


——————————————————————————————————————— 

2.1.3. Logging and Displaying Functions 

NMS functions are controlled by manual (operator commands) and semiautomatic 

functions (configuration-dependent parameters). This subsection includes information 

on logging and displaying, which are semiautomatic functions of NMS. 

Network administrators monitor events on the network. One example is the failure of 

a trunk link between two DCPs. Telcon provides a service for logging and displaying 

such information, as follows: 

• Each event is allocated to one of 16 classes and given one of 16 event numbers 

within each class. These combined classes and numbers are called CENLOG 

messages. The Telcon Message Manual (7436 0728) lists the currently defined 

class or events within the Telcon networking system and the suggested operator 

action. 

• The event classes can be logged or displayed at the local Telcon node, at another 

node (Telcon central node), or a combination of both. For each event class, use 

NMS commands to select a particular combination of logging actions. You can set 

logging up dynamically either through the NMS console (see the Telcon Operations 

Reference Manual [7831 5728]) or by configuring parameters on the PRCSR 

statement (see the Telcon Configuration Guide [7831 5678]). 

You can use any combination of the preceding logging possibilities. You can 

change these combinations at any time, as needed (including turning off all logging 

for a particular class). See the Telcon Configuration Guide (7831 5678) for an 

illustration of the use of logging. 

——————————————————————————————————————— 

7831 5785–200 2–3


Central logging and displaying 

You can log or display events at another Telcon node or on a host designated as the 

CENLOG central node. The CENLOG central node logs event messages within the 

network. An alternative to central logging is to perform logging locally at each DCP. 

Use the NMS LOGC and CONS commands to specify if events are to be logged to a 

central node, and if the events will be displayed to NMS consoles. Logging central 

nodes are optional. See the Telcon Configuration Guide (7831 5686) for a description 

of the CENLOG central node. 

——————————————————————————————————————— 

Local logging and displaying 

2–4 

An alternative to central logging is to perform logging locally at each DCP. You can 

log or display events at the local Telcon nodes by either logging to a file on the fixed 

disk of a DCP, or sending display data to one or more NMS consoles. 

——————————————————————————————————————— 

7831 5785–200

2.2. Restricting Network Access 


NMS authority allows the systems analyst (SA) to restrict the scope of a network and 

prevent unauthorized access to network management facilities. When an SA configures 

the network, the authority level for each NMS console is specified. The authority level 

determines the amount of the network the console can control. 

If the SA configures the console as privileged, you can execute all NMS network 

commands. If the SA configures the console as limited, you can access only a specified 

portion of the system. 

Table 2–1 explains the network divisions and the corresponding levels of authority. 

Figure 2–1 illustrates the divisions. (For information about configuring NMS authority, 

see the Telcon Configuration Guide [7831 5678].) 

Table 2–1. NMS Divisions and Authority 

Division Authority 

None No authority. You can only perform NMS commands that display the status of 

the network. 

Region The lowest level of subdivision, consisting of access to one or more lines 

connected to a single Telcon. 

Node The level above region, consisting of access to all facilities (lines and other 

devices, such as terminals) connected to a single Telcon. There may be one 

or more regions. 

Area The level above node, consisting of access to one or more regions or nodes. 

The regions within an area may be in different nodes and may overlap one 

another. Therefore, a region or node may appear in more than one area. (It is 

also possible for an area to cover less than a node, but this generally does 

not occur). 

Privileged or 

Global 

The highest level of control, consisting of access to the entire network. NMS 

consoles may have authority at any of the levels. Thus, an NMS console that 

has authority for a particular region may only receive information about that 

region and may only operate on network components within that region. 

7831 5785–200 2–5


2–6 

Figure 2–1. Network Divisions of NMS Authority 

——————————————————————————————————————— 

7831 5785–200

2.3. Opening NMS 


If you have an auto-allocated NMS console, the NMS sign-on screen displays when you 

turn on your system. If not, you may have to perform the following steps before you 

open NMS: 

Step Action 

1 Enter the $$SON command from any Telcon UNISCOPE or DCA-type terminal to sign 

on to your terminal. (See the Telcon End Use Guide [7436 0736] for instructions on 

how to enter the $$SON command. 

2 Supply password (IDEN PASS=). The default password is Telcon. 

or 

Supply user-id/password (if your system has the security feature). The network 

administrator assigns the initial user-id/password. 

Note: If you attempt to sign on to a console without using a password, or using 

an incorrect user-id/password, NMS and DCP/OS automatically close the 

session. 

3 Enter the $$OPEN command from any Telcon UNISCOPE or DCA-type terminal to 

open a specific application. (See the Telcon End Use Guide [7436 0736] for 

instructions on how to enter the $$OPEN command.) 

After the $$OPEN command executes, a two-line heading displays on your screen. 

Line 1 displays 

• Telcon product name 

• Telcon system level number 

• Node PRCSR name from your configuration file 

• Level number of your configuration if your configuration specifies a configuration 

number 

Line 2 contains a row of dashes separating the heading information from the rest of 

the screen. 

Lines 3 through 22 are blank. 

Line 23 contains a start-of-entry (SOE) character. NMS positions the cursor after the 

SOE. 

4 Enter NMS commands following the SOE character. NMS displays the response 

below the command and then scrolls the screen up. Following the response, a new 

SOE appears, followed by the cursor. The cursor is the prompt for the next entry. 

Figure 2–2 shows the NMS screen displayed after you sign on. 

7831 5785–200 2–7


Explanation 

2–8 

Unisys Telcon Level-10R1 Node=PRC1 Config-C12-V5 

------------------------------------------------------------------ 

Figure 2–2. NMS Sign On Screen 

——————————————————————————————————————— 

Level-10R1 

You can define the software release level when generating Telcon using COMUS. 

This level is the same as reported on the NMS STAT and SST commands. 

Node=PRC1 

You can define the node name in the configuration using the processor 

configuration statement. 

Config-C12-V5 

You can define the revision level of a source configuration file through the 

CLEVEL parameter on the EQU statement or through configuration level query at 

COMUS BUILD time. (See the Telcon Configuration Reference Manual [7831 5686] 

for information on the CLEVEL parameter and the Telcon Installation Guide [7831 

5645] for information on COMUS.) 

Figure 2–3 shows an example of screen where a command has been entered, but not 

transmitted. 

7831 5785–200



------------------------------------------------------------------ 

SET 

Figure 2–3. NMS Screen Before Command Transmittal 

Figure 2–4 shows a command screen after transmitting a command. 


------------------------------------------------------------------ 

SET DATE=94:04:10,TIME=13:13:13 

93/04/10 13:13:13 EXPLICIT TIME/DATE SETTING COMPLETED 

Figure 2–4. NMS Screen After Command Transmittal 

——————————————————————————————————————— 

7831 5785–200 2–9


2.4. Using Auxiliary Screen Control Commands 

Auxiliary screen control commands provide auxiliary printer and screen-insert, 

point-control options. These options include commands for printing, screen control, 

and response numbers. 

——————————————————————————————————————— 

2.4.1. Printing Console Messages 

Format 

You can use auxiliary printers attached to the NMS console to obtain a hard copy of 

console messages. You can either leave the printer on permanently, or turn it on and 

off as needed. To turn it on, enter the @@PRNT command. 

——————————————————————————————————————— 

@@PRNT n 

——————————————————————————————————————— 

Optional parameter 

Example 

2–10 

n 

The device number of the printer to turn on. All input and output are printed until you enter the 

@@NOPR command. (For information on the @@PRNT and @@NOPR command, see the 

DCP/OS Operations Reference Manual [7831 5702].) 

Default 

Printer number 1. 

——————————————————————————————————————— 

@@PRNT 1 

Explanation 

@@NOPR 

Prints a copy of all console traffic on auxiliary printer number 1. 

Explanation 

Cancels all console traffic printing on the auxiliary printer. 

——————————————————————————————————————— 

7831 5785–200


2.4.2. Customizing Screen Size by Using Insert Lines 

Format 

You can use screen control commands to customize the NMS screen size and define a 

new insert line. Because the last line on the screen does not scroll, any commands 

you insert on the last line remain while the responses scroll up the screen. The screen 

control is convenient for a frequently used command such as the STAT command. If 

one line is insufficient, you can use the @@INS command to set the prompt scroll 

point to a different line on the screen. 

——————————————————————————————————————— 

@@INS n 

——————————————————————————————————————— 

Required parameters 

Example 

n 

The insert line number. 

Range 

Default 

3 to 23 

Line 23. 

Note: Line 24 is the freeze line; it remains on the screen and does not 

scroll. 

——————————————————————————————————————— 

@@INS 16 

Explanation 

In this example, the command sets the prompt scroll point at line 16. This leaves the lower eight 

lines of the screen free to hold frequently used commands. This feature is particularly useful for 

dynamic reconfiguration. For example, you can design a “FORM” to identify a specific terminal 

and then insert this “FORM” on line 23. You can repeatedly enter this “FORM” on the screen, 

changing only the names and hardware addresses, thus improving your efficiency. 

——————————————————————————————————————— 

7831 5785–200 2–11


2.4.3. Using Response Numbers 

Format 

Telcon does not automatically generate response numbers, since they are usually not 

necessary. However, entering a response number with a command makes it easier to 

match input with output. Telcon displays the number with the output response. This is 

helpful if there is a long response time after input. For example, the following shows 

a COND command with a response number of 1. 

——————————————————————————————————————— 

COND 

——————————————————————————————————————— 


Example 

2–12 

None. 

——————————————————————————————————————— 

1 COND 

Range 

Normal response output will be prefixed with the response number 1. 

0 to 9 

——————————————————————————————————————— 

7831 5785–200


2.5. Creating Initial Unsolicited and Broadcast 

Message Files 

The unsolicited message (USM) central node handles unsolicited messages. The USM 

node is for broadcasting of messages using the MSG command (see the Telcon 

Operations Reference Manual [7831 5728] for more information). The USM central 

nodes and logging central nodes may be configured in the same node or distributed 

throughout the network. 

Before you can use the broadcast messages and unsolicited messages features, you 

must create and initialize files to hold these messages. Use the CAT command for 

creating the message file. (See the Telcon Operations Reference Manual [7831 5728] 

for more information on using the NMS CAT command). 

——————————————————————————————————————— 

2.5.1. Manipulating Broadcast Messages 

Broadcast message commands allow you to manipulate broadcast messages stored on 

disk. Messages can be broadcast to all eligible terminals (for example, non-batch 

terminals having dynamic sessions only, except parallel UNISCOPE terminals) on a 

DCP, or to all eligible terminals in the network. 

Table 2–2. Broadcast Message Commands 

Command Description 

ADDM Inserts a new broadcast message. 

CHAM Replaces an existing broadcast message. 

DELM Deletes an existing broadcast message. 

DISM Displays a specified broadcast message on the console. 

ISDM Initializes the standard broadcast message file. 

SNDM Sends broadcast messages to other terminals in the network. 

7831 5785–200 2–13


Format 

The following format illustrates and explains the ISDM command. (See the Telcon Operations 

Reference Manual [7831 5728] for information about how to use the broadcast message 

commands.) 

——————————————————————————————————————— 

ISDM 

——————————————————————————————————————— 


Example 

2–14 

None. 

——————————————————————————————————————— 

ISDM 

Response 

1994/07/24 08:40:30 STANDARD MESSAGE FILE INITIALIZED 

——————————————————————————————————————— 

7831 5785–200

2.5.2. Controlling USM Files 

Format 1 

Format 2 


Unsolicited message commands let you control USM file contents by manipulating 

message queues at destination terminals. In addition, you can create and send standard 

system messages to non-batch terminals configured on dynamic sessions. 

Users sending broadcast messages have limited access for altering messages if a 

terminal does not receive a message. The network administrator must make any other 

request to alter a message's characteristics. To use unsolicited message commands, 

you must have a minimum node authority. 

Table 2–3. Unsolicited Message Commands 

Command Description 

CHAD Changes the destination of USMs. 

CHAT Changes the existence time of USMs. 

DELQ Deletes USMs queued to a terminal. 

DISQ Displays details of USMs queued to a terminal. 

The following format illustrates and explains the CHAD command. 

——————————————————————————————————————— 

CHAD FROM=name,TO=name 

——————————————————————————————————————— 

CHAD FROM=name,TO=name[,MSG=name][,ORIG=name] 

——————————————————————————————————————— 

7831 5785–200 2–15



FROM=name 

Identifies the original (TERMINAL/SITE name) destination of the queued messages. 

TO=name 

Identifies a new (TERMINAL/SITE name) destination to which messages are queued. 

——————————————————————————————————————— 

Optional parameters 

Example 

2–16 

MSG=name 

Identifies the message to be moved. Default is all queued messages. 

ORIG=name 

Identifies terminal of message sender. Default is all senders. 

——————————————————————————————————————— 

CHAD FROM=PU1CON,TO=PU3CON 

Response 

1994/07/24 10:48:57 CHAD COMPLETE 

MESSAGES QUEUED TO TERMINAL PU1CON 

EMPTY 

MESSAGES QUEUED TO TERMINAL PU3CON 

MESSAGE ID ORIGINATOR EXISTENCE TIME 

MSGN1 SYSTEM 00:00 

MSGN1 PU3CON 00:00 

——————————————————————————————————————— 

7831 5785–200


2.6. Using the NMS HELP Command 

Format 

You can use the HELP command to obtain the following information: 

• A list of all standard NMS commands 

• A description of the command format for specific commands 

• A list of all valid software IDs (for use with TRON/TROF commands) 

• The state of all software IDs 

To use the HELP command, use the following format. (See the Telcon Operations 

Reference Manual (7831 5728) for more information on the HELP command.) 

——————————————————————————————————————— 

HELP 

——————————————————————————————————————— 


Example 

None. 

——————————————————————————————————————— 

HELP TYPE=CONS 

Response 

CONS {DCP=xxxxxxxx,NODE=xxxxxxxx,AUTH=cccc,ON=nn,OFF=nn,CDES=c,OPDS=c, 

TERM=cccccccc} 

Explanation 

Displays the format of a specific command. 

——————————————————————————————————————— 

7831 5785–200 2–17


2.7. Understanding NMS Commands 

You must be familiar with the following NMS command formats before you can enter 

NMS commands properly. Figure 2–4 illustrates a sample NMS command format. 

CNCL FUNC 

T, 

M 

DVC name 

FILE name 

X,XFER 

n 

$ 

,NODE 

name 

[[[n/]n/]n/]n 

Figure 2–5. NMS Command Format (Example) 

——————————————————————————————————————— 

Required Parameters 

CNCL 

FUNC= 

The command name. This is always entered first. 

Identifies the parameter. Parameters are entered immediately after the command name, and can 

be entered in any order unless stated otherwise. 

Note: Any parameter not enclosed in braces or brackets is required. For more 

information on command notation conventions, see the “About This Guide” 

section of this document. 

——————————————————————————————————————— 


2–18 

NODE= 

name 

[[[n/]n/]n 

Specifies either the name of the Telcon node or the DNS network address where the command 

is executed. If you omit the NODE parameter, NMS directs the command to the Telcon node to 

which your console is logically connected. For more information on the NODE parameter, see the 

Telcon Operations Reference Manual (7831 5728). 

——————————————————————————————————————— 

7831 5785–200

Example 1 

Example 2 

UP STN=UDSTN1 

Response 

1994/08/02 08:50:04 COMMAND ACCEPTED 

Explanation 


This example illustrates how to use the UP command to reactivate a station. 

——————————————————————————————————————— 

UP LINE=LINE32S 

Response 

1994/08/02 08:50:04 COMMAND ACCEPTED 

CENL: 13:22:54 DCP=PRC1 SEQ=48 CLASS=9 EVCD=1 

LINE=LINE32S PPID=32 

'UP' OF FACILITIES COMMAND 

CENL: 13:22:54 DCP=PRC1 SEQ=49 CLASS=6 EVCD=7 

LINE=LINE32S PPID=32 

LINE CONNECTION COMPLETED 

Explanation 

This example illustrates how to use the UP command to reactivate a line. You receive the 

illustrated response if CENLOG is turned on and the console is enabled for CENLOG display. 

——————————————————————————————————————— 

7831 5785–200 2–19


2.7.1. Rules for Entering NMS Commands 

2–20 

Observe the following rules when NMS commands: 

Subject NMS Command Rule 

Command name Must always be entered first. 

Spaces and special 

characters 

Commands and 

Parameters 

Ignored if they appear before the command word. 

• Either uppercase or lowercase letters are acceptable. 

• Commands and parameters can be abbreviated. See Section 2 

of the Telcon Operations Reference Manual (7831 5728). 

• Can appear in any order following the command name, unless 

otherwise indicated. 

• Limited to eight characters, unless otherwise indicated. You can 

use any non-blank character except a comma (,) a slash (/), or 

an equal sign (=). 

• You can replace commas and equal signs with spaces to 

separate parameters or parameter arguments. 

Numbers Denoted by n. Each base of the number has a different format, as 

follows: 

• A decimal starts with a single number, such as 101. 

• A hexadecimal starts with a leading zero, such as 0101. 

• An octal starts with a leading letter O and ends with a single 

quote, such as O'101'. 

• A binary starts with a leading letter B and ends with a singe 

quote, such as B'101'. 

Note: For complete command notation conventions information, see the “About 

This Guide” section of this document. 

——————————————————————————————————————— 

7831 5785–200

2.7.2. Characteristics of NMS Commands 


In addition to the command formats, you should be familiar with certain 

characteristics of NMS commands. 

Subject Characteristic 

NODE parameter • Optional for most commands. 

• Specifies the name of the remote Telcon node or DNS network 

address where the command will be executed. 

• If omitted, NMS directs the command to the Telcon node to which 

your console is logically connected. 

PGRP parameter • Applies only to UNISCOPE display terminal lines. 

• You must specify a line when using this parameter. 

Poll group • Not a configured entity; therefore, you cannot check its validity. 

• Only exists when the line is connected. 

• You can only add new poll groups if the general polling remote 

identifier (RID) does not exist for the UNISCOPE protocol line. 

• You cannot add a general polling group if another poll group 

already exists on that line. 

Terminals If configured as auto-allocated (after first input), they are also signed on 

when a poll group is added to dial-up or dedicated lines. 

UP command You can use this command to add a poll group to a multidropped line 

even if no terminal with the RID is configured on the line. 

UP state You must use the line name to place a communication line in this state. 

XTS parameter Specifies an external termination system. 

——————————————————————————————————————— 

7831 5785–200 2–21

Section 3 

Using the Intelligent Line Module (ILM) 


——————————————————————————————————————— 

This section describes the operations environment and expanded features of the 

Intelligent Line Module (ILM). This section also contains information about how to 

use the ILM in a DCP environment. This section contains the following topics: 


3.1 

3.1.1 

3.1.2 

3.1.3 

3.1.4 

3.1.5 

3.2 

3.2.1 

3.2.2 

Overview 

Description 

Diagnostics and troubleshooting 

ILM platform and manager 

Interface applications 

User interface 

Using ILM Conversational Mode 

Entering ILM Conversational Mode 

Exiting ILM Conversational Mode 

3.3 Using ILM NMS Commands 

3.4 Using the DISP Help Facility 

3.5 Using the ILM Online Help Facility 

3.6 Using the Trace Facility 

——————————————————————————————————————— 

7831 5785–200 3–1


3.1. Overview 

——————————————————————————————————————— 

3.1.1. Description 

ILMs are DCP line modules with faster processors and expanded functionality. ILMs 

increase transaction throughput by completing many tasks the DCP, the IOP, or both 

previously performed. ILMs also give the operator more information about 

communication ports. Because of these factors, ILMs are becoming increasingly 

important additions to the DCP. 

ILMs are constructed from a standard processing core and specific hardware to 

implement many different communication interfaces. (For detailed hardware 

specifications, see the DCP Series Configuration Reference Manual [UP–13329]). The 

standard processing core allows many types of ILMs, such as FDDI, Ethernet, and 

Token Ring, to execute the same programs. 

ILM software is loaded as part of Telcon initialization. The ILM environment is 

consistent with the Telcon environment and uses standard configuration statements, 

NMS commands, and CENLOG messages. Users familiar with Telcon should be able to 

easily learn the ILM environment. 

——————————————————————————————————————— 

3.1.2. Diagnostics and troubleshooting 

3–2 

Diagnostics and troubleshooting for the ILM occur online. Diagnostics and 

troubleshooting shortens repair time and eliminates the need to send dumps to a 

Unisys site. Information about diagnostics and troubleshooting is located on the ILM 

release tape. 

——————————————————————————————————————— 

7831 5785–200

3.1.3. ILM platform and manager 


To make ILMs easier to program and easier to use, Unisys developed a common 

operating environment for the ILM known as the ILM Platform. The operations feature 

of the ILM platform is called the ILM Manager. 

The ILM Manager executes in the ILM and implements a basic operator interface that 

allows the operator to 

• Collect statistics 

• Log service calls 

• Perform tracing 

• Debug 

——————————————————————————————————————— 

3.1.4. Interface applications 

Programs that operate in cooperation with the ILM Manager are called Interface 

Applications (IAs). You can direct several operator commands to a specific IA. IAs are 

independent programs that run from the ILM platform. There are two types of IAs 

• Standard ILM (such as FDDI IA and Ethernet) 

• User-created 

Each IA has its own suite of NMS-type commands. 

Use the ILM help facility to see which ILM commands you can direct to an IA. (See 

“Using the Online Help Facility” later in this section.) Use the ILM DISP command to 

display information about a specific IA. (For more information on the ILM DISP 

command, see the Telcon Operations Reference Manual [7831 5728]). 

——————————————————————————————————————— 

7831 5785–200 3–3


3.1.5. User interface 

3–4 

The ILM user interface is a suite of commands accessed from ILM mode. ILM 

conversational mode commands use the same syntax as Telcon NMS commands. You 

can find specific command syntax in Section 2 of this guide. Section 3.3 describes ILM 

NMS commands and command functions. 

You can access an extended ILM user interface through the NMS console. Enter ILM 

conversational mode to access the extended ILM NMS commands. After you are in ILM 

conversational mode, you cannot use the standard NMS commands until you exit the 

mode by entering the EXIT command. (For information on entering and exiting ILM 

conversational mode, see Section 3.2.) 

——————————————————————————————————————— 

7831 5785–200

3.2. Using ILM Conversational Mode 


Performing tasks in ILM conversational mode is similar to doing work in Telcon. ILM 

commands are similar to Telcon NMS commands. While many ILM commands are 

duplicates of NMS commands, others have the same name, but with parameters 

specific to ILM. Tracing occurs the same way as in Telcon, and ILM CENLOG 

messages are formatted exactly as Telcon CENLOG messages. 

You do not need to be in ILM mode to activate and deactivate entities connected to an 

ILM. The same is true for starting and stopping input or output from a facility (for 

example, terminals and stations) connected to an ILM. Execute these commands just 

as you would any other Telcon commands. 

——————————————————————————————————————— 

3.2.1. Entering ILM Conversational Mode 

Format 

To enter ILM conversational mode, you must be using an active NMS console (see 

Section 2 of this guide). Use the ILM command shown below to enter ILM 

conversational mode in NMS. 

——————————————————————————————————————— 

1. ILM 

2. ILM NODE= name 

[[[n/]n/]n/]n 

——————————————————————————————————————— 


NODE= name 

[ [ [n/ ]n/ ]n/ ]n 

Specifies the name of either the Telcon node or the DNS network address where the command 


which your console is logically connected. See the Telcon Operations Reference Manual 

(7831 5728) for information on the NODE parameter. 

——————————————————————————————————————— 

7831 5785–200 3–5


Explanation 

Example 

Format 1 

Use to access ILM conversational mode in the NODE to which you are logically 

connected. 

Format 2 

Use to access ILM conversational mode in a remote NODE. 

——————————————————————————————————————— 

ILM 

Response 

* ILM Management - Enter Command (Enter EXIT to Quit) := 

——————————————————————————————————————— 

3.2.2. Exiting ILM Conversational Mode 

Format 

Use the EXIT command shown below to exit ILM conversational mode. 

——————————————————————————————————————— 

EXIT 

——————————————————————————————————————— 


3–6 

None 

——————————————————————————————————————— 

7831 5785–200

3.3. Using ILM NMS Commands 


Table 3–1 describes the different types of ILM NMS commands and explains the 

function of each command. For complete information on format and parameters, see 

the Telcon Operations Reference Manual (7831 5728). 

Table 3–1. ILM NMS Commands 

ILM Command Function 

DISP Displays line statistics and other facility attributes about a 

specific line module or IA. Because the DISP command 

encompasses such a variety of information, it has its own 

help facility. 

DISP HELP Displays help screens for ILM information. (See Section 3.4 

for information on using the DISP help facility.) 

DUMP Initiates an ILM dump. After the dump completes, you can 

use the NMS XFER command to transfer the dump file to a 

host. 

ENV Controls ILM environment. You can use this command to 

change the ILM environment and set functions such as time, 

date, and heartbeat (HB). The HB function allows the CP to 

periodically inspect the ILM to ensure operability. 

FREE Clears line modules and frees ports from a Telcon run. 

To control configured facilities, use the Telcon NMS UP, 

DOWN, STRT, and STOP commands. For more detailed 

information about these commands, see the Telcon 

Operations Reference Manual (7831 5728). 

HELP Displays help information, including command syntax format 

and parameter information. 

LIST Lists the active lines and facilities (terminals, stations) within 

a specific ILM. The LIST command displays a list of lines on 

a specific ILM that are having or causing problems. 

Note: You can use the NMS STAT and LIST commands 

to display ILM Line and SAP statistics. For more 

information, see the Telcon Operations Reference 

Manual (7831 5728). 

continued 

7831 5785–200 3–7


3–8 

ILM Command Function 

LOAD Forces a long load of an ILM load file or element. 

LOOP Sends a loop request packet to a specific IA. The loop 

request packet commands the specified IA to perform 

loopback testing on a particular line as instructed by the 

SET command. 

SET Sets loopback test parameters for a specific line. You must 

have privileged authority to use the SET command. 

SNAP Activates trace facilities. 

SNOF Deactivates trace facilities. 

Note: For more information on loopback testing and 

diagnostic procedures, contact the Unisys Client 

Support Center (1-800-328-0440). 

STAR Starts line module reporting of ILM busy/buffer utilizations 

on periodic 30-second intervals. Use this command to 

monitor and verify network activity. 

To stop the repeating display, enter any ILM command. 

STAT Solicits line module CP busy/buffer and IA information and 

turns on statistics for a particular line. The information 

displayed includes the ILM activity state, memory use, 

number of active lines, and release levels of ILM 

components. Use this command to monitor and verify 

network activity. 

TCAT Catalogues a file for logging trace information. 

TCLS Closes a trace file. 

TOPN Opens a trace file. 

TSWT Switches trace files. 

——————————————————————————————————————— 

7831 5785–200

3.4. Using the DISP Help Facility 

Format 

Parameters 


Use the ILM mode DISP command to receive line module information supplemental to 

the information displayed when you use either NMS mode or ILM conversational mode 

LIST and STAT commands. 

Use the following format to enter the DISP help facility. 

——————————————————————————————————————— 

DISP PORT=n TYPE=HELP 

——————————————————————————————————————— 

PORT=n 

The number of the port where the IA resides. 

TYPE=HELP 

Displays general help screen for ILM DISP command. 

——————————————————————————————————————— 

7831 5785–200 3–9


Explanation 

3–10 

Figure 3–1 illustrates the first DISP help screen you see after accessing the help 

facility. To move from any of the help screens, press the TAB key until the Start of 

Entry (SOE) character is on the desired screen number, then press the XMIT key. To 

exit the help screens, type EXIT. 

DISP PORT=O1f 

Response 

ILM 'DISP' response for port # O1f 

Help screen # 1 (general commands) for ILM 'DISP' command: 

DISP port 01f displays this screen 

DISP port 01f type=help displays this screen 

DISP port 01f type help page 2 Tab,Xmit for LINE display help. 

DISP port 01f type help page 3 Tab,Xmit for TABLE display help. 

DISP port 01f type help page 4 Tab,Xmit MTF display for help. 

DISP port 01f type help page 5 Tab,Xmit MEMORY display for help. 

ILM> 

Figure 3–1. General DISP Command Help Screen 

——————————————————————————————————————— 

LINE display help 

Contains line attachment information. 

TABLE displays help 

Provides ILM internal table information. 

MTF display for help 

Provides message transfer facility information. 

MEMORY display for help 

Dumps ILM memory information to screen. 

7831 5785–200


Figure 3–2 illustrates the help screen for line attachment information. 

DISP PORT=01f,type=help,page=2 

Response 


Help screen # 2 (LINE display commands) 

Disp port=01f type=lcb line=zzzz - displays line's raw LCB 

Disp port=01f type=ocb name=zzzz - displays NAME's raw OCB 

Disp port=01f type=offs line=zzzz - displays LINE`s list of OCB(s) 

Disp port=01f type=stat line=zzzz - displays LINE's I/O statistics 

Disp port=01f type=stat line=zzzz fac=xxxxxxxx 

Disp port=01f type=MODEM line=zzzz - displays LINE's MODEM info 

Disp port=01f type=CNTRS line=zzzz - displays LINE's Counter info 

Disp port=01f type=DRVR line=zzzz - displays LINE's driver table 

Disp port=01f type=ERRS line=zzzz - displays LINE's driver table 

Disp port=01f type=MCAS line=zzzz - displays LINE's Multi-Cast Addrs 

Disp port=01f type=MENU line=zzzz - displays LINE's driver table 

Disp port=01f type=STATUS line=zzzz - displays LINE's driver level 

DISP port O1f type help page 1 Tab,Xmit for general display help. 

ILM> 

Figure 3–2. DISP Help Screen for Line Information 

Note: In Figure 3–2, zzzz can be a line name or a multiline number. 

7831 5785–200 3–11


3–12 

Figure 3–3 illustrates the help screen for ILM internal table information. 

DISP PORT=OA,type=help,page=3 

Response 


Help screen # 3 (TABLE display commands) 

Disp port=xx type='table' -displays this screen. 

(from list below) 

Disp port=xx type='table' [entr]=zz -displays edited table ENTRY # zz. 

Disp port=xx type='table` [adr]=zz -gives raw table dump at index ADR. 

Manager table types=: ISIT, AT, IUT, MERT, IA. 


ILM> 

Figure 3–3. DISP Help Screen for Internal Table Information 

7831 5785–200

Figure 3–4 illustrates the help screen for MTF information. 

DISP PORT=OA,type=help,page=4 

Response 

ILM 'DISP' response for port # OA 

Help screen # 4 (MTF display commands) 


Disp port=xx type=object adr=yyyyyyyy -displays edited MTF object. 

Disp port=xx type=pool adr=yyyyyyyy -allows stepping through an object pool. 

Starting at a specified address. 


ILM> 

Figure 3–4. DISP Help Screen for MTF Information 

7831 5785–200 3–13


3–14 

Figure 3–5 illustrates the help screen for memory information. 

DISP PORT=O1f,type=help,page=5 

Response 

ILM 'DISP' response for port # 01f 

Help screen # 5 (MEMORY display commands) 

Disp port=xx -displays this screen. 

Disp port=xx type=help -displays this screen. 

Disp port=xx type=mem adr=yyyyyyyy -displays memory in 16 bit words. 

Disp port=xx type=memb adr=yyyyyyyy -displays memory in 8 bit words. 

Disp port=xx type=mem1 adr=yyyyyyyy -displays memory in 32 bit words. 

DISP port 01f type help page 1 Tab,Xmit for general display info. 

ILM> 

Figure 3–5. DISP Help Screen for Memory Information 

Note: In Figures 3–4 and 3–5, yyyyyyyy is an address in the ILM to inspect. The 

value must be preceded with 0 to denote hexadecimal. For example, 

01000480. 

7831 5785–200


3.5. Using the ILM Online Help Facility 

Format 

Parameters 

You can use the HELP command to display 

• A list of the ILM commands recognized by the ILM platform 

• Format information about a specific ILM command 

• A list of IA specific commands recognized by a named IA 

You can use the HELP command without specifying a TYPE parameter to display a list 

of the ILM commands the ILM platform recognizes (see Example 1). 

You can use the HELP command, including the TYPE parameter, to display format 

information about a specific ILM command. Example 2 shows how to use the HELP 

command to display format information about the SNAP command. 

——————————————————————————————————————— 

1. HELP [TYPE=cmd] 

2. HELP PORT=n,IA=name 

——————————————————————————————————————— 

TYPE=cmd 

The name of the ILM command that you need information about. When you enter the name of the 

command, online information appears. 

PORT=n 

The number of the port where the IA resides. 

IA=name 

The name of the IA from which you want a list of commands. 

——————————————————————————————————————— 

7831 5785–200 3–15


Example 1 

HELP 

Example 2 

3–16 

Response 

-- DISP DUMP ENV FREE 

LIST LOAD -- LOOP -- 

SET SNAP SNOF STAR STAT 

TCAT TCLS TOPN TSWT 

For Parameter Information Enter := 

HELP [TYPE=cmd] 

HELP PORT=n,IA=name 

——————————————————————————————————————— 

HELP TYPE=SNAP 

Response 

SNAP TYPE=LMH,FAC=name ,LEV= CP [,PORT=port],IA=name 

LM 

——————————————————————————————————————— 

7831 5785–200

3.6. Using the Trace Facility 


Tracing enables ILM operators to trace data paths when troubleshooting. You can send 

traces to an NMS console, to a trace file, or both. You can submit trace files in 

suitable media to the Unisys Client Support Center for analysis. (See the Telcon 

Operations Reference Manual [7831 5728] for more information.) 

The NMS SNAP and SNOF commands turn tracing on and off (Table 3–1 lists other 

ILM NMS commands). You can specify tracing to occur at several levels, ranging from 

an overview to a detailed trace. 

The ILM traces use the same set of NMS commands as Telcon. However, when you 

use them for ILM, you must be in ILM mode. One suggested way to track network 

problems is to enable traces of programs implementing protocols such as TCP/IP. 

Table 3–2. Tracing Procedures 

Step Action 

1 Enter the ILM command to enter ILM mode. 

2 Enter the TCAT command to catalog a trace file. 

Example 

TCAT file trc1 

Response 

Opened Trace File:-TRC1$$00 

3 Enter the SNAP command to request tracing levels for a line. 

Example 

SNAP FAC=lplan2,TYPE=h,LEV=lm 

Response 

Trace Turned - On 

continued 

7831 5785–200 3–17


3–18 

Step Action 

4 Enter the ianame on the IA parameter. 

5 Enter the SNOF command to turn off tracing levels for a line. (Use SNOF before you 

use the TCLS command.) 

Example 

SNOF FAC=lplan2,TYPE=h,LEV=lm 

Response 

Trace Turned - Off 

6 Enter the TCLS command to close a trace file. 

Example 

TCLS file trc1 

Response 

Trace Turned - Off 

Note: You can use the HELP TYPE=command to display information about these 

commands and their parameters. 

7 Exit ILM mode. 

8 Enter the NMS XFER command to copy the trace file to a host. 

9 Convert the word addressable host file to an omnibus element by using the COPYW 

utility (contained in the 1100ABS file) in the following format: 

@COPYW tracefile.,newfile.element 

10 Send the new file to the Unisys Client Support Center for retrieval. 

——————————————————————————————————————— 

7831 5785–200

Section 4 

Operating the TCP–IP Stack 


——————————————————————————————————————— 

This section describes NMS commands providing the diagnostic and management 

functions of the TCP–IP Stack. 


4.1 Overview 

4.2 

4.2.1 

4.2.2 

4.2.3 

Using NMS Commands for TCP–IP Stack 

Monitoring Routes, Connections, and Addresses 

Modifying Routing Tables 

Tracing TCP/IP Information 

4.3 Entering TCP–IP Stack NMS Commands 

4.4 Using the TCP–IP Stack Online Help Facility 

——————————————————————————————————————— 

7831 5785–200 4–1


4.1. Overview 

4–2 

TCP–IP Stack is a program product that provides added functions for Telcon software 

on the DCP. TCP–IP Stack operation is part of Telcon network operations and uses 

Network Management Services (NMS). 

TCP–IP Stack allows you to 

• Use network addresses that support data routing in TCP/IP networks 

• Configure 

– IP routing capabilities on a DCP 

– Default gateways 

– A DCP to function as a network bridge node between a TCP/IP network and a 

Telcon network 

• Communicate with TCP/IP networks across 

– 802.2 and 802.3 local area networks (LANs) 

– X.25 packet switched networks, including Defense Data Network (DDN), 

public data networks (PDNs), and private packet networks 

– Unisys dynamic network services (DNS) 

– OS 22000-to-DCP host channels 

TCP–IP Stack software is loaded during Telcon initialization and is configured as part 

of the Telcon configuration. 

Note: For more information on the TCP–IP Stack or the TCP/IP protocol, see the 

DCP Series TCP–IP Stack Configuration and Operations Guide 

(7831 5546). 

——————————————————————————————————————— 

7831 5785–200


4.2. Using NMS Commands for TCP–IP Stack 

TCP–IP Stack has its own specific set of NMS commands (as shown in Table 4–1). Use 

these commands to manage the TCP/IP connections in your network. 

Table 4–1. TCP–IP Stack NMS Commands 

Description Function 

Expanded NMS 

DISPLAY commands 

NMS KILL and MODIFY 

commands 

Used to monitor TCP/IP routes, connections, and addresses. 

Allow you to delete and modify information in the TCP–IP Stack routing 

tables. 

TRACE commands Used to collect information about connectivity and to turn message 

tracing on or off. 

——————————————————————————————————————— 

7831 5785–200 4–3


4.2.1. Monitoring Routes, Connections, and Addresses 

4–4 

TCP–IP Stack has expanded display facilities that you can use to monitor TCP–IP 

routes, connections, and addresses. Table 4–2 lists the TCP–IP Stack expanded NMS 

DISPLAY commands. 

Table 4–2. Expanded NMS DISPLAY Commands 

Command Function 

DISPLAY=ARP Displays the physical address-to-IP address (ARP) mappings maintained 

by TCP–IP Stack. Typically, use the DISPLAY=ARP command to 

determine if the TCP–IP Stack is communicating with, or attempting to 

communicate with, another TCP/IP host. If you use the command 

without the DEST parameter, the mappings for every address that ARP 

maintains displays. 

DISPLAY=IP Collects and displays IP runtime statistics. You can reset IP-related 

statistical counters to begin data collection at a given time. The IP 

counters have a range of 0 to 65,535 events. Items counted include 

the following: 

• Inbound segments and datagrams 

• Outbound segments and datagrams 

• Inbound and outbound fragmented datagrams 

• Datagram errors and timeouts 

You can collect and display statistics for a specific network service 

provider (NSP) interface, a specific source or destination address, or 

for all IP communications handled through the local processor. 

DISPLAY=RIPNBR Displays information on all known RIP neighbors on the Telcon DNS 

network. This information includes the neighboring IP address and the 

subnetwork associated with the neighbor. 

DISPLAY=ROUTE Display IP routing table information for either a specified destination IP 

address or for all IP addresses known to TCP–IP Stack. 

DISPLAY=SAT Displays the entire source address table for TCP–IP Stack. 

DISPLAY=TCP Displays the status of all TCP connections. You can gather this status 

based on the source or destination IP address, on both, or on a source 

or destination TCP port number. To uniquely identify a single TCP 

connection, specify all the parameters. 

——————————————————————————————————————— 

7831 5785–200

4.2.2. Modifying Routing Tables 


TCP–IP Stack NMS KILL and MODIFY commands allow you to delete and modify 

information found in TCP–IP Stack routing tables. Table 4–3 lists these commands. 

Table 4–3. NMS KILL and MODIFY Commands 


KILL=ARP Deletes ARP address mappings from the cache. Normally, these 

addresses are updated when the ARP time expires. However, to update 

them before the timer expires, use the KILL ARP command. 

KILL=RIPNBR Removes discovered RIP neighbors. 

Note: Use this command on DNS networks only. 

KILL=TCP Terminates TCP connections. Use this command to free a suspended 

TCP connection when no keep-alive mechanism is configured. You must 

use all the parameters listed to uniquely identify a TCP connection. 

MODIFY=ROUTE Modifies entries in the routing table. 

——————————————————————————————————————— 

4.2.3. Tracing TCP/IP Information 

Use TCP/IP TRACE commands to verify an IP address, collect connectivity 

information, and turn message tracing on or off. Table 4–4 lists the TCP/IP TRACE 

commands. For more detailed information on format and parameters for these 

commands, see the Telcon Operations Reference Manual (7831 5728). 

Table 4–4. TCP/IP TRACE Commands 


PING Sends an Internet Control Message Protocol (ICMP) echo request to 

another TCP–IP host. The operator or network supervisor can use this 

command to verify an IP address and receive route information. 

SNAP=IP Turns on IP message tracing in the Internet component. 

SNOF=IP Turns off the IP message tracing started by the SNAP IP command. 

Also closes an IP trace file, if one is open. 

——————————————————————————————————————— 

7831 5785–200 4–5


4.3. Entering TCP–IP Stack NMS Commands 

Format 

To enter TCP–IP Stack NMS commands, you must be using an active NMS console. To 

specify these NMS commands apply to TCP–IP Stack, you must enter the prefix TCP, 

followed by a space, before each command. 

For example, at the prompt enter: 

TCP PING 

——————————————————————————————————————— 

TCP [command] NODE= name 

[[[n/]n/]n/]n 

——————————————————————————————————————— 

Optional Parameters 

Example 

Explanation 

4–6 

command 

The name of the TCP command entered. 

NODE= name 

[ [ [ n / ] n / ] n / ] n 





——————————————————————————————————————— 

TCP DISPLAY=ARP 

——————————————————————————————————————— 

This example shows the TCP DISPLAY command used to display all ARP address 

mappings. 

——————————————————————————————————————— 

7831 5785–200


4.4. Using the TCP–IP Stack Online Help Facility 

Format 

Parameters 

The TCP HELP command activates the TCP–IP Stack online help facility. The online 

help facility provides general help information about TCP–IP Stack NMS commands 

and displays a list of accepted CMD parameter values. If no parameters are specified, 

the help facility displays a complete list of commands supported by TCP–IP Stack. 

To enter the TCP–IP Stack help facility you must be using an active NMS console. 

——————————————————————————————————————— 

TCP HELP [CMD] [TYPE] 

——————————————————————————————————————— 

CMD 

TYPE 

Provides a list of accepted values for the TYPE parameter as well as general help about the 

CMD. 

Lists any parameters that may accompany the CMD parameter. 

——————————————————————————————————————— 

7831 5785–200 4–7

Section 5 

Operating OSI Transport Services 

(OSITS) 


——————————————————————————————————————— 

This section describes how to use NMS commands to provide the diagnostic and 

management functions of OSITS. 


5.1 Overview 

5.2 Using OSITS NMS Commands 

5.3 Entering OSITS NMS Commands 

5.4 Using the OSITS Online Help Facility 

5.5 

5.5.1 

5.5.2 

Making Online Parameter Changes 

Making changes using the help facility 

Making changes with the PARAMETER command 

——————————————————————————————————————— 

7831 5785–200 5–1

Operating OSI Transport Services (OSITS) 

5.1. Overview 

5–2 

OSI Transport Services (OSITS) operations are a part of Telcon network operations 

and use the Telcon Network Management Services (NMS). The main goal of an OSI 

network is to provide reliable end-to-end communication across networks and 

subnetworks of open systems. OSITS provides 

• Reliable OSI transport services between OS 2200 hosts and other hosts 

• DTP-to-OSI transport protocol conversion 

• Transport connection management 

• Internetwork protocol management 

• Internetwork communication between 

– X.25 packet networks 

– Channels 

– FDDI, Token Ring, and 802.3 LANs 

——————————————————————————————————————— 

7831 5785–200

5.2. Using OSITS NMS Commands 


OSITS has a set of NMS commands dedicated to its use. Table 5–1 lists the OSITS 

NMS commands, gives a brief description of each, and specifies if online parameter 

changes are allowed. 

Table 5–1. OSITS NMS Commands 

Command Description Changes 

OSI ADJACENCY Displays all directly connected subnetworks. NO 

OSI AREAADDR Displays list of area addresses making up a level 1 

area. 

OSI BROADT Displays broadcast link-state protocol data unit (PDU) 

transmission interval in milliseconds. 

OSI CIRCUITS Displays current status of each network interface. YES 

OSI CLOSE Closes a specified X.25 static circuit. NO 

OSI CSEQNUM Displays complete sequence number PDU interval in 

seconds. 

OSI DEFLIFE Displays current interval (in half seconds) before 

system-generated PDUs are discarded. 

OSI DESIGIIH Displays interval time (in seconds) between the 

generation of Intermediate System-to-Intermediate 

System Hello PDUs on a LAN . 

OSI DIRECTES Enables and disables direct routing to an End System 

connected on a subnetwork, but not in the level 1 

area. 

OSI HELP Displays online help. NO 

OSI LISTEN Enables a specified X.25 static circuit to open an 

outside request. 

OSI LSPBUFSIZE Displays the current maximum size of link-state PDUs 

and sequence-number PDUs. 

OSI MAXAREAS Displays maximum number of area addresses defining 

a level 1 area. 

YES 

YES 

YES 

YES 

YES 

YES 

YES 

YES 

YES 

continued 

7831 5785–200 5–3


5–4 


OSI MAXGEN Displays maximum link-state interval seconds of PDU 

generation. 

OSI MINGEN Displays minimum link-state interval seconds of PDU 

generation. 

OSI MINXMT Displays minimum link-state interval seconds of PDU 

transmission. 

OSI NEIGHBORS Displays all OSI level 1 IS routers on circuits. NO 

OSI NEWADDR Rereads all ADDRESS configuration statements 

entered through online configuration. 

OSI OPEN Opens a specified X.25 static circuit. NO 

OSI PARAMETERS Displays changeable parameter values. NO 

OSI PING Sends an echo request to a specified network service 

access point (NSAP) and displays reply. 

OSI POLLES Displays current value of the end system configuration 

timer in intermediate system Hello PDUs. 

OSI PSEQNUM Displays partial sequence numbers of PDU intervals in 

seconds. 

OSI RECVPASS Lists additional valid passwords for incoming packets. YES 

OSI RMPASS Removes a password. YES 

OSI RMROUTES Removes a specified route. YES 

OSI ROUTES Displays OSI routing information base. YES 

OSI STATS Displays non-changeable parameter values. NO 

OSI TRACE Turns OSI IP and OSITS tracing off and on. NO 

YES 

YES 

YES 

NO 

NO 

YES 

YES 

continued 

7831 5785–200



OSI TRANSLATE Toggles from numerical NSAP addresses to ASCII 

names. 

OSI WAITTIME Displays the current delay time before entering the ON 

state. 

OSI XMITPASS Lists or modifies the chosen password for outgoing 

packets and validates incoming packets. 

——————————————————————————————————————— 

7831 5785–200 5–5 

YES 

YES 

YES


5.3. Entering OSITS NMS Commands 

Format 

Parameters 

Example 

Explanation 

5–6 

To enter OSITS NMS commands, you must be using an active NMS console (see 

Section 2 of this guide, “Opening Network Management Services”). To specify the 

commands apply to OSITS, enter the prefix OSI, followed by a space before each 

command. 

For example, at the prompt enter: 

OSI ROUTES 

——————————————————————————————————————— 

OSI [command] ,NODE= name 

[[[n/]n/]n/]n 

——————————————————————————————————————— 

command 

The name of the OSITS command entered. 

NODE= name 

[ [ [ n / ] n / ] n / ] n 





——————————————————————————————————————— 

OSI STATS NODE=PSCR1 

——————————————————————————————————————— 

This example shows the OSI STATS command used to display general system statistics 

on PRSCR1. 

——————————————————————————————————————— 

7831 5785–200


5.4. Using the OSITS Online Help Facility 

Format 

Parameters 

The OSI HELP command activates the OSITS online help facility. You can use the 

online help facility to 

• Display a list of OSITS NMS commands 

• Display information about a specific OSITS NMS command 

• Modify parameter values 

To enter the OSITS online help facility, enter the OSI HELP command on an active 

NMS console. 

——————————————————————————————————————— 

OSI HELP [command] 

——————————————————————————————————————— 

command 

The name of the OSITS command you need information about. 

Use the HELP command without specifying the COMMAND parameter to display a complete list 

of OSI NMS commands. 

——————————————————————————————————————— 

7831 5785–200 5–7


Example 1 

Explanation 

5–8 

OSI HELP 

Response 

OSI HELP 

94/07/24 03:16:54 

The following commands are valid: 

OSI ? [command] 

OSI ADJACENCY 

OSI AREAADDR [2..10 [REST | {{TEMP|PERM} area_addr}]] 

OSI BROADT [REST | {{TEMP|PERM} [1..65535]]} 

OSI CIRCUITS [REST | {{TEMP|PERM} [name status type metric [iih[ish]]]]} 

OSI CLOSE osisn_name 

OSI CSEQNUM [REST | {{TEMP|PERM} [1..600]]} 

OSI DEFLIFE [REST | {{TEMP|PERM} [1..254]]} 

OSI DESIGIIH [REST | {{TEMP|PERM} [1..60]]} 

OSI DIRECTES [REST | {{TEMP|PERM} {ENABLED|DISABLED}] 

OSI HELP [command] OSI STATS [circuitname] 

OSI LISTEN osisn_name 

OSI LSPBUFSIZE [REST | {{TEMP|PERM} [512..1492]]} 

OSI MAXAREAS [REST | {{TEMP|PERM} [1..10]]} 

OSI MAXGEN [REST | {{TEMP|PERM} [60..900]}] 

OSI MINGEN [REST | {{TEMP|PERM} [5..30]]} 

DO YOU WISH TO DISPLAY THE NEXT PAGE ? XMIT Y OR N 

Y 

OSI MINXMT [REST | {{TEMP|PERM} [5..30]]} 

OSI NEIGHBORS 

OSI NEWADDR 

OSI OPEN osisn_name 

OSI PARAMETERS 

OSI PING nsap [{count|RECORD} [[size [lifetime]]] 

OSI POLLES [REST | {{TEMP|PERM} [1..50]]} 

OSI PSEQNUM [REST | {{TEMP|PERM} [1..600]]} 

OSI RECVPASS [{ADD|index} [REST | {{TEMP|PERM} {ASCIIpassword |X'...'}}]] 

OSI RMPASS {TEMP|PERM} {index|XMITPASS} 

OSI RMROUTE {TEMP|PERM} type nsap 

OSI ROUTES [type[nsap [{TEMP|PERM} snpa [circuit [lifetime]]]]]] 

OSI TRACE {IP|TP} [hex mask] 

OSI TRANSLATE [{ENABLED|DISABLED}] 

OSI WAITTIME [REST | {{TEMP|PERM} [1..120]]} 

OSI XMITPASS [REST | {{TEMP|PERM} {ASCIIpassword | X'...'}}] 

——————————————————————————————————————— 

This command shows the OSI HELP command used to display all OSI NMS 

commands. 

——————————————————————————————————————— 

7831 5785–200

Example 2 

Explanation 

OSI HELP BROADT 

Response 


93/01/01 03:19:06 

Displays/modifies the minimum LSP transmission interval. 

——————————————————————————————————————— 

This example shows the OSI HELP command used to display information on the 

BROADT command. 

——————————————————————————————————————— 

7831 5785–200 5–9


5.5. Making Online Parameter Changes 

The OSITS NMS user interface lets you make online parameter changes to the 

configuration. You can specify permanent or temporary changes. When you make 

permanent changes (PERM), OSITS writes them to the configuration. When you make 

temporary changes (TEMP), OSITS makes changes in the memory only. 

——————————————————————————————————————— 

5.5.1. Making changes using the help facility 

5–10 

Use the following steps to make online changes from the help facility. 

Step Action 

1 At the prompt, enter the following: 

OSI HELP 

A complete list of OSITS NMS commands displays. You can change all 

commands with the following parameters: 

or 

REST | {TEMP|PERM} 

{TEMP|PERM} 

Note: Keep a list of permanent value changes. A value with a permanent 

change is written to the configuration file, but is not displayed in the 

ASCII configuration file. 

2 Enter the OSITS NMS command, followed by any chosen parameters. 

Example 

OSI ROUTES MAN 

Response 

OSI ROUTES MAN 

TYPE NSAP SNPA CIRCUIT LT 

OSI MAN 470004001200048000B50084B P 08000B50084B 

LANL1 15 

OSI MAN 4900872345678 P 08000B300617 DNS 

30 

continued 

7831 5785–200

Step Action 


3 Move the cursor to the parameter value(s) you want to change. Make the 

necessary changes. 

Note: To restore changed parameters back to the original configuration 

value, type the parameter name followed by REST. 

4 Move the cursor to the end of the line. 

5 Press the transmit key. 

——————————————————————————————————————— 

5.5.2. Making changes with the PARAMETER command 

The OSI PARAMETERS command displays a list of the OSI NMS commands with 

changeable parameter values. 

To modify the command value, use the following steps: 

Step Action 

1 Move the cursor to the value you want to change. 

2 Overwrite the value with one of the following options: 

P indicates a permanent configuration value. 

T indicates a temporary value change not registered in the configuration. 

R restores a temporary value back to the permanent configuration value. 

3 Type the new value. 

or 

Type the parameter name, followed by the new value. 

4 Move the cursor to the end of the line. 

5 Press the transmit key. 

For detailed information on OSITS NMS command formats and functions, see the 


——————————————————————————————————————— 

7831 5785–200 5–11


Example 

Explanation 

5–12 

OSI PARAMETERS 

Response 

93/01/01 03:21:35 

Intermediate System (IS) Parameters 

OSI MAXGEN P 900 

OSI MINGEN P 30 

OSI MINXMT P 5 

OSI CSEQNUM P 10 

OSI PSEQNUM P 10 

OSI BROADT P 33 

OSI LSPBUFSIZE P 1492 

OSI POLLES P 50 

OSI WAITTIME P 60 

OSI DESIGIIH P 1 

OSI DEFLIFE P 15 

OSI DIRECTES P DISABLED 

OSI MAXAREAS P 5 

OSI AREAADDR 1 47000400120004 

OSI XMITPASS FRED 

OSI TRANSLATE ENABLED 

——————————————————————————————————————— 

This example shows the display of the OSI PARAMETERS command. The command 

name and the changeable values specific to each command is listed. For an 

explanation of each value, see the Telcon Operations Reference Manual 

(7831 5728). 

——————————————————————————————————————— 

7831 5785–200

Glossary 

A 

ABM 

See asynchronous balanced mode. 

adapt 

An interface (hardware or software) that converts the data, address, and control 

formats of an attachment of one communication architecture to the data, address, 

and control formats of another communication architecture. 

ADRD 

See automatic data rate detection. 

AMS 

See application management services. 

application management services (AMS) 

The group of network control service functions associated with a particular 

applications environment. These functions are accessed, principally by 

Communication System Users (CSUs) and Network Management Services (NMS), 

to establish session paths between ports. Logically, each AMS function group is 

treated as a CSU with attached AMS end users that provide services to host 

applications for managing the activation, monitoring, control, and deactivation of 

the various application processes. 

area 

A subdivision of a network that includes one or more regions or nodes. The 

regions within an area can be in different nodes and can overlap. The area 

subdivision is controlled by the area level of NMS authority. 

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. 

7831 5785–200 Glossary–1

Glossary 

Glossary–2 

automatic data rate detection (ADRD) 

A Telcon feature that detects the line speed of an asynchronous terminal by 

sampling the irst input character. 

B 

backup host 

A host that is not actively connected to a shared application group until a system 

failure occurs on the production host. When this happens, the Hot-Standby 

software installed on the backup host attaches the backup host to the application 

group and also recovers the failing host. The backup host assumes control for the 

failed host as soon as the application group is successfully attached. The backup 

host can process non-shared batch and demand programs while the production 

host of a Hot-Standby system is running. 

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. 

bisync 

See binary synchronous communication. 

BLDDIB 

See build directory information base. 

BNF 

An OS 2200 online configuration pattern processor. See also Telcon utilities. 

broadcast 

The simultaneous transmission of data or text to a variety of users over a network 

such as radio, coaxial cable, or satellite. 

broadcast messages 

A message that is broadcast simultaneously to a variety of users over a network. 

BSC 

See binary synchronous communication. 

buffer 

A storage area in random access memory where data is temporarily placed until 

the data can be transferred to a peripheral device or the next phase of operations. 

By removing data from the immediate processing environment, buffers free the 

computer to continue processing other data. 

buffer pool 

All local storage not used by resident elements. The segment pool is a pool of 4 

kilobyte buffers. The remainder of real storage becomes a general buffer pool of 

128 byte buffers. 

7831 5785–200

Glossary 

build directory information base (BLDDIB) 

Utility used to extract information from local Telcon configuration for inclusion in 

directory information base. See also directory information base (DIB). 

C 

CAP 

See CENLOG Analysis Program. 

CENLOG 

See critical event notification and logging. 

CENLOG Analysis Program (CAP) 

An OS 2200 interactive, menu-driven utility program that runs on OS 2200 systems 

and analyzes Telcon CENLOG files transferred from the DCP. See also Telcon 

utilities. 

CENLOG events 

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. 

central processing unit (CPU) 

A unit of a computer that includes the circuits that control the interpretation and 

execution of instructions. Sometimes called central processor. 

CLC 

See communication line controller. 

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. 

communication line controller (CLC) 

A processor in a DCP/24 or DCP/40 that manages the flow of data between the 

communications processor and a set of line modules. The current family of DCPs 

uses the term input/output processor. See also input/output processor. 

communication system 

The total environment in which Distributed Communications Architecture (DCA) 

controls logical structure as well as the interfaces and protocols. Logically, the 

communication system encompasses the transport network and all the connected 

termination systems, but not the attached TSUs and their end users. 

7831 5785–200 Glossary–3

Glossary 

Glossary–4 

communication system administrator (CSA) 

A package of information-gathering facilities that enables the system analyst or 

operator to acquire information about the operation of CMS 1100. 

communication system user (CSU) 

DCA Level I only. The applications-related control structure, external to DCA, that 

interfaces with the communication system through one or more ports. CSUs 

control one or more end users, directing data and commands to and from them. 

The standard Telcon CSU is called the Device Management Facility (DMF). CSUs 

in DCA Level I can be compared with TSUs in DCA Level II. 

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. 

communications processor (CP) 

(1) A general-purpose processor for network control and message management. 

(2) The primary location of DCP processing. 

Communications Processor Architecture (CPA) 

The model for Distributed Communications Processors (DCPs). CPA defines 

relationships among DCP hardware and software components. 

COMUS 

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. See also SOLAR. 

computer network 

A set of one or more computing systems, communication facilities, and terminals 

interconnected to provide services to a set of users. 

configuration 

The arrangement of a computer system or network, defined by the nature, number, 

and chief characteristics of its functional units. 

configuration generator (HCONFIG) 

Runs on a host computer and provides a means of online configuration. 

configuration ID information table 

A table that contains configuration names and ID numbers. The HCONFIG utility 

processor builds the table automatically. The table can be altered by online 

configuration. 

7831 5785–200

Glossary 

configuration source file 

A CMS 1100 or Telcon file that contains configuration information. CMS 1100 or 

Telcon reads this file during initialization to establish the initial operating 

environment and accesses this file during operation to obtain additional 

information. 

connection 

A logical communication path between two stations or users. 

console messages 

The messages generated in the Telcon environment by Network Management 

Services (NMS) to inform you of errors, events, and activities that occur. 

CP 

See communications processor. 

CPA 

See communications processor architecture. 

CPU 

See central processing unit. 

critical event notification and logging (CENLOG) 

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. 

CSA 

See communication system administrator. 

CSU 

See communication system user. 

cycle 

A complete sequence of operations at the end of which the series can be repeated. 

D 

data collection module 

A device that captures raw data before a file is created. 

data index number 

A number that specifies the data to be used in a test. 

data set ready (DSR) 

A hardware signal. If set, the data set (modem) is connected. For a dial line 

adapter, the communication line is in use. 

DCA 

See Distributed Communications Architecture. 

7831 5785–200 Glossary–5

Glossary 

Glossary–6 

DCA host 

A central processing system that adheres to end-to-end DCA protocols and the 

TS/TN interface. The termination system or systems, and the Application 

Management System implemented within the DCA host, must conform to an 

agreed subset of DCA rules and protocols. 

DCA network 

(1) A collection of facilities and attachments in which there are at least two TS/TN 

interfaces. Although there is no architectural difference between a DCA host and a 

DCA terminal, there is a significant functional difference. A DCA terminal is not 

necessarily an intelligent terminal, since (in many cases) the termination system 

(TS) is implemented in hardware or firmware. 

(2) One or more interconnected DCA nodes. Interconnections can be direct or 

indirect, for example, through a TCP/IP or OSI internetwork connection. 

(3) A system that runs DCA protocols. Each DCA node can contain one DNS node, 

one TS/TN node, or both. DCA nodes include Telcon nodes, CMS 1100 nodes, 

System 80 nodes, DCT terminals, and DCA products supplied by another vendor. 

DCA terminal 

A special type of terminal connected to a DCP through a trunk (UDLC protocol). 

DCA terminals are commonly used as network consoles. UTS 20L, SVT 1121, and 

DDP 4000 terminals are DCA terminals. DCA terminals operate as end systems in a 

DCA network. 

DCA transport network 

The systems and protocols that provide network-wide communication services in a 

distributed computing environment. The transport network includes layers 1 

through 4 of the Distributed Communications Architecture (DCA). 

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 connections 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 I. 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 

sessions, 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). 

DCATS 

A combined acronym for Distributed Communications Architecture (DCA) and 

termination system (TS). DCATS refers to any termination system (such as an OS 

2200 host, U Series host, or DCA terminal) that functions as an end system in a 

DCA network. 

7831 5785–200

DCP 

See Distributed Communications Processor. 

DCP/OS 

See Distributed Communications Processor Operating System. 

Glossary 

DCP/OS console 

A DCP/OS virtual workstation that has been put in console mode by an operator 

who entered the DCP/OS @RUN,X command. The operator enters console 

DCP/OS commands at this workstation. 

DCP/OS utilities 

A group of utility programs for file manipulation, DCP/OS configuration, and 

program building. A disk utility program is included. 

DCP/OS virtual workstation 

A Telcon terminal that has a DCA session to the target DCP/OS. Because it is 

Telcon-owned, the workstation is virtual. The operator can enter DCP/OS Job 

Control Language (JCL) commands or Telcon commands at this workstation. 

DCP/OS workstation 

A UNISCOPE type terminal that is owned and operated by DCP/OS. Telcon owns 

the port for the terminal. 

DCPTS 

A combined acronym for Distributed Communications Processor (DCP) and 

termination system (TS). DCPTS refers specifically to a termination system on a 

DCP that operates as an intermediate system (routing node) or as a front-end 

processor in a DCA network. 

DDN 

See defense data network. 

DDP 

See distributed data processing. 

Defense Data Network (DDN) 

An X.25 LAN based connectionless packet-switched network operated by the U. S. 

Department of Defense. The DDN is a telecommunications carrier service that 

supports a large system of interconnected military and research networks, 

commonly called Internet. 

demand mode 

The mode of operation in which a terminal operator can enter a job stream 

statement-by-statement and have each statement transacted immediately (on 

demand). 

device identifier (DID) 

A character that represents the address of an auxiliary device attached to a 

UNISCOPE display terminal or UTS 400 display terminal cluster. 

7831 5785–200 Glossary–7

Glossary 

Glossary–8 

dial-up line 

A standard telephone line used with a dial telephone or an automatic dialing 

device, as opposed to a dedicated or leased line. 

DIB 

See directory information base. 

DID 

See device identifier. 

directory information base (DIB) 

The database of a directory server agent (DSA). 

directory server agent (DSA) 

A stand-alone program that enables a Telcon run or other user to access the 

directory information base (DIB). When necessary, the DSA communicates with 

other DSAs so a user only has to send updates or request information from one 

DSA. 

directory service facility (DSF) 

A Telcon function that eliminates duplication of configuration statements in 

configurations. End user information no longer needs to be replicated for each 

DCP. DSF also enables separate Telcon configurations to be run in the same 

network. Although the DSF services only DCPs, it is a DCA application (layer 7) 

implementation from the perspective of network architecture. 

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 Communications Processor (DCP) 

A special-purpose computer designed exclusively for communication applications. 

The DCP is used as a front-end processor for OS 2200 computers, or to 

interconnect networks of OS 2200 computers and other machines. Depending on 

how it is configured, a DCP can function as a remote concentrator, a 

message-switch (or nodal) processor, or a front-end processor. DCPs are available 

in several models. Compare with communication terminal module controller 

(CTMC). 

Distributed Communications Processor Operating System (DCP/OS) 

A multi-programming operating system for DCPs. DCP/OS supports architectural 

entities defined by CPA, and controls all DCP hardware operations. The DCP/OS 

executes programs that are installed from diskettes or that are initially 

downloaded to the DCP from an OS 2200 system. DCP/OS is released in absolute 

format as part of the Telcon release tape. See also Telcon. 

7831 5785–200

Glossary 

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. 

Distributed Systems Processor 

A general purpose communications processor. 

DNS 

See dynamic network services protocol. 

DNS network 

One or more connected DNS nodes. 

DNS node 

A DCA network node that uses DNS protocol at the network layer. A DNS node 

can be a Telcon node or a CMS 1100 node. 

DSA 

See directory server agent. 

DSF 

See directory service facility. 

DSP 

See distributed systems processor. 

DSR 

See data set ready. 

DTP 

See DCA transport protocol 

DTPX 

See DCA transport protocol extension 

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. 

7831 5785–200 Glossary–9

Glossary 

E 

element 

A named grouping of information typically manipulated as a unit based on a 

primary element, and typically defining a logical program part such as a 

subroutine. There are four types of elements: absolute, omnibus, relocatable, and 

symbolic. 

end user (EU) 

An individual program, or physical device, that interacts directly with the network 

and is the human and nonhuman physical and logical sources and links of 

information across the network. Nonhuman end users are the programs and 

devices that generate and receive the data transmitted over a DCA communication 

system. 

entity 

A hardware or software component named in a configuration file. Software entities 

are individual processes, or elements, operating at each layer within an open 

systems architecture (for example, session entity, transport entity). These elements 

can represent one layer, one part of a layer, or several layers of the OSI Reference 

Model. One layer can include several entities. See also service. 

EOF 

Abbreviation for end of file. See also symbolic element. 

EU 

See end user. 

external termination system (XTS) 

A termination system external to a particular DCP, such as another DCP, host, or 

terminal. Used primarily for user applications. 

F 

Glossary–10 

FEP 

See front-end processor. 

file retrieval 

The process of retrieving a file from mass storage. 

foreign file 

A user file whose name is not in the system catalog, that does not reside on the 

system volume, and whose location on disk is specified by its data set label. 

front-end processor (FEP) 

A communication computer associated with a host computer. It can perform line 

control, message handling, code conversion, error control, and application 

functions such as control and operation of terminals. The function of the FEP is to 

offload the communication-related functions from the host. 

7831 5785–200

Glossary 

full-duplex 

A communication circuit that can transmit and receive data simultaneously across 

a serial or parallel communication link. Compare with two-way simultaneous, a 

function of software. 

H 

half-duplex 

A function of hardware, where both ends of a communication circuit can transmit 

and receive data, though not simultaneously. Compare with two-way alternate, a 

function of software. 

HCONFIG 

A configuration processor that converts configuration statements to omnibus 

elements that Telcon can read. See also Telcon utilities. 

HLC 

See host LAN controller. 

host 

A medium to large central processor attached to a network. Also referred to as an 

end system. The host is generally dedicated to data processing functions, such as 

executing application or system programs, rather than data communication 

functions. Architecturally, there is no distinction between a DCA host and a DCA 

terminal, since both contain a termination system, although of vastly differing 

powers. In SNA, a host is defined as an SNA node that contains a PU Type 5. See 

also backup host, Hot-Standby host, production host. 

host LAN controller (HLC) 

A control unit that connects a host to an IEEE 802.3 LAN. The HLC connects to a 

host through a block multiplexer channel. 

Hot-Standby 

A Resilient Systems software product that ensures the availability of Series 2200 

and 2200 system hardware and software. Hot-Standby uses redundant hardware 

and software to create an uninterruptible system. From the end user's viewpoint, 

the system never goes down. If a critical component (such as a processor) fails, 

the workload automatically switches to another host in the loosely coupled 

configuration. Features related to Hot-Standby exist in Exec/TIP, UDS/IRU, and 

communication software such as MCB, CMS 1100, and Telcon. 

Hot-Standby host 

A backup host or a production host in the Hot-Standby system. Hot-Standby is a 

dual-host system (for example, two 2200/92 systems) in which one host is the 

production host and the other is a backup host. The backup host can process 

batch and demand runs while the production host is running TIP, batch, and 

demand runs. Each host has its own operating system, mass storage, and shared 

mass storage. 

7831 5785–200 Glossary–11

Glossary 

I 

IA 

Glossary–12 

See interface application. 

ILM 

See intelligent line module. 

ILM Manager 

The operations feature of the ILM Platform. The ILM Manager executes in the ILM 

and implements a basic operator interface that allows the operator to collect 

statistics, log service calls, perform tracing and debugging. 

ILM Platform 

A Unisys product that provides a common software environment for ILM 

applications. These applications provide specific functions, such as asynchronousto-UTS 

protocol conversion, and UDLC protocol handling. The ILM Platform 

resides in both the CP and the ILM and creates a pipeline between the two that 

ILM applications can use. 

initial program load (IPL) 

A load from a host processor (or a DCP, for a remote load). An IPL places the 

generated system on mass storage and completely loads and initializes the system. 

input 

(1) Information or data to be entered in computer storage from tape, keyboard, or 

disk devices. 

(2) The devices used to input data, such as a tape reader. 

input/output processor (IOP) 

An independent hardware processor (within a DCP) that implements virtual port 

processors (PPs), which manage line modules. IOPs can support up to 16 different 

interfaces, which provide a powerful programmable communication channel. The 

IOP provides the line handling protocol required by a particular type or class. 

Previously, IOPs were referred to as communication line controllers (CLCs). 

intelligent line module (ILM) 

A special line module that contains an M68XXXX microprocessor and dedicated 

main memory, enabling an ILM to perform communications processing functions 

that previously had to be performed by the communications process (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. 

interface 

(1) A shared boundary between two identifiable entities. 

(2) Hardware or software designed to ensure that two other pieces of hardware or 

software function as a single unit. 

7831 5785–200

Glossary 

interface applications (IA) 

Independent programs that operate in cooperation with the ILM Manager and run 

from the ILM platform. There are two types of IAs; standard ILM (such as FDDI 

IA and Ethernet) or user-created. 

internet protocol (IP) 

The routing protocol that resides at the internet (network) layer (layer 2) of the 

TCP/IP architecture model. The TCP/IP internet protocol is based on MIL-STD 

1777 specifications for the Defense Data Network system. The IP is a 

connectionless datagram protocol that routes data to host systems within a 

complex system of complex system of multiple network nodes and interconnected 

networks. The IP provides datagram service, delivery service, general network 

services, and error reporting services. compare with OSI internetwork protocol. 

I/O 

Abbreviation for input/output. 

IOP 

See input/output processor. 

IP 

See internet protocol. 

IPL 

See initial program load. 

L 

LCB 

See line control block. 

level 

A logical structure in which the system is partitioned into a number of levels or 

layers. It is normally applied to software where each level transforms lower layers 

(nearer the hardware) or virtual machines into more useful machines. 

line 

The conductors that connect communication devices in a physical circuit. 

line control block (LCB) 

The in-core control table that contains information for controlling a physical 

communication line. 

line module (LM) 

The hardware in the DCP that terminates and controls data transmission of serial 

communication lines, host channel connections, and peripheral connections. 

line parameter 

A line parameter is necessary during testing procedures if the line to be tested is 

configured as a dial-up line. 

7831 5785–200 Glossary–13

Glossary 

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, 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). 

line switch module (LSM) 

A module 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. 

LM 

See line module. 

logging central node 

The node that centrally logs event messages in a network. Logging can be done 

locally or at a logging central node. 

loopback test 

The circuit configuration in which test signals are returned by a remote terminal to 

the originating point. 

LPH 

See line protocol handler. 

LPHTRS 

See line protocol handler terminal resource services (LPHTRS) 

LSM 

See line switch module. 

M 

Glossary–14 

mass storage 

The ancillary memory storage media, usually disk subsystems. 

MCC 

See multichannel communications controller. 

MCT 

See message control table. 

7831 5785–200

Glossary 

message control table (MCT) 

The programming vehicle for passing messages through the DCP series systems. 

multichannel communications controller (MCC) 

An interface between remote terminals and a 90/60, a 90/70, or a 90/80 virtual 

processor. 

N 

NDS 

See configuration statement. 

network 

A group of hardware and software components that are physically and logically 

linked, and that interact according to established protocols. Network functions are 

determined by the types of cooperating application systems within the network. 

network address 

(1) The unique address supplied by the PDN that identifies a node of the network. 

(2) The address of a DNS node, which consists of the following hierarchical 

components: subnetwork number, super cluster number, simple cluster number, 

and node number. 

(3) In OSI, the network address that identifies transport entities in the network 

layer (layer 3 of the OSI model). 

network administrator 

(1) The person responsible for trouble-free, efficient operation of a data 

communication network. 

(2) A person or program that uses Network Management Services (NMS) for 

external control and monitoring all or part of a communication system. 

network commands 

The instructions an operator enters to change or display the status of network 

entities. In CMS 1100, network commands are referred to as communication 

system administrator (CSA) commands. 

network connection 

A connection, used by the DCA transport protocol (DTP), between two peer 

transport layer entities. The network connection replaces the logical port in DTP. 

network definition statement (NDS) 

See configuration statement. 

7831 5785–200 Glossary–15

Glossary 

Glossary–16 

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 is subdivided into a hierarchy of control points. 

The network control ports are linked to the Applications Management System 

(AMS) ports through a preestablished session path to control the total network. 

NMS commands are the Telcon equivalent of the CMS 1100 communication system 

administrator (CSA) commands. 

network supervisor 

Same as network administrator. 

Nine Thousand Remote 

A program that controls communication between a Telcon network and any 

terminal using NTR batch communication protocol. 

NMS 

See Network Management Services. 

NMS authority 

A Telcon feature that enables you to configure NMS consoles with varying levels 

of control over the network. These levels are classified by the following network 

subdivision: region, node, area, and global. 

nodal processor (NP) 

A processor that performs communication (message-switching) functions at a node 

in a network. 

node 

(1) A data communication device that follows the instructions of the host 

computer to control various functions that ultimately affect the network. 

(2) An intersection of two or more trunks in a network that uses Telcon. 

(3) An element that supports dynamic network services (DNS) in a network that 

uses Telcon. 

(4) A network switch in public data networks (PDNs). 

NP 

See nodal processor. 

NTR 

See Nine Thousand Remote. 

7831 5785–200

O 

Glossary 

online configuration 

A means of dynamically modifying or extending a network that is already 

operating. Online configuration also enables networks to be built using it as the 

primary means of network generation. 

operating system (OS) 

A set of computer programs that control the operation of a computer and 

peripherals. These programs perform many housekeeping tasks for those who use 

the computer system. The operating system includes the entire set of system 

software available for the system that is either a part of, or operates under, the 

Exec system. This includes the Exec system proper, compilers, utility programs, 

and subroutine libraries. The operating system handles input and output, processes 

runs, allocates system resources, manages files and data, generates programs, and 

provides a library of useful subroutines. 

OS 

See operating system. 

OS 2200 

System software for Series 2200 systems. 

OSI Transport Services (OSITS) 

The software that provides a system foundation from which to route messages, 

connect devices to the network, and detect transmission errors. OSITS is a Telcon 

program product that implements the ISO transport and internetwork protocols. It 

connects a DCP to an OSI network using either X.25 or 802.3 lower layer 

protocols. OSITS provides OSI data transport services for message handling system 

(MHS) and file transfer, access, and management (FTAM) applications operating 

on OS 2200 systems. Transport services generally reside among the lower four 

layers of the OSI Reference Model. 

OSITS 

See OSI Transport Services. 

P 

packet 

(1) A defined data area in memory (a contiguous set of words) that is used to pass 

parameters between two programs. Packets contain information for executing an 

operation or function such as controlling data routing and assembling and 

disassembling messages. 

(2) A self-contained portion of data routed through a communication network by a 

connectionless (datagram or packet-switching) protocol. 

7831 5785–200 Glossary–17

Glossary 

Glossary–18 

packet (X.25) 

A packet is a layer 3 block of information. Data is transmitted from DTE-to-DTE in 

packets. Packets are transmitted through a network using the information field of 

layer 2 frames. Different types of packets are concerned with call set-up, flow and 

error control, and transmission of data. The data field of a layer 3 packet is used 

to communicate higher layer data and control information. 

packet layer services (PLS) 

(1) A feature of PSCS that gives application software (in a Series 2200 host) access 

to the X.25 services of the PSCS level 3/4 platform. 

(2) A dedicated communication link between two stations. 

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 

packet-switched 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. 

PCF 

See permanent correction file. 

PCR 

See process control register. 

PCT 

See program control table. 

PDN 

See public data network. 

PDT 

See physical device table. 

PDU 

See protocol data unit. 

peripheral device 

A device configured for DCP/OS use which is not a part of the CPs, IOPs, or 

memory. 

7831 5785–200

Glossary 

permanent correction file (PCF) 

A permanent file of symbolic correction elements with which you can create and 

update a variety of symbolic elements. 

PGT 

See poll group table. 

physical device table (PDT) 

A table that contains the name and device-dependent details of every device 

configured for DCP/OS use. It is built by the system loader using information from 

the program control table (PCT). 

PID 

See port identifier. 

poll group table (PGT) 

The in-core control table that contains information for controlling a poll group on 

a UNISCOPE display terminal communication line. 

port 

The unique physical address of each line module installed in a DCP. See also port 

number. 

port identifier (PID) 

A numeric identifier that gives the location of ports in a DCP. 

port number 

The physical address of a DCP line module. For example, the port number can be 

specified in a configuration source file for a cross-channel load or a 

communication line download through a specific line module. 

port processor (PP) 

A virtual processor within a DCP IOP, on which the line protocol handler (LPH) 

operates in the communications processor with an external terminal or device. 

PP 

See port processor. 

process control register (PCR) 

A hardware entity in the DCP that is used to direct processes. 

production host 

The online Series 2200 hardware system. In a Resilient System, the production host 

can process TIP, batch, and demand runs. See also backup host. 

program control table (PCT) 

A table maintained by the Exec for each active run in the system. The PCT 

contains control information about a particular run and the program currently 

executing within the run. The PCT also includes the list of files assigned to the 

run. 

7831 5785–200 Glossary–19

Glossary 

protocol 

The set of rules or conventions used to govern the interactions of processes, 

applications, or components within the system. 

protocol data unit (PDU) 

A unit of protocol control information and service user data that is prepared by 

the underlying service and exchanged between peer service providers across a 

logical connection. PDUs are exchanged between peer service providers. Service 

data units (SDUs) are exchanged between peer service users and are transferred 

across service access points (SAPs) in the form of interface data units (IDUs). 

SDUs remain intact and are carried in PDUs on behalf of service users. 

PSCS 

See Packet Switched Communications Software and X.25 Packet Switched 


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 


Q 

queue 

A line or group of items waiting to be processed. These items are usually in-core 

and chained together by address words. 

R 

Glossary–20 

RC 

See remote concentrator. 

region 

A network subdivision that consists of one or more lines connected to a single 

DCP, and all the entities connected to those lines. The region subdivision is 

controlled by the region level of NMS authority. 

relocatable element 

An element containing a program part in relocatable binary format, suitable for 

combining with other relocatable elements to produce an executable program 

(absolute element). Relocatable elements are most commonly the output of a 

language processor for input to a collection. They are usually produced by MASM 

from the source element and stored in a temporary program file. 

7831 5785–200

Glossary 

remote concentrator (RC) 

A communication computer (usually a DCP) with a direct connection to only one 

termination system (TS) of the two TSs that make up the end points of a session. 

This enables multiplexed communication between many low-speed synchronous or 

asynchronous lines and one or more high-speed, usually synchronous, lines. The 

remote concentrator can be polled by a computing system and can in turn poll 

terminals. For example, if several terminals are directly connected to a node (the 

RC), messages from the RC can go to another node (an FEP), then to a host. 

Remote File System (RFS) 

A system that consists of a set of related functions for manipulating files across a 

distributed computing network. The RFS communicates with peers on other 

systems (any host or DCP in the network) to create, purge, and copy files. 

remote identifier (RID) 

A character representing the address of a poll group in a UNISCOPE display 

terminal communications line. 

response number 

A number that can be entered with commands to relate output with input. The 

number displays with the output response. 

RFS 

See Remote File System. 

RID 

See remote identifier. 

route 

A path through the transport network whose identity is assigned when the 

transport network session is established. This route ID is subsequently appended 

to the message header. 

route control (RTC) protocol 

A protocol that determines the transport network route or path over which 

particular network data units (NDUs) travel to reach the paired data unit control 

(DUC) entity. RTC applies one of a selection of routing algorithms according to 

the needs of the transport network. 

routing node 

(1) A node that enables data related to Network Management Services (NMS) to be 

transferred around a network even when two end points do not have an 

established session. 

(2) An intermediate node that routes messages to other destinations within the 

network. 

routing table 

An internal database that TCP–IP Stack uses to find IP routers. 

7831 5785–200 Glossary–21

Glossary 

RTC 

See route control protocol. 

runstream 

A sequence of linked Exec control language (ECL) statements that form a selfcontained 

unit of work. 

S 

Glossary–22 

SCR 

See system control register. 

SCT 

See system control table. 

service 

(1) A collection of communications processing functions provided by one or more 

entities at a given architecture layer, plus the combined functions of all supporting 

lower layer entities in the communications processing path. One specific service, 

compared to another specific service, may require a different combination of 

entities at each layer to provide the appropriate hierarchy of functions. The 

services available at a given layer depend on services available at subsequent 

layers. 

(2) A computer routine or program that performs computer system maintenance 

and operations and prepares and corrects programs. Services are general purpose 

programs such as debugging routines, executive routines, diagnostic routines, and 

general input/output routines. 

session path 

The logical path through the network from one end user to another, including any 

internal associations within the CSU environment. 

SID 

See site identifier. 

site-developed code 

All code written and controlled by users. This includes applications programs and 

site-developed code in any of the communication network processors. Formerly 

called user-own-code. 

site identifier (SID) 

A 1- to 8-character identifier for a terminal. 

SOE 

Abbreviation for start-of-entry. ASCII character code IE, which determines start of 

input on UNISCOPE compatible terminals, up to the cursor position. 

7831 5785–200

Glossary 

SOLAR 

Acronym for Software Library Administration, an installation facility for all Unisys 

software products. SOLAR is the successor to COMUS, which it replaces. SOLAR 

simplifies the installation process and makes it the same for all Unisys software. 

SRL 

See system registration log. 

SSG 

See symbolic stream generator. 

SSN 

See system segment number. 

SST 

See system segment table. 

start of entry 

See SOE. 

STE 

See symbol table entry. 

symbol table entry (STE) 

A ten word structure in the symbol table that names a configured facility. The 

name is the user-assigned first field of a Telcon configuration statement. 

symbolic element 

An element containing information generally in a format intelligible to humans. The 

most common use of symbolic elements is as source language to be input to a 

language processor. A symbolic element contains variable-length text records 

terminated by end-of-file sentinels. Each record begins with a 16-bit count that 

specifies the number of data bytes in the record. The ASCII data bytes follow. 

Each element ends with an end-of-file terminator that is a record byte count of 

X'FFFF'. 

Symbolic Stream Generator (SSG) 

A general purpose Series 2200 language processor that creates and manipulates 

symbolic streams. By using the SSG, temporary correction files (TCFs) and 

permanent correction files (PCFs) can be updated, merged with another set of 

corrections, printed in the symbolic output stream, or reinserted in the original 

input file for future programming. The SSG creates a runstream that, when 

executed, generates software on an OS 2200 system. 

system control register (SCR) 

A set of sixteen 32-bit registers that provide information for all communications 

processing. 

system control table (SCT) 

A table that provides pointers to the port processor control tables, starting and 

stopping mechanisms, and other port processor controls. 

7831 5785–200 Glossary–23

Glossary 

system registration log (SRL) 

A document created by COMUS when you enter the REGISTER command. SRLs 

contain data related to a product release master tape or a separately packaged 

feature tape. 

system segment number (SSN) 

A number that identifies entries in the system segment table. 

system segment table (SST) 

A table in which program data can be stored. The SST starts at a fixed block 

number in an absolute element and is used as a directory for the rest of the 

system. 

T 

Glossary–24 

task 

(1) An item of work that an activity is scheduled to perform. 

(2) A discrete processing step in a run, involving the execution of an absolute 

element. Synonymous with program in run processing contexts. 

TCB 

See terminal control block. 

TCF 

See temporary correction file. 

TCP 

See transmission control protocol. 

TCP/IP 

See transmission control protocol/internet protocol. 

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 front-end communications for OS 2200 hosts running DDN 1100, which 

provides two TCP/IP applications-file transfer protocol (FTP) and simple mail 

transfer protocol (SMTP). TCP–IP Stack enables communication with peer devices 

running compatible TCP/IP software. 


A Unisys distributed communications software system for data communication 

networks. The software runs in a Distributed Communications Processor (DCP) 

and is defined by the Distributed Communications Architecture (DCA). Telcon 

software handles communication connections to CMS 1100, Telcon software in 

other DCPs, various terminal types, and other DCA compliant entities. 

7831 5785–200

Glossary 

Telcon network 

One or more interconnected Telcon nodes. Node interconnections can be direct or 

indirect. A node interconnection can be through an intermediate CMS 1100 node or 

through a TCP/IP or OSI internetwork connection. 

Telcon node 

A Telcon program in a DCP. Each DCP can contain more than one Telcon node. 

Each Telcon node has a separate configuration file. 

Telcon terminal 

A terminal that is owned and operated by Telcon. Telcon owns the port for the 

terminal. 

Telcon utilities 

Group of absolute elements that execute on an OS 2200 host. See also BNF, 

CENLOG Analysis Program (CAP), and HCONFIG. 

temporary correction file (TCF) 

A temporary file of symbolic correction elements used to create or update a 

permanent correction file (PCF) or a variety of symbolic elements. 

terminal 

A device for sending or receiving data over a communications channel. 

terminal control block (TCB) 

The Telcon in-core control table that contains information needed to control a 

terminal on a communication line. 

terminal resource services (TRS) 

The Telcon module that manages resources for terminals. This includes allocating 

and removing resources as needed. 

termination system (TS) 

A facility that enables an application system to interface with another application 

system and use the services provided by the communication system. 

trace 

A diagnostic technique used to isolate data flow in computer programs. This 

process records the sequence in which the program instructions were executed. 

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. 

7831 5785–200 Glossary–25

Glossary 

transmission control protocol/internet protocol (TCP/IP) 

A set of protocols developed by the Department of Defense 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. 

Some UNIX vendors integrate TCP/IP communication software into operating 

system software. 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). 

transaction 

A real-time sequence of operations in which an input message from a terminal is 

followed by an output response from a host. 

transport connection 

A connection established between two or more session entities, identified by their 

transport service access point (TSAP) addresses, to exchange transport service 

data units. In DTP, transport connection replaces system session. 

TRS 

See terminal resource services. 

TS 

See termination system. 

TS/TN 

A combination of the terms termination system (TS) and transport network (TN), 

both defined in this glossary. TS/TN is a connection-oriented protocol that handles 

the TS/TN interface. 

TS/TN network 

One or more interconnected TS/TN nodes. 

TS/TN node 

A DCA network node that uses TS/TN protocols (TS/TN, RTC) at the network 

layer. A TS/TN node can be a Telcon node, CMS 1100 node, or DCA terminal. 

U 

Glossary–26 

UCF 

See user communication form. 

UDLC 

See universal data-link control. 

7831 5785–200

UDM 

See undeliverable message. 

Glossary 

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. 

UNISCOPE 

(1) A Unisys interactive synchronous line protocol for display terminals. 

(2) An early series of Unisys (Sperry Univac) nonintelligent interactive display 

terminals. 

universal data-link control (UDLC) 

A set of data-link protocols defined by Unisys for carrying data over a data link 

with error and flow controls. UDLC can be compared with the high-level data-link 

control (HDLC) procedure defined by ISO and the synchronous data-link control 

(SDLC) procedure developed by IBM. 

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. 

User Communication Form (UCF) 

The form used at computer sites to report system problems to Unisys. Formerly 

called System User Report (SUR). 

USM 

See unsolicited message. 

X 

X.25 Packet-Switched Communications Software (PSCS) 

See Packet-Switched Communications Software. 

7831 5785–200 Glossary–27

Bibliography 

DCP Series Communications Delivery Software Operations Guide (7831 5777). 

Unisys Corporation. 

DCP Series Distributed Communications Processor Operating System (DCP/OS) 

Operations Reference Manual (7831 5702). Unisys Corporation. 

DCP Series Distributed Communications Processor Operating System (DCP/OS) 

Programming Reference Manual (7431 6894). Unisys Corporation. 

DCP Series Intelligent Line Module Asynchronous-to-UTS Converter Configuration 

and User Guide (7831 5801). Unisys Corporation. 

DCP Series Intelligent Line Module Asynchronous-to-UTS Converter Software Release 

Announcement (7831 6155). Unisys Corporation. 

DCP Series LAN Platform Configuration and Operations Guide (7831 5512). 


DCP Series OSI Transport Services (OSITS) Configuration and Operations Guide 

(7831 5587). Unisys Corporation. 

DCP Series OSI Transport Services (OSITS) Programming Reference Manual 


DCP Series Systems, System Reference, Volumes I, II, and III (UP–8720, Rev.2). 


DCP Series TCP–IP Stack Configuration and Operations Guide (7831 5546). 


DCP Series TCP–IP Stack Programming Reference Manual (7831 5561). 


DCP Series TCP–IP Stack TELNET User Guide (7831 5553). Unisys Corporation. 

DCP Series Telcon Configuration Guide (7831 5678). Unisys Corporation. 

DCP Series Telcon Configuration Reference Manual (7831 5686). Unisys Corporation. 

DCP Series Telcon End Use Guide (7436 0736). Unisys Corporation. 

DCP Series Telcon Implementation Reference Manual, Volumes 1, 2, and 3 

(UP–12728). Unisys Corporation. 

7831 5785–200 Bibliography–1

Bibliography 

Bibliography–2 

DCP Series Telcon Installation Guide (7831 5645). Unisys Corporation. 

DCP Series Telcon Internals Programming Reference Manual (UP–9255). 


DCP Series Telcon Message Manual (7436 0728). Unisys Corporation. 

DCP Series Telcon Operations Reference Manual (7831 5728). Unisys Corporation. 

DCP Series Telcon Terminal Handler Platform Programming Reference Manual 

(UP-13460). Unisys Corporation. 

DCP Series X.25 Packet Switched Communications Software (PSCS) Configuration 

and Operations Guide (7831 5470). Unisys Corporation. 

DCP Series X.25 Packet Switched Communications Software (PSCS) Programming 

Reference Manual (7831 5496). Unisys Corporation. 

DCP Series X.25 Packet Switched Communications Software (PSCS) X.28/Packet 

Assembler/Disassembler (PAD) End Use Guide (7831 5488). Unisys Corporation. 

OS 1100 Communication Management System (CMS 1100) Configuration Reference 

Manual (7830 9853). Unisys Corporation. 

OS 1100 Communications Management System (CMS 1100) Operations Reference 


OS 1100 Communications Management System (CMS 1100) Programming Reference 


OS 1100 COMUS End Use Reference Manual (7830 7758). Unisys Corporation. 

OS 1100 COMUS Installation and Configuration Guide (7830 9846). 


OS 1100 Distributed Communications Architecture (DCA) Technical Overview 

(UP–9676 Rev. 1). Unisys Corporation. 

OS 1100/DCP Series Open Systems Communications Software Conceptual Overview 


7831 5785–200

Index 

A 

abbreviating 

commands, 2–20 

parameters, 2–20 

accessing 

ILM user interface, 3–4 

NMS functions, 1–5 

activating trace facilities 

using SNAP command, 3–8 

adding 

poll groups, 2–21 

ADDM command 

described, 2–13 

addresses 

TCP–IP, monitoring, 4–4 

ADJACENCY command 


AREAADDR command 


authority levels 

NMS, illustrated, 2–6 

auxiliary screen control 

customizing screens, 2–11 

printing console messages, 2–10 

using response numbers, 2–12 

B 

broadcast messages 

commands, described, 2–13 

creating files, 2–13 

manipulating, 2–13 

BROADT command 


C 

CENLOG messages 

displaying, 2–3 

central logging and displaying 


CHAD command 


CHAM command 


characters 

required, described, x 

CHAT command 


CIRCUITS command 


CLOSE command 


command conventions 

examples, ix 

command notation conventions 

examples, viii 

commands 

auxiliary screen control, using, 2–10 

broadcast message, described, 2–13 

HELP, for OSITS, 5–7, 5–10 

HELP, for TCP–IP Stack, 4–8 

ILM HELP, using, 3–16 

ILM NMS, described, 3–7 to 3–8 

NMS HELP, using, 2–17 

NMS, rules for entering, 2–20 

OSITS NMS, described, 5–3 

OSITS online help, example, 5–8 

TCP–IP NMS, described, 4–3 

unsolicited messages, described, 2–15 

connections 


console messages 

printing, 2–10 

control centers 


7831 5785–200 Index–1

Index 

controlling 

USM file contents, 2–15 

conversational mode 

entering, 3–4 

creating 

broadcast message files, 2–13 

unsolicited message files, 2–13 

CSEQNUM command 


customizing 

NMS screen size, 2–11 

D 

defining 

insert line, 2–11 

release level, 2–8 

revision level, 2–8 

source configuration file, 2–8 

DEFLIFE command 


DELM command 


DELQ command 


DESIGIIH command 


DIRECTES command 


DISM command 


DISP command 


using, 3–9 

DISP HELP command 


DISP help facility 

entering, 3–9 

DISP help screens 

explained, 3–10 

illustrated, 3–10 to 3–14 

DISPLAY command 

expanded NMS 

for TCP/IP, described, 4–3 to 4–4 

DISPLAY=ARP command 


Index–2 

DISPLAY=IP command 


DISPLAY=RIPNBR command 


DISPLAY=ROUTE command 


DISPLAY=SAT command 


DISPLAY=TCP command 


displaying 

CENLOG messages, 2–3 

event classes, 2–3 

ILM commands, 3–16 

network events, 2–3 

OSI NMS commands, 5–12 

OSITS NMS commands, 5–7 

TCP–IP Stack help information, 4–8 

DISQ command 


DNS (See Dynamic Network Services) 

DUMP command 


Dynamic Network Services (DNS) 


E 

end users 

access to networks, 1–7 


entering 

CMS 1100 commands, x 

DCP/OS commands, x 

DISP help facility, 3–9 

ILM conversational mode, 3–4 to 3–5 

NMS commands, 2–20 

online help facility, for OSITS, 5–7 

OSITS NMS commands, 5–6 

TCP–IP Stack commands, 4–7 

Telcon commands, x 

ENV command 


event classes 

logging and displaying, 2–3 

exiting 

ILM conversational mode, 3–6 

7831 5785–200

F 

format 

for NMS HELP command, 2–17 

FREE command 


functions 

NMS, logging and displaying, 2–3 

H 

hardware 

requirements, described, 1–3 

HELP commands 

ILM NMS, described, 3–7, 3–16 

NMS, described, 2–17 

OSI, illustrated, 5–8 to 5–9 

OSITS, described, 5–3, 5–8 to 5–9 

TCP–IP Stack, described, 4–8 

I 

IAs (See Interface Applications) 

ILM (See Intelligent Line Module) 

ILM conversational mode 

using, 3–5 

Intelligent Line Module (ILM) 

commands, accessing, 3–4 

commands, displaying, 3–16 

conversational mode, described, 3–5 


diagnostics, online, 3–2 

getting help, 3–9 to 3–16 

manager, described, 3–3 

NMS commands, listed, 3–7 

platform, described, 3–3 

tracing procedures, 3–18 

troubleshooting, online, 3–2 

user interface, described, 3–4 

using commands, 3–7 

Interface Applications (IAs) 


ISDM command 


K 

KILL command 


KILL=ARP command 


KILL=RIPNBR command 


KILL=TCP command 


L 

LIST command 


LISTEN command 


LOAD command 


local logging and displaying 


logging 

CENLOG messages, 2–3 

event classes, 2–3 

LOOP command 


LSPBUFSIZE command 


M 

MAXAREAS command 


MAXGEN command 


message files 

controlling, 2–15 

MINGEN command 


MINXMT command 


Index 

7831 5785–200 Index–3

Index 

MODIFY command 



MODIFY=ROUTE command 


monitoring 

TCP–IP routes, connections, 

addresses, 4–4 

N 

NEIGHBORS command 


network 

access, restricting, 2–5 

administrators, described, 1–7 

components, described, 1–3 

control centers, described, 1–5 

divisions, illustrated, 2–6 

DNS, described, 1–2 

managing TCP/IP connections, 4–3 

multiple node, described, 1–5 

multiple node, illustrated, 1–6 

node, described, 1–2 

OSI, described, 5–2 

single node, described, 1–5 

Telcon, described, 1–3 

Telcon, illustrated, 1–4 

Telcon, types of, 1–5 

X.25 packet-switched, described, 1–2 

Network Management Services (NMS) 

authority levels, described, 2–5 

command characteristics, 


command format example, 2–18 

defining insert lines, 2–11 


entering commands, rules for, 2–20 

opening, steps for, 2–7 

NEWADDR command 


NMS (See Network Management Services) 

node 

network, described, 1–2 

notation conventions 

described, viii to ix 

numbers 

using in NMS commands, 2–20 

Index–4 

O 

online help 

ILM, described, 3–16 

OSITS, described, 5–7 

TCP–IP, described, 4–8 

online parameter changes 

procedure for, 5–11 

OPEN command 


opening 

NMS, steps for, 2–7 

OSI protocol 


OSI Transport Services (OSITS) 

changing parameters, 5–11 


entering commands, 5–6 

getting help, 5–7 

NMS commands, described, 5–3 

specifying commands, 5–6 

OSITS (See OSI Transport Service) 

P 

parameters 

changing online, 5–11 

characteristics, 2–21 

separating, ix 

PARAMETERS commands 


PING command 

OSITS, described, 5–4 

TCP–IP Stack, described, 4–5 

poll groups 

adding, 2–21 

POLLES command 


printing 

console messages, 2–10 

protocols 


PSEQNUM command 


7831 5785–200

R 

RECVPASS command 


response numbers 

using, 2–12 

restricting 

network access, 2–5 

RMPASS command 


RMROUTES command 


routes 


ROUTES command 


routing table 

modifying, 4–5 

S 

SET command 


SNAP command 


SNAP=IP command 


SNDM command 


SNOF command 


SNOF=IP command 


software 

ILM, described, 3–2 

Telcon components, described, 1–3 

STAR command 


STAT command 


STATS command 


T 

TCAT command 


TCLS command 


TCP/IP Protocol 


TCP–IP Stack 

addresses, monitoring, 4–4 

connections, monitoring, 4–4 


display facilities, using, 4–4 

entering commands, 4–7 

HELP command, illustrated, 4–8 

KILL command, described, 4–5 

MODIFY command, described, 4–5 

modifying routing tables, 4–5 

NMS commands, described, 4–3 

online help facility, 4–8 

routes, monitoring, 4–4 

TRACE commands, described, 4–5 

tracing information, 4–5 



network, described, 1–3 

network, illustrated, 1–4 

networks, types of, 1–5 

users, described, 1–7 

TOPN command 


trace 

facility, using, 3–18 

OSI, described, 5–4 

ILM information, 3–18 

procedures, described, 3–18 

TRACE commands 


tracing 


procedures, described, 3–18 

TRANSLATE command 


TSWT command 


Index 

7831 5785–200 Index–5

Index 

U 

unsolicited message (USM) 

commands, described, 2–13, 2–15 

files, controlling, 2–15 

UP command 


user interface 

OSITS NMS, using, 5–11 

USM (See unsolicited message) 

W 

WAITTIME command 


X 

X.25 packet-switched network 


XMITPASS command 


XTS parameter 


Index–6 

7831 5785–200

DCP Series Telcon Operations Guide - Public Support Login - Unisys

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?