#!/bin/sh
more INSTRUCTIONS; exit
#******************************************************************************
#                       ISTP LZPR SOFTWARE
#               Property of the U.S. Government
#                       NASA/GSFC/Code 560
#******************************************************************************
 
 
  UNIT NAME:  INSTRUCTIONS
 
 
  PURPOSE:  To document the procedures, hardware/software requirements,
            and major functionality associated with each build/release of
            of the Re-Engineered ISTP LZP system.
 
 
  DEVELOPMENT HISTORY:
  Author           Change-ID        Release     Date      Description of Change
  ---------------  ---------------  ----------  --------  ---------------------
  R. Wiechert      ISTP             ISTP_B2     09/22/97  Original text
  R. Wiechert      ISTP             ISTP_B2     10/01/97  Corrections for B2
  R. Wiechert      ISTP             ISTP_B1     10/01/97  Updates for R1
  R. Wiechert      ISTP             ISTP_R1.0A  10/14/97  Updates for R1.0A patch
  R. Wiechert      ISTP             ISTP_R1.0C  12/21/97  Updates for R1.0C patch
  R. Wiechert      ISTP             ISTP_R1.0D  12/21/97  Updates for R1.0D patch
  R. Wiechert      ISTP             ISTP_R1.1   03/15/98  Updates for R1.1 release
  R. Wiechert      ISTP             ISTP_R1.2   04/27/98  Updates for R1.2 release
  R. Wiechert      ISTP             ISTP_R1.2A  05/10/98  Updates for R1.2A patch
  A. Tung          ISTP             ISTP_R1.4   01/19/98  Updates for R1.4
 
 
  Overview of Build Procedure:
  -------------------------------------------------------------
  1.  Software Extraction          (45 minutes total)
  2.  Software Transport           (10 minutes total)
  3.  Build Environment            (10 minutes total)
  4.  AD Software Build            ( 2 minutes times 3 missions)
  5.  TREND Software Build         ( 2 minutes times 3 missions)
  6.  FS Software Build            (10 minutes total)
  7.  DPS Software Build           (40 minutes total)
  8.  Controlled Shutdown          (20 minutes times 3 missions)
  9.  DPS Database Creation        (60 minutes times 3 instances)
  10. DPS Database Population      (15 minutes times 3 instances)
  11. RECON Tablespace Creation    (60 minutes times 4 tablespaces)
  12. RECON Tablespace Population  (15 minutes times 4 tablespaces)
  13. System Environment           (15 minutes times 2 hosts)
  14. Mission Environment          (15 minutes times 3 missions)
 
  Overview of Build Requirements:
  -------------------------------------------------------------
  1.  CM account on archive host
  2.  PVCS account on archive host
  3.  Several 150MB physical tapes
  4.  CM account on runtime host
  5.  ORACLE account on runtime host
  6.  MISSION accounts on runtime host
  7.  SUPERUSER account on runtime host
  8.  500MB local disk space
  9.  30GB RAID disk space
 
  Overview of Build Software:
  -------------------------------------------------------------
  It is assumed that the following COTS/GOTS hardware and
  software packages have been delivered, installed, and made
  available to users on the ISTP LZP runtime hosts, except for
  the PVCS software which resides only on the archive host:

  1.  Any ASCII program text editor
  2.  PVCS: get, put, vcs, vlog
  3.  UNIX: tar, ftp, compress, uncompress, crontab
  4.  Solaris 2.5 or 2.6 Operating System
  5.  Oracle 7.3.2 or 7.3.3 with Pro*C 2.2.2 compiler
  6.  X/Motif 1.2.3 with Software Development Kit
  7.  LabView 4.01 G compiler/interpreter
  8.  Washington University ftpd 2.4.2 beta 15
  9.  SunWSpro C compiler
  10. Perl 5 shell interpreter
  11. IRTS frame synchronizer
  12. RDA client software package
 
  Special Instructions:
  -------------------------------------------------------------
  To avoid constantly editing these instructions, the examples will
  always refer to the current release as "R1.4" from now on.  You
  should substitute the actual release name wherever you see "R1.4"
  in the examples.  For instance, if you are building release R3.2A
  you should change "/opt/local/cm/R1.4" to "/opt/local/cm/R3.2A".
  The software will often suggest "/opt/local/cm/current" for some
  of the prompts.  You should also substitute the actual release name
  wherever you see "current" in the suggested prompts.

  If this is the first time you are installing the ISTP LZP system,
  then you will have to work closely with the SUPERUSER in order to
  setup the various user accounts, system configuration options, and
  filesystems required by the software.  The SUPERUSER is encouraged
  to review this document and the dps/pdp/tools/lzp_system utility
  which is used to create filesystems and control the ISTP LZP system.
  Section 13 "System Environment" should be performed immediately
  after Section 3 "Build Environment".

  Sections 9 "DPS Database Creation" and 11 "RECON Database Creation"
  are only performed in the event of a full build, when there are
  no pre-existing database instances to be altered.  Sections 10
  "DPS Database Population" and 12 "RECON Database Population" may
  not be performed in their entirety.  It is strongly encouraged
  that the appointed database administrator be present to guide the
  CM team through sections 9, 10, 11, and 12 in order to prevent
  any time consuming mistakes.  As an alternative, it is strongly
  encouraged that the appointed database administrator actually
  perform these sections of the build instead of the CM team.

  The TREND subsystem has been obsoleted in release R1.0D, having
  been replaced with functionality on external systems.  Do not
  perform section 5 when building the LZP system after release R1.0C.

  Operation of the LZP system requires the IRTS frame synchronizer
  software which is delivered and installed independently of the LZP
  software.  Changes in IRTS frame synchronizer software may imply
  changes in configuration files which are under LZP code management.
  Also, changes in IRTS frame synchronizer software may imply changes
  in the lzpshow utility which is under LZP code management.

  In order to archive incoming data properly, the LZP system requires
  the RDA client software which is delivered and installed independently
  of the LZP software.  The RDA client software is a SUN COTS package.


*****************************************************************
 
  1.  S O F T W A R E   E X T R A C T I O N
  -------------------------------------------------------------
 
  OVERVIEW:
 
  The CM account on the archive host is used to extract
  the baselined software from the PVCS archives.  The
  code is compressed and prepared for transport to the
  runtime host.  A physical tape may be required.
 
  REQUIREMENTS:
 
  1.  CM account on archive host
  2.  PVCS account on archive host
  3.  150MB free disk space
  4.  150MB tape (optional)
  5.  45 minutes
 
  SOFTWARE:
 
  1.  PVCS: get, put, vcs, vlog
  2.  UNIX: tar, compress, uncompress
 
  NOTES:

  1.  The hidden files supplied with the installation
      scripts are NOT required, but optional.

  2.  FTP service may be used instead of physical tape.

*****************************************************************

Switch to the CM account on the ARCHIVE host
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

pluto% rlogin pacor.gsfc.nasa.gov -l cm
Last login: Fri Sep 19 11:06:38 from 150.144.200.60
Sun Microsystems Inc.   SunOS 5.5       Generic_103093-03

tools1:cm[/export/home/cm]41=> mkdir ISTP
tools1:cm[/export/home/cm]42=> mkdir ISTP/R1.4
tools1:cm[/export/home/cm]43=> cd ISTP/R1.4
tools1:cm[/export/home/cm/ISTP/R1.4]44=> ln -s /usr/pvcs/CM/sys/istp/vcs.inst vcs.cfg
tools1:cm[/export/home/cm/ISTP/R1.4]45=> setenv PROJECT istp
tools1:cm[/export/home/cm/ISTP/R1.4]46=> setenv SUBSYSTEM ad
tools1:cm[/export/home/cm/ISTP/R1.4]47=> get -w -VISTP_R1.4 "*,v"
tools1:cm[/export/home/cm/ISTP/R1.4]48=> chmod u+x *
chmod: WARNING: can't change vcs.cfg

tools1:cm[/export/home/cm/ISTP/R1.4]49=> ls -la
total 1034
drwxr-xr-x   7 cm       pvcs        1024 Dec 30 10:02 .
drwxr-xr-x   9 cm       pvcs         512 Dec 30 09:19 ..
-rw-r--r--   1 cm       pvcs        1710 Sep 18 16:27 .alias
-rw-r--r--   1 cm       pvcs        2941 Sep 18 16:28 .cshrc
-rw-r--r--   1 cm       pvcs        5398 Jun  3  1997 .dtprofile
-rw-r--r--   1 cm       pvcs         358 Nov  8  1996 .exrc
-rw-r--r--   1 cm       pvcs        1770 Sep 18 16:29 .login
-rwxr--r--   1 cm       pvcs        2735 Sep 18 19:01 Create_ISTP.ad
-rwxr--r--   1 cm       pvcs        5646 Sep 20 14:33 Create_ISTP.dps
-rwxr--r--   1 cm       pvcs        4575 Sep 18  1997 Create_ISTP.fs
-rwxr--r--   1 cm       pvcs        5180 Sep 18 19:01 Create_ISTP.recon
-rwxr--r--   1 cm       pvcs        3917 Sep 26 15:10 Create_ISTP.trend
-rwxr--r--   1 cm       pvcs        3115 Sep 20 15:28 Extract_ISTP.ad
-rwxr--r--   1 cm       pvcs       40672 Apr 10 07:45 Extract_ISTP.dps
-rwxr--r--   1 cm       pvcs        4076 Sep 20  1997 Extract_ISTP.fs
-rwxr--r--   1 cm       pvcs        5344 Oct  2 20:30 Extract_ISTP.recon
-rwxr--r--   1 cm       pvcs        3731 Sep 26 15:10 Extract_ISTP.trend
-rwxr--r--   1 cm       pvcs      115429 Apr 22 17:17 INSTRUCTIONS
-rwxr--r--   1 cm       pvcs       11783 Apr 22 17:02 Install_ISTP
-rwxr--r--   1 cm       pvcs        3134 Mar 17 21:37 ckin
-rwxr--r--   1 cm       pvcs        4686 Dec 30 09:18 label
lrwxrwxrwx   1 cm       pvcs          30 Dec 29 11:07 vcs.cfg -> /usr/pvcs/CM/sys/istp/vcs.inst

>>> The hidden files you have just extracted (e.g. ".cshrc") are supplied in
>>> order to provide an optional default working environment on most UNIX
>>> systems, however, they are NOT required.  If you do not have a working
>>> environment, you may choose to copy these hidden files to your home
>>> directory, logout, and login again in order to activate them now.  Don't
>>> forget to change directories back to ISTP/R1.4 before continuing...
 
tools1:cm[/export/home/cm/ISTP/R1.4]50=> Install_ISTP
 
 
 
============================================================
 
                Installing  ISTP  Software
 
============================================================
 
 
 
Create directory tree (Y/N)? Y
Enter full path of target tree (/export/home/cm/ISTP/R1.4): 
/export/home/cm/ISTP/R1.4
Enter subsystem (fs/ad/trend/recon/dps/all): all
Merge into existing tree (Y/N)? Y
Skipping fs...
Creating ad...
Skipping trend...
Creating recon...
Creating dps...
 
Creation complete
 
 
 
Create directory tree (Y/N)? n
 
 
 
Extract code from archives (Y/N)? Y
Enter full path of target tree (/export/home/cm/ISTP/R1.4): 
/export/home/cm/ISTP/R1.4
Enter subsystem (fs/ad/trend/recon/dps/all): all
Extract by promotion or version label (P/V)? V
Enter version label: ISTP_R1.4
Skipping fs...
Extracting ad...
Skipping trend...
Extracting recon...
Extracting dps...

.
.
.

Extracting dbxLib...
Extracting dbxInclude...
Extracting dbpLib...
Extracting xxxLib...
Linking shared files...
81.0u 65.0s 8:08 29% 0+0k 0+0io 0pf+0w
ERROR: extraction failed:  ad=4, recon=7,
 
>>> Expect to wait about 30 minutes for file extraction.
>>> Expect "ERROR: extraction failed:  ad=4, recon=7,"
>>> Any other errors would indicate a true failure.

 
 
Extract code from archives (Y/N)? n
 
 
 
Compress source code (Y/N)? n
 
 
 
Decompress source code (Y/N)? n
115.0u 145.0s 44:08 9% 0+0k 0+0io 0pf+0w

tools1:cm[/export/home/cm/ISTP/R1.4]51=> ls -la
total 1034
drwxr-xr-x   7 cm       pvcs        1024 Dec 30 10:02 .
drwxr-xr-x   9 cm       pvcs         512 Dec 30 09:19 ..
-rw-r--r--   1 cm       pvcs        1710 Sep 18 16:27 .alias
-rw-r--r--   1 cm       pvcs        2941 Sep 18 16:28 .cshrc
-rw-r--r--   1 cm       pvcs        5398 Jun  3  1997 .dtprofile
-rw-r--r--   1 cm       pvcs         358 Nov  8  1996 .exrc
-rw-r--r--   1 cm       pvcs        1770 Sep 18 16:29 .login
-rwxr--r--   1 cm       pvcs        2735 Sep 18 19:01 Create_ISTP.ad
-rwxr--r--   1 cm       pvcs        5646 Sep 20 14:33 Create_ISTP.dps
-rwxr--r--   1 cm       pvcs        4575 Sep 18  1997 Create_ISTP.fs
-rwxr--r--   1 cm       pvcs        5180 Sep 18 19:01 Create_ISTP.recon
-rwxr--r--   1 cm       pvcs        3917 Sep 26 15:10 Create_ISTP.trend
-rwxr--r--   1 cm       pvcs        3115 Sep 20 15:28 Extract_ISTP.ad
-rwxr--r--   1 cm       pvcs       40672 Apr 10 07:45 Extract_ISTP.dps
-rwxr--r--   1 cm       pvcs        4076 Sep 20  1997 Extract_ISTP.fs
-rwxr--r--   1 cm       pvcs        5344 Oct  2 20:30 Extract_ISTP.recon
-rwxr--r--   1 cm       pvcs        3731 Sep 26 15:10 Extract_ISTP.trend
-rwxr--r--   1 cm       pvcs      116168 Apr 22 17:17 INSTRUCTIONS
-rwxr--r--   1 cm       pvcs       11783 Apr 22 17:02 Install_ISTP
-rw-r--r--   1 cm       pvcs       33803 Apr 22 17:07 Logfile_ISTP.ad
-rw-r--r--   1 cm       pvcs      240119 Apr 22 17:17 Logfile_ISTP.dps
-rw-r--r--   1 cm       pvcs       52611 Apr 22 17:08 Logfile_ISTP.recon
drwxr-xr-x   8 cm       pvcs         512 Dec 30 09:22 ad
-rwxr--r--   1 cm       pvcs        3134 Mar 17 21:37 ckin
drwxr-xr-x  13 cm       pvcs         512 Dec 30 09:28 dps
-rwxr--r--   1 cm       pvcs        4686 Dec 30 09:18 label
drwxr-xr-x   7 cm       pvcs         512 Dec 30 09:22 recon
lrwxrwxrwx   1 cm       pvcs          30 Dec 29 11:07 vcs.cfg -> /usr/pvcs/CM/sys/istp/vcs.inst

>>> Examine the logfiles (e.g. "Logfile_ISTP.ad") for extraction errors.
>>> Expect "get: warning, version ISTP_R1.4 not found in archive" for obsolete units.
>>> Expect "get: error, no files match *,v" for empty directories.
 
tools1:cm[/export/home/cm/ISTP/R1.4]52=> grep -c 'get: warning, version' Logfile*
Logfile_ISTP.ad:35
Logfile_ISTP.dps:511
Logfile_ISTP.recon:104
 
tools1:cm[/export/home/cm/ISTP/R1.4]53=> grep -c 'get: error, no files match' Logfile*
Logfile_ISTP.ad:3
Logfile_ISTP.dps:34
Logfile_ISTP.recon:3

>>> A directory comparison tool is available in order to flag expected
>>> and unexpected differences between releases.  It may be invoked as
>>> follows (answer interactive prompts as needed):

tools1:cm[/export/home/cm/ISTP/R1.4]54=> dps/pdp/tools/diffdir

>>> Regardless of whether FTP service is available between the archive
>>> and runtime hosts, you should consolidate the "R1.4" directory into
>>> a single tar file at this time.  The following commands may be used,
>>> depending on whether the tar file will reside on tape or disk:
>>>
>>> TAPE:  cd ~/ISTP                 DISK:  cd ~/ISTP
>>>        tar cv R1.4                     tar cvf R1.4.tar R1.4

tools1:cm[/export/home/cm/ISTP/R1.4]55=> exit
tools1:cm[/export/home/cm/ISTP/R1.4]56=> logout
Connection closed.

