[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | *OLD* ALL-IN-1 (tm) Support Conference |
Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
Moderator: | IOSG::PYE |
|
Created: | Thu Jan 30 1992 |
Last Modified: | Tue Jan 23 1996 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 4343 |
Total number of notes: | 18308 |
3815.0. "Reverse Lookup Addresses And Edit Profile" by ZUR01::WORK19::BURKHALTER (Rolf Burkhalter @RLE) Wed Jan 26 1994 15:43
Hi
ALL-IN-1 V3.0A
I have several reverse lookup addresses defined in my DDS entry, for
example:
Master copy owning node : ZUR01
MHS/VMS address number : 1
MHS/VMS address part : ZUR01
MHS mailbox : AM
MHS User identifier : BURKHALTER
MHS/VMS address number : 2
MHS/VMS address part : ZUR01
MHS mailbox : A1
MHS User identifier : BURKHALTER
MHS/VMS address number : 3
MHS/VMS address part : PCSA01
MHS mailbox : AM
MHS User identifier : BURKHALTER
If I now edit my profile entry in MGT MUA (for example change the initial
field), and then check my DDS entry in MBMAN, the changes are made, but the
ALL-IN-1 lookup address will be written to the first reverse lookup
address and not the one it was before (2nd). My DDS entry in MBMAN looks
then:
Master copy owning node : ZUR01
MHS/VMS address number : 1
MHS/VMS address part : ZUR01 <
MHS mailbox : A1 < <---
MHS User identifier : BURKHALTER <
MHS/VMS address number : 2
MHS/VMS address part : ZUR01
MHS mailbox : A1
MHS User identifier : BURKHALTER
MHS/VMS address number : 3
MHS/VMS address part : PCSA01
MHS mailbox : AM
MHS User identifier : BURKHALTER
As you can see I now have two entries for the A1 mailbox, but my AM mailbox
entry has been overwritten.
Is this a known problem and how can I prevent ALL-IN-1 from writting the
reverse lookup address for ALL-IN-1 to MHS/VMS address number 1?
Any help will be appreciated
Rolf
T.R | Title | User | Personal Name | Date | Lines |
---|
3815.1 | used to be known | AIMTEC::WICKS_A | Atlanta's Most (In)famous Welshman | Wed Jan 26 1994 16:58 | 9 |
| Rolf,
I think it has worked this way since ALL-IN-1 v2.3 was released in
1989. It was in the v2.3 release notes but what happened after that
I don't remember.
Regards,
Andrew.D.Wicks
|
3815.2 | Used to update 2nd but that was a bug | IOSG::COTTINGHAM | | Wed Jan 26 1994 18:22 | 8 |
| Rolf,
I remeber a bug in V2.3 or V2.4 where multiple Reverse Lookups caused
ALL-IN-1 to incorrectly update the 2nd entry. It should and now will
always update the 1st ORADDR
Regards
Alan
|