Aps

EWSD

Application Program System

1.0 Introduction: The application program system (APS) covers the software stored on external memory (magnetic disk) in a certain EWSD exchange, in the common memory (CMY) of the CP and in the memories of GPs and which must be loaded upon initial start up. Together with the hardware and firmware, the APS forms a certain exchange according to following criteria: According to type: • local exchange • long distance exchange • international gateway exchange • mobile switching centre According to operating company features: • call-processing and O&M features. According to scope and type of line assignment: • line categories, trunk groups, etc. According to network environment: • administration of traffic routes, zoning, tariffs, etc

ALTTC/SW-II

1/46

5.4-APS/1.08.2002

EWSD

Application Program System

In the exchange, the APS is loaded to the CMY of the CP and the external memory. The APS contains recovery, backup (save) and generation files. In EWSD software is categorized in the following way:

Resident Software Software modules belonging to the above group are linked in one major linkage run and deposited in a file named SY.TASKLIB or SY.PSW.Txxx. The term “resident” signifies that the software is permanently in the memory.

Non Resident Software Some modules are linked to form one unit (e.g. a non-resident process) and stored in a file named SY.LOADLIB. The latter file contains many-separate-units which are generated by many -separate-linkage runs. The term “non-resident” signifies that the unit is loaded to memory when required.

Off-line Software These modules are stored in a file -e.g. SY.INSTALL- in an additional linkage run. The modules are not required for running operations but instead to initialize a hard disk, for example, or to copy to disk the storage content of magnetic tape.

ALTTC/SW-II

2/46

5.4-APS/1.08.2002

EWSD

Application Program System

Firmware By means of a special device, programs subsequently required to be stored in the PROM are installed as FW in the PROMS after linkage.

2.0 APS Files and Data 2.1 Version-SW This is the basic component of the APS and consists of CHILL-and Assembler-modules for the central processor and all group processors. It includes all planned feature for this version of APS.

2.2 Exchange Type-SW It contains general SW components of the APS, which are required whenever the same exchange type is used. e.g. generic L (Local) or generic T (Transit) etc.

2.3 Project specific-SW It includes SW components and variants, which are only developed for certain projects i.e. realization of special types of signaling. The components 1 and 2 do not contain this software.

2.4 ALTTC/SW-II

Base APS (BAPS) 3/46

5.4-APS/1.08.2002

EWSD

Application Program System

It is composed of 2.1,2.2, and the 2.3. The Base-APS contains all planned, global features and all data structures for one project. The data modules are generated in the BAPS with initial values from the minimal database (MDB). The CPsoftware is realized in CHILL or Assembler, the GP-software in Assembler. The CP-software is contained in the files: SY.TASKLIB resident CP-software SY.LOADLIB. MA non-resident masks SY.LOADLIB. LA non resident CP-software SY.LOADLIB. CA non resident command descriptions The GP-software is contained in the files: SY.PSW.Txxxx The CCNC-software is contained in the files: SY.PSW.T097 SY.PSW.T098

processor software for CCNC-CPI processor softawre for CCNC-SIMP

The SW for IOP-SCDP is contained in tthe file: SY.PSW.T100

2.5 Exchange Specific Data (ESD)

ALTTC/SW-II

4/46

5.4-APS/1.08.2002

EWSD

Application Program System

This data the so called DATA BASE is input in MMLformat into the APS. It is delivered on a magnetic tape which stores the necessary command files. It consists of the data groups OCD, HWCD, NOD, SUD.

2.5.1

ODAGEN-Control Data (OCD)

This data is needed by ODAGEN, to expand the data modules according to exchange specifications. The file CF.ODAGEN contains the relevant commands.

2.5.2 Hardware-Configuration (HWCD)

Data

This data results from the hardware relevant construction data of an exchange (i.e. CR LTG: create line trunk group or CR CRMOD: create code receiver module). The command files on tape are often called CF.HW1, CF.HW2, CF.DLU,......etc.

2.5.3

Network Operation Data (NOD)

This data results from zoning, tariffing, trunk types, trunk group allocation, numbering system and routing of an exchange.

2.5.4

ALTTC/SW-II

Subscriber Data (SUD)

5/46

5.4-APS/1.08.2002

EWSD

Application Program System

This data results from the subscriber lines and from the port numbers of an exchange. Data is thus normally given by the administration.

2.6 Data Area (ODAGEN) Sufficient memory space for the data modules of a customer specific APS is generated with ODAGEN, by means of the ODAGEN- control data.

2.7 Customer Specific APS In this APS , the data area generator ODAGEN generates sufficient memory space for the data modules. The size of the data modules in the C-APS is selected in such a way that all exchange specific data could be stored.

2.8 Exchange Specific Customer-APS (ECAPS) It is ready for use for exchange opeartion. All necessary data is incorporated in the exchange, the additional modification to the SW is done and the correct function is tested.

3.0 EWSD Files: 3.1 System Files ALTTC/SW-II

6/46

5.4-APS/1.08.2002

EWSD

Application Program System

System files are essential to system opeartion and are therefore permanently stored as double files on both magnetic disks. For security reasons (e.g. failure of both the magnetic disks), these files are regularly copied to a backup tape. They are: SY.TASKLIB

Resident CP software ( Basic APS file) SY.SEMILIB Semipermanent CP data SY.SIMP Semipermanent CCN data (CCNC data base) SY.LOADLIB.LA Non resident CP software (Basic APS file) SY.LOADLIB.MA Non resident output masks (Basic APS file) SY.LOADLIB.CA Non resident command descriptions (Basic APS file) SY.GENLIST List of all files which belong to various generations SY.INSTALL Offline program for loading the APS.(Basic APS file) SY.SLRAM Part of SY.INSTALL: required for startup from disk SY.TRANSLOG Intermediate storage for updating the file SY.SEMILIB SY.PSW.Txxx Software for GP and CCNP (Basic APS file) SY.MSGXREF Version dependent information about SY.SEMILIB ALTTC/SW-II

7/46

5.4-APS/1.08.2002

EWSD

SY.SPOOL

Application Program System

Buffer file for output jobs to the OMT

3.2 Safeguarding HISTORY files Safeguarding information messages are collected in these files. Detailed knowledge of the software is required for interpretation of the files. SG.OPER SG.SESYMP SG.RECY

Collects safeguarding messages from/to the periphery Collects all software error symptoms messages Collects safeguarding messages during recovery

3.3 Archive files Alarm messages are stored in these files. HF.ARCHIVE

Stores all messages relating to a mtce. function HF.MCP.HWERROR Stores all messages concerning sporadic CP errors

3.4 Alarm files

Any alarm message which have not yet been dealt with are stored in these file. AM.ALARM ALTTC/SW-II

Alarm messages requiring 8/46

5.4-APS/1.08.2002

EWSD

HF.ALARM

Application Program System

intervention by mtce. person remain stored in these files until completion of repair.

