G06.31 Software Installation and Upgrade Guide

G06.31 Installation and Fallback Alerts
G06.31 Software Installation and Upgrade Guide—544626-002
2-6
OSS Files Greater Than 2 Gigabytes (Large Files)
If the DP2 fallback SPR is not installed, you cannot access any Format 2 files using
either OSS or Enscribe on systems running an RVU earlier than G06.28, even if they
are smaller than 2 GB.
DP2 has a dependency on DSAP/DCOM. If you install the DP2 fallback SPR
(T9053AQS), you must also install T9543G08^ABJ.
DSAP/DCOM Migration and Fallback
Migration
The DSAPDDL file is changed in the product revision of DSAP/DCOM delivered in the
G06.29 RVU (T9543G08^ABJ), resulting in changes to the work-file layout. You must
use the DSAPDDL file distributed with T9543G08^ABJ when running ENFORM
queries on the work file created using this SPR. The DSAPDDL file for T9543G08^ABJ
contains these changes to the directory-record structure:
•
The field named fifth is changed from type binary unsigned to type binary 32
unsigned.
•
These fields are added to the end of the structure:
°
Field flab2_flags1 of type binary unsigned identifies OSS files larger than 2
GB.
°
Field ext-0-fsu of type binary unsigned contains the extent size of large
OSS files for extent number 0.
°
Field ext-1-128-fsu of type binary unsigned contains the extent size of
large OSS files for extent number 1-128.
Fallback
The product revision of DSAP/DCOM delivered in the G06.29 and later RVUs
(T9543G08^ABJ) is “large OSS file safe”, but product revisions delivered in earlier
RVUs are not. The aforementioned migration considerations apply. If you fall back to a
pre-G06.29 RVU, HP recommends that you install T9543G08^ABJ during the fallback.
DP2 has a dependency on DSAP/DCOM. If you install the DP2 fallback SPR
(T9053AQS), you must also install T9543G08^ABJ.
Backup and Restore 2 Fallback
If you have a tape file with a mix of OSS files smaller than 2 GB and larger than 2 GB
that needs to be restored to a G06.23 to G06.28 file set that does not support files
Note. An application that is “large file safe” causes no data loss or corruption when it
encounters an OSS file larger than 2 GB. It might not be able to process OSS files larger than
2 GB, but it has the appropriate logic to handle errors or warnings detected during file
manipulation operations and fail gracefully.