Open System Services Porting Guide (G06.24+, H06.03+)
Table Of Contents
- What’s New in This Manual
- About This Manual
- 1 Introduction to Porting
- 2 The Development Environment
- 3 Useful Porting Tools
- 4 Interoperating Between User Environments
- Purpose of Interoperability
- The OSS User Environment
- OSS Commands for the Guardian User
- Guardian Commands for the UNIX User
- OSS Pathname and Guardian Filename Conversions
- Running the OSS Shell and Commands From TACL
- Running Guardian Commands From the OSS Shell
- Running OSS Processes With Guardian Attributes
- Using OSS Commands to Manage Guardian Objects
- 5 Interoperating Between Programming Environments
- 6 OSS Porting Considerations
- 7 Porting UNIX Applications to the OSS Environment
- 8 Migrating Guardian Applications to the OSS Environment
- General Migration Guidelines
- C Compiler Issues for Guardian Programs
- Using New and Extended Guardian Procedures
- Using OSS Functions in a Guardian Program
- Interoperating With OSS Programs
- Starting an OSS Program From the Guardian Environment
- C Compiler Considerations for OSS Programs
- Porting a Guardian Program to the OSS Environment
- How Arguments Are Passed to the C or C++ Program
- Differences in the Two Run-Time Environments
- Which Run-Time Routines Are Available
- Use of Common Run-Time Environment (CRE) Functions
- Replacing Guardian Procedure Calls With Equivalent OSS Functions
- Which IPC Mechanisms Can Be Used
- Interactions Between Guardian and OSS Functions
- 9 Porting From Specific UNIX Systems
- 10 Native Migration Overview
- 11 Porting or Migrating Sockets Applications
- 12 Porting Threaded Applications
- A Equivalent OSS and UNIX Commands for Guardian Users
- B Equivalent Guardian Commands for OSS and UNIX Users
- C Equivalent Inspect Debugging Commands for dbx Commands
- D Equivalent Native Inspect Debugging Commands for dbx Commands
- E Standard POSIX Threads Functions: Differences Between the Previous and Current Standards
- Glossary
- Index
The Development Environment
Open System Services Porting Guide—520573-006
2-21
Using the noft and enoft Utilities on Native Program
Files
•
A single Inspect or Native Inspect command cannot accept both Guardian and
OSS filenames, with the exception of the Inspect SOURCE ASSIGN.
•
Core files, known as save or saveabend files in Inspect and as snapshot files in
Native Inspect, are named ZZSAnnnn.
•
You cannot use a Guardian filename while the Inspect systype is OSS.
Using the noft and enoft Utilities on Native Program Files
Three additional development utilities, the native linkers (ld, eld, and nld) and the
native object file tools (noft and enoft), are used with native object files. The Binder
program is used on TNS object files. For working with native object files, these tools do
not offer identical features, but they offer similar features.
The nld utility links non-position-independent code (non-PIC) TNS/R native object files
with libraries specified on the c89 command line to create an executable program. The
ld utility links TNS/R PIC object files with dynamic-link libraries (DLLs) to create a PIC
loadfile. The eld utility links TNS/E PIC object files with DLLs to create a PIC loadfile.
The PIC loadfile can be executed after being loaded into memory by the rld utility.
The noft utility reads and displays information from TNS/R native object files,
providing some debugging options not available with the Inspect debugger. The enoft
utility reads and displays information from TNS/E native object files, providing some
debugging options not available with the Native Inspect debugger.
You can display the following object file components with the noft and enoft utilities:
•
File headers
•
Program text and data
•
Symbol table and its component parts
•
Run-Time Data Units (RTDUs)
The ld, eld, nld, noft, and, enoft utilities can be used in the Guardian or OSS
environments. For details, refer to the following manuals:
•
ld Manual
•
eld Manual
•
rld Manual
•
nld Manual
•
noft Manual
•
enoft Manual
Note. You cannot use ld, eld, rld, nld, noft, or enoft on TNS or accelerated object files.