3.5 Call charge files The subscriber charge meter levels, statistics meters and trunk meters are stored in these files. CA.SU.UCHA CA.ST.UCHA CA.TR.UCHA CA.IC.UCHA

Subscriber charge meter Statistics meter Trunk meter ICHASTA meter

3.6 Individual recorded call data The complete call data are stored in these files IC.ICMAL Malicious call data IA.ICISA ISDN subscriber charges IA.ICMOB Call data for temporary meter observation IA.ICAMA Data for detailed call record

3.7 Command Files Command files are used either for the installation of mass data (e.g. subscriber data) or for the execution of MML command sequencees which are repeated at regular intervals. CF.xxxxxx Basic APS files

ALTTC/SW-II

9/46

5.4-APS/1.08.2002

EWSD

Application Program System

3.8 Files for test results The test results obtained in the corresponding are stored in these files. e.g. MY.RDS RDS measurement result MY.NACC.1234 Test result for test job with job number 1234

3.9 Traffic Recording and PCM monitoring files These files contain data recorded for traffic measurements & PCM monitoring. TS.xxxxxxxxx file for traffic measurement data TM.xxxxxxxx file for PCM alarm statistics data.

4.0 Development and Installation of APS 4.1 Development Source library Following flow chart displays, how the APS is (basic components developed. of the APS) Compiler/Assembler Linker Basic APS (SY.Files): 5.4-APS/1.08.2002 10/46 The BAPS contains after passing the Integration Department the complete (project specific and general parts) SW of an APS-version for a country. The database is not yet adapted to a specific exchange

ALTTC/SW-II

EWSD

Application Program System

Adaption of size and contents of an APS to the requirements of a specific exchange is done during the APS installation procedure. Together with the APS tapes and manuals the APS-RELEASE documentation is delivered to the customer. Example: RELEASE DOCUMENTATION P30305-V2054-V166-05-7620 EWSD-APS GRICBV1V.6640 VERSION 6.2 W, CP113 Contents • additional information (e.g. SW/HW dependencies) • scope of delivery (e.g. how many tapes, manuals...) • patch descriptions • operator hints

4.2 Identification of the magnetic tapes: ALTTC/SW-II

11/46

5.4-APS/1.08.2002

EWSD

Application Program System

An APS, and the appropriate exchange specific data are brought, in general, on magnetic tapes to the exchange. Thus, several magnetic tapes are distinguished: • magnetic tape with B-APS • magnetic tape with ODAGEN and DATA BASE • magnetic tape with command files which contain modifications to the CP-SW • magnetic tape with command files which contain modifications to the GP-SW • magnetic tape with command files for COFIP-procedures The VSN(volume serial number) for the magnetic tapes are listed in the valid APS release documentation.

4.3 Installation (general information) In the basic APS delivered by the manufacturer all expandable data structures are presented in minimal sizes and are provided with initial values. Example : one LTG Initial Value : operational status “planned” Procedure used for the installation of new APS is known as “INSTALLATION RECOVERY”. It consists of following main steps: • transfer of the APS files onto the hard disk. ALTTC/SW-II

12/46

5.4-APS/1.08.2002

EWSD

Application Program System

• boot from hard disk and start installation recovery • expansion of data structures according to the exchange specifications (ODAGEN) • modification to the CP-and GP-SW (if necessary) • supply the expanded data structures with data. The final status is an APS with incorporated data, i.e. an APS specific for that exchange. The installation is carried out in several steps. The procedure “installation recovery” is a part of maintenance manual and the ITMN:INSTALL. The name of the procedure is SW-140.if it is on mag. tape. For MOD it is SW-141

4.4 Installation Recovery (Main Steps): The following figures and explanations give an overview of the first installation of an APS in a new EWSD exchange.

4.4.1

Formatting and Labeling the MDDs:

Basic APS tape is mounted on the MTD. Using the Boot key on the BAP master, the CP113 is to be started in the offline mode. The disks must be first prepared. For this, sectors are entered in the disks, provided with addresses, and then tested. Substitute sectors must be entered in the event of faulty sectors. This procedure is known as initialisation or ALTTC/SW-II

13/46

5.4-APS/1.08.2002

EWSD

Application Program System

formatting. The disks are subsequently assigned names(labeled), and the file SY.SLRAM is created in specific sectors. The contents of this file are the loaders CIL(core image loader), BIOS(basic input/output system) and IML(installation monitor loader), which were originally stored on the tape in one file, SY.INSTALL, together with IMON. IMON is used to execute the disk preparation ( commands INIT MD, LABEL MD). The file SY.TRANSLOG is generated additionally. Fig 4.1.1 gives the sequences of this step.

IPL a

b IMON c

BIOS CIL Fig 4.1.1

4.1.2 ALTTC/SW-II

SY.SLRAM SY.TRANSL

M

a) Transfer of IMON, in the memory. b) Formatting and labeling of MDDs. c) Creation of SY.SLRAM and SY.TRANSLOG in MDDs.

Loading the APS files from MTD to 14/46

5.4-APS/1.08.2002

EWSD

Application Program System

MDD: Now the entire software must be copied from tape to disk. The entire software means the SW for CP,LTG,DLU,CCNC,IOP. IMON is again used for the copying procedure(command TRANS FILE). IPL SW IMON

SY.SLRAM SY.TRANSLOG

Fig. 4.1.2

4.1.3

Loading resident CP-SW:

The CIL (from SY.SLRAM) is used to load the TASKLIB( resident CP-SW) to the CMY and to the LMY of the BAPM. AT this point of time tasklib contains resident code and the minimal database, i.e. expandable tables are defined at minimum size. This will be performed by booting the processor. IPL

a CIL

b

Memory ALTTC/SW-II

15/46

SY.SLRAM SY.TRANSLOG SY.TASKLIB SY.LOADLIB.LA SY.LOADLIB.CA SY.LOADLIB.MA SY.PSW.Txxx 5.4-APS/1.08.2002 SY.INSTALL

EWSD

Application Program System

Fig 4.1.3 a) CIL is transferred to CMY b) SY.TASKLIB is loaded using CIL.

4.1.3

Preparation for expanding the data tables:

• copy back to disk, in a file named SY.SEMILIB, the permanet data (P data) in the data base. • combine the SY. files into one generation and name the latter. New generation is entered in the file SY.GENLIST • “inhibit” the P files in the tasklib. SY.GENLIST IPL CODE SY.SLRAM P-DATA SY.TASKLIB SY.LOADLIB.LA HEAP(Free SY.LOADLIB.CA Space) SY.LOADLIB.MA SY.PSW.Txxx T- DATA SY.INSTALL Memory SY.SEMILIB ALTTC/SW-II 16/46 5.4-APS/1.08.2002 SY.SIMP

EWSD

Application Program System

Fig. 4.1.4

4.1.5

Expanding the data tables:

