HP eld User manual

eld Manual
Abstract
This manual describes how programmers can use eld, the object file linker for TNS/E,
to create loadfiles for execution on HP Integrity NonStop™ NS-series servers.
Product Version
N.A.
Supported Release Version Updates (RVUs)
This publication supports J06.03 and all subsequent J-series RVUs and H06.01 and all
subsequent H-series RVUs, until otherwise indicated by its replacement publications.
Part Number Published
527255-009 February 2012

Document History
Part Number Product Version Published
527255-004 N.A. July 2005
527255-005 N.A. May 2010
527255-007 N.A. August 2010
527255-008 N.A. May 2011
527255-009 N.A. February 2012

Legal Notices
© Copyright 2012 Hewlett-Packard Development Company L.P.
Confidential computer software. Valid license from HP required for possession, use or copying.
Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software
Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under
vendor's standard commercial license.
The information contained herein is subject to change without notice. The only warranties for HP
products and services are set forth in the express warranty statements accompanying such products
and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be
liable for technical or editorial errors or omissions contained herein.
Export of the information contained in this publication may require authorization from the U.S.
Department of Commerce.
Microsoft, Windows, and Windows NT are U.S. registered trademarks of Microsoft Corporation.
Intel, Itanium, Pentium, and Celeron are trademarks or registered trademarks of Intel Corporation or its
subsidiaries in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
Motif, OSF/1, UNIX, X/Open, and the "X" device are registered trademarks and IT DialTone and The
Open Group are trademarks of The Open Group in the U.S. and other countries.
Open Software Foundation, OSF, the OSF logo, OSF/1, OSF/Motif, and Motif are trademarks of the
Open Software Foundation, Inc.
OSF MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THE OSF MATERIAL PROVIDED
HEREIN, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS FOR A PARTICULAR PURPOSE.
OSF shall not be liable for errors contained herein or for incidental consequential damages in connection
with the furnishing, performance, or use of this material.
© 1990, 1991, 1992, 1993 Open Software Foundation, Inc. This documentation and the software to
which it relates are derived in part from materials supplied by the following:
© 1987, 1988, 1989 Carnegie-Mellon University. © 1989, 1990, 1991 Digital Equipment Corporation.
© 1985, 1988, 1989, 1990 Encore Computer Corporation. © 1988 Free Software Foundation, Inc.
© 1987, 1988, 1989, 1990, 1991 Hewlett-Packard Company. © 1985, 1987, 1988, 1989, 1990, 1991,
1992 International Business Machines Corporation. © 1988, 1989 Massachusetts Institute of
Technology. © 1988, 1989, 1990 Mentat Inc. © 1988 Microsoft Corporation. © 1987, 1988, 1989, 1990,
1991, 1992 SecureWare, Inc. © 1990, 1991 Siemens Nixdorf Informationssysteme AG. © 1986, 1989,
1996, 1997 Sun Microsystems, Inc. © 1989, 1990, 1991 Transarc Corporation.
This software and documentation are based in part on the Fourth Berkeley Software Distribution under
license from The Regents of the University of California. OSF acknowledges the following individuals
and institutions for their role in its development: Kenneth C.R.C. Arnold, Gregory S. Couch,
Conrad C. Huang, Ed James, Symmetric Computer Systems, Robert Elz. © 1980, 1981, 1982, 1983,
1985, 1986, 1987, 1988, 1989 Regents of the University of California.
Printed in the US

Hewlett-Packard Company—527255-009
i
eld Manual
Glossary Index Tables
Legal Notices
What’s New in This Manual v
Manual Information v
New and Changed Information v
About This Manual ix
Notation Conventions xi
1. Introduction to eld
eld Overview 1-1
Example Command Line 1-2
eld Functionality 1-2
Linker Version Information 1-3
Native Object Files 1-3
The Linker Command Stream 1-5
Obey Files and the Use of Standard Input 1-7
Example of Use 1-9
2. eld Input and Output
Host Platforms 2-1
Target Platforms 2-2
Filenames and The File Identifier 2-2
Output Object Files 2-4
The Creation of Output Object Files 2-5
Creating Segments of the Output Loadfile 2-6
Using a DLL Registry 2-8
Input Object Files 2-12
Using Archives 2-16
3. Binding of References
Overview 3-1
Presetting Loadfiles 3-5
To Preset or Not to Preset, and Creation of the LIC 3-7

