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-22
Running OSS Processes With Guardian Attributes
•
The following command line executes the Guardian STATUS command and directs
the output to the grep utility by using a pipe character (|). grep finds all of the
processes (from the STATUS command output) currently executing the FUP
program:
gtacl -c 'STATUS *' | grep FUP
•
The following command line creates the /tmp/systemfiles file and places in it
the list of files on the $SYSTEM volume:
gtacl -p FUP INFO \$SYSTEM.\*.\* > /tmp/systemfiles
•
A Guardian command file can be started using gtacl. In the following example,
the command file $DATA01.REPORTS.MONTHLY is executed. Be sure to precede
the filename with a backslash (\):
gtacl -c 'OBEY \$DATA01.REPORTS.MONTHLY' &
The ampersand (&) instructs that the command file be run in background. When
using an ampersand, control returns to the user immediately after the command is
initiated.
For a complete description of the gtacl utility, refer to the gtacl(1) reference page
either online or in the Open System Services Shell and Utilities Reference Manual.
Running OSS Processes With Guardian
Attributes
The OSS run or runv utility enables you to execute OSS programs with attributes
specific to the Guardian environment, such as process names and processor numbers.
Following are examples of using the built-in run utility.
•
In the following example, the Guardian process name $SVR1 is assigned to an
OSS process:
run -name=/G/svr1 server
•
The following example specifies a processor in which a process is to run. This
process executes in processor 5 with the Guardian process name $SVR2:
run -name=/G/svr2 -cpu=5 server
•
The following example starts the testprog program running under the Inspect
debugger on TNS/R systems or the Native Inspect debugger on TNS/E systems,
or, if a Visual Inspect client connection has been established, the program is
started under the Visual Inspect debugger:
run -debug -inspect=on testprog
The Open System Services Shell and Utilities Reference Manual contains a complete
description of the run(1) and runv(1) utilities. Additionally, the Open System