5.4 Make Software Update(s) Official
OVERVIEW
This procedure takes the software update(s) previously loaded into the /etc/bwm from
either SCANS or tape, and verifies the files, then applies the software update in
"temporary" mode. Next the update enters into a soak period during which time any
problems with the update may be discovered. This soak period may last a day or more.
Following the soak period, the overwrite is made official and the files are removed
from /etc/bwm.
With this procedure, a desired point of installation may be entered. Maintenance
personnel can:
1. Step through each stage of an SU Installation one step at a time, or
2. Install an SU through any stage of the installation (including make-official) with
just one poke. The SU Installation will stop if an error occurs or if the stop
installation poke is entered.
Following is a list of status indicators that will appear during this procedure:
Status Color Key Word
not executed yellow —
completed green COMPLTD
stopped blue (steady) STOPPED
aborted red ABORTED
in progress blue (flashing) INPROGR
PROCEDURE
1. Using the listing of software updates, choose the software update with lowest
sequence number.
2. At the MCC Page 1990, type and enter: 9,"yyyyyyyyyy" to start the software
update process.
Where: y...y= 6-digit or 10-digit software update number, craft (CFT)
software update number, or temporary (TMP) software update
number.
This will introduce an SU for installation.
Response: The SU name will appear in the page title.
3. At the MCC Page 1990, type and enter: 1 to verify software update and build
executable message file.
Response: The verify stage box will change from yellow to a flashing blue and
display the word INPROGR. This will continue until the verify
aborts or completes. If aborted, the indicator box will change to red
and display ABORTED. If the verify successfully completes, the
indicator box will change to green and display the word COMPLTD.
4. At the MCC Page 1990, type and enter: 11 to print entire message file.
Response: Message file printed at ROP.
Review message file for events that will take place during activation, or any
special actions which must be accomplished manually.
235-200-150
January 2003
ROUTINE MAINTENANCE
Procedure 5.4
Issue 3.00 Page 5.4-1
To Next Page
Loading...
Need help?
General