siemens emergency cases

7/23/2019 SIEMENS Emergency Cases

http://slidepdf.com/reader/full/siemens-emergency-cases 1/407

Emergency Cases

Software

EMCYMN

A30808-X3074-A473-2-7620



AD – 2 A30808-X3074-A473-2-7620

EMCYMN Emergency Cases Software

Copyright (C) Siemens AG 1996

Issued by the Public Communication Network Group

Hofmannstraße 51

D-81359 München

Technical modifications possible.

Technical specifications and features are binding only insofar as

they are specifically and expressly agreed upon in a written contract.



A30808-X3074-A473-2-7620 AD - 3

Emergency Cases Software 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 Titel Page(s) Issue/Ind.

Register ADMIN

EMCYMN . . . . . . . . . . . . AD . . . . . . . . . . . . . . . . . . . . . . . . . 1... 10 2 G

EMCYMN . . . . . . . . . . . . IN. . . . . . . . . . . . . . . . . . . . . . . . . . 1... 6 1

Register TL

EMCYMN . . . . . . . . . . . . TL . . . . . . . . . . . . . . . . . . . . . . . . . 1... 4 2 GRegister PROC

EMCYMN . . . . . . . . . . . . PROCIN. . . . . . . . . . . . . . . . . . . . . 1... 4 1

EMCYMN . . . . . . . . . . . . ENTRY . . . . . . . . . . . . . . . . . . . . . 1... 14 1

EMCYMN . . . . . . . . . . . . EY100 . . . . . . . . . . . . . . . . . . . . . . 1... 6 2 G

EMCYMN . . . . . . . . . . . . EY130 . . . . . . . . . . . . . . . . . . . . . . 1... 12 2 G

EMCYMN . . . . . . . . . . . . EY150 . . . . . . . . . . . . . . . . . . . . . . 1... 40 2 G

EMCYMN . . . . . . . . . . . . EY170 . . . . . . . . . . . . . . . . . . . . . . 1... 14 2 G

EMCYMN . . . . . . . . . . . . EY190 . . . . . . . . . . . . . . . . . . . . . . 1... 18 2 G

EMCYMN . . . . . . . . . . . . EY191 . . . . . . . . . . . . . . . . . . . . . . 1... 12 2 G

EMCYMN . . . . . . . . . . . . EY192 . . . . . . . . . . . . . . . . . . . . . . 1... 24 2 G

EMCYMN . . . . . . . . . . . . EY193 . . . . . . . . . . . . . . . . . . . . . . 1... 24 2 G

EMCYMN . . . . . . . . . . . . EY194 . . . . . . . . . . . . . . . . . . . . . . 1... 22 2 G

EMCYMN . . . . . . . . . . . . EY350 . . . . . . . . . . . . . . . . . . . . . . 1... 18 2 G

EMCYMN . . . . . . . . . . . . EY360 . . . . . . . . . . . . . . . . . . . . . . 1... 10 2 G

EMCYMN . . . . . . . . . . . . EY370 . . . . . . . . . . . . . . . . . . . . . . 1... 12 2 G

EMCYMN . . . . . . . . . . . . EY380 . . . . . . . . . . . . . . . . . . . . . . 1... 16 2 G

EMCYMN . . . . . . . . . . . . EY400 . . . . . . . . . . . . . . . . . . . . . . 1... 8 2 G

EMCYMN . . . . . . . . . . . . EY500 . . . . . . . . . . . . . . . . . . . . . . 1... 4 2 G

EMCYMN . . . . . . . . . . . . EY501 . . . . . . . . . . . . . . . . . . . . . . 1... 40 2 G

EMCYMN . . . . . . . . . . . . EY502 . . . . . . . . . . . . . . . . . . . . . . 1... 18 2 G

EMCYMN . . . . . . . . . . . . EY503 . . . . . . . . . . . . . . . . . . . . . . 1... 8 2 GEMCYMN . . . . . . . . . . . . EY504 . . . . . . . . . . . . . . . . . . . . . . 1... 12 2 G

EMCYMN . . . . . . . . . . . . EY710 . . . . . . . . . . . . . . . . . . . . . . 1... 18 2 G

EMCYMN . . . . . . . . . . . . EY730 . . . . . . . . . . . . . . . . . . . . . . 1... 18 2 G

EMCYMN . . . . . . . . . . . . EY920 . . . . . . . . . . . . . . . . . . . . . . 1... 4 2 G

EMCYMN . . . . . . . . . . . . EY930 . . . . . . . . . . . . . . . . . . . . . . 1... 8 2 G

Register TAB

EMCYMN . . . . . . . . . . . . TABIN . . . . . . . . . . . . . . . . . . . . . . 1... 2 1

Register APP

EMCYMN . . . . . . . . . . . . APP . . . . . . . . . . . . . . . . . . . . . . . . 1... 2 1



AD- 4 A30808-X3074-A473-2-7620


This document consists of a total of 408 Pages



EMCYMN

A30808-X3074-A473-2-7620 AD – 5

Emergency Cases Software

Contents

Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AD - 3

Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AD - 5

Illustrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AD - 7

Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AD - 9

1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN - 1

1.1 Recommendations to the Emergency Manual . . . . . . . . . . . . . . . . . . . . IN - 1

1.2 List of CALL numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN - 2

1.3 Emergency Manual remarks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN - 2

1.4 Definition of an Emergency Situation . . . . . . . . . . . . . . . . . . . . . . . . . . . IN - 2

1.5 Alarm Notification in Emergencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN - 3

1.6 Postprocessing of Emergencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN - 3

1.7 Recommendations for emergency precautions . . . . . . . . . . . . . . . . . . . IN - 4

2 Task List EMCYMN, MMN:SW and NM:SW. . . . . . . . . . . . . . . . . . . . . .TL - 1

3 Procedures (PROCIN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PROCIN - 1

3.1 Identifying an Emergency Situation . . . . . . . . . . . . . . . . . . . . . . . .ENTRY - 1

3.2 Actions after unsuccessful recovery . . . . . . . . . . . . . . . . . . . . . . . . EY100 - 1

3.3 Manual Initial Start from MDD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . EY130 - 1

3.4 Manual Initial Start from an APS Save Tape . . . . . . . . . . . . . . . . . EY150 - 1

3.5 Rescue of Background Memory Data. . . . . . . . . . . . . . . . . . . . . . . EY170 - 1

3.6 Initial Start (FALLBACK GENERATION) . . . . . . . . . . . . . . . . . . . . EY190 - 1

3.7 Initial Start (FALLBACK GENERATION) . . . . . . . . . . . . . . . . . . . . EY191 - 13.8 Initial Start (FALLBACK GENERATION) . . . . . . . . . . . . . . . . . . . . EY192 - 1



3.11 Total Shutdown / Partial Shutdown. . . . . . . . . . . . . . . . . . . . . . . . . EY350 - 1

3.12 Partial Restart after Partial Shutdown. . . . . . . . . . . . . . . . . . . . . . . EY360 - 1

3.13 Total Restart after Total Shutdown . . . . . . . . . . . . . . . . . . . . . . . . . EY370 - 1

3.14 Measures after a power failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . EY380 - 1

3.15 Measures after unsuccessful FEPROM patching . . . . . . . . . . . . . . EY400 - 1

3.16 Restoration of files on the background memories. . . . . . . . . . . . . . EY500 - 1





3.21 Fault Clearance CP113 : Double disk failure MDD. . . . . . . . . . . . . EY710 - 1

3.22 Fault Clearance CP113C/CR : Double disk failure MDD . . . . . . . . EY730 - 1

3.23 Emergency Situation for CCNC Data . . . . . . . . . . . . . . . . . . . . . . . EY920 - 1

3.24 Emergency Situation for Trunk Data. . . . . . . . . . . . . . . . . . . . . . . . EY930 - 1

4 Tables (TAB). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TAB - 1

5 Appendix (APP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . APP - 1




AD – 6 A30808-X3074-A473-2-7620



A30808-X3074-A473-2-7620 AD – 7


Illustrations

Fig. 3.0.1 Elements used in the procedures . . . . . . . . . . . . . . . . . . . . . . PROCIN - 3

Fig. 3.2.1 Diagram of procedure EY100 . . . . . . . . . . . . . . . . . . . . . . . . . . EY100 - 3





AD – 8 A30808-X3074-A473-2-7620




A30808-X3074-A473-2-7620 AD – 9


Tables

Tab. 1.1.1 Example of a call list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN - 1

Tab. 1.2.1 List of CALL numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN - 2

Tab. 1.7.1 Example of a test call list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN - 5

Tab. 3.11.1 Creation of MINIMAL CONFIGURATION LIST (MCL). . . . . . . . EY350 - 3

Tab. 3.11.2 Example of a minimum configuration list (MCL) . . . . . . . . . . . . EY350 - 4

Tab. 3.15.1 Assignment between processor and processor number . . . . . . EY400 - 3



AD – 10 A30808-X3074-A473-2-7620




A30808-X3074-A473-1-7620 IN - 1


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 thenetwork node to which it is pertinent. It must be updated after every hardware/firm-

ware/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 306/488 ...

2. Mr. Smith office: 304/564 ... private: 306/832 ...

if no answer:

3. Mr. Miller office: 304/569 ... private: 312/217 ...

Tab. 1.1.1 Example of a call list



IN- 2 A30808-X3074-A473-1-7620


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.

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

1.4 Definition of an Emergency Situation

The definitions of emergency situations are to be taken from the customer specific

dokumentation.

CALL NUMBERS FOR EMERGENCY SITUATIONS

To call in any emergency situation:

1. TAC 1

2. office: private:

if no answer:

3. office: private:

Tab. 1.2.1 List of CALL numbers

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.



A30808-X3074-A473-1-7620 IN - 3


1.5 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 aresignaled 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 tele-

phone with the higher-ranking TAC

• any other information to be provided by word of mouth or exchange of letters

1.6 Postprocessing of Emergencies

The reason for postprocessing emergencies is to prevent such emergencies from recur-

ring 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 refer-

ences 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.

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.



IN- 4 A30808-X3074-A473-1-7620


1.7 Recommendations for emergency precautions

Recommendations for equipping the OMC and switching centers to cope with emer-

gency 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 situa-

tion.

• Telephone communication to and from the affected network node must be guaran-

teed 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.



A30808-X3074-A473-1-7620 IN - 5


1.7.3 Example of a call list

A call list for testing switching operation in emergency situations

Local network node MILFORD 237 ...

controlled by OMC DEVON

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



IN- 6 A30808-X3074-A473-1-7620




A30808-X3074-A473-2-7620 TL - 1


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 Main-tenance 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MMN:SW, ADMIN, IN

MMN:SW, APP, APPSave the current APS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MMN:SW, PROC,

SW210

Startup test of the saved APS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MMN:SW, PROC,SW211Checksum mismatch:

General remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MMN:SW, ADMIN, INRestoration of defective files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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,

SW231Expansion:

Expansion of data area (ODAGEN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NM:SW, PROC, SW451

Fallback:Fallback to older generation (ISTART2G). . . . . . . . . . . . . . . . . . . . . . . . . . . . EMCYMN, PROC, EY190

Files:

Saving, reading of tape MMN:SW, PROC,SW210

GP Software:Replacement of PSW files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NM:SW, PROC, SW441

History Files:History file saving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MMN:SW, PROC,

SW231Reading history files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MMN:SW, PROC,

SW232IARSTAT:

IARSTAT measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MMN:SW, PROC,SW221

http://a004m983.pdf/





http://a002o852.pdf/





































TL - 2 A30808-X3074-A473-2-7620


IMON:Background informations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NM:SW, ADMIN, IN

Individual Call Data:

Save the individual call data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MMN:SW, PROC,SW224

Initial Start:Fallback generation / ISTART2G. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EMCYMN, PROC, EY190from MDD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EMCYMN, PROC, EY130from MTD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EMCYMN, PROC, EY150

Initialization:Initialization of background memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MMN:SW, PROC,

SW310Installation 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) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EMCYMN, PROC, EY710Double disk failure MDD (CP113C/CR). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EMCYMN, PROC, EY730Initilization of background memory (MDD). . . . . . . . . . . . . . . . . . . . . . . . . . . . MMN:SW, PROC,

SW310Manual initial start from MDD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EMCYMN, PROC, EY130Rescue of background memory data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EMCYMN, PROC, EY170Restoration of files on the background memories . . . . . . . . . . . . . . . . . . . . . . EMCYMN, PROC, EY502

EMCYMN, PROC, EY503

Magnetic Tape Device (MTD):Manual initial start (save tape) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EMCYMN, PROC, EY150Cleaning MTD 2922 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NM:CP113, PROC,

MTD:STC 2922Cleaning MTD 2925 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NM:CP113C/CR, PROC,

MTD:STC 2925New Start:

General remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MMN:SW, ADMIN, IN Background informations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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. . . . . . . . . . . . . . . . . . . . . . . . . . . . MMN:SW, PROC,

SW222ODAGEN:

Expansion of the CP database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NM:SW, PROC, SW451

OMT:

Initialization PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MMN:PC-BASIS, ADMIN,IN



















http://a006f109.pdf/


































A30808-X3074-A473-2-7620 TL - 3


Cleaning OMT for CP113 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MMN:CP113, TAB,CLEANOMT

Cleaning OMT for CP113C/CR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MMN:CP113C/CR, TAB,CLEANOMT

Split mode operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MMN:PC-BASIS, PROC,OMT-SPLIT

Overheating:System total shutdown / partial shutdown. . . . . . . . . . . . . . . . . . . . . . . . . . . . EMCYMN, PROC, EY350System partial restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EMCYMN, PROC, EY360System total restart. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EMCYMN, PROC, EY370

Patch:Measures after unsuccessful FEPROM patching . . . . . . . . . . . . . . . . . . . . . . EMCYMN, PROC, EY400Patch FEPROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MMN:SW, PROC,

SW412Patch Software (CP, CCNC, GP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MMN:SW, PROC,

SW411DCP Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MMN:SW-DCP, ADMIN,

IN

PC (OMT):Initialization PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MMN:PC-BASIS, ADMIN,

INFault Clearance PC for CP113 MMN:CP113, PROC,

CP870Fault Clearance PC for CP113C/CR MMN:CP113C/CR,

PROC, CP970Split mode operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MMN:PC-BASIS, PROC,

OMT-SPLITTLWS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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

Recovery:Actions after unsuccessful recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EMCYMN, PROC, EY100Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NM:SW, ADMIN, INEvaluation of recovery messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MMN:SW, PROC,

SW330Installation recovery from MTD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NM:SW, PROC, SW140Measures after recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NM:SW, PROC, SW110Plausibility failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MMN:SW, PROC,

SW330Recovery using fallback generation (ISTART2G). . . . . . . . . . . . . . . . . . . . . . EMCYMN, PROC, EY190Treatment of recovery messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MMN:SW, PROC,

SW330Restart:



















































TL - 4 A30808-X3074-A473-2-7620


Evaluation of initial reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MMN:SW, PROC,SW330

Restoration:Restoration of statistic meters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MMN:SW, PROC,

SW223Restoration of generation files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EMCYMN, PROC, EY501

EMCYMN, PROC, EY502Restoration of non-generation files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EMCYMN, PROC, EY503

Saving disk contentsto MTD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MMN:SW, PROC,

SW210Saving of:

APS (quarterly, routine) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MMN:SW, PROC,SW210,MMN:SW, PROC,

SW211Error symptoms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MMN:SW, PROC,

SW231History files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MMN:SW, PROC,

SW231Individual call data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MMN:SW, PROC,

SW224Interadministration revenue accounting and statistics (IARSTAT). . . . . . . . . . MMN:SW, PROC,

SW221Shutdown:

System total shutdown/partial shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EMCYMN, PROC, EY350System partial restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EMCYMN, PROC, EY360System total restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EMCYMN, PROC, EY370

Software Changes:General remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NM:SW, ADMIN, INInput of patches for exchange software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MMN:SW, PROC,

SW411Input of FEPROM Firmware (CP113C/CR) . . . . . . . . . . . . . . . . . . . . . . . . . . . MMN:SW, PROC,

SW412Input of patches for DCP Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MMN:SW-DCP, ADMIN,

INSoftware change for PC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MMN:PC-BASIS, ADMIN,

IN

Statistic meters:Restoration of defective statistic meters from tape . . . . . . . . . . . . . . . . . . . . . MMN:SW, PROC,

SW223

UPDATE Messages:Treatment of UPDATE Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MMN:SW, PROC,

SW320



































































A30808-X3074-A473-1-7620 PROCIN - 1


3 Procedures (PROCIN)

3.0.1 General remarks

3.0.1.1 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 under-

standing it.

SENDER : @#######

RECEIVER : @#######

START START



-+----------------+------+-----+-+-----+-+--+----+---------+-----+-----

S SY.MSGXREF LOGTAP TR @ @#### @ @# @### @######## @#### @####

R SY.MSGXREF SYSVSN CRD @ @#### @ @# @### @######## @#### @####



PROCIN- 2 A30808-X3074-A473-1-7620


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

2. Interpretation

exch-name/exch-id/aps-name,version/xyz yy-mm-dd hh:mm:ss

job-no [[/OMT-0x/userid] datatype/masknumber

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 start-

up of the exchange via MML dialog

aps-name name of APS, created during initial start-up of theexchange via MML dialog

version APS function version, created during APS production

xyz CP operating mode

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

yy-mm-dd hh:mm:ss date and time of the output message

jobnumber[/jobnumber] jobnumber(s) created by the message control; during

command file processing a second jobnumber

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 PROCIN - 3


3.0.2 Explanations of the Procedure Elements

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;

12 Decision block

Must clearance of this fault be postponed (e.g. because no spare

modules available)?

Commentary are always written in italics

b CONF LTG:LTG=tsg-ltg,OST=ACT;

CONFIGURATION ABORTED, PLEASE DO STAT

To evaluate the system output, see

Continue according to the system reaction:

- EXEC’D..................................................................................................- NOT EXEC’D..........................................................................................

- else.........................................................................................................

i....PROC:LG001N

h.......18

h.......19

Y h .....13

N h .....16

.....4.19

Block number

Commentary(in italics)

MML commandinput

MML mask(Courier

Multiplebranch

Branch symbol

Yes/Nobranch

Branch dest.(block number)

Block

Reference tochapter withadditionalinformation

Branch symbolwith reentry

13 Decision block

typeface)

http://a006i176.pdf/








PROCIN- 4 A30808-X3074-A473-1-7620




A30808-X3074-A473-1-7620 ENTRY - 1


3.1 Identifying an Emergency Situation

3.1.1 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) indepen-

dently. In any case first of all a system specialist (TAC) is to be consulted!

3.1.2 Alarm Indication Plan for an Emergency Situation

*) For emergency coordinator function see register “Introduction (IN)”,

chapter 1.7 “Recommendations for emergency precautions”.

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.



ENTRY- 2 A30808-X3074-A473-1-7620


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:

• Note the time.

• Inform the emergency coordinator immediately.

3.1.3.2 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:

– 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 ENTRY - 3


3.1.3.3 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 recog-

nized a central problem and is reacting correctly within the programmed opera-

tions plan for this.

Entry point: SYP_AL

[2] System does not react to inputs

It must first be guaranteed that the malfunction is not the result of a malfunctionin the terminal or of a defective feeder. A temporary computer overload is also

considered as a cause.

Don´t 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: SYS_N_REA



ENTRY- 4 A30808-X3074-A473-1-7620


[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 (commonLTGB, 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 destina-

tions.

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



A30808-X3074-A473-1-7620 ENTRY - 5


T_CALLS

Revise the prepared test call

lists (see chapter 1.7 “Recom-

mendations for emergency

precautions”)

These lists must identify specifi-

cally 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 “Recommenda-

tions for emergency precautions”).

Is exchange traffic

disrupted ?Y

N

Is there a display on the

SYPD now?Y

N

Interrogate system status:

STAT SSP;

Is a list of the SSP units

and their corresponding

OSTs displayed?N

Y

SSP_LIST

EMCY

SYP_AL

EMCY





ENTRY- 6 A30808-X3074-A473-1-7620


SSP_LIST

The system is, apparently,

operating normally (again).

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)

YWere recovery messagesoutput 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 bySTAT SSP; show equipment

in UNA or MBL?

B

A C

MBL UNA

A: equipment in MBL:

Ascertain the cause:

- Has fault clearance begun?

- HW changes?

B: equipment in UNA:

An alarm must be displayed at

SYPD

Is an appropriate alarm

being displayed at

SYPD?Y

N

Special fault clearance SYPProceed further in consulta-

tion with TAC

NO

SYP_AL

END





A30808-X3074-A473-1-7620 ENTRY - 7


SYP_AL

Is there a critical alarm

(high flicker frequency)

for the lamps SYP and

CU?

Y

N

Standard Fault Clearance HW:

Entry as per MMN number of

the alarm messages deter-

mined in SYP100

Note:

This question should only be

asked after a few minutes have

passed because the SYP and

CU lamps can also flash during

recoveries.

Note:

The SYP100 procedure containsinterrogations for recognizing

emergency situations:

- Failure of both MDDs

- ISTART2G

- call processing basic operation

and directs the user to the corre-

sponding procedure.

Emergency Situation!

Consult TAC personnel!

Fault clearance only via TAC

(Phase 3) !

Emergency Situations :

A -> Failure of both MDDs.

B -> ISTART2G

A B

SYP100:

Emergency Situation

detected?N

Y

MMN:xxx

Normal entry into

MMN:SYP, procedureSYP100

Failure of both MDDs:

EMCYMN:EY710

ISTART2G (automatic fall-

back to backup gener.):

EMCYMN:EY190

(postprocessing)

EMCY

A total CP breakdown is likely

(EMCY).

MMN:XXX

EY710 EY190



ENTRY- 8 A30808-X3074-A473-1-7620


EMCY

Emergency situation!

(Phase 3 is initiated)

Were recovery messages

output at the assignedprinter in the OMC? N

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



A30808-X3074-A473-1-7620 ENTRY - 9


TAC_MENU

Further action is dependent on

the determined system status.

There exist 3 groups of emer-

gency procedures:

Entry situation 1:

“Unsuccessful Recovery”:

EY100

Entry situation 2:

“Overheating / Power failure”

EY350

Entry situation 3:

Critical alarm / alarm mask /

MMN:SYP / SYP 100 :

EY130 :manual initial startfrom MDD

EY170 / EY150 :rescue of backgroundmemory data / manual initial startfrom save tape

EY350 / EY370 :total shutdown / total restart

EY350 :total / partial shutdownEY350: ShutdownEY360: Partial restart

EY370: Total restart

EY380 :Measures after powerfailure

EY190 :Initial start (fall backgeneration)

EY500:Restoration of back-ground memory filesEY501: ChecksumEY502: GEN-filesEY503: NON-GEN- filesEY504: Restoration after double disk failure

EY710 :Double disk failureMDDEY730: (CP113C)



ENTRY- 10 A30808-X3074-A473-1-7620


SY_N_REA

5 minutes have passed

since first detection ?N

Y

Critical alarm on the

SYPD?Y

N

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?

Dial tone at service hand-

sets ?N

Y

EMCY

T_CALLS

SYP_AL



A30808-X3074-A473-1-7620 ENTRY - 11


SUB_COM

Connection to test

destination possible now?N

Y

EMCY

Critical alarm at SYPD? Y

N

SYP_AL

T_CALLS

Connection to test

destination possible?N

Y

In order to exclude a call-

processing error, a SSP recovery

of level NSTART3 should be

executed:

RECOV SSP:LEVEL=NSTART3;





ENTRY- 12 A30808-X3074-A473-1-7620


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 themessage 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 : ISTART2G

PERFORMED LEVEL : ISTART2G

PERFORMED ACTION(S) : 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.





A30808-X3074-A473-1-7620 ENTRY - 13


MML command inputs:

If the system reacts again to inputs, after recovery has been completed, further informa-

tion 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 BAP´s:

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)
























ENTRY- 14 A30808-X3074-A473-1-7620




A30808-X3074-A473-2-7620 EY100 - 1


3.2 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 iden-

tified 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 inte-

grated 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.



EY100- 2 A30808-X3074-A473-2-7620


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 deci-

sion 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 blockthat 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.



A30808-X3074-A473-2-7620 EY100 - 3


3.2.7 Diagram

Fig. 3.2.1 Diagram of procedure EY100

1 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.

i ...EMCYMN,PROC, ENTRY

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 impor-

tant advice on error identification.

...... Introduction

see procedure ENTRY

yes

any unused generations ?

manual initial start from MDD

(EY130) with different generations

EY130 successful ?

evaluate trace points andoutput messages

no

determine error cause

HW fault in HW fault in theperipheralsCP area

SW error

offline diagnostics;fault clearance;

run EY130

INSTALL MODE;diagnostics;

run EY130

manual initial startform save tape

(EY150)

error cleared ?

end of procedure

yes

no

no

end of procedure

yes

Overheating ?no

run procedure EY350 yes







EY100- 4 A30808-X3074-A473-2-7620


2 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.

Is total shutdown/restart necessary ? Y h...EMCYMN,

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.

Are there any APS generations which were not used by recovery ? Y h...4

N h...7

4 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.

i....EMCYMN,PROC, EY130



5 Success of Manual initial start from MDD

Was a manual initial start according to procedure EY130 successful ? Y h...16

N h...6

6 Further unused generations

Are there any unused APS generations on the background memories ? Y h...4

N h...7











A30808-X3074-A473-2-7620 EY100 - 5


7 Unused HW combination

Are there any unused HW combinations ? Y h...8

N h...9

8 Change HW combination

The hardware combination must be changed and then a manual initial start

must be initiated. h...4

9 Trace point A x x 5

Start-up attempts are made with all APS generations existing on the back-

ground 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 ? Y h...12N h...10

10 Trace point B x 7 4

Were the trace points B x 7 4 passed through in every start-up ? Y h...11

N h...2

11 Trace point B 2 5 4

Were the trace points B 2 5 4 reached in every start-up ? Y h...2

N h...14

12 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). h...1513 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.)







