On Jan 3, 2007, at 3:11 PM, Andrew Raibeck wrote:

Hi Karel,

Are you saying that the password expires DURING a scheduled
operation, and
the operation subsequently fails? If so, and assuming that you are
running
a supported TSM configuration, you should open a ticket with IBM
support,
as this does not seem right to me (be sure to provide detailed
recreate
scenario in order to facilitate a complete understanding of the
problem).

Just to add a bit:  Whereas this problem is said to manifest itself
on Unix, it would be trivial to construct a small monitor to examine
the TSM password file attributes every second or so during TSM
operations and then log and alarm when there is any change to that
file.  The timestamp on the event could then be correlated with a
position in the scheduler log, and possibly dsmerror.log; and I would
also look at the Unix process accounting records to see if any rogue
action was afoot at that time.

  Richard Sims