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

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

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 Base APS (BAPS)
ALTTC/SW-II 3/46 5.4-APS/1.08.2002

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 CP-
software 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 processor software for CCNC-CPI

SY.PSW.T098 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

This data the so called DATA BASE is input in MML-

format 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 Data

(HWCD)
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 Subscriber Data (SUD)
ALTTC/SW-II 5/46 5.4-APS/1.08.2002

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

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

SY.SPOOL 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 Collects safeguarding messages

from/to the periphery
SG.SESYMP Collects all software error symptoms
messages
SG.RECY 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 Alarm messages requiring
ALTTC/SW-II 8/46 5.4-APS/1.08.2002

intervention by mtce. person

HF.ALARM 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 Subscriber charge meter

CA.ST.UCHA Statistics meter
CA.TR.UCHA Trunk meter
CA.IC.UCHA 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

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
(basic displays, how the APS is
components
developed. of the APS)
Compiler/Assembler
Linker
ALTTC/SW-II
Basic APS
10/46
(SY.Files): 5.4-APS/1.08.2002
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
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

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

• 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

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 b
a IMON SY.SLRAM
SY.TRANSL
BIOS c
CIL
M
Fig 4.1.1
a) Transfer of IMON, in the memory.

b) Formatting and labeling of MDDs.
c) Creation of SY.SLRAM and
SY.TRANSLOG in MDDs.
4.1.2 Loading the APS files from MTD to
ALTTC/SW-II 14/46 5.4-APS/1.08.2002
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 SY.SLRAM
SY.TRANSLOG
IMON
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 SY.SLRAM
a
SY.TRANSLOG
CIL
b SY.TASKLIB
SY.LOADLIB.LA
SY.LOADLIB.CA
Memory SY.LOADLIB.MA
SY.PSW.Txxx
ALTTC/SW-II 15/46 SY.INSTALL
5.4-APS/1.08.2002
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 SY.SIMP
5.4-APS/1.08.2002
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
CODE FIRST
P-DATA GENERATION
b
HEAP(Free SI SL TL
LLL
Space) SECOND
PS LL LLM GENERATION
ODAGEN
T- DATA
Memory
ALTTC/SW-II 17/46 5.4-APS/1.08.2002

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 SY.GENLIST
CODE
UPDATE
P-DATA
CF. SI SL TL LLL
command HEAP(Free
files Space)
ODAGEN
ALTTC/SW-II 18/46 SI SL TL LLL
5.4-APS/1.08.2002
Data base T- DATA LLM

PS LLC
Memory
Fig. 4.1.6
Note: Abbreviations are same as in fig.4.1.5.
4.1.7 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
HEAP PSW
T-DATA
PSW
ALTTC/SW-II 19/46 5.4-APS/1.08.2002

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 This APS will be called Generation A
SY.PSW.xxx
•
ALTTC/SW-II 20/46 5.4-APS/1.08.2002

•
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 Generation B
SY.TASKLIB SY.TASKLIB
SY.LOADLIB.LA SY.LOADLIB.LA
SY.SEMILIB SY.SEMILIB
SY.SIMP 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 (Fig. 5.3).
If files belong to several generations, this is indicated in the power set.
DISPGEN ;
NAME OF ACTUAL GENERATION : 11500100

LIST OF GENERATIONS :
HISTORY GENERATION VALIDITY FILES CREATION DATE SET REFGEN

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; ACCEPTED
ALTTC/SW-II 21/46 5.4-APS/1.08.2002

DISPGEN: DISPL= FILES;
NAME OF THE ACTUAL GENERATION :11500100

VALIDITY : VALID
LIST OF ALL FILES OF GENERATION : 11500100
file: powerset: disk0: disk 1 apsvers:

sy.loadlib.ca h’00000004 VALID VALID 1150
sy.loadlib.la h’00000004 VALID VALID 1150
sy.loadlib.ma h’00000004 VALID VALID 1150
sy.psw.t002 h’00000004 VALID VALID 1150
sy.tasklib h’00000004 VALID VALID 1150
sy.semilib h’00000004 VALID VALID 1150
sy.simp h’00000004 VALID VALID 1150
END TEXT JOB 7614
ODAGEN
GEN=11500034(MOD DBSIZE) GEN=11500100
SY.SIMP SY.SIMP
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

