Open System Services Porting Guide (G06.24+, H06.03+)

Table Of Contents
Interoperating Between User Environments
Open System Services Porting Guide520573-006
4-19
Running the OSS Shell and Commands From TACL
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.
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
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.