Contents
eld Manual—527255-009
ii
4. Other eld Processing
Handling Unresolved References 3-8
Using User Libraries 3-10
Creating Import Libraries 3-11
Creating an Import Library at the Same Time That a DLL is Created 3-12
Creating Import Libraries From Existing DLLs 3-12
Ignoring Optional Libraries 3-14
Merging Symbols Found in Input Linkfiles 3-16
Accepting Multiply-Defined Symbols 3-17
Rules For Data Items 3-17
Rules for Procedures 3-18
Using the -cross_dll_cleanup option 3-19
Specifying Which Symbols to Export, and Creating the Export Digest 3-20
Processing of Code and Data Sections 3-21
Concatenating Code and Data Sections Found in the Input Linkfiles 3-21
Public Libraries and DLLs 3-22
The Public Library Registry 3-23
Finding and Reading The Public DLL Registry (ZREG) File 3-23
4. Other eld Processing
Adjusting Loadfiles: The -alf Option 4-1
Additional rules about -alf 4-3
The -set and -change Options 4-8
eld Functionality for 64-Bit 4-12
Checking the C++ Language Dialect 4-12
Renaming Symbols 4-13
Creating Linker-Defined Symbols 4-14
Updating Or Stripping DWARF Symbol Table Information 4-14
Modifying the Data Sections that Contain Stack Unwinding Information 4-15
Creating the MCB 4-15
Processing of Floating Point Versions and Data Models 4-16
Specification of the Main Entry Point 4-17
Specifying Runtime Search Path Information for DLLs 4-18
Merging Source RTDUs 4-19
5. Summary of Linker Options
6.
Output Listings and Error Handling
General Information 6-1
Error Messages 6-4

Contents
eld Manual—527255-009
iii
A. TNS/E Native Object Files
Glossary of Errors 6-126
A. TNS/E Native Object Files
The Object File Format A-1
Basic Properties of Object Files A-1
Types of TNS/E Object Files A-2
How to Distinguish the Different Types of Object Files A-3
Summary of the Contents of an Object File A-3
Code and Data Sections A-11
User Code A-12
User Data A-13
The MCB (Master Control Block) A-14
Predefined Symbols A-14
Relocation Tables A-16
How -alf Updates DWARF A-24
Finding Information About Procedures and Subprocedures in Linkfiles A-26
The DWARF Symbol Table A-26
Archives A-27
Tools That Work With Object Files A-29
Glossary
Index
Tables
Table 2-1. Parameters to the -instance_data Option 2-7
Table 4-1. The -set and -change Options 4-8
Table 5-1. Set Attributes 5-8
Table 6-1. Completion Codes - The Severity Levels of Messages 6-1
Table A-1. Types of TNS/E Object Files A-2
Table A-2. Contents of a Loadfile or Import Library A-5
Table A-3. Additional Predefined Symbols Optionally Created By The Linker In
Loadfiles A-15
Table A-4. Relocation Types A-18

Contents
eld Manual—527255-009
iv

eld Manual—527255-009
v
What’s New in This Manual
Manual Information
eld Manual
Abstract
This manual describes how programmers can use eld, the object file linker for TNS/E,
to create loadfiles for execution on HP Integrity NonStop™ NS-series servers.
Product Version
N.A.
Supported Release Version Updates (RVUs)
This publication supports J06.03 and all subsequent J-series RVUs and H06.01 and all
subsequent H-series RVUs, until otherwise indicated by its replacement publications.
Document History
New and Changed Information
Changes to the H06.24/J06.13 manual:
•In the section, The Steps in Looking for Archives and DLLs on page 2-17:
°Updated the fourth and fifth step and also added a new content on page 2-17.
°Updated information on 2-18.
•In the section, Additional rules about -alf on page 4-3:
°Updated the list on page 4-4.
•In the table, The -set and -change Options on page 4-8:
°Added a new entry on page 4-8.
Part Number Published
527255-009 February 2012
Part Number Product Version Published
527255-004 N.A. July 2005
527255-005 N.A. May 2010
527255-007 N.A. August 2010
527255-008 N.A. May 2011
527255-009 N.A. February 2012