GEN=11500100 GEN=11500101
SY.SIMP SY.SIMP
SY.LOADLIB.MA SY.LOADLIB.MA
SY.LOADLIB.CA SY.LOADLIB.CA
SY.PSW.Txxx SY.PSW.Txxx
FIXPOINT/ MERGED (COPYGEN:OUTPUT=FIX...)

(TRANSSYFILE:GEN=...., REASON=REINST;)
(MERGEGEN:GENTASKL=...., GENSEMIL=....)
GEN=11500101 GEN=11500102
SY.SIMP SY.SIMP
SY.TASKLIB
SY.LOADLIB.LA
SY.LOADLIB.MA
SY.LOADLIB.CA
SY.PSW.Txxx
Fig. 5.3: Example of Create Generations
Meaning of the generation name :
ALTTC/SW-II 23/46 5.4-APS/1.08.2002

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

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

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 MML-
commands 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

6.20 Deletion of files no longer needed

ODAGEN-auxiliary files
Command files
6.21 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

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 CG.SA.R11AP CG.SA.R21AP

METER SAVING CG.SA.M11AP CG.SA.M21AP
Qrly SAVING CG.SA.Q11AP CG.SA.Q21AP

CG.SA.Q12AP CG.SA.Q22AP
METER SAVING CG.SA.M11AP CG.SA.M21AP
ALTTC/SW-II 28/46 5.4-APS/1.08.2002

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 SOFTWARE PROCEDURE FOR INSTALLATION RECOVERY ON MAGTAP

SW-141 SOFTWARE PROCEDURE FOR INSTALLATION RECOVERY ON MOD
SW–210 APS SAVING PROCEDURE
SW-211 START-UP TEST AFTER QRLY SAVING
SW-212 QRLY SAVING ON MAGTAP
SW-213 ROUTINE SAVING ON MAGTAP
SW-216 QRLY SAVING ON MOD
SW-217 ROUTINE SAVING ON MOD
7.3 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

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

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 :

<DISP GEN;
command repetition
NAME OF CURRENT GENERATION: <actgen>
LIST OF GENERATIONS :
History Generation Validity Files Creation Date SET REFGEN

ODAGEN <acgen> VALID value yy-mm-dd hh:mm:s value <pregen>
or s
APSCHG
or
ALTTC/SW-II 31/46 5.4-APS/1.08.2002

BACKUP
INSTALL <instgen> VALID value yy-mm-dd hh:mm:s value <pregen>

and/or s
BACKUP <backgen> VALID value yy-mm-dd value <pregen>
and/or hh:mm:s
name-x <namegen> VALID value yy-mm-dd s value <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 <actgen> 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.
<CAN GEN: GEN = <instgen> ;

and/or
<CAN GEN: GEN = <backgen> ;
and/or
<CAN GEN: GEN = <namegen> ;
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

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

routine saving every 2 weeks end of the
year
A1 A2 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 Tape B = SA1TAP

SA2TAP
SY.GENLIST SY.GENLIST
SY.SEMILIB FIXPOINT SY.INSTALL
SY.SIMP SY.TASKLIB
LG.LOG1-n SY.SEMILIB
Dummy SY.LOADLIB.CA SNAPSHOT
UCHA SY.LOADLIB.LA
SY.LOADLIB.MA
SY.PSW.xxxx
SY.SIMP
SY.MSGXREF
CG.
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

(a) Create a FIXPOINT on tape
COPY GEN: VSN=LOGTAP, OUTPUT=FIX;
a) create fixpoint
ACT GEN on disk SY.GENLIST
SY.SEMILIB
FIXPOINT b) Transfer SY.SIMP
fixpoint to tape
BACKUP
GOLDEN
b) Create BACKUP GEN on disk
COPY GEN: VSN = SYSVSN, OUTPUT = GEN ;
(a) create new BACKUP generation

ACT GEN
FIXPOINT
b) cancel old BACKUP and FIXPOINT
BACKUP (old) generation
BACKUP (new)
GOLDEN
Fig. 7.5.2 : Basic steps of routine saving