The data tables can now be expanded on the disk with ODAGEN (office data generator tape). ODAGEN copies to disk the files SY.LOADLIB.LA, SY.TASKLIB and SY.SEMILIB and expands the latter two files as dictated by the command(MML command MOD DB SIZE). In order to have the expanded data base in the CP, CIL is used to reload the SY.TASKLIB( this is a new TASKLIB which corresponds with the new addresses of the SEMILIB data tables) and SY.SEMILIB. Upto this moment the expanded data tables are not yet filled with data. They are filled with logical “0”. SY.GENLIST IPL a SI SL TL LLL FIRST CODE GENERATION P-DATA b SI SL TL HEAP(Free LLL SECOND Space) PS LL LLM GENERATION ODAGEN T- DATA Memory ALTTC/SW-II

17/46

5.4-APS/1.08.2002

EWSD

Application Program System

Fig. 4.1.5 a) data tables are expanded. b) CIL loads the new SEMILIB and TASKLIB into the memory. Abbreviations in the diagram 4.1.5 :SL= SY.SEMILIB LLL= SY.LOADLIB.LAPS= SY.PSW.Txxx SI= SY.SIMP LLC= SY.LOADLIB.CA TL= SY.TASKLIB LLM= SY.LOADLIB.MA

4.1.6

Incorporation of exchange specific data base:

Command files(ENTR and CONF commands) are used to fill up the tables in the memory. After starting the command files the stored MML commands are executed one after each other. The data tables in SY.SEMILIB and CMY are now filled with the exchange specific data. These changes are reproduced on the disk ( with UPDATE). IPL CF. command files ALTTC/SW-II

Data base

HEAP(Free Space) ODAGEN 18/46

T- DATA Memory

SY.GENLIST UPDATE

CODE P-DATA

SI

SL

TL LLL

SI SL TL LLL 5.4-APS/1.08.2002 PS

LLC

LLM

EWSD

4.1.7

Application Program System

Fig. 4.1.6 Note: Abbreviations are same as in fig.4.1.5.

Loading of peripheral SW:

Finally the periphery must be loaded likewise. This entails the transfer of the codes(various load types SY.PSW.T0xxx) to the LTG and CCNC. The data components for the LTG and DLU are loaded from CMY, the data for the CCNC from SY.SIMP( for SIMP) and from CMY (for CPI). On completion of this final step, normal EWSD operation is established. That is to say the system is running, subscriber can telephone, call charges are stored and operator input is possible. CCNC

LTG

LTG

CODE P-DATA

PSW PSW

HEAP T-DATA

ALTTC/SW-II

PSW

19/46

5.4-APS/1.08.2002

EWSD

Application Program System

Fig. 4.1.7

5.0 APS-Generation Concept: The generation concept offers the possibility for several, chronologically ordered application program systems, called APS-Generations. Thus, a manually or automatically-controlled return to an operable APS of an older state is possible whilst recovery measures are being taken. this is necessary if a newly incorporated APS (=new generation) or changes in the program code or data (-> changed generation) prove to be faulty or even inoperable. One APS generation is always made up of several files (fig. 5.1). So as not to take up too much memory space on the magnetic disks, files which are identical in several generations are only stored once per disk and are indicated as being part of other generations. For the recovery “fallback to an old generation” concept it is not allowed that files of one generation are shared with other generations (fig.5.2). The table of contents belonging to a generation takes place through the generation list (SY.GENLIST). This contains all the necessary information for a generation - e.g. generation name, indication of status and related disk files - are given. The information from the SY.GENLIST can be read using the following commands: DISP GEN ; (Protocoling of the generation list) DISP GEN : DISPL = FILES, [GEN= (Display of the files of a generation)

];

Each APS consists of several files SY.TASKLIB SY.LOADLIB.LA SY.LOADLIB.MA SY.LOADLIB.CA SY.SEMILIB SY.PSW.xxx • ALTTC/SW-II

This APS will be called Generation A

20/46

5.4-APS/1.08.2002

EWSD

Application Program System • SY.SIMP

Fig. 5.1 : Files of an APS Generation In the file label (F1) each file is indicated as belonging to generation A. Should, for example, files be changed as a result of changing the data base area, (ODAGEN), a new generation will result in the following way. Changed files are created new for the new generation and unchanged files are shared. In the files SY.LOADLIB.CA, SY.LOADLIB.MA and PSW-files, no data is changed and it thereofre belongs to both generations. Generation A SY.TASKLIB SY.LOADLIB.LA SY.SEMILIB SY.SIMP

Generation B SY.TASKLIB SY.LOADLIB.LA SY.SEMILIB SY.SIMP SY.LOADLIB.CA SY.LOADLIB.MA SY.PSW.xxx

Fig. 5.2 : Files of two generations The generations are distinguish by a 4byte HEX-value called generation name If files belong to several generations, this is indicated in the power set.

(Fig. 5.3).

DISPGEN ; NAME OF ACTUAL GENERATION : 11500100 LIST OF GENERATIONS : HISTORY

GENERATION

VALIDITY

FILES

CREATION

DATE

ODAGEN

11500100

VALID

13

93-09-03

13:59:56 2

11500034

BACKUP

11500123

VALID

13

93-09-03

16:06:03 4

11500100

GOLDEN

11500121

VALID

13

93-09-03

15:12:09 1

11500100

DISPGEN:DISPL=FILES;

ALTTC/SW-II

SET

REFGEN

ACCEPTED

21/46

5.4-APS/1.08.2002

EWSD

Application Program System

DISPGEN: DISPL= FILES; NAME OF THE ACTUAL GENERATION :11500100 VALIDITY : VALID LIST OF ALL FILES OF GENERATION : 11500100 file: sy.loadlib.ca sy.loadlib.la sy.loadlib.ma sy.psw.t002 sy.psw.t004 sy.psw.t050 sy.psw.t090 sy.psw.t097 sy.psw.t098 sy.psw.t100 sy.tasklib sy.semilib sy.simp

powerset: h’00000004 h’00000004 h’00000004 h’00000004 h’00000004 h’00000004 h’00000004 h’00000004 h’00000004 h’00000004 h’00000004 h’00000004 h’00000004

disk0: VALID VALID VALID VALID VALID VALID VALID VALID VALID VALID VALID VALID VALID

disk 1 VALID VALID VALID VALID VALID VALID VALID VALID VALID VALID VALID VALID VALID

apsvers: 1150 1150 1150 1150 1150 1150 1150 1150 1150 1150 1150 1150 1150

END TEXT JOB 7614

ODAGEN

GEN=11500034(MOD DBSIZE) SY.SEMILIB SY.SIMP SY.TASKLIB SY.LOADLIB.LA

GEN=11500100 SY.SEMILIB SY.SIMP SY.TASKLIB SY.LOADLIB.LA

SY.LOADLIB.MA SY.LOADLIB.CA SY.PSW.Txxx BACKUP/GOLDEN (COPYGEN:OUTPUT=GEN....;) ALTTC/SW-II

22/46

5.4-APS/1.08.2002

EWSD

Application Program System

GEN=11500100

GEN=11500101

