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

Table 3 Currently Used TACL PARAMs for the OSS Monitor (continued)
DescriptionPARAM
value for the FSCKCPU attribute of the subsystem. If this PARAM is
supplied after the first execution of the OSS Monitor, it replaces the current
value for the FSCKCPU attribute of the subsystem. This value is kept in
the ZOSSPARM file and controlled through the SCF ALTER SUBSYS
command. See “ALTER SUBSYS, ALTER MON, and ALTER PROCESS
Commands” (page 285) for more information about the values that can
be specified.
Defines the amount of time that the OSS Monitor normally waits for a
response from an OSS name server. For longer requests where the OSS
OSS^NAMESERVER^TIMEOUT seconds
name server cycles through the disk volumes in an OSS fileset, the OSS
Monitor will wait up to 10 times the IOTIMEOUT attribute value for an
OSS name server response (for example, the STOP FILESET and CONTROL
FILESET <fileset>, SYNC commands). Increasing the IOTIMEOUT
attribute value will also increase the overall timeout period used for these
requests.
This PARAM can provide the initial configuration value for the IOTIMEOUT
attribute of the subsystem. If this PARAM is supplied after the first execution
of the OSS Monitor, it replaces the current value for the IOTIMEOUT
attribute of the subsystem. This value is kept in the ZOSSPARM file and
controlled through the SCF ALTER SUBSYS command. See “ALTER
SUBSYS, ALTER MON, and ALTER PROCESS Commands” (page 285) for
more information about the value that can be specified.
The TACL PARAMs listed in Table 4 were used in G-series RVUs preceding G04.00 but no longer
affect OSS Monitor or OSS environment behavior. These PARAMs can be safely deleted from TACL
scripts.
Table 4 Obsolete TACL PARAMs for the OSS Monitor
DescriptionPARAM Name
Defines the volume and subvolume used for FSCK swap files.This value is now
automatically provided by the NonStop Kernel subsystem.
OSS^FSCK^SWAPVOL
Defines the processor number of the processor on which the primary OSS name
server process is started.This value is now kept in the ZOSSSERV file and
controlled through the SCF ALTER SERVER command.
OSS^NAMESERVER^CPU
Defines the volume and subvolume of the ZPCONFIG file.This value is no longer
meaningful, because the location of configuration files is permanently set to
$SYSTEM.ZXOSSMON.
POSIX^CONFIG^LOC
Specifying a Home Terminal
If you start the OSS Monitor from a terminal connected through Telserv (that is, a TELNET
pseudo-terminal), you must specify a different device as your home terminal in the RUN command
that starts the OSS Monitor. If you do not specify a different device and if your terminal session
exits after you start the OSS Monitor, the OSS Monitor can no longer start an OSS name server
or the FSCK utility. A valid terminal device must exist when the OSS Monitor starts these programs.
One possible solution to the problem is to select a permanent terminal such as an asynchronous
terminal or a terminal-simulator process (such as $ZHOME) and then specify that device as the
OSS Monitor home terminal. For example, to specify the $ZHOME process as the home terminal
for the OSS Monitor, enter:
OSSMON /NAME $ZPMON, NOWAIT, TERM $ZHOME, PRI 180/
54 Operating the OSS Environment