|
|
Communicator 3000 MPE/iX Release 6.0 (Platform Software Release C.60.00): HP 3000 MPE/iX Computer Systems > Chapter 3 System Management Overview of HP Stage/iX |
|
by Venugopal Commercial Systems Division HP Stage/iX is an operating system facility for applying and managing MPE/iX patches on your system. Using HP Stage/iX reduces system downtime and provides an easy and reliable method for backing out patches. Use HP Stage/iX to place PowerPatch and/or reactive patches into staging areas on disk while the system is up, then choose a staging area to use at boot time to apply the patches. After the patches are applied, they can be backed out at any time through a reboot to the Base (the version applied by the last tape update). Once you are satisfied with the patches on the running system, you can commit the staging area to form a new Base while the system is running (no reboot is needed). HP Stage/iX is targeted for larger HP 3000 systems with adequate extra disk space. Since putting patches in staging areas requires that additional files be placed on disk, using HP Stage/iX uses a lot of disk space. Adequate disk space on LDEV1 is especially critical, since a large percentage of patches require changes to large files that must be staged on LDEV1 (NL.PUB.SYS is an example).
HP Stage/iX has three interfaces:
Your operating system resides in what HP Stage/iX refers to as the Base. This is the set of files laid down by the last system installation or update (from tape). HP Stage/iX creates and manages staging areas, which are file containers on disk that hold versions of files that are different from the Base. (A staging area is actually an HFS directory which holds all the files associated with that staging area.) More than one staging area can exist at a time. Each staging area contains the difference, or delta, between the Base Operating System and a patched OS. When a staging area is activated on the next boot, the files in the staging area's directory are moved (renamed) into their natural locations. (For example, the staged version of the NL is moved into NL.PUB.SYS.) At the same time, the Base versions of the files are saved into an HP Stage/iX archive directory. When the staging area is backed out (when the system is booted back to the Base), the converse takes place, and the system is restored to its original state. When an active staging area is committed to the Base, the staging area's directory is deleted, and all archived Base files are purged. The files that were switched into their natural locations when the staging area was activated remain there as part of the new Base. This releases any disk space that was used by the staging area. HP Stage/iX (with the help of HP Patch/iX) allows new patches to be staged and applied in a cumulative fashion. If you create a new staging area while a staging area is active, the new staging area will contain all the changes between the Base and the active staging area, plus the new patches applied to the new staging area. HP Stage/iX is part of the Fundamental Operating System (FOS), and is therefore automatically installed when you update to OS version 6.0 or later. To be able to use HP Stage/iX you must:
Using the STAGEMAN utility, you can control and obtain information about your HP Stage/iX environment. The HP Stage/iX environment can be uninstalled any time there is no active staging area. This action deletes all staging areas and any files and directories that HP Stage/iX has built. This activity does not just turn off HP Stage/iX; it completely removes any and all files associated with the environment. There are two safety nets available for HP Stage/iX users: Title not available (Safety Features )
|
|