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

Objective: How to Make changes to a Plan Window, using an sql report/tool
which is located on SOGS in the LRP account.


The Tools to Use:

SET_DINK.COM Generates the records which allow the Plan Window
changes to occur.


PW_FIXUP.COM Runs the SQL which "dinks" the plan window for the choosen
LRP.


Proper usage:

SET_DINK.COM

@set_dink SU_ID dink_type [wnd_start wnd_end]

Creates records that allow dinking of plan windows
Allowed dink types are:
APPEND - appends more PWs for REPLACE
DELETE - deletes existing dink records
INTERSECT - replaces PW with intersection of given window and CWv
REPLACE - replaces PW with given window
USECWV - replaces PW with CWv

Care must be taken when choosing which "type" of dink record to
use. For example, an APPEND is generally used (only?) after
a REPLACE record already exits. The DELETE is used if there
is any other sort of change made to a previously modified
PW (REPLACE needs to become an INTERSECT).

It is also very important to carefully select the start and
end times to enter as they will have direct ramifications on the
calendar builders.

(More input here is needed by Michelle SVPL)


The method for dinking,is to go to the directory
[lrp.mmb.dink], and create a file named:
DINK_DDD_V.FILE

with the format and commands as follows


$ ty DINK_024_1.FILE
$do set_dink 0609702 intersect 1996.084:00:00:00 1996.148:00:00:00

Run the file by typing

@DINK_DDD_V.FILE


Watch to see that the command runs and does not get blocked by
other database actvities.

When the command has finished you must then run the command

PW_FIXUP.COM

Proper usage:
@pw_fixup lrp_name


Runs the SQL to dink all the needed PWs, that is it effects the changes to
the Plan Window for a given LRP.
To input lower case, you must use quotes around the lrp_name.


A very usefull tool to view the PWs, CWvs and Visit LRP information
is to run the tool on SOGS side from PLANNING account,

do lrp_info visit_id (or prop_id) LRPname (default released) tt: (to send to screen)

it can also accept a list of visit or prop ids.

EXAMPLE:

do lrp_info 632911,632912
Please try not to press ^C or ^Y during the execution of this program--
it is quite database intensive.

Getting info for SU 0632911

SU 0632911 PC: BREMMER Cycle: 4 scheduling
Est. orb: 5 cw_status: S in SPSS: Y LRP: 96033A
-----------------------------------------------------------------------
QSP order_num: (none) week_id: (none)
USC 1996.034:00:00:00 1996.084:19:56:40 M:o C:19-Sep-1995 N:cyc_4_pws
Comment: Allows old cyc 4 PWs to be passed through -wmk
LNK prim. to 0632912 with delta = +0021:00:00:00 and tolerance = 0014:00:00:00
MOD 1996.057:09:00:00 1996.117:00:00:00
PW 1996.057:09:30:51 1996.076:19:57:39
1996.080:17:14:06 1996.116:10:32:05
CWV 1996.057:09:30:51 1996.076:19:57:39 created on 1996.032:20:53:58
1996.080:17:14:06 1996.116:10:32:05 created on 1996.032:20:53:58
CW 1996.034:00:00:00 1996.084:19:56:40 created on 1996.021:15:29:41


Getting info for SU 0632912

SU 0632912 PC: BREMMER Cycle: 4 scheduling
Est. orb: 2 cw_status: S in SPSS: Y LRP: 96033A
-----------------------------------------------------------------------
QSP order_num: (none) week_id: (none)
USC 1996.057:00:00:00 1996.112:22:28:20 M:o C:19-Sep-1995 N:cyc_4_pws
Comment: Allows old cyc 4 PWs to be passed through -wmk
LNK sec. to 0632911 with delta = +0021:00:00:00 and tolerance = 0014:00:00:00
MOD 1996.057:09:00:00 1996.117:00:00:00
PW 1996.057:09:30:51 1996.076:19:57:39
1996.079:23:32:41 1996.116:20:11:08
CWV 1996.057:09:30:51 1996.076:19:57:39 created on 1996.032:20:46:23
1996.079:23:32:41 1996.116:20:11:08 created on 1996.032:20:46:23
CW 1996.057:00:00:00 1996.112:22:26:40 created on 1996.021:15:29:42