EY100- 6 A30808-X3074-A473-2-7620


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 ? Y h...16

N h...1

16 End of procedure

End of procedure

END



A30808-X3074-A473-2-7620 EY130 - 1


3.3 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 orin 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 suppres-

sion 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.












EY130- 2 A30808-X3074-A473-2-7620


3.3.2 Diagram


1 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 situa-

tions. During error free operation this procedure may not be executed. ......Introduction

2 CP selection

What kind of CP is installed ?

– CP113 h...3 – CP113C h...6

3 BAP selection at CP113

Which BAP shall execute the manual initial start ?

– BAP-0 h...4 – BAP-1 h...5

analyzing recovery message

noyes

irreparable faults duringmeter check ?

restoration of faultymeter counts according

to procedure SW223

display hardwareconfiguration

symptom savingaccording to

procedure SW231

manual initial start fromMDD is initiated

manual initial startsuccessful ?

delete alarmsback to previous

procedure

yes

no



A30808-X3074-A473-2-7620 EY130 - 3


4 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. Addi-

tionally 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

5 BOOT BAP 1 at CP113




Press RESET key for BAP-0


switch SPB in the ON position (up) on both modules.


6 BAP selection at CP113C


– BAP-0 h...7 – BAP-1 h...8

7 BOOT BAP 0 at CP113C




Locate module DCCMC for BAP-1 in BCMY-1 (moloc 101). Put switch S1 in the

OFF position (down).


8 BOOT BAP 1 at CP113C





OFF position (down).




EY130- 4 A30808-X3074-A473-2-7620


9 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 : “DIAG;”

TO FORMAT MEMORY : “FORMAT;”

TO CONTINUE : “;ETX”

b ;IPL113: MANUAL START ENTER PARAMS

TO START APS MANUALLY : “MANUALLY;”

TO START INSTALLAT.RECOV. : “INSTALLATION;”TO START UTILITY(MONITOR) : “UTILITY;”

TO STOP INITIAL START : “STOP;”

TO START APS AUTOMATICALLY : “;ETX”

10 Selection of MDD

Shall the manual initial start be carried out specific from MDD-0 or MDD-1 ? Y h...11N h...17



A30808-X3074-A473-2-7620 EY130 - 5


11 Start from fixed MDD

b MAN;IOC-0 MDD : BZS/AKD AND GENERATION-LIST

@#############

actgen @#######################

-------

backgen @#######################

-------

goldgen @#######################

IOC-1 MDD : BZS/AKD AND GENERATION-LIST

@#############

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 ?

– IOC-0 h...13 – IOC-1 h...14

13 Loading via IOC-0

b 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

b actgen;MANUAL RECOVERY - LTG LOADING : “Y;/N;”

Should the LTGs be load ? Y h...15N h...16



EY130- 6 A30808-X3074-A473-2-7620


14 Loading via IOC-1


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

b actgen;MANUAL RECOVERY - LTG LOADING : “Y;/N;”

Should the LTGs be load ? Y h...15N h...16

15 LTG loading

b Y; h...18

16 LTG not loading

b N; h...18

17 No fixed MDD

b ;

18 Selection of CP

What kind of CP is installed ?

– CP113 h...19 – CP113C h...22

19 BAP selection at CP113


– BAP-0 h...20 – BAP-1 h...21

20 BAP-0 booted at CP113


switch SPB in the OFF position (down) on both modules.

h...25

21 BAP-1 booted at CP113


switch SPB in the OFF position (down) on both modules.

h...25

22 BAP selection at CP113C


– BAP-0 h...23 – BAP-1 h...24



A30808-X3074-A473-2-7620 EY130 - 7


23 BAP-0 booted at CP113C


ON position (up).

h...25

24 BAP-1 booted at CP113C


ON position (up).

h...25



EY130- 8 A30808-X3074-A473-2-7620


25 Start-up messages

The following messages are an extract of whole recovery messages output.

SYSTEM - RECOVERY ALARM MMN:SW330-0001

DATE : @#######@

TIME : @#######@

PERFORMED LEVEL : ISTART2

PERFORMED ACTION(S) : @############################################

@##############################


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

##### INITIALSTART PROGRESS MESSAGE ##### 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. ......Introduction









A30808-X3074-A473-2-7620 EY130 - 9


26 Recovery message

SYSTEM - RECOVERY INFORMATION

REASON : @################################

@#######################################

DATE : @#######@

TIME : @#######@

UNIT : @#####

REQUESTED LEVEL : ISTART2

PERFORMED LEVEL : @########

PERFORMED ACTION(S) : @##############################################

@##############################

@###############################





THRESHOLD : @###





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

@######## @######## @######## @######## @########

For detailed information about the recovery output message see. ......NM:SW,ADMIN, IN

27 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 ? Y h...30

N h...29





EY130- 10 A30808-X3074-A473-2-7620


29 Return to procedure EY100

Was this procedure called by procedure EY100 ? Y h...EMCYMN,

PROC, EY100N h...EMCYMN,

PROC, EY190

30 Display alarm status

b DISP ALARM:OBJECT=RECOV;

The following message is an example for the whole alarm messages output.

command repetition EXEC’D

OBJECT = RECOV ALPRIO = MAJOR ALSTAT = @# MSGNO = @####

ALTYPE = @#######################

PABCAUSE= @#################################################

ALARM-ID: @#############################################################

31 Delete alarms

The following command has to be executed for all alarms with ALPRIO = MAJOR

that are assigned to an ISTART message.

b SET ALSTAT:MSGNO=msgno,ALSTAT=C;command repetition EXEC’D

32 Meter check

Are irreparable comparator faults determined during meter check ? Y h...33

N h...34

33 Meter restoration’name’ METER AUDIT

RESULT : NOT REPAIRABLE ERRORS ON FILE CA.ST.UCHA DETECTED

PLEASE START ’SAVE MET’WITH 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





















A30808-X3074-A473-2-7620 EY130 - 11


34 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.

b STAT SSP;command repetition EXEC’D

b STAT CCG;command repetition EXEC’D

b STAT MB;command repetition EXEC’D

b STAT SN;command repetition EXEC’D

b STAT CCNC:UNIT=CCNP-X;command repetition EXEC’D

b STAT CCNC:UNIT=SILT-X;command repetition EXEC’D

b STAT LTG:LTG=X-X;command repetition EXEC’D

b STAT DLU:DLU=X;command repetition EXEC’D

b STAT SYP;command repetition EXEC’D

35 Hardware status

Are all hardware units in the correct operating state ? Y h...36N 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






































EY130- 12 A30808-X3074-A473-2-7620




A30808-X3074-A473-2-7620 EY150 - 1


3.4 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.

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 following magnetic tapes are to be held ready

1. Tapes for reading of quarterly saved data

2. Tapes for reading of routine saved data

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.



the IOP:AUC module.

In certain cases the appropriate authentification key must be loaded from ACM cards viaa Chip Card Reader into the IOC:AUC modules. Description see OMN:SSS, SU,

TS-011.

tape (/ continuation tape) of the last APS quarterly saving

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)



EY150- 2 A30808-X3074-A473-2-7620


3. Tapes for reading of other saved data

3.4.1.2 For users of the function “Manual on PC”:





via the menu item DISPLAY/HISTORY. When this menu item is called up, a list of theprocedure 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


3.4.2 Procedure description

1 Information

Before execution of this procedure, rescue of background memory data is to be

done, according to procedure EY170. i....EMCYMN,PROC, EY170



2 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.

3 Decision.

Is there a CP113C in use? Y h...6

N h...4

4 Reset BAP-1.

Press RESET-key for BAP-1.

5 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). h...7

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)







A30808-X3074-A473-2-7620 EY150 - 3


6 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

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.



EY150- 4 A30808-X3074-A473-2-7620


8 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.





b FORMAT;IPL113: MANUAL START - CURRENT CONFIGURATION

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 @##### @#####





b ;



A30808-X3074-A473-2-7620 EY150 - 5


9 Manual bootstrap - parameter input.IPL113: MANUAL START ENTER PARAMS

TO START APS MANUALLY : “MANUALLY;”TO START INSTALLAT.RECOV. : “INSTALLATION;”

TO START UTILITY(MONITOR) : “UTILITY;”



b UTI;

10 Manual bootstrap - set up installation monitor.UTILITY-RECOVERY - DEVICE-TYPE TO USE : “MDD;/MTD;/MOD;”

b MTD;UTILITY-REC. - LOAD FROM IOC/IOP/DEVICE-NO (HEX):

b device-no;PLEASE ENTER UTILITY-FILE-NAME

The following command must be entered without a semicolon!

b SY.INSTALLIMON: (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? Y h...12

N h...13

12 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.

CP113D device-no=010D03 marks the physical address of MTD-0 CP113C device-no=010C03 marks the physical address of MTD-0



EY150- 6 A30808-X3074-A473-2-7620


b INIT MD:DEVOUT=devout;VOLIN: FORMATTING DISK ...

IMON: COMMAND INITMD EXECUTED

IMON: ENTER COMMAND

b LABEL MD:DEVOUT=devout;IMON: COMMAND LABELMD EXECUTED

PLEASE ENTER UTILITY-FILE-NAME

b INIT MD:DEVOUT=devout;VOLIN: FORMATTING DISK ...

IMON: COMMAND INITMD EXECUTED

IMON: ENTER COMMAND


IMON: ENTER COMMAND

h...14

13 Installation monitor - initialize background memories.


PLEASE ENTER UTILITY-FILE-NAME


IMON: ENTER COMMAND

CP113D DEVOUT=010E01 marks the physical address of MDD-0

CP113C DEVOUT=010C01 marks the physical address of MDD-0









A30808-X3074-A473-2-7620 EY150 - 7


14 Decision.


N h...15

15 CP113D: Enable bus access for BAP-1.


On both modules put switch SPB in the OFF position (down). h...17

16 CP113C: Enable bus access for BAP-1.


Put switch S1 in the ON position (up). h...17

17 Decision.

Is it necessary to carry out continuation tape handling during the quarterly save

of the APS? Y h...19N h...18

18 Installation monitor - transfer APS quarterly save tape files to MDD-0.

b TRANS FILE:DEVIN=devin,DEVOUT=devout,FILECAT=*,OLDGEN=*,

NEWGEN=*;

TRANS: FILE file name-1 GEN powerset-inf COPIED TO FILE

file name-1 GEN powerset-inf

: : : : : : : : :

: : : : : : : : :

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

file name-n GEN powerset-inf

TRANS: ADDITIONAL TAPES ? (Y/N)

h...21

CP113D DEVIN= 010D03 marks the physical address of MTD-0

DEVOUT= 010E01 marks the physical address of MDD-0

CP113C DEVIN= 010C03 marks the physical address of MTD-0

DEVOUT= 010C01 marks the physical address of MDD-0

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



EY150- 8 A30808-X3074-A473-2-7620



b TRANS FILE:DEVIN=devin,DEVOUT=devout,FILECAT=*,OLDGEN=*,

NEWGEN=*;

TRANS: FILE file name-1 GEN powerset-inf COPIED TO FILE

file name-1 GEN powerset-inf

: : : : : : : : :

: : : : : : : : :

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

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

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).

b Press ENTER-key.TRANS: FILE file name-x+1 GEN powerset-inf COPIED TO FILE

file name-x+1 GEN powerset-inf

TRANS: FILE file name-x+2 GEN powerset-inf COPIED TO FILE

file name-x+2 GEN powerset-inf

: : : : : : : : :

: : : : : : : : :

Was another continuation tape requested? Y h...20

N h...21





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-1SY.LOADLIB.LA SY.PSW.Txxn :

SY.LOADLIB.MA SY.SEMILIB :

SY.SIMP CG.SA.name-n

SY.TASKLIB D9.VLRAL



A30808-X3074-A473-2-7620 EY150 - 9


20 Installation monitor - transfer APS quarterly save tape files to MDD-0.TRANS: FILE file name-y GEN powerset-inf COPIED TO FILE

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).

Mount and load APS quarterly save tape (part 3).

b Press ENTER-key.TRANS: FILE file name-y GEN powerset-inf COPIED TO FILE

file name-y GEN powerset-inf

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

file name-y+1 GEN powerset-inf

: : : : : : : : :

: : : : : : : : :

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

file name-n GEN powerset-inf



b NIMON: COMMAND TRANSFILE EXECUTED

IMON: ENTER COMMAND

Rewind tape to the load point manually. h...22

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? Y h...24

N h...27


Mount and load the save tape with file D9.VLRAL which was created during

procedure EY170.



EY150- 10 A30808-X3074-A473-2-7620


25 Installation monitor - transfer file D9.VLRAL to MDD-0.

b CAN FILE:FILE=D9.VLRAL,DEVOUT=devout,OLDGEN=00;

b TRANS FILE:DEVIN=devin,DEVOUT=devout,

FILECAT=D9.VLRAL,

OLDGEN=*,NEWGEN=*;

TRANS: FILE D9.VLRAL GEN powerset-inf COPIED TO FILE

D9.VLRAL GEN powerset-inf


b NIMON: COMMAND TRANSFILE EXECUTED

IMON: ENTER COMMAND

Rewind tape to the load point manually.


Rewind and remove save tape with file D9.VLRAL.

27 Decision.

Are statistic meters administered in the network node ? Y h...28N h...35

28 Decision.

Were statistic meters saved according to procedure EY170? Y h...29N h...32


Mount and load the meter save tape which was created during procedure

EY170.







A30808-X3074-A473-2-7620 EY150 - 11


30 Installation monitor - transfer APS meter save tape files to MDD-0.


FILECAT=CA.ST.UCHA

OLDGEN=*,NEWGEN=*;

TRANS: FILE CA.ST.UCHA GEN powerset-inf COPIED TO FILE

CA.ST.UCHA GEN powerset-inf

IMON: COMMAND TRANSFILE EXECUTED

IMON: ENTER COMMAND



Rewind and remove statistic meter save tape. 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.


FILECAT=CA.ST.UCHAOLDGEN=*,NEWGEN=*; TRANS: FILE CA.ST.UCHA GEN powerset-inf COPIED TO FILE

CA.ST.UCHA GEN powerset-inf

IMON: COMMAND TRANSFILE EXECUTED

IMON: ENTER COMMAND



Rewind and remove APS routine save tape.











EY150- 12 A30808-X3074-A473-2-7620


35 Installation monitor - display catalog entries.

b 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 quarterup to now? Y h...37

N h...82

37 Decision.


N h...38

38 Reset BAP-1.


CP113D DEVIN=010E01 marks the physical address of MDD-0

CP113C DEVIN=010C01 marks the physical address of MDD-0



A30808-X3074-A473-2-7620 EY150 - 13










Important note:

The entries “;” and “INS;“ according to the next two blocks must be made imme-

diately after the corresponding requests for entry have been made.


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 : “DIAG;”TO FORMAT MEMORY : “FORMAT;”


b ;



EY150- 14 A30808-X3074-A473-2-7620







b INS;

44 Manual bootstrap - initiate installation recovery.IOC-0 MDD : BZS/AKD AND GENERATION-LIST

@#############

backgen @#######################


@#############

INSTALLATION RECOV. - LOADING VIA IOC : “IOC-0;/IOC1;”


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”).

b backgen;

Note:

Due to system recovery entries will not be accepted for several minutes!

45 Decision.


N h...46

46 CP113D: Enable bus access for BAP-1.Locate module PIDAT for BAP-1 in BCMY-0 and BCMY-1 (moloc 145).







A30808-X3074-A473-2-7620 EY150 - 15




and the password. After input of user identification and password the command 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.

b START FCP;command repetition ACCEPTED

: : : :

: : : :


h...50

50 Recovery report.FCP RECOVERY REPORT


-------+----+-----------

MDD-00 ACT YES

MDD-01 ACT NO


---------+------------------+------------

backgen @####### @####### YES

FCP UPDATE REPORT

LAST EXECUTED TRANSACTION : DATE = @####### @#######

JOBNO= @###

FILES UPDATED BY LAST TRANSACTION :

FILENAME: GENERATION:

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

SY.SEMILIB backgen


faulty. ...... Important userinformation

51 Start operation and maintenance processes.

b START OM;command repetition ACCEPTED

: : : :

: : : :












EY150- 16 A30808-X3074-A473-2-7620


52 Start safeguarding processes.

b START SFGSW;command repetition ACCEPTED

: : : :

: : : :


53 Start control and switching devices process group (CSWD).

b START CSWD;command repetition ACCEPTED

: : : :

: : : :




Use the APS routine save tape which was used latest.

55 Determine generation name on disk.

b DISP GEN;NAME OF CURRENT GENERATION: backgen

LIST OF GENERATIONS:

HISTORY GENERATION VALIDITY FILES CREATION DATE SET REFGEN

----------+----------+---------+-----+-----------------+---+------------

BACKUP backgen VALID @## @####### @####### @## @#######


56 Determine generation name on tape.

b DISP GEN:VSN=LOGTAP;NAME OF CURRENT GENERATION: backgen



----------+----------+---------+-----+-----------------+---+------------

FIXPOINT fixgen BLOCKED @## @####### @####### @## @#######



















A30808-X3074-A473-2-7620 EY150 - 17


57 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.

b TRANS SYFILE:GEN=fixgen,VSN=LOGTAP,REASON=REINST,VERIFY=Y;command repetition ACCEPTED

58 Tape to disk transfer of fixpoint generation - continuation.

Was the fixpoint generation “fixgen” transferred successfully? Y h...59

N h...60

59 Tape to disk transfer of fixpoint generation - continuation.command repetition EXEC’D

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 @### @### @######## @####### h...62

60 Tape to disk transfer of fixpoint generation - continuation.command repetition NOT EXEC’D

Additional texts relating to NOT EXEC’D can be ignored.


Rewind and remove APS routine save tape. h...82

62 Determine generation names on disk.




----------+----------+---------+-----+-----------------+---+------------


FIXPOINT fixgen BLOCKED @## @####### @####### @## @#######














EY150- 18 A30808-X3074-A473-2-7620


63 Set the fixpoint generation valid.

The name of the fixpoint generation on tape (“fixgen”), which was determined


b MOD GEN:GEN=fixgen,VALIDITY=VALID;command repetition EXEC’D





----------+----------+---------+-----+-----------------+---+------------


FIXPOINT fixgen VALID @## @####### @####### @## @#######


65 Decision.

Is file D9.VLRAL administered in the network node and was the saving of this

file according to procedure EY170 successful? Y h...68

N h...66

66 Transfer of file D9.VLRAL

b DEL FILE:FILE=D9.VLRAL;


b TRANS FILE:FILE=D9.VLRAL,VSNS=LOGTAP;command repetition ACCEPTED

: : : :

: : : :


SENDER : @#######RECEIVER : @#######

START START



-+-----------------+------+-----+-+-----+-+--+----+---------+-----+-----

S D9.VLRAL @##### @#### @ @#### @ @# @### @######## @#### @####

R D9.VLRAL @##### @#### @ @#### @ @# @### @######## @#### @####





















A30808-X3074-A473-2-7620 EY150 - 19


68 Decision.


N h...69

69 Reset BAP-1.










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.


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 @##### @#####





b ;



EY150- 20 A30808-X3074-A473-2-7620







b MAN;


@#############

backgen @#######################

fixgen @#######################


@#############




(“fixgen”).


(“fixgen”).

b fixgen;MANUAL RECOVERY - LTG LOADING : “Y;/N;”

b Y;

Note:


76 Decision.

Is there a CP113C in use? Y h...78N h...77









A30808-X3074-A473-2-7620 EY150 - 21


79 Decision.

Was the recovery successful? Y h...81

N h...80

80 Decision.

The system reactions, described in the next block, do not appear or do only

incompletely appear. Or recovery escalations are started. h...82

81 Recovery report.

Extract of the recovery report.

: : : :

: : : :





EY150- 22 A30808-X3074-A473-2-7620


DATE : @#######@

TIME : @#######@


PERFORMED ACTION(S) : MEMORY HAS BEEN INITIALIZED @##############################

APS GENERATION : fixgen

FCP RECOVERY REPORT


-------+----+-----------

MDD-00 ACT YES

MDD-01 ACT NO


---------+------------------+------------

fixgen @####### @####### YES

: : : :

: : : :




: : :

: : :






##### INITIALSTART PROGRESS MESSAGE ##### START OF LTU-DATA DOWNLOADING






START OF DLU-DATA DOWNLOADING


END OF LTG LOADING

: : : :

: : : :


: : : :

: : : :


REASON : REQUIRED MANUAL START

@#######################################

DATE : @#######@

TIME : @#######@

UNIT : @#####







A30808-X3074-A473-2-7620 EY150 - 23




PERFORMED ACTION(S) : MEMORY HAS BEEN INITIALIZED @##############################




APS GENERATION : fixgen


THRESHOLD : @###





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

@######## @######## @######## @######## @########

: : : :

: : : :


faulty. ...... Important userinformation

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 h...94

82 Decision.


N h...83

83 Reset BAP-1.









EY150- 24 A30808-X3074-A473-2-7620







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.


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 @##### @#####





b ;



TO START INSTALLAT.RECOV. : “INSTALLATION;”




b MAN;



A30808-X3074-A473-2-7620 EY150 - 25



@#############

backgen @#######################------

fixgen @#######################

------


@#############


Remark:




(“backgen”).


(“backgen”).

b backgen;MANUAL RECOVERY - LTG LOADING : “Y;/N;”

b Y;

Note:


90 Decision.



Locate module PIDAT for BAP-1 in BCMY-0 and BCMY-1 (moloc 145).On both modules put switch SPB in the OFF position (down). h...93






EY150- 26 A30808-X3074-A473-2-7620


93 Recovery report.


: : : :

: : : :


DATE : @#######@

TIME : @#######@



@##############################

APS GENERATION : backgen

FCP RECOVERY REPORT


-------+----+-----------

MDD-00 ACT YES

MDD-01 ACT NO


---------+------------------+------------

backgen @####### @####### YES

: : : :

: : : :


LTG-CODE DOWNLOADING LOADTYPE xx START xx. OF nn CODE SEGMENTS

: : :

: : :















END OF LTG LOADING

: : : :

: : : :


: : : :

: : : :









A30808-X3074-A473-2-7620 EY150 - 27



@#######################################

DATE : @#######@

TIME : @#######@UNIT : @#####




@##############################




APS GENERATION : backgen


THRESHOLD : @###





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

@######## @######## @######## @######## @########

: : : :

: : : :









STATISTIC CHARGING




is executed.



95 Display Generation

Note:

Due to system recovery entries will not be accepted for several minutes! Try to


b DISP GEN;








EY150- 28 A30808-X3074-A473-2-7620


96 Decision.

Was at least one APS routine saving already carried out in the current quarter

up to now? Y h...98N h...97

97 Determine generation name on disk.NAME OF CURRENT GENERATION: backgen



----------+----------+---------+-----+-----------------+---+------------



h...99

98 Determine generation names on disk.NAME OF CURRENT GENERATION: @#######



----------+----------+---------+-----+-----------------+---+------------