ALTTC/SW-II 35/46 5.4-APS/1.08.2002
FIX.1 FIX.2 FIX.3 FIX.4 FIX.5 FIX.6 FIX.1

LG.1 LG.1+2 LG.1-3 LG.1-4 LG.1-5 LG.1-6 LG.1
DUMMY DUMMY DUMMY DUMMY DUMMY DUMMY DUMMY
METE METER METER METER METER METER METER
RS S S S S S S
A1 A1 A1 A1 A1 A1 A2
A-GEN A-GEN A-GEN A-GEN A-GEN A-GEN A-GEN

B-GEN B-GEN B-GEN B-GEN B-GEN
G-GEN G-GEN G-GEN G-GEN G-GEN G-GEN G-GEN
LG.1 LG.2 LG.3 LG.4 LG.5 LG.6 LG.1
B1yy
B1yy B2
APS APS
(GOLDEN (GOLDEN
GEN) GEN)
Abbreviations :
B1yy APS change tape (yearly save tape)

B2 Save tape of the first quarterly saving
A1 Fixpoint tape with LOG files of the first quarter and charge meter files
A2 Fixpoint tape with LOG files of the second quarter and charge meter files
A-GEN Actual generation
B-GEN Backup generation
G-GEN Golden generation
Fig.7.5.3 : Overview of APS Saving Sequences
ALTTC/SW-II 36/46 5.4-APS/1.08.2002

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 LOG-
files 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
B C D E F G H I K L M N
QS 1.RS 2.RS 3.RS 4.RS 5.RS QS 1.RS 2.RS 3.RS 4.RS 5.RS QS
AO 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

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 MDD-0 / MDD-1

