Re: errors in the dsmerror.log each time we start "dsmc sched" and/or "dsmcad"

[Remco Post]

Pavel Sitnikov wrote:

maybe somebody have the same problem (it is supposed  that this error
appear after sysback installation)
we have this errors in the dsmerror.log each time we start "dsmc sched"
and/or "dsmcad"

07/05/09   09:57:26 dlopen() of
/usr/tivoli/tsm/client/ba/bin/plugins/libPiIMG.a failed.
07/05/09   09:57:26 0509-130 Symbol resolution failed for
/usr/tivoli/tsm/client/ba/bin/plugins/libPiIMG.a because:
0509-136   Symbol tsmBeginGetDataEx (number 246) is not exported
from
   dependent module /usr/lib/libApiDS.a(dsmapish.o).
0509-022 Cannot load module
/usr/tivoli/tsm/client/ba/bin/plugins/libPiIMG.a.
0509-026 System error: Cannot run a file that does not have a
valid format.
0509-192 Examine .loader section symbols with the
 'dump -Tv' command..
07/05/09   09:57:26 dlopen() of
/usr/tivoli/tsm/client/ba/bin/plugins/libPiNAS.a failed.
07/05/09   09:57:26 0509-130 Symbol resolution failed for
/usr/tivoli/tsm/client/ba/bin/plugins/libPiNAS.a because:
0509-136   Symbol tsmLoadToc (number 106) is not exported from
   dependent module /usr/lib/libApiDS.a(dsmapish.o).
0509-136   Symbol tsmSendImageObjRtrv (number 107) is not exported
from
   dependent module /usr/lib/libApiDS.a(dsmapish.o).
0509-022 Cannot load module
/usr/tivoli/tsm/client/ba/bin/plugins/libPiNAS.a.
0509-026 System error: Cannot run a file that does not have a
valid format.
0509-192 Examine .loader section symbols with the
 'dump -Tv' command..

pls help fix this


It looks like your client install is broken. I would reinstall
everything (ba client, api, sysback). If that doesn't fix it, contact
IBM support.

--
Met vriendelijke groeten,

Remco Post, PLCS

errors in the dsmerror.log each time we start "dsmc sched" and/or "dsmcad"

[Pavel Sitnikov]

maybe somebody have the same problem (it is supposed  that this error
appear after sysback installation)
we have this errors in the dsmerror.log each time we start "dsmc sched"
and/or "dsmcad"

07/05/09   09:57:26 dlopen() of
/usr/tivoli/tsm/client/ba/bin/plugins/libPiIMG.a failed.
07/05/09   09:57:26 0509-130 Symbol resolution failed for
/usr/tivoli/tsm/client/ba/bin/plugins/libPiIMG.a because:
0509-136   Symbol tsmBeginGetDataEx (number 246) is not exported
from
   dependent module /usr/lib/libApiDS.a(dsmapish.o).
0509-022 Cannot load module
/usr/tivoli/tsm/client/ba/bin/plugins/libPiIMG.a.
0509-026 System error: Cannot run a file that does not have a
valid format.
0509-192 Examine .loader section symbols with the
 'dump -Tv' command..
07/05/09   09:57:26 dlopen() of
/usr/tivoli/tsm/client/ba/bin/plugins/libPiNAS.a failed.
07/05/09   09:57:26 0509-130 Symbol resolution failed for
/usr/tivoli/tsm/client/ba/bin/plugins/libPiNAS.a because:
0509-136   Symbol tsmLoadToc (number 106) is not exported from
   dependent module /usr/lib/libApiDS.a(dsmapish.o).
0509-136   Symbol tsmSendImageObjRtrv (number 107) is not exported
from
   dependent module /usr/lib/libApiDS.a(dsmapish.o).
0509-022 Cannot load module
/usr/tivoli/tsm/client/ba/bin/plugins/libPiNAS.a.
0509-026 System error: Cannot run a file that does not have a
valid format.
0509-192 Examine .loader section symbols with the
 'dump -Tv' command..

pls help fix this

ANS5250E in dsmerror.log

[neilsolent]

Tim

I have the same problem as you. I can't help - but did you ever get to the 
bottom of the problem?

thanks
Neil

+--
|This was sent by [EMAIL PROTECTED] via Backup Central.
|Forward SPAM to [EMAIL PROTECTED]
+--

ANS5250E in dsmerror.log

[Tim Brown]

 Windows client is 2003 SP2
 TSM client is 5.4.2

  Errors in dsmerror.log

  Anyone seen this.

04/14/2008 10:55:21 ANS5250E An unexpected error was encountered.
   TSM function name : CompareFile
   TSM function  : fioGetLegacyAcl() returned '267' for file \\
server\c$\WINDOWS\system32\CatRoot\{127D0A1D-4EF2-11D1-8608-00C04FC295EE
}'

   TSM return code   : 267
   TSM file  : incrdrv.cpp (15968)
04/14/2008 10:55:22 ANS1228E Sending of object 'SYSTEM STATE' failed
04/14/2008 10:55:22 ANS4973E An error occurred accessing NTFS security
information for file 'SYSTEM STATE'


 Tim Brown
Systems Specialist - Project Leader
Central Hudson Gas & Electric
284 South Ave
Poughkeepsie, NY 12601
Email: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
Phone: 845-486-5643
Fax: 845-486-5921
Cell: 845-235-4255

Re: ANS5250E, ANS1999E and ANS1950E errors in Windows 2003 clients dsmerror.log

[Timothy Hughes]

Dwight- thanks


Dwight Cook wrote:

There are some patches that have to do with VSS issues which are only
available by request, they are:

Windows 2003 -IA64bit servers
WindowsServer2003-KB887827-v3-ia64-enu.exe

Windows 2003 - 32bit servers
WindowsServer2003-KB887827-v3-x86-enu.exe

Windows 2003 SP1 -IA64 bit servers
WindowsServer2003-KB913648-ia64-ENU.exe


Windows 2003 SP1 - 32bit servers
WindowsServer2003-KB913648-x86-ENU.exe

Windows 2003 SP1 - x64bit servers
WindowsServer2003.WindowsXP-KB913648-x64-ENU.exe

Hope this helps...

Re: ANS5250E, ANS1999E and ANS1950E errors in Windows 2003 clients dsmerror.log

[Dwight Cook]

There are some patches that have to do with VSS issues which are only
available by request, they are:

Windows 2003 -IA64bit servers
WindowsServer2003-KB887827-v3-ia64-enu.exe

Windows 2003 - 32bit servers
WindowsServer2003-KB887827-v3-x86-enu.exe

Windows 2003 SP1 -IA64 bit servers
WindowsServer2003-KB913648-ia64-ENU.exe


Windows 2003 SP1 - 32bit servers
WindowsServer2003-KB913648-x86-ENU.exe

Windows 2003 SP1 - x64bit servers
WindowsServer2003.WindowsXP-KB913648-x64-ENU.exe

Hope this helps...

Re: ANS5250E, ANS1999E and ANS1950E errors in Windows 2003 clients dsmerror.log

[Timothy Hughes]

Andy - Thanks,  I  looked in the Event Viewer log for VSS and it showed
the following error for 10/30/07.

Volume Shadow Copy Service error: Error calling a routine on the Shadow
Copy Provider
{b5946137 - 7b9f - 4925 -af80-51abd60b20d5}

Routine details
EndprepareSnapshots[{3d86e222-9ac6-44c8-9430-5250f66cf955}) [hr =
0x8000]


Where do I find the NT log?







Andy Huebner wrote:

When we have VSS issues we first look in the NT log for the error.  Most
of the time that will lead us to a MS solution.  What errors are in the
NT log?

Andy Huebner

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Timothy Hughes
Sent: Tuesday, October 30, 2007 12:59 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] ANS5250E, ANS1999E and ANS1950E errors in Windows 2003
clients dsmerror.log

Hello All,

We are receiving the following error message in a dsmerror.log on a
Windows 2003 client.
I know it's a Microsoft Volume Shadow copy issue I just need help on
possible solutions
Or areas to investigate. Is this error familiar to anyone? I did a
search on this an found
a hit from 10/24/06 (which I found interesting because these errors
started showing up in
our clients dsmerror.log around 10/24/07) Anyway there were no replies
to that post
possibly due to it not being a TSM issue?


10/28/2007 00:19:37 ANS5250E An unexpected error was encountered.
TSM function name : VssRequestor::QueryStatus
TSM function : pAsync->QueryStatus() for caller 'CreateSnapshotSet()'
returned VSS_E_UNEXPECTED_PROVIDER_ERROR
TSM return code : -1
TSM file : vssreq.cpp (8270)
10/28/2007 00:19:40 ANS1999E Incremental processing of '\\snc355\c$'
stopped.
10/28/2007 00:19:40 ANS1950E Backup using Microsoft volume shadow copy
failed.
10/28/2007 00:19:40 ANS1512E Scheduled event 'MIDNIGHT' failed. Return
code = 12.
10/28/2007 23:53:46 ANS5250E An unexpected error was encountered.
TSM function name : VssRequestor::QueryStatus
TSM function : pAsync->QueryStatus() for caller 'CreateSnapshotSet()'
returned VSS_E_UNEXPECTED_PROVIDER_ERROR
TSM return code : -1
TSM file : vssreq.cpp (8270)

10/28/2007 23:53:50 ANS1999E Incremental processing of '\\snc355\c$'
stopped.
10/28/2007 23:53:50 ANS1950E Backup using Microsoft volume shadow copy
failed.
10/28/2007 23:53:50 ANS1512E Scheduled event 'MIDNIGHT' failed. Return
code = 12.


Thanks for any help or suggestions in advance!


TSM 5.3.3.2
AIX 5.3
Windows 2003 R2 Standard x64 Edition
TSM Client 5.3.4x 64 bit


This e-mail (including any attachments) is confidential and may be legally 
privileged. If you are not an intended recipient or an authorized 
representative of an intended recipient, you are prohibited from using, copying 
or distributing the information in this e-mail or its attachments. If you have 
received this e-mail in error, please notify the sender immediately by return 
e-mail and delete all copies of this message and any attachments.
Thank you.

Re: ANS5250E, ANS1999E and ANS1950E errors in Windows 2003 clients dsmerror.log

[Andy Huebner]

When we have VSS issues we first look in the NT log for the error.  Most
of the time that will lead us to a MS solution.  What errors are in the
NT log?

Andy Huebner

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Timothy Hughes
Sent: Tuesday, October 30, 2007 12:59 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] ANS5250E, ANS1999E and ANS1950E errors in Windows 2003
clients dsmerror.log

Hello All,

We are receiving the following error message in a dsmerror.log on a 
Windows 2003 client.
I know it's a Microsoft Volume Shadow copy issue I just need help on 
possible solutions
Or areas to investigate. Is this error familiar to anyone? I did a 
search on this an found
a hit from 10/24/06 (which I found interesting because these errors 
started showing up in
our clients dsmerror.log around 10/24/07) Anyway there were no replies 
to that post
possibly due to it not being a TSM issue?


10/28/2007 00:19:37 ANS5250E An unexpected error was encountered.
TSM function name : VssRequestor::QueryStatus
TSM function : pAsync->QueryStatus() for caller 'CreateSnapshotSet()' 
returned VSS_E_UNEXPECTED_PROVIDER_ERROR
TSM return code : -1
TSM file : vssreq.cpp (8270)
10/28/2007 00:19:40 ANS1999E Incremental processing of '\\snc355\c$' 
stopped.
10/28/2007 00:19:40 ANS1950E Backup using Microsoft volume shadow copy 
failed.
10/28/2007 00:19:40 ANS1512E Scheduled event 'MIDNIGHT' failed. Return 
code = 12.
10/28/2007 23:53:46 ANS5250E An unexpected error was encountered.
TSM function name : VssRequestor::QueryStatus
TSM function : pAsync->QueryStatus() for caller 'CreateSnapshotSet()' 
returned VSS_E_UNEXPECTED_PROVIDER_ERROR
TSM return code : -1
TSM file : vssreq.cpp (8270)

10/28/2007 23:53:50 ANS1999E Incremental processing of '\\snc355\c$' 
stopped.
10/28/2007 23:53:50 ANS1950E Backup using Microsoft volume shadow copy 
failed.
10/28/2007 23:53:50 ANS1512E Scheduled event 'MIDNIGHT' failed. Return 
code = 12.


Thanks for any help or suggestions in advance!


TSM 5.3.3.2
AIX 5.3
Windows 2003 R2 Standard x64 Edition
TSM Client 5.3.4x 64 bit


This e-mail (including any attachments) is confidential and may be legally 
privileged. If you are not an intended recipient or an authorized 
representative of an intended recipient, you are prohibited from using, copying 
or distributing the information in this e-mail or its attachments. If you have 
received this e-mail in error, please notify the sender immediately by return 
e-mail and delete all copies of this message and any attachments.
Thank you.

ANS5250E, ANS1999E and ANS1950E errors in Windows 2003 clients dsmerror.log

[Timothy Hughes]

Hello All,

We are receiving the following error message in a dsmerror.log on a 
Windows 2003 client.
I know it’s a Microsoft Volume Shadow copy issue I just need help on 
possible solutions
Or areas to investigate. Is this error familiar to anyone? I did a 
search on this an found
a hit from 10/24/06 (which I found interesting because these errors 
started showing up in
our clients dsmerror.log around 10/24/07) Anyway there were no replies 
to that post

possibly due to it not being a TSM issue?


10/28/2007 00:19:37 ANS5250E An unexpected error was encountered.
TSM function name : VssRequestor::QueryStatus
TSM function : pAsync->QueryStatus() for caller 'CreateSnapshotSet()' 
returned VSS_E_UNEXPECTED_PROVIDER_ERROR

TSM return code : -1
TSM file : vssreq.cpp (8270)
10/28/2007 00:19:40 ANS1999E Incremental processing of '\\snc355\c$' 
stopped.
10/28/2007 00:19:40 ANS1950E Backup using Microsoft volume shadow copy 
failed.
10/28/2007 00:19:40 ANS1512E Scheduled event 'MIDNIGHT' failed. Return 
code = 12.

10/28/2007 23:53:46 ANS5250E An unexpected error was encountered.
TSM function name : VssRequestor::QueryStatus
TSM function : pAsync->QueryStatus() for caller 'CreateSnapshotSet()' 
returned VSS_E_UNEXPECTED_PROVIDER_ERROR

TSM return code : -1
TSM file : vssreq.cpp (8270)