99 Decision.

Was the saving of LOG files according to procedure EY170 successful? Y h...100

N h...106


Mount and load the LOG file save tape.

Use the LOG file save tape which was created during procedure EY170.

101 Define process-switches.

b RESET CFOPT;command repetition EXEC’D

b SET CFOPT:ON=15;command repetition EXEC’D











A30808-X3074-A473-2-7620 EY150 - 29


102 Start command file CG.SA.REC51.

Copying of actual LOG files is to be executed.

b EXEC CMDFILE:FILE=CG.SA.REC51; ......MMN:SW, TAB,REC51

command repetition STARTED

: : : :

: : : :

command repetition FINISHED


Rewind and remove LOG file save tape.




Activation of LOG function is to be executed.



: : : :

: : : :


106 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

107 Decision.


up to now? Y h...112

N h...108

108 Decision.

Was the saving of LOG files according to procedure EY170 successful? Y h...110N h...109



















EY150- 30 A30808-X3074-A473-2-7620


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 All entries should be done according to the note. h...129



b SET CFOPT:ON=16;



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.

b ACT IAOPT:BLBUFR=ADMREC;DANGEROUS COMMAND ACTIAOPT READY TO EXECUTE<

b ;command repetition EXEC’D

Updating database is to be executed.



: : : :

: : : :


Before updating of database was started, the storage of administrative records

was suppressed. This suppression is canceled again using the following

command.

b CAN IAOPT:BLBUFR=ADMREC;DANGEROUS COMMAND CANIAOPT READY TO EXECUTE<


h...129




















A30808-X3074-A473-2-7620 EY150 - 31




Use the tape which was created during the last APS routine saving.




Copying of actual LOG files is to be executed.



: : : :

: : : :







Activation of LOG function is to be executed.



: : : :

: : : :






















EY150- 32 A30808-X3074-A473-2-7620




Which routine saving was the last one which was executed in this quarter?

– The 1st routine saving was the last one in the current quarter. h...119 – The 2st routine saving was the last one in the current quarter. h...120 – The 3st routine saving was the last one in the current quarter. h...121 – The 4st routine saving was the last one in the current quarter. h...122 – The 5st routine saving was the last one in the current quarter. h...123



h...124



h...124



h...124



h...124



h...124















A30808-X3074-A473-2-7620 EY150 - 33











: : : :

: : : :




command.



125 Decision.

Was the saving of LOG files according to procedure EY170 successful? Y h...127N h...126

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.

b All entries should be done according to the note. h...129















EY150- 34 A30808-X3074-A473-2-7620














: : : :

: : : :




command.



h...129
























A30808-X3074-A473-2-7620 EY150 - 35



Postprocessing after recovery is to be executed.



: : : :

: : : :


131 Display alarm status.

b DISP ALARM:OBJECT=RECOV;


OBJECT = RECOV ALPRIO = MAJOR ALSTAT = NP MSGNO = msgno

ALTYPE = @#######################

PABCAUSE= @#################################################

ALARM-ID: CLASS=ISTART

NO (MORE) DATA FOR DISPLAY AVAILABLE.

The following block is to be executed with the determined message number

(“msgno”).

132 Reset alarm.


133 Decision.


up to now? Y h...135

N h...134

134 Determine generation name on disk.




----------+----------+---------+-----+-----------------+---+------------



h...140























EY150- 36 A30808-X3074-A473-2-7620


135 Decision.

Was a successful recovery carried out by using the fixpoint generation

(“fixgen”)? Y h...138N h...136





----------+----------+---------+-----+-----------------+---+------------




137 Delete fixpoint generation.

The name of the fixpoint generation on disk (“fixgen”), which was determined


b CAN GEN:GEN=fixgen;DANGEROUS COMMAND CANGEN READY TO EXECUTE<

b ;command repetition

NAME OF CURRENT GENERATION: backgen



----------+----------+---------+-----+-----------------+---+------------



DO YOU REALLY WANT TO CANCEL GENERATION ?

PLEASE ENTER (YES: +/NO: -)<

b +LIST OF ERASED FILES OF THE FORMER GENERATION : fixgen

FILE:

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

SY.SEMILIB

SY.SIMP


h...140

















A30808-X3074-A473-2-7620 EY150 - 37



b DISP GEN;NAME OF CURRENT GENERATION: fixgen



----------+----------+---------+-----+-----------------+---+------------




139 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.

b CAN GEN:GEN=backgen;DANGEROUS COMMAND CANGEN READY TO EXECUTE<


NAME OF CURRENT GENERATION: fixgen



----------+----------+---------+-----+-----------------+---+------------





b +LIST OF ERASED FILES OF THE FORMER GENERATION : backgen

FILE:

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

SY.SEMILIB

SY.SIMP


140 List traffic measurement jobs.

b DISP TRAMORD:STATUS=ALL;

141 Decision.

Were traffic measurement jobs running at the time the APS quarterly save tape

used in this procedure was generated? Y h...142

N h...143




















EY150- 38 A30808-X3074-A473-2-7620


142 List traffic measurement jobs - continuation.LIST OF STARTED TRAFFIC MEASUREMENT ORDERS

JOB COMMAND B:BEGIN INTERVAL PER FILENAMENO AND ADDITIONAL DATA E:END IOD

----+--------------------------+----------+-----------+---+-------------

-- ----

no code @ @############## @#@####### @########## @## name

: : : : : : :

: : : : : : :

no code @ @############## @#@####### @########## @## name

no code @ @############## @#@####### @########## @## @##########

: : : : : : :

: : : : : : :

no code @ @############## @#@####### @########## @## @##########

-- ----


Remark:

One, more or all mask entry (entries) between broken lines is (are) present. h...144

143 List traffic measurement jobs - continuation.NO (MORE) DATA FOR DISPLAY AVAILABLE.


h...146

144 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.

b CAN JOB:JN=no,CMDCOD=code;command repetition EXEC’D

145 List traffic measurement jobs.b DISP TRAMORD:STATUS=ALL;




b DISP MUSMORD:STATUS=ALL;


















A30808-X3074-A473-2-7620 EY150 - 39


147 Decision.

Were traffic measurement jobs running at the time the APS quarterly save tape

used in this procedure was generated? Y h...148N h...149

148 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 @ @############## @#@####### @########## @## @##########

-- ----


Remark:


149 List traffic measurement jobs - continuation.NO (MORE) DATA FOR DISPLAY AVAILABLE.


h...152

150 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.

b CAN JOB:JN=no,CMDCOD=code;command repetition EXEC’D


b DISP MUSMORD:STATUS=ALL;NO (MORE) DATA FOR DISPLAY AVAILABLE.
















EY150- 40 A30808-X3074-A473-2-7620


152 Activate meter fallback measures.

b SAVE MET:FUNC=FALLBACK;command repetition ACCEPTED

: : : :

: : : :


153 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 immedi-

ately! h...MMN:SW,PROC, SW210

154 End of procedure.

END










A30808-X3074-A473-2-7620 EY170 - 1


3.5 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 configura-

tion).

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 nega-

tive reaction occurs, which is caused by a main memory mutilation, this procedure

should be aborted and is to be considered inexecutable.

The following magnetic tapes are to be held ready

1. Tapes for saving of data call records

2. Tapes for saving of logging data

3. Tapes for saving history data



the IOP:AUC module.



TS-011.

1 large magnetic tape with write ring for saving the file IA.ICAMA

1 large magnetic tape with write ring for saving the file IA.ICMCR

1 small magnetic tape with write ring for saving the file IA.ICINA

1 medium-sized magnetic tape with write ring for saving the LOG data

1 large magnetic tape with write ring for saving the history files



EY170- 2 A30808-X3074-A473-2-7620


4. Tapes for saving of HLR specific data


1 Decision.


N h...2

2 Reset BAP-1.










Important note:

The entries “;” and “INS;“ according to the next two blocks must be made imme-

diately after the corresponding requests for entry have been made.

1 small-sized magnetic tape with write ring for saving the file D9.VLRAL



A30808-X3074-A473-2-7620 EY170 - 3



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 @##### @#####





b ;







b INS;



EY170- 4 A30808-X3074-A473-2-7620



@#############

gen-x @####################### : :

: :

gen-n @#######################


@#############

gen-x @#######################

: :

: :

gen-n @#######################


b IOC-0;

LOAD.DEV.=*MDD0* -GENERATION TO LOAD : “NAME;”(8 CHAR)

The generation list displayed above shows the names of the available genera-

tions (“gen-x” to “gen-n”).


(“gen-n”).

If recovery is not successful, the procedure can be repeated with the other

generations.

b gen-n;

Note: Due to system recovery entries will not be accepted for several minutes! Try to





is executed.



10 Start file control process (FCP).

b START FCP;command repetition ACCEPTED

: : : :

: : : :


h...11





A30808-X3074-A473-2-7620 EY170 - 5


11 Recovery report.FCP RECOVERY REPORT

ACTUAL CONFIGURATION: UNIT OST LOAD DEVICE -------+----+-----------

MDD-00 ACT YES

MDD-01 ACT NO


---------+------------------+------------

actgen @####### @####### YES

FCP UPDATE REPORT


JOBNO= @###



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

SY.SEMILIB gen-n

: : : :

: : : :

DEFAULT OUTPUT! DATATYPE/MSGRPNO: @### FORMAT: @####

CAUSE: DLL NOT RUNNING

: : : :

: : : :

If error messages for IOP:AUC are displayed, the authentification keys may be faulty. ...... Important user

information


b START OM;command repetition ACCEPTED

: : : :

: : : :



b START SFGSW;command repetition ACCEPTED

: : : :

: : : :














EY170- 6 A30808-X3074-A473-2-7620


14 Start process ICOM1.

b START PROCESS:NAME=ICOM1;command repetition ACCEPTED

: : : :

: : : :


15 Start process MMILF.

b START PROCESS:NAME=MMILF;command repetition ACCEPTED

: : : :

: : : :


16 Decision.








19 Display catalog entries.

b DISP FILE;command repetition EXEC’D

@################## @#############################

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.














A30808-X3074-A473-2-7620 EY170 - 7


20 Decision.

Was file CA.ST.UCHA determined in the catalog display ? Y h...21

N h...27


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.


b RESET CFOPT;



Saving of file CA.ST.UCHA is to be executed.



: : : :

: : : :



Rewind and remove CA.ST.UCHA tape.

Was the file transferred? Y h...25

N h...26

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.

h...27


The tape is to be held ready for other use.

27 Decision.

Was file IA.ICAMA determined in the catalog display ? Y h...28N h...35












EY170- 8 A30808-X3074-A473-2-7620



Mount and load for saving of file IA.ICAMA.

A large magnetic tape with write ring, overwritable or empty, is to be used.

Is the file IA.ICAMA protected by a password against unauthorized reading? Y h...29

N h...30

29 Enable read access.

b ENTR FILEPSW;PLEASE ENTER FILEPASSWORD

<

b file-password





Saving of file IA.ICAMA is to be executed.



: : : :

: : : :



Rewind and remove IA.ICAMA data record tape.

Was the file transferred? Y h...33

N h...34


The tape is to be marked as IA.ICAMA data record tape and is to be stored for

further use.

h...35




















A30808-X3074-A473-2-7620 EY170 - 9


35 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).

Was the file IA.ICMCR determined in the catalog display? Y h...36

N h...43


Mount and load for saving of file IA.ICMCR .


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



<

b file-passwordcommand repetition EXEC’D




Saving of file IA.ICMCR is to be executed.



: : : :

: : : :



Rewind and remove IA.ICMCR data record tape.

Was the file transferred? Y h...41N h...42

















EY170- 10 A30808-X3074-A473-2-7620



The tape is to be marked as IA.ICMCR data record tape and is to be stored for

further use.

h...43



43 Decision.

Was the file IA.ICINA determined in the catalog display? Y h...44

N h...51


Mount and load for saving of file IA.ICINA .

A small magnetic tape with write ring, overwritable or empty, is to be used.

Is the file IC.INA protected by a password against unauthorized reading? Y h...45N h...46



<

b file-passwordcommand repetition EXEC’D




Saving of file IA.ICINA is to be executed.



: : : :

: : : :



















A30808-X3074-A473-2-7620 EY170 - 11



Rewind and remove IA.ICINA data record tape.

Was the file transferred? Y h...49N h...50


The tape is to be marked as IA.ICINA data record tape and is to be stored for

further use.

h...51



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

N h...58


Mount and load for LOG data saving.

A small-sized magnetic tape with write ring, overwritable or empty, is to be used.




LOG data saving is to be executed.



: : : :

: : : :



Rewind and remove LOG data save tape.

Were LOG data files transferred? Y h...56

N h...57












EY170- 12 A30808-X3074-A473-2-7620



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.

h...58



58 Decision.

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

N h...65


Mount and load for history files saving.





History files saving is to be executed.



: : : :

: : : :



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

N h...64


The tape is to be marked as the save tape of the faulty generation and sent to

the diagnostic center (TAC 3).

h...65















A30808-X3074-A473-2-7620 EY170 - 13


65 Decision.

Was the file D9.VLRAL determined in the catalog display? Y h...66

N h...71


Mount and load for D9.VLRAL data saving.

A small-sized magnetic tape with write ring, overwritable or empty, is to be used.


D9.VLRAL saving is to be executed.



: : : :

: : : :



Rewind and remove meter file save tape.

Was file D9.VLRAL transferred? Y h...69N h...70


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.

h...71



71 Execute EMCYMN procedure EY150.

Recovery from the APS quarterly save tape is to be executed in accor-

dance with EMCYMN procedure EY150. h...EMCYMN,PROC, EY150


END














EY170- 14 A30808-X3074-A473-2-7620




A30808-X3074-A473-2-7620 EY190 - 1


3.6 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

!

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 inthe IOP:AUC module.



TS-011.



EY190- 2 A30808-X3074-A473-2-7620




when this procedure has been worked through it will be necessary to return to the deci-sion block of the calling procedure.



procedure blocks that have been processed so far is displayed. In this list, the last block



1 Decision.

How is the procedure to be used? – Manual recovery (FALLBACK GENERATION) is to be done. h...2 – Manual postprocessing after automatic recovery (FALLBACK GENERA-

TION) is to be done. h...3

2 Initiate ISTART2G.

b RECOV SYSTEM:LEVEL=ISTART2G;DANGEROUS COMMAND RECOVSYSTEM READY TO EXECUTE<

b ;






A30808-X3074-A473-2-7620 EY190 - 3


3 Recovery report. : : : :

: : : :

FCP RECOVERY REPORT


-------+----+-----------

MDD-00 ACT YES

MDD-01 ACT NO


---------+------------------+------------

@####### @####### @####### @##

: : : :

: : : :

SYSTEM - RECOVERY ALARM MMN:EY190-0000

DATE : @#######@

TIME : @#######@



@##############################


: : : :

: : : :

FCP UPDATE REPORT

LAST EXECUTED TRANSACTION : DATE = @####### @####### JOBNO= @###



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

@################ @#######

: : : :

: : : :


: : : :

: : : :




: : :

: : :









START OF LTG-PORTDATA DOWNLOADING##### INITIALSTART PROGRESS MESSAGE #####










EY190- 4 A30808-X3074-A473-2-7620






END OF LTG LOADING


faulty. ......General infor-mation.

4 Recovery report 2. : : : :

: : : :


REASON : @################################

@#######################################

DATE : @#######@

TIME : @#######@

UNIT : @#####

REQUESTED LEVEL : ISTART2G



@##############################






THRESHOLD : @###





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

@######## @######## @######## @######## @########




is executed.





A30808-X3074-A473-2-7620 EY190 - 5



b DISP ALARM:OBJECT=RECOV;command repetition EXEC’D

OBJECT = @####### ALPRIO = @####### ALSTAT = @# MSGNO = @####

ALTYPE = @#######################

PABCAUSE= @#################################################

ALARM-ID: @#############################################################

: : : :

: : : :

OBJECT = RECOV ALPRIO = CRITICAL ALSTAT = NP MSGNO = @####

ALTYPE = @#######################

PABCAUSE= @#################################################

ALARM-ID: CLASS=ISTART2G : : : :

: : : :


ALTYPE = @#######################

PABCAUSE= @#################################################

ALARM-ID: @#############################################################

NO (MORE) DATA FOR DISPLAY AVAILABLE. h...7

7 Search alarm.

This block is to be executed with all message numbers of category ALPRIO=CRITICAL.

b SRCH ALARM:MSGNO=msgno; : : : :

: : : :

SYSTEM - RECOVERY ALARM MMN:@#########

DATE : @#######@

TIME : @#######@



@##############################


: : : :

: : : :



















EY190- 6 A30808-X3074-A473-2-7620


8 Delete alarm.

This block is to be executed with all message numbers assigned to the

ISTART2G message.


9 Decision.

Are statistic meters administered? Y h...10

N h...11

10 Cancel time job for meter routine saving.

b DISP CFTJOB;command repetition EXEC’D

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.

b CAN JOB:JN=jobnumber,CMDCOD=EXECCMDFILE;command repetition EXEC’D













A30808-X3074-A473-2-7620 EY190 - 7


11 List generations.

b DISP GEN;command repetition

NAME OF CURRENT GENERATION: @#######



----------+----------+---------+-----+-----------------+---+------------

@######### actgen @######## @## @####### @####### @## @#######

@######### backgen @######## @## @####### @####### @## @#######

@######### oldgold @######## @## @####### @####### @## @#######


Which of the generations listed above is the current generation (compare NAME

OF CURRENT GENERATION and LIST OF GENERATIONS)? This is thegeneration 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 – The NAME OF THE CURRENT GENERATION is identical to the entry in the

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

– The NAME OF THE CURRENT GENERATION is identical to the entry in the3rd 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














EY190- 8 A30808-X3074-A473-2-7620


13 Decision.


N h...16

14 Activation of the charging fallback actions.


: : : :

: : : :



Rewind and remove APS routine save tape.The tape is to be marked as current APS routine save tape and to be held ready

for further use.


Symptom saving is to be executed according to procedure SW231.

Continue here, after execution of MMN:SW, procedure SW231

i....MMN:SW,PROC, SW231



17 Decision.

Are statistic meters administered? Y h...18N h...52


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 D ISP METSAV a nd delay the

start of the command file if necessary.

b EXEC CMDFILE:FILE=CG.SA.METAP; ......MMN:SW,TAB, METAP


: : : :

: : : :






















A30808-X3074-A473-2-7620 EY190 - 9


20 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 a nd adjust the

starting time of the command file ( TIME =..-..) accordingly.

b EXEC CMDFILE:FILE=CG.SA.METAP,DATE=yy-mm-dd,TIME=hh-mm,

PER=YES;

......MMN:SW,TAB, METAP

command repetition 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). h...52

21 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:









('SAVE MET : FUNC=FALLBACK') IS REQUIRED FOR THE FOLLOWING CHARGING TYPE(S) :

STATISTIC CHARGING

22 Deactivate LOG function.

b RSET LOG;DANGEROUS COMMAND RSETLOG READY TO EXECUTE<

b ;LOG-FUNCTION MESSAGE:

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

MASTER-LOG-FILE READY FOR USE: @################




















EY190- 10 A30808-X3074-A473-2-7620


23 Blocking of memory entries.



regeneration of LOG data is avoided.



24 Define process- switches.

b RESET CFOPT;



Regeneration of LOG data is to be executed.

b EXEC CMDFILE:FILE=CG.SA.REC91; ......MMN:SW,TAB, REC91


: : : :

: : : :


26 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.



27 Decision.


N h...31

28 Information.

During account suspension, no begin and end meter readings are displayed

when subscribers are created or canceled.


















A30808-X3074-A473-2-7620 EY190 - 11




: : : :

: : : :




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

of save.






----------+----------+---------+-----+-----------------+---+------------

@######### actgen @######## @## @####### @####### @## @#######

@######### @####### @######## @## @####### @####### @## @#######

@######### @####### @######## @## @####### @####### @## @#######


The entry in the 1st line of the column GENERATION is the name of the muti-

lated 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.


Mount and load the tape for saving the mutilated generation.


33 Initialize save tape of the mutilated generation.b INIT MT:MTD=00,CD=EBC,DENS=6250,VSN=GE1TAP;


: : : :

: : : :














EY190- 12 A30808-X3074-A473-2-7620


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).

b COPY GEN:OUTPUT=GEN,VERIFY=NO,VSN=GE1TAP,GEN=actgen,REWIN

D=YES;command repetition ACCEPTED

: : : :

: : : :

Was continuation tape handling requested by the system? Y h...36N h...35















A30808-X3074-A473-2-7620 EY190 - 13


35 Tape saving the mutilated generation. : : : :

: : : :


b REWIND MT:MTD=00;command repetition EXEC’D

Rewind and remove save tape.

The tape is to be marked as a mutilated generation save tape and sent to the

diagnostic center.

After that continue h...38

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.A large magnetic tape with write ring, overwritable or empty, is to be used.

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: : : : :

: : : :






diagnostic center.














EY190- 14 A30808-X3074-A473-2-7620


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).

b CAN GEN:GEN=actgen;DANGEROUS COMMAND CANGEN READY TO EXECUTE<





----------+----------+---------+-----+-----------------+---+------------

@######### actgen @######## @## @####### @####### @## @#######

@######### @####### @######## @## @####### @####### @## @#######

@######### @####### @######## @## @####### @####### @## @#######



b +LIST OF ERASED FILES OF THE FORMER GENERATION : actgen

FILE:

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

@################


Depending on the history of the generation, which is to be cancelled, the

number of erased files, listed above, varies.




Interrogation of configuration is to be executed.



: : : :

: : : :























A30808-X3074-A473-2-7620 EY190 - 15


41 Restore the desired configuration.

Was the requested configuration achieved?

– 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


APS quarterly saving is to be executed according to procedure SW210.

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

i ...MMN:SW,PROC, SW210



43 Execution of procedure SW231.Symptom saving is to be executed according to procedure SW231.





44 Decision.

Are individual call data administered in the network node? Y h...45

N h...46


Saving of individual call data is to be executed according to procedure SW224.

Continue here, after execution of: MMN:SW, procedure SW224




46 Decision.


N h...50




b INIT MT:MTD=00,CD=EBC,DENS=6250,VSN=LOGTAP;command repetition ACCEPTED

: : : :

: : : :


















EY190- 16 A30808-X3074-A473-2-7620



Meter routine saving is to be done.

Important note :







: : : :

: : : :




Important note :






PER=YES; ......MMN:SW,

TAB, METAP



device.





routine saving is to be restarted).

50 Decision.

Have PATCHES been incorporated in the APS since the time when the last APS

routine- or quarterly saving was carried out? Y h...51

N h...52

























A30808-X3074-A473-2-7620 EY190 - 17


51 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.


At this point the procedure is finished.

END



EY190- 18 A30808-X3074-A473-2-7620




A30808-X3074-A473-2-7620 EY191 - 1



EY191


This procedure describes the restoration of switching operation using the GOLDEN

GENERATION, which is stored in duplicate on background memories.



•

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






1 List generations.


NAME OF CURRENT GENERATION: oldgold



----------+----------+---------+-----+-----------------+---+------------

@######### actgen VALID @## @####### @####### @## @#######

@######### backgen VALID @## @####### @####### @## @#######

BACKUP oldgold VALID @## @####### @####### @## @#######


! If there is a generation fallback in a HLR, it must be safeguarded that the authentificationkey of the fallback generation is identical to the authentification key which is loaded in

the IOP:AUC module.



TS-011.








EY191- 2 A30808-X3074-A473-2-7620


2 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 genera-

tion, 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)

b MERGE GEN:GENTASKL=oldgold,GENSEMIL=actgen;command repetition ACCEPTED

: : : :

: : : :







A30808-X3074-A473-2-7620 EY191 - 3


4 List generations.





----------+----------+---------+-----+-----------------+---+------------

@######### actgen VALID @## @####### @####### @## @#######

@######### backgen VALID @## @####### @####### @## @#######

@######### oldgold VALID @## @####### @####### @## @#######

MERGED merggen1 BLOCKED @## @####### @####### @## @#######



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).

b MERGE GEN:GENTASKL=oldgold,GENSEMIL=backgen;command repetition ACCEPTED

: : : :

: : : :


6 List generations.





----------+----------+---------+-----+-----------------+---+------------

@######### actgen VALID @## @####### @####### @## @#######

@######### backgen VALID @## @####### @####### @## @#######

@######### oldgold VALID @## @####### @####### @## @#######



















EY191- 4 A30808-X3074-A473-2-7620


7 Set CP SPLIT mode operation.


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).

