We have a postschedcmd that checks the TSM backup and also checks whether
the dsmc sched is running. It frequently finds it NOT running. It runs at
"now + 5 minutes".

1. Should it run later?
2. Why does the dsmc sched ever go down?
3. What causes the "Process Interrupted!!  Severing connection." message?
4. Is the dsmerror.log relevant? What is it indicating?

03/16/04   03:04:55 Schedule will be refreshed in 4 hours.
03/16/04   03:04:55
Time remaining until execution:

>>>>>> Process Interrupted!!  Severing connection. <<<<<<
03/16/04   03:09:56 Querying server for next scheduled event.
03/16/04   03:09:56 Node Name: CHD007B
03/16/04   03:09:56 Session established with server CIDB3301: AIX-RS/6000
03/16/04   03:09:56   Server Version 5, Release 1, Level 6.1
03/16/04   03:09:56   Server date/time: 03/16/04   03:09:56  Last access:
03/16/
04   03:04:55

chd007b-root:/var/adm/tsm> cat dsmerror.log
03/11/04   02:07:01 ANS1074W *** User Abort ***

03/13/04   02:44:17 cuPing: Out of sequence verb: verb: 61
03/13/04   02:44:17 cuPing: Out of sequence verb: verb: 61
03/13/04   02:44:17 sessOpen: Session state transition error, sessState:
sSigned
On.
03/13/04   02:44:17 sessOpen: Transitioning: sSignedOn state ===> sTRANSERR
stat
e
03/13/04   02:44:17 ANS1074W *** User Abort ***

chd007b-root:/opt/tivoli/tsm/client/ba/bin> cat postschedcmd
/usr/bin/at -f /opt/tivoli/tsm/client/ba/bin/tsm-audit now + 5 minutes

We are running  Server Version 5, Release 1, Level 6.1, in an HPUX
environment.

Mike Vandeman
510-784-3172
UNIX SSS
> (888) 226-8649 - SSS Helpdesk
>
>