Go to the bottom.

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!
! SDDL Name:	cl_catalog.sddl
!
! Purpose:      This SDDL file defines the cl_catalog relation.
!
! Modification History:
!
!   Date       PR      Who                       Reason
! --------   -------   ---   -------------------------------------------------
! 11/13/01   44750     MRB   Original implementation
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

LANGUAGE  SQL

INCLUDE  ZSPSS_USER_TYPES.SDDL

RECORD  cl_catalog_type

!------------------------------------------------------------------------------
!
!   RECORD INFORMATION
!
!------------------------------------------------------------------------------

    DESCRIPTION      "This relation associates a PASS Command Loader (CL) 
                      run with a mission schedule run and a CL run with its 
                      input files.  This helps to distinguish between flight 
                      and non-flight products and to track the inputs.  

                      The file names stored here clearly record what went into 
                      a given run.  This information is helpful to document 
                      what a run consisted of and very helpful when cleaning up
                      after runs.  More information about the input file fields 
                      can be gleaned from PASS documentation.  

                      No SPSS software populates this relations.  SPST
                      operations tools are planned to populate and read 
                      this relation."

!------------------------------------------------------------------------------
!
!   FIELD INFORMATION
!
!------------------------------------------------------------------------------


    FIELD cl_name
        DESCRIPTION    "Tells the command loader name for the run.  Typically
                        the name is similar to the ms_name with the addition
                        of an underscore and a number or letter and number.
                        The additional characters indicate the run sequence
                        or if it is a final;  this is only by user convention."
        TYPE           C*16
    END_FIELD

 

    FIELD ms_name
        TYPE PASS_MS_NAME_TYPE
    END_FIELD


   FIELD status
        DESCRIPTION    "Indicates whether the run is for a non-flight product 
                        or for a flight-product.  Discrete values for this 
                        field are 0 of non-flight product and 1 for flight 
                        product. "
        TYPE           I*4
    END_FIELD


    FIELD continuity_cl_486
        DESCRIPTION    "The field contains the (typically) previous command
                       loader file identifier for the run. The continuity 
                       CL comes from a previous run of the mission scheduler
                       with another SMS.  This file is specific to the 486."
        TYPE           C*16
    END_FIELD


    FIELD continuity_cl_nssci
        DESCRIPTION    "The field contains the (typically) previous command
                       loader file identifier for the run. The continuity 
                       CL comes from a previous run of the mission scheduler
                       with another SMS.  This file is specific to the NSCCI."
        TYPE           C*16
    END_FIELD


    FIELD cl_start_file
        DESCRIPTION    "Contains the command loader start namelist file.
                        It can be used to determine load breaks as well as
                        specifying other command loader parameters. "
        TYPE           C*16
    END_FIELD



    FIELD cl_base_file     	
        DESCRIPTION    "Contains the command loader base file namelist
                        for the run.  "
        TYPE           C*16
    END_FIELD


    FIELD moc_input_file
        DESCRIPTION    "Contains the Mission Operations Center (MOC) 
                        command loader input file (typically).  This
                        is a fairly static file but can be varied for any run. "
        TYPE           C*16
    END_FIELD


    FIELD moc_text_file
        DESCRIPTION    "Contains the Mission Operations Center (MOC) 
                        command loader text file.  Like moc_input_file, this
                        is a fairly static file but can be varied for any run. "
        TYPE           C*16
    END_FIELD

END_RECORD


!------------------------------------------------------------------------------
!
!   RELATION DECLARATION
!
!------------------------------------------------------------------------------


RELATION  cl_catalog

    TYPE             cl_catalog_type

    DESCRIPTION      "PASS Run Configuration By SMS Relation"

    SUBSYSTEM_USING  "SPSS", "SCS", "PASS"

    RELATED_FIELDS  "pass_status.*" "pass_run_names.*" "pass_sms_edits.*" "ms_catalog.*" "ms_merge_sms.*"


    INDEX  cl_catalog_1
        TYPE       unique, clustered
        FIELDS     cl_name
    END_INDEX

END_RELATION

Go to the top.