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-21
Interactively Using TACL and the OSS Shell
The following example illustrates the execution of an interactive shell using OSSTTY
instead of Telserv. An OSS application (testprog) receives input interactively from a
Guardian process ($vhs, the Guardian virtual hometerm subsystem).
TACL> run osstty /name $tty, in $vhs, nowait/
TACL> osh -p /home/stu01/testprog < /G/tty/#stdin
OSSTTY is started with $vhs as its standard input. OSSTTY redirects this input to
/G/tty/#stdin, which is redirected to testprog.
See the Open System Services Management and Operations Guide for more
information on OSSTTY.
Interactively Using TACL and the OSS Shell
Most users want to switch from an interactive TACL session to an interactive OSS shell
and continue using the OSS shell. This operation is done with either of the following
commands:
osh -ls
osh
The symbol in front of the ls flag (in this case, “-”) determines whether login
initialization occurs when the OSS shell is started. See Factors Affecting Shell
Operation on page 4-5 for more information on OSS shell start-up files and login
initialization.
The Open System Services Shell and Utilities Reference Manual contains a complete
description of the osh(1) utility.
Running Guardian Commands From the OSS
Shell
This subsection describes running Guardian commands from the OSS shell and
getting information into the OSS environments. The OSS gtacl utility creates a
Guardian process to execute any of the following from a OSS shell:
•
A Guardian program
•
A Guardian command (OBEY) file
•
A Guardian command, routine, alias, or macro
The following examples present different ways of using the OSS gtacl utility.
•
The following command executes a single Guardian command:
gtacl -c 'FUP SECURE $DATA01.REPORT.JAN94,"AOAO"'
The single quotes (' ') are used to avoid any special processing of the $ and "
characters by the shell.