Download SCOS-2000 Database Import ICD

Ref.:
SCOS-2000 Database Import ICD
EGOS-MCS-S2K-ICD-0001
Issue:
6. 9
Date:
2010-07-06
Page:
10
specified, the domain from which the import operation is initiated will be assumed in order to identify the
database to be imported.

‘Check only’: this option does not affect any data but just reports about the outputs of the tables structure and
field length checks performed by the importer.
As from SCOS-2000 Release 5.0, the run-time management of command sequence and TM display definitions has
been modified. The content of the relevant ASCII files (see Section 3.3.2.7 and 3.3.3.3) is converted upon user
request into XML files which are then imported into the FARC (and not imported into the POST run-time database).
The relevant applications (e.g. command sources, TM desktop) load the required definitions from the FARC. The
structure of the XML files which are used when loading sequences/displays in the relevant application is documented
in [AD-4] and [AD-5] , respectively.
It should be noted that the S2K-R5 approach described above for the run-time management of sequences and
displays definitions implies the following changes in the database import philosophy:

The import of command sequences and display definitions is managed independently. This removes the
need to import a new version of the TM/TC database in order to update a command sequence or a display
definition

The import of the ASCII files containing sequence or display definitions is based on a ‘delta’ approach i.e.
only the definitions contained in the ASCII files to be converted/imported are updated in the FARC. The
existing definitions are not removed and thus are still available to the relevant applications for loading.
ESA/OPS-GIC