SY.SEMILIB SY.SIMP SY.TASKLIB SY.LOADLIB.LA SY.LOADLIB.MA SY.LOADLIB.CA SY.PSW.Txxx

SY.SEMILIB SY.SIMP SY.TASKLIB SY.LOADLIB.LA SY.LOADLIB.MA SY.LOADLIB.CA SY.PSW.Txxx

FIXPOINT/ MERGED (COPYGEN:OUTPUT=FIX...) (TRANSSYFILE:GEN=...., REASON=REINST;) (MERGEGEN:GENTASKL=...., GENSEMIL=....) GEN=11500101

GEN=11500102

SY.SEMILIB SY.SIMP

SY.SEMILIB SY.SIMP SY.TASKLIB SY.LOADLIB.LA SY.LOADLIB.MA SY.LOADLIB.CA SY.PSW.Txxx

Meaning of the generation name : ALTTC/SW-II

Fig. 5.3: Example of Create Generations

23/46

5.4-APS/1.08.2002

EWSD

Application Program System

Generation name

11

50

0

1

00

Version Correction Status Local Correction counter ODAGEN counter Fixpoint counter The local correction counter is incremented during APSCHG, the ODAGEN counter after each ODAGEN run, the FIXPOINT counter after the routine or quarterly saving. Meaning of the power set : The power set indicates how many generation a file belongs to. FILE: POWERSET: -------------------------------------------------------------------------------SY.LOADLIB.CA H’0000000A binary bit position ...... 6543210 = SET Nr. power set ...... 0001010 The file SY.LOADLIB.CA belongs to the generation set 1 and 3. Possible Generation labels in the file SY.GENLIST INSTALL

Name of the first generation created during installation

ODAGEN

Created by extending the data base

APSCHG

Created in the case of APS change with the command ENTRGEN.

BACKUP

Created during routine saving. A copy of all files belongong to the actual generation.

GOLDEN

Created during quarterly saving. A copy of all files belonging to the actual generation which has been “startup tested”

ALTTC/SW-II

24/46

5.4-APS/1.08.2002

EWSD

6.0

Application Program System

FIXPOINT

Copy of the data base SY.SEMILIB, SY.SIMP on disk or tape (FIXPOINT-generation)

MERGED

Merging of code and data of different generations

Sequence of Individual Actions of procedure SW 140 ( Summary): This procedure includes the following individual actions:

6.1.1 Memory unit(MU) and background memory (MDD) are initialised (formatted and labeled) 6.1.2 All necessary files are transferred from magnetic tape onto magnetic disk. 6.2

Loading and starting the opearting system from magnetic disk (initial start) with the special start address.

6.3

START FCP (File control Process) duplicated files are automatically copied from one magnetic disk to the other ( doubled and synchronized ).

6.4

START O&M Process for the operation and mainenance (O&M) is started i.e. UPDATE process is

started. 6.5

ENTR INSTGEN

6.5.1 Installation generator is started. 6.5.2 The first generation of APS-files is made and the file SY.GENLIST is created. 6.5.3 The file SY.SEMILIB is created and all semiresident data from SY.TASKLIB are transferred into SY.SEMILIB. 6.5.4 The address relations between TASKLIB and LOADLIB are created. 6.6

ENTR TIME System-time and date is entered.

ALTTC/SW-II

25/46

5.4-APS/1.08.2002

EWSD

Application Program System

6.7

START SFGSW All safeguarding processes are started.

6.8

START CSWD The process group for the configuration of the peripheral units is started.

6.9

EXEC CMDFILE:FILE=cf.mf. ..... All patches, possible in INSTALL, are entered. the start sequence and the name of the command file can be found in the APS release documentation. 6.10

ENTR EXDDAT..... The exchange description data are input:counntry and network identifier, DE-type,Meter-type.

6.11

MOD DEAUT Device authorisation for both OMTs are entered.

6.12

MOD DBSIZE With the help of the program ODAGEN(office data area generator), the expandable data area are brought to the desired size. A command file which contains the necessary MMLcommands to modify the data structure is supplied by the manufacturer. The name of the file can be found in the APS-release documentation. 6.13 Second installation recovery: loading the ODAGEN generation from MDD into the CMY. 6.14

SAVE MET Generation of meter files.

6.15

IAR STAT Call charge registartion between two exchanges which are separately administrated.

6.16 Incorporation of data base which can be executed in installation mode. The relevant command files are started. 6.17

RECOV SYSTEM:LEVEL=ISTART2F; The APS with extended data structure (ODAGEN & DATA BASE) is loaded from magnetic disk. 6.18

Software modifications for the semiresident software are started.

6.19

Incorporation of dat base which can be executed in operation mode only.

ALTTC/SW-II

26/46

5.4-APS/1.08.2002

EWSD 6.20 6.21

Application Program System

Deletion of files no longer needed ODAGEN-auxiliary files Command files EXEC CMDFILE:FILE=CG.SA.REC54; creation of a fall back gneration.

6.22

SAVE TAPE

6.23

Start the exchange from the save tape.

7.0

APS-Saving Concept

7.1

General Requirements Contents of a fallback generation on disk A fallback generation on disk is either a generation with the attribute BACKUP, created during the routine saving, or a generation with the attribute GOLDEN. The later is created during the quarterly saving and startup tested afterwards. (only for exchanges with 780 Mbyte background memories). Fallback generation and golden generation consist of an equal number of files since the file lists of the two generations are identical, the generations can only be identified by their HISTORY attributes (GOLDEN or BACKUP respectively). A fallback generation labeled as GOLDEN remains unchanged in the background memories during the whole saving cycle. At the beginning of the next cycle, i.e. the date of the next quarterly saving, the golden generation is updated by the actual generation and startup tested afterwards. At this time the fallback generation with the attribute BACKUP will be deleted on the background memories. A new fallback generation labeled as BACKUP is created during each first routine saving in the current quarter and is updated by the actual generation during all later routine savings. The following files are essential parts of a fallback generation on disk: SY.GENLIST SY.LOADLIB.CA SY.LOADLIB.LA SY.LOADLIB.MA SY.TASKLIB SY.PSW.Txxx (number depending on project)

ALTTC/SW-II

27/46

5.4-APS/1.08.2002

EWSD

Application Program System

SY.SEMILIB SY.SIMP •

Contents of a fall back generation on tape The following files are parts of a golden or fallback generation on tape : SY.GENLIST SY.INSTALL SY.LOADLIB.CA SY.LOADLIB.LA SY.LOADLIB.MA SY.TASKLIB SY.PSW.Txxx (number depending on project) SY.SEMILIB SY.SIMP SY.MSGXREF CG.SA.yyyy (save procedures) The generation with the attribute FIXPOINT, which is created on tape during the routine saving, consists of the following files : SY.GENLIST SY.SEMILIB SY.SIMP The tape contains in addition all LOG files which were created since the last quarterly saving was carried out. Additional the meter files which are saved daily are also written to that tape.

7.2

Command Files for APS Saving Command files for quarterly/routine saving and meter saving

