|
|
To prepare and secure the system for updating:
From the console, log on with the following conditions, or
if already logged on, change group to PUB.
:HELLO MANAGER.SYS,PUB;HIPRI
or
:CHGROUP PUB
If you are performing an Update, go to Step 3.
If you are performing an Add-on, go to Step 4.
Update Tasks
Run HP Predictive Support and turn it off.
If you are using the HP Predictive Support software as part of your
Hewlett-Packard hardware support contract, ensure that an HP Predictive
Support run completes successfully.
Issue the HP Predictive Support command:
:RUN PSCONFIG.PRED.SYS
This run of HP Predictive Support may include a transfer of files
to the Hewlett-Packard Response Center. If a transfer is needed,
be sure it completes because the system update
overwrites the information in the file
PSDCFILE.PRED.SYS.
Select item 4, Configuration, from the Main menu.
Select item 5, Schedule, from the Configuration Options menu.
Select item 1, Schedule (ON/OFF), from the Schedule menu.
Set the preference, at the prompt, type OFF:
Type schedule preference (on/off) or // to cancel: __
Exit the program, at the prompt, type EXIT:
Type an item number, an item key, or a command: __
Save the values, at the prompt, type YES:
Do you wish to save these values (Y/N)?__
Go to Step 4.
Update and Add-On Tasks
Lower session and job limits.
:LIMIT0,0
Warn, then log users off.
:WARN@ PLEASE LOG OFF! SYSTEM UPDATE ABOUT TO BEGIN
Wait approximately five minutes. Make sure users have saved their
work and logged off, then abort jobs or sessions still executing. Use
the SHOWJOB command to determine session and job numbers. For
each job and session still executing (except yours) type:
:ABORTJOB #Jnn
:ABORTJOB #Snnn
where:
Jnn — the ID number for each job to be aborted.
Snnn — the ID number for each session to be aborted.
Deactivate NS 3000/iX, if applicable.
:NSCONTROL STOP
:NSCONTROL ABORT
:NETCONTROL STOP
Terminate logging processes.
Enter the following command to determine if user logging
processes are running:
:SHOWLOGSTATUS
If logging processes are running on your system, a message
similar to the following will be displayed:
LOGID CHANGE AUTO USERS STATE CUR REC MAX REC % USED CUR FSET
SHPLOGID YES YES 1 ACTIVE 120 10016 1% 1
ORBLOGID YES YES 9 ACTIVE 3812 10016 38% 1
If no logging processes are running, go to Step 8.
Terminate logging processes as shown below.
:LOG logid,STOP
where logid is the ID number for each logging process to
be stopped.
Record the names of the logging processes on your checklist, if
you want to restart them later.
Prepare additional manually installed products.
If you have ALLBASE/SQL already installed on your system, issue
starts for each DBEnvironment before you back up the system. Refer
to the ALLBASE/SQL Database Administration Guide for more
information. Briefly, you need to:
Identify all your ALLBASE/SQL databases, type:
:LISTFILE @.@.@,6;seleq[code=-491]
RunISQL.PUB.SYS and issue a STARTDBE
command. This ensures that the DBEnvironment is logically
consistent in the event that it has not been accessed since a
system failure occurred.
Run SQLUTIL.PUB.SYS and issue the STORE
command to backup each DBEnvironment.
Log files are not stored using this command. In addition,
you should use the SHOWDBE command to ensure that all
parameters are OK.
If you have ALLBASE/4GL already on your system, unload all
existing ALLBASE/4GL applications. For information on unloading
ALLBASE/4GL applications, refer to the HP ALLBASE/4GL Developer
Administration Manual.
If you are installing AutoRestart/iX for the first time,
install AutoRestart/iX before you run AUTOINST. Refer to
the AutoRestart/iX Reference Manual for installation
instructions.
If you have a current full backup, you may proceed to Step 11.
If you do not already have a current full backup, proceed to Step 10.
Backup the System
Back up the system, if you do not already have a current full backup.
Specify a class name.
:FILE SYSGTAPE;DEV=dev_number
where the dev_number is the DAT class name or LDEV number
of the tape device. Specify this value if you are using a DAT or
any device that has a class name other than TAPE.
Mount a write-enabled tape and create an SLT.
:SYSGEN
sysgen>TAPE
sysgen>EXIT
If you are prompted for lockwords on system files, record the
names of each system file as prompted, then type the lockword and
continue with the backup. You will need to restore these lockwords
later in the section, "Setting Passwords and Lockwords." Record
the names on your checklist.
Dismount the tape, label as SLT with date, time and system
version.
Mount another blank tape and backup your user files.
:FILE T;DEV=TAPE
:STORE @.@.SYS,@.@.@-@.@.SYS;*T;DIRECTORY;SHOW
or
:STORE /SYS/, / - /SYS/;*T;DIRECTORY;SHOW; &
ONVS=volume_set_name1, volume_set_name2, ...
where the volume_set_name is the name for each user
volume set you want to backup.
Dismount the tape, label with date, time and system version.
Go to Step 11.
If it exists, purge HPINSTFL:
:PURGE HPINSTFL.INSTALL.SYS
Purge spool files.
:SPOOLF @;DELETE
Purge staging groups.
:PURGEGROUP UNL
:PURGEGROUP USL
:PURGEGROUP UXL
Verify each purge, type Y, at the prompt.
Do not purge the group install.sys or the file
supacct.pub.sys; they are needed for future patch and add-on
processes.
If you are performing an Update task, go to Step 15.
If you are performing an Add-on task, go to Step 16.
Update Tasks
Purge specified files and groups.
Purge each osxnn and xptnnnn
group in the telesup account.
:REPORT OS?##.TELESUP
:PURGEGROUP OSxnn.TELESUP
:REPORT XPT####.TELESUP
:PURGEGROUP XPT@.TELESUP
where:
x — an alphabetic character
nn — the numeric release number (for example,
OSA10.TELESUP and 0SB23.TELESUP).
These files may not exist.
Go to Step 16.
Rename the COMMAND.PUB.SYS file.
:RENAME COMMAND.PUB.SYS,command_name
where command_name is a temporary name you are assigning the
file. This preserves your UDC information for later use. Record the
temporary name on your checklist.
|