If your client is running a read-only map, which means that one is up on
the server or on another client that has it read-write, then you will see
status chnages but not new additions to the map.  This is the limitation of
shared maps and has always been the case.  No new items and no alterations
will take place on a read-only map until it is refreshed, only color
chnages due to changing status.  This included no new interfaces cards and
no new items in a smartset collection.  Sorry to disappoint you but this is
entirely normal.

This is one big reason why many people prefer the web client, since it
continually publishes new copies of the server map all on its own.

James Shanks
Team Leader, Level 3 Support
Tivoli NetView for UNIX and NT


John Mackney <john.mackney AT uk.logical DOT com>@tkg.com on 07/09/2001 05:55:22
AM

Please respond to IBM NetView Discussion <nv-l AT tkg DOT com>

Sent by:  owner-nv-l AT tkg DOT com


To:   "Netview Support list (E-mail)" <nv-l AT tkg DOT com>
cc:
Subject:  [NV-L] Client does not reflect Server MAP changes





We have a NetView server (running on SUN Solaris 2.8) and a NetView client
(AIX 4.3.3). The client has the NetView server databases and conf
directories mounted with NFS.

The client only shows the correct state of the NetView Server MAP when a
manual refresh is performed. Shouldn't the client map update automatically.
When we first installed the client, the maps on the client and the server
stayed in synch. We can't explain why it doesn't happen now. We have
severed the client/server link and joined them up again, but it hasn't
helped.

Any suggestions?

John Mackney

Technical Design Authority

Logical eBOC

Logical (UK) Ltd.

Email:      john.mackney AT uk.logical DOT com