Brian,
------------------------------------------------------------------------------------------------------------------------------------
 For the unknown system error - return code is in dsmerror.log in adsm
 For the unknown system error - return code is in dsmerror.log in adsm
client directory.
(like return code -- 915) The error code is coming from either main system
or database.
Here the error 915 is due to the file-lock while takin backup.
One case we got was, when it was trying to copy opened-database-files from
directory to adsm,
     thru normal backup, which are not necessary, as backup of such dynmic
file is useless.
     By excluding these directories (db backup taken by other procedures)
such errors can be avoided.

Also adsm 3.7 version has a bad habit of stopping service on such cases,
and needs a restart of
     adsm client schedule service, otherwise backup gets missed till it is
restarted.

-----------------------------------------------------------
eg:
eg:
dsmsched.log
===========
12/22/00   00:26:14 Elapsed processing time:           00:10:31
12/22/00   00:26:14 --- SCHEDULEREC STATUS END
12/22/00   00:26:14 Unknown system error
Please check the TSM Error Log for any additional information

12/22/00   00:26:14 --- SCHEDULEREC OBJECT END 0000SP2PRD 12/22/00   00:00:00
12/22/00   00:26:14 ANS1512E Scheduled event '0000SP2PRD' failed.  Return code =
 4.
12/22/00   00:26:14 Sending results for scheduled event '0000SP2PRD'.
12/22/00   00:26:14 Will attempt to send results for 0000SP2PRD again in 12 hour
s.
12/22/00   09:10:25
               (service halt)
dsmerror.log:
==========
 12/22/00   00:26:14 cuPing: Out of sequence verb: verb: 61
12/22/00   00:26:14 sessOpen: Session state transition error, sessState: sSigned
On.
12/22/00   00:26:14 sessOpen: Transitioning: sSignedOn state ===> sTRANSERR stat
e
12/22/00   00:26:14 Return code 195 unknown
12/22/00   00:26:14 Return code 195 unknown
12/22/00   00:26:14 Unknown system error
Please check the TSM Error Log for any additional information

-----------------------------------------------------------
Hope this helps.
Hope this helps.
Vijay.
>=========================================================
>
>Date:    Tue, 19 Dec 2000 08:22:51 -0600
>From:    Brian Heiling <Brian.Heiling AT NETASPX DOT COM>
>Subject: Unknown system error
>MIME-Version: 1.0
>Content-Type: text/plain; charset="us-ascii"
>
>Question,
>
>I'm running TSM Solaris 2.6/7 Server Version 3, Release 7, Level 3.0
>And the Client  TSM Solaris 2.6 Client VERSION:  Version 3 Release 7 Level
>2
>
>
>About once a week I will get the following error in the dsmsched.log:
>
>=======================snipit=======================
>12/18/00   20:32:08 Elapsed processing time:           00:02:05
>12/18/00   20:32:08 --- SCHEDULEREC STATUS END
>12/18/00   20:32:08 Unknown system error
>Please check the TSM Error Log for any additional information
>
>12/18/00   20:32:08 --- SCHEDULEREC OBJECT END SRV0509_INCR 12/18/00
>20:30:00
>12/18/00   20:32:08 Scheduled event 'SRV0509_INCR' completed successfully.
>12/18/00   20:32:08 Sending results for scheduled event 'SRV0509_INCR'.
>12/18/00   20:32:08 Will attempt to send results for SRV0509_INCR again in
>12 ho
>urs.
>12/18/00   20:32:08
>Time remaining until execution:
>=======================snipit=======================
>
>The schedule eventually fails but by looking at the log it actually
>worked.  I just couldn't send
>the results back to the server.
>Then all schedules for that box will fail until I kill and restart the
>dsmc sched on the box.
>This actually happens randomly on various sun boxes.
>
>Has anyone seen this error before?  The Unknown system error does not even
>have a error code.
>
>Thanks
>        Brian Heiling
>