!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! ! ! SDDL Name: OMS_SCHED_TABLE.SDDL ! ! Purpose: This SDDL file defines relation OMS_SCHED_TABLE ! ! Modification History: ! ! Date OPR Who Reason !---------------------------------------------------------------------- ! 28-APR-97 31344 PERRINE original ! 06/03/97 31344_02 Perrine Make table names lowercase ! 10/13/99 38203 Ken S. Add trim and rject events. !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! ! ! LANGUAGE SQL RECORD OMSCHD_TYPE !---------------------------------------------------------------------- ! ! RECORD INFORMATION ! !---------------------------------------------------------------------- ! DESCRIPTION "This SDDL file defines relation OMS_SCHED_TABLE. Records are appended to this relation when OMSEVT processes a new EVT file created by YECMSC parsing of the weekly PASSOPS versionof the SMS. OMSUPD removes records after OMSANAL successfully processes subsets found in the SUTABLE relation." !---------------------------------------------------------------------- ! ! FIELD INFORMATION ! !---------------------------------------------------------------------- FIELD ctime TYPE C*56 DESCRIPTION "Calender time format yyyy.ddd:hh:mm:ss.ss of events read from the EVT or ER0 file." UNITS END_FIELD FIELD jtime TYPE R*8 DESCRIPTION "Julian time format hhhhh.sssss of events read from the EVT or ER0 file." UNITS END_FIELD FIELD event TYPE C*31 DESCRIPTION "Name of an event read from the EVT or ER0 file. Beginning and ending events exist for the mission schedule, each subset,gaps within subsets and special and expected events found in the SPECIAL EVENTS file." UNITS END_FIELD FIELD delay TYPE R*8 DESCRIPTION "Julian time to delay processing important event occurring in a telemetry gap. The default appears for certain events in the SPECIAL EVENTS file. This time is decremented whenever the scheduler runs and set to 0.0 when telemetry is available. Only when the delay time is 0.0 will events be scheduled." UNITS END_FIELD FIELD type TYPE C*5 DESCRIPTION "There are four types of events (SPEC,XSPEC,TRIM, and REJEC) that are defined in the SPECIAL EVENTS file. SPEC events are those which, by default, delay OMS processing when they occur within a telemetry gap. XSPEC events are interesting orbital events that are by default acceptable to (eXPECted by) OMS processing when found near or within a telemetry gap. TRIM and REJEC are special sorts of XPEC events that apply only to COMCON events. These values imply that the event in the mission schedule has been altered or rejected by NCC and may not occur when the schedule executes. Records with type TELM mark the beginning and ending of telemetry data segments and are not derived from the mission schedule." UNITS END_FIELD FIELD status TYPE C*4 DESCRIPTION "The status field is used internally to select events for scheduling, to prevent rescheduling and to delete events already scheduled W-wait,P-processed,S-start, E-end,L-already scheduled,C-completed,D-ready for deletion." UNITS END_FIELD FIELD insert_time TYPE SYBASE_DATETIME DESCRIPTION "Only TELM types are assigned a current system time when added to the table to determine the most recent subset. Datetime is 2I*4 values,representing days since 1/1/1900 and time of day (1/300sec)." UNITS END_FIELD END_RECORD !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! ! ! RELATION DECLARATION ! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! RELATION oms_sched_table TYPE OMSCHD_TYPE DESCRIPTION "OMS table of mission schedule and telemetry events needed to select subsets for processing" SUBSYSTEM_USING "OMS" END_RELATION !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! ! ! INSTANCE DECLARATION ! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! INSTANCE oms_sched_table GLOBAL TYPE OMSCHD_TYPE END_INSTANCE