*****************************************************************
 
  2.  S O F T W A R E   T R A N S P O R T
  -------------------------------------------------------------
 
  OVERVIEW:
 
  The CM account on the runtime host is used to receive
  the software from the archive host, either via binary FTP
  service or via physical tape.
 
  REQUIREMENTS:
 
  1.  CM account on archive host
  2.  CM account on runtime host
  3.  150MB free disk space
  4.  150MB tape
  5.  10 minutes
 
  SOFTWARE:
 
  1.  UNIX: tar, ftp, compress, uncompress
 
  NOTES:
 
  1.  FTP service may be used instead of physical tape
      in order to transport code from the archive host.
 
  2.  At least one tape is required in order to archive
      older builds to free up disk space for new builds.
 
*****************************************************************
 
Switch to the CM account on the RUNTIME host
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
 
pluto% rlogin ggslzp-1 -l cm
Last login: Fri Sep 19 16:45:38 from ggslzp-1
Sun Microsystems Inc.   SunOS 5.5.1     Generic May 1996

ggslzp-1:cm[/opt/cal/cm]55=> ll
total 1534
drwxr-xr-x   2 cm       dba          512 Dec  3 19:30 R1.0B
drwxr-xr-x   2 cm       dba          512 Dec  3 19:30 R1.0C

>>> Now make room on disk for the new build by purging the oldest
>>> build to tape.  Always keep the most recent build along with
>>> the new build in case the new build fails.  Load the default
>>> tape drive and issue:

ggslzp-1:cm[/opt/local/cm]56=> tar -cv R1.0B
ggslzp-1:cm[/opt/local/cm]57=> rm -rf R1.0B

>>> If FTP service is available between the archive and runtime
>>> hosts, you should get the tar file "R1.4.tar" from the
>>> archive host as binary data, placing it into the cm home
>>> directory:  (otherwise skip this subsection)

ggslzp-1:cm[/opt/local/cm]58=> cd
ggslzp-1:cm[/opt/local/cm]59=> ftp pacor.gsfc.nasa.gov
Connected to pacor.gsfc.nasa.gov.
220 tools1 FTP server (UNIX(r) System V Release 4.0) ready.
Name (pacor.gsfc.nasa.gov:cm): cm
331 Password required for cm.
Password:
230 User cm logged in.
ftp> cd ISTP
250 CWD command successful.
ftp> type binary
200 Type set to I.
ftp> get R1.4.tar
200 PORT command successful.
150 Binary data connection for R1.4.tar (150.144.200.60,35068) (75773440 bytes).
226 Binary Transfer complete.
local: R1.4.tar remote: R1.4.tar
75773440 bytes received in 1e+02 seconds (7.1e+02 Kbytes/s)
ftp> bye
221 Goodbye.
ggslzp-1:cm[/opt/local/cm]60=> tar xvf R1.4.tar
ggslzp-1:cm[/opt/local/cm]61=> rm R1.4.tar

>>> If FTP service is NOT available between the archive and
>>> runtime hosts, you should load the "R1.4" directory from
>>> physical tape at this time:  (otherwise skip this subsection)

ggslzp-1:cm[/opt/local/cm]58=> cd
ggslzp-1:cm[/opt/local/cm]59=> tar -xv
ggslzp-1:cm[/opt/local/cm]60=> exit
ggslzp-1:cm[/opt/local/cm]61=> logout
Connection closed.

*****************************************************************
 
  3.  B U I L D   E N V I R O N M E N T
  -------------------------------------------------------------
 
  OVERVIEW:

  The CM account on the runtime host is used to modify and
  verify the state of the build environment in preparation
  for the actual build.

  REQUIREMENTS:
 
  1.  CM account on runtime host
  2.  10 minutes
 
  SOFTWARE:
 
  1.  Any ASCII program text editor

  NOTES:
 
*****************************************************************
 
Switch to the CM account on the RUNTIME host
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
 
pluto% rlogin ggslzp-1 -l cm
Last login: Fri Sep 19 16:45:38 from ggslzp-1
Sun Microsystems Inc.   SunOS 5.5.1     Generic May 1996
 
ggslzp-1:cm[/opt/local/cm]55=> cd /opt/local/lzp/bin
ggslzp-1:cm[/opt/local/lzp/bin]56=> ls -la
total 28
drwxr-xr-x   5 cm       dba          512 Dec 31 14:36 .
drwxrwxr-x   3 root     root         512 Jun  6  1997 ..
-rwxr--r--   1 cm       dba         2876 Nov 11 11:27 dbalogin.sql
-rwxr-xr-x   1 cm       dba          903 Oct  2 12:43 dly_db_dump
-rwxr-xr-x   1 cm       dba         3317 Oct  2 16:18 dly_recon_imp
-rwxr-xr-x   1 cm       dba          322 Sep 17 18:07 dly_wind_exp
-rwxr-xr-x   1 cm       dba          416 Sep 17 18:07 dly_wind_imp
-rwxr-xr-x   1 cm       dba          782 Oct  1 18:29 full_db_dump
drwxr-xr-x   4 cm       dba          512 Oct  7 16:02 geotail
drwxr-xr-x   4 cm       dba          512 Oct  7 16:01 polar
drwxr-xr-x   4 cm       dba          512 Oct  7 16:00 wind

>>> Verify that the "/opt/local/lzp/bin" directory exists and that
>>> it has been created with ownership "cm", group "dba".  If the
>>> ownership and group are not set properly, contact the superuser
>>> in order to create the "/opt/local/lzp/bin" directory with
>>> ownership "cm", group "dba".

ggslzp-1:cm[/opt/local/cm]57=> cd
ggslzp-1:cm[/opt/local/cm]58=> ls -la
total 1652
drwxr-xr-x   7 cm       dba         1024 Dec  3 19:27 .
drwxr-xr-x  14 root     root         512 Nov 20 06:26 ..
-rw-------   1 cm       dba          249 Oct  6 19:16 .Xauthority
-rw-r--r--   1 cm       dba         2734 Oct 15 18:00 .alias
-rw-r--r--   1 cm       dba         3264 Oct  6 20:00 .cshrc
-rw-r--r--   1 cm       dba         2205 Oct  6 20:00 .dps_compile_info
-rw-r--r--   1 cm       dba         4854 Oct  6 20:00 .dps_user_env
drwx------  12 cm       dba          512 Oct  6 19:38 .dt
-rw-r--r--   1 cm       dba         5398 Oct  6 20:00 .dtprofile
-rw-r--r--   1 cm       dba          358 Oct  6 20:00 .exrc
-rw-------   1 cm       dba          389 Dec  3 19:40 .history
-rw-r--r--   1 cm       dba          466 Oct 20 19:23 .labviewrc
-rw-r--r--   1 cm       dba         3612 Oct  6 20:03 .login
-rw-r--r--   1 cm       dba          144 Oct  6 20:00 .profile
-rw-r--r--   1 cm       dba          790 Oct  6 20:00 .xsession
drwxr-xr-x   2 cm       dba         1024 Dec 30 19:30 R1.0C
drwxr-xr-x   2 cm       dba         1024 Dec 30 19:30 R1.4
 
>>> Verify that the "R1.4" directory exists and that it has been
>>> created with ownership "cm", group "dba".  If the ownership and
>>> group are not set properly, contact the superuser in order to
>>> default the CM account to ownership "cm", group "dba".  The CM
>>> and ORACLE accounts should share the ownership group "dba".
>>>
>>> The hidden files in the CM account home directory will now be
>>> overwritten with delivered units from the DPS subsystem and
>>> personalized for the newest build.  Be careful not to use the
>>> recursive option for the cp command.

ggslzp-1:cm[/opt/local/cm]56=> cd
ggslzp-1:cm[/opt/local/cm]57=> chmod u+w .*
chmod: WARNING: can't change ..
ggslzp-1:cm[/opt/local/cm]58=> cp -p R1.4/dps/pics/.* .
cp: R1.4/dps/pics/.: is a directory
cp: R1.4/dps/pics/..: is a directory

>>> Use an ASCII program text editor to personalize the ".login" file
>>> for the newest build.  The PACOR2HOME environment variable must
>>> be set to indicate the location of the DPS subsystem for this
>>> release.  Find the following lines:

#       The ISTP environment was automatically selected based on the
#       the current UNIX user id.  The following lines may be used
#       by developers in order to override the default settings:

#setenv ORACLE_SID NULL
#setenv PACOR2HOME /export/home/dev/dps1/current/dps

>>>
>>> Modify the above lines, uncommenting the setenv commands, to read:
>>>

#       The ISTP environment was automatically selected based on the
#       the current UNIX user id.  The following lines may be used
#       by developers in order to override the default settings:
   
setenv ORACLE_SID NULL
setenv PACOR2HOME /opt/local/cm/R1.4/dps
   
>>> The C-Shell environment is determined both by the system default,
>>> as well as the hidden files supplied with the DPS subsystem.
>>> Software behaviour will depend strongly on this environment.
>>> Manually source the ".login" and ".cshrc" files to activate the
>>> new build environment.  No errors or warnings are expected.

ggslzp-1:cm[/opt/local/cm]59=> source .login

Generic ISTP maintenance environment

ggslzp-1:cm[/opt/local/cm]60=> source .cshrc
Please edit .mycshrc to personalize your environment.
Please do NOT modify the .cshrc and .alias files.

>>> Touch or edit the .mycshrc file to quiet the messages shown above.
>>> Note that if you are using multiple login shells or windows,
>>> you will have to source the ".login" and ".cshrc" in each such
>>> shell individually, or the new environment will not take effect.
>>> Another way to do this is to logout and then login again.

ggslzp-1:cm[/opt/local/cm]61=> exit
ggslzp-1:cm[/opt/local/cm]62=> logout
Connection closed.

*****************************************************************
 
  4.  A D   S O F T W A R E   B U I L D
  -------------------------------------------------------------
 
  OVERVIEW:
 
  The AD software executables are dynamically compiled
  binary files associated with the LabView software package
  from National Instruments.  The only executables to be
  built are embedded shell scripts which will be created as
  part of the MISSION OPS ENVIRONMENT section later on.
  However, the delivered executables occasionally need to
  be relinked.  Linking is performed automatically when
  the executable is invoked, causing minor changes which
  should be saved in order to prevent relinking again.
 
  REQUIREMENTS:
 
  1.  CM account on runtime host
  2.  1MB free disk space per mission
  3.  5 minutes per mission
 
  SOFTWARE:
 
  1.  Any ASCII program text editor
  2.  Solaris Operating System
  3.  LabView G compiler/interpreter
 
  NOTES:

*****************************************************************

Switch to the CM account on the RUNTIME host
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
 
pluto% rlogin ggslzp-1 -l cm
Last login: Fri Sep 19 16:45:38 from ggslzp-1
Sun Microsystems Inc.   SunOS 5.5.1     Generic May 1996
 
Generic ISTP maintenance environment
 
ggslzp-1:cm[/opt/local/cm]55=> cd R1.4/ad
ggslzp-1:cm[/opt/local/cm/R1.4/ad]56=> ll
total 24
drwxr-xr-x   2 cm       dba         6656 Dec 30 14:41 common
drwxr-xr-x   2 cm       dba          512 Dec 30 14:41 config
drwxr-xr-x   2 cm       dba          512 Dec 30 14:22 geotail
drwxr-xr-x   2 cm       dba          512 Dec 30 14:41 help
drwxr-xr-x   2 cm       dba          512 Dec 30 14:22 polar
drwxr-xr-x   2 cm       dba          512 Dec 30 14:22 wind

>>> Relink the ad executables as shown in the following examples.
>>> Dialog boxes may appear which prompt you to find various files.
>>> All files should be found under one of the various "R1.4/ad"
>>> subdirectories.  Do not use any other files.  Once linking is
>>> completed, save the executables by selecting (from the upper
>>> left hand corner) "File", "Quit".  A dialog box should appear
>>> prompting you whether or not to save the changes.  Select the
>>> "Yes to all" option in order to save all the changes.

ggslzp-1:cm[/opt/local/cm/R1.4/ad]57=> cd common
ggslzp-1:cm[/opt/local/cm/R1.4/ad/common]58=> labview Assembly_Decom.vi &
ggslzp-1:cm[/opt/local/cm/R1.4/ad/common]59=> labview control_quality_rank.vi &
ggslzp-1:cm[/opt/local/cm/R1.4/ad/common]60=> labview make_station_table.vi &
ggslzp-1:cm[/opt/local/cm/R1.4/ad/common]61=> labview Monitor_cs_state_report.vi &
ggslzp-1:cm[/opt/local/cm/R1.4/ad/common]62=> labview Monitor_system_state.vi &
ggslzp-1:cm[/opt/local/cm/R1.4/ad/common]63=> labview ProductDifferenceTools.vi &
ggslzp-1:cm[/opt/local/cm/R1.4/ad/common]64=> labview recon_util_menu.vi &
ggslzp-1:cm[/opt/local/cm/R1.4/ad/common]65=> labview rules_control.vi &
ggslzp-1:cm[/opt/local/cm/R1.4/ad/common]66=> labview States_Description.vi &
ggslzp-1:cm[/opt/local/cm/R1.4/ad/common]67=> labview Tables_Descriptions.vi &
ggslzp-1:cm[/opt/local/cm/R1.4/ad/common]68=> labview TTCDmain.vi &
ggslzp-1:cm[/opt/local/cm/R1.4/ad/common]68=> labview TTCD_value_plot.vi &
ggslzp-1:cm[/opt/local/cm/R1.4/ad/common]68=> labview TTCD_estimate_check.vi &
ggslzp-1:cm[/opt/local/cm/R1.4/ad/common]68=> labview amf_filter_duplicate_mnfs.vi &
ggslzp-1:cm[/opt/local/cm/R1.4/ad/common]68=> labview QLdup.vi &
ggslzp-1:cm[/opt/local/cm/R1.4/ad/common]69=> exit
ggslzp-1:cm[/opt/local/cm/R1.4/ad/common]70=> logout
Connection closed.

*****************************************************************
 
  5.  T R E N D   S O F T W A R E   B U I L D
  -------------------------------------------------------------
 
  OVERVIEW:
 
  The TREND software executables are dynamically compiled
  binary files associated with the LabView software package
  from National Instruments.  The only executables to be
  built are embedded shell scripts which will be created as
  part of the MISSION OPS ENVIRONMENT section later on.
  However, the delivered executables occasionally need to
  be relinked.  Linking is performed automatically when
  the executable is invoked, causing minor changes which
  should be saved in order to prevent relinking again.
 
  REQUIREMENTS:
 
  1.  CM account on runtime host
  2.  1MB free disk space per mission
  3.  5 minutes per mission
 
  SOFTWARE:
 
  1.  Any ASCII program text editor
  2.  Solaris Operating System
  3.  LabView G compiler/interpreter
 
  NOTES:

  The TREND software has been obsoleted in release R1.4,
  having been functionally replaced by processes external
  to the LZP system.  Data is forwarded to these external
  processes via cron jobs using the lzp_trend script which
  uses binary FTP service to transmit data.
 
*****************************************************************

Switch to the CM account on the RUNTIME host
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
 
pluto% rlogin ggslzp-1 -l cm
Last login: Fri Sep 19 16:45:38 from ggslzp-1
Sun Microsystems Inc.   SunOS 5.5.1     Generic May 1996
 
Generic ISTP maintenance environment
 
ggslzp-1:cm[/opt/local/cm]55=> cd R1.4/trend
ggslzp-1:cm[/opt/local/cm/R1.4/trend]56=> ll
total 12
drwxr-xr-x   4 cm       dba          512 Dec 30 14:22 common
drwxr-xr-x   2 cm       dba          512 Dec 30 14:22 config
drwxr-xr-x   4 cm       dba          512 Dec 30 14:22 geotail
drwxr-xr-x   2 cm       dba          512 Dec 30 14:22 help
drwxr-xr-x   4 cm       dba          512 Dec 30 14:22 polar
drwxr-xr-x   4 cm       dba          512 Dec 30 14:22 wind
 
>>> Relink the trend executables as shown in the following examples.
>>> Dialog boxes may appear which prompt you to find various files.
>>> All files should be found under one of the various "R1.0C/trend"
>>> subdirectories.  Do not use any other files.  Once linking is
>>> completed, save the executables by selecting (from the upper
>>> left hand corner) "File", "Quit".  A dialog box should appear
>>> prompting you whether or not to save the changes.  Select the
>>> "Yes to all" option in order to save all the changes.

