Information

System

OGL-MN

A50016-D1110-A502-1-7619
OGL-MN Information
System

f Important Notice on Product Safety

Elevated voltages are inevitably present at specific points in this electrical equipment. Some of the
parts may also have elevated operating temperatures.
Non-observance of these conditions and the safety instructions can result in personal injury or in prop-
erty damage.
Therefore, only trained and qualified personnel may install and maintain the system.
The system complies with the standard EN 60950 / IEC 60950. All equipment connected has to comply
with the applicable safety standards.

The same text in German:

Wichtiger Hinweis zur Produktsicherheit
In elektrischen Anlagen stehen zwangsläufig bestimmte Teile der Geräte unter Spannung. Einige Teile
können auch eine hohe Betriebstemperatur aufweisen.
Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Körperverletzungen und
Sachschäden führen.
Deshalb wird vorausgesetzt, dass nur geschultes und qualifiziertes Personal die Anlagen installiert und
wartet.
Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Angeschlossene Geräte
müssen die zutreffenden Sicherheitsbestimmungen erfüllen.

Trademarks:
All designations used in this document can be trademarks, the use of which by third parties for their
own purposes could violate the rights of their owners.

Copyright (C) Siemens AG 2002.

Issued by Information and Communication Mobile

Hofmannstraße 51
D-81359 München

Technical modifications possible.

Technical specifications and features are binding only insofar as
they are specifically and expressly agreed upon in a written contract.

2 A50016-D1110-A502-1-7619
Information OGL-MN
System

This document consists of a total of 24 pages. All pages are issue 1.