What’s New in This Manual
eld Manual—527255-009
vi
Changes to the 527255-008 manual:
°Updated the information on the attributes for -set and -change option on
pages 4-9 and 4-10.
•Added eld Functionality for 64-Bit on page 4-12.
•In the table, Set Attributes on page 5-8:
°Added a new entry on page 5-8.
•In the title, Output Listings and Error Handling on page 6-1:
°Updated the message 1557 on page 6-95.
°Added a new message 1510 on page 6-77.
°Added a new message 1665 on page 6-124.
°Added a new message 1666 on page 6-124.
°Added a new message 1667 on page 6-125.
°Added a new message 1668 on page 6-125.
°Added a new message 1669 on page 6-125.
°Added a new message 1670 on page 6-125.
°Added a new message 1672 on page 6-125.
Changes to the 527255-008 manual:
•Added a new message 1132 on page 6-20.
Changes to the 527255-007 manual:
•Added the following linker options:
°-NS_extent_size extent-size on page 5-6
°-NS_max_extents max_extents on page 5-7
°-warn_common on page 5-12
•Updated systype attribute information under Target Platforms on 2-2.
•Added Using the -cross_dll_cleanup option on page 3-19.
•Added information about -cross_dll_cleanup on page 5-2.
•Added the following new messages:
°1233 on page 6-39 to 1236 on page 6-39
°1389 on page 6-69
°1391 on page 6-69
•Updated error message 1519 on page 6-79.

What’s New in This Manual
eld Manual—527255-009
vii
Changes to the 527255-005 Manual:
•Added applicability note for data2protected parameter support on page 2-7 and
3-16.
•Updated list of sections under Binding of References on page 3-1.
Changes to the 527255-005 Manual:
•Updated information on how the linker searches for indirect DLLs on page 2-12
and 2-19.
•Added consideration for -set libname on page 3-10.
•Added consideration for -change libname on page 4-10.
•Added the following error messages:
•1229 to 1232 on page 6-38
•1657, 1659, and 1660 on page 6-124

What’s New in This Manual
eld Manual—527255-009
viii
Changes to the 527255-005 Manual

eld Manual—527255-009
ix
About This Manual
This publication describes how programmers can use eld, the object file linker for
TNS/E, to create loadfiles for execution on H-series software NonStop servers.
Section 1, Introduction to eld consists of the following topics:
•eld Overview - explains the general functionality of the product.
•Native Object Files - introduces the different types of object files.
•The Linker Command Stream - shows the conventions for entering tokens
(options, parameters and filenames) on the command line.
•Example of Use - presents an example of using eld to link a main program and
a DLL .
Section 2, eld Input and Output consists of the following topics:
•Host Platforms - where the linker may be used.
•Target Platforms - where the output from the linker may be used.
•Output Object Files - what forms (libraries, loadfiles and DLLs) that output may
take.
•The Creation of Output Object Files - how you control that process.
•Creating Segments of the Output Loadfile - how parts of a loadfile are created.
•Using a DLL Registry - how you can manage DLL addressing.
•Input Object Files - which files you can use as input.
•Using Archives - how you can group multiple input or output files together.
Section 3, Binding of References consists of the following topics:
•Overview - an overview of symbol resolution and code relocation.
•Presetting Loadfiles - the process of resolving references to DLLs at linktime.
•To Preset or Not to Preset, and Creation of the LIC - eld rules for presetting.
•Handling Unresolved References - what happens if a symbol is not found in
any loadfile in the linker’s search list?
•Using User Libraries - introduces the libname options.
•Creating Import Libraries - three types are available.
•Ignoring Optional Libraries - a command stream toggle is available.

About This Manual
eld Manual—527255-009
x
•Finding and Reading The Public DLL Registry (ZREG) File - three ways to find
it.
Section 4, Other eld Processing consists of the following topics:
•Adjusting Loadfiles: The -alf Option - how to repeat the presetting of a loadfile
when DLLs change.
•The -set and -change Options - how to set various options within the loadfile.
•eld Functionality for 64-Bit - how the linker performs consistency checks.
•Renaming Symbols - how the linker treats each input file.
•Updating Or Stripping DWARF Symbol Table Information - from the input and
output object files.
•Modifying the Data Sections that Contain Stack Unwinding Information - when
concatenating sections to create a new loadfile.
•Creating the MCB - the Master Control Block contains key settings such as
product version numbers, valid file types, language dialects, and so on.
•Processing of Floating Point Versions and Data Models - more consistency
checks.
•Specification of the Main Entry Point - there are two ways to specify the main
entry point.
•Specifying Runtime Search Path Information for DLLs - eld tells rld where to
find the DLLs.
•Merging Source RTDUs - used with SQL/MP.
Section 5, Summary of Linker Options consists of a list and description of every linker
option.
Section 6, Output Listings and Error Handling consists of the following topics:
•General Information - when and how messages are created.
•Error Messages - individual cause, effect and recovery information.
•Glossary of Errors - a glossary of terms used in the error messages.
Appendix A, TNS/E Native Object Files consists of the following topics:
•The Object File Format - the types of object files and their content.
•Code and Data Sections - the "ordinary" code and data sections that come
from application source code, possibly with additions by the compiler or linker.