ggslzp-1:cm[/opt/local/cm/R1.4/trend]57=> exit
ggslzp-1:cm[/opt/local/cm/R1.4/trend]58=> logout
Connection closed.

*****************************************************************
 
  6.  F S   S O F T W A R E   B U I L D
  -------------------------------------------------------------
 
  OVERVIEW:
 
  The CM account on the runtime host is used to build the
  FS software executables and install them into operations.
 
  REQUIREMENTS:
 
  1.  CM account on runtime host
  2.  2MB free disk space
  3.  10 minutes
 
  SOFTWARE:
 
  1.  Any ASCII program text editor
  2.  Solaris Operating System
  3.  SunWSpro C compiler
  4.  IRTS frame synchronizer

 
  NOTES:

  As of release ISTP_R1.0B, the frame synchronizer software
  is delivered separatly as a part of the ISTP Real-Time System.
  The legacy FS subsystem directory tree and configuration files
  are retained for compatibility with the LZP system.  The ISTP
  LZPR software expects the IRTS software to be installed in the
  /opt/irts directory.  Changes to IRTS software may impact
  mission specific configuration files located in the mission
  config directories, as well as the lzpshow script which parses
  the log files generated by the IRTS sw_sync executable.
 
*****************************************************************

Switch to the CM account on the RUNTIME host
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
 
pluto% rlogin ggslzp-1 -l cm
Last login: Fri Sep 19 16:45:38 from ggslzp-1
Sun Microsystems Inc.   SunOS 5.5.1     Generic May 1996
 
Generic ISTP maintenance environment

ggslzp-1:cm[/opt/local/cm]55=> cd /opt/irts/bin
ggslzp-1:cm[/opt/local/cm/R1.4/fs]56=> ll
total 1298
-rwxr-xr-x   1 root     other       1916 Apr 15 16:07 irts_logs
-rwxr-xr-x   1 root     other      30976 Apr 15 16:07 istp_cdr
lrwxrwxrwx   1 root     other         21 Apr 15 16:07 lzpSTR_FP -> /opt/irts/bin/lzpscan
lrwxrwxrwx   1 root     other         21 Apr 15 16:07 lzpdiff -> /opt/irts/bin/lzpscan
lrwxrwxrwx   1 root     other         21 Apr 15 16:07 lzpedit -> /opt/irts/bin/lzpscan
lrwxrwxrwx   1 root     other         21 Apr 15 16:07 lzpprod -> /opt/irts/bin/lzpscan
-rwxr-xr-x   1 root     other     185310 Apr 15 16:07 lzpscan
-rwxr-xr-x   1 root     other     196051 Apr 15 16:07 scan
lrwxrwxrwx   1 root     other         18 Apr 15 16:07 scanSTR_FP -> /opt/irts/bin/scan
lrwxrwxrwx   1 root     other         18 Apr 15 16:07 scandiff -> /opt/irts/bin/scan
lrwxrwxrwx   1 root     other         18 Apr 15 16:07 scanedit -> /opt/irts/bin/scan
lrwxrwxrwx   1 root     other         18 Apr 15 16:07 scanprod -> /opt/irts/bin/scan
-rwxr-xr-x   1 root     other      29246 Apr 15 16:07 shm_dump
-rwxr-xr-x   1 root     other     176796 Apr 15 16:07 sw_sync
-rwxr-xr-x   1 root     other       3005 Apr 15 16:07 tcp_parms

>>> Verify that the lzpscan, scan, and sw_sync executables are
>>> present.  Other files are not important since they will not
>>> be used by the LZP runtime system.

ggslzp-1:cm[/opt/local/cm]57=> cd /opt/irts/etc
ggslzp-1:cm[/opt/local/cm/R1.4/fs]58=> ll
total 408
-r--r--r--   1 root     other       1765 Apr 15 16:07 CDHF_RT_POLAR.cfg
-r--r--r--   1 root     other       1762 Apr 15 16:07 CDHF_RT_WIND.cfg
-r--r--r--   1 root     other       1757 Apr 15 16:07 GEOTAIL_AG.cfg
-r--r--r--   1 root     other       1758 Apr 15 16:07 GEOTAIL_AI.cfg
-r--r--r--   1 root     other       1757 Apr 15 16:07 GEOTAIL_BG.cfg
-r--r--r--   1 root     other       1758 Apr 15 16:07 GEOTAIL_BI.cfg
-r--r--r--   1 root     other       1830 Apr 15 16:07 GEOTAIL_CG.cfg
-r--r--r--   1 root     other       1831 Apr 15 16:07 GEOTAIL_CI.cfg
-r--r--r--   1 root     other       1831 Apr 15 16:07 GEOTAIL_DG.cfg
-r--r--r--   1 root     other       1832 Apr 15 16:07 GEOTAIL_DI.cfg
-r--r--r--   1 root     other       1293 Apr 15 16:07 POCC_FRFILE_SOHO.cfg
-r--r--r--   1 root     other       2102 Apr 15 16:07 POCC_MD_SOHO.cfg
-r--r--r--   1 root     other       1721 Apr 15 16:07 POCC_PBFILE_GEOTAIL.cfg
-r--r--r--   1 root     other       1920 Apr 15 16:07 POCC_PBFILE_POLAR.cfg
-r--r--r--   1 root     other       1916 Apr 15 16:07 POCC_PBFILE_WIND.cfg
-r--r--r--   1 root     other       1784 Apr 15 16:07 POCC_PBHIST_POLAR.cfg
-r--r--r--   1 root     other       1780 Apr 15 16:07 POCC_PBHIST_WIND.cfg
-r--r--r--   1 root     other       1729 Apr 15 16:07 POCC_PB_GEOTAIL.cfg
-r--r--r--   1 root     other       1862 Apr 15 16:07 POCC_PB_POLAR.cfg
-r--r--r--   1 root     other       2170 Apr 15 16:07 POCC_PB_SOHO.cfg
-r--r--r--   1 root     other       1859 Apr 15 16:07 POCC_PB_WIND.cfg
-r--r--r--   1 root     other       1919 Apr 15 16:07 POCC_RTFILE_POLAR.cfg
-r--r--r--   1 root     other       1916 Apr 15 16:07 POCC_RTFILE_WIND.cfg
-r--r--r--   1 root     other       1783 Apr 15 16:07 POCC_RTHIST_POLAR.cfg
-r--r--r--   1 root     other       1780 Apr 15 16:07 POCC_RTHIST_WIND.cfg
-r--r--r--   1 root     other       1852 Apr 15 16:07 POCC_RT_POLAR.cfg
-r--r--r--   1 root     other       2103 Apr 15 16:07 POCC_RT_SOHO.cfg
-r--r--r--   1 root     other       1849 Apr 15 16:07 POCC_RT_WIND.cfg
-r--r--r--   1 root     other       1893 Apr 15 16:07 POLAR_AG.cfg
-r--r--r--   1 root     other       1894 Apr 15 16:07 POLAR_AI.cfg
-r--r--r--   1 root     other       1893 Apr 15 16:07 POLAR_BG.cfg
-r--r--r--   1 root     other       1894 Apr 15 16:07 POLAR_BI.cfg
-r--r--r--   1 root     other       1895 Apr 15 16:07 POLAR_CG.cfg
-r--r--r--   1 root     other       1896 Apr 15 16:07 POLAR_CI.cfg
-r--r--r--   1 root     other       1895 Apr 15 16:07 POLAR_DG.cfg
-r--r--r--   1 root     other       1896 Apr 15 16:07 POLAR_DI.cfg
-r--r--r--   1 root     other       1957 Apr 15 16:07 POLAR_GG.cfg
-r--r--r--   1 root     other       1958 Apr 15 16:07 POLAR_GI.cfg
-r--r--r--   1 root     other       1901 Apr 15 16:07 POLAR_PBHIST.cfg
-r--r--r--   1 root     other       1900 Apr 15 16:07 POLAR_RTHIST.cfg
-r--r--r--   1 root     other       1810 Apr 15 16:07 SOHO_MD.cfg
-r--r--r--   1 root     other       2071 Apr 15 16:07 SOHO_MDHIST.cfg
-r--r--r--   1 root     other       2060 Apr 15 16:07 SOHO_MDIDR.cfg
-r--r--r--   1 root     other       2218 Apr 15 16:07 SOHO_PBHIST.cfg
-r--r--r--   1 root     other       2286 Apr 15 16:07 SOHO_PBIDR.cfg
-r--r--r--   1 root     other       1280 Apr 15 16:07 SOHO_REV.cfg
-r--r--r--   1 root     other       2053 Apr 15 16:07 SOHO_RR.cfg
-r--r--r--   1 root     other       2153 Apr 15 16:07 SOHO_RTHIST.cfg
-r--r--r--   1 root     other       2227 Apr 15 16:07 SOHO_RTIDR.cfg
-r--r--r--   1 root     other       1890 Apr 15 16:07 WIND_AG.cfg
-r--r--r--   1 root     other       1891 Apr 15 16:07 WIND_AI.cfg
-r--r--r--   1 root     other       1890 Apr 15 16:07 WIND_BG.cfg
-r--r--r--   1 root     other       1891 Apr 15 16:07 WIND_BI.cfg
-r--r--r--   1 root     other       1891 Apr 15 16:07 WIND_CG.cfg
-r--r--r--   1 root     other       1892 Apr 15 16:07 WIND_CI.cfg
-r--r--r--   1 root     other       1891 Apr 15 16:07 WIND_DG.cfg
-r--r--r--   1 root     other       1892 Apr 15 16:07 WIND_DI.cfg
-r--r--r--   1 root     other       1891 Apr 15 16:07 WIND_EG.cfg
-r--r--r--   1 root     other       1892 Apr 15 16:07 WIND_EI.cfg
-r--r--r--   1 root     other       1892 Apr 15 16:07 WIND_FG.cfg
-r--r--r--   1 root     other       1893 Apr 15 16:07 WIND_FI.cfg
-r--r--r--   1 root     other       1897 Apr 15 16:07 WIND_PBHIST.cfg
-r--r--r--   1 root     other       1897 Apr 15 16:07 WIND_RTHIST.cfg
-rw-r--r--   1 root     other       1635 Apr 15 16:07 codes.dsid
-rw-r--r--   1 root     other        618 Apr 15 16:07 codes.sat
-rw-r--r--   1 root     other      12842 Apr 15 16:07 codes.src
-rw-r--r--   1 root     other         15 Apr 15 16:07 gf16.gft
-rw-r--r--   1 root     other        255 Apr 15 16:07 gf256.gft
-rw-r--r--   1 root     other        255 Apr 15 16:07 gf256d.gft
-rw-r--r--   1 root     other       5802 Apr 15 16:07 ginetd.conf
-r--r--r--   1 root     other       6479 Apr 15 16:07 mss_fe.dat
-r--r--r--   1 root     other       6482 Apr 15 16:07 mss_table.dat
-rw-r--r--   1 root     other       8642 Apr 15 16:07 pinetd.conf
-rw-r--r--   1 root     other      11229 Apr 15 16:07 sinetd.conf
-rw-r--r--   1 root     other       8602 Apr 15 16:07 winetd.conf

>>> Verify that all of the WIND, POLAR, and GEOTAIL configuration
>>> files are present.  Other files are not important since they
>>> will not be used by the LZP runtime system.

ggslzp-1:cm[/opt/local/cm/R1.4/fs]59=> exit
ggslzp-1:cm[/opt/local/cm/R1.4/fs]60=> logout
Connection closed.

*****************************************************************
 
  7.  D P S   S O F T W A R E   B U I L D
  -------------------------------------------------------------
 
  OVERVIEW:
 
  The CM account on the runtime host is used to build the DPS
  software executables and link them into the operational
  environment.  The build script will require knowledge of
  of the DPS software database user/password/encryption key
  combinations for each database instance.
 
  REQUIREMENTS:
 
  1.  CM account on runtime host
  2.  100MB free disk space
  3.  40 minutes
 
  SOFTWARE:
 
  1.  Any ASCII program text editor
  2.  Solaris Operating System
  3.  Oracle with Pro*C compiler
  4.  X/Motif with Software Development Kit
  5.  SunWSpro C compiler
 
  NOTES:

  1.  The database user is identical to the database installation
      account (username) which must be "dpsuser" for all database instances.
 
  2.  The database password is identical to the database installation
      account password which should vary for different database instances.
 
  3.  The encryption key is a predefined constant.
 
*****************************************************************
 
Switch to the CM account on the RUNTIME host
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
 
pluto% rlogin ggslzp-1 -l cm
Last login: Fri Sep 19 16:45:38 from ggslzp-1
Sun Microsystems Inc.   SunOS 5.5.1     Generic May 1996
 
Generic ISTP maintenance environment
 
>>> Execute the DPS software build script once in order to build the
>>> DPS software executables which will be shared by all missions.
>>> Start a script file to capture screen output since the build
>>> script does not create its own error log.
 
ggslzp-1:cm[/opt/local/cm]55=> cd R1.4/dps
ggslzp-1:cm[/opt/local/cm/R1.4/dps]56=> script dps_build.log
Script started, file is dps_build.log
ggslzp-1:cm[/opt/local/cm/R1.4/dps]57=> Build_ISTP.dps
 
Generic ISTP maintenance environment
 

 
 
 
============================================================
 
                 Building ISTP dps subsystem
 
============================================================
 
 
 
Enter mission (common/wind/polar/geotail): common
 
Enter baseline path (/opt/local/cm/current/dps):
/opt/local/cm/R1.4/dps

Enter operations path (/opt/local/lzp/bin):
/opt/local/lzp/bin

Building /opt/local/cm/R1.4/dps
Build baseline executables (Y/N)? Y

.
.
.

Build completed.

Linking /opt/local/lzp/bin/common -> /opt/local/cm/R1.4/dps
Reset operations links (Y/N)? n
 
ggslzp-1:cm[/opt/local/cm/R1.4/dps]58=> exit
ggslzp-1:cm[/opt/local/cm/R1.4/dps]59=> Script done, file is dps_build.log

>>> Examine the script file "dps_build.log" for unexpected errors...
>>>
>>> Expect "warning: macro redefined: NULL"
>>> Expect "warning: argument is incompatible with prototype"
>>> Expect "xxx_db_PutEventLog.c, line 2315: warning: argument #1 is incompatible"
>>> Expect "pei_Main.c, line 396: warning: statement not reached"
>>> Expect "pcgp_ReformatPWIW.c, line 480: warning: statement not reached"
>>> Expect "make: Fatal error: Don't know how to make target clean"
>>> Expect "activityDetail.c, line 157: warning: initialization type mismatch"
>>> Expect "dpsMain.c, line 154: warning: initialization type mismatch"
>>> Expect "eventListCallbacks.c, line 362: warning: argument #2 is incompatible"
>>> Expect "eventListFilter.c, line 1202: warning: assignment type mismatch"
>>> Expect "pdpsDataMaintCallbacks.c, line 2218: warning: argument #2 is incompatible"
>>> Expect "pdpsDataMaintCallbacks.c, line 2375: warning: argument #2 is incompatible"
>>> Expect "pdpsDataMaintTape.c, line 269: warning: argument #1 is incompatible"
>>> Expect "productGapsFilter.c, line 875: warning: assignment type mismatch"
>>> Expect "productListFilter.c, line 937: warning: assignment type mismatch"
>>> Expect "productSpecListFilter.c, line 759: warning: assignment type mismatch"
>>> Expect "sessionListFilter.c, line 1004: warning: assignment type mismatch"
>>> Expect "sessionMonitor.c, line 621: warning: initialization type mismatch"

ggslzp-1:cm[/opt/local/cm/R1.4/dps]60=> exit
ggslzp-1:cm[/opt/local/cm/R1.4/dps]61=> logout
Connection closed.

