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
Migrating Guardian Applications to the OSS
Environment
Open System Services Porting Guide—520573-006
8-3
Migration Options
Migration Options
The first thing you need to do when you decide you want to add more openness to
your Guardian application is to decide how far you can or want to migrate your
application. The options available are as follows:
•
Add open functions to the Guardian application
•
Set up a communication channel with an OSS application
•
Migrate the Guardian application to the OSS environment
Some features are not supported in the OSS environment; thus, applications that
depend on these features cannot be migrated to the OSS environment. For example,
process pairs are not supported in the OSS environment.
However, even for programs that cannot be migrated completely to Open System
Services, the use of open functions can make your program more open and easier to
integrate with other open programs in the future.
In some cases, interprocess communication features can be added to a Guardian
application to set up communication channels with OSS applications. To make your
Guardian application as open as possible, and, therefore, in a position to access new
open facilities as they are introduced, you can migrate your application to run in the
OSS environment. The next few subsections introduce various aspects of migrating
your Guardian application.
Converting TAL or pTAL Code to C or C++
Many existing Guardian programs are written in TAL or pTAL, which are HP
programming languages; some of these programs are not CRE-compliant. Migrating
these programs to a more open environment involves writing or rewriting them in the C
or C++ language. To do this by hand is a tremendous undertaking. Some third-party
tools have been developed to help with the effort of converting TAL or pTAL programs
to C, but none of them do the complete job. Particularly, if the programs are not CRE-
compliant, much of the conversion effort must be done by hand.
Using New and Extended Guardian Procedures in Guardian
Programs
Extensions to existing Guardian procedures as well as open-oriented Guardian
procedures give Guardian applications better access to OSS features. The
manipulation of OSS objects from the Guardian environment provides a greater degree
of openness for the Guardian application program. In addition, using these procedures
and extended Guardian procedures make it easier to migrate a Guardian program to
the OSS environment in the future.
The Guardian procedures introduced and extended to promote this interoperability with
the OSS environment are documented under Using New and Extended Guardian
Procedures on page 8-10. These Guardian procedures support security, file system,
and process management in the OSS environment.