LOGMOD A0
LG.LOG6.A* LG.LOG1A*
(LQ.LOG6.A*) (LQ.LOG1.A*
-------------------- TLG.LG.LOG6.A*
(TLG.LQ.LOG6.A
*
CA.xxx
After meter saving LOGTAP A0 or MDD-0 / MDD-1

(LOGMOD A0
LG.LOG6.A* LG.LOG1.A*
(LQ.LOG6.A*) (LQ.LOG1.A*)
--------------------- TLG.LG.LOG6.A*
DUMMY.MET (TLG.LQ.LOG6.A
CA.xxx *
CA.xxx
TCA.CA. xx
Section B to G (medium A1)
Before1 st routine LOGTAP A1 or MDD-0 / MDD-1

saving LOGMOD A1
DUMMY. MET LG.LOG1.A*
CA.xxx (LQ.LOG1.A*)
OLD.CA.SU.xxx TLG.LG.LOG6.*
(TLG.LQLOG6.A
*
CA.xxx
TCA.CA.SU.xxx
OLD.CA.SU.xxx
After 1 st routine LOGTAP A1 or MDD-0 / MDD-1

saving LOGMOD A1
Tape contents I SY. GENLIST LQ.LOG2.A*
ALTTC/SW-II 38/46 5.4-APS/1.08.2002

After execution of I SY.SEMILIB (LQ.LOG2.A*)

CG.SA.Rxxap I SY.SIMP TLG.LG.LOG1.A*
I LG.LOG1.A* (TLG.LG.LOG1A*
I (LQ.LOG1.A*) )
-------------------- CA.xxx
DUMMY.MET TCA.CA.SU.xxx
CA.xxx OLD.CA.SU.xxx
OLD.CA.SU.xxx
After 2nd routine saving LOGTAP A1 or MDD-0 / MDD-1

LOGMOD A1
Tape contents I SY.GENLIST LG.LOG3.A*
After execution of I SY.SEMILIB (LQ.LOG3.A*)
CG. SA.RxxAP I SY.SIMP TLG.LG.LOG1.A*
I LG.LOG1.A* (TLG..LQ.LOG1.A
I (LQ.LOG1.A*) )
I LG.LOG2.A* TLG.GG.LOG2.A*
I (LQ.LOG2.A*) (TLG.LQ.LOG2.A
---------------------- *
DUMMY.MET CA.xxx
CA.xxx TCA.CA.SU.xxx
OLD.CA.SU.xxx OLD.CA.SU.xxx
After 3th routine LOGTAP A1 or MDD-0 / MDD-1

saving LOGMOD A1
Tape contents SY. GENLIST LG.LOG4.A*
I SY.SEMILIB (LQ.LOG4.A*)
after execution of SY.SIMP TLG.LG.LOG1.A*
I LG.LOG1.A* (TLG.LG.LOG1.A
CG.SA.RxxAP (LQ.LOG1.A*) *)
I LG.LOG2.A* TLG.LG.LOG2.A*
(LQ.LOG2.A*) (TLG.LQ.LOG2.A
I LG.LOG3.A* *)
(LQ.LOG3.A*) TLG.LG.LOG3.A*
I -------------------- (TLG.LQ.LOG3.A
DUMMY. MET *)
I CA.xxx CA.xxx
OLD.CA.SU.xxx TCA.CA.SU.xxx
I OLD.CA.SU.xxx
ALTTC/SW-II 39/46 5.4-APS/1.08.2002

After 4th routine saving LOGTAP A1 or MDD-0 / MDD-1

LOGMOD A1
Tape contents SY. GENLIST LG.LOG5.A*
I After execution of SY.SEMILIB (LQ.LOG5.A*)
I SY.SIMP TLG.LG.LOG1.A*
CG.SA.RxxAP LG.LOG1.A* (TLG.LQ.LOG1.A
I (LQ.LOGQ.A*) *)
LG.LOG2.A* TLG.LG.LOG2.A*
I (LQ.LOG2.A*) (TLG.LQ.LOG2.A
LG.LOG3.A* *)
I (LQ.LOG3.A*) TLG.LG.LOG3.A*
LG.LOG4.A* (TLG.LQ.LOG3.A
I (LQ.LOG4.A*) *)
--------------------- TLG.LG.LOG4.A*
I DUMMY.MET (TLG.LQ.LOG4.A
CA.xxx *)
I OLD.CA.SU.xxx CA.xxx
TCA.CA. SU.xxx
I OLD.CA.SU.xxx
After 5th routine saving LOGTAP A1 or MOD-0 / MDD-1

LOGMOD A1
Tape contents I SY. GENLIST LG.LOG6.A*
After execution I SY. SEMILIB (LQ.LOG6.A*)
CG.SA. RxxAP I SY.SIMP TLG.LG. LOG1.A*
I LG.LOG1.A* (TLG.LQ.LOG1.A*)
I (LQ.LOG1.A*) TLG.LG..LOG2.A*
I LG.LOG3.A* TLG.LQ.LOG3.A*)
ALTTC/SW-II 40/46 5.4-APS/1.08.2002

I LG.LOG4.A* (TLG.LQ.LOG4 A*)

I (LQ.LOG5.A*) CA.xxx
---------------------- TCA.CA.SU.xxx
DUMMY. MET OLD.CA.SU.xxx
CA.xxx
OLD.CA.SU.xxx
After quarterly saving LOGTAP A1 or MDD-0 / MDD-1

LOGMOD A1
Tape contents SY. GENLIST LG. LOG1.A*
I SY. SEMILIB (LQ. LOG1.A*)
After execution of SY.SIMP TLG.LG.LOG1.A*
CG.SA.QxxAP (LQ.LOG1.A*) TLG.LG.LOG2.A*
(LQ.LOG6.A*) CA.xxx
I --------------------- TCA.CA.SU.xxx
I CA.xxx
OLD.CA.SU.xxx
I
ALTTC/SW-II 41/46 5.4-APS/1.08.2002

Section H to N (medium A2)
Before tst routine LOGTAP A2 or

saving LOGMOD A2
DUMMY .MET LG.LOG1.A*
CA.xxx (LQ.LOG1.A*)
OLD.CA.SU.xxx 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
After 1 st routine LOGTAP A2 or MDD-0 / MDD-1

saving LOGMOD A2
Tape contents I SY. GENLIST LG.LOG2.A*

After execution of I SY. SEMILIB (LQ.LOG2.A*)
CG.SA.RxxAP I SY.SIMP TLG.LG.LOG1.A*
I LQ.LOG1.A* CA.xxx
-------------------- TCA.CA.SU.xxx
CA.xxx
OLD.CA.SU.xxx
ALTTC/SW-II 42/46 5.4-APS/1.08.2002

ALTTC/SW-II 43/46 5.4-APS/1.08.2002

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
1.FIX-
METERS DUMMY LG.1 LABEL
POINT BOT
cancel before each meter saving

c) content of the LOGTAP after the second routine saving
LG.1 2.FIX-
METERS DUMMY LABEL
+2 POINT BOT
a)
b)
c)
d)
sequence :
a) buffer LG-files on disk