About This Manual
eld Manual—527255-009
xi
Notation Conventions
•Relocation Tables - when code is relocated, who resolves the address and
prepares relocation tables?
•Finding Information About Procedures and Subprocedures in Linkfiles - an
introduction to the .procinfo and .procnames sections of linkfiles.
•The DWARF Symbol Table - this table contains information used by debuggers
and the Cobol compiler.
•Archives - contains an extension of material covered in a previous section of
this manual.
•Tools That Work With Object Files - a quick look at which HP NonStop
operating system tools use object files.
Notation Conventions
The specific conventions for eld may be found in The Linker Command Stream on
page 1-5.
The conventions shown below are generic, applying to most manuals in the NonStop
Technical Library.
Hypertext Links
Blue underline is used to indicate a hypertext link within text. By clicking a passage of
text with a blue underline, you are taken to the location described. For example:
This requirement is described under Backup DAM Volumes and Physical Disk
Drives on page 3-2.
General Syntax Notation
This list summarizes the notation conventions for syntax presentation in most NonStop
manuals. Some of these conventions may not apply to this particular manual.
UPPERCASE LETTERS. Uppercase letters indicate keywords and reserved words. Type
these items exactly as shown. Items not enclosed in brackets are required. For
example:
MAXATTACH
lowercase italic letters. Lowercase italic letters indicate variable items that you supply.
Items not enclosed in brackets are required. For example:
file-name
computer type. Computer type letters within text indicate C and Open System Services
(OSS) keywords and reserved words. Type these items exactly as shown. Items not
enclosed in brackets are required. For example:
myfile.c

About This Manual
eld Manual—527255-009
xii
General Syntax Notation
italic computer type. Italic computer type letters within text indicate C and Open
System Services (OSS) variable items that you supply. Items not enclosed in brackets
are required. For example:
pathname
<filename>. TThis represents the name of a file. Filenames follow whatever rules apply to
the corresponding host platform when the linker needs to do something with the file.
For example, filenames are not case sensitive on Guardian or NT, but are case
sensitive on OSS. The linker keeps all filenames in the same form that they were
specified, unless otherwise stated in this document.
<symbol name> . This represents the name of a symbol as it appears within an object file.
It is case sensitive. There are rules that depend upon the source language for mapping
between the way the symbol appears in the source code and the way the symbol
appears within the object file. Each source language has its own rules for this.
<path> . This is the kind of string used in the -rld_L and -rld_first_L options.
<dllname>. This is the kind of string used in the -dllname option.
<location> . This is the kind of string used in the -L and -first_L options.
<number> . This indicates a 64-bit numerical value. It is interpreted as a hexadecimal
number if it begins with “0x”, “0X”, “%h”, or “%H”, in which case the rules given below
for a <hexadecimal number> apply. If it has none of these prefixes then it is interpreted
as a decimal number and the rest of the token must be a sequence of decimal digits.
The TNS/E linker does not accept octal numbers.
<hexadecimal number> . This indicates a 64-bit hexadecimal number, and may optionally
begin with “0x”, “0X”, “%h”, or “%H”. The letters “a” through “f” (representing the values
10 through 15) are not case sensitive. Periods are allowed in hexadecimal numbers to
subdivide the number for readability, using one of the following two methods. There
may be one period in the number, and then the period is assumed to divide the number
into two 32-bit portions. Or, there may be three periods, in which case the periods are
assumed to divide the number into four 16-bit portions.
<attribute> and <value>. These notations are explained under the description of the -set
option.
[ ] Brackets. Brackets enclose optional syntax items. For example:
TERM [\system-name.]$terminal-name
INT[ERRUPTS]
A group of items enclosed in brackets is a list from which you can choose one item or
none. The items in the list can be arranged either vertically, with aligned brackets on

About This Manual
eld Manual—527255-009
xiii
General Syntax Notation
each side of the list, or horizontally, enclosed in a pair of brackets and separated by
vertical lines. For example:
FC [ num ]
[ -num ]
[ text ]
K [ X | D ] address
{ } Braces. A group of items enclosed in braces is a list from which you are required to
choose one item. The items in the list can be arranged either vertically, with aligned
braces on each side of the list, or horizontally, enclosed in a pair of braces and
separated by vertical lines. For example:
LISTOPENS PROCESS { $appl-mgr-name }
{ $process-name }
ALLOWSU { ON | OFF }
| Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed in
brackets or braces. For example:
INSPECT { OFF | ON | SAVEABEND }
… Ellipsis. An ellipsis immediately following a pair of brackets or braces indicates that you
can repeat the enclosed sequence of syntax items any number of times. For example:
M address [ , new-value ]…
[ - ] {0|1|2|3|4|5|6|7|8|9}…
An ellipsis immediately following a single syntax item indicates that you can repeat that
syntax item any number of times. For example:
"s-char…"
Punctuation. Parentheses, commas, semicolons, and other symbols not previously
described must be typed as shown. For example:
error := NEXTFILENAME ( file-name ) ;
LISTOPENS SU $process-name.#su-name
Quotation marks around a symbol such as a bracket or brace indicate the symbol is a
required character that you must type as shown. For example:
"[" repetition-constant-list "]"
Item Spacing. Spaces shown between items are required unless one of the items is a
punctuation symbol such as a parenthesis or a comma. For example:
CALL STEPMOM ( process-id ) ;
If there is no space between two items, spaces are not permitted. In this example, no
spaces are permitted between the period and any other items:
$process-name.#su-name

