Open System Services Management and Operations Guide (G06.30+, H06.08+, J06.03+)

for its own startup. However, not configuring or starting $NULL or $ZSMP could affect the
functioning of other products or subsystems.
• If $NULL or $ZSMP is already running and not configured as a generic object, and you have
used the EASYSETUP^STARTUP param to specify $NULL or $ZSMP, you must stop it before
you can use OSSSETUP to configure it as a generic object. To stop $NULL, use the TACL STOP
command. To stop $ZSMP, use the SAFECOM STOP command. If you are not using the
EASYSETUP^STARTUP param to specify either of these processes, these processes are ignored.
• If you want to start $ZSMP, the full Safeguard product must be installed on your system for
you to:
◦ Run OSSSETUP
◦ Add user ID aliases
◦ Configure the INITIAL-DIRECTORY attribute for a user ID
• The OSSSETUP utility and the files it creates must be appropriately secured for access by users
other than the super ID, according to your site’s security guidelines.
• The OSSSETUP command installs all code and text files from current pax archive files in the
ZOSSUTL subvolume into the filesets it creates. The ZOSSUTL subvolume is in the $SYSTEM
volume, you override this location using the EASYSETUP^UTILVOL param.
• The OSSSETUP command does not define users or user attributes such as INITIAL-DIRECTORY
in the security database.
• You cannot use this command from a remote Expand node.
• You cannot use this command from the system startup TACL session ($YMIOP.#CLCI). You
should use a Telserv session instead.
• If you have installed the SPI definition files in a volume other than $SYSTEM, you must use the
EASYSETUP^EMSVOL param to specify the volume on which these files are installed. The
default value for this param is $SYSTEM. You are not required to have installed SPI definition
files, but if the SPI definition files are not installed in the specified location, this utility will not
generate EMS events.
• Fileset mount points should be checked after installation to ensure that they have security
permissions consistent with your site’s security policies. The OSS shell chmod command can
be used to modify permissions as necessary.
• Beginning with the J06.16 and H06.27 RVUs, the OSSSETUP utility automatically creates
symbolic links for the TCP/IP configuration files in the OSS environment, under the /etc
directory. You do not need to manually create the symbolic links, which was required in earlier
RVUs.
If you have installed the TCP/IP configuration files in a subvolume other than the default
installation subvolume, $SYSTEM.ZTCPIP, you must use the EASYSETUP^TCPIP^SUBVOL param
to specify the subvolume on which these files are installed. For an example of using the
EASYSETUP^TCPIP^SUBVOL param, see “Examples” (page 402).
STARTOSS Utility
The STARTOSS utility starts the processes and filesets previously configured through the OSSSETUP
utility or subsequently added to the OSSINFIL file. STARTOSS is intended for use after a system
load or after the STOPOSS utility has been used.
EasySetup Utilities 405