b DISP SPLITOPT;command repetition EXEC’D

STATUS OF FLAG SPLITOPT: @#########

Is the APS change flag in the status RESET? Y h...10

N h...9


b RSET SPLITOPT;DANGEROUS COMMAND RSETSPLITOPT READY TO EXECUTE<

b ;STATUS OF FLAG SPLITOPT: RESET



Are all prerequisites for the CP SPLIT met? Y h...12N h...11

!

ATTENTION:

All commands in this block must be entered at a DCP (OMC); this means thata session with the corresponding exchange must be set up.


















A30808-X3074-A473-2-7620 EY191 - 5


11 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. h...31


b SPLIT SSP:TEST=NO;DANGEROUS COMMAND SPLITSSP READY TO EXECUTE<


Has CP SPLIT mode operation been started successfully? Y h...14

N h...13

13 SPLIT mode operation could not be set.

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.

h...31

14 Interrogation of the system status.


15 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).

!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












EY191- 6 A30808-X3074-A473-2-7620



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 @##### @#####





b ;







b MAN;



A30808-X3074-A473-2-7620 EY191 - 7


18 Manual bootstrap - initiate manual recovery.IOC-0 MDD : BZS/AKD AND GENERATION-LIST

@#############

actgen @#######################backgen @#######################

oldgold @#######################

merggen2 @#######################

merggen1 @#######################

MANUAL RECOV: - LOADING VIA IOC : “IOC-0;/IOC-1;”


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.

b merggen1;MANUAL RECOVERY - LTG LOADING : “Y;/N;”

b N;



EY191- 8 A30808-X3074-A473-2-7620



: : : :

MDD-1 : INOPERABLE AND THEREFORE DEACTIVATED.

ALL FILES ON OTHER DISK AVAILABLE.

: : : :

: : : :

FCP RECOVERY REPORT


-------+----+-----------

MDD-00 ACT YES

MDD-01 NAC NO


---------+------------------+------------

merggen1 @####### @####### @##

: : : :

: : : :

FCP UPDATE REPORT


JOBNO= @###



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

@################ @####### : : : :

: : : :






is executed.



21 Displaying system status.


h...22












A30808-X3074-A473-2-7620 EY191 - 9


22 Decision.

Was the start-up test successful? Y h...EMCYMN,

PROC, EY192N 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).


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 @##### @#####





b ;







b MAN;







EY191- 10 A30808-X3074-A473-2-7620



@#############

actgen @#######################backgen @#######################

oldgold @#######################

merggen2 @#######################

merggen1 @#######################




(2nd variant: merggen2) is to be taken over.


b merggen2;MANUAL RECOVERY - LTG LOADING : “Y;/N;”

b N;



A30808-X3074-A473-2-7620 EY191 - 11



: : : :



: : : :

: : : :

FCP RECOVERY REPORT


-------+----+-----------

MDD-00 ACT YES

MDD-01 NAC NO


---------+------------------+------------

merggen2 @####### @####### @##

: : : :

: : : :

FCP UPDATE REPORT


JOBNO= @###



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

@################ @####### : : : :

: : : :






is executed.





h...30












EY191- 12 A30808-X3074-A473-2-7620


30 Decision.

Was the start-up test successful? Y h...EMCYMN,

PROC, EY193N h...EMCYMN,

PROC, EY194



END











A30808-X3074-A473-2-7620 EY192 - 1



EY192

3.8.1 General information





•



















the IOP:AUC module.



TS-011.



EY192- 2 A30808-X3074-A473-2-7620


1 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.

2 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 @##### @#####





b FOR;IPL113: ENTER PARAMS




b ;



A30808-X3074-A473-2-7620 EY192 - 3







b MAN;


@#############

actgen @#######################

backgen @#######################

oldgold @#######################

merggen2 @#######################

merggen1 @#######################




(1st variant:merggen1) is to be taken over.


b merggen1;

MANUAL RECOVERY - LTG LOADING : “Y;/N;”

b Y;



EY192- 4 A30808-X3074-A473-2-7620



: : : :



: : : :

: : : :

FCP RECOVERY REPORT


-------+----+-----------

MDD-00 ACT YES

MDD-01 NAC NO


---------+------------------+------------

merggen1 @####### @####### @##

: : : :

: : : :

FCP UPDATE REPORT


JOBNO= @###



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

@################ @####### : : : :

: : : :


faulty. ......General infor-mation




is executed.





h...9












A30808-X3074-A473-2-7620 EY192 - 5


9 Decision.


N h...49




ALTYPE = @#######################

PABCAUSE= @#################################################

ALARM-ID: @#############################################################

: : : :

: : : :

OBJECT = RECOV ALPRIO = MAJOR ALSTAT = NP MSGNO = @####

ALTYPE = @#######################

PABCAUSE= @#################################################


: : : :

: : : :


ALTYPE = @#######################

PABCAUSE= @#################################################

ALARM-ID: @#############################################################


11 Delete alarm.

This block is to be executed with all message numbers of category

ALPRIO=MAJOR which are assigned to an ISTART message.














EY192- 6 A30808-X3074-A473-2-7620




NAME OF CURRENT GENERATION: merggen1



----------+----------+---------+-----+-----------------+---+------------

@######### actgen VALID @## @####### @####### @## @#######

@######### backgen VALID @## @####### @####### @## @#######

@######### oldgold VALID @## @####### @####### @## @#######




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.

b MOD GEN:GEN=merggen1,VALIDITY=VALID;command repetition EXEC’D






----------+----------+---------+-----+-----------------+---+------------

@######### actgen VALID @## @####### @####### @## @#######

@######### backgen VALID @## @####### @####### @## @#######

@######### oldgold VALID @## @####### @####### @## @#######


MERGED merggen1 VALID @## @####### @####### @## @#######

















A30808-X3074-A473-2-7620 EY192 - 7


15 Information.



following cases:











STATISTIC CHARGING

16 Decision.

Are statistic meters administered in the network node? Y h...17N h...18



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:

b CONF BAP:BAP=0,OST=MBL;


b CONF BAP:BAP=0,OST=SPR;DANGEROUS COMMAND !

DO YOU WANT COMMAND TO BE EXECUTED ? (YES: +/NO: -) <

b +command repetition ACCEPTED

: : : :

: : : :














EY192- 8 A30808-X3074-A473-2-7620







----------+----------+---------+-----+-----------------+---+------------

@######### actgen VALID @## @####### @####### @## @#######

@######### backgen VALID @## @####### @####### @## @#######

@######### oldgold VALID @## @####### @####### @## @#######




The entry in the 1st line of the column “GENERATION” is the name of the muti-

lated generation actgen , i.e. the generation which was active before the fall-

back.

Important:

The value of actgen should be written down since it is needed in the following to

complete MML commands.




21 Initialize save tape of the mutilated generation.

b INIT MT:MTD=00,CD=EBC,DENS=6250,VSN=GE1TAP;command repetition ACCEPTED

: : : :

: : : :











A30808-X3074-A473-2-7620 EY192 - 9



Important note :





REWIND = YES ;

PLEASE MOUNT CONTINUATION TAPE TO VSN = @#####









last generation list printout, is to be used in the following command ( GEN =actgen).



: : : :

: : : :
















EY192- 10 A30808-X3074-A473-2-7620



: : : :





diagnostic center.

h...26

24 Mutilated generation saving - continuation tape handling.

Each time, the messages


REWIND = YES ;





sent to the diagnostic center.2. Mount and load a tape for mutilated generation saving.




(y=2, 3, .....,n)




: : : :






diagnostic center.



















A30808-X3074-A473-2-7620 EY192 - 11







----------+----------+---------+-----+-----------------+---+------------

@######### actgen VALID @## @####### @####### @## @#######

@######### backgen VALID @## @####### @####### @## @#######

@######### oldgold VALID @## @####### @####### @## @#######











EY192- 12 A30808-X3074-A473-2-7620


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 genera-

tion list printout, is to be used for the parameter GEN in the following command.

b CAN GEN:GEN=generation;DANGEROUS COMMAND CANGEN READY TO EXECUTE<





----------+----------+---------+-----+-----------------+---+------------

@######### actgen VALID @## @####### @####### @## @#######

@######### backgen VALID @## @####### @####### @## @#######

@######### oldgold VALID @## @####### @####### @## @#######





b +LIST OF ERASED FILES OF THE FORMER GENERATION : @#######

FILE:

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

@################




!This block is to be executed for all generations, except the current generation

merggen1.












A30808-X3074-A473-2-7620 EY192 - 13


28 Activation of the second disk.

The disk which was switched off during the system start with the tested genera-

tion is switched on, initialized and configured.

Switch on power for MDD-1.

Configuration of MDD-1:

b CONF MDD:MDD=1,OST=MBL;command repetition EXEC’D

Initialization of MDD-1:

b INIT MD:MDD=1;command repetition EXEC’D


b CONF MDD:MDD=1,OST=ACT;command repetition EXEC’D

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: ALL DOUBLE FILES SYNCHRONIZED







: : : :

: : : :command repetition FINISHED



























EY192- 14 A30808-X3074-A473-2-7620










The save tape for the current quarter is to be used.

(Large tape with write ring.)

34 Tape saving of the latest LOG file.

b TRANS FILE:FILE=LG.,VSNR=LOGTAP,COPMOD=SSWF;command repetition EXEC’D




The tape is to be marked as APS routine save tape Ax and to be stored in tape

group A under date of save.













A30808-X3074-A473-2-7620 EY192 - 15


36 Delete the latest LOG file.

b DISP FILE:FILE=LG.;command repetition EXEC’D

b DACT FNS:FNS=LG;DANGEROUS COMMAND DACTFNS READY TO EXECUTE<


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 ;.

b MOD FILEAUT:AR=NOAR,FILE=name;DANGEROUS COMMAND MODFILEAUT READY TO EXECUTE<


b DEL FILE:FILE=name;command repetition EXEC’D

b ACT FNS:FNS=LG.;DANGEROUS COMMAND ACTFNS READY TO EXECUTE<


37 Activate LOG function.

b SET LOG:FILE=LOG6,SIZE=24,ERASE=Y;DANGEROUS COMMAND SETLOG READY TO EXECUTE<







----------+----------+---------+-----+-----------------+---+------------































EY192- 16 A30808-X3074-A473-2-7620




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










41 Decision.

Are individual call data administered? Y h...42

N h...43







43 Decision.


N h...47




b INIT MT:MTD=00,CD=EBC,DENS=6250,VSN=LOGTAP;command repetition ACCEPTED

: : : :

: : : :command repetition EXEC’D

















A30808-X3074-A473-2-7620 EY192 - 17




Important note :


administered meter saving.





: : : :

: : : :




Important note :






PER=YES; ......MMN:SW,

TAB, METAP



device.






47 Decision.


routine- or quarterly saving was carried out? Y h...48

N h...62























EY192- 18 A30808-X3074-A473-2-7620


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.



A30808-X3074-A473-2-7620 EY192 - 19



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 @##### @#####









b ;





TO STOP INITIAL START : “STOP;”TO START APS AUTOMATICALLY : “;ETX”

b MAN;



EY192- 20 A30808-X3074-A473-2-7620



@#############

actgen @#######################backgen @#######################

oldgold @#######################

merggen2 @#######################

merggen1 @#######################



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.

b oldgold;MANUAL RECOVERY - LTG LOADING : “Y;/N;”

b Y;



A30808-X3074-A473-2-7620 EY192 - 21



: : : :



: : : :

: : : :

FCP RECOVERY REPORT


-------+----+-----------

MDD-00 NAC NO

MDD-01 ACT YES


---------+------------------+------------

oldgold @####### @####### @##

: : : :

: : : :

FCP UPDATE REPORT


JOBNO= @###



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

@################ @####### : : : :

: : : :






is executed.





h...57












EY192- 22 A30808-X3074-A473-2-7620









BAP-0, which was switched off before the recovery attempt with the tested

generation merggenx was carried out, is switched on again and configured.



b CONF BAP:BAP=0,OST=MBL;command repetition EXEC’D




: : : :

: : : :
















A30808-X3074-A473-2-7620 EY192 - 23





ALTYPE = @#######################

PABCAUSE= @#################################################

ALARM-ID: @#############################################################

: : : :

: : : :


ALTYPE = @#######################

PABCAUSE= @#################################################

ALARM-ID: CLASS=ISTART : : : :

: : : :


ALTYPE = @#######################

PABCAUSE= @#################################################

ALARM-ID: @#############################################################


60 Delete alarm.

This block is to be executed with all message numbers of category ALPRIO=MAJOR which are assigned to an ISTART message.


61 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.

......EMCYMN,PROC, EY194

















EY192- 24 A30808-X3074-A473-2-7620




END



A30808-X3074-A473-2-7620 EY193 - 1



EY193

3.9.1 General information





•



















the IOP:AUC module.



TS-011.



EY193- 2 A30808-X3074-A473-2-7620


1 Preparation for recovery with the tested generation.

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



2 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 @##### @#####









b ;



A30808-X3074-A473-2-7620 EY193 - 3







b MAN;


@#############

actgen @#######################

backgen @#######################

oldgold @#######################

merggen2 @#######################

merggen1 @#######################




(2nd variant: merggen2) is to be taken over.


b merggen2;

MANUAL RECOVERY - LTG LOADING : “Y;/N;”

b Y;



EY193- 4 A30808-X3074-A473-2-7620



: : : :



: : : :

: : : :

FCP RECOVERY REPORT


-------+----+-----------

MDD-00 ACT YES

MDD-01 NAC NO


---------+------------------+------------

merggen2 @####### @####### @##

: : : :

: : : :

FCP UPDATE REPORT


JOBNO= @###



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

@################ @####### : : : :

: : : :






is executed.





h...9












A30808-X3074-A473-2-7620 EY193 - 5


9 Decision.


N h...50




ALTYPE = @#######################

PABCAUSE= @#################################################

ALARM-ID: @#############################################################

: : : :

: : : :


ALTYPE = @#######################

PABCAUSE= @#################################################


: : : :

: : : :


ALTYPE = @#######################

PABCAUSE= @#################################################

ALARM-ID: @#############################################################


11 Delete alarm.

This block is to be executed with all message numbers of category

ALPRIO=MAJOR which are assigned to an ISTART message.














EY193- 6 A30808-X3074-A473-2-7620







----------+----------+---------+-----+-----------------+---+------------

@######### actgen VALID @## @####### @####### @## @#######

@######### backgen VALID @## @####### @####### @## @#######

@######### oldgold VALID @## @####### @####### @## @#######




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.

b MOD GEN:GEN=merggen2,VALIDITY=VALID;command repetition EXEC’D






----------+----------+---------+-----+-----------------+---+------------

@######### actgen VALID @## @####### @####### @## @#######

@######### backgen VALID @## @####### @####### @## @#######

@######### oldgold VALID @## @####### @####### @## @#######























A30808-X3074-A473-2-7620 EY193 - 7











regeneration of LOG data is avoided.b ACT IAOPT:BLBUFR=ADMREC;

DANGEROUS COMMAND ACTIAOPT READY TO EXECUTE<



Regeneration of LOG files is to be executed.

b EXEC CMDFILE:FILE=CG.SA.REC91;

......MMN:SW,TAB, REC91


: : : :

: : : :




records was suppressed. This suppression is canceled again using the

following command.





















EY193- 8 A30808-X3074-A473-2-7620


20 Information.



following cases:











STATISTIC CHARGING

21 Decision.


22 Information.

During account suspension no begin and end meter readings are displayed




: : : :

: : : :




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

date of save.








A30808-X3074-A473-2-7620 EY193 - 9



BAP-0, which was switched off before the start-up test was carried out, is

switched on again and configured.







: : : :

: : : :







----------+----------+---------+-----+-----------------+---+------------

@######### actgen VALID @## @####### @####### @## @#######

@######### backgen VALID @## @####### @####### @## @#######

@######### oldgold VALID @## @####### @####### @## @#######





lated generation actgen , i.e. the generation which was active before the fallback.

Important:





















EY193- 10 A30808-X3074-A473-2-7620




: : : :

: : : :



Important note :

The number and size of the files which are to be transferred to magnetic tape

may require one or several continuation tapes.




REWIND = YES ;










last generation list printout, is to be used in the following command

( GEN =actgen).



: : : :

: : : :

Was continuation tape handling requested by the system? Y h...31

N h...30

















A30808-X3074-A473-2-7620 EY193 - 11



: : : :





diagnostic center.

h...33




REWIND = YES ;









(y=2, 3, .....,n)




: : : :






diagnostic center.



















EY193- 12 A30808-X3074-A473-2-7620







----------+----------+---------+-----+-----------------+---+------------

@######### actgen VALID @## @####### @####### @## @#######

@######### backgen VALID @## @####### @####### @## @#######

@######### oldgold VALID @## @####### @####### @## @#######











A30808-X3074-A473-2-7620 EY193 - 13



Important


exception of the current generation merggen2 , are to be cancelled, i.e. the


cancelled.



b CAN GEN:GEN=generation;DANGEROUS COMMAND CANGEN READY TO EXECUTE<





----------+----------+---------+-----+-----------------+---+------------

@######### actgen VALID @## @####### @####### @## @#######

@######### backgen VALID @## @####### @####### @## @#######

@######### oldgold VALID @## @####### @####### @## @#######






FILE:

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

@################





merggen2.












EY193- 14 A30808-X3074-A473-2-7620



The disk which was switched off during the system start with the tested genera-

tion is switched on, initialized and configured.

















: : : :





























A30808-X3074-A473-2-7620 EY193 - 15







----------+----------+---------+-----+-----------------+---+------------






i ...MMN:SW,

PROC, SW210









42 Decision.

Are individual call data administered in the exchange? Y h...43N h...44







44 Decision.





















EY193- 16 A30808-X3074-A473-2-7620




A large magnetic tape with write ring, overwritable or empty, is to be used.b INIT MT:MTD=00,CD=EBC,DENS=6250,VSN=LOGTAP;


: : : :

: : : :




Important note :

The starting time of the command file must not be within a time interval of the administered meter saving.





: : : :

: : : :




Important note :






PER=YES;

......MMN:SW,

TAB, METAP



device.
































A30808-X3074-A473-2-7620 EY193 - 17


48 Decision.


routine- or quarterly saving was carried out? Y h...49N h...63

49 Patch treatment.

Important




h...63

50 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





EY193- 18 A30808-X3074-A473-2-7620



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 @##### @#####









b ;





TO STOP INITIAL START : “STOP;”TO START APS AUTOMATICALLY : “;ETX”

b MAN;



A30808-X3074-A473-2-7620 EY193 - 19



@#############

actgen @#######################backgen @#######################

oldgold @#######################

merggen2 @#######################

merggen1 @#######################



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.

b oldgold;MANUAL RECOVERY - LTG LOADING : “Y;/N;”

b Y;



EY193- 20 A30808-X3074-A473-2-7620



: : : :



: : : :

: : : :

FCP RECOVERY REPORT


-------+----+-----------

MDD-00 NAC NO

MDD-01 ACT YES


---------+------------------+------------

oldgold @####### @####### @##

: : : :

: : : :

FCP UPDATE REPORT


JOBNO= @###



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

@################ @####### : : : :

: : : :






is executed.





h...58












A30808-X3074-A473-2-7620 EY193 - 21









BAP-0, which was switched off before the recovery attempt with the tested

generation merggenx was carried out, is switched on again and configured.







: : : :

: : : :
















EY193- 22 A30808-X3074-A473-2-7620





ALTYPE = @#######################

PABCAUSE= @#################################################

ALARM-ID: @#############################################################

: : : :

: : : :


ALTYPE = @#######################

PABCAUSE= @#################################################

ALARM-ID: CLASS=ISTART : : : :

: : : :


ALTYPE = @#######################

PABCAUSE= @#################################################

ALARM-ID: @#############################################################


61 Delete alarm.

This block is to be executed with all message numbers of category ALPRIO=MAJOR which are assigned to an ISTART message.


62 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.

......EMCYMN,PROC, EY194

















A30808-X3074-A473-2-7620 EY193 - 23




END



EY193- 24 A30808-X3074-A473-2-7620




A30808-X3074-A473-2-7620 EY194 - 1



EY194






•


















1 Decision.

Was this procedure called by procedure EY191? Y h...2

N h...5

2 Preparation for merging the two system halves.






EY194- 2 A30808-X3074-A473-2-7620


3 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.


b MERGE SSP:DIAG=NO;command repetition EXEC’D







5 Renaming the active LOG file.

The active LOG file is renamed by copying the file first and deleting the source file afterwards.

b TRANS FILE:FILE=TEMP./LG.;command repetition EXEC’D

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.

b MOD FILEAUT:AR=NOAR,FILE=LG.name.Ax;DANGEROUS COMMAND MODFILEAUT READY TO EXECUTE<


b DEL FILE:FILE=LG.;command repetition EXEC’D


























A30808-X3074-A473-2-7620 EY194 - 3


6 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.b DACT FNS:FNS=LG;

DANGEROUS COMMAND DACTFNS READY TO EXECUTE<


b TRANS FILE:FILE=LG.,VSNS=LOGTAP;command repetition ACCEPTED

: : : :

: : : :


SENDER : @#######RECEIVER : @#######

START START



-+-----------------+------+-----+-+-----+-+--+----+---------+-----+-----

@ @################ @##### @#### @ @#### @ @# @### @######## @#### @####

@ @################ @##### @#### @ @#### @ @# @### @######## @#### @####

b ACT FNS:FNS=LG;DANGEROUS COMMAND ACTFNS READY TO EXECUTE< READY TO EXECUTE<




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

date of save.




regeneration of LOG data is avoided.b ACT IAOPT:BLBUFR=ADMREC;

DANGEROUS COMMAND ACTIAOPT READY TO EXECUTE<

















EY194- 4 A30808-X3074-A473-2-7620


9 Decision.

Which routine saving was carried out at latest?

– The first routine saving was the latest, which was carried out. h...10 – The second routine saving was the latest, which was carried out. h...11 – The third routine saving was the latest, which was carried out. h...12 – The fourth routine saving was the latest, which was carried out. h...13 – The fifth routine saving was the latest, which was carried out. h...14



A30808-X3074-A473-2-7620 EY194 - 5


10 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.

b EXEC CMDFILE:FILE=LG.LOG1.A0;command repetition STARTED

: : : :

: : : :


b DEL FILE:FILE=LG.;command repetition ACCEPTED

FILE

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

@################

ERASE ALL FILES LISTED ?

ENTER (YES: + /NO: -) <

b +command repetition EXEC’D

Activate LOG function.

b SET LOG:FILE=LOG6,SIZE=24,ERASE=YES;DANGEROUS COMMAND SETLOG READY TO EXECUTE<


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 immedi-

ately after TEMP.LOG2.A1.

b EXEC CMDFILE:FILE=TEMP.LOG2.A1;command repetition STARTED

: : : :

: : : :


h...15


















EY194- 6 A30808-X3074-A473-2-7620



Updating the database is done by starting the LOG files LG.LOG1.A0 and

LG.LOG2.A0.

Important :




: : : :

: : : :



: : : :

: : : :



FILE

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

@################








entry.

Important :





: : : :

: : : :


h...15

























A30808-X3074-A473-2-7620 EY194 - 7



Updating the database is done by starting the LOG files LG.LOG1.A0,

LG.LOG2.A0 and LG.LOG3.A0.

Important :




: : : :

: : : :



: : : :

: : : :



: : : :

: : : :


b DEL FILE:FILE=LG.;


FILE

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

@################








entry.

Important :
























EY194- 8 A30808-X3074-A473-2-7620



: : : :

: : : :

command repetition FINISHEDh...15







A30808-X3074-A473-2-7620 EY194 - 9




LG.LOG2.A0, LG.LOG3.A0 and LG.LOG4.A0.

Important :




: : : :

: : : :



: : : :

: : : :



: : : :

: : : :


b EXEC CMDFILE:FILE=LG.LOG4.A0;

command repetition STARTED : : : :

: : : :



FILE

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

@################






























EY194- 10 A30808-X3074-A473-2-7620



entry.

Important :

If due to an overflow of the file LG.LOG5.A1 further files LG.LOG5.Ay were created and renamed to TEMP.LOG5.Ay, these files must be started immedi-



: : : :

: : : :


h...15







A30808-X3074-A473-2-7620 EY194 - 11




LG.LOG2.A0, LG.LOG3.A0, LG.LOG4.A0 and LG.LOG5.A0.

Important :




: : : :

: : : :



: : : :

: : : :



: : : :

: : : :