About This Manual
eld Manual—527255-009
xiv
Notation for Messages
Line Spacing. If the syntax of a command is too long to fit on a single line, each
continuation line is indented three spaces and is separated from the preceding line by
a blank line. This spacing distinguishes items in a continuation line from items in a
vertical list of selections. For example:
ALTER [ / OUT file-spec / ] LINE
[ , attribute-spec ]…
!i and !o. In procedure calls, the !i notation follows an input parameter (one that passes data
to the called procedure); the !o notation follows an output parameter (one that returns
data to the calling program). For example:
CALL CHECKRESIZESEGMENT ( segment-id !i
, error ) ; !o
!i,o. In procedure calls, the !i,o notation follows an input/output parameter (one that both
passes data to the called procedure and returns data to the calling program). For
example:
error := COMPRESSEDIT ( filenum ) ; !i,o
!i:i. In procedure calls, the !i:i notation follows an input string parameter that has a
corresponding parameter specifying the length of the string in bytes. For example:
error := FILENAME_COMPARE_ ( filename1:length !i:i
, filename2:length ) ; !i:i
!o:i. In procedure calls, the !o:i notation follows an output buffer parameter that has a
corresponding input parameter specifying the maximum length of the output buffer in
bytes. For example:
error := FILE_GETINFO_ ( filenum !i
, [ filename:maxlen ] ) ; !o:i
Notation for Messages
This list summarizes the notation conventions for the presentation of displayed
messages in this manual.
Bold Text. Bold text in an example indicates user input typed at the terminal. For example:
ENTER RUN CODE
?123
CODE RECEIVED: 123.00
The user must press the Return key after typing the input.
Nonitalic text. Nonitalic letters, numbers, and punctuation indicate text that is displayed or
returned exactly as shown. For example:
Backup Up.

About This Manual
eld Manual—527255-009
xv
Change Bar Notation
lowercase italic letters. Lowercase italic letters indicate variable items whose values are
displayed or returned. For example:
p-register
process-name
[ ] Brackets. Brackets enclose items that are sometimes, but not always, displayed. For
example:
Event number = number [ Subject = first-subject-value ]
A group of items enclosed in brackets is a list of all possible items that can be
displayed, of which one or none might actually be displayed. The items in the list can
be arranged either vertically, with aligned brackets on each side of the list, or
horizontally, enclosed in a pair of brackets and separated by vertical lines. For
example:
proc-name trapped [ in SQL | in SQL file system ]
{ } Braces. A group of items enclosed in braces is a list of all possible items that can be
displayed, of which one is actually displayed. The items in the list can be arranged
either vertically, with aligned braces on each side of the list, or horizontally, enclosed in
a pair of braces and separated by vertical lines. For example:
obj-type obj-name state changed to state, caused by
{ Object | Operator | Service }
process-name State changed from old-objstate to objstate
{ Operator Request. }
{ Unknown. }
| Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed in
brackets or braces. For example:
Transfer status: { OK | Failed }
% Percent Sign. A percent sign precedes a number that is not in decimal notation. The
% notation precedes an octal number. The %B notation precedes a binary number.
The %H notation precedes a hexadecimal number. For example:
%005400
%B101111
%H2F
P=%p-register E=%e-register
Change Bar Notation
Change bars are used to indicate substantive differences between this manual and its
preceding version. Change bars are vertical rules placed in the right margin of
changed portions of text, figures, tables, examples, and so on. Change bars highlight
new or revised information. For example:

About This Manual
eld Manual—527255-009
xvi
Change Bar Notation
The message types specified in the REPORT clause are different in the COBOL85
environment and the Common Run-Time Environment (CRE).
The CRE has many new message types and some new message type codes for
old message types. In the CRE, the message type SYSTEM includes all
messages except LOGICAL-CLOSE and LOGICAL-OPEN.