ATMAS Division

UNCLASSIFIED

ES010006101UM05
E184
Issue
B
Date:
27/03/2003

ROMANIA PROJECT

BACKUP
SOFTWARE USER MANUAL

CDRL No. :

TEMP-UK (ATC-Km 12.400) rev 6

ISSUED BY :
Alenia Marconi Systems S.p.A.
Via Tiburtina Km 12.400 - Roma
ITALY
The copyright in this document is the property of Alenia
Marconi Systems S.p.A. The document is supplied on the
express understanding that it is to be treated as confidential
and that it may not be copied, used or disclosed to others in
whole or in part for any purpose except as authorized in
writing by Alenia Marconi Systems S.p.A.
This document contains a total of 42 pages

UNCLASSIFIED

Page 1

ATMAS Division

UNCLASSIFIED

ES010006101UM05
E184
Issue
B
Date:
27/03/2003

DOCUMENT SECURITY CLASSIFICATION:

This document is intended for the use of the recipient only, and for communication to such persons as may be
required to be acquainted with its contents in the course of their duties.
The recipient, and any other person to whom the recipient has communicated the contents of this document,
shall treat this document in accordance with the requirements of Alenia document Security Instructions, 15
February 1992.
Any person others the authorised holder upon obtaining possession of this document, by finding or otherwise,
should forward it by registered post, together with his name and address, in a sealed envelope to:
Ufficio Sicurezza
Alenia Marconi systems S.p.A.
Via Tiburtina 12.400
00131 Roma
ITALY

Any questions arising from this document should be addressed to:

Simonetta Di Domenico
Alenia Marconi Systems S.p.A.
Air Traffic Management & Airport Systems Division
Via Tiburtina, Km 12.400 - 00131 Roma
ITALY

Telephone
Fax

+39-06 4150-2612
+39-06 4131133 / 4131436 / 4131091

UNCLASSIFIED

Page 2

ATMAS Division

UNCLASSIFIED

ES010006101UM05
E184
Issue
B
Date:
27/03/2003

Issue Authority
Prepared by :

......................................................
(Simonetta Di Domenico)

Date:

......................................................
(Antonio Mattogno)

Date:

Checked by:
(QA Responsible)

......................................................
(Sergio Pignotti)

Date:

Authorised by:
(Project Manager)

......................................................
(Sergio Arceri)

Date:

Approved by:
(Project Leader)

UNCLASSIFIED

Page 3

ATMAS Division

UNCLASSIFIED

ES010006101UM05
E184
Issue
B
Date:
27/03/2003

REVISIONS RECORD SHEET

This sheet is a record of revisions to this document.

Issue/AL

Date

Revised Pages

22/11/01

MRT_RPB_TCA UM

27/03/03

First Issue

UNCLASSIFIED

Document Change Note

(DCN)

Page 4

ATMAS Division

UNCLASSIFIED

ES010006101UM05
E184
Issue
B
Date:
27/03/2003

LIST OF ABBREVIATIONS
ABBR.

DESCRIPTION

ACC

Area Control Centre

ACD

Advanced Common Database

ACK

Acknowledge

ACL

Arrival CLearance

ACR

Arrival Clearance with Re-routing

AFTN

Aeronautical Fixed Traffic Network

AIS

Aeronautical Information Service

ALV

Authorization LeVel

APP

APProach control

ARR

ARRival

ASF

Assistant function

ASQ

Arrival SeQuencing

ASS

Assistant Controller

ATA

Actual Time of Arrival

ATC

Air Traffic Control

ATD

Actual Time of Departure

ATI

Actual Time of Inbound

ATM

Air Traffic Management

ATO

Actual Time Over

ATS

Air Traffic Service

ATW

Auxiliary Working Position

BRW

BroWse

CNL

CaNceL

CoMap

Coordination Maps display

CSCI

Computer Software Configuration Item

CWP

Controller Working Position

DAIW

Danger Area Infringement Warning

UNCLASSIFIED

Page 5

ATMAS Division

UNCLASSIFIED

ES010006101UM05
E184
Issue
B
Date:
27/03/2003

DARD

Direct Access Radar Data

DCL

Departure CLearance

DCR

Departure Clearance with Re-routing

DEP

DEParture list

DIS

DISabled

DLA

DeLAy departure

DMD

Dangerous area Map Display

EMG

EmerGency

EST

ESTimate

ETA

Estimated Time of Arrival / Estimated Exit Time from the feeding fix (in
ACL order)

ETD

Estimated Time of Departure

ETI

Estimated Time of Inbound

ETL

Estimated Time of Landing

ETO

Estimated Time Over

EXE

EXEcutive function

FCK

Formality ChecK

FCN

Flight data CaNcellation

FDM

Flight Data Management

FDP

Flight Data Processing

FIR

Flight Information Region

FL

Flight Level

FLD

FLDA Displaying

FLDA

FLight DAta page list

FLDI

FLight DIrectory list

FPLM

