Digital PDFs

EK-457AA-SG-001

2000

73 pages

Original

4.2MB

view download

OCR Version

3.1MB

view download

Document:	DSSI Warm Swapping Guide for BA400-Series Enclosures and KFQSA Adapters
Order Number:	EK-457AA-SG
Revision:	001
Pages:	73
Original Filename:

OCR Text

$0.0.6.9.00.0.900.0.000.00000.0.090066000008049066600060.9064¢000.4

$0.90.0,0.0.6.0.0.9$.¢.0.0.000.89695.60.6.6060000.65$0005088096694
.9.0.0,0,0.0.0.0.0.0.66.0.0.6.9.0.0.0.99.06.09¢66¢.090060069006000674
).0.0.0.9.0,0.6.9,6.0.0,0.9.0.0.0.8.00.6¢.¢6940000006666.099¢9¢00¢4
10.8.4.0.60.0.6.0008.6808086069089966¢0606006.6609000¢4

)0.9.0.8.9.9.0.0.00.69.¢9.9.9¢.00¢00085900086¢00¢0¢94604
$0.0.0.0.0.00.63.0,0060.095000069909,68000660069.64
).0.9.9.0.0.8:4.9.6.¢.8.$,0.8.0.4,0.¢.¢.6.6.0.6,0.6.0,6.6.0,09.0.6.0,0.94
§.9.9.0.0.0.00.0.8.0.68080.8.¢.90.8880950668006600604
p8.8.0.6.6.9.0.08.98.8400.00066945649.6000906061

P0.9.6.8.6.9.000006%.0.9.606690..6066$.06081
§0.0.0.0.0.
8668 806.$00.4998¢4004
9.6.0.93
$.0.0.0.9.6.0.80.9.0.00.6.0.0,¢.0.0000.0060¢4

$0.0.0.9.4.0.0.0.0.68.0.9.9.4,69.9.99.9.9664
).$.0.0.0.0.9,0.0.90.00.6.9.6.9.0.4.¢.0.8,04

XXXH XXX

KOOI

AAXAX

KXXXXA
XK KK XX XX
XX XXX

XXX XAXA XA XK XXX X
XXXXKX
XX XXX XXX

XXXXXXXHXXXXX
XXKAXXXAXXX
XXXAXXXAX

XHAXXX
A

XXXXX
XXX
X

X
XXX

XXXXX
XXKXAXX
$.9.9:4.9.0.6:0,94

KAAAXXXXAXX
,0.9.0.9.4.9.8.¢.0.9.0.¢.¢

XXXXXX
XK XX XX XK X
).9.0.0.6.6.0.¢.9.¢29.9¢.6.99.¢

$8.8.9.9,0.9.9.84.4.046906¢¢0¢
XX XXKXKAXKX
KX KA XA KR K
X

}0.9.0.9:4.9.0.8.0.6.6.08.0.9.0$$.6.60.9.¢
05.9.9.0,0.8.9:0.0.89.9.9.4.0,0$06.0$09

1 $.0:00.0.0.6.9.6.0.¢.0.0.0 008006060800
§0.0,0.9.8.8:40.9:0.6.0.0.0.6.0.90.06.0,466:9.69991
}0.6.6.0.00.9.906,0.6.0.9:6.906669.8.080600094
D00 990900809798 0865069.0800090000004

09.90.96:9.6.90¢.68.06,009.006.9.60060.604068004

§0.0.0.9.0,9.9,0.0.0.0.000.060865090068¢06900.00.091
000.0.0.6.0.60.0000.00000605006666960.9.900.09.00601

10,9.0,0.0.0.9.0.8.90.0099000600.680690006600099.6:9.904
£$.0.0.9.0.0.9.6.8.06.0.06690906000099090¢0099906000998
LO0.0.8.¢.
650965 5000.08$6609.
9.6.9
9.90.6.60.0:0
.2.00
.0.00908
98

10.9.0.9.09/0.9,0.99.0.0930.0.0,¢8.85 0880900066900 050680900
94
0.8,0.0.9.
9.8 090960060
0.080
80809000048
.0.00
0¢0.9.00¢008
0000
919.9.9.0.4:9.6,9.9.0.00.0.9:$0000090002
.0.90.00980
:00:0.0090
09.99090 004

DSSI Warm Swapping Guide for
BA400-Series Enclosures and
KFQSA Adapters
Order Number: EK-457AA-SG-001

Booting of CPU Modules

246

-----------------------

3 Warm Swapping Procedures for KFQSA Q-bus DSSI
Modules
3.1

Introduction . ......

3-1

3.2
3.2.1

Warm Swapping KFQSA Q-Bus Modules . . . ...........
KFQSA (M7769, revision K04 and later) Support

3-1

...

. ...

Warm Swapping . ... ..ot

KFQSA Revisions That do not Support Warm
S RTTZ221
) ¢3 1.6
7=

3.4
3.4.1
3.4.2
3.4.3

Removal and Installation Procedures ... .............
Considerations for System Enclosures .. ...........
Shutting Down VMS System Software. ............
Obtaining and Recording KFQSA Module Specific
Parameters

3.43.1

. ........ ...

3.44
345

3-4

Accessing a KFQSA Module's Configuration
Table .. ...

3432

... . . i

...

3-4

Obtaining CSR Settings Using the Console
Command CONFIGURE ....................
Removal and Replacement of KFQSA Q-Bus
Modules ....... ... .. ...
Restoring the KFQSA Q-Bus Module’s Configuration
Table

......................................

Warm Swapping Procedures for DSS! Integrated

Storage Elements (ISE)
4.1

Introduction . . ........ ... ... . ... .. ..

4.2

Warm Swapping ISEs

421
4211

. . ....... ... . ... ... .. .. ....

ISE FRU Warm Swapping Requirements. ... ... .. ..
Warm Swapping RF-Series ISEs . .. ...........

4212
Warm Swapping TF-Series ISEs . .............
4.3
Obtaining and Recording Current ISE Specific
. .. ..

4-5

431

Ising the VMS Diagnostic Utility Protocol (DUP) . . ..

4-5

432

Obtaining Parameters Using DUP .. ... ...........

4-8

Obtaining Parameters Using VMS .. . .. ...........

4-12

Parameters

433
4.4

....... .. ..

Removal and Installation Procedures for ISEs.

.. ...
. ...

4-14

441

Finding Failed ISEFRUs. . . ....................

4-14

442

Enclosures That Support Warm Swapping.

.. ...
.. ..

4-14

443

Dismounting and Removing Failed ISEs ... ...
... ..

4-15

444

Installing Repaired or Replaced ISEs

4-17

45
451

Restoring the ISE Specific Parameters. ... ... .........
Replacement of FRUs Requiring Parameter

Reprogramming . .............................
Replacement of FRUs not Requiring Parameter

4-18

452

Reprogramming . ..................
... .......

4-22

Related Documents

Appendix B

Dismount Command Regarding Open Files

Appendix C

ISE Parameter Work Sheets

Storage System Interconnect (DSSI) Modules

intended Audience
This document is intended for Digital Services personnel and self-maintenance
customers.

vii

0.0000
006069004
o110 8070 07010 07919709100 0188 9101906, 0/0.0.014.8.0.0.0.0.0.6.9.
/0D S0P 0.019.99.8/00000000908¢54
0.010.00.
D10 81670060 0101070 ¢ 00
III 0400
DOT0TE9 00 00 0 97000 0 00 019109101000 0 00 00O
004
O 40 0 0T 0T 0 OIS0 OIS 0 0 P 0.0 0.0.9.0.0.0.0.6.9.0.9.0.0.8.0
X
XK
XK
KK
XK
KK
KX
RX
KX
X
X000
OO
KKK
XK XX XX XK KX KKK
LXK R KKK KKK
I XK XXKKK
LXK
KK
XK AK LKL AKX XKLL
KKK KKK KA XK XK KR KA KK KKXXKKKKK
KRAKE KKK KA KK KA KK AKX KKK KK KKKKKKX
KOO HK XX KX XK KKK KKK KKK KAKKK
KXKKKL LK KK KK KA KK KAKL XK KARKKKK

¢.0:0
01080070 019 0Y011619.91010'019:9.09.0.0
0000 00 9100 9 09 0100010 0 000 0 04

619:9.0.0.0.66.6.0.0.9.0
@
10.6.0'6.0.6:
PO
K
OOE
XX KHKKKK
XROOCOOO
XXX AAKHKXKAKXKKKKKKX

KK KKKXKK
TAKHKKKAKK

KKXKKKXEXKKKKKK
KXRAKKKEXKKKK

TARAKXKLXXK
KEAKRKAKKK
KXKKKKK

HARHAX
AKX
X

X
XXX
XAXKX
KAKLAXYL

XXXAXXXRX

OXXAXAKXAK
KAAXXXKXXANKX

P 4804006 40848094

XX XUXKAKAKKXAKAXLK
b 4869090808086 8880440
P

4949900640905 e606508¢

1.6.0.68.0.6.0.6.46.0.6660060¢49¢4

p0.6.0.44:996.069 6688400005606 4

XXERAAAAXUAXE
KK LXK AAKXKL LKL
000000908080885809060]
PAASAIN PPN
008604964
0409
8840089
PO GOt 600806008

AR KALX
EAXKAXAR KX KK AL XA XL XL KK XX LXK
KU KKK KKK XX I KKK K XK UK KA KK HAAAK
P 90400048800 000684808980 600044 8086809484

POH 0 0 060840040904 86800044804088.88050984664
9
W0 0084048800 0000044
000404
043
PS4 900806

80
08808 80044
P OGO 0PI 000GV ROIFI IS 00000066404
XX AL KUK A XA KA KA

XXAK AL KL

A A KA AR KA A HE KK KK KK LKA KL KL ALK

LR AL AR K LKL LA XK XK XA LA RS EE AR KN K KA XA AR AKA,
b0t06.9
48080
080086008
OGP NN00000300
OIONEIIPI
PO OGN

Understanding DSSI Warm Swapping
1.1 Introduction
This document describes warm swapping procedures for the Q-bus hardware
devices that are Digital Storage Systems Interconnect (DSSI) field-replaceable
units (FRU). This chapter contains a brief overview of the following:
¢

DSSI warm swapping

DSSI-based devices that do support warm swapping

DSSI-based devices that do not support warm swapping

Physical attributes of the DSSI bus

Warm swapping minimum requirements

1.2 Warm Swapping
DSSI warm swapping refers to the procedure by which a Digital Storage Systems
Interconnect (DSSI) field-replaceable unit (FRU) is powered off and removed from
an active DSSI bus without affecting availa*ility of the host system or the rest
of the DSSI subsystem. When performed properly, warm swapping eliminates
the need for shutting down the entire VAXcluster system during certain routine
maintenance activities.

