Go to the bottom.
!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!
! SDDL Name: QSCHED_POOL.SDDL
!
! Purpose: This SDDL file defines the qsched_pool relation.
!
! Modification History:
!
! Date OPR Who Reason
! -------- ------- --- -------------------------------------------------
! 11/16/94 27329 NLC Original implementation
! 02/02/95 28292 SK Modified "REPLICATION" wording under
! SUBSYSTEM_USING
! 08/23/95 29544 SK Add index qsched_pool_2
!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!
!
LANGUAGE SQL
INCLUDE ZSPSS_USER_TYPES.SDDL
RECORD QSCHPL_TYPE
!------------------------------------------------------------------------------
!
! RECORD INFORMATION
!
!------------------------------------------------------------------------------
DESCRIPTION "This relation is used by SPST to track the progress of
scheduling units as they are worked on during proposal
preparation and calendar building. One scheduling_pool
record is created for each scheduling unit (SU). The
record specifies the scheduling pool to which the SU is
assigned, and the SU's scheduling status.
The scheduling pool to which the SU is assigned is
specified by the value in the week_id field. There are
3 main scheduling pools which SUs are assigned to:
Snaps - SUs where the proposal type is 'SNAP'.
This indicates the SU uses a single
guide star and is a very small observation.
Pool - General SUs.
Special - SUs which have special scheduling
requirements.
There are other scheduling pools which the SU can be
assigned to; these are mainly for unselected
SUs or SUs which are problematic in scheduling.
When an SU is reserved for a specific week, the week_id is
set to the specified week. The SU is reserved by running an
operations command file which sets the week_id and
order_num field for all SUs which will be scheduled
a given week.
The order_num field specifies at what point in the
scheduling process the SU is at, including:
NG - Initial value upon entry into the PMDB;
Indicates the SU must be investigated
' ' - Useable SU that has not been reserved or
committed
Committed to a week -
The week_id field is set to the calendar week
to which this SU is committed.
Reserved for a week -
The week_id field is set to the calendar week
for which this SU is reserved.
Locked (or scheduled) for a week -
The week_id field is set to the calendar week
for which this SU is scheduled."
!------------------------------------------------------------------------------
!
! FIELD INFORMATION
!
!------------------------------------------------------------------------------
FIELD week_id
TYPE C*5
DESCRIPTION "This field specifies which pool the SU is assigned
to, or the week(format: yyddd) the SU is reserved for.
The 3 main pools to which SUs are assigned are
specified by:
'NPS' - Snap SUs --
A snap SU is a type of proposal
which uses a single guide star and
is a very small observation.
'SPEC' - SUs which have special scheduling
requirements.
'POOL' - SUs belonging to the general pool.
The remaining SU pools are used for SUs which are
either unselected or are problematic in scheduling.
These are specified by:
'CAL' - Calibration SUs (w/ no special
scheduling requirements).
'FGS3' - FGS Cycle 3 SUs
'HRS3' - HRS Cycle 3 SUs
'MT' - Moving Target SUs
'PSFS' - PSF Snaps
'UNK' - Committed POOL/Snaps SU where the SU
is NOT on the GLOBAL Baseline, but is
flagged as executed."
END_FIELD
FIELD sunit_id
TYPE SUNIT_ID_TYPE
END_FIELD
FIELD version_num
TYPE VERSION_NUM_TYPE
END_FIELD
FIELD order_num
TYPE C*2
DESCRIPTION "This field helps track the scheduling status of the
SU. This field is initially set to 'NG', to
indicate that the SU must be verified. Once the
SU has been verified by operations staff, this
field is set to blank. When a SU is reserved,
committed, or locked to a specific week,
the order_num is set to the week.
Locking to a week means the SU is required to
appear on the specified week.
The valid entries for this field are:
'NG' - Not useable...Guide star problems,
etc. ie. Needs investigation.
' ' - (BLANK) useable SU (ie, not reserved
or committed)
'AP' - Attached parallel (from the UPD file)
'CC' - CAL Committed
'CR' - CAL Reserved
'DF' - Deferred...Either a deferred
instrument mode (ie, FOC/48) or this
SU must wait until some other group
of SUs have all been used.
'EC' - SPEC Committed
'ER' - SPEC Reserved
'FC' - PSFS Committed
'FR' - PSFS Reserved
'GC' - FGS3 Committed
'GR' - FGS3 Reserved
'HC' - HRS3 Committed
'HR' - HRS3 Reserved
'MC' - MT Committed
'MR' - MT Reserved
'OC' - CAL SUs that are locked to a week.
'OE' - SPEC SUs that are locked to a week.
'OG' - FGS3 SUs that are locked to a week.
'OH' - HRS3 SUs that are locked to a week.
'OM' - MT SUs that are locked to a week.
'OP' - POOL SUs that are locked to a week.
'PC' - POOL Committed
'PR' - POOL Reserved
'SC' - NPS Committed
'SR' - NPS Reserved "
END_FIELD
END_RECORD
!------------------------------------------------------------------------------
!
! RELATION DECLARATION
!
!------------------------------------------------------------------------------
RELATION qsched_pool
TYPE QSCHPL_TYPE
DESCRIPTION "Scheduling Pool Relation"
SUBSYSTEM_USING "SPST", "REPLICATION-FROM-SOGS"
INDEX qsched_pool_1
TYPE unique, clustered
FIELDS week_id, sunit_id, version_num
END_INDEX
INDEX qsched_pool_2
TYPE nonclustered
FIELDS sunit_id, version_num
END_INDEX
END_RELATION
Go to the top.