File PCS

     Name:     pcs
     Code:     pcs
     Label:     S2.1.39
     Number:     26

Permanent Command Sequences (PCS), a permanent instantiation of an ICS held on-line in the IDCS, and available for INSCONs to upload when manual commanding is required, for example, manual activation/deactivation. Times when PCSs uplinked may be available from real time report - no, information not available

Configuration control information as to which PCSs are installed for each revolution and link to actual PCSs. No information about which PCS was actually uplinked is available (possible to extract somehow from TChistory, but very difficult). Very limited set of PCSs is actually used (excepting activation, deactivation and saturation related).
May be possible to extract a history of PCS uplinked on a time basis - to be investigated. If not, is it worth keeping PCSs on-line? Or should only PCS configuration information (e.g. revolution/version) be stored?

These are stored, as is, as ASCII files. Configuration control information must also be stored, see PCS Validity table.

Use and Related Data

Linked to PCS validity table, contains revolution period of use and location reference of actual file. These files are kept as is.

Post Operations

The PCSs have been obtained from configuration control and they have been manually copied to the directory /pmadata/, where all linked and viewable data resides, and ordered by version number.

Interim

Not applicable.

The following table gives the number of files, the average file size, and the resulting total size in KB.