DocumentSW

Nonstandard MaintenanceSoftware

NM:SW

A30828-X1187-N585-2-7620

2 A30828-X1187-N585-2-7620

NM:SW Nonstandard MaintenanceSoftware

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

Copyright (C) Siemens AG 2004-2005.Issued by the Information and Communication Networks GroupHofmannstrae 51D-81359 Mnchen

Technical modifications possible.Technical specifications and features are binding only insofar asthey are specifically and expressly agreed upon in a written contract.

A30828-X1187-N585-2-7620 3


NM:SW

Reason for UpdateSummary:

Details:

Chapter/Section Reason for Update

Several procedures Small corrections

Issue HistoryIssueNumber

Date of issue Reason for Update

1 12/2004 New

2 04/2005 Update

4 A30828-X1187-N585-2-7620


A30828-X1187-N585-2-7620 5


NM:SW

This document consists of a total of 168 pages. All pages are issue 2.

Contents1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

IN-NM1.1 Recovery description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.2 Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191.3 Progress Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321.4 IMON. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361.5 Recovery trace points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

2 Procedures (Preface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572.1 Measures after recovery (for NE with SSNC) . . . . . . . . . . . . . . . . . . . . . . . 59

SW1102.2 Measures after recovery (for NE without SSNC) . . . . . . . . . . . . . . . . . . . . 63

SW1202.3 Replacement of non-resident libraries

(for NE with SSNC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67SW422

2.4 Exchange of PSW files (for NE with SSNC) . . . . . . . . . . . . . . . . . . . . . . . . 85SW441

2.5 Expansion of the database area using ODAGEN(for NE with SSNC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

SW4512.6 Replacement of non-resident libraries

(for NE without SSNC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111SW462

2.7 Exchange of PSW files (for NE without SSNC) . . . . . . . . . . . . . . . . . . . . 133SW481

2.8 Expansion of the database area using ODAGEN(for NE without SSNC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

SW491

6 A30828-X1187-N585-2-7620


A30828-X1187-N585-2-7620 7


NM:SWIN-NM

1 Introduction

IN-NM

1.1 Recovery description

Extensive monitoring and self-checking processes, which can be activated in the caseof failures, are integrated into the Application Program System (APS).The location,gravity and subsequent results of the fault detected are evaluated and on the basis ofthis evaluation recoveries, with varying depths of penetration are started.In the case of particularly serious system malfunctions, the recovery selected by thesystem sometimes has no effect and is automatically followed by one or more deeplypenetrating recoveries. This is called recovery escalation.The operator can call up and activate all recoveries (with the exception of SASDAT,ISTART1B and NSTART1B) by means of MML command. Such calls, however, are aserious intervention in the system which impair or interrupt call processing. Thesecommands may only be used during operation if the self-checking equipment fails orimplausible program states or endless loops occur.In each case an attempt should be made to clear the fault by calling SSP recovery(NSTART), as this recoveries impair call processing less than SYSTEM recovery(ISTART). Only if this does not succeed is it permissible to call the SYSTEM recovery.For every Recovery a recovery message is output at the OMT. Additionally the recoverymessages are stored in the history file HF.ARCHIVE with a entry sequence number. Themessages can be read out using the entry number shown in the message (see SW282).

8 A30828-X1187-N585-2-7620

NM:SWIN-NM


1.1.1 Recovery initiation

The following table shows the possibilities to initiate the recoveries:

* Started by recovery peripheral after total outage of periphery** Manual startup with LTG code loading*** After pressing BOOT key an ISTART 2 is initiated. If the operator selects the nameof a generation older than the actual generation an ISTART 2G is carried out.

1.1.2 Recovery effects

The effects on the system depend on the recovery that is carried out. The SSP recoveryhave effects on the CP only. The SYSTEM recoveries have effects on the total system.The important effects of the single recoveries are described in the following sections.

1.1.2.1 Plausibility failure (SASDAT)In case of plausibility failure only one process is involved. When a failure is detected, thecurrent process is temporarily stopped to save error symptoms in the file SG.SESYMP.After that the process continues running. SASDAT has no effects on i.e. call setup,charge meters or AMA data.

automatic start per: manual start per:

software errortreatment

hardware errortreatment

MML command BOOT key

NSTART 0 NSTART 0 NSTART 0 ---NSTART 1 NSTART 1 NSTART 1 ---NSTART 2 NSTART 2 NSTART 2 ---NSTART 3 NSTART 3 NSTART 3 ---NSTART 1B --- --- ---ISTART 1 ISTART 1 ISTART 1 ---ISTART 2(F)* ISTART 2 ISTART 2 ISTART 2(R)**

ISTART 2(G) ***--- --- ISTART 2R ------ --- ISTART 2F ISTART 2FISTART 2G -- ISTART 2GISTART 1B --- --- ---

A30828-X1187-N585-2-7620 9


NM:SWIN-NM

1.1.2.2 SSP recovery (NSTART)The effects of SSP recoveries are described in the following figure:

Fig. 1.1 Effects of SSP recovery

- all non call processing CP processes are started new (call processing processes keep running)- existing connections are retained- one transient call may be lost (BAPM)- AMA data are not lost- charges are not lost

- load semipermanent data in the CP

- all processes in BAP and CAP are started new- in BAP and CAP a maximum of only one transient call (each) may be lost- MB, SYP and CCG are taken into the IOCP scan cycle

NSTART0

NSTART1

NSTART1B

NSTART2

- load of program code for all resident processes only in exeptional case- initialisation of all CP data- assemble list of active MCH in the IOCP NSTART3

- all processes are interrupted and a reduced number of processes are started only- a restricted number of processes are restarted- MB, SYP and CCG are taken into the IOCP scan cycle

- Emergency situation: start of basic operation !

10 A30828-X1187-N585-2-7620

NM:SWIN-NM


1.1.2.3 SYSTEM recovery (ISTART)The effects of SYSTEM recoveries are described in the following figure:

Fig. 1.2 Effects of SYSTEM recovery (1)

- no formatting of main memory- CP is loaded with actual APS generation- all CP processes are started- MB, SN and LTG are reset and activated (exeption: MB, SN and LTG in OST=PLA and MBL)- call setup is temporarily interrupted- existing connections are retained- DLU is reloaded with semipermanent data and both DLUsystems are started- AMA data and charges stored in the main memory are not lost (in keeping with CCITT specifications) ISTART1- formatting of main memory (exception: BOOT key initiation)- AMA data and charges stored in the background memory are not lost (in keeping with CCITT specifications)- LTG are loaded with semipermanent data (exception: LTG in OST= PLA or MBL)- CCNC is loaded with semipermanent code and data and CCNC unit are started ISTART2- no formatting of main memory- AMA data and charges stored in the main memory are not lost (in keeping with CCITT specifications)- LTG are loaded with semipermanent data and code (exception: LTG in OST= PLA or MBL) ISTART2R- no formatting of main memory (optionally in case of initiation via BOOT-key)- AMA data and charges stored in the main memory are not lost (in keeping with CCITT specifications)- LTG are loaded with semipermanent data and code (exception: LTG in OST= MBL) ISTART2F- formatting of main memory (execution: BOOT key initiation)- CP is loaded with former APS generation- AMA data and charges stored in the main memory are not lost (in keeping with CCITT specifications)- LTG are loaded with semipermanent data and code (exception: LTG in OST= PLA or MBL) ISTART2G

A30828-X1187-N585-2-7620 11


NM:SWIN-NM

Fig. 1.3 Effects of SYSTEM recovery (2)

- reaching basic operation- further effects as ISTART 1- all processes are restarted- only a reduced number of processec are started new

- Emergency situation: start of basic operation ! ISTART1B

12 A30828-X1187-N585-2-7620

NM:SWIN-NM


1.1.3 Recovery messages

1.1.3.1 Structure of recovery message

@###### RECOVERY INFORMATION

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

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

REQUESTED RECOVERY LEVEL : @#######PERFORMED RECOVERY LEVEL : @#######

CALLPROCESSING STARTED : @#######@

DURATION OF SERVICE INTERRUPTION : @####@ SECONDSRECOVERY DURATION : @####@ SECONDS

RESULT : @####################################################

SUPPLEMENTARY INFORMATION : @############################################### @############################################### @############################################### @############################################### @############################################### @############################################### @############################################### @###############################################

APS GENERATION : @#######

CRITICAL STATES---------------

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

A30828-X1187-N585-2-7620 13


NM:SWIN-NM

1.1.3.2 Output parameter

RECOVERY INFORMATIONThe recovery (SSP or SYSTEM) is output.REASONThe cause of recovery is output.

DATEThe date of recovery is print out. The question mark indicates a possible differencebetween system time and local time.

TIMEhour:minute:second of recovery is output (? means: time is insecure)UNITThe unit (BAP or CAP) in which the recovery was executed is output.REQUESTED LEVELThe requested level of the recovery is output. If there is a disparity betweenREQUESTED LEVEL and PERFORMED LEVEL an escalation to a more deeply pene-trating recovery took place.

PERFORMED LEVELThe performed level of the recovery is output. If there is a disparity betweenREQUESTED LEVEL and PERFORMED LEVEL an escalation to a more deeply pene-trating recovery took place.

CALLPROCESSING STARTEDThe line shows at what time call processing was resumed after completion of therecovery.(? means: time is insecure)RECOVERY DURATIONThis line indicates the duration of the interruption of call processing in seconds.

RESULTRecovery result is output.

APS GENERATIONThe APS generation used by recovery is print out. Normally this is the actual generation.In case of ISTART 2G it is the former (BACKUP or GOLDEN) generation.STATISTICSFault statistics from the recovery is output.

ERROR COUNTERThe value for error counter of software error treatment is output (normally no output).

14 A30828-X1187-N585-2-7620

NM:SWIN-NM


THRESHOLDThe defined value for threshold of software error treatment is output (normally nooutput).INTERVALThe value for interval in seconds is output.

CRITICAL STATESThe units which operation status has changed during recovery are listed. The output NO(MORE) DATA FOR DISPLAY AVAILABLE means that there are no (more) configura-tion faults.

A30828-X1187-N585-2-7620 15


NM:SWIN-NM

1.1.4 Recovery relevant procedures (EMCYMN and NM:SW)

Fig. 1.4 Recovery relevant Procedures (EMCYMN and NM:SW)

EY600

Fault clearance in CP basic operation

Fault clearance after ISTART1BEY601

Fault clearance after NSTART1BEY601

Measures after unsuccessful recovery

EY100

Manual initial start from MDD(actual generation)EY130

Manual initial start from MDD(fallback generation)EY290 -295

Emergency forCCNC data

EY920

Emergency fortrunk data

EY930

Rescue of backgroundmemory data

EY 170/171

Manual initial startfrom save medium

EY150/151

Measures after recoveryNSTART and ISTART 1/2

SW120

Installation recovery

SW140/141

EMCY

MN

NM

:SW

request from MMN:SW(PROC: SW380)

request from PROC: ENTRY

request from MMN:SW(PROC: SW380)saving of error symptoms

restoration of files onMDD (PROC: EY5xx)fault clearance accordingto MMN:CCS7 (PROC: CNxxx)

fault clearance accordingto MMN:CCS7 (PROC: CNxxx)

request from MMN:SW(PROC: SW380)

restoration of defective chargemeters according to MMN:SW(PROC: SW275)

saving of error symptoms

saving of error symptoms

16 A30828-X1187-N585-2-7620

NM:SWIN-NM


1.1.5 Recovery relevant Procedures (MMN:SW)

Fig. 1.5 Recovery relevant Procedures (MMN:SW)

1.1.6 Measures after output of recovery messages

The system maintenance philosophy does not call for system personnel to analyze andclear temporary software errors.Also, since no message statistics are kept and analyzed or "online dumps" analyzed onsite, it will not be possible in most cases to determine the type and location of an error.By automatically recording all recovery symptoms on the background memories in thehistory files, the system takes into account the fact that malfunctions caused by softwareerrors can only be analyzed and cleared by analyzing many different error symptomsand often only by long-term observation of faulty responses.

Plausibility failure

Measures by TAC (PROC: SW120)Evaluation ofrecovery message

NSTART 0-3

Measures by TAC (PROC: SW120)Measures by TAC

Measures by TAC (PROC: EY290)

Measures by TAC (PROC: EY600)

ISTART 1/2

ISTART

ISTART2G

NSTART1BNSTARt1B

SW380

Symptom saving Sending symptomsto TACSaving of error symptoms

Measures by TAC (PROC: SW120)

request from EMCYMN(PROC: EY290 - 295,EY150/154 etc.)

Restoration of defectivecharge meters

SW275

Saving the current APS

SW260 -267

Start-up test of the saved APS

SW261

A30828-X1187-N585-2-7620 17


NM:SWIN-NM

It is the duty of the maintenance personnel on site to save these files according toSaving of Error Symptoms and to send them to the specified diagnostic center for anal-ysis. Furthermore, the appropriate printer terminal printout, together with any previoushistory data must be saved every time a recovery message is output.In the case of serious malfunctions a software error report together with the printoutsmust be sent immediately to the specified diagnostic center for analysis. Otherwise theerror reports are sent collected to the diagnostic center. Further information arecollected in Saving of Error Symptoms.All measures that must be taken in case of recovery message output are described inSW330.

1.1.7 Special measures

Check List in the case of RecoveriesIn addition, the following questionnaire is to be discussed with TAC2:1. When were patches last incorporated into the APS? Which ones?2. Was the APS changed?3. Have extensive database activities been run? (e.g. ODAGEN, REGEN)4. Were HW/FW modifications carried out on central units before the recovery?5. Were central HW units configured? (by MML, through system status analysis after

HW failure)6. Were modules, frames, cables, etc. replaced during fault clearance?7. Were disk-copying procedures run? (e.g. ODAGEN expansion, configuration of IOC,

IOP:MDD, IOPUNI, IOPG, MDD)8. Was the message ALL DOUBLE FILES SYNCHRONIZED then output on the

OMT?9. Was a system expansion (e.g. CAP, MB, SN) performed?10. Were traffic measurement orders or scheduled test jobs executed? At what time did

they run?11. Were new features activated for the first time? (e.g. ISDN features, call-charge

features)12. Did the recovery occur during/after routine work at the exchange? (e.g. APS safe-

guarding, meter saving, maintenance)13. Have there been a large number of sporadic HW faults recently? (readout of

HF.MCP.HWERROR)14. Did errors occur recently during plausibility tests? (readout of AD.RESTART or

HF.ARCHIVE)

18 A30828-X1187-N585-2-7620

NM:SWIN-NM


Recovery Measures for ClearanceThe following recovery measures should only be carried out by trained and experiencedpersonnel after consultation with the Service department responsible or the systemcompanys TAC. The faults listed in the table are only examples of the malfunctions thatcan be removed with the recovery level given in the Measures column.Recovery should only be started after analysis of the malfunction. An NSTART orISTART should only be started as a last resort.If this recovery does not remove the malfunction, the next highest level should be usedafter consultation.A description of all recovery levels with effects of the system are described in NM:SWchapter 1.1.2Procedures in the Emergency Manual cover the steps to be taken after an unsuccessfulrecovery, manual recovery of disk/medium, the USTART2G and the entire or partialdisconnection of the system.If there is the risk of a recovery escalation or a rolling recovery and the fault cannot becleared at short notice, commands DISP/SET/RSET RECESC can be used to changethe parameters for recovery escalation. However, these commands may only be usedunder the supervision of the system companys TAC.

Examples of faults Action Measures

- Hanging job, call processing is not affected (commands STOP JOB or CAN JOB not successful),- Low-priority closed loop (evident from UNITEST, process change option),- System is no longer operable, no more inputs possible

- Release and cancel job queue- New start of all non- call- processing processes

NSTART0

RESET atBAP-M(ASO with NSTART0)

- As above, call processing is affected - Release and cancel job queue- New start of call processing

NSTART1

- Analysis showed that semipermanent data in the memory have been mutilated

- Reload semipermanent data- Reset and new start of all processes- Data initialization

NSTART2

- Code or data in the memory are mutilated; an auxiliary patch that was not updated on disk is suspect

- Re-load semipermanent data and code from the disk

NSTART3

- No dial tone, faults in peripheral units - Reset peripheral units ISTART1- Many peripheral units are faulty, many LTGs in UNA

- Parallel loading of LTGs Installation of faulty LTGs

ISTART2R

A30828-X1187-N585-2-7620 19


NM:SWIN-NM

1.2 Data Collection

1.2.1 Data Collection following unsuccessful ISTART because of SWerror

The Data Collection function safeguards important error data on the background memo-ries if a ISTART recovery is interrupted because of SW error.In following cases an additional symptom saving are possible:- ISTART2 direct start with SWSG- Total failure of all peripheral units during ISTART- Recovery interruption of INSTALLATION recovery with recovery >= NSTART0 because of SWSGFor the sake of dynamics and operation reliability, this safeguarding is carried out inbinary form. A readable title text is inserted in front of every data block so that the datacan be retrieved.As these data cannot be read in the stored form, they must first be edited. This is donewithin the MMN:SW Procedure 231 with the help of command files.Following files are automatically created by the system:DC.V00 to DC.V03 are generated on MDD-0 and DC.V04 to DC.V07 on MDD-1 assingle files.In the case of escalation within basic operation (ISTART1B -> ISTART1B) files DC.B00and DC.B01 are created.They can only be read out after preparation as DD. files in ASCII format (see also Savingof Error Symptoms).

- Analysis showed that call-charge data in the CMY have been mutilated

- Format the RAM ISTART2

Examples of faults Action Measures

20 A30828-X1187-N585-2-7620

NM:SWIN-NM


1 Output on the OMT:Following an ISTART escalation, the following outputs (depending on the recovery level)are possible on the OMT:

DATA COLLECTION INFORMATION:

DATE: 98-10-10 TIME: 16:01:12>>> SWSG INFORMATION

A30828-X1187-N585-2-7620 21


NM:SWIN-NM

Note for Tab. 1.4This is a list of all trace points of the recoveries involved in this exemplary escalation.The right-hand column shows a relative time marker in microseconds. It describes thetime intervals between two trace points.Some of the details concerning the date and time between the individual lines have beenremoved manually.

DATE: 98-10-10 TIME: 16:01:12

>>> TRACEPOINT HISTORY

22 A30828-X1187-N585-2-7620

NM:SWIN-NM


Note for Tab. 1.5Output only for NSTART1B and ISTART1B !This displays whether the following additional informations are running:OMC access (REMOTE_OMC) and switching parts of OSS and audit programs(DATABASE CHECK)For each escalation within the CP basic operation, one additional function is left out.

2 Safeguarding in DD. Files:The DC. files automatically created by the system (readable DD. files after conversion)contain a different number of entries depending on the fault pattern and recovery level.A table of contents is found at the end of the file (summary of data conversion).Important: A printout of the entire file may contain 80 to 100 pages!

The purpose of the file is to collect the error data before any core image formatting, soas to allow for subsequent evaluation.

DATE: 98-10-10 TIME: 16:03:40 EMCYMN:EY600>>> CALL PROCESSING BASIC OPERATION > SUMMARY OF DATA CONVERSION

A30828-X1187-N585-2-7620 23


NM:SWIN-NM

General points: The contents " SAVEAREA OF SWET " are only saved if an SWSG has been

performed on the BAP-MASTER. In order to be able to read the DC. files, a DD. file with the same extension must be

created. The DC. file is then copied into the DD. file with the MML commandDMP SFGSYMP and edited. (see Saving of Error Symptoms)

Possible escalation pattern (example until ISTART2G):

Fig. 1.1*) a DC.B00/B01 cannot be generated as it already exists.

N3 = NSTART3 Ix = ISTARTx

The names extend from DC.V00 - DC.V03 on MDD0, DC.V04 - DC.V07 on MDD1.If all these files exist on hard disk, the DC function cannot create any new files of thesame name. All existing files must therefore be deleted manually as soon as pos-sible after transfer with the MML command DEL FILE. The same applies for theDC.B00/B01 files.

Note: DD. files are deleted with CAN AFILE. The DC. files are primarily created by the developer for evaluation. The following printouts are examples, some of which have been shortened.

MDD0: V00 B00 *) V01 V02

MDD1: DC. V04 B01 * V05 V06

t

N3 I2GI1B I2I1B I1BI1

).DC

DATA:

>>> CREATIONTIME

24 A30828-X1187-N585-2-7620

NM:SWIN-NM


Note for Tab. 1.8The column "SWITCH BYTE" (SGC table) indicates the position of the LIS switch.

DATA:

>>> PERIPHERAL RECOVERY CONFIGURATION TABLE > PERIPHERAL RECOVERY LTG TABLE

A30828-X1187-N585-2-7620 25


NM:SWIN-NM

Note for Tab. 1.10This output shows the last message sent by the corresponding LTG.

Note for Tab. 1.11This table may still contain information on past recoveries. Check that the time is correct.

DATA:

>>> PERIPHERAL RECOVERY LAST MESSAGE ARRAY > ERROR INFORMATION OF PERIPHERAL RECOVERY > CENTRAL UNITS STATUS TABLE

26 A30828-X1187-N585-2-7620

NM:SWIN-NM


Note for Tab. 1.13This mask appears 20 times in the printout. All unused elements remain blank. Theaccess in MASK TABLE is possible via ELEMENT WITH LAST SYSTEMRECOVERY index.

DATA:

>>> CENTRAL RECOVERY MASK TABLE

A30828-X1187-N585-2-7620 27


NM:SWIN-NM

Note for Tab. 1.14All the trace points here are saved in the buffer memory, i.e. those at the beginning maydate from a previous recovery. The beginning of the recovery escalation must be foundwith the OMT protocol. (A relation is possible via MASK TABLE.)

DATA:

>>> CENTRAL RECOVERY TRACEPOINT HISTORY

28 A30828-X1187-N585-2-7620

NM:SWIN-NM


DATA:

>>> INFORMATION ABOUT ACTUAL RECOVERY

A30828-X1187-N585-2-7620 29


NM:SWIN-NM

Note for Tab. 1.16In this case, "HARDWARE RECOVERY" appears in the line RECOVERY INITIATOR.This entry is correct for each ISTART, even in the case of a SW error, as after ISTART,the hardware recovery starts running and the SW recovery is invoked.

DATA:

>>> INFORMATION ABOUT PREVIOUS RECOVERY

30 A30828-X1187-N585-2-7620

NM:SWIN-NM


Note for Tab. 1.17The digits specified in the lines "ADDRESS .. and "LOAD DEVICE..." are the physicalB:IOC port numbers in decimal form be equivalent to (CP113D: MDD-0 = 010E01 orCP113C/CR and CP113E: MDD-0= 010C01)

DATA:

>>> HARDWARE COMMUNICATION AREA

A30828-X1187-N585-2-7620 31


NM:SWIN-NM

Note for Tab. 1.18Outputs for "COMMUNICATION AREA OF SWET" vary according to the error symptompackage!

SYMTOMS PACKAGE NO : 2 SUBPACKAGE : COMMUNICATION AREA OF SWET

ID NEXT CAST PROCESSOR DATE TIME MODULE SWSG RECLEV STATUS--+----+----+--------+--------+--------+--------+----+--------+---------

0 1 OCCU @####### @####### @####### @####### 999 @####### FREE1 20 OCCU BAP_MS @####### @####### ZRCMDA0C 1 NSTART0 ACT2 21 FREE @####### @####### @####### @####### 999 @####### FREE3 21 FREE @####### @####### @####### @####### 999 @####### FREE

Tab. 1.18

32 A30828-X1187-N585-2-7620

NM:SWIN-NM


1.3 Progress Messages

1.3.1 LTG-Code Downloading Progress Mask

The following trace points produce an output on the OMT:

Fig. 1.1 Trace points for ISTART2 with LTG downloading ( on OMT )

The message START OF CODE DOWNLOAD REPETITION only appears when codedownloading is being repeated.1) CP113D: on module CPCL2) CP113C/CR and CP113E: on maintenance panel*) ... there are no trace points on the CP display for these messages.