b EXEC CMDFILE:FILE=LG.LOG4.A0;

command repetition STARTED : : : :

: : : :



: : : :

: : : :



FILE

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

@################
































EY194- 12 A30808-X3074-A473-2-7620



Update the database by starting the LOG file TEMP.LOG6.A1 or by manual entry.

Important :





: : : :

: : : :


h...15

15 Delete old LOG files.

b DEL FILE:FILE=TEMP.;command repetition ACCEPTED

FILE

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

@################



b +


Updating database is finished.



records was suppressed. This suppression is canceled again using the following

command.

b CAN IAOPT:BLBUFR=ADMREC;

DANGEROUS COMMAND CANIAOPT READY TO EXECUTE<


















A30808-X3074-A473-2-7620 EY194 - 13


17 Information.



following cases:











STATISTIC CHARGING

18 Decision.


19 Information.

During account suspension no begin and end meter readings are displayed




: : : :

: : : :









EY194- 14 A30808-X3074-A473-2-7620







----------+----------+---------+-----+-----------------+---+------------

@######### actgen VALID @## @####### @####### @## @#######

@######### backgen VALID @## @####### @####### @## @#######

@######### oldgold VALID @## @####### @####### @## @#######





lated generation actgen , i.e. the generation which was active before the fall-

back.

Important:








: : : :

: : : :











A30808-X3074-A473-2-7620 EY194 - 15



Important note :





REWIND = YES ;










last generation list printout, is to be used in the following command ( GEN =actgen).



: : : :

: : : :
















EY194- 16 A30808-X3074-A473-2-7620



: : : :





diagnostic center.

h...28




REWIND = YES ;









(y=2, 3, .....,n)




: : : :






diagnostic center.



















A30808-X3074-A473-2-7620 EY194 - 17







----------+----------+---------+-----+-----------------+---+------------

@######### actgen VALID @## @####### @####### @## @#######

@######### backgen VALID @## @####### @####### @## @#######

@######### oldgold VALID @## @####### @####### @## @#######











EY194- 18 A30808-X3074-A473-2-7620



Important


exception of the current generation oldgold , are to be cancelled, i.e. the


cancelled.



b CAN GEN:GEN=generation;DANGEROUS COMMAND CANGEN READY TO EXECUTE< READY TO EXECUTE<





----------+----------+---------+-----+-----------------+---+------------

@######### actgen VALID @## @####### @####### @## @#######

@######### backgen VALID @## @####### @####### @## @#######

@######### oldgold VALID @## @####### @####### @## @#######






FILE:

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

@################





oldgold.












A30808-X3074-A473-2-7620 EY194 - 19



The disk which was switched off in a former procedure step is switched on,

initialized and configured.

















: : : :




























EY194- 20 A30808-X3074-A473-2-7620







----------+----------+---------+-----+-----------------+---+------------

@######### oldgold VALID @## @####### @####### @## @#######





i....MMN:SW,

PROC, SW210









37 Decision.

Are individual call data administered in the exchange? Y h...38N h...39







39 Decision.





















A30808-X3074-A473-2-7620 EY194 - 21




A large magnetic tape with write ring, overwritable or empty, is to be used.b INIT MT:MTD=00,CD=EBC,DENS=6250,VSN=LOGTAP;


: : : :

: : : :




Important note :

The starting time of the command file must not be within a time interval of the administered meter saving.





: : : :

: : : :




Important note :






PER=YES;

......MMN:SW,

TAB, METAP



device.






























EY194- 22 A30808-X3074-A473-2-7620


43 Decision.


routine- or quarterly saving was carried out? Y h...44N h...45

44 Patch treatment.

Important






END



A30808-X3074-A473-2-7620 EY350 - 1


3.11 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.

The combination of EY350 and EY370 may also be used, if a recovery from the back-

ground 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:

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.

Emergency situation ShutdownReturn to normal

operation

Overheating / Partial Shutdown EY350 EY360

Overheating / Total Shutdown EY350 EY370

Power failure Initiated by the

power failure

EY380

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.)



EY350- 2 A30808-X3074-A473-2-7620


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.

Notes on the structure and preparation of the minimum configuration list are found in the

next section.

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.)



A30808-X3074-A473-2-7620 EY350 - 3


3.11.3 Notes on the preparation of the minimum configuration list

The DLUs assigned to the different subscribers should be labelled with the corre-

sponding 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:

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.

a) Listing the DLUs with the associated LTGs:Firstly a list of the DLUs with either the associated LTGs or with the associ-

ated 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).

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 !



EY350- 4 A30808-X3074-A473-2-7620


3.11.4 Minimum Configuration List (MCL)

DLUs with high priority Partial Shutdown PHASE 1

DLU LTG redundant LTG

destination with high priority

destination LTG redundant LTG

Partial Shutdown PHASE 3

DLUs with priority redundant LTG

destinations with priority

destination LTG redundant LTG

Partial Shutdown PHASE 2

DLUs without priority

DLU LTG redundant LTG

destinations without priority redundant LTG

destination LTG

Tab. 3.11.2 Example of a minimum configuration list (MCL)



A30808-X3074-A473-2-7620 EY350 - 5


1 Entry criteria.

What kind of procedure run is to be done?

– Procedure run after temperature rise h...2 – Procedure run after unsuccessful recovery (EY100) h...47

2 Temperature rise

Detecting the following emergency situation:

• 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 !

3 Improve ventilation.

Open all doors of the racks to improve ventilation if this has not already been

done!

4 Identify the name of the current generation.


NAME OF CURRENT GENERATION: actgen



----------+----------+---------+-----+-----------------+---+------------

@######### @####### @######## @## @####### @####### @## @#######

@######### @####### @######## @## @####### @####### @## @#######

@######### @####### @######## @## @####### @####### @## @#######


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).

i

The decision for a PARTIAL or TOTAL SHUTDOWN must be made in order to

prevent a further rise in temperature !








EY350- 6 A30808-X3074-A473-2-7620


5 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.



b STAT MB;








6 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 trans-

ferred from the main memory to the corresponding files in the background

memories.

b DISP FILE:FILE=CA.;

Are data for display available? Y h...7

N h...9

































A30808-X3074-A473-2-7620 EY350 - 7


7 CA files available.command repetition EXEC’D

@################## @#############################USED SPACE : @###### PAGES FOR @### FILES


-----------------+--------+------+-------------+-------------+-----+----

CA.ST.UCHA @####### @##### @############ @############ @### @### h...8

8 Save charge and statistic meters.

b SAVE MET;command repetition ACCEPTED

: : : :

: : : :


h...10

9 No CA files available.command repetition EXEC’D


10 Intermediate metersaving - IA files.

b DISP FILE:FILE=IA.;

Are data for display available? Y h...11

N h...1311 IA files available.


@################## @#############################



-----------------+--------+------+-------------+-------------+-----+----

----------

IA.ICAMA @####### @##### @############ @############ @### @###

IA.ICINA @####### @##### @############ @############ @### @###

IA.ICITR @####### @##### @############ @############ @### @###IA.ICMCR @####### @##### @############ @############ @### @###

IA.ICMIR @####### @##### @############ @############ @### @###

IA.ICOME @####### @##### @############ @############ @### @###

----------

Remark:
















EY350- 8 A30808-X3074-A473-2-7620


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):

b TRANS BUFFER:TYPE=type;command repetition EXEC’D

h...14

13 No IA files available.command repetition EXEC’D


14 Display IARSTAT measurement jobs.

b DISP IARJOB;Are data for display available? Y h...15

N h...17

15 IR files available.command repetition EXEC’D

IARSTAT MEASUREMENT-JOBS

MTYPE BEG TER JOBNO STATUS FILENAME

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

IARSTATx @#######@@# @#######@@# @### @######### IR.Aryymmnn

: : : :

: : : :

h...16

16 Saving IR files to disk.

b COPY IARACCT:MTYPE=IARSTATx;command repetition EXEC’D

h...18

17 No IR files available.command repetition EXEC’D


IA filename parameter <type>

IA.ICAMA AMA

IA.ICINA INA

IA.ICITR ITR

IA.ICMCR MCR

IA.ICMIR MIR

IA.ICOME OME





















A30808-X3074-A473-2-7620 EY350 - 9


18 Saving history data (SG files) to disk:

b DMP SGMSG;NO OF STORED SAFEGUARDING MESSAGES TO WRITE INTO SG.OPER FILE: @###


: : : :

: : : :


19 Decision block.

Which type of shutdown is to be carried out?

– TOTAL SHUTDOWN is to be carried out: h...46 – PARTIAL SHUTDOWN is to be carried out: h...20

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 config-

ured to MBL and switched off.

b CONF MDD:MDD=1,OST=MBL;DANGEROUS COMMAND !


+command repetition EXEC’D

22 PARTIAL SHUTDOWN of periphery according to MCL: PHASE 1.

Redundancy check of LTGs:


NO: LTG CH0 CH1 NO: LTG CH0 CH1 NO: LTG CH0 CH1 NO: LTG CH0 CH1

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

no. ost ost ost @### @## @## @## @### @## @## @## @### @## @## @##

@### @## @## @## @### @## @## @## @### @## @## @## @### @## @## @##

: : : :

: : : :

The status list should be evaluated in the following way:

Switch off the power supply to MDD-1.


















EY350- 10 A30808-X3074-A473-2-7620


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.

23 PARTIAL SHUTDOWN of switching network.

In order to reduce thermal stress, the following peripheral units should also be taken out of service:

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:

b STAT SN;


TSG SSG TSG SSG

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

0-a ost 0-a ost 1-a ost 1-a ost

@## @## @## @## @## @## @## @##

The SN half in OST=STB (half-x) is configured to MBL:

b CONF SN:SN=x;OST=MBL;command repetition

STARTING CONFIGURATION FOR SN -x FROM STB TO MBL

END OF CONFIGURATION FOR SN -x FROM STB TO MBL



TSG SSG TSG SSG

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

0-a ost 0-a ost 1-a ost 1-a ost

@## @## @## @## @## @## @## @##

Switch off the power supplies of all redundant LTGs (see above)

Disconnect extra equipment (if present), i.e., equipment that is not

part of the installation.

Switch off the power supply to the TSGs and SSGs in OST=MBL.




















A30808-X3074-A473-2-7620 EY350 - 11


24 Partial Shutdown of the CP.

The given sequence must be followed !

b CONF IOC:IOC=1,OST=MBL;DANGEROUS COMMAND !



b CONF CMY:CMY=1,OST=MBL;DANGEROUS COMMAND !


b +


b CONF BCMY:BCMY=1,OST=MBL;DANGEROUS COMMAND !



CAPs (if present) :

The maximum amount of CAPs that may be configured to OST = MBL is depen-

dent 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:

b CONF CAP:CAP=x,OST=MBL;DANGEROUS COMMAND !



25 Check the status of the configured CP units:


UNIT OST UNIT OST UNIT OST

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

BAP-0 ost BAP-1 ost @######### @@##

: : : :

: : : :

Which type of coordination processor is used in the network node?

– CP113C is in use: h...26

– CP113D is in use: h...27




























EY350- 12 A30808-X3074-A473-2-7620


26 CP113C is in use.

Execute the following steps in the given sequence !

h...28

27 CP113D is in use

Execute the following steps in the given sequence !

h...28

28 Switch off BAP-SPARE

The BAP-x (OST=SPR) configured as SPARE should be identified from the CP

status list.

b CONF BAP:BAP=x,OST=MBL;DANGEROUS COMMAND !



29 Decision block.

PARTIAL SHUTDOWN according to MCL phase 1 is completed. After a reason-

able amount of time has passed, the following question must be answered:

Has PARTIAL SHUTDOWN phase 1 averted the danger of overheating? Y h...30

N h...31

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.

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.

Switch off the power supply to BAP-x (OST=MBL).








A30808-X3074-A473-2-7620 EY350 - 13


30 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-condi-

tioning must be fixed). A PARTIAL RESTART must then be executed according

to procedure EY360 !

h...52

31 Environmental temperature still rises.

Despite the measures already taken, the temperature in the network node

continues to rise.

Decision for PARTIAL SHUTDOWN phase 2 ! h...32

32 PARTIAL SHUTDOWN of periphery according to MCL, phase 2.

(Only DLU with priority or high priority remain connected!)

(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:

Has PARTIAL SHUTDOWN phase 2 averted the danger of overheating? Y h...34N h...35


Having implemented the measures for PARTIAL SHUTDOWN phase 2 , the

temperature in the network node has fallen, or at least does not rise further.

The cause for PARTIAL SHUTDOWN must be removed (e.g., the air-condi-

tioning must be fixed). A PARTIAL RESTART must then be executed according

to procedure EY360 !

h...52

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.

Switch off LTG:

1. Identify all LTG 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.



EY350- 14 A30808-X3074-A473-2-7620


35 Environmental temperature continues to rise.


continues to rise.Decision for PARTIAL SHUTDOWN phase 3 ! h...36

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:

Has PARTIAL SHUTDOWN phase 3 averted the danger of overheating? Y h...38

N h...39


Having implemented the measures for PARTIAL SHUTDOWN phase 3 , the

temperature in the network node has fallen, or at least does not rise further.

The cause for PARTIAL SHUTDOWN must be removed (e.g., the air-condi-

tioning must be fixed). A PARTIAL RESTART must then be executed accordingto procedure EY360 !

h...52

39 Environmental temperature continues to rise.


continues to rise.

Decision for TOTAL SHUTDOWN ! h...40

40 Announcing TOTAL SHUTDOWN.

Informing adjacent network nodes and subscribers with priority (e.g. hospitals,

emergency numbers) of TOTAL SHUTDOWN.



A30808-X3074-A473-2-7620 EY350 - 15


41 TOTAL SHUTDOWN after preceding PARTIAL SHUTDOWN:


– CP113C is in use: h...42 – CP113D is in use: h...43


Switch off power supplies to the following units in the given sequence !

*Also switch off IOC-2 and IOC-3, if present.

h...44

43 CP113D is in use.


*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.

h...44

Switch off power supply to BAP-MASTER (OST=MAS).

MDD-0

IOC-0 (including IOPs)*

BCMY-0

CMY-0

Switch off power supply to all CAPs that are still switched on.

MDD-0

IOC-0*

BCMY-0**

CMY-0

IOP frames

Switch off power supply to all CAPs that are still switched on.



EY350- 16 A30808-X3074-A473-2-7620


44 Switch off all peripheral units.

All peripheral units that have not yet been switched off should be discon-

nected in the following sequence by switching off the corresponding power

supplies:

45 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 !

h...52

46 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 unsuc-

cessful 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.

b CONF MDD:MDD=1,OST=MBL;DANGEROUS COMMAND !



!

The power supply to the CCG in the R:MB must not be switched off, as other-

wise 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 DLUs

all LTGs

CCNC

SSG

TSG

MB

SYP








A30808-X3074-A473-2-7620 EY350 - 17


Identify BAP-SPARE and BAP-MASTER:


UNIT OST UNIT OST UNIT OST

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

BAP-0 ost BAP-1 ost @######### @@##

: : : :

: : : :

Switch off units in the given sequence !


– CP113C is in use: h...48 – CP113D is in use: h...49


Switch off power supplies to all units of the specified type in the given sequence!

h...50

49 CP113D is in use.


*If present, the BCMY modules in R:CP113B should also be switched off by

disconnecting the corresponding voltage converter.

Switch off power supply to MDD-1.

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.

IOC (including IOPs)

BCMY

CMY

CAPs (if present)

IOC

BCMY*

CMY

IOP frames

CAPs (if present)








EY350- 18 A30808-X3074-A473-2-7620


50 TOTAL SHUTDOWN of periphery.

The peripheral units should be switched off frame by frame via the corre-

sponding power supplies in the following sequence !

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 !

h...52


END

!

The power supply to the CCG in the R:MB must not be switched off, as other-

wise much time must be spent on synchronization after restarting.

all DLUs

all LTGs

CCNC

SSG

TSG

MB

SYP

Disconnection of extra equipment that may be present (non EWSD).



A30808-X3074-A473-2-7620 EY360 - 1


3.12 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 neces-

sary 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.



EY360- 2 A30808-X3074-A473-2-7620


1 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.

2 Deciding on system start-up measures.

In what condition is the network node?

PARTIAL SHUTDOWN was executed; the network node is operating while

remaining partially switched off.

h...3

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.

h...EMCYMN,PROC, EY370

3 Switching on periphery.

The peripheral units that were taken out of service during PARTIAL SHUT-

DOWN are to be switched on again frame by frame via the corresponding power

supplies in the following sequence !

Switch on power supplies of:

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.

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: h...5 – CP113D is used: h...6

all DLUs

all LTGs

SSG

TSG

Switch on power supply to extra equipment (if present).







A30808-X3074-A473-2-7620 EY360 - 3


5 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 (MST-

LED) appears on each module.

h...7

6 CP113D is in use.

h...7

7 Activate peripheral units.

There exist two alternatives to put the peripheral units back to service:

– 1st alternative (manual configuration of peripheral units). If only a few units

are out of service this alternative should be preferred: h...8 – 2nd alternative (ISTART2R): h...9

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.

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.

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.



EY360- 4 A30808-X3074-A473-2-7620


8 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” .



b STAT MB;








h...15

9 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:

b RECOV SYSTEM:LEVEL=ISTART2R;DANGEROUS COMMAND RECOVSYSTEM READY TO EXECUTE<

;

































A30808-X3074-A473-2-7620 EY360 - 5


10 Recovery report.


FCP RECOVERY REPORT


-------+----+-----------

MDD-00 ACT YES

MDD-01 NAC NO


---------+------------------+------------

actgen @####### @####### @##


DATE : @#######@

TIME : @#######@

PERFORMED LEVEL : ISTART2R

PERFORMED ACTION(S) : @############################################

@##############################

APS GENERATION : actgen

FCP UPDATE REPORT


JOBNO= @###



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

@################ actgen




: : :

: : :















END OF LTG LOADING









EY360- 6 A30808-X3074-A473-2-7620


REASON : REQUIRED MML START

@#######################################

DATE : @#######@

TIME : @#######@UNIT : BAPM

REQUESTED LEVEL : ISTART2R

PERFORMED LEVEL : ISTART2R

PERFORMED ACTION(S) : @##############################################

@##############################






THRESHOLD : @###





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

@######## @######## @######## @######## @########

11 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 POST-

PROCESSING.

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.





A30808-X3074-A473-2-7620 EY360 - 7




and the password. After input of user identification and password the command is executed.



13 Determine CP status.


h...14

14 Determine system status of periphery.

The current system status is obtained by using the recovery report and the

following status enquiries:







b STAT DLU:DLU=X;
































EY360- 8 A30808-X3074-A473-2-7620


15 Restoring default configuration.

To create default configuration:

– Compare the current system status with the default configuration (seeEY350).

– Restore the default configuration; faults may have to be cleared.

– The order in which measures are taken to clear any faults must be deter-

mined 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 redun-

dancy 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.

b CONF BAP:BAP=x,OST=SPR;DANGEROUS COMMAND !



17 Return MDD-1 to service.


The copying from MDD-0 to MDD-1 is started immediately after the configura-

tion command is positively acknowledged. End of copying is indicated by the

message: ALL DOUBLE FILES SYNCHRONIZED

Switch on power supply to BAP-x.

Switch on power supply to MDD-1.













A30808-X3074-A473-2-7620 EY360 - 9


18 List and delete alarms.


OBJECT = RECOV ALPRIO = @####### ALSTAT = @# MSGNO = msgno

ALTYPE = @#######################

PABCAUSE= @#################################################

ALARM-ID: @#############################################################

OBJECT = RECOV ALPRIO = MAJOR ALSTAT = NP MSGNO = msgno

ALTYPE = @#######################

PABCAUSE= @#################################################


OBJECT = RECOV ALPRIO = @####### ALSTAT = @# MSGNO = msgno

ALTYPE = @#######################PABCAUSE= @#################################################

ALARM-ID: @#############################################################


The following command is to be executed with all message numbers <msgno>

belonging to the category ALPRIO=MAJOR and assigned to an ISTART

message:


Further alarm entries can be displayed using the MML command DISP

ALARM;. Once any faults in the units have been successfully cleared, the corre-

sponding 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













EY360- 10 A30808-X3074-A473-2-7620




A30808-X3074-A473-2-7620 EY370 - 1


3.13 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 neces-

sary 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.



EY370- 2 A30808-X3074-A473-2-7620


1 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.

2 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:

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.

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 !



all DLUs

all LTGs

CCNC

SSG

TSG

MB

SYP

Switch on power supply to extra equipment (if present).




A30808-X3074-A473-2-7620 EY370 - 3


4 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 (MST- LED) appears on each module.

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) !

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

6 CP113D is in use.

h...7

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.

Switch on power to BAP-0.


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.



EY370- 4 A30808-X3074-A473-2-7620


7 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) !

During the processing of the next two blocks “FORMAT;”, “;” and “MAN;” have to be entered immediately after the corresponding input request is displayed.

Switch on power to BAP-0.




A30808-X3074-A473-2-7620 EY370 - 5


8 Manual bootstrap - parameter supply.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 @##### @#####






UNIT STATUS TEST

********************************************

BAP-0 @##### @#####

BAP-1 @##### @#####

B:CMY-0 @##### @#####

B:CMY-1 @##### @#####

CMY-0 @##### @#####

CMY-1 @##### @#####

IOC-0 @##### @#####

IOC-1 @##### @#####











b MAN;



EY370- 6 A30808-X3074-A473-2-7620


9 Manual bootstrap - initialise manual restart.IOC-1 MDD : BZS/AKD AND GENERATION-LIST

@#############

actgen @#######################-------

backgen @#######################

-------

goldgen @#######################


Remark:



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;”

b Y;



A30808-X3074-A473-2-7620 EY370 - 7


10 Recovery report.



DATE : @#######@

TIME : @#######@



@##############################


FCP RECOVERY REPORT


-------+----+-----------

MDD-00 NAC NO

MDD-01 ACT YES


---------+------------------+------------

actgen @####### @####### @##




: : :

: : :















END OF LTG LOADING



@#######################################

DATE : @#######@

TIME : @#######@

UNIT : BAPM







EY370- 8 A30808-X3074-A473-2-7620




@##############################


CALL PROCESSING STARTED: @#######@RECOVERY DURATION : @###@ SECONDS



THRESHOLD : @###





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

@######## @######## @######## @######## @########




is executed.



12 Display system time.

b DISP TIME;command repetition EXEC’D

DATE TIME DAY

@####### @####### @# mode h...13

13 Check system time.

Do system time and local time correspond? Y h...15

N h...14

14 Enter new system time.

b ENTR TIME:DATE=yy-mm-dd,TIME=hh-mm-ss,WD=wd;


DATE TIME DAY

@####### @####### @# INSECURE

15 Check mode of system time.

Is mode of system time “SECURE”? Y h...17

N h...16












A30808-X3074-A473-2-7620 EY370 - 9


16 Change mode of system time to SECURE.

b CORR TIME:MODE=SECURE;DANGEROUS COMMAND CORRTIME READY TO EXECUTE<


DATE 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).


PROCESSING.

SYSTEM - RECOVERY


DATE: @#######@ TIME: @#######@



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

@######## @######## @######## @######## @########

All units displayed should be noted and activated later on in this procedure.










EY370- 10 A30808-X3074-A473-2-7620


18 Determine status of periphery and CP.













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 deter-


– 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 redun-

dancy as quickly as possible.
































A30808-X3074-A473-2-7620 EY370 - 11


20 Return BAP-1 to service.




21 Return MDD-0 back to service.



The copying from MDD-1 to MDD-0 is started immediately after the configura-

tion command is positively acknowledged. End of copying is indicated by the

message: ALL DOUBLE FILES SYNCHRONIZED

Switch on power supply to BAP-1.

















EY370- 12 A30808-X3074-A473-2-7620


22 List and delete alarm(s).


OBJECT = RECOV ALPRIO = @####### ALSTAT = @# MSGNO = @####

ALTYPE = @#######################

PABCAUSE= @#################################################

ALARM-ID: @#############################################################


ALTYPE = @#######################

PABCAUSE= @#################################################



ALTYPE = @#######################PABCAUSE= @#################################################

ALARM-ID: @#############################################################


The following command is to be executed with all message numbers (msgno)

belonging to the category ALPRIO=MAJOR and assigned to the ISTART

message.


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













A30808-X3074-A473-2-7620 EY380 - 1


3.14 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 automaticallytaken 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):

*) If an ISTART2G was executed, post-processing according to procedure EY190-EY194 is to be executed.








