Which is why all my AIX systems are configured to swap the console to
/var/adm/log/`hostname`.console.log in out rc.local (not my idea, I swiped
it from the SP-frame convention). And then I've a real crummy echo command
in cron to drop a seperator line with the date & time in it to /dev/console
every 15 minutes, to give a clue on when things actually occurred.

Tom Kauffman
NIBCO, Inc

-----Original Message-----
From: Richard Sims [mailto:rbs AT BU DOT EDU]
Sent: Friday, April 25, 2003 10:38 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: SCSI Library Bulk Port operation


>My library does the same thing.  No detectable errors in either the TSM
>actlog or anywhere else on the server.  Just on the library.  TSM might be
>doing the same thing to your library, but it gobbles the errors and does
not
>report them as such.

A general advisory, which may or may not apply in this case:
In AIX, at least, and maybe other Unixes, subsystems (and sometimes,
drivers)
which run in the background (as when started in the system boot scripts)
write their messages to the operator console - which scroll off and
evaporate.
I discovered this to be the case with ADSM HSM, when I went looking for
error
messages and could find nothing in any logs.  This can also be the case with
SRC-controlled resources, where 'lssrc' on resources like "nfsd" show their
standout and standerr going to /dev/console by default.  And operators
always
ignore console messages.  :-(

Just something to be aware of and watch for, in systems work.

  Richard Sims, BU