LTG-Code Downloading Progress MaskTrace point B254 provides information on the progress of LTG-code downloading.

Note for Tab. 1.1This mask outputs the current LOADTYPE xx, the SEGMENT zz currently beingprocessed and the total number nn of segments of this load type.

1), 2) ##### INITIALSTART PROGRESS MESSAGE ##### LTG-CODE DOWNLOADING LOADTYPE xx time START xx. OF nn CODE SEGMENTS : : : : : :##### INITIALSTART PROGRESS MESSAGE ##### LTG-CODE DOWNLOADING LOADTYPE zz time START zz. OF nn CODE SEGMENTS##### INITIALSTART PROGRESS MESSAGE ##### START OF DIGIT-TABLE DOWNLOADING time##### INITIALSTART PROGRESS MESSAGE ##### START OF LTU-DATA DOWNLOADING time##### INITIALSTART PROGRESS MESSAGE ##### START OF LTG-PORTDATA DOWNLOADING time##### INITIALSTART PROGRESS MESSAGE ##### START OF LTG ACTIVATION time##### INITIALSTART PROGRESS MESSAGE ##### START OF DLU-DATA DOWNLOADING time##### INITIALSTART PROGRESS MESSAGE ##### END OF LTG

Trace points

B284

B274

B264

B2B4