Without warm swapping, the necessary removal or replacement of any one DSS{
device (such as disks, tape drives, or adapters) requires that an entire local area
VAXcluster system or multisystem DSSI VAXcluster configuration be properly
shut down and powered off.
Warm swapping procedures make it possible to preserve system resources

when replacement or removal of a device is necessary. Within DSSI VAXcluster
configurations, warm swapping DSSI Q-bus adapters, CPUs, and ISEs increases
system availability since there is no need for shutting down the entire VAXcluster
system and/or mass storage resources.

Understanding DSSI Warm Swapping

1-1

1.3 DSSI Devices and Warm Swapping
The following are DSSI FRUs:
e

Q-bus System CPUs with embedded DSSI adapters

Q-bus option DSSI adapters

RFxx or TFxx series Integrated Storage Elements (ISEs).

The following sections describe the devices that do and do not support warm
swapping procedures.
Note

Fer warm swap procedures of Digital’'s SFxx or TF857 DSSI storage
building blocks see related documentation listed in Appendix A.

1.3.1

DSSI Devices That do Support Warm Swapping

Using the procedures listed in this document, the following DSSI devices will
support warm swapping:

RFxx devices within BA400-Series and R23RF-series enclosures

TFxx devices within BA400-series enclosures

BA440-based and BA441-based CPUs with embedded DSSI adapters and the
H3604 (70-27400-01 revision C01) console panel

KFQSA (M7769, revision K04 or later) Q-bus option DSSI adapters with
S-box (70-26020-02) front handles.
Note

Warm swapping procedures are not supported for KFQSA (M7769) Q-bus
option adapters within BA200-series enclosures when the adapter is
configured as the primary DSSI adapter connected to the internal DSSI
bus of these enclosures.

However, if a second KFQSA (M7769, revision K04 or later) Q-bus
adapter with the S-box handle (70-26020-02) is configured within the
BA200-series enclosure, warm swapping of this adapter is supported.

1-2

Understanding DSSI Warm Swapping

1.3.2 DSSI Devices That do not Support Warm Swapping
Due to architectural limitations described within this document, the following
Digital DSSI devices do not support warm swapping:

RFxx devices within BA23-series, BA123-series, and BA200-series enclosures

TFxx table top enclosures

(CPUs with embedded DSSI adapter and DSSI terminators, such as the
KA640 (M7624), and the KA660 (M7626)

BA440-based and BA441-based CPUs with embedded DSSI adapters without

the H3604 console panel (70-27400-01 revision C01)

Any KFQSA Q-bus option DSSI adapter without the S-box front handle
(70-26020-02)
Caution

Warm swapping rules and regulation procedures should be fully
ur.derstood before attempting to repair or replace any DSSI device.

1.4 DSSI Bus Physical Properties
Like most electrical buses, the DSSI bus requires the maintaining of four physical
properties to support its signal integrity. The four properties are:
e

DSSI Termination

DSSI Continuity

DSSI VTERM

°*

DSSI Enclosure Power Cycling Limitations

To successfully perform warm swapping maintenance, you must fully understand

these four physical properties of the DSSI bus.

1.4.1

DSSI Termination
Note

Make certain that all DSSI buses are properly terminated at both ends.

Understanding DSSI Warm Swapping

1-3

There must be proper DSSI termination present at both ends of a DSSI bus. This
termination can be supplied by the presence of a DSSI termination connector
(12-29258-01) or DSSI CPUs and Q-bus adapters which employ embedded DSSI
termination through the use of resistive integrated circuit (IC) packages.
CPUs and Q-bus adapters with embedded termination are all KA640 (M7624)
and KA660 (M7626) CPU modules and KFQSA (M7769 revision J06 or earlier)
Q-bus adapter option. To be certain of which revision of the KFQSA a system
may contain, refer to Chapter 3, Warm Swapping Procedures for KFQSA Q-bus
DSSI Modules, later in this document.

CPU modules supported within the BA440 and BA441 system enclosure do not

contain embedded DSSI termination for their embedded DSSI adapters. Resident
on the BA440 and BA441 system backplane, are embedded resistive IC packages
that supply DSSI termination for the CPU end of DSSI BUS 0. This is true for all
VAX 4000 Model 300 and later systems. As for BUS 1 of the BA440 and BA441
enclosures, proper DSSI termination must be applied to both DSSI connections of
the CPU’s H3604 front console panel.

1.4.2 DSSI Continuity
Note

Make certain that all DSS1 buses are kept continuous during all moments
of operation.

Warm swapping procedures do not include the removal or repair of any enclosure
internal or external DSSI cables when they are attached to an active DSSI bus.
These cables include:

All enclosure internal DSSI cables attached to the DSSI connector of a CPU

All length variations of BC21M, BC22Q, and BC21Q external DSSI cables.

and/or KFQSA Q-bus adapter.

WARNING
The improper removal or replacement of any DSSI cable, terminator,
distribution panel, or DSSI adapter may render the bus non-continuous
or improperly terminated and can result in DSSI bus errors which could

potentially cause data corruption on ISEs.

1-4

Understanding DSSI Warm Swapping

1.4.3 DSSI VTERM
Note

Keep in mind that the DSSI cable carries internal terminator voltage
power (VTERM).

Unlike other components of a Q-bus system, the DSSI bus itself will still
have power applied to it even if an enclosure to which the bus is attached is
powered off. Due to the internal propagation of a +5 Vdc signal line, the DSSI
bus remains active even if only one of the systems or expanders to which it is
attached is powered up.
Known as D551 VITERM (for TERMinator Voltage), this +5 Vde signal line is
essential for the proper operation of DSSI bus termination circuitry. Therefore,
VTERM is applied by all BA400-series enclosures and adapters which support
DSSI devices.

VTERM is physically provided to the DSSI bus by the following enclosures and
adapters through the following means:
e

B400X—via M9715-AA module located to the left of H7874 power supply

R400X—via M7493-PA module located to the left of H7874 power supply

BA440 DSSI BUS ¢—via VTERM Regulator module (54-20404-01) on

backplane
*

BA440 DSSI BUS 1—via H3604s +5 Vde through 2.0 A 125 V (F3, fuse

KFQSA—on board via +5 Vde through 2.0 A 125 V (F1) fuse

KA640—on board via +5 Vdc through 1.5 A 125 V (F3) fuse

KA660—on board via +5 Vdc through 2.0 A 125 V (F3) fuse

For CPUs within BA440 system enclosures, VTERM is applied by either the

backplane resident VITERM regulator module or the +5 Vdc/fuse circuit of the
H3604 CPU console front panel.
For example, consider a BA440 attached via a common DSSI through an R400X

expander to a BA430 system enclosure. If the R400X is powered off for repair,
it appears that all of its components are inactive. However, the DSSI bus which

passes through the enclosure is still being powered with VITERM sourced at the
remaining two enclosures of the configuration.

It is for this reason that care must be taken to avoid inappropriately removing or
replacing DSSI devices.

Understanding DSSI Warm Swapping

1~5

1.4.4 DSSI Enclosure Power Cycling Limitations
Note

Before removing any DSSI device, the entire enclosure in which the device
is located must be powered off.

Within almost all Digital Q-bus systems and storage expansion pedestals, the
need for powering down a component contained within the enclosure mandates
the power cycling of the entire enclosure.
For example, consider the necessary maintenance of a BA440-based DSSI device.
In order to repair or replace the device, the entire enclosure must be powered off,
resulting in the temporary loss of all ISE, Q-bus, memory, and CPU resources
within the enclosure.

Consequently, proper system management tasks (for example, dismounting of all
affected devices) must be properly planned and executed.

1.5 Warm Swapping Requirements
The following are the minimum requirements for implementing any warm
swapping procedures:

All DSSI buscs must be properly terminated at both ends.

All DSSI buses must remain electrically continuous, from end-to-end.

Before warm swapping any device, the entire enclosure in which the device is

located must be powered off.
Be sure to follow all warm swapping instructions in the appropriate sections

of this document.

1-6

Understanding DSSI Warm Swapping

09406066

60000000&0000

ooooo;oxxxxxxxxx

FOOOONGOCOOE
K000 OO
XXX XX XX XX XXX
$00.06668.90000.08000000000608000606000¢5¢.4
P 89.0080088060000000088000008486808048044
PO OO C P08 9088000800 080000080008¢8004
PS80608000898080080488000866000434
p 190088800980 8040908080044004084
pre00038498046080000090080006044
XXOOOC0OOO00
XXX XK XK XXK
§.29.0.00.60690.9600004600000004

$0,6.0.000099000660690090¢4

p2.6.0.0.9.0.6.00.609060$96904
$ 4066906606¢60008004
p0.$990690060906664
D 4.6.0.0.69.6.9¢600¢04

P9960906800464
P3.4.6.60.46.0404
KRXAKXAXXX
OXAXYX
XXX
XXX
X

X
XXX

XXXXX
XXXXXXX

XXAXAXXAKAX
XXXAXXXAXKX

XAXXKAXARX
KKK

p 0 8006080004044
HAUXOK
XXX KAKAK,
XA
XXXXXUXKXKXXIKAXAAX

XKL XAKL XX XA XXRKAXANAK
b 0006486.0006000608040¢00M
p0.8.0.00608.0666.8666890008064
P.00.0.8.094809.600066066.060000
8
PO

E 0000680806 0006000900000¢4

p 000905900608 8809068669000606094

Is000s bttt 00000080009090
0¢004

b9 480940099000 08000090948084880900¢44
P9596900898008
00 4000066000800 88005944¢

P90 0088060080088 000006048080 00¢060644
PO O8600 0000800000000
0000808000 8806000494044
P oD S0P 040006000800
00 00000086 0040008846906099

f0 0905088080690
9¢888000 0080 8P H Ot EII V040103
OO00600000800808
0 Pttt 00004t oteesisesd

PO SN D

POt

E0000 08000000000 6000 0000900 43099¢95 08404

DI PIITOCEN OIS OO0 IO P0000400.08006098098000.9

adarpieobsdwDnptiwluoSteyrahswcoideu.nItg mrtplwenashoirylcantioghn.s SwWCM2aopadP.uril2Unemgs

pldiancoStCdDrihegSPoncetiUcastdlcIeny sr(hcaM3sCboKu8iep0tAcPrnde6/ioUr35wV9edl0Asny)X, sprwuCdtmsoapechsedPrtcpouimralsoiUnetbsge, mcou(nlfCwVoDtAiaXgPScuhwsitrlyaeUhufstoirtseIdnmrsaorewpWCmtanlopdlPhcauoerfilmUnedymrgst

Modules

2Q-1cb(ouKnMAsoi6dn5ueo0lr)neK,-sdDA3CS6t5Pe05cUIh/nmf)3ioer6cmaa0PlornoydMcei,ndKcoustrAruoe6pisV5lASm0iXwoe,asd(p,u(KlpiAKeon6Asgw36e0sW3)rua,0ctr,hImlaoMyfMsoi,rdce(rufmaoolnVveAadslXevoCitrchPeersUefpnolroNtanhoc-)enDms-SoeSDnIatSnotdIheoprtD2iSL.oSi2nIk.s,e1,
swaparimng.

2.2.2

DSSI CPU Modules (KA670 and KA680)

Due to DSSI signal routing between the H3604 console front panel module of

the KA670 and KA680 CPUs in the BA440 and BA441 enclosures, not all such
systemns support warm swapping of the resident CPU.

Only the H3604 (70-27400-01 revision CO1 or later) front panel will support warm

swapping of its CPU. This revision of the H3604 can be identified by the presence

of a small connector/printed circuit module combination (50-21575-01) attached to
the (17-02353-01 revision B01) cable assembly {Figure 2—1).
Figure 2-1

H3604 Console Front Panel (17-02353-01 revision B01)

S
=

\\ 50-21575.01
)

70-27400-01

Label

(

17-02353-01

—1
11

N
@

\5
BLO-007260

2-2

Warm Swapping Procedures for CPU Modules

Caution

Earlier models of the H3604 front panel (70-27400-01 revision B0l and
earlier) front panel do not have the appropriate cable assembly to support
warm swapping.

2.3 CPU Modules That do not Support Warm Swapping
The following section describes the details of those CPU modules that do not
support warm swapping procedures.

2.3.1

DSSI CPU Modules (KA640 and KA660)

The support for warm swapping both the MicroVAX 3300/3400 (KA640) and
VAX 4000 Model 200 (KA660) CPUs is not possible due to the modules’ on-board
DSSI termination designs. Removing such modules from a live DSSI will cause
improper DSSI termination.

2.4

Removal and Installation Procedures

The following sections describe the removal and replacement of failed Q-bus CPU
modules.

2.4.1

Considerations for System Enclosures

In the case of a failing system CPU within a multisystem DSSI configuration,
proper VMS operating system shutdown procedures must be performed for that

particular Q-bus system setup. Provided the system disk is not resident within
this enclosure, the remaining systems within the multisystem configuration
should remain up and running during the warm swapping maintenance.
All ISEs resident within the failing system enclosure, as well as any local
devices being served by the system, will be temporarily unavailable during
the replacement of the failing CPU. Consequently, proper system management
planning should be considered in advance so that all users are made aware of the
scheduled maintenance and all affected devices are properly dismounted.

Warm Swapping Procedures for CPU Modules

2-3

2.4.2 Shutting Down VMS System Software
If the VMS operating system is up and running on the failing CPU, the following
command should be issued:
$ @SYS$SYSTEM: SHUTDOWN

This should be followed by system-specific shutdown options.

For proper system shutdown procedures, refer to the VMS System Manager’s
Manual.

2.4.3 Obtaining and Recording CPU Module Specific Parameters
Within DSSI multisystem VAXcluster configurations, each CPU has specific
console level parameters used for proper system booting and configuring.
The CPU system-specific parameters are stored within the CPU’s embedded
System Support Chip’s (SSC) internal RAM, which is battery backed up by the

CPU’s front console panei battery pack. Disconnecting any console front panel
from its CPU module will cause the loss of these parameter values.
Before disconnecting any CPU from its console front panel, one must first note

the programmed CPU specific RAM parameters. Below is a list of the most

common parameters. Use the console command SHOW to record the failed
systems parameters in Table 2-1.
Note

For most MicroVAX series CPUs many of these parameters will be not

applicable.

Table 2-1

Failed System Specific Consoie Parameters

Command

Value

>>> SHOW BOOT
>>> SHOW BFLAG
>>> SHOW CONTROLP

>»> SHOW HALT
>>> SHOW LANGUAGE
>>> SHOW RECALL

2-4

Warm Swapping Procedures for CPU Modules

If the system has failed such that one cannot access these parameters, refer to
the site-specific configuration booklet for the proper values.

2.4.4 Removal and Replacement of CPU Modules
CAUTION

Static electricity can damage integrated circuits. Always use antistatic
wrist strap, grounding clip, and antistatic pad found in the staticprotective field service kit (29-26246-00) when working with the internal
parts of any computer system.

After the system manager shuts down the operating system and all appropriate
CPU-specific parameters are obtained, power down the system enclosure, remove
the failed CPU, and install the replacement CPU as described in the appropriate
enclosure maintenance manual listed in Appendix A.

2.4.5

Restoring CPU Module Specific Parameters

After the repaired or replaced CPU is installed, power up its enclosure. Use
the console command SET to reprogram the new CPU with the original CPU’s
system-specific console parameters which were recorded in Table 2-1.

2.4.6

Booting of CPU Modules

After the repaired or replacement CPU is reprogrammed, use the following

console command:
>>>BOOT

With its BOOT and BFLAG parameters properly reprogrammed as described

in Section 2.4.5, the replacement CPU will automatically boot the appropriate
device and VMS system root needed to bring up the entire VMS operating system

software.

Warm Swapping Procedures for CPU Modules

2-5

B O PG00 6099550058900 0000086000 0040800809000 8086868843
f:89.48050 0888048050800 400008060008080506806:9090004184

XXOOOOG

300000 KX XX KX XX
OO

K XXX

XK XK XXX XK

AKX

XK RHK

P OIS IDI G e0420808000080
0 0000058 086000606880¢4
PS40 20 06444000 EE PO PO

PIGIONI DGO ECIIIROE T

PP I NI 0004004

IR0000000408.0680.001

PO ES008800000000
080000 0046680059086
P 409500
48 003000
0000000.0.0660.0840404
8

PO 8088000008 4080800005 00404000444
B0

800 0080.0084000060004004

D050

00408804 68080008000004¢

PGV N

LGS

4048004944

p9.6.0.0.02005008600806.66.4.64.04

P4.8.0.609.05609.600.090806044

TUUXER
XXX KXKALXARAHKX
$99.0046.400.0064.945444
P IS OIOEGE G808 40

B2006.005.699.9.044¢
pA8.0.0.0.0.0.6.¢.4.¢4
p4.8.0.606.680
¢4

$.0.4.9.9.4.4.6.44
1.0.6.0.6.9.9.4

X
XXX

XXXXX
AXAXKXK
XXXHAKXXK
HAKKUUKLXXK

b69088404
8444
P900809000464
044
XXO
XXX
HA
XK
p0.9:0.0.8.0.4.9.¢604 4004444

KXXAKEXKLEEURKEAXAKKLK
F 8080069009000 ¢449645 6044
HUXXAX AKX

XA XXX KK L NAAAR

DS PGPS PO

080806060040404

p S0 E I08000
006600
0008
080000804
HEXX
KK KL LR AXAA
X LKL KK UK KKAREKR
K
XXX XX KL XX XXX

KA KA AN KK XA XKLL

KURH KA IA KA AKX LH KL KKK AR AKX XKAKKEKA R

AXAHAE KK XXX X LK AL R
XHALK KK KAK LKL N

XXAXKEEX AR KL KK
RIS APV
BE O

AR KKK LR LKA KKK XRNKK

AL KK A KK AR AKX KK KL NHNA K

KK XK KX KK KRN

LU KAK

F S04 000000 NG00 00080089406044

0.00000906 0868080408 00000050086969005
094

RS000.944060000.0.0.0506.00400000.60000.6:4.0:4.9:6.99
8.9

AL AR XA UK KK LR XL KA XK BN

WA KK LK KKK

KL KA KA ALK ALK

BSOS NS00 00000 ¢ 000080000850800400¢00.04069
68608

3
Warm Swapping Procedures for KFQSA
Q-bus DSSI Modules
3.1 Introducticn
This chapter contains a detailed descripiion of the following:
e

Description of KFQSA modules that do support warm swapping

Description of KFQSA modules that do not support warm swapping

Removal and installation procedures for warm swapping KFQSA modules

3.2 Warm Swapping KFQSA Q-Bus Modules
Warning

Warm Swapping of the KFQSA Q-bus option requires additional
information given in the KFQSA Installation and User Manual (EKKFQSA-IN). This manual should be obtained before performing warm
swapping procedures on any KFQSA Q-bus adapter.

Warm swapping of KFQSA Q-bus modules oniy applies to the repair and
replacement of failing KFQSA Q-bus modules within multisystem DSSI
VAXcluster ccnfigurations. The following section describes the KFQSA Q-bus
modules that support warm swapping maintenance, along with any restrictions
that may apply.

Warm Swapping Procedures for KFQSA Q-bus D3SI Modules

3-1

\m\_; e

Q%\i e

70-26020-01

[A—
e

Models of the KFQSA S-box Front Handle

[

Figure 3-1

70-26020-02
MLO-007259

3.2.1

KFQSA (M7769, revision K04 and later) Support Warm

Swapping
The KFQSA (M7769, revision K04) Q-bus module and its S-box front handle

(70-26020-02) are specifically designed to offer warm swapping capabilities.
Shown in Figure 3-1, this modified S-box front handle (70-26020-02) can easily
be distinguished from its single input counterpart (70-26020-01) by its physical
characteristic of having two external DSSI connectors.
The proper use of the warm swapping S-box front handle (70-26020-02) also

requires the simultaneous removal of on-board DSSI termination resistors from
the KFQSA (M7769, revision K04) Q-bus module. (See Section 3.4.4 for more

information.)

3-2

Warm Swapping Procedures for KFQSA Q-bus DSSI Modules

KFQSAs (M7769, revision K04 and later) are the only models that support warm
swapping procedures for the BA200-series and BA400-series enclosures.

3.3 KFQSA Revisions That do not Support Warm
Swapping
Due to a lack of provisions to maintain external DSSI bus continuity, coupled
with non-removable embedded DSS!I termination, KFQSA (M7769, revision J06 or
earlier) Q-bus modules do not support warm swapping maintenance techniques.
The attempted warm swapping of any of the earlier revisions of the KFQSA
Q-bus module will leave the DSSI bus not terminated and susceptible to bus
errors which could cause data corruption en ISEs.
Warm swapping procedures are also not supported for KFQSA (M7769) Q-bus
option adapters within BA200-series enclosures when the adapter is configured as
the primary DSSI adapter connected to the internal DSSI bus of these enclosures.

3.4

Removal and Installation Procedures

The following sections describe the procedures required to remove and replace
failed KFQSA (M7769, revision K04 or later) Q-bus modules.

3.4.1

Considerations for System Enclosures

Before replacing any system KFQSA Q-bus module, proper system management

shutdown procedures must be performed, if possible.
In the case of a failing KFQSA Q-bus adapter within a multisystem DSSI
configuration, proper VMS operating system shutdown procedures must be
performed for that particular Q-bus system setup. Provided the system
disk is not resident within this enclosure, the remaining systems within the
multisystem configuration should remain up and running during the warm
swapping maintenance.

3.4.2 Shutting Down VMS System Software
If the VMS operating system is up and running on the failing KFQSA Q-bus, the
following command should be issued:
$ QSYSSSYSTEM:SHUTDOWN

This should be followed by system-specific shutdown options.
For proper system shutdown procedures, refer to the VMS System Manager's

Manual.

Warm Swapping Procedures for KFQSA Q-bus DSSI Modules

3-3

3.4.3 Obtaining and Recording KFQSA Module Specific
Parameters
Similar to the system-specific parameters of a CPU, the KFQSA Q-bus module
contains programmed information that is specific {o the system configuration in
which it resides.

Each module within a Q-bus must use a set of unique Q-bus addresses and
interrupt vectors. These addresses, also known as the control and status register

(CSK) addresses, are necessary for each Storage System Port (SSP) controller

that resides on the Q-bus. Typically, these addresses are uniquely set with the
use of switches or jumpers resident on most Q-bus options.
Through its unique architecture, the KFQSA Q-bus module emulates an SSP
controller for each ISE connected to its DSSI bus. Therefore, the KFQSA Q-bus
module must present a separate CSR address for each emulated controller.
Unlike most Q-bus, modules the KFQSA CSR address values are not set using
physical switches or jumpers. Instead, the unique CSR addresses for each
KFQSA-based ISE are programmed and stored in the form of a configuration
table within the KFQSA Q-bus module’s on-board nonvolatile memory. It is
this specific information that must be obtained and restored when you replace a
KFQSA Q-bus module.
Interrupt vectors for the KFQSA Q-bus module are programmed automatically
by the operating system, and do not need to be programmed or restored manually.
The following sections describe how to access and record the failing KFQSA

Q-bus module’s unique configuration information.
3.4.3.1

Accessing a KFQSA Module’s Configuration Table

The configuration table of the KFQSA Q-bus module cannot be accessed under

the VMS operating system. This procedure must be performed at the CPU
console program level. Consequently, within multisystem DSSI VAXcluster

configurations, a KFQSA Q-bus module must be programmed from the console
terminal of its respective system enclosure.

3-4

Warm Swapping Procedures for KFQSA Q-bus DSS! Modules

Use the console command:
>>> SET HOST/UQSSP/MAINTENANCE/SERVICE n

where:

UQSssp

Selects a device to be accessed

/MAINTENANCE

Used exclusively to examine and modify KFQSA EEPROM

configuration parameters

/SERVICE n

Specifies the controller number of a KFQSA in service mode.
The range of n is from 0— 3.

Note

For details on accessirg the configuration table of the KFQSA Q-bus
module refer to the KFQSA Module Installation and User Manual.

After configuring the failed KFQSA Q-bus module within SERVICE mcde, the

appropriate SET HOST console command will display the current contents of the
configuration table.

. For example:

>>> set host/uqssp/maintenance/service 0
UQSSP Controller
Enter

SET,

(774420)

CLEAR,

SHOW,

HELP,

EXIT,

or QUIT

Node CSR Address Model

0
1

772150
760334

760340

e KFQSA ===-=-

Record the failed KFQSA configuration table’s contents within Table 3-1.
Note

If the failing KFQSA Q-bus module is resident within a system that

does not have support for console command accessing the module, the
MicroVAX diagnostic Monitor (MDM) must be used for this procedure.

Warm Swapping Procedures for KFQSA Q-bus D5S! Modules

3-5

Table 3-1
NODE

KFQSA Configuration Table
CSR ADDRESS

MODEL

0
1

When a KFQSA Q-bus module failure disables access to its configuration table,
refer to the site-specific configuration booklet for the module’s original settings

or recalculate the CSR settings using the console level CONFIGURE process
discussed in Section 3.4.3.2.
3.4.3.2

Obtaining CSR Settings Using the Console Command CONFIGURE

If the site-specific configuration booklet does not contain the necessary
information on the KFQSA Q-bus module’s unique configuration table, the
console command CONFIGURE must be used to determine the repaired or
replaced module’s CSR settings.
The console command CONFIGURE is similar to the VMS SYSGEN CONFIGURE

utility. It permits the user to enter device names, and then generates a table of
recommended Q-bus CSR address settings. To obtain the necessary CSR setting
using CONFIGURE, perform the following steps:
Note

For more information on the use of the console command CONFIGURE,

refer to the KFQSA Module Installation and User Manual.

At the console prompt, enter CONFIGURE.
>>> CONFIGURE

3-6

Warm Swapping Procedures for KFQSA Q-bus DSSI Modules

The system prompts the user for a device and a number. To find what valid
responses are, enter HELP. The console will display a list of all possible
devices that may be configured.
>>> CONFIGURE

Enter device confiquration,
Device,

HELP,

or EXIT

Humber?

Respond by entering the device name and the number of each device. After all
the devices are entered enter EXIT. For example, if the system is configured
with a TK70 tape drive, three RFxx ISEs, and a DESQA interconnect, respond
as follows:
Device, Number?
Device, Number?

tk70
kfqgsa~disk,3

Device, Humbzer?
Device, Number?

desqa
exit

The system responds with the CSR address and vector assignments for all
entered devices:
Address/Vector Assignments
-774440/120 DESQA
~-772150/154

KFQSA-DISK

-760334/300
-760340/304

KrQSA-DISK
KFPQSA-DISK

-774500/260

TK70

Record the address assignments within Table 3-1.
Remember only the CSR address assignments are necessary for programming
the KFQSA Q-bus module. The vector assignments will be calculated
automatically by the system software.
I

Continue the warm swapping maintenance procedures described in the next
section.

3.4.4 Removal and Replacement of KFQSA Q-Bus Modules
After making sure that the failing KFQSA Q-bus module supports warm

swapping maintenance procedures, complete the following steps:
1.

Set the Power switch of the enclosure that contains the failing module to off
(0).
Disconnect the S-box front handle (70-26020-02) from the KFQSA Q-bus

module, being careful not to disconnect the external DSSI cables or
terminators that are attached to the front of the handle itself.

Remove the failing module from its enclosure.

Warm Swapping Procedures for KFQSA Q-bus DSSi Modules

3-7

Remove the embedded DSSI termination (if present) of the repaired or
replaced KFQSA Q-bus module by removing the three resistor SIP packages

(13-29327-01 or 13-38234-01) located directly behind the 50-pin DSSI external
connector shown in Figure 3-2.

Store the SIP terminators in a safe place for possible re-use.

3-8

Warm Swapping Procedures for KFQSA Q-bus DS51 Modules

Figure 3-2

DSSI and SIP Terminators on KFQSA Revision K04 or Later

50-Pin DSSI
External
Connector

13-29327-01
SIP Package

13-29327-01

SIP Package ? :

MLO-007257

Warm Swapping Procedures for KFQSA Q-bus DSSI Modules

3-9

At this time do the following:

—

Set the Dual In-Line Plastic (DIP) switchpack of the repaired or replaced

—

Install the repaired or replaced KFQSA (M7769, revision K04 or later)
into the appropriate Q-bus enclosure.

—

Connect the S-box front handle to the KFQSA Q-bus module.

KFQSA to SERVICE mode.

Caution

The S-box front handle must be connected to the KFQSA Q-bus module,
in order to successfully restore the configuration table.

—

Set the enclosure Power switch to on (1).

Continue with the warm swap maintenance procedures described in the next
section.

3.4.5 Restoring the KFQSA Q-Bus Module’s Configuration Table
After the repaired or replaced KFQSA Q-bus module has been properly installed,
complete the following steps:
1.

Use the CSR settings previously recorded in Table 3—1 to reconfigure or
to reprogram the repaired or replaced module. For more information on

restoring the module refer to the KFQSA Module Installation and User
Manual.

Reset the DIP switchpack for normal operation (non-SERVICE mode).
Power off and then power on the system enclosure containing the repaired or
replaced KFQSA.

Verny that the KFQSA Q-bus module is properly reconfigured and that all
ISEs are seen using the console command SHOGW UQSSP.

3-10

Warm Swapping Procedures for KFQSA Q-bus DSSI Modules

For example:
>>> show ugssp

UQSSP Disk Controller 0
~-DUAD
(RF31)

(772150)

UQSSP Disk Controller 1
~DUB1
(RF72)

(760334)

UQSSP Disk Controller 2
-pUC2
(RF31)

(760340)

UQSSP Tape Controller 0
-MUAO
(TK70)

(774500)

Reboot the operating system software at this time

Warm Swapping Procedures for KFQSA Q-bus DSS! Modules

3~11

PSSO

E0080500665000
06040080 80604880600 4846444

PSSO OO AN

S805004000668000
08089 0860048040 000044

P00 5050 0080886000400
80.84 880000000008 0866004044
P OSSN S I NG

E PO 0000400000080 0000600884990 4

P058000400080000
5008 bttt et seis oo e esdd
b48040850006888
8008 588868684000 008800408444
PGS0884684608085
8038 00000880800 44444

NP O ES L e HE 0000400000806000000

PASAG

I006048800000
460 4000000006644 04

04800000 50000060088 0584060044

P08 54005 966080480804 5808.064084804484

EXUXXKEZX
XK XK LEA K LL AKX KL KKK
p:9:8.484.40.0.8.8.8.8.60.0.$.090004404.044

FAS

809060040 808600084808¢84

PO 98600050800 0886086404 1
P 5034604608000 08040004

AXAK KKK
AR AKEKLK
D40 984046005444
b4.4.40.4.6.084.694.4464

AKEAKAK

p.. 99,8464
.4

X
LAXXX
XXXHEXK

XXXXXXHKAX
p06566044044
KEXXXXKXAAKXX
XAXAAK
KKK AAXKX
KEXK UL XK AAALLLAKLX
EXXAXKKK
XX XX XEKE KL
PO 809.08680648609060644
pe.0888.6496088084866444044
ERAKDUXU
KU LK ALK AL KAKKKAL L
XAXA AL XAKK KX A X KK UK KKKARANALK

XAAL
XK UARK
K
KL H K AN

ALK

XA KU XL KK KR AR LK AU

p9.0.9.94809660000005
50.0.09 04005300004
S6.9.0.0.8.0.0000004096496.4.08660004000404
FXEX

KK KA KK KR LA LA KLU

KX KR KK KU A AKX LA K

PO S00005060000000
8080 890660009608944649.4

bOR GO NGOG4069800009480
8 0506900604600
XHXKXA X

AK KOO

KL KA

KA LA KA XL KR

AL KL KAR

B8 $.0:6.0.0.00086400006000580
000490 0.0.0904.4.44.644
J0000056000008
0 08080500t
s s et sdsoeessss v
PO0589900000008
4 008806900804 08:0 095069695664 ¢94
p0.3.6:4.00.9.09 9608000800000 0

1000 E0 0000808000 8.6.0.6.0.4:0.44

For example:
>>> show ugqssp

UQSSP Disk Controller 0
-DUA0

UQSSP Disk Controller 1
~DUB1

(760340)

(RF31)

UQSSP Tape Controller 0
~MUAO

(760334)

(RF72)

UQSSP Disk Controller 2
-pUC2

(772150)

(RF31)

(774500)

(TK70)

Reboot the operating system software at this time

Warm Swapping Procedures for KFQSA O-bus DSSI Moduies

3-11

4.2.1

ISE FRU Warm Swapping Requirements

The replacement of a failing ISE within an active DSSI bus is not as simple
as merely pulling out the failed device and installing the replacement device.
Using a detailed procedure similar to the techniques used in Hierarchical
Storage Element (HSC) configurations, the repaired or replaced ISE must be
pre-programmed with the failed ISE’s unique DSSI VAXcluster parameters.
CAUTION
This procedure must be followed carefully. If a parameter is not entered

correctly, then a system reboot will be necessary or the ISE (an? sussibly
the system) will be temporarily rendered unusable. The VMS operating
system recognizes an ISE by its unique values for these parameters. If
the appropriate parameters are not changed, VMS will refuse connections
to both the old and new parameter values for the ISE.

Values must be assigned for each of the ISE parameters described in Table 4-1.

4~2

Warm Swapping Procedures for DSSI Integrated Storage Elements (ISE)

Table 4-1

ISE PARAMETERS

Parameter

Description

ALLCLASS

Allocation class. The default value is 0 (false). Set the
ALLCLASS value to 0 or the allocation class chosen
for the system. Note that shadowed disk devices must
be set to a nonzero allocation class.

FORCENAM

Force name parameter that determines if the ISE is to
use the NODENAME parameter value instead of the
manufacturing name given to the ISE. The value must
be 0. If the value is 1 the ISE uses a generic device
name such as RF31x.

FORCEUNI

Force unit parameter. To use UNITNUM as the device
unit number, set the FORCEUNI parameter to 0.

The factory default value of 1 uses the DSSI node
plug value (on the front bezel of the ISE) as the unit
number.

NODENAME

Node name for an ISE. Each ISE has a node name that
is stored in EEPROM. The node name is determined
in the manufacturing process and is unique to each
ISE. The node name can be changed depending on the
needs of the system site.

SYSTEMID

System identification number. All SYSTEMIDs must
be unique within the system. Replacement drives
must be programmed with the identical SYSTEMID of
their failed counterpart.

UNITNUM

Unit number that specifies a numeric value within the
allocation class to which the ISE is being configured.
Follow the unit number scheme of the site system
setup.

HISPEED

The factory setting for this parameter is 0 (false).
If set to 1 (true), only half of the ISE capacity is
presented to hosts. This reduces the stroke of the
seek, and thus improves performance at the expense of
capacity.

Warm Swapping Procedures tor DSSI Integrated Storage Elements (ISE)

4-3

4.2.1.1

Warm Swapping RF-Series ISEs

The RF-series ISEs each consist of two basic FRUs:
¢

The head-disk assembly (HDA)

The drive module

See Figure 4-1.
Figure 4-1

RF-Series ISE Showing HDA and Drive Module

Module
MLO-007261

The drive module is a single printed circuit board containing the controller and

device electronics and is mounted on the right side of the HDA when situated in
a BA400-series enclosure.

4-4

Warm Swapping Procedures for DSSI Integrated Storage Elements (ISE)

4.2.1.2

Warm Swapping TF-Series ISES

The TF-series ISEs each consist of two basic FRUs:
1.

The two-board controller

The tape drive.

See Figure 4-2.

4.3 Obtaining and Recording Current ISE Specific
Parameters
The fundamental reason for using warm swapping techniques is to keep the VMS

operating system up and running while performing system maintenance.
In many system configurations it is possible to use console commands to
obtain these parameters. In DSSI-based single CPU systems, however, console
commands cannot be used if the VMS operating system is to be kept up and
running. The next three sections describe techniques for obtaining the ISE
parameters while the VMS operating system is operational.

4.3.1

Using the VMS Diagnostic Utility Protocol (DUP)

Perhaps the most important function of warm swapping ISEs is the proper
reconfiguring of repaired or replaced ISEs so that they appear to the VMS
operating system with the identical parameters of the originally failed ISEs.

This recording and restoring of ISE unique parameters can be done with the use

of the VMS diagnostic utility protocol (DUP).
Using DUP, a user can connect a terminal to a storage controller by first loading

the VMS DUP class driver followed by "setting host” to the ISE’s individual DUP
server which is resident within the ISE’s controller microcode.
Upon execution of the following Digital Command Language (DCL) command:
$ BET HOST/DUP/SERVER=MSCPS5DUP/TASK=taskname nodename

Warm Swapping Procedures for DSSI Integrated Storage Elements (ISE)

4-5

Figure 4-2

Showing Components of TF-Series ISE
TFxx Two-Board

Controller

TFxx Tape

Drive

MLO-007258

4-6

Warm Swapping Procedures for DSSI Integrated Storage Elements (ISE)

where:

taskname

the utility or diagnostic program name to be executed on the

nodename

the node name of the ISE

target ISE

This creates a virtual terminal connection to the MSCP$DUP server that allows
the execution of a utility or diagnostic program on the MSCP storage controller

(ISE) that uses the DUP standard dialogue.

Once the connection is established, operations are under the control of the utility
or diagnostic program. When the utility or program ends, control returns to the
local operating system.

PARAMS is the ISE management utility that lets you examine and change ISE
parameters such as node name, allocation class, and unit number. PARAMS is
also used to display the state of the ISE and performance statistics maintained
by the ISE.

PARAMS prompts the user for a command with the PARAMS> prompt. Upon

entering one command, PARAMS executes it, and prompts for another command.
To stop the PARAMS utility, press Ctrl/C, Ctrl/Y, Ctrl/Z, or enter Exit. Table 4-2
lists PARAMS commands.
Table 4-2

PARAMS Commands

Command

Description

EXIT

Stops the PARAMS utility

HELP

Displays infermation on how to use PARAMS commands

SHOW

Displays the setting of a parameter or a class of parameters

WRITE

Records in nonvolatile RAM the device parameter changes
made using the SET command

To find more information on reconfiguring and installing RF-series and TF-

series ISEs, refer to the BA400-Series Enclosures Storage Devices Installation
Procedures.

Warm Swapping Procedures for DSSI Integrated Storage Elements (ISE)

4-7

4.3.2 Obtaining Parameters Using DUP
Digital Equipment Corporation recommends that a worksheet of the parameters
for all ISEs, as well as the serial number of each ISE, be maintained within
the site-specific configuration booklet. This is especially important at sites that
maintain a set of spare drives that may be stored for some time before they are
used.
The worksheet, aids in:

Preventing duplicate parameters which render an ISE temporarily unusable
until the duplication is isolated and corrected

Determining the parameter setting of a non-operational ISE to create a
replacement unit with identical parameters.

Use the ISE parameter worksheets in Table 4-3 to identify and record critical
parameter names.

4-8

Warm Swapping Procedures for DSSI Integrated Storage Elements (ISE)

Table 4-3

Individual ISE Worksheet

Serial Number:
NODENAME:
SYSTEMID:

ALLCLASS:

UNITNUM:

. FORCEUNTI:
FORCENUM:

HISPEED:

Serial Number:
NODENAME:

SYSTEMID:
ALLCLASS:

UNITNUM:
FORCEUNI:
FORCENUM:
HISPEED:

Warm Swapping Procedures for DSSI Integrated Storage Elements (ISE)

4-2

If the parameter values were not recorded, use the following steps to extract the
information from the failed ISE:
1.

Find the node name (NODENAME) for an ISE needing replacement by using
one of the following DCL commands:
$

SHOW DEVICE [DI OR MI}

where:

= RF disks

TF tapes

For example:

$ SHOW DEV DI

Device
Name
$18D1A100:

$1$DIA101:

(WOOFA)

Device
Status
Mounted

Error
Count
0

Volume
Label
VMSRLS

Free
Trans
Blocks Count

1361730

246

Mnt
Cnt
1

(TWEETA)

Mounted

DISK1

174588

The nodename for the ISE is shown in parentheses.
SHOW CLUSTER

For example:

$ SHOW CLUSTER

View of Cluster from system ID 5487

\ AWDEO

| VMS V5.4

| MEMBER

WOOFA

RFX V255

TWEETA

RFX V255

node: AWDEO

Note

RFX V255

Firmware version number

Determine whether the VMS DUP class driver is loaded by entering following
DCL command:
S SHOW DEVICE FYAOQ
%

4-10

SYSTEM-W-NOSUCHDEV,

no such device available

Warm Swapping Procedures for DSSI Integrated Storage Elements (ISE)

’

If the driver is not loaded, load it as follows:
$ MCR SYSGEN

SYSGEN> CONNECT FYAQ/NOADAPTER
SYSGEN> EXIT

Use the SET HOST command to establish a DUP connection with the ISE:
$ SET HOST/DUP/SERVER=MSCP$DUP/TASK=PARAMS nodename

This invokes the DUP server on the ISE and runs the PARAMS utility
4.

Refer to the parameters listed in Table 4~1 and use the SHOW command
to show the appropriate values of the failed ISE. Be sure to record the new
parameters on the ISE worksheet as shown in Table 4-3.
For example:

$ SET HOST/DUP/SERVER=MSCP$DUP/TASK=PARAMS TWEETA
$HSCPAD-I-LOCPROGEXE, Local program executing - type “\ to exit
Copyright (C) 19%0
Digital Equipment Corporation
PARAMS> SHOW NODENAME

Parameter

Current

NODENAME

Default

TWEETA

RF31

PARAMS> SHOW SYSTEMID
Parameter
—— ——— ————

SYSTEMID

Current

— o —

s r 5

Type

Default

g S 2ot By o Py

0404100801484

- — "

SO T T

e S 2

Y S W

Radix

String

Ascii

Type

Radix

— ——————

0000000000000 Quadword

—

Hex

PARAMS> SHOW ALLCLASS

Parameter

Current

ALLCLASS

Default
1

PARAMS> SHOW UNITNUM

Parameter

Current

UNITNUM

Type
0

Default
101

Byte

Type
0

Word

Radix
Dec

PARAMS> SHOW FORCEUNI

Parameter

Current

FORCEUNI

Default

Type

Boolean

Radix

0/1

PARAMS> SHOW FORCENAM

Parameter
FORCENEM

Current

Default
0

Type
0

Boolean

Radix
0/1

Warm Swapping Procedures for DSSI Integrated Storage Elements (ISE)

4-11

PARAMS> SHCW HISPEED

Parameter

Current

Default

HISPEED

Type

Radix

Boolean

0/t

Note

SHOW HISPEED [Retain]
Only applicable to RF31,

RF35,

RF7Z,

and RF73 ISE devices

4.3.3 Obtaining Parameters Using VMS
{f connection cannot be established with the ISE DUP server, the VMS operating
system utilities can be utilized. To find information on some of the parameters
usc the DCL command ANALYZE/SYSTEM.
In the following sample output, the SYSTEMID is 404100801484 (taken from
"Contr! ID") and the ALLCLASS is 1.
S ANALYZE,/SYSTEM
VAX/VMS Syst.m analyzer

SDA> SHOW DEVICE $1$DIA101:
1/0 data structures

TWEETASDIALOL

RF31

UCB address:

803B17D0

Device status:
00021810 online,valid,unload,lcl
valid
Characteristics: 1C4D4108 dir,rct, fod, shr,avl,mnt,elq,
idv, odv, rnd
00002221 clu,mscp,
nom, loc
Owner GIC {[000001,0000C4]
Pib

00000000

Alloc.

lock ID

Alloc.

class

000C0O034
1

Class/Type
Def.

buf.

01/38
size

512

DEVDEPEND

7450832

FLCK index
DLCK address

34
0000600006

DEVDEPND2

00000000

Press

Operation count 306

ORB address

803B1900

Brror count

DDB address

806DE690

Reference count

DDT address

8042EC38

Online count

V(B address

803CCACO

BOFF

0000

CRB address

805E5590

Byte count

0200

PDT address

BO3A6DCO

CDDB address

803B1960

SVAPTE

DEVSTS

ERWAITCNT

8338CE54

0004

6000

[/0 wait queue

empty

for more.

SDA>
1/0 data structures
-

)

~=-~ Primary Class Driver Data Block (CDDBj

80G3E1960 -~~~

Status:

0040 alcls set

Controller Flags:

80D4 of miths,cf_this,cf
misc,cf attn,ci replc

4-12

Warm Swapping Procedures for DSSI Integrated Storage Elements (ISE)

1
Allocation class
00801484
System ID
0000
00801484
Contrl. ID
01644041
000006000

Response ID

CDRP Queue

empty

DDB address

Restart Queue

empty

CRB address

DAP Count
Contr. timeout
Reinit Count
Wait UCB Count

0
60
0
0

CDDB link
PDT address

Original UC
UCB chain

806DEAFO
805E5590
803B1B20
803A6DCO
00000000
803B17D0

MSCP Cmd status FFFFFFFF
%%

Press
SDA> EXIT

I/o

request

queue 1is empty ***

for more.

[Return]

For the remaining ISE parameters, enter the DCL command SHOW DEVICE DI
to display the following information:
$ SHOW DEV DI
Device

Device

Error

Volume

Free

Hame

Status

Count
0
5

Label
VMSRLS
DISK1

1361736
174588

$1$DIA1G0:

$18DIAI0L:

{WOOFA)

Mounted

IWEETA)

Mounted

Trans
Blocks Count

246
1

Mnt

Cnt
1
1

The failing ISE device name in the sample above is $1$DIA101.
NODENAME
The node name is shown in parentheses. In the above sample output the node
name of the failing ISE is TWEETA.
ALLCLASS
Aside from using the ANALYZE/SYSTEM command, the allocation class is
found in the device name between the the dollar signs ($). In $1$DIA101, the

failing ISE has an allocation class of 1. If the allocation class was 0, the node
name would display TWEETA$DIA101.
UNITNUM

The UNITNUM is the number following the DIA. In $1$DIA101: the
UNITNUM is 101. It is the MSCP unit number.
FORCENAM
The force unit name is set to 0 if NODENAME is anything other than an

RF31x. The "x" corresponds to a DSSI node 1D (A=0Q, B=1, and so on).
FORCEUNI
The force unit is set to 0 if the unit number of the device appears as
larger than seven (7). If the unit number of the device is between 0 and

7 and matches the DSSI node ID plug on the front bezel of the ISE, than
FORCEUNI is probably set to its default of 1.

Warm Swapping Procedures for DSSI integrated Storage Elements (ISE)

4-13

Although not directly shown in the sample output, HISPEED is set to 1 if the
DCL command, SHOW DEVICE/FULL devicename, reveals a device type of

RFHxx instead of RFxx. Otherwise, HISPEED is set to its default of 0.

4.4 Removal and Installation Procedures for ISEs
The following sections describe the procedures required for the removal and

replacement of failed ISEs.

4.4.1

Finding Failed ISE FRUs

The maintenance philosophy for the ISE is to replace the failing FRU. The failing

FRU can be determined through the use of host level diagnostic error reports,
operating system error reports, fault codes displayed on the ISE storage device

operator control panel (OCP), or the use of VAXsimPLUS.
For further information on determining an ISE’s failing FRU, refer to the

appropriate ISE service guide.

4.4.2 Enclosures That Support Warm Swapping
Only ISEs resident within the following enclosures support warm swapping
procedures:

BA430

BA431

BA440

BA441

B400X

¢ B401X

R400X

R23RF

Because these enclosures do not allow for individual power cycling of their ISE’s,

the entire enclosure must be shut down and/or powered off in order to perform
warm swapping maintenance on any one {or more) enclosed ISEs.
Prior to performing any warm swapping procedures, certain system management

tasks must be followed depending on which enclosure contains the failed ISE. All
drives contained within the same enclosure as the failed ISE, must be logically
dismounted.

4-14

Warm Swapping Procedures for DSSI Integrated Storage Elements (ISE)

WARNING

Warm swapping procedures are not to be used when connecting or
disconnecting an entire DSSI-based enclosure to or from an active DSSI
bus. Such maintenance requires the shutting down of the entire DSSI bus
prior to its execution.

4.4.3 Dismounting and Removing Failed ISEs
After obtaining the ISE’s unique parameters perform the following steps:
1.

If the ISE is mounted, logically dismount it from the system or VAXcluster
configuration using the following DCL command:
$ DISMOUNT/CLUSTER devicename

If the device fails to dismount due to installed files, spooled devices, or open

file violations, refer to Appendix B, DISMOUNT Command Regarding Open
Files.
Make the failing device unavailable to the entire VAXcluster configuration
using the VMS SYSMAN utility as follows:
¢ MCR SYSMAN

SYSMAN> SET ENVIRONMENT/CLUSTER
$SYSMAN-I-ENV,

current command environment:

Clusterwide on local cluster
Username SYSTEM
will be used on nonlocal nodes
SYSMAN> DO SET DEVICE/NOAVAILABLE devicename
SYSMAN> EXIT

Verify that the device has been marked as unavailable by entering the DCL
command SHOW DEVICE.
For example:

$ SHOW DEVICE $15DIA101 [Retuinm]
Device

Device

Error

Volume

Name

Status

Count

Label

$1$DIA101:

(TWEETA)

VUnavailable

Free

Trans

Mnt

Blocks Count

Cnt

If a failing ISE is resident within one of the following enclosures,
e

BA430

BA431

BA440

BA441

Warm Swapping Procedures for DSSI Integrated Storage Elements (ISE)

4-15

B401X

follow the proper VMS shutdown procedures for that particular Q-Bus
system setup prior to powering down the enclosure. The remaining

systems in a multisystem configuration, will remain up and running
during the warm swapping procedure, if the system disk is not resident in
the powered down enclosure.

This should be done using the following command:
S @SYS$SYSTEM:SHUTDOWN [REtGrm]

This is followed by system-specific shutdown options.

For proper system shutdown procedures, refer to the VMS System Manager’s
Manual.

Set the ISE’s enclosure Power switch to off (0). Wait 15 to 20 seconds (for the
drive to stop spinning and interlock solonoid to release).

CAUTION
Static electricity can damage integrated circuits. Always use antistatic

wrist strap, grounding clip, and antistatic pad found in the staticprotective field service kit (29-26246-00) when working with the internal
parts of any computer system.
Use great care when handling an ISE. Excessive shock can damage the
HDA.

Remove the ISE from the system or expander cabinet using those techniques

described in the appropriate enclosure manual.
Continue on to the next section.

4-16

Warm Swapping Procedures for DSSI Integrated Storage Elements (ISE)

. 4.4.4 Installing Repaired or Replaced ISEs

To install a repaired or replacement ISE, perform the following steps:
CAUTION

Use great care when handling an ISE. Excessive shock can damage the
HDA.

Install the replacement ISE into the correct enclosure using those techniques
described in the appropriate enclosure manual listed in Appendix A.

Set the ISE’s enclosure Power switch to on (1). Wait for the drive to start
spinning, lock the interlock solenoid, and complete its self tests.

If a failing ISE is resident within one of the following enclosures, boot the
operating system software at this time.

e BA430
e

BA431

BA440

BA441

B400X

B401X

’ Continue on to the next section.

4.5 Restoring the ISE Specific Parameters
Warm swapping restore procedures will vary, depending on which of the following

FRU components of the RF-series or TF-series ISEs is replaced:

RFxx drive module

RFxx HDA

TFxx tape drive

TFxx two-board controller

Warm Swapping Procedures for DSSI Integrated Storage Elements (ISE)

4-17

When the drive module of an RFxx ISE or the two-board controller of a TFxx ISE .
is to be replaced, all ISE unique parameters must be obtained from the failed
module and reprogrammed into the repaired or replaced module. Use those warm
swapping procedures listed in Section 4.5.1 when any one of the following need
replacement:

RFxx drive module

TFxx two-board controller

Complete RFxx or TFxx ISE

Parameter changes are not necessary when the FRU being replaced is one of the
following:

RFxx HDA

TFxx tape drive

When any of these FRUs needs replacement, continue with those warm swapping
procedures listed in Section 4.5.2.

4.5.1

Replacement of FRUs Requiring Parameter Reprogramming

When the drive module of an RFxx ISE or the two-board controller of a TFxx ISE
is to be replaced, complete the following steps to restore the parameters from the
failed ISE:
1.

Find the NODENAME parameter for the replacement ISE by using one of the
following DCL commands.
$ SHOW DEVICE {DI OR MI]
where:

= RF disks

= TF tapes

Fcr example:

$ SHOW DEV DI
Device

Device

Error

Volume

Free

Name

Status

Count

Label

Blocks

VMSRLS

1361574

R1IQSAASDIAZ:

$13DIA100:
$1$DIA101:

(WOOFA)
(TWEETA)

Online

Mounted
HostUnavailable

0
0

The nodename for the ISE is shown before the dollar sign ($) of the device
name.

4-18

Warm Swapping Procedures for DSSI Integrated Storage Elements (ISE)

Note

At this time, the original device will appear as HostUnavailable
since VMS does not see any ISE "host” with the identical ISE unique
parameters of that failed ISE.

$ SHOW CLUSTER
For example:

$ SHOW CLUSTER
View of Cluster from system ID 5487
et

EEE PR E PR

SYSTEMS

node: AWDEO

| MEMBERS |

NODE

SOFTWARE

STATUS

et
LR L E R R +

AWDEO

VMS V5.4

WOOFA

RFX V255

TWEETA | RFX V255
RIQSAA | RFX V255

MEMBER

o
e+

Note

V255
Firmware version number

Determine whether the VMS DUP class driver is loaded by entering following

DCL command:
$ SHOW DEVICE FYAQ
%
Q

SYSTEM-W-NOSUCHDEV,

no such device available

If the driver is not loaded, load it as follows:
$ MCR SYSGEN

[Return]

SYSGEN> CONNECT FYAO/NOADAPTER

SYSGEN> EXIT

Use the SET HOST command to establish a DUP connection with the ISE:
$ SET HOST/DUP/SERVER=MSCP$DUP/TASK=PARAMS nodename

This invokes the DUP server on the ISE and runs the PARAMS utility
Refer to the parameter listed in Table 4-1 and use the SET command to set
appropriate values for the parameters. Since the replacement ISE will have a
new serial number, be sure to record its new parameters on the worksheet for
the ISE.

Warm Swapping Procedures for DSSI Integrated Storage Elements (ISE)

4-19

For example:

$ SET HOST/DUP/SERVER=MSCPS5DUP/TASK=PARAMS R1(QSAA

$HSCPAD-I-LOCPROGEXE, Local program executing - type TM\ to exit
Copyright (C) 1990 Digital Equipment Corporation
PARAMS> SHOW NODENAME

Parameter

Current

Default
-

NODENAME

R1QSAA

Type

—

RF31

PARAMS> SET NODENAME TWEETA

Current

SYSTEMID

593200495860

String Ascii

—

PARAMS> SHOW SYSTEMID

Parameter

Radix
——

befault
0000000000000

Type

Radix

Quadword

Hex

Type

Radix

PARAMS> SET SYSTEMID 404100801484
PARAMS> SHOW ALLCLASS

Parameter
—— ——————
-

Current
——

Default

ALLCLASS

—

o
o~

Byte

Dec

PARAMS> SET ALLCLASS 1
PARAMS> SHOW UNITNUM

Parameter
D

Current
S e T Y R e . S it D

Default
e e W e B

UNITNUM

- - "

Type
. >

- o g o~

Radix
- -

Word

Dec

PARAMS> SET UNITNUM 101
PARAMS> SHOW FORCEUNI

Parameter

Current

FORCEUNI

Default

Type

Radixz

Boolean

0/1

PARAMS> SET FORCEUNI 0

PARAMS> SHOW FORCENAM

Parameter

Current

FORCENAM

[heEuin]

Default

Type

Radiz

Boolean

0/1

PARAMS> SHOW HISPEED

Parameter
HISPEED

Current

Default
0

Type
0

Boolear

ok?

[Y/[N]]

Radixz
9/1

PARAMS> WRITE

Changes require controller initialization,
Initializing. ..

4-20

Warm Swapping Procedures for DSSI Integrated Storage Elements (ISE)

HSCPAD~S-REMPGMEND, Remote program terminated - message number 3
%HSCPAD-S-END,

Control returned to AWDEO

$
Note

SHOW HISPEED

Only applicable to RF31, RF35, RF72, and RF73 ISE devices

Note

Do not forget to enter the WRITE command since no changes will be
stored without its execution.

When the initialization is complete, the replacement ISE and its parameters
are made available to the VMS operating system. This can be seen by using
the DCL command SHOW DEVICE DI
For example:
$ SHOW DEVICE DI
Device

Device

Error

Volume

Free

Name

Status

Count

Label

Blocks

R1QSAASDIASZ:

HostUnavailable

Online

VMSRLS

1361574

$1$DI1A100:
515DIA101;

(WOOFA)

(IWEETA)

Mounted

Note
The DCL commands SHOW DEVICE DI or SHOW CLUSTER continue to
show the name of the replacement ISE as HostUnavailable. This does not
harm the system. After the next reboot, this replacement ISE name will

disappear.

Make the repaired or replacement device available to the entire VAXcluster

configuration using the VMS SYSMAN utility as follows:
$ MCR SYSMAN [Return]

SYSMAN> SET ENVIRONMENT/CLUSTER
%SYSMAN-I-ENV,

current command environment:

Clusterwide on local cluster
Username SYSTEM
will be used on nonlocal nodes

SYSMAN> DO SET DEVICE/AVAILABLE devicename
SYSMAN> EXIT

Warm Swapping Procedures for DSSI Integrated Storage Elements (ISE)

4-21

Verify that the device has been marked as online by entering the DCL
command SHOW DEVICE. Fer example:
$ SHOW DEVICE DIA101
Device
Name
§15D1Aa101:

(TWEETA)

Device
Status
Online

Error
Count
0

Volume
Label

Free
Trans
Blocks Count

Mnt
Cnt

If appropriate, mount the device using the DCL MOUNT command which is
specific to the system site setup.

4.5.2 Replacement of FRUs not Requiring Parameter
Reprogramming
The following ISE FRUs allow for replacement but do not require parameter
reprogramming:

RFxx HDA

TFxx tape drive

For these FRUs, perform the following steps to complete the ISE warm swapping
procedure:
1.

iMake the repaired or replacement device available to the entire VAXcluster

configuration using the VMS SYSMAN utility as follows:
$ MCR SYSMAN
SYSMAN> SET ENVIRONMENT/CLUSTER
%SYSMAN-I-ENV,

current command envircnment:

Clusterwide on local cluster
Username SYSTEM
will be used on nonlocal nodes

SYSMAN> DO SET DEVICE/AVAILABLE devicename
SYSMAN> EXIT

Verify that the device has been marked as available by entering the DCL
command SHOW DEVICE.

For example:
$ SHOW DEVICE $15DIA101
Device

Device

Error

Volume

Name

Status

Count

Label

Online

$1$DIA101:

(TWEETA)

Free

Trans

Mnt

Blocks Count

Cnt

If appropriate, mount the device using the DCL MOUNT command which is
specific to the system site setup.

A D99

\Warm Quinanninr Pracart:irac far NOCE tatarratnd Ciaramea IDlantandes 1C0Y

P 42000900000008690008000808800066090¢804.000600008084
p$0.9006900648006068060000686306080606000964606044¢04
P 6965646008.600000600¢60008850004008400040408046094

P 8964856900904 6060800000060380804000¢00¢09¢4
PP 00680800808
6800 8000000000 00800 se 00446049
RARARL LXK LXK KR LA KK XA XX OOOOO0CO0OXX
X

P03 0400006088008 0040080608000 408060¢.40¢4
R 900806000904006600000008400868006084¢44
P e 0858480000808 80840868060460040444¢04
P8 2084948840600080808
8864869 04640444
P 80808309008 8608808480046604040004

XXX XXX

KKKAKXARAKKXKXLKAK

B3 40000505084000
0000809 00044
p00¢4099.99.86098900$0600694
P09049006.0960080090600044
$$8.¢99.6060000696044464
$.9.6.9.8.00.¢.6060800064649
£ 0.0.0.60.60.600696¢604
p09.0.8.066566604
64
1860606060604
FEEXKXALXKK
$.8.0.0.9.¢4.6.6.¢.4
KAXXKAX

XAXXX

XXX
X

X
XXX
XXXKX

XXXXAXX

XXAXKXXXK
XAXXXXXKXKK
XAXXXXKXEAK
AKX

AXAXOOOALXAXXXK
XAXAUXXKXKXKXXXALAXK
XXX XU XA XA XK KLXNAR
K

PO 9800484 64.009696048003
P9#08.8609.8000906000460¢4
F0 096600880504606.0600449¢9
p$9808 0000080000060¢08040¢4
PG 8000000000059 00040864800001

PO08000800
¢0000
40080
49060404444
PO 89400000068.+900060084664500949¢44

PO S G008 03000008000
06000
0004
4000044

PRSI DI PE008080084844
00 880488 ¢804004
pUO 4000000000080 0000080000400 08000044
P00 6000800
085 0094006048480
050080
0¢0086¢4
PSS

NSO O GG

PO EEIO LIPSO NI

I 0000068 8900800000 80004

VIEOTOFIOEHV000090800004

BT EOO VO LI 0000.08 0940000 840.0999009.600
08600469044

KHEE A RARE LK LK UL LA AR KA LA KA KL L LEE A KRR A KL KRR LKA KLY

BP09064888400080
E8 88000 TIINOIOEE S0 00.684900480¢

A
Related Documentation
Document

Order Number

BA400-Series Enclosures IPB

EK-440/430-AB*P

BA400-Series Enclosures Storage Devices
Installation Procedures

EK-BA44A*-IN

BA400-Series Mass Storage Devices

EK—441AC*-IP

BA430/440 Enclesure Maintenance

EK-348A*-MG

KA670 CPU System Maintenance

EK-347AB*-MG

KFQSA Module Installation and User
Manual

EK-~-KFQSA-IN

KFQSA Module Service Guide

EK-KFQSA-SG

MicroVAX Diagnostic Monitor User’s
Guide

AA-FM7A*-DN

R400X Expander Installation and
Maintenance

EK-349A*-MG

RF-Series Integrated Storage Eiement

EK-RF72D*-UG

User Guide
TF85 Cartridge Tape Subsystem Owner’s
Manual

EK-TF85-OM

TF857 Cartridge Tape Subsystem
Owner’s Manual

EK-TF837-OM

VMS General User’s Manual

AA-LA9BA*-TE

VMS System Manager’s Manual

AA-LAOOB*-TE

Note
* Indicates the revision code. The latest revision will always be shipped

when a manual is ordered.

Related Documentation

A-1

fOA50000060
000 bbb 000600000900
0680
8009008 60,9964
0

OSSP SOOI 0G0

00000040008800009048044.4004.4

LEEIOINI IO IE00080860086809648064

BO0 #6085 46005800580 808000 800000 E ettt 080004
DOS04000
0080
008000
000000408008 8040090
05
08044
[iS. 868000
0 8000000000840
008880
44460040 8644
8
P80 000008 600388080800 0860086080040400044

PO 6000000000
000088888 400000400]8
000

XXX IO

XK XA XK

KEXX KX MK UK HX KL LK KA KKK

KR K XANA KKK

LKA

KKK

XXX OO
K OO XXX
B8404806900000008
000 06460464

$9.8.0.8.95.0.4.0244 4064464008980
P$.6.09900.8.00609800.0006090¢44

p9.800.00.6.6.0.000060990805¢¢4
P 4.806,00064004099.4964¢44

P98.0.0.¢.6.860.¢96¢48004¢4
b 8.8.0.8.66.65645698449
$.0.8.0.8.4.6.¢.4.406.4.944
ZAXXKXHKARKNK
$6.4.0.6.4.0.4.0.9.9.4
HEXXXXKAXX

X
XXX
XXXYXX

XXXXXXX
XXAAXKXXK

KXXXXKXKXAXK

XAXXXXXXXKXKK
HUXXXXXXNAXKXHAKK,

EXAX XA XL XA XAXXXK
K
EXRX
KK KA KL
KAK
UK AUK LA

pO.9 0868.048840000006064¢4

KXEX KA XK XK XX KKKLNANKANK
P99.900.000.00804006040600064¢0]

PO SIS IO04984606
00068¢]
906
KXAXAXKXA
UK XA XX XXX X AKX XRKALAUXK
XX KAAXXAUX XA KA XKX AKX

KA XA KK XA KA K

bSO00808
00080 0000040080
080
04 0
0044

BOS 848 00 s b0 000000 E008080000006
00]
XU

KA XA LE XK IAX XXX AL XA KA XKL AX LKA

XXALXALK AXKL KA KL

EX XL KR KA KKK KAXKKAK

D004 8000000800000 800000608080 80804000¢8
XA

EX XXX KN KU A AL KL KA XX KR A KKK KKK KA KA KA A

Lo E0.0,860000 0800000004960 000850000999

99.44.6994

PO 0.0.6.6:000 806000
00NV
800
G 0.0099
000
940969088
4

PON 009 660080808000 9000000000000600009999.908069
00004
POV

S680005080008
0 450000
000
009.99 006950000
000
0604
0

DISMOUNT Command Regarding Open
Files

B.1 DISMOUNT Command
With VMS Version 5.2 and subsequent versions, the DISMOUNT command
checks for the following conditions that will prevent the dismount from
completing:
¢

Installed swap and page files

Installed images

Devices spooled to the volume

QOpen user files (any files not falling into one of the first three groups)

If none of these conditions are found, the volume is marked for dismount as

usual, and the volume changes quickly from the marked-for-dismount state to the
dismounted state. If any of these conditions exists, the DISMOUNT command
does not mark the volume for dismount, but instead displays messages indicating
that the volume cannot be dismounted, the conditions that exist, and the number
of instances of each condition. For example:
$ DISMOUNT $10$DJA100:
$DISM-W-CANNOTDMT,
$DISM-W-INSWPGFIL,

$10$DJA100: cannot be dismounted
4 swap or page files installed on volume

%DISM-W-SPOOLEDEV,

3 devices spooled to volume

$DISM-W-INSTIMAGE,
%¥DISM-W-USERFILES,

7 images installed on volume
& user files open on volume

As shown in the example, the conditions are displayed in order of decreasing
severity (severity refers to the level of difficulty you would have rectifying the
conditions).

DISMOUNT Command Regarding Open Files

B-1

The return status from the DISMOUNT command reflects the most severe
conditions. You can use this return status to construct a command procedure or
image that calls routines to handle the individual conditions. Once one condition
has been addressed, the procedure should loop back and attempt the DISMOUNT

command again to determine if other conditions exist. The symbol names and
values for the feur conditions are:
DISM$_INSWPGFIL = %X739018

DISM$_SPOOLEDEV = %X739020
DISM$_INSTIMAGE = %X739028
DISM$_USERFILES = %X739030

B.1.1

Closing Files

With VMS Version 5.2 and subsequent versions, you can address all the
conditions that prevent a volume from being dismounted if you have the
appropriate privileges.
Some knowledge of the files specific to your environment might be required to
eliminate the conditions preventing a volume from being dismounted.

First you must determine the names of the files open on the device and the

process that owns each file. Each file can then be addressed as shown in

the following sections. This information can be displayed using the following
command:
$ SHOW DEVICE/FILES ddcu:
where:

ddcu

Is the name of the device you are attempting to dismount

B.1.1.1

System-Owned Files (Process iD = 0) with the Extension SYS

The files INDEXF.SYS and QUOTA.SYS can remain open. INDEXF.SYS is
normally open on any mounted volume. QUOTA.SYS is normally open if quotas

are enabled on the volume. Neither of these open files prevents the volume from
being dismounted.
Any remaining files with the extension SYS are most likely installed secondary

swap and page files. You can verify this by examining the site-specific system

startup file SYSSMANAGER:SYPAGSWPFILES.COM and by using the DCL
command SHOW MEMORY/FILES/FULL. To cancel the installed status of these
files, use one of the following SYSGEN commands:
$ RUN SYS$SYSTEM:SYSGEN
SYSGEN> DEINSTALL filespec([/PAGEFILE]

SYSGEN> DEINSTALL filespec[/SWAPFILE]
SYSGEN> DEINSTALL/INDEX=page-file-number

B-2

DISMOUNT Command Regarding Open Files

For further information, refer to SYSGEN’s online help.

B.1.1.2 System-Owned Files (Process ID = 0) with the Extension EXE

System-owned files with the extension EXE are most likely installed images.
You should verify this by examining the installed-image list using the INSTALL
command LIST. You can then cancel the installed status of the files, as described
in the VMS Install Utility Manual.
B.1.1.3

Process-Owned Files

Process-owned files are normally closed when the processes accessing the files
finish with them. Contact the users who own the processes and ask them to
complete their work and close the files or log out. If this cannot be done, you can
force the processes to exit using the DCL command STOP PROCESS/ID=processid.

B.1.2 Spooled Devices
You can locate spooled devices using the DCL command SHOW DEVICE. The
SHOW DEVICE command displays "spooled” in the device status field if the
device is spooled. You can examine the system startup command procedure
SYS$MANAGER:SYSTARTUP_V5.COM to determine whether the device is
spooled to the volume that is being dismounted and to get the names of the
queues used by the spooled device. Once you have done this, you should first
prevent any queued files from being lost by setting the queue to retain jobs on
error, as follows:
$ SET QUEUE/RETAIN=ERROR queue-name
where:

queue-name

Is the name of the queue set to retain jobs on error.

Next, stop the queue while queuing the current job again but by placing it on
hold as follows:

$ STOP/QUEUE/REQUEUE/HOLD queue-name
where:

queue-name

Is the of the queite to be placed on hold.

The device can then be set not to be spooled:
$ SET DEVICE/NOSPOOLED device
where:

device

Is the device set not to be spooled.

DISMOUNT Command Regarding Open Files

B-3

You can now restart the queue without losing any jobs in the queue or any files
that have been spooled to the volume. If you do not want to wait until the volume
is remounted to restart the queue, you can set the device to be spooled to a
different volume and restart the queue immediately.

B.1.3 Clusterwide Support for DISMOUNT
You can use the DISMOUNT command throughout the cluster if you specify
DISMOUNT/CLUSTER. This command first checks for conditions that will
prevent the volume from dismounting on the local node. If none is found, it then
checks for such conditions on all of the other nodes in the cluster. If the command
DISMOUNT/CLUSTER finds one of the conditions on any node, it sends an error
message identifying the device and the node on which the error occurred, followed
by an error message indicating that there are open files on the volume. For
example:
$ DISMOUNT/CLUSTER $10$DJA100:
DISM-W-RMTDMTFAIL,

$105DJA100:

failed to dismount on node SALT

$DISM-W-FILESOPEN, volume has files open on remote node
$DISM~W~RMTDMIFRAIL, $10$DJAl00: failed to dismount on node PEPPER
$DISM-W-FILESOPEM,
$DISM~W-CANNOTDMT,

volume has files open on remote node
$10$DJA100: cannot be dismounted

In this example, the final return status is DISM-W- CANNOTDMT. Note that,
while this message is also displayed when one of the error conditions is found
on the local node, it acts as a return status only if the conditions are found on
a remote node. Thus, it can be used in a command procedure or an image to
distinguish the location of the error condition. The symbol and value for this
status are:
DISM$ CANNOTDMT = %X739010

B.1.4 Restoring the Previous Behavior of the DISMOUNT

Command
In some cases you might want to mark a volume for dismount even though
files are open on the volume. Marking the volume for dismount prevents users

from opening any new files, thereby allowing activity to wind down. Also,

file-system caches are flushed at the time the volume is marked for dismount,
which is especially important when the system is shutting down and the file-

system caches must be written to the disk. For these reasons, the qualifier
/OVERRIDE=CHECKS has beeen provided for the DCL command DISMOUNT to

override the new VMS Version 5.2 behavior and allow the volume to be marked
for dismount despite the fact that there are files open.

B-4

DISMOUNT Command Regarding Open Files

. If you specify the qualifier /OVERRIDE=CHECKS, the DISMOUNT command

reverts to the earlier behavior with the following exception. Informational
messages are displayed to inform you of conditions that will prevent the volume
from dismounting, immediately followed by an informational message indicating
that the volume has been marked for dismount. The final status is success with a
severity of informational (DISM$_MARKEDDMT). For example:
$ DISMOUNT/OVERRIDE=CHECKS $10$DJA100:
$DISM-I-INSWPGFIL, 2 swap or page files installed on volume
$DISM-I-SPOOLEDEV, 1 device spooled to volume

$DISM-I-~INSTIMAGE, 5 images installed on volume

. %$DISM~I-OPENFILES, 3 user files open on volume

$DISM~I~-MARKEDDMT, $105DJA100: has been marked for dismount

You can specify the equivalent of the qualifier /OVERRIDE=CHECKS when using
the $DISMOU system service by using the new DMT$M_OVR_CHECKS flag.
You should specify this flag in the flags argument to the $DISMOU system service
if you desire the behavior of previous versions of VMS.
The command procedure SYS$SYSTEM:SHUTDOWN.COM was modified in VMS
Version 5.2 to specify the /OVERRIDE=CHECKS qualifier when dismounting
volumes.

. You must dismount DIGITAL Distributed File Service (DFS) client pseudodevices
(DFSCn:) using the command DISMOUNT /OVERRIDE=CHECKS DFSCn:. For
example:

$ DISMOUNT/OVERRIDE=CHECKS DFSC1001:

The following informational message is displayed, and the device is dismounted:
%DISM~I-USERFILES,
$DISM~I-MARKEDDMT,

1 user file open on volume
DFSC1001 has been marked for dismount

DISMOUNT Command Regarding Open Files

B-5

BA 0SSP0 000t 4000600300006 000 000000¢00000006808008044

KX R XX A

XEAKEA XL XKL E X

K A

KK KX XXX

AN K LXKAXXK OO

XXX XA

K KKK

KA XA RKLKA KKK

p0.8.9.0000 0000806860056 8000.8000008800006.00.68400¢4

B9000000088860
6 0008088080000 00000 toss st
P4 0980000046000 40000000000 000080000000 8864
FA KX XA XK
PO 4SS

30000

OO0

XX XX XX

0004000300688 80880008804 040 ¢4

P 069000000 ¢4658 88880036080.8460004044
XXX XX XA KA KK XK KK AL KL LN LU NAL KK AL KKK
REEX XX KX LK AR HK KL XKAOOOOIHK XK KKK

b 09040800 880006000008604860.40¢1
P00 0008046048 00586800440084¢.4

PO 64006406608 6006090.0040¢4
p8.0.6.8.600.60968608066466444
$.0.9.0.06.65.9.060084540863454

p8.48.96806880¢005¢044
. $.60.60666099458804

$9.0.6.04.9.45.9.0.06.9.¢4
IIXXXHAXXXEXK

KXXEXXAELKA
.9:6.6.9.4.0.9.44
IXXXXXX

.0.4.0.4.4
XXX
X

XXXEX

KAUXKKY
XXAAKAXEK
XX XAKXAXXKLK
h 994,600,949 44444

. 0,8.6.9.0.4.4.06.6,04¢4
}19.0.9.6.9.6.0404.49484¢
$8.6.9.8.6.8.0684044.044444
$8.4.6.6.0.00.48644646846004

KAXXK
AKX K AKX LKA
URX
KAKKAK

09988900.00989089808.444

$500.60008008088000066940044
P oG00.0000906806000084.0400
48444

XXX
EALE KA R KKK NARK KA KL KK
AUKELAKAKLALE
KX KA KA UKL LXK A AK KK

PR E 6800004040808 640500448 0008400.47
JOO0868088008000
00 0000600044 00080¢00004
KX
POV

XK KK LR IA AL LA KA XA KK AR KK XA XA KA KA ALK

G060 0000008980800 990086000008 0066000091

KXXHIUX LR LUK LK

COD

KK AR KR KA MK KA KK

KHAE
YLLK KELU
L AR KK XA KA AL KK LA LAEA
KA LELR KKK LKL ALK

PO SV
DOV O
FOS

6004 30500899900 0006 0006048 46666484.0904404

OO0

00NN I 000060400006 00000404

G090 000000090 9.8.0.00
0000080445
60900009
8466698961
8

C
ISE Parameter Worksheets
This appendix contains several ISE worksheets that you can use and/or use to
make copies.

ISE Parameter Worksheets

C-1

Table C-1

individual ISE Worksheet

Serial Number:
NODENAME:
SYSTEMID:

ALLCLASS:
UNITNUM:

FORCEUNI:

FORCENUM:

HISPEED:

Serial Number:
NODENAME:

SYSTEMID:
ALLCLASS:

UNITNUM:

FORCEUNI:
FORCENUM:
HISPEED:

C-2

ISE Parameter Workshsets

Table C-2

individual ISE Worksheet

Serial Number:
NODENAME:

SYSTEMID:

ALLCLASS:
UNITNUM:

FORCEUNLI:
FORCENUM:
HISPEED:

Serial Number:
NODENAME:

SYSTEMID:
ALLCLASS:
UNITNUM:
FORCEUNI:
FORCENUM:
HISPEED:

ISE Parameter Worksheets

C-3

Table C-3

individual ISE Worksheet

Serial Number:

NODENAME:
SYSTEMID:

ALLCLASS:
UNITNUM:

FORCEUNTI:
FORCENUM:
HISPEED:

Serial Number:
NODENAME:
SYSTEMID:

ALLCLASS:
UNITNUM:

FORCEUNI:

FORCENUM:
HISPEED:

C~4

iSE Parameler Worksheeis

Table C~4

Individual ISE Worksheet

Serial Number:

NODENAME:
SYSTEMID:

ALLCLASS:
UNITNUM:

FORCEUNI:
FORCENUM:

HISPEED:

Serial Number:
NODENAME:
SYSTEMID:

ALLCLASS:
UNITNUM:
FORCEUNI:
FORCENUM:
HISPEED:

ISE Parameter Wortkshaets

C-5

$.2.69.8000000080086000606086000060000006080806088006¢94
p9006800.900080000000469006000696000045080469099080944
F 600900600008 808000008080080088¢06000000669060¢.4
0 $.68060000096058:9064080600869000080900006.40¢04

XX XXX XK HX KR XL XOOOOOOONCKOO
KX XX XK XXX

f.0 4606000666408 800000000008 0908080808404
P8 080000008060 60900008006080800580644004
PP 8006008800600 00000064004000460064¢04
b 4586808484066560000008064406
000440044
pe 8004000080080 500068600064060848044
PGS 056488008004648000408
46806044
P8 008080688 8840888460004044604004

P84 08906 88085000400 048084¢4
p9.0.60.6496.006.008600006.06¢¢4
p00.0.68695.03.5000060496664

6.0.6.0.0.0.0.6.0.6.0.66.600409¢4
PO9.6.6.0906.066064646464
44

$8.6.64096.6¢66.046064.4
}.0.4.9.6.6.4.9.0.4.6.6.40.44

p9.4.8.0.9.8.8.4.6.6¢41
$0.0.0.4.6.449.9¢4
AXAELALAX
§.4.4.6.0.¢44
XXHXX
X
X

X
XXX
XEXXX

XXXXAAX
XAXAKXKXKXK

P8:2.0946¢4494
KAXXALALXKXUXK
P4.8.6.4646046064944
§ 8.63464800004844
EXEXAKAUXAKXLAXXXLKKL

HKAXAXXXKXKXKXAAAKAAUKK
$ 90049906090664060699004
p9.898080606.6008 60660469644

p OO000000060050008960660¢91
PP OO0 00090006009¢04000900044
PO 600V E

4000606000088 080806¢.964

B0 00060900808604004860089066000644

P E OGSO E04000829
889005 080
049498044

$ 08000900080 8089800800804 0844600444004
KOO0

KX UA KL UE AKX MUK

KK KUK KX KAKE ALK

POOAO040006
80000466
808006
4080860060800
0
POV 0009080004
0060 080000040004
000
004

p8:8.0.9.
0880800
89.006084
0900:90000096090040
.¢08
¢646¢
FOOE

000666.06.0860.900 5800909000600 06060486053

p G 505000400008900.90.0600809909800040.6.066408904660604
bAS SO0 P 0 IO O PPV ¢S 000900000000 0800 0480680809090

Index
29-29246-00,
(12-29258-01),

2-5
14

(13-29327-01), 3-8
(50-21575-01), 2-2
(54-20404-01),

1-5

(70-26020-01),

3-2

Cable assembly (17-02353-01 revision
BO1), 2-2

Considerations for system enclosures,
3-3

(70-26020-02), 1-2, 3-2, 3-7
(17-02353-01 revision B01), 2-2
(70-27400-01 revision CO1 or later), 2-2

(70-27400-01 revision C01),

1-3

D
DIP switchpack,

3-10

DISMOUNT command, B-1to B-5
BA123-series enclosures,

1-3

BA200-series enclosure, 1-2
KFQSA (M7769, revision K04 or later),
1-2

BA200-series enclosures
KFQSA (M7769), 1-2, 3-3

BA23-series enclosures,
BA440, 1-3
bus 1 and H3604,

B-4
restoring previous behavior,

1-4

CPUs with embedded DSSI adapters,
1-2

bus 1 and H3604,

1-4

CPUs with embedded DSSI adapters,
1-2

(BC21M),

1-4

(BC21Q),

(BC22Q),

Booting,

2-5

B-2

cluster wide support,

1-4

BA441, 1-3
bus 0 and system backplane,

EXE, B-3
System-owned files with extension
SYS,

1-3

bus 0 and system backplane,

closing files, B-2 to B-3
process owned files, B-3
system-owned files with extension

spooled devices, B-3
DSSI devices no warm swapping

BA123-series enclosures,

1-3

BA200-series enclosures, 1-3
BAZ3-series enclosures, 1-3
BA440-based CPUs with embedded
DSSI adapter,

1-3

H3604 (70-27400-01 revision B0O1 and
earlier),

2-3

1-3
KA660 (M7626), 1-3
MicroVAX 3300/3400 (KA640),

KA640 (M7624),

RFxx within BA123-series,

1-3

RFxx within BA200-series,

1-3

RFxx within BA23-zeries,

2-3

1-3

index-1

DSSI devices no warm swapping (cont’d)
TFxx table top enclosures, 1-3
VAX 4000 Model 200 (KA660), 2-3
DSSI devices support warm swapping,
1-2

E
Embedded termination
KA640 (M7624), 1-4

1-2

KA660 (M7626),

BA440-based CPUs, 1-2
BA441-based CPUs, 1-2
H3604 (70-27400-01 revision CO1 or

earlier),

BA400-series,

later),

2-2

(KA670), 2-2
(KA680), 2-2
KFQSA (M7769, revision K04 or later),
1-2

TFxx within BA400-series, 1-2
DSSI enclosure power cycling, 1-6
DSSI FRUs
Q-bus option DSSI adapters, 1-2
Q-bus system CPUs,
RFxx ISEs,

1-2

TFxx ISEs,

1-2

DSSI Termination,

KFQSA (M7769, revision J06 or
1-4

H
H3604, 1-5
H3604 (70-27400-001 revision C01)
console panel, 1-2

ISEs
warm swapping,

1-2

4-1

RF-series,

TF-series,

4-5

warm swapping parameters,

1-4

4-2

warm swapping requirements,

DSSI termination connector (12-29258-01),

4-2

1-4

DssI VTERM,

BA440 bus 0,

1-5

B400X, 1-5
BA400-series enclosures,

KA640,

1-5

BA440 bus 1,

1-5
CPUs within BA440 enclosures,
KA640, 1-5
KA660, 1-5
KFQSA, 1-5
R400X, 1-5
regulator (54-20404-01),

DSSI Warm Swapping,

1-5

1-1

DUP

obtaining and recording ISE specific
parameters,

4-5 to 4-12

2-3
KA640 (M7624),
KA660, 2-3
KA660 (M7626;,
KA670, 2-2

1-3
1-3

KA680, 2-2
KFQSA
without S-box front handle
(07-26020-02), 1-3

KFQSA (M7769, revision K04 or later),
1-2

BAZ00-series enclosure,

1-2

removal and installation procedures,
3-3

KFQSA revisions no warm swapping

(M7769, revision J06 or earlier), 3-3
KFQSA support warm swapping
(M17769, revision K04 and later), 3-2
S-box front handle (70-26020-02), 3-2

Index-2

KFQSAs (M7769, revision K04 and later)
BA200-series, 3-3

Removal and installation procedures for
ISEs (cont’d)
enclosures, 4-14
finding failed ISEs, 4-14

BA400-series, 3-3

installing repaired or replaced ISEs,
4-17

(M7493),

Removal and replacement of CPUs,
multisystem DSSI configuration,

1-5

(M7624), 1-3,1-4
(M7626), 1-3, 1-4
(M7769, revision K04 or later),

(Ma715),

1-2

1-5

o)
Obtaining and recordirgz CPU specific
parameters,

Removal and replacement of KFQSAs,
3-7
DIP switchpack, 3-10
SIP packages (13-29327-01), 3-8
Restoring CPU specific parameters, 2-5
booting, 2-5
Restoring the ISE specific parameters,
4-17 to 4-22

2-4

Obtaining and recording ISE specific
parameters,

no parameter reprogramming,
parameter reprogramming,

4-5 to 4-14

using DUP, 4-5 to 4-12
using VMS, 4-12 to 4-14

Restoring the KFQSA’s configuration

3-4

configuration table, 3-4
CSR addresses, 3-4
CSR settings using console command
CONFIGURE, 3-6
Q-bus addresses,

4-22

4-18 to

4-22

Obtaining and recording KFQSA specific
parameters,

2-5
2-3

table, 3-10
RFxx ISEs, 1-2

S
S-box (70-26020-02) front handle,

1-2

S-box front handle (70-26020-01), 3-2
S-box front handle 70-26020-02, 3-2

3-4

S-box handle (70-26020-02),
SFXX, 1-2

Printed circuit module combination

Shutting down VMS system software,

(50-21575-01),

2-2

24, 3-3
SIP packages (13-29327-01),
SIP packages (13-38234-01),

Q
Q-bus option DSSI adapters,

Q-bus system CPUs,

1-2

3-7

3-8
3-8

Storage System Port (SSP) controller,
34

1-2
T

R
Removal and Installation Procedures

KFQSA (M7769, revision K04 or later),

TF857, 1-2
TFxx ISEs, 1-2

3-3

Removal and installation procedures for

ISEs,

4-14 to 4-17

dismounting and removing,

4-15

Index-3

non-DSSI MicroVAX II (KA630),
non-DSSI MicroVAX 3500/3600

vV
VAX 4000 Model 300,

1-4

VMS
obtaining and recording ISE specific
parameters,

4-12 to 4-14

(KA650), 2-1
non-DSSI MicroVAX 3800/3900

(KA655),

2-1

Warm swapping ISEs,
parameters,

requirements,

W
Warm swapping CPUs,

Index-4

2-1

4-1

4-2

RF-series, 4-4
TF-series, 4-5
Warm swapping requirements,

1-6

2-1