G06.32 Software Installation and Upgrade Guide
Overview of Installing G06.32
G06.32 Software Installation and Upgrade Guide—546068-002
1-25
DSM/SCM Client and Server Compatibility
Notes on the CLEANOSS Macro
If you fall back and then migrate to G06.32 RVU, DSM/SCM might notify you during the
Apply that the CLEANOSS macro must be run. The current OSS environment is being
managed by a logical target other than the one trying to manage OSS files with the
current DSM/SCM Build/Apply. You must cancel the Apply, and run the CLEANOSS
macro. The EMS message gives you basic instructions:
The current OSS environment is managed by target oss-system
(according to /zzDSMSCM.Managed). To switch OSS management
from oss-system to target-system, CANCEL the Apply, run
CLEANOSS, run Verify Database, then RESTART the Apply.
If you receive the following EMS message (5305) or a similar one, it indicates that you
are running the D46 PVU of T6031 but not the most current EMS templates to
effectively display the CLEANOSS message. It is possible that you restored the
T6041D46 or G02 PVU from tape and activated it, but the correct templates were
either not properly installed or the NonStop operating system is pointing to the wrong
template files:
11:43:03 AM 10/27/03 $Z420 DSM/SCM: *5305* Server Class TA-001 of PATHMON
\TINY.$YPHI activity id \TINY211933793397226152, activity code 20, planner id
SUPER.SUPER in stage 202:
EMSTEXT -- No template and no TEXT token for event. SSID = TANDEM.DSMSCM.D30
Event number = 5305 Subject = \TINY211933793397226152
For more information on what message should be displayed, see the
DSM/SCM
Messages Manual
. You can probably continue, but you will not receive properly
formatted and detailed DSM/SCM EMS messages.
For detailed information on using the FALLBACK macro and CLEANOSS, see
Section 2 in the
DSM/SCM User’s Guide
. For more information on configuring
DSM/SCM Targets, see the
DSM/SCM User's Guide
.
DSM/SCM Client and Server Compatibility
The D46 DSM/SCM client is backward compatible with other DSM/SCM product
versions (backward compatible to T6030D30/T6031D30 [AAO and later]). However,
some console messages might not be displayed because the client and the server side
do not match.
Running ZPHIRNM Again Before a System Load
After you have returned the SP firmware, processor boot code, and SCSI boot code
back to the previous versions, if needed, you must run the ZPHIRNM program again to
change the temporary names of the previous product files to their actual names.
ZPHIRNM renames all files associated with the software revision last applied to the
operating system image (SYS
n
n) subvolume.
After you run ZPHIRNM and it renames all OSS and Guardian files, ZPHIRNM
automatically runs ZMODGP if necessary.