B2A4

*)LOADING

##### INITIALSTART PROGRESS MESSAGE ##### OF CODE DOWNLOAD REPETITION

*)START

B254

##### INITIALSTART PROGRESS MESSAGE ##### LTG-CODE DOWNLOADING LOADTYPE xx START zz. OF nn CODE SEGMENTS

Tab. 1.1

A30828-X1187-N585-2-7620 33


NM:SWIN-NM

Downloading Progress Mask for ISTART1BFunction: During normal operation, the display of the CP113D processor moduleoutputs trace points only, to check the progress of the recovery during an ISTART1.Unlike this, however, the RP also outputs information relating to the trace points on theOMT during the ISTART1B in the absence of supplementary error data. These pointsare given the time stamp of the HW clock.

Fig. 1.2 Mask tests for ISTART1B1) CP113D: on module CPCL2) CP113C/CR and CP113E on maintenance panel

Post-Processing Progress Message:

Note for Tab. 1.2This information mask indicates the progress of post-processing.The cycle activity is given in line ZZZZZ, as follows: 1. Only activation of LTGs 2. Downloading of LTGs with data 3. Downloading of LTGs with code and dataFollowing an ISTART 1, all three cycles are run. For the other ISTARTs, only cycles 2and 3 are run.

1), 2)Trace points

C123

C113

C103

C143

C133

C1A3

Time stamp

DATA: JJ-MM-TT TIME: HH-MM-SS

C103 USTART1B START INITIALIZATION IOCP 2065029209C113 USTART1B START SETUP OF MESSAGE BUFFERS 2064621147C123 USTART1B START SETUP SWITCH GRP CONTROLLERS 2064544884C133 USTART1B START ACTIVATION MESSAGE CHANNELS 2063325828C143 USTART1B START LTG RECOVERY 2.1 OR 2.2 2062986219C1A3 USTART1B START ACTIVATION LTGS 2045131180

XXXXXXXXXXXXXXXXXXXXXX MMN:XXXXXXXXXX

POST PROCESSING PROGRESS MESSAGE

START OF CYCLE X. OF Y.ZZZZZZZZZZZZZZZZ

Tab. 1.2

34 A30828-X1187-N585-2-7620

NM:SWIN-NM


Post-Processing Alarm Mask:

Note for Tab. 1.3This alarm mask displays all peripheral units (SYP, CCG, MBU:SGC, MBU:LTG, TSG,SSG) that could not be configured successfully. Synchronizing channel errors ofLTGC(B) are marked seperately with an correspnding mask text. It also displays theLTGs that could not be activated by post-processing.

Post-Processing Information Mask:

Note for Tab. 1.4This information mask displays all LTGs that could be successfully configured byrecovery post-processing.

XXXXXXXXXXXXXXXXXXXXXX MMN:XXXXXXXXXX . .

STATUS OF PERIPHERAL PROCESSOR UNIT CHANGED DURING .SYSTEM-RECOVERY . .

CONFIGURATION : UNIT FROM TO .----------------------------------------- .

XXXX -X-XX XXX UNA

Tab. 1.3

SYSTEM - RECOVERY

STATUS OF PERIPHERAL PROCESSOR UNIT CHANGED DURING RECOVERY

CONFIGURATION : UNIT FROM TO -----------------------------------------

XXXX -9-99 XXX XXX

Tab. 1.4

