[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

312.0. "Whitespace in messages in wrong place" by NSSG::R_SPENCE (Nets don't fail me now...) Fri Sep 07 1990 16:37

    I know that this was reported in the first field test but since it
    hasn't changed for the current version I was wondering if it is going
    to be fixed?
    
    Note the following set of output;
    
    Node4 CLAUDI_NS:.dna_node.nets
    AT  7-SEP-1990 15:28:47
    
    
    Deregistration Successful
    Node4 CLAUDI_NS:.dna_node.slick
    AT  7-SEP-1990 15:28:53
    
    
    Deregistration Successful
    Node4 CLAUDI_NS:.dna_node.claudi
    AT  7-SEP-1990 15:28:59
    
    
    Deregistration Successful
    Node4 CLAUDI_NS:.dna_node.watch
    AT  7-SEP-1990 15:29:06
    
    
    No such entity: Node4 CLAUDI_NS:.dna_node.watch
                             Unknown Entity = Node4
    CLAUDI_NS:.dna_node.watch
    
    The white space lines are really in the wrong places this is
    particularly objectionable in the last case where a "Success"
    indication is associated with a "failed" command.
    
    Is the presentation of this info going to get improved soon?
    
    s/rob
T.RTitleUserPersonal
Name
DateLines
312.1I will look into itGOSTE::CALLANDERMon Sep 10 1990 09:348
    
    Sorry about that one. I will see what I can do about getting it
    fixed for the V1.1 releases. Up until now we have been (in the FCL
    PM) primarily concerned with getting the commands to work, more
    than cosmetics. Since the PM does a lot of the processing, such
    as that required for wildcarding/cross partition requests/with...,
    there has been a lot of work needed to get these items to interact
    properly both within the PM and across the call interface.