Go to the bottom.

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

LANGUAGE  SQL

INCLUDE  ZSPSS_USER_TYPES.SDDL

RECORD  ms_catalog_type

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

    DESCRIPTION      "This relation associates a PASS Mission Scheduler (MS) 
                      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 ms_name
        TYPE PASS_MS_NAME_TYPE
    END_FIELD


    FIELD  pass_sms_id
        TYPE PASS_SMS_ID_TYPE
    END_FIELD


    FIELD pass_run_type
        DESCRIPTION    "Indicates whether the run is for the initial ('I')
                        or final ('F') run of PASS for the SMS. 
                        Discrete values for this field are an I for initial 
                        and an F for final. "
        TYPE           C*1
    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 for a non-flight product and 1 for flight 
                        product. "
        TYPE           I*4
    END_FIELD


    FIELD continuity_ms
        DESCRIPTION    "The field contains the (typically) previous mission
                       scheduler file identifier for the run. The continuity 
                       MS comes from a previous run of the mission scheduler
                       with another SMS."
        TYPE           C*16
    END_FIELD


    FIELD basefile
        DESCRIPTION    "The field houses the basefile namelist file.  This 
                        namelist file contains additional run parameters."
        TYPE           C*16
    END_FIELD


    FIELD cin_file       	
        DESCRIPTION    "The continuity input namelist file used to link this 
                        MS run with a previous one."
        TYPE           C*16
    END_FIELD

END_RECORD


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


RELATION  ms_catalog

    TYPE             ms_catalog_type

    DESCRIPTION      "PASS Run Configuration By SMS Relation"

    SUBSYSTEM_USING  "SCS", "SPST", "PASS"

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


    INDEX  ms_catalog_1
        TYPE         unique, clustered
        FIELDS       ms_name
    END_INDEX

END_RELATION

Go to the top.