A30828-X1187-N585-2-7620 35


NM:SWIN-NM

Outputs following completed Post-ProcessingPost-Processing Final Mask:

Note for Tab. 1.5This mask displays all peripheral units which could not be successfully configured duringpost-processing.

SYSTEM - RECOVERY

POST-PROCESSING FINISHED

DATE: 99999999X TIME 99999999X

CONFIGURATION FAILURES DURING POSTPROCESSING

UNIT: UNIT: UNIT: UNIT: UNIT:----- ----- ----- ----- -----

XXX -9-99 XXX -9-99 XXX -9-99 XXX -9-99 XXX -9-99

Tab. 1.5

36 A30828-X1187-N585-2-7620

NM:SWIN-NM


1.4 IMON

1.4.1 IPL-Functions

Fig. 1.1

BOOT IPL113: MANUAL START - CURRENT CONFIGURATIONUNIT STATUS MEMSIZE TEST*******************************************************************

BAP-0 UNA BAP SPAREBAP-1 MASTER 0032 MB NO TEST RUNB:CMY-0 ACT NO TEST RUNB:CMY-1 UNA DIAGNOSIS FAULTCMY-0 ACT 0064 MB DIAGNOSIS OKCMY-1 ACT 0064 MB DIAGNOSIS OKIOC-0 ACT 0016 MB DIAGNOSIS OKIOC-1 ACT 0016 MB DIAGNOSIS OK

IPL113: ENTER PARAMSTO DISPLAY HISTORY : HIST;TO DIAGNOSE MEMORY : DIAG;TO FORMAT MEMORY : FORMAT;TO CONTINUE : ;

Automatic

IPL 113: 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 : ;

Stop Load specific filee.g.

AutomaticCall upinstallationrecoverys

;

;

start-upSY.INSTALL

start-up withselectionoption

STOP; MAN;INS;UTI;

A30828-X1187-N585-2-7620 37


NM:SWIN-NM

1.4.2 Description of the BZS/AKD and the Generation List

The following OMT outputs are achieved by disk access during manual startup from theIPL:

If BZS/AKD and GENERATION-LIST are available:

If BZS/AKD only available (GENERATION-LIST not available):

If BZS/AKD and GENERATION-LIST are not available:

In the CIL-acknowledgement of the Core Image Loaders (040271.....) e.g. the error code(ER1 u. ER2) is included. The interpretation of System Loader Error Message is to beexecuted with IMON description (see 1.4.7).

IOC-0 MDD: BZS/AKD AND GENERATION LIST001E070E06025C09320200 2B240B05025C000E0000000209320100 16240C08085B000E00000004

IOC-1 MDD: BZS/AKD AND GENERATION LIST

Tab. 1.1

IOC-0 MDD: BZS/AKD :001E070E060260

IOC-0 MDD : GENERATION-LIST :

04027100000000000000001110010C010401000500

Tab. 1.2

IOC-0 MDD : BZS/AKD : NOT AVAILABLE04027100000000000000001110010C010401000500

Tab. 1.3

38 A30828-X1187-N585-2-7620

NM:SWIN-NM


Fig. 1.2 Generation listNote for Fig. 1.2BZS=Betriebszustand - Operational state of the partner diskAKD=Aktualittsdatum - Current date

generation

001E070E060260

12320200 2B240B05025C000E00000002

12320100 16240C08085B000E00000004

001E070E060260

BZS AKD

generation generation

number

name date number

of files

Validityflag

A30828-X1187-N585-2-7620 39


NM:SWIN-NM

Generation Name

Fig. 1.3

Fig. 1.4

12 01

Fix point counterODAGEN counterLocal correction counterCorrection statusVersion number

Generation Date

Validity flag of the Generation:

Generatiober (4 bytes)

H'0000 0004

2 003

binary 0000 0100 = generation 2

(see description of AKD)

H'01 --> Invalid generationH'02 --> Blocked generation

H'00 --> Valid generation

The display of generation no is the powerset.

bit no 7654 3210 = generation name

HEX Status value

00010203040506070809

ACT-MASTERACT-SPAREUNAMBLSEZSPLITPLANACSTBUNDEF

BZS - Operational state of the partner disk

Symbol Status value

40 A30828-X1187-N585-2-7620

NM:SWIN-NM


Fig. 1.5

YS

time date

H D MM

AKD - Current date (and time)HEX ---> 1 E 0 7 0 E 0 6 0 2 0 0

DEC ---> 3 0 0 7 1 4 0 6 0 2 0 0 = 14:07:30 Time06.02.00 Date

A30828-X1187-N585-2-7620 41


NM:SWIN-NM

1.4.3 Loading from Save Medium

Fig. 1.6Sequence:1. Invoke IPL using the Boot key.2. Load the OFFLINE program SY.INSTALL with the help of the utility function.3. Installation Monitor gives out a prompt; the functions can be interrogated with

HELP.4. Format (INIT MD) and label MDD (LABEL MD), and using TRANS FILE transfer files

from saving medium (MO) to MDD.5. Startup with the loaded APS version.

SY.TASKLIBSY.LOADLIB.MASY.LOADLIB.LASY.LOADLIB.CASY.PSW...

System disk

IPL

SY.INSTALL

IMON TRANSFILE

INIT MD

LABEL MD SY.SLRAM SY.TRANSLOG

Save medium (MO)

BOOT IP UTI

CMY

L

MDD

42 A30828-X1187-N585-2-7620

NM:SWIN-NM


1.4.4 Startup of the IMON

Fig. 1.7

IPL113: MANUAL START - CURRENT CONFIGURATIONUNIT STATUS MEMSIZE TEST

BAP-0 UNA BAP SPAREBAP-1 MASTER 0032 MBYTE NO TEST RUNB:CMY-0 ACT NO TEST RUNB:CMY-1 UNA DIAGNOSIS FAULTCMY-0 ACT 0064 MBYTE DIAGNOSIS OKCMY1 ACT 0064 MBYTE DIAGNOSIS OKIOC-0 ACT 0016 MBYTE DIAGNOSIS OKIOC-1 ACT 0016 MBYTE DIAGNOSIS OK

IPL113

TO DIAGNOSE MEMORY : DIAG;TO FORMAT MEMORY : FORMAT;TO CONTINUE : ;

FORMAT;

UTI;

UTILITY-REC. - DEVICE-TYPE TO USE : MDD;/MTD;/MOD;

IOC-,IOP- and device number (6 figures in HEX)PLEASE ENTER UTILITY-FILE-NAMESY.INSTALLIMON: (aps-name, version) STARTEDIMON: ENTER COMMAND

, FILE=,SRANGE=SEC-SEC;CAN FILE : DEVOUT=devaddr, FILE=filename, OLDGEN=genset;DISP MDDIR : DEVIN=devaddr;DISP FILESEC : DEVIN=geradr, FILE=filename, OLDGEN=;INIT MD : DEVOUT=devaddr;LABEL MD : DEVOUT=devaddr;CAT FILE : DEVOUT=devaddr, NEWFILE=filename, OLDFILE=filename, OLDGEN=genset,

NEWGEN=;CREATE SLDISK : DEVOUT=devaddr;START CMDFILE : CMD=;HELP;IMON:ENTER COMMAND

HISTORY OF PRO-DISPLAYS (FORMAT: -DISPLAY>)=======================================================

0000 00-E761 00-D002 00-E611 00-D002 00-E931 00-D002 . . . . . . .

IPL113TO START APS MANUALLY : MANUALLY; TO START INSTALLATION RECOVERY : INSTALLATION; TO START UTILITY (MONITOR) : UTILITY; TO STOP INITIALSTART : STOP; TO START APS AUTOMATICALLY : ;

TO DISPLAY HISTORY : HIST;: ENTER PARAMS

: FILECAT=;: OLDGEN=, NEWGEN=;

A30828-X1187-N585-2-7620 43


NM:SWIN-NM

1.4.5 IMON Commands Description

HELPList of available commandsSyntax:HELP;

INIT MDFormatting diskSyntax:INIT MD:DEVOUT = devaddr;

DEVOUT Physical device address of disk device to be formatted devaddr= xx= IOC number(hex)yy= IOP number(hex) zz= Device number(hex)

DISP MDDIROutput of a disk content directory.Syntax:DISP MDDIR:DEVIN = devaddr;

DEVIN Physical device address of disk for which directory is to be output devaddr= (see INIT MD)

LABEL MDLabelling a disk.Syntax:LABEL MD:DEVOUT = devaddr;

DEVOUT Physic. disk device address to be labelled devaddr= (see INIT MD)

CREATE SLDISKCopying of a new SL DISK section without labelling the disk (existing files arepreserved).Syntax:CREATE SLDISK:DEVOUT=devaddr;

DEVOUT Physical device address of disk to whichthe new SL DISK section is to be transferred devaddr= (see INIT MD)

44 A30828-X1187-N585-2-7620

NM:SWIN-NM


CAT FILERenaming a file on the diskSyntax:CAT FILE:DEVOUT= devaddr, NEWFILE=filename, OLDFILE=filename,

OLDGEN= genset, NEWGEN=;

DEVOUT Physical device address of disk on which the file to be renamed is stored devaddr= (see INIT MD)

NEWFILE New file name OLDFILE Old file name

filename= 1-17 alphanumeric characters OLDGEN Generation powerset of file to be renamed NEWGEN Generation powerset of the new file

genset= 8 hex digitsNEWGEN= OLDGEN;

Entering the asterisk causes thegenset of NEWGEN to be OLDGEN

CAN FILEDeleting a file on the diskSyntax:CAN FILE:DEVOUT=devaddr, FILE=filename, OLDGEN=genset;

