OMSCHD
This pipeline process modifies the database table OMS_SCHED_TABLE.
Only a single instance can be in
the pipeline. OMSCHD is a time poller that evaluates events in
the database OMS_SCHED_TABLE to produce scheduling unit files
that trigger OMSANL runs. Although special and expected events
for the entire week are loaded in to the database, only events
down to the last subset processed by PREPRC are considered
eligible for scheduling. The first pass sets each event delay
time to zero when telemetry is available. Next, delay times are
set to zero when telemetry gaps are expected. Currently, the only
event that can explain small gaps is the engineering tape recorder
event ETR. The final pass before scheduling, is to decrement all
delay times greater than zero by the decrement amount DELAY_DECREMENT
found in the resource file.
Scheduling subsets begins with the first BOACQ event within a
subset and ends on the last BOACQ with a subset. An earlier
last BOACQ will be selected if the duration is more than
MAX_SCHED_DUR specified in the resource file. A scheduling
unit can not span across a non-zero delay time since it is
waiting on missing AEDP subsetS.
If OMSANL is suspended, OMSCHD will not reschedule the
same events twice. As entries are written to the SU file,
the same information is loaded into the historical database
table OMS_SU_TABLE with an 'L' status. Later, after OMSANL
runs, OMSUPD resets this status to 'C'.
Usage: OMSCHD i
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.