Open System Services Management and Operations Guide (G06.25+, H06.03+)

Open System Services Management and Operations Guide—527191-002
D-1
D
Falling Back to a Previous Release
Version Update
You can fall back to any G-series release version update (RVU) from a current
G-series RVU or to any H-series RVU from a current H-series RVU. You cannot fall
back to a G-series RVU from an H-series RVU because of hardware considerations.
The procedure you use for falling back depends on the RVU to which you are falling
back and the method you used to install the RVU of OSS from which you are falling
back:
•
For RVUs after G06.18, you can use the DSM/SCM backout feature for files in the
OSS file system if you used DSM/SCM to install and manage OSS files for both
RVUs involved in the fallback.
•
On RVUs prior to G06.19, you cannot use the DSM/SCM backout feature for files
in the OSS file system. DSM/SCM will have no old configuration to fall back to.
The procedures described in this appendix assume that you either do not use
DSM/SCM to manage OSS files (the Manage OSS Files check box is not selected in
the planner interface) or you do not have the T6031 D46 product version update (PVU)
or later installed. Use of the DSM/SCM backout feature is described in the DSM/SCM
User’s Guide.
Falling back to a G0x RVU preceding G05.00 requires a valid ZPCONFIG file. If the
backup copy created during installation (the file named ZXCONFIG) is not current or
has been deleted, you must create a new ZPCONFIG file.
•
Recreating the ZPCONFIG File on page D-1
•
Falling Back to a G06.xx Release Version Update on page D-5
•
Falling Back to a G05.0x Release Version Update on page D-7
•
Falling Back to a G0x Release Version Update Preceding G05.00 on page D-7
Recreating the ZPCONFIG File
The ZPCONFIG file is a Guardian EDIT file that defines the configuration of Open
System Services (OSS) filesets on the following RVUs:
•
D3x RVUs
•
G0x RVUs preceding G05.00
The ZPCONFIG file establishes a relationship among filesets, storage pools, catalog
volumes, and mount points. You must have a record (line) in the ZPCONFIG file for
each fileset on your system. A sample ZPCONFIG file is shown in Figure D-1.