10/28/2007 23:53:50 ANS1999E Incremental processing of '\\snc355\c$' 
stopped.
10/28/2007 23:53:50 ANS1950E Backup using Microsoft volume shadow copy 
failed.
10/28/2007 23:53:50 ANS1512E Scheduled event 'MIDNIGHT' failed. Return 
code = 12.



Thanks for any help or suggestions in advance!


TSM 5.3.3.2
AIX 5.3
Windows 2003 R2 Standard x64 Edition
TSM Client 5.3.4x 64 bit

Re: dsmerror.log & dsmsched.log gets too large

[Avy Wong]

Thank you fellas...(o:

Avy Wong
Business Continuity Administrator
Mohegan Sun
1 Mohegan Sun Blvd
Uncasville, CT 06382
(860) 862-8164
cell (860) 961-6976






 Charles A Hart
 <[EMAIL PROTECTED]
 .COM>  To
 Sent by: "ADSM:   ADSM-L@VM.MARIST.EDU
 Dist Stor  cc
 Manager"
 <[EMAIL PROTECTED] Subject
 .EDU> Re: [ADSM-L] dsmerror.log &
   dsmsched.log gets too large

 04/17/2007 10:52
 AM


 Please respond to
 "ADSM: Dist Stor
 Manager"
 <[EMAIL PROTECTED]
   .EDU>






There's options you can use to limit number of days to keep for the sched
and error logs...


SCHEDLOGname  /path/dsmsched2.log
SCHEDLOGRetention 5
ERRORLOGname  /path/dsmerror2.log
ERRORLOGRetention 33


Charles Hart
UHT - Data Protection
(763)744-2263
Sharepoint:
http://unitedteams.uhc.com/uht/EnterpriseStorage/DataProtection/default.aspx





Henrik Wahlstedt <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" 
04/17/2007 09:38 AM
Please respond to
"ADSM: Dist Stor Manager" 


To
ADSM-L@VM.MARIST.EDU
cc

Subject
Re: [ADSM-L] dsmerror.log & dsmsched.log gets too large






Hi,

There are some freeware you can use to split files, look at tucows.com.

However, you have the options to use Error- and Schedlogretention
together with Error- and Schedlogmax to control the log size.

Look in the client manual for more information.


Thanks
Henrik



-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Avy Wong
Sent: den 17 april 2007 16:05
To: ADSM-L@VM.MARIST.EDU
Subject: dsmerror.log & dsmsched.log gets too large

Hello
  Is there a way to open the dsmerror.log and dsmsched.log files
when it says, " The C:\Program Files\Tivoli\TSM\baclient\dsmerror.log
file is too large for Notepad. Use another editor to edit the file."
File is 779,624 KB.

I have tried wordpad, microsoft word, it does not open.  What is the
managable size before it gets too big?

Thanks,


Avy Wong
Business Continuity Administrator
Mohegan Sun
1 Mohegan Sun Blvd
Uncasville, CT 06382
(860) 862-8164
cell (860) 961-6976



**
The information contained in this message may be privileged and
confidential and protected from disclosure. If the reader of this
message is not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient, you
are hereby notified that any dissemination, distribution, or copy of
this communication is strictly prohibited. If you have received this
communication in error, please notify us immediately by replying to the
message and deleting it from your computer.

**


---
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of
the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and
delete
this message.
Thank you.



This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity to
which it is addressed. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.


**
The information contained in this message may be privileged and confidential and
protected from disclosure. If the reader of this message is not the intended 
recipient, or
an employee or agent responsible for delivering this message to the intended 
recipient,
you are hereby notified that any dissemination, distribution, or copy of this
communication is strictly prohibited. If you have received this communication 
in error,
please notify us immediately by replying to the message and deleting it from 
your
computer.
**

Re: dsmerror.log & dsmsched.log gets too large

[Charles A Hart]

There's options you can use to limit number of days to keep for the sched
and error logs...


SCHEDLOGname  /path/dsmsched2.log
SCHEDLOGRetention 5
ERRORLOGname  /path/dsmerror2.log
ERRORLOGRetention 33


Charles Hart
UHT - Data Protection
(763)744-2263
Sharepoint:
http://unitedteams.uhc.com/uht/EnterpriseStorage/DataProtection/default.aspx




Henrik Wahlstedt <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" 
04/17/2007 09:38 AM
Please respond to
"ADSM: Dist Stor Manager" 


To
ADSM-L@VM.MARIST.EDU
cc

Subject
Re: [ADSM-L] dsmerror.log & dsmsched.log gets too large






Hi,

There are some freeware you can use to split files, look at tucows.com.

However, you have the options to use Error- and Schedlogretention
together with Error- and Schedlogmax to control the log size.

Look in the client manual for more information.


Thanks
Henrik



-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Avy Wong
Sent: den 17 april 2007 16:05
To: ADSM-L@VM.MARIST.EDU
Subject: dsmerror.log & dsmsched.log gets too large

Hello
  Is there a way to open the dsmerror.log and dsmsched.log files
when it says, " The C:\Program Files\Tivoli\TSM\baclient\dsmerror.log
file is too large for Notepad. Use another editor to edit the file."
File is 779,624 KB.

I have tried wordpad, microsoft word, it does not open.  What is the
managable size before it gets too big?

Thanks,


Avy Wong
Business Continuity Administrator
Mohegan Sun
1 Mohegan Sun Blvd
Uncasville, CT 06382
(860) 862-8164
cell (860) 961-6976



**
The information contained in this message may be privileged and
confidential and protected from disclosure. If the reader of this
message is not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient, you
are hereby notified that any dissemination, distribution, or copy of
this communication is strictly prohibited. If you have received this
communication in error, please notify us immediately by replying to the
message and deleting it from your computer.

**


---
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of
the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and
delete
this message.
Thank you.



This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity to
which it is addressed. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.

Re: dsmerror.log & dsmsched.log gets too large

[Henrik Wahlstedt]

Hi,

There are some freeware you can use to split files, look at tucows.com.

However, you have the options to use Error- and Schedlogretention
together with Error- and Schedlogmax to control the log size.

Look in the client manual for more information.


Thanks
Henrik



-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Avy Wong
Sent: den 17 april 2007 16:05
To: ADSM-L@VM.MARIST.EDU
Subject: dsmerror.log & dsmsched.log gets too large

Hello
  Is there a way to open the dsmerror.log and dsmsched.log files
when it says, " The C:\Program Files\Tivoli\TSM\baclient\dsmerror.log
file is too large for Notepad. Use another editor to edit the file."
File is 779,624 KB.

I have tried wordpad, microsoft word, it does not open.  What is the
managable size before it gets too big?

Thanks,


Avy Wong
Business Continuity Administrator
Mohegan Sun
1 Mohegan Sun Blvd
Uncasville, CT 06382
(860) 862-8164
cell (860) 961-6976



**
The information contained in this message may be privileged and
confidential and protected from disclosure. If the reader of this
message is not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient, you
are hereby notified that any dissemination, distribution, or copy of
this communication is strictly prohibited. If you have received this
communication in error, please notify us immediately by replying to the
message and deleting it from your computer.

**


---
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and delete
this message.
Thank you.

dsmerror.log & dsmsched.log gets too large

[Avy Wong]

Hello
  Is there a way to open the dsmerror.log and dsmsched.log files when
it says,
" The C:\Program Files\Tivoli\TSM\baclient\dsmerror.log file is too large
for Notepad. Use another editor to edit the file."
File is 779,624 KB.

I have tried wordpad, microsoft word, it does not open.  What is the
managable size before it gets too big?

Thanks,


Avy Wong
Business Continuity Administrator
Mohegan Sun
1 Mohegan Sun Blvd
Uncasville, CT 06382
(860) 862-8164
cell (860) 961-6976


**
The information contained in this message may be privileged and confidential and
protected from disclosure. If the reader of this message is not the intended 
recipient, or
an employee or agent responsible for delivering this message to the intended 
recipient,
you are hereby notified that any dissemination, distribution, or copy of this
communication is strictly prohibited. If you have received this communication 
in error,
please notify us immediately by replying to the message and deleting it from 
your
computer.
**

Re: dsmerror.log is empty after a TSM service (schedule) restart?

[Heinz Flemming]

According to Henrik Wahlstedt:
> Hi
>
> I gotta be missing something here, so any help is appreciated.
> Scheduled backup runs fine and puts some information about skipped files
> in dsmerror.log. But when the TSM Schedule service is restarted it
> clears all messages in dsmerror.log. Adding SET
> DSM_LOG=C:\UTILS\tsm\baclient doesnt change that behaviour.
>

  May be APAR IC47537 is the "solution".


  Greetings,
  Heinz

dsmerror.log is empty after a TSM service (schedule) restart?

[Henrik Wahlstedt]

Hi

I gotta be missing something here, so any help is appreciated.
Scheduled backup runs fine and puts some information about skipped files
in dsmerror.log. But when the TSM Schedule service is restarted it
clears all messages in dsmerror.log. Adding SET
DSM_LOG=C:\UTILS\tsm\baclient doesnt change that behaviour.

I would like to have my old setting in dsm.opt to be a little more
persistent.
* Purge error log file after 30 days, then delete
ErrorLogRetention 30,d

What am I missing?


//Henrik

W2k3 with sp1:
Event Type: Information
Event Source:   AdsmClientService
Event Category: None
Event ID:   4103
Date:   27.03.2006
Time:   13:27:29
User:   NT AUTHORITY\SYSTEM
Computer:   W36
Description:
Backup/Archive Client Service Startup Parameters:
 

-
 Service Name   : TSM Schedule
 Last Update: Dec  8 2005
 Client PTF Level   : 5.3.2.2
 Service Directory  : C:\UTILS\tsm\baclient
 Client Options File: C:\UTILS\tsm\baclient\dsm.opt
 Client Node: ST-TW36
 Comm Method: (default or obtained from client options file)
 Server : (default or obtained from client options file)
 Port   : (default or obtained from client options file)
 Schedule Log   : dsmsched.log
 Error Log  : dsmerror.log
 Cluster Mode   : (default or obtained from client options file)
 

-


---
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and delete
this message.
Thank you.

Re: dsmerror.log missed

[Richard Sims]

On Dec 21, 2005, at 2:34 PM, Marcelo Barreto wrote:

Hi, one of my Linux servers have a file called dsmerror.log.old but  
doesn´t have a dsmerror.log file, how could I generate it?


Marcelo - The .old file would be one that your site renamed.

The rules for dsmerror.log creation are to be found in the Unix  
client manual appropriate to your TSM level. By default, they would  
be in the current directory where the client was initiated.


   Richard Sims

dsmerror.log missed

[Marcelo Barreto]

Hi, one of my Linux servers have a file called dsmerror.log.old but doesn´t 
have a dsmerror.log file, how could I generate it?
 
thanks in advance.
 
 
Marcelo Barreto
Departamento de Sistemas de Información
Dedicado Telecomunicaciones
Cont. Echevarriarza 3535 Torre A Piso 2
Montevideo - Uruguay
Tel: +598 2 6288428 int.158
[EMAIL PROTECTED]
 

Re: dsmerror.log in TSM 5.3

[Kathleen M Hallahan]

I've put in a DCR trying to get this changed back, in fact.  There's no
good reason for everyone who might run a backup or archive--including
DBAs, application/business users, etc.--to have write access to the file
like that.  And it runs contrary to the current climate of increasing
security.

DCRs from other users might help the process along...



_

Kathleen Hallahan
Freddie Mac
Distributed Backups
703-450-3317




   "Paul Zarnowski" <[EMAIL PROTECTED]>
   Sent by: "ADSM: Dist Stor Manager" 
   12/02/2005 04:53 PM
   Please respond to
"ADSM: Dist Stor Manager" 


To
ADSM-L@VM.MARIST.EDU
cc

Subject
dsmerror.log in TSM 5.3






Ok, so TSM client development has decided that starting with TSM 5.3,
the dsmerror.log file has to be writable, or else it will fail.

Why?  What was the overwhelming reason to make this behavior change?

Unless I am missing an easy solution to this problem, this is going
to cause our users grief, and I don't see a simple solution.  I liked
it better when the client just continued to work, but didn't write to
the error log.  Now we have to explain to our users that they have to
rewrite their scripts, or they have to set environment variables, or
they have to be careful which directory they run TSM out of.  They
don't need this annoyance.  I don't see the reason for the change.

grr.

Does anyone know if MacOS X has something similar to an /etc/environment
file?

..Paul


--
Paul ZarnowskiPh: 607-255-4757
Manager, Storage Systems  Fx: 607-255-8521
719 Rhodes Hall, Ithaca, NY 14853-3801Em: [EMAIL PROTECTED]

dsmerror.log in TSM 5.3

[Paul Zarnowski]

Ok, so TSM client development has decided that starting with TSM 5.3,
the dsmerror.log file has to be writable, or else it will fail.

Why?  What was the overwhelming reason to make this behavior change?

Unless I am missing an easy solution to this problem, this is going
to cause our users grief, and I don't see a simple solution.  I liked
it better when the client just continued to work, but didn't write to
the error log.  Now we have to explain to our users that they have to
rewrite their scripts, or they have to set environment variables, or
they have to be careful which directory they run TSM out of.  They
don't need this annoyance.  I don't see the reason for the change.

grr.

Does anyone know if MacOS X has something similar to an /etc/environment file?

..Paul


--
Paul ZarnowskiPh: 607-255-4757
Manager, Storage Systems  Fx: 607-255-8521
719 Rhodes Hall, Ithaca, NY 14853-3801Em: [EMAIL PROTECTED]

Re: dsmerror.log in TSM client version 5.3

[Rainer Holzinger]

Thank you Richard.

Rainer

> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf
> Of Richard Sims
> Sent: Wednesday, October 26, 2005 1:25 PM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] dsmerror.log in TSM client version 5.3
>
> On Oct 26, 2005, at 5:40 AM, Rainer Holzinger wrote:
>
> > after upgrading some TSM clients (on AIX and Solaris) to version
> > 5.3.2.0
> > I have noticed that there's always a 'new' dsmerror.log file
> existing,
> > even if there hasn't been an error.
> >
> > If dsmerror.log wasn't existing then the file size is 0 (zero)
> > bytes and
> > it seems dsmerror.log was created like the Unix 'touch' command is
> > doing. On the other hand, if dsmerror.log was existing and had
> entries
> > in, the timestamp has been updated with the one of the last
> scheduled
> > backup even if the wasn't an error in that backup operation.
> >
> > Has this something to do with IBM's changes for the DSM_LOG
> > environment
> > variable and the check that dsmerror.log is writable?
> >
>
> Hi, Rainer -
>
> Seems to be the case...
> The client download Readme file goes into more detail than the client
> manual:
>
> "Initialization of the client and its various components has been
> significantly revised. In particular, if you are using scripts to
> accomplish certain tasks, you will notice:
> The client application (dsmc, dsmadmc) will not run without a
> writable error log. If a log is not present, one will be opened under
> the uid of the user that invokes the application and with that user's
> default permissions. This may mean that another user may not have
> write permission and the client will not run.
> There must always be an error log. If it is created new for each run
> and there are no errors, it will be empty at process termination.
> If the error log exists and is writable by the invoking user, it will
> be preserved along with all permissions and ACLs if they exist. It is
> strongly recommended that you create any required logs in a directory
> and with proper permissions to allow all users write access."
>
> Richard Sims