that was executed in the calling procedure (= the branch destination) must be clicked onand confirmed with OK. The branch back to this block is then made.

periphery status: almost all LTGs are active only a few LTGs are

active

“Current generation” after

automatic recovery:

actgen *) backgen /

goldgen

actgen / backgen /

goldgen

proposed measures: activate inactive

units by manual

configuration

initiate a manual recovery, using

generation <actgen> (load LTGs with

code and data)



EY380- 2 A30808-X3074-A473-2-7620


1 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 !

2 Decision.

Is a session already established ? Y h...4N h...3




is executed.



4 Check current status of peripheral units (LTGs).


NO: LTG CH0 CH1 NO: LTG CH0 CH1 NO: LTG CH0 CH1 NO: LTG CH0 CH1

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

no. ost ost ost @### @## @## @## @### @## @## @## @### @## @## @##

@### @## @## @## @### @## @## @## @### @## @## @## @### @## @## @##

: : : :

: : : :

h...5








A30808-X3074-A473-2-7620 EY380 - 3


5 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 initi-

ated. 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.

6 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



EY380- 4 A30808-X3074-A473-2-7620


7 List generations:





----------+----------+---------+-----+-----------------+---+------------

@######### actgen @######## @## @####### @####### @## @#######

-------

@######### backgen @######## @## @####### @####### @## @#######

-------

@######### oldgold @######## @## @####### @####### @## @#######


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 – The NAME OF THE CURRENT GENERATION is identical to the entry in the


Fallback to the last backup generation <backgen>. h...11 – The NAME OF THE CURRENT GENERATION is identical to the entry in the

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...11

8 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 ? Y h...10N h...9








A30808-X3074-A473-2-7620 EY380 - 5


9 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. h...26

10 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. h...2611 ISTART2G with <backgen> or <goldgen>.

The automatic recovery was executed by using an older generation. The post-

processing 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 initi-

ated. h...12

12 Decision.



13 CP113C is in use: Manual Initial Start of BAP-0.


Put switch S1 on DCCMC of BAP-1 in the OFF position (down).




iThe next higher TAC level should be informed about the system status and the

ISTART2G.







EY380- 6 A30808-X3074-A473-2-7620


14 CP113D is in use: Manual Initial Start of BAP-0.

Press RESET key 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).






A30808-X3074-A473-2-7620 EY380 - 7


15 Manual bootstrap - parameter supply.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 @##### @#####






UNIT STATUS TEST

********************************************

BAP-0 @##### @#####

BAP-1 @##### @#####

B:CMY-0 @##### @#####

B:CMY-1 @##### @#####

CMY-0 @##### @#####

CMY-1 @##### @#####

IOC-0 @##### @#####

IOC-1 @##### @#####











b MAN;



EY380- 8 A30808-X3074-A473-2-7620


16 Manual bootstrap - initiate manual restart.IOC-0 MDD : BZS/AKD AND GENERATION-LIST

@#############

actgen @#######################-------

backgen @#######################

-------

goldgen @#######################


@#############

actgen @#######################

-------

backgen @#######################

-------

goldgen @#######################


Remark:



The generation name <actgen> can be determined from the printout above.

b actgen;

MANUAL RECOVERY - LTG LOADING :”Y;/N;”

b Y;

17 Decision.




Locate module DCCMC for BAP-1 (moloc 101).Put switch S1 in the ON position (up). h...20






A30808-X3074-A473-2-7620 EY380 - 9


20 Recovery report.



DATE : @#######@

TIME : @#######@



@##############################


FCP RECOVERY REPORT


-------+----+-----------

MDD-00 ACT YES

MDD-01 ACT NO


---------+------------------+------------

actgen @####### @####### @##




: : :

: : :















END OF LTG LOADING







EY380- 10 A30808-X3074-A473-2-7620



@#######################################

DATE : @#######@

TIME : @#######@

UNIT : BAPM




@##############################






THRESHOLD : @###





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

@######## @######## @######## @######## @########

21 Evaluation of the recovery.

– 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.If there is a call key at the OMT, the system requests the user identification and


!

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 thenext higher TAC level !



A30808-X3074-A473-2-7620 EY380 - 11


23 List generations:





----------+----------+---------+-----+-----------------+---+------------

@######### actgen @######## @## @####### @####### @## @#######

-------

@######### backgen @######## @## @####### @####### @## @#######

-------

@######### oldgold @######## @## @####### @####### @## @#######


Remark:


h...24

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.)



Startup with generation <actgen> (= the generation which was used for the

manual initial start) was successful. h...26 – The NAME OF THE CURRENT GENERATION is identical to the entry in the


Fallback to the last backup generation <backgen>. h...25 – The NAME OF THE CURRENT GENERATION is identical to the entry in the

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...25

25 ISTART2G was carried out.

The recovery was carried out by using an older generation (ISTART2G). For all

further measures consult the next higher TAC level.

End of procedure. h...35

iThe next higher TAC level should be informed about the system status and the

ISTART2G.








EY380- 12 A30808-X3074-A473-2-7620


26 Display system time.

b DISP TIME;command repetition EXEC’D

DATE TIME DAY

@####### @####### @# mode h...27

27 Check system time.

Do system time and local time correspond? Y h...29N h...28

28 Enter new system time.

b ENTR TIME:DATE=yy-mm-dd,TIME=hh-mm-ss,WD=wd;


DATE TIME DAY

@####### @####### @# INSECURE

29 Check mode of system time.

Is mode of system time “SECURE”? Y h...31

N h...30

30 Change mode of system time to SECURE.

b CORR TIME:MODE=SECURE;

DANGEROUS COMMAND CORRTIME READY TO EXECUTE<


DATE TIME DAY

@####### @####### @# SECURE

















A30808-X3074-A473-2-7620 EY380 - 13



The system status is determined in order to be able to restore the original condi-

tion of the network node prior to shutdown (default configuration).


PROCESSING.

SYSTEM - RECOVERY


DATE: @#######@ TIME: @#######@



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

@######## @######## @######## @######## @########

All units displayed should be noted and activated later in this procedure.





EY380- 14 A30808-X3074-A473-2-7620


32 Determine status of periphery and CP.













The system configuration before the power failure is defined as “default configu-

ration”.

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 deter-

































A30808-X3074-A473-2-7620 EY380 - 15


34 List and delete alarm(s).



ALTYPE = @#######################

PABCAUSE= @#################################################

ALARM-ID: @#############################################################

OBJECT = RECOV ALPRIO = @####### ALSTAT = NP MSGNO = @####

ALTYPE = @#######################

PABCAUSE= @#################################################



ALTYPE = @#######################PABCAUSE= @#################################################

ALARM-ID: @#############################################################


The following command is to be executed with all message numbers (msgno)

assigned to an ISTART / ISTART2G message.


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.


END













EY380- 16 A30808-X3074-A473-2-7620




A30808-X3074-A473-2-7620 EY400 - 1


3.15 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.








EY400- 2 A30808-X3074-A473-2-7620


3.15.2.1 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:

• Disconnect plugs to M:PEX module and DCCMC voltage converter

• Configure the relevant processor to OST=ACT (BAP to SPR)

3.15.2.2 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


• Disconnect plugs to M:BCM module and DCCMC voltage converter

3.15.2.3 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

A F B 5

A x x 5

A x x 5

A p c 5 (pc = patch counter for BACKUP PART)A F A 5

A x x 5

A x x 5

A p c 5 (pc = patch counter for FEPROM)

A 0 0 5

B C M x x x x x x x x x

patch counter value



A30808-X3074-A473-2-7620 EY400 - 3


• 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


• Disconnect plugs to M:CMYC module and DCCMC voltage converter

3.15.2.4 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.

PATCON 3 : x x x x x x x x

patch counter value

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



EY400- 4 A30808-X3074-A473-2-7620


3.15.3 Diagram











1 Decision about rolling recovery

Is there rolling recovery in the system ? Y h...2N h...3

abnormal termination

of FEPROM patching

rolling recovery ?

noyes

phase of abnormaltermination of

preparation andtest phase

master filephase

flash phase final evaluatingphase

fault clearanceby operating

personnel

call TAC3call TAC3call TAC3

symptomsaving

symptom symptomsaving saving

getimportant information

get

importantinformation

NO FURTHER ACTIONS

end of procedure

request replacementmodules

call TAC3FEPROM patching



A30808-X3074-A473-2-7620 EY400 - 5


2 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 replace-

ment modules must contain the state of firmware before patching in their

FEPROM.

Call TAC3

All further actions are instructed by TAC3 exclusively. h...8

3 Phase of abnormal termination of FEPROM patching

In which phase was the FEPROM patching aborted ?

– Preparation and test phase h...4 – Master file phase h...5 – Flash phase h...6 – Final evaluation phase h...7

4 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

5 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 ......Determinepatch countervalues

h...8

!No further actions

(No configuration, no activation or deactivation of system status analysis or routine test, no diagnosis, no

testing)







EY400- 6 A30808-X3074-A473-2-7620


6 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




Determine patch counter values under instruction of TAC3 ......Determinepatch countervalues

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)

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




Determine patch counter values under instruction of TAC3 ......Determinepatch counter

values

h...8

!No further actions


testing)

!No further actions


testing)











A30808-X3074-A473-2-7620 EY400 - 7


8 End of procedure

End of procedure.

END



EY400- 8 A30808-X3074-A473-2-7620




A30808-X3074-A473-2-7620 EY500 - 1


3.16 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 appro-

priate 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 proce-

dure:

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:

– MMN:SW / Register PROC / Procedure SW210



– EMCYMN / Register PROC / Procedure EY710




– MMN:CP113 if copying of the disk is not successful



EY500- 2 A30808-X3074-A473-2-7620



1 Interrogation of configuration.


2 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

------------------+-----------+------------

@################ @####### @######

Did the above message appear? Y h...5N h...6

5 Double file failure?

Important note:

Have several error messages been displayed and did they refer to both MDDs (DOUBLE FILE FAILURE)?

Y h...6N h...MMN:SW,

PROC, SW310




















A30808-X3074-A473-2-7620 EY500 - 3


6 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 theSY.PSW.Txxx files successful? Y h...7N h...EMCYMN,

PROC, EY502

7 List catalog entries.


@################## @#############################



-----------------+--------+------+-------------+-------------+-----+----

CG.SA.xxxxx @####### @##### @############ @############ @### SAM

: @####### @##### @############ @############ @### SAM

8 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...10N h...EMCYMN,

PROC, EY502

!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.




















EY500- 4 A30808-X3074-A473-2-7620



Golden generation files defective?

Are files of the generation GOLDEN (goldgen) defective, not valid, or not present?

Y h...11

N h...12


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

b CONF MDD:MDD=x,OST=MBL;command repetition EXEC’D

In direct mode the following command is to be typed without the path-name

“ - DIAG”: b DIAG MDD- DIAG:MDD=x;




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:



END





















A30808-X3074-A473-2-7620 EY501 - 1



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 couldn’t

be repaired automatically.

Checksum error on one background memory → MAJOR alarm

Checksum error on bot h background memories → CRITICAL alarm

BACKUP GENERATION A checksum error on a single or on both backgroundmemories was detected. The checksum error couldn’t


Checksum error on one background memory → MINOR alarm

Checksum error on both background memories → MINOR alarm

GOLDEN GENERATION A checksum error on a single or on both background

memories was detected. The checksum error couldn’t


Checksum error on one background memory → MINOR alarm

Checksum error on both background memories →

MINOR alarm



EY501- 2 A30808-X3074-A473-2-7620


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:

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 wasn’t successful a resto-

ration 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.

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



A30808-X3074-A473-2-7620 EY501 - 3










1 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 couldn’t 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: h...93 – Alarmed checksum error which could not be repaired automatically: h...2

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:



EY501- 4 A30808-X3074-A473-2-7620


ADMINISTRATION ALARM MMN:@#########

REASON: CHECKSUM MISMATCH

DATE: @#######

TIME: @#######

INDICATIONS

-----------

DEFECTIVE FILE MDD-00: @################


CHECKSUM (HEX) IND.

FILE GEN TYPE MD STORED COMPUTED RESULT FILE

-----------------+--------+--------+--+-----------------+------+----

@################ @####### ACTUAL @# @################ @##### @###

@################ @####### ACTUAL @# @################ @##### @###

2. The BACKUP GENERATION is affected: ADMINISTRATION ALARM MMN:@#########


DATE: @#######

TIME: @#######

INDICATIONS

-----------



CHECKSUM (HEX) IND.


-----------------+--------+--------+--+-----------------+------+----

@################ @####### BACKUP @# @################ @##### @###

@################ @####### BACKUP @# @################ @##### @###

3. The GOLDEN GENERATION is affected:

ADMINISTRATION ALARM MMN:@#########


DATE: @#######

TIME: @#######

INDICATIONS

----------- DEFECTIVE FILE MDD-00: @################


CHECKSUM (HEX) IND.


-----------------+--------+--------+--+-----------------+------+----

@################ @####### GOLDEN @# @################ @##### @###

@################ @####### GOLDEN @# @################ @##### @###

Were checksum errors detected for several generation files? Y h...3

N h...4









A30808-X3074-A473-2-7620 EY501 - 5


3 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 h...105 – Only o n e generation is affected by the checksum errors: h...4

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

5 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> :

Possible entries for the second part <bbb> (not always present):

CI = Checksum Information

CN = Checksum mismatch Not repaired

CR = Checksum mismatch Repaired

NC = No Checksum test

OK = checksum OKay



EY501- 6 A30808-X3074-A473-2-7620


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 !

6 Decision block.

Did the checksum error(s) appear on b o t h background memories? Y h...7

N h...8

7 The checksum error(s) did appear on both background memories.

The following alarm mask was printed out:

ADMINISTRATION ALARM MMN:SW500-0000


DATE: @#######

TIME: @#######

INDICATIONS

-----------

DEFECTIVE FILE MDD-00: AU.Cxxx

DEFECTIVE FILE MDD-01: AU.Dxxx

CHECKSUM (HEX) IND.


-----------------+--------+--------+--+-----------------+------+----

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 ( C hecksum mismatch N ot corrected) in the column RESULT for

both background memories (MDD-0 and MDD-1) is important. h...9

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





A30808-X3074-A473-2-7620 EY501 - 7


8 The checksum error(s) did appear only on one background memory.



REASON: CHECKSUM MISMATCH DETECTED ON MDD-01

DATE: @#######

TIME: @#######

INDICATIONS

-----------

DEFECTIVE FILE: AU.Dxxx

INTACT FILE : AU.Axxx

CHECKSUM (HEX) IND.


-----------------+--------+--------+--+-----------------+------+----

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

9 Checksum error of the CURRENT GENERATION (both disks):

SY.SIMP

Was a checksum error detected for the file SY.SIMP of the CURRENT GENER-

ATION <actgen> ? Y h...10N h...11


SY.SIMP

i This file cannot be restored !





EY501- 8 A30808-X3074-A473-2-7620


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 ?

– ISTART2G should be carried out: i....EMCYMN,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. h...93


SY.SEMILIB

Was a checksum error detected for the file SY.SEMILIB of the CURRENT

GENERATION <actgen> ? Y h...12

N h...13


SY.SEMILIB

Restore the file by using the data in memory:

b UPD GEN;command repetition ACCEPTED

: : : :

: : : :


h...13

13 Checksum error of the CURRENT GENERATION (both disks):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 ? Y h...14

N h...43














A30808-X3074-A473-2-7620 EY501 - 9



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? 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 fall-

back generation (BACKUP or GOLDEN).

Which APS saving (quarterly saving / routine saving) was carried out at latest?

– Routine saving was carried out at latest: h...16 – Quarterly saving was carried out at latest: h...23


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 corre-

sponding 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 path-

name “- DISKFAIL”.

b TRANS SYFILE - DISKFAIL:FILE=name,VSN=SYSVSN,GEN=actgen;command repetition EXEC’D


Further code files defective ?

Are further files of the CURRENT GENERATION <actgen> defective on b o t h

background memories? Y h...16

N h...18






EY501- 10 A30808-X3074-A473-2-7620



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” isn’t 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 indi-

cated by the entry “ CI MFS ” in the column RESULT .

b ACT MDDAUDIT:TYPE=ACTUAL,RESTORE=REST;command repetition ACCEPTED

: : : :

: : : :


CHECKSUM (HEX) IND.


-----------------+--------+--------+--+-----------------+------+-----

@################ @####### ACTUAL 00 @################ aa bbb @###

@################ @####### ACTUAL 01 @################ aa bbb @###

: : : :

: : : :


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:

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:

OK checksum OKay

CR Checksum mismatch Repaired








A30808-X3074-A473-2-7620 EY501 - 11


– 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:

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:

h...20


Current system status.

Which one of the three situations did occur ?

– All checksum errors repaired h...33

– Checksum errors on one background memory h...41 – Checksum errors on both background memories h...21


Code file(s) - patch status -

Were patches entered since the last APS quarterly saving was carried out ? Y h...39N h...22

CN Checksum mismatch Not repaired

CI MFS Checksum Information/Mismatch Flag Set



iIf 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 !



EY501- 12 A30808-X3074-A473-2-7620



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.

b CAN GEN:GEN=backgen;command repetition EXEC’D

Since there is no BACKUP GENERATION on the background memories, the

repair measures are automatically carried out with files of the GOLDEN

GENERATION. 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 GENER-

ATION <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 corre-

sponding file(s) of the GOLDEN 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”:

b TRANS SYFILE - DISKFAIL:FILE=name,VSN=SYSVSN,GEN=actgen;command repetition EXEC’D


Further code files defective ?

Are further files of the CURRENT GENERATION <actgen> defective on both

background memories? Y h...23

N h...25













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



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


The entries in column RESULT of that list are to be evaluated. (The 2nd entry

“bbb” isn‘t 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 indi-

cated by the entry “CI MFS” in the column RESULT.

b ACT MDDAUDIT:TYPE=ACTUAL,RESTORE=REST;


: : : :

: : : :


CHECKSUM (HEX) IND.


-----------------+--------+--------+--+-----------------+------+-----

@################ @####### ACTUAL 00 @################ aa bbb @###

@################ @####### ACTUAL 01 @################ aa bbb @###

: : : :

: : : :


Code file(s)






column RESULT:




OK checksum OKay









EY501- 14 A30808-X3074-A473-2-7620



memory are output.


of the following entries.At least one file has for a single background memory in the column







h...27







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? Y h...29

N h...39







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



Code file(s) - GOLDEN on save tape -

Together with the next higher TAC level it was decided to try to repair the defec-

tive file(s) by using the last APS save tape.

Mount and load the last startup tested APS save tape (SA1TAP).

b 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).


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



: : : :

: : : :


CHECKSUM (HEX) IND.


-----------------+--------+--------+--+-----------------+------+-----@################ @####### ACTUAL 00 @################ aa bbb @###

@################ @####### ACTUAL 01 @################ aa bbb @###

: : : :

: : : :


Code file(s)






column RESULT:




OK checksum OKay












EY501- 16 A30808-X3074-A473-2-7620



memory are output.


of the following entries,but at least one file has for a single background memory in the column







h...32







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.

– No LOADLIBs were replaced. h...35 – At least one of the files LOADLIB.CA/LA/MA was replaced. h...34



The following command is to be executed for all LOADLIBs which were replaced

during the repair measures.

(If a NOT EXEC’D message occurs it can be ignored as long as the respective

file is already connected (DLL_NO: 16)).

b ACT LOADLIB:LIB=SY.LOADLIB.xA;command repetition EXEC’D

h...35










A30808-X3074-A473-2-7620 EY501 - 17



Code file(s) - execute APS saving -

Was the BACKUP GENERATION deleted in a former step ? Y h...36N h...93



Was this procedure entered while an APS saving according to MMN:SW, proce-

dure SW210 was carried out ? Y h...37

N h...38


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. h...93



b STAT LOG;command repetition EXEC’D

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 ! h...93














EY501- 18 A30808-X3074-A473-2-7620



Code file(s) - fall back on older generation -

There exist two alternatives for further fault clearance measures:

– 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 GENERA-

TION 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.




After returning from EY19x, symptom saving is to be carried out. h...93



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.

– No LOADLIBs were replaced. h...43 – At least one of the files LOADLIB.CA/LA/MA was replaced. h...42



The following command is to be executed for all LOADLIBs which were replaced

during the repair measures.

(If a NOT EXEC’D message occurs it can be ignored as long as the respective

file is already connected (DLL_NO: 16)).


h...43

i 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 !)










A30808-X3074-A473-2-7620 EY501 - 19


43 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 ? Y h...44N 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 it’s checksum error only on one back-

ground 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: b ACT MDDAUDIT:TYPE=ACTUAL,RESTORE=REST;


: : : :

: : : :


CHECKSUM (HEX) IND.


-----------------+--------+--------+--+-----------------+------+-----

@################ @####### ACTUAL 00 @################ aa bbb @###

@################ @####### ACTUAL 01 @################ aa bbb @###

: : : :

: : : :


The repair measure was successful , if both statements are true:

• No alarm mask was output.

• All checked files (whole generation) have one of the following entries in the

column RESULT :

The repair measure was not successful , if at least one of the following state-

ments 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 :

OK ( = checksum OKay )

CR ( = Checksum mismatch Repaired )

CN ( = Checksum mismatch Not repaired )

CI MFS ( = Checksum Information / Mismatch Flag Set )








EY501- 20 A30808-X3074-A473-2-7620



Was the repair measure successful ? Y h...69

N h...47


Are only PSW files affected ? Y h...49N h...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):

• 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 !

h...105


PSW file(s) - BACKUP GENERATION on background memories -

Does the BACKUP GENERATION <backgen> exist on the background memo-

ries ? Y h...50N h...51


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

N h...52


PSW file(s) - patch status -

Were patches entered since the last quarterly saving was carried out ? Y h...73N h...59



A30808-X3074-A473-2-7620 EY501 - 21



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 path-

name “ - OVWRGENF “:

b TRANS SYFILE-OVWRGENF:

FILE=name,VSN=SYSVSN,GEN=actgen,REASON=OVWRGENF;command repetition ACCEPTED

: : : :

: : : :


53 Checksum error of the CURRENT GENERATION (one disk):PSW file(s)

Are further PSW files of the CURRENT GENERATION <actgen> defective ? Y h...52N h...54

54 Checksum error of the CURRENT GENERATION (one disk) :

PSW file(s)


: : : :

: : : :


CHECKSUM (HEX) IND.


-----------------+--------+--------+--+-----------------+------+-----

@################ @####### ACTUAL 00 @################ aa bbb @###

@################ @####### ACTUAL 01 @################ aa bbb @###

: : : :

: : : :

55 Checksum error of the CURRENT GENERATION (one disk) :

The repair measure was successful , if both statements are true: • No alarm mask was output.


column RESULT :
















EY501- 22 A30808-X3074-A473-2-7620



ments is true:


• At least one file has for one background memory one of the following entries in the column RESULT :



N h...57

57 Checksum error of the CURRENT GENERATION (one disk):PSW file(s) - patch status -

Were patches entered since the last quarterly saving was carried out ? Y h...73

N h...57


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.

b CAN GEN:GEN=backgen;command repetition EXEC’D

Since there is no BACKUP GENERATION on the background memories, the repair measures are automatically carried out with files of the GOLDEN

GENERATION. h...59








A30808-X3074-A473-2-7620 EY501 - 23



Code file(s) - Golden on disk -

Overwrite the defective file(s) by using the T RANS SYFILE c ommand: • Either the last APS saving was a quarterly saving or the BACKUP GENER-

ATION <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 corre-

sponding file(s) of the GOLDEN 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 “ - OVWRGENF ”:


FILE=name,VSN=SYSVSN,GEN=actgen,REASON=OVWRGENF;command repetition ACCEPTED

: : : :

: : : :



Further PSW files defective ?

Are further PSW files of the CURRENT GENERATION <actgen> defective on

both background memories? Y h...59

N h...61


PSW file(s)


: : : :

: : : :


CHECKSUM (HEX) IND.


-----------------+--------+--------+--+-----------------+------+-----

@################ @####### ACTUAL 00 @################ aa bbb @###@################ @####### ACTUAL 01 @################ aa bbb @###

: : : :

: : : :

















EY501- 24 A30808-X3074-A473-2-7620






column RESULT :


ments is true:





PSW file(s)

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

N h...64

64 Checksum error of the CURRENT GENERATION (one disk):PSW file(s) - GOLDEN on 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.

– 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).





iFor 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.









A30808-X3074-A473-2-7620 EY501 - 25



PSW file(s) - GOLDEN on tape -


