[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference iosg::all-in-1_v30

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

790.0. "dds entry disappearing" by MLNTSC::PASSALACQUA () Wed Jun 03 1992 10:31

    Hi all,
    
    a customer of mine using vms 5.4-2 all-in-1 2.4 and DDS, has the
    following problem:
    
    after a modification of a user in all-in-1 profile, the correspon-
    ding entry in DDS file disappears. In the all-in-1 profile the
    pointer to DDS is present, but no information on DDS file.
    
    I did some test on my system, but no similar problem.
    
    This stange behaviour is quite random, so I really don't know what
    to suggest him.
    
    He is working in a cluster, 3 nodes all world search node, and he
    uses deferred uptate.
    
    Any suggestion will be grattly appreciated.
    
    Ciao
    Sonia
    
T.RTitleUserPersonal
Name
DateLines
790.1Duplicate MANAGER entries in MBMAN?AIMTEC::LAMBERSON_MWed Jun 03 1992 13:4964
    I have seen this problem caused by "duplicate" MANAGER entries in MBMAN
    with ALL-IN-1 linked to the second entry.
    
    MBMAN>SHO DDS SUB/FULL/SURNAME="MANAGER"
    
    You should only see 1 entry owned by the cluster alias. If you see more
    than one entry, look to see if they have the "Proxy user agent" field
    filled in with "OA$alias$ALLIN1" (alias = cluster alias).
    
    If there are two entries use the following commands at the ALL-IN-1
    menu level to see the DDSID fields for the entries.
    
    DIR SMD <RETURN>
    MANAGER <RETURN> (you will now see all the MANAGER entries from DDS)
    
    Use the <SELECT> key to select one on the entries owned by your cluster
    and then enter the following command to see the DDSID.
    
    <GET OA$SCROLL_ADDRESS:32:2  (The DDSID will be displayed for the
    selected entry, save the information)
    
    Do this for each entry owned by the cluster. Then <EXIT SCREEN> back to
    the menus.
    
    To see the current value for DDSID for the MANAGER profil record use
    the following command.
    
    <GET PROFIL.DDSID["MANAGER"]
    
    Compare the values to determine which MBMAN entry is linked to
    ALL-IN-1 MANAGER. If the entry in MBMAN that is linked has the correct
    information (Proxy, Reverse lookup, etc.) then deleting the non-linked
    entry in MBMAN may solve the problem.
    
    MBMAN>DEL DDS SUB/FULL/SURNAME=MANAGER (this command will prompt you
    for which entry to delete. The entries will appear in the same order
    from first to last as occurred during the SMD command used earlier. You
    may have to be in SYSTEM or MBMANAGER to perform this step)
    
    
    Example of a "good" entry under Message Router V3.2 
    
	Given name			: System
	Surname				: Manager
	Position or role		: *** SUTHRN ***
	Name				: ALL-IN-1 System Manager
	Reverse lookup			: MANAGER@A1@SUTHRN
	Unique subscriber identifier	: OA$SUTHRN$ALLIN1
	Proxy user agent		: OA$SUTHRN$ALLIN1
	Master copy owning node		: SUTHRN
	MHS/VMS address number		: 1
		MHS/VMS address part	: SUTHRN
		MHS mailbox		: A1
		MHS User identifier	: MANAGER
	Access Time			: 13-MAR-1992 10:02:10.13
	Update Time			:  5-MAY-1992 23:28:21.93
	DDSID				: 21280A800095783D8D7FF8409E710000
 
    If none of the entries are correct then cleaning up from the previous
    adoption and re-adopting the Mail Directory may be the best option.
    
    Hope this helps.
    
    
790.2Deferred Updates are not goodAIMTEC::WICKS_ALiverpool win the F.A Cup again!Wed Jun 03 1992 20:1417
    Sonia,
    
    Apart from learning to spell our favourite product name correctly
    - it's ALL-IN-1 all in uppercase the things you need to also note
    are....
    
    1) Deferred Updates are NOT supported with ALL-IN-1 - this is highly
       likely to be the cause of your problem
    
    2) You say all 3 nodes of your cluster are world-search - I hope you
       mean that DDS is installed once cluster-wide and not 3 separate
       times because you certainly could create problems for yourself 
       that way also.
    
    regards,
    
    Andrew.D.wicks