[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

89.0. "SDD " by KERNEL::MOUNTFORD () Tue Jan 23 1990 07:45

From:	KERNEL::MCGAUGHRIN "I'd rather be playing cricket  22-Jan-1990 1742" 22-JAN-1990 17:47:19.48
To:	@POST:DEVICES,@POST:SYSTEMS,@SDDPT
CC:	MCGAUGHRIN
Subj:	SDD Call Flows - Out of Hours

         


	For the benefit of those who work out of hours and are likely to
	be handling SDD Calls, (Systems, Devices). Here is a simple explanation
	of the basic handling procedure.



		     ***** VAXSIMPLUS GENERATED FAULT CALLS *****


		On receipt of an SDD call - a call that has been generated by
	VAXSIMPLUS - please follow the guidelines below.

		(This information, and the SDD Call Flows, will be put in the
	Library (Box 8806) with the selection of manuals on SDD/VAXSIMPLUS.)


	  1. Obtain the VAXSIMPLUS Event Code and failing Device Name/Type
	     from Customer.


	  2. Convert the Event Code to a Spear Theory :- 

		$ run rsds$spear:spear
		$ SPEAR>                A
                $ QUERY                 CR 
		$ THEORY NUMBER         Enter Theory Number
                $ O/P 1st Page to File  CR


	  3. Select the 1st FRU that Spear calls out, and give the following
	     two FRU's as possible FRU's. These should be in order and any
	     HDA's need no validation. (The number to give to Logistics, is
	     on the SDD Desk, in the black HDA book.)

	     Where Spear cannot analyse the problem, connect to the system if

	     it is accessable, and carry out manual diagnosis.
 

	  4. Notify results :-

		Call Type            SDD

		Problem Summary      Device Name, Device Type, [Theory]

                                         ( e.g. DUA1 RA81 [1.15.8.10] )

		Tech Findings	     VAXSIMPLUS - 1ST FRU - "FRU NAME"


		All other Notify Fields to be filled out as normal.




T.RTitleUserPersonal
Name
DateLines
89.1KERNEL::MOUNTFORDWed Jan 24 1990 09:1180
From:	KERNEL::MCGAUGHRIN "I'd rather be playing cricket  24-Jan-1990 0906" 24-JAN-1990 09:08:34.97
To:	@POST:SYSTEMS,@POST:DEVICES
CC:	MCGAUGHRIN
Subj:	Spot the Difference, and win a major prize!

From:	KERNEL::JAMES        "ALAN JAMES @UVO, 7833-3443" 22-JAN-1990 17:56:52.03
To:	MCGAUGHRIN
CC:	
Subj:	SSD proceedure

From:	KERNEL::JAMES        "ALAN JAMES @UVO, 7833-3443" 16-DEC-1989 11:03:59.78
To:	JAMES
CC:	JAMES
Subj:	VAXSIMPLUS Procedure

		     ***** VAXSIMPLUS GENERATED FAULT CALLS *****


		On receipt of an SDD call - a call that has been generated by
	VAXSIMPLUS - please follow the guidelines below.


	  1. Obtain from the customer the FAILING DEVICE NAME, FAILING DEVICE
	     TYPE and VAXSIMPLUS EVENT CODE.
	     (It is sometimes advantageous to get controller type at this time.)

	     
	  2. Convert the Event Code to a Spear Theory :- 


	$ spear   (If NDT is being used)    ! run SPEAR from the "$" prompt  
	   or  
	$ run rsds$spear:spear

	SPEAR> T		            ! Ask SPEAR to go into theory mode

        Desired category (QUERY): <cr>	    ! Hit carriage return for query mode

        Theory number: n.nn.nn 		    ! Enter Event Code supplied by Cust

        O/P first page to file (NONE): <cr> ! hit carriage return 

        Type <cr> to confirm (/GO):         ! Hit carriage return to start

        Spear will now  run and eventually give you the benefit of its wisdom.


	  3. Note all the FRU's that Spear calls out.
	     
	     Where Spear cannot analyse the problem, it may be necessary to
	     connect to the system and carry out manual diagnosis. The VAXsim+
	     Mail to the Field Account will be useful in these circumstances. 


	  4. Notify results :-


	      Call Type         SDD


	      Problem Summary   Device Name, Device Type, [Theory]

                                         ( e.g. DUA1 RA81 [1.15.8.10] )


	      Tech Findings	 VAXSIMPLUS FRU LIST.  FRU/PART, FRU/PART ....

              			( e.g. VAXSIMPLUS FRU LIST. SERVO 70-19045-01,

			PERSONALITY 70-19046-01, POWER SUPPLY H776-D ...) 

			Ensure HDA Validation Number is on Notify if a 
			Validation has been carried out.


	      All other Notify Fields to be filled out as normal.




89.2What do you know about VAXsimPLUS?KERNEL::MCGAUGHRINWhat a Marvelous DeliveryWed Mar 14 1990 14:3414
    
    
    
    Recently I have been asked several quetions, around the use of SPEAR
    and handling VAXsimPLUS calls. There have been some issues related
    to the accuarcy of the call-outs, and which FRUs should be sent
    to site.
    
    I can assure you now, that there is more to a VAXsimPLUS call than
    just giving the engineer the fisrt FRU on the list. Rather than
    sit here and preach, I would like to invite you to ask questions
    on this topic here, and if necessary we can arrange some seminars.