Hi Melinda, Can you provide more information about the problem? The dsminfo.txt file created by the "dsmc query systeminfo" command would be helpful (make sure you use the same dsm.opt file as your scheduler uses). You can attach dsminfo.txt in a response. Also, check the server activity log to see what messages are issued therein at the time this problem occurs. What are these messages?
Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> wrote on 07/20/2004 07:59:54: > This has been very frustrating for us since when you review the log > files it says that the system objects and files have successfully been > backed up. > > This is the error code: > ANS1026E Session rejected: Communications protocol error. > Explanation: Communications protocol error. An unexpected communications > message was received by the client. > System Action: ADSM canceled the current operation. > User Response: Verify that your communication path is functioning > properly. If the problem continues, have your service representative > check for a possible program error. > > So at this point I don't know if it's in the dsm.opt file for with the > Unix server that has the TSM software.
