|  |     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.
 | 
|  |     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
 |