[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

4382.0. "ELM am and QAR problems" by ABACUS::BUKOWSKI () Wed Jan 13 1993 12:56

    Help.!
    
    	I am using the July SSB release of 1.2 on a 6410 with 96 meg
    	and VMS 5.4-3.  Last month I had discovered several problems
    	with the ELM am or Bridge software (DECbrdige 610 software v1.2).
    	I had posted two notes in this conference, 4201 and 4203, but
    	recently, when I haven't yet received any replies, somebody
    	suggested that I should submit a QAR to properly resolve these
    	issues.  I tried to follow the instructions for the QAR process posted
    	in note 7.1, but I was rejected because the field test for MCC012
    	is completed.
    
    	What am I supposed to do now?  I need to resolve these issues,
    	or I may be forced to buy LANbridge 200's ( you try acquiring
    	hardware now ).  Also, I do not have the option of upgrading to
    	t1.3.
    
    	Can/would somebody out there help me?
    
    	NEI-Data Networks,
    	Michael...
T.RTitleUserPersonal
Name
DateLines
4382.1QAR for FT=SPR for released codeTOOK::MINTZErik MintzThu Jan 14 1993 07:156
Once a product is released, the official problem reporting mechanism
is to file an SPR.  I've asked our maintainance specialists to post
information on how.

-- Erik

4382.2We're working on itQUIVER::WALTERThu Jan 14 1993 09:262
    I have posted replies to notes 4201 and 4203.
    
4382.3Internal users must file SPRs???MOLAR::CHRISB::BRIENENNetwork Management Applications!Thu Jan 14 1993 11:4513
>Once a product is released, the official problem reporting mechanism
>is to file an SPR.  I've asked our maintainance specialists to post
>information on how.
>
>-- Erik

  Having internal users (Mike is using MCC to help manage MKO) file SPRs
 seems like a colossal waste of time/effort/$$...

  Since the problems he's discovering also exist in 1.3, maybe he should
 be filing them in the 1.3 QAR database?

						Chris
4382.4I'm just reporting the process...TOOK::MINTZErik MintzThu Jan 14 1993 12:0512
Certainly, if problems are still present in a current field test,
the QAR system is the most efficient way to report those problems.
However, at least for customer sites, it is important to use
the SPR process for released code, in order to ensure that
the particular customer needs are addressed in time (the earliest
a problem reported by QAR will be fixed would be in a subsequent
product release, whereas under some circumstances an SPR results
in shipment of replacement images).

Please direct suggestions for maintainance process improvements
to Henry (TOOK::HDAVIS) Davis.