Flight Plan Message list

FTR

File TeRmination

GlobMap

Global Mps display

I/O

Input/Output

ICAO

International Civil Aviation Organization

UNCLASSIFIED

Page 6

ATMAS Division

UNCLASSIFIED

INBFIX

INBound (entry) FIX

INI

INItialize

LND

LANding report

LRW

Landing RunWay

LSV

LaSt leVel

LVA

planned/cleared LeVel Assignment

MET

METeorological

MIL

MILitary

MNG

MaNaGement

MPG

Map Generation System

MRT

Multi Radar Tracking

MSAW

Minimum Safe Altitude Warning

NAVAID

NAVigational AID

NM

Nautical Miles

NOTAM

NOtice to AirMan

NVS

NaVigator aid

OBT

Off Block Time

ODS

Operator input and Display System

ONL

ON Line

OP

Operational

OPRSUP

OpeRational SUPervisor

PCN

Planning Cancellation

PEN

PENding tracks

PKB

ParKing Bay allocation

PLB

PlayBack

PLC

Planning Controller

PLN

PlaNning function

QNH

Barometric pressure / enter QNH

RCL

en-Route CLearance

RCR

en-Route Clearance with Re-routing

UNCLASSIFIED

ES010006101UM05
E184
Issue
B
Date:
27/03/2003

Page 7

ATMAS Division

UNCLASSIFIED

ES010006101UM05
E184
Issue
B
Date:
27/03/2003

RDP

Radar Data Processing

REC

RECording

REG

REGistration number

REP

Position REport

REV

estimate REVision

RHP

Radar Head Processor

RNG

RaNGe scale

RWY

RunWaY

SBY

Stand-BY

SID

Standard Instrumental Departure

SIG

fir SIGmet

SMD

System Messages Dispatching (CSCI)

SRL

SSR code ReLease

SSR

Secondary Surveillance Radar / SSR code assignment

STAR

STandard Approaching Route

SUM

Software User Manual

SUP

SuPerVisor

SW

SoftWare

TAS

True Air Speed / change True Air Speed

TBD

To Be Defined

TCA

Traffic Conflict Alert

TKF

TaKe-oFf report

TMA

TerMinal Area

TMS

Terminal Area management

TRW

departure RunWay

TXT

free TeXT

TWR

control ToWeR

VDU

Video Display Unit

VFR

Visual Flight Rule

WTC

WaTCher

UNCLASSIFIED

Page 8

ATMAS Division

UNCLASSIFIED

ES010006101UM05
E184
Issue
B
Date:
27/03/2003

TABLE OF CONTENTS

1.

SCOPE................................................................................................................................................... 11

IDENTIFICATION........................................................................................................................................ 11
1.1 SYSTEM OVERVIEW.........................................................................................................................11
1.2 DOCUMENT OVERVIEW...................................................................................................................12
2.

REFERENCED DOCUMENTS.......................................................................................................... 13

3.

CONVENTIONS................................................................................................................................... 14

4.

THE INTERFACES DESCRIPTION................................................................................................. 15

4.1
4.2

INTERFACES TOWARDS SYSTEM COMPONENTS ...............................................................................15

OPERATOR INTERFACES...................................................................................................................16

5.

FUNCTIONALITY............................................................................................................................... 17

5.1 CONFIGURATION AND INITIALIZATION COMMANDS .........................................................................19

5.1.1 ORDERS......................................................................................................................................... 20
5.1.1.1 Orders Description...........................................................................................................................21
5.1.1.2 Orders sequence...............................................................................................................................26
5.1.1.3 Example of Configuration orders.................................................................................................27
5.2 START/STOP BACKUP COMMANDS ...................................................................................................28
5.3 INFORMATION PRESENTATION COMMANDS .....................................................................................29
5.3.1 ORDERS......................................................................................................................................... 29
5.3.1.1 Orders Description...........................................................................................................................30
5.3.1.2 Orders sequence...............................................................................................................................32
5.3.1.3 Examples of Information presentation orders...............................................................................32
6.

OPERATIVE EXAMPLES.................................................................................................................. 33

7.

ORDERS LIST...................................................................................................................................... 33

UNCLASSIFIED

Page 9

ATMAS Division

UNCLASSIFIED

ES010006101UM05
E184
Issue
B
Date:
27/03/2003

8.

ERROR AND ALARM MESSAGES................................................................................................... 34

8.1
8.2
8.3
8.4

GENERALITY....................................................................................................................................34
MESSAGES .......................................................................................................................................34
ERRORS........................................................................................................................................... 35
ALARMS ...........................................................................................................................................38

9.

DEGRADED EXECUTION................................................................................................................. 39

10.

OPERATIVE STARTING.................................................................................................................. 42

UNCLASSIFIED

Page 10

ATMAS Division

1.

UNCLASSIFIED

ES010006101UM05
E184
Issue
B
Date:
27/03/2003

SCOPE

IDENTIFICATION
This document is related to the package CSCI Back Up

