Binder Manual - NonStopTools

1 Binder ManualAbstractThis Manual describes Binder , the product that reads, links, and produces object files. This Manual is a user's guide and reference Manual for software developers who need to link and modify object VersionT9621 at and D30 Supported Release Version Updates (RVUs)This Manual supports and all subsequent D-series RVUs, and all subsequent G-series RVUs, and and all subsequent H-series RVUs until otherwise indicated in a new NumberPublished528613-003 July 2005 Document History Part NumberProduct VersionPublished48509 Binder C30 September 1991085670 Binder D10 January 1993109641 Binder D30 December 1994528613-001 Binder D30 August 2004528613-003T9621 2005 Hewlett-Packard Company 528613-003iBinder ManualGlossaryIndexFiguresTablesWhat s New in This ManualviiManual InformationviiNew and Changed InformationviiAbout This ManualixNotation Conventionsix1. IntroductionDefinition of binding1-1 Forms of Binder1-2 BINSERV1-2 BIND1-3 Languages Used with Binder1-4 Relation of Binder to Crossref, Inspect, and the Accelerator1-52.

2 Using BinderRunning Binder2-1 Manual Operation2-1 Command File Operation2-2 Examples2-2 Defining the Target File2-3 Specifying Input File Names2-3 Specifying the Target File Order2-4 Binding Modules2-5 Binding Rules2-6 Examples2-9 Binding COBOL85 and FORTRAN Programs2-10 Binding C Programs2-11 Binding Pascal Programs2-12 Binding Mixed-Language Programs2-13 Parameter Checking for a Mixed-Language Bind2-14 Binding SQL Program Files2-14 Resolving External References2-16 ContentsBinder Manual 528613-003ii2. Using Binder (continued)2. Using Binder (continued)Specifying a Different Volume for Binder Work Files2-17 When Using BIND2-18 When Using BINSERV2-18 Specifying the Swap Volume for Pascal and C Programs2-18 Generating Output Listings2-19 Target File Statistics2-19 Load Maps2-21 Cross-Reference Lists2-253. BIND CommandsSummary of Most Commonly Used Commands3-2 How to Use BIND Commands Efficiently3-3 Searching for Files3-3 Replacing Procedures3-3 Turning off Load Maps3-4 Binding without Fixups3-4 Syntax Conventions for Name Lists as Command Elements3-4 ADD Command3-6 ALTER Command3-9 BUILD Command3-10CD Command3-14 CHANGE Command3-15 CLEAR Command3-18 COMMENT Command3-18 DELETE Command3-19 DUMP Command3-20 ENV Command3-22 EXIT Command3-22FC Command3-22 FILE Command3-23 HELP Command3-23 INFO Command3-24 LIST Command3-27 LMAP Command3-31 LOG Command3-31 MODE Command3-32 MODIFY Command3-33 MOVE Command3-35 ContentsBinder Manual 528613-003iii3.

3 BIND Commands (continued)3. BIND Commands(continued)OBEY Command3-37 OUT Command3-38 RENAME Command3-39 REPLACE Command3-40 RESELECT Command3-42 RESET Command3-44 SATISFY Command3-46 SELECT Command3-48 SET Command3-56 SHOW Command3-65 STRIP Command3-73 SYSTEM Command3-75 VERIFY Command3-75 VOLUME Command3-764. Object File StructureCode Blocks, Entry Points, and Data Blocks4-1 Code Blocks4-1 Primary and Secondary Entry Points4-2 Data Blocks4-4 Object File Format4-8 Header4-9 Code Region4-9 Data Region4-11 Accelerator Region4-11 Inspect Region4-11 Binder Region4-115. Binder Input and OutputThe Input Control Lists5-1 Creating the Input Control Lists5-2 How Binder Uses the Input Control Lists5-3 The Target File5-8 Target File Attributes5-8 How Binder Builds the Target File5-11 ContentsBinder Manual 528613-003iv6. User Libraries6. User LibrariesBinding User-Library Procedures6-1 Object File Format6-2 Preventing Binder Resolution of Library Calls6-2 Compilation-Time Binding6-2 Command-Driven Binding6-2 Specifying a User Library6-3 Restrictions on User Libraries6-3 Shared Run-Time Libraries6-4 Building Applications That Use SRLs6-4 Using Binder Commands With SRLs6-4 Reserving Space With the SET RESERVE Command6-57.