DEVOUT Physical device address of disk from which the file is to be deleted devaddr= (see INIT MD)

FILE Name of file to be deleted OLDGEN Generation powerset of old file

genset= 8 hex digits

TRANS FILECopying files from DEVIN to DEVOUT.Syntax:TRANS FILE:DEVOUT = devaddr, DEVIN=devaddr,

FILECAT= , OLDGEN = , NEWGEN=;

DEVIN Physical device address of the input and

DEVOUT output device (disk/medium). devaddr= (see INIT MD)FILECAT Name of files to be copied (maximum 10)

file 1= 1-17 alphanumeric characters

file 2= 1-17 alphanumeric characters

*) all files

A30828-X1187-N585-2-7620 45


NM:SWIN-NM

OLDGEN Generation powerset of medium file

NEWGEN Generation powerset of disk file

genset = 8 hex digits

*) all generations (for OLDGEN) NEWGEN = OLDGEN (for NEWGEN)

MD DUMPPhysical disk copy from disk to medium or OMT (max. 16 MBYTES).Syntax:

MDDUMP:DEVIN =devaddr,DEVOUT=, FILE=filename, SRANGE=aaaaaa-bbbbbb;

DEVIN, Physical device address of input and DEVOUT output device (disk/medium). devaddr= (see INIT MD) FILE Name of output file on medium filename= 1-17 alphanumeric characters (Parameter not applicable if DEVOUT = *) SRANGE Sector range

aaaaaa= Start sector number as hexadecimal number; leading zeros need not be given.

bbbbbb= End sector number, as for aaaaaa. bbbbbb-aaaaaa< 2000H on medium (=> 16 MB)

40H on OMT (=> 128k)

DISP FILE SECOutput of the extent (physical position) of a file to the OMT.Syntax:DISP FILESEC:DEVIN = devaddr, FILE=,

OLDGEN= ;

DEVIN Physical device address of the disk. devaddr= (see INIT MD)

FILE Name of output file on diskfilename= 1-17 alphanumeric characters*) = extents of all files

OLDGEN Generation powerset of the file genset= 8 hex digits *) = current generation

46 A30828-X1187-N585-2-7620

NM:SWIN-NM


1.4.6 Physical Addresses of Devices

The physical device address is compiled using the IOC, IOP and the device address.It is needed by the Installation Monitor (IMON)

Fig. 1.8

IOC-3IOC-2IOC-1

MTD

IOC-0BAP-1BAP-0

XX YY ZZ

IOCAdress

IOPAdress

DeviceAdress

0D03

01

IOP:MTD

IOP:MDD

0EB:IOC

CP113D:

XX YY ZZ01 0D 03 MTD 003 0D 03 MTD 101 03 23 MOD 003 03 23 MOD 101 0E 01 MDD 003 0E 01 MDD 1

(00) (02) 01 03 05 07

CMY

e.g.

e.g.

IOP:UNI

e.g.0C

03

MDD

MDD

CP113C/CR and CP113E:

XX YY ZZ01 0C 03 MTD 003 0C 03 MTD 101 0C 23 MOD 003 0C 23 MOD 101 0C 01 MDD 003 0C 01 MDD 1

MTD

01

23

IOP:UNI

e.g.03 MOD

A30828-X1187-N585-2-7620 47


NM:SWIN-NM

1.4.7 Description of the IMON and System Loader Error Message

System Loader Error Message:

Fig. 1.9

Fig. 1.10

IMON Trans File Error Message

ER1 ER2

L o a d i n g n o t s u c c e s s f u l !

04 02 71 00000000 11 10 04 0100 0500OPcode Error code

00000000

Start address LIB versionQL QPBIOS ACK

Deviceaddress

Dev. IOC IOP

CIL acknowledgement BIOS acknowledgement

010C01

typ MES MES

TRANS: ADDITIONAL TAPES? (Y/N)TRANS: INPUT/OUTPUT ERROR ON MDD OR MTD 010C04ERROR: 1110 BIOS ACK (QL/QP)IOCMES: 0100IOPMES: 0500 from IOP:SCDV

phys. addr. of IOP

48 A30828-X1187-N585-2-7620

NM:SWIN-NM


CIL acknowledgementOP Code

ER1 Error code

SL INIT 00Load CIFLE 01Check disk 02Load GENLIST 03Load APS 04Load selective 05Load APS INSTALL 08Load CMY with TRANS 09Load CMY without TRANS 10Load LMY 11Load SYS selective 12

Tab. 1.4

OK 00File not valid 01File not found 02Format error 03Param error 04Wrong device 05Not available 06IO error 07Module not found 08File damaged 09File checksum error 10

Tab. 1.5

A30828-X1187-N585-2-7620 49


NM:SWIN-NM

ER2 Error code

OPCODE- Interpretation 00

Tab. 1.6

SLINIT MDD0 1xSLINIT MDD1 2xBIOS Initialization x1Init. of MDD (BIOS) x2Reading of VOL1-Sector (BIOS) x3No VOL1 x4Reading of last SL-Disk-Sector (BIOS) x5No SLOK x6Reading SL- Disk- Part (BIOS) x7Close MDD (BIOS) x8

Tab. 1.7

Load CIFILE 3xOpen of load device (BIOS) x1Reading SL- Disk- Part (BIOS) x2No CP113 LIB x3No TASKLIB or SEMILIB x4No dirload section x5Reading dirload (BIOS) x6No loadinfo or loadinfo too long x7Reading loadinfo (BIOS) x8More than one SSW- ACST- Loadsegment x9Reading loadsegments (BIOS) xAClose of load device (BIOS) xBNo SSW- ACST- Segment found xc

Tab. 1.8

OPCODE - Interpretation 40

Tab. 1.9

50 A30828-X1187-N585-2-7620

NM:SWIN-NM


Check disk 5xInit of MDD (BIOS) x1Device typ check x2Reading of VOL1- Sector (BIOS) x3No VOL1 x4Close MDD (BIOS) x5

Tab. 1.10

Load GENLIST 6xOpen of load device x1Device typ check x2Validity check x3Reading GENLIST x4Close load device (BIOS) x6

Tab. 1.11

A30828-X1187-N585-2-7620 51


NM:SWIN-NM

Load TASKLIB 7xLoad SEMILIB 8xLoad Selective 9xOpen of load device (BIOS) x1Reading LIB - Information (BIOS) x2No CP113 LIB x3No TASKLIB or SEMILIB x4No DIRLOAD/DIRNAME section x5Reading DIRLOAD/DIRNAME x6No load info or load info too long x7Read load info x8More than one SSW- ACST- Load segment x9Reading load segment (BIOS) xAClose of load device (BIOS) xBNo SSW- ACST- Segment found xCDevice type check xDValidity check xE

Tab. 1.12

Enter transactions AxOpen of SY.TRANSLOG (BIOS) x1Reading of SY.TRANSLOG (BIOS) x2Device type check for SY.TRANSLOG x3Validity check for SY.TRANSLOG x4Close of SY.TRANSLOG (BIOS) x5Check for valid transaction x6Search transaction for target file x7Open target file (BIOS) x8Validity check for target file x9Generation check for target file xAWrite transaction to target file xBClose target file xC

Tab. 1.13

52 A30828-X1187-N585-2-7620

NM:SWIN-NM


BIOS acknowledgements

QL (logical acknowledgements)OK 00End of file 10Time limit 11

Input limit 12File not found 20File found 21Write protection 22Inv. Alarm 30Function not available 31Function not impiemented 32No open 40Log dev ALR opend 41Wait no GET 42Wait no PUT 43PUT no open READ 44GET no open WRITE 45Wrong device 46LOGNR ex 47VOL1 error 50Label error 51Table of contents overflow 60No space 61Extent overflow 62Physical error 70Translation error F0

Tab. 1.14

A30828-X1187-N585-2-7620 53


NM:SWIN-NM

QP (physical acknowledgements)OK 00IOP error message 10IOC error message 11IOC time out 20IOP time out 21Invalid parameter 30No INIT 40LOGDEV seized 41Wait no PCOM 42Invalid device type 43Already INIT 44

Tab. 1.15

Device typePC 01MOD 03MDD 04Data link 07

Tab. 1.16

54 A30828-X1187-N585-2-7620

NM:SWIN-NM


IOC MESSAGE (MSG1/2)Command executed 0100Command executed window already created 0101Window NR wrong used 0106Wrong instruction 0601Wrong SET NR 0602SET NR not available 0603Wrong window blocks 0604Window NR >127 0605Wrong window NR 0606Wrong IOP NR 0607Wrong IOP connection 0608Wrong mapping 0609

Tab. 1.17

A30828-X1187-N585-2-7620 55


NM:SWIN-NM

OP MESSAGESIOP: MDD

0100 Command successful0300 Wrong OSTof device (/=ACT)0400 No request sense0401 Wrong status byte0402 Device fault0403 Signal does not vanish0404 Signal does not appear0405 Both defect lists bad for REA0406 Not the expected phase0407 Both defect lists bad for WRI0408 Wrong busyBF0409 Illegal DMA-Interrupt040A DMA-Error040B No syncrone mode040C No message out phase040D No busfree phase040E Time out040F Error in compare0500 Disk not formatted0501 Write protected0502 B:IOC too slow0600 Unknown type0601 Unknow command0602 Wrong sector address0603 Wrong offset0604 Wrong bytecount0605 Wrong address0700 Defective sector overflow0701 Defecfive sector

Tab. 1.18

56 A30828-X1187-N585-2-7620

NM:SWIN-NM


IOP: SCDV

IOP:UNI(see other IOPs)

1.5 Recovery trace points