Re: dsmerror.log in TSM client version 5.3

[Richard Sims]

On Oct 26, 2005, at 5:40 AM, Rainer Holzinger wrote:


after upgrading some TSM clients (on AIX and Solaris) to version
5.3.2.0
I have noticed that there's always a 'new' dsmerror.log file existing,
even if there hasn't been an error.

If dsmerror.log wasn't existing then the file size is 0 (zero)
bytes and
it seems dsmerror.log was created like the Unix 'touch' command is
doing. On the other hand, if dsmerror.log was existing and had entries
in, the timestamp has been updated with the one of the last scheduled
backup even if the wasn't an error in that backup operation.

Has this something to do with IBM's changes for the DSM_LOG
environment
variable and the check that dsmerror.log is writable?



Hi, Rainer -

Seems to be the case...
The client download Readme file goes into more detail than the client
manual:

"Initialization of the client and its various components has been
significantly revised. In particular, if you are using scripts to
accomplish certain tasks, you will notice:
The client application (dsmc, dsmadmc) will not run without a
writable error log. If a log is not present, one will be opened under
the uid of the user that invokes the application and with that user's
default permissions. This may mean that another user may not have
write permission and the client will not run.
There must always be an error log. If it is created new for each run
and there are no errors, it will be empty at process termination.
If the error log exists and is writable by the invoking user, it will
be preserved along with all permissions and ACLs if they exist. It is
strongly recommended that you create any required logs in a directory
and with proper permissions to allow all users write access."

   Richard Sims

dsmerror.log in TSM client version 5.3

[Rainer Holzinger]

Hello all,



after upgrading some TSM clients (on AIX and Solaris) to version 5.3.2.0
I have noticed that there's always a 'new' dsmerror.log file existing,
even if there hasn't been an error.

If dsmerror.log wasn't existing then the file size is 0 (zero) bytes and
it seems dsmerror.log was created like the Unix 'touch' command is
doing. On the other hand, if dsmerror.log was existing and had entries
in, the timestamp has been updated with the one of the last scheduled
backup even if the wasn't an error in that backup operation.

Has this something to do with IBM's changes for the DSM_LOG environment
variable and the check that dsmerror.log is writable?



Thanks, Rainer





RHo-Consulting

Rembrandtstr. 12

D-93093 Donaustauf

phone:   +49 9403 969188

mobile:  +49 162 2807 888

email:[EMAIL PROTECTED]

 [EMAIL PROTECTED]

Re: dsmerror.log and dsmsched.log changes in 5.3 windows client

[Rushforth, Tim]

OK, this is a MS bug, http://support.microsoft.com/kb/830885/

 

Fixed in SP1.

 

 

  _  

From: Rushforth, Tim 
Sent: Wednesday, August 10, 2005 4:39 PM
To: ADSM-L (ADSM-L@VM.MARIST.EDU)
Subject: dsmerror.log and dsmsched.log changes in 5.3 windows client

 

We have our Windows clients run a postschedulecmd that ftp the client's
dsmerror.log and dsmsched.log to a central location.

