HP OpenVMS Systems Documentation

HP OpenVMS Version 8.2 New Features and Documentation Overview

1. This command defines logical names and equivalents.
2. Each time you press Ctrl/T, the CPU and IO values increase, but the MEM and PF values do not, indicating that LIB$FIND_FILE is being called.

As shown in the following example, using an options file to set RMS_RELATED_CONTEXT to NO causes the link operation to finish immediately when it encounters the missing file.

$  DEFINE DSKD$ WORK4:[TEST.LINKER.OBJ.]
$  DEFINE RESD$ ROOT$, ROOT2$, ROOT3$, ROOT4$, ROOT5$, DISK_READ$:[SYS.]
$  DEFINE ROOT$ WORK4:[TEST.PUBLIC.TEST.]
$  DEFINE ROOT2$ WORK4:[TEST.LINKER.]
$  DEFINE ROOT3$ WORK4:[TEST.UTIL32.]
$  DEFINE ROOT4$ WORK4:[TEST.PUBLIC.]
$  DEFINE ROOT5$ WORK4:[TEST.PUBLIC.TMP.]
$  LINK/MAP/FULL/ CROSS /EXE=ALPHA.EXE SYS$INPUT:/OPTION
RMS_RELATED_CONTEXT=NO
RESD$:[TMPOBJ]A.OBJ,RESD$:[SRC]B.OBJ,RESD$:[SRC]C,DSKD$:[OBJ]D.OBJ
DSKD$:[OBJ]E,RESD$:[TMPSRC]F.OBJ,RESD$:[TEST]G.OBJ
RESD$:[SRC.OBJ]H,RESD$:[COM]DOES_NOT_EXIST.OBJ [Ctrl/Z]

%LINK-F-OPENIN, error opening DISK_READ$:[SYS.][COM]DOES_NOT_EXIST.OBJ; as input
-RMS-E-FNF, file not found
$

The Linker map has been enhanced with new information for OpenVMS I64 Linker. The Linker map comprises the following information, shown in Figure 7-1, Figure 7-2, Figure 7-3, Figure 7-4, Figure 7-5, Figure 7-6, Figure 7-7, and Figure 7-8.

• Object and image synopsis
• Cluster synopsis
• Image segment synopsis
• Program section synopsis
• Symbol cross reference
• Symbols by value
• Image synopsis
• Link run statistics

Callout descriptions describing new and changes portions of the Linker map are provided after the example Linker map.

Figure 7-1 Object and Image Synopsis and Cluster Synopsis

Figure 7-2 Image Segment Synopsis

Figure 7-3 Program Section Synopsis

Figure 7-4 Program Section Synopsis (Continued)

Figure 7-5 Symbol Cross Reference

Figure 7-6 Symbols by Value

Figure 7-7 Image Synopsis

Figure 7-8 Link Run Statistics

The following list correspond to the numbered items in the preceding figures:

1. Object and Image Synopsis. The Alpha section titled Object Module Synopsis has been renamed on I64 to Object and Image Synopsis.
2. Module/Image. The Alpha column Module Name has been renamed on I64 to Module/Image.
3. Attributes. New information has been added in the four columns titled Attributes. The first of the four columns indicates whether the search of the module is selective. If selective, "Sel" appears. If it is not selective, this column is blank.
   The second column indicates whether the module has call linkage information. If the module has linkage, "Lkg" appears. If the module does not have linkage, this column is blank.
   The third column indicates whether the module is compiled with the Reduced Floating Point model. If it is, "RFP" appears. If the module was not compiled with the Reduced Floating Point model, this column is blank. This designation is suppressed for shareable images.
   The fourth column indicates the whole program mode. Several abbreviations can appear in this column that are listed in the Key for Attributes section. The following example lists all of the possible abbreviations in the Keys for Attributes section. The Creation Date and Creator columns are truncated from this example; see the following map example for the the entire Object and Image Synopsis.

   Module/Image File Ident Attributes Bytes ------------ ---- ----- ---------------- ----- NONE V1.0 Lkg 568 DISK1:[JOE]NONE.OBJ;1 DNORM_CASE Lkg RFP Dnrm 504 DISK1:[JOE]DENORM_W.OBJ;1 FAST _CASE Lkg RFP Fast 504 DISK1:[JOE]FAST_W.OBJ;1 NEPCT_CASE Lkg RFP Inex 504 DISK1:[JOE]INEXACT_W.OBJ;1 SPCL _CASE Lkg RFP Spcl 504 DISK1:[JOE]SPECIAL_W.OBJ;1 UNDER_CASE Lkg RFP Undr 504 DISK1:[JOE]UNDERFLOW_W.OBJ;1 DG_FL_CASE Lkg RFP VXfl 504 DISK1:[JOE]VAXFLOAT_W.OBJ;1 DECC$SHR V8.2-00 Lkg 0 RESD$:[SYSLIB]DECC$SHR.EXE;1 SYS$PUBLIC_VECTORS X-2 Sel Lkg 0 RESD$:[SYSLIB]SYS$PUBLIC_VECTORS.EXE;1 Key for Attributes +------------------------------------------+ ! Sel - Module was selectively searched ! ! Lkg - Contains call linkage information ! ! RFP - Conforms to the reduced FP model ! ! VXfl - VAX Float FP model ! ! Dnrm - Denormal IEEE FP model ! ! Fast - Fast IEEE FP model ! ! Inex - Inexact IEEE FP model ! ! Undr - Underflow-to-zero IEEE FP model ! ! Spcl - Special FP model ! +------------------------------------------+

4. Cluster Synopsis. The Alpha section titled Image Section Synopsis has been divided into two sections for I64: Cluster Synopsis and Image Segment Synopsis. The Cluster Synopsis section no longer contains image sections, which on I64 are referred to as segments. Further, image sections are no longer printed for sharable images, which was formerly done on VAX map files whenever there was a possibility of having based shareable images. (Based shareable images are not allowed on Alpha or I64 systems.)
5. Cluster. The Cluster column shows clusters that were created for and used by the Linker, and the order in which they were processed.
6. Match, Majorid, and Minorid. The Match, Majorid, and Minorid columns show version criteria, if any.
7. Image Segment Synopsis. The Image Segment Synopsis section shows each image segment as it was created. It contains the remaining columns of the Image Section Synopsis on OpenVMS Alpha. The first column, Seg #, contains the image segment's number, which is used in the relocations that are applied to it. (See an analysis of an image for a display of the segment number in relocations.) The Alpha section Protection and Paging has been divided into two columns Protection and Attributes on I64. The column Global Section Name was eliminated.
8. If the module was compiled /TIE and the image is linked /NONATIVE only and if the image contains non-standard signatures, a separate segment will appear immediately after the short data segment (indicated by SHORT) that contains them.
9. The section attributes PIC, NOPIC are not valid attributes on I64 and were removed.
10. The Linker contributes storage for common or relaxed refdef symbols. It is marked with <Linker> under the Module/Image header. The section name is always named after the symbol. (This module was compiled with the default switch /EXTERN=RELAXED, and the variables ITMLST, FILLEN, FILLIM and IOSB are relaxed refdef symbols).
11. The Linker indicates which module made the initialization (if there was one) to sections which have the attributes OVR, REL and GBL with the designation "Initializing Contribution". If you get a multiple initializations error, the Linker will have two or more sections marked with the designation "Initializing Contribution", in order to help you debug an instance that has many contributors.
12. The Linker makes a contribution to the code segment containing trampolines (instructions with larger branches) or code to branch to another segment (either inside or outside the image). It is marked with <Linker> under the Module/Image header.
13. The designation of an external symbol has changed from Alpha maps. The prefix or suffix used on Alpha was RX, meaning relocatable and external. However, the Linker does not know whether an external symbol is relocatable or not. As a result, on I64 systems the prefix or suffix has been changed to X (external).
14. Keys for Special Characters. The keys for special characters have changed as follows:
    • On I64, the special character C appears for code address. When a function does not have a function descriptor assigned by the Linker, its value is its code address.
    • On OpenVMS Alpha, a universal symbol appeared once with its internal value. The map never displayed an external, universal value (its index into the symbol vector on I64). Universal symbols on I64 now appear once with a suffix of (U) defined by <Linker Option> to indicate the external value, and again, possibly with the prefix or suffix R, to indicate their internal value. If you had a symbol vector with an alias name the alias name appears with the universal value, and the internal name appears with the internal value. The prefixes and suffixes A and I (for Alias and Internal) on OpenVMS Alpha have been removed.
      For example, symbol_vector=(getjpi/internal_getjpi=procedure) yields:

      00000000 GETJPI (U) 00050098 R-INTERNAL_GETJPI

    • UNIX weak symbols, designated with UxWk, are a new addition to OpenVMS. They are similar to OpenVMS weak symbols; however, more than one symbol with a UNIX weak definition can be processed when linking multiple modules without producing a multiple definitions error. UNIX weak symbols are currently produced by the C++ compiler.