Identification number : 84
Title : Software User Manual for the advanced CSCI Back Up
Abbreviation : BCK
1.1

SYSTEM OVERVIEW

The BCK (Backup) CSCI is needed for saving on DAT the data previously recorded on disk by the Recording
CSCI. These data are:
orders, messages, radar data, etc.. coming from LAN
radar data coming from Radar
maps and data banks.

These data are organized on Hard Disk in Save Sets. When a save set is finished, recording goes
onto another free, while that as soon as closed is saved on DAT from the Backup CSCI.
After writing on DAT the save set is again available. The REC CSCI could continue a session of
recording.
Besides a save set could be used from the Playback for reproducing the data recorded in it.
This save set could be also read from DAT, for this the BCK CSCI is able to restore on Hard Disk a
Save Set from DAT (through an operator command).

UNCLASSIFIED

Page 11

ATMAS Division

1.2

UNCLASSIFIED

ES010006101UM05
E184
Issue
B
Date:
27/03/2003

DOCUMENT OVERVIEW

This document describes the procedures to be followed for the execution of the BCK CSCI.
The paragraph 1 supplies a brief description of the SATCAS system and of the content of this document.
The paragraph 2 supplies a list of referenced documents.
The paragraph 3 supplies a glossary.
The paragraph 4 contains the description of BCK interfaces with external world.

The paragraph 5 provides information about:

BaCKup CSCI brief functional description.
Operator commands description.

The paragraph 8 provides the list of messages and errors notifications issued from BCK CSCI.

UNCLASSIFIED

Page 12

ATMAS Division

2.

UNCLASSIFIED

ES010006101UM05
E184
Issue
B
Date:
27/03/2003

REFERENCED DOCUMENTS
Software Requirement Specification E000BCK0-D01SRS.
DoD_2167A_DI-MCCR-80019A.

UNCLASSIFIED

Page 13

ATMAS Division

3.

UNCLASSIFIED

ES010006101UM05
E184
Issue
B
Date:
27/03/2003

CONVENTIONS

CPU-M : Central Processor Unit - Master. It is the DEC Alpha Master Node.
CPU-S : Central Processor Unit - Slave. It is the DEC Alpha Slave Node.
DAT : Digital Audio Tape. It is the digital data recording unit.
FL : File Unit. It is the digital data recording unit on disk.
LAN : Local Area Network. Communication Line among the nodes.
SP : Serial Printer.
XPL : Play-Back function
XRE : Recording function

UNCLASSIFIED

Page 14

ATMAS Division

UNCLASSIFIED

4.

THE INTERFACES DESCRIPTION

4.1

INTERFACES TOWARDS SYSTEM COMPONENTS

ES010006101UM05
E184
Issue
B
Date:
27/03/2003

The interfaces between BaCKup and the external world are:

Identifier : NSV_Message
Description : They are all the messages exchanged with NSV CSCI and the information about the operations on the
peripherals.
Information type : To Degrade-To Restore the peripherals performance

Characteristic of exchange : Via Path

Referenced Documents : SRS & IRS BCK.

Identifier : NSV_Change_State
Description : It is the message that contains the BCK activation according to node role.
Information type : BCK activation (Master/Stand_by); To Degrade-To Restore the peripherals performance.
Characteristic of exchange : Via Path
Referenced Documents : SRS & IRS BCK.

Identifier : SMD_Command_To_BCK, BCK_Message_To_SMD

Description : They are operator orders and other kind of messages exchanged with SMD function
Information type : These are that information that correspond to the orders sent from the operator and the diagnostic
messages

Characteristic of exchange : Via Path

Referenced Documents : SRS & IRS BCK.

UNCLASSIFIED

Page 15

ATMAS Division

4.2

UNCLASSIFIED

ES010006101UM05
E184
Issue
B
Date:
27/03/2003

OPERATOR INTERFACES

The interface with operator is represented by possible operator commands.

UNCLASSIFIED

Page 16

ATMAS Division

5.

UNCLASSIFIED

ES010006101UM05
E184
Issue
B
Date:
27/03/2003

FUNCTIONALITY

The main purpose of BCK CSCI is to save on DAT the data and events occurred in the system and recorded
on disk by recording; then to restore a save set on disk to allow the playback.
The backup functionalities are controlled by:

1. The operator orders messages coming from SMD. These are the messages containing the
backup operator orders received from the enabled terminals or consoles and dispatched by
SMD towards BaCKup.
By means of these messages an operator can drive the BaCKup CSCI:
about the operations to do on the DAT devices and disk files,
to start or to stop the storing of save sets on the recording supports.
2. NSV messages. These messages contain information about:

The role changing of the node (from Master to Stand-by and viceversa).
The status changing (ON or OFF) of the DAT peripherals.

