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
Introduction to Porting
Open System Services Porting Guide—520573-006
1-10
Comparing Commands Between Environments
•
Typical source and target execution environment and exceptions to the typical
pairs
•
How to call OSS and Guardian functions and procedures and when to use them
•
Available editors, development and initial debugging on a workstation, and
transferring the code to a NonStop system
The remainder of this guide discusses most of the topics listed here, but usually
without the detail in the Open System Services Programmer’s Guide, because this
guide focuses on topics as they relate to porting. You will find, however, all of
Section 2, The Development Environment, centers on many development and
debugging tasks.
Comparing Commands Between Environments
Unlike a UNIX system, Open System Services is administered through software with
interactive interfaces in the Guardian environment. In general, this design means that
UNIX commands not specified in the POSIX.2 standard (refer to POSIX.2 Standard on
page 1-3) might not be available through the OSS shell. Utilities exist that allow an
OSS shell user to create and run Guardian scripts equivalent to UNIX commands that
are not OSS commands.
Table A-1 on page A-1 lists and compares Guardian commands with similar OSS
commands. This will help if you are familiar with the Guardian environment, and you
need to know equivalent OSS commands. For more information on each of the OSS
commands, refer to the online reference pages and the Open System Services User’s
Guide. For more information about the Guardian commands, refer to the Guardian
User’s Guide.
Table B-1 on page B-1 lists and compares OSS commands with similar Guardian
commands. This comparison should be helpful if your background comes from the
UNIX operating system, and you need to know equivalent Guardian commands. For
more information about the similar Guardian commands, refer to the Guardian User’s
Guide. For more information on each of the OSS commands, refer to the reference
pages either online or in the Open System Services User’s Guide.