Open System Services Management and Operations Guide (G06.25+, H06.03+)
Managing OSS Files
Open System Services Management and Operations Guide—527191-002
6-7
Using COPYOSS
From the archive files, COPYOSS copies the OSS product files into the OSS file
system, placing them in locations where you would find them on a typical UNIX
system—for example, into directories such as /bin, /usr/ucb, and
/usr/include.
This command completely installs the basic OSS product set and all other products
that use the same installation subvolume.
•
To load only the Java servlet product files, enter these commands from a TACL
prompt:
$tsvvol.ZOSSUTL.COPYOSS $tsv1.T0094PAX
tsvvol
is the disk volume where DSM/SCM put your basic OSS product set TSVs.
$tsv1
is the disk volume and subvolume where DSM/SCM put the NonStop Java
Server TSVs.
T0094PAX
is the pax archive containing the Java servlet files.
See the copyoss(8) reference page either online or in the Open System Services
Shell and Utilities Reference Manual for more information about command options.
Considerations
•
COPYOSS exists only in the target subvolume used for installation of the basic
OSS product set. If that subvolume is deleted after installation, your system will not
have the COPYOSS file. You can save the COPYOSS file to the $SYSTEM disk
volume if you need to use it again.
•
Do not use COPYOSS unless explicitly told to when DSM/SCM installs and
maintains OSS product files in your OSS file system (when the DSM/SCM Manage
OSS Files check box is selected).
•
Files installed by COPYOSS are not always secured in conformance with the best
practices at your site. You should always resecure files installed by COPYOSS. For
example, after installing SQL/MX files, you might enter commands such as the
following to secure the installed software and the directories it uses:
find / -WNOE -WNOG \( -type d -o -type f \) -perm -o+w |
xargs chmod o-w
chmod a=rwxt /tmp /usr/tmp /var/tmp /var/preserve
/usr/tandem/sqlmx/USERMODULES
•
Under rare conditions, the PINSTALL command used by COPYOSS can return an
error message that indicates a disk file could not be found; this message can be
ignored when the named file is an empty directory in the corresponding pax