|
HP OpenVMS System Manager's Manual, Volume 1:... |
Customizing the Operating System |
|
|
| |
Registering Images that Have System Version Dependencies
Registering an image records information about the image in a file called the image registry. The image activator, INSTALL, and SYSGEN do not check the versions of images that are recorded in the image registry.
The image registry allows you to continue to run application images (including main images, shared libraries, and device drivers) that were linked on prior versions of the operating system. Use extreme care with this capability. If the image needs to use a data structure that has a changed format, then results from running the image will be unpredictable and might result in a system crash. Register an image only if you are sure that none of the referenced system routines, data cells, and data structures have changed.
The Image Registry facility allows you to register different versions of an image independently. It also allows you to deregister, analyze, and show images in the image registry.
Understanding System Version Dependency and
the Image Registry
Applications
that depend on internal interfaces are bound to a particular version
of the operating system when the application is linked. Version-dependent
images reference both of the following version numbers:
When you attempt to run an image, the system checks to determine if the image requires a certain version of the operating system or of system components. If the version of the running system does not match the version requirements of the image, the image fails.
The system also checks version numbers when you attempt to install an image using the Install utility (INSTALL) or connect a device driver using the System Generation utility (SYSGEN).
When you upgrade your system to a new version of the operating system, an image might fail because the new version no longer matches the image's version requirements. However, an image might continue to be compatible with the new operating system version, even if it fails the version check.
 | In OpenVMS VAX Version 6.0, the major version number
was not changed; only the version numbers for the following components
were increased to reflect changes in these areas:
In OpenVMS VAX Version 6.1, no version numbers were changed. However, images built on VMS VAX Version 5.x systems needed to be registered if they referenced FILES_VOLUMES, MEMORY_MANAGEMENT, or SECURITY. |
 | You must inspect and test an image carefully to avoid system crashes and data corruption. Registering an image does not necessarily make it work; registering only bypasses the version checks. |
Using the Image Registry Facility
To register an image in the image registry, run the command
procedure SYS$UPDATE:REGISTER_PRIVILEGED_IMAGE.COM. Enter a command
in the following format: $ @SYS$UPDATE:REGISTER_PRIVILEGED_IMAGE keyword filename
where:
|
keyword
|
Specifies one or more of
the keywords described in
REGISTER_PRIVILEGED_IMAGE.COM Keywords, separated by commas.
|
|
filename
|
Specifies the name and location of the
image you want to register. The filename parameter accepts wildcard characters.
|
If the image does not have a version dependency, the following message is displayed:
REGISTER-I-SUMMARY n images examined, n have dependenciesIn this message, n is the number of images examined and the number of images that have dependencies.
The following example adds the V6USRAPP image to the registry:
$ @SYS$UPDATE:REGISTER_PRIVILEGED_IMAGE REGISTER SYS$LIBRARY:V6USRAPP %REGISTER-I-ADDED added V6USRAPP to registry
|
|
