Matching node number to node name?

2003-10-23 Thread Joe Howell
I'm seeing a couple of messages in my activity log:

ANR0538I A resource waiter has been aborted.
ANRD IMFS(3570): ThreadId6027 Lock conflict error in obtaining sLock for node 
39, filespace 7

I see these several times during my backup cycle.  I'm also seeing problems with 
throughput from many of my clients and the backups aren't completing.  I'm guessing 
that there's a connection and that whatever contention is causing these messages to be 
generated is also preventing my backups from running.  Unfortunately I don't have a 
node named 39 and I don't see a column name to contain a node_number in the 
database.  Anybody know how I can figure out which client this is?

TSM 5.1.5 on OS/390, all Win2K clients running TSM 5.1.6 or higher.


Joe Howell
Shelter Insurance Companies
Columbia, MO

-
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search


Re: Matching node number to node name?

2003-10-23 Thread Richard Sims
...
ANRD IMFS(3570): ThreadId6027 Lock conflict error in obtaining sLock for node 
39, filespace 7
...

Joe - I regret that I haven't the knowledge to advise on getting the nodename
  from the number; but you may see nearby messages about a client session
failing as a result, or the like.

You may be able to compensate for this problem by reducing the simultaneity of
sessions and processes, or by increasing server option RESOURCETimeout if
it is rather small (the default in v5 is 60 minutes, boosted from its
introductory value of 10 due to too many customer db contention problems).
But this may be a product problem that you need to refer to TSM Support.

  Richard Sims, BU


Re: Matching node number to node name?

2003-10-23 Thread Joe Howell
Thanks - I talked with support and they're going to send me some 'show' commands that 
I can run to find out what the problem is.  I've not been able to pin down exactly 
what the node_name to node_number relationship is using the database (yet!).   My 
concern is that some sort of global table lock is happening and that's causing 
problems for my backups.

Richard Sims [EMAIL PROTECTED] wrote:...
ANRD IMFS(3570): ThreadId6027 Lock conflict error in obtaining sLock for node 
39, filespace 7
...

Joe - I regret that I haven't the knowledge to advise on getting the nodename
from the number; but you may see nearby messages about a client session
failing as a result, or the like.

You may be able to compensate for this problem by reducing the simultaneity of
sessions and processes, or by increasing server option RESOURCETimeout if
it is rather small (the default in v5 is 60 minutes, boosted from its
introductory value of 10 due to too many customer db contention problems).
But this may be a product problem that you need to refer to TSM Support.

Richard Sims, BU


Joe Howell
Shelter Insurance Companies
Columbia, MO

-
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search


Re: Matching node number to node name?

2003-10-23 Thread Fred Johanson
Joe,

Good luck.  In my case it was DISKVOLID9.  It took months to find and
resolve the problem.
At 11:29 AM 10/23/2003 -0700, you wrote:
Thanks - I talked with support and they're going to send me some 'show'
commands that I can run to find out what the problem is.  I've not been
able to pin down exactly what the node_name to node_number relationship is
using the database (yet!).   My concern is that some sort of global table
lock is happening and that's causing problems for my backups.
Richard Sims [EMAIL PROTECTED] wrote:...
ANRD IMFS(3570): ThreadId6027 Lock conflict error in obtaining
sLock for node 39, filespace 7
...
Joe - I regret that I haven't the knowledge to advise on getting the nodename
from the number; but you may see nearby messages about a client session
failing as a result, or the like.
You may be able to compensate for this problem by reducing the simultaneity of
sessions and processes, or by increasing server option RESOURCETimeout if
it is rather small (the default in v5 is 60 minutes, boosted from its
introductory value of 10 due to too many customer db contention problems).
But this may be a product problem that you need to refer to TSM Support.
Richard Sims, BU

Joe Howell
Shelter Insurance Companies
Columbia, MO
-
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search


node number??

2001-12-19 Thread Karel Bos

The following error occured

12/19/2001 15:07:52  ANR0871E Cannot find file space name for node 85, file
space  1073741823.

How can I see which node node 85 is and what filespace 1073741823?

Thanx in advance.



Re: node number??

2001-12-19 Thread Kevin

Hello.

Query Filespace will work to find the Filespace, or I think query
occupancy.

Q fi nodename f=d.
Q occ.

I've never seen a node reported as a number before so I can't help you
there.

Kevin.


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]] On Behalf Of
Karel Bos
Sent: Wednesday, December 19, 2001 9:42 AM
To: [EMAIL PROTECTED]
Subject: node number??

The following error occured

12/19/2001 15:07:52  ANR0871E Cannot find file space name for node 85,
file
space  1073741823.

How can I see which node node 85 is and what filespace 1073741823?

Thanx in advance.



Re: node number??

2001-12-19 Thread Henk ten Have

On 19-Dec-01 Karel Bos wrote:
 12/19/2001 15:07:52  ANR0871E Cannot find file space name for node 85, file
 space  1073741823.

This is an old problem and fixed in 4.1.4.

 How can I see which node node 85 is and what filespace 1073741823?

You can't.

Cheers,
Henk ten Have