*****************************************************************
 
  8.  C O N T R O L L E D   S H U T D O W N
  -------------------------------------------------------------
 
  OVERVIEW:
 
  The CM team decides whether or not to continue the newest
  build past the point of no return, based on their confidence
  in the build so far.  This is the point of no return since
  all operations activities must be halted while the existing
  database instance and mission operations environment is
  archived and subsequently altered.  It may or may not be
  possible to rollback these changes in varying degrees.
 
  REQUIREMENTS:
 
  1.  CM account on runtime host
  2.  ORACLE account on runtime host
  3.  MISSION account on runtime host
  4.  SYS database account password
  5.  30 minutes per database instance
 
  SOFTWARE:
 
  1.  Solaris Operating System
  2.  Oracle with Pro*C compiler
 
  NOTES:
 
  Please be especially careful that you read the instructions
  completely and think before you issue your commands.  While
  logged in using the ORACLE account you are almost SUPERUSER.
  This means you can kill large portions of the system without
  even trying.  Get any other tasks you may have pending out
  of the way before starting this section so that you can give
  the build your full and undivided attention.  Thank you.

  The ISTP re-engineered LZP system assumes the existence of nine
  software database instances;  three for mission operations, three
  for testing, and three for development.  Each host is configured
  to support a maximum of four database instances at a time.  This
  requires the fine tuning of several global system resources.  Most
  important is the virtual memory system for which we recommend at
  least 300M real and 500M swap memory.  Several kernal shared
  memory parameters must also be configured.

  There are nine dedicated mission accounts;  three for mission
  operations, three for mission testing, and three for software
  development.  Database instances are distinguished by both the
  database instance name as well as the host machine name.  It
  is extremely important that you use the proper machine to build
  each mission user environment:
 
  Mission User   Environment   Runtime Host   Instance Name
  ------------   -----------   ------------   -------------
  wind           OPS           ggslzp-1       WIND
  polar          OPS           ggslzp-2       POLAR
  geotail        OPS           ggslzp-1       GEOTAIL
 
  wind           TEST          ggslzp-3       WIND
  polar          TEST          ggslzp-3       POLAR
  geotail        TEST          ggslzp-3       GEOTAIL
 
  winddev        DEV           ggslzp-3       WINDDEV
  polardev       DEV           ggslzp-3       POLARDEV
  geodev         DEV           ggslzp-3       GEODEV

  A particular database instance is selected by logging in to the
  proper host and setting the ORACLE_SID environment variable in
  the current shell.  Use extreme caution to ensure that you have
  selected the proper database instance on the proper host or you
  will suffer a severe loss of data.  The software is extremely
  sensitive to the instance names.  Do not change any of these
  predefined instance names.

*****************************************************************

The OPS team uses the MISSION account to stop the LZP system
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

pluto% rlogin ggslzp-1 -l wind
Last login: Fri Sep 19 16:45:38 from ggslzp-1
Sun Microsystems Inc.   SunOS 5.5.1     Generic May 1996

Welcome to WIND mission operations
 
ggslzp-1:wind[/wind/ops]51=> lzp_system stop wind

Stopping Level Zero Processor for wind on ggslzp-1
----------------------------------------------------------------
Waiting for semaphore...
Stopping IDF subsystem
Stopping PTT subsystem
Stopping PEP subsystem
Stopping PDP subsystem
Stopping GUI subsystem
Stopping A/D subsystem
Level Zero Processor is stopped
Level Zero Processor in manual mode

ggslzp-1:wind[/wind/ops]52=> crontab -r wind

>>> Now that all software processes have been stopped,
>>> exit all SQL shells, command shells, DPS windows, etc.
>>> in order to stop all human initiated processes.

ggslzp-1:wind[/wind/ops]53=> exit
ggslzp-1:wind[/wind/ops]54=> logout
Connection closed.
 
Switch to the ORACLE account on the RUNTIME host
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

pluto% rlogin ggslzp-1 -l oracle
Last login: Fri Sep 19 16:45:38 from ggslzp-1
Sun Microsystems Inc.   SunOS 5.5.1     Generic May 1996

!!! DANGER !!! WARNING !!! DANGER !!! WARNING !!! DANGER !!!
 
>>> Remember that you are SUPERUSER now as far as oracle is concerned.
>>> ALWAYS specify the database instance to be altered by setting the
>>> ORACLE_SID environment variable to indicate the proper database
>>> instance name.  If you forget to do this or do it wrong, you might
>>> destroy somebody's database.  Do this EACH and EVERY time you wish
>>> to reference the database within the scope of this software build.
>>> ALWAYS verify that you have selected the correct database instance
>>> by echoing it back to your screen.
 
!!! DANGER !!! WARNING !!! DANGER !!! WARNING !!! DANGER !!!

>>> The hidden files in the ORACLE account home directory will now be
>>> overwritten by units copied from the CM account DPS subsystem.
>>> Be careful not to use the recursive option for the cp command.
 
ggslzp-1:oracle[/oracle/app/oracle/product/7.3.2]47=> cd
ggslzp-1:oracle[/oracle/app/oracle/product/7.3.2]48=> chmod u+w .*
chmod: WARNING: can't change ..
ggslzp-1:oracle[/oracle/app/oracle/product/7.3.2]49=> cp -p ~cm/R1.4/dps/pics/.* .
cp: /opt/local/cm/R1.2/dps/pics/.: is a directory
cp: /opt/local/cm/R1.2/dps/pics/..: is a directory
ggslzp-1:oracle[/oracle/app/oracle/product/7.3.2]50=> cp -p ~cm/.login .

>>> The C-Shell environment is determined both by the system default,
>>> as well as the hidden files supplied with the DPS subsystem.
>>> Software behaviour will depend strongly on this environment.
>>> Manually source the ".login" and ".cshrc" files to activate the
>>> new build environment.  No errors or warnings are expected.

ggslzp-1:oracle[/oracle/app/oracle/product/7.3.2]51=> source .login
 
Generic ISTP maintenance environment
 
ggslzp-1:oracle[/oracle/app/oracle/product/7.3.2]52=> source .cshrc
Please edit .mycshrc to personalize your environment.
Please do NOT modify the .cshrc and .alias files.
 
>>> Touch or edit the .mycshrc file to quiet the messages shown above.
>>> Note that if you are using multiple login shells or windows,
>>> you will have to source the ".login" and ".cshrc" in each such
>>> shell individually, or the new environment will not take effect.
>>> Another way to do this is to logout and then login again.
>>>
>>> In this example the OPS WIND mission will be rebuilt.  Thus,
>>> the build must take place on ggslzp-1 and the ORACLE_SID
>>> environment variable must be set to WIND.

ggslzp-1:oracle[/oracle/app/oracle/product/7.3.2]53=> setenv ORACLE_SID WIND
ggslzp-1:oracle[/oracle/app/oracle/product/7.3.2]54=> echo $ORACLE_SID
WIND
 
>>> You will be using the ORACLE supplied database export utility.
>>> Since the export backup files may be extremely large, please do
>>> not attempt to locate them on any of the local disks.  Instead,
>>> locate them on one of the following RAID backup directories:
>>>
>>> Instance Name   RAID Backup Directory
>>> -------------   ---------------------
>>> WIND            /wind/ops/oracle
>>> POLAR           /polar/ops/oracle
>>> GEOTAIL         /geotail/ops/oracle
>>>
>>> WINDDEV         /wind/dev/oracle
>>> POLARDEV        /polar/dev/oracle
>>> GEODEV          /geotail/dev/oracle
>>>
>>> Verify that each backup directory exists and that it has been
>>> created with ownership "oracle", group "dba".  If the ownership
>>> and group are not set properly, contact the superuser in order
>>> to create the backup directory for owner "oracle", group "dba".

ggslzp-1:oracle[/oracle/app/oracle/product/7.3.2]55=> cd /wind/ops/oracle
ggslzp-1:oracle[/wind/ops/oracle]56=> lsla
total 60868
drwxr-xr-x   2 oracle   dba          512 Mar 19 18:26 .
drwxr-xr-x  21 wind     wind        1024 Apr 23 18:27 ..
-rw-r--r--   1 oracle   dba      31134720 Mar 19 18:30 WIND_full_export.dmp

>>> Verify that the mission user account and software have been
>>> shutdown.  The mission user account, software, and activities
>>> must be shutdown before the database can be rebuilt.  Use the
>>> lzp_system backup command to verify that the software is in
>>> a reasonably quiescent state:

ggslzp-1:oracle[/oracle/app/oracle/product/7.3.2]56=> \
/opt/local/cm/R1.4/dps/pdp/tools/lzp_system backup wind

Executing backup for wind on ggslzp-1
----------------------------------------------------------------
Checking for active processes

    USER   PID COMMAND
    wind  1891 oracleWIND
    wind  1841 oracleWIND
    wind  1849 oracleWIND
    wind  1830 oracleWIND
    wind  1866 oracleWIND
    wind  1854 oracleWIND
    wind  1880 oracleWIND
    wind  1858 oracleWIND
    wind  1873 oracleWIND

WARNING:  Backup may be incomplete
Proceed with backup now (y/n)? y

Copying config directory
Copying home directory
Exporting database objects
exp full=y userid=sys file=/wind/ops/oracle/WIND_1998May11_071231_full.dmp

Export: Release 7.3.3.0.0 - Production on Mon May 11 07:12:35 1998

Copyright (c) Oracle Corporation 1979, 1996.  All rights reserved.

Password: 

>>> If any activity is found, as with the wind account shown above,
>>> contact the operations, testing, or development staff in order
>>> to shutdown the offending processes.  The system must be in a
>>> quiescent state for the backup to be as reliable as possible.
>>>
>>> Do not continue the build until all backups have been performed
>>> without errors.  Keep these files online for now, but plan to
>>> archive them to tape and remove them within a few days.

ggslzp-1:oracle[/wind/ops/oracle]57=> exit
ggslzp-1:oracle[/wind/ops/oracle]58=> logout
Connection closed.

*****************************************************************

  9.  D P S   D A T A B A S E   C R E A T I O N
  -------------------------------------------------------------
 
  OVERVIEW:
 
  You may skip this section if the mission database instance
  already exists.  This section is performed only when creating
  a mission database instance for the first time.

  The CM and ORACLE accounts on the runtime host are used to
  create the DPS software database for a particular mission.
  It may be desirable to archive any existing database instances
  before deleting them.  Oracle's standard import/export utilities
  are available for this purpose.

  REQUIREMENTS:
 
  1.  CM account on runtime host
  2.  ORACLE account on runtime host
  3.  Knowledge of overall filesystem structure
  4.  2GB disk space, 60 minutes per small instance
  5.  9GB disk space, 120 minutes per large instance
 
  SOFTWARE:
 
  1.  Solaris Operating System
  2.  Oracle with Pro*C compiler
 
  NOTES:

  Please be especially careful that you read the instructions
  completely and think before you issue your commands.  While
  logged in using the ORACLE account you are almost SUPERUSER.
  This means you can kill large portions of the system without
  even trying.  Get any other tasks you may have pending out
  of the way before starting this section so that you can give
  the build your full and undivided attention.  Thank you.
 
  The ISTP re-engineered LZP system assumes the existence of nine
  software database instances;  three for mission operations, three
  for testing, and three for development.  Each host is configured
  to support a maximum of four database instances at a time.  This
  requires the fine tuning of several global system resources.  Most
  important is the virtual memory system for which we recommend at
  least 300M real and 500M swap memory.  Several kernel shared
  memory parameters must also be configured.
 
  There are nine dedicated mission accounts;  three for mission
  operations, three for mission testing, and three for software
  development.  Database instances are distinguished by both the
  database instance name as well as the host machine name.  It
  is extremely important that you use the proper machine to build
  each mission user environment:
 
  Mission User   Environment   Runtime Host   Instance Name
  ------------   -----------   ------------   -------------
  wind           OPS           ggslzp-1       WIND
  polar          OPS           ggslzp-2       POLAR
  geotail        OPS           ggslzp-1       GEOTAIL
 
  wind           TEST          ggslzp-3       WIND
  polar          TEST          ggslzp-3       POLAR
  geotail        TEST          ggslzp-3       GEOTAIL
 
  winddev        DEV           ggslzp-3       WINDDEV
  polardev       DEV           ggslzp-3       POLARDEV
  geodev         DEV           ggslzp-3       GEODEV

  A particular database instance is selected by logging in to the
  proper host and setting the ORACLE_SID environment variable in
  the current shell.  Use extreme caution to ensure that you have
  selected the proper database instance on the proper host or you
  will suffer a severe loss of data.  The software is extremely
  sensitive to the instance names.  Do not change any of these
  predefined instance names.

  The DBMS control/data files associated with each of the
  database instance must reside under RAID partitions because
  of the extreme file sizes involved.  Performance is also
  enhanced by locating the RAID partitions on separate disks.
 
  Instance Name  RAID Partition One  RAID Partition Two
  -------------  ------------------  ------------------
  WIND           /wind/wind1         /wind/wind2
  POLAR          /polar/polar1       /polar/polar2
  GEOTAIL        /geotail/geotail1   /geotail/geotail2

  WINDDEV        /wind/winddev1      /wind/winddev2
  POLARDEV       /polar/polardev1    /polar/polardev2
  GEODEV         /geotail/geodev1    /geotail/geodev2
 
  It was originally intended that the control file directories
  themselves actually be implemented as separate RAID partitions
  within the filesystem, however they may also be implemented
  as simple directories.  This is transparent to the software.
  Several control files contain hardcoded information about the
  filesystem.  Modifications to the RAID filesystem may also
  require modifications to these control files.
 
  WARNING:  The control files for each database instance must
  not be altered while the instance is still active.  Such
  alterations can result in a DBMS failover condition which
  is possible but difficult to recover from.

  Each database instance is created to support a particular mission
  which has associated with it a data file system and a set of
  symbolic executable links.  The data file system is located on a
  RAID partition because of the extreme file sizes which are involved.
  The executable links are used to enable the sharing of executable
  files located in the CM account by all missions.  Note that the
  DEV environment locates its executable links elsewhere.
 
  Instance Name  Symbolic Executable Links     RAID partition
  -------------  ----------------------------  --------------
  WIND           /opt/local/lzp/bin/wind       /wind/ops
  POLAR          /opt/local/lzp/bin/polar      /polar/ops
  GEOTAIL        /opt/local/lzp/bin/geotail    /geotail/ops
 
  WINDDEV        /export/home/dev/dps/wind     /wind/dev
  POLARDEV       /export/home/dev/dps/polar    /polar/dev
  GEODEV         /export/home/dev/dps/geotail  /geotail/dev

  It was originally intended that each instance correspond directly
  to a separate MISSION account and that the CM account would be used
  to manage the operational software executables.  A separate DEV
  account, with the home directory /export/home/dev/dps in this case,
  would be used to manage all development software executables.
 
  Following are snapshots of each of the operational database instance
  configurations.  The testing and development database instances should
  be configured similarly.  Use these templates to help guide you through
  the build.  Note that the installation account (username) must be
  "dpsuser" for all database instances while the installation account
  password should vary.


  Sample "WIND" database instance configuration:
  ----------------------------------------------
  Oracle instance (SID)          ---> WIND
  Oracle system account          ---> SYSTEM
  Installation account           ---> dpsuser
  DPS DB create script directory ---> /opt/local/cm/R1.4/dps/oracle/dba
  DPS DB table scripts directory ---> /opt/local/cm/R1.4/dps/oracle/dba
  DB disk partition 1            ---> /wind/wind1
  DB disk partition 2            ---> /wind/wind2
  DB dump partition              ---> /wind/wind1
  Installation type              ---> small
  Log file name                  ---> /oracle/app/oracle/product/7.3.2/WIND_create.log
 
  Population script path         ---> /opt/local/cm/R1.4/dps/oracle/populate
  Population log path            ---> /opt/local/cm
  Primary host name              ---> ggslzp-1
  Primary IP address             ---> 150.144.182.68
  Backup host name               ---> ggslzp-2
  Backup IP address              ---> 150.144.182.69
  Base port number               ---> 9000
  Data file path                 ---> /wind/ops
  Code file path                 ---> /opt/local/lzp/bin/wind
  FTP replay path                ---> /wind/ops/blks
  CDHF host name                 ---> ISTP2
  CDHF IP address                ---> 128.183.239.18
  CDHF account                   ---> LZP_INP
  DDF host name                  ---> IDDS
  DDF port number                ---> 4044
  DDF account                    ---> dpsuser
  FTP account                    ---> idds


  Sample "POLAR" database instance configuration:
  -----------------------------------------------
  Oracle instance (SID)          ---> POLAR
  Oracle system account          ---> SYSTEM
  Installation account           ---> dpsuser
  DPS DB create script directory ---> /opt/local/cm/R1.4/dps/oracle/dba
  DPS DB table scripts directory ---> /opt/local/cm/R1.4/dps/oracle/dba
  DB disk partition 1            ---> /polar/polar1
  DB disk partition 2            ---> /polar/polar2
  DB dump partition              ---> /polar/polar1
  Installation type              ---> big
  Log file name                  ---> /oracle/app/oracle/product/7.3.2/POLAR_create.log

  Population script path         ---> /opt/local/cm/R1.4/dps/oracle/populate
  Population log path            ---> /opt/local/cm
  Primary host name              ---> ggslzp-2
  Primary IP address             ---> 150.144.182.69
  Backup host name               ---> ggslzp-1
  Backup IP address              ---> 150.144.182.68
  Base port number               ---> 9000
  Data file path                 ---> /polar/ops
  Code file path                 ---> /opt/local/lzp/bin/polar
  FTP replay path                ---> /polar/ops/blks
  CDHF host name                 ---> ISTP2
  CDHF IP address                ---> 128.183.239.18
  CDHF account                   ---> LZP_INP
  DDF host name                  ---> IDDS
  DDF port number                ---> 4044
  DDF account                    ---> dpsuser
  FTP account                    ---> idds


  Sample "GEOTAIL" database instance configuration:
  -------------------------------------------------
  Oracle instance (SID)          ---> GEOTAIL
  Oracle system account          ---> SYSTEM
  Installation account           ---> dpsuser
  DPS DB create script directory ---> /opt/local/cm/R1.4/dps/oracle/dba
  DPS DB table scripts directory ---> /opt/local/cm/R1.4/dps/oracle/dba
  DB disk partition 1            ---> /geotail/geotail1
  DB disk partition 2            ---> /geotail/geotail2
  DB dump partition              ---> /geotail/geotail1
  Installation type              ---> big
  Log file name                  ---> /oracle/app/oracle/product/7.3.2/GEOTAIL_create.log
 
  Population script path         ---> /opt/local/cm/R1.4/dps/oracle/populate
  Population log path            ---> /opt/local/cm
  Primary host name              ---> ggslzp-1
  Primary IP address             ---> 150.144.182.68
  Backup host name               ---> ggslzp-2
  Backup IP address              ---> 150.144.182.69
  Base port number               ---> 9000
  Data file path                 ---> /geotail/ops
  Code file path                 ---> /opt/local/lzp/bin/geotail
  FTP replay path                ---> /geotail/ops/blks
  CDHF host name                 ---> ISTP2
  CDHF IP address                ---> 128.183.239.18
  CDHF account                   ---> LZP_INP
  DDF host name                  ---> IDDS
  DDF port number                ---> 4044
  DDF account                    ---> dpsuser
  FTP account                    ---> idds