BaCKup CSCI can handle four DAT devices and a mirrored disk.
When it is resident on a node of a couple of DEC Alpha computers, it is able to drive these devices
only when it is on the master node of the couple.
The BaCKup CSCI on the stand-by node is always updated about the changing of the content of the
main tables and variables by the BaCKup CSCI on the master node by means of an alignment file on
disk.
In this way the BaCKup activities can continue after a master -> stand-by switching.
The four DAT devices handled by BaCKup CSCI are identified through the physical number of the
unit. It is a number whose value is 1, 2, 3 or 4 and it is always associated to a specific DAT unit.
The backup activities start on the first unit assigned in writing and mounted; when the tape ends, BaCKup
CSCI starts storing the data on next tape (if mounted).

In the same way BaCKup CSCI handles five files on disk to read the save sets.
These files are defined by their physical numbers.
The value of the physical number can be: 1, 2, 3, 4. It is always associated to a specific file.
The Recording activities start on the main file unit; when this file is near to the end (eof), RECording
CSCI changes file and starts storing the data on the reserve file, if it is assigned, and sends a signal to
BaCKup to store a main file on DAT device.
When the backup has completed, RECording CSCI can use again main file, it starts storing the data
from the beginning of file and overwrites the data.
The SMD CSCI receives system orders from the enabled terminals and consoles, searches the
destination CSCI, and then dispatches the orders towards it.
A CSCI that receives and executes a system order has to send towards SMD an acknowledge
message. SMD dispatches this acknowledge towards the enabled terminals and consoles.

UNCLASSIFIED

Page 17

ATMAS Division

UNCLASSIFIED

ES010006101UM05
E184
Issue
B
Date:
27/03/2003

In this way an operator can give (and receive answers) commands towards BaCKup CSCI from the
enabled terminals and consoles.
The commands towards BCK have the following format:
BCK CCC A...A A...A A...A
where :
BCK : BCK threeliteral for SMD to understand that the command is for BaCKup.
CCC : It is the generic command
A...A : It is the parameter(s) of the command and it is different from command to command.
The BaCKup CSCI answers to an order with a message containing the string of the order plus the
result of the execution of the order itself (if the command can be executed immediately) or the string
ORDER ACCEPTED if the command requests more time for execution.
If the syntax of the order is not correct the answer is the string of the order plus the string
INVALID ORDER RECEIVED.
The commands towards BaCKup may be divided into three categories:
Configuration and initialization: to configure and to initialize the DAT devices;
Start/stop backup: to start or stop the storing of the save sets on the DAT;
Information presentation: to show information about the status of the peripherals.

UNCLASSIFIED

Page 18

ATMAS Division

5.1

UNCLASSIFIED

ES010006101UM05
E184
Issue
B
Date:
27/03/2003

CONFIGURATION AND INITIALIZATION COMMANDS

Before starting the backup session the operator has to give to BaCKup CSCI the information about
which is the tape unit used for writing or reading operations (ASSign command).
Then he mounts the DAT (MOU command).

If the operator wants that the recording of data continues on the other DAT at the end of the first
tape, he has to give the information about which is the next tape unit (ASS command) and then has
to mount it (MOU command).
Naturally, there are also the commands to dismount and to deassign a DAT tape.
In the same way for Playback: if the operator wants to restore the recorded data from a DAT, he has
to give the information about which is the DAT used for reading operation (ASS command ) and
then has to mount it (MOU command).

UNCLASSIFIED

Page 19

ATMAS Division

5.1.1

UNCLASSIFIED

ES010006101UM05
E184
Issue
B
Date:
27/03/2003

ORDERS

The commands that allow the before said operations are:

BCK ASS DTn {WR RD} Assign physical-logical DAT Unit

BCK DEA DTn Deassign DAT Unit
BCK MOU DTn [INI] Mount DAT Unit
BCK DMO DTn Dismount DAT Unit
BCK RST DTn Fxx FLy Restore file.

UNCLASSIFIED

Page 20

ATMAS Division

UNCLASSIFIED

ES010006101UM05
E184
Issue
B
Date:
27/03/2003

5.1.1.1 Orders Description

5.1.1.1.1

BCK ASS DTn {WR RD}

Description: This command assigns the logical name DTn for writing or reading operations to the DAT
device which physical number is n. By means of this command the DAT device which physical number is
n is dedicated to BaCKup CSCI (no other CSCI can use it).

Where:
n = 1, 2, 3, 4 (DAT device physical number);

Controls: The command is not accepted:

1. If the syntax is wrong (the string INVALID DATA RECEIVED is displayed)
2. When a previous ASS command is in execution on that DAT (the string ORDER ALREADY
RECEIVED is displayed).
When accepted, the command is not executed:
1. If the logical name in the command is already assigned to BCK (the string ERROR IN
COMMAND is displayed).
2. If the unit does not exist or it is in fault (the string NOT EXECUTABLE COMMAND is
displayed).
Result: If the order is executed the string COMMAND EXECUTED is displayed.

UNCLASSIFIED

Page 21

ATMAS Division

5.1.1.1.2

UNCLASSIFIED

