System Management Release Notes
4.21 Monitor Utility Changes
4.21.2 Version-to-Version Compatibility of MONITOR Data
Because the body of data MONITOR collects can change at each release, it is not
always possible to view MONITOR data collected in one version on a different
version.
The level of compatibility between releases depends on whether you examine
recorded binary data from a file (that is, playback) or live data from another
cluster node. In general, playing back recorded data provides more compatibility
than monitoring live remote data.
4.21.3 Playing Back Data from a Recording File
Each file of recorded MONITOR binary data is identified by a MONITOR
recording file-structure level ID. You can see this ID by entering the DCL
command DUMP /HEADER /PAGE on the file. The following table lists some
recent MONITOR versions and their associated structure level IDs:
Operating System Version
MONITOR Recording
File Structure ID
OpenVMS Version 7.3-2 with remedial kit
1
MON31050
OpenVMS Versions 8.2, 8.2-1 with remedial kit
1
MON01060
OpenVMS Versions 8.3, 8.3-1H1, 8.4 MON01060
1
These remedial kits are proposed kits that might be issued for the sole purpose of providing improved
compatibility.
Usually, for you to be able to play back a single MONITOR recording file, the last
two digits of the structure level ID must match those of the running MONITOR
version. For example, if you are running OpenVMS Version 7.3-2, you can play
back a file from Version 7.3-2 but not one from Version 8.2.
However, MONITOR Versions 8.2 and higher are specially coded to read
recording files with structure level IDs ending in "50." In addition, a utility
in SYS$EXAMPLES, called MONITOR_CONVERT.C, converts a MONxx060 file
to a MON31050 file. This allows the resulting file to be read by versions prior
to Version 8.2. See MONITOR_CONVERT.C for instructions for building and
running the program.
Note that, even though you are allowed to play back a file, certain MONITOR
data classes within the file might not be available. This can happen if you
are using an older MONITOR version to play back a file created by a newer
MONITOR version.
Finally, note that, when you produce a multifile summary from several recording
files, all 8 characters of the structure level ID from all the files must match.
4.22 System Parameters
V8.3-1H1
This release also contains the new GH_RES_CODE_S2 parameter, which specifies
the size in pages of the resident 64-bit S2 space resident image code granularity
hint region.
Only images linked with the /SEGMENT=CODE=P2 qualifier can have code
placed in this region. See the HP OpenVMS Linker Utility Manual and the
INSTALL utility in the HP OpenVMS System Manager’s Manual for more
information.
System Management Release Notes 4–21