TAPE

MOD

ROUTINE SAVING METER SAVING

CG.SA.R11AP CG.SA.M11AP

CG.SA.R21AP CG.SA.M21AP

Qrly SAVING

CG.SA.Q11AP CG.SA.Q12AP CG.SA.M11AP

CG.SA.Q21AP CG.SA.Q22AP CG.SA.M21AP

METER SAVING

ALTTC/SW-II

28/46

5.4-APS/1.08.2002

EWSD

Application Program System

The command files are to be started manually according to procedure SW210 at predetermined times. Procedure SW210 is used for the saving and generation of an APS fallback generation on disk. In case of a quarterly saving a complete generation is also saved on tape. In case of a routine saving only the semipermanent data (in the files SY.SEMILIB and SY.SIMP) are saved on tape. Please note SW-140 SW-141 SW–210 SW-211 SW-212 SW-213 SW-216 SW-217

7.3

SOFTWARE PROCEDURE FOR INSTALLATION RECOVERY ON MAGTAP SOFTWARE PROCEDURE FOR INSTALLATION RECOVERY ON MOD APS SAVING PROCEDURE START-UP TEST AFTER QRLY SAVING QRLY SAVING ON MAGTAP ROUTINE SAVING ON MAGTAP QRLY SAVING ON MOD ROUTINE SAVING ON MOD

Saving of Meters The type and number of meter files are project-dependent. The meter files CA.xx.UCHA or MS.TFSUCHA are to be saved daily. The following files can exist : CA.SU.UCHA (for subscriber charge meters) CA.ST.UCHA (for statistic counters) CA.IR.UCHA (for inter admn. & revenue meters ) CA.TR.UCHA (for trunk control meters) CA.IC.UCHA (for ICHASTA meters) MS.TF.UCHA (for TFS charge meter i.e.toll free service) From version 10 onwards we use ICHASTA meters in place of IAR ,ST and TR meters. The meter file saving is to be done using the command file CG.SA.M11AP for magtap or CG.SA.M21AP for MOD. The command file is to be started daily by a time job. The saving of individual data is done using the command files CG.SA.RCAMA, CG.SA.RCMAL, CG.SA.RCMOB, CG.SA.RCDNB and CG.SA.RCTST.

7.4

Saving Handling

7.4.1 Tape Saving Stages ALTTC/SW-II

29/46

5.4-APS/1.08.2002

EWSD

Application Program System

The two-stage saving principle gives the EWSD user the greatest possible safety in the generation and management of APS save tapes.

Level

Saving Stage

Group

1

APS routine saving

A

2

APS quarterly saving

B

7.4.2 Time Management For each exchange and year the following tapes are required for the two saving stages : Level

Saving Stage

Group

Quantity

Size

1

APS routine saving

A

4 large tapes

730 m

2

APS quarterly saving

B

6 large tapes

730 m

The tapes must be kept in a separate place, sorted and identified according to groups. The tapes of the various groups are assigned permanent VSN designations Tapes of group A: VSN = “LOGTAP”, Tapes of group B: VSN = “SA1TAP” and SA2TAP” and so on. MOD of group A: VSN = “LOGMOD”, MOD of group B: VSN = “SAVMOD” For IA. file saving : if required, large tapes : VSN = “AMATAP” and/or if required, small tapes : VSN = “MALTAP”, “MOBTAP” “DNBTAP”, “TSTTAP” 7.4.3 Fixing of Saving Times Configuration jobs in the CP and peripheral units as well as any kind of disk jobs (e.g. SAVEMET, TRANSBUFFER, local and remote file transfewr of other files) may not be done during saving operations. During APS saving, patches may not be implemented. ALTTC/SW-II

30/46

5.4-APS/1.08.2002

EWSD

Application Program System

MML commands which modify the data base should not be entered during the run time of the command file of the relevant saving branch.

7.4.4 Password Management The password management that is valid at the time of APS saving must be saved in order to ensure that the system can be operated in case of a fallback. The TAC1 must ensure that in an emergency the access time to the saved password management will be as short as possible.

7.4.5 First Application of the Saving Procedure For the introduction of this safeguarding concept the TAC 1 must initiate the following measures. -

Creating the tape management Installing command files The command files are supplied from TAC 2 Fixing the saving times Providing the password management Generating a yearly save tape (Btyy) for recovery check :

-

If the first application does not coincide with an installation, the following actions are not be done. Delete possibly existing previous generations : LIST OF GENERATIONS : History ODAGEN or APSCHG or

ALTTC/SW-II

Generation Validity VALID

Files value

31/46

Creation yy-mm-dd

Date SET hh:mm:s value s

REFGEN <pregen>

5.4-APS/1.08.2002

EWSD

Application Program System BACKUP INSTALL and/or BACKUP and/or name-x



VALID

value

yy-mm-dd

VALID

value

yy-mm-dd

VALID

value

yy-mm-dd

hh:mm:s value s value hh:mm:s s value

<pregen> <pregen> <pregen>

hh:mm:s s

The generation name in the line “NAME OF CURRENT GENERATION” of the printout and in the column “GENERATION” of the printout, called here, identifies the active generation in the system. If the printout contains further entries in the column “GENERATION”, all of these further generations are to be deleted. ; and/or ; and/or ;

7.5

Saving Operation

•

7.5.1 Routine saving Routine saving is considered level 1. At 2-week intervals, a fixpoint of the actual generation and the LOG file are written to a tape of group A. The same tape is additionally used for the daily saving of charge meters on tape. The meter saving is done before, during and after the routine saving. Fourteen days after the 5th routine saving has been carried out, the quarterly saving is done. At the next routine saving date a new tape of group A is to be used. This-14 days cycle is adhered to during the whole life of an APS version.

ALTTC/SW-II

32/46

5.4-APS/1.08.2002

EWSD

Application Program System

During the routine saving (command file) the active LOG file LG.LOGx.Ay is deactivated (RSET LOG) and a new file LG.LOGx+1.A1 is activated (SET LOG:FILE=LOGx1,...). The deactivated LOG file is copied to the save tape which already contains the fixpoint generation. After five routine savings have been carried out within a quarter the LOG files LG.LOG1.A0-A1 up to LG.LOG5.A0-A1 and the latest fixpoint are on the corresponding save tape. The still missing LOG fies LG.LOG6.A0-A1 will be copied to the saving tape during the quarterly saving which comes next.

ALTTC/SW-II

33/46

5.4-APS/1.08.2002

EWSD

Application Program System

routine saving every 2 weeks A1

A2

end of the year A3

A4

A1

2week 12 weeks

B1

B2

B3

B2

B1

B2

Quarterly saving every 3 months Contents of the tape after the first routinly/quarterly saving. Tape A = LOGTAP SY.GENLIST SY.SEMILIB SY.SIMP LG.LOG1-n Dummy UCHA

FIXPOINT

