Go to the bottom.
!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!
! SDDL: CONSTRAINT_WIN_VER_CRITERIA.SDDL
!
! Purpose: This SDDL defines the constraint_win_ver_criteria relation.
!
! Modification History:
!
! Date PR Who Reason
! -------- ------- --- -------------------------------------------------
! 07/18/94 27073 SSW SPSS Planning Windows Support
! 03/14/95 28429 RJS Comments update
! 05/08/98 36870 MRB Add C output
! 03/26/98 38307 rjs Constraint windows need to be padded before
! verification
! 10/01/01 44572 sss Added index
!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!
LANGUAGE C, FORTRAN,SQL
!------------------------------------------------------------------------------
!
! RECORD INFORMATION
!
!------------------------------------------------------------------------------
RECORD VER_CRIT_TYPE
DESCRIPTION "This relation contains the constraint window verification
criteria that SPSS CALOPT tool uses when verifying constraint
windows (CALOPT/VERIFY_WINDOWS command).
A constraint window is a SPIKE 'start to start' contraint.
This means that SPIKE expects SPSS to be able to schedule a
scheduling unit to start at any time during the constraint
window. Note that this imposes no restriction on where the
rest of the scheduling unit schedules. That is, a scheduling
unit may extend outside of a constraint window, as long as the
first science activity of the SU starts within the window.
Using CALOPT, SPSS determines whether an SU can indeed be
scheduled to start over the entire SPIKE constraint window.
In most cases, however, there will be periods or 'gaps' within
constraint windows where an SU cannot start. When a gap
exceeds the amount specified by the field max_delta (see field
descriptions below), that constraint window fails CALOPT
verification. When any one of the constraint windows for an
SU fails verification, CALOPT marks the field
QSCHEDULING.cw_status as failed or 'F'. That field is set to
'V' only if all the constraint windows pass verification.
In the process of SPIKE constraint window generation, CALOPT
computes SPSS 'verified' constraint windows. These are
'start to start' windows within each SPIKE constraint window
that are separated by gaps that are no larger than max_delta.
In a sense, verified constraint windows represent true
constraint windows because they were determined by SPSS,
whereas SPIKE constraint windows represent long range plan
estimates for constraint windows."
!------------------------------------------------------------------------------
!
! FIELD INFORMATION
!
!------------------------------------------------------------------------------
FIELD window_duration
TYPE I4
DESCRIPTION "This field defines the minimum constraint window
duration for which the data in this record is valid.
The data contained in this record will be used for
constraint windows with durations within the range
window_duration to the next higher window_duration
value in the table. If this is the largest, then
the data are valid up from window_duration to
infinity. A record for defining the smallest
duration case (window_duration=0) must exist in this
relation."
END_FIELD
FIELD duration_units
TYPE C10
DESCRIPTION "This field describes the type of duration that is
given in the above window_duration field."
DISCRETE "WEEKS", "DAYS", "ORBITS", "HOURS", "MINUTES"
END_FIELD
FIELD max_delta
TYPE I4
DESCRIPTION "This field is used to specify the largest allowable
gap within a SPIKE constraint window during
CALOPT/VERIFY=SPIKE_CW verification. A gap is a
period of time within the constraint window where
SPSS is unable to successfully place an SU. If a gap
larger than max_delta exists for any of the
constraint windows for an SU. CALOPT marks the
QSCHEDULING.cw_status flag as faied or 'F',
otherwise it is marked as verified='V'. This
does not apply to the verification of SGD windows
via CALOPT/VERIFY_WINDOWS=SGD.
SPSS also uses max_delta to create SPSS 'verified'
constraint windows. These are 'start to start'
windows within each SPIKE constraint window
(CALOPT/VERIFY=SPIKE_CW) or SPSS SGD window
(CALOPT/VERIFY_WINDOWS=SGD) that
are separated by gaps no smaller than max_delta.
The value of max_delta in this record is used
for SPIKE constraint windows with durations that
lie within the range window_duration in this record
to the next larger window_duration value that exists
in this table."
END_FIELD
FIELD delta_units
TYPE C10
DESCRIPTION "This field describes the type of duration that is
given in the above max_delta field."
DISCRETE "WEEKS", "DAYS", "ORBITS", "HOURS", "MINUTES"
END_FIELD
FIELD step_size
TYPE I4
DESCRIPTION "This field specifies the amount of time CALOPT
will advance the start time when verifying
constraint windows. This is used to speed up
CALOPT run time by optimally choosing the
next scheduling unit start time."
END_FIELD
FIELD step_size_units
TYPE C10
DESCRIPTION "This field describes the type of duration that is
given in the above step_size field."
DISCRETE "WEEKS", "DAYS", "ORBITS", "HOURS", "MINUTES"
END_FIELD
FIELD pad_size
TYPE I4
DESCRIPTION "This field specifies the amount of time added
to the start and end of the constraint window.
This padded window, not the constraint window,
is to be verified via CALOPT/VERIFY=SPIKE_CW."
END_FIELD
FIELD pad_size_units
TYPE C10
DESCRIPTION "This field describes the type of duration that is
given in the above cw_pad field."
DISCRETE "WEEKS", "DAYS", "ORBITS", "HOURS", "MINUTES"
END_FIELD
END_RECORD
!------------------------------------------------------------------------------
!
! RELATION DECLARATION
!
!------------------------------------------------------------------------------
RELATION constraint_win_ver_criteria
TYPE VER_CRIT_TYPE
DESCRIPTION "LRP Constraint Windows Verification Criteria Relation"
SUBSYSTEM_USING "SPSS", "CCLIST"
RELATED_FIELDS "constraint_windows.*" "constraint_windows_ver.*" "lrp_base_cat.*" "qscheduling.cw_status"
INDEX constraint_win_ver_criteria_1
TYPE clustered
FIELDS window_duration
END_INDEX
END_RELATION
!------------------------------------------------------------------------------
!
! INSTANCE DECLARATION
!
!------------------------------------------------------------------------------
INSTANCE constraint_win_ver_criteria
TYPE VER_CRIT_TYPE
! DESCRIPTION "This instance can be used for database queries."
END_INSTANCE
INSTANCE criteria_array
FILE
TYPE VER_CRIT_TYPE
! DESCRIPTION "This instance can is used to house criteria sets for
! CALOPT processing."
GLOBAL
DIMENSION 20
END_INSTANCE
INSTANCE num_criteria
FILE
TYPE I4
! DESCRIPTION "This instance is a count of the number of active elements
! in the above criteria_array instance."
GLOBAL
END_INSTANCE
Go to the top.