Previous Topic: Version NumbersNext Topic: OS/400 Installation Procedures


Version Installation Procedures

The installation process should be as simple and as automatic as possible. Often, it will be sufficient merely to use the OS/400 Restore Object (RSTOBJ) and Restore library (RSTLIB) commands—whether this is the case will depend upon the nature of the objects being shipped.

Execution objects, for example, items that do not contain data, such as programs, device files and message files, may generally be restored on top of the existing versions. (N.B. device files cannot be in use while this is done.)

Data objects, for example, items that contain data, such as database files and data areas, cannot generally be restored directly without losing the user’s existing data. They must, therefore, either be installed under a different name and be renamed after data conversion, or be installed to a different library and moved after data conversion.

It may also be necessary to rebuild any logical views that are based upon physical files that have been changed. In either case, a conversion program will need to be run to copy and or convert data from the existing files. It should be possible to run any data conversion procedures in one of two ways:

Note: To ensure upward compatibility, new software versions should include any necessary conversion programs.