[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

872.0. "DECnet FDA FM" by CCIIS1::ROGGEBAND (_ �hili��e _) Thu Apr 04 1991 04:07

    Hello,
    
    I have tried installing the DECnet FDA FM (the one I had handy i.e.
    MCCFDAUT011) on the DECmcc SSB kit. Some of the verbs I had before have
    "disappeared", eg : Perform Path Trace.
    
    Is there a more recent FDA kit available ?
    
    Thanks,
    
    Philippe.
T.RTitleUserPersonal
Name
DateLines
872.1Try DIAG_PATH_TRACE?ASD::HOWERHelen HowerThu Apr 04 1991 10:414
I also tried to register PERFORM PATH_TRACE for the TCP/IP DA, and was told to 
use the DIAG_PATH_TRACE that was already in use by Decnet DA....  Maybe that's 
the verb used in your kit?
		Helen
872.2CCIIS1::ROGGEBAND_ �hili��e _Fri Apr 05 1991 08:118
    Nope, that's not it, the very same kit which generated 6 or 7 verbs
    with DECmcc EFT1 now only generates 3 with DECmcc SSB... That's why I
    wondered if there was a more recent kit.
    
    Along the same line, when can we expect a FT version of the TCP/IP FDA
    & PA ? 
    
    �hR.
872.3TCP/IP FMs for EFTASD::ZAVALICKFri Apr 05 1991 15:2113
       Along the same line, when can we expect a FT version of the TCP/IP
    FDA & PA ?
    
    > The TCP/IP PA is being integrated with the DECnet and Bridge PA and
    > depending on the success of integration and porting *could* be
    > available on the Ultrix FT (April). Failing that it would be
    > available in the EFT of all V1.2 functionality which is looking
    > like mid-July.
    >
    > The TCP/IP Diagnostic Assistant will be available in the July V1.2
    > EFT.
    >
    > -Alan
872.4Realistic expectations for DECnet FDATOOK::MATTHEWSMon Apr 08 1991 12:4238
    Let me step in to set the record straight. As of the middle of March
    I am the manager of record for DECnet FDA. It has previously been
    an asynchronously released product which somehow (I really don't
    want to know how) got out of synchronization with the major releases.
    
    As part of my new responsibility, I need to make an analysis of the
    functionality of the current version for its usefulness. Whether
    or not there will be a DECnet FDA in V1.2 depends upon several things
    happening over the next 6-8 weeks. First, We have to feel that the
    quality of the current FDA including its documentation is high enough
    for FDA to be shipped. Second, We need to know where it goes after
    V1.2. If the future direction looks entirely different we need to
    reassess whether it makes sense to give the users something in one
    release that will look radically different in the next release.
    
    With the head count freeze we are under, something has to be deferred.
    FDA seems to be the candidate for V1.2. If it appears that the
    current product is USEFUL and can be fielded with minor bug fixes
    then it may be distributed with V1.2. If it is only marginally
    useful or it requires significant resources to get it fielded it
    will be deferred until after V1.2.
    
    Of all the functions that are in the current FDA, DECnet Path tracing
    appears to be the most useful. If resources allow, we may provide
    a DECnet Path trace.
    
    I apologize to the people that have found that there is no more current
    FDA available. NME has diverted people to higher priority tasks over
    the last several months and DECnet FDA has fallen through the cracks.
    Until it is clear which direction we will be going with it, it will
    stay in the crack it is in. I might wish it otherwise, but we do not
    have the resources to work on it at this time.
    
    None of this discussion applies to the TCP FDA. It is clearly a
    USEFUL function that will be included in the V1.2 kit. We would
    like to thank Alan Zavalick and ASDS for developing it.
    
    wally