: : : :

: : : :


CHECKSUM (HEX) IND.


-----------------+--------+--------+--+-----------------+------+-----

@################ @####### ACTUAL 00 @################ aa bbb @###

@################ @####### ACTUAL 01 @################ aa bbb @###

: : : :

: : : :






column RESULT :


ments is true:






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



Was the BACKUP GENERATION deleted in a former step ? Y h...70

N h...93












EY501- 26 A30808-X3074-A473-2-7620




Was this procedure entered while an APS saving according to MMN:SW, proce-dure SW210 was carried out ? Y h...71N h...72


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. h...9372 Checksum error of the CURRENT GENERATION (both disks):



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 SW210, postprocessing is to be carried out ! h...93


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.


the next higher TAC level.














A30808-X3074-A473-2-7620 EY501 - 27


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 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 was deleted in a former step, it has to be

replaced by a new fallback generation after finishing the fault clearance

measures successfully ! h...105

74 Checksum error of the BACKUP GENERATION











OK = checksum OKay



EY501- 28 A30808-X3074-A473-2-7620






answered with YES !

75 Decision block

Did the checksum error(s) appear on b o t h background memories? Y h...76

N h...77





DATE: @#######

TIME: @#######

INDICATIONS

-----------



CHECKSUM (HEX) IND.


-----------------+--------+--------+--+-----------------+------+----

name @####### BACKUP 00 @################ CN AU.C

name @####### BACKUP 01 @################ CN AU.D


The file “name” of the BACKUP GENERATION (BACKUP) is defective on both










NOH = NO Heap







A30808-X3074-A473-2-7620 EY501 - 29


77 The checksum error(s) did appear only on a single background memory.




DATE: @#######

TIME: @#######

INDICATIONS

-----------



CHECKSUM (HEX) IND.


-----------------+--------+--------+--+-----------------+------+----

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


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...93

iAfter 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 backgroundmemory (if existing) are also cleared.









EY501- 30 A30808-X3074-A473-2-7620


79 Checksum error of the BACKUP GENERATION (one disk):


background memories.If several files are defective, each file has it’s checksum error only on one back-




list is to be evaluated:

b ACT MDDAUDIT:TYPE=BACKUP,RESTORE=REST;command repetition ACCEPTED

: : : :

: : : :


CHECKSUM (HEX) IND.


-----------------+--------+--------+--+-----------------+------+-----

@################ @####### BACKUP 00 @################ aa bbb @###

@################ @####### BACKUP 01 @################ aa bbb @###

: : : :

: : : :

80 Checksum error of the BACKUP GENERATION (one disk) :




column RESULT :


ments is true:




81 Checksum error of the BACKUP GENERATION (one disk)


N h...82












A30808-X3074-A473-2-7620 EY501 - 31


82 Checksum error of the BACKUP GENERATION (one disk) :


the next higher TAC level.Suggestions for further fault clearance measures:

• Suggestion 1:

The suggested fault clearance measure can only be applied, if no crossed

faults were detected. That means all checksum errors appeared on the same


– 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 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











OK = checksum OKay



EY501- 32 A30808-X3074-A473-2-7620






answered with YES !




REASON: CHECKSUM MISMATCH DATE: @#######

TIME: @#######

INDICATIONS

-----------



CHECKSUM (HEX) IND.


-----------------+--------+--------+--+-----------------+------+----

name @####### GOLDEN 00 @################ CN AU.C

name @####### GOLDEN 01 @################ CN AU.D


The file “name” of the GOLDEN GENERATION (GOLDEN) is defective on both










NOH = NO Heap







A30808-X3074-A473-2-7620 EY501 - 33


85 The checksum error(s) did appear only on a single background memory.




DATE: @#######

TIME: @#######

INDICATIONS

-----------



CHECKSUM (HEX) IND.


-----------------+--------+--------+--+-----------------+------+----

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


86 Checksum error of the GOLDEN GENERATION (both disks):

The next APS quarterly saving is to be carried out immediately:


Is file LOG6 active ? Y h...88N h...87








EY501- 34 A30808-X3074-A473-2-7620



Change from LOGx to LOG6:

b MOD LOGFILE:FILE=LOG6,SIZE=24,ERASE=YES;command repetition EXEC’D

Mount the APS routine save tape (LOGTAP) (possibly already done).

b DEL FILE:FILE:DUMMY.MET,VSN=LOGTAP;command repetition EXEC’D

The closed LOG file (LOGx) is transferred to tape:

b TRANS FILE:FILE=LG.LOGx.,VSNR=LOGTAP,COPMOD=SSWF;command repetition EXEC’D


b DEL FILE:FILE=LG.LOGx.;command repetition EXEC’D

h...88


The next quarterly saving is to be carried out immediately. i....MMN:SW,PROC, SW210



h...93

iAfter 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.






















A30808-X3074-A473-2-7620 EY501 - 35


89 Checksum error of the GOLDEN GENERATION (one disk):


background memories.If several files are defective, each file has it’s checksum error only on one back-




list is to be evaluated:

b ACT MDDAUDIT:TYPE=BACKUP,RESTORE=REST;command repetition ACCEPTED

: : : :

: : : :


CHECKSUM (HEX) IND.


-----------------+--------+--------+--+-----------------+------+-----

@################ @####### GOLDEN 00 @################ aa bbb @###

@################ @####### GOLDEN 01 @################ aa bbb @###

: : : :

: : : :





column RESULT :


ments is true:






N h...92












EY501- 36 A30808-X3074-A473-2-7620




the next higher TAC level.Suggestions for further fault clearance measures:

• Suggestion 1:

The suggested fault clearance measure can only be applied, if no crossed

faults were detected. That means all checksum errors appeared on the same


– 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 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.

b DISP FILE:FILE=AU.;

Do AU. files exist on the background memories ? Y h...94

N h...95

94 Postprocessing: AU files available.command repetition EXEC’D

@################## @#############################



-----------------+--------+------+-------------+-------------+-----+----

AU.xxx @####### @##### @############ @############ @### @###

AU.yyy @####### @##### @############ @############ @### @###

: : : : : : : :

h...96

95 Postprocessing: No AU files available.command repetition EXEC’D

NO (MORE) DATA FOR DISPLAY AVAILABLE. h...99










A30808-X3074-A473-2-7620 EY501 - 37


96 Postprocessing: Saving of AU files (init tape).

Mount and load a new magnetic tape.

b INIT MT:MTD=00,VSN=AU1TAP,DENS=6250,CD=EBC;command repetition ACCEPTED

: : : :

: : : :


97 Postprocessing: Saving of AU files (trans file).

b 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: M OUNT TAPE : DEV = MTD -00;


SENDER : @#######

RECEIVER : @#######

START START



-+-----------------+------+-----+-+-----+-+--+----+---------+-----+-----

S AU.xxx @##### TR @ @#### @ @# @### @######## @#### @####

R AU.xxx AU1TAP CR @ @#### @ @# @### @######## @#### @#### : : : :

: : : :


Rewind and remove AUxTAP.

98 Postprocessing: Saving of AU files (del file).

b DEL FILE:FILE=AU.;command repetition ACCEPTED

FILE

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

AU.xxx

:

:


























EY501- 38 A30808-X3074-A473-2-7620


99 Postprocessing: Delete alarm entries.

b DISP ALARM:OBJECT=ADMINAL;command repetition EXEC’D

OBJECT = ADMINAL ALPRIO = @####### ALSTAT = @# MSGNO = @####

ALTYPE = @#######################

PABCAUSE= @#################################################

ALARM-ID: @#############################################################

: : : :

: : : :


ALTYPE = @#######################

PABCAUSE= CORRUPT DATA

ALARM-ID: @############################################################# : : : :

: : : :


ALTYPE = @#######################

PABCAUSE= @#################################################

ALARM-ID: @#############################################################

: : : :

: : : :


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.


100 Postprocessing: Save history files according to SW231.

In order to save further symptoms, procedure SW231 is to be carried out ! i....MMN:SW,PROC, SW231



101 Postprocessing: Return to calling procedure.

Was (were) the checksum error(s) detected during an APS saving ? Y h...102

N h...105

iThe 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.

















A30808-X3074-A473-2-7620 EY501 - 39


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 ? Y h...103N h...104

103 Postprocessing.

Since the requested APS saving was already carried out, it is not necessary to

return to procedure SW210.

h...105

104 Postprocessing.

The checksum errors were repaired successfully. Therefore APS saving

according to MMN:SW, procedure SW210 can be continued.

h...105

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



END



EY501- 40 A30808-X3074-A473-2-7620




A30808-X3074-A473-2-7620 EY502 - 1



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 oper-

ations 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.






priate point in the referenced procedures.



MMN:SW IN for information) must be used in the following manner in the present proce-

dure:

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:

- MMN:SW / Register PROC / Procedure SW211

- EMCYMN / Register PROC / Procedure EY500


- MMN:CP113 if copying of the disk is not successful



EY502- 2 A30808-X3074-A473-2-7620











1 DOUBLE FAILURE OF A GENERATION FILE:

Decision block.

Was a checksum error detected for the file SY.SIMP of the CURRENT GENER-

ATION (actgen) in the previous procedure EY501? Y h...19

N h...2


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...7N h...3


Restoration of the valid PSW file.

Mount and load the latest (startup tested) APS save tape (part 1) in MTD.

The parameter GEN must be given the name of the CURRENT GENERATION

(actgen).


name “ - OVWRGENF ” :

b 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;












A30808-X3074-A473-2-7620 EY502 - 3



Decision block.

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


Decision block.

Is another LTG load type (SY.PSW.Txxx file) of the CURRENT GENERATION

(actgen) defective, not valid or not present? 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.


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 DISP FILE c ommand results in a dummy output, generation file(s)

SY.LOADLIB.CA/LA/MA is (are) defective, not valid, or not present on both

disks.


@################## @#############################



-----------------+--------+------+-------------+-------------+-----+----

filename @####### @##### @############ @############ @### @###

: : : :

: : : :

8 DOUBLE FAILURE OF A GENERAL FILE:

Decision block.

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

(actgen) defective, not valid or not present?

(If DISP FILE command results in a default output, the answer is YES!) Y h...9N h...18


















EY502- 4 A30808-X3074-A473-2-7620



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 param-

eter FILE . The parameter GEN must be given the name of the CURRENT

GENERATION.


name “ - DISKFAIL” :

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


: : : :

: : : :


After the commands for all files were input, the following questions are to be

answered.

h...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! h...50 – All commands were accepted. h...11


Success of restoration measures.

“Not successful” means that the TRANS SYFILE command is acknowledged

with “NOT EXEC’D”.

– Restoration measures were successful: h...14 – Restoration measures were not successful: h...12
















A30808-X3074-A473-2-7620 EY502 - 5



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 defec-

tive, 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 param-

eter FILE . The parameter GEN must be given the name of the CURRENT

GENERATION.



b TRANS SYFILE - DISKFAIL:GEN=actgen,FILE=name,VSN=SA1TAP;command repetition ACCEPTED





After the commands for all files were input the following question is to be

answered.

h...13


Success of restoration measures.

“Not successful” means that the TRANS SYFILE command is acknowledged

with “NOT EXEC’D”.

– 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 EXEC’D message occurs with DLL-No. 16 it can be ignored as long as

the respective file is already connected.)


After the commands for all files were input, all possibly deactivated IOPLAU’S

and X25LINK’s are to be reactivated:

Possibly deactivated IOPLAU’s and X25LINK’s are to be activated again. h...15





















EY502- 6 A30808-X3074-A473-2-7620



Are further generation files defective?


@################## @#############################



-----------------+--------+------+-------------+-------------+-----+----

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 – No further generation file is defective: h...EMCYMN,

PROC, EY503


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 – No generation file of the CURRENT GENERATION (actgen) is defective. h...EMCYMN,

PROC, EY503


SY.SIMP

Is the file SY.SIMP of the CURRENT GENERATION (actgen) defective, not valid

or not present? Y h...19N h...18

18 DOUBLE FAILURE OF A GENERATION FILE:SY.SEMILIB

Is the file SY.SEMILIB of the CURRENT GENERATION (actgen) defective, not

valid or not present? Y h...38

N h...19


Changes in CCS7 database.

Did the CCS7 database change since the APS save tape was created? Y h...50

N h...20
















A30808-X3074-A473-2-7620 EY502 - 7



CCS7 patches.

Have CCS7 patches been incorporated in the APS since the save tape wascreated? Y h...50N 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 semiper-

manent 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.

b MOD LOGFILE:FILE=LOG6,SIZE=24,ERASE=YES;

– switch off MDD-0


– Wait for failure message:

(Failure messages and alarms are to be ignored!)MDD-@#: INOPERABLE AND THEREFORE DEACTIVATED.

DOUBLE DISK FAILURE!

– switch on MDD-0

– switch on MDD-1

Wait approx. 1 minute!

Configure both MDD to OST=MBL:

b CONF MDD:MDD=0,OST=MBL;


b CONF MDD:MDD=0,OST=ACT;

b CONT MDDACT:LABEL;CONFIGURATION MDD-0 FROM MBL TO ACT

























EY502- 8 A30808-X3074-A473-2-7620



Tape to disk transfer of save tape files.

Mount and load the latest (startup tested) APS quarterly save tape (part 1) inMTD.

The parameter GEN must be given the name of the CURRENT GENERATION

(actgen) which is active at the moment.(If necessary/possible find out by using

command DISP GEN):



b TRANS SYFILE - DISKFAIL:GEN=actgen,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


TRANSSYFILE:GEN=actgen,VSN=SA1TAP PART. EXEC’D

TRANSFER RESULT



-+-----------------+--------+------+------+----------+---------+--------

@ 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. EXEC’D, 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.


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)? Y h...25

N h...24















A30808-X3074-A473-2-7620 EY502 - 9



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




name “ - DIAG ”:

b DIAG MDD - DIAG:MDD=x;

b CONF MDD:MDD=x,OST=ACT;

b CONT MDDACT:LABEL; h...22


Updating of semipermanent data.

b UPD GEN;command repetition EXEC’D

b DACT FNS:FNS=X;DANGEROUS COMMAND DACTFNS READY TO EXECUTE<



Continuation tape handling.

Was continuation tape handling carried out during the APS saving? Y h...28

N h...27


Tape to disk transfer of non-generation files (no continuation tape).

Mount and load APS quarterly save tape.

b TRANS FILE:FILE=X,VSNS=SA1TAP;command repetition ACCEPTED

h...29






























EY502- 10 A30808-X3074-A473-2-7620



Tape to disk transfer of non-generation files (continuation tape).

Mount and load APS quarterly save tape (part 1).b TRANS FILE:FILE=X,VSNS=SA1TAP;




handling and then enter: MOUNT TAPE : DEV = MTD -0; h...29









A30808-X3074-A473-2-7620 EY502 - 11



command repetition PART.EXEC’D

SENDER : @#######

RECEIVER : @#######

START START



-+-----------------+------+-----+-+-----+-+--+----+---------+-----+-----

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 @ @#### @ @# @### @######## @#### @####

: : :

i

The previous TRANS FILE command was acknowledged with PART. EXEC’D,

since all files marked with error “L FA 12” had already been transferred by theprevious TRANS SYFILE command. So these files were already present on

disk!





EY502- 12 A30808-X3074-A473-2-7620




The list of files shown below represents the expected status of the disk content: b DISP FILE;


@################## @#############################



-----------------+--------+------+-------------+-------------+-----+----

CG.SA.xxxxx @####### @##### @############ @############ @### SAM

: : : : : : :

CG.SA.yyyyy @####### @##### @############ @############ @### SAM

D9.VLRAL @####### @##### @############ @############ @### SAM

HF.xxxxxx @####### @##### @############ @############ @### CYCIA.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


Decision block.

Are all files of the APS quarterly save tape available on disk? Y h...34N h...32

32 DOUBLE FAILURE OF A GENERATION FILE: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. h...26 – Other reasons (e.g. tape not readable): h...33








A30808-X3074-A473-2-7620 EY502 - 13



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 on MDD-0

Wait approx. 1 minute




b DIAG MDD - DIAG:MDD=0;

b CONF MDD:MDD=0,OST=ACT;

b CONT MDDACT:LABEL; h...22


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 DOUBLE FAILURE OF A GENERATION FILE.

Tape to disk transfer of statistic files.

b TRANS FILE:FILE=CA.,VSNS=LOGTAP;command repetition ACCEPTED


SENDER : @#######

RECEIVER : @#######

START START



-+-----------------+------+-----+-+-----+-+--+----+---------+-----+-----

S CA.ST.UCHA LOGTAP TR @ @#### @ @# @### @######## @#### @####

R CA.ST.UCHA @##### CRD @ @#### @ @# @### @######## @#### @####


























EY502- 14 A30808-X3074-A473-2-7620



Post-processing.

If the updating of the semipermanent data by using command UPD GEN; wassuccessful 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

i....MMN:SW,

PROC, SW210




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


Update semipermanent data.

b UPD GEN;command repetition EXEC’D

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

iAt this point the next saving specified in the safeguarding concept is to be

carried out according to MMN:SW:


















A30808-X3074-A473-2-7620 EY502 - 15



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 path-


b TRANS SYFILE - DISKFAIL:GEN=actgen,FILE=name,VSN=SYSVSN;command repetition ACCEPTED

: : : :

: : : :


Was the transfer of the file(s) successful? Y h...43

N h...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.



b TRANS SYFILE - DISKFAIL: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



After the commands for all files were input the following question is to be

answered.

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! h...48 – All commands were accepted. h...43


















EY502- 16 A30808-X3074-A473-2-7620



Other defective generation files.

Is another generation file of the CURRENT GENERATION (actgen) defective,not valid or not present? Y h...40N h...44


Defective file(s) in BACKUP GENERATION.

Is one of the generation files of the BACKUP GENERATION defective, not valid

or not present? Y h...45

N h...46


Defective file(s) in BACKUP GENERATION.




After procedure SW210 has been successfully completed, this procedure is to

be continued:

h...46


Defective file(s) in GOLDEN GENERATION.

Is one of the generation files of the GOLDEN GENERATION defective, not valid

or not present? Y h...47

N h...50

iThe next saving specified in the safeguarding concept is to be immediately

carried out according to MMN:SW, procedure SW210 !







A30808-X3074-A473-2-7620 EY502 - 17



Defective file(s) in GOLDEN GENERATION.

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, SW210For users of the function ” Manual on PC ” : the branch back to this block is made


After procedure SW210 has been successfully completed, this procedure is to

be continued:

h...50


Restoration of files not possible.

Are files of the GOLDEN GENERATION (goldgen) defective, not valid or not

present? 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


(Failure messages and alarms are to be ignored!)MDD-*#: INOPERABLE AND THEREFORE DEACTIVATED.

i The next quarterly saving specified in the safeguarding concept is to be imme-diately carried out according to MMN:SW, procedure SW210 !









EY502- 18 A30808-X3074-A473-2-7620



– switch on MDD-x


b CONF MDD:MDD=x,OST=MBL;



b DIAG MDD - DIAG:MDD=x; h...EMCYMN,PROC, EY504


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.




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 DOUBLE FAILURE OF A GENERATION FILE:Symptom saving.

Are symptoms to be saved on tape? Y i....MMN:SW,

PROC, SW231

N h...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:

h...MMN:CP113,PROC, CP890


End of procedure.

END





























A30808-X3074-A473-2-7620 EY503 - 1



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.









MMN:SW IN for information) must be used in the following manner in the present proce-dure:

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



EY503- 2 A30808-X3074-A473-2-7620











1 DOUBLE FAILURE OF A NON-GENERATION FILE.



@################## @#############################



-----------------+--------+------+-------------+-------------+-----+----

filename @####### @##### @############ @############ @### @###


Decision block.

Are files defective, not valid, or not present which do not belong to a genera-

tion? Y h...3

N h...22

3 DOUBLE FAILURE OF A FILE NOT BELONGING TO A GENERATION.

SJ.SECDATA defective?

Is the file SJ.SECDATA defective, not valid or not present? Y h...4

N h...6


Update file SJ.SECDATA

b UPD SECDATA:command repetition EXEC’D


Cyclic IA file defective?

Is the file which is defective, not valid, or not present a cyclic IA file? Y h...6

N h...14











A30808-X3074-A473-2-7620 EY503 - 3


6 DOUBLE FAILURE OF A CYCLIC IA FILE.

Deactivate recording of call data.

b DISP IAFEAT;command repetition EXEC’D

- Cancel active features:

b CAN IAFEAT:TYPE=feature;DANGEROUS COMMAND CANIAFEAT READY TO EXECUTE<


7 DOUBLE FAILURE OF ACYCLIC IA FILE.


b DISP FILE:FILE=IA.;command repetition EXEC’D

@################## @#############################



-----------------+--------+------+-------------+-------------+-----+----

filename @####### @##### @############ @############ @### @###

: : : :

: : : :


IA file still present?

Is the IA file still present? Y h...9

N h...10


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:

b 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 DACT FNS:FNS=fns;

b CAT FILE:FILE=new_name/old_name;command repetition EXEC’D























EY503- 4 A30808-X3074-A473-2-7620


10 DOUBLE FAILURE OF A CYCLIC IA FILE

Activate call data recording.

b ACT IAFEAT:TYPE=feature,SIZE=size;DANGEROUS COMMAND ACTIAFEAT READY TO EXECUTE<





@################## @#############################



-----------------+--------+------+-------------+-------------+-----+----

filename @####### @##### @############ @############ @### @###

: : : :

: : : :


Another cyclic IA file defective?

Is there another cyclic IA file that is defective, not valid, or not present? Y h...6

N h...13


Delete file.

If the tape saving of the IA files was successful, delete the files that were

renamed. If the files couldn’t be saved successfully and therefore are to be kept

for later postprocessing, the procedure is to be continued with:

b DEL FILE:FILE=new name;command repetition EXEC’D

14 DOUBLE FAILURE OF A LOG FILE.

Defective LOG file?

Is the file which is defective, not valid or not present a a LOG file? Y h...15N h...17














A30808-X3074-A473-2-7620 EY503 - 5



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 corre-

sponding 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:

b RSET LOG;

DANGEROUS COMMAND RSETLOG READY TO EXECUTE<


Because of a protected file name segment it may be necessary to change the

appropriate file attribute before executing the following command:

b DACT FNS:FNS=fns;DANGEROUS COMMAND RSETLOG READY TO EXECUTE<

b ;


b SET LOG:SIZE=24,ERASE=YES,FILE=logfilename;DANGEROUS COMMAND SETLOG READY TO EXECUTE<

b ;

Delete the file renamed previously:

b DEL FILE:FILE=new name;command repetition EXEC’D


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:




When Procedure SW210 has been completed successfully, continue procedure

EY503 with:

h...17






















EY503- 6 A30808-X3074-A473-2-7620


17 DOUBLE FAILURE OF A GENERAL FILE.

Another cyclic file defective or invalid?

Is there another cyclic file that is defective, not valid, or not present? Y h...18N h...22


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 DACT FNS:FNS=fns;



CA-file defective?

Is the file which is defective, not valid or not present a CA-file? Y h...20

N h...22


Save meters.

b SAVE MET;command repetition EXEC’D

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:

b TRANS FILE:FILE=name,VSNS=SA1TAP;command repetition ACCEPTED


displayed after the end of tape was reached, proceed with continuation tape

handling and then enter: MOUNT TAPE:DEV=MTD-0;


SENDER : @#######

RECEIVER : @#######

START START



-+-----------------+------+-----+-+-----+-+--+----+---------+-----+-----

S @######## SAxTAP TR @ @#### @ @# @### @######## @#### @####R @######## @##### CRD @ @#### @ @# @### @######## @#### @####

















A30808-X3074-A473-2-7620 EY503 - 7






@################## @#############################



-----------------+--------+------+-------------+-------------+-----+----

filename @####### @##### @############ @############ @### @###

: : : :

: : : :


All files available?

Are all save tape files available on disk? Y h...24

N h...17


Delete files.

Delete the files renamed previously:

b DEL FILE:FILE=new name;



Update security data.

Update access security data:

b UPD SECDATA;command repetition EXEC’D


Symptoms to be saved?Are symptoms to be saved on tape? Y i ...MMN:SW,

PROC, SW231

N h...27




















EY503- 8 A30808-X3074-A473-2-7620


27 SYMTOM SAVING:

Postprocessing.

Note: It must 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 the

MMN:CP113:

h...MMN:CP113,PROC, CP890

End of procedure.


END



A30808-X3074-A473-2-7620 EY504 - 1



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 oper-

