Hi Eric,
Most likely these messages are being generated as a result of an excluded
file (we still examine the file, even if it is excluded), or else you
would get an error message indicating that backup for a file had failed.
We eliminated these "junk" error messages via APAR IC27750, which was
fixed in the 4.1.2 PTF.
Try the 4.1.3 (or higher) client; you should find that these messages go
away.
Best regards,
Andy
Andy Raibeck
IBM Tivoli Systems
Tivoli Storage Manager Client Development
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.
"Loon, E.J. van - SPLXM" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
08/07/2001 02:34
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject: The good old RC 32
Hi *SM-ers!
The dsmerror.log of one of our Windows NT clients contains several of the
following messages:
08/06/2001 10:59:32 GetBackupStreamSize(): CreateFile(): Win32 RC = 32.
08/06/2001 10:59:32 TransWin32RC(): Win32 RC 32 from fioGetAttrib():
GetBackupStreamInfo
I know that the rc 32 means sharing violation because of a locked file,
but
TSM does not report which file that is! Even stranger is that TSM reports
at
the end of the backup 0 failed objects!!!!
This worries me a bit! We are using client level 3.7.2.16.
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines
**********************************************************************
This e-mail and any attachment may contain confidential and privileged
material intended for the addressee only. If you are not the addressee,
you are notified that no part of the e-mail or any attachment may be
disclosed, copied or distributed, and that any other action related to
this e-mail or attachment is strictly prohibited, and may be unlawful. If
you have received this e-mail by error, please notify the sender
immediately by return e-mail, and delete this message. Koninklijke
Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees
shall not be liable for the incorrect or incomplete transmission of this
e-mail or any attachments, nor responsible for any delay in receipt.
**********************************************************************