ES010006101UM05
E184
Issue
B
Date:
27/03/2003

BCK DEA DTn

Description: This command deassigns (releases) the DAT device with logical name DTn.

Where:
n = 1, 2, 3, 4 (DAT device physical number);

Controls: The command is not accepted:

1. If the syntax is wrong (the string INVALID DATA RECEIVED is displayed)
2. When a previous DEA command is in execution on that DAT (the string ORDER
ALREADY RECEIVED is displayed).
When accepted, the command is not executed:
1. If the logical name in the command is not assigned (by means ASS command) (the string
COMMAND NOT IN SEQUENCE is displayed).
2. If the DAT tape is mounted (the string COMMAND NOT IN SEQUENCE is displayed ).

Result: If the order is executed the string COMMAND EXECUTED is displayed.

UNCLASSIFIED

Page 22

ATMAS Division

5.1.1.1.3

UNCLASSIFIED

ES010006101UM05
E184
Issue
B
Date:
27/03/2003

BCK MOU DTn [INI]

Description: This command allows the mounting of the DAT tape.

Controls: The command is not accepted:

1. If the syntax is wrong (the string INVALID DATA RECEIVED is displayed ).
2. When a previous MOU command is in execution on that DAT (the string ORDER
ALREADY RECEIVED is displayed).
3. When a MON command is in execution on that DAT (the string ORDER FOR DAT IN
MONITORING is displayed).
Results: If no error occurs the string MOU DTn: ORDER ACCEPTED is shown but the command is not
executed:
If the tape is not assigned (with the ASS command). The string COMMAND NOT IN
SEQUENCE is displayed.
If the tape is already mounted (the string ERROR IN COMMAND is shown ).
If the option INI is specified but the DAT is assigned in read (the string ERROR IN
COMMAND is shown ).

If the unit is not operative. The string NOT EXECUTABLE COMMAND is

displayed.
If any I/O operation on DAT fails. The string DEVICE ERROR is shown.
Result : At the end of the execution, in case of positive result, the string
BCK MOU DTn : ORDER EXECUTED will appear.
The MOU command executes the following operations:
If the DAT unit is assigned in reading or in writing without INI option

Positioning on BOT
Reading the file containing the DAT information data.

If the DAT unit is assigned in writing and INI option is required

Positioning of the DAT to the beginning
Writing of the initialization status at the beginning of the DAT.
After the correct positioning of the DAT, digital data can be restored on Disk or
the backup of digital data starts automatically on this tape.

UNCLASSIFIED

Page 23

ATMAS Division

5.1.1.1.4

UNCLASSIFIED

ES010006101UM05
E184
Issue
B
Date:
27/03/2003

BCK DMO DTn

Description: This command allows the dismounting of the DAT tape.

Controls: The command is not accepted:

If the syntax is wrong (the string INVALID ORDER RECEIVED is shown).
When a previous DMO command is in execution on that DAT (the string ORDER ALREADY
RECEIVED is shown).
When a MON command is in execution on that DAT (the string ORDER FOR DAT IN
MONITORING is shown ).

Results: If no error occurs the string DMO DTn: ORDER ACCEPTED is shown and its execution begins. The
command is not executed :
If the tape is not assigned (by means ASS command). The string COMMAND NOT IN SEQUENCE
is displayed.
If the tape is not mounted. The string COMMAND NOT IN SEQUENCE is displayed.
If the DAT device is not operative. The string NOT EXECUTABLE COMMAND is displayed.
If any I/O operation on that DAT fails. The string DEVICE ERROR is shown.

Results: If the command is successfully executed the string COMMAND EXECUTED is shown.
At this point the operator can remove the DAT tape from the DAT device.

UNCLASSIFIED

Page 24

ATMAS Division

5.1.1.1.5

UNCLASSIFIED

ES010006101UM05
E184
Issue
B
Date:
27/03/2003

BCK RST DTn Fxx FLy

Description: To restore files from DAT unit to disk.

The command restores the file xx from DAT n to file y on disk

Where:
n = 1, 2, 3, 4 (up to the DAT number).
xx = 00, 01, 02, ..., 99 (number of file recorded on DAT)
y = 1,2,3,4,5 (number of file on disk).
Control : The command is not accepted:
If the syntax is wrong. The string INVALID ORDER RECEIVED is shown.
When a previous RST command is in execution on that DAT (the string ORDER ALREADY
RECEIVED is shown ).
When a MON command is in execution on that DAT ( the string ORDER FOR DAT IN
MONITORING is shown ).
Results : If no error occurs the string RST DTn Fxx FLy: ORDER ACCEPTED is shown and its execution begins.
The command is not executed:
If the tape is not assigned (by means ASS command). The string COMMAND NOT IN SEQUENCE
is displayed.
If the tape is not mounted. The string COMMAND NOT IN SEQUENCE is displayed.
If the file on disk is busy (that is it is used by another CSCI). The string ERROR IN COMMAND is
shown.
If the xx file is not present on DAT (that is the number xx is greater than the number of files saved on
that DAT). The string ERROR IN COMMAND is shown.
If the DAT device is not operative. The string NOT EXECUTABLE COMMAND is displayed.
If any I/O error occurs. The string DEVICE ERROR is shown.