Tape B = SA1TAP SA2TAP SY.GENLIST SY.INSTALL SY.TASKLIB SY.SEMILIB SY.LOADLIB.CA SY.LOADLIB.LA SY.LOADLIB.MA SY.PSW.xxxx SY.SIMP SY.MSGXREF CG.

SNAPSHOT

Fig 7.5.1 : Yearly List of save tapes of groups A and B. ALTTC/SW-II

34/46

5.4-APS/1.08.2002

EWSD (a)

Application Program System Create a FIXPOINT on tape COPY GEN: VSN=LOGTAP, OUTPUT=FIX;

ACT GEN

a) create fixpoint on disk

FIXPOINT

b)

BACKUP

Transfer fixpoint to tape

SY.GENLIST SY.SEMILIB SY.SIMP

GOLDEN

b)

Create BACKUP GEN on disk COPY GEN: VSN = SYSVSN, OUTPUT = GEN ;

ACT GEN FIXPOINT BACKUP (old)

(a) create new BACKUP generation b)

cancel old BACKUP and FIXPOINT generation

BACKUP (new) GOLDEN

Fig. 7.5.2 : Basic steps of routine saving ALTTC/SW-II

35/46

5.4-APS/1.08.2002

EWSD

Application Program System

FIX.1 LG.1 DUMMY

METE RS

FIX.2 LG.1+2 DUMMY METER S

FIX.3 LG.1-3 DUMMY METER S

FIX.4 LG.1-4 DUMMY METER S

FIX.5 LG.1-5 DUMMY METER S

FIX.6 LG.1-6 DUMMY METER S

FIX.1 LG.1 DUMMY METER S

A1

A1

A1

A1

A1

A1

A2

A-GEN

A-GEN B-GEN G-GEN LG.2

G-GEN LG.1

A-GEN B-GEN G-GEN LG.3

A-GEN B-GEN G-GEN LG.4

A-GEN B-GEN G-GEN LG.5

A-GEN B-GEN G-GEN LG.6

B1yy

B1yy

A-GEN G-GEN LG.1

B2

APS (GOLDEN GEN)

APS (GOLDEN GEN)

Abbreviations : B1yy B2 A1 A2 A-GEN B-GEN G-GEN

APS change tape (yearly save tape) Save tape of the first quarterly saving Fixpoint tape with LOG files of the first quarter and charge meter files Fixpoint tape with LOG files of the second quarter and charge meter files Actual generation Backup generation Golden generation Fig.7.5.3 : Overview of APS Saving Sequences

ALTTC/SW-II

36/46

5.4-APS/1.08.2002

EWSD

Application Program System

7.5.4 Using the LOGTAP In order to reduce the expenditure of labor with regards to meter saving the meter files as well as the routinely backup files (LOG-file, FIXPOINT) are saved to a common tape LOGTAP). (a)

Meter saving Normally, the saving of meter files is performed daily. For the saving of new meter files the old ones must be deleted from tape. the saving process is controlled by a command file. To simplify the deletion, a neutral dummy file is created on the tape before the meter file, each of which is deleted afterwards. Thus, all consecutive files are marked as deleted, too.

(b)

Routine saving During every routine saving the tape is initialized. In order to prevent the loss of LOG.files these must first be buffered on disk.

After the FIXPOINT has been created, both, the buffered and the new LOGfiles are saved to tape. Subsequently the meter files are saved to the same tape and the buffered LOG files are retained on disk with TLG.prefix e.g. TLG.LG.LOG1.A1 etc.. 3.2.1.3 Saving time table QS AO

B C D E F G H I K L M N 1.RS 2.RS 3.RS 4.RS 5.RS QS 1.RS 2.RS 3.RS 4.RS 5.RS QS First Saving Quarter A1 Second Saving Quarter A2

A0

First quarterly saving, immediately following the APS installation or the start of The saving schedule

A1

First saving quarter

A2

Second saving quarter

::

::

An Nth saving quarter 3.2.1.4 Contents of save media and disks at the saving time

ALTTC/SW-II

37/46

5.4-APS/1.08.2002

EWSD

Application Program System

Meter saving on medium A0 after the first quarterly saving (immediately following the APS installation of the saving schedule) Section A (medium A0) Before meter saving

LOGTAP A0 or LOGMOD A0 LG.LOG6.A* (LQ.LOG6.A*) --------------------

