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

Conference azur::mcc

Title:DECmcc user notes file. Does not replace IPMT.
Notice:Use IPMT for problems. Newsletter location in note 6187
Moderator:TAEC::BEROUD
Created:Mon Aug 21 1989
Last Modified:Wed Jun 04 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:6497
Total number of notes:27359

5703.0. "Target Assignments disappear" by COPCLU::SANDGREN (Keep it simple) Mon Nov 01 1993 08:35

	Customer has a problem with target assignments. It appears on
	VMS V5.5-2, DECmcc V1.2.3 & V1.3, DECwindows and DECwindows Mo-
	tif. Problem is the same with use of DNS or local MIR.

	Whenever he add a list of target assignments, they vanish in a
	random way. He claims it to happen on a _new_installed_system.
	He makes a list of, say 30 target assignments in the form:

				LOCAL_NS:.name

	He puts them in a command procedure and runs it. Afterwards
	when he checks it, some of them are gone. At another look some
	more are gone; at last he can have five or so left.
	There seems to be no resource problems on the system, and there
	are no error messages.

	Anybody have a clue?

	Thanks,

	Poul Sandgren, Network Group /Denmark
T.RTitleUserPersonal
Name		DateLines
5703.1TOOK::GUERTINI am never worngMon Nov 01 1993 13:3511
    Is the customer switching between DNS and Local MIR?  Switching will
    from Local MIR to DNS will probably cause the entries to "disappear",
    since the software will probably start looking up names by their
    real Namespace names, which will not match the names in the MIR
    (LOCAL_NS:.name).
    
    Entering the target assignments again might work.  Or just tell the
    user that this feature was never intended to be used in this way
    (switching back and forth).
    
    -Matt.
5703.2no switchingCOPCLU::SANDGRENKeep it simpleThu Nov 04 1993 08:4813
	re -1: I just verified with customer that he doesn't switch
	between DNS and MIR. He does a plain installation with either
	DNS or MIR as namespace. Also, a small correction in how the
	problem occurs:
	In his target assignment procedure, he has 30 target assign-
	ments. He runs it, and then afterwards checks the assignments.
	Then only, say 12 are left, and it stays like this. Appearent-
	ly, there is no consistency in which assignments are left or
	how many. Strange.

	Poul
5703.3See note 7 for problem reportingTOOK::MINTZErik MintzThu Nov 04 1993 10:406
I'm fairly sure that there was a previous CLD on this problem, but
the people who handle CLDs do not participate in this conference.
You will probably have better luck following the formal process.

-- Erik
5703.4solvedCOPCLU::SANDGRENKeep it simpleMon Nov 15 1993 05:4614
	The problem with the disappearing target assignments was solved
	with the patched version af MCC_NOTIFICATION_FM.EXE:

	    TOOK::NSM_CLD:[DECMCC.CFS_4138]MCC_NOTIFICATION_FM.EXE

	Then customer had another problem with alarms coming up with
	status 'indeterminate'. To solve this, he had to avoid using
	wildcards in his target assignments.

	Thanks for any help,

	Poul
5703.5TIMA?CSC32::M_EVANShate is STILL not a family valueTue Nov 30 1993 08:124
    Has this fix been submitted through TIMA so we have a chance of getting
    it at the CSC?
    
    Meg