Our init script pipes all dsmserv output through logger with the tag
tsm'n', where 'n' is the instance number on the server. This lets us
collect the logs in syslog, which is especially helpful if the TSM
server itself is not available.

-- Skylar Thompson (skylar2 AT u.washington DOT edu)
-- Genome Sciences Department, System Administrator
-- Foege Building S046, (206)-685-7354
-- University of Washington School of Medicine

On 10/ 2/12 01:17 PM, Thomas Denier wrote:

We sometimes start a TSM server in the foreground so that we can see
the initialization messages. However, this is potentially risky in
our environment if a TSM problem occurs outside of office hours.
The VPN facilities I and my coworkers use to log on to Unix and Linux
servers from our homes are subject to timeouts based on the time
since the connection was made rather than the time since the last
activity.

Is there any way to make the initialization messages available for
inspection without the risk that the termination of a specific
terminal connection will bring down the TSM server?

We have a TSM 5.5 server and several TSM 6.2 servers. All of our
TSM servers run under zSeries Linux.

Thomas Denier
Thomas Jefferson University Hospital