We've just noticed some of the Windows 2003 clients at level 5.3.05 are
failing to ftp the files (we get error "dsmerror.log:No such device or
address").

If we stop the TSM Client Schedule Service (and maybe the Client
Acceptor) then we are able to transfer the files via ftp.

It appears that the 5.3 client on Windows 2003 keeps these files open
when the services above are running.  We can copy them when the services
are running using windows copy but cannot ftp them using windows ftp.

We have two Windows 2003 clients at 5.3.05 that are able to ftp the
files and about 4 that cannot at the moment.  We are trying to see the
differences between these servers but have not been able to figure it
out yet.  It nearly seems at this time that perhaps some hotfix isn't
allowing windows ftp to put a file that is open!

We are wondering if anyone has any insight to this.  

Thanks,

Tim Rushforth

City of Winnipeg

 

 

 

 

dsmerror.log and dsmsched.log changes in 5.3 windows client

[Rushforth, Tim]

We have our Windows clients run a postschedulecmd that ftp the client's
dsmerror.log and dsmsched.log to a central location.

We've just noticed some of the Windows 2003 clients at level 5.3.05 are
failing to ftp the files (we get error "dsmerror.log:No such device or
address").

If we stop the TSM Client Schedule Service (and maybe the Client
Acceptor) then we are able to transfer the files via ftp.

It appears that the 5.3 client on Windows 2003 keeps these files open
when the services above are running.  We can copy them when the services
are running using windows copy but cannot ftp them using windows ftp.

We have two Windows 2003 clients at 5.3.05 that are able to ftp the
files and about 4 that cannot at the moment.  We are trying to see the
differences between these servers but have not been able to figure it
out yet.  It nearly seems at this time that perhaps some hotfix isn't
allowing windows ftp to put a file that is open!

We are wondering if anyone has any insight to this.  

Thanks,

Tim Rushforth

City of Winnipeg

 

 

 

 

Re: dsmerror.log configuration

[Richard Sims]

Greg - It's unusual and unhealthy, from both logical an physical
standpoints,
   to mingle the error logging from all sessions - which may involve
simultaneous sessions.  In such an error log, you want a clear-cut
sequence
of operations and consequences reflected.
What I would recommend is the creation of a wrapper script for dsmc,
named
the same or differently, which will put all error logs into a single,
all-writable directory, with an error log path spec which appends the
username, for uniqueness and singularity.  The wrapper script would
invoke
dsmc with the -ERRORLOGname= option spec.
   Richard Sims   http://people.bu.edu/rbs
On Sep 22, 2004, at 12:38 PM, Greg wrote:
Hi,
I am having a little trouble getting the client error log set up
correctly for non-administrators on MacOS X servers. I have defined
ERRORLOGName in  /Library/Preferences/Tivoli Storage Manager/TSM System
Preferences file. As it should this definition overrides any
environmental export of DSM_LOG by the non-administrator user. However
when the dsmerror.log is written by the TSM scheduler the mode on the
file is 644 and owned by root:wheel. So when the non-administrator user
invokes DSMC they get the infamous 'ANS0110E Unable to open error log
file '/path/to/dsmerror.log' for output" problem.
If leave the path undefined in the dsm.sys the export of DSM_LOG for
each user works correctly. But I want all system invoked TSM logs
written to the hosts central log path, and any user TSM logs written to
the path of there choice. I just can't seem to find a way to do it.
Can someone shed some light on this for me?
Thanks,
Greg

dsmerror.log configuration

[Greg]

Hi,
I am having a little trouble getting the client error log set up
correctly for non-administrators on MacOS X servers. I have defined
ERRORLOGName in  /Library/Preferences/Tivoli Storage Manager/TSM System
Preferences file. As it should this definition overrides any
environmental export of DSM_LOG by the non-administrator user. However
when the dsmerror.log is written by the TSM scheduler the mode on the
file is 644 and owned by root:wheel. So when the non-administrator user
invokes DSMC they get the infamous 'ANS0110E Unable to open error log
file '/path/to/dsmerror.log' for output" problem.
If leave the path undefined in the dsm.sys the export of DSM_LOG for
each user works correctly. But I want all system invoked TSM logs
written to the hosts central log path, and any user TSM logs written to
the path of there choice. I just can't seem to find a way to do it.
Can someone shed some light on this for me?
Thanks,
Greg

Re: dsmerror.log 2003 Active Directory Server

[Tim Brown]

  same problem when server is at Version 5, Release 2, Level 3.0

tim
- Original Message -
From: "Stapleton, Mark" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, July 14, 2004 9:37 AM
Subject: Re: dsmerror.log 2003 Active Directory Server


From: ADSM: Dist Stor Manager on behalf of Tim Brown
getting these messages for my 2003 AD Servers
i installed the latest client Version 5, Release 2, Level 2.10
07/13/2004 23:06:39 sessRecvVerb(): Invalid verb received.
07/13/2004 23:06:39 sessRecvVerb(): length=, verb=00,magic=04
07/13/2004 23:06:39 sessRecvVerb(): Invalid verb received.
07/13/2004 23:06:39 sessRecvVerb(): length=, verb=00,magic=04
07/13/2004 23:06:42 ANS1026E Session rejected: Communications protocol error
server on z/os is Version 5, Release 2, Level 0.0
any one seen this before
===

First of all, get off the base level of server code. Go to the latest
maintenance level, and then see if the problem persists.

--
Mark Stapleton

Re: dsmerror.log 2003 Active Directory Server

[Stapleton, Mark]

From: ADSM: Dist Stor Manager on behalf of Tim Brown
getting these messages for my 2003 AD Servers
i installed the latest client Version 5, Release 2, Level 2.10
07/13/2004 23:06:39 sessRecvVerb(): Invalid verb received.
07/13/2004 23:06:39 sessRecvVerb(): length=, verb=00,magic=04
07/13/2004 23:06:39 sessRecvVerb(): Invalid verb received.
07/13/2004 23:06:39 sessRecvVerb(): length=, verb=00,magic=04
07/13/2004 23:06:42 ANS1026E Session rejected: Communications protocol error
server on z/os is Version 5, Release 2, Level 0.0 
any one seen this before
===

First of all, get off the base level of server code. Go to the latest maintenance 
level, and then see if the problem persists.

--
Mark Stapleton

dsmerror.log 2003 Active Directory Server

[Tim Brown]

getting these messages for my 2003 AD Servers
i installed the latest client Version 5, Release 2, Level 2.10

07/13/2004 23:06:39 sessRecvVerb(): Invalid verb received.
07/13/2004 23:06:39 sessRecvVerb(): length=, verb=00,magic=04
07/13/2004 23:06:39 sessRecvVerb(): Invalid verb received.
07/13/2004 23:06:39 sessRecvVerb(): length=, verb=00,magic=04
07/13/2004 23:06:42 ANS1026E Session rejected: Communications protocol error

server on z/os is Version 5, Release 2, Level 0.0 

any one seen this before

Tim Brown
Systems Specialist
Central Hudson Gas & Electric
284 South Ave
Poughkeepsie, NY 12601
Email: [EMAIL PROTECTED]
Phone: 845-486-5643
Fax: 845-486-5921

Re: Error in DSMERROR.log

[Andrew Raibeck]

No, I don't think that's related to the timeout. The journal DB can not
exceed 2 GB (actually 2 * 1024^3 - 1 bytes), so if it's growing that
large, there are other issues.

I recommend you go to
http://www-306.ibm.com/software/sysmgmt/products/support/ and do a search
on

  journal based backup

You will find several useful articles, including a FAQ, that should help
answer many questions.

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.



"Kamp, Bruce" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
02/19/2004 06:49
Please respond to
"ADSM: Dist Stor Manager"


To
[EMAIL PROTECTED]
cc

Subject
Re: Error in DSMERROR.log






Thanks I missed the JNLINBNPTIMEOUT setting.
One other thing I noticed that my journal DB is over 2Gig.  Could this be
the cause of the timeout?


-
Bruce Kamp
Senior Midrange Systems Analyst
Memorial Healthcare System
E-Mail: [EMAIL PROTECTED]
Phone: (954) 987-2020 x4597
Pager: (954) 286-9441
Alphapage: [EMAIL PROTECTED]
Fax: (954) 985-1404
-

-Original Message-
From: Andrew Raibeck [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 19, 2004 8:34 AM
To: [EMAIL PROTECTED]
Subject: Re: Error in DSMERROR.log

Bruce,

5.2.0.1 or 5.2.0.3  not important.

I suggest you carefully re-read the article. If it still doesn't make
sense, post again and quote the part(s) you don't understand so we can
clarify.

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.



"Kamp, Bruce" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
02/19/2004 06:06
Please respond to
"ADSM: Dist Stor Manager"


To
[EMAIL PROTECTED]
cc

Subject
Re: Error in DSMERROR.log






The problem is I'm above that level 5.2.0.3.  The article talks about
version 5.2.0.1.


-
Bruce Kamp
Senior Midrange Systems Analyst
Memorial Healthcare System
E-Mail: [EMAIL PROTECTED]
Phone: (954) 987-2020 x4597
Pager: (954) 286-9441
Alphapage: [EMAIL PROTECTED]
Fax: (954) 985-1404
-

-Original Message-
From: Warren, Matthew (Retail) [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 19, 2004 6:30 AM
To: [EMAIL PROTECTED]
Subject: Re: Error in DSMERROR.log

Hallo,

A search for

psNpPeek

at www.ibm.com (search box top right of page) returns 3 items, the third
looks promising .. :-)

Matt.

-Original Message-
From: "Kamp, Bruce" <[EMAIL PROTECTED]>@EME
Sent: Wednesday, February 18, 2004 12:28 PM
To: [EMAIL PROTECTED]
Subject: Error in DSMERROR.log


Envirnment:
Windows 2000 SP4 with TSM client version 5.2.0.3
TSM server version is 5.2.0.0 on AIX 5.1.

I have been seeing the following error on onre of my
Windows 2000 nodes:

02/17/2004 01:11:33 processSysvol():
NtFrsApiGetBackupRestoreSets(): RC = 2
02/17/2004 01:11:33 processSysvol():
NtFrsApiDestroyBackupRestore(): RC = 0
02/17/2004 01:45:45 psNpPeek(): Timed out waiting for 4
bytes to arrive on
pipe.
02/17/2004 01:45:55 psNpPeek(): Timed out waiting for 4
bytes to arrive on
pipe.
02/17/2004 01:46:05 psNpPeek(): Timed out waiting for 4
bytes to arrive on
pipe.
02/17/2004 01:46:15 psNpPeek(): Timed out waiting for 4
bytes to arrive on
pipe.
02/17/2004 01:46:25 psNpPeek(): Timed out waiting for 4
bytes to arrive on
pipe.

Has anybody else seen this?

Thanks,
-
Bruce Kamp
Senior Midrange Systems Analyst
Memorial Healthcare System
E-mail: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
Phone: (954) 987-2020 x4597
Pager: (954) 286-9441
Alphapage:  [EMAIL PROTECTED]
Fax: (954) 985-1404
-


__

Re: Error in DSMERROR.log

[Kamp, Bruce]

Thanks I missed the JNLINBNPTIMEOUT setting.
One other thing I noticed that my journal DB is over 2Gig.  Could this be
the cause of the timeout?


-
Bruce Kamp
Senior Midrange Systems Analyst
Memorial Healthcare System
E-Mail: [EMAIL PROTECTED]
Phone: (954) 987-2020 x4597
Pager: (954) 286-9441
Alphapage: [EMAIL PROTECTED]
Fax: (954) 985-1404
-

-Original Message-
From: Andrew Raibeck [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 19, 2004 8:34 AM
To: [EMAIL PROTECTED]
Subject: Re: Error in DSMERROR.log

Bruce,

5.2.0.1 or 5.2.0.3  not important.

I suggest you carefully re-read the article. If it still doesn't make
sense, post again and quote the part(s) you don't understand so we can
clarify.

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.



"Kamp, Bruce" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
02/19/2004 06:06
Please respond to
"ADSM: Dist Stor Manager"


To
[EMAIL PROTECTED]
cc

Subject
Re: Error in DSMERROR.log






The problem is I'm above that level 5.2.0.3.  The article talks about
version 5.2.0.1.


-
Bruce Kamp
Senior Midrange Systems Analyst
Memorial Healthcare System
E-Mail: [EMAIL PROTECTED]
Phone: (954) 987-2020 x4597
Pager: (954) 286-9441
Alphapage: [EMAIL PROTECTED]
Fax: (954) 985-1404
-

-Original Message-
From: Warren, Matthew (Retail) [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 19, 2004 6:30 AM
To: [EMAIL PROTECTED]
Subject: Re: Error in DSMERROR.log

Hallo,

A search for

psNpPeek

at www.ibm.com (search box top right of page) returns 3 items, the third
looks promising .. :-)

Matt.

-Original Message-
From: "Kamp, Bruce" <[EMAIL PROTECTED]>@EME
Sent: Wednesday, February 18, 2004 12:28 PM
    To: [EMAIL PROTECTED]
Subject: Error in DSMERROR.log


Envirnment:
Windows 2000 SP4 with TSM client version 5.2.0.3
TSM server version is 5.2.0.0 on AIX 5.1.

I have been seeing the following error on onre of my
Windows 2000 nodes:

02/17/2004 01:11:33 processSysvol():
NtFrsApiGetBackupRestoreSets(): RC = 2
02/17/2004 01:11:33 processSysvol():
NtFrsApiDestroyBackupRestore(): RC = 0
02/17/2004 01:45:45 psNpPeek(): Timed out waiting for 4
bytes to arrive on
pipe.
02/17/2004 01:45:55 psNpPeek(): Timed out waiting for 4
bytes to arrive on
pipe.
02/17/2004 01:46:05 psNpPeek(): Timed out waiting for 4
bytes to arrive on
pipe.
02/17/2004 01:46:15 psNpPeek(): Timed out waiting for 4
bytes to arrive on
pipe.
02/17/2004 01:46:25 psNpPeek(): Timed out waiting for 4
bytes to arrive on
pipe.

Has anybody else seen this?

Thanks,
-
Bruce Kamp
Senior Midrange Systems Analyst
Memorial Healthcare System
E-mail: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
Phone: (954) 987-2020 x4597
Pager: (954) 286-9441
Alphapage:  [EMAIL PROTECTED]
Fax: (954) 985-1404
-


___ Disclaimer Notice __
This message and any attachments are confidential and should only be read
by those to whom they are addressed. If you are not the intended
recipient,
please contact us, delete the message from your computer and destroy any
copies. Any distribution or copying without our prior permission is
prohibited.

Internet communications are not always secure and therefore the Powergen
Group does not accept legal responsibility for this message. The recipient
is responsible for verifying its authenticity before acting on the
contents. Any views or opinions presented are solely those of the author
and do not necessarily represent those of the Powergen Group.

Registered addresses:

Powergen UK plc, 53 New Broad Street, London, EC2M 1SL
Registered in England & Wales No. 2366970

Powergen Retail Limited,  Westwood Way, Westwood Business Park,
Coventry CV4 8LG.
Registered in England and Wales No: 3407430

Telephone +44 (0) 2476 42 4000
Fax   +44 (0) 2476 42 5432

Re: Error in DSMERROR.log

[Andrew Raibeck]

Bruce,

5.2.0.1 or 5.2.0.3  not important.

I suggest you carefully re-read the article. If it still doesn't make
sense, post again and quote the part(s) you don't understand so we can
clarify.

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.



"Kamp, Bruce" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
02/19/2004 06:06
Please respond to
"ADSM: Dist Stor Manager"


To
[EMAIL PROTECTED]
cc

Subject
Re: Error in DSMERROR.log






The problem is I'm above that level 5.2.0.3.  The article talks about
version 5.2.0.1.


-
Bruce Kamp
Senior Midrange Systems Analyst
Memorial Healthcare System
E-Mail: [EMAIL PROTECTED]
Phone: (954) 987-2020 x4597
Pager: (954) 286-9441
Alphapage: [EMAIL PROTECTED]
Fax: (954) 985-1404
-

-Original Message-
From: Warren, Matthew (Retail) [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 19, 2004 6:30 AM
To: [EMAIL PROTECTED]
Subject: Re: Error in DSMERROR.log

Hallo,

A search for

psNpPeek

at www.ibm.com (search box top right of page) returns 3 items, the third
looks promising .. :-)

Matt.

-Original Message-
From: "Kamp, Bruce" <[EMAIL PROTECTED]>@EME
Sent: Wednesday, February 18, 2004 12:28 PM
    To: [EMAIL PROTECTED]
Subject: Error in DSMERROR.log


Envirnment:
Windows 2000 SP4 with TSM client version 5.2.0.3
TSM server version is 5.2.0.0 on AIX 5.1.

I have been seeing the following error on onre of my
Windows 2000 nodes:

02/17/2004 01:11:33 processSysvol():
NtFrsApiGetBackupRestoreSets(): RC = 2
02/17/2004 01:11:33 processSysvol():
NtFrsApiDestroyBackupRestore(): RC = 0
02/17/2004 01:45:45 psNpPeek(): Timed out waiting for 4
bytes to arrive on
pipe.
02/17/2004 01:45:55 psNpPeek(): Timed out waiting for 4
bytes to arrive on
pipe.
02/17/2004 01:46:05 psNpPeek(): Timed out waiting for 4
bytes to arrive on
pipe.
02/17/2004 01:46:15 psNpPeek(): Timed out waiting for 4
bytes to arrive on
pipe.
02/17/2004 01:46:25 psNpPeek(): Timed out waiting for 4
bytes to arrive on
pipe.

Has anybody else seen this?

Thanks,
-
Bruce Kamp
Senior Midrange Systems Analyst
Memorial Healthcare System
E-mail: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
Phone: (954) 987-2020 x4597
Pager: (954) 286-9441
Alphapage:  [EMAIL PROTECTED]
Fax: (954) 985-1404
-


___ Disclaimer Notice __
This message and any attachments are confidential and should only be read
by those to whom they are addressed. If you are not the intended
recipient,
please contact us, delete the message from your computer and destroy any
copies. Any distribution or copying without our prior permission is
prohibited.

Internet communications are not always secure and therefore the Powergen
Group does not accept legal responsibility for this message. The recipient
is responsible for verifying its authenticity before acting on the
contents. Any views or opinions presented are solely those of the author
and do not necessarily represent those of the Powergen Group.

Registered addresses:

Powergen UK plc, 53 New Broad Street, London, EC2M 1SL
Registered in England & Wales No. 2366970

Powergen Retail Limited,  Westwood Way, Westwood Business Park,
Coventry CV4 8LG.
Registered in England and Wales No: 3407430

Telephone +44 (0) 2476 42 4000
Fax   +44 (0) 2476 42 5432

Re: Error in DSMERROR.log

[Kamp, Bruce]

The problem is I'm above that level 5.2.0.3.  The article talks about
version 5.2.0.1.


-
Bruce Kamp
Senior Midrange Systems Analyst
Memorial Healthcare System
E-Mail: [EMAIL PROTECTED]
Phone: (954) 987-2020 x4597
Pager: (954) 286-9441
Alphapage: [EMAIL PROTECTED]
Fax: (954) 985-1404
-

-Original Message-
From: Warren, Matthew (Retail) [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 19, 2004 6:30 AM
To: [EMAIL PROTECTED]
Subject: Re: Error in DSMERROR.log

Hallo,

A search for

psNpPeek

at www.ibm.com (search box top right of page) returns 3 items, the third
looks promising .. :-)

Matt.

-Original Message-
From: "Kamp, Bruce" <[EMAIL PROTECTED]>@EME
Sent: Wednesday, February 18, 2004 12:28 PM
To: [EMAIL PROTECTED]
    Subject: Error in DSMERROR.log


Envirnment:
Windows 2000 SP4 with TSM client version 5.2.0.3
TSM server version is 5.2.0.0 on AIX 5.1.

I have been seeing the following error on onre of my
Windows 2000 nodes:

02/17/2004 01:11:33 processSysvol():
NtFrsApiGetBackupRestoreSets(): RC = 2
02/17/2004 01:11:33 processSysvol():
NtFrsApiDestroyBackupRestore(): RC = 0
02/17/2004 01:45:45 psNpPeek(): Timed out waiting for 4
bytes to arrive on
pipe.
02/17/2004 01:45:55 psNpPeek(): Timed out waiting for 4
bytes to arrive on
pipe.
02/17/2004 01:46:05 psNpPeek(): Timed out waiting for 4
bytes to arrive on
pipe.
02/17/2004 01:46:15 psNpPeek(): Timed out waiting for 4
bytes to arrive on
pipe.
02/17/2004 01:46:25 psNpPeek(): Timed out waiting for 4
bytes to arrive on
pipe.

Has anybody else seen this?

Thanks,
-
Bruce Kamp
Senior Midrange Systems Analyst
Memorial Healthcare System
E-mail: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
Phone: (954) 987-2020 x4597
Pager: (954) 286-9441
Alphapage:  [EMAIL PROTECTED]
Fax: (954) 985-1404
-


___ Disclaimer Notice __
This message and any attachments are confidential and should only be read
by those to whom they are addressed. If you are not the intended recipient,
please contact us, delete the message from your computer and destroy any
copies. Any distribution or copying without our prior permission is
prohibited.

Internet communications are not always secure and therefore the Powergen
Group does not accept legal responsibility for this message. The recipient
is responsible for verifying its authenticity before acting on the
contents. Any views or opinions presented are solely those of the author
and do not necessarily represent those of the Powergen Group.

Registered addresses:

Powergen UK plc, 53 New Broad Street, London, EC2M 1SL
Registered in England & Wales No. 2366970

Powergen Retail Limited,  Westwood Way, Westwood Business Park,
Coventry CV4 8LG.
Registered in England and Wales No: 3407430

Telephone +44 (0) 2476 42 4000
Fax   +44 (0) 2476 42 5432

Re: Error in DSMERROR.log

[Warren, Matthew (Retail)]

Hallo,

A search for

psNpPeek

at www.ibm.com (search box top right of page) returns 3 items, the third
looks promising .. :-)

Matt.

-Original Message-
From: "Kamp, Bruce" <[EMAIL PROTECTED]>@EME 
Sent: Wednesday, February 18, 2004 12:28 PM
To: [EMAIL PROTECTED]
Subject: Error in DSMERROR.log


Envirnment:
Windows 2000 SP4 with TSM client version 5.2.0.3
TSM server version is 5.2.0.0 on AIX 5.1.

I have been seeing the following error on onre of my
Windows 2000 nodes:

02/17/2004 01:11:33 processSysvol():
NtFrsApiGetBackupRestoreSets(): RC = 2
02/17/2004 01:11:33 processSysvol():
NtFrsApiDestroyBackupRestore(): RC = 0
02/17/2004 01:45:45 psNpPeek(): Timed out waiting for 4
bytes to arrive on
pipe.
02/17/2004 01:45:55 psNpPeek(): Timed out waiting for 4
bytes to arrive on
pipe.
02/17/2004 01:46:05 psNpPeek(): Timed out waiting for 4
bytes to arrive on
pipe.
02/17/2004 01:46:15 psNpPeek(): Timed out waiting for 4
bytes to arrive on
pipe.
02/17/2004 01:46:25 psNpPeek(): Timed out waiting for 4
bytes to arrive on
pipe.

Has anybody else seen this?

Thanks,
-
Bruce Kamp
Senior Midrange Systems Analyst
Memorial Healthcare System
E-mail: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
Phone: (954) 987-2020 x4597
Pager: (954) 286-9441
Alphapage:  [EMAIL PROTECTED]
Fax: (954) 985-1404
-


___ Disclaimer Notice __
This message and any attachments are confidential and should only be read
by those to whom they are addressed. If you are not the intended recipient, please 
contact us, delete the message from your computer and destroy any copies. Any 
distribution or copying without our prior permission is
prohibited.

Internet communications are not always secure and therefore the Powergen 
Group does not accept legal responsibility for this message. The recipient is 
responsible for verifying its authenticity before acting on the 
contents. Any views or opinions presented are solely those of the author 
and do not necessarily represent those of the Powergen Group.

Registered addresses:

Powergen UK plc, 53 New Broad Street, London, EC2M 1SL
Registered in England & Wales No. 2366970

Powergen Retail Limited,  Westwood Way, Westwood Business Park,
Coventry CV4 8LG.
Registered in England and Wales No: 3407430

Telephone +44 (0) 2476 42 4000
Fax   +44 (0) 2476 42 5432

Error in DSMERROR.log

[Kamp, Bruce]

Envirnment:
Windows 2000 SP4 with TSM client version 5.2.0.3
TSM server version is 5.2.0.0 on AIX 5.1.

I have been seeing the following error on onre of my Windows 2000 nodes:

02/17/2004 01:11:33 processSysvol(): NtFrsApiGetBackupRestoreSets(): RC = 2
02/17/2004 01:11:33 processSysvol(): NtFrsApiDestroyBackupRestore(): RC = 0
02/17/2004 01:45:45 psNpPeek(): Timed out waiting for 4 bytes to arrive on
pipe.
02/17/2004 01:45:55 psNpPeek(): Timed out waiting for 4 bytes to arrive on
pipe.
02/17/2004 01:46:05 psNpPeek(): Timed out waiting for 4 bytes to arrive on
pipe.
02/17/2004 01:46:15 psNpPeek(): Timed out waiting for 4 bytes to arrive on
pipe.
02/17/2004 01:46:25 psNpPeek(): Timed out waiting for 4 bytes to arrive on
pipe.

Has anybody else seen this?

Thanks,
-
Bruce Kamp
Senior Midrange Systems Analyst
Memorial Healthcare System
E-mail: [EMAIL PROTECTED] 
Phone: (954) 987-2020 x4597
Pager: (954) 286-9441
Alphapage:  [EMAIL PROTECTED]
Fax: (954) 985-1404
-

Re: W2K error "NtFrsApi" in dsmerror.log

[Mike Dile]

This message means that FRS (file replication services) is not
present/active on your system. This message can be ignored. In TSM 5.2.2
(forthcoming) these messages will no longer be logged to alleviate
confusion.

Regards,

Mike Dile
Tivoli Storage Manager Client Development
Tivoli Software, IBM Software Group
[EMAIL PROTECTED]

W2K error "NtFrsApi" in dsmerror.log

[Schmitz Garnebode]

Hi,

have anybody seen this failure bevor on windows 2000 Server with Service Pack 3
and 4 and TSM-Client 5.2.0.6??

0001 17.12.2003 23:09:37 processSysvol(): NtFrsApiGetBackupRestoreSets(): RC = 2
0002 17.12.2003 23:09:37 processSysvol(): NtFrsApiDestroyBackupRestore(): RC = 0

Our TSM-Server w2K  on Level 5.1.6.4


regards

Michael Garnebode
Diplom-Informatiker
Systemberater

Schmitz RZ Consult
Gesellschaft für DV-Beratung und Projektmanagement mbH
Im Blumersfeld 22
50259 Pulheim
Tel.: +49 (0) 2238/922266
Fax:  +49 (0) 2238/922267
EMail: [EMAIL PROTECTED]

Odd entries in DSMERROR.LOG

[Zoltan Forray/AC/VCU]

On this new 2K3 server with 5.1.6.9 client, I am see these entries in the
DSMERROR.LOG file ?

10/17/2003 07:58:59 ConsoleEventHandler(): Caught Logoff console event .
10/17/2003 07:58:59 ConsoleEventHandler(): Process Detached.
10/17/2003 07:59:00 ConsoleEventHandler(): Caught Logoff console event .
10/17/2003 07:59:00 ConsoleEventHandler(): Process Detached.
10/17/2003 07:59:05 ConsoleEventHandler(): Caught Logoff console event .
10/17/2003 07:59:05 ConsoleEventHandler(): Process Detached.
10/17/2003 07:59:08 ConsoleEventHandler(): Caught Shutdown console event .
10/17/2003 07:59:08 ConsoleEventHandler(): Cleaning up and terminating
Process ...


Should I be concerned ?

Re: Dsmerror.log

[Zlatko Krastev/ACIT]

Is your client scheduler in POlling or PRompted mode? Have you changed the
mode during upgrade?

Zlatko Krastev
IT Consultant






Mark Hayden <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
13.05.2003 00:30
Please respond to "ADSM: Dist Stor Manager"


To: [EMAIL PROTECTED]
cc:
Subject:Dsmerror.log


Hi all, quick question. We have upgraded out TSM client on Netware to
5.1.5.
Since then, we get this error daily in the client dsmerror.log below.
Backups run fine, but have a feeling, this is some sort of
hickup.Thanks for your help!

05/10/2003 00:51:35 TCP/IP received rc 35 trying to accept connection
from server.
05/10/2003 00:51:35 acceptOne: Error -50 accepting inbound connection
05/10/2003 01:51:40 TCP/IP received rc 35 trying to accept connection
from server.
05/10/2003 01:51:40 acceptOne: Error -50 accepting inbound connection
05/10/2003 02:51:45 TCP/IP received rc 35 trying to accept connection
from server.
05/10/2003 02:51:45 acceptOne: Error -50 accepting inbound connection
05/10/2003 03:51:50 TCP/IP received rc 35 trying to accept connection
from server.
05/10/2003 03:51:50 acceptOne: Error -50 accepting inbound connection
05/10/2003 04:51:55 TCP/IP received rc 35 trying to accept connection
from server.
05/10/2003 04:51:55 acceptOne: Error -50 accepting inbound connection
05/10/2003 05:52:00 TCP/IP received rc 35 trying to accept connection
from server.
05/10/2003 05:52:00 acceptOne: Error -50 accepting inbound connection
05/10/2003 06:52:04 TCP/IP received rc 35 trying to accept connection
from server.
05/10/2003 06:52:04 acceptOne: Error -50 accepting inbound connection
05/10/2003 07:52:09 TCP/IP received rc 35 trying to accept connection
from server.
05/10/2003 07:52:09 acceptOne: Error -50 accepting inbound connection

Re: TSM Scheduler shows backups completed successfully dsmerror.log shows backups failed ?

[Andrew Raibeck]

OK... and does your script behave in the manner I suggested in my prior
post? If it does, then TSM should be behaving as I described, and you
should be able to distinguish failed vs. successful operations.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: [EMAIL PROTECTED] (change eye to i to reply)

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




shekhar Dhotre <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
12/30/2002 11:53
Please respond to "ADSM: Dist Stor Manager"


To: [EMAIL PROTECTED]
cc:
Subject:Re: TSM Scheduler shows backups  completed successfully 
dsmerror.log
shows backups failed ?



Andy ,

Here is the information on  TSM client and server .

Server : 5.1.1.0
Client : 5.1.5.0

TSM server is Configured on one of the node of  RS/6000 SP
system(AIX433-10 )   and client is also  AIX  node 4.33.10.


  - TSM schedule  is calling a shell scriptwhich does  following :

Part 1
alter tablespace ,beginbackup -   dumps oracle database files in one of
the file systems -

Part 2
TSM  archives  filesystems   using proper management classes.




f2n21 />dsmc
Tivoli Storage Manager
Command Line Backup/Archive Client Interface - Version 5, Release 1, Level
5.0
(C) Copyright IBM Corporation 1990, 2002 All Rights Reserved.

tsm>

f1n05 />dsmadmc
Tivoli Storage Manager
Command Line Administrative Interface - Version 5, Release 1, Level 1.0
(C) Copyright IBM Corporation 1990, 2002 All Rights Reserved.


Thank You

SD







Andrew Raibeck <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
12/30/2002 05:05 AM
Please respond to "ADSM: Dist Stor Manager"


To: [EMAIL PROTECTED]
cc:
Subject:Re: TSM Scheduler shows backups  completed
successfully dsmerror.log
shows backups failed ?


You don't indicate which TSM client and server versions you are running,
nor do you indicate what the scheduled event is doing. In general, though,
I would say that this behavior is a probable bug and should be reported to
IBM support.

--

Starting with version 5.1, the output from QUERY EVENT FORMAT=DETAILED
should more accurately reflect the status of the scheduled event (See the
chapter on "Automating Tasks", section "Return codes from the command line
interface" in the client manual for details). As I mentioned above, you
did not say what the scheduled command was. However, some caveats for
scheduled events where ACTION=COMMAND:

1) If the command ends with a nonzero return code that is less than 12,
the event will be reported as "Complete" (note that QUERY EVENT
FORMAT=DETAILED will show the return code). This problem is described in
APAR IC35203.

2) If the command is executed asynchronously, then it is not possible for
TSM to track the outcome, in which case the event will be reported as
"Complete" with return code 0. For example:

;my script
start command1   ;command1 launched asynchronously
exit lastrc  ;command1 launched successfully, exits with rc 0

Note: the "scripts" in this post are written in a "pseudo" code to
illustrate my meaning, and do not represent actual working scripts.

If you wish to see a more accurate status reported to TSM, then the
command should be configured to run synchronously (if possible). For
example:

;my modified script
command1  ;run command1, wait for completion
exit lastrc   ;exits with rc from command1

3) If the command is a script that includes several commands, and each of
those commands may or may not end with return code 0, but ultimately the
script exits with a return code of 0, then the event will be reported as
"Complete" with return code 0. For instance, if the script does this:

;my script
command1  ;fails with lastrc = 4
command2  ;succeeds with lastrc = 0
exit lastrc   ;exits with rc 0

In this case, if you wish to see a more accurate status reported to TSM,
then the script will need to be modified to exit with a nonzero return
code as appropriate (i.e. the script will need to track the return code
from each command within the script, then exit with a nonzero return code
if any command fails). For instance:

;my modified script to exit with highest rc
set scriptrc = 0  ;initialize scriptrc
command1  ;fails with lastrc = 4
if lastrc > scriptrc then scriptrc = lastrc   ;scriptrc = 4
command2  ;succeeds with lastrc = 0
if lastrc > scriptrc then scriptrc = lastrc   ;scriptrc still = 4
exit scriptrc ;exits with r

Re: TSM Scheduler shows backups completed successfully dsmerror.log shows backups failed ?

[shekhar Dhotre]

Andy ,

Here is the information on  TSM client and server .

Server : 5.1.1.0
Client : 5.1.5.0

TSM server is Configured on one of the node of  RS/6000 SP
system(AIX433-10 )   and client is also  AIX  node 4.33.10.


  - TSM schedule  is calling a shell scriptwhich does  following :

Part 1
alter tablespace ,beginbackup -   dumps oracle database files in one of
the file systems -

Part 2
TSM  archives  filesystems   using proper management classes.




f2n21 />dsmc
Tivoli Storage Manager
Command Line Backup/Archive Client Interface - Version 5, Release 1, Level
5.0
(C) Copyright IBM Corporation 1990, 2002 All Rights Reserved.

tsm>

f1n05 />dsmadmc
Tivoli Storage Manager
Command Line Administrative Interface - Version 5, Release 1, Level 1.0
(C) Copyright IBM Corporation 1990, 2002 All Rights Reserved.


Thank You

SD







Andrew Raibeck <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
12/30/2002 05:05 AM
Please respond to "ADSM: Dist Stor Manager"


To: [EMAIL PROTECTED]
cc:
Subject:Re: TSM Scheduler shows backups  completed successfully 
dsmerror.log
shows backups failed ?


You don't indicate which TSM client and server versions you are running,
nor do you indicate what the scheduled event is doing. In general, though,
I would say that this behavior is a probable bug and should be reported to
IBM support.

--

Starting with version 5.1, the output from QUERY EVENT FORMAT=DETAILED
should more accurately reflect the status of the scheduled event (See the
chapter on "Automating Tasks", section "Return codes from the command line
interface" in the client manual for details). As I mentioned above, you
did not say what the scheduled command was. However, some caveats for
scheduled events where ACTION=COMMAND:

1) If the command ends with a nonzero return code that is less than 12,
the event will be reported as "Complete" (note that QUERY EVENT
FORMAT=DETAILED will show the return code). This problem is described in
APAR IC35203.

2) If the command is executed asynchronously, then it is not possible for
TSM to track the outcome, in which case the event will be reported as
"Complete" with return code 0. For example:

