Programming Release Notes
5.26 Hypersort Utility
5.26.5 Using Hypersort with Search Lists and Other Uses of Logical Names
Permanent Restriction
Hypersort does not fully support search lists and logical names used for input
files and work files. If you encounter this problem, use SORT32.
5.26.6 Lack of Free Space for Work Files
Permanent Restriction
Hypersort does not properly terminate if free space is exhausted in all available
sort work files. To avoid this problem, do one of the following:
• Allocate sufficient free space for the devices used for sort work files.
• Use SORT32 to detect that work file space has been exhausted.
5.26.7 Input Asterisk (*) Restriction
Permanent Restriction
Hypersort does not support asterisk (*) as an input file specification.
5.26.8 Optimal Working Set Extent and Page File Quota Settings
Permanent Restriction
SORT32 and Hypersort use different sorting and work file algorithms.
The relative speed of these utilities depends on the input file and the
memory/disk/CPU configuration. Make sure that the working set extent is
no more than one third of the page file quota. Both SORT32 and Hypersort
perform best with a working set extent appropriate to a specific input file.
5.27 Intel Assembler (Integrity servers Only)
Permanent Restriction
All modules written in Intel assembly language must contain appropriate
unwind directives, either by automatic generation using the -Xunwind flag or by
explicitly placing unwind directives into the source module. Without accurate
unwind information, the operating system’s condition handling and exception
dispatching does not work, and your program fails in unexpected ways. Programs
without accurate unwind information are not supported by OpenVMS. This is a
permanent requirement.
5.28 Librarian Utility
The following release notes pertain to the Librarian Utility and Library Service
routines.
5.28.1 Linking Against Data-Reduced ELF Object Libraries Not Recommended
(Integrity servers Only)
V8.2
DCX data-reduced ELF object libraries are not stored in contiguous space in
the library. As a result, the module cannot be directly mapped into process P2
space because data expansion must first occur. The LBR$MAP_MODULE library
service expands and copies the module into process P2 space. This action causes
the resulting pages in P2 space to be counted against process quota.
5–24 Programming Release Notes
