Ray,
I don't know if you are experiencing the same thing we have, but we to have
an application which is constructed such that if the loc attr is not set
correctly on the DR server/app, one cannot successfully run the
application. We found that in running buldacct on a nightly basis on our
production box and transferring buldjob1 and buldjob2 over to the DR server
to insure that all users created on the production server are replicated on
the DR server, that buldacct does not 'honor' the loc attr from the
production server. Thus, every time we stream the buldjobs on the DR we
must insure that a altacct xxx;locattr=-1 and altuser mgr.xxx;locsttr=-1
are set AFTER the buljob1 runs. (The local attribute for the application is
"-1").
Could this be your dilemma ?
Regards,
Reid E. Baxter
Raymond Familar
<far_north_flip@Y To: [log in to unmask]
AHOO.COM> cc:
Sent by: HP-3000 Subject: [HP3000-L] MPE local attribute on userid
Systems
Discussion
<[log in to unmask]
tc.edu>
12/06/2005 10:13
AM
Please respond to
Raymond Familar
Hello.
I recently performed a failover test for an applicaiton that tracks some
userid information. The local attribute (LOC ATTR) is tracked, so when a
user logs in on the DR system, if their LOC ATTR does not match, then they
cannot log in. I do not recall this being much of an issue in past DR
tests, so I assume they matched during the last test (6-12 months ago).
Under what circumstances would a userid LOC ATTR be changed. We use Vesoft
Sec/3000 in our environment.
Thanks.
Ray
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
