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-23
Using OSS Commands to Manage Guardian Objects
Services User’s Guide provides examples of using the run utility and descriptions of
the run options.
Using OSS Commands to Manage Guardian
Objects
You can use some OSS utilities to manage Guardian processes and files as well as to
manage OSS objects. To manage Guardian objects, frequently requires that you use
the -W parameter, described following.
Accessing Guardian files is made possible by the /G and /E directories. This
subsection describes some of the more frequently used interoperability features. For a
detailed discussion of the OSS utilities described in this subsection, refer to the Open
System Services User’s Guide and Open System Services Shell and Utilities
Reference Manual.
Managing Guardian Processes From the OSS Shell
The OSS ps utility displays information on OSS processes. Additionally, you can use
the ps utility to display information on Guardian processes by using the -W parameter.
The following shows different ways of using the ps utility for Guardian processes:
ps -W all displays status of all Guardian processes.
ps -W name=/G/SVR1 displays status of Guardian process $SVR1.
ps -W cpu=5 displays status of all processes running in processor 5.
The OSS kill utility can be used to terminate Guardian and OSS processes. The
kill utility uses a signal named GUARDIAN for terminating Guardian processes.
The syntax to specify a Guardian process in a kill utility is /G/processname or
/G/cpu,pin. The following examples show each syntax. The first example terminates
the Guardian process named $SVR1; the second example terminates the Guardian
process 5,48:
kill -s GUARDIAN /G/SVR1
The equivalent Guardian command for this example is STOP $SVR1.
kill -s GUARDIAN /G/5,48
The equivalent Guardian command for this example is STOP 5,48.
Manipulating Guardian Files From the OSS Shell
This subsection provides information on accessing Guardian files and performing other
file operations such as moving, copying, listing, and changing attributes.