Contents
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2 Manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.1 Operating Manuals (OMN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.1.1 Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.1.2 Entry into the manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.1.3 Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.2 Maintenance and Nonstandard Maintenance . . . . . . . . . . . . . . . . . . . . . . . 13
2.2.1 Maintenance manuals (MMN). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.2.2 Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.2.3 Nonstandard Maintenance Manuals (NM) . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.2.4 Emergency manual (EMCYMN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.2.5 Using the Exchange Configuration Documents . . . . . . . . . . . . . . . . . . . . . 17
2.3 Man-machine language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.3.1 Task manual (TML). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.3.2 Output manual (OML) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.4 Fault Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

3 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

A50016-D1110-A502-1-7619 3
OGL-MN Information
System

Illustrations
Fig. 2.1 Practical example from OMN-RO and TML . . . . . . . . . . . . . . . . . . . . . . 11
Fig. 2.2 SDL symbols. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

4 A50016-D1110-A502-1-7619
Information OGL-MN
System

Tables
Tab. 2.1 Examples of operation functions in OMN. . . . . . . . . . . . . . . . . . . . . . . . . 8
Tab. 2.2 Structure of the OMN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Tab. 2.3 Structure of the MMN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Tab. 2.4 Structure of the NM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Tab. 2.5 Structure of the OML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

A50016-D1110-A502-1-7619 5
OGL-MN Information
System

6 A50016-D1110-A502-1-7619
Information OGL-MN
System

1 Introduction
This register MN of the operator guidelines (OGL) provides an overview of the manuals
available to assist to the personnel responsible for Operation and Maintenance (O&M)
of core network (CN)/switching subsystem(SSS) nodes in carrying out their tasks.
The O&M tasks which arise in general at the request of the administration (order driven
tasks) or as a response to alarm messages (system driven tasks) are converted by O&M
personnel into tasks and entered via the man-machine interface (see OGL-MMI).
Operation and maintenance (O&M) of network nodes involves the completion of a vari-
ety of tasks. These tasks, or the commands needed to execute them, are described in
the following manuals:
– Operation Manuals (OMN, see chapter 2.1)
– Maintenance Manuals (MMN, see chapter )2.2.1
– Nonstandard maintenance manuals (NM; see chapter 2.2.3)
– Emergency manuals (EMCYMN see chapter 2.2.4)
– Task manuals (TML, see chapter 2.3.1)
– Operator Hints = Operator Information (attached special yellow pamphlets)
It is assumed that the users of these manuals already have the basic knowledge that
can be attained through training. The Operator Guidelines (OGL) describes the main
points of the basic knowledge required as well as tasks that extend beyond the bound-
aries of O&M.
The tasks required for operation of a trouble-free network node are described in the
OMN, which is structured in accordance with the task-oriented procedures (TOP) con-
cept.
The sequences of operations required for maintenance and upkeep are to be found in
the MMN. This also makes use of documentation specific to network nodes, e.g. ex-
change configuration documents.
The network-node-specific exchange configuration documents (see OGL-ECD) indicate
the current status of a certain network node. They include, for example, a list of all avail-
able trunks, modules, allocations, etc.
Whereas the OMN and MMN manuals set out the activities and the commands required
for performing tasks in their chronological sequence or their logical context, the TML de-
scribes each individual command separately.
The OMN provides an overview of the possible tasks and their commands, and the TML
supplements this with a project-specific selection of the commands required for the
project in question.
Operator hints provide supplementary information on operation and maintenance pro-
cedures. They are issued on yellow paper, independently of the the manuals issued,
and are inserted after the index of issues/table of contents page or before the relevant
procedure in the manual concerned.
Appropriate training is required if network nodes are to be operated successfully with the
above documents. A basic requirement for all activities involving the system is to ob-
serve the operating personnel information and the warnings (see Notice on Product
Safety on the reverse side of the Register Title Sheet and document titled "Safety In-
structions for Personal and Products (EN60950/IEC60950").

A50016-D1110-A502-1-7619 7
OGL-MN Information
System

2 Manuals

2.1 Operating Manuals (OMN)

Operation of network nodes is described in the OMN. The terminology used in the OMN
is based as far as possible on the ITU Recommendation.
The OMN is subdivided into several functional areas (see Tab. 2.1). It is intended to as-
sist the user in determining the MML commands of the command sequences (known as
procedures) which are needed to formulate a task.
The term ”task” here refers to the entry of commands, parameters and identifiers to at-
tain a specific objective.

Functional area Register

Subscriber SU:HLR
Subscriber SU:CSC
Database in MSC/VLR MSCDB
SS7 SS7:SSNC
Routing RO
Charging CHA
Traffic and Performance Data TR
System Administration SY
Network Node Configuration NNC

Tab. 2.1 Examples of operation functions in OMN

2.1.1 Structure
The OMN is divided into ”registers”, each of which is a self-contained section of the man-
ual devoted to a specific functional area. Each register is subdivided into the following
main sections which provide users with an overview of all the functional areas as repre-
sented by the man-machine language (MML).

Chapter Contents

Introduction (IN) The introduction describes the interrelations between sys-

tem functions and provides examples of the more complex
administrative tasks within the particular subject area.
Task List (TL) The task list contains all the tasks in the subject area, there-
by forming an initial entry into the administrative tasks.
Task Summary Lists The task summary lists are general, sequential lists of tasks
(TS) with no cross-references or reverse links.
Task Procedures (TP) The task procedures are non-sequential lists of tasks using
sub-procedures.

Tab. 2.2 Structure of the OMN

8 A50016-D1110-A502-1-7619
Information OGL-MN
System

Chapter Contents

Feature Procedures The feature procedures describe the function and contain a
(FTP), optional sequential list of tasks for the creation and administration of
each feature.

Tab. 2.2 Structure of the OMN

2.1.2 Entry into the manual

The OMN is entered via the task list. The task list makes reference to the following sub-
points:
– Task summary list, if the task sequence to be executed can be performed without
any cross-references and reverse links. The task summary lists themselves can con-
tain further references to task summary lists, procedures or commands.
– Procedure TP, which works through the task sequence step by step.
A procedure is basically a sequence of commands with the parameters and identifi-
ers required for performing the tasks, though not all the mandatory parameters
(these can be found in the task manual, TML).
When the configuration of the network node can differ, prerequisites are extracted
and the corresponding cases are distinguished. Comments following the procedure
title or certain command inputs refer to any particular characteristics.
– Task complex TC, if the task to be executed is complex and concerns a number of
administrative areas.
A task complex is basically a sequence of commands with the parameters and iden-
tifiers from various manuals (e.g. SU:HLR/CSC, RO, SY) required for performing the
tasks, though not all the mandatory parameters.
Identical parameters are highlighted in each case. Comments following the proce-
dure title or certain command inputs refer to any particular characteristics.
– Command in the command manual, if the task can be performed by executing a
command.
The cross-reference from the task list to a command can contain parameters and
identifiers. However, not all the mandatory parameters for the command are given,
just those parameters of relevance to the task in question.
– Feature procedure (FTP). Feature procedures are peculiar to the subscriber admin-
istration manual.
They first describe the service and/or the functions as well as the prerequisites for
creating, modifying and canceling. This is followed by the procedure, a sequence of
commands with the parameters and identifiers required for performing the tasks,
though not all the mandatory parameters.

A50016-D1110-A502-1-7619 9
OGL-MN Information
System

2.1.3 Structure
An OMN user has to convert a clearly specified job into an MML task that can be under-
stood by the switching system. The job must be traced step-by-step back to the proce-
dure/command to be executed (TOP concept).
The task is dealt with by noting or executing the commands, information or instructions
given in the main sections of the relevant OMN division (register). However, all manda-
tory parameters are not given. These must be taken from the CML. An explanation of
the contents of the main sections is given below.

Introduction IN
In the introduction (IN) the OMN user is informed about the functional task (as deter-
mined by the task requirements. This gives the reader details of, for example, the rela-
tionships between system functions, MML objects and their independencies.

Task list TL
The reference for dealing with a task, once the introduction has been studied, is to be
found in general in the task list (TL).
This contains:
– a list of all tasks belonging to the area involved
– references to task summary lists (TS), task procedures (TP) or individual commands
(TML).
References to a command can contain parameters and identifiers which are required for
carrying out the task or which identify this task (see Fig. 2.1 for example).

Task summary lists TS

The task summary lists (TS) supply the following specific information for dealing with a
task:
– unambiguous task description
– long versions of instructions
– sequences of operations (no decision branching)
– references to other task summary lists, task procedures (OMN), or individual com-
mands (TML)

Task procedures TP
In the procedures (TP) short, restricted activities are represented by SDL (specification
and description language) symbols (see Fig. 2.2). These contain MML commands,
MML parameters and MML identifiers, specifically required for carrying out the tasks (for
mandatory parameters, see TML).

10 A50016-D1110-A502-1-7619
Information OGL-MN
System

TL 2.6 Trunk Groups

.
.
.
Display data for trunks................................................................................................................ DISP TRUNK
Display line status for trunks....................................................................................................... STAT TRUNK
Block trunk for administrative reasons........................................................................................ ENTR TRDAT
Unblock trunk for administrative reasons................................................. .................................. CAN TRDAT
Create trunks............................................................................................................................... TP-281
Modify port of a trunk ............................................................................................. ................... TS-281
Cancel trunks ..................................................................................................................................TP-282
...

TS
TS-281 Modify port of a trunk

1 Cancel trunk at old port................................................................................ .................... TP-283

2 Create trunk at new port........................................................................................................TP-281

TP + CML CR TRUNK
Create trunk Create trunk

TP-281

CR TRUNK:TGNO= , EQN= , LCOS=,

CR
TRUNK

TP-281-1

Fig. 2.1 Practical example from OMN-RO and TML

A50016-D1110-A502-1-7619 11
OGL-MN Information
System

SDL symbols Meaning

Start symbol
contains the procedure name

State symbol
contains a state

Input symbol
contains commands

Output symbol
contains commands

Decision symbol

Task symbol
contains the name of the task to
be executed
Output symbol
contains messages

Procedure call symbol

contains the procedure name
and current parameters

Symbol for warning

e.g. for danger to persons, de-
Warning
vice failure, or interruption to op-
This command
eration

Text extension symbol

Text extension contains notes and/or explana-
tions of the contents of the sym-
bol to which it is attached

Comment symbol
comment conains a comment on the con-
tens of the symbol to which it is
attached

Connector symbol

Return symbol

End of procedure symbol

Or symbol
A C
B

Fig. 2.2 SDL symbols

12 A50016-D1110-A502-1-7619
Information OGL-MN
System

2.2 Maintenance and Nonstandard Maintenance

The maintenance and nonstandard maintenance manuals support the troubleshooting
and the reactivation of the network node following troubleshooting.
• The maintenance manuals (MMN) are available for troubleshooting the network
node by means of module replacement.
• The nonstandard maintenance manuals (NM) are available for troubleshooting the
network node in special cases.
• The emergency manual (EMCYMN) is available for troubleshooting the network
node in cases of emergency.
The maintenance manuals are organized according to the software and the various
hardware components.
Thanks to the modular construction of the hardware components, the maintenance per-
sonnel can remove faults caused by defective modules. The maintenance manuals con-
tain procedures for troubleshooting on the basis of module replacement as well as
procedures for the preventive maintenance of additional equipment such as magnetic
tape devices, etc. In general, such troubleshooting procedures are sufficient for locating
the suspected modules of a network node. The module suspected of being faulty is then
replaced by another module, according to the instructions in the maintenance manual.
After the replaced module has been successfully tested, the original operating state is
restored.
Other faults, e.g. cable defects, are removed with the help of the nonstandard mainte-
nance manuals.
The emergency manual contains information on how to reactivate an network node that
has broken down completely or is operating only in part.
In the event of difficult cases or emergency cases, help should be requested from the
technical assistance center (TAC) in the technical service center.

2.2.1 Maintenance manuals (MMN)

The maintenance manuals (MMN) are uniform in their structure (Table 2.3):

Chapter Contents

Introduction The Introduction provides maintenance-specific

information on the system components.
Task List List of tasks concerning the subject area.
The chapter is optional.
Procedures Procedures for step-by-step troubleshooting of the
inactive unit (modules are replaced and not repaired).
Tables The tables contain fault lists, allocation lists and
references to construction sections.

Tab. 2.3 Structure of the MMN

A50016-D1110-A502-1-7619 13
OGL-MN Information
System

Entry into the manual

The following steps are a summary of the general procedure for locating and removing
faults with the help of a maintenance manual:
– The routine tests or the system’s supervisory circuits discover a fault and send an
alarm to the alarm surveillance of the network node.
– The alarm surveillance of the switch commander extracts the fault number and, with
the aid of the unambiguous procedure number in the documentation, can refer to the
correct fault clearance procedure.
– The corresponding procedure is to be executed. The procedure can be executed lo-
cally, remotely or centrally from the O&M terminal. The procedure continues step-
by-step through the task “Locate fault”.
– The on-site maintenance personnel locate the inactive module and replace it.
– The appropriate procedure is then used to reactivate the replaced unit.
– The faulty module is marked in accordance with the guidelines for electrostatic-sen-
sitive components, packed and sent to the repair service.
As a rule, the troubleshooting procedures are sufficient for removing most faults that can
occur in the hardware component in question. However, if all suspected modules have
already been replaced and the fault is still occurring, or the diagnostics test has not been
able to find the reason for the fault, the next higher-ranking troubleshooting level must
be called in (TAC1 -> TAC2 -> TAC3). This will call for additional information and means
for fault location and troubleshooting.

14 A50016-D1110-A502-1-7619
Information OGL-MN
System

2.2.2 Structure
The Maintenance Manuals MMN are structured according to the equipment they deal
with.
They are divided into the following registers:

ADMIN Administration
IN Introduction
TL Task Lists
PROC Fault Clearance
TAB Tables
APP Appendix
The registers contain information on:

ADMIN
Register ADMIN contains the administrative parts of the manual (content, list of figures,
list of tables).

IN
Register IN explains how to use this manual and gives a description of the procedures
of this manual.

TL
Register TL refers to preventive maintenance measures.

PROC
Register PROC contains fault clearance and diagnostic procedures, listed according to
the MMN number.

TAB
Register TAB provides an overview of module frame allocation to the fuses, assignment
of module frames with modules, assignment of front panels of the modules and the
switching points.

APP
Register APP describes the structure and configuration of the relevant subsystem, safe-
guarding, alarm reporting, state interrogations, configurations and the diagnostics, tests,
file handling and the physical inputs/outputs.

2.2.3 Nonstandard Maintenance Manuals (NM)

Module faults can generally be cleared up by using the procedures in the MMN. Howev-
er, if the procedures in the MMN do not provide a successful outcome, troubleshooting
should be continued in accordance with the nonstandard maintenance manual (NM).
The nonstandard maintenance manuals contain additional information on each type of
fault.
The nonstandard maintenance manuals (NM) are uniform in their structure (Table 2.4):

A50016-D1110-A502-1-7619 15
OGL-MN Information
System

Chapter Contents

Introduction The Introduction provides information on the system com-

ponents as well as information specific to nonstandard
maintenance.
Fault Descriptions The Fault Description explains the results of the diagnosis
and the system outputs.
Replacement The Replacement Instructions contain information on re-
Instructions placing frames, modules and cables.

Tab. 2.4 Structure of the NM

For each possible fault listing, the NM contains a section MMN:UUxxx-zzzz, arranged
according to the full MMN number. Fault listings without MMN numbers are grouped to-
gether in separate sections. The nonstandard maintenance manual (NM) contains:
– Interpretations of hexadecimal additional information from the fault listing output
– Descriptions of the function of the defective system component
– Outline of the procedure leading to the system reactions within the safeguarding
– Information on suspect hardware included only partially in the troubleshooting pro-
cedures
– Explanations on the procedure and the function of the diagnosis
– Interpretations of the results of the diagnosis
– Additional troubleshooting notes for the various fault patterns
– Instructions for replacing modules, voltage transformers, module frames and cables
– Illustration of the racks and module frames
– Illustration of the standard cabling

Entry into the manual

The nonstandard maintenance manual (NM) is entered by means of cross-references
from the maintenance manuals (MMN).

16 A50016-D1110-A502-1-7619
Information OGL-MN
System

2.2.4 Emergency manual (EMCYMN)

The emergency manual (EMCYMN) contains emergency information on how to reacti-
vate an network node that has broken down completely or is only partially functioning.
The operating company is supported in this task by the technical assistance centers
(TAC1 -> TAC 2 -> TAC 3).
The emergency manual (EMCYMN) contains troubleshooting procedures for:
– Restoring normal system operation
– Safeguarding data (e.g. semipermanent inputs, charges, indices, etc.)

Entry into the manual

The emergency manual (EMCYMN) is entered by means of cross-references from the
maintenance manuals (MMN) or via alarms (e.g. failure of air-conditioning system).

2.2.5 Using the Exchange Configuration Documents

At certain points of the MMN specific information on the configuration of the network
node is required. The configuration of the network nodes is described in the exchange
configuration documents, so the information required can be found in these documents
(see OGL-ECD).

2.3 Man-machine language

The man-machine language (MML) of the network node is divided into two manuals:
• Task manual (TML)
• Output manual (OML)
The system outputs pertaining to the commands are shown in a cross-reference list.

2.3.1 Task manual (TML)

The Task Manual (TML) is a reference document which contains all tasks needed to op-
erate the system including those tasks intended only for system specialists with special
authorization. Technological advances have led to changes in the way the switch is ad-
dressed. Concretely this means that there are new interfaces via which communication
with the switch is possible. Therefore some tasks communicate with the switch via tra-
ditional commands, others via a slightly different input format. For the sake of continuity
all of these elements will be called tasks in future and will be described in this document.
As in the past, the reader accesses the required information from the TML Table of Con-
tents, or if task access is made from one of the manuals, through links in those docu-
ments
Care has been taken to make input format representation as similar as possible. There
are however differences which the user must be aware of. For example the output
masks for traditional commands are described in an independent document (OML).
However, if further clarification is required, the outputs of the new task formats are de-
scribed in the relevant task itself. Another example is that the length of the input param-
eters is not limited to 8 characters in the new tasks: instead, the parameter names may
be up to 20 characters long.

A50016-D1110-A502-1-7619 17
OGL-MN Information
System

Structure
The structure of the TML is as follows:
• Overview and Index of issues
• Introduction
• Cross reference lists for MML
• Task descriptions

Overview and Index of Issues

The TML overview makes up the administration section. The overview contains all tasks
in tabular order. All entries contain an issue report and, if necessary, a change designa-
tion.
In addition it contains a list of the other TML sections, for example Introduction.The over-
view contains links which allow the user to jump to the information in the other TML sec-
tion.

Introduction
The Introduction contains specific instructions for using the TML including the differenc-
es relevant to operation between traditional commands (MML tasks) and the newer
tasks. Where the information is valid for all tasks, it appears only once. Where there are
differences it is clearly stated for which type of task the information is intended.

Task descriptions
The task descriptions are the main part of the TML and reflect the set of tasks relevant
to a specific APS. Task descriptions include information about the syntax, parameters,
and, where applicable, paths and parameter values.
Task descriptions are structured as follows:
1. Task short and long name
2. Task helptext
3. Task syntax
4. Parameter information including general parameter information, and, where applica-
ble, subparameter and parameter value information
Input syntax
This section provides an overview of the input format for tasks and the syntax. The syn-
tax is displayed in Backus-Naur Notation:
Input format

Graphic display of parameters Comment

DEMO= Mandatory parameter
[,DEMO=] Optional parameter
{,DEMO1=|, DEMO2=} Entering exactly one parameter is mandatory
[{,DEMO1=|, DEMO2= }] Entering exactly one parameter is optional

18 A50016-D1110-A502-1-7619
Information OGL-MN
System

Graphic display of parameters Comment

[DEMO1=,DEMO2=] Entering all parameters or none entered
Possible combinations:
All parameters are entered
[DEMO1=[DEMO2=]] Possible combinations:
All parameters are entered
Enter only DEMO1
Enter both parameters (DEMO2 may not be
entered alone)
<,DEMO1=,DEMO2=, DEMO3=> At least one parameter must be entered.
The syntax diagrams contain links which allow direct access to the individual parameter
descriptions.
MML task-specific remarks
MML tasks which can be used for different purposes are split into different input formats
(paths). This applies particularly in cases in which the above mentioned syntax is not
able to represent all the dependencies among parameters, parameters and parameter
values, or among parameter values. An overview of the input formats is given at the be-
ginning of each command description.
Example: The MML task has the following paths:

1. CR TEQ - ATCL ACCESS TEST CIRCUIT SUB LINE

2. CR TEQ - ATE AUTOMATIC TEST EQUIPMENT
3. CR TEQ - ATEMAN ATE FOR TESTING AND MEASURING
4. CR TEQ - ATESELF ATE FOR SELFTEST
5. CR TEQ - TEMLE TEST MODULE LEVEL
6. CR TEQ - TESTSET TEST SET
7. CR TEQ - RBSI RING BACK SERVICE INTEGRATED
8. CR TEQ - TLFI TRANSLATION SERVICE INTEGRATED
9. CR TEQ - ADDATE ADDITIONAL ATE PORT

The paths also contain links which allow direct access to the individual input descrip-
tions.
Input parameters
The description of the input parameters explains the syntax of the individual parameters.
In the simplest cases, parameters are described by the parameter short and long name
and the parameter value range. The parameter value range may be a range of decimal
numbers or it may be defined by a specific character set as shown below:

Alphanumeric A...Z 0...9. + * % #

symbolic names:
Alphanumeric text A...Z 0...9 . + * % # < ( & ! $ ) ; - / , _ > ? : @ ' = <enter> <line feed>
strings:
Text strings must be enclosed in quotation marks ("), If a quotation mark must be includ-
ed in a text string, it must be doubled (""). The maximum length of a text string including
the quotation marks is 72 characters.
Example:

A50016-D1110-A502-1-7619 19
OGL-MN Information
System

PARDM1 PARAMETER DEMONSTRATION 1 =

5...8 characters from the symbolic name character set
In certain cases, however, mnemonic abbreviations may be entered for a parameter.
These abbreviations are also called identifiers. Identifiers have short and long names
and may be supplemented by a helptext.
Example:

PARD2 PARAMETER DEMONSTRATION 2 =

IDF1 LONGNAME IDENTIFIER NO. 1
IDF2 LONGNAME IDENTIFIER NO. 2
Under certain circumstances a parameter may have up to four subparameters. Subpa-
rameters are also called information units; they must be separated by a hyphen. In the
Task Manual, information units are symbolized by the lowercase letters a, b, c and d.
Example:

PARD3 PARAMETER DEMONSTRATION 3 =a-b-c-d

a: FIRST INFORMATION UNIT=
0...7, range of decimal numbers
b: SECOND INFORMATION UNIT = etc.
The old and new parameters are also represented by lowercase letters.
Example:

DIGIT DIGITS =
The parameter specifies the prefix digits for test multiple.
n/o
n/
/o
1...8 hexadecimal number where B is interchangeable with *
and C is interchangeable with #
In this case, new and old have a very general meaning.
Example:

MOD TEQ: DIGITS= newvalue/oldvalue Changes the prefix value newval-

ue/oldvalue
MOD TEQ: DIGITS= newvalue/ Enters new prefix digit
MOD TEQ: DIGITS= /oldvalue Deletes old prefix digit
Default values
If the syntax allows omission of a parameter or subparameter, the key word Default in
the parameter helptext describes how the system will respond. The following cases are
possible:
1. Default value: <value>
<value> is a parameter value within the permissible range that is automatically used
if the parameter is omitted.
2. Default behavior: <value>
Values given are added to the default value. This combination indicates that one can
add other values to default values.

20 A50016-D1110-A502-1-7619
Information OGL-MN
System

3. Default behavior <text>

<text> describes the behavior of the system if the parameter is omitted. This option
is selected if it is not possible to specify a default value.
Examples:
• Optional parameter DATE
Default value: current date.
The current date is used.
• Optional selection parameter for DISP and STAT commands
Default behavior: no restriction of output.
Output is not restricted by omission of the parameter.
• Optional control parameter for CR, ENTR, CAN and MOD commands
Default behavior: no effect on the database.
The database is not modified.
• Optional control parameter for ACT, DACT, DIAG and TEST commands
Default behavior: no effect on the process.
The process is not affected by omission of the parameter.

2.3.2 Output manual (OML)

Like the TML, the output manual (OML) is also generated on a version- and project-spe-
cific basis and contains all command outputs applicable for the project in question.
The output manual (OML) describes the system outputs. The output masks are ar-
ranged in numerical order. For each mask, the output format is shown and the individual
output parameters are explained.
Table 2.5 shows the structure of the OML:

Chapter Contents

Introduction (IN) Structure of the command description, command syntax

Masks (MSK) Description of the MML output masks
(project-specific scope)
Reference Lists (TAB) Relationship between the output masks and the
possible commands

Tab. 2.5 Structure of the OML

The table part of the output manual contains a reference list arranged according to the:
– Mask number,
leading to the mask variant, message group and command name.
– Message group,
leading to the mask number, mask variant and command name.

A50016-D1110-A502-1-7619 21
OGL-MN Information
System

2.4 Fault Reports

Faults that are found during operation or maintenance are classified as follows:
– software errors
– hardware faults
– documentation errors.
Error reports can be submitted by the customer (external error report) and by internal
departments.
The customer should submit error reports according to the prearranged procedure. It is
sufficient to send an informal letter including a “red-pen correction” of the document con-
cerned.
Internal error reports can be submitted after release of the operating documents as
from B600 (as from B500 for TML).
Error messages are logged on a document correction tool or a decentralized logging tool
(FMERF), or entered centrally in a database directly via FEKAT.
Reminder lists are generated from FEKAT and sent at predefined intervals to the re-
sponsible departments and the project integrator (supervisor), to draw their attention to
error reports which have not been dealt with.

22 A50016-D1110-A502-1-7619
Information OGL-MN
System

3 Abbreviations
CN core network
CSC combined switching center
ECD exchange configuration documents
EMCYMN emergency manual
EMML extended man-machine language for
screen-oriented terminals
HLR home location register
ITU International Telecommunication Union
MMI man-machine interface
MML man-machine language
MMN maintenance manual
MN manual
MSC mobile-services switching center
NM nonstandard maintenance manual
O&M operation and maintenance
OGL operator guidelines
OMN operation manual
SDL specification and description language
SS7 signaling system no.7
SSNC signaling system network control
SSS switching subsystem
SU subscriber
TML task manual
TOP task oriented procedures
VLR visitor location register

A50016-D1110-A502-1-7619 23
OGL-MN Information
System

24 A50016-D1110-A502-1-7619