The DMS-100 I/O System
691002656306392c07bee09e237b75b2e182ca385e2e2d20d43b97efebbca0d7
NORTHERN TELECOM PRACTICE 297-1001-129
ISSUED: 93 09 29
RELEASE: 06.03 STANDARD
DIGITAL SWITCHING SYSTEMS
DMS*-100 FAMILY
INPUT/OUTPUT SYSTEM
REFERENCE MANUAL
* DMS is a trademark of Northern Telecom
Page 1
83 pages
PRACTICE 297-1001-129
RELEASE: 06.03
(c) Northern Telecom 1984-1987, 1990-1993
Page 2
PRACTICE 297-1001-129
RELEASE: 06.03
CONTENTS
PAGE
1. INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . 5
General . . . . . . . . . . . . . . . . . . . . . . . . 5
Practice Application . . . . . . . . . . . . . . . . . . 5
Reason for Reissue . . . . . . . . . . . . . . . . . . . 5
Software Identification . . . . . . . . . . . . . . . . 5
Command Format Conventions . . . . . . . . . . . . . . . 5
References . . . . . . . . . . . . . . . . . . . . . . . 7
2. INPUT/OUTPUT HARDWARE . . . . . . . . . . . . . . . . . 8
Input/Output Controller . . . . . . . . . . . . . . . . 9
Device Controllers . . . . . . . . . . . . . . . . . . . 9
IO User Classes . . . . . . . . . . . . . . . . . . . . 11
3. INPUT CONTROL SOFTWARE . . . . . . . . . . . . . . . . . 15
Remote Access Security Control . . . . . . . . . . . . . 15
Security and Access Control . . . . . . . . . . . . . . 15
Command Screening . . . . . . . . . . . . . . . . . . . 19
Show-Password Feature . . . . . . . . . . . . . . . . . 22
Dumpsafe State . . . . . . . . . . . . . . . . . . . . . 22
Priority Map Terminal . . . . . . . . . . . . . . . . . 22
4. OUTPUT CONTROL SOFTWARE . . . . . . . . . . . . . . . . 23
Log System Interface . . . . . . . . . . . . . . . . . . 23
SYSLOG . . . . . . . . . . . . . . . . . . . . . . . . . 25
Critical Message Prioritization . . . . . . . . . . . . 26
Guaranteed Background Schedule . . . . . . . . . . . . . 27
Secret Logs . . . . . . . . . . . . . . . . . . . . . . 27
Report Routing . . . . . . . . . . . . . . . . . . . . . 28
Report Thresholding . . . . . . . . . . . . . . . . . . 30
Thresholding for INIT and TRAP Logs . . . . . . . . . . 33
Log Format - Offices With Enhanced Core . . . . . . . . 33
5. MAN-MACHINE INTERFACE . . . . . . . . . . . . . . . . . 34
Types of MMI . . . . . . . . . . . . . . . . . . . . . . 34
Bilingual Man-Machine Interface . . . . . . . . . . . . 34
Parameters and Responses . . . . . . . . . . . . . . . . 35
Common Commands . . . . . . . . . . . . . . . . . . . . 35
Prompting . . . . . . . . . . . . . . . . . . . . . . . 35
Security and Access Control MMI . . . . . . . . . . . . 35
Command Screening MMI . . . . . . . . . . . . . . . . . 43
Report Routing MMI . . . . . . . . . . . . . . . . . . . 55
Search and Display (Browse) MMI . . . . . . . . . . . . 70
6. ABBREVIATIONS . . . . . . . . . . . . . . . . . . . . . 83
Page 3
PRACTICE 297-1001-129
RELEASE: 06.03
FIGURES
FIG. TITLE PAGE
1 Relationship of DMS-100 Family System to I/O Devices 10
2 Remote Access Security Control. . . . . . . . . . . . . 17
3 Security and Access Control Scheme. . . . . . . . . . . 18
4 Command Screening Scheme. . . . . . . . . . . . . . . . 21
5 Schematic Representation of Typical Log Buffer. . . . . 24
6 Report Routing Scheme. . . . . . . . . . . . . . . . . 32
TABLES
TABLE TITLE PAGE
A Common Parameters . . . . . . . . . . . . . . . . . . . 80
B Text of Common Command Responses . . . . . . . . . . . 81
Page 4
PRACTICE 297-1001-129
RELEASE: 06.03
1. INTRODUCTION
GENERAL
1.01 This Practice describes the hardware and software aspects
of the DMS-100 Family Input/Output (I/O) system. This
manual also contains details of the command syntax required to
execute the various I/O functions, and the machine responses that
occur as a result of these commands.
PRACTICE APPLICATION
1.02 The information contained in this Practice is applicable
to offices having Batch Change Supplement (BCS) 32 soft-
ware.
It is also applicable to offices having a BCS release greater
than BCS32 unless reissued. The application of all Northern
Telecom Practices (NTP) editions with respect to a given BCS
release is given in 297-1001-001.
REASON FOR REISSUE
1.03 This Practice has been reissued (06.03) to incorporate
minor changes to the log system interface description.
SOFTWARE IDENTIFICATION
1.04 Software applicable to a specific DMS-100 Family office is
identified by a BCS release number and by Northern Telecom
(NT) Product Engineering Codes (PEC). The significance of the
BCS number and the PEC is described in 297-1001-450 (section 32)
and in the Office Feature Record D-190.
1.05 A display of the BCS number and PEC for the NT feature
packages available in a specific office can be obtained by
entering the command string:
PATCHER;INFORM LIST;LEAVE
at a Maintenance and Administration Position (MAP).
COMMAND FORMAT CONVENTIONS
1.06 In this Practice, a uniform system of notation is used to
illustrate system commands and responses. It shows the
order in which command elements appear, the punctuation, and the
options. Where the conventions are not used, an explanation is
given in the text.
Page 5
PRACTICE 297-1001-129
RELEASE: 06.03
CAPITAL letters or show constants, commands, or keywords that
special characters the system accepts when entered as writ-
ten.
lowercase letters show a user- or system-supplied para-
meter. Definitions are given for each par-
ameter.
Brackets [ ] or enclose optional parameters. A vertical
list enclosed in brackets means that one
or more of the parameters may be selected.
Underlined parameter is a default. If no choice is entered, the
system acts as though the underlined para-
meter had been entered.
Underscore connecting means the words are to be treated as one
words item, for example, pm_type or #_one_two.
... indicates repeated steps or items.
In addition, the following conventions are used.
n (lowercase n) is a number from 0 to 9.
a (lowercase a) is a letter from A to Z.
h (lowercase h) is a hexadecimal integer from 0 to F.
1.07 Special features are implemented when the associated soft-
ware package is provisioned and installed. The following
features are available:
Feature In Package
Auto LOGIN NTX001
Bilingual Man-Machine Interface (BMMI) NTX066 Automatic
Dial Back NTX293
Critical Message Prioritization NTX001
Enhanced Command Screening NTX292
Guaranteed Background Schedule NTX000
MAP support for DISPLAYPHONE * NTX001
Password and Access Control NTX292
Priority MAP Terminal NTX001
Show Password (SHOWPW) Command NTX001
Secrecy NTX100
1 * DISPLAYPHONE is a trademark of Northern Telecom.
Page 6
PRACTICE 297-1001-129
RELEASE: 06.03
REFERENCES
1.08 References listed as prerequisites are essential for an
understanding of this Practice. Those listed as inform-
ative contain detailed information concerning other items men-
tioned in this Practice, but are not essential. References are
inserted at the appropriate places in the text.
Note: The documents listed may exist in more than one version.
See 297-1001-001 to determine the release code of the version
compatible with a specific release of software.
Prerequisite References
DOCUMENT
NUMBER TITLE
297-1001-100 System Description
Informative References
NUMBER DOCUMENT TITLE
297-1001-001 Master Index of Practices
297-1001-110 Maintenance and Administration Position (MAP)
297-1001-310 Table Editor Reference Manual
297-1001-450 Provisioning
297-1001-451 Customer Data Schema
297-1001-455 The Office Parameters Reference Manual
297-1001-510 Log Report Manual
297-1001-516 Trunks Maintenance Reference Manual
GS1X55 Disk Drive Controller
GS1X67 GS1X61 Terminal Controller Card
Input-Output Controller
GS1X68 Magnetic Tape Controller Card
Page 7
PRACTICE 297-1001-129
RELEASE: 06.03
2. INPUT/OUTPUT HARDWARE
2.01 Input/Output (I/O) hardware consists of various types of
controllers and I/O Devices (IOD) which enable the operat-
ing company to properly maintain, operate and administer the DMS
switch. This hardware is located in the maintenance and adminis-
tration area. (See 297-1001-100.)
2.02 The MAP (Maintenance and Administration Position) is the
2
primary device providing communication between the user
and the DMS switch. Through the MAP, the Man-Machine Interface
and display messages or reports. (See 297-1001-110 for details of
(MMI) is used to input commands, run tests, request information,
the MAP.)
2.03 In addition, full MAP support is provided for the DISPLAY-
PHONE terminal (F5439). The major difference between the
standard MAP position and the DISPLAYPHONE terminal is the line
editing control function, which is implemented using the cursor
movement keys and the control key sequences as follows:
Down Arrow causes the input line to be refreshed.
Up Arrow allows character insertion at the cursor position.
Right Arrow causes the cursor to advance one character position
to the right for each depression until the end of
the current input line is reached.
Left Arrow causes the cursor to back up one character position
to the left for each depression until the beginning
of the input line is reached.
CONTROL U this key sequence causes the contents of the input
line to be deleted (see Note).
CONTROL E this key sequence causes the input line from the
current cursor position to the end of the input line
to be deleted (see Note).
CONTROL X this key sequence turns off the effect of the Up
Arrow (see Note).
? retrieves the previous input line. The DMS remem-
bers the current and the two previous lines.
Note: The key sequence, CONTROL , means that the Con-
trol key is held down while the character is entered.
2.04 Other IOD are: printers, which can be used for MMI, and to
provide printed copies of reports; and magnetic tape or
disk recording devices, used for storage or retrieval of data.
2 MAP is a trademark of Northern Telecom
Page 8
PRACTICE 297-1001-129
RELEASE: 06.03
INPUT/OUTPUT CONTROLLER
2.05 The Input/Output Controller (IOC) is the hardware entity
which provides the interface between the Central Control
Complex (CCC) and the various types of IOD. (See Figure 1 on
page 10.) The CCC side of the IOC is connected via a pair of
32-channel, 2.56 Mb/s serial data links (designated DS30), to the
Central Message Controllers (CMC), and hence to the Central Proc-
essing Units (CPU) in the CCC.
2.06 Each of the two CMC has 70 serial data ports to which the
ports are assigned to the IOC, and others to the network message
DS30 data links are assigned in pairs. Some of these
controllers (NMC) in the two planes of the switching network.
2.07 Offices having BCS16 and higher software can have up to 12
pairs of ports assigned to links to up to 12 IOC (0 to
11). In this configuration, however, the number of pairs of
ports available for assignment to NMC is reduced to a maximum of
58. If less than 12 IOC are required, the number of ports avail-
able for assignment to NMC increases accordingly.
2.08 CMC port assignments to IOC and NMC are controlled by data
The format of the maintenance displays on the MAP, showing the
entered in the peripheral equipment assignment tables.
status of the IOC units, depends on which BCS release number is
in effect.
2.09 The other side of the IOC provides common parallel data
and address buses, to which up to nine (numbered 0 to 8)
Device Controllers (DC) are connected. The flow of data and its
routing to the addressed DC, is handled by the I/O message con-
troller.
2.10 Physically, the I/O message controller and the DC are cir-
The IOC shelves are housed in single-bay I/O equipment (IOE)
cuit cards which plug into the backplane of the IOC shelf.
frames. For more details of the IOC refer to GS1X61.
DEVICE CONTROLLERS
2.11 The DC converts the characteristics of the various IODs to
the common data bus format in the IOC. Three types of DC
circuit cards are required, and the number of each used depends
on the number of IOCs in service, and the number of IODs in use.
The provisioning of DC circuit cards forms part of the office
as follows: engineering process. The applications of the thre
e DC types are
* Disk Drive Controller (DDC) Interfaces the Disk Drive Unit
(DDU) with the IOC data bus. Enables the DDU to be con-
trolled by commands input at the MAP. Provides read/write
facilities for retrieval and storage of data on magnetic
disks. (See GS1X55 for details of the DDU.)
Page 9
PRACTICE 297-1001-129
RELEASE: 06.03
Program< > CPU < > Data
Store Store
(PS) A (DS)
DMS-100 Family
V CCC
CMC
A A A
To mate >To NMC
CMC and
CPU < DS30 >To other IOC
V V
I/O CONTROLLER SHELF
IO Message NT1X61
Controller
NT1X62
ADDRESS BUS
DATA BUS
0 6 7 8
DEVICE
CONTROLLERS TC . . . . . TC MTC DDC
(DC)
AA A A A A
0 .. 3 0 ... 3
EIA/ASCII
Interface MODEM V
DISK DRIVE UNIT
A
V
/ MAGNETIC TAPE DRIVE
MAP <
V V
Current Loop Interface
PRT REMOTE
PRINTER < I/O DEVICEV
DATAPAC or Datalink Devices
Fig. 1 - Relationship of DMS-100 Family System to I/O Devices
Page 10
PRACTICE 297-1001-129
RELEASE: 06.03
* Magnetic Tape Controller (MTC) Interfaces the Magnetic Tape
Drive (MTD) with the IOC data bus. Enables the MTD to be
controlled by commands input at the MAP. Provides read/write
facilities for retrieval and storage of data on magnetic
tapes. (See GS1X68 for details of the MTC.)
* Terminal Controller (TC) The TC are multi-purpose circuit
cards which interface up to four IOD per card with the IOC
data bus. The four ports to which IOD are connected can have
their configurations set to match the characteristics of the
IOD connected to that port. (See GS1X67 for more details of
the TC.) Port configurations are programmable, and are set
by entries in table TERMDEV to either of the following con-
figurations:
EIA/ASCII used for IOD (MAP or PRT) located within 50 ft
(15m) of the IOE frame; also to connect to a modem for
operation with remote devices.
Current Loop used for IOD located within 1200 ft (366m)
of the IOE frame.
2.12 The proper DC for each type of IOD is assigned by data
istics such as baud rate, port configuration, etc. are also
entered in the appropriate IOD table. Other character-
assigned in these tables.
2.13 IO devices and their associated data tables are as fol-
lows:
* Magnetic Tape Drives - table MTD
* Disk Drive Units - table DDU
* Visual Display Unit - (part of MAP), printers (PRT), or modem
3 to a remote PRT - table TERMDEV
* DATAPAC - table DPACDEV
* Data Link Controller - DLCDEV.
IO USER CLASSES
2.14 IO users should be organized into classes which define a
specific set of functions that these users are required to
perform. These functional needs in turn dictate the IOD require-
ments for each user class. The actual organization of I/O user
classes is completely flexible to meet operating company opera-
tional requirements. The general principle is that the division
of tasks shall serve the purpose of each user class, yet will
ensure that they do not interfere with each other's functions.
2.15 The selection of the type and quantity of IOD for each
user-class function depends on operating company require-
3 DATAPAC is a trademark of Bell Canada
Page 11
PRACTICE 297-1001-129
RELEASE: 06.03
ments, and forms part of the office engineering process. Infor-
mation on the provisioning is contained in 297-1001-450.
2.16 Following are the names and descriptions for some typical
I/O user classes:
Administration (ADMIN): provides the user with unlimited
access from any IOD to all command classes (see PRIVCLAS),
and in addition is assigned the highest priority level (see
PERMIT). The password associated with ADMIN cannot be dis-
played, and cannot be changed by any other user (see COMMAND
SCREENING).
© 2024 Packet Storm. All rights reserved.
%7Cutmcsr%3D(direct)%7Cutmcmd%3D(none)){kind=small}
Follow us on Twitter
Follow us on Facebook
Subscribe to an RSS Feed