;my script
start command1   ;command1 launched asynchronously
exit lastrc  ;command1 launched successfully, exits with rc 0

Note: the "scripts" in this post are written in a "pseudo" code to
illustrate my meaning, and do not represent actual working scripts.

If you wish to see a more accurate status reported to TSM, then the
command should be configured to run synchronously (if possible). For
example:

;my modified script
command1  ;run command1, wait for completion
exit lastrc   ;exits with rc from command1

3) If the command is a script that includes several commands, and each of
those commands may or may not end with return code 0, but ultimately the
script exits with a return code of 0, then the event will be reported as
"Complete" with return code 0. For instance, if the script does this:

;my script
command1  ;fails with lastrc = 4
command2  ;succeeds with lastrc = 0
exit lastrc   ;exits with rc 0

In this case, if you wish to see a more accurate status reported to TSM,
then the script will need to be modified to exit with a nonzero return
code as appropriate (i.e. the script will need to track the return code
from each command within the script, then exit with a nonzero return code
if any command fails). For instance:

;my modified script to exit with highest rc
set scriptrc = 0  ;initialize scriptrc
command1  ;fails with lastrc = 4
if lastrc > scriptrc then scriptrc = lastrc   ;scriptrc = 4
command2  ;succeeds with lastrc = 0
if lastrc > scriptrc then scriptrc = lastrc   ;scriptrc still = 4
exit scriptrc ;exits with rc 4

If the script contains commands that execute asynchronously, then it is
not possible for the script (or TSM) to track the outcome of the
asynchronous command(s). Refer to (2) above.

--

If you are not using the 5.1 client, then try the 5.1 client to see if it
makes a difference. If the 5.1 client still violates the behaviors
described above, then this is (probably) a bug and should be reported to
IBM support. For example, I would expect that 5.1 should report a
completion status of "Failed" for the behavior you describe.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: [EMAIL PROTECTED] (change eye to i to reply)

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough&qu

Re: TSM Scheduler shows backups completed successfully dsmerror.log shows backups failed ?

[Kathleen Hallahan]

This is an issue we have raised with Tivoli ourselves recently, even
requesting--and being turned down for-- a Design Change Request.  Their
recommendation was to check the dsmsched.logs on the clients.  This is
impossible for us and presumably for anyone in a large envorinment; we have
over 800 clients and I know there are organizations out there with many
more.  As it is, we've had to write an AIX script to catch the ones that
report as "In Progress," considering that they are rarely, if ever,
actually in progress at that time.  I have no idea how to chase down the
ones reporting as "Completed" when in fact they have not, on a daily basis
across our entire environment.  If anyone has any workable solutions I'd be
very interested in hearing them; I'm at a bit of a loss myself.





Mark Stapleton
  cc:
Sent by: Subject: Re: TSM Scheduler shows backups  
completed successfully
    "ADSM: Dist   dsmerror.log shows backups failed ?
Stor Manager"
<[EMAIL PROTECTED]
IST.EDU>


12/29/2002
09:58 PM
Please respond
to "ADSM: Dist
Stor Manager"






On Fri, 2002-12-27 at 14:07, shekhar Dhotre wrote:
>  q eve * * shows all backups are completing successfully but  clients
> dsmerror.log  file shows  schedule command failed ,How I can verify that
> these backups are completing successfully other than restore test?
>
> 26-12-2002 20:45:08 ANS1909E The scheduled command failed.
> 26-12-2002 20:45:08 ANS1512E Scheduled event 'EMEAPROD_HOT_DAILY' failed.

Remember that the *schedule* itself completed successfully. You're far
better off looking for the message numbers that appear in the summaries
that appear in the server activity log at the end of a successsful
backup. (I'm not within reach of a TSM server tonight, so I can't look
them ATM.)