1.5.1 CP113D, CP113C/CR and CP113E

Tracepoints for CP113D, CP113C/CR and CP113E are explainedin NM:CP113 TAB, CP0052.

0100 Input operation terminated0102 Input operation terminated by end0103 Data length exceeded0401 Transmission error0402 PC ot ready0500 Input time exceeded0501 Input time exceeded0600 Wrong device typ0601 Wrong instruction0602 Data length = 0

Tab. 1.19

A30828-X1187-N585-2-7620 57


NM:SW

2 Procedures (Preface)SW110 Measures after recovery (for NE with SSNC)SW120 Measures after recovery (for NE without SSNC)SW422 Replacement of non-resident libraries (for NE with SSNC)SW441 Exchange of PSW files (for NE with SSNC)SW451 Expansion of the database area using ODAGEN (for NE with

SSNC)SW462 Replacement of non-resident libraries (for NE without SSNC)SW481 Exchange of PSW files (for NE without SSNC)SW491 Expansion of the database area using ODAGEN (for NE

without SSNC)

58 A30828-X1187-N585-2-7620


A30828-X1187-N585-2-7620 59


NM:SWSW110

2.1 Measures after recovery (for NE with SSNC)

SW110

IntroductionExtensive monitoring and self-checking processes, which can be activated in the caseof failures, are integrated into the Application Program System (APS). The location,gravity and subsequent results of the fault detected are evaluated and on the basis ofthis evaluation recoveries, with varying depths of penetration are started.The recoveries and their affects on the system are described in the Introduction in detail.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 anddisplayed.

System messages which are stored for statistical purposes in the history fileHF.ARCHIVE as well as being output are identified in the job number line of themessage output with HF.ARCHIVE - vvvvv (vvvvv = entry sequence number).

Reading the history file is done with the MML Commands DISP AENTRY andSEL AENTRY.

60 A30828-X1187-N585-2-7620

NM:SWSW110


1 Start-up messages

Please wait until all start-up messages are output.

If one MDD is inoperable, it is to be cleared of faults according to MMN:SW,procedure SW310 after this procedure is finished.

2 User identification and passwordWhen the next command is input, the system requests the user identificationand the password. After input of user identification and password the commandis executed.

3 Analyzing the recovery messageWhat kind of recovery was reported ? SYSTEM recovery h...4 SSP recovery h...6

4 Display alarm statusUsing the Alarm Surveillance the alarm status is to be displayed and themessage number which is necessary for deleting the CP alarm is to be deter-mined.

5 Delete alarms

The following command has to be executed for all alarms with ALPRIO=MAJORthat are assigned to an ISTART message.

b SET ALSTAT:MSGNO=msgno,ALSTAT=C;

6 Meter checkAre irreparable comparator faults determined during meter check ? Y h...7

N h...8

7 Meter restorationThe defective charge meters are to be restored according to procedure SW225. h...SW225

8 Check the system status.

Inspection of system status is to be executed.

Please check the system redundancy and, if necessary, restore it.

A30828-X1187-N585-2-7620 61


NM:SWSW110

9 Hardware statusAre all hardware units in the correct operating state ? Y h...11

N h...10

10 Fault clearance of hardware units

The hardware units which are in the wrong operational state have to be clearedof faults and configured according to the appropriate maintenance manual. Afterthat this procedure is to be continued.

11 Symptom saving

When a recovery message is output it is to be cleared with help of the nexthigher TAC level whether the error has already been reported. If the error isntreported so far,, an error report is to be written and all necessary error symp-toms are to be saved (error classification: CP recovery). h...Symptom

saving

END

62 A30828-X1187-N585-2-7620

NM:SWSW110


A30828-X1187-N585-2-7620 63


NM:SWSW120

2.2 Measures after recovery (for NE without SSNC)

SW120

IntroductionExtensive monitoring and self-checking processes, which can be activated in the caseof failures, are integrated into the Application Program System (APS). The location,gravity and subsequent results of the fault detected are evaluated and on the basis ofthis evaluation recoveries, with varying depths of penetration are started.The recoveries and their affects on the system are described in the Introduction in detail.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 anddisplayed.

System messages which are stored for statistical purposes in the history fileHF.ARCHIVE as well as being output are identified in the job number line of themessage output with HF.ARCHIVE - vvvvv (vvvvv = entry sequence number).

Reading the history file is done according to SW282

1 Start-up messages

The following messages are an extract of whole start-up messages output.

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,procedure SW310 after this procedure is finished.

ALL DOUBLE FILES SYNCHRONIZED

64 A30828-X1187-N585-2-7620

NM:SWSW120


2 Recovery message@###### RECOVERY INFORMATION

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

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

REQUESTED RECOVERY LEVEL : @#######PERFORMED RECOVERY LEVEL : @#######

CALLPROCESSING STARTED : @#######@

DURATION OF SERVICE INTERRUPTION : @####@ SECONDSRECOVERY DURATION : @####@ SECONDS

RESULT : @####################################################

SUPPLEMENTARY INFORMATION : @############################################### @############################################### @############################################### @############################################### @############################################### @############################################### @############################################### @###############################################

APS GENERATION : @#######

CRITICAL STATES---------------

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

For detailed information about the recovery output message see NM:SWREG:IN. + ......IN-NM

3 User identification and passwordWhen the next command is input, the system requests the user identificationand the password. After input of user identification and password the commandis executed.If there is a call key at the OMT, the system requests the user identification andthe password as soon as the call key is pressed.

4 Analyzing recovery messageWhat kind of recovery was reported ? SYSTEM recovery h...5 SSP recovery h...7

A30828-X1187-N585-2-7620 65


NM:SWSW120

5 Display alarm statusb DISP ALARM:OBJECT=RECOV;

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

OBJECT = RECOV ALPRIO = MAJOR ALSTAT = @# MSGNO = @####ALTYPE = @#######################PABCAUSE= @#################################################ALARM-ID: @#############################################################

6 Delete alarms

The following command has to be executed for all alarms with ALPRIO=MAJORthat are assigned to an ISTART message.

b SET ALSTAT:MSGNO=msgno,ALSTAT=C;

7 Meter checkAre irreparable comparator faults determined during meter check ? Y h...8

N h...9

8 Meter restorationname METER AUDITRESULT : NOT REPAIRABLE ERRORS ON FILE *****.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 SW275 isto be done. h...SW275

9 Display hardwareb CHECK HWCONF

Using local operation without NetM the following command has to be entered:EXEC CMDFILE:FILE=CG.SA.REC53;

10 Hardware statusAre all hardware units in the correct operating state ? Y h...12

N h...11

66 A30828-X1187-N585-2-7620

NM:SWSW120


11 Fault clearance of hardware units

The hardware units which are in the wrong operational state have to be clearedof faults and configured according to the appropriate maintenance manual. Afterthat this procedur is to be continued. i....STARTUP

12 Symptom saving

When a recovery message is output it is to be cleared with help of the nexthigher TAC level whether the error has already been reported. If the error isntreported so far,, an error report is to be written and all necessary error symp-toms are to be saved (error classification: CP recovery). h...Symptom

saving

END

A30828-X1187-N585-2-7620 67


NM:SWSW422

2.3 Replacement of non-resident libraries(for NE with SSNC)

SW422

2.3.1 General information.

Larger-scale software corrections or the introduction of new features in/into the softwaremay require the replacement of one or more non-resident libraries. The replacement ofnon-resident libraries is to be executed according to the present procedure.

Attention:This procedure is executed only on the CP. There are no actions necessary on the MP.

This procedure constitutes a dangerous intervention in the operating EWSD system.Redundancy and stability of all units must be ensured before it is carried out.

By replacing non-resident libraries a new generation is created.A short interruption of operations is unavoidable because, as soon as the new genera-tion is valid, a NSTART1 must be started to introduce this new generation to the system.Interruption of the procedure should be avoided.

For reasons of security before and after a replacement of non-resident libraries thecurrent APS is to be saved. Before the replacement the next saving which is plannedaccording to the safeguarding schedule is to be executed.In any case a quarterly saving is to be executed after the replacement.In order to avoid a double execution of the time-consuming quarterly saving, thereplacement of non-resident libraries is to be planned for a time period where the nextsaving is a routine saving.

68 A30828-X1187-N585-2-7620

NM:SWSW422


Abbreviations:In connection with data transfer from/to magneto optical disk the following abbreviationsare used:

Attention!Note on synchronization of the MDDs:

After each synchronization of the MDDs (e.g. after recovery, configuration of the MDDsetc.) a CHECKSUM MDD AUDIT is started automatically, if the status of theMDDAUDIT is UNLOCKED. The audit starts after the synchronization of the MDDs isfinished and it lasts about 6 minutes. The result of the audit must have been displayedbefore proceeding further!If the audit detects a checksum error for one of the MDDs, this error is to be repairedaccording to procedure SW500 before the current procedure is continued. An inad-vertent copying of the error to the other MDD is therefore prevented.

The following MOs are to be held ready. MO with new system files (non-resident libraries) Current PATCH MO (if LOADLIB.LA is to replace)For saving the valid APS generation: 1 MO for saving the CP generation 1 MO for saving the MP generation and the LOG files 1 MO for saving the logical charging data from the CP-MDDFor saving the new APS generation: 1 MO for saving the CP generation 1 MO for saving the MP generation and the LOG files 1 MO for saving the logical charging data from the CP-MDD

MOD magneto optical disk deviceMO magneto optical disk (=save medium)FLD Floppy DiskOMT OMT denotes the operation terminal which is in use

(e.g. PC, NetM, EMN/OS etc.)

A30828-X1187-N585-2-7620 69


NM:SWSW422

2.3.2 Procedure description

