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-19
Running the OSS Shell and Commands From TACL
from a name in a Guardian filename to an OSS pathname using the pname utility, as
shown earlier. A Guardian filename associated with Guardian processes can be
translated to an OSS pathname with the gname utility.
For more information on the ls command, refer to the ls(1) reference page either
online or the Open System Services Shell and Utilities Reference Manual. For more
information on the Guardian STATUS and FILES commands, refer to the Guardian
User’s Guide.
Running the OSS Shell and Commands From
TACL
This subsection discusses starting the OSS shell and running individual OSS
commands from TACL. The OSH utility provides access to the OSS environment. OSH
can be used in one of two ways:
•
To perform one OSS command, script, or program
•
To switch back and forth from using TACL to using the OSS shell, both interactively
The remainder of this subsection contains several examples of using the OSH utility.
Performing a Single Command Under the OSS Shell
This example demonstrates how to execute a single OSS command under the control
of the OSS shell:
osh -c "ls -l /home/stu01/testfile"
Here an OSS shell is started; all standard login initialization takes place
(/etc/profile and $HOME/.profile); and the ls utility is run as a separate
process. After the command executes, you automatically exit the OSS shell and
receive your TACL prompt.
Performing a Single Program Without Invoking the OSS Shell
The following example executes one program without invoking the OSS shell. No login
initialization takes place in this example:
osh -p /home/stu01/testprog -x
Note. The ZYQ subvolumes have special restrictions. They are not accessible from the OSS
environment. From the Guardian environment, access is restricted to privileged users and the
super ID.