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

To list process names associated with commands being executed, use the Guardian STATUS
command for both OSS and Guardian process names. See “Guardian Commands for the UNIX
User” (page 62) for a sample output of the Guardian STATUS command. To obtain the status of
only OSS processes, use the OSS ps utility, discussed in “OSS Commands for the Guardian User”
(page 59).
OSS processes are identified by the program filename, with subvolume names beginning with
ZYQ. The program filename for the OSS process can be translated from a name in a Guardian
filename to an OSS pathname using the pname utility, as shown earlier. A Guardian filename
associated with Guardian processes can be translated to an OSS pathname with the gname utility.
NOTE: The ZYQ subvolumes have special restrictions. They are not accessible from the OSS
environment. From the Guardian environment, access is restricted to privileged users and the super
ID.
For more information on the ls command, refer to the ls(1) reference page either online or the
Open System Services Shell and Utilities Reference Manual. For more information on the Guardian
STATUS and FILES commands, refer to the Guardian User’s Guide.
Running the OSS Shell and Commands From TACL
This subsection discusses starting the OSS shell and running individual OSS commands from TACL.
The OSH utility provides access to the OSS environment. OSH can be used in one of two ways:
• To perform one OSS command, script, or program
• To switch back and forth from using TACL to using the OSS shell, both interactively
The remainder of this subsection contains several examples of using the OSH utility.
Performing a Single Command Under the OSS Shell
This example demonstrates how to execute a single OSS command under the control of the OSS
shell:
osh -c "ls -l /home/stu01/testfile"
Here an OSS shell is started; all standard login initialization takes place (/etc/profile and
$HOME/.profile); and the ls utility is run as a separate process. After the command executes,
you automatically exit the OSS shell and receive your TACL prompt.
Performing a Single Program Without Invoking the OSS Shell
The following example executes one program without invoking the OSS shell. No login initialization
takes place in this example:
osh -p /home/stu01/testprog -x
Starting an OSS Shell Script
You can start an OSS shell script in either of the ways shown in the previous two examples. The
results produced by the script can differ depending on the login initialization.
A script that depends on any login initialization such as aliases or functions can only execute
correctly with the -c option specified. The following command executes the shell script
/home/stu01/process_report:
osh -c "/home/stu01/process_report"
Redirecting Input and Output to a File
You can redirect input from a file to a command in the OSS environment using the left angle bracket
(<) operator. Output from a command, program, or script can be redirected to a file in the OSS
environment using the right angle bracket (>) operator.
Running the OSS Shell and Commands From TACL 65