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-15
Managing Processes From TACL
Managing Processes From TACL
Within a Guardian environment, you can use the Guardian STATUS command to
obtain the status of Guardian processes. This is equivalent to the OSS ps utility.
Examples
To list the status of your current Guardian processes, use the following command at
the TACL prompt:
STATUS *, USER
The next example lists the status of all Guardian processes:
STATUS *
The following sample command lists all status information of all processes belonging to
the user named OSS.STU01. Note that parameters are separated by commas (,). The
second parameter is a keyword value pair (USER and OSS.STU01) separated by a
space. The DETAIL option specifies that the full set of status information is to be
displayed:
STATUS *, USER OSS.STU01, DETAIL
The following sample command lists status information of processes running in
processor 0. Both Guardian and OSS processes are displayed in the output:
STATUS 0
In this sample output, the OSS processes have an “x” in the second column and
program names whose subvolume names begin with ZYQ (the output is only a small
portion of the output for this command):
Process Pri PFR %WT Userid Program file Hometerm
$XM00 0,278 199 P 041 255,255 $SYSTEM.SYS00.MEASCTL $TA0.#T2
$IMON B 0,279 148 P 001 255,255 $SYSTEM.SYS00.IMON $OSP
$XCVR0 0,280 199 P 001 255,255 $SYSTEM.SYS00.COVERMON $TA0.#T2
X 0,281 150 000 1,174 $XPG.ZYQ00000.Z0000R24 $ZTNT.#PTY007
X 0,282 150 003 1,33 $XPG.ZYQ00000.Z0000R24 $ZTNT.#PTY003
X 0,284 150 000 255,255 $XPG.ZYQ00000.Z0000R24$ZTNT.#PTY000
In the Guardian environment, you specify a process in Guardian commands either by
name or by the processor and process identification number (PIN). The processor
number and PIN are separated by a comma (,); see the next example.
Guardian process names begin with a dollar sign ($) followed by a letter. The process
name can have up to five characters (excluding the $). The Guardian process names
in the previous sample output are $XM00, $IMON, and $XCVR0.
Use the Guardian STOP command to stop processes. The STOP command uses
either the process name or the processor number and PIN combination to access the
process. For example, the following two commands are equivalent:
STOP $SRVR
STOP 5,48