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

Conference noted::sns

Title:POLYCENTER System Watchdog for VMS OSF/1 ULTRIX HP-UX AIX SunOS
Notice:Wishes:406,FAQ:845,Kits-VMS:1000,UNIX:694 VMS ECO01 FT kit: 521
Moderator:AZUR::HUREZZ
Created:Fri May 15 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1033
Total number of notes:4584

1000.0. "PSW V2.2 ECO04 FT version is ready..." by AZUR::HUREZ (Connectivity & Computing Services @VBE. DTN 828-5159) Tue Feb 18 1997 10:20

    I couldn't resist the temptation to enter the 1000'th topic in this
    conference ;-)  So here it is...
    
    
    A field test version of the ECO04 kit is available from
    
    	ADG$DISK:[PUBLIC.PSW22.FIELD_TEST]SNS%%%ECO04022*.*
    
    
    It currently holds a couple of problem fixes and the support for 16
    characters long nodenames on display (frames will adapt to the maximum
    nodename length), which should help identifying DECnet phase V or IP
    nodenames in some situations where names are longer than 6 characters
    (old limit) and are built with a same prefix (families of nodes).
    
    For additional information, please refer to the release notes (posted
    in the first reply to this note).
    
    Best Regards,
    
    	-- Olivier Hurez.
T.RTitleUserPersonal
Name		DateLines
1000.1PSW V2.2 ECO04 preliminary release notesAZUR::HUREZConnectivity & Computing Services @VBE. DTN 828-5159Tue Feb 18 1997 10:231187
1000.2KIT not pullableSMOKEN::BRUNELLESat Feb 22 1997 02:215
    The directory isn't allowing access, getting access denied (File
    Protection).
    
    John
1000.3CA wants to QA it before it be released...AZUR::HUREZConnectivity & Computing Services @VBE. DTN 828-5159Mon Feb 24 1997 07:5910
    Yes, last friday, C.A requested it be set write-locked until they'll have
    proceeded with QA...
    
    I'll let you know here when it will be available again.
    
    I'm sorry for the inconvenience...
    
    Best Regards,
    
    	-- Olivier.
1000.4when will it be available ?PRSSOS::MENICACCIMon Mar 10 1997 13:495
	Hi,

does anyone know when it will be available to customers ?

Maria.
1000.5early april ...AZUR::HUREZConnectivity & Computing Services @VBE. DTN 828-5159Mon Mar 10 1997 15:5724
    I would say early april...
    
    It currently works that way:
    
    1 I correct things,
      --> delay depends on problem nature.
    2 perform system, integration and regressive tests ...
      --> delay depends on modifications nature.
    3 make a tape,
    4 send it from Digital France to CA Marlborough (no electronic path
      working through firewalls)  --> 3 or 4 days.
    5 CA engineers proceed with Quality Assurance  --> I guess a couple of weeks
    6 CA gives the greenlight to ship kits to customers, as they do themselves
    
    
    I already went through 1 to 4 with the ECO04, and considering the few
    problem reports still logged in IPMT and in notes about the Agent
    hanging sometimes, I'm now reworking the TCP/IP and DECnet servers
    error handling; then it is likely we'll have to go through 2 to 6
    again for that kit.
    
    Best Regards,
    
    	-- Olivier.
1000.6V2.2-13 not V2.2-12SMOKEN::BRUNELLETue Mar 11 1997 14:4310
    I just installed the ECO4 and it identify itself as 
    
    	V2.2-13.  Have I done something wrong ?
    
    The greater then 6 chars for the nodename works fine on the display. 
    But when P1 is passed to an action routing, it is only 6 chars long.
    Any ideas ?
    
    John
1000.7Use P4 and P5 to get node and cluster names in full lengthAZUR::HUREZConnectivity & Computing Services @VBE. DTN 828-5159Wed Mar 12 1997 08:0324
    Hello John,
    
    I made a last minute change in the ECO04, which implied incrimenting
    the subversion to be able to identify the new kit.  The one you got
    is the one that is beeing QA'd at Computer Associates currently.
    
    However, CA asked me to put the ECO04 on hold, whatever subversion
    (so please do not push it to customers), till they complete QA tests
    on it, and a couple of additional fixes have to be included (it seems
    that I replaced the T2.2 with a V2.2 too early) so I'm rebuilding it
    today with a V2.2-14 version.
    
    
    As regards the action routine parameters, I left P1 unchanged because:
    
    	1_ Some user action routines do trust the fixed length of
           time stamp + short nodename prefix to extract the message
           text itself.
        2_ The nodename and cluster name are available in full length
           respectively as parameter P4 and P5.
    
    Best Regards,
    
    	-- Olivier.