If the option is set to YES, or if the TCPPORT and TCPADMINPORT are
the same value (the default), then the administrative sessions can use the
TCPPORT.
v NO If the option is set to NO, and if the TCPADMINPORT value is different
than the TCPPORT value, then administrative sessions cannot use
TCPPORT.COMMTimeout seconds Specifies the maximum number of seconds that the server waits for an
expected client message during an operation that causes a database update.
The default value is 60. The minimum value is 1. If the length of time
exceeds this time-out, the server ends the session with the client. You may
want to increase the time-out value to prevent clients from timing out.
Clients may time out if there is a heavy network load in your environment
or when they are backing up large files.
IDLETimeout minutes Specifies the maximum number of minutes that a client session can be idle
before the server cancels the session. The default value is 15 minutes. The
minimum value is 1 minute. You may want to increase the time-out value
to prevent clients from timing out if there is a heavy network load in your
environment. Note, however, that a large number of idle sessions could
prevent other users from connecting to the server.
MAXSessions number_of_sessions Specifies the maximum number of simultaneous client sessions that can
connect with the server. The default value is 25 client sessions. The
minimum value is 2 client sessions. The maximum value is limited only by
available virtual memory size or communication resources.
MSGSTACKTRACE on|off Specifies that a list of functions will be shown on the server console, and
will also be directed to the activity log after specific messages have been
issued. The output will help the Tivoli Storage Manager service team to
diagnose specific problems quicker. It is recommended that this option be
set to ON.
RESOURCETimeout minutes Specifies the maximum number of minutes that a storage agent waits for a
resource on the server. The default value is 60 minutes. The minimum
value is 1 minute.
For database resources and sessions on the storage agent, the Tivoli Storage
Manager resource monitor picks the shortest time-out value to start a
recovery process.
In contrast, in the case of library sharing, the resource monitor picks the
longest time for both the library manager and library client to recover. For
more efficient management of shared library resources, consider setting
resource time-outs at the same limit for all participants in a shared
configuration. In any case of error recovery, Tivoli Storage Manager always
defers to the longest timeout limit.
uses this option to monitor some of the storage agent sessions and
resources and will cancel sessions based on the value you specify.