This table contains the validity of CUS4 files that are also known as CUS16 files; there are four CUS4 files per instrument. The CUS4 files change over time and their configuration control has been maintained by each ISG.

Use and Related Data

Population

no args:      This assumes that all tables have been created in the database
     icsa, and that all temporary tables have been built and populated
     with the necessary uplink data.

-build:      Forces the building of the ISO Data Archive tables in the icsa database

-build_all:      Forces the building and population of all temporary tables needed.

-compress:      Is used to indicate that the datafiles have been compressed with
     the UNIX utility 'compress'. The data files will be re-compressed
     after use.

-nodrop:      Indicates that temporary tables should not be dropped after use.

Columns

Name	Datatype	Null
inst	char(1)	No
filetype	int	No
version	int	No
revstart	int	No
revend	int	No

column filetype

     The following integer values are used to represent the CUS-4 file types:

ICPT
ICS
IDSDB
VERBS
 

     Character representing the instrument:

     C     CAM
     L     LWS
     P     PHT
     S     SWS

column revend

     Revolution number until which CUS4 files are valid.

column revstart

     Revolution number from which CUS4 files are valid.

column version

     CUS4 configuration control version number.
 

Dependencies

Referencing Objects

Object Name	Object Type
dbo.cus4_validity.cus4_validity_pk	INDEX

Referenced Objects

Object Name

Object Type

DDL

CREATE TABLE dbo.cus4_validity 
(
    inst     char(1) NOT NULL,
    filetype int     NOT NULL,
    version  int     NOT NULL,
    revstart int     NOT NULL,
    revend   int     NOT NULL
)
LOCK ALLPAGES
go