This is a much better indicator of successful backups than the event
list.

--
Mark Stapleton ([EMAIL PROTECTED])

Re: TSM Scheduler shows backups completed successfully dsmerror.log shows backups failed ?

[Andrew Raibeck]

You don't indicate which TSM client and server versions you are running,
nor do you indicate what the scheduled event is doing. In general, though,
I would say that this behavior is a probable bug and should be reported to
IBM support.

--

Starting with version 5.1, the output from QUERY EVENT FORMAT=DETAILED
should more accurately reflect the status of the scheduled event (See the
chapter on "Automating Tasks", section "Return codes from the command line
interface" in the client manual for details). As I mentioned above, you
did not say what the scheduled command was. However, some caveats for
scheduled events where ACTION=COMMAND:

1) If the command ends with a nonzero return code that is less than 12,
the event will be reported as "Complete" (note that QUERY EVENT
FORMAT=DETAILED will show the return code). This problem is described in
APAR IC35203.

2) If the command is executed asynchronously, then it is not possible for
TSM to track the outcome, in which case the event will be reported as
"Complete" with return code 0. For example:

   ;my script
   start command1   ;command1 launched asynchronously
   exit lastrc  ;command1 launched successfully, exits with rc 0

Note: the "scripts" in this post are written in a "pseudo" code to
illustrate my meaning, and do not represent actual working scripts.

If you wish to see a more accurate status reported to TSM, then the
command should be configured to run synchronously (if possible). For
example:

   ;my modified script
   command1  ;run command1, wait for completion
   exit lastrc   ;exits with rc from command1

3) If the command is a script that includes several commands, and each of
those commands may or may not end with return code 0, but ultimately the
script exits with a return code of 0, then the event will be reported as
"Complete" with return code 0. For instance, if the script does this:

   ;my script
   command1  ;fails with lastrc = 4
   command2  ;succeeds with lastrc = 0
   exit lastrc   ;exits with rc 0

In this case, if you wish to see a more accurate status reported to TSM,
then the script will need to be modified to exit with a nonzero return
code as appropriate (i.e. the script will need to track the return code
from each command within the script, then exit with a nonzero return code
if any command fails). For instance:

   ;my modified script to exit with highest rc
   set scriptrc = 0  ;initialize scriptrc
   command1  ;fails with lastrc = 4
   if lastrc > scriptrc then scriptrc = lastrc   ;scriptrc = 4
   command2  ;succeeds with lastrc = 0
   if lastrc > scriptrc then scriptrc = lastrc   ;scriptrc still = 4
   exit scriptrc ;exits with rc 4

If the script contains commands that execute asynchronously, then it is
not possible for the script (or TSM) to track the outcome of the
asynchronous command(s). Refer to (2) above.

--

If you are not using the 5.1 client, then try the 5.1 client to see if it
makes a difference. If the 5.1 client still violates the behaviors
described above, then this is (probably) a bug and should be reported to
IBM support. For example, I would expect that 5.1 should report a
completion status of "Failed" for the behavior you describe.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: [EMAIL PROTECTED] (change eye to i to reply)

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




shekhar Dhotre <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
12/27/2002 13:07
Please respond to "ADSM: Dist Stor Manager"


    To: [EMAIL PROTECTED]
cc:
Subject:TSM Scheduler shows backups  completed successfully 
dsmerror.log shows
backups failed ?



Hi All ,

 q eve * * shows all backups are completing successfully but  clients
dsmerror.log  file shows  schedule command failed ,How I can verify that
these backups are completing successfully other than restore test?

26-12-2002 20:45:08 ANS1909E The scheduled command failed.
26-12-2002 20:45:08 ANS1512E Scheduled event 'EMEAPROD_HOT_DAILY' failed.
Retur


tsm: TSM>q eve * * begindate=today-1

Scheduled Start  Actual Start Schedule Name Node Name Status
  - -
-
12/26/02   01:00:00  12/26/02   01:02:06  AMERUAT_HOT_- F5N73 Completed
   DAILY
12/26/02   01:58:42  12/26/02   01:58:44  F2N17_CMD F2N17 Completed
12/26/02   02

Re: TSM Scheduler shows backups completed successfully dsmerror.log shows backups failed ?

[Mark Stapleton]

On Fri, 2002-12-27 at 14:07, shekhar Dhotre wrote:
>  q eve * * shows all backups are completing successfully but  clients
> dsmerror.log  file shows  schedule command failed ,How I can verify that
> these backups are completing successfully other than restore test?
>
> 26-12-2002 20:45:08 ANS1909E The scheduled command failed.
> 26-12-2002 20:45:08 ANS1512E Scheduled event 'EMEAPROD_HOT_DAILY' failed.

Remember that the *schedule* itself completed successfully. You're far
better off looking for the message numbers that appear in the summaries
that appear in the server activity log at the end of a successsful
backup. (I'm not within reach of a TSM server tonight, so I can't look
them ATM.)

This is a much better indicator of successful backups than the event
list.

--
Mark Stapleton ([EMAIL PROTECTED])

TSM Scheduler shows backups completed successfully dsmerror.log shows backups failed ?

[shekhar Dhotre]

Hi All ,

 q eve * * shows all backups are completing successfully but  clients
dsmerror.log  file shows  schedule command failed ,How I can verify that
these backups are completing successfully other than restore test?

26-12-2002 20:45:08 ANS1909E The scheduled command failed.
26-12-2002 20:45:08 ANS1512E Scheduled event 'EMEAPROD_HOT_DAILY' failed.
Retur


tsm: TSM>q eve * * begindate=today-1

Scheduled Start  Actual Start Schedule Name Node Name Status
  - -
-
12/26/02   01:00:00  12/26/02   01:02:06  AMERUAT_HOT_- F5N73 Completed
   DAILY
12/26/02   01:58:42  12/26/02   01:58:44  F2N17_CMD F2N17 Completed
12/26/02   02:25:29  12/26/02   02:32:57  F3N45_DAILY_- F3N45 Completed
   BACKUP
12/26/02   03:00:00  12/26/02   03:00:10  F2N29_DAILY_- F2N29 Completed
   BACKUP
12/26/02   05:00:00  12/26/02   05:01:15  F3N47_DAILY_- F3N47 Completed
   BACKUP
12/26/02   06:00:00  12/26/02   06:01:00  F3N43_DAILY_- F3N43 Completed
   BACKUP
12/26/02   09:00:00  12/26/02   12:06:30  CPD39_DAILY_- F3N37 Completed
   BACKUP
12/26/02   10:00:00  12/26/02   10:00:03  CPA35_DAILY   F3N35 Completed
12/26/02   19:00:00  12/26/02   19:13:01  EMEAPROD_HOT- F2N21 Completed
   _DAILY
12/26/02   19:18:00  12/26/02   19:19:30  SPCWS SPCWS01 Completed
12/26/02   19:35:00  12/26/02   19:48:18  TAHODEV_HOT_- F5N67 Completed
   DAILY
more...   ( to continue, 'C' to cancel)

tsm: TSM>q eve * *

Scheduled Start  Actual Start Schedule Name Node Name Status
  - -
-
12/27/02   01:00:00  12/27/02   01:01:20  AMERUAT_HOT_- F5N73 Completed
   DAILY
12/27/02   01:58:42  12/27/02   01:58:44  F2N17_CMD F2N17 Completed
12/27/02   02:25:29  12/27/02   02:32:59  F3N45_DAILY_- F3N45 Completed
   BACKUP
12/27/02   03:00:00  12/27/02   03:44:02  APUAT0_COLD_- F5N73 Completed
   DAILY
12/27/02   03:00:00  12/27/02   03:04:38  F2N29_DAILY_- F2N29 Completed
   BACKUP
12/27/02   05:00:00  12/27/02   05:06:44  F3N47_DAILY_- F3N47 Completed
   BACKUP
12/27/02   06:00:00  12/27/02   06:07:10  F3N43_DAILY_- F3N43 Completed
   BACKUP
12/27/02   09:00:00  12/27/02   11:47:14  CPD39_DAILY_- F3N37 Completed
   BACKUP
12/27/02   10:00:00  12/27/02   10:00:03  CPA35_DAILY   F3N35 Completed
12/27/02   11:00:00  12/27/02   11:06:23  APPROD_HOT_D- F2N21 Completed
   AILY

f2n21 /tsg/tsm>more dsmerror.log
26-12-2002 20:45:08 ANS1909E The scheduled command failed.
26-12-2002 20:45:08 ANS1512E Scheduled event 'EMEAPROD_HOT_DAILY' failed.
Retur
n code = 1.
27-12-2002 08:50:15 ANS1038S Invalid option specified
27-12-2002 08:50:15 ANS1820E Command line options must be preceded by a
'-'
27-12-2002 08:50:31 ANS1038S Invalid option specified
27-12-2002 08:50:31 ANS1820E Command line options must be preceded by a
'-'
27-12-2002 08:50:42 ANS1038S Invalid option specified
27-12-2002 08:50:42 ANS1820E Command line options must be preceded by a
'-'
27-12-2002 08:50:56 ANS1038S Invalid option specified
27-12-2002 08:50:56 ANS1820E Command line options must be preceded by a
'-'
27-12-2002 08:51:00 ANS1038S Invalid option specified
27-12-2002 08:51:00 ANS1820E Command line options must be preceded by a
'-'
27-12-2002 08:51:05 ANS1038S Invalid option specified
27-12-2002 08:51:05 ANS1820E Command line options must be preceded by a
'-'
27-12-2002 13:10:19 ANS1909E The scheduled command failed.
27-12-2002 13:10:19 ANS1512E Scheduled event 'APPROD_HOT_DAILY' failed.
Return
code = 1.
27-12-2002 13:10:19 ANS1005E TCP/IP read error on socket = 6, errno = 73,
reason
 : 'A connection with a remote socket was reset by that socket.'.

Thank You
SD

Re: dsm.opt / dsmerror.log / incl/excl oddity

[Andy Raibeck]

In both environments A and B, try the QUERY INCLEXCL command to see the
output differences. Maybe your MVS server has a client options set with
the EXCLUDE statement you are asking about.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: [EMAIL PROTECTED] (change eye to i to reply)

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




"Wholey, Joseph (TGA\\MLOL)" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
07/11/2002 06:57
Please respond to "ADSM: Dist Stor Manager"


To: [EMAIL PROTECTED]
    cc:
Subject:dsm.opt / dsmerror.log / incl/excl oddity



Envirionment A:
Client OS: NT 4
Client Version: Version 4, Release 2, Level 1.20
Server: Storage Management Server for MVS - Version 4, Release 2, Level
1.11

Environment B:
Client OS: NT 4
Client Version: Version 4, Release 2, Level 1.20
Server: Storage Management Server for MVS - Version 4, Release 1, Level
3.0

These clients are "cookie cutter" builds Starting from the OS down to the
dsm.opt (with the exception of the TSM server they point to).

Question:  Why is my dsmerror.log filling up with the following messages
in environmet B and not A when the directory structure and dsm.opt are
identical for both servers?

ANS1115W File '\\l06101s001\e$\Services\BUEXECV7\NT\reports\saved\empty'
excluded by Include/Exclude list

Any help would be appreciated.

Regards, Joe

dsm.opt / dsmerror.log / incl/excl oddity

[Wholey, Joseph (TGA\\MLOL)]

Envirionment A:
Client OS: NT 4
Client Version: Version 4, Release 2, Level 1.20
Server: Storage Management Server for MVS - Version 4, Release 2, Level 1.11

Environment B:
Client OS: NT 4
Client Version: Version 4, Release 2, Level 1.20
Server: Storage Management Server for MVS - Version 4, Release 1, Level 3.0

These clients are "cookie cutter" builds Starting from the OS down to the dsm.opt 
(with the exception of the TSM server they point to).

Question:  Why is my dsmerror.log filling up with the following messages in environmet 
B and not A when the directory structure and dsm.opt are identical for both servers?

ANS1115W File '\\l06101s001\e$\Services\BUEXECV7\NT\reports\saved\empty' excluded by 
Include/Exclude list

Any help would be appreciated.

Regards, Joe

Re: dsmerror.log location.

[Martin Trcka]