4 Guardian File Names and TACL CommandsDisk File Names7-1 Parts of a Disk File Name7-2 Partial File Names7-3 Logical File Names7-4 Internal File Names7-4 TACL Commands7-4 TACL DEFINE Commands7-5 Substituting a File Name7-5 TACL DEFINE Names7-5 Setting DEFINE CLASS Attributes7-6 TACL PARAM Commands7-7 PARAM BINSERV Command7-7 PARAM SAMECPU Command7-7 PARAM SWAPVOL Command7-8 PARAM SYMSERV Command7-8 Using PARAM Commands7-8 TACL ASSIGN Commands7-9 ContentsBinder Manual 528613-003v8. Binder Messages8. Binder MessagesError Messages and Warnings8-1 Completion Codes8-289. Syntax SummaryGlossaryIndexFiguresFigure : Compilation-Time Binding1-3 Figure : Command-Driven Binding1-4 Figure References2-17 Figure File Statistics2-20 Figure Entry Point Map for Entry Points and Code Blocks2-22 Figure Point Map by Location for Multiple Code Segments2-23 Figure Load Maps for Data Blocks2-24 Figure for Read-Only Data Blocks2-25 Figure Listing2-26 Figure of the Binder Object File Format4-8 TablesTa b l e 1 -1.

5 Languages used with Binder1-4Ta b l e 2 - 1 .Target File Specifications built by Binder2-4Ta b l e 2 - 2 . Binder Grouping of ENV Directive Parameters2-7Ta b l e 2 - 3 .Run-Time Environment Resulting From Binding Modules2-9Ta b l e 2 - 4 .Commands that Produce Listings2-19Ta b l e 2 - 5 . Binder Statistics2-20Ta b l e 2 - 6 .Information Included in Load Maps for Entry Points2-22Ta b l e 2 - 7 .Information Included in Load Maps for Data Blocks2-24Ta b l e 3 - 1 .Commonly Used BIND Commands3-2Ta b l e 3 - 2 .Syntax Conventions for Named Lists3-4Ta b l e 3 - 3 .Resulting Target Processor Type3-62Ta b l e 4 - 1 .Code Block Attributes4-2Ta b l e 5 - 1 .Commands That Create Control Lists5-2Ta b l e 5 - 2 .Target File Attributes5-9Ta b l e 6 - 1 . Binder Commands Used With Shared Run-Time Libraries6-5Ta b l e 8 - 1 . Binder Completion Codes8-28Ta b l e 9 - 1 . Binder Command Summary9-1 ContentsBinder Manual 528613-003viBinder Manual 528613-003viiWhat s New in This ManualManual InformationBinder ManualAbstractThis Manual describes Binder , the product that reads, links, and produces object files.

6 This Manual is a user's guide and reference Manual for software developers who need to link and modify object VersionT9621 at and D30 Supported Release Version Updates (RVUs)This Manual supports and all subsequent D-series RVUs, and all subsequent G-series RVUs, and and all subsequent H-series RVUs until otherwise indicated in a new History New and Changed InformationThis revision describes the changes and additions made to the D30 product version of Binder (T9621) and the Binder Manual . This revision also incorporates support for T9621 on TNS/E systems running software. Summary of ChangesThis edition of the Manual includes previously undocumented warnings and messages for the Binder product. The changes include: This publication has been updated to reflect new product NumberPublished528613-003 July 2005 Part NumberProduct VersionPublished48509 Binder C30 September 1991085670 Binder D10 January 1993109641 Binder D30 December 1994528613-001 Binder D30 August 2004528613-003T9621 2005 What s New in This ManualBinder Manual 528613-003viiiSummary of Changes Because the product names are changing over time, this publication might contain both HP and Compaq product names.

7 Product names in graphic representations are consistent with the current product interface. Section 8, Binder Messages now includes the descriptions of error 770, fatal error 233, and warning 234. The message text for error 15 and warning 106 has now been updated to match the current product interface. The description of the USERLIBRARY attribute is changed in Section 3, BIND One, the Introduction, has been extended to include an introduction to The Object Code Accelerator (OCA) on page following commands have been enhanced to support TNS/E usage: CHANGE Command on page 3-15 RESET Command on page 3-44 SET Command on page 3-57 SHOW Command on page 3-67 STRIP Command on page Manual 528613-003ixAbout This ManualNotation ConventionsHypertext LinksBlue 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 Syntax NotationThis list summarizes the notation conventions for syntax presentation in this letters indicate keywords and reserved words.

8 Type these items exactly as shown. Items not enclosed in brackets are required. For example:MAXATTACH lowercase italic italic letters indicate variable items that you supply. Items not enclosed in brackets are required. For example:file-namecomputer 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 computer 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[ ] enclose optional syntax items. For example:TERM [\system-name.]$terminal-nameINT[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 ManualBinder Manual 528613-003xGeneral Syntax Notationeach side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines.

9 For example:FC [ num ] [ -num ] [ text ]K [ X | D ] address{ } 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 vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces. For example:INSPECT { OFF | ON | SAVEABEND }.. 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:" " , commas, semicolons, and other symbols not previously described must be typed as shown.

10 For example:error := NEXTFILENAME ( file-name ) ;LISTOPENS SU $process-name.#su-nameQuotation 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 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-nameAbout This ManualBinder Manual 528613-003xiNotation for MessagesLine 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 ].