1 List catalog entries - IA. files.b DISP FILE:FILE=IA.;

2 List catalog entries - CA. files.b DISP FILE:FILE=CA.;

3 List catalog entries - LG. files.b STAT INPLOG;

4 Remove MO from CP-MOD.b RSET MO:VSN=archivename;

Remove the APS routine save MO from CP-MOD.The MO is to be marked as current APS routine save CP MO and to be heldready for further use.

5 Mount MO in CP-MOD.Mount the MO with the new system files.

6 Transfer system files to the background memories.b TRANS FILE:FILE=NEW.LOADLIB./SY.LOADLIB.,VSNS=archivename,

MODE=CRD;

One, two or all of the following files can be transferred: NEW.LOADLIB.LA/SY.LOADLIB.LA NEW.LOADLIB.MA/SY.LOADLIB.MA NEW.LOADLIB.CA/SY.LOADLIB.CA


Remove the MO with the new system files from CP-MOD.

8 Define process switches.b RESET CFOPT;b SET CFOPT:ON=12;

70 A30828-X1187-N585-2-7620

NM:SWSW422


9 Start command file CHECK LOADLRPL.


Attention!If the error messageSyntax Check ReportError: ..... Task xxxxx does not exist in the task databaseis output after the following command was entered, then proceed as follows:- in the workbench open the menu Options- there deactivate Verify Syntax- after that start the command file again- after successful execution activate Verify Syntax again (if necessary).

b CHECK LOADLRPL

Using local operation without NetM the following command has to be entered:EXEC CMDFILE:FILE=CG.SA.LOT01;

The previous output status information is to be checked.Redundancy and stability of all units must be ensured before the procedure iscontinued.

10 Delete non-resident processes.If running non-resident processes were detected during the interrogation ofcurrent jobs, these are to be deleted before the procedure is continued. MainlyACT BAPERF, if present, is to be stopped. Running timer jobs are to be stoppedbefore they can be deleted.The commands are:STOP JOB:JN=jobnumber;CAN JOB:JN=jobnumber,CMDCOD=commandcode;

11 Mount MO in CP-MOD.Mount the MO for APS routine saving.The APS routine save CP MO which was removed last is to be used.

12 Decision.Interrogate the status of the LOG function:

b STAT INPLOG;Was the Log file name LOGy6 determined in the status printout? Y h...13

N h...14

A30828-X1187-N585-2-7620 71


NM:SWSW422

13 Execution of procedure SW210.The next APS quarterly saving is to be executed according to procedureSW210.Continue here, after execution of: MMN:SW, procedure SW210.

i ...SW210

After that, continue h...15

14 Execution of procedure SW210.The next APS routine saving is to be executed according to procedure SW210.Continue here, after execution of: MMN:SW, procedure SW210.

i ...SW210

15 Inhibit routine test.b INHIB SSPRT;

16 Display meter save times.b DISP METSAV;

17 Postpone the meter save times.The meter save times are to be put off to a time after the replacement of non-resident libraries. Hereto in the following command a corresponding time is tobe entered for hh-mm. When the command is executed, the former save timesare deleted. In a later procedure step the old save times are reentered.

b ENTR METSAV:TIME=hh-mm,CHEKNO=0;

18 Deactivate X25LINKs.

Important note:The Application BCT-BOOT must be active for the V24-Interface on the OMT-0(NetM) before deactivation of X25LINKs.

In the following command, the number of the X25LINK which is to be config-ured, is to be entered for no.The command is to be executed for all X25LINKs.

b CONF X25LINK:X25LINK=no,OST=MBL;

19 Display the new system files.b DISP FILE:FILE=NEW.LOADLIB.;

One, two or all of the following files can be displayed: NEW.LOADLIB.LA NEW.LOADLIB.MA NEW.LOADLIB.CA

72 A30828-X1187-N585-2-7620

NM:SWSW422


20 Decision.Which SY.LOADLIB file is to be replaced? Only SY.LOADLIB.MA is to be replaced. h...21 Only SY.LOADLIB.CA is to be replaced. h...22 Two SY.LOADLIB files are to be replaced. h...23 Three SY.LOADLIB files are to be replaced. h...26 Only SY.LOADLIB.LA is to be replaced. h...29

21 Replacement of file SY.LOADLIB.MA.b ENTR GEN:LIB=NEW.LOADLIB.MA;

Now, several status messages are output:

STATUS MESSAGE :

NAME OF CURRENT GENERATION actgenNAME OF NEW GENERATION newgen

NEW GENERATION COMPLETE newgen NEW GENERATION IS VALID newgen NAME OF CURRENT GENERATION newgen

newgen is the name of the new generation which was created by ENTR GENand which is the name of the previous current generation- increased by 1 in the 5th place (xxxxXxxx) if an existing LOADLIB isexchanged.- increased by 1 in the 4th place (xxxXxxxx) if a new LOADLIB is installed.As soon as the new generation is valid, this generation takes over the GCS fromthe previously current generation, while the latter gets the GCS 9999 (invalid).A NSTART1 must be started to introduce the new generation to the system. h...36

A30828-X1187-N585-2-7620 73


NM:SWSW422

22 Replacement of file SY.LOADLIB.CA.b ENTR GEN:LIB=NEW.LOADLIB.CA;


STATUS MESSAGE :

NAME OF CURRENT GENERATION actgenNAME OF NEW GENERATION newgen

NEW GENERATION COMPLETE newgen NEW GENERATION IS VALID newgen NAME OF CURRENT GENERATION newgen


74 A30828-X1187-N585-2-7620

NM:SWSW422


23 Replacement of two SY.LOADLIB files.In the following command xx and yy are to be replaced by the name segments(CA, MA, LA) of the SY.LOADLIB files which are to be replaced.

b ENTR GEN:LIB=NEW.LOADLIB.xx&NEW.LOADLIB.yy;


STATUS MESSAGE :

NAME OF CURRENT GENERATION actgen

Is the command ENTR GEN terminated at this point?(only if SY.LOADLIB.LA is to be replaced) Y h...24

N h...25

24 Replacement of two SY.LOADLIB files.In this case a fault information with a list of patch IDs is output here.Thesepatches have address relations to non replaced libraries and therefore causethe termination of the command.

h...32

25 Replacement of two SY.LOADLIB files.The rest of the status messages are output:STATUS MESSAGE :

NEW GENERATION IS VALID newgen NAME OF CURRENT GENERATION newgen


A30828-X1187-N585-2-7620 75


NM:SWSW422

26 Replacement of three SY.LOADLIB files.b ENTR GEN:LIB=NEW.LOADLIB.MA&NEW.LOADLIB.CA&NEW.LOADLIB.LA;


STATUS MESSAGE :


Is the command ENTR GEN terminated at this point? Y h...27N h...28

27 Replacement of three SY.LOADLIB files.In this case a fault information with a list of patch IDs is output here.Thesepatches have address relations to non replaced libraries and therefore causethe termination of the command.

h...32

28 Replacement of three SY.LOADLIB files.The rest of the status messages are output:STATUS MESSAGE :



76 A30828-X1187-N585-2-7620

NM:SWSW422


29 Replacement of SY.LOADLIB.LA.b ENTR GEN:LIB=NEW.LOADLIB.LA;b ;


STATUS MESSAGE :


Is the command ENTR GEN terminated at this point? Y h...30N h...31

30 Replacement of SY.LOADLIB.LA.In this case a fault information with a list of patch IDs is output here.Thesepatches have address relations to non replaced libraries and therefore causethe termination of the command.

h...32

31 Replacement of SY.LOADLIB.LA.The rest of the status messages are output:STATUS MESSAGE :



A30828-X1187-N585-2-7620 77


NM:SWSW422

32 Replacement of file SY.LOADLIB.LA - exceptions.During replacement of file SY.LOADLIB.LA the creation of the new generationmay be terminated in some cases. This problem occurs, if patches, incorporatedin the APS, have address relations to resident software. In this case, togetherwith the negative command response, an error information is output, whichincludes the identifications of the affected patches.To enable an successful replacement of file SY.LOADLIB.LA, some additionalprerequisites must be met. The necessary actions are described in the followingblock.The current patch MO should be held ready.

33 List generations.b DISP GEN;

The command ENTR GEN was terminated but the creation of a new generationnewgen may have been already started.In this case, however, the new generation is incomplete and therefore markedas invalid in the generation list above. This invalid generation is to be cancelledbefore the procedure is continued.

34 Delete the invalid generation.If an incomplete and invalid generation newgen exists, then it is to becancelled:

b CAN GEN:GEN=newgen;

35 Replacement of file SY.LOADLIB.LA.All the patches mentioned in the preceding error information are to becancelled.The following command is to be executed for each patch-id.

b CAN CPPRPCH:ID=id;b ;

If the command is rejected for a certain patch-id, an additional helppatch may benecessary to make the original patch cancellable (TAC2).If all affected patches are cancelled, the replacement of file SY.LOADLIB.LA canbe repeated. h...20

!In any case TAC2 should be called in!

78 A30828-X1187-N585-2-7620

NM:SWSW422


36 Introduction of the new generation via NSTART1.The following NSTART1 ensures that the contents of the new LOADLIB(s) isused.

b RECOV SSP:LEVEL=NSTART1;

37 Recovery report.

Attention:Please wait until the recovery is finished (observe the corresponding systemmessages). When the synchronization of the MDDs is finished, a CHECKSUMMMD AUDIT is started automatically, if the status of the MDDAUDIT isUNLOCKED. The result of the audit should be displayed (after about 6 minutes)before the procedure is continued. For further information see introduction.