b) label tape
c) save FIXPOINT, LG-files, DUMMY & METERS
d) 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

• 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

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
a) create golden gen (temp.) on disk
GOLDEN (old) b) Transfer golden gen (temp.) to tape
GOLDEN (temp.) (c) cancel golden gen (temp.) oon disk
ALTTC/SW-II 46/46 5.4-APS/1.08.2002

b) Creation a new GOLDEN GEN on disk

the new GOLDEN GEN on disk is set to blocked
TRANSSYFILE: GEN = <golden new >, VSN=SA1TAP,
REASON = REINST ;
ACT GEN
SA1TAP
BACKUP
GOLDEN
GOLDEN (old)
(new)
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
Step 1 non Step 2
BACKUP - format memory call test commands
- start up with processing STAT SSP;
GOLDEN (old) GOLDEN (new) side STAT LOG;
GOLDEN (new)
ALTTC/SW-II 47/46 5.4-APS/1.08.2002

Perform all following steps on the call processing side

• if test is successful, set new GOLDEN GEN to valid
MOD GEN:GEN = <golden>, VALIDITY = VALID;
• cancel old GOLDEN GEN
CAN GEN:GEN = <golden old> ;
• cancel Backup GEN
CAN GEN:GEN = <backup> ;
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

Quarterly Saving Procedure
A-tape
during last routine saving BACKUP

ACTUAL
5 was created on disk; during the
BACKUP 5 Fixpoint 5
last quarterly saving GOLDEN X
GOLDEN X LG.1.. LG.5
was created
LG.6
B-tape
- change the LOG function
from LG.6 to LG.1
ACTUAL
- create GOLDEN
BACKUP 5 GOLDEN X +
generation X + 1 from current
GOLDEN X 1
generation on disk and copy of B-
LG.6
tape;
LG.1
B-tape
- transmit files having no
generation to tape with GOLDEN
ACTUAL GOLDEN X + 1
X+1
BACKUP 5 SY.MSGXREF
- transmit LG.6 to tape of
GOLDEN X CG.
last routine saving and delete
from disk.
LG.1
A-tape
Fixpoint 5
LG.1.. LG.6
Fig. 8
ALTTC/SW-II 49/46 5.4-APS/1.08.2002
B-tape
ACTUAL - Copy GOLDEN X + 1 to

GOLDEN X + 1
BACKUP 5 disk GOLDEN X + 1 is blocked.
SY.MSGXREF
GOLDEN X CG.
GOLDEN X+1
LG.1
- test of CP-SW of GOLDEN

X + 1 in CP split
ACTUAL
BACKUP 5
- deletion of GOLDEN X
GOLDEN X
and BACKUPS if test was
GOLDEN X+1
successful. Set GOLDEN X + 1
LG.1
valid.
- test of LTG-SW in normal

operation mode
Fig. 9
ALTTC/SW-II 50/46 5.4-APS/1.08.2002

Routine saving procedure
a) Initial routine saving two weeks after APS change, initial

installation or quarterly saving
ACTUAL
GOLDEN generation if
GOLDEN
simultaneously BACKUP generation
until the first routine saving
LG.1
- change LOG function from