Results: If the command is successfully executed the string COMMAND EXECUTED is shown.

UNCLASSIFIED

Page 25

ATMAS Division

UNCLASSIFIED

ES010006101UM05
E184
Issue
B
Date:
27/03/2003

5.1.1.2 Orders sequence

To execute some commands (ASS, DEA, MOU, DMO, RST), the operator has to respect a
determinate sequence, otherwise the string COMMAND NOT IN SEQUENCE (or other
diagnostic message, see orders description) is displayed to indicate a not correct sequence of
commands.
Other commands, on the contrary, could be requested in any case.
The command BCK MON DTn may be requested only if the tape is assigned or mounted.
The command BCK MOU DTn may be requested only if the tape is assigned.
The command BCK DMO DTn may be requested only if the tape is mounted.
The command BCK RST DTn may be requested only if the tape is mounted.

UNCLASSIFIED

Page 26

ATMAS Division

UNCLASSIFIED

ES010006101UM05
E184
Issue
B
Date:
27/03/2003

5.1.1.3 Example of Configuration orders

The most significant sequence of orders to execute to obtain a correct Configuration is the
following:
BCK ASS DTn WR Logical - Physical Tape Unit assigned
BCK MOU DTn Dtn mounted
If you want to deassign the DAT DTn you have to execute the following order: BCK DEA DTn
(Deassign Tape Unit)
If you want to dismount the DAT Dtn you have to execute the following order: BCK DMO DTn
(Dismount Tape Unit)
If you want to know the status of the tape units you have to execute the following order: BCK SHO
DAT (Display DAT Status)
If you want to know the status of the DAT units you have to execute the following order: BCK
MON DTn (Display DAT contents).

UNCLASSIFIED

Page 27

ATMAS Division

5.2

UNCLASSIFIED

ES010006101UM05
E184
Issue
B
Date:
27/03/2003

START/STOP BACKUP COMMANDS

To start backup functionality BCK CSCI does not need a proper command.
MOU command for DAT assigned with WR (write) option implies BCK is ready to start backup
operations. In this status BCK stores save sets on DAT every time a save set is released by REC
CSCI.
Backup may be interrupted by a DMO command.

UNCLASSIFIED

Page 28

ATMAS Division

UNCLASSIFIED

5.3

INFORMATION PRESENTATION COMMANDS

5.3.1

ORDERS

ES010006101UM05
E184
Issue
B
Date:
27/03/2003

This set of commands allows showing information about the status of the peripherals handled by the
BaCKup CSCI and the setting of the parameters.
These commands are:
BCK MON DTn Presentation of the information present on the tape (Version of BCK, number of
save sets stored on DAT, date and time for each of them).
BCK SHO DAT Displaying DAT status.

UNCLASSIFIED

Page 29

ATMAS Division

UNCLASSIFIED

ES010006101UM05
E184
Issue
B
Date:
27/03/2003

5.3.1.1 Orders Description

5.3.1.1.1

BCK MON DTn

Description: This command shows the information present on the DAT

(identification number of the save set, date and time of the first save set, date and time of the last
save set).
Controls:
If the command has not been written correctly INVALID ORDER RECEIVED is displayed.
If the DAT is not assigned, the string DAT NOT ASSIGNED is displayed.
If a command is in execution on that DAT, the string DAT BUSY - XXXX IN PROGRESS (where
XXXX is the command in execution) is displayed.
If none of the above conditions occurs the string ORDER ACCEPTED is displayed.
Results: when accepted, at the end of execution, the following table is displayed:

BCK MON Dtn :

VERSION : XXXXXX
N Save Set : nn
F000.REC : mm/dd/yyyy hh:mm:ss mm/dd/yyyy hh:mm:ss
........
........
F0nn.REC : mm/dd/yyyy hh:mm:ss mm/dd/yyyy hh:mm:ss
where:

XXXXXX
nn
dd/mm/yyyy
hh:mm:ss

Version of BCK CSCI

Number of save sets stored on DAT ( 00 ... 99 )
Recording initial/end date on save set
Recording initial/end time on save set

UNCLASSIFIED

Page 30

ATMAS Division

5.3.1.1.2

UNCLASSIFIED

ES010006101UM05
E184
Issue
B
Date:
27/03/2003

BCK SHO DAT

Description: This command shows the DAT Units status.

Controls: It checks the syntax of the command:

If the command has not been written correctly INVALID COMMAND RECEIVED is displayed.

Result: If the order is executed, it is displayed as follows:

BCK SHO DAT :

DTX STATE ASS MOU USE n/SAVE SET
DT1 xxx
yyy zzz hhh mm
.......................
DTn xxx
yyy zzz hhh mm

where:
n