After meter saving LOGTAP A0 or (LOGMOD A0 LG.LOG6.A* (LQ.LOG6.A*) --------------------DUMMY.MET CA.xxx

MDD-0 / MDD-1 LG.LOG1A* (LQ.LOG1.A* TLG.LG.LOG6.A* (TLG.LQ.LOG6.A * CA.xxx MDD-0 / MDD-1 LG.LOG1.A* (LQ.LOG1.A*) TLG.LG.LOG6.A* (TLG.LQ.LOG6.A * CA.xxx TCA.CA. xx

Section B to G (medium A1) Before1 st routine saving

After 1 st routine saving Tape contents I ALTTC/SW-II

LOGTAP A1 or LOGMOD A1 DUMMY. MET CA.xxx OLD.CA.SU.xxx

LOGTAP A1 or LOGMOD A1 SY. GENLIST 38/46

MDD-0 / MDD-1 LG.LOG1.A* (LQ.LOG1.A*) TLG.LG.LOG6.* (TLG.LQLOG6.A * CA.xxx TCA.CA.SU.xxx OLD.CA.SU.xxx MDD-0 / MDD-1 LQ.LOG2.A* 5.4-APS/1.08.2002

EWSD

Application Program System After execution of I CG.SA.Rxxap I I I

SY.SEMILIB SY.SIMP LG.LOG1.A* (LQ.LOG1.A*) -------------------DUMMY.MET CA.xxx OLD.CA.SU.xxx

(LQ.LOG2.A*) TLG.LG.LOG1.A* (TLG.LG.LOG1A* ) CA.xxx TCA.CA.SU.xxx OLD.CA.SU.xxx

After 2nd routine saving LOGTAP A1 or LOGMOD A1 Tape contents I SY.GENLIST After execution of I SY.SEMILIB CG. SA.RxxAP I SY.SIMP I LG.LOG1.A* I (LQ.LOG1.A*) I LG.LOG2.A* I (LQ.LOG2.A*) ---------------------DUMMY.MET CA.xxx OLD.CA.SU.xxx

MDD-0 / MDD-1

After 3th routine saving Tape contents I after execution of I CG.SA.RxxAP I

MDD-0 / MDD-1

I I I

LOGTAP A1 or LOGMOD A1 SY. GENLIST SY.SEMILIB SY.SIMP LG.LOG1.A* (LQ.LOG1.A*) LG.LOG2.A* (LQ.LOG2.A*) LG.LOG3.A* (LQ.LOG3.A*) -------------------DUMMY. MET CA.xxx OLD.CA.SU.xxx

I

ALTTC/SW-II

39/46

LG.LOG3.A* (LQ.LOG3.A*) TLG.LG.LOG1.A* (TLG..LQ.LOG1.A ) TLG.GG.LOG2.A* (TLG.LQ.LOG2.A * CA.xxx TCA.CA.SU.xxx OLD.CA.SU.xxx

LG.LOG4.A* (LQ.LOG4.A*) TLG.LG.LOG1.A* (TLG.LG.LOG1.A *) TLG.LG.LOG2.A* (TLG.LQ.LOG2.A *) TLG.LG.LOG3.A* (TLG.LQ.LOG3.A *) CA.xxx TCA.CA.SU.xxx OLD.CA.SU.xxx

5.4-APS/1.08.2002

EWSD

Application Program System I I After 4th routine saving Tape contents I After execution of I CG.SA.RxxAP I I I I I I

LOGTAP A1 or LOGMOD A1 SY. GENLIST SY.SEMILIB SY.SIMP LG.LOG1.A* (LQ.LOGQ.A*) LG.LOG2.A* (LQ.LOG2.A*) LG.LOG3.A* (LQ.LOG3.A*) LG.LOG4.A* (LQ.LOG4.A*) --------------------DUMMY.MET CA.xxx OLD.CA.SU.xxx

I

MDD-0 / MDD-1 LG.LOG5.A* (LQ.LOG5.A*) TLG.LG.LOG1.A* (TLG.LQ.LOG1.A *) TLG.LG.LOG2.A* (TLG.LQ.LOG2.A *) TLG.LG.LOG3.A* (TLG.LQ.LOG3.A *) TLG.LG.LOG4.A* (TLG.LQ.LOG4.A *) CA.xxx TCA.CA. SU.xxx OLD.CA.SU.xxx

I I

After 5th routine saving Tape contents After execution CG.SA. RxxAP

ALTTC/SW-II

I I I I I I I I I

LOGTAP A1 or LOGMOD A1 SY. GENLIST SY. SEMILIB SY.SIMP LG.LOG1.A* (LQ.LOG1.A*) LG.LOG2.A* (LQ.LOG2.A*) LG.LOG3.A* (LQ.LOG3.A*) 40/46

MOD-0 / MDD-1 LG.LOG6.A* (LQ.LOG6.A*) TLG.LG. LOG1.A* (TLG.LQ.LOG1.A*) TLG.LG..LOG2.A* (TLG.LQ.LOG2.A*) TLG.LG.LOG3.A* TLG.LQ.LOG3.A*) TLG.LG.LOG4.A* 5.4-APS/1.08.2002

EWSD

Application Program System I I I I

After quarterly saving Tape contents I After execution of I CG.SA.QxxAP I I I I I I I

LG.LOG4.A* (LQ.LOG4.A*) LG.LOG5.A* (LQ.LOG5.A*) ---------------------DUMMY. MET CA.xxx OLD.CA.SU.xxx

(TLG.LQ.LOG4 A*) TLG.LG.LOG5.A* (TLG.LQ.LOG5.A*) CA.xxx TCA.CA.SU.xxx OLD.CA.SU.xxx

LOGTAP A1 or LOGMOD A1 SY. GENLIST SY. SEMILIB SY.SIMP LG.LOG1.A* (LQ.LOG1.A*) LG.LOG2.A* (LQ.LOG2.A*) LG.LOG3.A* (LQ.LOG3.A*) LG.LOG4.A* (LQ.LOG4.A*) LG.LOG5.A* (LQ.LOG5.A*) LG.LOG6.A* (LQ.LOG6.A*) --------------------DUMMY. MET CA.xxx OLD.CA.SU.xxx

MDD-0 / MDD-1 LG. LOG1.A* (LQ. LOG1.A*) TLG.LG.LOG1.A* (TLG.LQ.LOG1.A*) TLG.LG.LOG2.A* (TLG.LQ.LOG2.A*) TLG.LG.LOG3.A* (TLG.LQ.LOG3.A*) TLG.LG.LOG4.A* (TLG.LQ.LOG4.A*) TLG.LG.LOG5.A* (TLG.LQ.LOG5.A*) TLG.LG.LOG6.A* (TLG.LQ.LOG6.A*) CA.xxx TCA.CA.SU.xxx OLD.CA.SU.xxx

I I I I I I

ALTTC/SW-II

41/46

5.4-APS/1.08.2002

EWSD

Application Program System

Section H to N (medium A2) Before tst routine saving

LOGTAP A2 or LOGMOD A2 DUMMY .MET CA.xxx OLD.CA.SU.xxx

After 1 st routine saving Tape contents After execution of CG.SA.RxxAP

ALTTC/SW-II

I I I I I

LG.LOG1.A* (LQ.LOG1.A*) TLG.LG.LOG1.A* (TLG.LQ.LOG1.A*) TLG.LG.LOG2.A* (TLG.LQ.LOG2.A*) TLG.LG.LOG3.A* (TLG.LQ.LOG3.A*) TLG.LG.LOG4.A* TLG.LQ.LOG4.A*) TLG.LG.LOG5.A* (TLG.LQ.LOG5.A*) TLG.LG.LOG6.A* (TLG.LQ.LOG6.A*) CA.xxx TDC.SU.xxx OLD.CA.SU.xxx

LOGTAP A2 or LOGMOD A2

MDD-0 / MDD-1

SY. GENLIST SY. SEMILIB SY.SIMP LG.LOG1.A* LQ.LOG1.A* -------------------DUMMY. MET CA.xxx OLD.CA.SU.xxx

LG.LOG2.A* (LQ.LOG2.A*) TLG.LG.LOG1.A* (TLG.LQ.LOG1.A*) CA.xxx TCA.CA.SU.xxx OLD.CA.SU.xxx

42/46

5.4-APS/1.08.2002

EWSD

ALTTC/SW-II

Application Program System

43/46

5.4-APS/1.08.2002

EWSD Application Program System a) content of LOGTAP before the first routine saving

METERS DUMMY

LABEL

BOT

cancel before each meter saving b)

content of LOGTAP after the first routine saving

METERS DUMMY

c)

LG.1

1.FIXPOINT

LABEL

BOT

cancel before each meter saving content of the LOGTAP after the second routine saving METERS

LG.1 +2

DUMMY

2.FIXPOINT

LABEL

BOT

a) c)

b)

d) sequence : a) b) c) d)

buffer LG-files on disk label tape save FIXPOINT, LG-files, DUMMY & METERS Rename buffered LG-files on disk starting with TLG. Fig. 7.5.4 : Contents of LOG-Tape

ALTTC/SW-II

44/46

5.4-APS/1.08.2002

EWSD

•

Application Program System

