Open System Services Porting Guide (G06.29+, H06.06+, J06.03+)

In this example, the show_define command displays the values of the unnamed DEFINE set just
created, and two add_define commands create the attributes unique to each DEFINE.
The following table shows the values of the DEFINEs created in this example.
=LEGAL=LETTERUnnamedAttribute
111COPIES
LASER02LASER01NoneLOC
100100100MAXPRINTPAGES
8466NonePAGESIZE
DEFINEs can be established and manipulated for use by invocations of Guardian programs and
Guardian commands from the OSS shell. (See “Running Guardian Commands From the OSS Shell”
(page 66).)
OSS Commands for the Guardian User
This subsection helps Guardian users understand the OSS commands and utilities. It contains
information on managing processes and files and on compiling and linking programs in an OSS
environment. Appendix A (page 198) contains a table of many common Guardian commands and
their functionally equivalent OSS shell commands. More information on working with the 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” (page 68) for information on using the
kill utility to terminate a Guardian process.
OSS Commands for the Guardian User 59