Communicator e3000 MPE/iX Release 6.5 (Non-Platform Software Release C.65.00 (30216-90291)

Chapter 3 53

Growth Solution

MPE/iX Large Files Overview

If you rely on 3rd party backup tools, please refer to your vendor for information regarding

the proper updates and procedures for using these tools on release 6.5.

Backdating Procedures

If for some reason it is necessary to “backdate” your system from the 6.5 release to a prior

MPE/iX release, very little extra work is required due to Large Files. Before attempting

the backdate operation, the 6.5 system must be shut down completely with the CNTRL-A

SHUTDOWN command. You must also wait for the ﬁnal system shutdown message to appear

before resetting the system and beginning the UPDATE command on the earlier MPE/iX

release.

Any Large Files that are in the directory structure of the system are unusable once the

system is backdated to a release earlier than 6.5. The Large Files can be purged from the

older system via the :PURGELINK command. Any other attempt to open or manipulate a

Large File results in an error. Once the system is again updated to release 6.5 or beyond,

the Large Files are once again accessible.

Utility and Subsystem Support

Nearly all utilities and subsystems support Large Files without change. This runs the

spectrum from FCOPY to SORT. The only word of caution is that not all utilities and

subsystems support ﬁle sizes that are less than 4GB. This includes such things as EDITOR

or HPEDIT. The general rule of thumb is if it doesn’t work on a 3GB ﬁle, it won’t work on a

Large File.

One exception of note is the DSCOPY subsystem. DSCOPY has not been enhanced to be able to

transfer Large Files, or the new KSAM64 ﬁles. The FTP utility has been enhanced to do

network transfers of these ﬁles, and is the preferred utility for network ﬁle transfer.

Impact on IMAGE Database

The introduction of Large Files has had no impact on the IMAGE/SQL product. Large

database support is still accomplished by use of Jumbo Datasets. Therefore there are no

compatibility issues to be concerned with in regards to changes in your IMAGE/SQL

databases.

HP SRC

Version A.01.29 of HP SRC does not support KSAM64 ﬁles. If an attempt is made to check

in a KSAM64 ﬁle, error 387 will be reported.

JAVA

Java programs will be able to access large MPE/iX ﬁles by using Java Native Interface

(JNI) to call MPE/iX intrinsics, but will not be able to access Large Files via the java.io

APIs. The java.io APIs treat all ﬁles as bytestream ﬁles and access these ﬁles through the

POSIX C language APIs. The ﬁrst release of Large Files for MPE/iX does not include

support for bytestream ﬁles larger than 2GB in size; therefore, there can be no Large Files

that are also bytestream ﬁles in this release.

HPSEARCH/iX

HPSearch/iX has been changed to provide for searching of Large Files. Additionally, it has