OMSTLM

This pipeline process modifies the database table OMS_SCHED_TABLE and should not be run interactively. Only a single instance can be in the pipeline. For every AEDP subset successfully processed by PREPRC, or every CCS subset successfully produced by CVTFOF, the BOF and EOF telemetry events from the subset *.ER* file are loaded into the database table. BGAP and EGAP events in the *.ER* are converted to EOF and BOF events respectively in the database, since they also delimit times when telemetry is available within the subset.

Be aware that there is a TLM_TIME_JUMP_LIMIT mnemonic in the resource file. The value of this mnemonic (fraction of Day) specifies the OMSTLM allowable time duration (EOF time - BOF time) of subset files. If the duration of a subset file is less than or equal to the TLM_TIME_JUMP_LIMIT value, OMSTLM will process the subset file; i.e., telemetry events for the subset file will be inserted into the OMS_SCHED_TABLE. If the duration of a subset file is greater than the TLM_TIME_JUMP_LIMIT value, OMSTLM will not process the subset file and the following will occur:

a "Telemetry Time Jump Limit Exceeded" message will be written to the OMSTLM Log file
an "_BAD" will be appended to the offending *.ER* file
the Sub Class OSF that triggered OMSTLM will be set to "F" in the TM column
no telemetry events from the subset file will be inserted into the OMS_SCHED_TABLE
no other *.ER* files having the same rootname as the offending *.ER* file will be processed

Format

$ OMSTLM i -f FILE

Parameters

i interactive

This parameter indicates that the command is interactive. Actually any string without a preceeding dash(-), anywhere within the command will indicate that the command is interactive.

Note: Interactive commands assume that the mnemonics assigned in the OPUS_DEFINITIONS_DIR:NULL.PATH file will be used.

-f FILE