*****************************************************************

Switch to the ORACLE account on the RUNTIME host
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
 
pluto% rlogin 150.144.200.60 -l oracle
Last login: Fri Sep 19 16:45:38 from ggslzp-1
Sun Microsystems Inc.   SunOS 5.5.1     Generic May 1996
 
Generic ISTP maintenance environment
 
!!! DANGER !!! WARNING !!! DANGER !!! WARNING !!! DANGER !!!
 
>>> Remember that you are SUPERUSER now as far as oracle is concerned.
>>> ALWAYS specify the database instance to be altered by setting the
>>> ORACLE_SID environment variable to indicate the proper database
>>> instance name.  If you forget to do this or do it wrong, you might
>>> destroy somebody's database.  Do this EACH and EVERY time you wish
>>> to reference the database within the scope of this software build.
>>> ALWAYS verify that you have selected the correct database instance
>>> by echoing it back to your screen.
 
!!! DANGER !!! WARNING !!! DANGER !!! WARNING !!! DANGER !!!

>>> In this example the WIND OPS mission will be rebuilt.  Thus,
>>> the build must take place on ggslzp-1 and the ORACLE_SID
>>> environment variable must be set to WIND.
 
ggslzp-1:oracle[/oracle/app/oracle/product/7.3.2]52=> setenv ORACLE_SID WIND
ggslzp-1:oracle[/oracle/app/oracle/product/7.3.2]53=> echo $ORACLE_SID
WIND
 
>>> Use the lzp_system stop command to shutdown the database instance.
>>> Once the database instance has been shutdown, deleting that instance
>>> is simply a matter of deleting its associated DBMS control/data files.

ggslzp-1:oracle[/oracle/app/oracle/product/7.3.2]54=> \
/opt/local/cm/R1.4/dps/pdp/tools/lzp_system stop wind

Executing server manager for wind on ggslzp-1
----------------------------------------------------------------
WIND> shutdown normal

Oracle Server Manager Release 2.3.3.0.0 - Production

Copyright (c) Oracle Corporation 1994, 1995. All rights reserved.

Oracle7 Server Release 7.3.3.0.0 - Production Release
PL/SQL Release 2.3.3.0.0 - Production

SVRMGR> Connected.
SVRMGR> Database closed.
Database dismounted.
ORACLE instance shut down.
SVRMGR> Server Manager complete.

>>> Verify that the control file directories for this instance exist.
 
ggslzp-1:oracle[/oracle/app/oracle/product/7.3.2]56=> cd /wind
ggslzp-1:oracle[/wind]57=> ll
total 24
drwx------   2 root     root        8192 Apr 28 00:02 lost+found
drwxr-xr-x   5 wind     wind         512 Apr 28 00:30 ops
drwxr-xr-x   3 oracle   dba          512 Apr 28 00:03 wind1
drwxr-xr-x   3 oracle   dba          512 Apr 28 00:06 wind2
 
>>> If the control file directories for this instance do not exist,
>>> contact the superuser in order to create or mount them with file
>>> ownership "oracle", group "dba".  All users should have read and
>>> execute permission for these directories, however only the ORACLE
>>> account should have write permission.  Delete the DBMS control
>>> file directory contents associated with this database instance.
 
