RESOURceutilization is an option which can be defined in a client option
set on the server.
The other possibility is that Node_B is indeed connecting and is having
NODename=Node_A in some dsm.sys stanza.
In fact I cannot recall when address seen in Nodes table is updated -
during client operations or when scheduler is connecting.

Zlatko Krastev
IT Consultant






"Wholey, Joseph (IDS DM&DS)" <joseph_wholey AT ML DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
20.09.2003 05:11
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        TCP/IP NAME TCP/IP ADDRESS


Need a little assistance on this.
I issue "q node f=d" from the server side for a NODE_A, I get a TCP/IP
NAME and TCP/IP ADDRESS that are incorrect (say NODE_B).
At some point I may have connected virtually w/ the TCP/IP NAME (NODE_B)
that I'm seeing, but even after I connect from the local host, NODE_A, the
 TCP/IP NAME and TCP/IP ADDRESS still reflect
NODE_B's information.
I've seen this on a few instances.  What drew this to my attention is the
fact that I had 8 sessions started for one archive on NODE_A and no
"resource" definition in the dsm.sys.  When I checked the
dsm.sys on NODE_B, lo and behold, resource utilization is set to 10.  What
am I missing?

Server Platform Z/os  running TSM Server v5,1,6.1
NODE_A Client Platform Sun2.8 running BAclient TSMv4,2,2.1
NODE_B Client Platform Sun2.8 running BAclient TSMv4,2,1.0

Any help would be greatly appreciated.  thx.