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

The $ZPMON prefix can be omitted if you have previously specified $ZPMON in an SCF
ASSUME command.
You can specify the following options in any order. You must specify at least one option:
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 by
AUTORESTART, the OSS Monitor no longer attempts to restart the server 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 ALTER SERVER command, the previous
value for the persistence count is unchanged.
BACKUPCPU backup_processor
specifies the processor number of the processor where the backup server process runs, where
backup_processor is either in the range 0 through 15 or equal to -1.
For the OSS name server, the value -1 specifies that the server will not run as a process pair.
For the OSS message-queue server, the value -1 specifies that the backup process will be started
on the next available CPU in the node.
If the BACKUPCPU option is omitted, the processor for the backup server process is unchanged.
BACKUPCPUOK { TRUE | FALSE }
specifies whether the server should be started in its configured backup processor when its
configured primary processor is unavailable and the server is being restarted automatically.
When the server is started in its configured backup processor and its configured primary
processor subsequently becomes available, the server automatically switches to its primary
processor.
When this option is omitted, the value in the server’s current configuration is not changed.
CPU primary_processor
specifies the processor number of the processor where the primary server process runs, where
primary_processor is in the range 0 through 15.
If the CPU option is omitted, the processor for the primary server process is unchanged.
280 Open System Services Monitor