number of configured DAT

xxx = ON
tape operative
= OFF
tape not operative
= COMM tape in restore
yyy = WR
= RD
= ----

tape assigned in writing

tape assigned in reading
tape not assigned

zzz = BCK
= RST
= ---

tape mounted in backup

tape mounted in restore
tape not mounted

hhh = YES tape in use (main tape mounted in backup or tape mounted in restore
with a restore in progress)
= NOT tape not in use (reserve tape mounted in backup or tape mounted in
restore without restore in progress )
= --tape not used (not mounted)
mm =

0,1,2,...,99 (number of save sets stored on DAT).

UNCLASSIFIED

Page 31

ATMAS Division

UNCLASSIFIED

ES010006101UM05
E184
Issue
B
Date:
27/03/2003

5.3.1.2 Orders sequence

The SHO command may be executed in any moment, without order of sequence.
The MON command needs an assigned DAT (by a previous ASS command).

5.3.1.3 Examples of Information presentation orders

BCK SHO DAT

UNCLASSIFIED

Page 32

ATMAS Division

6.

UNCLASSIFIED

ES010006101UM05
E184
Issue
B
Date:
27/03/2003

OPERATIVE EXAMPLES

See examples relative to the different functionalities.

7.

ORDERS LIST

1. BCK ASS DTn {WR RD}

: Logical DAT Unit assignment

2. BCK DEA DTn

: DAT Unit deassignment

3. BCK MOU DTn [INI]

: DAT mount

4. BCK DMO DTn

: DAT dismount

5. BCK RST DTn Fxx FLy

: Restore file n. xx from DAT in file n. y on disk

6. BCK MON DTn

: Display of the information stored on the tape n (version, number of Save
Set , initial/end date and initial/end time for each save set)
7. BCK SHO DAT

: Display of status of all configurated DATs

UNCLASSIFIED

Page 33

ATMAS Division

UNCLASSIFIED

8.

ERROR AND ALARM MESSAGES

8.1

GENERALITY

ES010006101UM05
E184
Issue
B
Date:
27/03/2003

The messages introduction, errors, alarms, are shown by the messages on I/O console.

8.2

MESSAGES

The following messages are displayed on I/O console after a command is typed:
COMMAND ALREADY RECEIVED: if an identical command previously typed for the same DAT is
still executing.

INVALID COMMAND RECEIVED: if any syntax error is detected in the command or some
values are out of range. The command must be rewritten correctly.
ORDER FOR DAT IN MONITORING: if commands are direct on a DAT where a
monitoring is in progress.
DAT NOT ASSIGNED: if a MON command is specified for a DAT not assigned. (The MON
command may be executed for DAT assigned or mounted).
DAT BUSY - XXXX IN PROGRESS: if a MON command is specified for a DAT where
another command (the XXXX command shown) is still executing.
FAILED MOUNT : if a MON command is specified for an assigned but not mounted DAT
and the mounting operation fails.
The following messages are displayed after a failed command execution:
COMMAND NOT IN SEQUENCE: the command does not respect the sequence of the
commands (see paragraphs Commands Sequence).
DEVICE ERROR: the I/O operations on DAT finished with error.
ERROR IN COMMAND: there is a logical error in the command (for example: restore a file
from a DAT assigned in read, dismount a DAT not mounted, mount a DAT already mounted, ...).
NOT EXECUTABLE ERROR: some errors occur in execution. This message is always
followed by a diagnostic that explains the occurred error.

UNCLASSIFIED

Page 34

ATMAS Division

8.3

UNCLASSIFIED

ES010006101UM05
E184
Issue
B
Date:
27/03/2003

ERRORS

The error messages sent out by BCK have the following format:
BCK CODE:RmPRSWppRESxxxxH ASCII STRING that contains the error explanation

Where:

m = module index where the error is occurred;

pp = procedure index internal to the module in which the error is occurred, represented
decimal format;

xxxx = hexadecimal code of the error represented in hexadecimal format;

Module codes are:

1 : B1 process
2 : B2 process
3 : GDAT process
4:

The procedure codes are defined in the high level documents.

When in a procedure an anomalous situation occurs, not directly dependent from a UNIX O.S. error, the
internal error is set. The possible explanation string of internal error codes for the Backup CSCI, are:
The following internal errors are specified according to the module in which the error occurs.
B1 (1) PROCESS and B2 (2) PROCESS:

"BUFFER BOUNCED" received a buffer bounced;

"COMMUTATION ERROR" fatal error is occurred during a switching ;
"INVALID POINTER" a pointer to a buffer is nil;
"POOL EMPTY" internal buffer pool empty;
"REPLY WITH NOK RESULTCODE" reply buffer with operation result code <> 0 ;
"UNKNOWN PU" received a message from NSV with a unknown device;
"UNKNOWN REPLY" reply buffer with unknown sender;
"UNKNOWN SEND" received a buffer with unknown sender;

UNCLASSIFIED

Page 35

ATMAS Division

