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

Conference kernel::csguk_systems

Title:CSGUK_SYSTEMS
Notice:No restrictions on keyword creation
Moderator:KERNEL::ADAMS
Created:Wed Mar 01 1989
Last Modified:Thu Nov 28 1996
Last Successful Update:Fri Jun 06 1997
Number of topics:242
Total number of notes:1855

179.0. "Should we process COMMS bugchecks deeper?" by KERNEL::PETTET (Norm Pettet CSC Basingstoke) Fri May 06 1994 18:02

    We are currently processing bugchecks in COMMS drivers. Brian Adams and
    myself had a brief chat with Richard Butt and he is quite happy for us
    to continue this task, however we pointed out that we don't have access
    to COMMS driver listings (LTDRIVER & the like) and also we don't have
    any access to associated databases. He said he could make available the
    listings and would checkout the possiblity of giving us access to their
    databases. 
    
    What does the panel think, should we take on this task given that COMMS
    don't now have the skills to process bugchecks (other than the UCX
    guys).
    
    
    Norm
T.RTitleUserPersonal
Name
DateLines
179.1 YES KERNEL::ADAMSBrian Adams CSC-Viables '833-3026Sun May 08 1994 23:081
    
179.2KERNEL::WRIGHTONI'll call you back later, alright !Mon May 09 1994 08:583
    
    
    	Only if we can spell deeper.
179.3If VMS crashes, it should be ours...COMICS::TRAVELLJohn T, UK VMS System SupportTue May 10 1994 18:587
Whatever the (DEC) product that caused the crash. However, to do this properly
does require that ALL of the needed listings are available, and that known 
issues be documented as quickly as possible.
This should not preclude working with members of other groups to gain some 
common ground in understanding problem areas.

		JT:
179.4YESKERNEL::ANTHONYTue May 10 1994 21:1216
    
    	Yes, we should do it.. I'm 100% in favour 
    
    	I am discussing this with BJ, not just comms, but other areas
    	as well.
    
    	As JT says, if VMS crashes we should be involved. 
    					
    	We will need access to their data, and listings etc.  
    	It will mean one of us putting together a little project to 
    	set this up properly.
    	
    	Also we must be seen to be doing a good job i.e. better than
    	the way the calls are handled now. 
    
    	Does the rest of the team agree with this?
179.5another YES voteKERNEL::BLANDNorman Bland 833 3797 CSC, BasingstokeTue May 10 1994 21:513
    I'm in favour.
    
    Norman
179.6COMICS::GLEDHILLSun Jun 19 1994 11:5713
belated voice from somewhere...

Me to. I have spoke to andy hopkins about this recently hopefully we can have
a meeting about it sometime. Want to make sure we are doing this official so
get some credit for it rather than as a hobby. 

As already said we need the sources else we do keep digging... bear in mind 
that we DO have lat sources, ethernet/fddi and decnet phase 4 sources. We have
also had at least psi,dns,les sources in the past, but not sure if up to date.

It is the other more peripheral products that might be harder to get hold of.

dg.
179.7COMMS crash dump analysis - info requiredKERNEL::PETTETNorm Pettet CSC BasingstokeMon Jan 30 1995 15:2929
    Chaps,
    
    	Dave Gledhill & myself will be working together to how best to
    handle the COMMS crash dump analysis issues. Dave Gledhill & I are
    having a meeting with Richard Butt next week, I intend to discuss the
    following:-
    
    1) Training
    2) Interaction between our groups
    3) Escalation
    4) Source code & associated data structures
    5) Database access (for  current issues not documented on
       stars/canasta)
    6) UCX
    
    	I suspect the training will consist of seminars given by Comms
    engineers from the applicable group (PSI, LAT etc) also Norm Bland will
    open a note on the system_technical notesfile to address any hot_tips
    etc.
    
    	If you have an issue you would like discussed (hardware or
    software)  please reply to this note.
    
    Regards,
    
    	Norm 
    
    
    
179.8My 2p...COMICS::TRAVELLJohn T, UK VMS System SupportTue Jan 31 1995 02:1422
    1) Training
		Of course, but when are we going to fit it in, i.e. which year ?
	
    2) Interaction between our groups
		Need to know who is both amenable and got brains worth picking..

    3) Escalation
		As is seems OK, escalate to Comms for Engineering. Still need to
		ensure running supported versions before it hits Engineering.

    4) Source code & associated data structures
		Critical, cannot do without...

    5) Database access (for current issues not documented on stars/canasta)
		Excuse me, WHY are comms problems NOT in STARS ?  

    6) UCX
		I suspect we will get to know this product quite well in the 
		next few months, with the I.S. changes to the networks bang 
		goes our `reliability'!!

	JT:
179.9my 2d ( that 2p in old money )KERNEL::PETTETNorm Pettet CSC BasingstokeWed Feb 01 1995 09:5216
    John,
    
    
    	I agree with you (now there's a first!!). As regards why some
    "known" problems aren't on stars is because some comms drivers almost
    change on a daily basis (remember LTDRIVER & its mates!!). 
    	As regards training I believe we need to understand comms products
    on a user basis (how to connect, use, stop/start etc) and its
    associated data structures. This is vital in order to process the
    crashes. Perhaps the training could take the form of a series of
    seminars detailing the product, its use and applicable data structures.
    This is something which will be discussed during the meeting. 
    
    	Has anybody else got any inputs?
    
    	Norm 
179.10I'll echo JT.KERNEL::ADAMSBrian Adams CSC-Viables '833-3026Mon Feb 06 1995 18:1417
    
    Norm,
    
    I think John has already said most of what I would have.
    
    As to the training, it is essential, but how can we fit it in ??
    
    We have to have all the resources available to us. It would have been
    nice to have Stars entries saying something like "Problem X due to old
    software version y" but seeing as comms have never worked this way,
    we'll never get that luxury.
    
    Also, I'd like to know how the customers respond to being told to try
    the latest version of software etc etc. Are they more prepared to
    accept that comms software changes with the weather, and that they
    have to be continually updating it.