TNSVU User’s Guide Abstract This manual describes how to install and use TNSVU. TNSVU is an interactive tool for browsing the TNS/E region of TNS object files generated by the Object Code Accelerator (OCA). Using TNSVU you can view general information about a type-100 (TNS) object file, learn what procedures are in the file, and view sections of the TNS and OCA-generated TNS/E object code. Product Version NA Supported Release Version Updates (RVUs) This publication supports D40.
Document History Part Number Product Version Published 528143-001 NA April 2005 528143-002 NA July 2005 528143-003 NA September 2005
TNSVU User’s Guide Glossary Index Tables What’s New in This Manual iii Manual Information iii New and Changed Information About This Manual iv Related Manuals iv Notation Conventions iii iv 1. Introducing TNSVU 2. TNSVU Command Summary 3.
Glossary Contents Example of Viewing File Information 4-2 Viewing Individual Procedures 4-2 Example of Viewing Individual Procedures 4-2 Viewing a List of Procedures 4-3 Examples of Viewing a List of Procedures 4-3 Viewing Local Millicode Information 4-4 Examples of Viewing Local Millicode Information 4-4 Viewing Names of Millicode Routines 4-5 Example of Viewing Names of Millicode Routines 4-5 Viewing the Names of External Library Routines 4-5 Example of Viewing the Names of External Library Routines 4-5
What’s New in This Manual Manual Information TNSVU User’s Guide Abstract This manual describes how to install and use TNSVU. TNSVU is an interactive tool for browsing the TNS/E region of TNS object files generated by the Object Code Accelerator (OCA). Using TNSVU you can view general information about a type-100 (TNS) object file, learn what procedures are in the file, and view sections of the TNS and OCA-generated TNS/E object code.
About This Manual This user’s guide introduces software developers to TNSVU and its command set. The following sections provide reference and task information about this product: 1. Introducing TNSVU 2. TNSVU Command Summary 3. Using TNSVU 4. Viewing TNS or TNS/E Region Information Related Manuals In addition to the TNSVU User’s Guide, the following manuals could be helpful to application developers.
General Syntax Notation About This Manual [] 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 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.
Change Bar Notation About This Manual 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: The message types specified in the REPORT clause are different in the COBOL85 environment and the Common Run-Time Environment (CRE).
1 Introducing TNSVU TNSVU is an interactive tool that browses a static, type-100 TNS object file, including the TNS/E region generated by the Object Code Accelerator (OCA).
2 TNSVU Command Summary This section introduces the TNSVU command set. Table 2-1 displays commands alphabetically including a brief description of and any synonyms for each command. Table 2-1. TNSVU Commands (page 1 of 5) Commands 1 Description Synonyms ! Repeats the previous command. See Repeating a Command on page 3-4 for more information. None ENDLOG Closes a log file. See Logging a TNSVU Session to a File on page 3-3 for more information.
TNSVU Command Summary Table 2-1. TNSVU Commands (page 2 of 5) Commands 1 Description Synonyms HISTORY Displays up to the last 20 previously issued commands. See Reviewing Command History on page 3-4 for more information. H ICODE 2 Displays TNS/E and TNS instructions. See Viewing TNS/E and TNS Instruction Sequences on page 4-6 for more information. I IPFtoTNS 2 When you specify the virtual address of a TNS/E instruction, this command returns the TNS address of the corresponding TNS instruction.
TNSVU Command Summary Table 2-1. TNSVU Commands (page 3 of 5) Commands 1 Description Synonyms LOG Opens a text file so that TNSVU can record all text written to the screen, including commands you invoke during the session. See Logging a TNSVU Session to a File on page 3-3 for more information. None LOGAPPEND Appends all text written to the screen during a session to an already existing file. See Logging a TNSVU Session to a File on page 3-3 for more information.
TNSVU Command Summary Table 2-1. TNSVU Commands (page 4 of 5) Commands 1 Description Synonyms OPTIONS 2 Displays the translation options you enter for selected procedures in a TNS object file. See Viewing Translation Options on page 4-24 for more information. None PROCINFO 2 Displays general information about a procedure that exists in a file. See Viewing Individual Procedures on page 4-2 for more information. INFO PROCS 2 Displays information about each procedure in an object file.
TNSVU Command Summary Table 2-1. TNSVU Commands (page 5 of 5) Commands 1 Description Synonyms TNStoIPF 2 When you specify the TNS address of a TNS instruction, this command returns the virtual address of the corresponding TNS/E address. See Viewing Address Correspondence Between TNS and TNS/E Code on page 4-23 for more information. TNStoITANIUM VERSION 2 Displays the OCA tool version field of the OCA header. See Viewing OCA Version Information on page 4-1 for more information.
3 Using TNSVU This section describes how to complete basic tasks such as: • • • • • • • • • • Invoking TNSVU on page 3-1 Opening a TNS Object File with TNSVU on page 3-1 Understanding the TNSVU Banner on page 3-2 Entering TNSVU Commands on page 3-2 Logging a TNSVU Session to a File on page 3-3 Reviewing Command History on page 3-4 Repeating a Command on page 3-4 Using TNSVU Help on page 3-6 Using the OBEY Command on page 3-5 Example of Exiting TNSVU on page 3-7 For a list of TNSVU commands in alphabeti
Understanding the TNSVU Banner Using TNSVU For example, to open the file named myfile: > OPEN myfile >myfile To invoke TNSVU and open myfile at the same time: TNSVU myfile TNSVU - Mar 19 2005 16:13:22 Copyright Hewlett-Packard, 2000-2005 Viewing on Jan 11 16:06:07 2005 Opened file myfile myfile> You can also use the OPEN command to change the file you are currently browsing.
Logging a TNSVU Session to a File Using TNSVU command specifies a command as summarized in TNSVU Commands on page 2-1. If you enter a command name that TNSVU does not recognize, TNSVU displays an error and returns you to its command prompt where you can enter another command. For example, suppose you type the command HELLO: > HELLO *** Could not recognize the command: HELLO (type “help” for summary) > Logging a TNSVU Session to a File TNSVU allows you to record all commands and output to a text file.
TNSVU Usage Example Using TNSVU You do not need to use ENDLOG before exiting the TNSVU program. ENDLOG does not close the object file you are currently viewing. Exiting TNSVU automatically closes the log file.
Example of Repeating a Command Using TNSVU command-number is the number associated with the previously issued command as displayed by the HISTORY command. TNSVU displays an error message if the command-number is not assigned to a command, or is not available on the command history list. For more information, see Reviewing Command History on page 3-4. command-prefix is a string that represents the prefix of a previously issued command.
Example of Using the OBEY Command Using TNSVU Example of Using the OBEY Command This example shows results from using the OBEY command. calls4xx> obey myobj second CSEG 0 PEP# 03 TNS Base: Itanium code: 0x70420550 Implemented in C 023 TNS Size: Itanium bundles: 07 0x11 TNS Entry: 023 Itanium entry: 0x70420550 in source file \SIERRA.$YOSE.KAAWORK.CALLS4A Using TNSVU Help Use the HELP command to display a summary of all TNSVU commands or get help for a specific command.
Example of Exiting TNSVU Using TNSVU OCAHEADER AXCELHEADER DUMPPMAPS OPTIONS TNStoIPF IPFtoTNS XEP VERSION EXACTPTS OBEY • - Displays the Itanium region header. Displays the Axcel region header. Displays Pmaps. Displays translation options. Converts TNS address to Itanium. Converts Itanium address to TNS. Displays proc targets of XEP entries.
4 Viewing TNS or TNS/E Region Information This section describes how to use TNSVU commands to view different kinds of information in a TNS or TNS/E file.
Viewing File Information Viewing TNS or TNS/E Region Information Viewing File Information The FILEINFO command displays general information about a TNS object file previously opened using the OPEN command. File information includes the code segment the file occupies in user code space, the date the file was translated, and the build date of the OCA version. The FI command is a synonym for the FILEINFO command. FILEINFO Example of Viewing File Information This example shows what FILEINFO returns.
Viewing a List of Procedures Viewing TNS or TNS/E Region Information myfile> Viewing a List of Procedures The PROCS command displays the names of all procedures in a TNS object file previously opened using the OPEN command. This includes the TNS/E address and length and the TNS address for each procedure. PROCS without an argument lists all procedures in alphabetical order; the command can also display information by location. The command does not print information about local millicode routines.
Viewing Local Millicode Information Viewing TNS or TNS/E Region Information Viewing Local Millicode Information The LOCAL command displays information about a specified millicode routine in a TNS object file previously opened using the OPEN command. Local millicode routines reside in the TNS/E region of the TNS object file, not in a separate millicode library. Millicode routine information includes the TNS/E address and length of the routine.
Viewing Names of Millicode Routines Viewing TNS or TNS/E Region Information Viewing Names of Millicode Routines The MILLICODE command displays the names of emulation and shared millicode routines used by a TNS object file previously opened using the OPEN command. MILLICODE also displays the static number of calls to each shared millicode routine in the OCA-generated code. The MILLI command is a synonym for the MILLICODE command.
Viewing TNS or TNS/E Region Information Viewing TNS/E and TNS Instruction Sequences REPLY RECEIVEINFO READUPDATE READ POSITION OPEN NUMOUT NUMIN MYTERM myfile> Viewing TNS/E and TNS Instruction Sequences The ICODE command displays instruction sequences in a TNS object file previously opened using the OPEN command. When you specify a starting address, TNSVU displays both TNS/E and corresponding TNS instructions.
Viewing TNS or TNS/E Region Information Examples of Viewing TNS/E and TNS Instruction Sequences end on an exact point. If you do not specify a for-clause value, TNSVU displays to the end of the procedure or local millicode routine. octal-num is a 16-bit word offset within the given TNS code segment for the first TNS instruction in the sequence you want to view. octal-num is prefixed by a 0. CSEG is a required keyword required for multi-segment programs. It defaults to the first segment.
Viewing TNS or TNS/E Region Information Viewing Header Information The code is displayed with TNS/E instructions alongside the TNS instructions. This display includes extra instructions to start and end at exact points. myfile> ICODE mine + 072 • The following command requests that a minimum of 020 TNS instructions be printed alongside their analogous TNS/E instructions, starting 050 instructions past the beginning of the TNS procedure named mine.
Example of Viewing TNS Header Information Viewing TNS or TNS/E Region Information Example of Viewing TNS Header Information • The following example displays TNS header information for the calls4x file.
Viewing TNS or TNS/E Region Information Example of Viewing TNS Header Information Process subtype: 0 Ext data: C IPIL length (double): 0x4f IPFL length (double): 0x8 Not Axcel generated OK to translate with Axcel File addr of OCA header: 0x5800 Length of IPF region: 0x3094 Run in translated mode on TNS/E OK to translate with OCA XEPTableVaddr[7]: 0x0 XEPTableVaddr[8]: 0x0 XEPTableVaddr[9]: 0x0 XEPTableVaddr[10]: 0x0 XEPTableVaddr[11]: 0x0 XEPTableVaddr[12]: 0x0 XEPTableVaddr[13]: 0x0 XEPTableVaddr[14]:
Viewing TNS or TNS/E Region Information Example of Viewing TNS Header Information TotalDataLength: 0x1800 TotalIPFCodeLength: 0x1450 IPFCodeVaddr: 0x70420000 IPFCodeFaddr: 0x1800 PmapFaddr[0]: 0x800 PmapBaseVaddr[0]: 0x4ffffeb0 PmapLength[0]: 0x60c PmapFaddr[1]: 0xe0c PmapBaseVaddr[1]: 0x4ffffeb0 PmapLength[1]: 0x60c PmapFaddr[2]: 0x0 PmapBaseVaddr[2]: 0x4ffffeb0 PmapLength[2]: 0x0 PmapFaddr[3]: 0x0 PmapBaseVaddr[3]: 0x4ffffeb0 PmapLength[3]: 0x0 PmapFaddr[4]: 0x0 PmapBaseVaddr[4]: 0x4ffffeb
Example of Viewing TNS Header Information Viewing TNS or TNS/E Region Information ResidentDataVaddr[1]: 0x0 ResidentDataLength[1]: 0x0 ResidentDataVaddr[2]: 0x0 ResidentDataLength[2]: 0x0 ResidentDataVaddr[3]: 0x0 ResidentDataLength[3]: 0x0 ResidentDataVaddr[4]: 0x0 ResidentDataLength[4]: 0x0 ResidentDataVaddr[5]: 0x0 ResidentDataLength[5]: 0x0 ResidentDataVaddr[6]: 0x0 ResidentDataLength[6]: 0x0 ResidentDataVaddr[7]: 0x0 ResidentDataLength[7]: 0x0 ResidentDataVaddr[8]: 0x0 ResidentDataLeng
Example of Viewing TNS Header Information Viewing TNS or TNS/E Region Information IPFVaddr[7]: 0x70421450 IPFLength[7]: 0x0 IPFVaddr[8]: 0x70421450 IPFLength[8]: 0x0 IPFVaddr[9]: 0x70421450 IPFLength[9]: 0x0 IPFVaddr[10]: 0x70421450 IPFLength[10]: 0x0 IPFVaddr[11]: 0x70421450 IPFLength[11]: 0x0 IPFVaddr[12]: 0x70421450 IPFLength[12]: 0x0 IPFVaddr[13]: 0x70421450 IPFLength[13]: 0x0 IPFVaddr[14]: 0x70421450 IPFLength[14]: 0x0 IPFVaddr[15]: 0x70421450 IPFLength[15]: 0x0 IPFVaddr[16]: 0x7042
Example of Viewing TNS Header Information Viewing TNS or TNS/E Region Information LocalMillicodeLength[13]: 0x0 LocalMillicodeLength[14]: 0x0 LocalMillicodeLength[15]: 0x0 LocalMillicodeLength[16]: 0x0 LocalMillicodeLength[17]: 0x0 LocalMillicodeLength[18]: 0x0 LocalMillicodeLength[19]: 0x0 LocalMillicodeLength[20]: 0x0 LocalMillicodeLength[21]: 0x0 LocalMillicodeLength[22]: 0x0 LocalMillicodeLength[23]: 0x0 LocalMillicodeLength[24]: 0x0 LocalMillicodeLength[25]: 0x0 LocalMillicodeLength[26]: 0x0 LocalMil
Example of Viewing TNS Header Information Viewing TNS or TNS/E Region Information IPFResidentVaddr[19]: 0x0 IPFResidentLength[0]: 0x0 IPFResidentVaddr[20]: 0x0 IPFResidentLength[0]: 0x0 IPFResidentVaddr[21]: 0x0 IPFResidentLength[0]: 0x0 IPFResidentVaddr[22]: 0x0 IPFResidentLength[0]: 0x0 IPFResidentVaddr[23]: 0x0 IPFResidentLength[0]: 0x0 IPFResidentVaddr[24]: 0x0 IPFResidentLength[0]: 0x0 IPFResidentVaddr[25]: 0x0 IPFResidentLength[0]: 0x0 IPFResidentVaddr[26]: 0x0 IPFResidentLength[0]: 0
Viewing TNS or TNS/E Region Information Example of Viewing TNS Header Information Itanium Header Vaddr: 0x70400000 Code Space Vaddr: 0x70000000 The OCAHEADER command displays header information in the TNS/E region of an open TNS object file. IPFHEADER is a synonym for the OCAHEADER command.
Viewing TNS or TNS/E Region Information Example of Viewing OCA Header Information Example of Viewing OCA Header Information • The following example displays OCA header information for the calls4x file.
Viewing TNS or TNS/E Region Information Example of Viewing OCA Header Information TotalDataLength: 0x1800 TotalIPFCodeLength: 0x1450 IPFCodeVaddr: 0x70420000 IPFCodeFaddr: 0x1800 PmapFaddr[0]: 0x800 PmapBaseVaddr[0]: 0x4ffffeb0 PmapLength[0]: 0x60c PmapFaddr[1]: 0xe0c PmapBaseVaddr[1]: 0x4ffffeb0 PmapLength[1]: 0x60c PmapFaddr[2]: 0x0 PmapBaseVaddr[2]: 0x4ffffeb0 PmapLength[2]: 0x0 PmapFaddr[3]: 0x0 PmapBaseVaddr[3]: 0x4ffffeb0 PmapLength[3]: 0x0 PmapFaddr[4]: 0x0 PmapBaseVaddr[4]: 0x4ffffeb
Example of Viewing OCA Header Information Viewing TNS or TNS/E Region Information ResidentDataVaddr[0]: 0x0 ResidentDataLength[0]: 0x0 ResidentDataVaddr[1]: 0x0 ResidentDataLength[1]: 0x0 ResidentDataVaddr[2]: 0x0 ResidentDataLength[2]: 0x0 ResidentDataVaddr[3]: 0x0 ResidentDataLength[3]: 0x0 ResidentDataVaddr[4]: 0x0 ResidentDataLength[4]: 0x0 ResidentDataVaddr[5]: 0x0 ResidentDataLength[5]: 0x0 ResidentDataVaddr[6]: 0x0 ResidentDataLength[6]: 0x0 ResidentDataVaddr[7]: 0x0 ResidentDataLeng
Example of Viewing OCA Header Information Viewing TNS or TNS/E Region Information IPFVaddr[6]: 0x70421450 IPFLength[6]: 0x0 IPFVaddr[7]: 0x70421450 IPFLength[7]: 0x0 IPFVaddr[8]: 0x70421450 IPFLength[8]: 0x0 IPFVaddr[9]: 0x70421450 IPFLength[9]: 0x0 IPFVaddr[10]: 0x70421450 IPFLength[10]: 0x0 IPFVaddr[11]: 0x70421450 IPFLength[11]: 0x0 IPFVaddr[12]: 0x70421450 IPFLength[12]: 0x0 IPFVaddr[13]: 0x70421450 IPFLength[13]: 0x0 IPFVaddr[14]: 0x70421450 IPFLength[14]: 0x0 IPFVaddr[15]: 0x704214
Example of Viewing OCA Header Information Viewing TNS or TNS/E Region Information LocalMillicodeLength[12]: 0x0 LocalMillicodeLength[13]: 0x0 LocalMillicodeLength[14]: 0x0 LocalMillicodeLength[15]: 0x0 LocalMillicodeLength[16]: 0x0 LocalMillicodeLength[17]: 0x0 LocalMillicodeLength[18]: 0x0 LocalMillicodeLength[19]: 0x0 LocalMillicodeLength[20]: 0x0 LocalMillicodeLength[21]: 0x0 LocalMillicodeLength[22]: 0x0 LocalMillicodeLength[23]: 0x0 LocalMillicodeLength[24]: 0x0 LocalMillicodeLength[25]: 0x0 LocalMil
Example of Viewing OCA Header Information Viewing TNS or TNS/E Region Information IPFResidentVaddr[18]: 0x0 IPFResidentLength[0]: 0x0 IPFResidentVaddr[19]: 0x0 IPFResidentLength[0]: 0x0 IPFResidentVaddr[20]: 0x0 IPFResidentLength[0]: 0x0 IPFResidentVaddr[21]: 0x0 IPFResidentLength[0]: 0x0 IPFResidentVaddr[22]: 0x0 IPFResidentLength[0]: 0x0 IPFResidentVaddr[23]: 0x0 IPFResidentLength[0]: 0x0 IPFResidentVaddr[24]: 0x0 IPFResidentLength[0]: 0x0 IPFResidentVaddr[25]: 0x0 IPFResidentLength[0]: 0
Viewing TNS or TNS/E Region Information Viewing Address Correspondence Between TNS and TNS/E Code Largest TNS code seg number: 0x1 Itanium Header Vaddr: 0x70400000 Code Space Vaddr: 0x70000000 Viewing Address Correspondence Between TNS and TNS/E Code TNStoIPF displays the TNS/E address equivalent closest to the exact point before the specified TNS location. Exact points are locations where the TNS code stream and the TNS/E code stream are synchronized.
Viewing TNS or TNS/E Region Information Example of Viewing Address Correspondence Between TNS/E and TNS Code Example of Viewing Address Correspondence Between TNS/E and TNS Code • The following command displays the address correspondence for TNS/E bundle 0X70420af0.
Viewing TNS or TNS/E Region Information Examples of Viewing the EXternal Entry Point Table Examples of Viewing the EXternal Entry Point Table • This example shows an EXternal Entry Point table listing produced for an object file called calls4xx.
Examples of Viewing Exact Point Locations Viewing TNS or TNS/E Region Information If you specify an argument for EXACTPT other than by procname or filename, TNSVU returns an error message. Examples of Viewing Exact Point Locations • This example shows a listing produced for all exact point locations in the file called calls4. As this listing can be extensive, this example shows information for only two exact point locations.
Examples of Viewing Exact Point Locations Viewing TNS or TNS/E Region Information • This example shows a listing produced for all exact point locations in the procedure called B. calls4xx> exact B Exact Points for procedure B CodeSeg Offset IPFAddress Slot IsRegisterExact 1 053 0x70421380 0 yes 35.000 1 054 0x704213e0 0 yes 36.000 1 055 0x70421440 0 yes 41.
Glossary absolute pathname. An Open System Services (OSS) pathname that begins with a slash (/) character and is resolved beginning with the root directory. Contrast with relative pathname. accelerate. To speed up emulated execution of a TNS object file by applying the Accelerator for TNS/R system execution or the Object Code Accelerator (OCA) for TNS/E system execution before running the object file. accelerated mode. See TNS accelerated mode. accelerated object code.
AXCEL Glossary AXCEL. The command used to invoke the Accelerator on a TNS/R or TNS/E system. Binder. A programming utility that combines one or more compilation units’ TNS object code files to create an executable TNS object code file for a TNS program or library. Used only with TNS object files. Binder region. The region of a TNS object file that contains header tables for use by the Binder program. binding.
client Glossary client. A software process, hardware device, or combination of the two that requests services from a server. Often, the client is a process residing on a programmable workstation and is the part of an application that provides the user interface. The workstation client might also perform other portions of the application logic. client application. An application that requests a service from a server application. Execution of remote procedure calls is an example of a client application.
Glossary cpu, pin cpu, pin. In the Guardian environment, a number pair that uniquely identifies a process during the lifetime of the process, consisting of the processor (CPU) number and the process identification number (PIN). See also PID. data segment. A virtual memory segment holding data. Every process begins with its own data segments for program global variables and runtime stacks (and for some libraries, instance data). Additional data segments can be dynamically created.
enoft utility Glossary the emulated system. For example, a TNS/R or TNS/E system emulates the behavior of a TNS system when executing interpreted or accelerated TNS object code. enoft utility. A utility that reads and displays information from TNS/E native object files. See also noft utility. EPTRACE. A performance investigation tool for Open System Services (OSS) and Guardian environments running H-series RVUs.
file Glossary file. An object to which data can be written or from which data can be read. A file has attributes such as access permissions and a file type. In the Open System Services (OSS) environment, file types include regular file, character special file, block special file, FIFO, and directory. In the Guardian environment, file types include disk files, processes, and subdevices. file description. See open system. file identifier.
flat segment Glossary architecture (for example, an adapter) is called firmware. Some firmware for ServerNet components is downloaded when the system or component is loaded. flat segment. A type of logical segment. Each flat segment has its own distinct address range within the process address space that never overlaps the range of any other allocated segments. Thus all allocated flat segments for a process are always available for use concurrently. See also logical segment and selectable segment.
Glossary HP NonStop™ operating system user ID HP NonStop™ operating system user ID. A user ID within an HP NonStop system. The Guardian environment normally uses the structured view of this user ID, which consists of either the group-number, user-number pair of values or the group-name.user-name pair of values. For example, the structured view of the super ID is (255, 255).
import control Glossary import control. The characteristic of a loadfile that determines from which other loadfiles it can import symbol definitions. The programmer sets a loadfile’s import control at link time. That import control can be localized, globalized, or semiglobalized. A loadfile’s import control governs the way the linker and loader construct that loadfile’s searchList and affects the search only for symbols required by that loadfile. import library.
instance data Glossary the same program simultaneously. Also, instance data refers to global data of a program or library. Each process has its own instance of the data. instance data. For each process using a dynamic-link library, a data segment area containing the global variables used by the library. interactive mode. A mode of operation that is characterized by having the same input and output device (a terminal or a process) for the session.
library Glossary library. A generic term for a collection of routines useful in many programs. An object code library can take the form of a linkfile to be physically included into client programs, it can be an OSS archive file containing several linkable modules, it can be a loadfile, or it can be a system-managed collection of preloaded routines. Source-code libraries fall outside the scope of this glossary. See also dynamic-link library (DLL) and shared runtime library (SRL). library client.
loadfile Glossary run-time loader and run-time linker. The loader for TNS and for TNS/R native programs and libraries that are not position-independent code (PIC) is part of the operating system. For PIC loadfiles, a loader called RLD works with the operating system to load programs and libraries. loadfile. An executable object code file that is ready for loading into memory and executing on the computer.
memory manager Glossary as they would be if the object file were running in TNS interpreted mode or on a TNS system. Most source statement boundaries are memory-exact points. Complex statements might contain several such points: at each function call, privileged instruction, and embedded assignment. Contrast with register-exact point and nonexact point. memory manager. An HP NonStop™ operating system process that implements the paging scheme for virtual memory.
MIPS RISC word Glossary MIPS RISC word. An instruction-set-defined unit of memory. A MIPS RISC word is 4 bytes (32 bits) wide, beginning on any 4-byte boundary in memory. Contrast with TNS word and word. See also Intel® Itanium® word. native. An adjective that can modify object code, object file, process, procedure, and mode of process execution.
nonexact point Glossary nonexact point. A code location within an accelerated object file that is between memoryexact points. The mapping between the TNS program counter and corresponding RISC instructions is only approximate at nonexact points, and interim changes to memory might have been completed out of order. Breakpoints cannot be applied at nonexact points. Contrast with memory-exact point and register-exact point. noninteractive mode.
OCA-generated Itanium instructions Glossary An OCA-accelerated object file contains the original TNS object code, the OCAaccelerated object code and related address map tables, and any Binder and symbol information from the original TNS object file. An OCA-accelerated object file also can be augmented by the Accelerator with equivalent MIPS RISC instructions. OCA-generated Itanium instructions. See Intel® Itanium® instructions. OCI. See TNS Object Code Interpreter (OCI). object code library.
Open Systems Interconnection Layer 2 Glossary Open Systems Interconnection Layer 2. The data-link control level of the Open Systems Interconnection (OSI) model, composed of asynchronous or minimal line control protocols, byte-oriented or character-oriented protocols, and bit-synchronous or bit-oriented protocols.
portable application Glossary portable application. An application that can execute on a wide range of hardware systems from multiple manufacturers. A portable application is a program that can be moved with little or no change in its source code from another manufacturer’s system to an HP NonStop™ system. portable filename character set. The set of characters that includes the Roman uppercase and lowercase letters, the Arabic numerals, the period, the underscore, and the hyphen.
process group lifetime Glossary process group lifetime. In the Open System Services (OSS) environment, the period that begins when a process group is created and ends when the lifetime of the last remaining process of the group ends. process ID. In the Guardian environment, the content of a 4-integer array that uniquely identifies a process during the lifetime of the process. See also PID. process identification number (PIN). A number that uniquely identifies a process running in a processor.
reconfiguration Glossary reconfiguration. The act of changing the hardware or software configuration of a running system. Examples include installing a new software release version update (RVU), adding hardware peripherals, and restructuring a database. Reconfiguring a system might or might not require a planned outage. reduced instruction-set computing (RISC).
RISC instructions Glossary RISC instructions. See MIPS RISC instructions. RISC processor. An instruction processing unit (IPU) that is based on reduced instruction-set computing (RISC) architecture. TNS/R processors contain RISC processors. rld library. A library that loads position-independent code (PIC) programs and their associated dynamic-link libraries (DLLs). The rld library also provides the dlopen(), dlclose(), dlresultcode(), dlsys(), and dlerror() functions. run-time linker. See linker.
server application Glossary Servers are designed to receive request messages from clients or requesters; perform the desired operations, such as database inquiries or updates, security verifications, numerical calculations, or data routing to other computer systems; and return reply messages to the clients or requesters. A server process is a running instance of a server program. server application. An application that provides a service to a client application.
static translation Glossary static translation. A TNS translation step explicitly invoked from the command line before a TNS object file is executed. The Accelerator and the TNS Object Code Accelerator (OCA) are static translators. subvolume. A group of related files stored on a disk. All the files have the same volume and subvolume name, but each file has a unique file identifier. super ID. On HP NonStop™ systems, a privileged user who can read, write, execute, and purge all files on the system.
System Library (SL) Glossary System Library (SL). See TNS code space. system library. A logically distinct part of the HP NonStop™ operating system that consists of user-callable library procedures and kernel procedures. system process. (1) A privileged process that comes into existence at system-load time and exists continuously for a given configuration for as long as the processor remains operable.
TNS compiler Glossary Library (SL). UC and UL exist on a per-process basis. SC and SL exist on a per-node basis. TNS compiler. A compiler in the TNS development environment that generates 16-bit TNS object code following the TNS conventions for memory, stacks, 16-bit registers, and call linkage. The TNS C compiler is an example of such a compiler. Contrast with TNS/R native compiler and TNS/E native compiler. TNS Emulation Library.
TNS loading Glossary TNS loading. A task performed at process startup time when executing a TNS object file. This task involves mapping the TNS instructions, procedure entry-point (PEP) table, and external entry-point (XEP) table from a TNS object file into memory. TNS mode. The operational environment in which TNS instructions execute by inline interpretation. See also accelerated mode and TNS/R native mode. TNS object code.
TNS State Library for TNS/E Glossary TNS State Library for TNS/E. A library of routines to access and modify the TNS state of a TNS process running on TNS/E. TNS system library. A collection of HP-supplied TNS-compiled routines available to all TNS processes. There is no per-program or per-process customization of this library. All routines are immediately available to a new process. No dynamic loading of code or creation of instance data segments is involved. See also native system library.
TNS/E native object code Glossary TNS/E native object code. The Intel®® Itanium® instructions that result from processing program source code with a TNS/E native compiler. TNS/E native object code executes only on TNS/E systems, not on TNS systems or TNS/R systems. TNS/E native object file. An object file created by a TNS/E native compiler that contains Intel® Itanium® instructions and other information needed to construct the code spaces and the initial data for a TNS/E native process.
TNS/R native object file Glossary TNS/R native object file. An object file created by a TNS/R native compiler that contains MIPS RISC instructions and other information needed to construct the code spaces and the initial data for a TNS/R native process. TNS/R native process. A process initiated by executing a TNS/R native object file. Contrast with TNS process and TNS/E native process. TNS/R native shared run-time library (TNS/R native SRL).
user library Glossary user library. (1) An object code file that the operating system links to a program file at run time. A program can have only one user library. See also TNS user library,TNS/R native user library, and TNS/E native user library. (2) A library loadfile associated with a program so that it emulates the user library feature of the operating system on TNS systems. For position-independent code programs on TNS/R and TNS/E systems, the user library is a dynamic-link library.
Index A Abstract iii Accessing Help system 3-6 Address correspondence TNS to TNS/E 4-23 TNS/E to TNS 4-23 Appending a TNSVU session text to an existing file 3-3 B Beginning a TNSVU session 3-1 C Changing files during TNSVU session 3-2 CLONED command 2-2, 4-4 Command case sensitivity 2-1 Command entry error 3-3 D Displaying instruction sequences by procedure name 4-6 starting address 4-6 TNS starting address 4-6 TNS/E starting address 4-6 Displaying TNSVU help 3-6 Document history iii Documentation roadma
L Index Instruction sequences displaying TNS 4-6 displaying TNS/E 4-6 Invoking TNSVU 3-1 IPFHEADER command 2-3, 4-16 IPFtoTNS command 2-2, 4-23 usage examples 4-24 ITANIUMtoTNS command 2-2, 4-23 L Listing procedure names in file 4-3 LOCAL command 2-2, 4-4 usage examples 4-4 LOG command 2-3, 3-3 LOGAPPEND command 2-3, 3-3 Logging a TNSVU session to a file 3-3 M MAPIPFtoTNS command 2-2, 4-23 MAPITANIUMtoTNS coimmand 2-2 MAPITANIUMtoTNS command 4-23 MAPTNStoIPF command 2-5 MAPTNStoITANIUM command 2-5, 4-23
T Index T T16HEADER command 2-4, 4-8 TNS address and length 4-3 headers 4-8 instruction sequences 4-6 TNSHEADER command 2-4, 4-8 usage examples 4-9 TNStoIPF command 2-5, 4-23 usage examples 4-23 TNStoITANIUM command 2-5, 4-23 TNSVU banner 3-2 command case sensitivity 2-1 I 4-6 summary 2-1 command summary /2-5 commands CLONED 4-4 command synonyms 2-1 E 3-7 ENDLOG 3-3 EXACT 4-25 EXACTPT 4-25 EXACTPTS 4-25 EXT 4-5 EXTERNAL 4-5 EXTERNALS 4-5 FI 4-2 FILEINFO 4-2 HELP 3-6 HISTORY 3-4 ICODE 4-6 INFO 4-2 IPFHEADE
U Index TNS/E headers 4-8 instruction sequences 4-6 Translation options 4-24 Viewing Address Correspondence Between TNS/E addresses and TNS addresses 4-23 X U XEP command 2-5, 4-24 usage examples 4-24 User code space 4-2 User library names 4-5 Special Characters V ! command 2-1, 3-4 ? command 2-1, 3-6 VERSION command 2-5, 4-1 usage example 4-1 Viewing address correspondence between TNS and TNS/E code 4-23 address correspondence between TNS/E and TNS code 4-23 emulation millicode routines 4-5 exac
