Документ взят из кэша поисковой машины. Адрес оригинального документа : http://www.stsci.edu/spst/lrpg/how-to.baseline Дата изменения: Mon Apr 26 17:29:26 1999 Дата индексирования: Sat Mar 1 07:34:35 2014 Кодировка: Поисковые слова: п п п п п п п п п п п п п п

How to Baseline an LRP
The reports are on the SOGS side under the "LRP"
account: rlogin homer lrp password

The following directories include all the tools and reports
used in the baselining process.

Directory DISK$SPSS_DATA:[LRP]


MMB.DIR;1 6-OCT-1995 12:34:39.14
TEMP.DIR;1 5-OCT-1995 17:58:41.19
TOOLS.DIR;1 5-OCT-1995 17:58:32.50
WEEKLY.DIR;1 6-OCT-1995 14:29:19.36







When do you Baseline an LRP?

Every Wednesday morning.


Checklist of Steps for preparing to Baseline an LRP

1) Check all e-mail from PCs regarding changes from the week.
complete any/all changes and transactions. This may include
the need to change Plan Windows, either with a USC or a DINK
record. (see /cerb/data1/operational/lrp/work/how-to.dink-pws)

2) Confirm SPSS has sent the cal file over to the cerberus side.
check:
/cerb/data1/operational/flight-calendars/yydddvv-spb.cal
also check the database using the command from the LRP account
on SOGS,
do latest_cal
if not there, call honcho and encourage them to send out the
latest version as along as all main-fix visits are set.

3) Check the difference report for any changes. Resolve or verify changes.
The difference report can be found in the directory, for example

[lrp.weekly] 96031A_96032A.DIFFERENCE where

oldLRP_newLRP.DIFFERENCE

4) Check uncom_sus and plannables from the [lrp.weekly]. They are named
UNCOM_SUS.YYDDDV and PLANNABLE.YYDDDV.
UNCOM_SUS.96025A and PLANNABLE.96025A are examples of these files.
Resolve or verify changes, by committing visits with a PW but no
commitment, use the command in the lisp interface

(write-spike-commentments-for-visits '("su_id" "su_id" etc))


5) Check if there are any sus without PWs wich are set to sched.

in the directory [lrp.mmb.tools] use the tool SCHED_NOPW.COM
with todays lrp name. Any su that is without a PW and set to sched
should, have a USC or dink record made, or be set to back to
implementation.


6) Now go to the cerberus side. /cerb/data3/reports

For the current daily reports grep on the key word
VIOLATES. This will report on any violsted link sets.
for example

grep VIOLATES *ddd*

grep for HAS, this will report if a pc has changed something
like a status or a commit etc..

grep on LOADED, this will report on props that may have had
loading errors and didn't make it into the lrp. Follow up
with the PC to correct or verify the current status odf the prop.




The Steps and Commands to Baseline an LRP


1) Submitting the nightly reports, a set of usefull reports
is generated and written to the [lrp.weekly] directory. The
reports com files are in the [lrp.tools] directory. This
should be done daily.

To run the command:
do submit_nightly_work.com oldlrpname newlrpname tomorrow+12

The reports generated are:

PLANNABLE.96024A
UNCOM_SUS.96024A
96024A_96025A.DIFFERENCE
NIGHTLY_WORK.LOG

2) After the nightly reports are completed the next step is to run the tool
RELEASE_LRP.COM, which will populate the fields that will allow
the PCs' tools to work with the newly released PWs.

Proper usage:
@release_lrp lrp_name


3) Go to [lrp.temp] create a com file named SUBMIT_BASE.COM see example below.
This command will both baseline an LRP and generate the
PC_REPORT, which runs the lrp_diff report for each PC and mails
them the result.


type SUBMIT_BASE.COM

$set def [lrp.temp]
$show time
$do RUN_PC_REPORT.com 96013A 96024A
$show time
$do baseline_reports 96013A 96024A 1996.050 1996.058 1997.182
$show time
$

The dates used in the command are the following:

baseline_reports oldbaseline newbaseline startcalweek endcalweek
endcyc6(97.182)

4) If there is any conscern of run errors please check the file,

submit_base.log

also in the [lrp.temp] directory.


5) When the baseline com file has completed, you must then send e-mail
to the calendar Honcho's informing them that the PWs are ready for
calendar building to begin. The message should be CC:'ed to
the LRP and PC groups, and Reinhart. Special scheduling requests
and Visits of imprtance may be noted as well (eg "MUST GOES" "LMC
CVZ" ect...)


Hello,

The 96031A has been baselined. The LRP is ready for the 96057 calendar
to begin building.

LRP Group.