SIEMENS Emergency Cases

Emergency Cases
Software
EMCYMN
A30808-X3074-A473-2-7620
EMCYMN
Emergency Cases Software
Copyright (C) Siemens AG 1996

Issued by the Public Communication Network Group
Hofmannstrae 51
D-81359 Mnchen
Technical modifications possible.
Technical specifications and features are binding only insofar as
they are specifically and expressly agreed upon in a written contract.
AD 2
A30808-X3074-A473-2-7620
EMCYMN
Issues
Note on the change indication:
The change indications for a title marked as issue 1 refer to the previous version. The
change indications for a title with an issue greater than 1 refer to the preceding issue.
Change indications (Ind.):
N = new;
G = modified;
0 = deleted;
Document
Register
Titel
Page(s)
ADMIN
EMCYMN . . . . . . . . . . . . AD . . . . . . . . . . . . . . . . . . . . . . . . . 1... 10
EMCYMN . . . . . . . . . . . . IN . . . . . . . . . . . . . . . . . . . . . . . . . . 1... 6
Register
2 G
1
TL
EMCYMN . . . . . . . . . . . . TL . . . . . . . . . . . . . . . . . . . . . . . . . 1... 4
Register
Issue/Ind.
2 G
PROC
EMCYMN . . . . . . . . . . . . PROCIN. . . . . . . . . . . . . . . . . . . . . 1...

EMCYMN . . . . . . . . . . . . ENTRY . . . . . . . . . . . . . . . . . . . . . 1...
EMCYMN . . . . . . . . . . . . EY100 . . . . . . . . . . . . . . . . . . . . . . 1...
EMCYMN . . . . . . . . . . . . EY130 . . . . . . . . . . . . . . . . . . . . . . 1...
EMCYMN . . . . . . . . . . . . EY150 . . . . . . . . . . . . . . . . . . . . . . 1...
EMCYMN . . . . . . . . . . . . EY170 . . . . . . . . . . . . . . . . . . . . . . 1...
EMCYMN . . . . . . . . . . . . EY190 . . . . . . . . . . . . . . . . . . . . . . 1...
EMCYMN . . . . . . . . . . . . EY191 . . . . . . . . . . . . . . . . . . . . . . 1...
EMCYMN . . . . . . . . . . . . EY192 . . . . . . . . . . . . . . . . . . . . . . 1...
EMCYMN . . . . . . . . . . . . EY193 . . . . . . . . . . . . . . . . . . . . . . 1...
EMCYMN . . . . . . . . . . . . EY194 . . . . . . . . . . . . . . . . . . . . . . 1...
EMCYMN . . . . . . . . . . . . EY350 . . . . . . . . . . . . . . . . . . . . . . 1...
EMCYMN . . . . . . . . . . . . EY360 . . . . . . . . . . . . . . . . . . . . . . 1...
EMCYMN . . . . . . . . . . . . EY370 . . . . . . . . . . . . . . . . . . . . . . 1...
EMCYMN . . . . . . . . . . . . EY380 . . . . . . . . . . . . . . . . . . . . . . 1...
EMCYMN . . . . . . . . . . . . EY400 . . . . . . . . . . . . . . . . . . . . . . 1...
EMCYMN . . . . . . . . . . . . EY500 . . . . . . . . . . . . . . . . . . . . . . 1...
EMCYMN . . . . . . . . . . . . EY501 . . . . . . . . . . . . . . . . . . . . . . 1...
EMCYMN . . . . . . . . . . . . EY502 . . . . . . . . . . . . . . . . . . . . . . 1...
EMCYMN . . . . . . . . . . . . EY503 . . . . . . . . . . . . . . . . . . . . . . 1...
EMCYMN . . . . . . . . . . . . EY504 . . . . . . . . . . . . . . . . . . . . . . 1...
EMCYMN . . . . . . . . . . . . EY710 . . . . . . . . . . . . . . . . . . . . . . 1...
EMCYMN . . . . . . . . . . . . EY730 . . . . . . . . . . . . . . . . . . . . . . 1...
EMCYMN . . . . . . . . . . . . EY920 . . . . . . . . . . . . . . . . . . . . . . 1...
EMCYMN . . . . . . . . . . . . EY930 . . . . . . . . . . . . . . . . . . . . . . 1...
4
14
6
12
40
14
18
12
24
24
22
18
10
12
16
8
4
40
18
8
12
18
18
4
8
1
1
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
EMCYMN . . . . . . . . . . . . TABIN . . . . . . . . . . . . . . . . . . . . . . 1... 2
Register
Register
TAB
APP
EMCYMN . . . . . . . . . . . . APP . . . . . . . . . . . . . . . . . . . . . . . . 1... 2
A30808-X3074-A473-2-7620
G
G
G
G
G
G
G
G
G
G
G
G
G
G
G
G
G
G
G
G
G
G
G
AD - 3
EMCYMN
This document consists of a total of 408 Pages
AD- 4
A30808-X3074-A473-2-7620
EMCYMN
Contents
Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AD - 3
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AD - 5
Illustrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AD - 7
Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AD - 9
1
1.1
1.2
1.3
1.4
1.5
1.6
1.7
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN - 1
Recommendations to the Emergency Manual . . . . . . . . . . . . . . . . . . . . IN - 1
List of CALL numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN - 2
Emergency Manual remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN - 2
Definition of an Emergency Situation . . . . . . . . . . . . . . . . . . . . . . . . . . . IN - 2
Alarm Notification in Emergencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN - 3
Postprocessing of Emergencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN - 3
Recommendations for emergency precautions . . . . . . . . . . . . . . . . . . . IN - 4
Task List EMCYMN, MMN:SW and NM:SW . . . . . . . . . . . . . . . . . . . . . . TL - 1
3
3.1
3.2
3.3
3.4
3.5
3.6
3.7
3.8
3.9
3.10
3.11
3.12
3.13
3.14
3.15
3.16
3.17
3.18
3.19
3.20
3.21
3.22
3.23
3.24
Procedures (PROCIN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PROCIN - 1

Identifying an Emergency Situation . . . . . . . . . . . . . . . . . . . . . . . . ENTRY - 1
Actions after unsuccessful recovery . . . . . . . . . . . . . . . . . . . . . . . . EY100 - 1
Manual Initial Start from MDD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . EY130 - 1
Manual Initial Start from an APS Save Tape . . . . . . . . . . . . . . . . . EY150 - 1
Rescue of Background Memory Data . . . . . . . . . . . . . . . . . . . . . . . EY170 - 1
Initial Start (FALLBACK GENERATION) . . . . . . . . . . . . . . . . . . . . EY190 - 1
Total Shutdown / Partial Shutdown. . . . . . . . . . . . . . . . . . . . . . . . . EY350 - 1
Partial Restart after Partial Shutdown. . . . . . . . . . . . . . . . . . . . . . . EY360 - 1
Total Restart after Total Shutdown . . . . . . . . . . . . . . . . . . . . . . . . . EY370 - 1
Measures after a power failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . EY380 - 1
Measures after unsuccessful FEPROM patching . . . . . . . . . . . . . . EY400 - 1
Restoration of files on the background memories. . . . . . . . . . . . . . EY500 - 1
Fault Clearance CP113 : Double disk failure MDD. . . . . . . . . . . . . EY710 - 1
Fault Clearance CP113C/CR : Double disk failure MDD . . . . . . . . EY730 - 1
Emergency Situation for CCNC Data . . . . . . . . . . . . . . . . . . . . . . . EY920 - 1
Emergency Situation for Trunk Data. . . . . . . . . . . . . . . . . . . . . . . . EY930 - 1
Tables (TAB). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TAB - 1
Appendix (APP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . APP - 1
A30808-X3074-A473-2-7620
AD 5
EMCYMN
AD 6
A30808-X3074-A473-2-7620
EMCYMN
Illustrations
Fig.
Fig.
Fig.
Fig.
A30808-X3074-A473-2-7620
3.0.1
3.2.1
3.3.1
3.15.1
Elements used in the procedures . . . . . . . . . . . . . . . . . . . . . . PROCIN - 3

Diagram of procedure EY100 . . . . . . . . . . . . . . . . . . . . . . . . . . EY100 - 3
AD 7
EMCYMN
AD 8
A30808-X3074-A473-2-7620
EMCYMN
Tables
Tab. 1.1.1
Tab. 1.2.1
Tab. 1.7.1
Tab. 3.11.1
Tab. 3.11.2
Tab. 3.15.1
A30808-X3074-A473-2-7620
Example of a call list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN - 1

List of CALL numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN - 2
Example of a test call list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN - 5
Creation of MINIMAL CONFIGURATION LIST (MCL). . . . . . . . EY350 - 3
Example of a minimum configuration list (MCL) . . . . . . . . . . . . EY350 - 4
Assignment between processor and processor number . . . . . . EY400 - 3
AD 9
EMCYMN
AD 10
A30808-X3074-A473-2-7620
EMCYMN
1 Introduction
1.1
Recommendations to the Emergency Manual
We request that each action in an emergency situation has to be discussed with the
TAC 1 first.
We recommend that the telephone numbers of assistance personnel be listed in
chapter 1.2 List of CALL numbers by the PTT administration (use the empty
formular according to the example below). This would help to ensure fast response
in an emergency situation.
Some of these numbers may be network node-specific.
An example of such a list is given on the next page.
We recommend that you prepare a partly filled in master form with all fixed data of
an network node. This form should there be available in the O&M center and in the
network node to which it is pertinent. It must be updated after every hardware/firmware/GP or CP software upgrade/modification.
If an emergency situation occurs the first craft person in the network node should
enter the current emergency situation into this form. He can then give fast and
precise information over telephone.
CALL NUMBERS FOR EMERGENCY SITUATIONS
To call in any emergency situation:

1.
TAC 1
2.
Mr. Smith
306/488 ...
office:
304/564 ...
private:
306/832 ...
office:
304/569 ...
private:
312/217 ...
if no answer:
3.
Mr. Miller
Tab. 1.1.1 Example of a call list
A30808-X3074-A473-1-7620
IN - 1
EMCYMN
1.2
List of CALL numbers

According to the example in chapter 1.1, the relevant phone numbers are to be written
down in this chapter.
CALL NUMBERS FOR EMERGENCY SITUATIONS
To call in any emergency situation:
1.
TAC 1
2.
office:
private:
office:
private:
if no answer:
3.
Tab. 1.2.1 List of CALL numbers
1.3
Emergency Manual remarks

Some procedures are supported by command files.
Knowledge about the content of these command files is not needed to process these
procedures. If however more information is required, the command files are reproduced
in the MMN:SW.
The command files are supplied on magnetic tape with the MMN:SW.
Important note
If deviations from the described normal sequence of operations result during the
processing of emergency procedures, it is necessary to consult the next higher
TAC level up to TAC 3 / system company for special fault clearance.
1.4
Definition of an Emergency Situation

The definitions of emergency situations are to be taken from the customer specific
dokumentation.
IN- 2
A30808-X3074-A473-1-7620
1.5
EMCYMN
Alarm Notification in Emergencies

The operating personnel must inform the emergency service of the TAC-1 immediately
after the emergency has occurred.
The TAC-2 is to be informed half an hour after the emergency has occurred.
Alarms from the operating personnel to the TAC-1 and from the TAC-1 to the TAC-2 are
signaled in a similar way:
call to a call handler (organized on a regional basis)
provision of the following information:
name and telephone number of the person notifying the alarm

office (network node)
time at which the emergency occurred
brief description of the problem
send further information, in the form of the questionnaire to the TAC:

as FAX, TELEX, TELETEX, ...
if none of these options is available, go through the list of questions on the telephone with the higher-ranking TAC
any other information to be provided by word of mouth or exchange of letters
If deviations from the described normal sequence of operations result during the
processing of emergency procedures, it is necessary to consult the next higher
TAC level up to TAC 3 / system company for special fault clearance.
1.6
Postprocessing of Emergencies
The reason for postprocessing emergencies is to prevent such emergencies from recurring for the same reasons in the future. An emergency is only considered by the TAC-1
as having been dealt with completely when the following reports have been produced.
An outage report must be completed from scratch after each emergency.

For faults which are caused by software / documentation errors there must be references in the outage report to SW error reports.
An error report should only be generated once per SW version and project for each
error. The normal error symptoms (e.g. service notification no. 81) for SW error
reports should be included, provided they were not lost when the emergency was
dealt with.
If in the TAC-1 the data collection tools (DACOS) have been installed, the appropriate
reports (outage reports, HW-trouble reports or SW-reports) shall be made by means of
these tools.
On the next three pages are found the paper form, being in temporary use, for the
outage report and the explanatory instructions on how to fill it in.
The reports must reach the TAC-2 within 24 hours after emergency case.
SW errors are rectified via the system modification procedures.
A30808-X3074-A473-1-7620
IN - 3
EMCYMN
1.7
Recommendations for emergency precautions

Recommendations for equipping the OMC and switching centers to cope with emergency situations.
1.7.1
Appoint an emergency coordinator:

In order to avoid uncoordinated behavior in emergency situations, we recommend to
appoint one experienced operator in every OMC as emergency coordinator (of
course, where operators work in shifts more than one is needed). During absence of the
emergency coordinator a substitute should be available.
If an emergency is suspected, the operators should not act independently, but should
instead notify the emergency coordinator immediately. He will decide on the action to be
taken. The emergency coordinator should, of course, have access to the save tapes.
1.7.2
Equipping with Service Handsets:

The following recommendations to the operator of the system result from two aspects
concerning the fastest possible method of successfully handling an emergency situation.
Telephone communication to and from the affected network node must be guaranteed during the emergency situation.
When assessing the relative seriousness of an emergency it must be determined, to

which extent switching operation is impaired.
Therefore we would strongly recommend the following:

Another service handset which is connected to a remote exchange should also be
installed in the network node. It should be placed within reach of the local OMT and
within sight to the local SYPD.
The operator should prepare call lists and insert these into the Call Numbers register
in the Emergency Manual (EMCYMN). In an emergency situation calling these numbers
will allow a fast overview to which extent switching operation is impaired.
The layout of these lists should be at least partly specific to the relevant network node
or O&M center. For each network node it should also be different for tests from the OMC
and for local tests from the network node.
IN- 4
A30808-X3074-A473-1-7620
1.7.3
EMCYMN
Example of a call list
A call list for testing switching operation in emergency situations

Local network node
MILFORD
controlled by OMC
DEVON
237 ...
Service handsets in the network node

- at the own network node
237 11 88
- at remote network node
264 326
Local network node ORANGE

EMD
Tab. 1.7.1 Example of a test call list
A30808-X3074-A473-1-7620
IN - 5
EMCYMN
IN- 6
A30808-X3074-A473-1-7620
EMCYMN
2 Task List EMCYMN, MMN:SW and NM:SW

This list is an aid to find the instructions associated with a maintenance task within an MMN binder.
It contains cross-references to the maintenance tasks or other information that enables entry to the Maintenance Manual (MMN/NM/EMCYMN) if the MMN number is missing.
The parameter xx represents the name of the manual for the relevant equipment unit.
2.1
Cross Reference List
APS Saving:
General remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Save the current APS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Startup test of the saved APS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MMN:SW, ADMIN, IN
MMN:SW, APP, APP
MMN:SW, PROC,
SW210
MMN:SW, PROC,
SW211
Checksum mismatch:
General remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Restoration of defective files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MMN:SW, ADMIN, IN
EMCYMN, PROC, EY501
Database:
Expansion via ODAGEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NM:SW, PROC, SW451
Data Collection:
After unsuccessful ISTART. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NM:SW, ADMIN, IN
Emergency Situations:
Identifying an Emergency Situation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EMCYMN, ADMIN, IN
Error Symptoms Saving:

History file saving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MMN:SW, PROC,
SW231
Expansion:
Expansion of data area (ODAGEN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NM:SW, PROC, SW451
Fallback:
Fallback to older generation (ISTART2G). . . . . . . . . . . . . . . . . . . . . . . . . . . .
EMCYMN, PROC, EY190
Files:
Saving, reading of tape
GP Software:
Replacement of PSW files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
History Files:
History file saving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reading history files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IARSTAT:
IARSTAT measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A30808-X3074-A473-2-7620
MMN:SW, PROC,
SW210
NM:SW, PROC, SW441
MMN:SW, PROC,
SW231
MMN:SW, PROC,
SW232
MMN:SW, PROC,
SW221
TL - 1
EMCYMN
IMON:
Background informations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Individual Call Data:
Save the individual call data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Initial Start:
Fallback generation / ISTART2G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
from MDD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
from MTD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Initialization:
Initialization of background memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NM:SW, ADMIN, IN
MMN:SW, PROC,
SW224
EMCYMN, PROC, EY190
EMCYMN, PROC, EY130
EMCYMN, PROC, EY150
MMN:SW, PROC,
SW310
Installation Recovery:
by tape
...................................................
NM:SW, PROC, SW140
LOADLIB:
Replacement of Nonresident Libraries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NM:SW, PROC, SW422
Magnetic Disk Device (MDD):

Double disk failure MDD (CP113D) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Double disk failure MDD (CP113C/CR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Initilization of background memory (MDD). . . . . . . . . . . . . . . . . . . . . . . . . . . .
Manual initial start from MDD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Rescue of background memory data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Restoration of files on the background memories . . . . . . . . . . . . . . . . . . . . . .
Magnetic Tape Device (MTD):

Manual initial start (save tape) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cleaning MTD 2922 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cleaning MTD 2925 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EMCYMN, PROC, EY710

EMCYMN, PROC, EY730
MMN:SW, PROC,
SW310
EMCYMN, PROC, EY130
EMCYMN, PROC, EY170
EMCYMN, PROC, EY502
EMCYMN, PROC, EY503
EMCYMN, PROC, EY150

NM:CP113, PROC,
MTD:STC 2922
NM:CP113C/CR, PROC,
MTD:STC 2925
New Start:
General remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Background informations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MMN:SW, ADMIN, IN
NM:SW, ADMIN, IN
Nonresident Libraries:
Replacement of LOADLIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NM:SW, PROC, SW422
Nonstandard Maintenance:
Support documentation general. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NM:SW
Occupancy Level Messages:

Treatment of Occupancy Level Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . .
ODAGEN:
Expansion of the CP database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MMN:SW, PROC,
SW222
NM:SW, PROC, SW451
OMT:
Initialization PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TL - 2
MMN:PC-BASIS, ADMIN,
IN
A30808-X3074-A473-2-7620
Cleaning OMT for CP113 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Cleaning OMT for CP113C/CR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Split mode operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overheating:
System total shutdown / partial shutdown. . . . . . . . . . . . . . . . . . . . . . . . . . . .
System partial restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System total restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Patch:
Measures after unsuccessful FEPROM patching . . . . . . . . . . . . . . . . . . . . . .
Patch FEPROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Patch Software (CP, CCNC, GP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DCP Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PC (OMT):
Initialization PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EMCYMN
MMN:CP113, TAB,
CLEANOMT
MMN:CP113C/CR, TAB,
CLEANOMT
MMN:PC-BASIS, PROC,
OMT-SPLIT
EMCYMN, PROC, EY350
EMCYMN, PROC, EY360
EMCYMN, PROC, EY370
EMCYMN, PROC, EY400

MMN:SW, PROC,
SW412
MMN:SW, PROC,
SW411
MMN:SW-DCP, ADMIN,
IN
..................................................
IN
MMN:CP113, PROC,
CP870
MMN:CP113C/CR,
PROC, CP970
MMN:PC-BASIS, PROC,
OMT-SPLIT
MMN:PC-TLWS
Power Failure:
Measures after a power failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EMCYMN, PROC, EY380
Progress Messages:
Progress masks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NM:SW, ADMIN, IN
PSW Files:
Replacement of GP Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NM:SW, PROC, SW441
Fault Clearance PC for CP113

Fault Clearance PC for CP113C/CR
Split mode operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TLWS
Recovery:
Actions after unsuccessful recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Evaluation of recovery messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installation recovery from MTD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Measures after recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Plausibility failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Recovery using fallback generation (ISTART2G) . . . . . . . . . . . . . . . . . . . . . .
Treatment of recovery messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EMCYMN, PROC, EY100

NM:SW, ADMIN, IN
MMN:SW, PROC,
SW330
NM:SW, PROC, SW140
NM:SW, PROC, SW110
MMN:SW, PROC,
SW330
EMCYMN, PROC, EY190
MMN:SW, PROC,
SW330
Restart:
A30808-X3074-A473-2-7620
TL - 3
EMCYMN
Evaluation of initial reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Restoration:
Restoration of statistic meters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Restoration of generation files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Restoration of non-generation files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Saving disk contents
to MTD
...................................................
Saving of:
APS (quarterly, routine) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Error symptoms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
History files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Individual call data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Interadministration revenue accounting and statistics (IARSTAT). . . . . . . . . .
Shutdown:
System total shutdown/partial shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System partial restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System total restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Software Changes:
General remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Input of patches for exchange software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Input of FEPROM Firmware (CP113C/CR) . . . . . . . . . . . . . . . . . . . . . . . . . . .
Input of patches for DCP Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Software change for PC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Statistic meters:
Restoration of defective statistic meters from tape . . . . . . . . . . . . . . . . . . . . .
UPDATE Messages:
Treatment of UPDATE Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TL - 4
MMN:SW, PROC,
SW330
MMN:SW, PROC,
SW223
EMCYMN, PROC, EY501
EMCYMN, PROC, EY502
EMCYMN, PROC, EY503
MMN:SW, PROC,
SW210
MMN:SW, PROC,
SW210,
MMN:SW, PROC,
SW211
MMN:SW, PROC,
SW231
MMN:SW, PROC,
SW231
MMN:SW, PROC,
SW224
MMN:SW, PROC,
SW221
EMCYMN, PROC, EY350
EMCYMN, PROC, EY360
EMCYMN, PROC, EY370
NM:SW, ADMIN, IN
MMN:SW, PROC,
SW411
MMN:SW, PROC,
SW412
MMN:SW-DCP, ADMIN,
IN
IN
MMN:SW, PROC,
SW223
MMN:SW, PROC,
SW320
A30808-X3074-A473-2-7620
EMCYMN
3 Procedures (PROCIN)
3.0.1
3.0.1.1
General remarks
Continuing the processing of an interrupted command file after end of session

If end of session has been reached after interruption of a command file processing
(Initial Start, New Start or Time Out), the session switches must be redefined before the
command file can be started again.
The respective starting point within the command file is addressed via the position of the
process switches.
At the beginning of each command file, there is a list of the possible entry points together
with the appropriate switch positions.
3.0.1.2
Remark for the interpretation of MML masks

SENDER
RECEIVER
: @#######
: @#######
START START
FILE IDENTIFICATION
DATA TYPE
BYTES/
/END- /END: FILE
VSN
STATE : ERROR
RECORDS
DATE TIME
-+----------------+------+-----+-+-----+-+--+----+---------+-----+----@ @#########
@##### @##
@ @#### @ @# @### @######## @#### @####
@ @#########
@##### @##
@ @#### @ @# @### @######## @#### @####
In displayed MML masks the dummy entries @ and @###..# are only replaced by
values in the places which are relevant to the current process and necessary for understanding it.
SENDER
RECEIVER
: @#######
: @#######
START START
FILE IDENTIFICATION
DATA TYPE
BYTES/
/END- /END: FILE
VSN
STATE : ERROR
RECORDS
DATE TIME
-+----------------+------+-----+-+-----+-+--+----+---------+-----+----S SY.MSGXREF
LOGTAP TR
@ @#### @ @# @### @######## @#### @####
R SY.MSGXREF
SYSVSN CRD
@ @#### @ @# @### @######## @#### @####
A30808-X3074-A473-1-7620
PROCIN - 1
EMCYMN
3.0.1.3
Remark for the interpretation of system messages (message header)

Each system output message, whether command controlled or unsolicited, begins with
a message header, which is to be interpreted as follows:
1. Message header
exch-name/exch-id/aps-name,version/xyz
job-no
[[/OMT-0x/userid]
yy-mm-dd hh:mm:ss
datatype/masknumber
2. Interpretation
exch-name
name of the exchange, created during initial start-up of

the exchange via MML dialog
exch-id
identification of the exchange, created during initial startup of the exchange via MML dialog
aps-name
name of APS, created during initial start-up of the

exchange via MML dialog
version
APS function version, created during APS production
xyz
CP operating mode
yy-mm-dd hh:mm:ss
x=(0-5)
B:CMY status
y=(0,1)
BAP-MASTER number
z=(0-2)
SYSTEM status
0=normal
1=split/ switching
2=split/ non-switching
date and time of the output message
jobnumber[/jobnumber] jobnumber(s) created by the message control; during

command file processing a second jobnumber
PROCIN- 2
OMT-0x
not displayed for unsolicited system output messages;

shows the input device used before a dialog message is
output
userid
not displayed for unsolicited system output messages;

shows the user identification for the used input device
datatype/masknumber
computerised incorporation of the message text
A30808-X3074-A473-1-7620
3.0.2
Block number
Commentary
(in italics)
EMCYMN
Explanations of the Procedure Elements
Branch symbol
12 Decision block
Must clearance of this fault be postponed (e.g. because no spare
modules available)?
Y h .....13
N h .....16
Branch dest.
(block number)
Commentary are always written in italics
MML command
input
13 Decision block
b CONF LTG:LTG=tsg-ltg,OST=ACT;
MML mask
(Courier
typeface)
CONFIGURATION ABORTED, PLEASE DO STAT

To evaluate the system output, see
.....4.19
Continue according to the system reaction:
Multiple
branch
- EXECD..................................................................................................
- NOT EXECD..........................................................................................
- else.........................................................................................................
Yes/No
branch
i....PROC:LG001N
h.......18
h.......19
Reference to
chapter with
additional
information
Block
Branch symbol
with reentry
Fig. 3.0.1 Elements used in the procedures

The commands used correspond to EMML. Commands with a hyphen in the command
header (before the colon) must be entered in BMML without the hyphen and the
following parameter.
Example:
STAT CR-CR:LTG=tsg-ltg;
must be entered in the BMML as
STAT CR:LTG=tsg-ltg;
A30808-X3074-A473-1-7620
PROCIN - 3
EMCYMN
PROCIN- 4
A30808-X3074-A473-1-7620
3.1
3.1.1
EMCYMN
Identifying an Emergency Situation

Important Preliminary Remarks
In emergency situations the system reacts with automatically executed immediate
measures which prevent a total breakdown and which should, at least partly, maintain
switching operations.
Therefore, it is extremely important to allow the system the chance to regenerate itself
using automatic recovery measures !
Important Note:
Operating personnel may not carry out emergency procedures (EYxxx) independently. In any case first of all a system specialist (TAC) is to be consulted!
3.1.2
Alarm Indication Plan for an Emergency Situation
Phase 1:
The operator recognizes the first error symptoms of an emergency

situation.
The operator informs the emergency coordinator.
Phase 2:
The emergency coordinator*) orders and controls all further

measures in order to ascertain the system status and the effect of the
fault (see flowchart).
The emergency coordinator then decides on the EMERGENCY and
informs the system specialist (TAC).
Phase 3:
The system specialist (TAC) orders all further measures and

decides on which emergency procedure to use.
*) For emergency coordinator function see register Introduction (IN),

chapter 1.7 Recommendations for emergency precautions.
A30808-X3074-A473-1-7620
ENTRY - 1
EMCYMN
3.1.3
Flow Chart for an Emergency Situation (SSS side)

We will look at the following four types of events (1-4) which could be initiated by an
emergency and which should therefore be checked.
3.1.3.1
Instructions for the operator (Phase 1)

At least one of these four events has occurred:
1. Critical alarm on the SYPD
Both lamps on the affected display (CENTRAL UNITS, RECOVERY, SYP, ...)
are flashing alternately.
2. System does not react to inputs and / or no dial tone (Service Handsets)
(Has it been guaranteed that the malfunction is not the result of a malfunction in the
terminal or of a faulty feeder?)
3. Many subscriber complaints: ... no MOC possible ...
4. Many subscriber complaints: ... certain directions are not available ...
Actions of the operator:
3.1.3.2
Note the time.
Inform the emergency coordinator immediately.
Instructions for the emergency coordinator (Phase 2)

Actions of the emergency coordinator:
Reason for the alarm:

The emergency coordinator is alerted by the operator. The operator tells him which
emergency indicating event (1-4) has occurred.
Entering the flow chart:

The emergency coordinator evaluates the information given by the operator and the
decides which of the four entry points [1], [2], [3] or [4] of the following flow chart to
start with.
All further measures (according to the flow chart) are initiated by the emergency
coordinator and are carried out under his instructions !
Comment:
ENTRY- 2
For emergency coordinators functions see: 1.7 Recommendations for emergency

precautions.
In the following flow chart symbolic terms are used as connectors:
SUB_COM, EMCY, TAC_MENU, SSP_LIST, T_CALLS, SYP_AL,
SYS_N_REA
A30808-X3074-A473-1-7620
3.1.3.3
EMCYMN
Flow Chart
[1]
Critical alarm on the SYPD

A critical alarm is displayed by both lamps on the affected display (CENTRAL
UNITS, SYP, ...).
In contrast to the following 3 situations, the system has most probably recognized a central problem and is reacting correctly within the programmed operations plan for this.
Entry point:
[2]
SYP_AL
System does not react to inputs

It must first be guaranteed that the malfunction is not the result of a malfunction
in the terminal or of a defective feeder. A temporary computer overload is also
considered as a cause.
Dont Panic!
Do not interrupt the system !
Some recovery stages may last approximately 20 minutes (e.g. ISTART2G); in
general, no call setup can take place during this time.
As operator, give the system the chance to carry out the programmed recovery
measures (see chapter 3.1.4).
Entry point:
A30808-X3074-A473-1-7620
SYS_N_REA
ENTRY - 3
EMCYMN
[3]
Many subscriber complaints: ... no MOC possible ...

So that we can exclude a breakdown of peripheral sections, the equipment
number of the faulty subscribers should first of all be checked (common
LTGB, DSU/DLU or in RSS, ICE, BCE, BTS).
Difference between situation [3] & [2]:
A few minutes have surely passed since the beginning of the emergency so
that the system must have reached a quasi stationary status by this time (see
chapter 3.1.4)
-
The system has reorganized itself using automatic recovery measures

- ISTART2G is still working
- Rolling Recovery
- Central hardware breakdown
- Power supply breakdown
- Overheating
Some recovery stages may last approximately 30 minutes (e.g. ISTART2G);

in general, no call setup can take place during this time.
As operator, give the system the chance to carry out the programmed
recovery measures (see chapter 3.1.4).
Entry point: SUB_COM
[4]
Many subscriber complaints: ... certain directions are unavailable ...

Difference between situation [4] & [3]:
The subscriber is receiving a connection but cannot reach certain destinations.
This could mean:
-
Breakdowns in peripheral areas of the own network node (DLU, LTG, SN

areas, MB, CCNC parts)
- Breakdowns / partial breakdowns of the distant network node (local
network node, long distance network node, special network node) or of
trunks to this network node
- SW faults, data base faults
Entry point: SUB_COM
ENTRY- 4
A30808-X3074-A473-1-7620
EMCYMN
T_CALLS
These lists must identify specifically for each site which numbers
are to be dialed from which service
handsets, in order to determine
which traffic type could be faulty
(see chapter 1.7 Recommendations for emergency precautions).
Revise the prepared test call

lists (see chapter 1.7 Recommendations for emergency
precautions)
Is exchange traffic
disrupted ?
EMCY
SYP_AL
EMCY
Is there a display on the

SYPD now?
N
Interrogate system status:
STAT SSP;
Is a list of the SSP units

and their corresponding
OSTs displayed?
Y
SSP_LIST
A30808-X3074-A473-1-7620
ENTRY - 5
EMCYMN
SSP_LIST
The previously noted fault could
be caused by:
- Temporary Overload
- Operation of Recov. (see 3.1.4)
- Operation of central diagnosis
- Switching over of a central unit
- HW / SW fault in the OMT
(or in previously connected units
inc. DCP, connection CP-DCP)
The system is, apparently,

operating normally (again).
Were recovery messages

output at the assigned
printer in the OMC?
N
Evaluate the messages in

consultation with TAC.
All further measures in
consultation with TAC.
Does the output initiated by

STAT SSP; show equipment
in UNA or MBL?
B
MBL
A: equipment in MBL:
Ascertain the cause:
- Has fault clearance begun?
- HW changes?
UNA
NO
B: equipment in UNA:
An alarm must be displayed at
SYPD
Is an appropriate alarm
being displayed at
SYPD?
END
SYP_AL
N
Proceed further in consultation with TAC
ENTRY- 6
Special fault clearance SYP
A30808-X3074-A473-1-7620
EMCYMN
SYP_AL
Note:
This question should only be
asked after a few minutes have
passed because the SYP and
CU lamps can also flash during
recoveries.
Is there a critical alarm

(high flicker frequency)
for the lamps SYP and
CU?
EMCY
N
Normal entry into
MMN:SYP, procedure
SYP100
Note:
The SYP100 procedure contains
interrogations for recognizing
emergency situations:
- Failure of both MDDs
- ISTART2G
- call processing basic operation
and directs the user to the corresponding procedure.
SYP100:
Emergency Situation
detected?
A total CP breakdown is likely

(EMCY).
Standard Fault Clearance HW:

Entry as per MMN number of
the alarm messages determined in SYP100
Y
Emergency Situation!
Consult TAC personnel!
Fault clearance only via TAC
(Phase 3) !
MMN:xxx
MMN:XXX
Emergency Situations :
A
Failure of both MDDs:

EMCYMN:EY710
EY710
A30808-X3074-A473-1-7620
A -> Failure of both MDDs.

B -> ISTART2G
ISTART2G (automatic fallback to backup gener.):

EMCYMN:EY190
(postprocessing)
EY190
ENTRY - 7
EMCYMN
EMCY
Emergency situation!
(Phase 3 is initiated)
Were recovery messages

output at the assigned
printer in the OMC?
Y
The messages should be kept
ready for consultation with
TAC!
Call TAC!
All further measures are only
to be done in consultation with
TAC (Phase 3)!
TAC_MENU
ENTRY- 8
A30808-X3074-A473-1-7620
EMCYMN
TAC_MENU
Further action is dependent on

the determined system status.
There exist 3 groups of emergency procedures:
Entry situation 1:
Unsuccessful Recovery:
Entry situation 2:
Overheating / Power failure
EY100
EY350
EY130 :
manual initial start
from MDD
EY170 / EY150 :
rescue of background
memory data /
from save tape
EY350 / EY370 :
total shutdown /
total restart
EY350 :
total / partial shutdown
EY350: Shutdown
EY360: Partial restart
EY370: Total restart
EY380 :
Measures after power
failure
Entry situation 3:
Critical alarm / alarm mask /
MMN:SYP / SYP 100 :
EY190 :
Initial start (fall back
generation)
EY500:
Restoration of background memory files
EY501: Checksum
EY502: GEN-files
EY503: NON-GENfiles
EY504: Restoration
after double
disk failure
EY710 :
Double disk failure
MDD
EY730: (CP113C)
A30808-X3074-A473-1-7620
ENTRY - 9
EMCYMN
SY_N_REA
In the OMC:
Record the tasks which were
carried out with exactly this
network node?
N
Personnel at the site?
Y
Determine cause:
- Hardware Interruption?
- Software Interruption?
- Preparation of tape copies?
5 minutes have passed

since first detection ?
Critical alarm on the

SYPD?
Y
SYP_AL
Dial tone at service handsets ?
N
EMCY
Y
T_CALLS
ENTRY- 10
A30808-X3074-A473-1-7620
EMCYMN
SUB_COM
Connection to test
destination possible?
Y
In order to exclude a callprocessing error, a SSP recovery
of level NSTART3 should be
executed:
RECOV SSP:LEVEL=NSTART3;
Connection to test
destination possible now?
EMCY
Critical alarm at SYPD?
SYP_AL
T_CALLS
A30808-X3074-A473-1-7620
ENTRY - 11
EMCYMN
3.1.4
Information on the current system status

So that a system recovery is not interrupted by any rash actions it is advisable to first
obtain an overview (one which is as complete as possible) of the current system status.
There are various ways of achieving this:
3.1.4.1
SYPD display panel in connection with messages on the

message printer
ISTART2G:
Critical alarm on the SYPD display RECOVERY i.e. both lamps flash alternately and
thereby display an ISTART2G. (This recovery can take up to 30 minutes.)
System messages of the form ##### ... give information on recovery progress. (see
EY190 Block 3).
The system message:
##### INITIAL START PROGRESS MESSAGE #####
END OF LTG LOADING
in conjunction with the following mask:
@##### - RECOVERY INFORMATION
REASON
: @################################
@#######################################
: @#######@
: @#######@
: @#####
DATE
TIME
UNIT
REQUESTED LEVEL
PERFORMED LEVEL
PERFORMED ACTION(S)
: ISTART2G
: ISTART2G
: MEMORY HAS BEEN INITIALIZED
@##############################
LTGS RELOADED WITH CODE AND DATA
CALL PROCESSING STARTED: @#######@
RECOVERY DURATION
: @###@
SECONDS
APS GENERATION
: @#######
STATISTICS
: ERROR COUNTER : @###

THRESHOLD
: @###
INTERVAL
: @#### SEC
EXCEPTIONS
==========
: CONFIGURATION FAILURES OF PERIPHERAL UNITS

DURING RECOVERY
UNIT
---@########
UNIT
---@########
UNIT
---@########
UNIT
---@########
UNIT
---@########
report that ISTART2G was successful and has not run into a loop.
ENTRY- 12
A30808-X3074-A473-1-7620
EMCYMN
MML command inputs:

If the system reacts again to inputs, after recovery has been completed, further information on the type of recovery and the actions carried out can be obtained using the
following MML commands:
DISP ALARM;
SRCH ALARM;
After system reacts again to inputs, after recovery has been completed, information on
the status of the system hardware can be obtained using the following commands:
STAT SSP;
STAT LTG:LTG=X-X;
STAT SN;
STAT SYP;
STAT MB;
STAT DLU:DLU=X;
STAT CCNC:CCNP=X;
The current system status may offer important informations about the reason(s) for the
recoveries.
3.1.4.2
HEX displays on both BAPs:

The HEX displays provide the most exact information on the system status during
recovery and normal operation (see NM:CP113, CP0053), however they require
personnel to be present in the network node!
HEX Display
Interpretation
Axx5
HW recovery is running
Bxx4
SW recovery is running
Dxx2 (xx 80)
normal operation
Exx1 (xx < 99)
normal operation
Dxx2 (xx >80)
Call processing overload

(system reacts automatically)
E991
Processor Overload
(system reacts automatically)
A30808-X3074-A473-1-7620
ENTRY - 13
EMCYMN
ENTRY- 14
A30808-X3074-A473-1-7620
3.2
EMCYMN
Actions after unsuccessful recovery

EY100
3.2.1
Introduction
This procedure should be entered from the procedure ENTRY and only after informing
TAC. The procedure ENTRY contains important advice on evaluating the trace points
(HEX displays on both BAP, module CPCL, socket 189 or maintenance panel display),
which are required in this procedure. The complete trace points are described in
NM:SW-APP .
An unsuccessful recovery can be caused by four different errors. The errors can be identified with help of the following error characteristics.
3.2.2
HW fault in CP area
Causes:
Double failure of HW installations, e.g. MDD-0 and MDD-1, IOC-0 and IOC-1, BCMY-0
and BCMY-1 etc.
Reloading APS generation from the background memory is impossible because of the
HW double failure mentioned.
Symptoms:
In all system start-ups, only the trace points within the HW startup are run through. Then
the restart is aborted.
trace points: A x x 5 (x = optional value)
3.2.3
SW error in CP area
Causes:
No bootable APS generation on the background memories. All APS generations integrated into the escalation are destroyed.
APS generations with the status BLOCKED are used for manual start-ups according to
procedure EY130, but they also do not result in a successful restart.
Symptoms:
All trace points of the HW recovery are run trough. The start-up is aborted within the SW
recovery.
trace points: before B x 7 4 (x = 8, 9, A or B)
3.2.4
HW fault in the peripherals

Causes:
Double failures in HW installations, e.g. SN-0 and SN-1, MB-0 and MB-1 etc.
A30808-X3074-A473-2-7620
EY100 - 1
EMCYMN
Although the APS generation is error-free, the GP software cannot be loaded to the LTG
because of the existing HW fault. The start-up is aborted after an unsuccessful load
attempt.
Symptoms:
All start-up attempts are aborted during loading of the call processing peripherals.
trace points: B x 7 4 (x = 8, 9, A or B)
3.2.5
SW error in the peripherals

Causes:
The code and the data for the LTG is faulty. The start-up is aborted after an unsuccessful
load attempt.
Symptoms:
All start-up attempts are aborted during loading of the call processing peripherals.
trace points: B 2 5 4
3.2.6
For users of the function Manual on PC:

In this procedure it is possible that a branch may be made to a different procedure, and
when this procedure has been worked through it will be necessary to return to the decision block of the calling procedure.
When using the Manual on PC function, the branch back must be made in this case
via the menu item DISPLAY/HISTORY. When this menu item is called up, a list of the
procedure blocks that have been processed so far is displayed. In this list, the last block
that was executed in the calling procedure (= the branch destination) must be clicked on
and confirmed with OK. The branch back to this block is then made.
EY100- 2
A30808-X3074-A473-2-7620
3.2.7
EMCYMN
Diagram
see procedure ENTRY

run procedure
EY350
yes
Overheating ?
no
any unused generations ?
no
yes
manual initial start from MDD

(EY130) with different generations
yes
EY130 successful ?
no
end of procedure
evaluate trace points and
output messages
determine error cause
HW fault in
CP area
HW fault in the
peripherals
offline diagnostics;
fault clearance;
run EY130
INSTALL MODE;
diagnostics;
run EY130
SW error
form save tape
(EY150)
error cleared ? no
yes
end of procedure
Fig. 3.2.1 Diagram of procedure EY100
Information
Before running this procedure, the procedure ENTRY should be executed to

ensure that an emergency situation exists which justifies the execution of this
procedure.
For users of the function Manual on PC : the branch back to this block is made
via menu item DISPLAY/HISTORY.
In addition the introduction of this procedure should be read. It contains important advice on error identification.
A30808-X3074-A473-2-7620
i ... EMCYMN,
PROC, ENTRY
...... Introduction
EY100 - 3
EMCYMN
Total shutdown/restart
In special fault situations ( e.g. overheating) it is necessary to execute a total

shutdown/restart. This must be carried out on the instruction of TAC.
Y h ...EMCYMN,
Is total shutdown/restart necessary ?
PROC, EY350
N h ... 3
3
Unused generations
If an error occurs, the system starts recovery automatically, using all not blocked
APS generations existing on the background memories.
Y h ... 4
N h ... 7
Are there any APS generations which were not used by recovery ?
Manual initial start from MDD
A manual initial start from background memory has to be executed according to

procedure EY130. The existing generations should be used in the following
sequence:
A manual initial start from background memory has to be executed according to
procedure EY130. The existing generations should be used in the following
sequence:
1. attempt: procedure EY130 with ACTGEN (active generation)
2. attempt: procedure EY130 with BACKGEN (backup generation)
3. attempt: procedure EY130 with GOLDGEN (golden generation)
In order to exclude HW faults, the HW configuration (MDD, IOC, etc.) used for
the start-up is to be varied.
The progress of every start-up should be observed using the indicated trace
points on the module (socket 189 in both BAP or maintenance panel). Next,
every start-up should be evaluated with respect to the trace points which were
passed through and the messages output.
PROC, EY130
Success of Manual initial start from MDD

Was a manual initial start according to procedure EY130 successful ?
i....EMCYMN,
Y h ... 16
N h ... 6
Further unused generations

Are there any unused APS generations on the background memories ?
EY100- 4
Y h ... 4
N h ... 7
A30808-X3074-A473-2-7620
Unused HW combination
Are there any unused HW combinations ?
Y h ... 8
N h ... 9
Change HW combination
The hardware combination must be changed and then a manual initial start
must be initiated.
EMCYMN
h ... 4
Trace point A x x 5
Start-up attempts are made with all APS generations existing on the background memories. All start-up attempts were aborted. To determine the error
cause, the messages output have to be evaluated.
Were only the trace points A x x 5 passed through in every start-up ?
10
Trace point B x 7 4
Were the trace points B x 7 4 passed through in every start-up ?
11
Y h ... 11
N h ... 2
Trace point B 2 5 4
Were the trace points B 2 5 4 reached in every start-up ?
12
Y h ... 12
N h ... 10
Y h ... 2
N h ... 14
HW fault in CP area
If there is a fault in the CP area, proceed as follows:
1. off-line diagnostics of CP units (IOC, MDD, etc.)
2. fault clearance of CP units according to the relevant MMN
3. manual initial start with active generation (ACTGEN) from MDD according to
procedure EY130
The individual actions must be carried out on the instruction of TAC (according
to MMN:CP113 and CML).
13
h ... 15
Manual initial start from save tape
If all available generations are destroyed, a manual initial start from save tape
(according to procedure EY150) is to be executed.
h ... EMCYMN,
PROC, EY150
14
HW fault in the peripherals

In case of HW faults in the peripherals, proceed as follows:
1. BOOT system in INSTALL MODE
2. diagnostics of HW units (SN, MB, etc.)
A30808-X3074-A473-2-7620
EY100 - 5
EMCYMN
3. fault clearance of CP units according to the relevant MMN (e.g. MMN:SN)

4. manual initial start with active generation (ACTGEN) from MDD according to
procedure EY130
The individual actions must be carried out on the instruction of TAC (according
to the relevant MMN and CML).
15
Result of fault clearance

Has fault been cleared with actions taken ?
16
Y h ... 16
N h ... 1
End of procedure
End of procedure
END
EY100- 6
A30808-X3074-A473-2-7620
3.3
EMCYMN
Manual Initial Start from MDD

EY130
3.3.1
Introduction
A manual initial start from MDD causes the Application Program System (APS) to be
reloaded from a MDD selected by the user and to be initialized.
Before the loading process is started, appropriate parameter input during the manual
initial start makes it possible to format the main memory.
During the initial start phase, existing connections are cleared down and new ones
cannot be setup.
This procedure should be used only in case of failures of system initial start routines or
in case of serious hardware faults and software errors.
Notes:
The restart time of call processing is notified in the output line: CALL PROCESSING
STARTED AT : hh:mm:ss
All system messages shown in this procedure are output only if the output suppression has been removed. By entering the commands ACT OUTSUP ,
DACT OUTSUP and DISP OUTSUP the output suppression can be changed and
displayed.
System messages which are stored for statistical purposes in the history file
HF.ARCIVE as well as being output are identified in the job number line of the
message output with HF.ARCHIVE - vvvv (vvvvv = entry sequence number).
Reading the history file is done according to SW232.
If there is a generation fallback in a HLR, it must be safeguarded that the authentification

key of the fallback generation is identical to the authentification key which is loaded in
the IOP:AUC module.
In certain cases the appropriate authentification key must be loaded from ACM cards via
a Chip Card Reader into the IOC:AUC modules. Description see OMN:SSS, SU,
TS-011.
A30808-X3074-A473-2-7620
EY130 - 1
EMCYMN
3.3.2
Diagram
manual initial start from

MDD is initiated
analyzing recovery message
successful ?
no
yes
back to previous
procedure
delete alarms
irreparable faults during
meter check ?
no
yes
restoration of faulty
meter counts according
to procedure SW223
display hardware
configuration
symptom saving
according to
procedure SW231
Important information
It must be pointed out that calling of initial start constitutes a serious intervention
in the switching system and that the user may only execute it in special situations. During error free operation this procedure may not be executed.
......Introduction
CP selection
What kind of CP is installed ?
CP113
CP113C
h ... 3
h ... 6
BAP selection at CP113

Which BAP shall execute the manual initial start ?
BAP-0
BAP-1
EY130- 2
h ... 4
h ... 5
A30808-X3074-A473-2-7620
EMCYMN
BOOT BAP 0 at CP113
The entries ; and MAN according to the following blocks must be made
immediately after the correspondent requests for entry have been made. Additionally the following actions have to be done one after the other without delay.
Press RESET key for BAP-1
Locate module PIDAT for BAP-1 in BCMY-0 and BCMY-1 (moloc 145). Put
switch SPB in the ON position (up) on both modules.
Press BOOT key for BAP-0
h ... 9
BOOT BAP 1 at CP113
Press RESET key for BAP-0
switch SPB in the ON position (up) on both modules.
h ... 9
BAP selection at CP113C

BAP-0
BAP-1
h ... 7
h ... 8
BOOT BAP 0 at CP113C
Locate module DCCMC for BAP-1 in BCMY-1 (moloc 101). Put switch S1 in the
OFF position (down).
h ... 9
BOOT BAP 1 at CP113C
OFF position (down).
A30808-X3074-A473-2-7620
h ... 9
EY130 - 3
EMCYMN
Start IPL113
A faulty entry during the manual bootstrap (IPL113) may lead to a situation that
no further entries will be accepted. In this case the procedure is to be continued
with block 2.
IPL113: MANUAL START - CURRENT CONFIGURATION
UNIT
STATUS
TEST
********************************************
BAP-0
@#####
@#####
BAP-1
@#####
@#####
B:CMY-0
@#####
@#####
B:CMY-1
@#####
@#####
CMY-0
@#####
@#####
CMY-1
@#####
@#####
IOC-0
@#####
@#####
IOC-1
@#####
@#####
IPL113: ENTER PARAMS
TO DIAGNOSE MEMORY
TO FORMAT MEMORY
TO CONTINUE
:
:
:
DIAG;
FORMAT;
;ETX
;
IPL113: MANUAL START ENTER PARAMS
TO
TO
TO
TO
TO
10
START APS MANUALLY

START INSTALLAT.RECOV.
START UTILITY(MONITOR)
STOP INITIAL START
START APS AUTOMATICALLY
:
:
:
:
:
MANUALLY;
INSTALLATION;
UTILITY;
STOP;
;ETX
Selection of MDD
Shall the manual initial start be carried out specific from MDD-0 or MDD-1 ?
EY130- 4
Y h ... 11
N h ... 17
A30808-X3074-A473-2-7620
11
b
EMCYMN
Start from fixed MDD

MAN;
IOC-0 MDD : BZS/AKD AND GENERATION-LIST
@#############
actgen
@#######################
------backgen
@#######################
------goldgen
@#######################
@#############
actgen
@#######################
------backgen
@#######################
------goldgen
@#######################
MANUAL RECOV. - LOADING VIA IOC : IOC-0;/IOC-1;
Remark:
Mask entries between broken lines are not always present.
12
Selection of IOC
Which IOC shall be used for loading ?
h ... 13
h ... 14
IOC-0
IOC-1
13
b
Loading via IOC-0

IOC-0;
LOAD.DEV.=*MDD0* -GENERATION TO LOAD
NAME;(8 CHAR)
For the following entry the name of the generation (actgen) can be taken from
the generation list. In case of procedure entry from EY100 also backgen or
goldgen is possible.
...... 11
actgen;
MANUAL RECOVERY
LTG LOADING :
Should the LTGs be load ?
A30808-X3074-A473-2-7620
Y;/N;
Y h ... 15
N h ... 16
EY130 - 5
EMCYMN
14
b
Loading via IOC-1

IOC-1;
NAME;(8 CHAR)
For the following entry the name of the generation (actgen) can be taken from
the generation list. In case of procedure entry from EY100 also backgen or
goldgen is possible.
actgen;
MANUAL RECOVERY
LTG LOADING :
Y;/N;
Should the LTGs be load ?
15
b
16
b
...... 11
Y h ... 15
N h ... 16
LTG loading
Y;
h ... 18
LTG not loading

N;
17
b
18
Selection of CP
h ... 18
No fixed MDD
What kind of CP is installed ?

CP113
CP113C
19
h ... 19
h ... 22
BAP selection at CP113

BAP-0
BAP-1
20
BAP-0 booted at CP113

switch SPB in the OFF position (down) on both modules.
21
h ... 25
BAP-1 booted at CP113

switch SPB in the OFF position (down) on both modules.
22
h ... 20
h ... 21
h ... 25
BAP selection at CP113C

BAP-0
BAP-1
EY130- 6
h ... 23
h ... 24
A30808-X3074-A473-2-7620
23
BAP-0 booted at CP113C

ON position (up).
24
EMCYMN
h ... 25
BAP-1 booted at CP113C

ON position (up).
A30808-X3074-A473-2-7620
h ... 25
EY130 - 7
EMCYMN
25
Start-up messages
The following messages are an extract of whole recovery messages output.

SYSTEM - RECOVERY
DATE
TIME
PERFORMED LEVEL
PERFORMED ACTION(S)
APS GENERATION
ALARM
MMN:SW330-0001
:
:
:
:
@#######@
@#######@
ISTART2
@############################################
@##############################
: @#######
FCP RECOVERY REPORT

ACTUAL CONFIGURATION: UNIT
OST LOAD DEVICE
-------+----+----------MDD-00 @## @##
MDD-01 @## @##
ACTUAL GENERATION
: NAME
CREATION DATE
LAST CREATED
---------+------------------+-----------@####### @####### @####### @##
If one MDD is inoperable, it is to be cleared of faults according to MMN:SW,

REG: CP113, PROC: SW310 after this procedure is finished.
#####
#####
#####
#####
#####
#####
#####
#####
INITIALSTART PROGRESS MESSAGE

LTG-CODE DOWNLOADING LOADTYPE xx
START xx. OF nn CODE SEGMENTS
:
:
:
:
:
:
LTG-CODE DOWNLOADING LOADTYPE zz
START zz. OF nn CODE SEGMENTS
START OF DIGIT-TABLE DOWNLOADING
START OF LTU-DATA DOWNLOADING
START OF LTG-PORTDATA DOWNLOADING
START OF LTG ACTIVATION
START OF DLU-DATA DOWNLOADING
END OF LTG LOADING
#####
#####
#####
#####
#####
#####
#####
#####
ALL DOUBLE FILES SYNCHRONIZED
If error messages for IOP:AUC are displayed, the authentification keys may be
faulty.
EY130- 8
......Introduction
A30808-X3074-A473-2-7620
26
EMCYMN
Recovery message
SYSTEM - RECOVERY INFORMATION
REASON
: @################################
@#######################################
: @#######@
: @#######@
: @#####
DATE
TIME
UNIT
REQUESTED LEVEL
PERFORMED LEVEL
PERFORMED ACTION(S)
: ISTART2
: @########
: @##############################################
@##############################
@###############################
RECOVERY DURATION
: @###@
SECONDS
APS GENERATION
: @#######
STATISTICS

THRESHOLD
: @###
INTERVAL
: @#### SEC
EXCEPTIONS
==========

DURING RECOVERY
UNIT
---@########
UNIT
---@########
UNIT
---@########
UNIT
---@########
UNIT
---@########
For detailed information about the recovery output message see.
27
...... ADMIN,
NM:SW,
IN
User identification and password
When the next command is input, the system requests the user identification
and the password. After input of user identification and password the command
is executed.
If there is a call key at the OMT, the system requests the user identification and
the password as soon as the call key is pressed.
28
Analyzing recovery message
The recovery messages must be analyzed.

Was the manual initial start successful ?
A30808-X3074-A473-2-7620
Y h ... 30
N h ... 29
EY130 - 9
EMCYMN
29
Return to procedure EY100
Y h ...EMCYMN,
Was this procedure called by procedure EY100 ?
PROC, EY100
N h ...EMCYMN,
PROC, EY190
30
b
Display alarm status

DISP ALARM:OBJECT=RECOV;
The following message is an example for the whole alarm messages output.
command repetition
OBJECT =
ALTYPE =
PABCAUSE=
ALARM-ID:
31
EXECD
RECOV
ALPRIO = MAJOR
ALSTAT = @# MSGNO = @####
@#######################
@#################################################
@#############################################################
Delete alarms
The following command has to be executed for all alarms with ALPRIO=MAJOR
that are assigned to an ISTART message.
SET ALSTAT:MSGNO=msgno,ALSTAT=C;
command repetition
32
EXECD
Meter check
Y h ... 33
N h ... 34
Are irreparable comparator faults determined during meter check ?
33
Meter restoration
name METER AUDIT
RESULT : NOT REPAIRABLE ERRORS ON FILE CA.ST.UCHA
DETECTED
PLEASE START SAVE METWITH REPAIRFILE.

IF THERE IS NO VALID REPAIRFILE ; ENTER SAVE MET with ZEROIN=YES
A restoration of the defective charge meters according to procedure SW223 is

to be done.
i....MMN:SW,
PROC, SW223
EY130- 10
A30808-X3074-A473-2-7620
34
EMCYMN
Check hardware
The following commands have to be executed one after the other. The
messages output have to be analyzed. Additionally the start-up messages and
the recovery message output may report units that are faulty.
STAT SSP;
command repetition
STAT CCG;
command repetition
EXECD
STAT SYP;
command repetition
35
EXECD
STAT DLU:DLU=X;
command repetition
EXECD
STAT LTG:LTG=X-X;
command repetition
EXECD
STAT CCNC:UNIT=SILT-X;
command repetition
EXECD
STAT CCNC:UNIT=CCNP-X;
command repetition
EXECD
STAT SN;
command repetition
EXECD
STAT MB;
command repetition
EXECD
EXECD
Hardware status
Are all hardware units in the correct operating state ?
Y h ... 36
N h ... MMN:SYP,
PROC,
PROC:SYP100
36
Symptom saving
When a recovery message is output the TAc is to be informed. If there is a

failure that has not yet been reported, an error report is to be written and all
necessary error symptoms are to be saved according to procedure SW231
(error classification: CP recovery).
h ... MMN:SW,
PROC, SW231
END
A30808-X3074-A473-2-7620
EY130 - 11
EMCYMN
EY130- 12
A30808-X3074-A473-2-7620
3.4
EMCYMN
Manual Initial Start from an APS Save Tape

EY150
3.4.1
Introduction
The following start-up procedure Manual Initial Start from an APS save tape describes
the restoration of switching operations in an network node following total system failure
after which disk access was no longer possible.
The system files which are necessary for the start-up are taken from the save tapes
which were created during the last quarterly save of the APS.
In addition the fixpoint generation on the APS routine save tape is used for the start-up,
since the data of the fixpoint generation are newer than those of the golden generation.
Formatting and initialization of the two background memories, as well as installation of
all the necessary system files by copying from the interval save tapes to background
memory 0, is performed with the aid of the installation monitor (IMON).
Formatting the background memories lengthens the down time by about 20-30 minutes.
Therefore formatting should only be done when faulty sectors are suspected.
All files marked with a duplication identifier are copied automatically onto background
memory 1 in a further procedure step.
Important: Before this procedure is started, all individual call data and LOG files stored
on background memories are to be saved according to procedure EY170.
3.4.1.1
Important user information

Since according to the safeguarding concept a start-up test of the golden generation on
tape is done during each quarterly saving, the golden generation which was saved at
latest is used for the initial start from the save tape.
In order to minimize LOG data postprocessing, an initial start is carried out by using the
fixpoint generation of the latest APS routine saving combined with the code of the golden
generation.

the IOP:AUC module.
TS-011.
The following magnetic tapes are to be held ready
1. Tapes for reading of quarterly saved data
tape (/ continuation tape) of the last APS quarterly saving
2. Tapes for reading of routine saved data
tape of the last APS routine saving
(if at the time of recovery at least one APS routine saving has already been
carried out in the current quarter)
A30808-X3074-A473-2-7620
EY150 - 1
EMCYMN
3. Tapes for reading of other saved data

meter save tape which was created during procedure EY170
(if procedure EY170 was not successful, the actual meter routine save tape
is to be held ready)
log data save tape which was created during procedure EY170
(if procedure EY170 was successful)
tape with file D9.VLRAL which was created in procedur EY170
(if procedure EY170 was successful)
3.4.1.2

3.4.2
Procedure description
Information
Before execution of this procedure, rescue of background memory data is to be

done, according to procedure EY170.
i....EMCYMN,
PROC, EY170
Mount tape in magnetic tape device.

Mount and load quarterly save tape or quarterly save tape (part 1).
The tape created during last APS saving is to be used.
Decision.
Is there a CP113C in use?
Y h ... 6
N h ... 4
Reset BAP-1.
Press RESET-key for BAP-1.
CP113D: Disable bus access for BAP-1.

Locate module PIDAT for BAP-1 in BCMY-0 and BCMY-1 (moloc 145).
On both modules put switch SPB in the ON position (up).
EY150- 2
h ... 7
A30808-X3074-A473-2-7620
EMCYMN
CP113C: Disable bus access for BAP-1.

Locate module DCCMC for BAP-1 (moloc 101).
Put switch S1 in the OFF position (down).
h ... 7
Manual bootstrap - start.

Press BOOT-key for BAP-0.
Important note:
The entries FORMAT;, ; and UTI; according to the next two blocks must be
made immediately after the corresponding requests for entry have been made.
A30808-X3074-A473-2-7620
EY150 - 3
EMCYMN
Manual bootstrap - parameter input.
Important note:
A faulty entry during the manual bootstrap may lead to a situation that no further
entries will be excepted. In this case the procedure is to be continued with
BOOT of BAP-x!
UNIT
STATUS
TEST
********************************************
BAP-0
MASTER
@#####
BAP-1
UNA
@#####
B:CMY-0
ACT
@#####
B:CMY-1
ACT
@#####
CMY-0
@#####
@#####
CMY-1
@#####
@#####
IOC-0
ACT
@#####
IOC-1
@#####
@#####
At least one of the B:CMY units, one of the CMY units and unit IOC-0 must be in
status ACT; otherwise carry out fault clearance according to MMN:CP113.
TO DIAGNOSE MEMORY
TO FORMAT MEMORY
TO CONTINUE
:
:
:
DIAG;
FORMAT;
;ETX
FORMAT;
UNIT
STATUS
TEST
********************************************
BAP-0
MASTER
@#####
BAP-1
UNA
@#####
B:CMY-0
ACT
@#####
B:CMY-1
ACT
@#####
CMY-0
@#####
@#####
CMY-1
@#####
@#####
IOC-0
ACT
@#####
IOC-1
@#####
@#####
TO DIAGNOSE MEMORY
TO FORMAT MEMORY
TO CONTINUE
:
:
:
DIAG;
FORMAT;
;ETX
EY150- 4
A30808-X3074-A473-2-7620
EMCYMN

TO
TO
TO
TO
TO
START APS MANUALLY

STOP INITIAL START
:
:
:
:
:
MANUALLY;
INSTALLATION;
UTILITY;
STOP;
;ETX
UTI;
10
Manual bootstrap - set up installation monitor.

UTILITY-RECOVERY - DEVICE-TYPE TO USE
MDD;/MTD;/MOD;
CP113D
device-no=010D03 marks the physical address of MTD-0
CP113C
device-no=010C03 marks the physical address of MTD-0
MTD;
UTILITY-REC. - LOAD FROM IOC/IOP/DEVICE-NO (HEX):
device-no;
PLEASE ENTER UTILITY-FILE-NAME
The following command must be entered without a semicolon!
SY.INSTALL
IMON: (aps-name, version) STARTED
11
Decision.
Formatting and labeling of both MDD is to be executed only in case of faulty

sectors. To accelerate system availability formatting and labeling of only one
MDD is possible. The second MDD has to be formatted and labeled after
successful start-up.
Are there any disk sectors suspected of being defect?
12
Y h ... 12
N h ... 13
Installation monitor - initialize background memories.
The MDD are formatted to recognize defect sectors and to exclude those
sectors from further use. Formatting takes 20 or more minutes for each MDD.
After formatting labeling is executed.
A30808-X3074-A473-2-7620
EY150 - 5
EMCYMN
CP113D
DEVOUT=010E01 marks the physical address of MDD-0
CP113C
DEVOUT=010C01 marks the physical address of MDD-0
INIT MD:DEVOUT=devout;
VOLIN: FORMATTING DISK ...
IMON: COMMAND INITMD EXECUTED
IMON: ENTER COMMAND
LABEL MD:DEVOUT=devout;
IMON: COMMAND LABELMD EXECUTED
CP113D
CP113C
INIT MD:DEVOUT=devout;
VOLIN: FORMATTING DISK ...
IMON: COMMAND INITMD EXECUTED
IMON: ENTER COMMAND
IMON: ENTER COMMAND
13
h ... 14
Installation monitor - initialize background memories.
CP113D
CP113C
CP113D
CP113C
IMON: ENTER COMMAND
EY150- 6
A30808-X3074-A473-2-7620
14
EMCYMN
Decision.
Y h ... 16
N h ... 15
15
CP113D: Enable bus access for BAP-1.

h ... 17
On both modules put switch SPB in the OFF position (down).
16
CP113C: Enable bus access for BAP-1.

h ... 17
Put switch S1 in the ON position (up).
17
Decision.
Is it necessary to carry out continuation tape handling during the quarterly save
of the APS?
18
Installation monitor - transfer APS quarterly save tape files to MDD-0.
CP113D
CP113C
Y h ... 19
N h ... 18
DEVIN=
010D03 marks the physical address of MTD-0
DEVOUT=
010E01 marks the physical address of MDD-0
DEVIN=
010C03 marks the physical address of MTD-0
DEVOUT=
010C01 marks the physical address of MDD-0
TRANS FILE:DEVIN=devin,DEVOUT=devout,FILECAT=*,OLDGEN=*,
NEWGEN=*;
The following files are stored on the APS save tape (including any continuation tapes):
SY.GENLIST
SY.PSW.Txx1
SY.MSGXREF
SY.INSTALL
SJ.SECDATA
SY.LOADLIB.CA
CG.SA.name-1
SY.LOADLIB.LA
SY.PSW.Txxn
SY.LOADLIB.MA
SY.SEMILIB
SY.SIMP
CG.SA.name-n
SY.TASKLIB
D9.VLRAL
TRANS: FILE file name-1

file name-1
:
:
:
:
:
:
:
:
TRANS: FILE file name-n

file name-n
TRANS: ADDITIONAL TAPES ? (Y/N)
A30808-X3074-A473-2-7620
GEN powerset-inf COPIED TO FILE

GEN powerset-inf
:
:
:
:
:
:
:
:
:
:

GEN powerset-inf
h ... 21
EY150 - 7
EMCYMN
19
CP113D
CP113C
DEVIN=
DEVOUT=
DEVIN=
DEVOUT=
TRANS FILE:DEVIN=devin,DEVOUT=devout,FILECAT=*,OLDGEN=*,
NEWGEN=*;
The following files are stored on the APS save tape (including any continuation tapes):
SY.GENLIST
SY.PSW.Txx1
SY.MSGXREF
SY.INSTALL
SJ.SECDATA
SY.LOADLIB.CA
CG.SA.name-1
SY.LOADLIB.LA
SY.PSW.Txxn
SY.LOADLIB.MA
SY.SEMILIB
TRANS: FILE file name-1

file name-1
:
:
:
:
:
:
:
:
SY.SIMP
CG.SA.name-n
SY.TASKLIB
D9.VLRAL

GEN powerset-inf
:
:
:
:
:
:
:
:
:
:
TRANS: FILE file name-x

file name-x

GEN powerset-inf
TRANS: FILE file name-x+1

file name-x+1

GEN powerset-inf PARTLY
TRANS: PLEASE MOUNT CONTINUATION TAPE TO VSN=SA1TAP THEN TYPE ETX
Rewind and remove APS quarterly save tape (part 1).

Mount and load APS quarterly save tape (part 2).
Press ENTER-key.
file name-x+1

GEN powerset-inf

file name-x+2

GEN powerset-inf
:
:
:
:
:
:
:
:
:
:
:
:
Was another continuation tape requested?
EY150- 8
:
:
:
:
:
:
Y h ... 20
N h ... 21
A30808-X3074-A473-2-7620
20
EMCYMN

TRANS: FILE file name-y
file name-y

GEN powerset-inf PARTLY
TRANS: PLEASE MOUNT CONTINUATION TAPE TO VSN=SA1TAP THEN TYPE ETX
Rewind and remove APS quarterly save tape (part 2).

Press ENTER-key.
TRANS: FILE file name-y
file name-y

GEN powerset-inf
TRANS: FILE file name-y+1

file name-y+1

GEN powerset-inf
:
:
:
:
:
:
:
:
TRANS: FILE file name-n

file name-n
:
:
:
:
:
:
:
:
:
:

GEN powerset-inf
21
b

N
IMON: COMMAND TRANSFILE EXECUTED
IMON: ENTER COMMAND
Rewind tape to the load point manually.
22
h ... 22
Remove tape from magnetic tape device.

Rewind and remove APS quarterly save tape (part x).
23
Decision.
Is file D9.VLRAL administered in the network node and was the saving of this
file according to procedure EY170 successful?
24
Y h ... 24
N h ... 27

Mount and load the save tape with file D9.VLRAL which was created during
procedure EY170.
A30808-X3074-A473-2-7620
EY150 - 9
EMCYMN
25
Installation monitor - transfer file D9.VLRAL to MDD-0.
CP113D
CP113C
b
b
DEVIN=
DEVOUT=
DEVIN=
DEVOUT=
CAN FILE:FILE=D9.VLRAL,DEVOUT=devout,OLDGEN=00;
TRANS FILE:DEVIN=devin,DEVOUT=devout,
FILECAT=D9.VLRAL,
OLDGEN=*,NEWGEN=*;
TRANS: FILE D9.VLRAL
D9.VLRAL

GEN powerset-inf
N
IMON: ENTER COMMAND
26

Rewind and remove save tape with file D9.VLRAL.
27
Decision.
Are statistic meters administered in the network node ?
28
Decision.
Were statistic meters saved according to procedure EY170?
29
Y h ... 28
N h ... 35
Y h ... 29
N h ... 32

Mount and load the meter save tape which was created during procedure
EY170.
EY150- 10
A30808-X3074-A473-2-7620
30
Installation monitor - transfer APS meter save tape files to MDD-0.
CP113D
CP113C
EMCYMN
DEVIN=
DEVOUT=
DEVIN=
DEVOUT=
FILECAT=CA.ST.UCHA
OLDGEN=*,NEWGEN=*;
TRANS: FILE CA.ST.UCHA
CA.ST.UCHA

GEN powerset-inf

IMON: ENTER COMMAND
31

Rewind and remove statistic meter save tape.
32
h ... 35

Mount and load APS routine save tape.
Use the APS routine save tape which was used latest.
33
Installation monitor - transfer APS meter save tape files to MDD-0.
CP113D
CP113C
DEVIN=
DEVOUT=
DEVIN=
DEVOUT=
FILECAT=CA.ST.UCHA
OLDGEN=*,NEWGEN=*;
TRANS: FILE CA.ST.UCHA
CA.ST.UCHA

GEN powerset-inf

IMON: ENTER COMMAND
34

Rewind and remove APS routine save tape.
A30808-X3074-A473-2-7620
EY150 - 11
EMCYMN
35
Installation monitor - display catalog entries.
CP113D
DEVIN=010E01 marks the physical address of MDD-0
CP113C
DEVIN=010C01 marks the physical address of MDD-0
DISP MDDIR:DEVIN=devin;
VOLIN: DIR FOR MDD devin
FILENAME
GEN
SIZE
TYPE
FILEFLAG
----------------------------------------------------------------SY.SLRAM
powerset-inf
@##
PAM
@##
SY.TRANSLOG
powerset-inf
@##
PAM
@##
SY.GENLIST
powerset-inf
@##
PAM
@##
SY.INSTALL
powerset-inf
@##
PAM
@##
SY.LOADLIB.CA
powerset-inf
@##
PAM
@##
SY.LOADLIB.MA
powerset-inf
@##
PAM
@##
SY.PSW.Txx1
powerset-inf
@##
PAM
@##
:
:
:
:
:
:
:
:
:
:
SY.PSW.Txxn
powerset-inf
@##
PAM
@##
SY.LOADLIB.LA
powerset-inf
@##
PAM
@##
SY.TASKLIB
powerset-inf
@##
PAM
@##
SY.SEMILIB
powerset-inf
@##
PAM
@##
SY.SIMP
powerset-inf
@##
PAM
@##
SY.MSGXREF
powerset-inf
@##
PAM
@##
SJ.SECDATA
powerset-inf
@##
PAM
@##
CG.SA.name-1
powerset-inf
@##
PAM
@##
:
:
:
:
:
:
:
:
:
:
CG.SA.name-n
powerset-inf
@##
PAM
@##
CA.ST.UCHA
powerset-inf
@##
PAM
@##
D9.VLRAL
powerset-inf
@##
PAM
@##
FREE SECTORS ON DISK : @##
IMON: COMMAND DISPMDDIR EXECUTED

IMON: ENTER COMMAND
36
Decision.
Was at least one APS routine saving already carried out in the current quarter
up to now?
37
Decision.
38
Y h ... 37
N h ... 82
Y h ... 40
N h ... 38
Reset BAP-1.
EY150- 12
A30808-X3074-A473-2-7620
39
EMCYMN

40
h ... 41

41
h ... 41

Important note:
The entries ; and INS; according to the next two blocks must be made immediately after the corresponding requests for entry have been made.
42
Important note:
entries will be excepted. In this case the procedure is to be continued with the
block 44!
UNIT
STATUS
TEST
********************************************
BAP-0
MASTER
@#####
BAP-1
UNA
@#####
B:CMY-0
ACT
@#####
B:CMY-1
ACT
@#####
CMY-0
@#####
@#####
CMY-1
@#####
@#####
IOC-0
ACT
@#####
IOC-1
@#####
@#####
TO DIAGNOSE MEMORY
TO FORMAT MEMORY
TO CONTINUE
:
:
:
DIAG;
FORMAT;
;ETX
A30808-X3074-A473-2-7620
EY150 - 13
EMCYMN
43

TO
TO
TO
TO
TO
START APS MANUALLY

STOP INITIAL START
:
:
:
:
:
MANUALLY;
INSTALLATION;
UTILITY;
STOP;
;ETX
INS;
44
Manual bootstrap - initiate installation recovery.

@#############
backgen
@#######################
@#############
INSTALLATION RECOV. - LOADING VIA IOC : IOC-0;/IOC1;
IOC-0;
NAME;(8 CHAR)
The generation list displayed above shows the name of the available generation
(backgen).
For the following command take over the generation name from the bottom line
(backgen).
backgen;
Note:
Due to system recovery entries will not be accepted for several minutes!
45
Decision.
46
Y h ... 47
N h ... 46

47
h ... 49

EY150- 14
h ... 49
A30808-X3074-A473-2-7620
48
EMCYMN
is executed.
49
Start file control process (FCP).
Note:
Due to system recovery entries will not be accepted for several minutes! Try to
execute the next command after approximately 3 minutes.
START FCP;
command repetition
:
:
command repetition
50
ACCEPTED
:
:
:
:
:
:
EXECD
h ... 50
Recovery report.
FCP RECOVERY REPORT
OST LOAD DEVICE
-------+----+----------MDD-00 ACT YES
MDD-01 ACT NO
ACTUAL GENERATION
: NAME
CREATION DATE
LAST CREATED
---------+------------------+-----------backgen
@####### @####### YES
FCP UPDATE REPORT

LAST EXECUTED TRANSACTION : DATE = @####### @#######
JOBNO= @###
FILES UPDATED BY LAST TRANSACTION :
FILENAME:
GENERATION:
----------------------------------SY.SEMILIB
backgen
faulty.
51
b
...... information
Important user
Start operation and maintenance processes.

START OM;
command repetition
:
:
command repetition
A30808-X3074-A473-2-7620
ACCEPTED
:
:
:
:
:
:
EXECD
EY150 - 15
EMCYMN
52
b
Start safeguarding processes.

START SFGSW;
command repetition
:
:
command repetition
53
b
ACCEPTED
:
:
:
:
:
:
EXECD
Start control and switching devices process group (CSWD).

START CSWD;
command repetition
:
:
command repetition
54
ACCEPTED
:
:
:
:
:
:
EXECD

Use the APS routine save tape which was used latest.
55
b
Determine generation name on disk.

DISP GEN;
NAME OF CURRENT GENERATION: backgen
LIST OF GENERATIONS:
HISTORY
GENERATION VALIDITY FILES CREATION DATE
SET REFGEN
----------+----------+---------+-----+-----------------+---+-----------BACKUP
backgen
VALID
@##
@####### @####### @## @#######
command repetition
56
b
EXECD
Determine generation name on tape.

DISP GEN:VSN=LOGTAP;
HISTORY
SET REFGEN
----------+----------+---------+-----+-----------------+---+-----------FIXPOINT
fixgen
BLOCKED
@##
@####### @####### @## @#######
command repetition
EY150- 16
EXECD
A30808-X3074-A473-2-7620
57
EMCYMN
Tape to disk transfer of fixpoint generation.
The name of the fixpoint generation on tape (fixgen), which was determined
before, is to be used as parameter value for GEN=fixgen.
TRANS SYFILE:GEN=fixgen,VSN=LOGTAP,REASON=REINST,VERIFY=Y;
command repetition
58
ACCEPTED
Tape to disk transfer of fixpoint generation - continuation.
Y h ... 59
N h ... 60
Was the fixpoint generation fixgen transferred successfully?
59

command repetition
EXECD
TRANSFER RESULT
ERROR
BYTES /
START-/
FILE
GENER.
VSN
STAT
ID NO
RECORDS
END TIME
-+-----------------+--------+------+------+----------+---------+-------S SY.SEMILIB
@####### LOGTAP TR
@### @### @######## @#######
R SY.SEMILIB
@####### SYSVSN DCR
@### @### @######## @#######
S SY.SIMP
@####### LOGTAP TR
@### @### @######## @#######
R SY.SIMP
@####### SYSVSN DCR
@### @### @######## @#######
60
h ... 62

command repetition
NOT EXECD
Additional texts relating to NOT EXECD can be ignored.
61
h ... 82
62
b
Determine generation names on disk.

DISP GEN;
HISTORY
SET REFGEN
----------+----------+---------+-----+-----------------+---+-----------BACKUP
backgen
VALID
@##
@####### @####### @## @#######
FIXPOINT
fixgen
BLOCKED
@##
@####### @####### @## @#######
command repetition
A30808-X3074-A473-2-7620
EXECD
EY150 - 17
EMCYMN
63
Set the fixpoint generation valid.
The name of the fixpoint generation on tape (fixgen), which was determined
MOD GEN:GEN=fixgen,VALIDITY=VALID;
command repetition
64
b
EXECD

DISP GEN;
HISTORY
SET REFGEN
----------+----------+---------+-----+-----------------+---+-----------BACKUP
backgen
VALID
@##
@####### @####### @## @#######
FIXPOINT
fixgen
VALID
@##
@####### @####### @## @#######
command repetition
65
EXECD
Decision.
Is file D9.VLRAL administered in the network node and was the saving of this
file according to procedure EY170 successful?
66
b
Transfer of file D9.VLRAL

DEL FILE:FILE=D9.VLRAL;
command repetition
Y h ... 68
N h ... 66
EXECD
TRANS FILE:FILE=D9.VLRAL,VSNS=LOGTAP;
command repetition
:
:
command repetition
SENDER
RECEIVER
ACCEPTED
:
:
:
:
:
:
EXECD
: @#######
: @#######
START START
FILE IDENTIFICATION
DATA TYPE
BYTES/
/END- /END: FILE
VSN
STATE : ERROR
RECORDS
DATE TIME
-+-----------------+------+-----+-+-----+-+--+----+---------+-----+----S D9.VLRAL
@##### @#### @ @#### @ @# @### @######## @#### @####
R D9.VLRAL
@##### @#### @ @#### @ @# @### @######## @#### @####
67

EY150- 18
A30808-X3074-A473-2-7620
68
EMCYMN
Decision.
69
Y h ... 71
N h ... 69
Reset BAP-1.
70

71
h ... 72

72
h ... 72

Important note:
The entries ; and MAN; according to the next two blocks must be made
immediately after the corresponding requests for entry have been made.
73
Important note:
block 74!
UNIT
STATUS
TEST
********************************************
BAP-0
MASTER
@#####
BAP-1
UNA
@#####
B:CMY-0
ACT
@#####
B:CMY-1
ACT
@#####
CMY-0
@#####
@#####
CMY-1
@#####
@#####
IOC-0
ACT
@#####
IOC-1
@#####
@#####
TO DIAGNOSE MEMORY
TO FORMAT MEMORY
TO CONTINUE
:
:
:
DIAG;
FORMAT;
;ETX
A30808-X3074-A473-2-7620
EY150 - 19
EMCYMN
74

TO
TO
TO
TO
TO
START APS MANUALLY

STOP INITIAL START
:
:
:
:
:
MANUALLY;
INSTALLATION;
UTILITY;
STOP;
;ETX
MAN;
75

@#############
backgen
@#######################
fixgen
@#######################
@#############
IOC-0;
NAME;(8 CHAR)
(fixgen).
(fixgen).
fixgen;
MANUAL RECOVERY
LTG LOADING :
Y;/N;
Y;
Note:
76
Decision.
77
Y h ... 78
N h ... 77

78
h ... 79

EY150- 20
h ... 79
A30808-X3074-A473-2-7620
79
EMCYMN
Decision.
Y h ... 81
N h ... 80
Was the recovery successful?
80
Decision.
The system reactions, described in the next block, do not appear or do only
incompletely appear. Or recovery escalations are started.
81
h ... 82
Recovery report.
Extract of the recovery report.

:
:
SYSTEM - RECOVERY
A30808-X3074-A473-2-7620
:
:
ALARM
:
:
:
:
MMN:SW330-0001
EY150 - 21
EMCYMN
DATE
TIME
PERFORMED LEVEL
PERFORMED ACTION(S)
:
:
:
:
@#######@
@#######@
ISTART2
MEMORY HAS BEEN INITIALIZED
@##############################
: fixgen
APS GENERATION
FCP RECOVERY REPORT

OST LOAD DEVICE
-------+----+----------MDD-00 ACT YES
MDD-01 ACT NO
ACTUAL GENERATION
:
:
#####
#####
#####
#####
#####
#####
#####
#####
: NAME
CREATION DATE
LAST CREATED
---------+------------------+-----------fixgen
@####### @####### YES
:
:
:
:
:
:

:
:
:
:
:
:
END OF LTG LOADING
:
:
:
:

:
:
:
:
#####
#####
#####
#####
#####
#####
#####
#####
:
:
:
:
:
:
:
:

REASON
DATE
TIME
UNIT
EY150- 22
: REQUIRED MANUAL START

@#######################################
: @#######@
: @#######@
: @#####
A30808-X3074-A473-2-7620
EMCYMN
REQUESTED LEVEL
PERFORMED LEVEL
PERFORMED ACTION(S)
: ISTART2
: ISTART2
@##############################
RECOVERY DURATION
: @###@
SECONDS
APS GENERATION
: fixgen
STATISTICS

THRESHOLD
: @###
INTERVAL
: @#### SEC
EXCEPTIONS
==========

DURING RECOVERY
UNIT
---@########
UNIT
---@########
:
:
:
:
UNIT
---@########
:
:
UNIT
---@########
:
:
UNIT
---@########
faulty.
...... information
Important user
CHARGING SAFEGUARDING MESSAGE :

CAUTION : AN APS-GENERATION CHANGE HAS BEEN DETECTED BY THE
CHARGING SAFEGUARDING. FOR THE DURATION OF THE
DATA BASE SYNCHRONIZATION, CHARGING SAFEGUARDING
ACTIONS ARE INHIBITED.
MANUAL ACTIVATION OF THE CHARGING FALLBACK ACTIONS
('SAVE MET : FUNC=FALLBACK') IS REQUIRED FOR THE
FOLLOWING CHARGING TYPE(S) :
STATISTIC CHARGING
82
Decision.
83
h ... 94
Y h ... 85
N h ... 83
Reset BAP-1.
84

A30808-X3074-A473-2-7620
h ... 86
EY150 - 23
EMCYMN
85

h ... 86
86

Important note:
The entries ; and MAN; according to the next two blocks must be made
immediately after the corresponding requests for entry have been made.
87
Important note:
block 88!
UNIT
STATUS
TEST
********************************************
BAP-0
MASTER
@#####
BAP-1
UNA
@#####
B:CMY-0
ACT
@#####
B:CMY-1
ACT
@#####
CMY-0
@#####
@#####
CMY-1
@#####
@#####
IOC-0
ACT
@#####
IOC-1
@#####
@#####
TO DIAGNOSE MEMORY
TO FORMAT MEMORY
TO CONTINUE
:
:
:
DIAG;
FORMAT;
;ETX
88

TO
TO
TO
TO
TO
START APS MANUALLY

STOP INITIAL START
:
:
:
:
:
MANUALLY;
INSTALLATION;
UTILITY;
STOP;
;ETX
MAN;
EY150- 24
A30808-X3074-A473-2-7620
89
EMCYMN

@#############
backgen
@#######################
-----fixgen
@#######################
-----IOC-1 MDD : BZS/AKD AND GENERATION-LIST
@#############
Remark:
IOC-0;
NAME;(8 CHAR)
(backgen).
(backgen).
backgen;
MANUAL RECOVERY
LTG LOADING :
Y;/N;
Y;
Note:
90
Decision.
91
Y h ... 92
N h ... 91

92
h ... 93

A30808-X3074-A473-2-7620
h ... 93
EY150 - 25
EMCYMN
93
Recovery report.

:
:
:
:
SYSTEM - RECOVERY
:
:
:
:
ALARM
DATE
TIME
PERFORMED LEVEL
PERFORMED ACTION(S)
MMN:SW330-0001
:
:
:
:
@#######@
@#######@
ISTART2
@##############################
: backgen
APS GENERATION
FCP RECOVERY REPORT

OST LOAD DEVICE
-------+----+----------MDD-00 ACT YES
MDD-01 ACT NO
ACTUAL GENERATION
:
:
#####
#####
#####
#####
#####
#####
#####
#####
: NAME
CREATION DATE
LAST CREATED
---------+------------------+-----------backgen
@####### @####### YES
:
:
:
:
:
:

:
:
:
:
:
:
END OF LTG LOADING
:
:
:
:

:
:
:
:
#####
#####
#####
#####
#####
#####
#####
#####
:
:
:
:
:
:
:
:
EY150- 26
A30808-X3074-A473-2-7620
REASON
EMCYMN

@#######################################
: @#######@
: @#######@
: @#####
DATE
TIME
UNIT
REQUESTED LEVEL
PERFORMED LEVEL
PERFORMED ACTION(S)
: ISTART2
: ISTART2
@##############################
RECOVERY DURATION
: @###@
SECONDS
APS GENERATION
: backgen
STATISTICS

THRESHOLD
: @###
INTERVAL
: @#### SEC
EXCEPTIONS
==========

DURING RECOVERY
UNIT
---@########
UNIT
---@########
:
:
:
:
UNIT
---@########
:
:
UNIT
---@########
:
:
UNIT
---@########

STATISTIC CHARGING
94
is executed.
95
Display Generation
Note:
DISP GEN;
A30808-X3074-A473-2-7620
EY150 - 27
EMCYMN
96
Decision.
up to now?
97
Y h ... 98
N h ... 97

HISTORY
SET REFGEN
----------+----------+---------+-----+-----------------+---+-----------BACKUP
backgen
VALID
@##
@####### @####### @## @#######
command repetition
98
EXECD
h ... 99

NAME OF CURRENT GENERATION: @#######
HISTORY
SET REFGEN
----------+----------+---------+-----+-----------------+---+-----------BACKUP
backgen
VALID
@##
@####### @####### @## @#######
FIXPOINT
fixgen
VALID
@##
@####### @####### @## @#######
command repetition
99
EXECD
Decision.
Y h ... 100
N h ... 106
Was the saving of LOG files according to procedure EY170 successful?
100

Mount and load the LOG file save tape.
Use the LOG file save tape which was created during procedure EY170.
101
b
Define process-switches.
RESET CFOPT;
command repetition
EXECD
SET CFOPT:ON=15;
command repetition
EY150- 28
EXECD
A30808-X3074-A473-2-7620
102
EMCYMN
Start command file CG.SA.REC51.
Copying of actual LOG files is to be executed.
command repetition
:
:
command repetition
103
...... REC51
MMN:SW, TAB,
EXEC CMDFILE:FILE=CG.SA.REC51;
STARTED
:
:
:
:
:
:
FINISHED

Rewind and remove LOG file save tape.
104
b
RESET CFOPT;
command repetition
105
EXECD
Activation of LOG function is to be executed.
command repetition
:
:
command repetition
106
107
...... REC51
MMN:SW, TAB,
STARTED
:
:
:
:
:
:
FINISHED
Decision.
A successful recovery was carried out by using the fixpoint generation
(fixgen).
h ... 108
A successful recovery was carried out by using the backup generation

(backgen).
h ... 107
Decision.
up to now?
108
Y h ... 112
N h ... 108
Decision.
A30808-X3074-A473-2-7620
Y h ... 110
N h ... 109
EY150 - 29
EMCYMN
109
Update the database manually.
Important note:
All changes to the database, which according to the manually kept
protocol were entered since the creation date of the used save tape, must
again be entered in the old order.
b
110
b
h ... 129
All entries should be done according to the note.

RESET CFOPT;
command repetition
EXECD
SET CFOPT:ON=16;
command repetition
111
EXECD
Using the following command, the storage of administrative records is

suppressed. Thus a multiple charging of subscriber facilities during the following
updating of database is avoided.
ACT IAOPT:BLBUFR=ADMREC;
DANGEROUS COMMAND ACTIAOPT READY TO EXECUTE<
;
command repetition
EXECD
Updating database is to be executed.
......MMN:SW,
TAB,
REC51
command repetition
:
:
command repetition
STARTED
:
:
:
:
:
:
FINISHED
Before updating of database was started, the storage of administrative records

was suppressed. This suppression is canceled again using the following
command.
CAN IAOPT:BLBUFR=ADMREC;
DANGEROUS COMMAND CANIAOPT READY TO EXECUTE<
;
command repetition
EY150- 30
EXECD
h ... 129
A30808-X3074-A473-2-7620
112
EMCYMN

Use the tape which was created during the last APS routine saving.
113
b
RESET CFOPT;
command repetition
114
EXECD
Copying of actual LOG files is to be executed.
command repetition
:
:
command repetition
115
...... REC56
MMN:SW, TAB,
STARTED
:
:
:
:
:
:
FINISHED

116
b
RESET CFOPT;
command repetition
117
EXECD
Activation of LOG function is to be executed.
...... REC51
MMN:SW, TAB,
command repetition
:
:
command repetition
A30808-X3074-A473-2-7620
STARTED
:
:
:
:
:
:
FINISHED
EY150 - 31
EMCYMN
118
b
RESET CFOPT;
command repetition
EXECD
Which routine saving was the last one which was executed in this quarter?
h ... 119
h ... 120
h ... 121
h ... 122
h ... 123
The 1st routine saving was the last one in the current quarter.
119
b
SET CFOPT:ON=12;
command repetition
120
b
h ... 124
EXECD
h ... 124
EXECD
h ... 124
EXECD
h ... 124
SET CFOPT:ON=14;
SET CFOPT:ON=15;
command repetition
123
b
EXECD
SET CFOPT:ON=13;
command repetition
122
b
h ... 124
command repetition
121
b
EXECD
SET CFOPT:ON=16;
command repetition
EY150- 32
A30808-X3074-A473-2-7620
124
EMCYMN

;
command repetition
EXECD
...... REC52
MMN:SW, TAB,
command repetition
:
:
command repetition
STARTED
:
:
:
:
:
:
FINISHED

command.
;
command repetition
125
EXECD
Decision.
126
Y h ... 127
N h ... 126
Update the database manually.
Important note:
All changes to the database, which according to the manually kept
protocol were entered since the creation date of the used save tape, must
again be entered in the old order.
All entries should be done according to the note.
A30808-X3074-A473-2-7620
h ... 129
EY150 - 33
EMCYMN
127
b
RESET CFOPT;
command repetition
EXECD
SET CFOPT:ON=16;
command repetition
128
EXECD

;
command repetition
EXECD
......MMN:SW,
TAB,
REC51
command repetition
:
:
command repetition
STARTED
:
:
:
:
:
:
FINISHED

command.
;
command repetition
129
b
EXECD
h ... 129
RESET CFOPT;
command repetition
EY150- 34
EXECD
A30808-X3074-A473-2-7620
130
EMCYMN
Postprocessing after recovery is to be executed.
command repetition
:
:
command repetition
131
b
...... REC53
MMN:SW, TAB,
STARTED
:
:
:
:
:
:
FINISHED
Display alarm status.

command repetition
OBJECT =
ALTYPE =
PABCAUSE=
ALARM-ID:
EXECD
RECOV
ALPRIO = MAJOR
ALSTAT = NP MSGNO = msgno
@#######################
@#################################################
CLASS=ISTART
NO (MORE) DATA FOR DISPLAY AVAILABLE.
The following block is to be executed with the determined message number

(msgno).
132
b
Reset alarm.
command repetition
133
EXECD
Decision.
up to now?
134
b
Y h ... 135
N h ... 134

DISP GEN;
HISTORY
SET REFGEN
----------+----------+---------+-----+-----------------+---+-----------BACKUP
backgen
VALID
@##
@####### @####### @## @#######
command repetition
A30808-X3074-A473-2-7620
EXECD
h ... 140
EY150 - 35
EMCYMN
135
Decision.
Was a successful recovery carried out by using the fixpoint generation
(fixgen)?
136
b
Y h ... 138
N h ... 136

DISP GEN;
HISTORY
SET REFGEN
----------+----------+---------+-----+-----------------+---+-----------BACKUP
backgen
VALID
@##
@####### @####### @## @#######
FIXPOINT
fixgen
VALID
@##
@####### @####### @## @#######
command repetition
137
EXECD
Delete fixpoint generation.
The name of the fixpoint generation on disk (fixgen), which was determined
CAN GEN:GEN=fixgen;
DANGEROUS COMMAND CANGEN READY TO EXECUTE<
;
command repetition
HISTORY
SET REFGEN
----------+----------+---------+-----+-----------------+---+-----------BACKUP
backgen
VALID
@##
@####### @####### @## @#######
FIXPOINT
fixgen
VALID
@##
@####### @####### @## @#######
DO YOU REALLY WANT TO CANCEL GENERATION ?
PLEASE ENTER
(YES: +/NO: -)<
+
LIST OF ERASED FILES OF THE FORMER GENERATION :
fixgen
FILE:
---------------------------------------------------------------------SY.SEMILIB
SY.SIMP
command repetition
EY150- 36
EXECD
h ... 140
A30808-X3074-A473-2-7620
138
b
EMCYMN

DISP GEN;
NAME OF CURRENT GENERATION: fixgen
HISTORY
SET REFGEN
----------+----------+---------+-----+-----------------+---+-----------BACKUP
backgen
VALID
@##
@####### @####### @## @#######
FIXPOINT
fixgen
VALID
@##
@####### @####### @## @#######
command repetition
139
EXECD
Delete backup generation.
The name of the backup generation on disk (backgen), which was determined
before, is to be used as parameter value for GEN=backgen.
CAN GEN:GEN=backgen;
;
command repetition
NAME OF CURRENT GENERATION: fixgen
HISTORY
SET REFGEN
----------+----------+---------+-----+-----------------+---+-----------BACKUP
backgen
VALID
@##
@####### @####### @## @#######
FIXPOINT
fixgen
VALID
@##
@####### @####### @## @#######
PLEASE ENTER
(YES: +/NO: -)<
+
backgen
FILE:
---------------------------------------------------------------------SY.SEMILIB
SY.SIMP
command repetition
140
b
141
EXECD
List traffic measurement jobs.

DISP TRAMORD:STATUS=ALL;
Decision.
Were traffic measurement jobs running at the time the APS quarterly save tape
used in this procedure was generated?
A30808-X3074-A473-2-7620
Y h ... 142
N h ... 143
EY150 - 37
EMCYMN
142
List traffic measurement jobs - continuation.

LIST OF STARTED TRAFFIC MEASUREMENT ORDERS
JOB COMMAND
B:BEGIN
INTERVAL
PER FILENAME
NO
AND ADDITIONAL DATA
E:END
IOD
----+--------------------------+----------+-----------+---+----------------no
code
@ @############## @#@####### @########## @## name
:
:
:
:
:
:
:
:
:
:
:
:
:
:
no
code
@ @############## @#@####### @########## @## name
no
code
@ @############## @#@####### @########## @## @##########
:
:
:
:
:
:
:
:
:
:
:
:
:
:
no
code
@ @############## @#@####### @########## @## @##########
----command repetition
EXECD
Remark:
One, more or all mask entry (entries) between broken lines is (are) present.
143
h ... 144

command repetition
144
EXECD
h ... 146
Terminate traffic measurement jobs.
The following command must be executed for all jobs which were determined in
the foregoing block.
The values (no and code), which were determined before, are to be used as
parameter values for JN=no and CMDCOD=code.
CAN JOB:JN=no,CMDCOD=code;
command repetition
145
b
EXECD

DISP TRAMORD:STATUS=ALL;
command repetition
146
b
EXECD

DISP MUSMORD:STATUS=ALL;
EY150- 38
A30808-X3074-A473-2-7620
147
EMCYMN
Decision.
Were traffic measurement jobs running at the time the APS quarterly save tape
used in this procedure was generated?
148
Y h ... 148
N h ... 149

LIST OF STARTED TRAFFIC MEASUREMENT ORDERS
JOB COMMAND
B:BEGIN
INTERVAL
PER FILENAME
NO
AND ADDITIONAL DATA
E:END
IOD
----+--------------------------+----------+-----------+---+----------------no
code
@ @############## @#@####### @########## @## name
:
:
:
:
:
:
:
:
:
:
:
:
:
:
no
code
@ @############## @#@####### @########## @## name
no
code
@ @############## @#@####### @########## @## @##########
:
:
:
:
:
:
:
:
:
:
:
:
:
:
no
code
@ @############## @#@####### @########## @## @##########
----command repetition
EXECD
Remark:
149
h ... 150

command repetition
150
EXECD
h ... 152
Terminate traffic measurement jobs.
The following command must be executed for all jobs which were determined in
the foregoing block.
The values (no and code), which were determined before, are to be used as
parameter values for JN=no and CMDCOD=code.
CAN JOB:JN=no,CMDCOD=code;
command repetition
151
b
EXECD

DISP MUSMORD:STATUS=ALL;
command repetition
A30808-X3074-A473-2-7620
EXECD
EY150 - 39
EMCYMN
152
b
Activate meter fallback measures.

SAVE MET:FUNC=FALLBACK;
command repetition
:
:
command repetition
153
ACCEPTED
:
:
:
:
:
:
EXECD
Execution of procedure SW210.
Important note:
The APS quarterly saving, which should be the next according to the
schedule is to be placed on an earlier date and must be executed immediately!
h ...MMN:SW,
PROC, SW210
154
End of procedure.
END
EY150- 40
A30808-X3074-A473-2-7620
3.5
EMCYMN
Rescue of Background Memory Data

EY170
3.5.1
Introduction
A total system failure, after which a manual initial start from a background memory was
not successful, makes it necessary to perform a manual initial start from an APS save
tape (procedure EY150).
Procedure EY150 includes formatting of the background memories which causes disk
contents to be lost.
The procedure is to be executed before procedure EY150 and saves the contents of files
IA. and D9.VLRAL (if available), LOG files and history data on tape.
This is done in the installation mode.
Execution of the procedure is described for use with system half 1 (IOC-0/ MDD-0).
With slight modifications, the procedure can be executed with system half 1. In this case
the output messages may appear on OMT-1 (depending on actual system configuration).
If the responsible command files cannot be executed due to system configuration, the
file contents should be saved manually on tape (if possible).
The following magnetic tapes are to be held ready:
3.5.1.1
Important user information

In this procedure only the positive reactions are described for all actions. When a negative reaction occurs, which is caused by a main memory mutilation, this procedure
should be aborted and is to be considered inexecutable.

the IOP:AUC module.
TS-011.
The following magnetic tapes are to be held ready
1. Tapes for saving of data call records
1
large magnetic tape with write ring for saving the file IA.ICAMA
large magnetic tape with write ring for saving the file IA.ICMCR
small magnetic tape with write ring for saving the file IA.ICINA
2. Tapes for saving of logging data

1
medium-sized magnetic tape with write ring for saving the LOG data
3. Tapes for saving history data

1
A30808-X3074-A473-2-7620
large magnetic tape with write ring for saving the history files
EY170 - 1
EMCYMN
4. Tapes for saving of HLR specific data

1
3.5.2
small-sized magnetic tape with write ring for saving the file D9.VLRAL
Decision.
Y h ... 4
N h ... 2
Reset BAP-1.

h ... 5

h ... 5

Important note:
The entries ; and INS; according to the next two blocks must be made immediately after the corresponding requests for entry have been made.
EY170- 2
A30808-X3074-A473-2-7620
EMCYMN
Important note:
block 5!
UNIT
STATUS
TEST
********************************************
BAP-0
MASTER
@#####
BAP-1
UNA
@#####
B:CMY-0
@#####
@#####
B:CMY-1
@#####
@#####
CMY-0
@#####
@#####
CMY-1
@#####
@#####
IOC-0
@#####
@#####
IOC-1
@#####
@#####
TO DIAGNOSE MEMORY
TO FORMAT MEMORY
TO CONTINUE
:
:
:
DIAG;
FORMAT;
;ETX

TO
TO
TO
TO
TO
START APS MANUALLY

STOP INITIAL START
:
:
:
:
:
MANUALLY;
INSTALLATION;
UTILITY;
STOP;
;ETX
INS;
A30808-X3074-A473-2-7620
EY170 - 3
EMCYMN

@#############
gen-x
@#######################
:
:
:
:
gen-n
@#######################
@#############
gen-x
@#######################
:
:
:
:
gen-n
@#######################
IOC-0;
NAME;(8 CHAR)
The generation list displayed above shows the names of the available generations (gen-x to gen-n).
(gen-n).
If recovery is not successful, the procedure can be repeated with the other
generations.
gen-n;
Note:
is executed.
10
b
Start file control process (FCP).

START FCP;
command repetition
:
:
command repetition
EY170- 4
ACCEPTED
:
:
:
:
:
:
EXECD
h ... 11
A30808-X3074-A473-2-7620
11
EMCYMN
Recovery report.
FCP RECOVERY REPORT
OST LOAD DEVICE
-------+----+----------MDD-00 ACT YES
MDD-01 ACT NO
ACTUAL GENERATION
: NAME
CREATION DATE
LAST CREATED
---------+------------------+-----------actgen
@####### @####### YES
FCP UPDATE REPORT

JOBNO= @###
FILENAME:
GENERATION:
----------------------------------SY.SEMILIB
gen-n
:
:
:
:
:
:
:
:
DEFAULT OUTPUT!
DATATYPE/MSGRPNO: @###
CAUSE: DLL NOT RUNNING
:
:
:
:
:
:
:
:
FORMAT: @####
faulty.
12
b

START OM;
command repetition
:
:
command repetition
13
b
...... information
Important user
ACCEPTED
:
:
:
:
:
:
EXECD

START SFGSW;
command repetition
:
:
command repetition
A30808-X3074-A473-2-7620
ACCEPTED
:
:
:
:
:
:
EXECD
EY170 - 5
EMCYMN
14
b
Start process ICOM1.

START PROCESS:NAME=ICOM1;
command repetition
:
:
command repetition
15
b
ACCEPTED
:
:
:
:
:
:
EXECD
Start process MMILF.

START PROCESS:NAME=MMILF;
command repetition
:
:
command repetition
16
ACCEPTED
:
:
:
:
:
:
EXECD
Decision.
Y h ... 18
N h ... 17
17

h ... 19
18

h ... 19
19
b
Display catalog entries.

DISP FILE;
command repetition
EXECD
@################## @#############################
USED SPACE : @###### PAGES FOR @### FILES
FILE
GEN
SIZE VSN000
VSN001
CLASS TYPE
-----------------+--------+------+-------------+-------------+-----+---filename
@####### @##### @############ @############ @### @###
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
filename
@####### @##### @############ @############ @### @###
The catalog display above shows all files administered in the network node. In
the following blocks some important files have to be saved with help of
command files. It is to be evaluated whether these files are administered in the
network node.
EY170- 6
A30808-X3074-A473-2-7620
20
EMCYMN
Decision.
Y h ... 21
N h ... 27
Was file CA.ST.UCHA determined in the catalog display ?
21

Mount and load for saving of file CA.ST.UCHA.
A medium-sized magnetic tape with write ring, overwritable or empty, is to be

used.
22
b
RESET CFOPT;
command repetition
23
EXECD
Saving of file CA.ST.UCHA is to be executed.
command repetition
:
:
command repetition
24
...... REC71
MMN:SW, TAB,
STARTED
:
:
:
:
:
:
FINISHED

Rewind and remove CA.ST.UCHA tape.
Was the file transferred?
25
Remove tape from magnetic tape device - continuation.

The tape is to be marked as IA.ICAMA data record tape and is to be stored for
further use.
26
Y h ... 25
N h ... 26
h ... 27

The tape is to be held ready for other use.
27
Decision.
Was file IA.ICAMA determined in the catalog display ?
A30808-X3074-A473-2-7620
Y h ... 28
N h ... 35
EY170 - 7
EMCYMN
28

Mount and load for saving of file IA.ICAMA.
A large magnetic tape with write ring, overwritable or empty, is to be used.
Y h ... 29
N h ... 30
Is the file IA.ICAMA protected by a password against unauthorized reading?
29
b
Enable read access.

ENTR FILEPSW;
PLEASE ENTER FILEPASSWORD
<
file-password
command repetition
30
b
EXECD
RESET CFOPT;
command repetition
31
EXECD
Saving of file IA.ICAMA is to be executed.
command repetition
:
:
command repetition
32
......MMN:SW,
TAB,
REC72
STARTED
:
:
:
:
:
:
FINISHED

Rewind and remove IA.ICAMA data record tape.
Y h ... 33
N h ... 34
33

The tape is to be marked as IA.ICAMA data record tape and is to be stored for
further use.
34
h ... 35

EY170- 8
A30808-X3074-A473-2-7620
35
EMCYMN
Decision.
The file IA.ICMCR contains the mobile call records and it is important to save
the file in the most actual state. Therefore saving via FTAM is to prefer (if this is
possible).
Y h ... 36
N h ... 43
Was the file IA.ICMCR determined in the catalog display?
36

Mount and load for saving of file IA.ICMCR .

Is the file IC.MCR protected by a password against unauthorized reading?
37
b
Y h ... 37
N h ... 38
Enable read access.

ENTR FILEPSW;
<
file-password
command repetition
38
b
EXECD
RESET CFOPT;
command repetition
39
EXECD
Saving of file IA.ICMCR is to be executed.
command repetition
:
:
command repetition
40
...... REC75
MMN:SW, TAB,
STARTED
:
:
:
:
:
:
FINISHED

Rewind and remove IA.ICMCR data record tape.
A30808-X3074-A473-2-7620
Y h ... 41
N h ... 42
EY170 - 9
EMCYMN
41

The tape is to be marked as IA.ICMCR data record tape and is to be stored for
further use.
42
h ... 43

43
Decision.
Y h ... 44
N h ... 51
Was the file IA.ICINA determined in the catalog display?
44

Mount and load for saving of file IA.ICINA .
A small magnetic tape with write ring, overwritable or empty, is to be used.
Y h ... 45
N h ... 46
Is the file IC.INA protected by a password against unauthorized reading?
45
b
Enable read access.

ENTR FILEPSW;
<
file-password
command repetition
46
b
EXECD
RESET CFOPT;
command repetition
47
EXECD
Saving of file IA.ICINA is to be executed.
......MMN:SW,
TAB,
REC76
command repetition
:
:
command repetition
EY170- 10
STARTED
:
:
:
:
:
:
FINISHED
A30808-X3074-A473-2-7620
48
EMCYMN

Rewind and remove IA.ICINA data record tape.
Y h ... 49
N h ... 50
49

The tape is to be marked as IA.ICINA data record tape and is to be stored for
further use.
50
h ... 51

51
Decision.
Y h ... 52
N h ... 58
Were LOG files determined in the catalog display?
52

Mount and load for LOG data saving.
A small-sized magnetic tape with write ring, overwritable or empty, is to be used.
53
b
RESET CFOPT;
command repetition
54
EXECD
LOG data saving is to be executed.
command repetition
:
:
command repetition
55
...... REC73
MMN:SW, TAB,
STARTED
:
:
:
:
:
:
FINISHED

Rewind and remove LOG data save tape.
Were LOG data files transferred?
A30808-X3074-A473-2-7620
Y h ... 56
N h ... 57
EY170 - 11
EMCYMN
56

The tape is to be marked as LOG data save tape and to be kept for use when
executing procedure EY150 following completion of this procedure.
57
h ... 58

58
Decision.
Y h ... 59
N h ... 65
Were history files (SG.-, HF.-, TM.-files) determined in the catalog display?
59

Mount and load for history files saving.
60
b
RESET CFOPT;
command repetition
61
EXECD
History files saving is to be executed.
command repetition
:
:
command repetition
62
......MMN:SW,
TAB,
REC74
STARTED
:
:
:
:
:
:
FINISHED

Rewind and remove history files save tape.
Y h ... 63
N h ... 64
Were history files transferred?
63

The tape is to be marked as the save tape of the faulty generation and sent to
the diagnostic center (TAC 3).
64
h ... 65

EY170- 12
A30808-X3074-A473-2-7620
65
EMCYMN
Decision.
Y h ... 66
N h ... 71
Was the file D9.VLRAL determined in the catalog display?
66

Mount and load for D9.VLRAL data saving.
A small-sized magnetic tape with write ring, overwritable or empty, is to be used.
67
D9.VLRAL saving is to be executed.
command repetition
:
:
command repetition
68
...... REC77
MMN:SW, TAB,
STARTED
:
:
:
:
:
:
FINISHED

Rewind and remove meter file save tape.
Was file D9.VLRAL transferred?
69

The tape is to be marked as D9.VLRAL save tape and to be kept for use when
executing procedure EY150 following completion of this procedure.
70
Y h ... 69
N h ... 70
h ... 71

71
Execute EMCYMN procedure EY150.
Recovery from the APS quarterly save tape is to be executed in accordance with EMCYMN procedure EY150.
h ... EMCYMN,
PROC, EY150
72
End of procedure.
END
A30808-X3074-A473-2-7620
EY170 - 13
EMCYMN
EY170- 14
A30808-X3074-A473-2-7620
3.6
EMCYMN
Initial Start (FALLBACK GENERATION)

EY190
3.6.1
General information.
This procedure describes the restoration of switching operation using the FALLBACK
GENERATION(S), which is (are) stored in duplicate on background memories.
Manual recovery (FALLBACK GENERATION) is to be used,
if start-up attempts from the valid generation done according to procedure SW110
or EY130 were not successful
if after start-up from the valid generation no or only restricted switching operation is
possible.
Automatic recovery (FALLBACK GENERATION) is started by the system itself

(recovery escalation) in some fault situations. In this case manual postprocessing is to
be done using this procedure.
x large magnetic tapes with write ring for saving the mutilated APS generation
x large magnetic tapes with write ring for saving the APS generation
1 large magnetic tape with write ring for saving fixpoints, LOG data and meter files
1 large magnetic tape with write ring for saving the history files
2 large magnetic tapes with write ring for saving the file IA.ICAMA
2 large magnetic tapes with write ring for saving the file IA.ICMCR
2 large magnetic tapes with write ring for saving the file IA.ICOME
2 large magnetic tapes with write ring for saving the file IA.ICITR
2 large magnetic tapes with write ring for saving the file IA.ICMIR
2 large magnetic tapes with write ring for saving the file IA.ICINA

the IOP:AUC module.
TS-011.
A30808-X3074-A473-2-7620
EY190 - 1
EMCYMN
3.6.2

Decision.
How is the procedure to be used?
2
b
Manual recovery (FALLBACK GENERATION) is to be done.
h ... 2
Manual postprocessing after automatic recovery (FALLBACK GENERATION) is to be done.
h ... 3
Initiate ISTART2G.
RECOV SYSTEM:LEVEL=ISTART2G;
DANGEROUS COMMAND RECOVSYSTEM READY TO EXECUTE<
EY190- 2
A30808-X3074-A473-2-7620
EMCYMN
Recovery report.
:
:
:
:
:
:
:
:
FCP RECOVERY REPORT

OST LOAD DEVICE
-------+----+----------MDD-00 ACT YES
MDD-01 ACT NO
ACTUAL GENERATION
:
:
: NAME
CREATION DATE
LAST CREATED
---------+------------------+-----------@####### @####### @####### @##
:
:
:
:
:
:
SYSTEM - RECOVERY
DATE
TIME
PERFORMED LEVEL
PERFORMED ACTION(S)
ALARM
APS GENERATION
:
:
MMN:EY190-0000
:
:
:
:
@#######@
@#######@
ISTART2G
@##############################
: @#######
:
:
:
:
:
:
FCP UPDATE REPORT

JOBNO= @###
FILENAME:
GENERATION:
----------------------------------@################
@#######
:
:
:
:
:
:
:
:

:
:
:
:
:
:
#####
#####
#####
#####
#####
#####
:
:

:
:
:
:
:
:
A30808-X3074-A473-2-7620
#####
#####
#####
#####
#####
#####
EY190 - 3
EMCYMN
#####
#####

END OF LTG LOADING
#####
#####
faulty.
......General
information.
Recovery report 2.
:
:
:
:
:
:
:
:

REASON
: @################################
@#######################################
: @#######@
: @#######@
: @#####
DATE
TIME
UNIT
REQUESTED LEVEL
PERFORMED LEVEL
PERFORMED ACTION(S)
: ISTART2G
: ISTART2G
@##############################
RECOVERY DURATION
: @###@
SECONDS
APS GENERATION
: @#######
STATISTICS

THRESHOLD
: @###
INTERVAL
: @#### SEC
EXCEPTIONS
==========

DURING RECOVERY
UNIT
---@########
UNIT
---@########
UNIT
---@########
UNIT
---@########
UNIT
---@########
is executed.
EY190- 4
A30808-X3074-A473-2-7620
6
b
EMCYMN

command repetition
EXECD
OBJECT =
ALTYPE =
PABCAUSE=
ALARM-ID:
@####### ALPRIO = @####### ALSTAT = @# MSGNO = @####

@#######################
@#################################################
@#############################################################
:
:
:
:
:
:
:
:
OBJECT =
ALTYPE =
PABCAUSE=
ALARM-ID:
RECOV
ALPRIO = CRITICAL ALSTAT = NP MSGNO = @####
@#######################
@#################################################
CLASS=ISTART2G
:
:
:
:
:
:
:
:
OBJECT =
ALTYPE =
PABCAUSE=
ALARM-ID:
NO (MORE)

@#######################
@#################################################
@#############################################################
DATA FOR DISPLAY AVAILABLE.
h ... 7
Search alarm.
This block is to be executed with all message numbers of category

ALPRIO=CRITICAL.
SRCH ALARM:MSGNO=msgno;
:
:
SYSTEM - RECOVERY
:
:
:
:
ALARM
DATE
TIME
PERFORMED LEVEL
PERFORMED ACTION(S)
APS GENERATION
:
:
:
:
MMN:@#########
:
:
:
:
@#######@
@#######@
ISTART2G
@##############################
: @#######
:
:
:
:
:
:
command repetition
EXECD
A30808-X3074-A473-2-7620
EY190 - 5
EMCYMN
Delete alarm.
This block is to be executed with all message numbers assigned to the

ISTART2G message.
command repetition
EXECD
Decision.
Y h ... 10
N h ... 11
Are statistic meters administered?
10
b
Cancel time job for meter routine saving.

DISP CFTJOB;
command repetition
EXECD
LIST OF TIME CONTROLLED COFIP JOBS:

JN
FILE
VSN
CHOL
DATE
TIME
WDCAT
PER
-----+------------------+-------+-----+---------+-----+-------+--------@### CG.SA.METAP
LOGTAP @##
@####### @#### @###### @#######
If a job number is determined for the meter routine saving time job
(FILE=CG.SA.METAP) it must be used in the following cancel command as
value for jobnumber.
CAN JOB:JN=jobnumber,CMDCOD=EXECCMDFILE;
command repetition
EY190- 6
EXECD
A30808-X3074-A473-2-7620
11
b
EMCYMN
List generations.
DISP GEN;
command repetition
HISTORY
SET REFGEN
----------+----------+---------+-----+-----------------+---+-----------@######### actgen
@######## @##
@####### @####### @## @#######
@######### backgen
@######## @##
@####### @####### @## @#######
@######### oldgold
@######## @##
@####### @####### @## @#######
command repetition
EXECD
Which of the generations listed above is the current generation (compare NAME
OF CURRENT GENERATION and LIST OF GENERATIONS)? This is the
generation which was successfully used by the preceding ISTART2G.
The NAME OF THE CURRENT GENERATION is identical to the entry in the
1st line of LIST OF GENERATIONS.
Fallback to generation actgen, which was active before the ISTART2G was
carried out, was successful.
h ... 12

2nd line of LIST OF GENERATIONS.
Fallback to the last backup generation backgen, i.e. either backup generation
of the last routine saving or the golden generation of the last quarterly
saving, was successful.
h ... 21

3rd line of LIST OF GENERATIONS.
Fallback to the last backup generation backgen was not successful
but
fallback to the last backup generation oldgold, i.e. golden generation of the
last quarterly saving, was successful.
h ... EMCYMN,
PROC, EY191
12
Information.
If an APS generation change has been detected and therefore the fallback flag
has been set, the CHARGING SAFEGUARDING MESSAGE is output in the
following cases:
- every 10 minutes as long as charging safeguarding actions are inhibited.
- after each action for meter saving.
STATISTIC CHARGING
A30808-X3074-A473-2-7620
EY190 - 7
EMCYMN
13
Decision.
Y h ... 14
N h ... 16
14
b
Activation of the charging fallback actions.

command repetition
:
:
command repetition
15
ACCEPTED
:
:
:
:
:
:
EXECD

The tape is to be marked as current APS routine save tape and to be held ready
for further use.
16
i....MMN:SW,
Symptom saving is to be executed according to procedure SW231.

Continue here, after execution of MMN:SW, procedure SW231
PROC, SW231
17
Decision.
Y h ... 18
N h ... 52
18

Mount and load the tape for APS routine saving.
Mount and load the APS routine save tape which was removed beforehand.
19
Start command file CG.SA.METAP.

Meter routine saving is to be executed.
Important note:
The starting time of the command file must not be within a time interval of the
administered automatic meter saving.
Find out the administration with MML command DISP METSAV and delay the
start of the command file if necessary.
......MMN:SW,
TAB, METAP
EXEC CMDFILE:FILE=CG.SA.METAP;
command repetition
:
:
command repetition
EY190- 8
STARTED
:
:
:
:
:
:
FINISHED
A30808-X3074-A473-2-7620
20
EMCYMN
Start command file CG.SA.METAP by a periodical time job.

Meter routine saving is to be executed.
Important note:
Find out the administration with MML command DISP METSAV and adjust the
starting time of the command file (TIME=..-..) accordingly.
EXEC CMDFILE:FILE=CG.SA.METAP,DATE=yy-mm-dd,TIME=hh-mm,
PER=YES;
command repetition
...... TAB,
MMN:SW,
METAP
ACCEPTED
The APS routine save tape remains permanently mounted in the magnetic tape
device.
If the magnetic tape device is shortly needed for another purpose, the APS
routine save tape must be removed (if necessary the time job for meter routine
saving is to be cancelled). However, after the other tape job is finished, the APS
routine save tape must be mounted again (if necessary the time job for meter
routine saving is to be restarted).
21
h ... 52
Information.
following cases:
STATISTIC CHARGING
22
b
Deactivate LOG function.

RSET LOG;
DANGEROUS COMMAND RSETLOG READY TO EXECUTE<
;
LOG-FUNCTION MESSAGE:
LOG-FILE(S)
READY FOR USE: @################ @################
MASTER-LOG-FILE READY FOR USE: @################
command repetition
EXECD
A30808-X3074-A473-2-7620
EY190 - 9
EMCYMN
23
Blocking of memory entries.

regeneration of LOG data is avoided.
;
command repetition
24
b
EXECD
Define process- switches.

RESET CFOPT;
command repetition
25
EXECD
Regeneration of LOG data is to be executed.
command repetition
:
:
command repetition
26
......MMN:SW,
TAB, REC91
STARTED
:
:
:
:
:
:
FINISHED
Remove the blocking of memory entries.
Before the regeneration of LOG data was started, the storage of administrative
records was suppressed. This suppression is canceled again using the following
command.
;
command repetition
27
EXECD
Decision.
28
Y h ... 28
N h ... 31
Information.
During account suspension, no begin and end meter readings are displayed
when subscribers are created or canceled.
EY190- 10
A30808-X3074-A473-2-7620
29
b

command repetition
:
:
command repetition
30
EMCYMN
ACCEPTED
:
:
:
:
:
:
EXECD

The tape is to be marked as APS routine save tape and to be stored under date
of save.
31
b
List generations.
DISP GEN;
command repetition
HISTORY
SET REFGEN
----------+----------+---------+-----+-----------------+---+-----------@######### actgen
@######## @##
@####### @####### @## @#######
@######### @#######
@######## @##
@####### @####### @## @#######
@######### @#######
@######## @##
@####### @####### @## @#######
command repetition
EXECD
The entry in the 1st line of the column GENERATION is the name of the mutilated generation actgen, i.e. the generation which was active before fallback.
Important:
The value of actgen should be written down, since it is needed to complete
MML commands in the following.
32

Mount and load the tape for saving the mutilated generation.
33
b
Initialize save tape of the mutilated generation.

INIT MT:MTD=00,CD=EBC,DENS=6250,VSN=GE1TAP;
command repetition
:
:
command repetition
A30808-X3074-A473-2-7620
ACCEPTED
:
:
:
:
:
:
EXECD
EY190 - 11
EMCYMN
34
Tape saving the mutilated generation.
Important note:
The number and size of the files which are to be transferred to magnetic tape
may require one or several continuation tapes.
If end of tape is reached before the generation is transferred completely (once
or several times), the following messages are displayed:
COPY GEN:OUTPUT=GEN,VERIFY=NO,VSN=GE1TAP,GEN=actgen,
REWIND=YES;
PLEASE MOUNT CONTINUATION TAPE TO VSN = GExTAP
(VSN=GExTAP with x=1, 2, 3, ....., n)

Each time the above messages are displayed, the magnetic tape device is to be
unloaded, the tape is to be removed, the continuation tape is to be mounted and
the tape device is to be loaded.
After that, the following two commands are to be entered manually:
INIT MT:CD=EBC,DENS=6250,VSN=GE(y)TAP,MTD=00; (with y=2, 3, .....,n)
MOUNT TAPE:DEV=MTD-00;
The value for actgen which was determined and written down according to the
last generation list printout, is to be used in the following command
(GEN=actgen).
COPY GEN:OUTPUT=GEN,VERIFY=NO,VSN=GE1TAP,GEN=actgen,REWIN
D=YES;
command repetition
:
:
ACCEPTED
:
:
:
:
:
:
Was continuation tape handling requested by the system?
EY190- 12
Y h ... 36
N h ... 35
A30808-X3074-A473-2-7620
35
EMCYMN

:
:
:
:
:
:
:
:
command repetition
EXECD
REWIND MT:MTD=00;
command repetition
EXECD
Rewind and remove save tape.

The tape is to be marked as a mutilated generation save tape and sent to the
diagnostic center.
h ... 38
After that continue
36
Mutilated generation saving - continuation tape handling.
Each time, the messages

COPYGEN:OUTPUT=GEN,VERIFY=NO,VSN=GE1TAP,GEN=actgen,
REWIND=YES;
PLEASE MOUNT CONTINUATION TAPE TO VSN=GE(x)TAP
are output, the following 4 actions are to be executed:
1. Unload magnetic tape device, remove save tape.
The tape is to be marked as a mutilated generation save tape (part x) and
sent to the diagnostic center.
2. Mount and load a tape for mutilated generation saving.
The tape is to be initialized:
3. INIT MT:VSN=GE(y)TAP,MTD=00,CD=EBC,DENS=6250;
(y=2, 3, .....,n)
4. Continuation of the transfer:
After successful continuation tape handling:
:
:
:
:
:
:
command repetition
37
b
:
:
EXECD

REWIND MT:MTD=00;
command repetition
EXECD

diagnostic center.
A30808-X3074-A473-2-7620
EY190 - 13
EMCYMN
38
Delete mutilated generation.
The mutilated generation actgen which was just saved onto tape is now to be
deleted from the MDDs.
The value for actgen which was determined according to the last generation list
printout and noted, must be entered in the following command (GEN=actgen).
CAN GEN:GEN=actgen;
;
command repetition
HISTORY
SET REFGEN
----------+----------+---------+-----+-----------------+---+-----------@######### actgen
@######## @##
@####### @####### @## @#######
@######### @#######
@######## @##
@####### @####### @## @#######
@######### @#######
@######## @##
@####### @####### @## @#######
PLEASE ENTER
(YES: +/NO: -)<
+
actgen
FILE:
---------------------------------------------------------------------@################
command repetition
EXECD
Depending on the history of the generation, which is to be cancelled, the

number of erased files, listed above, varies.
39
b

RESET CFOPT;
command repetition
40
EXECD
Interrogation of configuration is to be executed.
......MMN:SW,
TAB, REC92
command repetition
:
:
command repetition
EY190- 14
STARTED
:
:
:
:
:
:
FINISHED
A30808-X3074-A473-2-7620
41
EMCYMN
Restore the desired configuration.

Was the requested configuration achieved?
42
The requested configuration was achieved.
h ... 42
According to the previous output, the requested configuration was not

achieved and therefore has to be restored before the procedure is continued.
h ... 42
i ... MMN:SW,
APS quarterly saving is to be executed according to procedure SW210.

Continue here, after execution of MMN:SW, procedure SW210.
PROC, SW210
43
i ... MMN:SW,

PROC, SW231
44
Decision.
Y h ... 45
N h ... 46
Are individual call data administered in the network node?
45

Saving of individual call data is to be executed according to procedure SW224.
Continue here, after execution of: MMN:SW, procedure SW224
i ... MMN:SW,
PROC, SW224
46
Decision.
Y h ... 47
N h ... 50
47

INIT MT:MTD=00,CD=EBC,DENS=6250,VSN=LOGTAP;
command repetition
:
:
command repetition
A30808-X3074-A473-2-7620
ACCEPTED
:
:
:
:
:
:
EXECD
EY190 - 15
EMCYMN
48

Meter routine saving is to be done.
Important note:
command repetition
:
:
command repetition
49
......MMN:SW,
TAB, METAP
STARTED
:
:
:
:
:
:
FINISHED

Important note:
......MMN:SW,
TAB, METAP
PER=YES;
command repetition
ACCEPTED
device.
50
Decision.
Have PATCHES been incorporated in the APS since the time when the last APS
routine- or quarterly saving was carried out?
EY190- 16
Y h ... 51
N h ... 52
A30808-X3074-A473-2-7620
51
EMCYMN
Patch treatment.
Important
Before repeating PATCH input, wait for tests to be made by TAC3.
The PATCHES, which may have been modified by TAC3, must be entered.
After that, the procedure is finished.
52
End of procedure.
At this point the procedure is finished.
END
A30808-X3074-A473-2-7620
EY190 - 17
EMCYMN
EY190- 18
A30808-X3074-A473-2-7620
3.7
EMCYMN

EY191
3.7.1
This procedure describes the restoration of switching operation using the GOLDEN
GENERATION, which is stored in duplicate on background memories.

the IOP:AUC module.
TS-011.
1
b
List generations.
DISP GEN;
command repetition
NAME OF CURRENT GENERATION: oldgold
HISTORY
SET REFGEN
----------+----------+---------+-----+-----------------+---+-----------@######### actgen
VALID
@##
@####### @####### @## @#######
@######### backgen
VALID
@##
@####### @####### @## @#######
BACKUP
oldgold
VALID
@##
@####### @####### @## @#######
command repetition
EXECD
A30808-X3074-A473-2-7620
EY191 - 1
EMCYMN
Merging of generations.
Merging of generations means the creation of a new generation by using the

code of one generation and the semipermanent data of a second generation.
In order to create new generations with the most current data base status
possible, already existing generations are merged.
1st variant: The code of the current generation (GOLDEN GENERATION) is
merged with the semipermanent data of the faulty generation (i.e. the generation, which was active before).
2nd variant: The code of the current generation (GOLDEN GENERATION) is
merged with the semipermanent data of the latest backup generation.
After creation of the new generations, these are to be start-up tested during
SPLIT mode operation.
The semipermanent data of the 1st variant are the most current and therefore
this generation is start-up tested first. The 2nd generation is only created in
order to have an immediate alternative if the start-up test with the 1st variant
was not successful.
1st variant
The following parameter values are to be used for the following command:
GENTASKL = Name of the GOLDEN GENERATION
(3rd line in the foregoing generation list)
GENSEMIL = Name of the generation, which was active before the fallback
(1st line in the foregoing generation list)
MERGE GEN:GENTASKL=oldgold,GENSEMIL=actgen;
command repetition
:
:
command repetition
EY191- 2
ACCEPTED
:
:
:
:
:
:
EXECD
A30808-X3074-A473-2-7620
4
b
EMCYMN
List generations.
DISP GEN;
command repetition
HISTORY
SET REFGEN
----------+----------+---------+-----+-----------------+---+-----------@######### actgen
VALID
@##
@####### @####### @## @#######
@######### backgen
VALID
@##
@####### @####### @## @#######
@######### oldgold
VALID
@##
@####### @####### @## @#######
MERGED
merggen1
BLOCKED
@##
@####### @####### @## @#######
command repetition
EXECD
2nd variant
The following parameter values are to be used for the following command:
GENTASKL = Name of the GOLDEN GENERATION
(3rd line of the foregoing generation list).
GENSEMIL = Name of the BACKUP GENERATION
(2nd line of the foregoing generation list).
MERGE GEN:GENTASKL=oldgold,GENSEMIL=backgen;
command repetition
:
:
command repetition
6
b
ACCEPTED
:
:
:
:
:
:
EXECD
List generations.
DISP GEN;
command repetition
HISTORY
SET REFGEN
----------+----------+---------+-----+-----------------+---+-----------@######### actgen
VALID
@##
@####### @####### @## @#######
@######### backgen
VALID
@##
@####### @####### @## @#######
@######### oldgold
VALID
@##
@####### @####### @## @#######
MERGED
merggen2
BLOCKED
@##
@####### @####### @## @#######
MERGED
merggen1
BLOCKED
@##
@####### @####### @## @#######
command repetition
EXECD
A30808-X3074-A473-2-7620
EY191 - 3
EMCYMN
Set CP SPLIT mode operation.
ATTENTION:
All commands in this block must be entered at a DCP (OMC); this means that
a session with the corresponding exchange must be set up.
STAT SSP;
command repetition
EXECD
If the following prerequisites are met, the CP SPLIT can be performed.
OMT-0 must be active
A DCP (OMC) service must be active.
IOC-0 and IOC-1 must be active.
Both CMYs and B:CMYs must be active.
Both MDDs and their corresponding IOPs must be active.
MTD-0 must be active.
All IOP:MBs must be active.
BAP-0 must be configured as SPARE (if this is not the case, the required
configuration must be established using the command COM BAP)
If not all prerequisites for a CP SPLIT are met, TAC2 must be consulted before
further steps are taken.
CP SPLIT mode operation may only be set if the APS change flag is in the
status RESET. Therefore this flag must be checked and, if necessary, must be
reset (in case of problems consult TAC).
DISP SPLITOPT;
command repetition
STATUS OF FLAG SPLITOPT:
EXECD
@#########
Y h ... 10
N h ... 9
Is the APS change flag in the status RESET?
9
b

RSET SPLITOPT;
DANGEROUS COMMAND RSETSPLITOPT READY TO EXECUTE<
;
STATUS OF FLAG SPLITOPT:
command repetition
10
RESET
EXECD

Are all prerequisites for the CP SPLIT met?
EY191- 4
Y h ... 12
N h ... 11
A30808-X3074-A473-2-7620
11
EMCYMN
No CP SPLIT possible.
CP SPLIT mode operation cannot be set.

Consult TAC2 as to how to continue.
The procedure must be terminated at this point.
Re-entry is made after consultation with TAC2.
End of procedure.
12
!
h ... 31

ATTENTION:
The following command must be entered at the DCP (OMC).
When the command is executed, on the split-off CP half (NSS) a manual
recovery is started automatically. After that, the entries ; and MAN must be
made immediately after the corresponding requests for entry have been made.
If the pause is too long, the system starts an automatic recovery instead of the
requested manual recovery
SPLIT SSP:TEST=NO;
DANGEROUS COMMAND SPLITSSP READY TO EXECUTE<
;
command repetition
EXECD
Y h ... 14
N h ... 13
Has CP SPLIT mode operation been started successfully?
13
SPLIT mode operation could not be set.
h ... 31
Consult TAC2 as how to continue.

The procedure must be terminated at this point.
Re-entry is made after consultation with TAC2.
End of procedure.
14
b
Interrogation of the system status.

STAT SSP;
command repetition
15
EXECD
Start-up test using the new generation (1st variant).
A manual recovery is attempted by using the newly created generation

(1st variant: code of the GOLDEN GENERATION and semipermanent data of
the generation, which was active before fallback).
The execution of the command SPLIT SSP automatically initiates a recovery on
the non-switching system half (NSS).
A30808-X3074-A473-2-7620
EY191 - 5
EMCYMN
16
Important note:
A faulty entry during the manual bootstrap may lead to a situation where no
further entries will be accepted. In this case press BOOT key for BAP-0 (NSS)
and continue procedure with block 16!
UNIT
STATUS
TEST
********************************************
BAP-0
@#####
@#####
BAP-1
@#####
@#####
B:CMY-0
@#####
@#####
B:CMY-1
@#####
@#####
CMY-0
@#####
@#####
CMY-1
@#####
@#####
IOC-0
@#####
@#####
IOC-1
@#####
@#####
TO DIAGNOSE MEMORY
TO FORMAT MEMORY
TO CONTINUE
:
:
:
DIAG;
FORMAT;
;ETX
17

TO
TO
TO
TO
TO
START APS MANUALLY

STOP INITIAL START
:
:
:
:
:
MANUALLY;
INSTALLATION;
UTILITY;
STOP;
;ETX
MAN;
EY191- 6
A30808-X3074-A473-2-7620
18
EMCYMN
Manual bootstrap - initiate manual recovery.

@#############
actgen
@#######################
backgen
@#######################
oldgold
@#######################
merggen2
@#######################
merggen1
@#######################
MANUAL RECOV: - LOADING VIA IOC : IOC-0;/IOC-1;
IOC-0;
NAME;(8 CHAR)
For the following command the name of the new generation

(1st variant: merggen1) is to be taken over.
The name can be found in the 5th line of the generation list displayed above.
merggen1;
MANUAL RECOVERY
LTG LOADING :
Y;/N;
N;
A30808-X3074-A473-2-7620
EY191 - 7
EMCYMN
19
Recovery report.
:
:
:
:
:
:
:
:
MDD-1 : INOPERABLE AND THEREFORE DEACTIVATED.

ALL FILES ON OTHER DISK AVAILABLE.
:
:
:
:
:
:
:
:
FCP RECOVERY REPORT
OST LOAD DEVICE
-------+----+----------MDD-00 ACT YES
MDD-01 NAC NO
ACTUAL GENERATION
:
:
: NAME
CREATION DATE
LAST CREATED
---------+------------------+-----------merggen1 @####### @####### @##
:
:
:
:
:
:
FCP UPDATE REPORT

JOBNO= @###
FILENAME:
GENERATION:
----------------------------------@################
@#######
:
:
:
:
:
:
:
:
faulty.
20
......General
information.
is executed.
21
b
Displaying system status.

STAT SSP;
command repetition
EY191- 8
EXECD
h ... 22
A30808-X3074-A473-2-7620
22
EMCYMN
Decision.
Was the start-up test successful?
Y h ... EMCYMN,
PROC, EY192
N h ... 23
23
Start-up test of the new generation (2nd variant).
Since the start-up test with the new generation (1st variant) was not successful,
a manual recovery is attempted by using the newly created generation
(2nd variant: code of the GOLDEN GENERATION and semipermanent data of
the latest BACKUP GENERATION).
Press BOOT key for BAP-0 (NSS).
24
Important note:
further entries will be accepted. In this case press BOOT key for BAP-0 (NSS)
and continue procedure with block 25!
UNIT
STATUS
TEST
********************************************
BAP-0
@#####
@#####
BAP-1
@#####
@#####
B:CMY-0
@#####
@#####
B:CMY-1
@#####
@#####
CMY-0
@#####
@#####
CMY-1
@#####
@#####
IOC-0
@#####
@#####
IOC-1
@#####
@#####
TO DIAGNOSE MEMORY
TO FORMAT MEMORY
TO CONTINUE
:
:
:
DIAG;
FORMAT;
;ETX
25

TO
TO
TO
TO
TO
START APS MANUALLY

STOP INITIAL START
:
:
:
:
:
MANUALLY;
INSTALLATION;
UTILITY;
STOP;
;ETX
MAN;
A30808-X3074-A473-2-7620
EY191 - 9
EMCYMN
26

@#############
actgen
@#######################
backgen
@#######################
oldgold
@#######################
merggen2
@#######################
merggen1
@#######################
IOC-0;
NAME;(8 CHAR)

(2nd variant: merggen2) is to be taken over.
merggen2;
MANUAL RECOVERY
LTG LOADING :
Y;/N;
N;
EY191- 10
A30808-X3074-A473-2-7620
27
EMCYMN
Recovery report.
:
:
:
:
:
:
:
:

:
:
:
:
:
:
:
:
FCP RECOVERY REPORT
OST LOAD DEVICE
-------+----+----------MDD-00 ACT YES
MDD-01 NAC NO
ACTUAL GENERATION
:
:
: NAME
CREATION DATE
LAST CREATED
---------+------------------+-----------merggen2 @####### @####### @##
:
:
:
:
:
:
FCP UPDATE REPORT

JOBNO= @###
FILENAME:
GENERATION:
----------------------------------@################
@#######
:
:
:
:
:
:
:
:
faulty.
28
...... mation.
General infor-
is executed.
29
b

STAT SSP;
command repetition
A30808-X3074-A473-2-7620
EXECD
h ... 30
EY191 - 11
EMCYMN
30
Decision.
Was the start-up test successful?
Y h ...EMCYMN,
PROC, EY193
N h ...EMCYMN,
PROC, EY194
31
End of procedure.
END
EY191- 12
A30808-X3074-A473-2-7620
3.8
EMCYMN

EY192
3.8.1
General information

the IOP:AUC module.
TS-011.
3.8.2

A30808-X3074-A473-2-7620
EY192 - 1
EMCYMN
Preparation for recovery with the tested generation.

Switch off power for BAP-0 and MDD-1.
This is done in order to have the opportunity to fallback on MDD-1, if problems

occur while entering the LOG files on MDD-0.
Manual recovery with the tested generation.
The manual recovery, using the tested generation, includes formatting of the
memory and LTG loading.
Press BOOT key for BAP-1 (active CP half).
Important note:
further entries will be accepted. In this case the procedure is to be continued
with block 2!
UNIT
STATUS
TEST
********************************************
BAP-0
@#####
@#####
BAP-1
@#####
@#####
B:CMY-0
@#####
@#####
B:CMY-1
@#####
@#####
CMY-0
@#####
@#####
CMY-1
@#####
@#####
IOC-0
@#####
@#####
IOC-1
@#####
@#####
TO DIAGNOSE MEMORY
TO FORMAT MEMORY
TO CONTINUE
:
:
:
DIAG;
FORMAT;
;ETX
FOR;
TO DIAGNOSE MEMORY
TO FORMAT MEMORY
TO CONTINUE
:
:
:
DIAG;
FORMAT;
;ETX
EY192- 2
A30808-X3074-A473-2-7620
EMCYMN

TO
TO
TO
TO
TO
START APS MANUALLY

STOP INITIAL START
:
:
:
:
:
MANUALLY;
INSTALLATION;
UTILITY;
STOP;
;ETX
MAN;

@#############
actgen
@#######################
backgen
@#######################
oldgold
@#######################
merggen2
@#######################
merggen1
@#######################
IOC-0;
NAME;(8 CHAR)

(1st variant:merggen1) is to be taken over.
merggen1;
MANUAL RECOVERY
LTG LOADING :
Y;/N;
Y;
A30808-X3074-A473-2-7620
EY192 - 3
EMCYMN
Recovery report.
:
:
:
:
:
:
:
:

:
:
:
:
:
:
:
:
FCP RECOVERY REPORT
OST LOAD DEVICE
-------+----+----------MDD-00 ACT YES
MDD-01 NAC NO
ACTUAL GENERATION
:
:
: NAME
CREATION DATE
LAST CREATED
---------+------------------+-----------merggen1 @####### @####### @##
:
:
:
:
:
:
FCP UPDATE REPORT

JOBNO= @###
FILENAME:
GENERATION:
----------------------------------@################
@#######
:
:
:
:
:
:
:
:
faulty.
......General
information
is executed.
8
b

STAT SSP;
command repetition
EY192- 4
EXECD
h ... 9
A30808-X3074-A473-2-7620
EMCYMN
Decision.
Y h ... 10
N h ... 49
10
b

command repetition
11
EXECD
OBJECT =
ALTYPE =
PABCAUSE=
ALARM-ID:

@#######################
@#################################################
@#############################################################
:
:
:
:
:
:
:
:
OBJECT =
ALTYPE =
PABCAUSE=
ALARM-ID:
RECOV
ALPRIO = MAJOR
ALSTAT = NP MSGNO = @####
@#######################
@#################################################
CLASS=ISTART
:
:
:
:
:
:
:
:
OBJECT =
ALTYPE =
PABCAUSE=
ALARM-ID:
NO (MORE)

@#######################
@#################################################
@#############################################################
Delete alarm.

ALPRIO=MAJOR which are assigned to an ISTART message.
command repetition
A30808-X3074-A473-2-7620
EXECD
EY192 - 5
EMCYMN
12
b
List generations.
DISP GEN;
command repetition
NAME OF CURRENT GENERATION: merggen1
HISTORY
SET REFGEN
----------+----------+---------+-----+-----------------+---+-----------@######### actgen
VALID
@##
@####### @####### @## @#######
@######### backgen
VALID
@##
@####### @####### @## @#######
@######### oldgold
VALID
@##
@####### @####### @## @#######
MERGED
merggen2
BLOCKED
@##
@####### @####### @## @#######
MERGED
merggen1
BLOCKED
@##
@####### @####### @## @#######
command repetition
EXECD
13
Set the generation valid.
The name of the tested new generation (1st variant: merggen1) is to be used
for the parameter GEN in the following command.
MOD GEN:GEN=merggen1,VALIDITY=VALID;
command repetition
14
b
EXECD
List generations.
DISP GEN;
command repetition
HISTORY
SET REFGEN
----------+----------+---------+-----+-----------------+---+-----------@######### actgen
VALID
@##
@####### @####### @## @#######
@######### backgen
VALID
@##
@####### @####### @## @#######
@######### oldgold
VALID
@##
@####### @####### @## @#######
MERGED
merggen2
BLOCKED
@##
@####### @####### @## @#######
MERGED
merggen1
VALID
@##
@####### @####### @## @#######
command repetition
EXECD
EY192- 6
A30808-X3074-A473-2-7620
15
EMCYMN
Information.
following cases:
STATISTIC CHARGING
16
Decision.
Y h ... 17
N h ... 18
Are statistic meters administered in the network node?
17

The tape is to be marked as APS routine save tape and to be stored under date
of save.
18
Configuration of the BAP.
BAP-0, which was switched off before the start-up test was carried out, is
switched on again and configured.
Switch on power for BAP-0.
Configuration of BAP-0:
CONF BAP:BAP=0,OST=MBL;
command repetition
EXECD
CONF BAP:BAP=0,OST=SPR;
DANGEROUS COMMAND !
DO YOU WANT COMMAND TO BE EXECUTED ?
(YES: +/NO: -) <
+
command repetition
:
:
command repetition
A30808-X3074-A473-2-7620
ACCEPTED
:
:
:
:
:
:
EXECD
EY192 - 7
EMCYMN
19
b
List generations.
DISP GEN;
command repetition
HISTORY
SET REFGEN
----------+----------+---------+-----+-----------------+---+-----------@######### actgen
VALID
@##
@####### @####### @## @#######
@######### backgen
VALID
@##
@####### @####### @## @#######
@######### oldgold
VALID
@##
@####### @####### @## @#######
MERGED
merggen2
BLOCKED
@##
@####### @####### @## @#######
MERGED
merggen1
VALID
@##
@####### @####### @## @#######
command repetition
EXECD
The entry in the 1st line of the column GENERATION is the name of the mutilated generation actgen, i.e. the generation which was active before the fallback.
Important:
The value of actgen should be written down since it is needed in the following to
complete MML commands.
20

21
b

command repetition
:
:
command repetition
EY192- 8
ACCEPTED
:
:
:
:
:
:
EXECD
A30808-X3074-A473-2-7620
22
EMCYMN
Important note:
REWIND=YES;
PLEASE MOUNT CONTINUATION TAPE TO VSN = @#####

(GEN=actgen).
D=YES;
command repetition
:
:
ACCEPTED
:
:
:
:
:
:
A30808-X3074-A473-2-7620
Y h ... 24
N h ... 23
EY192 - 9
EMCYMN
23

:
:
:
:
:
:
:
:
command repetition
EXECD
REWIND MT:MTD=00;
command repetition
EXECD

diagnostic center.
24
h ... 26

REWIND=YES;

(y=2, 3, .....,n)
:
:
:
:
:
:
command repetition
25
b
:
:
EXECD

REWIND MT:MTD=00;
command repetition
EXECD

diagnostic center.
EY192- 10
A30808-X3074-A473-2-7620
26
b
EMCYMN
List generations.
DISP GEN;
command repetition
HISTORY
SET REFGEN
----------+----------+---------+-----+-----------------+---+-----------@######### actgen
VALID
@##
@####### @####### @## @#######
@######### backgen
VALID
@##
@####### @####### @## @#######
@######### oldgold
VALID
@##
@####### @####### @## @#######
MERGED
merggen2
BLOCKED
@##
@####### @####### @## @#######
MERGED
merggen1
VALID
@##
@####### @####### @## @#######
command repetition
EXECD
A30808-X3074-A473-2-7620
EY192 - 11
EMCYMN
27
Delete generations.
Important
All generations, which were displayed in the last generation list printout, with the
exception of the current generation merggen1, are to be cancelled, i.e. the
following command sequence is to be used for each generation which is to be
cancelled.
In each case the corresponding generation name, determined from the generation list printout, is to be used for the parameter GEN in the following command.
CAN GEN:GEN=generation;
;
command repetition
HISTORY
SET REFGEN
----------+----------+---------+-----+-----------------+---+-----------@######### actgen
VALID
@##
@####### @####### @## @#######
@######### backgen
VALID
@##
@####### @####### @## @#######
@######### oldgold
VALID
@##
@####### @####### @## @#######
MERGED
merggen2
BLOCKED
@##
@####### @####### @## @#######
MERGED
merggen1
VALID
@##
@####### @####### @## @#######
PLEASE ENTER
(YES: +/NO: -)<
+
@#######
FILE:
---------------------------------------------------------------------@################
command repetition
EXECD

This block is to be executed for all generations, except the current generation
merggen1.
EY192- 12
A30808-X3074-A473-2-7620
28
EMCYMN
Activation of the second disk.
The disk which was switched off during the system start with the tested generation is switched on, initialized and configured.
Switch on power for MDD-1.
Configuration of MDD-1:
CONF MDD:MDD=1,OST=MBL;
command repetition
EXECD
Initialization of MDD-1:
INIT MD:MDD=1;
command repetition
EXECD
CONF MDD:MDD=1,OST=ACT;
command repetition
EXECD
The contents of MDD-0 are copied to MDD-1.

The procedure can be continued with the next block when the following
message is output:
29
b

RESET CFOPT;
command repetition
30
EXECD
command repetition
:
:
command repetition
31
...... TAB,
MMN:SW,
REC92
STARTED
:
:
:
:
:
:
FINISHED

h ... 32

h ... 32
A30808-X3074-A473-2-7620
EY192 - 13
EMCYMN
32
b

RSET LOG;
;
LOG-FILE(S)
READY FOR USE: @################ @################
command repetition
EXECD
33

The save tape for the current quarter is to be used.
(Large tape with write ring.)
34
b
Tape saving of the latest LOG file.

TRANS FILE:FILE=LG.,VSNR=LOGTAP,COPMOD=SSWF;
command repetition
REWIND MT:MTD=00;
command repetition
35
EXECD
EXECD

The tape is to be marked as APS routine save tape Ax and to be stored in tape
group A under date of save.
EY192- 14
A30808-X3074-A473-2-7620
36
b
Delete the latest LOG file.

DISP FILE:FILE=LG.;
command repetition
EMCYMN
EXECD
DACT FNS:FNS=LG;
DANGEROUS COMMAND DACTFNS READY TO EXECUTE<
;
command repetition
EXECD
The name of the LOG file, which was determined before is to be used for the
parameter FILE in the following commands.
The command MOD FILEAUT; is to be entered for each file LG.name.Ax, which
is to be deleted. Wildcards can be used for the parameter FILE of the command
DEL FILE;.
MOD FILEAUT:AR=NOAR,FILE=name;
DANGEROUS COMMAND MODFILEAUT READY TO EXECUTE<
;
command repetition
DEL FILE:FILE=name;
command repetition
EXECD
EXECD
ACT FNS:FNS=LG.;
DANGEROUS COMMAND ACTFNS READY TO EXECUTE<
;
command repetition
37
b
EXECD
Activate LOG function.

SET LOG:FILE=LOG6,SIZE=24,ERASE=Y;
DANGEROUS COMMAND SETLOG READY TO EXECUTE<
;
command repetition
38
b
EXECD
List generations.
DISP GEN;
command repetition
HISTORY
SET REFGEN
----------+----------+---------+-----+-----------------+---+-----------MERGED
merggen1
VALID
@##
@####### @####### @## @#######
command repetition
EXECD
A30808-X3074-A473-2-7620
EY192 - 15
EMCYMN
39
i....MMN:SW,

Continue here, after execution of: MMN:SW, procedure SW210.
PROC, SW210
40
i....MMN:SW,

PROC, SW231
41
Decision.
Y h ... 42
N h ... 43
Are individual call data administered?
42

i....MMN:SW,
PROC, SW224
43
Decision.
Y h ... 44
N h ... 47
44

command repetition
:
:
command repetition
EY192- 16
ACCEPTED
:
:
:
:
:
:
EXECD
A30808-X3074-A473-2-7620
45
EMCYMN

Important note:
administered meter saving.
command repetition
:
:
command repetition
46
...... TAB,
MMN:SW,
METAP
STARTED
:
:
:
:
:
:
FINISHED

Important note:
PER=YES;
command repetition
...... TAB,
MMN:SW,
METAP
ACCEPTED
device.
47
Decision.
A30808-X3074-A473-2-7620
Y h ... 48
N h ... 62
EY192 - 17
EMCYMN
48
Patch treatment.
Important
h ... 62
49
Preparation of manual recovery with the golden generation.
The recovery with the new tested generation merggen1 (1st variant) was not
successful.
So first switching operation is to be restored via a start-up with the GOLDEN
GENERATION. After that TAC should be consulted to decide on how to
continue.
Switch off power for MDD-0.
50
Manual recovery with the golden generation.
The manual recovery with the GOLDEN GENERATION includes formatting the
Press BOOT key for BAP-1.
EY192- 18
A30808-X3074-A473-2-7620
51
EMCYMN
Important note:
with block 53!
UNIT
STATUS
TEST
********************************************
BAP-0
@#####
@#####
BAP-1
@#####
@#####
B:CMY-0
@#####
@#####
B:CMY-1
@#####
@#####
CMY-0
@#####
@#####
CMY-1
@#####
@#####
IOC-0
@#####
@#####
IOC-1
@#####
@#####
TO DIAGNOSE MEMORY
TO FORMAT MEMORY
TO CONTINUE
:
:
:
DIAG;
FORMAT;
;ETX
FOR;
TO DIAGNOSE MEMORY
TO FORMAT MEMORY
TO CONTINUE
:
:
:
DIAG;
FORMAT;
;ETX
52

TO
TO
TO
TO
TO
START APS MANUALLY

STOP INITIAL START
:
:
:
:
:
MANUALLY;
INSTALLATION;
UTILITY;
STOP;
;ETX
MAN;
A30808-X3074-A473-2-7620
EY192 - 19
EMCYMN
53

@#############
actgen
@#######################
backgen
@#######################
oldgold
@#######################
merggen2
@#######################
merggen1
@#######################
IOC-1;
NAME;(8 CHAR)
For the following command the name of the golden generation oldgold is to be
taken over.
The name can be found in the 3rd line of the generation list displayed above.
oldgold;
MANUAL RECOVERY
LTG LOADING :
Y;/N;
Y;
EY192- 20
A30808-X3074-A473-2-7620
54
EMCYMN
Recovery report.
:
:
:
:
:
:
:
:

:
:
:
:
:
:
:
:
FCP RECOVERY REPORT
OST LOAD DEVICE
-------+----+----------MDD-00 NAC NO
MDD-01 ACT YES
ACTUAL GENERATION
:
:
: NAME
CREATION DATE
LAST CREATED
---------+------------------+-----------oldgold
@####### @####### @##
:
:
:
:
:
:
FCP UPDATE REPORT

JOBNO= @###
FILENAME:
GENERATION:
----------------------------------@################
@#######
:
:
:
:
:
:
:
:
faulty.
55
...... mation
General infor-
is executed.
56
b

STAT SSP;
command repetition
A30808-X3074-A473-2-7620
EXECD
h ... 57
EY192 - 21
EMCYMN
57
b

RSET LOG;
;
LOG-FILE(S)
READY FOR USE: @################ @################
command repetition
EXECD
58
BAP-0, which was switched off before the recovery attempt with the tested
generation merggenx was carried out, is switched on again and configured.
command repetition
EXECD
DANGEROUS COMMAND !
(YES: +/NO: -) <
+
command repetition
:
:
command repetition
EY192- 22
ACCEPTED
:
:
:
:
:
:
EXECD
A30808-X3074-A473-2-7620
59
b

command repetition
60
EMCYMN
EXECD
OBJECT =
ALTYPE =
PABCAUSE=
ALARM-ID:

@#######################
@#################################################
@#############################################################
:
:
:
:
:
:
:
:
OBJECT =
ALTYPE =
PABCAUSE=
ALARM-ID:
RECOV
ALPRIO = MAJOR
@#######################
@#################################################
CLASS=ISTART
:
:
:
:
:
:
:
:
OBJECT =
ALTYPE =
PABCAUSE=
ALARM-ID:
NO (MORE)

@#######################
@#################################################
@#############################################################
Delete alarm.

command repetition
61
EXECD
Further actions.
Further actions should only be done after consultation of TAC2/3.

It is possible that data are mutilated. In this case the LOG data must be entered
step-by-step. If desired, the entering of the LOG files according to procedure
EY194, can be started immediately.
Attention:
The account suspension for CA. and IARSTAT is still active.
A30808-X3074-A473-2-7620
...... PROC,
EMCYMN,
EY194
EY192 - 23
EMCYMN
62
End of procedure.
END
EY192- 24
A30808-X3074-A473-2-7620
3.9
EMCYMN

EY193
3.9.1
General information

the IOP:AUC module.
TS-011.
3.9.2

A30808-X3074-A473-2-7620
EY193 - 1
EMCYMN
Preparation for recovery with the tested generation.

Switch off power for BAP-0 and MDD-1.

Manual recovery with the tested generation.
The manual recovery, using the tested generation, includes formatting of the
Press BOOT key for BAP-1 (active CP half).
Important note:
with block 2!
UNIT
STATUS
TEST
********************************************
BAP-0
@#####
@#####
BAP-1
@#####
@#####
B:CMY-0
@#####
@#####
B:CMY-1
@#####
@#####
CMY-0
@#####
@#####
CMY-1
@#####
@#####
IOC-0
@#####
@#####
IOC-1
@#####
@#####
TO DIAGNOSE MEMORY
TO FORMAT MEMORY
TO CONTINUE
:
:
:
DIAG;
FORMAT;
;ETX
FOR;
TO DIAGNOSE MEMORY
TO FORMAT MEMORY
TO CONTINUE
:
:
:
DIAG;
FORMAT;
;ETX
EY193- 2
A30808-X3074-A473-2-7620
EMCYMN

TO
TO
TO
TO
TO
START APS MANUALLY

STOP INITIAL START
:
:
:
:
:
MANUALLY;
INSTALLATION;
UTILITY;
STOP;
;ETX
MAN;

@#############
actgen
@#######################
backgen
@#######################
oldgold
@#######################
merggen2
@#######################
merggen1
@#######################
IOC-0;
NAME;(8 CHAR)

(2nd variant: merggen2) is to be taken over.
merggen2;
MANUAL RECOVERY
LTG LOADING :
Y;/N;
Y;
A30808-X3074-A473-2-7620
EY193 - 3
EMCYMN
Recovery report.
:
:
:
:
:
:
:
:

:
:
:
:
:
:
:
:
FCP RECOVERY REPORT
OST LOAD DEVICE
-------+----+----------MDD-00 ACT YES
MDD-01 NAC NO
ACTUAL GENERATION
:
:
: NAME
CREATION DATE
LAST CREATED
---------+------------------+-----------merggen2 @####### @####### @##
:
:
:
:
:
:
FCP UPDATE REPORT

JOBNO= @###
FILENAME:
GENERATION:
----------------------------------@################
@#######
:
:
:
:
:
:
:
:
faulty.
......General
information
is executed.
8
b

STAT SSP;
command repetition
EY193- 4
EXECD
h ... 9
A30808-X3074-A473-2-7620
EMCYMN
Decision.
Y h ... 10
N h ... 50
10
b

command repetition
11
EXECD
OBJECT =
ALTYPE =
PABCAUSE=
ALARM-ID:

@#######################
@#################################################
@#############################################################
:
:
:
:
:
:
:
:
OBJECT =
ALTYPE =
PABCAUSE=
ALARM-ID:
RECOV
ALPRIO = MAJOR
@#######################
@#################################################
CLASS=ISTART
:
:
:
:
:
:
:
:
OBJECT =
ALTYPE =
PABCAUSE=
ALARM-ID:
NO (MORE)

@#######################
@#################################################
@#############################################################
Delete alarm.

command repetition
A30808-X3074-A473-2-7620
EXECD
EY193 - 5
EMCYMN
12
b
List generations.
DISP GEN;
command repetition
HISTORY
SET REFGEN
----------+----------+---------+-----+-----------------+---+-----------@######### actgen
VALID
@##
@####### @####### @## @#######
@######### backgen
VALID
@##
@####### @####### @## @#######
@######### oldgold
VALID
@##
@####### @####### @## @#######
MERGED
merggen2
BLOCKED
@##
@####### @####### @## @#######
MERGED
merggen1
BLOCKED
@##
@####### @####### @## @#######
command repetition
EXECD
13
Set the generation valid.
The name of the tested new generation (2nd variant: merggen2) is to be used
for the parameter GEN in the following command.
MOD GEN:GEN=merggen2,VALIDITY=VALID;
command repetition
14
b
EXECD
List generations.
DISP GEN;
command repetition
HISTORY
SET REFGEN
----------+----------+---------+-----+-----------------+---+-----------@######### actgen
VALID
@##
@####### @####### @## @#######
@######### backgen
VALID
@##
@####### @####### @## @#######
@######### oldgold
VALID
@##
@####### @####### @## @#######
MERGED
merggen2
VALID
@##
@####### @####### @## @#######
MERGED
merggen1
BLOCKED
@##
@####### @####### @## @#######
command repetition
EXECD
15
b

RESET CFOPT;
command repetition
EY193- 6
EXECD
A30808-X3074-A473-2-7620
16
b
EMCYMN

RSET LOG;
;
LOG-FILE(S)
READY FOR USE: @################ @################
command repetition
EXECD
17

;
command repetition
18
EXECD
Regeneration of LOG files is to be executed.
command repetition
:
:
command repetition
19
...... TAB,
MMN:SW,
REC91
STARTED
:
:
:
:
:
:
FINISHED
records was suppressed. This suppression is canceled again using the
following command.
;
command repetition
A30808-X3074-A473-2-7620
EXECD
EY193 - 7
EMCYMN
20
Information.
following cases:
STATISTIC CHARGING
21
Decision.
Y h ... 22
N h ... 25
22
Information.
During account suspension no begin and end meter readings are displayed
23
b

command repetition
:
:
command repetition
24
ACCEPTED
:
:
:
:
:
:
EXECD

The tape is to be marked as APS routine save tape and to be stored under the
date of save.
EY193- 8
A30808-X3074-A473-2-7620
25
EMCYMN
BAP-0, which was switched off before the start-up test was carried out, is
switched on again and configured.
command repetition
EXECD
DANGEROUS COMMAND !
+
command repetition
:
:
command repetition
26
b
(YES: +/NO: -) <
ACCEPTED
:
:
:
:
:
:
EXECD
List generations.
DISP GEN;
command repetition
HISTORY
SET REFGEN
----------+----------+---------+-----+-----------------+---+-----------@######### actgen
VALID
@##
@####### @####### @## @#######
@######### backgen
VALID
@##
@####### @####### @## @#######
@######### oldgold
VALID
@##
@####### @####### @## @#######
MERGED
merggen2
VALID
@##
@####### @####### @## @#######
MERGED
merggen1
BLOCKED
@##
@####### @####### @## @#######
command repetition
EXECD
Important:
27

A30808-X3074-A473-2-7620
EY193 - 9
EMCYMN
28
b

command repetition
:
:
command repetition
29
ACCEPTED
:
:
:
:
:
:
EXECD
Important note:
REWIND=YES;

(GEN=actgen).
D=YES;
command repetition
:
:
ACCEPTED
:
:
:
:
:
:
EY193- 10
Y h ... 31
N h ... 30
A30808-X3074-A473-2-7620
30
EMCYMN

:
:
:
:
:
:
:
:
command repetition
EXECD
REWIND MT:MTD=00;
command repetition
EXECD

diagnostic center.
31
h ... 33

REWIND=YES;

(y=2, 3, .....,n)
:
:
:
:
:
:
command repetition
32
b
:
:
EXECD

REWIND MT:MTD=00;
command repetition
EXECD

diagnostic center.
A30808-X3074-A473-2-7620
EY193 - 11
EMCYMN
33
b
List generations.
DISP GEN;
command repetition
HISTORY
SET REFGEN
----------+----------+---------+-----+-----------------+---+-----------@######### actgen
VALID
@##
@####### @####### @## @#######
@######### backgen
VALID
@##
@####### @####### @## @#######
@######### oldgold
VALID
@##
@####### @####### @## @#######
MERGED
merggen2
VALID
@##
@####### @####### @## @#######
MERGED
merggen1
BLOCKED
@##
@####### @####### @## @#######
command repetition
EXECD
EY193- 12
A30808-X3074-A473-2-7620
34
EMCYMN
Delete generations.
Important
exception of the current generation merggen2, are to be cancelled, i.e. the
cancelled.
;
command repetition
HISTORY
SET REFGEN
----------+----------+---------+-----+-----------------+---+-----------@######### actgen
VALID
@##
@####### @####### @## @#######
@######### backgen
VALID
@##
@####### @####### @## @#######
@######### oldgold
VALID
@##
@####### @####### @## @#######
MERGED
merggen2
VALID
@##
@####### @####### @## @#######
MERGED
merggen1
BLOCKED
@##
@####### @####### @## @#######
PLEASE ENTER
(YES: +/NO: -)<
+
@#######
FILE:
---------------------------------------------------------------------@################
command repetition
EXECD

merggen2.
A30808-X3074-A473-2-7620
EY193 - 13
EMCYMN
35
The disk which was switched off during the system start with the tested generation is switched on, initialized and configured.
command repetition
EXECD
INIT MD:MDD=1;
command repetition
EXECD
command repetition
EXECD

message is output:
36
b

RESET CFOPT;
command repetition
37
EXECD
command repetition
:
:
command repetition
38
......MMN:SW,
TAB, REC92
STARTED
:
:
:
:
:
:
FINISHED

h ... 39

h ... 39
EY193- 14
A30808-X3074-A473-2-7620
39
b
EMCYMN
List generations.
DISP GEN;
command repetition
HISTORY
SET REFGEN
----------+----------+---------+-----+-----------------+---+-----------MERGED
merggen2
VALID
@##
@####### @####### @## @#######
command repetition
EXECD
40

i ... MMN:SW,
PROC, SW210
41

i ... MMN:SW,
PROC, SW231
42
Decision.
Are individual call data administered in the exchange?
43
Y h ... 43
N h ... 44

i ... MMN:SW,
PROC, SW224
44
Decision.
A30808-X3074-A473-2-7620
Y h ... 45
N h ... 48
EY193 - 15
EMCYMN
45

command repetition
:
:
command repetition
46
ACCEPTED
:
:
:
:
:
:
EXECD

Important note:
command repetition
:
:
command repetition
47
......MMN:SW,
TAB, METAP
STARTED
:
:
:
:
:
:
FINISHED

Important note:
......MMN:SW,
TAB, METAP
PER=YES;
command repetition
ACCEPTED
device.
EY193- 16
A30808-X3074-A473-2-7620
48
Decision.
49
EMCYMN
Y h ... 49
N h ... 63
Patch treatment.
Important
50
h ... 63
Preparation of manual recovery with the golden generation.
The recovery with the new tested generation merggen2 (2nd variant) was not
successful.
So first switching operation is to be restored via a start-up with the GOLDEN
GENERATION. After that TAC should be consulted to decide on how to
continue.
51
Manual recovery with the golden generation.
The manual recovery with the GOLDEN GENERATION includes formatting the
A30808-X3074-A473-2-7620
EY193 - 17
EMCYMN
52
Important note:
with block 53!
UNIT
STATUS
TEST
********************************************
BAP-0
@#####
@#####
BAP-1
@#####
@#####
B:CMY-0
@#####
@#####
B:CMY-1
@#####
@#####
CMY-0
@#####
@#####
CMY-1
@#####
@#####
IOC-0
@#####
@#####
IOC-1
@#####
@#####
TO DIAGNOSE MEMORY
TO FORMAT MEMORY
TO CONTINUE
:
:
:
DIAG;
FORMAT;
;ETX
FOR;
TO DIAGNOSE MEMORY
TO FORMAT MEMORY
TO CONTINUE
:
:
:
DIAG;
FORMAT;
;ETX
53

TO
TO
TO
TO
TO
START APS MANUALLY

STOP INITIAL START
:
:
:
:
:
MANUALLY;
INSTALLATION;
UTILITY;
STOP;
;ETX
MAN;
EY193- 18
A30808-X3074-A473-2-7620
54
EMCYMN

@#############
actgen
@#######################
backgen
@#######################
oldgold
@#######################
merggen2
@#######################
merggen1
@#######################
IOC-1;
NAME;(8 CHAR)
For the following command the name of the golden generation oldgold is to be
taken over.
The name can be found in the 3rd line of the generation list displayed above.
oldgold;
MANUAL RECOVERY
LTG LOADING :
Y;/N;
Y;
A30808-X3074-A473-2-7620
EY193 - 19
EMCYMN
55
Recovery report.
:
:
:
:
:
:
:
:

:
:
:
:
:
:
:
:
FCP RECOVERY REPORT
OST LOAD DEVICE
-------+----+----------MDD-00 NAC NO
MDD-01 ACT YES
ACTUAL GENERATION
:
:
: NAME
CREATION DATE
LAST CREATED
---------+------------------+-----------oldgold
@####### @####### @##
:
:
:
:
:
:
FCP UPDATE REPORT

JOBNO= @###
FILENAME:
GENERATION:
----------------------------------@################
@#######
:
:
:
:
:
:
:
:
faulty.
56
......General
information
is executed.
57
b

STAT SSP;
command repetition
EY193- 20
EXECD
h ... 58
A30808-X3074-A473-2-7620
58
b
EMCYMN

RSET LOG;
;
LOG-FILE(S)
READY FOR USE: @################ @################
command repetition
EXECD
59
BAP-0, which was switched off before the recovery attempt with the tested
generation merggenx was carried out, is switched on again and configured.
command repetition
EXECD
DANGEROUS COMMAND !
(YES: +/NO: -) <
+
command repetition
:
:
command repetition
A30808-X3074-A473-2-7620
ACCEPTED
:
:
:
:
:
:
EXECD
EY193 - 21
EMCYMN
60
b

command repetition
61
EXECD
OBJECT =
ALTYPE =
PABCAUSE=
ALARM-ID:

@#######################
@#################################################
@#############################################################
:
:
:
:
:
:
:
:
OBJECT =
ALTYPE =
PABCAUSE=
ALARM-ID:
RECOV
ALPRIO = MAJOR
@#######################
@#################################################
CLASS=ISTART
:
:
:
:
:
:
:
:
OBJECT =
ALTYPE =
PABCAUSE=
ALARM-ID:
NO (MORE)

@#######################
@#################################################
@#############################################################
Delete alarm.

command repetition
62
EXECD
Further actions.
Further actions should only be done after consultation of TAC2/3.

It is possible that data are mutilated. In this case the LOG data must be entered
step-by-step. If desired, the entering of the LOG files according to procedure
EY194, can be started immediately.
Attention:
The account suspension for CA. and IARSTAT is still active.
EY193- 22
......EMCYMN,
PROC, EY194
A30808-X3074-A473-2-7620
63
EMCYMN
End of procedure.
END
A30808-X3074-A473-2-7620
EY193 - 23
EMCYMN
EY193- 24
A30808-X3074-A473-2-7620
3.10
EMCYMN

EY194
3.10.1
3.10.2

Decision.
Was this procedure called by procedure EY191?
Y h ... 2
N h ... 5
Preparation for merging the two system halves.


A30808-X3074-A473-2-7620
EY194 - 1
EMCYMN
Merging the two system halves.
Attention:
All commands of this block must be entered at a DCP (OMC). This means that a
session with the corresponding network node must be set up.
STAT SSP;
command repetition
EXECD
MERGE SSP:DIAG=NO;
command repetition
4
b
EXECD

RSET LOG;
;
LOG-FILE(S)
READY FOR USE: @################ @################

command repetition
EXECD
Renaming the active LOG file.
The active LOG file is renamed by copying the file first and deleting the source
file afterwards.
TRANS FILE:FILE=TEMP./LG.;
command repetition
EXECD
Deleting the source file(s) LG.name.Ax:

In the following commands the name of the source file(s) is to be used for the
parameter FILE.
The command MOD FILEAUT is to be entered for each file LG.name.Ax, which
is to be deleted. Wildcards can be used for the parameter FILE of the DEL FILE
command.
MOD FILEAUT:AR=NOAR,FILE=LG.name.Ax;
DANGEROUS COMMAND MODFILEAUT READY TO EXECUTE<
;
command repetition
EXECD
DEL FILE:FILE=LG.;
command repetition
EY194- 2
EXECD
A30808-X3074-A473-2-7620
EMCYMN
Tape/disk transfer of LOG files.
The APS routine save tape which contains the LOG files to be transferred
should still be mounted in the magnetic tape device.
DACT FNS:FNS=LG;
;
command repetition
EXECD
TRANS FILE:FILE=LG.,VSNS=LOGTAP;
command repetition
:
:
command repetition
SENDER
RECEIVER
ACCEPTED
:
:
:
:
:
:
EXECD
: @#######
: @#######
START START
FILE IDENTIFICATION
DATA TYPE
BYTES/
/END- /END: FILE
VSN
STATE : ERROR
RECORDS
DATE TIME
-+-----------------+------+-----+-+-----+-+--+----+---------+-----+----@ @################ @##### @#### @ @#### @ @# @### @######## @#### @####
@ @################ @##### @#### @ @#### @ @# @### @######## @#### @####
ACT FNS:FNS=LG;
DANGEROUS COMMAND ACTFNS READY TO EXECUTE< READY TO EXECUTE<
;
command repetition
EXECD

The tape is to be marked as APS routine save tape and to be stored under the
date of save.

;
command repetition
A30808-X3074-A473-2-7620
EXECD
EY194 - 3
EMCYMN
Decision.
Which routine saving was carried out at latest?
The first routine saving was the latest, which was carried out.
The second routine saving was the latest, which was carried out.
The third routine saving was the latest, which was carried out.
The fourth routine saving was the latest, which was carried out.
The fifth routine saving was the latest, which was carried out.
EY194- 4
h ... 10
h ... 11
h ... 12
h ... 13
h ... 14
A30808-X3074-A473-2-7620
10
EMCYMN
Updating the database and activating the LOG function.
Updating the database is done by starting the LOG file LG.LOG1.A0.

Important:
If, according to the printout, one or more LOG command(s) was (were) not
executed, the reason must be determined and the fault must be cleared.
EXEC CMDFILE:FILE=LG.LOG1.A0;
command repetition
:
:
command repetition
STARTED
:
:
:
:
:
:
FINISHED
DEL FILE:FILE=LG.;
command repetition
ACCEPTED
FILE
----------------@################
ERASE ALL FILES LISTED ?
ENTER (YES: + /NO: -) <
+
command repetition
EXECD
SET LOG:FILE=LOG6,SIZE=24,ERASE=YES;
;
command repetition
EXECD
Update the database by starting the LOG file TEMP.LOG2.A1 or by manual

entry.
Important:
If due to an overflow of the file LG.LOG2.A1 further files LG.LOG2.Ay were
created and renamed to TEMP.LOG2.Ay, these files must be started immediately after TEMP.LOG2.A1.
EXEC CMDFILE:FILE=TEMP.LOG2.A1;
command repetition
:
:
command repetition
A30808-X3074-A473-2-7620
STARTED
:
:
:
:
:
:
FINISHED
h ... 15
EY194 - 5
EMCYMN
11
Updating the database is done by starting the LOG files LG.LOG1.A0 and
LG.LOG2.A0.
Important:
command repetition
:
:
command repetition
:
:
:
:
FINISHED
command repetition
:
:
command repetition
STARTED
:
:
STARTED
:
:
:
:
:
:
FINISHED
DEL FILE:FILE=LG.;
command repetition
ACCEPTED
FILE
----------------@################
+
command repetition
EXECD
;
command repetition
EXECD

entry.
Important:
command repetition
:
:
command repetition
EY194- 6
STARTED
:
:
:
:
:
:
FINISHED
h ... 15
A30808-X3074-A473-2-7620
12
EMCYMN
Updating the database is done by starting the LOG files LG.LOG1.A0,

LG.LOG2.A0 and LG.LOG3.A0.
Important:
command repetition
:
:
command repetition
:
:
FINISHED
STARTED
:
:
:
:
:
:
FINISHED
command repetition
:
:
command repetition
:
:
command repetition
:
:
command repetition
STARTED
:
:
STARTED
:
:
:
:
:
:
FINISHED
DEL FILE:FILE=LG.;
command repetition
ACCEPTED
FILE
----------------@################
+
command repetition
EXECD
;
command repetition
EXECD

entry.
Important:
A30808-X3074-A473-2-7620
EY194 - 7
EMCYMN
command repetition
:
:
command repetition
EY194- 8
STARTED
:
:
:
:
:
:
FINISHED
h ... 15
A30808-X3074-A473-2-7620
13
EMCYMN

LG.LOG2.A0, LG.LOG3.A0 and LG.LOG4.A0.
Important:
command repetition
:
:
command repetition
FINISHED
STARTED
:
:
:
:
:
:
FINISHED
STARTED
:
:
:
:
:
:
FINISHED
command repetition
:
:
command repetition
:
:
command repetition
:
:
command repetition
:
:
command repetition
:
:
command repetition
STARTED
:
:
STARTED
:
:
:
:
:
:
FINISHED
DEL FILE:FILE=LG.;
command repetition
ACCEPTED
FILE
----------------@################
+
command repetition
EXECD
;
command repetition
A30808-X3074-A473-2-7620
EXECD
EY194 - 9
EMCYMN

entry.
Important:
command repetition
:
:
command repetition
EY194- 10
STARTED
:
:
:
:
:
:
FINISHED
h ... 15
A30808-X3074-A473-2-7620
14
EMCYMN

LG.LOG2.A0, LG.LOG3.A0, LG.LOG4.A0 and LG.LOG5.A0.
Important:
command repetition
:
:
command repetition
STARTED
:
:
:
:
:
:
FINISHED
STARTED
:
:
:
:
:
:
FINISHED
STARTED
:
:
:
:
:
:
FINISHED
command repetition
:
:
command repetition
FINISHED
command repetition
:
:
command repetition
:
:
command repetition
:
:
command repetition
:
:
command repetition
:
:
command repetition
STARTED
:
:
STARTED
:
:
:
:
:
:
FINISHED
DEL FILE:FILE=LG.;
command repetition
ACCEPTED
FILE
----------------@################
+
command repetition
EXECD
A30808-X3074-A473-2-7620
EY194 - 11
EMCYMN
;
command repetition
EXECD

entry.
Important:
command repetition
:
:
command repetition
15
b
STARTED
:
:
:
:
:
:
FINISHED
h ... 15
Delete old LOG files.

DEL FILE:FILE=TEMP.;
command repetition
ACCEPTED
FILE
----------------@################
+
command repetition
EXECD
Updating database is finished.
16
records was suppressed. This suppression is canceled again using the following
command.
;
command repetition
EY194- 12
EXECD
A30808-X3074-A473-2-7620
17
EMCYMN
Information.
following cases:
STATISTIC CHARGING
18
Decision.
Y h ... 19
N h ... 21
19
Information.
During account suspension no begin and end meter readings are displayed
20
b

command repetition
:
:
command repetition
A30808-X3074-A473-2-7620
ACCEPTED
:
:
:
:
:
:
EXECD
EY194 - 13
EMCYMN
21
b
List generations.
DISP GEN;
command repetition
HISTORY
SET REFGEN
----------+----------+---------+-----+-----------------+---+-----------@######### actgen
VALID
@##
@####### @####### @## @#######
@######### backgen
VALID
@##
@####### @####### @## @#######
@######### oldgold
VALID
@##
@####### @####### @## @#######
MERGED
merggen2
BLOCKED
@##
@####### @####### @## @#######
MERGED
merggen1
BLOCKED
@##
@####### @####### @## @#######
command repetition
EXECD
Important:
22

23
b

command repetition
:
:
command repetition
EY194- 14
ACCEPTED
:
:
:
:
:
:
EXECD
A30808-X3074-A473-2-7620
24
EMCYMN
Important note:
REWIND=YES;

(GEN=actgen).
D=YES;
command repetition
:
:
ACCEPTED
:
:
:
:
:
:
A30808-X3074-A473-2-7620
Y h ... 26
N h ... 25
EY194 - 15
EMCYMN
25

:
:
:
:
:
:
:
:
command repetition
EXECD
REWIND MT:MTD=00;
command repetition
EXECD

diagnostic center.
26
h ... 28

REWIND=YES;

(y=2, 3, .....,n)
:
:
:
:
:
:
command repetition
27
b
:
:
EXECD

REWIND MT:MTD=00;
command repetition
EXECD

diagnostic center.
EY194- 16
A30808-X3074-A473-2-7620
28
b
EMCYMN
List generations.
DISP GEN;
command repetition
HISTORY
SET REFGEN
----------+----------+---------+-----+-----------------+---+-----------@######### actgen
VALID
@##
@####### @####### @## @#######
@######### backgen
VALID
@##
@####### @####### @## @#######
@######### oldgold
VALID
@##
@####### @####### @## @#######
MERGED
merggen2
BLOCKED
@##
@####### @####### @## @#######
MERGED
merggen1
BLOCKED
@##
@####### @####### @## @#######
command repetition
EXECD
A30808-X3074-A473-2-7620
EY194 - 17
EMCYMN
29
Delete generations.
Important
exception of the current generation oldgold, are to be cancelled, i.e. the
cancelled.
DANGEROUS COMMAND CANGEN READY TO EXECUTE< READY TO EXECUTE<
;
command repetition
HISTORY
SET REFGEN
----------+----------+---------+-----+-----------------+---+-----------@######### actgen
VALID
@##
@####### @####### @## @#######
@######### backgen
VALID
@##
@####### @####### @## @#######
@######### oldgold
VALID
@##
@####### @####### @## @#######
MERGED
merggen2
BLOCKED
@##
@####### @####### @## @#######
MERGED
merggen1
BLOCKED
@##
@####### @####### @## @#######
PLEASE ENTER
(YES: +/NO: -)<
+
@#######
FILE:
---------------------------------------------------------------------@################
command repetition
EXECD

oldgold.
EY194- 18
A30808-X3074-A473-2-7620
30
EMCYMN
The disk which was switched off in a former procedure step is switched on,
initialized and configured.
command repetition
EXECD
INIT MD:MDD=0;
command repetition
EXECD
command repetition
EXECD

message is output:
31
b

RESET CFOPT;
command repetition
32
EXECD
command repetition
:
:
command repetition
33
...... TAB,
MMN:SW,
REC92
STARTED
:
:
:
:
:
:
FINISHED

h ... 34

h ... 34
A30808-X3074-A473-2-7620
EY194 - 19
EMCYMN
34
b
List generations.
DISP GEN;
command repetition
HISTORY
SET REFGEN
----------+----------+---------+-----+-----------------+---+-----------@######### oldgold
VALID
@##
@####### @####### @## @#######
command repetition
EXECD
35
i....MMN:SW,

PROC, SW210
36
i....MMN:SW,

PROC, SW231
37
Decision.
Y h ... 38
N h ... 39
Are individual call data administered in the exchange?
38

i....MMN:SW,
PROC, SW224
39
Decision.
EY194- 20
Y h ... 40
N h ... 43
A30808-X3074-A473-2-7620
40
EMCYMN

command repetition
:
:
command repetition
41
ACCEPTED
:
:
:
:
:
:
EXECD

Important note:
command repetition
:
:
command repetition
42
...... TAB,
MMN:SW,
METAP
STARTED
:
:
:
:
:
:
FINISHED

Important note:
PER=YES;
command repetition
...... TAB,
MMN:SW,
METAP
ACCEPTED
device.
A30808-X3074-A473-2-7620
EY194 - 21
EMCYMN
43
Decision.
44
Y h ... 44
N h ... 45
Patch treatment.
Important
45
End of procedure.
END
EY194- 22
A30808-X3074-A473-2-7620
3.11
EMCYMN
Total Shutdown / Partial Shutdown

EY350
3.11.1
Overview about the procedures EY350, EY360, EY370 and EY380

In the following an overview about the emergency situations and the corresponding
procedures is given.
Emergency situation
Shutdown
Return to normal
operation
Overheating / Partial Shutdown
EY350
EY360
Overheating / Total Shutdown
EY350
EY370
Power failure
Initiated by the
power failure
EY380
The combination of EY350 and EY370 may also be used, if a recovery from the background memories (according to EY130) was not successful. Especially if problems
occurred during loading of the peripheral units (LTGs).
3.11.2
General
This procedure describes the measures to be taken for partial or total removal from
service of the network node (PARTIAL SHUTDOWN or TOTAL SHUTDOWN).
The procedure should be used if the environmental temperature of the network node
exceeds a predetermined threshold level, and the overheating and consequent damage
of the installation are likely. This would typically occur as a result of a breakdown in the
air-conditioning unit.
The procedure is designed to allow either an immediate TOTAL SHUTDOWN, or, if
necessary, a PARTIAL SHUTDOWN at some point after which the network node can be
taken out of service. The course action chosen will depend on the circumstances.
PARTIAL SHUTDOWN is divided into 3 phases to ensure that switching operation is
restricted no more than is absolutely necessary:
Phase 1:
Disconnection of all redundant LTGs. (All destinations and subscribers

remain accessible after this step.)
Phase 2:
50% of the peripheral units (DLU, LTG) are disconnected. (Subscribers

and destinations with high priority remain accessible.)
Phase 3:
90% of the peripheral units (DLU, LTG) are disconnected. (Only

subscribers and destinations with high priority remain accessible.)
After one phase has been completed, the effectiveness of the measures taken is
assessed to decide whether or not the next phase is needed to prevent a further rise in
temperature.
A30808-X3074-A473-2-7620
EY350 - 1
EMCYMN
Phased PARTIAL SHUTDOWN is executed according to a Minimum Configuration List

(MCL) which exactly determines the peripheral units (DLU, LTG) to be disconnected in
each of the three phases. The list must be compiled according to each individual
network node.
The MINIMUM CONFIGURATION LIST must be created in advance for
each network node individually.
(PARTIAL SHUTDOWN can only be performed on the basis of a minimum
configuration list.)
Notes on the structure and preparation of the minimum configuration list are found in the
next section.
EY350- 2
A30808-X3074-A473-2-7620
3.11.3
EMCYMN
Notes on the preparation of the minimum configuration list
a)
Listing the DLUs with the associated LTGs:

Firstly a list of the DLUs with either the associated LTGs or with the associated LTG pairs should be compiled.
b)
Listing the destinations and routes (trunks):

A similar list is to be compiled for the destinations to be reached, associating
the proper LTGs to each destination and each inter-network node trunk,
respectively.
c)
Prioritizing the peripheral units:

The subscribers are to be divided into three classes of priority according to
their importance:
- Subscribers without priority
- Subscribers with priority
- Subscribers with high priority
Tab. 3.11.1 Creation of MINIMAL CONFIGURATION LIST (MCL).

The DLUs assigned to the different subscribers should be labelled with the corresponding priority according to these categories. Examples of subscribers with high
priority are: hospitals, emergency call numbers etc. (All LTGs are also divided up into
the three classes of priority, according to the priority of the subscribers that are
connected to them.)
Similarly, the destinations and inter-network node trunks should be divided into these
classes of priority. Examples of destinations with high priority are: those which must
always be accessible, signalling highways without alternative routes etc.
3.11.3.1
Important boundary conditions:

Subscribers and destinations with high priority must not occupy
more than 10% of the available periphery !
Subscribers and destinations with priority or even high priority
must not occupy more than 50% of the available periphery when
taken together !
The tables drawn up according to these boundary conditions can now be combined to
form one minimum configuration list (MCL) which serves as a reference for each
PARTIAL SHUTDOWN to be carried out.
A suggested layout for such a minimum configuration list is shown on the next page.
A30808-X3074-A473-2-7620
EY350 - 3
EMCYMN
3.11.4
Minimum Configuration List (MCL)
DLUs with high priority
Partial Shutdown PHASE 1
DLU
redundant LTG
LTG
destination with high priority

destination
LTG
redundant LTG

DLUs with priority
redundant LTG
destinations with priority

destination
LTG
redundant LTG

DLUs without priority
DLU
LTG
destinations without priority

destination
redundant LTG
redundant LTG
LTG
Tab. 3.11.2 Example of a minimum configuration list (MCL)
EY350- 4
A30808-X3074-A473-2-7620
EMCYMN
Entry criteria.
What kind of procedure run is to be done?
h ... 2
h ... 47
Procedure run after temperature rise

Procedure run after unsuccessful recovery (EY100)
Temperature rise
Detecting the following emergency situation:
i
3
The environmental temperature of the network node has risen (e.g. due to
failure of air conditioning).
The predetermined threshold level has already been exceeded !
The decision for a PARTIAL or TOTAL SHUTDOWN must be made in order to

prevent a further rise in temperature !
Improve ventilation.
Open all doors of the racks to improve ventilation if this has not already been
done!
4
b
Identify the name of the current generation.

DISP GEN;
command repetition
NAME OF CURRENT GENERATION: actgen
HISTORY
SET REFGEN
----------+----------+---------+-----+-----------------+---+-----------@######### @#######
@######## @##
@####### @####### @## @#######
@######### @#######
@######## @##
@####### @####### @## @#######
@######### @#######
@######## @##
@####### @####### @## @#######
command repetition
EXECD
From the NAME OF CURRENT GENERATION line in the above generation list
the name of the current generation <actgen> should be noted for further use
(manual start-up after restart according to EY370).
A30808-X3074-A473-2-7620
EY350 - 5
EMCYMN
Determination of the system status.
By using the following commands, the current system status can be obtained.
The system status prior to shutdown is termed default configuration. As part
of postprocessing after return to service (according to procedure EY360 or
EY370), the default configuration of the switching system must be restored.
STAT SSP;
command repetition
STAT CCG;
command repetition
EXECD
STAT SYP;
command repetition
EXECD
STAT DLU:DLU=X;
command repetition
EXECD
STAT LTG:LTG=X-X;
command repetition
EXECD
command repetition
EXECD
command repetition
EXECD
STAT SN;
command repetition
EXECD
STAT MB;
command repetition
EXECD
EXECD
Intermediate meter saving - CA files.
As a precaution, intermediate meter saving is implemented in order to avoid

loss of charge meter data; i.e., the current charge meter readings are transferred from the main memory to the corresponding files in the background
memories.
DISP FILE:FILE=CA.;
Are data for display available?
EY350- 6
Y h ... 7
N h ... 9
A30808-X3074-A473-2-7620
EMCYMN
CA files available.
command repetition
EXECD
@################## @#############################
FILE
GEN
SIZE VSN000
VSN001
CLASS TYPE
-----------------+--------+------+-------------+-------------+-----+---CA.ST.UCHA
@####### @##### @############ @############ @### @###
8
b
Save charge and statistic meters.

SAVE MET;
command repetition
:
:
command repetition
h ... 8
ACCEPTED
:
:
:
:
:
:
EXECD
h ... 10
No CA files available.
command repetition
EXECD
10
b
Intermediate metersaving - IA files.

DISP FILE:FILE=IA.;
Y h ... 11
N h ... 13
11
IA files available.
command repetition
EXECD
@################## @#############################
FILE
GEN
SIZE VSN000
VSN001
CLASS TYPE
-----------------+--------+------+-------------+-------------+-----+------------IA.ICAMA
@####### @##### @############ @############ @### @###
IA.ICINA
@####### @##### @############ @############ @### @###
IA.ICITR
@####### @##### @############ @############ @### @###
IA.ICMCR
@####### @##### @############ @############ @### @###
IA.ICMIR
@####### @##### @############ @############ @### @###
IA.ICOME
@####### @##### @############ @############ @### @###
----------
Remark:
A30808-X3074-A473-2-7620
h ... 12
EY350 - 7
EMCYMN
12
Saving individual call data to disk.
For each IA file output, the corresponding parameter <type> is to be determined

using the following table. The TRANS BUFFER command is to be executed
with the corresponding parameters (see table below):
IA filename
parameter <type>
IA.ICAMA
AMA
IA.ICINA
INA
IA.ICITR
ITR
IA.ICMCR
MCR
IA.ICMIR
MIR
IA.ICOME
OME
TRANS BUFFER:TYPE=type;
command repetition
13
EXECD
h ... 14
No IA files available.
command repetition
EXECD
14
b
Display IARSTAT measurement jobs.

DISP IARJOB;
Y h ... 15
N h ... 17
15
IR files available.
command repetition
EXECD
IARSTAT MEASUREMENT-JOBS
MTYPE
BEG
TER
JOBNO STATUS
FILENAME
-----------------------------------------------------------------------IARSTATx @#######@@# @#######@@# @###
@######### IR.Aryymmnn
:
:
:
:
:
:
:
:
16
b
Saving IR files to disk.

COPY IARACCT:MTYPE=IARSTATx;
command repetition
17
h ... 16
EXECD
h ... 18
No IR files available.
command repetition
EXECD
EY350- 8
A30808-X3074-A473-2-7620
18
b
EMCYMN
Saving history data (SG files) to disk:

DMP SGMSG;
NO OF STORED SAFEGUARDING MESSAGES TO WRITE INTO SG.OPER FILE: @###
command repetition
ACCEPTED
:
:
:
:
:
:
:
:
command repetition
EXECD
19
Decision block.
Which type of shutdown is to be carried out?
h ... 46
h ... 20
TOTAL SHUTDOWN is to be carried out:

PARTIAL SHUTDOWN is to be carried out:
20
Announcing PARTIAL SHUTDOWN.

Inform adjacent network nodes and subscribers with priority of the PARTIAL
SHUTDOWN.
21
PARTIAL SHUTDOWN: Reconfigure and switch off MDD-1.
On returning to service (after TOTAL SHUTDOWN), MDD-1 serves as a start-up

facility for recovery with specified conditions for the peripheral units. To avoid
modifying the content of MDD-1 with the following measures, MDD-1 is configured to MBL and switched off.
DANGEROUS COMMAND !
(YES: +/NO: -) <
+
command repetition
EXECD
Switch off the power supply to MDD-1.

22
PARTIAL SHUTDOWN of periphery according to MCL: PHASE 1.
Redundancy check of LTGs:
STAT LTG:LTG=X-X;
command repetition
NO: LTG CH0 CH1
---------------no. ost ost ost
@### @## @## @##
:
:
EXECD
NO: LTG CH0 CH1
---------------@### @## @## @##
@### @## @## @##
:
:
:
:
NO: LTG CH0 CH1

---------------@### @## @## @##
@### @## @## @##
:
:
NO: LTG CH0 CH1

---------------@### @## @## @##
@### @## @## @##
The status list should be evaluated in the following way:
A30808-X3074-A473-2-7620
EY350 - 9
EMCYMN
1. Identify all LTG pairs using the MCL.

2. The operational state of both LTGs of a pair may be obtained by examining
the column LTG in the list above.
3. Note all pairs with both LTGs in OST=ACT.
4. The LTG marked redundant LTG in the MCL of each pair noted under 3)
should be taken out of service: Switch off the corresponding power supplies
frame by frame without configuring the LTG.
Switch off the power supplies of all redundant LTGs (see above)
23
PARTIAL SHUTDOWN of switching network.
In order to reduce thermal stress, the following peripheral units should also be
taken out of service:
Disconnect extra equipment (if present), i.e., equipment that is not

part of the installation.
The following steps should be taken to identify the standby half (OST=STB) of
the switching network (SN). This half is configured to OST=MBL and switched
off:
STAT SN;
command repetition
TSG
------0-a ost
@## @##
SSG
------0-a ost
@## @##
EXECD
TSG
------1-a ost
@## @##
SSG
------1-a ost
@## @##
The SN half in OST=STB (half-x) is configured to MBL:
CONF SN:SN=x;OST=MBL;
command repetition
STARTING CONFIGURATION FOR SN -x
END OF CONFIGURATION FOR SN -x

command repetition
FROM STB TO MBL
FROM STB TO MBL

EXECD
STAT SN;
command repetition
TSG
------0-a ost
@## @##
SSG
------0-a ost
@## @##
EXECD
TSG
------1-a ost
@## @##
SSG
------1-a ost
@## @##
Switch off the power supply to the TSGs and SSGs in OST=MBL.
EY350- 10
A30808-X3074-A473-2-7620
24
EMCYMN
Partial Shutdown of the CP.
The given sequence must be followed !
CONF IOC:IOC=1,OST=MBL;
DANGEROUS COMMAND !
(YES: +/NO: -) <
+
command repetition
EXECD
CONF CMY:CMY=1,OST=MBL;
DANGEROUS COMMAND !
(YES: +/NO: -) <
+
command repetition
EXECD
CONF BCMY:BCMY=1,OST=MBL;
DANGEROUS COMMAND !
(YES: +/NO: -) <
+
command repetition
EXECD
CAPs (if present) :

The maximum amount of CAPs that may be configured to OST=MBL is dependent on the call processing load. Ensure that the system - even without the
CAPs configured to OST=MBL - does not overload !
For each CAP labelled as dispensable the following command should be
executed:
CONF CAP:CAP=x,OST=MBL;
DANGEROUS COMMAND !
(YES: +/NO: -) <
+
command repetition
25
b
EXECD
Check the status of the configured CP units:

STAT SSP;
command repetition
UNIT
OST
-----------------BAP-0
ost
:
:
EXECD
UNIT
OST
-----------------BAP-1
ost
:
:
:
:
UNIT
OST
-----------------@#########
@@##
:
:
Which type of coordination processor is used in the network node?

CP113C is in use:
CP113D is in use:
A30808-X3074-A473-2-7620
h ... 26
h ... 27
EY350 - 11
EMCYMN
26
CP113C is in use.
Execute the following steps in the given sequence !
Switch off power supply to IOC-1 (OST=MBL).

(IOC-1 and the corresponding IOPs are switched off).
Switch off power supply to CMY-1 (OST=MBL).
Switch off power supply to BCMY-1 (OST=MBL).
Switch off power supply to all present CAPs in OST=MBL.
h ... 28
27
CP113D is in use
Execute the following steps in the given sequence !
Switch off power supply to IOC-1 (OST=MBL).

Switch off power supply to CMY-1 (OST=MBL).
Switch off power supply to BCMY-1 (OST=MBL).
Switch off power supply to all present CAPs in OST=MBL.
h ... 28
28
Switch off BAP-SPARE
The BAP-x (OST=SPR) configured as SPARE should be identified from the CP

status list.
CONF BAP:BAP=x,OST=MBL;
DANGEROUS COMMAND !
(YES: +/NO: -) <
+
command repetition
EXECD
Switch off the power supply to BAP-x (OST=MBL).

29
Decision block.
PARTIAL SHUTDOWN according to MCL phase 1 is completed. After a reasonable amount of time has passed, the following question must be answered:
Has PARTIAL SHUTDOWN phase 1 averted the danger of overheating?
EY350- 12
Y h ... 30
N h ... 31
A30808-X3074-A473-2-7620
30
EMCYMN
Environmental temperature does not rise any further.
Having implemented the measures for PARTIAL SHUTDOWN phase 1, the

temperature in the network node has fallen, or at least has not risen any further.
The cause for PARTIAL SHUTDOWN must be removed (e.g., the air-conditioning must be fixed). A PARTIAL RESTART must then be executed according
to procedure EY360 !
31
h ... 52
Environmental temperature still rises.
Despite the measures already taken, the temperature in the network node
continues to rise.
Decision for PARTIAL SHUTDOWN phase 2 !
32
h ... 32
PARTIAL SHUTDOWN of periphery according to MCL, phase 2.
Switch off DLU:

1. Identify all DLU units corresponding to phase 2 in the MCL.
2. These units must be taken out of service without configuration:
Switch off the corresponding power supplies frame by frame.
(Only DLU with priority or high priority remain connected!)
Switch off LTG:

1. Identify all LTG units corresponding to phase 2 in the MCL.
(Only LTG with priority or high priority remain connected!)
33
Decision block.
PARTIAL SHUTDOWN according to MCL phase 2 is completed. Only 50% of

the available periphery (DLU, LTG) is operational. After a reasonable amount of
time has passed, the following question must be answered:
34
Y h ... 34
N h ... 35

temperature in the network node has fallen, or at least does not rise further.
A30808-X3074-A473-2-7620
h ... 52
EY350 - 13
EMCYMN
35
Environmental temperature continues to rise.
continues to rise.
h ... 36
Decision for PARTIAL SHUTDOWN phase 3 !
36
PARTIAL SHUTDOWN of periphery according to MCL, phase 3.

Switch off DLU:
1. Identify all DLU units corresponding to phase 3 in the MCL.
(Only DLUs with priority or high priority remain connected!)

Switch off LTG:
1. Identify all LTG units corresponding to phase 3 in the MCL.
(Only LTGs with priority or high priority remain connected!)
37
Decision block.
PARTIAL SHUTDOWN according to MCL phase 3 is completed. Only 10% of

the available periphery (DLU, LTG) is operational. After a reasonable amount of
time has passed, the following question must be answered:
Y h ... 38
N h ... 39
38

temperature in the network node has fallen, or at least does not rise further.
39
h ... 52
Environmental temperature continues to rise.
continues to rise.
h ... 40
Decision for TOTAL SHUTDOWN !
40
Announcing TOTAL SHUTDOWN.

Informing adjacent network nodes and subscribers with priority (e.g. hospitals,
emergency numbers) of TOTAL SHUTDOWN.
EY350- 14
A30808-X3074-A473-2-7620
41
EMCYMN
TOTAL SHUTDOWN after preceding PARTIAL SHUTDOWN:
Switch off power supply to BAP-MASTER (OST=MAS).

CP113C is in use:
CP113D is in use:
42
h ... 42
h ... 43
CP113C is in use.
Switch off power supplies to the following units in the given sequence !
MDD-0
IOC-0 (including IOPs)*
BCMY-0
CMY-0
*Also switch off IOC-2 and IOC-3, if present.
Switch off power supply to all CAPs that are still switched on.
h ... 44
43
CP113D is in use.
MDD-0
IOC-0*
BCMY-0**
CMY-0
IOP frames
*Also switch off IOC-2 and IOC-3, if present.

**BCMY modules in R:CP113B should also be switched off by disconnecting the
corresponding voltage converter.
Switch off power supply to all CAPs that are still switched on.
h ... 44
A30808-X3074-A473-2-7620
EY350 - 15
EMCYMN
44
!
Switch off all peripheral units.

The power supply to the CCG in the R:MB must not be switched off, as otherwise much time must be spent on synchronization after restarting.
Exeption:
If this procedure is called by procedure EY100 (no temperature rise) the CCG
has to be switched off also.
All peripheral units that have not yet been switched off should be disconnected in the following sequence by switching off the corresponding power
supplies:
45
all DLUs
all LTGs
CCNC
SSG
TSG
MB
SYP
Note block.
The cause for TOTAL SHUTDOWN must be removed (e.g., the air-conditioning
must be repaired). A TOTAL RESTART must then be executed according to
procedure EY370 !
46
h ... 52
Announcing TOTAL SHUTDOWN.

Informing adjacent network nodes and subscribers with priority (e.g., hospitals,
emergency numbers) of TOTAL SHUTDOWN.
47
TOTAL SHUTDOWN of CP.
The given sequence must be followed! (In case of procedure run after unsuccessful recover (EY100) the following commands can not be executed.
Configure and switch off MDD-1:
On returning to service (after TOTAL SHUTDOWN), MDD-1 serves as a startup
facility for recovery with specified conditions for the peripheral units.
To avoid modifying the content of MDD-1 with the following measures, MDD-1 is
switched off.
DANGEROUS COMMAND !
(YES: +/NO: -) <
+
command repetition
EY350- 16
EXECD
A30808-X3074-A473-2-7620
EMCYMN
Switch off power supply to MDD-1.

Identify BAP-SPARE and BAP-MASTER:
STAT SSP;
command repetition
UNIT
OST
-----------------BAP-0
ost
:
:
EXECD
UNIT
OST
-----------------BAP-1
ost
:
:
:
:
UNIT
OST
-----------------@#########
@@##
:
:
Switch off units in the given sequence !
Switch off power supply to BAP-SPARE (OST=SPR).

Switch off power supply to BAP-MASTER (OST=MAS).
Switch off power supply to MDD-0.
CP113C is in use:
CP113D is in use:
48
h ... 48
h ... 49
CP113C is in use.
Switch off power supplies to all units of the specified type in the given sequence!
IOC (including IOPs)

BCMY
CMY
CAPs (if present)
h ... 50
49
CP113D is in use.
IOC
BCMY*
CMY
IOP frames
CAPs (if present)
*If present, the BCMY modules in R:CP113B should also be switched off by
disconnecting the corresponding voltage converter.
A30808-X3074-A473-2-7620
EY350 - 17
EMCYMN
50
!
TOTAL SHUTDOWN of periphery.

The power supply to the CCG in the R:MB must not be switched off, as otherwise much time must be spent on synchronization after restarting.
The peripheral units should be switched off frame by frame via the corresponding power supplies in the following sequence !
all DLUs
all LTGs
CCNC
SSG
TSG
MB
SYP
Disconnection of extra equipment that may be present (non EWSD).
51
Note block.
The cause for TOTAL SHUTDOWN must be removed (e.g., the air-conditioning
must be repaired). A TOTAL RESTART must then be executed according to
procedure EY370 !
52
h ... 52
End of procedure.
END
EY350- 18
A30808-X3074-A473-2-7620
3.12
EMCYMN
Partial Restart after Partial Shutdown

EY360
3.12.1
General
This procedure should be applied after a PARTIAL SHUTDOWN (PS) due to excessive
temperature has been executed according to procedure EY350 and the cause for the
excessive temperature (e.g., faulty air-conditioning) has been removed.
This procedure describes all the measures necessary for returning the network node
which has been partially switched off to normal operation.
Once the peripheral units have again been fully switched on and the CP has been
almost completely switched on, one has to decide on further measures:
Alternative 1:
Only a few LTGs have been switched off. In this case it is better to configure the
peripheral units manually. A total outage of the system can be avoided.
Alternative 2:
An ISTART2R is initiated by MML command:
with MDD-0
with current generation
all LTGs are reloaded
After restarting the system, an attempt must be made to restore the status of the network
node prior to shutdown (default configuration) by manual post-processing. The necessary information on the system status is obtained by analyzing the recovery report and
by making inquiries regarding the system status. The objective is to return all units to
their original operational status. CP redundancy is then completed by returning
MDD-1 and BAP-x to service.
A30808-X3074-A473-2-7620
EY360 - 1
EMCYMN
Cause for shutdown removed.

Prerequisites:
1. The cause for the excessive temperature which led to the shutdown of the
network node has been removed (e.g., the air-conditioning has been
repaired).
2. The temperature has fallen below the threshold level.
Deciding on system start-up measures.

In what condition is the network node?
h ... 3
PARTIAL SHUTDOWN was executed; the network node is operating while

remaining partially switched off.
h ...EMCYMN,
A PARTIAL SHUTDOWN was carried out initially, and at some later stage a
TOTAL SHUTDOWN was executed. The network node has been completely
shut down.
PROC, EY370
Switching on periphery.
The peripheral units that were taken out of service during PARTIAL SHUTDOWN are to be switched on again frame by frame via the corresponding power
supplies in the following sequence !
Switch on power supplies of:
all DLUs
all LTGs
SSG
TSG
Since it takes some time for the LTGs to reach a specified restart status, it will
take about 5 minutes to reach recovery after switching on the LTGs.
Switch on power supply to extra equipment (if present).

4
Switching on CP.
When switching on the CP the given sequence must be followed to ensure a

safe restart !
BAP-x and MDD-1 remain without power !
Which type of coordination processor is used in the network node ?
CP113C is used:
CP113D is used:
EY360- 2
h ... 5
h ... 6
A30808-X3074-A473-2-7620
EMCYMN
CP113C is in use.
After the BCMY and CMY modules have been switched on, the operator must
wait until test routines have been completed and a constant green light (MSTLED) appears on each module.
Switch on power supply to BCMY-1.

Switch on power supply to CMY-1.
Switch on power supply to IOC-1 (including IOPs).
Switch on power supply to all CAPs which were switched off.
h ... 7
6
CP113D is in use.
Switch on power supply to BCMY-1 (also in R:CP113B, if present).

Switch on power supply to CMY-1.
Switch on power supply to IOC-1.
Switch on power supply to all CAPs which were switched off.
h ... 7
7
Activate peripheral units.
There exist two alternatives to put the peripheral units back to service:
1st alternative:
Configure the peripheral units manually (only a few units

are switched off).
advantage:
No downtime of the system. (Restricted switching operation

during manual post processing).
disadvantage:
Time consuming activities to restore default configuration

(long outage time for affected trunks and subscribers).
2nd alternative:
Initiate ISTART2R via MML command.
advantage:
All peripheral units are put back to service automatically.
disadvantage:
The system outage time is at least 10 minutes and may

increase in dependence on the installed capacity of the
network node.
1st alternative (manual configuration of peripheral units). If only a few units

are out of service this alternative should be preferred:
2nd alternative (ISTART2R):
A30808-X3074-A473-2-7620
h ... 8
h ... 9
EY360 - 3
EMCYMN
Returning the entire periphery to service (manually).
The current system status is obtained by using the following status inquiries.
All units which do not have the same operational state as they had before the
partial shutdown, must be configured, in order to reestablish the default
configuration.
STAT SSP;
command repetition
STAT CCG;
command repetition
EXECD
STAT SYP;
command repetition
EXECD
STAT DLU:DLU=X;
command repetition
EXECD
STAT LTG:LTG=X-X;
command repetition
EXECD
command repetition
EXECD
command repetition
EXECD
STAT SN;
command repetition
EXECD
STAT MB;
command repetition
EXECD
EXECD
h ... 15
Returning the entire periphery to service (ISTART2R).
To return the entire periphery to service, an ISTART2R (unconditional loading of

periphery) is initiated via MML command:
RECOV SYSTEM:LEVEL=ISTART2R;
DANGEROUS COMMAND RECOVSYSTEM READY TO EXECUTE<
EY360- 4
A30808-X3074-A473-2-7620
10
EMCYMN
Recovery report.

FCP RECOVERY REPORT
OST LOAD DEVICE
-------+----+----------MDD-00 ACT YES
MDD-01 NAC NO
ACTUAL GENERATION
: NAME
CREATION DATE
LAST CREATED
---------+------------------+-----------actgen
@####### @####### @##
SYSTEM - RECOVERY
DATE
TIME
PERFORMED LEVEL
PERFORMED ACTION(S)
APS GENERATION
ALARM
MMN:SW330-0001
:
:
:
:
@#######@
@#######@
ISTART2R
@############################################
@##############################
: actgen
FCP UPDATE REPORT

JOBNO= @###
FILENAME:
GENERATION:
----------------------------------@################
actgen
#####
#####
#####
#####
#####
#####
#####
#####

:
:
:
:
:
:
END OF LTG LOADING
#####
#####
#####
#####
#####
#####
#####
#####
A30808-X3074-A473-2-7620
EY360 - 5
EMCYMN
REASON
: REQUIRED MML START

@#######################################
: @#######@
: @#######@
: BAPM
DATE
TIME
UNIT
REQUESTED LEVEL
PERFORMED LEVEL
PERFORMED ACTION(S)
: ISTART2R
: ISTART2R
: @##############################################
@##############################
RECOVERY DURATION
: @###@
SECONDS
APS GENERATION
: @#######
STATISTICS

THRESHOLD
: @###
INTERVAL
: @#### SEC
EXCEPTIONS
==========

DURING RECOVERY
UNIT
---@########
11
UNIT
---@########
UNIT
---@########
UNIT
---@########
UNIT
---@########
Evaluate recovery report.
Firstly, the system status is determined in order to be able to restore the original
condition of the network node prior to shutdown (default configuration).
Identify those units which could not be configured without error during POSTPROCESSING.
SYSTEM - RECOVERY
POST-PROCESSING FINISHED
DATE:
@#######@
TIME: @#######@
CONFIGURATION FAILURES DURING POSTPROCESSING:

UNIT:
----@########
UNIT:
----@########
UNIT:
----@########
UNIT:
----@########
UNIT:
----@########
All units displayed should be noted and activated later on in this procedure.
EY360- 6
A30808-X3074-A473-2-7620
12
EMCYMN
is executed.
13
b
Determine CP status.
STAT SSP;
command repetition
14
EXECD
h ... 14
Determine system status of periphery.
The current system status is obtained by using the recovery report and the
following status enquiries:
STAT CCG;
command repetition
STAT MB;
command repetition
EXECD
STAT DLU:DLU=X;
command repetition
EXECD
STAT LTG:LTG=X-X;
command repetition
EXECD
command repetition
EXECD
command repetition
EXECD
STAT SN;
command repetition
EXECD
EXECD
STAT SYP;
command repetition
A30808-X3074-A473-2-7620
EXECD
EY360 - 7
EMCYMN
15
Restoring default configuration.

To create default configuration:
Compare the current system status with the default configuration (see
EY350).
Restore the default configuration; faults may have to be cleared.
The order in which measures are taken to clear any faults must be determined by the situation.
If fault clearance is time-consuming, give priority to the return to service of
MDD-1 and BAP-x (see the following blocks) in order to complete CP redundancy as quickly as possible.
All units that are still deactivated are to be taken into service again.
Clear all defective units of faults and then return them to service.
16
Return BAP-x to service.
Switch on power supply to BAP-x.

b
CONF BAP:BAP=x,OST=SPR;
DANGEROUS COMMAND !
+
command repetition
17
(YES: +/NO: -) <
EXECD
Return MDD-1 to service.
Switch on power supply to MDD-1.

b
command repetition
EXECD
The copying from MDD-0 to MDD-1 is started immediately after the configuration command is positively acknowledged. End of copying is indicated by the
message:
EY360- 8
A30808-X3074-A473-2-7620
18
b
EMCYMN
List and delete alarms.

command repetition
EXECD
OBJECT =
ALTYPE =
PABCAUSE=
ALARM-ID:
RECOV
ALPRIO = @####### ALSTAT = @# MSGNO = msgno
@#######################
@#################################################
@#############################################################
OBJECT =
ALTYPE =
PABCAUSE=
ALARM-ID:
RECOV
ALPRIO = MAJOR
ALSTAT = NP MSGNO = msgno
@#######################
@#################################################
CLASS=ISTART
OBJECT =
ALTYPE =
PABCAUSE=
ALARM-ID:
RECOV
ALPRIO = @####### ALSTAT = @# MSGNO = msgno
@#######################
@#################################################
@#############################################################
The following command is to be executed with all message numbers <msgno>

belonging to the category ALPRIO=MAJOR and assigned to an ISTART
message:
command repetition
EXECD
Further alarm entries can be displayed using the MML command DISP
ALARM;. Once any faults in the units have been successfully cleared, the corresponding alarm entry must be reset in the same way as OBJECT=RECOV.
19
Close rack doors.

Close the doors which were opened during the period of excessive temperature
(if this has not yet been done).
END
A30808-X3074-A473-2-7620
EY360 - 9
EMCYMN
EY360- 10
A30808-X3074-A473-2-7620
3.13
EMCYMN
Total Restart after Total Shutdown

EY 370
3.13.1
General
This procedure describes all the measures which must be taken to return the network
node to normal service after a total shutdown. The order in which they are given here
must be followed strictly. Once the peripheral units have again been fully switched on
and the CP has been almost completely switched on, a manual restart is executed with
the current generation:
1. Format memory
2. Restart with current generation
3. Restart with MDD-1 (basis for restart)
4. All LTGs are reloaded
After restarting the system, an attempt must be made to restore the status of the network
node prior to shutdown (default configuration) by manual post-processing. The necessary information on the system status is obtained by analyzing the recovery report and
by making enquiries regarding the system status. The objective is to return all units to
their original operational status. CP redundancy is then completed by returning
MDD-0 and BAP-1 to service.
A30808-X3074-A473-2-7620
EY370 - 1
EMCYMN
Cause for shutdown removed.

Prerequisites:
1. The cause for the excessive temperature which led to the shutdown of the
network node has been removed (e.g., the air-conditioning has been
repaired).
2. The temperature has fallen below the threshold level.
3. The network node has been completely switched off.
Switching on periphery.
All peripheral units must be switched on again via the corresponding power
supplies in the following sequence ! (If this procedure is called by procedure
EY100 (no temperature rise) the CCG has to be switched on also.)
Switch on peripheral units:
all DLUs
all LTGs
CCNC
SSG
TSG
MB
SYP
Since it takes some time for the LTGs to reach a specified restart status, it will
take about 5 minutes to reach recovery after switching on the LTGs.
Switch on power supply to extra equipment (if present).

3
Switching on CP (part 1).
When switching on the CP the given sequence must be followed to ensure a

safe restart !
BAP-0, BAP-1 and MDD-0 remain without power !

CP113C is used:
CP113D is used:
EY370- 2
h ... 4
h ... 6
A30808-X3074-A473-2-7620
EMCYMN
CP113C is in use.
After the BCMY and CMY modules have been switched on, the operator must
wait until test routines have been completed and a constant green light (MSTLED) appears on each module.
Switch on power supply to all BCMYs.

Switch on power supply to CMYs.
Switch on power supply to IOCs (including IOPs).
Switch on power supply to all present CAPs.
h ... 5
5
CP113C is in use: Switching on CP (part 2).
The trace points may only be displayed when the maintenance panel has been
appropriately connected to BAP-0.
Switch on power supply of BAP-0 and press BOOT key after trace point A8C5 is
displayed (trace point A885 is displayed for approx. 10 sec.).
After that the interactive mode (A925) is initiated.
If trace point A925 is passed over, automatic recovery will be initiated.
Since manual recovery is required, the system has to be restarted (BOOT key
on BAP-0) !
Switch on power to BAP-0.

During the processing of the next two blocks FORMAT;, ; and MAN; have to
be entered immediately after the corresponding input request is displayed.
h ... 8
CP113D is in use.
Switch on power supply to all BCMYs (also in the R:CP113B, if

present).
Switch on power supply to CMYs.
Switch on power supply to IOCs.
Switch on power supply to IOP frames.
Switch on power supply to all present CAPs.
h ... 7
A30808-X3074-A473-2-7620
EY370 - 3
EMCYMN
CP113D is in use: Switching on CP (part 2).
Switch on power supply of BAP-0 and press BOOT key after trace point A8C5 is
displayed (trace point A885 is displayed for approx. 10 sec.).
After that the interactive mode (A925) is initiated.
If trace point A925 is passed over, automatic recovery will be initiated.
Since manual recovery is required, the system has to be restarted (BOOT key
on BAP-0) !
Switch on power to BAP-0.

EY370- 4
A30808-X3074-A473-2-7620
EMCYMN
Manual bootstrap - parameter supply.

UNIT
STATUS
TEST
********************************************
BAP-0
@#####
@#####
BAP-1
@#####
@#####
B:CMY-0
@#####
@#####
B:CMY-1
@#####
@#####
CMY-0
@#####
@#####
CMY-1
@#####
@#####
IOC-0
@#####
@#####
IOC-1
@#####
@#####
TO DIAGNOSE MEMORY
TO FORMAT MEMORY
TO CONTINUE
:
:
:
DIAG;
FORMAT;
;ETX
FORMAT;
UNIT
STATUS
TEST
********************************************
BAP-0
@#####
@#####
BAP-1
@#####
@#####
B:CMY-0
@#####
@#####
B:CMY-1
@#####
@#####
CMY-0
@#####
@#####
CMY-1
@#####
@#####
IOC-0
@#####
@#####
IOC-1
@#####
@#####
TO DIAGNOSE MEMORY
TO FORMAT MEMORY
TO CONTINUE
:
:
:
DIAG;
FORMAT;
;ETX
;
TO
TO
TO
TO
TO
START APS MANUALLY

STOP INITIAL START
:
:
:
:
:
MANUALLY;
INSTALLATION;
UTILITY;
STOP;
;ETX
MAN;
A30808-X3074-A473-2-7620
EY370 - 5
EMCYMN
Manual bootstrap - initialise manual restart.

@#############
actgen
@#######################
------backgen
@#######################
------goldgen
@#######################
MANUAL RECOV. - LOADING VIA IOC :
IOC-0;/IOC-1;
Remark:
IOC-1;
LOAD.DEV.=*MDD1* -GENERATION TO LOAD : NAME;(8 CHAR)
The generation name <actgen> was already noted at the beginning of shutdown
(see EY350). However, the name can also be found in the printout above.
actgen;
MANUAL RECOVERY - LTG LOADING :Y;/N;
Y;
EY370- 6
A30808-X3074-A473-2-7620
10
EMCYMN
Recovery report.

SYSTEM - RECOVERY
DATE
TIME
PERFORMED LEVEL
PERFORMED ACTION(S)
ALARM
APS GENERATION
MMN:SW330-0001
:
:
:
:
@#######@
@#######@
ISTART2
@##############################
: actgen
FCP RECOVERY REPORT

OST LOAD DEVICE
-------+----+----------MDD-00 NAC NO
MDD-01 ACT YES
ACTUAL GENERATION
#####
#####
#####
#####
#####
#####
#####
#####
: NAME
CREATION DATE
LAST CREATED
---------+------------------+-----------actgen
@####### @####### @##

:
:
:
:
:
:
END OF LTG LOADING
#####
#####
#####
#####
#####
#####
#####
#####

REASON
DATE
TIME
UNIT

@#######################################
: @#######@
: @#######@
: BAPM
REQUESTED LEVEL
: ISTART2
A30808-X3074-A473-2-7620
EY370 - 7
EMCYMN
PERFORMED LEVEL
PERFORMED ACTION(S)
: ISTART2
@##############################
RECOVERY DURATION
: @###@
SECONDS
APS GENERATION
: @#######
STATISTICS

THRESHOLD
: @###
INTERVAL
: @#### SEC
EXCEPTIONS
==========

DURING RECOVERY
UNIT
---@########
11
UNIT
---@########
UNIT
---@########
UNIT
---@########
UNIT
---@########
is executed.
12
b
Display system time.

DISP TIME;
command repetition
DATE
@#######
13
TIME
@#######
EXECD
DAY
@#
h ... 13
mode
Check system time.
Y h ... 15
N h ... 14
Do system time and local time correspond?
14
b
Enter new system time.

ENTR TIME:DATE=yy-mm-dd,TIME=hh-mm-ss,WD=wd;
command repetition
DATE
@#######
15
TIME
@#######
EXECD
DAY
@#
INSECURE
Check mode of system time.

Is mode of system time SECURE?
EY370- 8
Y h ... 17
N h ... 16
A30808-X3074-A473-2-7620
16
b
EMCYMN
Change mode of system time to SECURE.

CORR TIME:MODE=SECURE;
DANGEROUS COMMAND CORRTIME READY TO EXECUTE<
;
command repetition
DATE
@#######
17
EXECD
TIME
@#######
DAY
@#
SECURE
Firstly, the system status is determined in order to be able to restore the original
condition of the network node prior to shutdown (default configuration).
SYSTEM - RECOVERY
DATE:
@#######@
TIME: @#######@

UNIT:
----@########
UNIT:
----@########
UNIT:
----@########
UNIT:
----@########
UNIT:
----@########
All units displayed should be noted and activated later on in this procedure.
A30808-X3074-A473-2-7620
EY370 - 9
EMCYMN
18
Determine status of periphery and CP.
STAT SSP;
command repetition
STAT CCG;
command repetition
EXECD
STAT SYP;
command repetition
19
EXECD
STAT DLU:DLU=X;
command repetition
EXECD
STAT LTG:LTG=X-X;
command repetition
EXECD
command repetition
EXECD
command repetition
EXECD
STAT SN;
command repetition
EXECD
STAT MB;
command repetition
EXECD
EXECD

To create default configuration:
Compare the current system status with the default configuration (see
EY350).
The order in which measures are to be taken to clear any faults will be determined by the situation.
If fault clearance is time-consuming, give priority to the return to service of
MDD-0 and BAP-1 (see following blocks) in order to complete CP redundancy as quickly as possible.
EY370- 10
A30808-X3074-A473-2-7620
20
EMCYMN
Return BAP-1 to service.
Switch on power supply to BAP-1.

b
DANGEROUS COMMAND !
+
command repetition
21
(YES: +/NO: -) <
EXECD
Return MDD-0 back to service.

b
command repetition
EXECD
command repetition
EXECD
The copying from MDD-1 to MDD-0 is started immediately after the configuration command is positively acknowledged. End of copying is indicated by the
message:
A30808-X3074-A473-2-7620
EY370 - 11
EMCYMN
22
b
List and delete alarm(s).

command repetition
EXECD
OBJECT =
ALTYPE =
PABCAUSE=
ALARM-ID:
RECOV
ALPRIO = @####### ALSTAT = @# MSGNO = @####
@#######################
@#################################################
@#############################################################
OBJECT =
ALTYPE =
PABCAUSE=
ALARM-ID:
RECOV
ALPRIO = MAJOR
@#######################
@#################################################
CLASS=ISTART
OBJECT =
ALTYPE =
PABCAUSE=
ALARM-ID:
RECOV
@#######################
@#################################################
@#############################################################
The following command is to be executed with all message numbers (msgno)

belonging to the category ALPRIO=MAJOR and assigned to the ISTART
message.
command repetition
EXECD
Further alarm entries can be displayed using the MML command DISP ALARM;.
Once any faults in the units have been successfully cleared, the corresponding
alarm entry must be reset in the same way as OBJECT=RECOV.
23
Close rack doors.

Close the doors which were opened during the period of excessive temperature
(if this has not yet been done).
END
EY370- 12
A30808-X3074-A473-2-7620
3.14
EMCYMN
Measures after a power failure

EY380
3.14.1
General
The aim of this procedure is to support the service personnel after a power failure to
bring the network node back to normal service. The current status of the network node
is to be analyzed. In a second step a decision about the next measures is to be made.
After a power failure the system reacts automatically with a recovery, after returning of
power. Since the peripheral units (LTGs) need some time for diagnosis measures, it is
likely that the periphery is not completely working after the recovery.
In order to reduce down time for subscribers and trunks which were not automatically
taken back to service after the automatic recovery, the decision is to be made whether
a manual recovery should be initiated. Within the manual recovery most LTGs will be
activated (self-diagnosis of the LTGs is finished).
The activities of the service personnel depend on the current system status. There are
two main points which must be evaluated:
1. Status of peripheral units
2. Determine the name of the current generation:
evaluate the recovery printout
determine the current generation (ISTART2G during automatic recovery ?)
In the following table the manual measures are described, depending on the system
status after the automatic recovery (current system status):
periphery status:
almost all LTGs are active
only a few LTGs are

active
Current generation after actgen *)

automatic recovery:
backgen /
goldgen
proposed measures:
initiate a manual recovery, using

generation <actgen> (load LTGs with
code and data)
activate inactive
units by manual
configuration
actgen / backgen /
goldgen
*) If an ISTART2G was executed, post-processing according to procedure EY190EY194 is to be executed.
3.14.2

A30808-X3074-A473-2-7620
EY380 - 1
EMCYMN
Entry situation.
This procedure should be used if the following events have occurred:
Power failure
A power failure caused a total break down of the switching system.
Automatic recovery after returning of power

After the power returned, the system reacted by executing an automatic
recovery. The central units are available a short time after the power has
returned. The LTGs need some minutes for diagnosis-measures after power
returned. This could lead to a situation that only a few peripheral modules
(LTGs, DLUs etc.) are active after the automatic recovery is finished.
Analyze the current status of the LTGs

In order to reduce the downtime, the current status of the peripheral units is
to be analyzed. If only a few LTGs are active, another manual recovery is to
be initiated. Within the recovery all LTGs are loaded with code and data.
Since the time interval between the returning of power and this manual
recovery is long enough to finish all diagnosis measures of the peripheral
units, (almost) all LTGs will be reactivated within the manual recovery.
(The manual configuration of the units will take too much time !)
The main aim of this procedure is to decide, whether or not a manual recovery
should be initiated in order to reduce system downtime !
Decision.
Y h ... 4
N h ... 3
Is a session already established ?
is executed.
4
b
Check current status of peripheral units (LTGs).

STAT LTG:LTG=X-X;
command repetition
NO: LTG CH0 CH1
---------------no. ost ost ost
@### @## @## @##
:
:
EY380- 2
EXECD
NO: LTG CH0 CH1
---------------@### @## @## @##
@### @## @## @##
:
:
:
:
NO: LTG CH0 CH1

---------------@### @## @## @##
@### @## @## @##
:
:
NO: LTG CH0 CH1

---------------@### @## @## @##
@### @## @## @##
h ... 5
A30808-X3074-A473-2-7620
EMCYMN
Evaluate the current status of the peripheral units.
The printout of the LTGs and their current status is to be evaluated. There exist
two different possibilities to reactivate LTG units.
1. Reactivate inactive LTGs manually:
Inactive units can be configured via MML command. This takes several
minutes for each inactive LTG. In order to reduce the downtime the manual
configuration should only be applied, if only a few LTGs are inactive.
Inactive LTGs are reactivated by the system within the post-processing
measures after the automatic recovery. This takes several minutes for
each inactive LTG.
2. Initiate a manual recovery including LTG loading:
If many LTGs are inactive, a manual recovery (ISTART2) should be initiated. During the recovery all LTGs will be reloaded. The recovery duration
is at least 10 minutes and may increase in dependence on the installed
capacity of the network node.
After this time all peripheral units should be active again.
The manual recovery is initiated several minutes after the power returned.
This means that all LTGs are prepared for the recovery, i.e. the diagnosis
measures of the LTGs are finished.
The decision about all further measures depends on the number of inactive
LTGs. The total downtime of at least 10 minutes in the case of a manual
recovery is to be compared with the time for the manual configuration of single
LTGs.
Decision about further measures.

After evaluating the periphery status and comparing the system downtime by
regarding alternative 1) and 2) the decision about further measures is to be
made:
The (few) inactive LTGs should be reactivated by manual configuration.
(Long outage time for affected subscribers and trunks).
h ... 7
A manual recovery should be initiated. After a total downtime of at least 10

minutes (the recovery duration depends on the installed capacity of the
network node), (almost) all LTGs will be in OST=ACT again.
h ... 12
A30808-X3074-A473-2-7620
EY380 - 3
EMCYMN
7
b
List generations:
DISP GEN;
command repetition
HISTORY
SET REFGEN
----------+----------+---------+-----+-----------------+---+-----------@######### actgen
@######## @##
@####### @####### @## @#######
------@######### backgen
@######## @##
@####### @####### @## @#######
------@######### oldgold
@######## @##
@####### @####### @## @#######
command repetition
EXECD
Remark:
OF CURRENT GENERATION and LIST OF GENERATIONS )? (This is the
generation which was successfully used by the preceding ISTART2 / 2G.)

Startup with generation <actgen> (= the generation which was active before
the ISTART2/2G was carried out) was successful.
h ... 8

Fallback to the last backup generation <backgen>.
h ... 11

Fallback to the last backup generation <backgen> was not successful
but
fallback to the last backup generation <oldgold>, i.e. golden generation of
the last quarterly saving, was successful.
h ... 11
Current generation: <actgen>.
The system is running with generation <actgen>. In order to determine whether

an ISTART2G was executed or not the printouts of the automatic recovery
(RECOVERY INFORMATION, RECOVERY REPORT, etc.) are to be evaluated.
In addition an ISTART2G is indicated by a critical alarm at the SYP panel
(RECOVERY).
Was an ISTART2G executed during the automatic recovery ?
EY380- 4
Y h ... 10
N h ... 9
A30808-X3074-A473-2-7620
EMCYMN
ISTART2 with <actgen>.
The system is running with generation <actgen>. (Almost) all LTGs are active.
The system can be taken back to normal service by manual configuration of
inactive units.
10
h ... 26
ISTART2G with <actgen>.

Carry out all necessary postprocessing steps according to EMCYMN, procedure
EY190-EY194.
i ... EMCYMN,
PROC, EY190
Now the system can be taken back to normal service by manual configuration of
inactive units.
11
i
ISTART2G with <backgen> or <goldgen>.

The next higher TAC level should be informed about the system status and the
ISTART2G.
The automatic recovery was executed by using an older generation. The postprocessing measures according to EMCYMN, procedure EY190-EY194 will
take some time and may cause additional system downtime. Although (almost)
all LTGs are active, a manual recovery with generation <actgen> should be initiated.
12
h ... 26
h ... 12
Decision.
CP113C is used:
CP113D is used:
13
h ... 13
h ... 14
CP113C is in use: Manual Initial Start of BAP-0.

Put switch S1 on DCCMC of BAP-1 in the OFF position (down).
A30808-X3074-A473-2-7620
h ... 15
EY380 - 5
EMCYMN
14
CP113D is in use: Manual Initial Start of BAP-0.

Press RESET key for BAP-1.
EY380- 6
h ... 15
A30808-X3074-A473-2-7620
15
EMCYMN
Manual bootstrap - parameter supply.

UNIT
STATUS
TEST
********************************************
BAP-0
@#####
@#####
BAP-1
@#####
@#####
B:CMY-0
@#####
@#####
B:CMY-1
@#####
@#####
CMY-0
@#####
@#####
CMY-1
@#####
@#####
IOC-0
@#####
@#####
IOC-1
@#####
@#####
TO DIAGNOSE MEMORY
TO FORMAT MEMORY
TO CONTINUE
:
:
:
DIAG;
FORMAT;
;ETX
FORMAT;
UNIT
STATUS
TEST
********************************************
BAP-0
@#####
@#####
BAP-1
@#####
@#####
B:CMY-0
@#####
@#####
B:CMY-1
@#####
@#####
CMY-0
@#####
@#####
CMY-1
@#####
@#####
IOC-0
@#####
@#####
IOC-1
@#####
@#####
TO DIAGNOSE MEMORY
TO FORMAT MEMORY
TO CONTINUE
:
:
:
DIAG;
FORMAT;
;ETX
;
TO
TO
TO
TO
TO
START APS MANUALLY

STOP INITIAL START
:
:
:
:
:
MANUALLY;
INSTALLATION;
UTILITY;
STOP;
;ETX
MAN;
A30808-X3074-A473-2-7620
EY380 - 7
EMCYMN
16
Manual bootstrap - initiate manual restart.

@#############
actgen
@#######################
------backgen
@#######################
------goldgen
@#######################
@#############
actgen
@#######################
------backgen
@#######################
------goldgen
@#######################
Remark:
IOC-0;
LOAD.DEV.=*MDD0* -GENERATION TO LOAD : NAME;(8 CHAR)
The generation name <actgen> can be determined from the printout above.
actgen;
MANUAL RECOVERY - LTG LOADING :Y;/N;
Y;
17
Decision.
CP113C is used:
CP113D is used:
18
h ... 18
h ... 19

19
h ... 20

EY380- 8
h ... 20
A30808-X3074-A473-2-7620
20
EMCYMN
Recovery report.

SYSTEM - RECOVERY
DATE
TIME
PERFORMED LEVEL
PERFORMED ACTION(S)
APS GENERATION
FCP RECOVERY REPORT
ALARM
MMN:SW330-0001
:
:
:
:
@#######@
@#######@
ISTART2
@##############################
: actgen

OST LOAD DEVICE
-------+----+----------MDD-00 ACT YES
MDD-01 ACT NO
ACTUAL GENERATION
#####
#####
#####
#####
#####
#####
#####
#####
: NAME
CREATION DATE
LAST CREATED
---------+------------------+-----------actgen
@####### @####### @##

:
:
:
:
:
:
END OF LTG LOADING
#####
#####
#####
#####
#####
#####
#####
#####
A30808-X3074-A473-2-7620
EY380 - 9
EMCYMN
REASON

@#######################################
: @#######@
: @#######@
: BAPM
DATE
TIME
UNIT
REQUESTED LEVEL
PERFORMED LEVEL
PERFORMED ACTION(S)
: ISTART2
: ISTART2
@##############################
RECOVERY DURATION
: @###@
SECONDS
APS GENERATION
: @#######
STATISTICS

THRESHOLD
: @###
INTERVAL
: @#### SEC
EXCEPTIONS
==========

DURING RECOVERY
UNIT
---@########
21
!
22
UNIT
---@########
UNIT
---@########
UNIT
---@########
UNIT
---@########
Evaluation of the recovery.

If the manual recovery is not successful, the next higher TAC level should be
consulted ! All further measures should only be done in agreement with the
next higher TAC level !
The manual recovery was successful.
h ... 24
The manual recovery using <actgen> was not successful. (The manual
recovery can be repeated by using other HW units (BAP, IOC, MDD) and (if
necessary) fallback generations.)
h ... 35
is executed.
EY380- 10
A30808-X3074-A473-2-7620
23
b
EMCYMN
List generations:
DISP GEN;
command repetition
HISTORY
SET REFGEN
----------+----------+---------+-----+-----------------+---+-----------@######### actgen
@######## @##
@####### @####### @## @#######
------@######### backgen
@######## @##
@####### @####### @## @#######
------@######### oldgold
@######## @##
@####### @####### @## @#######
command repetition
EXECD
Remark:
24
h ... 24
Evaluate the generation list.

OF CURRENT GENERATION and LIST OF GENERATIONS )? (This is the
generation which was successfully used by the preceding ISTART2 / 2G.)
25
i

Startup with generation <actgen> (= the generation which was used for the
manual initial start) was successful.
h ... 26

Fallback to the last backup generation <backgen>.
h ... 25

Fallback to the last backup generation <backgen> was not successful
but
fallback to the last backup generation <oldgold>, i.e. golden generation of
the last quarterly saving, was successful.
h ... 25
ISTART2G was carried out.

The next higher TAC level should be informed about the system status and the
ISTART2G.
The recovery was carried out by using an older generation (ISTART2G). For all
further measures consult the next higher TAC level.
End of procedure.
A30808-X3074-A473-2-7620
h ... 35
EY380 - 11
EMCYMN
26
b
Display system time.

DISP TIME;
command repetition
DATE
@#######
27
TIME
@#######
EXECD
DAY
@#
h ... 27
mode
Check system time.
Y h ... 29
N h ... 28
Do system time and local time correspond?
28
b
Enter new system time.

ENTR TIME:DATE=yy-mm-dd,TIME=hh-mm-ss,WD=wd;
command repetition
DATE
@#######
29
TIME
@#######
EXECD
DAY
@#
INSECURE
Check mode of system time.
Y h ... 31
N h ... 30
Is mode of system time SECURE?
30
b
Change mode of system time to SECURE.

CORR TIME:MODE=SECURE;
DANGEROUS COMMAND CORRTIME READY TO EXECUTE<
;
command repetition
DATE
@#######
EY380- 12
TIME
@#######
EXECD
DAY
@#
SECURE
A30808-X3074-A473-2-7620
31
EMCYMN
The system status is determined in order to be able to restore the original condition of the network node prior to shutdown (default configuration).
SYSTEM - RECOVERY
DATE:
@#######@
TIME: @#######@

UNIT:
----@########
UNIT:
----@########
UNIT:
----@########
UNIT:
----@########
UNIT:
----@########
All units displayed should be noted and activated later in this procedure.
A30808-X3074-A473-2-7620
EY380 - 13
EMCYMN
32
Determine status of periphery and CP.
STAT SSP;
command repetition
STAT CCG;
command repetition
EXECD
STAT SYP;
command repetition
33
EXECD
STAT DLU:DLU=X;
command repetition
EXECD
STAT LTG:LTG=X-X;
command repetition
EXECD
command repetition
EXECD
command repetition
EXECD
STAT SN;
command repetition
EXECD
STAT MB;
command repetition
EXECD
EXECD
The system configuration before the power failure is defined as default configuration.
To restore the default configuration the following steps are to be carried out:
Compare the current system status with the default configuration.

The order in which measures are to be taken to clear any faults will be determined by the situation.
EY380- 14
A30808-X3074-A473-2-7620
34
b
EMCYMN
List and delete alarm(s).

command repetition
EXECD
OBJECT =
ALTYPE =
PABCAUSE=
ALARM-ID:
RECOV
@#######################
@#################################################
@#############################################################
OBJECT =
ALTYPE =
PABCAUSE=
ALARM-ID:
RECOV
ALPRIO = @####### ALSTAT = NP MSGNO = @####
@#######################
@#################################################
CLASS=ISTART
OBJECT =
ALTYPE =
PABCAUSE=
ALARM-ID:
NO (MORE)
RECOV
@#######################
@#################################################
@#############################################################
The following command is to be executed with all message numbers (msgno)

assigned to an ISTART / ISTART2G message.
command repetition
EXECD
Further alarm entries can be displayed using the MML command DISP ALARM;.
Once any faults in the units have been successfully cleared, the corresponding
alarm entry must be reset in the same way as OBJECT=RECOV.
35
End of procedure.
END
A30808-X3074-A473-2-7620
EY380 - 15
EMCYMN
EY380- 16
A30808-X3074-A473-2-7620
3.15
EMCYMN
Measures after unsuccessful FEPROM patching

EY400
3.15.1
Introduction
This procedure is intended to help TAC1 and TAC2 to take measures after abnormal
termination of FEPROM patching for CP113C. The TAC is called by the operating
personnel who registered an error during execution of MMN:SW, SW412.
The operating personnel deliver all necessary symptoms connected with the termination
of procedure MMN:SW, SW412 to make restoration of the complete system function
possible.
3.15.2
Determine patch counter values

In case of unsuccessful FEPROM patching the TAC3 may request the patch counter
values for one or several CP units. The maintenance panel is described in the
NM:CP113, MP:CP113C. The following instructions to determine the patch counter
values are instructed by TAC3 exclusively.
A30808-X3074-A473-2-7620
EY400 - 1
EMCYMN
3.15.2.1
3.15.2.2
Patch counter for processors BAP, CAP and IOC
Configure the relevant processor to OST=MBL
Connect the maintenance panel to the voltage supply on the front panel plug of any
active DCCMC voltage converter
Connect the maintenance panel via the front panel plug to the M:PEX module of the
relevant processor (see 3.15.2.4)
Select command RESET
Press SEND-key
The following values are displayed on the maintenance panel:

A
(pc = patch counter for BACKUP PART)
(pc = patch counter for FEPROM)
Disconnect plugs to M:PEX module and DCCMC voltage converter
Configure the relevant processor to OST=ACT (BAP to SPR)
Patch counter for BCMY
Connect the maintenance panel via the front panel plug to the M:BCM module of the
relevant BCMY
Select command FWVERA
Press ESC-key
Press DISP-key (to have the lines 2 and 3 of the maintenance panel for additional
information)
Press SEND-key

BCMx
xxxx
xxxx
patch counter value
3.15.2.3
EY400- 2
Disconnect plugs to M:BCM module and DCCMC voltage converter
Patch counter for CMY
Connect the maintenance panel via the front panel plug to the M:CMYC module of
the relevant CMY
Select command ICINF
A30808-X3074-A473-2-7620
EMCYMN
Press ESC-key
Press DISP-key (to have the lines 2 and 3 of the maintenance panel for additional
information)
Press SEND-key
Press ++++-key two times

PATCON
3:
xxxx
xxxx
patch counter value
3.15.2.4
Disconnect plugs to M:CMYC module and DCCMC voltage converter
Processor numbers
The following table shows the assignment between processor and processor number
displayed by the maintenance panel. The table should be used to control whether the
right processor is connected with the maintenance panel to determine the patch counter
values.
Processor number
Processor
PRO 0
BAP 0
PRO 1
IOC 0
PRO 2
BAP 1
PRO 3
IOC 1
PRO 4
CAP 0
PRO 5
IOC 2
PRO 6
CAP 1
PRO 7
IOC 3
PRO 8
CAP 2
PRO 9
CAP 3
PRO A
CAP 4
PRO B
CAP 5
PRO C
CAP 6
PRO D
CAP 7
PRO E
CAP 8
PRO F
CAP 9
Tab. 3.15.1 Assignment between processor and processor number
A30808-X3074-A473-2-7620
EY400 - 3
EMCYMN
3.15.3
Diagram
abnormal termination
of FEPROM patching
rolling recovery ?
no
yes
phase of abnormal
termination of
FEPROM patching
request replacement
modules
call TAC3
preparation and
test phase
master file
phase
flash phase
final evaluating
phase
fault clearance
by operating
personnel
call TAC3
call TAC3
call TAC3
symptom
saving
symptom
saving
symptom
saving
get
important
information
get
information
important
NO FURTHER ACTIONS
end of procedure
3.15.4

Decision about rolling recovery

Is there rolling recovery in the system ?
EY400- 4
Y h ... 2
N h ... 3
A30808-X3074-A473-2-7620
EMCYMN
Rolling recovery
Rolling recovery is initiated because an error occurred during patching of the

FEPROM.
Request and send replacement modules to the system location. The replacement modules must contain the state of firmware before patching in their
FEPROM.
Call TAC3
All further actions are instructed by TAC3 exclusively.
h ... 8
Phase of abnormal termination of FEPROM patching

In which phase was the FEPROM patching aborted ?
Preparation and test phase
Master file phase
Flash phase
Final evaluation phase
h ... 4
h ... 5
h ... 6
h ... 7
Error during preparation phase or test phase
A hardware error occurred during the check of the operating state of the CP
units or during the test of the CP units before patching.
The operating personnel perform the fault clearance themselves, in agreement
with TAC1/TAC2 (according to MMN:CP113).
h ... 8
Error during master file phase
The master command file was aborted (analyze message output). A recovery
may be initiated or a command rejection has taken place (due to: lack of
resources, patch counter value still existing, wrong patch address,...).
Call TAC3
Save symptoms according to procedure SW231 (error classification: CP
recovery) and send them to TAC3
Determine patch counter values under instruction of TAC3
i ... MMN:SW,
PROC, SW231
...... patch
Determine
counter
values
No further actions
(No configuration, no activation or deactivation of system status analysis or routine test, no diagnosis, no
testing)
h ... 8
A30808-X3074-A473-2-7620
EY400 - 5
EMCYMN
Error during FEPROM flash phase
The patching of the FEPROM was aborted because the test of the CP units
after execution of the master command file was not successful. The test was not
executed, rejected or executed with errors.
Call TAC3
i....MMN:SW,

PROC, SW231
......Determine
patch counter
values
In case of command rejection give the following information to TAC3:
does CP unit redundancy exist

were system status analysis and/or routine test inhibited
were tests due to MML input activated
processor load while command input
output messages (if test was finished with errors)
No further actions
testing)
h ... 8
7
Error during final evaluation phase
The patching of the FEPROM was executed successfully but in the evaluation
phase there were errors detected that may be connected with patching of the
FEPROM. There may be an error in a CP unit (with or without configuration).
Call TAC3
i....MMN:SW,
PROC, SW231
......Determine
patch counter
values
No further actions
testing)
h ... 8
EY400- 6
A30808-X3074-A473-2-7620
EMCYMN
End of procedure
End of procedure.
END
A30808-X3074-A473-2-7620
EY400 - 7
EMCYMN
EY400- 8
A30808-X3074-A473-2-7620
3.16
EMCYMN
Restoration of files on the background memories

EY500
3.16.1
Introduction
It is decided in the procedure whether it concerns a double disk error, checksum error,
unsuccessful startup test of loading software, double file or catalog error etc.
The following procedures describe the transfer of files from a fallback generation or an
(startup tested) APS save tape without adverse effects on the switching operations if the
contents of both background memories are destroyed (double file, catalog or disk
failure) and the saving of meter files and symptoms.
It is essential to follow the procedure precisely, as otherwise manual recovery from the
APS quarterly save tape will be necessary.
This procedure is always carried out in the network note in case of transfer from the APS
quarterly save tape.
If the transfer of files to a background memory is not successful, the procedure must be
repeated with the redundant background memory.
Each time files are loaded from the save tape, it is necessary to check whether patches
have been incorporated in the APS since the time when the save tape was created. If
patches have been incorporated, manual recovery has to be carried out after transfer of
the save tape files in order to avoid inconsistencies in the APS. After this, the missing
patches are incorporated. The necessary actions are described in detail at the appropriate point in the referenced procedure.
Information on the safeguarding strategy:
The APS save tapes generated in accordance with the safeguarding concept (see
MMN:SW, IN for information) must be used in the following manner in the present procedure:
a) Transfer from the most recent valid APS quarterly save tape of category B,
if this is not successful:
b) Transfer from the next elder valid APS quarterly save tape of category B,
In case of a possible intermediate saving, two large magnetic tapes are to be prepared.
This procedure can be entered from:
A30808-X3074-A473-2-7620
MMN:SW / Register PROC / Procedure SW210

EMCYMN / Register PROC / Procedure EY710
MMN:CP113 if copying of the disk is not successful
EY500 - 1
EMCYMN
3.16.2
1
b
Interrogation of configuration.
STAT SSP;
command repetition
EXECD
Double disk failure?

Is there a DOUBLE DISK FAILURE?
(Both MDDs are in OST unequal ACT!)
Y h ...EMCYMN,
PROC, EY504
N h ... 3
3
Checksum error?
Was (were) the checksum error(s) detected in a generation file which was/were
not repaired by the by system itself?
Y h ...EMCYMN,
PROC, EY501
N h ... 4
4
Files invalid?
ADMINISTRATION ALARM
MMN : EY500-0000
MDD-@#: INOPERABLE AND THEREFORE DEACTIVATED.

LIST OF LOST OR INVALID FILES:
FILENAME
GENERATION LOST/INVALID
------------------+-----------+-----------@################ @#######
@######
Y h ... 5
N h ... 6
Did the above message appear?
Double file failure?
Important note:
Have several error messages been displayed and did they refer to both MDDs
(DOUBLE FILE FAILURE)?
Y h ... 6
N h ...MMN:SW,
PROC, SW310
EY500- 2
A30808-X3074-A473-2-7620
EMCYMN
Startup test successful?

Was the startup test of the LTG loading software during the APS quarterly
saving and the loading of CCNC (during the last routine test) with the
SY.PSW.Txxx files successful?
Y h ... 7
N h ... EMCYMN,
PROC, EY502
List catalog entries.
Customer-specific files which are not part of the save tape must possibly be
created again. These files are not covered by this procedure!
If the DISPFILE command results in a dummy output, generation file(s)
SY.LOADLIB.CA/LA/MA is (are) defective, not valid, or not present on both
disks.
DISP FILE;
command repetition
EXECD
@################## @#############################
FILE
GEN
SIZE VSN000
VSN001
CLASS TYPE
-----------------+--------+------+-------------+-------------+-----+---CG.SA.xxxxx
@####### @##### @############ @############ @### SAM
:
@####### @##### @############ @############ @### SAM
DOUBLE FILE FAILURE:

SY.LOADLIBs defective?
Is (are) the file(s) SY.LOADLIB.CA/LA/MA of the CURRENT GENERATION

(actgen) defective, not valid or not present?
(If the DISPFILE; command results in a default output, the answer is YES!)
Y h ... 9
N h ... EMCYMN,
PROC, EY502

Patches incorporated?
Have patches been incorporated in the APS since the time when the save tape
was created?
Y h ... 10
N h ... EMCYMN,
PROC, EY502
A30808-X3074-A473-2-7620
EY500 - 3
EMCYMN
10

Golden generation files defective?
Are files of the generation GOLDEN (goldgen) defective, not valid, or not
present?
Y h ... 11
N h ... 12
11

No possibility for restoration.
A fallback to this generation is not possible. A Manual Initial Start from the APS
quarterly save tape must be carried out, whereby the contents of the save tape
can be transferred ONLINE. After response from the next higher TAC level carry
out the following actions:
Switch off MDD-x
Switch off MDD-y
Wait for failure message: DOUBLE DISK FAILURE!
Switch on MDD-x again
Wait for approx. 1 minute
CONF MDD:MDD=x,OST=MBL;
command repetition
EXECD
In direct mode the following command is to be typed without the path-name

- DIAG:
DIAG MDD- DIAG:MDD=x;

command repetition
EXECD
h ...EMCYMN,
PROC, EY504
12

No possibility for restoration.
There is no possibility to restore the defective file. After response from the next
higher TAC level a fallback with ISTART2G to an old generation according to
procedure EY190 is to be carried out:
13
h ...EMCYMN,
PROC, EY190
End of procedure.
END
EY500- 4
A30808-X3074-A473-2-7620
3.17
EMCYMN

EY501
3.17.1
General
a) Saving AU files
x large magnetic tapes with write ring for saving the checksum history files (AU files)
b) APS quarterly save tape(s)
It might be necessary within this procedure to transfer files from the last (verified)
APS quarterly save tape. Therefore the save tapes of the last quarterly saving are
to be held ready.
3.17.1.1
Entry into the procedure

The entry into this procedure is caused by alarms:
CURRENT GENERATION
A checksum error on a single or on both background

memories was detected. The checksum error couldnt
be repaired automatically.
Checksum error on one background memory
MAJOR alarm
Checksum error on bot h background memories
CRITICAL alarm
BACKUP GENERATION

MINOR alarm
Checksum error on both background memories
MINOR alarm
GOLDEN GENERATION

MINOR alarm
Checksum error on both background memories
MINOR alarm
A30808-X3074-A473-2-7620
EY501 - 1
EMCYMN
3.17.1.2
Fault clearance of checksum errors

The aim of procedure EY501 is to clear checksum errors, which were detected by the
system, but could not be repaired automatically.
The entrance is triggered by alarms.
The fault clearance measures depend on the type of the generation file(s) and on the
affected generation.
Checksum error for files of the CURRENT GENERATION:
The measures for repairing files of the CURRENT GENERATION (actgen) depend on
the affected file:
SY.SIMP
A fallback to an elder generation (ISTART2G) is probable necessary.

An ISTART2G should only be initiated, after the next higher TAC level
has been consulted.
SY.SEMILIB This file can be repaired by using the data the memory (UPD GEN
command).
Code files
All other generation files contain only code, which means that they can
be overwritten by the corresponding file of a fallback generation.
TRANS SYFILE from background memories
TRANS SYFILE from save tape
If the checksum error occurred only on a single background memory, it is tried to repair
the defective file by using the intact files on the other background memory. This is done
by using the MML command ACT MDDAUDIT.
If a PSW file is defective and the measure described above wasnt successful a restoration can be tried by using the command TRANS SYFILE (background memory / save
tape).
This measure can only be applied for PSW files, since it is possible to overwrite valid
PSW files (the PSW file is still valid and intact on the other background memory).
Checksum errors for files of BACKUP or GOLDEN GENERATION:
If a file of a fallback generation is defective on both background memories, the next APS
saving is to be carried out, in order to replace the faulty generation by a new copy of the
CURRENT GENERATION.
In this case all files of a generation are replaced.
If the checksum error occurred only on a single background memory, it is tried to repair
the files by using the MML command ACT MDDAUDIT.
Note:
If only one background memory is active (other disk is in operational status DEF or
MBL), this procedure is to be used in a way as if the errors occurred on both background
memories.
EY501- 2
A30808-X3074-A473-2-7620
3.17.2
EMCYMN

Entry block.
Checksum errors can be divided into two groups:

1. Automatically repaired checksum errors:
The checksum error(s) occurred only on a single background memory. By
using the checksum information of the second (intact) file on the other
background memory, the defective file could be identified and repaired.
NO alarm mask was printed out.
History files (AU files) were created. The AU files can be saved onto tape
by using this procedure.
2. Alarmed checksum errors which could not be repaired automatically:
The checksum audit detected an error, but the system couldnt repair the
file(s) automatically.
Further fault clearance measures are to be carried out manually by using
this procedure.
At least one alarm mask was printed out.
History files (AU files) were created. After repairing the file(s) successfully,
the AU files are saved onto tape and the alarm entry (entries) is (are) reset.
Which group of checksum error did appear?
Automatically repaired checksum error:
Alarmed checksum error which could not be repaired automatically:
h ... 93
h ... 2
Decision block.
In order to answer the following questions, it is necessary to evaluate the alarm

mask(s) which was (were) printed out.
The entry in the column TYPE is very important:
1. The CURRENT GENERATION is affected:
A30808-X3074-A473-2-7620
EY501 - 3
EMCYMN
MMN:@#########
REASON: CHECKSUM MISMATCH

DATE:
@#######
TIME:
@#######
INDICATIONS
----------DEFECTIVE FILE MDD-00: @################
DEFECTIVE FILE MDD-01: @################
CHECKSUM (HEX)
IND.
FILE
GEN
TYPE
MD STORED
COMPUTED RESULT FILE
-----------------+--------+--------+--+-----------------+------+---@################ @####### ACTUAL
@# @################ @##### @###
@################ @####### ACTUAL
@# @################ @##### @###
2. The BACKUP GENERATION is affected:

MMN:@#########

DATE:
@#######
TIME:
@#######
INDICATIONS
CHECKSUM (HEX)
IND.
FILE
GEN
TYPE
MD STORED
-----------------+--------+--------+--+-----------------+------+---@################ @####### BACKUP
@# @################ @##### @###
@################ @####### BACKUP
@# @################ @##### @###
3. The GOLDEN GENERATION is affected:

MMN:@#########

DATE:
@#######
TIME:
@#######
INDICATIONS
CHECKSUM (HEX)
IND.
FILE
GEN
TYPE
MD STORED
-----------------+--------+--------+--+-----------------+------+---@################ @####### GOLDEN
@# @################ @##### @###
@################ @####### GOLDEN
@# @################ @##### @###
Were checksum errors detected for several generation files?
EY501- 4
Y h ... 3
N h ... 4
A30808-X3074-A473-2-7620
EMCYMN
Decision block.
Do a l l defective files belong to the s a m e generation (only one generation is
affected by the checksum errors) ?
M o r e than o n e generation is affected:
The next higher TAC level should be consulted, in order to decide on the next
steps.
In any case the CURRENT GENERATION is the first one to be repaired.
End of procedure
Only o n e generation is affected by the checksum errors:
h ... 105
h ... 4
Decision block.
Which generation is affected by the checksum error(s) ?
Entry ACTUAL in the column TYPE means:

The CURRENT GENERATION is affected.
h ... 5
Entry BACKUP in the column TYPE means:

The BACKUP GENERATION is affected.
h ... 74
Entry GOLDEN in the column TYPE means:

The GOLDEN GENERATION is affected.
h ... 83
Checksum error of the CURRENT GENERATION (ACTUAL):
The alarm mask(s) is (are) to be evaluated. The decision is to be made whether

the error(s) occurred on a single or on both background memories.
Therefore check the entries in the column RESULT. The entries can be divided
into two parts: <aa> <bbb>
Possible entries for the first part <aa>:
CI
Checksum Information
CN
Checksum mismatch Not repaired
CR
Checksum mismatch Repaired
NC
No Checksum test
OK
checksum OKay
Possible entries for the second part <bbb> (not always present):
A30808-X3074-A473-2-7620
EY501 - 5
EMCYMN
CNC =
Copy Not Completed
DMA =
DaMAged file sector
EF1
Error in F1-label
INC
Indicationfile Not Complete
MFS =
Mismatch Flag Set
NF1
F1-label Not readable
NFA
No File Access
NOH =
NO Heap
NSD =
No Space on Disk
USR =
audit controlled by USeR
If several files are defective, the files which are defective on both background
memories should be repaired first.
If more than one file is defective and at least one of the defective files has a
checksum error on both background memories, the following question is to be
answered with YES !
Decision block.
Y h ... 7
N h ... 8
Did the checksum error(s) appear on b o t h background memories?
The checksum error(s) did appear on both background memories.
The following alarm mask was printed out:

MMN:SW500-0000

DATE:
@#######
TIME:
@#######
INDICATIONS
----------DEFECTIVE FILE MDD-00: AU.Cxxx
DEFECTIVE FILE MDD-01: AU.Dxxx
CHECKSUM (HEX)
IND.
FILE
GEN
TYPE
MD STORED
-----------------+--------+--------+--+-----------------+------+---name
@####### ACTUAL
00 @################ CN
AU.C
name
@####### ACTUAL
01 @################ CN
AU.D
This mask is an example for a checksum error on both background memories.

The file name of the CURRENT GENERATION (ACTUAL) is defective on
both background memories.
The entry CN (Checksum mismatch Not corrected) in the column RESULT for
both background memories (MDD-0 and MDD-1) is important.
EY501- 6
h ... 9
A30808-X3074-A473-2-7620
EMCYMN
The checksum error(s) did appear only on one background memory.

MMN:SW500-0000
REASON: CHECKSUM MISMATCH DETECTED ON MDD-01

DATE:
@#######
TIME:
@#######
INDICATIONS
----------DEFECTIVE FILE: AU.Dxxx
INTACT FILE
: AU.Axxx
CHECKSUM (HEX)
IND.
FILE
GEN
TYPE
MD STORED
-----------------+--------+--------+--+-----------------+------+---name
@####### ACTUAL
00 @################ OK
AU.A
name
@####### ACTUAL
01 @################ CN
AU.D
This alarm mask is an example for a checksum error on a single background

memory which could not be repaired automatically.
MDD-01. The entry CN for MDD-01 is important. If the defective file is on the
other background memory, the entries are modified correspondingly.
If more than one file is a defective, a similar alarm mask is printed out for each
defective file.
h ... 44
Checksum error of the CURRENT GENERATION (both disks):

SY.SIMP
Was a checksum error detected for the file SY.SIMP of the CURRENT GENERATION <actgen> ?
10
i
Y h ... 10
N h ... 11

SY.SIMP
This file cannot be restored !
A30808-X3074-A473-2-7620
EY501 - 7
EMCYMN
There is no possibility to restore the file SY.SIMP !

Together with the next higher TAC level decide on further measures:
ISTART2G (system downtime)
if the CCS7 database was not modified since the last APS quarterly saving
and no CCS7 patches were entered since that time, measures according to
procedure EY502 are possible (no system downtime).
Which fault clearance measure was decided on together with the next higher
TAC level ?
i....EMCYMN,
ISTART2G should be carried out:
PROC, EY190
Fault clearance measures according to procedure EY502 should be carried
out:
i....EMCYMN,
PROC, EY502
The fault clearance was done by falling back to an older generation. All other
checksum errors which might have been detected are also cleared, since all
files were replaced.
11
h ... 93

SY.SEMILIB
Was a checksum error detected for the file SY.SEMILIB of the CURRENT
GENERATION <actgen> ?
12
Y h ... 12
N h ... 13

SY.SEMILIB
Restore the file by using the data in memory:
UPD GEN;
command repetition
:
:
command repetition
13
ACCEPTED
:
:
:
:
:
:
EXECD
h ... 13

Other defective files
Is (are) there another (other) generation file(s) of the CURRENT GENERATION
which is (are) defective on b o t h background memories ?
EY501- 8
Y h ... 14
N h ... 43
A30808-X3074-A473-2-7620
14
EMCYMN

Code file(s): LOADLIB, TASKLIB, PSW files, etc.
Checksum error in code file(s) :

Were patches entered since the last APS saving (quarterly saving / routine
saving) was carried out?
15
Y h ... 39
N h ... 15

Code file(s) - fallback generation on disk It is tried to repair the defective file by using the corresponding file of the last fallback generation (BACKUP or GOLDEN).
Which APS saving (quarterly saving / routine saving) was carried out at latest?
h ... 16
h ... 23
Routine saving was carried out at latest:

Quarterly saving was carried out at latest:
16

Code-file(s) - Backup on disk Overwrite the defective file by using the TRANS SYFILE command:
The last saving was a routine saving. By using the following command it is tried
to replace the defective file(s) of the CURRENT GENERATION by the corresponding file(s) of the BACKUP GENERATION
The parameter GEN must be given the generation name of the CURRENT
GENERATION <actgen>.
In direct mode (BMML) the following command is to be typed without the pathname - DISKFAIL.
TRANS SYFILE - DISKFAIL:FILE=name,VSN=SYSVSN,GEN=actgen;

command repetition
17
EXECD

Further code files defective ?
Are further files of the CURRENT GENERATION <actgen> defective on b o t h
background memories?
A30808-X3074-A473-2-7620
Y h ... 16
N h ... 18
EY501 - 9
EMCYMN
18

Code file(s)
By using the following command a checksum audit on demand is initiated. A list

of all checked files is output. This list is to be analyzed in order to check whether
or not the repair measures were successful.
The entries in column RESULT of that list are to be evaluated. (The 2nd entry
bbb isnt always present.)
It is possible that files which were defective on one single background memory
before the audit was started are repaired automatically during the audit.
A checksum error which already caused an alarm and which is not repaired up
to now, will not be alarmed again. In this case the checksum error will be indicated by the entry CI MFS in the column RESULT.
ACT MDDAUDIT:TYPE=ACTUAL,RESTORE=REST;
command repetition
:
:
command repetition
ACCEPTED
:
:
:
:
:
:
EXECD
CHECKSUM (HEX)
IND.
FILE
GEN
TYPE
MD STORED
-----------------+--------+--------+--+-----------------+------+----@################ @####### ACTUAL
00 @################ aa bbb @###
@################ @####### ACTUAL
01 @################ aa bbb @###
:
:
:
:
:
:
:
:
19

Code file(s)
Within the next procedure steps the current system status is to be evaluated.
The system should have reached one of the three situations mentioned below:
1. All checksum errors repaired
No alarm mask was output.
All checked files /whole generation) have one of the following entries in the
column RESULT:
OK
checksum OKay
CR
2. Checksum errors on one background memory

All files which were defective on both background memories were repaired successfully, but there is at
least one file present which has a checksum error on a single background memory:
EY501- 10
A30808-X3074-A473-2-7620
EMCYMN
Possibly alarm masks indicating checksum errors on a single background

memory are output.
No file has for both background memories in the column RESULT e.g. one
of the following entries.
At least one file has for a single background memory in the column
RESULT e.g. one of the following entries:
CN
CI MFS
Checksum Information/Mismatch Flag Set
3. Checksum errors on both background memories

Possibly alarm masks indicating checksum errors on both background
memories were output.
At least one file has for both background memories in the column RESULT
e.g. one of the following entries:
CN
CI MFS
h ... 20
20

Current system status.
Which one of the three situations did occur ?
All checksum errors repaired
Checksum errors on one background memory
Checksum errors on both background memories
21
i
h ... 33
h ... 41
h ... 21

Code file(s) - patch status If patches were entered since the last APS quarterly saving the GOLDEN
GENERATION cannot be used for repairing the defective file(s) of the
CURRENT GENERATION !
Were patches entered since the last APS quarterly saving was carried out ?
A30808-X3074-A473-2-7620
Y h ... 39
N h ... 22
EY501 - 11
EMCYMN
22

Code file(s) - GOLDEN on disk -
The repair measures using the file(s) of the BACKUP GENERATION were not
successful.
It is possible to repeat the repair measures by using the files of the GOLDEN
GENERATION. In a first step the BACKUP GENERATION is to be deleted on
the background memories. After that the file(s) of the GOLDEN GENERATION
are automatically used, when the TRANS SYFILE command is executed.
All these measures should only be done after the next higher TAC level has
been consulted !
After all defective files were repaired successfully, the deleted BACKUP
GENERATION is to be substituted by carrying out the next APS saving.
command repetition
EXECD
Since there is no BACKUP GENERATION on the background memories, the

repair measures are automatically carried out with files of the GOLDEN
GENERATION.
23
h ... 23

Code file(s) - Golden on disk -
Overwrite the defective file(s) by using the TRANS SYFILE command:
Either the last APS saving was a quarterly saving or the BACKUP GENERATION <backgen> was deleted in a former step of the procedure. By using
the following command it is tried to replace the defective file(s) by the corresponding file(s) of the GOLDEN GENERATION.
In direct mode (BMML) the following command is to be typed without the

pathname - DISKFAIL:
TRANS SYFILE - DISKFAIL:FILE=name,VSN=SYSVSN,GEN=actgen;

command repetition
24
EXECD

Further code files defective ?
Are further files of the CURRENT GENERATION <actgen> defective on both
background memories?
EY501- 12
Y h ... 23
N h ... 25
A30808-X3074-A473-2-7620
25
EMCYMN

Code file(s)

The entries in column RESULT of that list are to be evaluated. (The 2nd entry
bbb isnt always present.)
It is possible that files which were defective on one single background memory
before the audit was started were repaired automatically during the audit.
A checksum error which already caused an alarm and which is not repaired up
to now, will not be alarmed again. In this case the checksum error will be indicated by the entry CI MFS in the column RESULT.
command repetition
:
:
command repetition
ACCEPTED
:
:
:
:
:
:
EXECD
CHECKSUM (HEX)
IND.
FILE
GEN
TYPE
MD STORED
-----------------+--------+--------+--+-----------------+------+----@################ @####### ACTUAL
00 @################ aa bbb @###
@################ @####### ACTUAL
01 @################ aa bbb @###
:
:
:
:
:
:
:
:
26

Code file(s)
column RESULT:
OK
checksum OKay
CR

A30808-X3074-A473-2-7620
EY501 - 13
EMCYMN

memory are output.
of the following entries.
At least one file has for a single background memory in the column
CN
CI MFS

CN
CI MFS
h ... 27
27

h ... 33
h ... 44
h ... 28

28

Code file(s) - GOLDEN on save tape -
For all further steps the next higher TAC level must be consulted !
The next repair attempt could be started by using the files on the last (verified)
APS save tape.
Should another repair attempt be executed by using the files on the APS save
tape?
EY501- 14
Y h ... 29
N h ... 39
A30808-X3074-A473-2-7620
29
EMCYMN

Code file(s) - GOLDEN on save tape -
Together with the next higher TAC level it was decided to try to repair the defective file(s) by using the last APS save tape.
Mount and load the last startup tested APS save tape (SA1TAP).
TRANS SYFILE:GEN=actgen,FILE=name,VSN=SA1TAP;
The command is to be executed for all defective files.

(If necessary, continuation tape handling is to be carried out).
30

Code file(s)

command repetition
:
:
command repetition
ACCEPTED
:
:
:
:
:
:
EXECD
CHECKSUM (HEX)
IND.
FILE
GEN
TYPE
MD STORED
-----------------+--------+--------+--+-----------------+------+----@################ @####### ACTUAL
00 @################ aa bbb @###
@################ @####### ACTUAL
01 @################ aa bbb @###
:
:
:
:
:
:
:
:
31

Code file(s)
column RESULT:
OK
checksum OKay
CR

A30808-X3074-A473-2-7620
EY501 - 15
EMCYMN

memory are output.
of the following entries,
but at least one file has for a single background memory in the column
CN
CI MFS

CN
CI MFS
h ... 32
32

h ... 33
h ... 44
h ... 39

33

Code file(s) - connect LOADLIBs Each defective LOADLIB of the CURRENT GENERATION which was replaced
by the corresponding LOADLIB of a fallback generation (BACKUP or GOLDEN)
is to be connected.
h ... 35
h ... 34
No LOADLIBs were replaced.

At least one of the files LOADLIB.CA/LA/MA was replaced.
34

Code file(s) - connect LOADLIBs -
The following command is to be executed for all LOADLIBs which were replaced
during the repair measures.
(If a NOT EXECD message occurs it can be ignored as long as the respective
file is already connected (DLL_NO: 16)).
ACT LOADLIB:LIB=SY.LOADLIB.xA;
command repetition
EY501- 16
EXECD
h ... 35
A30808-X3074-A473-2-7620
35
EMCYMN

Code file(s) - execute APS saving -
Y h ... 36
N h ... 93
Was the BACKUP GENERATION deleted in a former step ?
36

Code file(s) - execute APS saving Was this procedure entered while an APS saving according to MMN:SW, procedure SW210 was carried out ?
Y
h ... 37
N h ... 38
37

Code file(s) - no replacement of BACKUP GENERATION -
The checksum error(s) has (have) been detected and alarmed while an APS
saving was carried out.
Since the BACKUP GENERATION is replaced by a new copy of the CURRENT
GENERATION after returning to MMN:SW, procedure SW210, the deleted
BACKUP GENERATION needs not to be replaced yet.
38
b
h ... 93

Code file(s) - execute APS saving STAT LOG;
command repetition
EXECD
Depending on the currently active LOG function the next APS saving is to be
carried out:
LOG6 is currently active:
The next APS saving according to the time schedule is a quarterly saving,
which is to be carried out immediately.
i ... MMN:SW,
PROC, SW210
Another LOG file is currently active:

Since the BACKUP GENERATION was deleted in a former step the next
routine saving is to be carried out immediately.
i ... MMN:SW,
PROC, SW210
After retuning from the APS saving, postprocessing is to be carried out !
A30808-X3074-A473-2-7620
h ... 93
EY501 - 17
EMCYMN
39
i

Code file(s) - fall back on older generation This file cannot be restored !
Together with the next higher TAC level the decision about further measures is
to be made. (ISTART2G causes system downtime !)
There exist two alternatives for further fault clearance measures:
40
Together with the next higher TAC level it was decided to carry out an
ISTART2G.
The fallback to an older generation (ISTART2G according to EMCYMN,
EY190) means that all files of the CURRENT GENERATION <actgen> were
replaced. So all further checksum errors of files of the CURRENT GENERATION must not be repaired.
If the BACKUP GENERATION was deleted in a former step it must be
replaced.
h ... 40
Together with the next higher TAC level it was decided on executing other
fault clearance measures. One has to make sure that all defective files are
cleared (including all files which are defective on one single background
memory). Finally the history files (AU files) and other symptoms are to be
saved.
h ... 105

ISTART2G
Together with the next higher TAC level it was decided on carrying out an
ISTART2G.
PROC, EY190
h ... 93
After returning from EY19x, symptom saving is to be carried out.
41
i....EMCYMN,

Code file(s) - connect LOADLIBs Each defective LOADLIB of the CURRENT GENERATION which was replaced
by the corresponding LOADLIB of a fall back generation (BACKUP or GOLDEN)
is to be connected.
h ... 43
h ... 42
No LOADLIBs were replaced.

At least one of the files LOADLIB.CA/LA/MA was replaced.
42

Code file(s) - connect LOADLIBs -
The following command is to be executed for all LOADLIBs which were replaced
during the repair measures.
(If a NOT EXECD message occurs it can be ignored as long as the respective
file is already connected (DLL_NO: 16)).
command repetition
EY501- 18
EXECD
h ... 43
A30808-X3074-A473-2-7620
43
EMCYMN
Checksum error of the CURRENT GENERATION (one disk):

Is at least one file of the CURRENT GENERATION <actgen> defective on o n e
single background memory ?
44
Y h ... 44
N h ... 69
If only one file is defective, the checksum error occurred only on one of the two
background memories.
If several files are defective, each file has its checksum error only on one background memory. Nevertheless, both background memories can be affected:
crossed single faults.
By using the following command it is tried to repair the defective file(s). The file
list is to be evaluated:
command repetition
:
:
command repetition
ACCEPTED
:
:
:
:
:
:
EXECD
CHECKSUM (HEX)
IND.
FILE
GEN
TYPE
MD STORED
-----------------+--------+--------+--+-----------------+------+----@################ @####### ACTUAL
00 @################ aa bbb @###
@################ @####### ACTUAL
01 @################ aa bbb @###
:
:
:
:
:
:
:
:
45
The repair measure was successful, if both statements are true:
All checked files (whole generation) have one of the following entries in the
column RESULT:
OK
( = checksum OKay )
CR
( = Checksum mismatch Repaired )
The repair measure was not successful, if at least one of the following statements is true:
At least one alarm mask was output.
At least one file has for one background memory one of the following entries
in the column RESULT:
CN
( = Checksum mismatch Not repaired )
CI MFS ( = Checksum Information / Mismatch Flag Set )
A30808-X3074-A473-2-7620
EY501 - 19
EMCYMN
46
Y h ... 69
N h ... 47
Was the repair measure successful ?
47
Y h ... 49
N h ... 48
Are only PSW files affected ?
48
It is not possible to repair the defective file(s) by using the intact file(s) of the
other background memory.
Before carrying out further fault clearance measures, it is necessary to consult
the next higher TAC level.
The suggested fault clearance measure can only be applied, if no crossed
single faults were detected, i.e. all checksum errors appeared on the same
background memory (either MDD-0 or MDD-1):
49
The background memory containing the defective files is to be configured to

MBL.
After that the background memory is to be configured to ACT again.
After finishing the fault clearance measures successfully, the history files (AU
files) are to be saved onto tape and the alarms are to be reset.
If the BACKUP GENERATION has been deleted in a former step, it has to be

replaced by a new fallback generation after finishing the fault clearance
measures successfully !

PSW file(s) - BACKUP GENERATION on background memories Does the BACKUP GENERATION <backgen> exist on the background memories ?
50
Y h ... 50
N h ... 51

PSW file(s) - patch status Were patches entered since the last routine saving was carried out ?
51
h ... 105
Y h ... 73
N h ... 52

PSW file(s) - patch status Were patches entered since the last quarterly saving was carried out ?
EY501- 20
Y h ... 73
N h ... 59
A30808-X3074-A473-2-7620
52
EMCYMN

PSW file(s) - BACKUP on disk -
The parameter GEN must be given the name of the CURRENT GENERATION
<actgen>.
In direct mode (BMML) the following command is to be typed without the pathname - OVWRGENF :
TRANS SYFILE-OVWRGENF:
FILE=name,VSN=SYSVSN,GEN=actgen,REASON=OVWRGENF;
command repetition
:
:
command repetition
53
ACCEPTED
:
:
:
:
:
:
EXECD

PSW file(s)
Are further PSW files of the CURRENT GENERATION <actgen> defective ?
54
b
Y h ... 52
N h ... 54
Checksum error of the CURRENT GENERATION (one disk) :

PSW file(s)
command repetition
:
:
command repetition
ACCEPTED
:
:
:
:
:
:
EXECD
CHECKSUM (HEX)
IND.
FILE
GEN
TYPE
MD STORED
-----------------+--------+--------+--+-----------------+------+----@################ @####### ACTUAL
00 @################ aa bbb @###
@################ @####### ACTUAL
01 @################ aa bbb @###
:
:
:
:
:
:
:
:
55
Checksum error of the CURRENT GENERATION (one disk) :
column RESULT:
OK
( = checksum OKay )
CR
A30808-X3074-A473-2-7620
EY501 - 21
EMCYMN
CN
56
Y h ... 93
N h ... 57
57

PSW file(s) - patch status -
Y h ... 73
N h ... 57
Were patches entered since the last quarterly saving was carried out ?
58

Code file(s) - GOLDEN on disk -
The repair measures using the file(s) of the BACKUP GENERATION were not
successful.
It is possible to repeat the repair measures by using the files of the GOLDEN
GENERATION. In a first step the BACKUP GENERATION is to be deleted on
the background memories. After that the file(s) of the GOLDEN GENERATION
are automatically used, when the TRANS SYFILE command is executed.
All these measures should only be done after the next higher TAC level has
been consulted !
After all defective files were repaired successfully, the deleted BACKUP
GENERATION is to be substituted by carrying out the next APS saving.
command repetition
EXECD
Since there is no BACKUP GENERATION on the background memories, the

repair measures are automatically carried out with files of the GOLDEN
GENERATION.
EY501- 22
h ... 59
A30808-X3074-A473-2-7620
59
EMCYMN

Code file(s) - Golden on disk -
Overwrite the defective file(s) by using the TRANS SYFILE command:
Either the last APS saving was a quarterly saving or the BACKUP GENERATION <backgen> was deleted in a former step of the procedure. By using
the following command it is tried to replace the defective file(s) by the corresponding file(s) of the GOLDEN GENERATION.
In direct mode (BMML) the following command is to be typed without the

pathname - OVWRGENF:
FILE=name,VSN=SYSVSN,GEN=actgen,REASON=OVWRGENF;
command repetition
:
:
command repetition
60
ACCEPTED
:
:
:
:
:
:
EXECD

Further PSW files defective ?
Are further PSW files of the CURRENT GENERATION <actgen> defective on
both background memories?
61
b
Y h ... 59
N h ... 61

PSW file(s)
command repetition
:
:
command repetition
ACCEPTED
:
:
:
:
:
:
EXECD
CHECKSUM (HEX)
IND.
FILE
GEN
TYPE
MD STORED
-----------------+--------+--------+--+-----------------+------+----@################ @####### ACTUAL
00 @################ aa bbb @###
@################ @####### ACTUAL
01 @################ aa bbb @###
:
:
:
:
:
:
:
:
A30808-X3074-A473-2-7620
EY501 - 23
EMCYMN
62
column RESULT:
OK
( = checksum OKay )
CR
CN
63

PSW file(s)
Y h ... 69
N h ... 64
Could the defective PSW file(s) be repaired ?
64
i

PSW file(s) - GOLDEN on tape For all further he next higher TAC level must be consulted !
The next repair attempt could be started by using the files on the last (verified)
APS save tape.
Together with the next higher TAC level it is to be decided whether or not
another repair attempt using the last APS save tape should be carried out.
65
No further repair attempt should be carried out:
h ... 73
Together with the next higher TAC level it was decided to try to repair the
defective file(s) by using the last APS save tape:
h ... 65

PSW files - GOLDEN on tape The last startup tested APS save tape (SA1TAP) is to be loaded and after this
the following command is to be entered:
FILE=name,VSN=SA1TAP,GEN=actgen,REASON=OVWRGENF;
The command is to be executed for all defective files. (If necessary, continuation
tape handling is to be carried out).
EY501- 24
A30808-X3074-A473-2-7620
66
b
EMCYMN

PSW file(s) - GOLDEN on tape ACT MDDAUDIT:TYPE=ACTUAL,RESTORE=REST;
command repetition
:
:
command repetition
ACCEPTED
:
:
:
:
:
:
EXECD
CHECKSUM (HEX)
IND.
FILE
GEN
TYPE
MD STORED
-----------------+--------+--------+--+-----------------+------+----@################ @####### ACTUAL
00 @################ aa bbb @###
@################ @####### ACTUAL
01 @################ aa bbb @###
:
:
:
:
:
:
:
:
67

PSW file(s) - GOLDEN on tape -
column RESULT:
OK
( = checksum OKay )
CR
CN
68

PSW file(s) - GOLDEN on tape Could the defective PSW file(s) be repaired ?
69
Y h ... 69
N h ... 73

Code file(s) - execute APS saving Was the BACKUP GENERATION deleted in a former step ?
A30808-X3074-A473-2-7620
Y h ... 70
N h ... 93
EY501 - 25
EMCYMN
70

Code file(s) - execute APS saving Was this procedure entered while an APS saving according to MMN:SW, procedure SW210 was carried out ?
Y
h ... 71
N h ... 72
71

Code file(s) - no replacement of BACKUP GENERATION -
The checksum error(s) has (have) been detected and alarmed while a quarterly
saving was carried out.
Since the BACKUP GENERATION is replaced by a new copy of the CURRENT
GENERATION after returning to MMN:SW, procedure SW210, the deleted
BACKUP GENERATION needs not to be replaced yet.
72
b
h ... 93

Code file(s) - execute APS saving STAT LOG;
command repetition
EXECD
Depending on the currently active LOG function the next APS saving is to be
carried out:
LOG6 is currently active:
The next APS saving according to the time schedule is a quarterly saving,
which is to be carried out immediately.
i....MMN:SW,
PROC, SW210
Another LOG file is currently active:

Since the BACKUP GENERATION was deleted in a former step the next
routine saving is to be carried out immediately.
i....MMN:SW,
PROC, SW210
h ... 93
After retuning from SW210, postprocessing is to be carried out !
73

Repair of PSW file(s) not successful / not possible.
The repair measures using PSW files of a fallback generation either were not
successful or not possible due to the patch status.
EY501- 26
A30808-X3074-A473-2-7620
EMCYMN
The suggested fault clearance measure can only be applied, if no crossed single
faults were detected. That means all checksum errors appeared on the same
background memory (either MDD-0 or MDD-1).
The background memory containing the defective files, is to be configured to

MBL..
After finishing the fault clearance measures successfully, the history files (AU
files) are to be saved onto tape and the alarms are to be reset.
If the BACKUP GENERATION was deleted in a former step, it has to be

replaced by a new fallback generation after finishing the fault clearance
measures successfully !
74
h ... 105
Checksum error of the BACKUP GENERATION

CI
CN
CR
NC
No Checksum test
OK
checksum OKay
A30808-X3074-A473-2-7620
EY501 - 27
EMCYMN
CNC =
Copy Not Completed
DMA =
DaMAged file sector
EF1
Error in F1-label
INC
MFS =
Mismatch Flag Set
NF1
NFA
No File Access
NOH =
NO Heap
NSD =
No Space on Disk
USR =
answered with YES !
75
Decision block
Y h ... 76
N h ... 77
Did the checksum error(s) appear on b o t h background memories?
76

MMN:SW500-0000

DATE:
@#######
TIME:
@#######
INDICATIONS
CHECKSUM (HEX)
IND.
FILE
GEN
TYPE
MD STORED
-----------------+--------+--------+--+-----------------+------+---name
@####### BACKUP
00 @################ CN
AU.C
name
@####### BACKUP
01 @################ CN
AU.D

The file name of the BACKUP GENERATION (BACKUP) is defective on both
EY501- 28
h ... 78
A30808-X3074-A473-2-7620
77
EMCYMN
The checksum error(s) did appear only on a single background memory.

MMN:SW500-0000

DATE:
@#######
TIME:
@#######
INDICATIONS
INTACT FILE
: AU.Axxx
CHECKSUM (HEX)
IND.
FILE
GEN
TYPE
MD STORED
-----------------+--------+--------+--+-----------------+------+---name
@####### BACKUP
00 @################ OK
AU.A
name
@####### BACKUP
01 @################ CN
AU.D

memory, which could not be repaired automatically.
other background memory, the entries are modified, correspondingly.
If more than one file is defective, a similar alarm mask is printed out for each
defective file.
78
Checksum error of the BACKUP GENERATION (both disks):
The APS saving which is the next according to the schedule (routine saving or
quarterly saving) is to be carried out immediately.
h ... 79
i ... MMN:SW,
PROC, SW210
After finishing the APS saving successfully, a new fallback generation

(BACKUP or GOLDEN) exists on the background memories.
This means that all checksum errors detected only one single background
memory (if existing) are also cleared.
h ... 93
A30808-X3074-A473-2-7620
EY501 - 29
EMCYMN
79
Checksum error of the BACKUP GENERATION (one disk):
ACT MDDAUDIT:TYPE=BACKUP,RESTORE=REST;
command repetition
:
:
command repetition
ACCEPTED
:
:
:
:
:
:
EXECD
CHECKSUM (HEX)
IND.
FILE
GEN
TYPE
MD STORED
-----------------+--------+--------+--+-----------------+------+----@################ @####### BACKUP
00 @################ aa bbb @###
@################ @####### BACKUP
01 @################ aa bbb @###
:
:
:
:
:
:
:
:
80
Checksum error of the BACKUP GENERATION (one disk) :
column RESULT:
OK
( = checksum OKay )
CR
CN
81
Checksum error of the BACKUP GENERATION (one disk)

EY501- 30
Y h ... 93
N h ... 82
A30808-X3074-A473-2-7620
82
EMCYMN
Checksum error of the BACKUP GENERATION (one disk) :

Suggestions for further fault clearance measures:
Suggestion 1:
The background memory containing the defective files is to be configured
to MBL.
After finishing the fault clearance measures successfully, the history files
(AU files) are to be saved on tape and the alarms are to be reset.
Suggestion 2:
Use the same fault clearance measures as in the case of checksum error on
both background memories (i.e. execute the next APS saving).
h ... 105
83
Checksum error of the GOLDEN GENERATION

CI
CN
CR
NC
No Checksum test
OK
checksum OKay
A30808-X3074-A473-2-7620
EY501 - 31
EMCYMN
CNC =
Copy Not Completed
DMA =
DaMAged file sector
EF1
Error in F1-label
INC
MFS =
Mismatch Flag Set
NF1
NFA
No File Access
NOH =
NO Heap
NSD =
No Space on Disk
USR =
answered with YES !
84

MMN:SW500-0000

DATE:
@#######
TIME:
@#######
INDICATIONS
CHECKSUM (HEX)
IND.
FILE
GEN
TYPE
MD STORED
-----------------+--------+--------+--+-----------------+------+---name
@####### GOLDEN
00 @################ CN
AU.C
name
@####### GOLDEN
01 @################ CN
AU.D

The file name of the GOLDEN GENERATION (GOLDEN) is defective on both
EY501- 32
h ... 86
A30808-X3074-A473-2-7620
85
EMCYMN
The checksum error(s) did appear only on a single background memory.

MMN:SW500-0000

DATE:
@#######
TIME:
@#######
INDICATIONS
INTACT FILE
: AU.Axxx
CHECKSUM (HEX)
IND.
FILE
GEN
TYPE
MD STORED
-----------------+--------+--------+--+-----------------+------+---name
@####### GOLDEN
00 @################ OK
AU.A
name
@####### GOLDEN
01 @################ CN
AU.D

memory, which could not be repaired automatically.
other background memory, the entries are modified, correspondingly.
If more than one file is defective, a similar alarm mask is printed out for each
defective file.
86
h ... 89
Checksum error of the GOLDEN GENERATION (both disks):
The next APS quarterly saving is to be carried out immediately:
STAT LOG;
command repetition
Is file LOG6 active ?
A30808-X3074-A473-2-7620
EXECD
Y h ... 88
N h ... 87
EY501 - 33
EMCYMN
87
Change from LOGx to LOG6:
MOD LOGFILE:FILE=LOG6,SIZE=24,ERASE=YES;
command repetition
EXECD
Mount the APS routine save tape (LOGTAP) (possibly already done).
DEL FILE:FILE:DUMMY.MET,VSN=LOGTAP;
command repetition
EXECD
The closed LOG file (LOGx) is transferred to tape:
TRANS FILE:FILE=LG.LOGx.,VSNR=LOGTAP,COPMOD=SSWF;
command repetition
REWIND MT:MTD=00;
command repetition
EXECD
DEL FILE:FILE=LG.LOGx.;
command repetition
88
EXECD
EXECD
h ... 88
i....MMN:SW,
The next quarterly saving is to be carried out immediately.
PROC, SW210
After finishing the APS saving successfully, a new fallback generation

(BACKUP or GOLDEN) exists on the background memories.
This means that all checksum errors detected only one single background
memory (if existing) are also cleared.
h ... 93
EY501- 34
A30808-X3074-A473-2-7620
89
EMCYMN
Checksum error of the GOLDEN GENERATION (one disk):
ACT MDDAUDIT:TYPE=BACKUP,RESTORE=REST;
command repetition
:
:
command repetition
ACCEPTED
:
:
:
:
:
:
EXECD
CHECKSUM (HEX)
IND.
FILE
GEN
TYPE
MD STORED
-----------------+--------+--------+--+-----------------+------+----@################ @####### GOLDEN
00 @################ aa bbb @###
@################ @####### GOLDEN
01 @################ aa bbb @###
:
:
:
:
:
:
:
:
90
column RESULT:
OK
( = checksum OKay )
CR
CN
91

A30808-X3074-A473-2-7620
Y h ... 93
N h ... 92
EY501 - 35
EMCYMN
92

Suggestions for further fault clearance measures:
Suggestion 1:
The background memory containing the defective files is to be configured
to MBL.
After finishing the fault clearance measures successfully, the history files
(AU files) are to be saved on tape and the alarms are to be reset.
Suggestion 2:
Use the same fault clearance measures as in the case of checksum error on
both background memories (i.e. execute the next APS saving).
h ... 105
93
Postprocessing: Saving AU files (part 1).
The Au files which were created during the checksum audit, are to be saved
onto tape and sent to TAC2/TAC3.
DISP FILE:FILE=AU.;
Y h ... 94
N h ... 95
Do AU. files exist on the background memories ?
94
Postprocessing: AU files available.

command repetition
EXECD
@################## @#############################
FILE
GEN
SIZE VSN000
VSN001
CLASS TYPE
-----------------+--------+------+-------------+-------------+-----+---AU.xxx
@####### @##### @############ @############ @### @###
AU.yyy
@####### @##### @############ @############ @### @###
:
:
:
:
:
:
:
:
95
h ... 96
Postprocessing: No AU files available.

command repetition
EY501- 36
EXECD
h ... 99
A30808-X3074-A473-2-7620
96
EMCYMN
Postprocessing: Saving of AU files (init tape).

Mount and load a new magnetic tape.
INIT MT:MTD=00,VSN=AU1TAP,DENS=6250,CD=EBC;
command repetition
:
:
command repetition
97
b
ACCEPTED
:
:
:
:
:
:
EXECD
Postprocessing: Saving of AU files (trans file).

TRANS FILE:FILE=AU.,VSNR=AU1TAP,COPMOD=SSWF;
If the message PLEASE MOUNT CONTINUATION TAPE TO VSN=AU1TAP is

displayed after end of tape was reached, proceed with continuation tape
handling. Initialize a new tape (AUxTAP) and enter: MOUNT TAPE:
DEV=MTD-00;
command repetition
SENDER
RECEIVER
EXECD
: @#######
: @#######
START START
FILE IDENTIFICATION
DATA TYPE
BYTES/
/END- /END: FILE
VSN
STATE : ERROR
RECORDS
DATE TIME
-+-----------------+------+-----+-+-----+-+--+----+---------+-----+----S AU.xxx
@##### TR
@ @#### @ @# @### @######## @#### @####
R AU.xxx
AU1TAP CR
@ @#### @ @# @### @######## @#### @####
:
:
:
:
:
:
:
:
REWIND MT:MTD=00;
command repetition
EXECD
Rewind and remove AUxTAP.
98
b
Postprocessing: Saving of AU files (del file).

DEL FILE:FILE=AU.;
command repetition
ACCEPTED
FILE
----------------AU.xxx
:
:
+
command repetition
A30808-X3074-A473-2-7620
EXECD
EY501 - 37
EMCYMN
99
b
Postprocessing: Delete alarm entries.

DISP ALARM:OBJECT=ADMINAL;
command repetition
EXECD
OBJECT =
ALTYPE =
PABCAUSE=
ALARM-ID:
ADMINAL
@#######################
@#################################################
@#############################################################
:
:
:
:
:
:
:
:
OBJECT =
ALTYPE =
PABCAUSE=
ALARM-ID:
ADMINAL
@#######################
CORRUPT DATA
@#############################################################
:
:
:
:
:
:
:
:
OBJECT =
ALTYPE =
PABCAUSE=
ALARM-ID:
ADMINAL
@#######################
@#################################################
@#############################################################
:
:
:
:
:
:
:
:
The following command is to be executed for all message numbers <msgno>,

which have the entry PABCAUSE=CORRUPT DATA. The corresponding alarm
priority (ALPRIO) depends on the affected generation.
command repetition
100
EXECD
Postprocessing: Save history files according to SW231.
i....MMN:SW,
In order to save further symptoms, procedure SW231 is to be carried out !
PROC, SW231
101
i
Postprocessing: Return to calling procedure.

The magnetic tape which was mounted when entering this procedure
(SAxTAP, LOGTAP, ...) is to be mounted again !
If an APS saving was carried out during the fault clearance measures, the
routine save tape of the current save interval (LOGTAP) is to be mounted.
Was (were) the checksum error(s) detected during an APS saving ?
EY501- 38
Y h ... 102
N h ... 105
A30808-X3074-A473-2-7620
102
Postprocessing: Return to calling procedure.

Was an APS saving (quarterly or routine) or a fallback to an elder generation
executed in the cause of fault clearance measures ?
103
h ... 105
Postprocessing.
The checksum errors were repaired successfully. Therefore APS saving

according to MMN:SW, procedure SW210 can be continued.
105
Y h ... 103
N h ... 104
Postprocessing.
Since the requested APS saving was already carried out, it is not necessary to
return to procedure SW210.
104
EMCYMN
h ... 105
Continue calling procedure.

Continue the calling procedure in the decision block in which it was left.
For users of the function Manual on PC: the branch back to this block is made
106
End of procedure.
END
A30808-X3074-A473-2-7620
EY501 - 39
EMCYMN
EY501- 40
A30808-X3074-A473-2-7620
3.18
EMCYMN

EY502
3.18.1
Introduction
The procedure describes the transfer of generation files from a fallback generation or an
(startup tested) APS quarterly save tape without adverse effects on the switching operations if the contents of both background memories are destroyed (double file, catalog
or disk failure) and the saving of meter files and symptoms.
Customer-specific files which are not part of the save tape must possibly be created
again. These files are not covered by this procedure!
This procedure is always carried out in the network node in case of transfer from the
APS quarterly save tape.
patches are incorporated. The necessary actions are described in detail at the appropriate point in the referenced procedures.
MMN:SW IN for information) must be used in the following manner in the present procedure:
a) Transfer from the most recent valid APS quarterly save tape of category B,
if this is not successful:
b) Transfer from the next elder valid APS quarterly save tape of category B,
- MMN:SW / Register PROC / Procedure SW211
- EMCYMN / Register PROC / Procedure EY500
- MMN:CP113 if copying of the disk is not successful
A30808-X3074-A473-2-7620
EY502 - 1
EMCYMN
3.18.2

3.18.3
DOUBLE FAILURE OF A GENERATION FILE:

Decision block.
Was a checksum error detected for the file SY.SIMP of the CURRENT GENERATION (actgen) in the previous procedure EY501?

Decision block.
Was the startup test of the LTG loading software during the APS quarterly
saving and the loading of the CCNC (during the last routine test) with the
SY.PSW.Txxx files successful?
Y h ... 19
N h ... 2
Y h ... 7
N h ... 3

Restoration of the valid PSW file.
Mount and load the latest (startup tested) APS save tape (part 1) in MTD.
(actgen).
In direct mode (BMML) the following command is to be typed without the pathname -OVWRGENF :
TRANS SYFILE OVWRGENF:REASON=OVWRGENF,GEN=actgen,FILE=name,VSN=SA1TAP

;
command repetition
ACCEPTED
If the message PLEASE MOUNT CONTINUATION TAPE TO VSN = SA1TAP

is displayed after the end of tape was reached, proceed with continuation tape
handling and then enter: MOUNT TAPE:DEV=MTD-0;
command repetition
EY502- 2
EXECD
A30808-X3074-A473-2-7620
EMCYMN

Decision block.
Y h ... 5
N h ... 3
Was the transfer of the save copy successful?

Decision block.
Is another LTG load type (SY.PSW.Txxx file) of the CURRENT GENERATION
Y h ... 3
N h ... 6

Repeat APS quarterly saving.
Since the startup test with the LTG loading software during SW210 / SW211
was unsuccessful, the APS quarterly saving according to SW210 is to be
executed for a second time!
h ... MMN:SW,
PROC, SW210
End of procedure.

Customer-specific files which are not part of the save tape must possibly be
created again. These files are not covered by this procedure.
If the DISP FILE command results in a dummy output, generation file(s)
SY.LOADLIB.CA/LA/MA is (are) defective, not valid, or not present on both
disks.
DISP FILE;
command repetition
EXECD
@################## @#############################
FILE
GEN
SIZE VSN000
VSN001
CLASS TYPE
-----------------+--------+------+-------------+-------------+-----+---filename
@####### @##### @############ @############ @### @###
:
:
:
:
:
:
:
:
DOUBLE FAILURE OF A GENERAL FILE:

Decision block.
Is (are) the file(s) SY.LOADLIB.CA/LA/MA of the CURRENT GENERATION
(If DISP FILE command results in a default output, the answer is YES!)
A30808-X3074-A473-2-7620
Y h ... 9
N h ... 18
EY502 - 3
EMCYMN

Restoration of the defective file (disk).
SY.LOADLIB.MA/LA/CA of the CURRENT GENERATION (actgen) are defective, not valid or not present (only one, both or all files). The following
TRANS SYFILE command is always to be executed for all files, first for
SY.LOADLIB.MA and then for SY.LOADLIB.LA/CA. If only one file is affected,
the rejection of the second command is to be ignored.
SY.LOADLIB.MA/LA/CA are the names which are to be entered for the parameter FILE. The parameter GEN must be given the name of the CURRENT
GENERATION.
In direct mode (BMML) the following command is to be typed without the pathname - DISKFAIL :
TRANS SYFILE - DISKFAIL:GEN=actgen,FILE=name,VSN=SYSVSN;

command repetition
:
:
command repetition
ACCEPTED
:
:
:
:
:
:
EXECD
h ... 10
After the commands for all files were input, the following questions are to be
answered.
10

Were commands rejected?
Rejected means that the command was not started at all and a corresponding
error message occurred. If commands were rejected the corresponding file
cannot be repaired. Possible reasons for rejecting are:
SY.GENLIST is defective, not valid or not present
defect sector in catalog
defect sector on file
no spare sectors available
magnetic tape error

Commands were rejected. The corresponding files cannot be restored!
All commands were accepted.
11
h ... 50
h ... 11

Success of restoration measures.
Not successful means that the TRANS SYFILE command is acknowledged
with NOT EXECD.
Restoration measures were successful:
Restoration measures were not successful:
EY502- 4
h ... 14
h ... 12
A30808-X3074-A473-2-7620
12
EMCYMN

Restoration of the defective file (save tape).
Mount and load the latest (startup tested) APS save tape (part 1) in MTD.
SY.LOADLIB.MA/LA/CA of the CURRENT GENERATION (actgen) are defective, not valid or not present (only one, both or all files). The following
TRANS SYFILE command is always to be executed for all files, first for
SY.LOADLIB.MA and then for SY.LOADLIB.LA/CA. If only one file is affected,
the rejection of the second command is to be ignored.
SY.LOADLIB.MA/LA/CA are the names which are to be entered for the parameter FILE. The parameter GEN must be given the name of the CURRENT
GENERATION.
TRANS SYFILE - DISKFAIL:GEN=actgen,FILE=name,VSN=SA1TAP;

command repetition
ACCEPTED

command repetition
EXECD
After the commands for all files were input the following question is to be
answered.
13
h ... 13

Success of restoration measures.
Not successful means that the TRANS SYFILE command is acknowledged
with NOT EXECD.
14
Restoration measures from SA1TAP were successful:
h ... 14
Restoration measures were not successful. There is no possibility to restore

the file!
h ... 50

Connecting of SY.LOADLIB.MA/LA/CA.
The following command is always to be executed for SY.LOADLIB.MA/LA/CA.

(If a NOT EXECD message occurs with DLL-No. 16 it can be ignored as long as
the respective file is already connected.)
command repetition
EXECD
After the commands for all files were input, all possibly deactivated IOPLAUS
and X25LINKs are to be reactivated:
Possibly deactivated IOPLAUs and X25LINKs are to be activated again.
A30808-X3074-A473-2-7620
h ... 15
EY502 - 5
EMCYMN
15
b

Are further generation files defective?
DISP FILE;
command repetition
EXECD
@################## @#############################
FILE
GEN
SIZE VSN000
VSN001
CLASS TYPE
-----------------+--------+------+-------------+-------------+-----+---filename
@####### @##### @############ @############ @### @###
:
:
:
:
:
:
:
:
The printout above is to be evaluated, in order to check whether or not further

generation files of the CURRENT GENERATION are defective:
At least one additional file of the CURRENT GENERATION (actgen) is
defective, not valid or not present.
h ... 17
h ...EMCYMN,
No further generation file is defective:
PROC, EY503
16

Further defective files in the CURRENT GENERATION <actgen>.
File SY.GENLIST is defective, not valid or not present.
This file cannot be restored!
h ... 50
One of the generation files of the CURRENT GENERATION (actgen) is

defective, not valid or not present.
h ... 17
h ...EMCYMN,
No generation file of the CURRENT GENERATION (actgen) is defective.
PROC, EY503
17

SY.SIMP
Is the file SY.SIMP of the CURRENT GENERATION (actgen) defective, not valid
or not present?
18

SY.SEMILIB
Is the file SY.SEMILIB of the CURRENT GENERATION (actgen) defective, not
valid or not present?
19
Y h ... 19
N h ... 18
Y h ... 38
N h ... 19

Changes in CCS7 database.
Did the CCS7 database change since the APS save tape was created?
EY502- 6
Y h ... 50
N h ... 20
A30808-X3074-A473-2-7620
20
EMCYMN

CCS7 patches.
Have CCS7 patches been incorporated in the APS since the save tape was
created?
21
Y h ... 50
N h ... 21

Configuration of MDD.
The SY.SIMP generation file cannot be restored individually. It is possible,

however to transfer all APS quarterly save tape files and to update the semipermanent data (UPD GEN;) and thereby correct the fault in the CCNC database
without fallback to an older generation (ISTART2G).
Together with the next higher TAC level the decision about further measures is
to be made. It is to be decided whether or not all APS quarterly save tape files
should be transferred from tape to disk according to the following steps, after
saving of charge and log files.
MOD LOGFILE:FILE=LOG6,SIZE=24,ERASE=YES;
switch off MDD-0
switch off MDD-1
Wait for failure message:
(Failure messages and alarms are to be ignored!)
DOUBLE DISK FAILURE!
switch on MDD-0
switch on MDD-1
Wait approx. 1 minute!
Configure both MDD to OST=MBL:
b
b
b
b
CONT MDDACT:LABEL;
CONFIGURATION
MDD-0
A30808-X3074-A473-2-7620
FROM
MBL
TO
ACT
EY502 - 7
EMCYMN
22

Tape to disk transfer of save tape files.
Mount and load the latest (startup tested) APS quarterly save tape (part 1) in
MTD.
(actgen) which is active at the moment.(If necessary/possible find out by using
command DISP GEN):
TRANS SYFILE - DISKFAIL:GEN=actgen,VSN=SA1TAP;

command repetition
ACCEPTED

TRANSSYFILE:GEN=actgen,VSN=SA1TAP
TRANSFER RESULT
PART. EXECD
ERROR
BYTES /
START-/
FILE
GENER.
VSN
STAT
ID NO
RECORDS
END TIME
-+-----------------+--------+------+------+----------+---------+-------@ SY.INSTALL
@####### SA1TAP @#### @### @### @######## @#######
@ SY.INSTALL
@####### SYSVSN @#### @### @### @######## @#######
@ SY.LOADLIB.CA
@####### SA1TAP @#### @### @### @######## @#######
@ SY.LOADLIB.CA
@####### SYSVSN @#### @### @### @######## @#######
@ SY.LOADLIB.MA
@####### SA1TAP @#### @### @### @######## @#######
@ SY.LOADLIB.MA
@####### SYSVSN @#### @### @### @######## @#######
@ SY.LOADLIB.LA
@####### SA1TAP @#### @### @### @######## @#######
@ SY.LOADLIB.LA
@####### SYSVSN @#### @### @### @######## @#######
@ SY.PSW.Txxx
@####### SAxTAP @#### @### @### @######## @#######
@ SY.PSW.Txxx
@####### SYSVSN @#### @### @### @######## @#######
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
@ SY.SIMP
@####### SAxTAP @#### @### @### @######## @#######
@ SY.SIMP
@####### SYSVSN @#### @### @### @######## @#######
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
@ SY.MSGXREF
@####### SAxTAP @#### FTSY 121
@######## @#######
The TRANS SYFILE command is acknowledge with PART. EXECD, since the
file SY.INSTALL already exists on the background memories and the file
SY.MSGXREF is the first generationless file on the tape (Error: FILE L FA 121)
and is therefore not transferred.
23

Tape to disk transfer successful?
Were all files belonging to the CURRENT GENERATION (actgen) transferred to
disk (compare the system printout with the output mask above)?
EY502- 8
Y h ... 25
N h ... 24
A30808-X3074-A473-2-7620
24
EMCYMN

Carry out tape to disk transfer once again (preparation).
The tape to disk transfer of previous steps was terminated abnormally or not
executed completely. Consult the next higher TAC level in order to decide on a
repetition of the tape to disk transfer.
The following preparatory steps must be executed in the given sequence:
switch off MDD-x


switch on MDD-x
In direct mode (BMML) the following command is to be typed without the pathname - DIAG:
b
b
b
25
b
DIAG MDD - DIAG:MDD=x;

CONF MDD:MDD=x,OST=ACT;

Updating of semipermanent data.
UPD GEN;
command repetition
h ... 22
CONT MDDACT:LABEL;
EXECD
DACT FNS:FNS=X;
;
command repetition
26
EXECD

Continuation tape handling.
Y h ... 28
N h ... 27
Was continuation tape handling carried out during the APS saving?
27

Tape to disk transfer of non-generation files (no continuation tape).
Mount and load APS quarterly save tape.
TRANS FILE:FILE=X,VSNS=SA1TAP;
command repetition
A30808-X3074-A473-2-7620
ACCEPTED
h ... 29
EY502 - 9
EMCYMN
28

Tape to disk transfer of non-generation files (continuation tape).
command repetition
ACCEPTED

EY502- 10
h ... 29
A30808-X3074-A473-2-7620
29
i
EMCYMN

The previous TRANS FILE command was acknowledged with PART. EXECD,
since all files marked with error L FA 12 had already been transferred by the
previous TRANS SYFILE command. So these files were already present on
disk!
command repetition
SENDER
RECEIVER
PART.EXECD
: @#######
: @#######
START START
FILE IDENTIFICATION
DATA TYPE
BYTES/
/END- /END: FILE
VSN
STATE : ERROR
RECORDS
DATE TIME
-+-----------------+------+-----+-+-----+-+--+----+---------+-----+----S SY.GENLIST
SA1TAP NTR
@ PARAM L FC 24
@######## @#### @####
R SY.GENLIST
@##### NCR
@ @#### @ @# @### @######## @#### @####
S SY.INSTALL
SA1TAP NTR
@ PARAM L FC 24
@######## @#### @####
R SY.INSTALL
@##### NCR
@ @#### @ @# @### @######## @#### @####
S SY.LOADLIB.CA
SA1TAP NTR
@ PARAM L FA 12
@######## @#### @####
R SY.LOADLIB.CA
@##### NCR
@ @#### @ @# @### @######## @#### @####
S SY.LOADLIB.LA
SA1TAP NTR
@ PARAM L FA 12
@######## @#### @####
R SY.LOADLIB.LA
@##### NCR
@ @#### @ @# @### @######## @#### @####
S SY.LOADLIB.MA
SA1TAP NTR
@ PARAM L FA 12
@######## @#### @####
R SY.LOADLIB.MA
@##### NCR
@ @#### @ @# @### @######## @#### @####
S SY.PSW.Txxx
SA1TAP NTR
@ PARAM L FA 12
@######## @#### @####
R SY.PSW.Txxx
@##### NCR
@ @#### @ @# @### @######## @#### @####
:
:
:
S SY.PSW.Tyyy
SAxTAP NTR
@ PARAM L FA 12
@######## @#### @####
R SY.PSW.Tyyy
@##### NCR
@ @#### @ @# @### @######## @#### @####
S SY.TASKLIB
SAxTAP NTR
@ PARAM L FA 12
@######## @#### @####
R SY.TASKLIB
@##### NCR
@ @#### @ @# @### @######## @#### @####
S SY.SEMILIB
SAxTAP NTR
@ PARAM L FA 12
@######## @#### @####
R SY.SEMILIB
@##### NCR
@ @#### @ @# @### @######## @#### @####
S SY.SIMP
SAxTAP NTR
@ PARAM L FA 12
@######## @#### @####
R SY.SIMP
@##### NCR
@ @#### @ @# @### @######## @#### @####
R SY.MSGXREF
SAxTAP TR
@ @#### @ @# @### @######## @#### @####
R SY.MSGXREF
@##### CRD
@ @#### @ @# @### @######## @#### @####
R SJ.SECDATA
SAxTAP TR
@ @#### @ @# @### @######## @#### @####
R SJ.SECDATA
@##### CRD
@ @#### @ @# @### @######## @#### @####
R D9.VLRAL
SAxTAP TR
@ @#### @ @# @### @######## @#### @####
R D9.VLRAL
@##### CRD
@ @#### @ @# @### @######## @#### @####
R CG.SA.xxxxx
SAxTAP TR
@ @#### @ @# @### @######## @#### @####
R CG.SA.xxxxx
@##### CRD
@ @#### @ @# @### @######## @#### @####
:
:
:
A30808-X3074-A473-2-7620
EY502 - 11
EMCYMN
30

The list of files shown below represents the expected status of the disk content:
DISP FILE;
command repetition
EXECD
@################## @#############################
FILE
GEN
SIZE VSN000
VSN001
CLASS TYPE
-----------------+--------+------+-------------+-------------+-----+---CG.SA.xxxxx
@####### @##### @############ @############ @### SAM
:
:
:
:
:
:
:
CG.SA.yyyyy
@####### @##### @############ @############ @### SAM
D9.VLRAL
@####### @##### @############ @############ @### SAM
HF.xxxxxx
@####### @##### @############ @############ @### CYC
IA.xxxxxx
@####### @##### @############ @############ PP
CYC
LG.LOGx.Ay
@####### @##### @############ @############ PP
SAM
MS.xxxxxx
@####### @##### @############ @############ @### PAM
SG.xxxxxx
@####### @##### @############ @############ @### CYC
SJ.SECDATA
@####### @##### @############ @############ APS
PAM
SY.GENLIST
@####### @##### @############ @############ APS
PAM
SY.INSTALL
@####### @##### @############ @############ APS
PAM
SY.LOADLIB.CA
xxxxxxxx @##### @############ @############ APS
PAM
SY.LOADLIB.LA
xxxxxxxx @##### @############ @############ APS
PAM
SY.LOADLIB.MA
xxxxxxxx @##### @############ @############ APS
PAM
SY.MSGXREF
@####### @##### @############ @############ APS
PAM
SY.PSW.Txxx
xxxxxxxx @##### @############ @############ APS
PAM
:
:
:
:
:
:
:
SY.PSW.Tyyy
xxxxxxxx @##### @############ @############ APS
PAM
SY.SEMILIB
xxxxxxxx @##### @############ @############ APS
PAM
SY.SIMP
xxxxxxxx @##### @############ @############ APS
PAM
SY.TASKLIB
xxxxxxxx @##### @############ @############ APS
PAM
SY.TRANSLOG
@####### @##### @############ @############ APS
PAM
31

Decision block.
Y h ... 34
N h ... 32
Are all files of the APS quarterly save tape available on disk?
32

Prepare repetition of tape to disk transfer.
Transfer error:
Delete all files that have already been transferred to disk via TRANS FILE
command. After this carry out the tape to disk transfer again.
Other reasons (e.g. tape not readable):
EY502- 12
h ... 26
h ... 33
A30808-X3074-A473-2-7620
33
EMCYMN

Other reasons.
Load MTD with next elder valid APS quarterly save tape (part 1).
The tape to disk transfer must be repeated completely, i.e. including generation
files.
switch off MDD-0
switch on MDD-0
Wait approx. 1 minute
b
b
b
34
DIAG MDD - DIAG:MDD=0;

h ... 22
CONT MDDACT:LABEL;
Unload quarterly save tape / load routine save tape.
Rewind and remove APS quarterly save tape.
Mount and load the latest routine save tape (VSN=LOGTAP).
35
b
DOUBLE FAILURE OF A GENERATION FILE.

Tape to disk transfer of statistic files.
TRANS FILE:FILE=CA.,VSNS=LOGTAP;
command repetition
ACCEPTED
command repetition
EXECD
SENDER
RECEIVER
: @#######
: @#######
START START
FILE IDENTIFICATION
DATA TYPE
BYTES/
/END- /END: FILE
VSN
STATE : ERROR
RECORDS
DATE TIME
-+-----------------+------+-----+-+-----+-+--+----+---------+-----+----S CA.ST.UCHA
LOGTAP TR
@ @#### @ @# @### @######## @#### @####
R CA.ST.UCHA
@##### CRD
@ @#### @ @# @### @######## @#### @####
A30808-X3074-A473-2-7620
EY502 - 13
EMCYMN
36

Post-processing.
If the updating of the semipermanent data by using command UPD GEN; was
successful carry out the following measures on consultation with the next higher
TAC level:
update IA files
transfer previously saved LOG files to disk
activate protected file name segments
configure redundant disk to ACT
At this point the next saving specified in the safeguarding concept is to be

carried out according to MMN:SW:
i....MMN:SW,
PROC, SW210
37

Checksum error.
Was a checksum error in file SY.SIMP of the CURRENT GENERATION (actgen)
the reason for the previous measures?
Y h ...EMCYMN,
PROC, EY501
N h ... 51
38
b

Update semipermanent data.
UPD GEN;
command repetition
39
EXECD
h ... 39

Decision block.
Is another file of the CURRENT GENERATION (actgen) defective, not valid or
not present?
Y h ... 40
N h ...EMCYMN,
PROC, EY503
EY502- 14
A30808-X3074-A473-2-7620
40
EMCYMN

Restoration of the defective file from disk.
The parameter GEN must be given for the CURRENT GENERATION <actgen>.
In direct mode (BMML) the following command is to be typed without the pathname -DISKFAIL :
TRANS SYFILE - DISKFAIL:GEN=actgen,FILE=name,VSN=SYSVSN;

command repetition
:
:
command repetition
ACCEPTED
:
:
:
:
:
:
EXECD
Y h ... 43
N h ... 41
Was the transfer of the file(s) successful?
41

Restoration of the defective file from tape.
Mount and load the latest (startup tested) APS quarterly save tape (part 1) in
MTD, after the next higher TAC level has been consulted.
TRANS SYFILE - DISKFAIL:GEN=actgen,FILE=name,VSN=SA1TAP;

command repetition
ACCEPTED

command repetition
EXECD
After the commands for all files were input the following question is to be
answered.
42
h ... 42

Rejected means that the command was not started at all and a corresponding
error message occurred. If commands were rejected the corresponding file
cannot be repaired. Possible reasons for rejecting are:
SY.GENLIST is defective, not valid or not present
defect sector in catalog
defect sector on file
no spare sectors available
magnetic tape error
Commands were rejected. The corresponding files cannot be restored!

All commands were accepted.
A30808-X3074-A473-2-7620
h ... 48
h ... 43
EY502 - 15
EMCYMN
43

Other defective generation files.
Is another generation file of the CURRENT GENERATION (actgen) defective,
not valid or not present?
44

Defective file(s) in BACKUP GENERATION.
Is one of the generation files of the BACKUP GENERATION defective, not valid
or not present?
45
i
Y h ... 40
N h ... 44
Y h ... 45
N h ... 46

Defective file(s) in BACKUP GENERATION.
The next saving specified in the safeguarding concept is to be immediately
carried out according to MMN:SW, procedure SW210 !
i....MMN:SW,
PROC, SW210
After procedure SW210 has been successfully completed, this procedure is to
be continued:
46
h ... 46

Defective file(s) in GOLDEN GENERATION.
Is one of the generation files of the GOLDEN GENERATION defective, not valid
or not present?
EY502- 16
Y h ... 47
N h ... 50
A30808-X3074-A473-2-7620
47
i
EMCYMN

Defective file(s) in GOLDEN GENERATION.
The next quarterly saving specified in the safeguarding concept is to be immediately carried out according to MMN:SW, procedure SW210 !
If file LOG6 is not already active, the following steps are to be carried out in
advance:
b
The LOG file which has just been closed is to be saved on the current routine
save tape (LOGTAP) and after this deleted from the background memories.
Before the tape saving of the LOG file is started, the file DUMMY.MET must be
deleted on the LOGTAP!
Carry out quarterly saving:
i ... MMN:SW,
PROC, SW210
After procedure SW210 has been successfully completed, this procedure is to
be continued:
48

Restoration of files not possible.
Are files of the GOLDEN GENERATION (goldgen) defective, not valid or not
present?
49
h ... 50
Y h ... 48
N h ... 50

Manual start from APS save tape generation.
A fall back on the GOLDEN GENERATION on the background memories is not

possible. A manual initial start using the GOLDEN GENERATION on the save
tape is to be carried out. The content of the APS save tape can be transferred
ONLINE to disk.
All further actions should only be done in accordance with the next higher
TAC level!
The following preparatory steps must be executed in the given sequence:
switch off MDD-x

switch off MDD-y
MDD-*#: INOPERABLE AND THEREFORE DEACTIVATED.
A30808-X3074-A473-2-7620
EY502 - 17
EMCYMN
switch on MDD-x
h ...EMCYMN,
DIAG MDD - DIAG:MDD=x;
PROC, EY504
50

ISTART2G.
There is no possibility to restore the defective file!

After consulting the next higher TAC level a fall back to an older generation
(ISTART2G) is to be carried out according to EMCYMN, procedure EY190.
i....EMCYMN,
PROC, EY190
Was a checksum error in file SY.SIMP of the CURRENT GENERATION (actgen)
the reason for the ISTART2G ?
Y h ...EMCYMN,
PROC, EY501
N h ... 52
51

Symptom saving.
Y i....MMN:SW,
Are symptoms to be saved on tape?
PROC, SW231
N h ... 52
52

Symptom saving / post-processing.
It is to be decided in each individual case whether it is necessary or possible to

save call charges and/or symptoms from the redundant disk by splitting the
system.
If necessary, the redundant disk is now to be cleared of faults according to
MMN:CP113, procedure CP890:
53
h ...MMN:CP113,
PROC, CP890

End of procedure.
END
EY502- 18
A30808-X3074-A473-2-7620
3.19
EMCYMN

EY503
3.19.1
Introduction
The procedure describes the transfer of generation files from an startup tested APS
quarterly save tape without adverse effects on the switching operations if the contents
of both background memories are destroyed (double file, catalog or disk failure) and the
saving of meter files and symptoms.
This procedure is always carried out in the net work node in case of transfer from the
APS quarterly save tape.
a) Transfer from the most recent valid APS quarterly save tape of category B, if this is
not successful:
b) Transfer from the next to the last recent valid APS quarterly save tape of category B,
- MMN:CP113 if copying of the disk is not successful
A30808-X3074-A473-2-7620
EY503 - 1
EMCYMN
3.19.2

3.19.3
DOUBLE FAILURE OF A NON-GENERATION FILE.

DISP FILE;
command repetition
EXECD
@################## @#############################
FILE
GEN
SIZE VSN000
VSN001
CLASS TYPE
-----------------+--------+------+-------------+-------------+-----+---filename
@####### @##### @############ @############ @### @###

Decision block.
Are files defective, not valid, or not present which do not belong to a generation?
Y h ... 3
N h ... 22
DOUBLE FAILURE OF A FILE NOT BELONGING TO A GENERATION.

SJ.SECDATA defective?
Y h ... 4
N h ... 6
Is the file SJ.SECDATA defective, not valid or not present?
4
b

Update file SJ.SECDATA
UPD SECDATA:
command repetition
EXECD

Cyclic IA file defective?
Is the file which is defective, not valid, or not present a cyclic IA file?
EY503- 2
Y h ... 6
N h ... 14
A30808-X3074-A473-2-7620
6
b
EMCYMN
DOUBLE FAILURE OF A CYCLIC IA FILE.

Deactivate recording of call data.
DISP IAFEAT;
command repetition
EXECD
- Cancel active features:
CAN IAFEAT:TYPE=feature;
DANGEROUS COMMAND CANIAFEAT READY TO EXECUTE<
;
command repetition
7
b
EXECD
DOUBLE FAILURE OF ACYCLIC IA FILE.

DISP FILE:FILE=IA.;
command repetition
EXECD
@################## @#############################
FILE
GEN
SIZE VSN000
VSN001
CLASS TYPE
-----------------+--------+------+-------------+-------------+-----+---filename
@####### @##### @############ @############ @### @###
:
:
:
:
:
:
:
:

IA file still present?
Y h ... 9
N h ... 10
Is the IA file still present?

Rename the IA file.
If possible, the IA file is to be saved on tape. Otherwise the file authorization is to

be updated as follows:
MOD FILEAUT:FILE=name,SAFCOP=1;
Because of the protected file name segment IA it may be necessary to change

the corresponding file attribute before executing the following commands:
b
b
DACT FNS:FNS=fns;
CAT FILE:FILE=new_name/old_name;
command repetition
A30808-X3074-A473-2-7620
EXECD
EY503 - 3
EMCYMN
10
b
DOUBLE FAILURE OF A CYCLIC IA FILE

Activate call data recording.
ACT IAFEAT:TYPE=feature,SIZE=size;
DANGEROUS COMMAND ACTIAFEAT READY TO EXECUTE<
;
command repetition
11
b
EXECD

DISP FILE;
command repetition
EXECD
@################## @#############################
FILE
GEN
SIZE VSN000
VSN001
CLASS TYPE
-----------------+--------+------+-------------+-------------+-----+---filename
@####### @##### @############ @############ @### @###
:
:
:
:
:
:
:
:
12

Another cyclic IA file defective?
Y h ... 6
N h ... 13
Is there another cyclic IA file that is defective, not valid, or not present?
13

Delete file.
If the tape saving of the IA files was successful, delete the files that were
renamed. If the files couldnt be saved successfully and therefore are to be kept
for later postprocessing, the procedure is to be continued with:
DEL FILE:FILE=new name;

command repetition
14
EXECD
DOUBLE FAILURE OF A LOG FILE.

Defective LOG file?
Is the file which is defective, not valid or not present a a LOG file?
EY503- 4
Y h ... 15
N h ... 17
A30808-X3074-A473-2-7620
15
EMCYMN

Postprocessing for LOG files.
Creation of a LOG file and of a BACKUP GENERATION (backgen) is carried out

as part of an advance routing saving. As an advance provision for the corresponding command file, the active LOG function has to be deactivated and then
activated again with the old file name (to be used in the SET LOG; command for
LOG file name).
Attention:
The safeguarding concept is ensured through this saving. It must however be
noted, that the LOG file saved in this way does not contain the LOG commands
which were entered from the last save time until the present. It is possible that
the necessary steps for saving these data must be taken:
RSET LOG;
;
command repetition
EXECD
Because of a protected file name segment it may be necessary to change the

appropriate file attribute before executing the following command:
DACT FNS:FNS=fns;
b
b
;
command repetition
EXECD
SET LOG:SIZE=24,ERASE=YES,FILE=logfilename;
Delete the file renamed previously:

command repetition
16
EXECD

Postprocessing for LOG files.
Attention:
At this point the next saving specified in the safeguarding concept must be
carried out in accordance with MMN:SW:
i ... MMN:SW,
PROC, SW210
When Procedure SW210 has been completed successfully, continue procedure
EY503 with:
A30808-X3074-A473-2-7620
h ... 17
EY503 - 5
EMCYMN
17
DOUBLE FAILURE OF A GENERAL FILE.

Another cyclic file defective or invalid?
Y h ... 18
N h ... 22
Is there another cyclic file that is defective, not valid, or not present?
18

Rename the defective or invalid file.
Because of the protected file name segment it may be necessary to change the
corresponding file attribute before executing the following commands:
b
b
DACT FNS:FNS=fns;
command repetition
19
EXECD

CA-file defective?
Y h ... 20
N h ... 22
Is the file which is defective, not valid or not present a CA-file?
20
b

Save meters.
SAVE MET;
command repetition
21
EXECD
h ... 21

Mount and load the APS save tape (part 1).

The parameter FILE in the following command must be given the name of the
file to be transferred:
TRANS FILE:FILE=name,VSNS=SA1TAP;
command repetition
ACCEPTED

displayed after the end of tape was reached, proceed with continuation tape
command repetition
SENDER
RECEIVER
EXECD
: @#######
: @#######
START START
FILE IDENTIFICATION
DATA TYPE
BYTES/
/END- /END: FILE
VSN
STATE : ERROR
RECORDS
DATE TIME
-+-----------------+------+-----+-+-----+-+--+----+---------+-----+----S @########
SAxTAP TR
@ @#### @ @# @### @######## @#### @####
R @########
@##### CRD
@ @#### @ @# @### @######## @#### @####
EY503- 6
A30808-X3074-A473-2-7620
22
EMCYMN

DISP FILE;
command repetition
EXECD
@################## @#############################
FILE
GEN
SIZE VSN000
VSN001
CLASS TYPE
-----------------+--------+------+-------------+-------------+-----+---filename
@####### @##### @############ @############ @### @###
:
:
:
:
:
:
:
:
23

All files available?
Y h ... 24
N h ... 17
Are all save tape files available on disk?
24

Delete files.
Delete the files renamed previously:

command repetition
25
EXECD

Update security data.
Update access security data:
UPD SECDATA;
command repetition
26
EXECD

Symptoms to be saved?
Are symptoms to be saved on tape?
Y i ... MMN:SW,
PROC, SW231
N h ... 27
A30808-X3074-A473-2-7620
EY503 - 7
EMCYMN
27
SYMTOM SAVING:
Postprocessing.
Note:
It must be decided in each individual case whether it is necessary or possible to
system.
If necessary, the redundant disk is now to be cleared of faults according to the
MMN:CP113:
h ...MMN:CP113,
PROC, CP890
End of procedure.
28
End of procedure.
END
EY503- 8
A30808-X3074-A473-2-7620
3.20
EMCYMN

EY504
3.20.1
Introduction
The procedure describes the transfer of generation files from a fallback generation or an
(startup tested) APS quarterly save tape without adverse effects on the switching operations if the contents of both background memories are destroyed (double file, catalog
or disk failure) and the saving of meter files and symptoms.
Customer-specific files which are not part of the save tape must possibly be created
again. These files are not covered by this procedure!
This procedure is always carried out in the network node.
If the transfer of files to a background memory is not successful, the procedure must be
repeated with the redundant background memory.
a) Transfer from the most recent valid APS quarterly save tape of category B, if this is
not successful:
b) Transfer from the next to the last recent valid APS quarterly save tape of category B,
A30808-X3074-A473-2-7620
EY504 - 1
EMCYMN
3.20.2

3.20.3
DOUBLE DISK FAILURE:

Configuration MDD.
Configure the MDD which was diagnosed, or which was cleared of faults to
OST = ACT :
CONF MDD:MDD=0x,OST=ACT;
At this point, one of the three following masks (2110, 2111, 2120) is possible as
a response:
THE ACTUAL GENERATION @####### WITH THE CREATION DATE @####### @#######
IS VALID AND COMPLETE ON THE DISK TO BE ACTIVATED.
PLEASE ENTER :
STOP MDDACT; OR
CONT MDDACT:LABEL; OR
CONT MDDACT;
THE ACTUAL GENERATION ON @###@# IS NOT COMPLETE AND VALID.

ACTIVATION WITHOUT LABELING NOT POSSIBLE
PLEASE ENTER :
STOP MDDACT; OR
CONT MDDACT:LABEL;
VOL-LABEL OF @###@# IS INVALID

ACTIVATION WITHOUT LABELING NOT POSSIBLE
PLEASE ENTER :
STOP MDDACT; OR
CONT MDDACT:LABEL;
command repetition
ACCEPTED
In each case continue with following command:
CONT MDDACT:LABEL;
command repetition
CONFIGURATION
EY504- 2
MDD-x
EXECD
FROM
MBL
TO
ACT
A30808-X3074-A473-2-7620
EMCYMN

Before loading the quarterly save tape, remove any other tape (e.g. APS routine
save tape) still in the tape device. If necessary/possible: rewind tape with:
REWIND MT:MTD=0;
(otherwise press keys RESET and REW/UNLD).

Mount and load the latest (startup tested) APS quarterly save tape (part 1)
The APS quarterly save tape contains the following files:

- generation list SY.GENLIST
- installation program SY.INSTALL (IMON)
- office database at time of interval save SY.SEMILIB
- non-resident system software files SY.LOADLIB.CA/LA/MA
- application program system (APS) SY.TASKLIB
- message group reference list SY.MSGXREF
- CCNC database file SY.SIMP
- access security data SJ.SECDATA
- GP software files SY.PSW.Txxx
- file D9.VLRAL
- procedure command files CG.SA.xxxxx
A30808-X3074-A473-2-7620
EY504 - 3
EMCYMN


- DISKFAIL:
In the following TRANS SYFILE command the parameter GEN must be given
the name of the CURRENT GENERATION (actgen) which is active at the
moment: (If necessary/possible find out with DISP GEN:VSN=SA1TAP;)
TRANS SYFILE - DISKFAIL:GEN=actgen,VSN=SA1TAP;

command repetition
ACCEPTED
If the message:
command repetition
EXECD
TRANSFER RESULT
ERROR
BYTES /
START-/
FILE
GENER.
VSN
STAT
ID NO
RECORDS
END TIME
-+-----------------+--------+------+------+----------+---------+-------@ SY.INSTALL
@####### SA1TAP @#### @### @### @######## @#######
@ SY.INSTALL
@####### SYSVSN @#### @### @### @######## @#######
@ SY.LOADLIB.CA
@####### SA1TAP @#### @### @### @######## @#######
@ SY.LOADLIB.CA
@####### SYSVSN @#### @### @### @######## @#######
@ SY.LOADLIB.MA
@####### SA1TAP @#### @### @### @######## @#######
@ SY.LOADLIB.MA
@####### SYSVSN @#### @### @### @######## @#######
@ SY.LOADLIB.LA
@####### SA1TAP @#### @### @### @######## @#######
@ SY.LOADLIB.LA
@####### SYSVSN @#### @### @### @######## @#######
@ SY.PSW.Txxx
@####### SAxTAP @#### @### @### @######## @#######
@ SY.PSW.Txxx
@####### SYSVSN @#### @### @### @######## @#######
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
@ SY.SIMP
@####### SAxTAP @#### @### @### @######## @#######
@ SY.SIMP
@####### SYSVSN @#### @### @### @######## @#######
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
@ SY.MSGXREF
@####### SAxTAP @#### FTSY 121
@######## @#######

All files transferred?
Were all files which belong to the CURRENT GENERATION (actgen) transferred? (see the expected output mask)
EY504- 4
Y h ... 8
N h ... 5
A30808-X3074-A473-2-7620
EMCYMN

Preparation for repetition of TRANSSYFILE.
The transfer process was terminated abnormally, or not executed completely,

for one of the following reasons:
Transfer error:
The following steps must be executed in the specified sequence:
- Switch off MDD-x
- Wait for failure message
- Switch on MDD-x again
- Wait for approx. 1 minute
command repetition
EXECD

- DIAG:
DIAG MDD- DIAG:MDD=x;

command repetition
command repetition
EXECD
CONT MDDACT:LABEL;
command repetition
EXECD
EXECD

Decision of continuation tape.
Was continuation tape handling performed in the exchange when the APS quarterly saving was done?
Y
h ... 7
N h ... 3

Mount tape.
h ... 3
Rewind and remove APS save tape (part x)

Mount and load APS quarterly save tape (part 1)
h ... 3
Other reasons (e.g. tape not readable):

Load MTD with the next elder APS quarterly save tape (part 1)
8
b

Update semipermanent data.
UPD GEN;
command repetition
ACCEPTED
Was update of semipermanent database successfully executed (EXECD)?
A30808-X3074-A473-2-7620
Y h ... 10
N h ... 9
EY504 - 5
EMCYMN
Manual initial start from Save tape

Manual initial start from Save tape according to Procedure EY150 is to be done
in accordance with the responsible TAC-department.
10
b
h ...EMCYMN,
PROC, EY150
DACT FNS
DACT FNS:FNS=X;
;
command repetition
EY504- 6
EXECD
A30808-X3074-A473-2-7620
11
EMCYMN

IMPORTANT:
The following TRANS FILE command is acknowledged with PART. EXECD
because the files marked with error L FA 12 were already transferred with the
previous TRANS SYFILE command and thus are already present on the disk.
Mount and load APS quarterly save tape (part 1):
command repetition
ACCEPTED
If the message:
command repetition
SENDER
RECEIVER
PART.EXECD
: @#######
: @#######
START START
FILE IDENTIFICATION
DATA TYPE
BYTES/
/END- /END: FILE
VSN
STATE : ERROR
RECORDS
DATE TIME
-+-----------------+------+-----+-+-----+-+--+----+---------+-----+----S SY.GENLIST
SA1TAP NTR
@ PARAM L FC 24
@######## @#### @####
R SY.GENLIST
@##### NCR
@ @#### @ @# @### @######## @#### @####
S SY.INSTALL
SA1TAP NTR
@ PARAM L FC 24
@######## @#### @####
R SY.INSTALL
@##### NCR
@ @#### @ @# @### @######## @#### @####
S SY.LOADLIB.CA
SA1TAP NTR
@ PARAM L FA 12
@######## @#### @####
R SY.LOADLIB.CA
@##### NCR
@ @#### @ @# @### @######## @#### @####
S SY.LOADLIB.LA
SA1TAP NTR
@ PARAM L FA 12
@######## @#### @####
R SY.LOADLIB.LA
@##### NCR
@ @#### @ @# @### @######## @#### @####
S SY.LOADLIB.MA
SA1TAP NTR
@ PARAM L FA 12
@######## @#### @####
R SY.LOADLIB.MA
@##### NCR
@ @#### @ @# @### @######## @#### @####
S SY.PSW.Txxx
SA1TAP NTR
@ PARAM L FA 12
@######## @#### @####
R SY.PSW.Txxx
@##### NCR
@ @#### @ @# @### @######## @#### @####
:
:
:
S SY.PSW.Tyyy
SAxTAP NTR
@ PARAM L FA 12
@######## @#### @####
R SY.PSW.Tyyy
@##### NCR
@ @#### @ @# @### @######## @#### @####
S SY.TASKLIB
SAxTAP NTR
@ PARAM L FA 12
@######## @#### @####
R SY.TASKLIB
@##### NCR
@ @#### @ @# @### @######## @#### @####
S SY.SEMILIB
SAxTAP NTR
@ PARAM L FA 12
@######## @#### @####
R SY.SEMILIB
@##### NCR
@ @#### @ @# @### @######## @#### @####
S SY.SIMP
SAxTAP NTR
@ PARAM L FA 12
@######## @#### @####
R SY.SIMP
@##### NCR
@ @#### @ @# @### @######## @#### @####
R SY.MSGXREF
SAxTAP TR
@ @#### @ @# @### @######## @#### @####
R SY.MSGXREF
@##### CRD
@ @#### @ @# @### @######## @#### @####
R SJ.SECDATA
SAxTAP TR
@ @#### @ @# @### @######## @#### @####
R SJ.SECDATA
@##### CRD
@ @#### @ @# @### @######## @#### @####
R D9.VLRAL
SAxTAP TR
@ @#### @ @# @### @######## @#### @####
R D9.VLRAL
@##### CRD
@ @#### @ @# @### @######## @#### @####
R CG.SA.xxxxx
SAxTAP TR
@ @#### @ @# @### @######## @#### @####
R CG.SA.xxxxx
@##### CRD
@ @#### @ @# @### @######## @#### @####
:
:
:
A30808-X3074-A473-2-7620
EY504 - 7
EMCYMN
12

DISP FILE;
command repetition
EXECD
@################## @#############################
FILE
GEN
SIZE VSN000
VSN001
CLASS TYPE
-----------------+--------+------+-------------+-------------+-----+---CG.SA.xxxxx
@####### @##### @############ @############ @### SAM
:
:
:
:
:
:
:
CG.SA.yyyyy
@####### @##### @############ @############ @### SAM
D9.VLRAL
@####### @##### @############ @############ @### SAM
HF.xxxxxx
@####### @##### @############ @############ @### CYC
IA.xxxxxx
@####### @##### @############ @############ PP
CYC
LG.LOGx.Ay
@####### @##### @############ @############ PP
SAM
MS.xxxxxx
@####### @##### @############ @############ @### PAM
SG.xxxxxx
@####### @##### @############ @############ @### CYC
SJ.SECDATA
@####### @##### @############ @############ APS
PAM
SY.GENLIST
@####### @##### @############ @############ APS
PAM
SY.INSTALL
@####### @##### @############ @############ APS
PAM
SY.LOADLIB.CA
xxxxxxxx @##### @############ @############ APS
PAM
SY.LOADLIB.LA
xxxxxxxx @##### @############ @############ APS
PAM
SY.LOADLIB.MA
xxxxxxxx @##### @############ @############ APS
PAM
SY.MSGXREF
@####### @##### @############ @############ APS
PAM
SY.PSW.Txxx
xxxxxxxx @##### @############ @############ APS
PAM
:
:
:
:
:
:
:
SY.PSW.Tyyy
xxxxxxxx @##### @############ @############ APS
PAM
SY.SEMILIB
xxxxxxxx @##### @############ @############ APS
PAM
SY.SIMP
xxxxxxxx @##### @############ @############ APS
PAM
SY.TASKLIB
xxxxxxxx @##### @############ @############ APS
PAM
SY.TRANSLOG
@####### @##### @############ @############ APS
PAM
D9.VLRAL
@####### @##### @############ @############ APS
PAM
13

All files available.
Are all APS quarterly save tape files available on disk?
EY504- 8
Y h ... 15
N h ... 14
A30808-X3074-A473-2-7620
14
EMCYMN

Preparation for repetition of TRANSSYFILE.
The transfer process was terminated abnormally, or not executed completely,

for one of the following reasons:
1. Transfer error:
Delete any files that have already been transferred with the TRANSFILE
command and repeat the transfer from the APS quarterly save tape:
h ... 11
2. Other reasons (e.g. tape not readable):

After response from the next higher TAC level load MTD with next elder APS
quarterly save tape (part 1)
Transfer must be repeated completely, i.e. including generation files.
- Switch off MDD-x

- Wait for failure message
- Switch on MDD-x again
- Wait for approx. 1 minute
command repetition
EXECD

- DIAG:
DIAG MDD -DIAG:MDD=x;

command repetition
command repetition
EXECD
CONT MDDACT:LABEL;
command repetition
15
EXECD
EXECD
h ... 3

Load MTD.
Mount and load the last tape for APS routine saving.
16
b

Tape to disk transfer of the APS Routine save tape.
TRANS FILE:FILE=CA.ST.UCHA,VSNS=LOGTAP;
command repetition
ACCEPTED
command repetition
EXECD
SENDER
RECEIVER
: @#######
: @#######
A30808-X3074-A473-2-7620
EY504 - 9
EMCYMN
START START
FILE IDENTIFICATION
DATA TYPE
BYTES/
/END- /END: FILE
VSN
STATE : ERROR
RECORDS
DATE TIME
-+-----------------+------+-----+-+-----+-+--+----+---------+-----+----S CA.ST.UCHA
LOGTAP TR
@ @#### @ @# @### @######## @#### @####
R CA.ST.UCHA
@##### CRD
@ @#### @ @# @### @######## @#### @####
17
b

Activate protected file name segments.
ACT FNS:FNS=X;
DANGEROUS COMMAND DANGEROUS COMMAND ACTFNS READY TO EXECUTE<
;
command repetition
18
EXECD

Decision on CCS7 database.
Was the CCS7 database (SY.SIMP) not modified or not present and was the
previous update of semipermanent data with UPD GEN; successful?
19
Y h ... 20
N h ... 19

Manual Initialstart.
After response from the next higher TAC-level a Manual Initial Start from a background memory is to be executed according to procedure EY150 block 36.
(Decision block):
i....EMCYMN,
Continue here, after execution of EY150:
PROC, EY150
For users of the function Manual on PC : the branch back to this block is
made via menu item DISPLAY/HISTORY.
20

Postprocessing for patches.
Important:
It must be checked if during the time from the generation of the save tape until
the time of reload patches were brought into the APS. These are not available
on the save tape!
In this case, the missing patches must absolutely be brought into the APS!
EY504- 10
A30808-X3074-A473-2-7620
21
EMCYMN

Postprocessing for IA-files.
Display features:
DISP IAFEAT;
command repetition
EXECD
Cancel all active features:
CAN IAFEAT:TYPE=feature;
DANGEROUS COMMAND CANIAFEAT
READY TO EXECUTE<
;
command repetition
EXECD
Create file again by activating the features:
ACT IAFEAT:TYPE=feature,SIZE=size;
DANGEROUS COMMAND ACTIAFEAT READY TO EXECUTE<
;
command repetition
22
EXECD

Postprocessing.
It must be decided in each individual case whether it is necessary or possible to

system.
Customer-specific files which are not part of the save tape, must possibly be
created again.
As the last step a timer job for periodic charge meter saving is to be entered and
the appropriate tape is to be remounted in the tape device.
The redundant disk is now to be cleared of faults according to CP890:
End of this procedure.
h ... MMN:CP113,
PROC, CP890
If a routine saving was already carried out in the current quater, the file
D9.VLRAL is to be replaced from LOGTAP.
23

h ... MMN:SW,
PROC, SW210
A30808-X3074-A473-2-7620
EY504 - 11
EMCYMN
24
End of procedure.
END
EY504- 12
A30808-X3074-A473-2-7620
3.21
EMCYMN
Fault Clearance CP113 : Double disk failure MDD

EY710
When a double disk failure occurs, the steps in this procedure are to be followed exactly.
This must be done in order to avoid a manual restart from save tape.
All restart actions initiated with MML commands are forbidden.
The execution of all configuration commands which contain a transition to ACT or MBL
and all diagnosis commands of all CP113 units are preceeded by the system request for
confirmation:
DANGEROUS COMMAND !
(YES: +/NO: -) <
The output is to be confirmed with +

MDD-x = last failed MDD
MDD-y = redundant MDD
IOP-x = last failed IOP
IOP-y = redundant IOP
IOC-x = last failed IOC
IOC-y = redundant IOC
Unsuccessful fault clearance with unit -x means that the fault clearance should be
continued with unit -y.
If there is a double disk failure during the disk copying, the MDD-x must be taken as the
source disk and the MDD-y as the destination disk.
It is possible that between the failure of the first and second MDD patches were entered.
This means that two MDDs have different patch statuses, this can be reconstructed from
the fault printouts.
If this is the case and only the first MDD to fail (oldest patch status) can be successfully
cleared of faults with this procedure, then a descrepancy occurs between main memory
and this disk.
What action is to be taken is to be clarified with the next higher TAC (e.g. reload of the
CP, entry of patches, etc).
Entry via: Alarm (Critical): directly from procedure SYP100 or via CP procedures CP810,
CP861, CP868, CP880.
IOPLAU
The IOPLAU is operated via the software; the loading phase is on the disk as PSW file
and is loaded in the IOPLAU from the CP. This means that the IOPLAU must be treat
separately in the case of double disk failure.
Decision block
Was this procedure entered from one of the following procedures : CP810,
CP861, CP868 or CP880 ?
A30808-X3074-A473-2-7620
Y h ... 2
N h ... 3
EY710 - 1
EMCYMN
Connector
h ... 17
h ... 45
With connector A :
With connector B :
Decision block
Y h ... 6
N h ... 4
Are two OMTs present ?
Decision block
Is there to be cleared of faults in the module frame IOC/IOP-0 ?
Y h ... 5
N h ... 6
Replug OMT
Pull OMT in frame IOP-0, MOLOC C215P1
Insert OMT in frame IOP-1, MOLOC C215P1
So that the messages can be output on OMT-1.
CONF OMT:OMT=0,OST=MBL;
The command is repeated with the added comment:
EXEC'D
STOP MDDACT;
Interruption of possible running activation

Ignore output
6
b
Status request CP113

STAT SSP;
7
b
Configure MDD-x to MBL

8
b
EXEC'D
Configure MDD-y to MBL

CONF MDD:MDD=y,OST=MBL;
EXEC'D
EXEC'D
Decision block
Is one IOC-x in OST=UNA ?
EY710- 2
Y h ... 10
N h ... 17
A30808-X3074-A473-2-7620
10
EMCYMN
Decision block
Y h ... 11
N h ... 13
Are IOPLAU available ?
11
b
Fault clearance of the x branch

DISP IOC:IOC=x;
Configuration of all IOPLAU of the defect IOC to PLA
b
b
CONF IOP:IOP=IOPLAU-no,OST=MBL;
CONF IOP:IOP=IOPLAU-no,OST=PLA;
The following system responses are possible:

Reaction 1R:
EXEC'D
Reaction 2R:
The command is repeated with the added comment: NOT EXEC'D
Continue according to the system reaction
h ... 13
h ... 12
1R
2R
12
b
Configure all IOPLAU

DISP IOP:IOP=IOPLAU-x;
Configuration of all LAUs of the defect and redundant IOPLAU to MBL
b
b
b
CONF LAU:LAU=no,OST=MBL;
13
b
EXEC'D
Configure IOC-x to MBL

CONF IOC:IOC=x,OST=MBL;
A30808-X3074-A473-2-7620
EXEC'D
EY710 - 3
EMCYMN
14
Diagnose IOC-x
In direct mode the following command is to be typed without the pathname

- DIAG :
DIAG IOC-DIAG:IOC=x;

Reaction 1R:
EXEC'D
END OF DIAGN. WITHOUT FAILURE
Reaction 2R:
EXEC'D
END OF DIAGNOSIS WITH FAILURE

h ... 16
h ... 15
1R
2R
15
Continue
h ...MMN:CP113,
continue in
PROC, CP810
After successful fault clearance return to procedure EY710 connector A
16
b
Configure IOC-x to ACT

CONF IOC:IOC=x,OST=ACT;
17
Decision block
Is one IOPMDD-x in OST=UNA ?
18
EXEC'D
Y h ... 18
N h ... 25
Decision block
EY710- 4
Y h ... 19
N h ... 21
A30808-X3074-A473-2-7620
19
b
EMCYMN

DISP IOC:IOC=x;
b
b

Reaction 1R:
EXEC'D
Reaction 2R:
h ... 21
h ... 20
1R
2R
20
b

b
b
b
21
b
EXEC'D
Configure IOPMDD-x to MBL

CONF IOP:IOP=IOPMDD-x,OST=MBL;
A30808-X3074-A473-2-7620
EXEC'D
EY710 - 5
EMCYMN
22
Diagnose IOPMDD-x

- DIAG :
DIAG IOP-DIAG:IOP=IOPMDD-x;

Reaction 1R:
EXEC'D
Reaction 2R:
EXEC'D

h ... 24
h ... 23
1R
2R
23
Continue
h ...MMN:CP113,
continue in
PROC, CP868
or
h ...MMN:CP113,
continue in
PROC, CP880
24
b
Configure IOPMDD-x to ACT

CONF IOP:IOP=IOPMDD-x,OST=ACT;
EY710- 6
EXEC'D
A30808-X3074-A473-2-7620
25
EMCYMN
Diagnose MDD-x
The following command entry including TA = T6 is mandatory:

- DIAG :
DIAG MDD-DIAG:MDD=x,TA=T6;

Reaction 1R:
EXEC'D
Reaction 2R:
EXEC'D

1R
2R
26
Decision block
Is the power supply suspect ?
27
h ... 29
h ... 26
Y h ... 27
N h ... 36
Power
Restore power supply
Switch on power
Wait 1 - 3 minutes
A30808-X3074-A473-2-7620
EY710 - 7
EMCYMN
28
Diagnose MDD-x

- DIAG :

Reaction 1R:
EXEC'D
Reaction 2R:
EXEC'D

h ... 29
h ... 36
1R
2R
29
b
Configure MDD-x to ACT

ACCEPTED
Is the actual generation valid and complete on the disk ?
EY710- 8
Y h ... 30
N h ... 31
A30808-X3074-A473-2-7620
30
b
EMCYMN
Continue MDDACT
CONT MDDACT;

Reaction 1R:
EXEC'D
Reaction 2R:
h ... 32
h ... 36
1R
2R
31
b
32
b
Stop MDDACT
Save generation
UPD GEN;
EXEC'D
DISP FILE;
33
h ... 36
STOP MDDACT;
EXEC'D
Decision block
Was DISP FILE; executed and are all files valid ?
34
Comment
MDD-x is fault-free
35
Y h ... 34
N h ... 35
h ... 69
Power at MDD-x
Switch off power at MDD-x and wait for the failure message.
36
Replug OMT
If necessary replug OMT.
37
Decision block
Is one IOC-y in OST=UNA ?
A30808-X3074-A473-2-7620
Y h ... 38
N h ... 47
EY710 - 9
EMCYMN
38
Decision block
Y h ... 39
N h ... 41
39
b
Fault clearance of the y branch

DISP IOC:IOC=y;
b
b

Reaction 1R:
EXEC'D
Reaction 2R:
h ... 41
h ... 40
1R
2R
40
b

DISP IOP:IOP=IOPLAU-y;
b
b
b
41
b
EXEC'D
Configure IOC-y to MBL

CONF IOC:IOC=y,OST=MBL;
EY710- 10
EXEC'D
A30808-X3074-A473-2-7620
42
EMCYMN
Diagnose IOC-y

- DIAG :
DIAG IOC-DIAG:IOC=y;

Reaction 1R:
EXEC'D
Reaction 2R:
EXEC'D

h ... 44
h ... 43
1R
2R
43
Continue
h ... MMN:CP113,
continue in
PROC, CP810
After successful fault clearance return to procedure EY710 connector B
44
b
Configure IOC-y to ACT

CONF IOC:IOC=y,OST=ACT;
45
Decision block
Is one IOPMDD-y in OST=UNA ?
46
EXEC'D
Y h ... 46
N h ... 53
Decision block
A30808-X3074-A473-2-7620
Y h ... 47
N h ... 49
EY710 - 11
EMCYMN
47
b

DISP IOC:IOC=y;
b
b

Reaction 1R:
EXEC'D
Reaction 2R:
h ... 49
h ... 48
1R
2R
48
b

b
b
b
49
b
EXEC'D
Configure IOPMDD-y to MBL

CONF IOP:IOP=IOPMDD-y,OST=MBL;
EY710- 12
EXEC'D
A30808-X3074-A473-2-7620
50
EMCYMN
Diagnose IOPMDD-y

- DIAG :
DIAG IOP-DIAG:IOP=IOPMDD-y;

Reaction 1R:
EXEC'D
Reaction 2R:
EXEC'D

h ... 52
h ... 51
1R
2R
51
Continue
h ... MMN:CP113,
continue in
PROC, CP868
or
h ... MMN:CP113,
continue in
PROC, CP880
52
b
Configure IOPMDD-y to ACT

CONF IOP:IOP=IOPMDD-y,OST=ACT;
A30808-X3074-A473-2-7620
EXEC'D
EY710 - 13
EMCYMN
53
Diagnose MDD-y

- DIAG :
DIAG MDD-DIAG:MDD=y,TA=T6;

Reaction 1R:
EXEC'D
Reaction 2R:
EXEC'D

1R
2R
54
Decision block
55
h ... 57
h ... 54
Y h ... 55
N h ... 65
Power
Switch on power
Wait 1 - 3 minutes
EY710- 14
A30808-X3074-A473-2-7620
56
EMCYMN
Diagnose MDD-y

- DIAG :

Reaction 1R:
EXEC'D
Reaction 2R:
EXEC'D

h ... 57
h ... 65
1R
2R
57
b
Configure MDD-y to ACT

CONF MDD:MDD=y,OST=ACT;
ACCEPTED
A30808-X3074-A473-2-7620
Y h ... 58
N h ... 59
EY710 - 15
EMCYMN
58
b
Continue MDDACT
CONT MDDACT;

Reaction 1R:
EXEC'D
Reaction 2R:
h ... 60
h ... 65
1R
2R
59
b
60
b
Stop MDDACT
Save generation
UPD GEN;
EXEC'D
DISP FILE;
61
h ... 65
STOP MDDACT;
EXEC'D
Decision block
Y h ... 62
N h ... 63
62
Comment
h ... 69
MDD-y is fault-free
63
Power
Switch off power at MDD-y and wait for the failure message.
Switch on power
Wait 1-3 minutes
64
b

EY710- 16
EXEC'D
A30808-X3074-A473-2-7620
65
EMCYMN
Diagnose MDD-y

- DIAG :
DIAG MDD-DIAG:MDD=y;

Reaction 1R:
EXEC'D
Reaction 2R:
EXEC'D

1R
h ... EMCYMN,
PROC, EY500
2R
66
h ... 66
Replace modules
Consult TAC as how to continue. The procedure must be terminated at this

point. Re-entry is made after consultation with TAC.
Switch off MDD and unscrew fuse
Pull out cable
Replace disk device
Plug in cable
Screw in fuse again
Switch on MDD
A30808-X3074-A473-2-7620
EY710 - 17
EMCYMN
67
Diagnose MDD-y

- DIAG :

Reaction 1R:
EXEC'D
Reaction 2R:
EXEC'D

h ...EMCYMN,
1R
PROC, EY500
h ... 68
2R
68
Cable suspect
h ...NM:CP113,
With cable details
PROC, CP0050
69
b

STAT SSP;
EXEC'D
Reactivate the IOPLAU if necessary

Run diagnosis for the remaining suspect units and clear fault according to the
MMN No.
If necessary replug OMT
END
EY710- 18
A30808-X3074-A473-2-7620
3.22
EMCYMN
Fault Clearance CP113C/CR : Double disk failure MDD

EY730
When a double disk failure occurs, the steps in this procedure are to be followed exactly.
This must be done in order to avoid a manual restart from save tape.
All restart actions initiated with MML commands are forbidden.
MDD-x = last failed MDD
MDD-y = redundant MDD
IOP-x = last failed IOP
IOP-y = redundant IOP
IOC-x = last failed IOC
IOC-y = redundant IOC
Unsuccessful fault clearance with unit -x means that the fault clearance should be
continued with unit -y.
If there is a double disk failure during the disk copying, the MDD-x must be taken as the
source disk and the MDD-y as the destination disk.
It is possible that between the failure of the first and second MDD patches were entered.
This means that two MDDs have different patch statuses, this can be reconstructed from
the fault printouts.
If this is the case and only the first MDD to fail (oldest patch status) can be successfully
cleared of faults with this procedure, then a descrepancy occurs between main memory
and this disk.
What action is to be taken is to be clarified with the next higher TAC (e.g. reload of the
CP, entry of patches, etc).
Entry via: Alarm (Critical): directly from procedure SYP100 or via CP procedures CP910,
CP968, CP980.
IOPLAU
The IOPLAU is operated via the software; the loading phase is on the disk as PSW file
and is loaded in the IOPLAU from the CP. This means that the IOPLAU must be treat
separately in the case of double disk failure.
Decision block
Was this procedure entered from one of the following procedures : CP910,
CP968 or CP980 ?
Y h ... 2
N h ... 3
Connector
With connector A :
With connector B :
A30808-X3074-A473-2-7620
h ... 17
h ... 45
EY730 - 1
EMCYMN
Decision block
Y h ... 6
N h ... 4
Are two OMTs present ?
Decision block
Is there to be cleared of faults in the module frame IOC/IOP-0 ?
Y h ... 5
N h ... 6
Replug OMT
Pull OMT in frame IOP-0, MOLOC C243P1
Insert OMT in frame IOP-1, MOLOC C243P1
So that the messages can be output on OMT-1.
CONF OMT:OMT=0,OST=MBL;
EXEC'D
STOP MDDACT;
Interruption of possible running activation

Ignore output
6
b

STAT SSP;
7
b
Configure MDD-x to MBL

8
b
EXEC'D
Decision block
Is one IOC-x in OST=UNA ?
10
EXEC'D

EXEC'D
Y h ... 10
N h ... 17
Decision block
EY730- 2
Y h ... 11
N h ... 13
A30808-X3074-A473-2-7620
11
b
EMCYMN

DISP IOC:IOC=x;
b
b

Reaction 1R:
EXEC'D
Reaction 2R:
h ... 13
h ... 12
1R
2R
12
b

b
b
b
13
b
EXEC'D
Configure IOC-x to MBL

CONF IOC:IOC=x,OST=MBL;
A30808-X3074-A473-2-7620
EXEC'D
EY730 - 3
EMCYMN
14
Diagnose IOC-x

- DIAG :
DIAG IOC-DIAG:IOC=x;

Reaction 1R:
EXEC'D
Reaction 2R:
EXEC'D

h ... 16
h ... 15
1R
2R
15
Continue
h ...MMN:CP113C,
continue in
PROC, CP910
16
b
Configure IOC-x to ACT

CONF IOC:IOC=x,OST=ACT;
17
Decision block
Is one IOPUNI-x in OST=UNA ?
18
EXEC'D
Y h ... 18
N h ... 25
Decision block
EY730- 4
Y h ... 19
N h ... 21
A30808-X3074-A473-2-7620
19
b
EMCYMN

DISP IOC:IOC=x;
b
b

Reaction 1R:
EXEC'D
Reaction 2R:
h ... 21
h ... 20
1R
2R
20
b

b
b
b
21
b
EXEC'D
Configure IOPUNI-x to MBL

CONF IOP:IOP=IOPUNI-x,OST=MBL;
A30808-X3074-A473-2-7620
EXEC'D
EY730 - 5
EMCYMN
22
Diagnose IOPUNI-x

- DIAG :
DIAG IOP-DIAG:IOP=IOPUNI-x;

Reaction 1R:
EXEC'D
Reaction 2R:
EXEC'D

h ... 24
h ... 23
1R
2R
23
Continue
h ...MMN:CP113C,
continue in
PROC, CP968
or
h ...MMN:CP113C,
continue in
PROC, CP980
24
b
Configure IOPUNI-x to ACT

CONF IOP:IOP=IOPUNI-x,OST=ACT;
EY730- 6
EXEC'D
A30808-X3074-A473-2-7620
25
EMCYMN
Diagnose MDD-x

- DIAG :

Reaction 1R:
EXEC'D
Reaction 2R:
EXEC'D

1R
2R
26
Decision block
27
h ... 29
h ... 26
Y h ... 27
N h ... 36
Power
Switch on power
Wait 1 - 3 minutes
A30808-X3074-A473-2-7620
EY730 - 7
EMCYMN
28
Diagnose MDD-x

- DIAG :

Reaction 1R:
EXEC'D
Reaction 2R:
EXEC'D

h ... 29
h ... 36
1R
2R
29
b
Configure MDD-x to ACT

ACCEPTED
EY730- 8
Y h ... 30
N h ... 31
A30808-X3074-A473-2-7620
30
b
EMCYMN
Continue MDDACT
CONT MDDACT;

Reaction 1R:
EXEC'D
Reaction 2R:
h ... 32
h ... 36
1R
2R
31
b
32
b
Stop MDDACT
Save generation
UPD GEN;
EXEC'D
DISP FILE;
33
h ... 36
STOP MDDACT;
EXEC'D
Decision block
34
Comment
MDD-x is fault-free
35
Y h ... 34
N h ... 35
h ... 69
Power at MDD-x
Switch off power at MDD-x and wait for the failure message.
36
Replug OMT
If necessary replug OMT.
37
Decision block
Is one IOC-y in OST=UNA ?
A30808-X3074-A473-2-7620
Y h ... 38
N h ... 45
EY730 - 9
EMCYMN
38
Decision block
Y h ... 39
N h ... 41
39
b

DISP IOC:IOC=y;
b
b

Reaction 1R:
EXEC'D
Reaction 2R:
h ... 41
h ... 40
1R
2R
40
b

b
b
b
41
b
EXEC'D
Configure IOC-y to MBL

CONF IOC:IOC=y,OST=MBL;
EY730- 10
EXEC'D
A30808-X3074-A473-2-7620
42
EMCYMN
Diagnose IOC-y

- DIAG :
DIAG IOC-DIAG:IOC=y;

Reaction 1R:
EXEC'D
Reaction 2R:
EXEC'D

h ... 44
h ... 43
1R
2R
43
Continue
h ... MMN:CP113C,
continue in
CP910
44
b
Configure IOC-y to ACT

CONF IOC:IOC=y,OST=ACT;
45
Decision block
Is one IOPUNI-y in OST=UNA ?
46
EXEC'D
Y h ... 46
N h ... 53
Decision block
A30808-X3074-A473-2-7620
Y h ... 47
N h ... 49
EY730 - 11
EMCYMN
47
b

DISP IOC:IOC=y;
b
b

Reaction 1R:
EXEC'D
Reaction 2R:
h ... 49
h ... 48
1R
2R
48
b

b
b
b
49
b
EXEC'D
Configure IOPUNI-y to MBL

CONF IOP:IOP=IOPUNI-y,OST=MBL;
EY730- 12
EXEC'D
A30808-X3074-A473-2-7620
50
EMCYMN
Diagnose IOPUNI-y

- DIAG :
DIAG IOP-DIAG:IOP=IOPUNI-y;

Reaction 1R:
EXEC'D
Reaction 2R:
EXEC'D

h ... 52
h ... 51
1R
2R
51
Continue
h ... MMN:CP113C,
continue in
CP968
or
h ... MMN:CP113C,
continue in
CP980
52
b
Configure IOPUNI-y to ACT

CONF IOP:IOP=IOPUNI-y,OST=ACT;
A30808-X3074-A473-2-7620
EXEC'D
EY730 - 13
EMCYMN
53
Diagnose MDD-y

- DIAG :

Reaction 1R:
EXEC'D
Reaction 2R:
EXEC'D

1R
2R
54
Decision block
55
h ... 57
h ... 54
Y h ... 55
N h ... 65
Power
Switch on power
Wait 1 - 3 minutes
EY730- 14
A30808-X3074-A473-2-7620
56
EMCYMN
Diagnose MDD-y

- DIAG :

Reaction 1R:
EXEC'D
Reaction 2R:
EXEC'D

h ... 57
h ... 65
1R
2R
57
b
Configure MDD-y to ACT

CONF MDD:MDD=y,OST=ACT;
ACCEPTED
A30808-X3074-A473-2-7620
Y h ... 58
N h ... 59
EY730 - 15
EMCYMN
58
b
Continue MDDACT
CONT MDDACT;

Reaction 1R:
EXEC'D
Reaction 2R:
h ... 60
h ... 65
1R
2R
59
b
60
b
Stop MDDACT
Save generation
UPD GEN;
EXEC'D
DISP FILE;
61
h ... 65
STOP MDDACT;
EXEC'D
Decision block
Y h ... 62
N h ... 63
62
Comment
h ... 69
MDD-y is fault-free
63
Power
Switch off power at MDD-y and wait for the failure message.
Switch on power
Wait 1-3 minutes
64
b

EY730- 16
EXEC'D
A30808-X3074-A473-2-7620
65
EMCYMN
Diagnose MDD-y

- DIAG :

Reaction 1R:
EXEC'D
Reaction 2R:
EXEC'D

1R
h ... EMCYMN,
PROC, EY500
2R
66
h ... 66
Replace modules
Consult TAC as how to continue. The procedure must be terminated at this

point. Re-entry is made after consultation with TAC.
Switch off MDD and unscrew fuse
Pull out cable
Replace disk device
Plug in cable
Screw in fuse again
Switch on MDD
A30808-X3074-A473-2-7620
EY730 - 17
EMCYMN
67
Diagnose MDD-y

- DIAG :

Reaction 1R:
EXEC'D
Reaction 2R:
EXEC'D

h ...EMCYMN,
1R
PROC, EY500
h ... 68
2R
68
Cable suspect
h ...NM:CP113,
With cable details
PROC, CP0050
69
b

STAT SSP;
EXEC'D
Reactivate the IOPLAU if necessary

Run diagnosis for the remaining suspect units and clear fault according to the
MMN No.
If necessary replug OMT
END
EY730- 18
A30808-X3074-A473-2-7620
3.23
EMCYMN
Emergency Situation for CCNC Data

EY920
3.23.1

A30808-X3074-A473-2-7620
EY920 - 1
EMCYMN
3.23.2
Fault description
For this emergency situation the responsible diagnostic center (TAC1) must be
notified.
Attention!
If data saving (COPY GEN) is performed before the error has been cleared, the
fault-free saved data are replaced by faulty saved data. Therefore, do not
perform APS saving (COPY GEN) again until the existing data corruption has
been cleared.
This procedure can be reached through a MMN-number as well as through a
fault number determined during diagnosis.
This message indicates that during loading of the CCNP, data corruptions were
found in files SY.PSW.T097, SY.PSW.T098 or SY.SIMP (checksum errors).
If there are data errors in SY.SIMP, please note:
Since file SY.SIMP cannot be replaced individually, fallback to the 'fallback
generation' or 'golden generation' is necessary.
If no successful CCNP diagnosis or configuration was performed between
generation of the last backup-APS and the occurrence of the error, it is necessary to fall back to a backup-APS that was generated before successful loading
of the CCNP (the CCNP is loaded daily at 3.20 a.m.).
If there are errors in SY.PSW.T097 or T098, please note:
It is possible to replace the files. To do this, however, the files have to be saved
on a magnetic tape and copied in again from the tape.
If no successful CCNP diagnosis or configuration was performed between
generation of the last backup-APS and the occurrence of the error, it is necessary to fall back to a backup-APS that was generated before successful loading
of the CCNP (the CCNP is loaded daily at 3.20 a.m.).
Continue
h ... 2
Decision block
What types of files are faulty?
Only SY.SIMP
Only SY.PSW.T09x
Both SY.SIMP and SY.PSW.T09x
EY920- 2
h ... 6
h ... 3
h ... 6
A30808-X3074-A473-2-7620
Preparation for restoration of the SY.PSW.T09x file(s)

Is a golden generation available that corresponds to the described status?
EMCYMN
Y h ... 5
N h ... 4
Special fault clearance
Special fault clearance if necessary
Continue fault clearance

Prepare the tape with the golden generation.
In procedure EY500 the corresponding suspect file must be replaced.
h ... EMCYMN,
PROC, EY500
Fallback to a backup-APS
Fall back to the 'fallback generation' is necessary.
This is done by means of procedure EY190
i ... EMCYMN,
PROC, EY190
Was the recovery with the 'fallback generation successful
(both CCNP are loaded)?
The fault clearance was successful

The fault clearance was successful because of the
recovery with 'fallback generation'.
Y h ... 9
N h ... MMN:CCS7

The 'fallback generation' contains the same error. A fallback to the 'golden
generation' occurs if procedure EY190 is started again.
10
h ... 10

Was a (error) message again output with hints to this procedure
during loading of CCNC?
Y h ... 7
N h ... 8
h ... EMCYMN,
PROC, EY190
Decision block
Was this procedure entered with an instruction to return to the calling procedure?
Y h ... 11
N h ... MMN:SYP,
PROC,
PROC:SYP101
A30808-X3074-A473-2-7620
EY920 - 3
EMCYMN
11

12
End of procedure.
END
EY920- 4
A30808-X3074-A473-2-7620
3.24
EMCYMN
Emergency Situation for Trunk Data

EY930
3.24.1

A30808-X3074-A473-2-7620
EY930 - 1
EMCYMN
3.24.2
Fault description
notified.
Attention! If data saving (COPY GEN) is performed before the error has been
cleared, the fault-free saved data are replaced by faulty saved data. Therefore,
do not perform APS saving (COPY GEN) again until the existing data corruption
has been cleared.
notified.
Attention! If data saving (COPY GEN) is performed before the error has been
cleared, the fault-free saved data are replaced by faulty saved data. Therefore,
do not perform APS saving (COPY GEN) again until the existing data corruption
has been cleared.
This procedure can reached be through a MMN-number as well as through a
fault number determined during diagnosis.
In such cases no detailed information can be given as to whether data was only
corrupted in the CP memory or in the MDD as well.
The extent to which the data have been corrupted is reflected by the number of
trunks in state NSYNP.
The worst possible situation is that both CCNPs fail. Then one of the CCNPs is
nonetheless configured to ACT in spite of the corrupted data and the other
remains UNA.
If the number of trunks in state NSYNP is low or still within acceptable limits
- cancel and recreate the affected trunks
If the task of cancelling and recreating trunks does not seem acceptable, the
following possibilities exist:
- Recovery 1-2. This reloads the CP memory data from the MDD (which is sufficient if data in CP memory were corrupted).
- Fallback to a backup APS. Ensure that a save-tape is used which was generated before the last error-free loading of the CCNC (e.g. error-free diagnostics
or configuration). (The routine loading takes place every 24 hours alternately for
each CCNP).
Continue
EY930- 2
h ... 2
A30808-X3074-A473-2-7620
Decision block
Has diagnostics been started for the CCNP during the course of this fault clearance?
h ... 16

Is the CCNP to be diagnosed in OST = MBL?
6
b
Y h ... 4
N h ... 8

Suspect modules have already been replaced. However, the fault has not been
cleared.
Y h ... 3
N h ... 5

Have the suspect modules been replaced?
EMCYMN
Y h ... 7
N h ... 6
Configure CCNP
CONF CCNC:UNIT=CCNP-no,OST=MBL;
i ... MMN:CCS7,
CONF:CN
7
b
Diagnose CCNP
DIAG CCNC:UNIT=CCNP-no;
i ... MMN:CCS7,
DIAG:CN
The following result are possible:
Diagnose was not executed
Repeat the command after determining cause of job
Diagnose was executed. The processor is all right .
Diagnose was executed. The processor is not all right .
h ... 7
h ... 12
h ... 8

Find the defective modules in the fault number catalog FNRK:
i ... NM:CCS7
Does fault list FNRK:* only refer to this procedure?
A30808-X3074-A473-2-7620
Y h ... 9
N h ... 10
EY930 - 3
EMCYMN
h ... 16
Thus no suspect modules are specified.
10

It is first necessary to make sure that the fault is not caused by a faulty module
i....MMN:CCS7,
CN050
Y h ... 13
N h ... 11
Was it possible to clear the fault by replacing the modules?
11

Suspect modules have already been replaced. However, the fault has not been
cleared
12
b
h ... 16
Configure CCNP
i....MMN:CCS7,
CONF CCNC:UNIT=CCNP-no,OST=STB;
CONF:CN
13
Decision block
Y h ... 27
N h ... 14
Have both CCNPs been reloaded after the fault clearance?
14
b
Soft CCNP switchover
i....MMN:CCS7,
CONF CCNC:UNIT=CCNP-no,OST=ACT;
CONF:CN
15
b
16
Configure CCNP
CONF CCNC:UNIT=CCNP-no,OST=MBL;
h ... 7
Decision block
Was a RECOV SSP already started during this procedure?
EY930- 4
Y h ... 24
N h ... 17
A30808-X3074-A473-2-7620
17
EMCYMN
Determine trunks in NSYNP state
If logging of the trunks shows that the output is too long, it is possible to stop the
output using the command:
- STOP JOB:JN=no; or - STOP DISP:JN=no;
STAT TRUNK:TGNO=X,STATUS=NSYNP;
Are there one or more trunks previously determined in status NSYNP?
18

Is the number of trunks to be canceled and created again determined within
reasonable limits?
19
Y h ... 18
N h ... 20
Y h ... 19
N h ... 20
The trunks that are determined are to be canceled and created again. The
command sequence is as follows
- block (ENTR TRDAT)
- cancel (CAN TRUNK)
- create (CR TRUNK)
- release (CAN TRDAT)
i ... OMN
Could all trunks be canceled and created again?
20
Load the CP memory from MDD

Was a RECOV SSP NSTART2 already started during this procedure?
21
Y h ... 24
N h ... 21

The effect of the recovery is that the CP memory is reloaded again from the
disk. It is a precondition that all CP units are redundant. Are all CPs redundant?
22
Y h ... 7
N h ... 20
Y h ... 23
N h ... 22

Faults in the CP area must be cleared first
i ... MMN:CP113
A30808-X3074-A473-2-7620
EY930 - 5
EMCYMN
23

A NSTART2 recovery according to MMN:SW must be made. continue here, after
execution of: MMN:SW, register CP113, chapter SW120
i....MMN:CP113
h ... 7
Wait 15 minutes (Synchronization of all trunks lasts approx. 15 min. after

loading)
24
Fallback to a backup-APS
i....EMCYMN,
Fall back to the 'fallback generation' is necessary. This is done by means of

procedure EY190
EY190
Was the recovery with the 'fallback generation successful (both CCNP are
loaded)?
25
Y h ... 25
N h ... 26
The fault clearance was successful because of the recovery with 'fallback generation'.
26
h ... 27
The 'fallback generation' contains the same error. A fallback to the 'golden
generation' occurs if procedure EY190 is started again.
h ...EMCYMN,
PROC, EY190
27
Decision block
Was this procedure entered with an instruction to return to the calling procedure?
Y h ... 28
N h ...MMN:SYP,
PROC,
PROC:SYP101
28

EY930- 6
A30808-X3074-A473-2-7620
29
EMCYMN
End of procedure.
END
A30808-X3074-A473-2-7620
EY930 - 7
EMCYMN
EY930- 8
A30808-X3074-A473-2-7620
EMCYMN
4 Tables (TAB)
This manual does not contain tables.
A30808-X3074-A473-1-7620
TABIN - 1
EMCYMN
TABIN- 2
A30808-X3074-A473-1-7620
EMCYMN
5 Appendix (APP)
This manual does not contain an appendix.
A30808-X3074-A473-1-7620
APP - 1
EMCYMN
APP- 2
A30808-X3074-A473-1-7620

SIEMENS Emergency Cases

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

SIEMENS Emergency Cases

Transféré par

Droits d'auteur :

Formats disponibles

Emergency Cases

Emergency Cases Software

Copyright (C) Siemens AG 1996

Emergency Cases Software

EMCYMN . . . . . . . . . . . . PROCIN. . . . . . . . . . . . . . . . . . . . . 1...

EMCYMN . . . . . . . . . . . . TABIN . . . . . . . . . . . . . . . . . . . . . . 1... 2

EMCYMN . . . . . . . . . . . . APP . . . . . . . . . . . . . . . . . . . . . . . . 1... 2

Emergency Cases Software

This document consists of a total of 408 Pages

Emergency Cases Software

Task List EMCYMN, MMN:SW and NM:SW . . . . . . . . . . . . . . . . . . . . . . TL - 1

Procedures (PROCIN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PROCIN - 1

Tables (TAB). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TAB - 1

Appendix (APP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . APP - 1

Emergency Cases Software

Emergency Cases Software

Elements used in the procedures . . . . . . . . . . . . . . . . . . . . . . PROCIN - 3

Emergency Cases Software

Emergency Cases Software

Example of a call list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN - 1

Emergency Cases Software

Emergency Cases Software

Recommendations to the Emergency Manual

To call in any emergency situation:

Tab. 1.1.1 Example of a call list

Emergency Cases Software

List of CALL numbers

Tab. 1.2.1 List of CALL numbers

Emergency Manual remarks

Definition of an Emergency Situation

Emergency Cases Software

Alarm Notification in Emergencies

call to a call handler (organized on a regional basis)

provision of the following information:

name and telephone number of the person notifying the alarm

send further information, in the form of the questionnaire to the TAC:

any other information to be provided by word of mouth or exchange of letters

An outage report must be completed from scratch after each emergency.

Emergency Cases Software

Recommendations for emergency precautions

Appoint an emergency coordinator:

Equipping with Service Handsets:

When assessing the relative seriousness of an emergency it must be determined, to

Therefore we would strongly recommend the following:

Emergency Cases Software

Example of a call list

A call list for testing switching operation in emergency situations

Service handsets in the network node

- at remote network node

Local network node ORANGE

Tab. 1.7.1 Example of a test call list

Emergency Cases Software

Emergency Cases Software

2 Task List EMCYMN, MMN:SW and NM:SW

Cross Reference List

NM:SW, PROC, SW451

Error Symptoms Saving:

NM:SW, PROC, SW451

EMCYMN, PROC, EY190

NM:SW, PROC, SW441

Emergency Cases Software

NM:SW, PROC, SW140

NM:SW, PROC, SW422

Magnetic Disk Device (MDD):