38 IACHASTA message.Was the IACHASTA MESSAGE output after recovery with the new generation? Y h...39

N h...40

39 IACHASTA message.After the generation change the current IACHASTA backup file CA.IC.UCHAwas closed and renamed to CA.IC.UCHA.dddhhs (ddd=daynumber of the year,hh=hour, s=sequential number 0-9). For the new generation a new backup fileCA.IC.UCHA was created.If requested, the closed and renamed file can be saved and prepared foraccounting using the MML command EDIT MET.

40 List generations.

While entering the first command after the recovery a session with theexchange is to be opened.

b DISP GEN;

41 Decision.Was the representation of the correction version within the name of the newgeneration (= 4th place, xxxXxxxx) increased in comparison with the formercurrent generation? Y h...42

N h...43

!If the recovery with the new generation is not successful, a fallback to the oldgeneration will be carried out via an automatic ISTART2G/LOADREC3.After appropriate postprocessing (procedure EY190) and fault clearance a newattempt can be made to replace the non-resident libraries.Previously consult the next higher TAC level.

A30828-X1187-N585-2-7620 79


NM:SWSW422

42 Actualize the APS name.The last place of the APS name (= correction version) is to be adapted to therepresentation within the name of the new generation (= 4th place, xxxXxxxx),using the MML command ENTR APSNAME.

Example:old generation: 9021xxxxold APS name: xxxxxxxx9021

new generation: 9022xxxxnew APS name: xxxxxxxx9022

b ENTR APSNAME:NAME=newname;

43 Decision.Were patches deleted in a previous procedure step? Y h...44

N h...45

44 Reenter patches.

All deleted patches are to be reentered from the current patch MO.After that, continue with the procedure.

45 Define process switches.b RESET CFOPT;

46 Start command file CHECK HWCONFRPL.

Postprocessing after LOADLIB replacement is to be executed.

b CHECK HWCONFRPL


!TAC2 is to be called in!

80 A30828-X1187-N585-2-7620

NM:SWSW422


47 Activate X25LINKs.All X25LINKs, which were deactivated before the LOADLIB replacement, arenow to be reactivated.In the following command, the number of the X25LINK which is to be config-ured, is to be entered for no.

b CONF X25LINK:X25LINK=no,OST=ACT;

Important note:The Application BCT-BOOT (V24-Interface) is to be deactivated on the OMT-0(NetM) after the activation X25LINKs.

48 Enter meter save times and release routine test.The meter save times are to be entered in the same way as they were before thereplacement of non-resident libraries (see DISP METSAV protocol).Hereto in the following command a corresponding time is to be entered forhh-mm and a corresponding number is to be entered for value.The command is to be entered for each individual save time.

b ENTR METSAV:TIME=hh-mm,CHEKNO=value;

In addition, the routine test is to be released.b ALLOW SSPRT;

49 Define process switches.b RESET CFOPT;b SET CFOPT:ON=12;

50 Start command file CHECK SYSSTAT.


Attention!If the error messageSyntax Check ReportError: ..... Task xxxxx does not exist in the task databaseis output after the following command was entered, then proceed as follows:- in the workbench open the menu Options- there deactivate Verify Syntax- after that start the command file again- after successful execution activate Verify Syntax again (if necessary).

b CHECK SYSSTAT


A30828-X1187-N585-2-7620 81


NM:SWSW422

51 List generations.b DISP GEN;

In the following block generation actgen, which was active before the replace-ment of non-resident libraries and which now has the GCS 9999 (invalid), is tobe deleted.

52 Delete the generation which was active before the LOADLIB replacement.

The previously current generation was replaced by the newly created generationand was set to invalid (GCS=9999). This old generation is to be deleted now.

b CAN GEN:GEN=actgen;

53 Remove MO from MP-MOD.Remove the APS routine save MO from MP-MOD.The MO is to be marked as current APS routine save MP MO and to be heldready for further use.

54 Mount MO in MP-MOD.Mount the MO for LOG data saving.A MO without write protection which is empty or overwritable is to be used.

Now the MO is to be initialized:b CONF MODMP:Side=0,Administrative State=locked,Label=No;b CONF MODMP:Side=0,Administrative State=unlocked,Label=Yes;

55 Decision.Interrogate the status of the LOG function:

Within the file name LOGyx the part y must be determined and jotted downbecause this value is needed for parameter input in some of the followingcommands.

b STAT INPLOG;Was the Log file name LOGy6 determined in the status printout? Y h...56

N h...57

56 Deactivate LOG function.b RSET INPLOG; h...58

82 A30828-X1187-N585-2-7620

NM:SWSW422


57 Open new LOG file LG.LOGy6..

For LOGy6 see the previous STAT INPLOG.

b MOD INPLOGFILE:New log file name=LOGy6;

58 Save the LOG files to the MP-MO.The LOG files which were closed in the previous block are to be saved onto theMP-MO.In the following command the corresponding Log file name is to beentered.

b COPY INPLOGFILE:Log file name=LOGyx,Device name=MOD0;

59 Delete LOG files.Delete the LOG files which were saved onto MP-MO in a previous procedurestep:

b CAN INPLOGFILE:Log file name=LOGyx,Device name=MDD;

60 Decision.Was the LOG function deactivated with MML command RSET INPLOG beforethe LOG files were saved? Y h...61

N h...62

61 Activate LOG function.

For LOGy6 see the previous STAT INPLOG.

b SET INPLOG:Log file name=LOGy6;

62 Remove MO from the MP-MOD.Remove the MO with the saved LOG files from MP-MOD.

63 Mount MO in CP-MOD.The current APS routine save CP MO should still be mounted in the CP-MOD.If necessary:Mount the CP-MO for APS routine saving.The APS routine save CP-MO which was removed last is to be used.

64 Mount MO in MP-MOD.Mount the MP-MO for APS routine saving.The APS routine save MP-MO which was removed last is to be used.

65 Execution of procedure SW210.APS quarterly saving is to be executed according to procedure SW210. h...SW210

A30828-X1187-N585-2-7620 83


NM:SWSW422

END

84 A30828-X1187-N585-2-7620

NM:SWSW422


A30828-X1187-N585-2-7620 85


NM:SWSW441

2.4 Exchange of PSW files (for NE with SSNC)

SW441

2.4.1 General information.

Larger-scale software corrections or the introduction of new features in/into the periph-eral software may require the exchange of one or more PSW files. The exchange ofPSW files is to be executed according to the present procedure.

Attention:This procedure is executed only on the CP. There are no actions necessary on the MP.

This procedure constitutes a dangerous intervention in the operating EWSD system.Redundancy and stability of all units must be ensured before it is carried out.

By exchanging PSW files a new generation is created.A short interruption of operations is unavoidable because a recovery is started automat-ically, as soon as the new generation is valid: If an already existing PSW file of type LTG-LIB is exchanged, an ISTART2R is initi-

ated. In this case the procedure should be carried out only during periods of lowtraffic volume.

If a new PSW file of type LTG-LIB is entered, a NSTART1 is initiated. In this casethe procedure can be executed at any time.

If an already existing or new PSW file of type IOP-LIB or IPH-LIB is exchanged orentered, a NSTART0 is initiated.

Interruption of the procedure should be avoided.

For reasons of security before and after an exchange of PSW files the current APS is tobe saved. Before the exchange the next saving which is planned according to the safe-guarding schedule is to be executed.In any case a quarterly saving is to be executed after the exchange.In order to avoid a double execution of the time-consuming quarterly saving, theexchange of PSW files is to be planned for a time period where the next saving is aroutine saving.

In the procedure it is expected, that the PSW files to be exchanged are held ready on amagneto optical disk, where they must be stored according to the name conventionsand without being linked to any generation.

86 A30828-X1187-N585-2-7620

NM:SWSW441


Abbreviations:In connection with data transfer from/to magneto optical disk the following abbreviationsare used:

Attention!Note on synchronization of the MDDs:

After each synchronization of the MDDs (e.g. after recovery, configuration of the MDDsetc.) a CHECKSUM MDD AUDIT is started automatically, if the status of theMDDAUDIT is UNLOCKED. The audit starts after the synchronization of the MDDs isfinished and it lasts about 6 minutes. The result of the audit must have been displayedbefore proceeding further!If the audit detects a checksum error for one of the MDDs, this error is to be repairedaccording to procedure SW500 before the current procedure is continued. An inad-vertent copying of the error to the other MDD is therefore prevented.

The following MOs are to be held ready. MO with new system files (non-resident libraries)For saving the valid APS generation: 1 MO for saving the CP generation 1 MO for saving the MP generation and the LOG files 1 MO for saving the logical charging data from the CP-MDDFor saving the new APS generation: 1 MO for saving the CP generation 1 MO for saving the MP generation and the LOG files 1 MO for saving the logical charging data from the CP-MDD

MOD magneto optical disk deviceMO magneto optical disk (=save medium)FLD Floppy DiskOMT OMT denotes the operation terminal which is in use

(e.g. PC, NetM, EMN/OS etc.)

A30828-X1187-N585-2-7620 87


NM:SWSW441

2.4.2 Procedure description

1 List catalog entries - IA. files.b DISP FILE:FILE=IA.;

2 List catalog entries - CA. files.b DISP FILE:FILE=CA.;

3 List catalog entries - LG. files.b STAT INPLOG;


Remove the APS routine save MO from CP-MOD.The MO is to be marked as current APS routine save CP MO and to be heldready for further use.

5 Mount MO in CP-MOD.Mount the MO with the new PSW files.

6 Transfer system files to the background memories.b TRANS FILE:FILE=NEW.PSW./SY.PSW.,VSNS=archivename,

MODE=CRD;All PS

Documents

DocumentSW