ggslzp-1:oracle[/wind]58=> rm -rf wind1/*
rm: cannot read directory wind1/lost+found: Permission denied
ggslzp-1:oracle[/wind]59=> rm -rf wind2/*
rm: cannot read directory wind2/lost+found: Permission denied
 
>>> Verify that the global SQL login file "glogin.sql" has file
>>> ownership "oracle:dba" and user/group read/write permission set.
 
ggslzp-1:oracle[/wind]60=> cd ~oracle/sqlplus/admin
ggslzp-1:oracle[/oracle/app/oracle/product/7.3.2/sqlplus/admin]61=> chmod ug+w glogin.sql
ggslzp-1:oracle[/oracle/app/oracle/product/7.3.2/sqlplus/admin]62=> chmod +rx glogin.sql
ggslzp-1:oracle[/oracle/app/oracle/product/7.3.2/sqlplus/admin]63=> ll
total 12
-rwxrwxr-x   1 oracle   dba          915 Sep 16 13:58 glogin.sql
drwxr-xr-x   2 oracle   dba          512 Jun  7 02:29 help
-rw-r--r--   1 oracle   dba         3989 Mar 27  1996 pupbld.sql
 
>>> Execute the DPS software database create script in order to create the
>>> new database instance which replaces the one that was dropped earlier.
>>> It is intended that future releases will only make alterations to the
>>> existing database instances rather than recreating them from scratch.

ggslzp-1:oracle[/oracle/app/oracle/product/7.3.2/sqlplus/admin]64=> cd ~cm/R1.4/dps/oracle/dba
ggslzp-1:oracle[/opt/local/cm/R1.4/dps/oracle/dba]65=> dps_db.create

Enter the Oracle instance name [WIND]:
WIND
Enter the Oracle system account name [SYSTEM]:
SYSTEM
Enter the Oracle system account password:

Again to confirm: 

Enter the Oracle installation account name:
dpsuser
Enter the Oracle installation account password:
 
Again to confirm: 

Enter DPS database create scripts directory pathname [/opt/local/cm/current/dps/oracle/dba]: 
/opt/local/cm/R1.4/dps/oracle/dba
Enter DPS database table scripts directory pathname [/opt/local/cm/R1.4/dps/oracle/dba]: 
/opt/local/cm/R1.4/dps/oracle/dba
Enter the UNIX mission user account name [wind]: 
wind
Enter the file partition name for disk drive 1 [/wind/wind1]: 
/wind/wind1
Enter the file partition name for disk drive 2 [/wind/wind2]: 
/wind/wind2
Enter the file partition name for dump files [/wind/wind1]: 
/wind/wind1
Enter WIND installation type [Big/Small/Tiny]: 
small 
Enter the log file name [/oracle/app/oracle/product/7.3.2/WIND_create.log]: 
/oracle/app/oracle/product/7.3.2/WIND_create.log



The following are your selections:
 
Oracle instance (SID)          ---> WIND
Oracle system account          ---> SYSTEM
Installation account           ---> dpsuser
DPS DB create script directory ---> /opt/local/cm/R1.4/dps/oracle/dba
DPS DB table scripts directory ---> /opt/local/cm/R1.4/dps/oracle/dba
DB disk partition 1            ---> /wind/wind1
DB disk partition 2            ---> /wind/wind2
DB dump partition              ---> /wind/wind1
Installation type              ---> small
Log file name                  ---> /oracle/app/oracle/product/7.3.2/WIND_create.log
 
Are these correct [N]:
Y

/wind/wind1/data/WIND: No such file or directory
/wind/wind2/data/WIND: No such file or directory
 
Oracle Server Manager Release 2.3.2.0.0 - Production
 
Copyright (c) Oracle Corporation 1994, 1995. All rights reserved.
 
Oracle7 Server Release 7.3.2.3.0 - Production Release
With the distributed, replication and parallel query options
PL/SQL Release 2.3.2.3.0 - Production
 
SVRMGR> Connected to an idle instance.
SVRMGR> SVRMGR> ORACLE instance started.
Total System Global Area       4513064 bytes
Fixed Size                       39732 bytes
Variable Size                  4055540 bytes
Database Buffers                409600 bytes
Redo Buffers                      8192 bytes
SVRMGR>      2>      3>      4>      5>      6>      7>      8>      9>     10>
.
.
.

DPS Database has been created
Check the file /oracle/app/oracle/product/7.3.2/WIND_create.log for errors


 
>>> Expect "wind/wind1/data/WIND: No such file or directory"
>>> Expect "wind/wind2/data/WIND: No such file or directory"
>>> Expect to wait about 30 minutes for the next prompt.
>>>
>>> Examine the database instance creation log "WIND_create.log" for errors.
>>> The creation log should terminate with several lists of tables, indexes,
>>> and sequences which were created.  Expect exactly 109 tables, 100 indexes,
>>> and 9 sequences.  Use the command "grep 'ORA\-' filename |more" to
>>> search for unexpected errors...
>>>
>>> Expect "ORA-01432: public synonym to be dropped does not exist"
>>> Expect "ORA-01434: private synonym to be dropped does not exist"
>>> Expect "ORA-00942: table or view does not exist"
>>> Expect "ORA-06553: PLS-213: package STANDARD not accessible"
>>> Expect "ORA-01921: role name 'EXP_FULL_DATABASE' conflicts with another user or role name"
>>> Expect "ORA-01921: role name 'IMP_FULL_DATABASE' conflicts with another user or role name"
>>> Expect "object DBMS_STANDARD does not exist"
>>> Expect "object DIANA does not exist"
>>> Expect "object DIUTIL does not exist"
>>> Expect "object PSTUBT does not exist"
>>> Expect "object PSTUB does not exist"
>>> Expect "object SUBPTXT2 does not exist"
>>> Expect "object SUBPTXT does not exist"
>>> Expect "object PLITBLM does not exist"
>>> Expect "ORA-02289: sequence does not exist"
>>> Expect "ORA-00001: unique constraint (SYS.I_DUC) violated"
>>> Expect "ORA-03114: not connected to ORACLE"
>>> Expect "ORA-02443: Cannot drop constraint  - nonexistent constraint"
>>> Expect "ORA-01418: specified index does not exist"
>>> Expect "ORA-02441: Cannot drop nonexistent primary key"
>>>
>>> Execute the DPS software database install script in order to prepare
>>> the new database instance for population.  The install script may be
>>> used to import data from other instances into an existing instance
>>> as well.  The install script is responsible for enabling integrity
>>> constraints, granting access privileges, and creating synonyms.
 
ggslzp-1:oracle[/opt/local/cm/R1.4/dps/oracle/dba]66=> dps_db.install

Enter the Oracle instance name [WIND]:
WIND
Enter the Oracle system account name [SYSTEM]:
SYSTEM
Enter the Oracle system account password:

Again to confirm: 
 
Enter the Oracle delivery account name:
it_pics
Enter the Oracle installation account name:
dpsuser
Enter the Oracle installation account password:

Again to confirm: 
 
Enter the name of the log file [/oracle/app/oracle/product/7.3.2/WIND_install.log]:
/oracle/app/oracle/product/7.3.2/WIND_install.log

 
 
The following are your selections:
 
Oracle instance (SID) ---> WIND
Oracle system account ---> SYSTEM
Delivery account      ---> it_pics
Installation account  ---> dpsuser
Log file name         ---> /oracle/app/oracle/product/7.3.2/WIND_install.log
 
Are these correct [N]:
Y
 
Dropping referential integrity ...
Creating roles so users can share be assigned to a group ...
DPS roles have been created ...
 
Is any part of another database to be imported into this one? (y/n) [Y]
Y
 
Enter the name of the file to be imported [pacor2db.dmp]:
pacor2db.dmp
 
Import entire database (Y/N)? [N]:
N
List of available tables:
DB_DATASOURCE
DB_MESSAGE                                 DB_PMSSINPUTLINE
 
Enter the name of the table(s) to import separated by commas
Tablename(s):
DB_DATASOURCE, DB_MESSAGE, DB_PMSSINPUTLINE
 
 
Import: Release 7.3.2.3.0 - Production on Fri Sep 19 21:01:22 1997
 
Copyright (c) Oracle Corporation 1979, 1994.  All rights reserved.
 
 
Connected to: Oracle7 Server Release 7.3.2.3.0 - Production Release
With the distributed, replication and parallel query options
PL/SQL Release 2.3.2.3.0 - Production
 
Export file created by EXPORT:V07.02.02 via conventional path
 
Warning: the objects were exported by IT_PICS, not by you
 
. . importing table                   "DB_MESSAGE"        326 rows imported
. . importing table                "DB_DATASOURCE"          9 rows imported
. . importing table             "DB_PMSSINPUTLINE"         23 rows imported
Import terminated successfully without warnings.
 
The database import has completed ...
Creating role grants so users can share tables ...
Adding referential integrity ...
Creating synonyms that may be granted to users ...
Synonyms have been created ...
 


DPS Database has been installed
Check the file /oracle/app/oracle/product/7.3.2/WIND_install.log for errors


 
>>> Examine the database instance installation log "WIND_install.log" for
>>> errors.  Use the command "grep 'ORA\-' filename |more" to search for
>>> unexpected errors...
>>>
>>> Expect "ORA-02443: Cannot drop constraint  - nonexistent constraint"
>>> Expect "ORA-00942: table or view does not exist"
>>> Expect "ORA-03114: not connected to ORACLE"
>>> Expect "ORA-01919: role 'DPSUSER_ANALYST' does not exist"
>>> Expect "ORA-01919: role 'DPSUSER_SOFTWARE' does not exist"
>>> Expect "ORA-00901: invalid CREATE command"
>>> Expect "ORA-01918: user 'DPSUSER_PICSPROCESS' does not exist"
>>> Expect "ORA-01918: user 'DPSUSER_PDPSPROCESS' does not exist"

ggslzp-1:oracle[/opt/local/cm/R1.4/dps/oracle/dba]67=> exit
ggslzp-1:oracle[/opt/local/cm/R1.4/dps/oracle/dba]68=> logout
Connection closed.

*****************************************************************
 
  10.  D P S   D A T A B A S E   P O P U L A T I O N
  -------------------------------------------------------------

  OVERVIEW:
 
  The ORACLE account on the runtime host is used to populate
  the DPS software database for a particular mission.  It may
  be desirable to archive any existing database instances
  before altering them.  Oracle's standard import/export
  utilities are available for this purpose.

  REQUIREMENTS:

  1.  CM account on runtime host
  2.  ORACLE account on runtime host
  3.  Knowledge of overall filesystem structure
  4.  15 minutes per database instance

  SOFTWARE:

  1.  Solaris Operating System
  2.  Oracle with Pro*C compiler
  3.  DPS software database
 
  NOTES:

  Please be especially careful that you read the instructions
  completely and think before you issue your commands.  While
  logged in using the ORACLE account you are almost SUPERUSER.
  This means you can kill large portions of the system without
  even trying.  Get any other tasks you may have pending out
  of the way before starting this section so that you can give
  the build your full and undivided attention.  Thank you.

  When populating the DPS database for the first time execute
  all of the mission specific and generic population scripts
  (i.e. wind*, polar*, geotail*, istp*) exactly once.  Never
  execute the first and second sets of mission specific scripts
  (i.e. *001*.sql, *002*.sql) more than once or duplicate rows
  will be created.  If duplicate rows are created you will
  have to remove them by hand or re-create the entire database.
  Execute the generic population scripts (istp*) only when
  re-configuring and/or changing passwords.  It is okay to
  execute the third set of mission specific scripts (*003*.sql)
  as well as the generic population scripts (istp*) multiple
  times;  these scripts will not create any duplicate rows.
 
  Please review the notes for "DPS DATABASE CREATION".

*****************************************************************

Switch to the ORACLE account on the RUNTIME host
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

pluto% rlogin 150.144.182.68 -l oracle
Last login: Fri Sep 19 16:45:38 from ggslzp-1
Sun Microsystems Inc.   SunOS 5.5.1     Generic May 1996
 
Generic ISTP maintenance environment
 
>>> Execute the DPS software database population script in order to populate
>>> the new database instance.  The population script will also be used in
>>> future releases in order to alter existing database instances without
>>> having to drop them first.  The population script will require detailed
>>> knowledge of the ISTP LZP system interfaces including, but not limited to:
>>> structure of the local filesystem, structure of the RAID filesystem,
>>> the local FTP account user/password, the CDHF FTP account user/password,
>>> the DDF FTP account user/password and DAN protocol socket port number.
>>> It is possible to supply dummy values for the CDHF and DDF parameters
>>> with the expectation that these values will be corrected when they are
>>> actually known sometime in the future.  Most other parameters require
>>> actual and correct values at this time.

ggslzp-1:oracle[/oracle/app/oracle/product/7.3.2]51=> cd ~cm/R1.4/dps/oracle/populate
ggslzp-1:oracle[/opt/local/cm/R1.2/dps/oracle/populate]52=> dps_db.populate

Enter the Oracle instance name [WIND]:
WIND
Enter the Oracle installation account name [dpsuser]:
dpsuser
 
Enter the Oracle installation account password:
 
Again to confirm:
 
 
Enter the population script path [/opt/local/cm/R1.4/dps/oracle/populate]:
/opt/local/cm/R1.4/dps/oracle/populate
Enter the population log path [/oracle/app/oracle/product/7.3.2]:
/oracle/app/oracle/product/7.3.2

Enter the primary host name [ggslzp-1]:
ggslzp-1
Enter the primary IP address [150.144.182.68]:
150.144.182.68
Enter the backup host name [ggslzp-2]:
ggslzp-2
Enter the backup IP address [150.144.182.69]:
150.144.182.69

Enter the base port number [9000]:
9000
Enter data file path [/wind/ops]:
/wind/ops
Enter code file path [/opt/local/lzp/bin/wind]:
/opt/local/lzp/bin/wind
Enter FTP replay path [/wind/ops/blks]:
/wind/ops/blks
 
Enter CDHF host name [ISTP2]:
ISTP2
Enter CDHF IP address [128.183.239.18]:
128.183.239.18
Enter CDHF account [LZP_INP]:
LZP_INP
 
Enter CDHF password:
 
Again to confirm:
 
 
Enter DDF host name [IDDS]:
IDDS
Enter DDF port number [4044]:
4044
Enter DDF account [dpsuser]:
dpsuser
 
Enter DDF password:
 
Again to confirm:
 
Enter FTP account [idds]:
idds
 
Enter FTP password:
 
Again to confirm:
 
 
 
The following are your selections:
 
Oracle instance (SID)      ---> WIND
Installation account       ---> dpsuser
 
Population script path     ---> /opt/local/cm/R1.4/dps/oracle/populate
Population log path        ---> /oracle/app/oracle/product/7.3.2

Primary host name          ---> ggslzp-1
Primary IP address         ---> 150.144.182.68
Backup host name           ---> ggslzp-2
Backup IP address          ---> 150.144.182.69

Base port number           ---> 9000
Data file path             ---> /wind/ops
Code file path             ---> /opt/local/lzp/bin/wind
FTP replay path            ---> /wind/ops/blks
 
CDHF host name             ---> ISTP2
CDHF IP address            ---> 128.183.239.18
CDHF account               ---> LZP_INP
 
DDF host name              ---> IDDS
DDF port number            ---> 4044
DDF account                ---> dpsuser
FTP account                ---> idds
 
Are these values correct (Yes/No/Quit)?
Y

>>> If you are populating the DPS database for the first time
>>> then execute all of the mission specific population scripts
>>> (i.e. wind*, polar*, or geotail*).  Otherwise, execute only
>>> the third set of mission specific scripts (*003*.sql).  Do
>>> not execute the first and second set of mission specific
>>> scripts more than once or duplicate rows will be created.

WARNING:  Some scripts may only be run once
Enter population script name [exit]: 
wind003*
 
The following population scripts were found: 
 
wind003a.sql
 
WARNING:  Existing values will be changed
Execute ALL scripts in listed order [N]? 
Y

>>> If you are populating the DPS database for the first time
>>> or you are changing passwords and/or configuration then
>>> execute all of the generic population scripts (i.e. istp*).
>>> If you do not know the correct passwords then do not
>>> execute the generic population scripts since you could
>>> alter existing passwords and/or configuration parameters.
>>> The generic population scripts may be executed multiple
>>> times without creating any duplicate rows.

WARNING:  Some scripts may only be run once
Enter population script name [exit]: 
istp*

The following population scripts were found: 
 
istp_Add_BackupHost.sql
istp_Set_CDHFConfiguration.sql
istp_Set_DDFConfiguration.sql
istp_Set_DisplayTerminals.sql
istp_Set_PDPConfiguration.sql
istp_Set_PrimaryHost.sql
 
WARNING:  Existing values will be changed
Execute ALL scripts in listed order [N]? 
Y

WARNING:  Some scripts may only be run once
Enter population script name [exit]: 
exit
 


DPS Database has been populated
Check the file /oracle/app/oracle/product/7.3.2/WIND_populate.log for errors


 
>>> Examine the database instance population log "WIND_populate.log" for
>>> errors.  Use the command "grep 'ORA\-' filename |more" to search for
>>> unexpected errors...  Expect "ORA-00001: unique constraint violated".

ggslzp-1:oracle[/opt/local/cm/R1.2/dps/oracle/populate]53=> exit
ggslzp-1:oracle[/opt/local/cm/R1.2/dps/oracle/populate]54=> logout
Connection closed.

*****************************************************************
 
  11.  R E C O N   D A T A B A S E   C R E A T I O N
  -------------------------------------------------------------
 
  OVERVIEW:
 
  You may skip this section if the recon mission tablespaces
  already exist.  This section is performed only when creating
  a recon mission tablespace for the first time.

  The CM account on the runtime host is used to create the
  RECON software database.  The existence of the DPS software
  database is a prerequisite for the existence of the RECON
  software database.  Remember to repeat this script for the
  pwiw mission after creating the polar recon database.

  REQUIREMENTS:
 
  1.  CM account on runtime host
  2.  Knowledge of overall filesystem structure
  3.  4GB disk space, 60 minutes per recon mission

  SOFTWARE:
 
  1.  Any ASCII program text editor
  2.  Solaris Operating System
  3.  Oracle with Pro*C compiler
  4.  SunWSpro C compiler
  5.  DPS software database
 
  NOTES:
 
  Please review the notes for "DPS DATABASE CREATION".  Recall
  from Oracle-101 that each database instance is composed of
  potentially multiple tablespaces, each tablespace generally
  corresponding to a separate database account (similar to the
  notion of a UNIX account).  All of the tablespaces within a
  given database instance are isolated from each other by the
  DBMS software (similar to UNIX application processes).
 
  The RECON software database is built on top of the existing
  DPS software database by creating extra tablespaces within the
  existing database instances.  In general, two recon tablespaces
  are added to each existing database instance, one for data, and
  one for indexes.  It is also possible for data and indexes to
  share the same tablespace.
 
  Because of difficulties associated with implementing the special
  pwiw data format for the polar mission, the recon subsystem
  introduces the notion of recon missions, different from the
  simple notion of missions.  This allows the recon subsystem to
  treat the pwiw data format as a separate mission while keeping
  it part of the polar mission overall.  The recon-mission to
  database-instance to tablespace-name mapping used within the
  recon subsystem is depicted in the following table.  Note that
  the pre-existing DPS tablespaces are not shown.

  Recon Mission  Environment    Instance Name  Tablespace Name
  -------------  -------------  -------------  ---------------
  wind           OPS            WIND           WIND
  wind           OPS            WIND           WIND_INDEX
  polar          OPS            POLAR          POLAR
  polar          OPS            POLAR          POLAR_INDEX
  pwiw           OPS            POLAR          PWIW
  pwiw           OPS            POLAR          PWIW_INDEX
  geotail        OPS            GEOTAIL        GEOTAIL
  geotail        OPS            GEOTAIL        GEOTAIL_INDEX

  wind           TEST           WIND           WIND
  wind           TEST           WIND           WIND_INDEX
  polar          TEST           POLAR          POLAR
  polar          TEST           POLAR          POLAR_INDEX
  pwiw           TEST           POLAR          PWIW
  pwiw           TEST           POLAR          PWIW_INDEX
  geotail        TEST           GEOTAIL        GEOTAIL
  geotail        TEST           GEOTAIL        GEOTAIL_INDEX

  wind           DEV            WINDDEV        WINDDEV
  wind           DEV            WINDDEV        WINDDEV_INDEX
  polar          DEV            POLARDEV       POLARDEV
  polar          DEV            POLARDEV       POLARDEV_INDEX
  pwiw           DEV            POLARDEV       PWIWDEV
  pwiw           DEV            POLARDEV       PWIWDEV_INDEX
  geotail        DEV            GEODEV         GEODEV
  geotail        DEV            GEODEV         GEODEV_INDEX
 
  Following are snapshots of each of the operational recon mission
  configurations.  The development recon missions should be configured
  similarly.  Use these templates to help guide you through the build.


  Sample "wind" recon mission configuration:
  ------------------------------------------
  Mission name            ---> wind
  Baseline path           ---> /opt/local/cm/R1.4/recon
  Operations path         ---> /opt/local/lzp/bin
  Oracle instance (SID)   ---> WIND
  DB disk partition 1     ---> /wind/wind1
  DB disk partition 2     ---> /wind/wind2
  Oracle system account   ---> SYS
  Rules tablespace name   ---> WIND
  Index tablespace name   ---> WIND_INDEX
  Reconstruction account  ---> WIND
 
 
  Sample "polar" recon mission configuration:
  -------------------------------------------
  Mission name            ---> polar
  Baseline path           ---> /opt/local/cm/R1.4/recon
  Operations path         ---> /opt/local/lzp/bin
  Oracle instance (SID)   ---> POLAR
  DB disk partition 1     ---> /polar/polar1
  DB disk partition 2     ---> /polar/polar2
  Oracle system account   ---> SYS
  Rules tablespace name   ---> POLAR
  Index tablespace name   ---> POLAR_INDEX
  Reconstruction account  ---> POLAR


  Sample "pwiw" recon mission configuration:
  ------------------------------------------
  Mission name            ---> pwiw
  Baseline path           ---> /opt/local/cm/R1.4/recon
  Operations path         ---> /opt/local/lzp/bin
  Oracle instance (SID)   ---> POLAR
  DB disk partition 1     ---> /polar/polar1
  DB disk partition 2     ---> /polar/polar2
  Oracle system account   ---> SYS
  Rules tablespace name   ---> PWIW
  Index tablespace name   ---> PWIW_INDEX
  Reconstruction account  ---> PWIW
 
 
  Sample "geotail" recon mission configuration:
  ---------------------------------------------
  Mission name            ---> geotail
  Baseline path           ---> /opt/local/cm/R1.4/recon
  Operations path         ---> /opt/local/lzp/bin
  Oracle instance (SID)   ---> GEOTAIL
  DB disk partition 1     ---> /geotail/geotail1
  DB disk partition 2     ---> /geotail/geotail2
  Oracle system account   ---> SYS
  Rules tablespace name   ---> GEOTAIL
  Index tablespace name   ---> GEOTAIL_INDEX
  Reconstruction account  ---> GEOTAIL
 
 
*****************************************************************

Switch to the CM account on the RUNTIME host
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

pluto% rlogin 150.144.182.68 -l cm
Last login: Fri Sep 19 16:45:38 from ggslzp-1
Sun Microsystems Inc.   SunOS 5.5.1     Generic May 1996

Generic ISTP maintenance environment

>>> Execute the RECON software database build script in order to create
>>> the RECON tablespaces within the existing DPS database instances.
 
ggslzp-1:cm[/opt/local/cm]51=> cd R1.4/recon/common/source
ggslzp-1:cm[/opt/local/cm/R1.4/recon/common/source]52=> Build_ISTP.recon



============================================================
 
               Building ISTP recon subsystem
 
============================================================
 
 
 
Enter the Reconstruction mission name [wind/polar/pwiw/geotail]: wind
Enter baseline path [/opt/local/cm/current/recon]: /opt/local/cm/R1.4/recon
Enter operations path [/opt/local/lzp/bin]: /opt/local/lzp/bin

Enter the Oracle instance name [WIND]: WIND
Enter file partition name for disk drive 1 [/wind/wind1]:
/wind/wind1
Enter file partition name for disk drive 2 [/wind/wind2]:
/wind/wind2
Enter the Oracle system account name [SYS]: SYS
Enter the Oracle system account password: 
Again to confirm: 

Enter the Rules tablespace name [WIND]: WIND
Enter the Index tablespace name [WIND_INDEX]: WIND_INDEX
Enter the Reconstruction account name [WIND]: WIND
Enter the Reconstruction account password:
Again to confirm:
 
Create or Populate Reconstruction Database [Populate]: Create 
 
Create Rules Tablespace            [Y]: Y
Create Index Tablespace            [Y]: Y
Create Reconstruction Account      [Y]: Y
Activate Reconstruction Account    [Y]: Y
Install Oracle Supplied Packages   [Y]: Y
Build Reconstruction Tables        [Y]: Y
Build Reconstruction Indexes       [Y]: Y
Install Reconstruction Procedures  [N]: N
Pin Procedures in Memory           [N]: N
Install Reconstruction Utilities   [N]: N
Import Reconstruction Tables       [N]: N



Creating WIND reconstruction database as follows:
 
Mission name            ---> wind
Baseline path           ---> /opt/local/cm/R1.4/recon
Operations path         ---> /opt/local/lzp/bin
 
Oracle instance (SID)   ---> WIND
Oracle system account   ---> SYS
DB disk partition 1     ---> /wind/wind1
DB disk partition 2     ---> /wind/wind2
 
Rules tablespace name   ---> WIND
Index tablespace name   ---> WIND_INDEX
Reconstruction account  ---> WIND

Create rules tablespace ---> Y
Create index tablespace ---> Y
Create recon account    ---> Y
Activate recon account  ---> Y
Install Oracle packages ---> Y
Build recon tables      ---> Y
Build recon indexes     ---> Y
Install procedures      ---> N
Pin procedures in SGA   ---> N
Install recon utilities ---> N
Import recon tables     ---> N

Are these parameters correct [N]: Y
WARNING:  Existing tablespaces will be dropped
WARNING:  Existing account will be dropped
WARNING:  Existing passwords will be modified
WARNING:  Oracle supplied packages will be replaced
WARNING:  Existing objects may be duplicated
WARNING:  Existing indexes will be dropped

Are you sure [N]: Y

Interrupts are not recommended
Initializing Reconstruction Log
Creating Rules Tablespace
Creating Index Tablespace
Creating Reconstruction Account
Activating Reconstruction Account
Installing Oracle Supplied Packages
Building Reconstruction Tables
Building Reconstruction Indexes



Reconstruction Database has been created
Check the file /export/home/dev/dps1/WIND_recon.log for errors



>>> Examine the recon database installation log "WIND_recon.log" for
>>> errors.  Use the command "grep 'ORA\-' filename |more" to search for
>>> unexpected errors...
>>>
>>> Expect "ORA-01918: user does not exist".
>>> Expect "ORA-00959: tablespace does not exist".
>>>
>>> If you are recreating a reconstruction mission database without
>>> recreating the DPS software database, you will have to execute
>>> the Build_ISTP.recon script twice.  The first execution will
>>> drop the appropriate tablespaces, after which the ORACLE account
>>> must be used to remove the associated data files.  DO NOT REMOVE
>>> REMOVE DATA FILES UNTIL AFTER THE TABLESPACES ARE DROPPED OR YOU
>>> WILL CRASH THE DATABASE INSTANCE.  The second execution of the
>>> Build_ISTP.recon script should then run properly.
>>>
>>> If you are creating the polar recon database, remember to repeat
>>> execution of the Build_ISTP.recon script for the pwiw mission.

ggslzp-1:cm[/opt/local/cm/R1.4/recon/common/source]53=> exit
ggslzp-1:cm[/opt/local/cm/R1.4/recon/common/source]54=> logout
Connection closed.

*****************************************************************
 
  12.  R E C O N   D A T A B A S E   P O P U L A T I O N
  -------------------------------------------------------------

  OVERVIEW:
 
  The CM account on the runtime host is used to populate
  the RECON software database for a particular mission.  It
  may be desirable to archive any existing database instances
  before altering them.  Oracle's standard import/export
  utilities are available for this purpose.
 
  REQUIREMENTS:
 
  1.  CM account on runtime host
  2.  Knowledge of overall filesystem structure
  3.  15 minutes per database instance
 
  SOFTWARE:
 
  1.  Any ASCII program text editor
  2.  Solaris Operating System
  3.  Oracle with Pro*C compiler
  4.  SunWSpro C compiler
  5.  DPS software database
  6.  RECON software database
 
  NOTES:

  The database administrator is responsible for altering
  table schemas and table contents within the reconstruction
  database.  In general, the table creation option may NOT
  be used for this purpose since existing data will be lost
  from and/or duplicate rows inserted into many tables.
  The purpose of this section is to update the database
  functions, procedures, passwords, and environment only.

  Please review the notes for "DPS DATABASE CREATION".
  Please review the notes for "RECON DATABASE CREATION".
 
*****************************************************************
 
Switch to the CM account on the RUNTIME host
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
 
pluto% rlogin 150.144.182.68 -l cm
Last login: Fri Sep 19 16:45:38 from ggslzp-1
Sun Microsystems Inc.   SunOS 5.5.1     Generic May 1996
 
Generic ISTP maintenance environment
 
>>> Execute the RECON software database build script in order to populate
>>> the RECON tablespaces within the existing DPS database instances.
 
ggslzp-1:cm[/opt/local/cm]51=> cd R1.4/recon/common/source
ggslzp-1:cm[/opt/local/cm/R1.4/recon/common/source]52=> Build_ISTP.recon
 
 
 
============================================================
 
Building ISTP recon subsystem

============================================================



Enter the Reconstruction mission name [wind/polar/pwiw/geotail]: wind
Enter baseline path [/opt/local/cm/current/recon]: /opt/local/cm/R1.4/recon
Enter operations path [/opt/local/lzp/bin]: /opt/local/lzp/bin

Enter the Oracle instance name [WIND]: WIND
Enter file partition name for disk drive 1 [/wind/wind1]: 
/wind/wind1
Enter file partition name for disk drive 2 [/wind/wind2]: 
/wind/wind2
Enter the Oracle system account name [SYS]: SYS
Enter the Oracle system account password:
Again to confirm:

Enter the Rules tablespace name [WIND]: WIND
Enter the Index tablespace name [WIND_INDEX]: WIND_INDEX
Enter the Reconstruction account name [WIND]: WIND
Enter the Reconstruction account password:
Again to confirm:

Create or Populate Reconstruction Database [Populate]: Populate

Create Rules Tablespace            [N]: N
Create Index Tablespace            [N]: N
Create Reconstruction Account      [N]: N
Activate Reconstruction Account    [Y]: Y
Install Oracle Supplied Packages   [N]: N
Build Reconstruction Tables        [N]: N
Build Reconstruction Indexes       [N]: N
Install Reconstruction Procedures  [Y]: Y
Pin Procedures in Memory           [Y]: Y
Install Reconstruction Utilities   [Y]: Y
Import Reconstruction Tables       [Y]: Y
 
 
 
Populating WIND reconstruction database as follows:

Mission name            ---> wind
Baseline path           ---> /opt/local/cm/R1.4/recon
Operations path         ---> /opt/local/lzp/bin

Oracle instance (SID)   ---> WIND
Oracle system account   ---> SYS
DB disk partition 1     ---> /wind/wind1
DB disk partition 2     ---> /wind/wind2

Rules tablespace name   ---> WIND
Index tablespace name   ---> WIND_INDEX
Reconstruction account  ---> WIND

Create rules tablespace ---> N
Create index tablespace ---> N
Create recon account    ---> N
Activate recon account  ---> Y
Install Oracle packages ---> N
Build recon tables      ---> N
Build recon indexes     ---> N
Install procedures      ---> Y
Pin procedures in SGA   ---> Y
Install recon utilities ---> Y
Import recon tables     ---> Y

Are these parameters correct [N]: Y
WARNING:  Existing passwords will be modified
WARNING:  Existing procedures will be replaced
WARNING:  Pinning requires 100M of shared memory
WARNING:  Shared environments will be modified
WARNING:  Old objects will be imported

Are you sure [N]: Y

Interrupts are not recommended
Initializing Reconstruction Log
Sharing Rules Tablespace with Indexes
Activating Reconstruction Account
Installing Reconstruction Procedures
Pinning Procedures in Memory
Installing Reconstruction Utilities

Importing Reconstruction Tables
Enter Dump Directory [/wind/ops/oracle]: 
/wind/ops/oracle

List of available dump files: 
-rw-r--r--   1 oracle   dba      231580672 Mar 19 19:09 WIND_full_export.dmp
-rw-r--r--   1 oracle   dba      26166272 Apr 23 15:37 WIND_full_export_042198.dmp
 
Enter Dump File [WIND_full_export_042198.dmp]: 
WIND_full_export_042198.dmp

List of available tables: 
.
.
.

Enter Tables [TTCDACCT,TTCDHIST,TTCDVALUE,STATION_TABLE]: 
TTCDACCT,TTCDHIST,TTCDVALUE,STATION_TABLE

Enter Original Table Owner [WIND] or Quit: 
WIND

Import: Release 7.3.2.2.0 - Production on Fri Apr 24 20:02:03 1998
 
Copyright (c) Oracle Corporation 1979, 1994.  All rights reserved.
 
 
Connected to: Oracle7 Server Release 7.3.2.3.0 - Production Release
With the distributed, replication and parallel query options
PL/SQL Release 2.3.2.3.0 - Production
 
Export file created by EXPORT:V07.03.02 via conventional path
. importing WIND's objects into WIND
. . importing table                "STATION_TABLE"         21 rows imported
IMP-00033: Warning: Table "TTCDACCT" not found in export file
IMP-00033: Warning: Table "TTCDHIST" not found in export file
IMP-00033: Warning: Table "TTCDVALUE" not found in export file
Import terminated successfully with warnings.



Reconstruction Database has been populated
Check the file /opt/local/cm/WIND_recon.log for errors



>>> Examine the recon database installation log "WIND_recon.log" for
>>> errors.  Use the command "grep 'ORA\-' filename |more" to search for
>>> unexpected errors...
>>>
>>> Expect "IMP-00033: Warning: Table TTCDACCT not found in export file"
>>> Expect "IMP-00033: Warning: Table TTCDHIST not found in export file"
>>> Expect "IMP-00033: Warning: Table TTCDVALUE not found in export file"
>>>
>>> If you are creating the polar recon database, remember to repeat
>>> the recon database population for the pwiw recon database.

ggslzp-1:cm[/opt/local/cm/R1.4/recon/common/source]53=> exit
ggslzp-1:cm[/opt/local/cm/R1.4/recon/common/source]54=> logout
Connection closed.

*****************************************************************
 
  13.  S Y S T E M   E N V I R O N M E N T
  -------------------------------------------------------------
 
  OVERVIEW:
 
  The SUPERUSER account on the runtime host is used to
  install and verify the UNIX system level executables
  and configuration, including the system cron tables.
 
  REQUIREMENTS:
 
  1.  CM account on runtime host
  2.  SUPERUSER account on runtime host
  3.  15 minutes per host
 
  SOFTWARE:
 
  1.  Any ASCII program text editor
  2.  Solaris Operating System
 
  NOTES:

  When installing the ISTP LZP system from scratch, it may
  be necessary to execute this section at an earlier point
  in time.  In particular, the lzp_system make command must
  be used to create and tune the mission filesystem after
  the appropriate RAID volumes are defined.  The CM, ORACLE
  and MISSION accounts must be created before attempting
  the lzp_system make command.

*****************************************************************

Switch to the CM account on the RUNTIME host
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
 
pluto% rlogin 150.144.182.68 -l cm
Generic ISTP maintenance environment
 
ggslzp-1:cm[/opt/local/cm]51=> cd R1.4/dps/pdp/tools
ggslzp-1:cm[/opt/local/cm/R1.4/dps/pdp/tools]52=> ll
total 4080
lrwxrwxrwx   1 cm       dba           12 Apr 23 18:07 Makefile -> ../Makefile2
-r--r--r--   1 cm       dba         1296 Dec 22 11:38 decrypt.c
-r-xr-xr-x   1 cm       dba        37572 Apr 23 17:39 decrypt.sql
-rwxr-xr-x   1 cm       dba         5059 May 29 04:42 diffdir
-rwxr-xr-x   1 cm       dba          137 Sep 16  1997 dlog
-rwxr-xr-x   1 cm       dba        11428 Apr 23 17:39 fread
-rw-r--r--   1 cm       dba         4675 Nov 24 08:34 fread_main.c
-rw-r--r--   1 cm       dba        13400 Apr 23 17:39 fread_main.o
-rwxr-xr-x   1 cm       dba       106888 Apr 23 17:38 hashinit
-rw-r--r--   1 cm       dba         1865 Nov 24 08:21 hexout.h
-rwxr-xr-x   1 cm       dba        11368 Mar 12 23:23 loadtape
-rwxr-xr-x   1 cm       dba         5481 Jan 30 09:20 lzp_checkftp
-rwxr-xr-x   1 cm       dba         1659 Apr  8 19:37 lzp_install
-rwxr-xr-x   1 cm       dba        77804 Apr 23 17:39 lzp_isas
-rwxr-xr-x   1 cm       dba        23392 Apr  3 22:22 lzp_process
-rwxr-xr-x   1 cm       dba         4474 Apr 20 23:44 lzp_remove
-rwxr-xr-x   1 cm       dba        25932 Feb 10 21:14 lzp_rename
-rwxr-xr-x   1 cm       dba        24327 Apr 21 16:26 lzp_replay
-rwxr-xr-x   1 cm       dba        28759 Jan 30 02:21 lzp_split
-rwxr-xr-x   1 cm       dba         9555 Mar 14 18:06 lzp_system
-rwxr-xr-x   1 cm       dba         8634 Mar 26 00:06 lzp_trend
-rwxr-xr-x   1 cm       dba         7028 May 22 16:35 lzp_verify
-rwxr-xr-x   1 cm       dba          429 Apr  9 16:24 lzp_xmit
lrwxrwxrwx   1 cm       dba            9 Apr 23 18:07 lzpdiff -> ./lzpscan
lrwxrwxrwx   1 cm       dba            9 Apr 23 18:07 lzpedit -> ./lzpscan
-rw-r--r--   1 cm       dba        15957 Mar 16 00:22 lzpisas_main.c
-rw-r--r--   1 cm       dba        63008 Apr 23 17:39 lzpisas_main.o
lrwxrwxrwx   1 cm       dba            9 Apr 23 18:07 lzpprod -> ./lzpscan
-rwxr-xr-x   1 cm       dba       185306 Apr  2 18:42 lzpscan
-rwxr-xr-x   1 cm       dba        42344 Apr 20 03:15 lzpshow
-rwxr-xr-x   1 cm       dba       145524 Apr 23 17:39 lzptime
-rw-r--r--   1 cm       dba         9515 Dec 23 18:18 lzptime_main.c
-rw-r--r--   1 cm       dba        78244 Apr 23 17:39 lzptime_main.o
-rwxr-xr-x   1 cm       dba         1054 Mar 17 05:38 mvx
-rwxr-xr-x   1 cm       dba          607 Sep 16  1997 plog
-rw-r--r--   1 cm       dba         1386 Mar 17 17:42 prototype.crontab.geotail
-rw-r--r--   1 cm       dba         1740 Mar 17 17:43 prototype.crontab.polar
-rw-r--r--   1 cm       dba         1873 Mar 17 17:43 prototype.crontab.root.1
-rw-r--r--   1 cm       dba         1873 Mar 17 17:43 prototype.crontab.root.2
-rw-r--r--   1 cm       dba         1734 Mar 17 17:42 prototype.crontab.wind
-rw-r--r--   1 cm       dba          641 Mar 17 17:59 prototype.hosts.root.1
-rw-r--r--   1 cm       dba          636 Mar 17 17:59 prototype.hosts.root.2
-rw-r--r--   1 cm       dba         2275 Apr 24 22:01 prototype.system.root
-rw-r--r--   1 cm       dba         1170 Mar 17 18:09 prototype.userlogin.root
-rw-r--r--   1 cm       dba         5535 Apr  3 09:27 prototype.vfstab.root.1
-rw-r--r--   1 cm       dba         5536 Apr  3 09:27 prototype.vfstab.root.2
-rwxr-xr-x   1 cm       dba          290 Apr 10 12:00 pspdp
-rw-r--r--   1 cm       dba        73441 Apr 23 17:38 pxx_hashinit.c
-rw-r--r--   1 cm       dba        60384 Apr 23 17:38 pxx_hashinit.o
-rw-r--r--   1 cm       dba        21098 Feb 26 19:31 pxx_hashinit.pc
-rwxr-xr-x   1 cm       dba       130856 Apr 23 17:38 time_convert
-rw-r--r--   1 cm       dba         9505 Apr 10 11:31 time_convert.c
-rw-r--r--   1 cm       dba        45392 Apr 23 17:38 time_convert.o
-rwxr-xr-x   1 cm       dba        98732 Apr 23 17:38 verifyhash
-rw-r--r--   1 cm       dba         6632 Apr 10 11:32 verifyhash.c
-rw-r--r--   1 cm       dba        63336 Apr 23 17:38 verifyhash.o
-rwxr-xr-x   1 cm       dba        55436 Apr 23 17:38 vhashindex
-rw-r--r--   1 cm       dba        84435 Apr 23 17:38 vhashindex.c
-rw-r--r--   1 cm       dba        63976 Apr 23 17:38 vhashindex.o
-rw-r--r--   1 cm       dba         4165 Apr 10 11:32 vhashindex.pc
-rwxr-xr-x   1 cm       dba        61060 Apr 23 17:38 viewhash
-rw-r--r--   1 cm       dba        82340 Apr 23 17:38 viewhash.c
-rw-r--r--   1 cm       dba        65344 Apr 23 17:38 viewhash.o
-rw-r--r--   1 cm       dba         6674 Apr 10 11:31 viewhash.pc
-rwxr-xr-x   1 cm       dba         1242 Feb 19 23:03 writetape
lrwxrwxrwx   1 cm       dba           29 Apr 23 18:07 xxxTimeConvert.c -> ../../xxxLib/...
-rw-r--r--   1 cm       dba        96108 Apr 23 17:38 xxxTimeConvert.o

>>> Contact the SUPERUSER in order to edit and verfiy the system
>>> cron table entries which are used to schedule automated jobs,
>>> including system log maintenance/deletion, system backups,
>>> and precision time keeping.  The following files are supplied
>>> as prototypes only and should not be taken literally:
>>>
>>> prototype.crontab.root.1
>>> prototype.crontab.root.2
>>> prototype.hosts.root.1
>>> prototype.hosts.root.2
>>> prototype.system.root
>>> prototype.userlogin.root
>>> prototype.vfstab.root.1
>>> prototype.vfstab.root.2
>>>
>>> In particular, be sure that the /etc/system file is configured
>>> to enable semaphores and shared memory objects which are
>>> primarily required by the Oracle DBMS.  The use of pinned
>>> procedures will require at least 100M of sharable physical
>>> memory per database instance to be shared by server processes.
>>>
>>> The UNIX command crontab -l may be used to list a particular
>>> user's cron table without editing it.  The crontab -e command
>>> may be used to edit a particular user's cron table.  Unless
>>> you are SUPERUSER you will not have permission to view or
>>> edit cron tables which do not belong to you since passwords
>>> are sometimes included in these files.
 
Switch to the SUPERUSER account on the RUNTIME host
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
 
ggslzp-1:cm[/opt/local/cm/R1.4/dps/pdp/tools]53=> su
Password:
# cd /opt/local/cm/R1.4/dps/pdp/tools
# pwd
/opt/local/cm/R1.4/dps/pdp/tools
# crontab -l
 
>>> Verify that all system level scripts are compatible with all
>>> missions currently supported on your host machine.  The
>>> release notes should have special instructions concerning
>>> compatible/incompatible releases.  You may also contact the
>>> development team for a recommendation.
>>>
>>> SYSTEM LEVEL SCRIPTS ARE SHARED BY ALL MISSIONS ON THE HOST.
>>>
>>> Use the lzp_install script to copy the following automation
>>> scripts to the /opt/local/bin directory:
>>>
>>>           lzp_checkftp          lzp_isas
>>>           lzp_process           lzp_remove
>>>           lzp_rename            lzp_replay
>>>           lzp_split             lzp_system
>>>           lzp_trend
>>>
>>> These scripts are invoked both manually and automatically by
>>> cron jobs in order to accept and process data through the
>>> Level Zero Processor.  Only root may execute lzp_install.
 
# cd /opt/local/cm/R1.4/dps/pdp/tools
# pwd
/opt/local/cm/R1.4/dps/pdp/tools
# ./lzp_install
Install automation scripts in /opt/local/bin now (y/n)? y
Installing automation scripts in /opt/local/bin
Installing auxiliary scripts in /opt/local/lzp/bin
Installation completed.

>>> Assuming that RAID volumes have been created in advance,
>>> verify that the /etc/vfstab file has been edited in order
>>> to correctly define the device drivers and mount options
>>> associated with each RAID volume.
>>>
>>> DO NOT EXECUTE LZP_SYSTEM MAKE IF FILESYSTEM ALREADY EXISTS
>>>
>>> If the filesystem does not already exist, particularly if
>>> this is the first installation of the ISTP LZP software,
>>> use the lzp_system make script in order to create and tune
>>> the mission filesystem.  Do not execute lzp_system make
>>> while the ISTP LZP software is active.

# ./lzp_system make wind



============================================================

              Making ISTP wind filesystem

============================================================



Enter database account [oracle:dba]:
Reformat filesystems (y/n)? y
Enter newfs options or null [-i 131072 -c 32]:
Tune filesystems (y/n)? y
Enter tunefs options or null [-m 5 -o time]:

You have made the following selections:

Database for wind on ggslzp-1 owned by oracle:dba
Reformat using:  newfs -i 131072 -c 32 filesystem
Tune using:  tunefs -m 5 -o time filesystem

WARNING:  REFORMATTING DESTROYS EXISTING DATA

Make wind filesystems (y/n)? y

Making filesystem for wind on ggslzp-1
----------------------------------------------------------------
Mounting all filesystems
Unmounting /wind/ops/brmltapes
Unmounting /wind/ops/data2
umount: warning: /wind/ops/data2 not in mnttab
umount: /wind/ops/data2 no such file or directory
Removing old mount points
Unmounting /wind/wind1
Removing old mount points
Unmounting /wind/wind2
umount: warning: /wind/wind2 not in mnttab
umount: /wind/wind2 no such file or directory
Removing old mount points
Unmounting /wind
Removing old mount points
Making /wind
newfs: /dev/vx/rdsk/windgrp/windhome last mounted as /wind
newfs: construct a new file system /dev/vx/rdsk/windgrp/windhome: (y/n)? y
/dev/vx/rdsk/windgrp/windhome:  13770752 sectors in 6724 cylinders of 32 tracks, 64 sectors
6724.0MB in 211 cyl groups (32 c/g, 32.00MB/g, 256 i/g)
super-block backups (for fsck -F ufs -o b=#) at:
 32, 65632, 131232, 196832, 262432, 328032, 393632, 459232, 524832, 590432,
 656032, 721632, 787232, 852832, 918432, 984032, 1049632, 1115232, 1180832,
 12910944, 12976544, 13042144, 13107744, 13173344, 13238944, 13304544,
 13370144, 13435744, 13501344, 13566944, 13632544, 13698144, 13763744,
minimum percentage of free space changes from 10% to 5%
should optimize for space with minfree < 10%
optimization preference remains unchanged as time
Making /wind/ops
Making /wind/wind1
newfs: /dev/vx/rdsk/windgrp/windora1 last mounted as /wind/wind1
newfs: construct a new file system /dev/vx/rdsk/windgrp/windora1: (y/n)? y
/dev/vx/rdsk/windgrp/windora1:  13312000 sectors in 6500 cylinders of 32 tracks, 64 sectors
6500.0MB in 204 cyl groups (32 c/g, 32.00MB/g, 256 i/g)
super-block backups (for fsck -F ufs -o b=#) at:
 32, 65632, 131232, 196832, 262432, 328032, 393632, 459232, 524832, 590432,
 656032, 721632, 787232, 852832, 918432, 984032, 1049632, 1115232, 1180832,
 12453792, 12519392, 12582944, 12648544, 12714144, 12779744, 12845344,
 12910944, 12976544, 13042144, 13107744, 13173344, 13238944, 13304544,
minimum percentage of free space changes from 10% to 5%
should optimize for space with minfree < 10%
optimization preference remains unchanged as time
Making /wind/wind2
newfs: /dev/vx/rdsk/windgrp/windora2 last mounted as /wind/wind2
newfs: construct a new file system /dev/vx/rdsk/windgrp/windora2: (y/n)? y
/dev/vx/rdsk/windgrp/windora2:  13312000 sectors in 6500 cylinders of 32 tracks, 64 sectors
6500.0MB in 204 cyl groups (32 c/g, 32.00MB/g, 256 i/g)
super-block backups (for fsck -F ufs -o b=#) at:
 32, 65632, 131232, 196832, 262432, 328032, 393632, 459232, 524832, 590432,
 656032, 721632, 787232, 852832, 918432, 984032, 1049632, 1115232, 1180832,
 12453792, 12519392, 12582944, 12648544, 12714144, 12779744, 12845344,
 12910944, 12976544, 13042144, 13107744, 13173344, 13238944, 13304544,
minimum percentage of free space changes from 10% to 5%
should optimize for space with minfree < 10%
optimization preference remains unchanged as time
Making /wind/ops/oracle
Making /wind/ops/cdrblks
Making /wind/ops/data2
newfs: /dev/vx/rdsk/windgrp/winddata2 last mounted as /wind/ops/data2
newfs: construct a new file system /dev/vx/rdsk/windgrp/winddata2: (y/n)? y
/dev/vx/rdsk/windgrp/winddata2: 13312000 sectors in 6500 cylinders of 32 tracks, 64 sectors
6500.0MB in 204 cyl groups (32 c/g, 32.00MB/g, 256 i/g)
super-block backups (for fsck -F ufs -o b=#) at:
 32, 65632, 131232, 196832, 262432, 328032, 393632, 459232, 524832, 590432,
 656032, 721632, 787232, 852832, 918432, 984032, 1049632, 1115232, 1180832,
 12453792, 12519392, 12582944, 12648544, 12714144, 12779744, 12845344,
 12910944, 12976544, 13042144, 13107744, 13173344, 13238944, 13304544,
minimum percentage of free space changes from 10% to 5%
should optimize for space with minfree < 10%
optimization preference remains unchanged as time
Make finished successfully

Filesystem status for wind on ggslzp-1
----------------------------------------------------------------
Filesystem            kbytes    used   avail capacity  Mounted on
/dev/vx/dsk/windgrp/windhome
                     6875228      21 6531447     1%    /wind
/dev/vx/dsk/windgrp/windora1
                     6646188       9 6313874     1%    /wind/wind1
/dev/vx/dsk/windgrp/windora2
                     6646188       9 6313874     1%    /wind/wind2
/dev/vx/dsk/windgrp/winddata2
                     6646188       9 6313874     1%    /wind/ops/data2

# exit
ggslzp-1:cm[/opt/local/cm/R1.4/dps/pdp/tools]54=> exit
ggslzp-1:cm[/opt/local/cm/R1.4/dps/pdp/tools]55=> logout
Connection closed.

*****************************************************************
 
  14.  M I S S I O N   E N V I R O N M E N T
  -------------------------------------------------------------
 
  OVERVIEW:
 
  The CM and MISSION accounts on the runtime host are used
  to setup each of the mission operations environments.  This
  involves dynamically creating the directory tree, creating
  a few small shell scripts, initializing the DPS software
  hash files, copying configuration files from the baseline
  software in the CM account, and editing the MISSION account
  cron tables which automate the software.
 
  REQUIREMENTS:
 
  1.  CM account on runtime host
  2.  MISSION account on runtime host
  3.  1MB free disk space per mission
  4.  15 minutes per mission
 
  SOFTWARE:

  1.  Any ASCII program text editor
  2.  Solaris Operating System
  3.  Oracle with Pro*C compiler
  4.  X/Motif with Software Development Kit
  5.  LabView G compiler/interpreter
  6.  Washington University ftpd 2.4.2 beta 15
  7.  SunWSpro C compiler
  8.  Perl 5 shell interpreter
  9.  RDA client software package
  10. FS software executables
  11. AD software executables
  12. DPS software database
  13. DPS software executables
  14. RECON software database
  15. RECON software executables
 
  NOTES:
 
  There are nine dedicated mission accounts;  three for mission
  operations, three for mission testing, and three for software
  development.  Database instances are distinguished by both the
  database instance name as well as the host machine name.  It
  is extremely important that you use the proper machine to build
  each mission user environment:
 
  Mission User   Environment   Runtime Host   Instance Name
  ------------   -----------   ------------   -------------
  wind           OPS           ggslzp-1       WIND
  polar          OPS           ggslzp-2       POLAR
  geotail        OPS           ggslzp-1       GEOTAIL
 
  wind           TEST          ggslzp-3       WIND
  geotail        TEST          ggslzp-3       GEOTAIL
  polar          TEST          ggslzp-3       POLAR
 
  winddev        DEV           ggslzp-3       WINDDEV
  geodev         DEV           ggslzp-3       GEODEV
  polardev       DEV           ggslzp-3       POLARDEV

  Automation can only be enabled for a single operations
  account on a single host for each mission.  Typically
  ggslzp-1 supports WIND and GEOTAIL operations while
  ggslzp-2 supports POLAR operations.  Continuing with
  this scenario, automation must be implemented as follows:
 
  Mission User   Environment   Runtime Host   Automated?
  ------------   -----------   ------------   ----------
  wind           OPS           ggslzp-1       YES
  geotail        OPS           ggslzp-1       YES
  polar          OPS           ggslzp-2       YES
 
  wind           OPS           ggslzp-2       NO
  geotail        OPS           ggslzp-2       NO
  polar          OPS           ggslzp-1       NO
 
  wind           TEST          ggslzp-3       YES
  geotail        TEST          ggslzp-3       YES
  polar          TEST          ggslzp-3       YES
 
  winddev        DEV           ggslzp-3       NO
  geodev         DEV           ggslzp-3       NO
  polardev       DEV           ggslzp-3       NO

*****************************************************************
 
Switch to the CM account on the RUNTIME host
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
 
pluto% rlogin 150.144.182.68 -l cm
Last login: Fri Oct  3 01:13:00 from ggslzp-1
Sun Microsystems Inc.   SunOS 5.5.1     Generic May 1996
 
Generic ISTP maintenance environment
 
>>> Use the DPS build script to reset the operations executable
>>> links located in the /opt/local/lzp/bin directory.

ggslzp-1:cm[/opt/local/cm]55=> cd R1.4/dps
ggslzp-1:cm[/opt/local/cm]56=> Build_ISTP.dps



============================================================
 
                 Building ISTP dps subsystem
 
============================================================
 
 
 
Enter mission (common/wind/polar/geotail): wind
 
Enter baseline path (/opt/local/cm/current/dps): 
/opt/local/cm/R1.4/dps

Enter operations path (/opt/local/lzp/bin): 
/opt/local/lzp/bin
 
Building /opt/local/cm/R1.4/dps
Build baseline executables (Y/N)? n

Linking /opt/local/lzp/bin/wind -> /opt/local/cm/R1.4/dps
Reset operations links (Y/N)? Y

Removing directories...
Creating directories...
Updating links...
 
Enter database user (dpsuser): dpsuser
 
Enter database password:  
Again to confirm:  
 
Enter encryption key:  
Again to confirm:  
 
Links reset.

ggslzp-1:cm[/opt/local/cm]57=> exit
ggslzp-1:cm[/opt/local/cm]58=> logout
Connection closed.

Switch to the MISSION account on the RUNTIME host
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
 
pluto% rlogin 150.144.182.68 -l wind
Last login: Mon Sep 22 04:07:40 from ggslzp-1
Sun Microsystems Inc.   SunOS 5.5.1     Generic May 1996

>>> Copy the hidden files which determine the mission runtime
>>> environment from the CM account and source the hidden files
>>> in order to activate the new environment.  Be careful not
>>> to use the recursive option for the cp command.

ggslzp-1:wind[/wind/ops]51=> chmod u+w .*
chmod: WARNING: can't change ..
ggslzp-1:wind[/wind/ops]52=> cp -p /opt/local/cm/R1.4/dps/pics/.* .
cp: /opt/local/cm/R1.4/dps/pics/.: is a directory
cp: /opt/local/cm/R1.4/dps/pics/..: is a directory
ggslzp-1:wind[/wind/ops]53=> source .login
 
Welcome to WIND mission operations

ggslzp-1:wind[/wind/ops]54=> source .cshrc
Please edit .mycshrc to personalize your environment.
Please do NOT modify the .cshrc and .alias files.

>>> Touch or edit the .mycshrc file to quiet the messages shown above.
>>> Note that if you are using multiple login shells or windows,
>>> you will have to source the ".login" and ".cshrc" in each such
>>> shell individually, or the new environment will not take effect.
>>> Another way to do this is to logout and then login again.
>>>
>>> Use the AD build script in order to create and initialize
>>> the AD directories and configuration files for this release.
>>> Expect no errors from the AD build script.

ggslzp-1:wind[/wind/ops]55=> ~cm/R1.4/ad/common/Build_ISTP.ad
 
 
 
============================================================
 
                 Building ISTP ad subsystem
 
============================================================
 
 
 
Enter mission (wind/polar/geotail): wind
 
Enter baseline path (/opt/local/cm/current/ad):
/opt/local/cm/R1.4/ad
 
Enter data path (/wind/ops):
/wind/ops
 
Baseline path --> /opt/local/cm/R1.4/ad
Mission home  --> /wind/ops
 
Create directories (Y/N)? Y
Creating directories...
Copying files...
Build complete

>>> Depending on the release, it may be necessary to run the
>>> DPS hashinit utility.  One of the less desirable effects
>>> of the hashinit utility is that all sessions will be
>>> removed from the DPS hash tables, thus preventing these
>>> sessions from being included in any future products
>>> until they are pre-processed again.  This may impact
>>> daily mission operations.  The release notes should have
>>> special instructions concerning whether or not to run
>>> hashinit.  You may also contact the development team for
>>> a recommendation.
>>>
>>> HASHINIT DESTROYS DATA AND IS NOT REQUIRED FOR ALL RELEASES.
>>>
>>> Use the DPS hashinit utility to create and initialize
>>> the DPS data directories and hash table information.
>>> For safety reasons, hashinit requires the mission ID
>>> as an argument.  Executing hashinit without arguments
>>> will cause it to warn you of the proper mission ID.

ggslzp-1:wind[/wind/ops]55=> hashinit
 
Truncating hash index: pdp_hash_index
 
Created capture directory: /wind/ops/data1/25
 
Created ftp directory: /wind/ops/blks
 
Created hash directory: /wind/ops/data2/25
 
                ** initializing hash files (1 per apid) ** ( 20)
 
Created product directory /wind/ops/data3/25

>>> Depending on the mission, environment, and host machine
>>> the software may or may not be automated.  If the software
>>> should NOT be automated for this particular mission account
>>> then remove the cron table file from the config directory.
>>>
>>> DISABLE AUTOMATION DEPENDING ON THE MISSION AND ENVIRONMENT.
>>>
>>> The release notes should have special instructions concerning
>>> whether or not to automate the software.  You may also contact
>>> the development team for a recommendation.

ggslzp-1:wind[/wind/ops]56=> cd config
ggslzp-1:wind[/wind/ops/config]57=> rm crontab.wind
ggslzp-1:wind[/wind/ops/config]58=> logout
Connection closed.

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * 
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
 
>>> Congratulations!
>>>
>>> You have finished building this release of the Re-Engineered
>>> ISTP LZP system.  Please notify the development, test, and
>>> operations teams of your success so that they can resume
>>> their normal day-to-day operations.
>>>
>>> Note that there may still be some cleanup to do.  Definitely
>>> there are database backups and such to be archived on tape.
>>> These backups should be located on the RAID, probably under
>>> /wind/ops/oracle, /polar/ops/oracle, and /geotail/ops/oracle.
>>> Please remove these backups from disk once they are on tape
>>> since they take away disk space from the mission accounts.
>>>
>>> Recall that the tar command to archive to the default tape
>>> drive is as follows:  tar cv myfilename

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * 
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
