HP 3000 Manuals HP 3000 Manuals
Backdating Occasionally it is necessary to reinstall an earlier version of MPE/iX after having updated a system to the latest release. This is called backdating a system. The HP 3000 MPE/iX Installation, Update, and Add-On Manual (36123-90001) provided with the MPE/iX software includes the information required for backdating a system.
NOTE Backdating a system is not a trivial task and should be done only if absolutely necessary. You should contact the Response Center before backdating. Response Center engineers may be able to help you solve the problem without having to backdate the system.
The introduction of the hierarchical file system at Releases 4.5 and 5.0 allows for the possible presence of hierarchical directories, files located outside groups, byte-stream files, FIFO files, symbolic link files, and device link files on MPE/iX systems. These new features could make it difficult to backdate MPE/iX Release 5.0 to an earlier release and could prevent the earlier version of MPE/iX from operating correctly. MPE/iX provides a program called BDREPORT to simplify backdating. You must back up the entire system before running this program and backdating your system. BDREPORT identifies any operating system incompatibilities (such as files and HFS directories existing outside of MPE groups) and produces two script files called BDSCRP1 and BDSCRP2. The script files contain the commands necessary to delete files and directories that would not be compatible with an earlier release of MPE/iX. Once the incompatibilities are identified, you can store the files and directories onto tape. You can then execute the scripts to correct other incompatibilities, such as files whose file labels, ACDs, or transaction management logs that are not compatible with the earlier release. Executing the BDSCRP1 script file does the following: * Purges the incompatible files and directories * Modifies file labels if required * Backdates transaction management for all mounted user volume sets Executing the BDSCRP2 script does the following: * Stores the directory structure * Backdates the user and group databases using PXUTIL * Backdates the system volume set transaction management logs After the incompatibilities are identified and handled using this process, you can backdate the system to the earlier release. You will then need to restore the user information that was backdated and any files you want to retain from the STORE tape.