You can avoid this behavior by setting environmental variable DSM_LOG (f.e.
in user's profile for particular users, or in system wide profiles like
/etc/environment) pointing to the directory where your (let's say main)
dsmerror.log resides..

Best regards,
Martin Trcka

> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On
> Behalf Of Denis L'Huillier
> Sent: Monday, April 08, 2002 6:08 PM
> To: [EMAIL PROTECTED]
> Subject: Re: dsmerror.log location.
>
>
> Also,
> If you have other people loggin into the machine tsm will drop a
> dsmerror.log file in the current directory
> the user is in when they execute dsm/dsmc and there is an error condition.
>
> Likely the dsmerror.log files which are appearing in odd places are caused
> by users executing tsm.
> Look at the contents of the dsmerror.log file and see if the timestamp is
> during the backup cycle.
> I'll bet it's during the day.
>
> Regards,
>
> Denis L. L'Huiller
> 973-360-7739
> [EMAIL PROTECTED]
> Enterprise Storage Forms ->
> http://admpwb01/misc/misc/storage_forms_main.html
>
>
>
>
>   Pitur Ey~srsson
>
>   <[EMAIL PROTECTED]>   To:
> [EMAIL PROTECTED]
>
>   Sent by: "ADSM:  cc:
>
>   Dist StorSubject: Re:
> dsmerror.log location.
>
>   Manager"
>
>   <[EMAIL PROTECTED]
>
>   T.EDU>
>
>
>
>
>
>   04/08/2002 11:53
>
>   AM
>
>   Please respond
>
>   to "ADSM: Dist
>
>   Stor Manager"
>
>
>
>
>
>
>
>
>
> yes William the only place i know about where you can define the errorlog
> retention is in the dsm.sys file.
>
> you can do it like this
>
> ERRORLOGNAME %the path and the name of the errrolog file%
> ERRORLOGRETENTION %how long you are going to keep the log%
>
> Example
>
> ERRORLOGNAME /usr/tivoli/tsm/client/ba/dsmerror.log
> ERRORLOGRETENTION 10D
>
>
>
>
> Kvedja/Regards
> Petur Eythorsson
> Taeknimadur/Technician
> IBM Certified Specialist - AIX
> Tivoli Storage Manager Certified Professional
> Microsoft Certified System Engineer
>
> [EMAIL PROTECTED]
>
>  Nyherji Hf  Simi TEL: +354-569-7700
>  Borgartun 37105 Iceland
>  URL:http://www.nyherji.is
>
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
> Evans, William C
> Sent: 8. aprml 2002 15:02
> To: [EMAIL PROTECTED]
> Subject: dsmerror.log location.
>
>
> Folks,
>   While I S.A. about 16 TSM servers I am not a TSM administrator and know
> little about TSM other than how to install and config the client
> and how to
> kick off the scheduler.  However, I am responsible for the
> scheduled backup
> of these TSM servers to other servers and therein lies my dilema.  I am
> finding my dsmerror.log files all over the place which makes scripting to
> have them emailed to me every Monday morning a pain.  It was my
> understanding that you set up the location for your dsmsched and
> dsmerror.logs in your dsm.sys file along with their retention periods.  Is
> there somewhere else that those locations can be set?  On those servers
> where I'm finding these log files put in odd locations I find no entry in
> the dsm.sys file that would put them where they're being found.
> TIA,
> Bill
>
> Bill Evans, UNIX System Administrator
> Phone: 719.535.4194
> E-mail: [EMAIL PROTECTED]
> Pager: 1-800-759-  PIN 8775027415
> Sametime Connect: c-bill.evans
>
>  <<...OLE_Obj...>> ...the recognized global leader in ensuring clients
> achieve superior value in the digital economy
>
> =

Re: dsmerror.log location.

[Denis L'Huillier]

Also,
If you have other people loggin into the machine tsm will drop a
dsmerror.log file in the current directory
the user is in when they execute dsm/dsmc and there is an error condition.

Likely the dsmerror.log files which are appearing in odd places are caused
by users executing tsm.
Look at the contents of the dsmerror.log file and see if the timestamp is
during the backup cycle.
I'll bet it's during the day.

Regards,

Denis L. L'Huiller
973-360-7739
[EMAIL PROTECTED]
Enterprise Storage Forms ->
http://admpwb01/misc/misc/storage_forms_main.html


   

  Pétur Eyþórsson  

  <[EMAIL PROTECTED]>   To:  [EMAIL PROTECTED]   

  Sent by: "ADSM:  cc: 

  Dist StorSubject: Re: dsmerror.log location. 

  Manager" 

  <[EMAIL PROTECTED] 

  T.EDU>   

   

   

  04/08/2002 11:53 

  AM   

  Please respond   

  to "ADSM: Dist   

  Stor Manager"

   

   





yes William the only place i know about where you can define the errorlog
retention is in the dsm.sys file.

you can do it like this

ERRORLOGNAME %the path and the name of the errrolog file%
ERRORLOGRETENTION %how long you are going to keep the log%

Example

ERRORLOGNAME /usr/tivoli/tsm/client/ba/dsmerror.log
ERRORLOGRETENTION 10D




Kvedja/Regards
Petur Eythorsson
Taeknimadur/Technician
IBM Certified Specialist - AIX
Tivoli Storage Manager Certified Professional
Microsoft Certified System Engineer

[EMAIL PROTECTED]

 Nyherji Hf  Simi TEL: +354-569-7700
 Borgartun 37105 Iceland
 URL:http://www.nyherji.is


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Evans, William C
Sent: 8. apríl 2002 15:02
To: [EMAIL PROTECTED]
Subject: dsmerror.log location.


Folks,
  While I S.A. about 16 TSM servers I am not a TSM administrator and know
little about TSM other than how to install and config the client and how to
kick off the scheduler.  However, I am responsible for the scheduled backup
of these TSM servers to other servers and therein lies my dilema.  I am
finding my dsmerror.log files all over the place which makes scripting to
have them emailed to me every Monday morning a pain.  It was my
understanding that you set up the location for your dsmsched and
dsmerror.logs in your dsm.sys file along with their retention periods.  Is
there somewhere else that those locations can be set?  On those servers
where I'm finding these log files put in odd locations I find no entry in
the dsm.sys file that would put them where they're being found.
TIA,
Bill

Bill Evans, UNIX System Administrator
Phone: 719.535.4194
E-mail: [EMAIL PROTECTED]
Pager: 1-800-759-  PIN 8775027415
Sametime Connect: c-bill.evans

 <<...OLE_Obj...>> ...the recognized global leader in ensuring clients
achieve superior value in the digital economy

Re: dsmerror.log location.

[Pétur Eyþórsson]

yes William the only place i know about where you can define the errorlog
retention is in the dsm.sys file.

you can do it like this

ERRORLOGNAME %the path and the name of the errrolog file%
ERRORLOGRETENTION %how long you are going to keep the log%

Example

ERRORLOGNAME /usr/tivoli/tsm/client/ba/dsmerror.log
ERRORLOGRETENTION 10D




Kvedja/Regards
Petur Eythorsson
Taeknimadur/Technician
IBM Certified Specialist - AIX
Tivoli Storage Manager Certified Professional
Microsoft Certified System Engineer

[EMAIL PROTECTED]

 Nyherji Hf  Simi TEL: +354-569-7700
 Borgartun 37105 Iceland
 URL:http://www.nyherji.is


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Evans, William C
Sent: 8. apríl 2002 15:02
To: [EMAIL PROTECTED]
Subject: dsmerror.log location.


Folks,
  While I S.A. about 16 TSM servers I am not a TSM administrator and know
little about TSM other than how to install and config the client and how to
kick off the scheduler.  However, I am responsible for the scheduled backup
of these TSM servers to other servers and therein lies my dilema.  I am
finding my dsmerror.log files all over the place which makes scripting to
have them emailed to me every Monday morning a pain.  It was my
understanding that you set up the location for your dsmsched and
dsmerror.logs in your dsm.sys file along with their retention periods.  Is
there somewhere else that those locations can be set?  On those servers
where I'm finding these log files put in odd locations I find no entry in
the dsm.sys file that would put them where they're being found.
TIA,
Bill

Bill Evans, UNIX System Administrator
Phone: 719.535.4194
E-mail: [EMAIL PROTECTED]
Pager: 1-800-759-  PIN 8775027415
Sametime Connect: c-bill.evans

 <<...OLE_Obj...>> ...the recognized global leader in ensuring clients
achieve superior value in the digital economy

dsmerror.log location.

[Evans, William C]

Folks,
  While I S.A. about 16 TSM servers I am not a TSM administrator and know
little about TSM other than how to install and config the client and how to
kick off the scheduler.  However, I am responsible for the scheduled backup
of these TSM servers to other servers and therein lies my dilema.  I am
finding my dsmerror.log files all over the place which makes scripting to
have them emailed to me every Monday morning a pain.  It was my
understanding that you set up the location for your dsmsched and
dsmerror.logs in your dsm.sys file along with their retention periods.  Is
there somewhere else that those locations can be set?  On those servers
where I'm finding these log files put in odd locations I find no entry in
the dsm.sys file that would put them where they're being found.
TIA,
Bill

Bill Evans, UNIX System Administrator
Phone: 719.535.4194
E-mail: [EMAIL PROTECTED]
Pager: 1-800-759-  PIN 8775027415
Sametime Connect: c-bill.evans

 <<...OLE_Obj...>> ...the recognized global leader in ensuring clients
achieve superior value in the digital economy

Re: dsmerror.log location

[Herve CHIBOIS]

Hi

export DSM_LOG=/you_dir

in /etc/environment will fix your pb with log files...


Herve

Re: dsmerror.log location

[Seay, Paul]

I tried this and it worked fine for me.

However, I found out that the dsm.sys was orginally in the
/usr/tivoli/tsm/.../ba directory not the sub directory bin.  It is confusing
because the the .smp versions are in the /ba directory.  Make sure you are
modifying the right thing.

-Original Message-
From: Joshua S. Bassi [mailto:[EMAIL PROTECTED]]
Sent: Monday, December 03, 2001 7:08 PM
To: [EMAIL PROTECTED]
Subject: Re: dsmerror.log location


Try setting the DSM_LOG environment variable to the correct log
location.


--
Joshua S. Bassi
Independent IT Consultant
IBM Certified - AIX/HACMP, SAN, Shark
Tivoli Certified Consultant- ADSM/TSM
Cell (408)&(831) 332-4006
[EMAIL PROTECTED]

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]] On Behalf Of
Evans, William C
Sent: Monday, December 03, 2001 2:10 PM
To: [EMAIL PROTECTED]
Subject: dsmerror.log location

Sorry for the stupid question but I've recently noticed that, despite
the
fact that I have the location for the dsmerror.log specified in dsm.sys,
TSM
consistently places the error log under root.  What causes that and how
can
I correct it?
Thanks in advance,

Bill Evans, UNIX System Administrator
Phone: 719.535.4194
E-mail: [EMAIL PROTECTED]
Pager: 1-800-759-  PIN 8775027415
AIM: bievans4194
 <<...OLE_Obj...>>
the recognized global leader in ensuring clients achieve
superior value in the digital economy

Re: dsmerror.log location

[Joshua S. Bassi]

Try setting the DSM_LOG environment variable to the correct log
location.


--
Joshua S. Bassi
Independent IT Consultant
IBM Certified - AIX/HACMP, SAN, Shark
Tivoli Certified Consultant- ADSM/TSM
Cell (408)&(831) 332-4006
[EMAIL PROTECTED]

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]] On Behalf Of
Evans, William C
Sent: Monday, December 03, 2001 2:10 PM
To: [EMAIL PROTECTED]
Subject: dsmerror.log location

Sorry for the stupid question but I've recently noticed that, despite
the
fact that I have the location for the dsmerror.log specified in dsm.sys,
TSM
consistently places the error log under root.  What causes that and how
can
I correct it?
Thanks in advance,

Bill Evans, UNIX System Administrator
Phone: 719.535.4194
E-mail: [EMAIL PROTECTED]
Pager: 1-800-759-  PIN 8775027415
AIM: bievans4194
 <<...OLE_Obj...>>
the recognized global leader in ensuring clients achieve
superior value in the digital economy

dsmerror.log location

[Evans, William C]

Sorry for the stupid question but I've recently noticed that, despite the
fact that I have the location for the dsmerror.log specified in dsm.sys, TSM
consistently places the error log under root.  What causes that and how can
I correct it?
Thanks in advance,

Bill Evans, UNIX System Administrator
Phone: 719.535.4194
E-mail: [EMAIL PROTECTED]
Pager: 1-800-759-  PIN 8775027415
AIM: bievans4194
 <<...OLE_Obj...>>
the recognized global leader in ensuring clients achieve
superior value in the digital economy

Re: dsmerror.log

[Andrew Raibeck]

It's not necessarily an error, per se. Rather, this message is issued
whenever the scheduler service is terminated. For example, stopping the
TSM scheduler service explicitly or implicitly (like when you shut down
the system for reboot) will cause this message to be written to the error
log. Unless you are having some problem with backups (i.e. the scheduler
service is shutting down in the middle of the backup for no apparent
reason), these messages can be safely ignored.

There's probably room for improvement in the message text and when it gets
logged to help avoid confusion.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
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.




Patricia LeBlanc <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
11/17/2001 08:21
Please respond to "ADSM: Dist Stor Manager"


To: [EMAIL PROTECTED]
cc:
Subject:dsmerror.log



Does anyone know what this error is??  I'm seeing this alot in my
dsmerror.log.  Running on an NT client ver 4.1.2.12.  We are also running
the TDP for Exchange.


11/16/2001 09:16:07 ConsoleEventHandler(): Caught Logoff console event .
11/16/2001 09:16:07 ConsoleEventHandler(): Process Detached.

Thanks!
Pattie
Liberty Mutual

dsmerror.log

[Patricia LeBlanc]

Does anyone know what this error is??  I'm seeing this alot in my
dsmerror.log.  Running on an NT client ver 4.1.2.12.  We are also running
the TDP for Exchange.


11/16/2001 09:16:07 ConsoleEventHandler(): Caught Logoff console event .
11/16/2001 09:16:07 ConsoleEventHandler(): Process Detached.

Thanks!
Pattie
Liberty Mutual

Re: dsmerror.log, " ERROR: **llStrP == NULL in InsertSlashHack! "

[Pothula S Paparao]

check APAR IC29368.
also check ur vols (drives).
what the previous sucessful backup summary says??  run expiration and
observe the statistics.
regards
sreekumar.



Kent Monthei
   cc:
Sent by: Subject: dsmerror.log,  " ERROR: **llStrP 
== NULL in InsertSlashHack!
"ADSM: Dist   "
Stor Manager"
<[EMAIL PROTECTED]
IST.EDU>


11/03/2001
04:40
Please respond
to "ADSM: Dist
Stor Manager"





TSM Client for Tru64 Unix v4.1.2.0

The client dsmerror.log of a "failed" client contains these errors:
ERROR: **llStrP == NULL in InsertSlashHack!
ANS1074I *** User Abort ***

The 1st occurred 2 nights in a row; however the User Abort
(& client 'failed' event) only occurred the 2nd night.

I searched ADSM.ORG for InsertSlashHack, but found nothing.
Anyone else ever seen this error or know what it is?

-rsvp, thanks

Kent Monthei
GlaxoSmithKline

dsmerror.log, " ERROR: **llStrP == NULL in InsertSlashHack! "

[Kent Monthei]

TSM Client for Tru64 Unix v4.1.2.0

The client dsmerror.log of a "failed" client contains these errors:
ERROR: **llStrP == NULL in InsertSlashHack!
ANS1074I *** User Abort ***

The 1st occurred 2 nights in a row; however the User Abort
(& client 'failed' event) only occurred the 2nd night.

I searched ADSM.ORG for InsertSlashHack, but found nothing.
Anyone else ever seen this error or know what it is?

-rsvp, thanks

Kent Monthei
GlaxoSmithKline

sessSendVerb error in dsmerror.log