ations 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.









MMN:SW IN for information) must be used in the following manner in the present proce-

dure:

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,







EY504- 2 A30808-X3074-A473-2-7620











1 DOUBLE DISK FAILURE:

Configuration MDD.

Configure the MDD which was diagnosed, or which was cleared of faults to

OST = ACT :

b 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;


In each case continue with following command:

b CONT MDDACT:LABEL;command repetition EXEC’D

CONFIGURATION MDD-x FROM MBL TO ACT

















A30808-X3074-A473-2-7620 EY504 - 3




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:

b 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






EY504- 4 A30808-X3074-A473-2-7620




In direct mode the following command is to be typed without the path-name “ - DISKFAIL”:

In the following T RANS SYFILE c ommand 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 D ISP GEN : V SN =SA1TAP;)

b TRANS SYFILE - DISKFAIL:GEN=actgen,VSN=SA1TAP;command repetition ACCEPTED

If the message: PLEASE MOUNT CONTINUATION TAPE TO VSN = @#####




TRANSFER RESULT



-+-----------------+--------+------+------+----------+---------+--------

@ 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) trans-

ferred? (see the expected output mask) Y h...8

N h...5
























A30808-X3074-A473-2-7620 EY504 - 5



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


In direct mode the following command is to be typed without the path-name “ - DIAG ”:

b DIAG MDD- DIAG:MDD=x;command repetition EXEC’D

b CONF MDD:MDD=x,OST=ACT;command repetition EXEC’D



Decision of continuation tape.

Was continuation tape handling performed in the exchange when the APS quar-

terly saving was done? Y h...7

N h...3


Mount tape.

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)

h...3


Update semipermanent data.

b UPD GEN;command repetition ACCEPTED

Was update of semipermanent database successfully executed (EXEC’D)? Y h...10N h...9





















EY504- 6 A30808-X3074-A473-2-7620


9 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 DACT FNS

b DACT FNS:FNS=X;DANGEROUS COMMAND DACTFNS READY TO EXECUTE<











A30808-X3074-A473-2-7620 EY504 - 7




IMPORTANT: The following TRANS FILE command is acknowledged with “PART. EXEC’D“

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):

b TRANS FILE:FILE=X,VSNS=SA1TAP;command repetition ACCEPTED

If the message: PLEASE MOUNT CONTINUATION TAPE TO VSN = @#####



command repetition PART.EXEC’D

SENDER : @#######

RECEIVER : @#######

START START



-+-----------------+------+-----+-+-----+-+--+----+---------+-----+-----

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 @ @#### @ @# @### @######## @#### @####

: : :



















EY504- 8 A30808-X3074-A473-2-7620






@################## @#############################



-----------------+--------+------+-------------+-------------+-----+----

CG.SA.xxxxx @####### @##### @############ @############ @### SAM

: : : : : : :

CG.SA.yyyyy @####### @##### @############ @############ @### SAM

D9.VLRAL @####### @##### @############ @############ @### SAM

HF.xxxxxx @####### @##### @############ @############ @### CYCIA.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


All files available.

Are all APS quarterly save tape files available on disk? Y h...15

N h...14








A30808-X3074-A473-2-7620 EY504 - 9



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


In direct mode the following command is to be typed without the path-name

“ - DIAG”:

b DIAG MDD -DIAG:MDD=x;command repetition EXEC’D

b CONF MDD:MDD=x,OST=ACT;command repetition EXEC’D


h...3


Load MTD.

Mount and load the last tape for APS routine saving.


Tape to disk transfer of the APS Routine save tape.

b TRANS FILE:FILE=CA.ST.UCHA,VSNS=LOGTAP;command repetition ACCEPTED


SENDER : @#######

RECEIVER : @#######























EY504- 10 A30808-X3074-A473-2-7620


START START



-+-----------------+------+-----+-+-----+-+--+----+---------+-----+-----S CA.ST.UCHA LOGTAP TR @ @#### @ @# @### @######## @#### @####

R CA.ST.UCHA @##### CRD @ @#### @ @# @### @######## @#### @####


Activate protected file name segments.

b ACT FNS:FNS=X;DANGEROUS COMMAND DANGEROUS COMMAND ACTFNS READY TO EXECUTE<



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? Y h...20N h...19


Manual Initialstart.

After response from the next higher TAC-level a Manual Initial Start from a back-

ground memory is to be executed according to procedure EY150 block 36.

(Decision block):

Continue here, after execution of EY150: i....EMCYMN,PROC, EY150

For users of the function ” Manual on PC ” : the branch back to this block is

made via menu item DISPLAY/HISTORY.


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!













A30808-X3074-A473-2-7620 EY504 - 11



Postprocessing for IA-files.

Display features:b DISP IAFEAT;


Cancel all active features:

b CAN IAFEAT:TYPE=feature;DANGEROUS COMMAND CANIAFEAT READY TO EXECUTE<


Create file again by activating the features:

b ACT IAFEAT:TYPE=feature,SIZE=size;DANGEROUS COMMAND ACTIAFEAT READY TO EXECUTE<



Postprocessing.

It must 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.

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.


APS quarterly saving is to be executed according to procedure SW210. h...MMN:SW,PROC, SW210
















EY504- 12 A30808-X3074-A473-2-7620



END



A30808-X3074-A473-2-7620 EY710 - 1


3.21 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 !


The output is to be confirmed with +

MDD-x = last failed MDDMDD-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 fileand is loaded in the IOPLAU from the CP. This means that the IOPLAU must be treat

separately in the case of double disk failure.

1 Decision block

Was this procedure entered from one of the following procedures : CP810,

CP861, CP868 or CP880 ? Y h...2

N h...3





EY710- 2 A30808-X3074-A473-2-7620


2 Connector

With connector A : h...17

With connector B : h...45

3 Decision block

Are two OMTs present ? Y h...6N h...4

4 Decision block

Is there to be cleared of faults in the module frame IOC / IOP-0 ? Y h...5

N h...6

5 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.

b CONF OMT:OMT=0,OST=MBL;

The command is repeated with the added comment: EXEC'D

b STOP MDDACT;

Interruption of possible running activation Ignore output

6 Status request CP113

b STAT SSP;


7 Configure MDD-x to MBL



8 Configure MDD-y to MBL

b CONF MDD:MDD=y,OST=MBL;


9 Decision block

Is one IOC-x in OST=UNA ? Y h...10

N h...17


















A30808-X3074-A473-2-7620 EY710 - 3


10 Decision block

Are IOPLAU available ? Y h...11

N h...13

11 Fault clearance of the x branch

b DISP IOC:IOC=x;

Configuration of all IOPLAU of the defect IOC to PLA

b CONF IOP:IOP=IOPLAU-no,OST=MBL;

b CONF IOP:IOP=IOPLAU-no,OST=PLA;

The following system responses are possible:

Reaction 1R:


Reaction 2R:

The command is repeated with the added comment: NOT EXEC'D

Continue according to the system reaction

– 1R h...13

– 2R h...12

12 Configure all IOPLAU

b DISP IOP:IOP=IOPLAU-x;

Configuration of all LAU’s of the defect and redundant IOPLAU to MBL

b CONF LAU:LAU=no,OST=MBL;




13 Configure IOC-x to MBL

b CONF IOC:IOC=x,OST=MBL;




























EY710- 4 A30808-X3074-A473-2-7620


14 Diagnose IOC-x

In direct mode the following command is to be typed without the pathname

“ - DIAG “:

b DIAG IOC-DIAG:IOC=x;


Reaction 1R:


END OF DIAGN. WITHOUT FAILURE

Reaction 2R:


END OF DIAGNOSIS WITH FAILURE


– 1R h...16 – 2R h...15

15 Continue

continue in h...MMN:CP113,PROC, CP810

After successful fault clearance return to procedure EY710 connector A

16 Configure IOC-x to ACT

b CONF IOC:IOC=x,OST=ACT;


17 Decision block

Is one IOPMDD-x in OST=UNA ? Y h...18

N h...25

18 Decision block

Are IOPLAU available ? Y h...19N h...21













A30808-X3074-A473-2-7620 EY710 - 5



b DISP IOC:IOC=x;





Reaction 1R:


Reaction 2R:



– 1R h...21 – 2R h...20








21 Configure IOPMDD-x to MBL

b CONF IOP:IOP=IOPMDD-x,OST=MBL;




























EY710- 6 A30808-X3074-A473-2-7620


22 Diagnose IOPMDD-x


“ - DIAG “:

b DIAG IOP-DIAG:IOP=IOPMDD-x;


Reaction 1R:



Reaction 2R:




– 1R h...24 – 2R h...23

23 Continue


or



24 Configure IOPMDD-x to ACT

b CONF IOP:IOP=IOPMDD-x,OST=ACT;














A30808-X3074-A473-2-7620 EY710 - 7


25 Diagnose MDD-x

The following command entry including TA = T6 is mandatory:


“ - DIAG “:

b DIAG MDD-DIAG:MDD=x,TA=T6;


Reaction 1R:



Reaction 2R:




– 1R h...29 – 2R h...26

26 Decision block

Is the power supply suspect ? Y h...27N h...36

27 Power

Restore power supply

Switch on power

Wait 1 - 3 minutes









EY710- 8 A30808-X3074-A473-2-7620


28 Diagnose MDD-x



“ - DIAG “:



Reaction 1R:



Reaction 2R:




– 1R h...29 – 2R h...36

29 Configure MDD-x to ACT


The command is repeated with the added comment: ACCEPTED

Is the actual generation valid and complete on the disk ? Y h...30

N h...31












A30808-X3074-A473-2-7620 EY710 - 9


30 Continue MDDACT

b CONT MDDACT;


Reaction 1R:


Reaction 2R:



– 1R h...32 – 2R h...36

31 Stop MDDACT

b STOP MDDACT; h...36

32 Save generation

b UPD GEN;


b DISP FILE;


33 Decision block

Was DISP FILE; executed and are all files valid ? Y h...34N h...35

34 Comment

MDD -x is fault-free h...69

35 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 ? Y h...38N h...47


















EY710- 10 A30808-X3074-A473-2-7620


38 Decision block


N h...41

39 Fault clearance of the y branch

b DISP IOC:IOC=y;





Reaction 1R:


Reaction 2R:



– 1R h...41

– 2R h...40


b DISP IOP:IOP=IOPLAU-y;






41 Configure IOC-y to MBL

b CONF IOC:IOC=y,OST=MBL;




























A30808-X3074-A473-2-7620 EY710 - 11


42 Diagnose IOC-y


“ - DIAG “:

b DIAG IOC-DIAG:IOC=y;


Reaction 1R:



Reaction 2R:




– 1R h...44 – 2R h...43

43 Continue


After successful fault clearance return to procedure EY710 connector B

44 Configure IOC-y to ACT

b CONF IOC:IOC=y,OST=ACT;


45 Decision block

Is one IOPMDD-y in OST=UNA ? Y h...46

N h...53

46 Decision block














EY710- 12 A30808-X3074-A473-2-7620



b DISP IOC:IOC=y;





Reaction 1R:


Reaction 2R:



– 1R h...49 – 2R h...48








49 Configure IOPMDD-y to MBL

b CONF IOP:IOP=IOPMDD-y,OST=MBL;




























A30808-X3074-A473-2-7620 EY710 - 13


50 Diagnose IOPMDD-y


“ - DIAG “:

b DIAG IOP-DIAG:IOP=IOPMDD-y;


Reaction 1R:



Reaction 2R:




– 1R h...52 – 2R h...51

51 Continue


or



52 Configure IOPMDD-y to ACT

b CONF IOP:IOP=IOPMDD-y,OST=ACT;














EY710- 14 A30808-X3074-A473-2-7620


53 Diagnose MDD-y



“ - DIAG “:

b DIAG MDD-DIAG:MDD=y,TA=T6;


Reaction 1R:



Reaction 2R:




– 1R h...57 – 2R h...54

54 Decision block


55 Power


Switch on power

Wait 1 - 3 minutes









A30808-X3074-A473-2-7620 EY710 - 15


56 Diagnose MDD-y



“ - DIAG “:



Reaction 1R:



Reaction 2R:




– 1R h...57 – 2R h...65

57 Configure MDD-y to ACT

b CONF MDD:MDD=y,OST=ACT;



N h...59












EY710- 16 A30808-X3074-A473-2-7620


58 Continue MDDACT

b CONT MDDACT;


Reaction 1R:


Reaction 2R:



– 1R h...60 – 2R h...65

59 Stop MDDACT


60 Save generation

b UPD GEN;


b DISP FILE;


61 Decision block


62 Comment

MDD -y is fault-free h...69

63 Power

Switch off power at MDD-y and wait for the failure message.

Switch on power

Wait 1-3 minutes
























A30808-X3074-A473-2-7620 EY710 - 17


65 Diagnose MDD-y


“ - DIAG “:

b DIAG MDD-DIAG:MDD=y;


Reaction 1R:



Reaction 2R:




– 1R h...EMCYMN,PROC, EY500

– 2R h...66

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













EY710- 18 A30808-X3074-A473-2-7620


67 Diagnose MDD-y


“ - DIAG “:



Reaction 1R:



Reaction 2R:





– 2R h...68

68 Cable suspect

With cable details h...NM:CP113,PROC, CP0050


b STAT SSP;


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
















A30808-X3074-A473-2-7620 EY730 - 1


3.22 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 becontinued 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 theCP, 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.

1 Decision block

Was this procedure entered from one of the following procedures : CP910,

CP968 or CP980 ? Y h...2

N h...3

2 Connector

With connector A : h...17With connector B : h...45



EY730- 2 A30808-X3074-A473-2-7620


3 Decision block

Are two OMTs present ? Y h...6

N h...4

4 Decision block

Is there to be cleared of faults in the module frame IOC / IOP-0 ? Y h...5N h...6

5 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.

b CONF OMT:OMT=0,OST=MBL;


b STOP MDDACT;

Interruption of possible running activation

Ignore output


b STAT SSP;


7 Configure MDD-x to MBL






9 Decision block

Is one IOC-x in OST=UNA ? Y h...10

N h...17

10 Decision block


N h...13


















A30808-X3074-A473-2-7620 EY730 - 3



b DISP IOC:IOC=x;





Reaction 1R:


Reaction 2R:



– 1R h...13 – 2R h...12








13 Configure IOC-x to MBL

b CONF IOC:IOC=x,OST=MBL;




























EY730- 4 A30808-X3074-A473-2-7620


14 Diagnose IOC-x


“ - DIAG “:

b DIAG IOC-DIAG:IOC=x;


Reaction 1R:



Reaction 2R:




– 1R h...16 – 2R h...15

15 Continue

continue in h...MMN:CP113C,PROC, CP910


16 Configure IOC-x to ACT

b CONF IOC:IOC=x,OST=ACT;


17 Decision block

Is one IOPUNI-x in OST=UNA ? Y h...18

N h...25

18 Decision block














A30808-X3074-A473-2-7620 EY730 - 5



b DISP IOC:IOC=x;





Reaction 1R:


Reaction 2R:



– 1R h...21 – 2R h...20








21 Configure IOPUNI-x to MBL

b CONF IOP:IOP=IOPUNI-x,OST=MBL;




























EY730- 6 A30808-X3074-A473-2-7620


22 Diagnose IOPUNI-x


“ - DIAG “:

b DIAG IOP-DIAG:IOP=IOPUNI-x;


Reaction 1R:



Reaction 2R:




– 1R h...24 – 2R h...23

23 Continue


or



24 Configure IOPUNI-x to ACT

b CONF IOP:IOP=IOPUNI-x,OST=ACT;














A30808-X3074-A473-2-7620 EY730 - 7


25 Diagnose MDD-x



“ - DIAG “:



Reaction 1R:



Reaction 2R:




– 1R h...29 – 2R h...26

26 Decision block


27 Power


Switch on power

Wait 1 - 3 minutes









EY730- 8 A30808-X3074-A473-2-7620


28 Diagnose MDD-x



“ - DIAG “:



Reaction 1R:



Reaction 2R:




– 1R h...29 – 2R h...36

29 Configure MDD-x to ACT




N h...31












A30808-X3074-A473-2-7620 EY730 - 9


30 Continue MDDACT

b CONT MDDACT;


Reaction 1R:


Reaction 2R:



– 1R h...32 – 2R h...36

31 Stop MDDACT


32 Save generation

b UPD GEN;


b DISP FILE;


33 Decision block


34 Comment

MDD -x is fault-free h...69

35 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 ? Y h...38N h...45


















EY730- 10 A30808-X3074-A473-2-7620


38 Decision block


N h...41


b DISP IOC:IOC=y;





Reaction 1R:


Reaction 2R:



– 1R h...41

– 2R h...40








41 Configure IOC-y to MBL

b CONF IOC:IOC=y,OST=MBL;




























A30808-X3074-A473-2-7620 EY730 - 11


42 Diagnose IOC-y


“ - DIAG “:

b DIAG IOC-DIAG:IOC=y;


Reaction 1R:



Reaction 2R:




– 1R h...44 – 2R h...43

43 Continue

continue in h...MMN:CP113C,CP910


44 Configure IOC-y to ACT

b CONF IOC:IOC=y,OST=ACT;


45 Decision block

Is one IOPUNI-y in OST=UNA ? Y h...46

N h...53

46 Decision block














EY730- 12 A30808-X3074-A473-2-7620



b DISP IOC:IOC=y;





Reaction 1R:


Reaction 2R:



– 1R h...49 – 2R h...48








49 Configure IOPUNI-y to MBL

b CONF IOP:IOP=IOPUNI-y,OST=MBL;




























A30808-X3074-A473-2-7620 EY730 - 13


50 Diagnose IOPUNI-y


“ - DIAG “:

b DIAG IOP-DIAG:IOP=IOPUNI-y;


Reaction 1R:



Reaction 2R:




– 1R h...52 – 2R h...51

51 Continue


or



52 Configure IOPUNI-y to ACT

b CONF IOP:IOP=IOPUNI-y,OST=ACT;














EY730- 14 A30808-X3074-A473-2-7620


53 Diagnose MDD-y



“ - DIAG “:



Reaction 1R:



Reaction 2R:




– 1R h...57 – 2R h...54

54 Decision block


55 Power


Switch on power

Wait 1 - 3 minutes









A30808-X3074-A473-2-7620 EY730 - 15


56 Diagnose MDD-y



“ - DIAG “:



Reaction 1R:



Reaction 2R:




– 1R h...57 – 2R h...65

57 Configure MDD-y to ACT

b CONF MDD:MDD=y,OST=ACT;



N h...59












EY730- 16 A30808-X3074-A473-2-7620


58 Continue MDDACT

b CONT MDDACT;


Reaction 1R:


Reaction 2R:



– 1R h...60 – 2R h...65

59 Stop MDDACT


60 Save generation

b UPD GEN;


b DISP FILE;


61 Decision block


62 Comment

MDD -y is fault-free h...69

63 Power

Switch off power at MDD-y and wait for the failure message.

Switch on power

Wait 1-3 minutes
























A30808-X3074-A473-2-7620 EY730 - 17


65 Diagnose MDD-y


“ - DIAG “:



Reaction 1R:



Reaction 2R:





– 2R h...66

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













EY730- 18 A30808-X3074-A473-2-7620


67 Diagnose MDD-y


“ - DIAG “:



Reaction 1R:



Reaction 2R:





– 2R h...68

68 Cable suspect

With cable details h...NM:CP113,PROC, CP0050


b STAT SSP;


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
















A30808-X3074-A473-2-7620 EY920 - 1


3.23 Emergency Situation for CCNC Data

EY920












EY920- 2 A30808-X3074-A473-2-7620



1 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 neces-

sary 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

2 Decision block

What types of files are faulty?

– Only SY.SIMP h...6 – Only SY.PSW.T09x h...3 – Both SY.SIMP and SY.PSW.T09x h...6



A30808-X3074-A473-2-7620 EY920 - 3


3 Preparation for restoration of the SY.PSW.T09x file(s)

Is a golden generation available that corresponds to the described status? Y h...5

N h...4

4 Special fault clearance

Special fault clearance if necessary

5 Continue fault clearance

Prepare the tape with the golden generation.

In procedure EY500 the corresponding suspect file must be replaced.


6 Fallback to a backup-APSFall 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)? Y h...7

N h...8

7 The fault clearance was successful

The fault clearance was successful because of the

recovery with 'fallback generation'.h...10


Was a (error) message again output with hints to this procedure

during loading of CCNC? 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.

h...EMCYMN,

PROC, EY190

10 Decision block

Was this procedure entered with an instruction to return to the calling proce-

dure? Y h...11

N h...MMN:SYP,

PROC,

PROC:SYP101





















EY920- 4 A30808-X3074-A473-2-7620







END



A30808-X3074-A473-2-7620 EY930 - 1


3.24 Emergency Situation for Trunk Data

EY930












EY930- 2 A30808-X3074-A473-2-7620



1 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 suffi- cient if data in CP memory were corrupted).

- Fallback to a backup APS. Ensure that a save-tape is used which was gener-

ated 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 h...2



A30808-X3074-A473-2-7620 EY930 - 3


2 Decision block

Has diagnostics been started for the CCNP during the course of this fault clear-

ance? Y h...3N h...5


Have the suspect modules been replaced? Y h...4

N h...8


Suspect modules have already been replaced. However, the fault has not been

cleared.

h...16


Is the CCNP to be diagnosed in OST = MBL? Y h...7N h...6

6 Configure CCNP

b CONF CCNC:UNIT=CCNP-no,OST=MBL; i ...MMN:CCS7,CONF:CN



7 Diagnose CCNP

b 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 h...7 – Diagnose was executed. The processor is all right . h...12 – Diagnose was executed. The processor is not all right . h...8


Find the defective modules in the fault number catalog FNRK: i ...NM:CCS7



Does fault list FNRK:* only refer to this procedure? Y h...9

N h...10









http://a002h439.pdf/



http://a002h439.pdf/







EY930- 4 A30808-X3074-A473-2-7620



Thus no suspect modules are specified. h...16


It is first necessary to make sure that the fault is not caused by a faulty module i....MMN:CCS7,CN050



Was it possible to clear the fault by replacing the modules? Y h...13N h...11


Suspect modules have already been replaced. However, the fault has not beencleared

h...16

12 Configure CCNP

b CONF CCNC:UNIT=CCNP-no,OST=STB; i....MMN:CCS7,CONF:CN



13 Decision block

Have both CCNPs been reloaded after the fault clearance? Y h...27N h...14

14 Soft CCNP switchover

b CONF CCNC:UNIT=CCNP-no,OST=ACT; i....MMN:CCS7,CONF:CN



15 Configure CCNP

b CONF CCNC:UNIT=CCNP-no,OST=MBL; h...7

16 Decision block

Was a RECOV SSP already started during this procedure? Y h...24

N h...17
























A30808-X3074-A473-2-7620 EY930 - 5


17 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;

b STAT TRUNK:TGNO=X,STATUS=NSYNP;

Are there one or more trunks previously determined in status NSYNP? Y h...18N h...20


Is the number of trunks to be canceled and created again determined within

reasonable limits? 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? Y h...7N h...20

20 Load the CP memory from MDD

Was a RECOV SSP NSTART2 already started during this procedure? Y h...24

N h...21


The effect of the recovery is that the CP memory is reloaded again from thedisk. It is a precondition that all CP units are redundant. Are all CPs redundant? Y h...23

N h...22


Faults in the CP area must be cleared first i ...MMN:CP113








EY930- 6 A30808-X3074-A473-2-7620



A NSTART2 recovery according to MMN:SW must be made. continue here, after

execution of: MMN:SW, register CP113, chapter SW120

i....MMN:CP113



Wait 15 minutes (Synchronization of all trunks lasts approx. 15 min. after

loading)

h...7

24 Fallback to a backup-APS

Fall back to the 'fallback generation' is necessary. This is done by means of

procedure EY190

i....EMCYMN,EY190



Was the recovery with the 'fallback generation successful (both CCNP are

loaded)? Y h...25N h...26


The fault clearance was successful because of the recovery with 'fallback gener-

ation'. 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 proce-

dure? Y h...28

N h...MMN:SYP,

PROC,

PROC:SYP101



















A30808-X3074-A473-2-7620 EY930 - 7



END



EY930- 8 A30808-X3074-A473-2-7620




A30808-X3074-A473-1-7620 TABIN - 1


4 Tables (TAB)

This manual does not contain tables.



TABIN- 2 A30808-X3074-A473-1-7620





5 Appendix (APP)

This manual does not contain an appendix.

siemens emergency cases

Documents