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

[ , SEEPPRI [ priority ] ]
[ , SEEPPARAMTEXT [ startup-param-text ] ]
OUT filename
specifies the name of a Guardian output file for informational messages. You can either read
this file with a text editor or display it with the FUP COPY command.
SERVER server_processname
specifies the server being added. server_processname has the following form:
[ $ZPMON.]servername
servername
specifies the name of the server to add. servername must begin with a pound sign (#)
followed by a letter, which can be followed by 0 through 5 letters or digits. Only names
not currently defined in the ZOSSSERV file are valid values. Server names are not
case-sensitive.
The $ZPMON prefix can be omitted if you have previously specified $ZPMON in an SCF
ASSUME command.
TYPE NAME
specifies that an OSS name server is being added. Currently, OSS name servers are the only
OSS servers that can be added.
CPU primary_processor
specifies the processor number of the processor where the primary server process will run.
primary_processor is an integer in the range 0 through 15.
You can specify the following options in any order:
AUTORESTART ntimes
specifies the persistence count of the server, where ntimes is an integer value in the range 0
through 10. The persistence count is the number of times the OSS Monitor will automatically
restart the server during a 10-minute period.
The persistence count helps to prevent excessive attempts at restarting or an endless loop during
restart. The OSS Monitor counts the number of restart attempts for each server during the
previous 10 minutes; this number is the current persistence count.
Once the current persistence count for a server reaches the number specified for it for
AUTORESTART, the OSS Monitor no longer attempts to restart it and generates an EMS event
so that the operator can attempt to identify and correct a possible problem. After the problem
is corrected, the operator must take an action that causes the current persistence count to be
reset to 0; otherwise, the server and any associated filesets will not be automatically restarted.
A server’s current persistence count is reset to 0 at the following times:
• When the OSS Monitor starts or restarts
• When an SCF STOP SERVER, START SERVER, or ALTER SERVER command for the affected
server is completed
• When a START FILESET command for a fileset managed by the affected OSS name server
is completed
• After the server has run for 10 minutes without being restarted
The current persistence count for each server is incremented when that server terminates
abnormally or is stopped by something other than SCF. The current persistence count is not
incremented because of processor failure.
When the AUTORESTART option is omitted from the ADD SERVER command, the default
specification is AUTORESTART 3.
266 Open System Services Monitor