[Maurice van 't Loo]

Hi,

I see sessSendVerb errors in the dsmerror.log.
Does anybody knows what that meens?

AIX client version 4.1

18-09-2001 11:51:36 sessSendVerb: Error sending Verb, rc: -451
18-09-2001 12:08:58 sessSendVerb: Error sending Verb, rc: -451
19-09-2001 03:24:26 sessSendVerb: Error sending Verb, rc: -451
19-09-2001 03:26:15 sessSendVerb: Error sending Verb, rc: -451
19-09-2001 09:22:24 sessSendVerb: Error sending Verb, rc: -451
19-09-2001 10:50:57 sessSendVerb: Error sending Verb, rc: -451


Thanks,
   Maurice

dsmerror.log ownership issue

[mike_crawford]

We are having a problem with what seems to be the ownership of the dsmerror.log
file.  It is currently owned by root.  When we launch dsm as a non-root user,
it reports being unable to open dsmerror.log.

We tried to chown the file to the user, root retakes ownership of the file.


Client System is as follows:
SunOS 5.6
ADSM 3.1

This is the only client having this problem.  Anyone have any suggestions?

Thanks,
Mike

Re: dsmerror.log messages

[Chibois, Herve]

Hi

when you install TSM client, check the API check-box to install API support
files

in C:\Program Files\TSM\api\include\dsmrc.h contains all the Return Codes
used in TSM.

Bye
rv

> -Message d'origine-
> De : George Lesho [mailto:[EMAIL PROTECTED]]
> Envoyé : mercredi 28 mars 2001 22:20
> À : [EMAIL PROTECTED]
> Objet : Re: dsmerror.log messages
> 
> 
> How do you check an RC code or as you put it  "check an API"???
> thanks
> 
> George Lesho
> Storage/System Admin
> AFC Enterprises
> 
> 
> 
> 
> 
> 
> "Chibois, Herve" <[EMAIL PROTECTED]> on 03/28/2001 08:21:41 AM
> 
> Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
> 
> To:   [EMAIL PROTECTED]
> cc:(bcc: George Lesho/Partners/AFC)
> Fax to:
> Subject:  Re: dsmerror.log messages
> 
> 
> 
> Hi Don,
> 
> check the API #define DSM_RC_REJECT_ID_UNKNOWN  53
> 
> Don't you have a postSched command that tries to connect w/ 
> an invalid user
> ?
> 
> rv
> 
> > -Message d'origine-
> > De : Don Matush [mailto:[EMAIL PROTECTED]]
> > Envoy
> 

Re: dsmerror.log messages

[George Lesho]

How do you check an RC code or as you put it  "check an API"???
thanks

George Lesho
Storage/System Admin
AFC Enterprises






"Chibois, Herve" <[EMAIL PROTECTED]> on 03/28/2001 08:21:41 AM

Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>

To:   [EMAIL PROTECTED]
cc:(bcc: George Lesho/Partners/AFC)
Fax to:
Subject:  Re: dsmerror.log messages



Hi Don,

check the API #define DSM_RC_REJECT_ID_UNKNOWN  53

Don't you have a postSched command that tries to connect w/ an invalid user
?

rv

> -Message d'origine-
> De : Don Matush [mailto:[EMAIL PROTECTED]]
> Envoy


é : mercredi 28 mars 2001 16:13
> À : [EMAIL PROTECTED]
> Objet : dsmerror.log messages
>
>
> Server MVS  TSM 4.1.3
> Client   AIX 4.3  TSM 4.1.2
>
> The backups run with out failure. Everything appears to be normal.
> But I get the following messages in the dsmerror.log. There are no
> error messages in the server activity log.
>
> 03/28/01   01:30:01 cuSignOnResp: Server rejected session;
> result code: 53
> 03/28/01   01:30:52 cuSignOnResp: Server rejected session;
> result code: 53
>
> Has anyone seen these messages or know what I should do to correct the
> problem.
>
> Thanks,
>
> Don ...
>

Re: dsmerror.log messages

[Chibois, Herve]

Hi Don,

check the API #define DSM_RC_REJECT_ID_UNKNOWN  53

Don't you have a postSched command that tries to connect w/ an invalid user
?

rv

> -Message d'origine-
> De : Don Matush [mailto:[EMAIL PROTECTED]]
> Envoyé : mercredi 28 mars 2001 16:13
> À : [EMAIL PROTECTED]
> Objet : dsmerror.log messages
> 
> 
> Server MVS  TSM 4.1.3
> Client   AIX 4.3  TSM 4.1.2
> 
> The backups run with out failure. Everything appears to be normal.
> But I get the following messages in the dsmerror.log. There are no
> error messages in the server activity log.
> 
> 03/28/01   01:30:01 cuSignOnResp: Server rejected session; 
> result code: 53
> 03/28/01   01:30:52 cuSignOnResp: Server rejected session; 
> result code: 53
> 
> Has anyone seen these messages or know what I should do to correct the
> problem.
> 
> Thanks,
> 
> Don ...
> 

dsmerror.log messages

[Don Matush]

Server MVS  TSM 4.1.3
Client   AIX 4.3  TSM 4.1.2

The backups run with out failure. Everything appears to be normal.
But I get the following messages in the dsmerror.log. There are no
error messages in the server activity log.

03/28/01   01:30:01 cuSignOnResp: Server rejected session; result code: 53
03/28/01   01:30:52 cuSignOnResp: Server rejected session; result code: 53

Has anyone seen these messages or know what I should do to correct the
problem.

Thanks,

Don ...

Re: Errors in the DSMerror.log file.... Help

[Malbrough, Demetrius]

-Alan-

This might be why you are getting these errors in the dsmerror.log: Within
one dsmc session, 3 consequentive query backups are issued with quotes
surrounding the filespeciation with a wildcard and the 2nd  query command
uses the options -todate and -fromdate.

For example:

# dsmc -se=ewathens
ADSTAR Distributed Storage Manager
Command Line Backup Client Interface - Version 3, Release 1, Lev
(C) Copyright IBM Corporation, 1990, 1998, All Rights Reserved.
dsmc> q backup "/home/ericka/d*"
Node Name:   established with server ADSM: AIX-RS/6000
  Server Version 3, Release 1, Level 1.3
  Server date/time: 06/24/1998 10:00:20  Last access: 06/24/1998
 Size  Backup Date Mgm A/I File
25  06/23/1998 17:11:56 DEFAULT  A  /home/ericka/dsm.opt
   973  06/23/1998 17:11:56 DEFAULT  A  /home/ericka/dsm.opt.smp
43,600  06/24/1998 09:48:33 DEFAULT  A  /home/ericka/dsmerror.30
   461  06/24/1998 09:48:33 DEFAULT  A  /home/ericka/dsmerror.lo
dsmc> q backup "/home/ericka/d*" -fromdate=06/23/1998
-todate=06/24/1998
 Size  Backup Date Mgm A/I File

25  06/23/1998 17:11:56 DEFAULT  A  /home/ericka/dsm.opt
   973  06/23/1998 17:11:56 DEFAULT  A  /home/ericka/dsm.opt.smp
43,600  06/24/1998 09:48:33 DEFAULT  A  /home/ericka/dsmerror.30
   461  06/24/1998 09:48:33 DEFAULT  A  /home/ericka/dsmerror.lo
dsmc> q backup "/home/ericka/d*"
ANS1102E Excessive number of command line arguments passed to
 the program!
ANS1133W An expression might contain a wildcard not enclosed
 in quotes
dsmc> quit

Local Fix:
1.  Do not use the quotes around the file specification.
2.  Place a space behind the closing quote for the 3rd query.

Thanks,
Demetrius Malbrough
TSM Consultant

-Original Message-
From: Sulzer, Alan [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 09, 2001 8:49 AM
To: [EMAIL PROTECTED]
Subject: Errors in the DSMerror.log file Help


I am getting the following errors in the /dsmerror.log file constantly. If
any one has an idea why this seems to be happening, I am all ears.

ANS1102E Excessive number of command line arguments passed t
o the program!
ANS1133W An expression might contain a wildcard not enclosed
 in quotes

They seemed to start up all of a sudden.  My UNIX adminer removed some of
the data so it is relatively impossible to state with 100% accuracy what
changed on the systems that could have caused this.

Does any one have any idea what is causing this?  Here is some more details
if you need them.  We have no dsmc client listener processes running on the
client box for either nodes. We have two node names defined on the TSM
server for the client host. One node name is defined for the normal client
and the other node name is defined for the TDP API client.  I believe the
TSM adminer has tried to expire or disable the node from the policy domains
so as to render them inactive.

Any help would be appreciated.

Alan Sulzer
Informix DBA
Unity Health
(314) 364-3164
[EMAIL PROTECTED]

Errors in the DSMerror.log file.... Help

[Sulzer, Alan]

I am getting the following errors in the /dsmerror.log file constantly. If
any one has an idea why this seems to be happening, I am all ears.

ANS1102E Excessive number of command line arguments passed t
o the program!
ANS1133W An expression might contain a wildcard not enclosed
 in quotes

They seemed to start up all of a sudden.  My UNIX adminer removed some of
the data so it is relatively impossible to state with 100% accuracy what
changed on the systems that could have caused this.

Does any one have any idea what is causing this?  Here is some more details
if you need them.  We have no dsmc client listener processes running on the
client box for either nodes. We have two node names defined on the TSM
server for the client host. One node name is defined for the normal client
and the other node name is defined for the TDP API client.  I believe the
TSM adminer has tried to expire or disable the node from the policy domains
so as to render them inactive.

Any help would be appreciated.

Alan Sulzer
Informix DBA
Unity Health
(314) 364-3164
[EMAIL PROTECTED]

Re: HPUX11 tsm client 3.7.2 message in dsmerror.log

[Thiha Than]

hi Eric,

For now, you cannot use TDPO and Image utility together at 3.7.2 level.  We
are working on the solution.

regards,
Thiha

>Yes, I have installed HP TDP Oracle v2.1.10 and according to APAR IC27223
>replaced v3.7.2 libApiDS.sl with a v3.7.1 libApiDS.sl.
>Yesterday I found that dsmc works fine with v3.7.2 libApiDS.sl but error
>message "/opt/tivoli/tsm/client/ba/bin/plugins/libPiIMG.sl failed, errno:
>215 "  when v3.7.1 libApiDS.sl is used. Have raised pmr 02508,000,738.
>Is there any further workaround so that I can use v3.7.2 client with TDP
>for Oracle?

Re: HPUX11 tsm client 3.7.2 message in dsmerror.log

[Eric Tang]

Hi Thiha,

Yes, I have installed HP TDP Oracle v2.1.10 and according to APAR IC27223
replaced v3.7.2 libApiDS.sl with a v3.7.1 libApiDS.sl.
Yesterday I found that dsmc works fine with v3.7.2 libApiDS.sl but error
message "/opt/tivoli/tsm/client/ba/bin/plugins/libPiIMG.sl failed, errno:
215 "  when v3.7.1 libApiDS.sl is used. Have raised pmr 02508,000,738.
Is there any further workaround so that I can use v3.7.2 client with TDP
for Oracle?
Thanks.

Regards,
Eric Tang

HPUX11 tsm client 3.7.2 message in dsmerror.log

[Thiha Than]

hi Eric,

Oracle connect agent 2.1.10 works with TSM 3.7.1 API only.  I think you
have V3.7.2 b/a client, image library (libPiIMG.sl), and V3.7.1 API
installed on your machine.  Image library needs API level (3.7.2) to be
loaded successfully.  That might be the reason that you are seeing the
error you described.

regards,
Thiha


>I am upgrading HP-UX11.0  ADSM client from v3.1 to v3.7.2 & connectAgent
>v2.1.7 to TDP Oracle v2.1.10. (AIX ADSM Server v3.1.2.57)

>After upgrade, dsmc can be invoked and backup/restore is working, however
>the following message is displayed in dsmerror.log once dsmc is invoked.

>12/18/00   23:19:00 shl_load() of
>/opt/tivoli/tsm/client/ba/bin/plugins/libPiIMG.sl failed, errno: 215

>IBM support suggests the uninstall of old ADSM client is not clean, so I
>swremove the 3.7.2 client & TDP Oracle; also manually remove the /usr/adsm
>& /usr/adsmagent old directories and swinstall TSM 3.7.2 client and TDP
>Oracle again.

>But there is still the same error message in dsmerror.log when invoking
>dsmc. Anyone encounters this before? Thanks in advance.

Re: HPUX11 tsm client 3.7.2 message in dsmerror.log

[David Longo]

>From past experience with general UNIX problems, this looks like a Shared Library 
>problem.  As you upgraded from ADSM to TSM the directory paths changed.  

Do you have any environment variables that need to be changed?  Do you have any like a 
"LIBPATH" setup?


David B. Longo
Systems Administrator
Health First, Inc. I/T
3300 Fiske Blvd.
Rockledge, FL 32955-4305
PH  321.434.5536
Pager  321.634.8230
Fax:321.434.5525
[EMAIL PROTECTED]



>>> [EMAIL PROTECTED] 12/18/00 10:44AM >>>
Hi All,

I am upgrading HP-UX11.0  ADSM client from v3.1 to v3.7.2 & connectAgent
v2.1.7 to TDP Oracle v2.1.10. (AIX ADSM Server v3.1.2.57)

After upgrade, dsmc can be invoked and backup/restore is working, however
the following message is displayed in dsmerror.log once dsmc is invoked.

12/18/00   23:19:00 shl_load() of
/opt/tivoli/tsm/client/ba/bin/plugins/libPiIMG.sl failed, errno: 215

IBM support suggests the uninstall of old ADSM client is not clean, so I
swremove the 3.7.2 client & TDP Oracle; also manually remove the /usr/adsm
& /usr/adsmagent old directories and swinstall TSM 3.7.2 client and TDP
Oracle again.

But there is still the same error message in dsmerror.log when invoking
dsmc. Anyone encounters this before? Thanks in advance.


Regards,
Eric Tang

HPUX11 tsm client 3.7.2 message in dsmerror.log

[Eric Tang]

Hi All,

I am upgrading HP-UX11.0  ADSM client from v3.1 to v3.7.2 & connectAgent
v2.1.7 to TDP Oracle v2.1.10. (AIX ADSM Server v3.1.2.57)

After upgrade, dsmc can be invoked and backup/restore is working, however
the following message is displayed in dsmerror.log once dsmc is invoked.

12/18/00   23:19:00 shl_load() of
/opt/tivoli/tsm/client/ba/bin/plugins/libPiIMG.sl failed, errno: 215

IBM support suggests the uninstall of old ADSM client is not clean, so I
swremove the 3.7.2 client & TDP Oracle; also manually remove the /usr/adsm
& /usr/adsmagent old directories and swinstall TSM 3.7.2 client and TDP
Oracle again.

But there is still the same error message in dsmerror.log when invoking
dsmc. Anyone encounters this before? Thanks in advance.


Regards,
Eric Tang

ADSM reoccurring message in dsmerror.log

[Garrott, Brad M.]

Hello,

I am running my client process on an hp platform and receiving the
following message in my dsmerror.log every day:
sessInit: Starting communications initialization
sessInit: Transitioning: SInit state ===> sTRANSERR state

The server has one scheduled time for my backups to be taken and the
client has the dsmc process running on it waiting to be contacted by the
server.  Can anyone tell me how to stop this message from being output to my
dsmerror.log so that it will quit filling up the file?

Any help that you can provide me will be greatly appreciated.  Thank
you.

Brad Garrott