The users workspaces will not affect which map opens.
Check the message from James, what you can do is copy
the /usr/OV/app-defaults/OVw file to the users home
directory and edit the OVw*mapname variable to WANmap.
I think this should work as you want it to. There are
a number of variables that can be changed the same
way with any file in app-defaults, take some time to
look around in there(and always keep a backup!) you
might be surprised by what you find.
I renamed the map to "Default" originally and it still didn't work, so I
renamed it to "default" and it works fine. I don't understand why we can
rename it to "WANmap" and it opens fine as root, but will not open as user.
Also, I set a variable a while back in a Netview config file allowing each
user to setup their own workspaces and it saves it within their user
NvEnvironments directories. Now I can't remember which Netview file I made
this change to... any help would be great.
From: Paul [mailto:firstname.lastname@example.org]
Sent: Monday, December 22, 2003 7:34 AM
Subject: Re: [nv-l] maps + solaris accounts problem
Try setting WANmap as the default for that user or have you already done
that? NetView by default wants to open the map named Default, you have to
change this behavior.
So either, someone changed the default map for root to WANmap or there is an
alias or something in roots environment that is causing this to happen. I
would be willing to be when the user is starting the map, it is trying to
open the Default map.
When we log on as root and start "netview", it opens our Default map
named "WANmap" just fine, yet when we use a standard user account and
try and execute "netview", it begins loading Netview and when it needs
to open the map, it crashes out and we get an error in the nv6000.log file
ovw:Cannot open map
We found that if the user executes "netview -map WANmap" it opens
fine. Why doesn't it open the map when executing "netview"? Is there
a file that requires the map to be named "default"? Where is this
file? We have had a ticket open with IBM now for over 2 weeks and
they haven't been able to help us find the problem here, any help would be
Az Dept of Trans