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
Interoperating Between User Environments
Open System Services Porting Guide—520573-006
4-4
Scopes of Interoperability
Scopes of Interoperability
There are a number of views of interoperability between the OSS and Guardian
environments. They can be divided into three job responsibilities or audiences:
•
Those who develop application program interfaces (APIs), applications, and other
programs. To perform their jobs, this group relies on development tools including
editors, development utilities, compilers, linkers, optimizers, debuggers, and
performance analyzers. They work with entities such as run-time libraries, files,
functions, processes, and so forth. For more information on these topics and this
scope of interoperability, refer to the list of related programming guides in About
This Manual on page xx.
•
Those who provide system support and maintenance. This group manages and
controls the production, change, performance, problems, and daily system
operations of large systems and networks. To perform their jobs, this group relies
on utilities, applications, tools, and many other facilities. They work with logs (audit,
error, operator), physical devices (terminals, printers, tape drives, small and large
computers), and many other communications and distributed computing devices.
For more information on these topics and this scope of interoperability, refer to the
Open System Services Management and Operations Guide.
•
Those who use a NonStop system or other system to perform their daily job
responsibilities, which can be any task related to developing code or managing
computer systems. This group, usually called “users,” works mostly with the files
and interactive command interfaces of the OSS and Guardian environments.
The remainder of this section covers interoperating between user environments. For
more information on this scope of interoperability, refer to the Open System Services
User’s Guide.
The OSS User Environment
This subsection focuses on the factors that affect the operation of the OSS shell. It
includes an overview of OSS shell operations: start-up files, shell variables, functions,
command settings, and command editing modes. Refer to the Open System Services
User’s Guide for detailed information on working with the OSS shell.
OSS Shell
Most UNIX systems provide three shells for the interactive user: the Korn, Bourne, and
C shells. The OSS shell is compliant with the POSIX.2 standard (which is based on the
Korn shell). It has the same programming syntax as the Bourne shell but adds new
facilities for better interactive use.