Документ взят из кэша поисковой машины. Адрес оригинального документа : http://www.stsci.edu/spst/lrpg/mupid/Task-BaselineControl.txt Дата изменения: Thu May 10 22:19:18 2001 Дата индексирования: Sat Mar 1 16:17:38 2014 Кодировка:

ABSTRACT
========
The DCL programs diff_lrps.com, main.com, available.com,
whats_super.com, supersnap_cand.com, baseline_lrp.com,
submit_baseline_reports_now.com, baseline_reports.com,
submit_baseline_reports.com, clean_pool_tool.com, merge_cal_lrp.com,
expire_list.com, mustgo.com, submit_base.com, archive_lrps.com and the
tcsh script makesuper will be replaced by a new tool: baseline. This
new baseline tool will baseline an LRP and perform all of the
necessary checks and reports.


PREREQUISITES
=============
These requirements assume the availability of the following:

1. DBSA OPR XXXXX New fields lrp_cat.start_time lrp_cat.baselinable

2. DBSA OPR XXXXX New field lrp_case_cat.override_comment

3. replace lrp-batch-even.command and lrp-batch-odd.command with a
single command that handles both the even and odd LRPs and
populates lrp_cat.start_time

4. implement a tool to check the quality of each daily LRP and set
lrp_cat.baselinable accordingly.

5. establish regular automatic notification to LRP staff when:

A. a visit loses its plan windows between LRPs
B. a visit gains plan windows between LRPs
C. a visit's plan window moves by more than ~56 days
D. a visit has a plan window of zero duration
E. a visit has su_track.lrp_state = "ready" and no plan windows

6. establish automatic maintenance of the super-snap pool.

7. update baseline reports for PCs and management and port them to
Unix

8. update OPM reports and port them to Unix


Control File
------------
All of the numerical constants mentioned in these requirements should
be stored in a user-modifiable control file. The name of this control
file should be referenced through an environment variable.


Command Syntax and Parameters
-----------------------------
baseline [LRP name]

If the LRP name is omitted, the most recent released LRP will be used.


Optional Qualifiers
-------------------
qualifier: -force
default: disabled
function: Baseline the LRP even if lrp_cat.baselinable is not "Y".
Record comment in lrp_base_cat.override_comment.


Baseline Functionality
----------------------
0. If errors are encountered in any of the following steps, abort
baseline gracefully.

1. Compare wbase_cat.base_time to lrp_cat.start_time for the previous
calendar. If the previous calendar was baselined after the LRP
start time, the LRP must be rerun before it can be baselined. In
this is the case, report it to the user as an error end abort
baselining.

2. Check lrp_cat.baselinable.

A. If baselinable is Y, proceed to step 3.

B. If baselinable is N or blank and the -force qualifier is not
specified, issue and error indicating that the LRP will not be
baselined and end the program.

C. If baselinable is N or blank and the -force qualifier is
specified, then enter the force comment in
lrp_base_cat.override_comment and proceed to step 3.

3. Insert the LRP into lrp_base_cat.

4. Send mail to LRPG and SPST informing them that the LRP has been
baselined for the coming week's flight calendar. Include a list
of must go visits that are not yet flight ready, if any. Give the
user the opportunity to manually add additional text into the mail
message.

5. Delete all non-baselined LRPs that are older than 7 days and have
lrp_name like %AUTO% or have lrp_name of the format YYDDDV.

6. Archive baselined LRPs older than 8 weeks. To archive an LRP
move all of its data from the assist tables plan_windows,
plan_orient, lrp_processing_errors, plan_window_status,
lrp_unschedulables, lrp_cat, and lrp_base_cat into the
corresponding tables in archive_assist.

7. Report baseline results.

A. Report to individual PCs any must go visits that are not yet
flight ready.

B. Report to individual PCs any programs that have been dropped
between LRPs.

C. Report to the user and to the PC when a visit has expired plan
windows.

D. Generate the standard baseline reports for the PCs. Some PCs
find these reports useful. Other PCs do not. Perhaps the
reports should be sent only to those PCs that want them.

E. Generate the standard baseline reports for management. Mail
these to the OPT lead, SPST lead, and/or any LRP staff that
want them.

1) full unschedulable report

2) cycle 7 report

3) full difference report

4) Full Expired, Open, & Opening Soon Report

5) summary report

Some of these are also written to disk and saved. Do we need
to keep doing that? If so, they should be written to
$lrp_dir/reports instead of /data/cerberus3/reports.

F. run ANT

G. Generate OPM reports