ACTUAL LG.1 to LG.2
- create fixpoint on tape Fixpoint 1
GOLDEN - transmit LG.1 to tape LG.1
- rename LG.1 on disk with
LG.2 TLG. prefix
ACTUAL
BACKUP 1 Fixpoint 1
- create BACKUP
GOLDEN LG.1
generation on disk
LG.2
Fig. 10
ALTTC/SW-II 51/46 5.4-APS/1.08.2002
b) Routine saving n + 1 (n + 1 < 5)
ACTUAL
BACKUP during nth routine saving, BACKUP Fixpoint n
GOLDEN n was created on disk and LG.1... LG.1.. LG.n
LG.n +1 LG.n were copied on disk
ACTUAL - transmit LG.1 ... LG.n

BACKUP n from tape to disk
GOLDEN
LG.1.. LG.n - initialize tape
LG.n + 1
- change LOG function from

LG.n + 1 to LG.n + 2
ACTUAL - create fixpoint on tape Fixpoint n + 1
BACKUP n - transmit LG.1 ... LG.n+1 to LG.1.. LG.n + 1
GOLDEN tape
LG.n + 2 - rename LG.1 ... LG.n+1
on disk with TLG. prefix
- delete the BACKUP generation n

and create the Backup Fixpoint
generation n + 1 on disk n+1
ACTUAL LG.1..
BACKUP n + 1 LG.n + 1
GOLDEN
LG.n + 2
Fig .11
ALTTC/SW-II 52/46 5.4-APS/1.08.2002

APS

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

APS

Uploaded by

Copyright:

Available Formats

EWSD Application Program System

According to operating company features:

According to scope and type of line assignment:

According to network environment:

ALTTC/SW-II 1/46 5.4-APS/1.08.2002

In the exchange, the APS is loaded to the CMY of the CP and

In EWSD software is categorized in the following way:

Non Resident Software

ALTTC/SW-II 2/46 5.4-APS/1.08.2002

2.0 APS Files and Data

2.2 Exchange Type-SW

2.3 Project specific-SW

2.4 Base APS (BAPS)

ALTTC/SW-II 3/46 5.4-APS/1.08.2002

It is composed of 2.1,2.2, and the 2.3. The Base-APS

SY.TASKLIB resident CP-software

The GP-software is contained in the files:

The CCNC-software is contained in the files:

SY.PSW.T097 processor software for CCNC-CPI

The SW for IOP-SCDP is contained in tthe file:

2.5 Exchange Specific Data (ESD)

ALTTC/SW-II 4/46 5.4-APS/1.08.2002

This data the so called DATA BASE is input in MML-

2.5.1 ODAGEN-Control Data (OCD)

2.5.2 Hardware-Configuration Data

2.5.3 Network Operation Data (NOD)

ALTTC/SW-II 5/46 5.4-APS/1.08.2002

2.6 Data Area (ODAGEN)

2.7 Customer Specific APS

2.8 Exchange Specific Customer-APS (ECAPS)

3.0 EWSD Files:

ALTTC/SW-II 6/46 5.4-APS/1.08.2002

System files are essential to system opeartion and are

SY.TASKLIB Resident CP software

ALTTC/SW-II 7/46 5.4-APS/1.08.2002

SY.SPOOL Buffer file for output jobs to

3.2 Safeguarding HISTORY files

SG.OPER Collects safeguarding messages

3.3 Archive files

HF.ARCHIVE Stores all messages relating to a

AM.ALARM Alarm messages requiring

ALTTC/SW-II 8/46 5.4-APS/1.08.2002

intervention by mtce. person

3.5 Call charge files

CA.SU.UCHA Subscriber charge meter

3.6 Individual recorded call data

3.7 Command Files

ALTTC/SW-II 9/46 5.4-APS/1.08.2002

3.8 Files for test results

3.9 Traffic Recording and PCM monitoring

4.0 Development and Installation of APS

Adaption of size and contents of an APS to the requirements

Example: RELEASE DOCUMENTATION

4.2 Identification of the magnetic tapes:

ALTTC/SW-II 11/46 5.4-APS/1.08.2002

An APS, and the appropriate exchange specific data are

The VSN(volume serial number) for the magnetic tapes

4.3 Installation (general information)

Example : one LTG

ALTTC/SW-II 12/46 5.4-APS/1.08.2002

• boot from hard disk and start installation recovery

The final status is an APS with incorporated data, i.e. an

4.4 Installation Recovery (Main Steps):