15. Quota Usage. A new section titled Quota Usage was added to the Link Run Statistics section to keep track of the quotas that are being used by the I64 Linker. If quota issues occur, the Linker is able to work around them. But the Linker outputs a special message to the Quota Usage section indicating, as best it can, what quota should be increased to improve performance. For example:

    Performance of this link operation could be improved by increasing quotas Quota related to status return: %SYSTEM-SECTBLFUL, process or global section table is full 2688 extra file I/O operations performed due to current process quota(s) 36 performed on object files; 2652 performed on library files

Table 8-1 describes any reorganization of the OpenVMS documentation set for OpenVMS Version 8.2. For this release, two new manuals are added to the OpenVMS Documentation Set, and three manuals have been archived. Also, the following manuals are again in hardcopy format:

• HP OpenVMS Management Station Overview and Release Notes
• COM, Registry, and Events for HP OpenVMS Developer's Guide

OpenVMS documentation is provided, in the following ways:

• Printed documentation
  If you need paper documents, you can purchase most OpenVMS manuals in the form of printed documentation sets. Individual OpenVMS hardcopy documents cannot be purchased separately but are available in kits. One exception is the Porting Applications from HP OpenVMS Alpha to HP OpenVMS Industry Standard 64 for Integrity Servers, which you can order in hardcopy.
• Online documentation on CD
  All OpenVMS manuals are available in online formats on CDs that also include the documentation for many associated products. You automatically receive the documentation CDs in your OpenVMS media kit.
• Online documentation on the OpenVMS documentation Web site
  You can preview or read any OpenVMS document, including archived manuals, on the OpenVMS Web site.
• Online help
  You can quickly display online help for OpenVMS commands, utilities, and system routines when you need task-related information.

The following sections describe each format in which OpenVMS documentation is provided and specifies the titles that are available in that format.

9.1 Printed Documentation

Some printed documentation comes with your OpenVMS Media Kit. All other printed manuals are orderable in kits. This section describes the OpenVMS printed documentation offerings, which are categorized as follows:

• Media kit
• Documentation sets:
  • Base
  • Full
  • Operating Environment Extensions
• System-integrated products
• Archived manuals

The OpenVMS Media Kit, for both OpenVMS Alpha and OpenVMS I64 systems, contains the documents you need to get started with the latest version of the OpenVMS operating system. Table 9-1 lists the books included in the OpenVMS media kit. The books you receive are determined by whether you are a new or a service customer. New customers receive all books; service customers receive only new books and books that have been updated since the last release.

OpenVMS documentation is available in the following documentation sets:

There is one common documentation set for both OpenVMS Alpha and OpenVMS I64 systems. OpenVMS Alpha documentation set and the OpenVMS I64 documentation set contain the identical books with one exception. The OpenVMS Alpha documentation set contains the COM, Registry, and Events for HP OpenVMS Developer's Guide, which is an Alpha-only document. Table 9-2 lists the manuals in the OpenVMS Base and Full Documentation sets. For a description of each manual, see Section 10.2.