[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

48.0. "11750 hints & kinks." by KERNEL::MOUNTFORD () Thu Jul 13 1989 16:19


Please be aware of the following pre-requisites on Vax 11/750 systems
being updated to VMS V5

1. FCO 11750-I009 which takes PCS750 to V103.

(and for the few customers with the KU750 option,)

2. FCO KU750-R002 for G & H Floating microcode.

The reasons are that the old V4 loaders and drivers do not work with
VMS V5.

I found the full procedures in Stars, in a most unlikely article, as
a result of a Telesupport call. The article is being split up into
more meaningfull separate articles in the next few days. Meanwhile,
if you put in the query "PCS750" and read the article titled 
"Latest FCO Report Sheet - PLEASE USE " in database 21 'Local_FCO'
you will get the details.

/Brian.
 
T.RTitleUserPersonal
Name
DateLines
48.1Adapter types on SystemKERNEL::BLANDtoward 2000 ...Sat Oct 21 1989 15:3520
    		What adapters has this 11750 got?
    
    From the console prompt you can examine four longwords in the RPB,
    Field Name "RPB$B_CONFREG", Contents "Byte array of adapter types"
    
    This field is loaded by VMB.EXE and therefore to be valid, VMB must
    have run and memory should not have been initilised/overwritten.
    
    E 90
	P  000090  00000010	! Memory
    E 94
    	P  000094  00000000
    E 98
    	P  000098  00000028	! UBI, DW0
    E 9C
    	P  00009C  00380000	! CI750

    If you see a 20 then you have an RH750, RH0.

    			Cheers, Norman Bland
48.2PCS750 Version 104KERNEL::BLANDtoward 2000 ...Sat Oct 21 1989 16:097
	A field service engineer mentioned to me this week that he had
    been given a TU58 with PCS750.BIN V104 on it. Steve Edmunds queried
    this version with me today. I have not been able to find this on
    VAXPAX # 37. Would anyone who here's more; like where we can get
    a copy and what it fixes, please put a reply here.
    
    	Waiting with baited breath, Norman Bland
48.3KERNEL::WRIGHTONPass me a +L-14005Mon Oct 30 1989 16:3225
         <<< FINALY::FINALY$DUA0:[NOTES$LIBRARY]FIELD_SERVICE.NOTE;1 >>>
                          -< Help for Field Service >-
================================================================================
Note 662.0                  ?? PCS750.BIN rev 104 ??                     1 reply
KAOFS::W_VIERHOUT "I is a school of high grad"        9 lines  14-SEP-1989 19:07
--------------------------------------------------------------------------------

    
      Hi
    
    Anyone out there in net land know of a 750 microcode rev of 104. I
    recently found a PSC750.bin on vaxpax 36 that sets the second byte
    of the SID to 68. I guess this is rev 104. What does this fix, can it
    be used?? 
                                                         Wayne V
                                                     798 District Support
================================================================================
Note 662.1                  ?? PCS750.BIN rev 104 ??                      1 of 1
POKIE::SCHOENFELD "I may be used but I ain't used up" 3 lines  24-OCT-1989 17:16
                        -< Needed for VMS 5.2 DEBUGGER >-
--------------------------------------------------------------------------------

    It is needed for VMS5.2 version of DEBUGGER which will fail if the
    Microcode isn't up to rev. FCO out about it also.
    
48.4L0003 versus L0003-YAKERNEL::BLANDtoward 2000 ...Tue Oct 31 1989 21:3331
	***** I WAS ASKED A QUESTION ABOUT THE DIFFERENCE BETWEEN *****
    	*****   THE L0003 & L0003-YA, RECENTLY. THE NOTE BELOW    *****
	*****               MAY HELP				  *****

			Regards, Norman Bland.

SUBJECT: 11/750 L0003/L0003-YA Replacement Strategy

Problem Statement
=================

	Recently, there has been some confusion in the Field caused by
the Logistics organization shipping L0003-YA's as a replacement for
L0003-00's.   This has been brought on by depletion of existing L0003-00
stock, over years through the repair cycle.   
	The L0003-YA is a functional replacement for the L0003-00 and
enjoys added reliablity from the use of denser cache rams (fewer chips)
and proper address line termination (less "soft" TB/CACHE ram parity
errors).

Summary
=======

	From a revision level/functional point of view, there is ABSOLUTELY
NO DIFFERENCE between the L0003-00 and the L0003-YA.   Hardware reliablity
leans towards the L0003-YA, however, with the microcode retry capability in
place (PCS750 V98 or above), most sites would see NO DIFFERENCE in perceived
reliablity.   ULTRIX sites seem to beat up the cache/TB rams more than does
VMS; ULTRIX sites suffering a reliablity problem with L0003-00's should
migrate toward L0003-YA's.   Otherwise, whatever is received from Logistics
should be sufficient.
48.5PCS750 V104KERNEL::BLANDtoward 2000 ...Thu Nov 30 1989 17:478
    There is a copy of PCS750 V104 on COMICS in SYS$PUBLIC named
    PCS750104.BIN. This was extracted from from VAXPAX 36 on YODA. I
    was not certain that this was V104 until I recently downline loaded
    it on a VMS V5.2 system.
    Just as a reminder, the 2nd byte of the SID will be 68 hex with
    this version of pcs750 loaded. It is required for a problem with
    DEBUGGER released with VMS V5.2.
    				Cheers, Norman Bland