UNCLASSIFIED

ES010006101UM05
E184
Issue
B
Date:
27/03/2003

GDAT (3) PROCESS:

"BACKUP ERROR" fatal error during backup operation;

"BACKUP IS NOT OPERATIVE" invalid order received when Backup is not ready.
"CONFIGURATION ERROR" a parameter read from configuration file is wrong;
"CORRUPTED DAT" Data on DAT are corrupted;
"DAT ERROR" fatal error on DAT;
"DAT IN USE" invalid Dismount order of DAT in use;
"DAT NOT AVAILABLE" received order about a DAT busy;
"DAT NOT CONFIGURATED" received an order about a DAT not configurated;
"DAT TABLE FULL" the number of DAT is greater than Configuration file of Backup;
"DATA CARTRIDGE FULL" DAT Full;
"DISK ERROR" fatal error on disk ;
"INVALID DATA PRESENT IN DAT" when the DAT is not written by BaCKup;
"INVALID SW VERSION PRESENT IN DAT" the version of Backup is not compatible;
"SYSTEM ERROR" fatal system error.

UNCLASSIFIED

Page 36

ATMAS Division

UNCLASSIFIED

ES010006101UM05
E184
Issue
B
Date:
27/03/2003

STOP of the Backup

The stopping event for BCK are:

impossibility to open with other CSCI or CSC;
when system error occurs.

If one of these case BCK CSCI in a undetermined status is stopped. To restart BCK CSCI is
necessary to restart the node.
Diagnostic messages are provided.

UNCLASSIFIED

Page 37

ATMAS Division

8.4

UNCLASSIFIED

ES010006101UM05
E184
Issue
B
Date:
27/03/2003

ALARMS

Not applicable

UNCLASSIFIED

Page 38

ATMAS Division

9.

UNCLASSIFIED

ES010006101UM05
E184
Issue
B
Date:
27/03/2003

DEGRADED EXECUTION

The BCK CSCI must handle the following failure conditions:

Master/Stand-by Switching;
Peripherals failure (DAT Unit, Disk Unit).

UNCLASSIFIED

Page 39

ATMAS Division

UNCLASSIFIED

ES010006101UM05
E184
Issue
B
Date:
27/03/2003

Master / Stand-By Switching

It is possible to divide the Master/Stand-by switching problem, as follows:

Mechanism of the switching decision.

Execution of the switching.
Stand-by operativity.

Mechanism of the switching decision.

The switching has only a type:

forced switching;

The switching decision is executed from N.S. that communicates to the applicative functions when
the disconnection or the new connection operations towards the peripherals are already executed
(hard deassign, news activation and assign towards the peripherals of the neo_master).
For this reason:

the ex_master function can send to SMD function, the error messages.
the neo_master function, on the contrary, can start according to its own specific modalities.

The starting of the Backup CSCI on the neo_master computer is executed automatically, when the DAT Tape
peripherals reach the status visible from ex_master computer.
If this does not happen the BCK CSCI is not operative.

Stand-by Operativity:
To allow the switching it is important to maintain updated the tables between the Master and Standby functions.
A communication mechanism exists between the master and stand-by node.
Particularly the Stand-by will receive, during the life of the system, some information from Master, in
this way the stand_by function will be constantly aligned with the data elaborated.
The communication between Master and Stand-by is through the disk the master and standby are
aligned by means of an alignment file on disk.

UNCLASSIFIED

Page 40

ATMAS Division

UNCLASSIFIED

ES010006101UM05
E184
Issue
B
Date:
27/03/2003

Peripherals Failure

The Failure of PUs handled by BCK, is managed according to the information that the function has.
DAT Unit:
If the DAT Unit currently in use is not available, a message to I/O console is sent.
If other DAT is mounted, the backup will continue on this one with the loss of few minutes.
The first DAT unit is dismounted but not closed correctly.
Backup will be able to use it to restore operation but last Save set is lost.

If no other DAT are available, the backup stops his activity, it will continue when a new DAT is
assigned and mounted for writing operations
I/O console:

Even if the application task takes information about failure on I/O console, it continues to work
without testing.
Node Supervisor will have to send a stopping communication to the application tasks that use it.
The application task will be able to notify to NS some particular conditions regarding to peripheral
units known by it.
NS can decide what to and can ask to the application task to carry out it.

UNCLASSIFIED

Page 41

ATMAS Division

10.

UNCLASSIFIED

ES010006101UM05
E184
Issue
B
Date:
27/03/2003

OPERATIVE STARTING

When system is loaded for the operative starting the following operations are executed:
BCK ASS DTn WR Logical - Physical Unit assignment

BCK MOU DTn DAT number n mount

To restore a save set the following operations are executed:
BCK ASS DTn RD Logical - Physical Unit assignment

BCK MOU DTn DAT number n mount

BCK MON Dtn to know save sets stored
BCK RST DTn Fxx FLy to restore a save set on disk.

UNCLASSIFIED

Page 42