Conference msgaxp::optical

810.0. "1000A,4100,2100A or 600" by CSC32::S_WASKEWICZ () Tue Mar 18 1997 15:47

    I haven't see any notes regarding this issue, so I thought I'd start one.

Use **Caution** when attaching an Optical Library to one of the following:
	AlphaServer 1000A
	AlphaServer 4100
	AlphaServer 2100A
	AlphaStation 600.

Why?
     VMS sizes the backplane slots/adapters on these systems in a machine
"specific" manner that is UNLIKE what one sees at the console level.
     If, for example, one has an RW532 attached to a KZPAA installed in PCI slot
#1, and the Juke is successfully seen at the console prompt as DKBxxx devices,
DON'T assume you're on the "B" bus when installing OSMS.
     You must CHANGE what controller you answer to when installing OSMS.
     By this, I mean that when presented with options of PKA or PKB, and OSMS 
defaults to [B], you must lie to it, and tell it your optical is on the
"A" bus.

Strange you say?
    This is documented in detail in the VMS Release Notes for version 7.1, 
Appendix A and has some layouts of the aforementioned processor backplanes. 
There are explanations also on how VMS sizes these backplanes.
Read and understand these release notes, especially Appendix A.

So whats it mean to me?
	Since VMS changes what you see at the console level, its quite 
possible to properly configure/install OSMS and yet be unable to communicate
with your library.
Many thanks to Dale Green and Frank Bernal in San Antonio for successfully
working out a particularly lengthy trouble call with me on this subject.