Open System Services Management and Operations Guide (G06.25+, H06.03+)
Falling Back to a Previous Release Version Update
Open System Services Management and Operations Guide—527191-002
D-9
Falling Back to a G0x Release Version Update
Preceding G05.00
file created in Step 1c). If the ZXCONFIG file is current, enter the following at
the TACL prompt:
RENAME $SYSTEM.ZXOSSMON.ZXCONFIG $SYSTEM.ZXOSSMON.ZPCONFIG
•
If the ZXCONFIG file is not current or if it does not exist, use a text editor to
recreate the current configuration in a new ZPCONFIG file as described in
Recreating the ZPCONFIG File on page D-1. Use the information in the log file
created in Step 1c.
4. Use the subsystem information in the log file created in Step 1c to create
equivalent PARAM values for the D40 OSS Monitor on your fallback system. See
PARAMs Used by the OSS Monitor on page 2-10 for a description of those
parameters.
5. Remove the configuration files for the RVU from which you are falling back by
entering the following commands at the TACL prompt:
VOLUME $SYSTEM.ZXOSSMON
PURGE ZPOSFSET ZPOSFS00 ZPOSFS01 ZPOSSERV ZPOSPARM
6. Load the previous G0x RVU. Restore any needed files from backups you made
before you installed the RVU from which you are falling back.
7. Load the corresponding OSS product files for the previous G0x RVU using
COPYOSS or the pinstall utility as described in Installing New Product Files on
page 6-4.
8. Start the D40 OSS Monitor by performing the following steps:
a. At the TACL prompt, enter:
OSSMON / NAME $ZPMON, NOWAIT, CPU nn, TERM name /
nn
is the processor number of the processor you want the D40 OSS Monitor
to run on.
name
is the name of the home terminal for the D40 OSS Monitor. Ensure that this
terminal is always available and that it is not a Telserv or Multilan session.
b. Use the TACL STATUS command to verify that the D40 OSS Monitor process
$ZPMON is running:
STATUS $ZPMON
c. If the D40 OSS Monitor process is not running, check the Event Management
Service (EMS) log for related event messages. For explanation of any console
messages received and possible corrective actions, see Appendix A,
Messages.