Open System Services Management and Operations Guide (G06.29+, H06.07+)
Open System Services Monitor
Open System Services Management and Operations Guide—527191-005
12-18
ADD SERVER Command
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 from the ADD SERVER command, the default
specification is BACKUPCPUOK TRUE.
INODECACHE size1
specifies the number of entries permitted in the inode cache used by an OSS
name server. size1 is in the range 128 through 500000. The default value is 4096
entries.
LINKCACHE size2
specifies the number of entries permitted in the link cache used by an OSS name
server. size2 can have a value in the range 128 through 500000. The default
value is 4096 entries.
MAXWAITTIME seconds2
specifies the maximum number of seconds that the OSS Monitor waits for the OSS
name server’s primary processor to become available during an automatic restart
of the server; seconds2 must be in the range 0 through 32767. A value of 0
means that the OSS Monitor does not wait for the primary processor to become
available.
If the BACKUPCPUOK attribute for the server is TRUE and the primary processor
does not become available after the specified period has elapsed, the OSS Monitor
attempts to start the server in its backup processor.
When the MAXWAITTIME option is omitted from the ADD SERVER command, the
default specification is MAXWAITTIME 0.
SQLTIMEOUT seconds
specifies the number of seconds an OSS name server waits for a response from
SQLCAT to a request. seconds can have a value in the range 60 through 300.
The default value is 60.
Considerations
•
The ADD SERVER command does not start the server; it merely stores information
about the server within the OSS Monitor configuration file. An OSS name server is
started when the first fileset managed by that OSS name server is mounted. The