! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! ! ! SDDL Name: ZQSLINK_INFO.SDDL ! ! Purpose: This SDDL file defines the qslink_info relation. ! ! Modification History: ! ! Date OPR Who Reason ! -------- ------- --- ------------------------------------------------- ! 10/21/94 27329 EGB Original implementation ! 01/20/95 27845 MRB Added af_rev_number for partial trans generation ! 09/05/96 32570 RJS Added Link type field. ! 02/07/97 33001 SXT Rename QSLINK_SPEC to QSLINK_TIMING ! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! ! ! LANGUAGE FORTRAN, SQL INCLUDE ZSPSS_USER_TYPES.SDDL RECORD LKINFO_TYPE !------------------------------------------------------------------------------ ! ! RECORD INFORMATION ! !------------------------------------------------------------------------------ DESCRIPTION "This is a housekeeping record that is used to track changes to the linked set specification information that is stored in qslink_orient and/or qslink_timing. This housekeeping includes link set validation status and various time stamps. A linked set is a collection of two or more scheduling units with a timing (link_type=TIMING) or orientation (link_type=ORIENT) relationship between the SUs. There is a 1 to N relationship between this housekeeping record and the qslink_timing or qslink_orient records." !------------------------------------------------------------------------------ ! ! FIELD INFORMATION ! !------------------------------------------------------------------------------ FIELD link_set_id TYPE LINK_SET_ID_TYPE RELATED_FIELDS "qslink_timing.link_set_id" END_FIELD FIELD validity TYPE C1 DESCRIPTION "This is the status of link set specification. The following definitions are valid for this field. 'I' designates the link set is INVALID, meaning there are one or more problems with the relationships that are specified between the link set members (SUs). A link set is always INVALID when first created or when it gets modified. If the link set is modified from SPSS PFORM LSD and a consistency check is performed from the form (via the keypad 1 keystroke), the validity flag will be changed to 'C', meaning the link relationships/set is CONSISTENT. This is good, but the link set must still undergo more rigorous checks from PMDB/VALIDATE. When the SPSS command PMDB/VALIDATE is run on the link set a more rigorous check on the link relationships is applied. That check involves link member information from the GLOBAL baseline. Should the checks prove successful the validity flag will be changed to 'P', meaning the link set should be POSSIBLE to schedule. In order for link information to be scheduled on a calendar by SPSS this field must be 'P'. FORM NAME "LSD" LABEL "LINK VALIDITY STATUS (I=Invalid/C=Consistent/P=Possible to schedule)" END_FORM DISCRETE "I", "C", "P" END_FIELD FIELD valid_date TYPE INT_TIME_STAMP_TYPE UNITS "SEC" DESCRIPTION "This is the date the last PMDB/VALIDATE command was performed on the link set (irregardless of the outcome of the command). See update_field below to see one way this field is used. If this field is 0 the link set has never been validated." FORM NAME "LSD" LABEL "DATE OF LAST LINK SET VALIDATION ATTEMPT" END_FORM END_FIELD FIELD update_date TYPE INT_TIME_STAMP_TYPE UNITS "SEC" DESCRIPTION "This is the date of last link specification update, i.e. the last time the qslink_timing records for this link set were changed (via PFORM LSD). If the above valid_date is earlier (less than) this update_date field, that means the link set specification has been changed after the last validation attempted. If this field is 0, the link set has never been changed." FORM NAME "LSD" LABEL "DATE OF LAST LINK SET SPECIFICATION UPDATE" END_FORM END_FIELD FIELD af_rev_number TYPE AF_REVISION_NUMBER_TYPE RELATED_FIELDS "qpdescrip.af_rev_number" END_FIELD FIELD af_load_date TYPE TIME_STAMP_TYPE DESCRIPTION "This field is the date the assignment file was loaded." END_FIELD FIELD prop_rev_number TYPE I2 DESCRIPTION "This field is the proposal revision number for which the assignment file was last generated. This will be populated by Trans. This information is also stored in proposals_processing, which is replicated into SOGS, in the prop_rev_generated field, but that is updated only when GENERATE_AF is run. Passing it through in the assignment file will provide verification that the AF came from the same version of the proposal that the PC thought was being provided via the GENERATE_AF and TRANSFER tools." END_FIELD FIELD spike_version TYPE C6 DESCRIPTION "This field is the software version of Trans or SPIKE that was used to generate the assignment file. This information is already being provided in QPPComments and QSUComments for proposal-level and SU entities, but needs to be provided as well for targets and links." END_FIELD FIELD link_type TYPE C6 DESCRIPTION "This field specifies whether the linked set constrains the link members based on time (TIMING), or V3 position angle at the target (ORIENT)." END_FIELD END_RECORD !------------------------------------------------------------------------------ ! ! RELATION DECLARATION ! !------------------------------------------------------------------------------ RELATION qslink_info TYPE LKINFO_TYPE DESCRIPTION "Link Set Housekeeping Information Relation" SUBSYSTEM_USING "SPSS", "TRANS" RELATED_FIELDS "qslink_timing.*", "qslink_orient.*" FORM NAME "LSD" END_FORM INDEX qslink_info_1 TYPE unique, clustered FIELDS link_set_id END_INDEX END_RELATION !------------------------------------------------------------------------------ ! ! INSTANCE DECLARATION ! !------------------------------------------------------------------------------ INSTANCE qslink_info GLOBAL TYPE LKINFO_TYPE END_INSTANCE