7.5.5 Quarterly saving Quarterly saving is considered level 2. It is divided into two sections. 7.5.5a APS saving For quarterly saving, two tapes of group B are normally required. the two save tapes are created in accordance with a fixed time pattern. The first two tapes of this group form yearly tape 1 (B1yy) and are indentical with the APS change tapes. Two further quarterly saves are made, each on two new tapes (B2, B3). When the third quarterly save is done, tapes B2 are overwritten and when the fourth quarterly save is done, tapes B3 are overwritten, etc.. Thus in addition to the APS change tape here are always two pairs of tapes with a complete generation. 7.5.5b Startup test of the GOLDEN generation The save tape created during the first part of the quarterly save is verified acording to the procedure described in SW211. The startup test consists of several stages. First of all, during the software split on the non-switching system side, manual startup is performed of the APS copied in beforehand from the quarterly save tape. This verifies that the CP software can be started up. After this, the test of the startup ability of the GP software is performed on selected LTGs in the merged ON-LINE system. Finally the routine switchover of the CCNC in the night resulsts in the startup test of PSW.T097 and PSW.T098. After a successful startup test, the tape must be marked as having been tested for startup. Note 1 : If a recovery of level OSTART1/2/2R/2F is run between two quarterly saves, the tape created prior to the recovery is question must be specially identified and it must be marked accordingly in the table of the quarterly ovewrview of the APS saving. Note 2 : In addition to the savings performed at fixed times during the year, a quarterly saving must also be performed after the following events :

ALTTC/SW-II

45/46

5.4-APS/1.08.2002

EWSD

Application Program System

ODAGEN, ISTART2G using BACKUP or GOLDEN, CALL PROCESSING BASIC OPERATION, MANUAL BOOTSTRAP. In these cases a startup with the appropriate generation is integrated in the sequence of operations. However, testing of the generation written to tape must still be performed in CP split mode operation in order to check the save tape. In these cases it is then not necessary to check the loadability of the periphery as this has been demonstrated by the successful startup. For SP-SW replacement, a startup test is performed in connection with an ISTART2R; in the case of a double disk failure the startup test is only performed by means of a manual startup. An APS quarterly saving is to be started without a timer job. The save tapes for APS must be created in accordance with MMN procedure SW210 (quarterly saving). a)

Saving of the entire APS (quarterly saving) COPY GEN: VSN = SA1TAP, OUTPUT = GEN;

ACT GEN SA1TAP BACKUP GOLDEN (old) GOLDEN (temp.)

ALTTC/SW-II

a)

create golden gen (temp.) on disk

b)

Transfer golden gen (temp.) to tape

(c)

cancel golden gen (temp.) oon disk

46/46

5.4-APS/1.08.2002

EWSD

b)

Application Program System

Creation a new GOLDEN GEN on disk the new GOLDEN GEN on disk is set to blocked TRANSSYFILE: GEN = , VSN=SA1TAP, REASON = REINST ;

ACT GEN SA1TAP BACKUP GOLDEN (new)

GOLDEN (old) GOLDEN (new)

Fig. 7.5.5a : Basic steps of quarterly saving

Start up test . Split the system SPLIT SSP : TEST = NO; Step 1 and 2 must be performed on the call processing side

ACT GEN BACKUP GOLDEN (old)

Step 1 - format memory - start up with GOLDEN (new)

non call processing side

Step 2 test commands STAT SSP; STAT LOG;

GOLDEN (new)

ALTTC/SW-II

47/46

5.4-APS/1.08.2002

EWSD

Application Program System

Perform all following steps on the call processing side • if test is successful, set new GOLDEN GEN to valid MOD GEN:GEN = , VALIDITY = VALID; • cancel old GOLDEN GEN CAN GEN:GEN = ; • cancel Backup GEN CAN GEN:GEN = ;

ACT GEN

cancel generations

BACKUP GOLDEN (old) GOLDEN (new)

set generation valid

merge system MERGE SSP ;

copy ACT GEN GOLDEN (new) disk-x

disk-y Fig. 7.5.5b : Basic steps of start up test

ALTTC/SW-II

48/46

5.4-APS/1.08.2002

EWSD

Application Program System

Quarterly Saving Procedure A-tape ACTUAL BACKUP 5 GOLDEN X

during last routine saving BACKUP 5 was created on disk; during the last quarterly saving GOLDEN X was created

Fixpoint 5 LG.1.. LG.5

LG.6

ACTUAL BACKUP 5 GOLDEN X LG.6 LG.1

change the LOG function from LG.6 to LG.1 create GOLDEN generation X + 1 from current generation on disk and copy of Btape;

B-tape

-

B-tape

ACTUAL BACKUP 5 GOLDEN X LG.1

transmit files having no generation to tape with GOLDEN X+1 transmit LG.6 to tape of last routine saving and delete from disk.

GOLDEN X + 1

GOLDEN X + 1 SY.MSGXREF CG.

A-tape

Fixpoint 5 LG.1.. LG.6

Fig. 8 ALTTC/SW-II

49/46

5.4-APS/1.08.2002

EWSD

Application Program System

B-tape ACTUAL BACKUP 5 GOLDEN X GOLDEN X+1 LG.1

ACTUAL BACKUP 5 GOLDEN X GOLDEN X+1 LG.1

-

Copy GOLDEN X + 1 to disk GOLDEN X + 1 is blocked.

-

test of CP-SW of GOLDEN X + 1 in CP split

-

deletion of GOLDEN X and BACKUPS if test was successful. Set GOLDEN X + 1 valid.

-

test of LTG-SW in normal operation mode

GOLDEN X + 1 SY.MSGXREF CG.

Fig. 9

ALTTC/SW-II

50/46

5.4-APS/1.08.2002

EWSD

Application Program System

Routine saving procedure a)

Initial routine saving two weeks after APS change, initial installation or quarterly saving

ACTUAL GOLDEN LG.1

ACTUAL GOLDEN LG.2

ACTUAL BACKUP 1 GOLDEN

GOLDEN generation if simultaneously BACKUP generation until the first routine saving

-

change LOG function from LG.1 to LG.2 create fixpoint on tape transmit LG.1 to tape rename LG.1 on disk with TLG. prefix

Fixpoint 1 LG.1

-

Fixpoint 1 LG.1

create BACKUP generation on disk

LG.2

Fig. 10 ALTTC/SW-II

51/46

5.4-APS/1.08.2002

EWSD b)

Application Program System

Routine saving n + 1 (n + 1 < 5)

ACTUAL BACKUP GOLDEN LG.n +1

during nth routine saving, BACKUP n was created on disk and LG.1... LG.n were copied on disk

ACTUAL BACKUP n GOLDEN

-

LG.1.. LG.n LG.n + 1

-

Fixpoint n LG.1.. LG.n

transmit LG.1 ... LG.n from tape to disk initialize tape

ACTUAL BACKUP n GOLDEN LG.n + 2

ACTUAL BACKUP n + 1 GOLDEN

change LOG function from LG.n + 1 to LG.n + 2 create fixpoint on tape transmit LG.1 ... LG.n+1 to tape rename LG.1 ... LG.n+1 on disk with TLG. prefix

- delete the BACKUP generation n and create the Backup generation n + 1 on disk

Fixpoint n + 1 LG.1.. LG.n + 1

Fixpoint n+1 LG.1.. LG.n + 1

LG.n + 2 Fig .11 ALTTC/SW-II

52/46

5.4-APS/1.08.2002