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-11
Managing Processes From OSS
OSS shell commands is contained in the Open System Services User’s Guide and the
online reference pages.
Managing Processes From OSS
To obtain the status of OSS processes, use the OSS ps utility. This utility is equivalent
to the Guardian STATUS command.
Examples
To list all your OSS processes, use:
ps
To list all OSS processes except kernel processes, use:
ps -e
The -u parameter limits the output of ps to specific users. In the following example,
the -u parameter lists processes for the users admin, mark, and os.helen. The -l
parameter requests detailed information or a long listing of all of the processes found:
ps -l -u "admin mark os.helen"
To stop a process, use the OSS kill utility, which is equivalent to the Guardian STOP
command. In the following example, the command to terminate process 10206621 is:
kill 10206621
This kill utility is actually a general mechanism; it sends the default signal
(SIGTERM). Any signal can be sent to a process using this general form of the kill
utility. The process might “catch” the signal and perform some other function, it might
ignore the signal, or it might terminate the specified process.
The kill utility requires either a signal name or number and the OSS process ID
(PID). The signal is specified with the -s parameter.
In the following example, the process 10307524 is sent the SIGKILL signal, which
automatically terminates the process:
kill -s SIGKILL 10307524
SIGKILL is a special signal that cannot be ignored or caught.
See Managing Guardian Processes From the OSS Shell on page 4-23 for information
on using the kill utility to terminate a Guardian process.
Managing Files From OSS
In the OSS environment, several utilities provide file operations. In the Guardian
environment, the File Utility Program (FUP) is used to provide this function. The