MajenkoProjects/decdoctex
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Moved paper details to individual docs

Browse Source
This commit is contained in:
Matt Jenkins
2026-02-15 23:21:34 +00:00
parent ee1c433368
commit 7d3d933d5f
15 changed files with 759 additions and 195 deletions
Download Patch File Download Diff File Expand all files Collapse all files

BIN
EK-RF71D-IM-001.pdf
View File

Binary file not shown.

541
EK-RF71D-IM-001.tex
View File

@@ -1,4 +1,5 @@
\documentclass{decsectionalv2}
\usepackage[paperheight=228mm,paperwidth=174mm,inner=1.0in,outer=1.0in,top=0.4in,bottom=0.5in,headheight=15pt,headsep=3em,includeheadfoot,footskip=0em]{geometry}
\product{RF71 Integrated Storage Element}
\title{Installation Manual}
\ordernumber{EK-RF71D-IM-001}
@@ -88,7 +89,8 @@ EK-RF71D-IM-001.tex(NR03/W3) Order Processing Section
\pagestyle{main}
\chapter{General Information}
This chapter describes the RF71 integrated storage element (ISE) and the
\setcounter{page}{1}
This chapter describes the RF71 integrated storage element\Index{Integrated storage element} (ISE) and the
enclosures into which it can be installed.
All installations should be documented using LARS. The correct system
@@ -105,7 +107,7 @@ embedded within it an intelligent controller and Mass Storage Control
Protocol (MSCP) server.
DSSI devices support up to seven ISEs daisy chained through a single
cable to an adapter in the host. DSSI adapters can be adapters embedded
cable to an adapter in the host. DSSI adapters\Index{DSSI adapters} can be adapters embedded
within a CPU module (for example the KA640 module) or non-embedded
modules, such as the KFQSA adapter.
@@ -113,7 +115,7 @@ modules, such as the KFQSA adapter.
\section{The BA213 Enclosure}
The BA213 enclosure (\figref{1-2}) has a mass storage bay above the card
The BA213\Index{BA213} enclosure (\figref{1-2}) has a mass storage bay above the card
cage that contains either a TK70 tape drive or a TK50 tape drive, and up
to three DSSI ISEs.
@@ -126,9 +128,11 @@ shock-mounting hardware is different for each ISE model that can be
installed.
\fig{RF71-BA213-IMAGE}{The BA213 Enclosure}
\newpage
\section{The BA215 Enclosure}
EK-RF71D-IM-001.tex
The BA215 enclosure (\figref{1-3}) has a mass storage bay that extends
The BA215\Index{BA215} enclosure (\figref{1-3}) has a mass storage bay that extends
across the top of the enclosure. It contains a TK70 tape drive or TK50
tape drive, and either one or two ISEs.
@@ -140,10 +144,11 @@ enclosed in rubber shock bushings. The shock-mounting hardware is different
for each ISE model that can be installed.
\fig{RF71-BA215-IMAGE}{The BA215 Enclosure}
\newpage
\section{The R215F Enclosure}
The RF215F enclosure is a BA215 enclosure with the card cage removed
The R215F\Index{R215F enclosure} enclosure is a BA215 enclosure with the card cage removed
and an additional mass storage bay. It has three mass storage bays: two
bays in the top of the cabinet, and a third bay in the misdle of the cabinet.
Each mass storage bay can hold one 13.3 cm (5.25-inch) ISE. \figref{1-4} is
@@ -160,6 +165,7 @@ for each ISE model installed.
\fig{RF71-R215F-IMAGE}{R215F Configuration (Example)}
\chapter{Unpacking Information}
\setcounter{page}{1}
Unpacking the RF71 ISE consists of removing it from the shipping
container and inspecting for damage. Report any damage to the shipper
@@ -185,6 +191,8 @@ possible future use.}
\fig{RF71-RF71E-SF}{RF71E-SF Option Kit}
\newpage
\section{Inspection}
\begin{enumerate}
@@ -209,6 +217,7 @@ EK-RF71D-UG & 1 & RF30{/}RF71 ISE User Guide \\
\end{tbl}
\chapter{Controls and Indicators}
\setcounter{page}{1}
This chapter describes the controls and indicators for the RF71 ISE.
@@ -216,12 +225,12 @@ This chapter describes the controls and indicators for the RF71 ISE.
\figref{3-1} shows the location of the switches and LEDs on the RF71 ISE.
\fig{RF71-SWITCHES}{RF71 ISE Switch and LED Locations}
\fig[0.8]{RF71-SWITCHES}{RF71 ISE Switch and LED Locations}
\newpage
\subsection{DSSI Node ID Select Switches}
The RF71 ISE had a DIP switchpack located next to the DSSI connector
that is used to assign a DSSI node IDE number to the ISE. Each device on
that is used to assign a DSSI node ID number\Index{DSSI node ID number} to the ISE. Each device on
the DSSI bus must be assigned a unique node IDE between zero and seven.
Assignment of the DSSI node ID is made during installation by setting
@@ -246,26 +255,27 @@ number (see \tabref{3-1}).
\end{tbl}
\note{These switches are ignored by the RF71 ISE when it is connected to an operator control
panel (OCP). In this case, use the OCP controls described in \hyperlink{section.3.9}{Section 3.9}
panel. In this case, use the OCP controls described in \hyperlink{section.3.9}{Section 3.9}
to select the DSSI node ID.}
\subsection{READY Indicator}
This indicator is a green LED. When the ISE is powered up, this indicator is turned on. After successful
completion of the power-on self-test (POST), the indicator is turned off until the ISE is read/write ready.
\newpage
The READY LED is turned off during a seek until the drive heads are on a cylinder
and read/write ready. Then the indicator is turned on again for as long as the heads remain
on track. Thus, during read or write operations, the indicator flickers on and off rapidly.
\subsection{FAULT Indicator}
\Index{FAULT indicator}
This indicator is a red LED. It is turned on when a read/write error or serious physical
error condition is detected. Initially, when the ISE is powered up, this indicator
is turned on. Upon successful completion of POST, this indicator is turned off.
\section{Operator Control Panel (OCP)}
\Index{Operator control panel}
When the RF71 ISE is installed in a BA213, BA215 or R215F enclosure,
the operator interfave is a control panel on the enclosure. \figref{3-2}
shows the OCP. Its functions are described in \tabref{3-2}. Each RF-series
@@ -329,6 +339,7 @@ Restart & Pressed & Reinitialises system state.
\chapter{Installation Procedure}
\setcounter{page}{1}
This chapter explains how to install the RF71 ISE into a BA200 Series enclosure.
@@ -358,7 +369,7 @@ cover (\figref{4-2}). Open the door as follows:
\begin{enumerate}
\item Insert the key into the lock on the front door. Turn the key to the
bottom position (fully clockwise).
\newpage
\item Slide the window all the way down.
\item Turn the \keystroke{1 0} power switch off (to the right) and unpluf the ac power
@@ -385,10 +396,10 @@ as this may damage the latch.}
\end{enumerate}
\fig{RF71-BA213-ACCESS}{Removing the Media Faceplate and OCP}
\newpage
\subsection{Installing the Mass Storage Shock Mounts}
Install the upper and lower shock mounts in the mass storage bay
Install the upper and lower shock mounts\Index{shock mounts} in the mass storage bay
using the following procedure:
\caution{Make sure to install the shock mounts shipped with the option
@@ -422,7 +433,7 @@ may be damaged.}
\end{enumerate}
\fig{RF71-SHOCK-INSTALL}{Attaching the Metal Ground Strip}
\newpage
\subsection{Installing the ISE Into the Enclosure}
\caution{The RF71 ISE is susceptible to electrostatic damage. Do not
@@ -481,7 +492,7 @@ Remove the front panel as follows:
\end{enumerate}
\caution{Do not use a screwdriver or other tool to pry open the release
latch as this may damage the latch.}
\newpage
\subsection{Gaining Access to the Top Mass Storage Bays}
\caution{Static electricity can damage integrated circuits. Use an
antitstatic wrist strap and mat when performing this procedure.}
@@ -521,6 +532,13 @@ Use the static-protective Field Service kit (PN 29-26246).}
\caution{Make sure you install the shock mounts shipped with the devices.
Check the part number agains \tabref{2-1}. Installing the wrong
shock mounts may result in damage to the ISE.}
\newpage
\begin{enumerate}[resume]
\item Install the slide rails using the four screws provided (see \figref{4-5})
\end{enumerate}
\caution{Make sure you use the screws provided. Longer screws may
damage the ISE.}
\begin{enumerate}[resume]
\item Slide the ISE into the mass storage bay (drive module to the left) and
@@ -538,7 +556,7 @@ shock mounts may result in damage to the ISE.}
\end{enumerate}
\fig{RF71-CONNECTOR-LOCS}{DSSI Bus, Power, and OCP Connectors}
\newpage
\section{The R215F Enclosure}
The R215F expansion enclosure holds up to three RF21 ISEs.
@@ -574,8 +592,8 @@ expansion cable to prevent high error rates.}
\end{enumerate}
\caution{Do not use a screwdriver or other tool to pry open the release
latch as this may damage the latch.}
\subsection{Gaining access to the Top Mass Storage Bays}
\newpage
\subsection{Gaining Access to the Top Mass Storage Bays}
\caution{Static electricity can damage integrated circuits. Use an antistatic
wrist strap and mat when performing this procedure.}
@@ -588,6 +606,7 @@ wrist strap and mat when performing this procedure.}
\end{enumerate}
\fig{RF71-B215F-SCREWS}{Removing the Top Media Faceplate}
\newpage
\begin{enumerate}[resume]
\item The shipping brackets inside the mass storage area(s) should already
@@ -610,7 +629,7 @@ Loosen the four captive screws that hold the bottom media faceplaye to
the R215F frame and remove the faceplate (\figref{4-9}).
\fig{RF71-R215F-LOWER}{Removing the Bottom Media Faceplate}
\newpage
\subsection{Installing the RF71 ISE}
\caution{The RF71 ISE is susceptible to electrostatic damage. Do not
@@ -652,6 +671,7 @@ damage the ISE.}
\end{enumerate}
\chapter{Verification}
\setcounter{page}{1}
This chapter explains how to verify the correct operation of the ISE once it is installed.
@@ -672,7 +692,7 @@ This chapter explains how to verify the correct operation of the ISE once it is
\hyperlink{chapter.6}{Chapter 6}. Make sure the green LED in the
center of the READY button on the OCP comes on for that ISE. If the red
FAULT LED comes on, test the ISE.
\newpage
\item Once the READY LED lights, access the local program DRVTST using
the following procedure:
@@ -721,20 +741,21 @@ control to the system, press \keystroke{CTRL/C} or \keystroke{CTRL/Y}.}
\end{enumerate}
\chapter{Diagnostics}
\setcounter{page}{1}
This chapter describes the diagnostics available for verifying the operation
of the RF71 ISE.
\section{Power-On Self-Test (POST)}
All DSSI devices run a power-on self-test (POST) at power-up or when
All DSSI devices run a power-on self-test (POST)\Index{Power-on self-test (POST)} at power-up or when
the device is reset to check the integrity of the device hardware. POST
has two functions: it performs a sequence of tests to check that the ISE
hardware is functioning properly, and it performs start-up procedures to
make the ISE operational before becoming available to the host.
POST is executed whenever power is applied. If it is executed successfully,
the green READY indicator lights and the red FAULT indicator goes out.
the green READY indicator\Index{READY indicator} lights and the red FAULT indicator goes out.
If POST fails, the red FAULT indicator remains lit and the READY
indicator does not come on, or both indicators remain on.
@@ -744,7 +765,7 @@ spindle to come up to speed. Other tests are performed while the spindle
is spinning up. When there is more than one ISE on the system, spindle
spin-up is staggered to limit the starting current drawn from the power
supply for this function. The system controls the staggering through the
ACOK signal.
ACOK\Index{ACOK} signal.
POST is also used to handle the following types of error conditions:
@@ -755,7 +776,7 @@ POST is also used to handle the following types of error conditions:
controller can't establish a logical connection to the host.
The result of a failure due to controller error is that the
red FAULT LED lights.
\newpage
\item \textit{Device errors} - These are errors caused by the hardware
associated with the device control function of the drive
module. These errors are not fatal, since the ISE can establish
@@ -797,10 +818,10 @@ Local programs can be accessed by using console commands (for MicroVAX
HOST/DUP command. Once the connection is established, operations are
performed under the control of the local program. When the program
terminates, control is returned to the system.
\newpage
\subsection{DIRECT}
DIRECT provides a directory of all available local programs resident in
DIRECT\Index{DIRECT} provides a directory of all available local programs resident in
the RF71 ISE. An example of a DIRECT program display is:
\begin{ttfig*}
@@ -816,7 +837,7 @@ the RF71 ISE. An example of a DIRECT program display is:
\subsection{DRVTST}
DRVTST invokes a comprehensive test of the RF71 ISE hardware. Errors
DRVTST\Index{DRVTST} invokes a comprehensive test of the RF71 ISE hardware. Errors
detected by this program are isolated to the FRU level. Dialogue for this
test includes:
@@ -845,7 +866,7 @@ chapter.} \\
Answering no to the first question results in a read-only test, and
DRVTST writes are limited to a diagnostic area on the disk. Answering
yes to the first question results in the second question being asked.
\newpage
Answering no to the second question has the same effect as answering no
to the first question. Answering yes to the second question permits write
and read operations anywhere on the medium.
@@ -862,6 +883,464 @@ saves the counters again. It computes the uncorrectable error rate and
byte (symbol) error rate. If either rate is too high, the test fails and the
appropriate error code is displayed.
\howtoorder
\end{document}
\subsection{DRVEXR}
The DRVEXR\Index{DRVEXR} local program exercises the RF71 ISE. The test is data
transfer intensive and indicates the overall integrity of the device. The
dialogue for DRVEXR includes:
\begin{tbl}{}{p{1cm} l}
\textbf{Message Type} & \textbf{Message} \\
\hline
I & Copyright \copy 1988 Digital Equipment Corporation \\
Q & Write/read anywhere on the medium? [1=yes/(0=no)] \\
Q & User data will be corrupted. Proceed? [1=yes/(0=no)] \\
Q & Test time in minutes? [(10)-100] \\
I & ddd minutes to complete. \\
I & dddddddd blocks (512 bytes) transferred. \\
I & dddddddd bytes in error (soft). \\
I & dddddddd uncorrectable ECC errors (recoverable). \\
T & Complete \\
\multicolumn{2}{c}{or} \\
FE & Unit is currently in use.\textsuperscript{1}\\
\end{tbl}
\textsuperscript{1}This can mean either the device is inoperative, is in use by a host, or is currently running another local program.
\newpage
\begin{tbl}{}{p{1cm} l}
\textbf{Message Type} & \textbf{Message} \\
\hline
FE & Operation aborted by user. \\
FE & xxxx - Unit diagnostics failed.\textsuperscript{2}\\
FE & xxxx - Unit read/write test failed.\textsuperscript{2}\\
\hline
\multicolumn{2}{p{10cm}}{\textsuperscript{2}For the available error codes, refer to the diagnostic error code table at the end of this chapter.}\\
\end{tbl}
Answering no to the first question results in a read-only test, and
DRVEXR writes are limited to a diagnostic area on the disk. Answering
yes to the first question results in the second question being asked.
Answering no to the second question has the same effect as answering no
to the first question. Answering yes to the second question permits write
and read operations anywhere on the medium.
\note{If the WRITE PROTECT switch on the OCP is pressed in (LED on)
and the answer to the second question is yes, the device does not
allow the test to run. The error message ``2008 - Unit read/write
test failed'' is displayed. In this case, the test has not failed, but
has been prevented from running.}
DRVEXR saves the error counters and then calls the timed I/O routine.
After the timed I/O routine completes, DRVEXR saves the counters again.
It then reports the total number of blocks transferred, bytes in error, and
uncorrectable errors.
DRVEXR uses the same timed I/O routine as DRVTST with two
exceptions. First, DRVTST always uses a fixed time of five minutes, while
DRVEXR varies the time of the routine as the user specifies. Second,
DRVTST determines whether the device is good or bad. DRVEXR simply
reports the data without making any judgements about the condition of
the device.
\newpage
\subsection{HISTRY}
This local program displays information about the history of the RF71
ISE. The output generated by HISTRY\Index{HISTRY} consists of the following:
\begin{tbl}{}{p{1cm} l l}
\textbf{Message Type} & \textbf{Field Length\textsuperscript{1}} & \textbf{Field Meaning} \\
\hline
I & 47 & Copyright notice \\
I & 4 & Product name \\
I & 12 & Drive serial number \\
I & 6 & Node name \\
I & 1 & Allocation class \\
I & 8 & Firmware revision level \\
I & 17 & Hardware revision level \\
I & 6 & Power-on hours \\
I & 5 & Power cycles \\
I\textsuperscript{2} & 4 & Hexadecimal fault code \\
T & & Complete. \\
\hline
\multicolumn{3}{p{10cm}}{\textsuperscript{1}Number of ASCII characters}\\
\multicolumn{3}{p{10cm}}{\textsuperscript{2}This displays the last 11 fault codes as Information messages. For available error codes, refer to the diagnostic error code table at the end of this chapter.}\\
\end{tbl}
\newpage
The following is an example of what appears on the screen when HISTRY
is running:
\begin{verbatim}
Copyright © 1988 Digital Equipment Corporation
RF71
RM01062
SUSAN
0
RFX V101
RF71 PCB-5/ECO-00
617
21
A04F
A04F
A103
A04F
A404
A04F
A404
A04F
A404
A04F
A404
Complete.
\end{verbatim}
If no errors have been logged, no hexadecimal fault codes are displayed.
\newpage
\subsection{ERASE}
The ERASE\Index{ERASE} local program is used to overwrite application data on the
device disks while leaving the replacement control table (RCT)\Index{Replacement control table (RCT)} intact.
This local program is used in the event that a mechanics set must be
replaced and the customer wants to protect confidential or sensitive data.
ERASE should be used only in the event that the mechanics set must be
replaced and only after you have backed up the customer's data.
The dialogue for this program is as follows:
\begin{tbl}{}{p{1cm} l}
\textbf{Message Type} & \textbf{Message} \\
\hline
I & Copyright \copy 1988 Digital Equipment Corporation \\
Q & Write/read anywhere on the medium? [1=yes/(0=no)] \\
Q & User data will be corrupted. Proceed? [1=yes/(0=no)] \\
I & 6 minutes to complete. \\
T & Complete \\
\multicolumn{2}{c}{or} \\
FE & Unit is currently in use. \\
FE & Operation aborted by user. \\
FE & xxxx - Unit diagnostics failed. \textsuperscript{1} \\
FE & xxxx - Operation failed. \textsuperscript{2} \\
\hline
\multicolumn{2}{p{10cm}}{\textsuperscript{1}For the available error codes, refer to the diagnostic error code table at the end of this chapter.} \\
\multicolumn{2}{p{10cm}}{\textsuperscript{2}xxxx = one of the following error codes:
\begin{itemize}
\item 000D : cannot write the RCT
\item 000E : cannot read the RCT
\item 000F : cannot find an RBN to revector to
\item 0010 : the RAM copy of the bad block table is full
\end{itemize}
}\\
\end{tbl}
\note{If the WRITE PROTECT switch on the OCP is pressed in (LED
on) and the answer to the second question is yes, the device does
not allow the test to run. The error message ``Operation aborted
by user'' is displayed. In this case, the test has not failed, but has
been prevented from running.}
If a failure is detected, the message indicating the fa;lure is followed by
one or more messages containing error codes.
\newpage
\section{Diagnostic Error Codes}
The diagnostic error codes\Index{Error codes} are displayed when running either DRVTST,
DRVEXR, or PARAMS. The following table lists the error codes that may
be displayed when running these local programs.
\begin{tbl}{}{l p{7cm}}
\textbf{Code} & \textbf{Meaning} \\
\hline
3000H - 3009H & Firmware bugcheck, replace the drive module or contact
Field Service support. \\
300AH & Replace the drive module. \\
300BH & Replace the drive module first, then if necessary the
mechanics set. \\
300CH & Replace the drive module. \\
300DH & Replace the drive module first, then if necessary the
meehanies set. \\
3300H - 3301H & Firmware bugcheck, replace the drive module or contact
Field Service support. \\
3302H - 3303H & Replace the mechanics set. \\
3304H & Write/read test failed. Replace the module. \\
330AH & Firmware bugcheck, replace the drive module or contact
Field Service support. \\
330BH & Replace the drive module. \\
3400H - 3D04H & Firmware bugcheck, replace the drive module or contact
Field Service support. \\
9001H - 9161H & Replace the drive module. \\
9162H & Replace the mechanics set. \\
9200H - 9604H & Replace the drive module. \\
9314H\textsuperscript{1} & Replace the drive module first, then if necessary the OCP. \\
9606H - 9608H & Replace the drive module first, then if necessary the
mechanics set. \\
9801H - A031H & Replace the drive module. \\
\end{tbl}
\textsuperscript{1}Front panel is broken. Could be either the module or the OCP or both.
\newpage
\begin{tbl}{}{l p{7cm}}
\textbf{Code} & \textbf{Meaning} \\
\hline
A032H\textsuperscript{2} & Replace the drive module first, then if necessary the
mechanics set. \\
A033H - A0039H & Replace the drive module. \\
A03AH\textsuperscript{3} & Replace the drive module or check the system power
supply. \\
A03BH - A04FH & Replace the drive module. \\
A100H - BF0SH & Firmware bugcheck, replace the drive module or contact
Field Service support. \\
\hline
\multicolumn{2}{p{10cm}}{\textsuperscript{2}FLT bit of the spindle control status register was asserted for one of the following reasons.
\begin{enumerate}
\item Reference clock not present
\item Stuck rotor
\item Bad connection between HDA and module
\end{enumerate}}\\
\multicolumn{2}{p{10cm}}{\textsuperscript{3}Cannot spin up, ACLOW is set in WrtFlt. Did not see ACOK signal which is supplied by the host system power supply for staggered spin-up.}\\
\end{tbl}
\chapter{The PARAMS Utility}
\setcounter{page}{1}
PARAMS is a local program that allows you to examine and edit internal
ISE parameters.
\section{Invoking PARAMS}
PARAMS is invoked in the same way as the local programs discussed in
the previous chapter. Once invoked, all interaction is through the use
of commands and responses. Valid PARAMS commands\Index{PARAMS commands} are listed in
\tabref{7-1}.
\begin{tbl}{Valid PARAMS Commands}{l p{7cm}}
\textbf{Command} & \textbf{Definition} \\
\hline
HELP & Shows all PARAMS commands and their syntax \\
SET & Sets a parameter to a value \\
SHOW & Displays a parameter or a class of parameters \\
STATUS & Displays module configuration, history, or current counters,
depending on the status type chosen \\
WRITE & Records the device parameters you changed using the SET
command \\
EXIT & Terminates the PARAMS local program \\
\end{tbl}
\newpage
\section{HELP}
The HELP\Index{HELP} command causes a brief list of available PARAMS commands
to be displayed. The following is an example of what appears on the
screen when you use the HELP command.
\begin{verbatim}
PARAMS> help
EXIT
HELP
SET {parameter | .} value
SHOW {parameter | . | /class}
/ALL /CONST /DRIVE
/SERVO /SCS /MSCP
/DUP
STATUS [type]
CONFIG LOGS DATALINK
PATHS
WRITE
PARAMS>
\end{verbatim}
\section{SET}
The SET\Index{SET} command is used to edit internal ISE parameters. Syntax for
the SET command is:
\begin{quote}
SET \textit{parameter} \textit{value}
\end{quote}
Where \textit{parameter} is the name of the parameter to be set,
and \textit{value} is the value you want assigned to the parameter.
If abbreviated, the first matching parameter is used without regard
to uniqueness.
The WRITE command must be used to record the edits made while using
the SET command. SET parameters that are available to the user are
listed in \tabref{7-2}.
Examples:
\begin{verbatim}
PARAMS> SET NODENAME SUSAN
\end{verbatim}
This sets the node name of the ISE to SUSAN.
\newpage
\begin{verbatim}
PARAMS> SET FORCENAM 1
\end{verbatim}
This sets the node name of an RF71 with a DSSI node ID of 0 to RF30A.
\begin{tbl}{Summary of SET and SHOW User Parameters}{l l p{6cm}}
\textbf{Parameter} & \textbf{Class} & \textbf{Definition} \\
\hline
VOLSERNO & DRIVE & Shows the volume serial number as a quadword. \\
ALLCLASS & MSCP & Sets or shows the controller allocation class. The
allocation class should be set to match that of the host.\\
UNITNUM & MSCP & Sets or shows the MSCP unit number.\\
FORCEUNI & MSCP & Determines whether the MSCP unit number or the
DSSI node ID will be used. If the FORCEUNI value is
0, the UNITNUM value will be used. If the FORCEUNI
value is 1, the DSSI node ID will be used. \\
FIVEDIME & MSCP & Determines credit connections. If set to 1, MSCP will
support five connections with ten credits each. If set
to 0, MSCP will support seven connections with seven
credits each. \\
CNT\_TMO & MSCP & Shows the MSCP controller timeout value.\\
ADD\_CR & DUP & Determines if DUP will append a RETURN character
after each message. True if set to 1, false if set to 0.\\
ADD\_LF & DUP & Determines if DUP will append a LINEFEED character
after each message. True if set to 1, false if set to 0.\\
SYSTEMID & SCS & Sets or shows the controller's 48-bit SCS system ID.\\
NODENAME & SCS & Sets or shows the SCS node name for the ISE.\\
FORCENAM & SCS & Determines whether the value set by the NODENAME
command will be used or not. If the FORCENAM
value is 1, the SCS node name should be forced to the
string RF30x or RF71x, where x is a letter from A to
H corresponding to the DSSI bus ID (for example, A=0,
B=1, and so on) If the FORCENAM value is 0, the value
set by NODENAME is used.\\
\end{tbl}
\newpage
\section{SHOW}
The SHOW\Index{SHOW} command displays the settings of a parameter or a class of
parameters. The full name of the parameter (8 characters or less), the
current value, the default value, radix and type, and any flags associated
with each parameter are displayed.
Syntax for the SHOW command is:
\begin{quote}
SHOW \textit{parameter\_or\_class}
\end{quote}
Where \textit{parameter\_or\_class} is either a parameter name or a class name.
If an abbreviation is used, the first matching parameter is displayed,
regardless of uniqueness. The parameter name may also be the special
character ``.'', which will display the last known parameter. If there is no
previous parameter, an error is given.
If a class name is used, the class name must be prefixed with a slash (/).
SHOW parameters that are available to the user are listed in tabref{7-2}.
Example:
\begin{verbatim}
PARAMS> SHOW ADD_CR
Parameter Current Default Type Radix
-------- --------------- --------------- ------- -----
ADD_CR 0 0 Boolean 0/1
PARAMS> SET ADD_CR 1
PARAMS> SHOW ADD_CR
Parameter Current Default Type Radix
-------- --------------- --------------- ------- -----
ADD_CR 1 0 Boolean 0/1
PARAMS>
\end{verbatim}
\newpage
\section{STATUS}
The STATUS\Index{STATUS} command can display module configuration, history, or
current counters. The syntax for the STATUS command is:
\begin{quote}
STATUS [\textit{type}]
\end{quote}
Where \textit{type} is an option that denotes the type of display desired. If
omitted, all available status information is displayed. If present, it may
be abbreviated.
\tabref{7-3} shows the types that are available to the user.
\begin{tbl}{Types Available to the STATUS Command}{l p{10cm}}
\textbf{Type} & \textbf{Definition} \\
\hline
CONFIG & Displays the module name, node name, power-on hours, power
cycles, and unit failures. \\
LOGS & Displays the last eleven machine and bugchecks on the module.
Included in the display are the processor registers (D0-D7, A0-A7),
the time and date of each failure (if available, otherwise the
date 17 November 1858 is displayed), and some of the hardware
registers. \\
DATALINK & Displays the data link counters. \\
PATHS & Displays available path information (open virtual circuits) from
the point of view of the controller. The information displayed
includes the remote node names, DSSI IDs, software type and
version, and counters for the messages/datagrams sent and/or
recieved. \\
\end{tbl}
Example:
\begin{verbatim}
PARAMS> STAT CONF
Configuration:
Node R39JNA is an RF71 controller
Software RFX V102 built on 1-NOV-1988 13:39:09
Electronics module name is EN0O00245
In 41 power-on hours, power has cycled 1 times
System time is 12-NOV-1988 15:00:12
PARAMS>
\end{verbatim}
\newpage
\section{WRITE}
This command is used to record the changes you have made using
PARAMS back to nonvolatile memory. The WRITE\Index{WRITE} command is similar in
nature to the VMS SYSGEN WRITE command. There are no parameters
available. The syntax is simply WRITE at the PARAMS> prompt.
However, when using the WRITE command you must be aware of the
system and/or ISE requirements and use the command accordingly or it
may not succeed in writing the changes.
The WRITE command may fail for one of the following reasons:
\begin{itemize}
\item The user altered a parameter that required the unit, and the unit
cannot be acquired (for example, it's not in the available state with
respect to the host). Changing the unit number is an example of a
parameter that requires the unit.
\item The user altered a parameter that required a controller initialization,
and the user replied negatively to the request for reboot. Changing
the node name or the allocation class are examples of parameters that
require controller initialization.
\item Initial drive calibrations were in progress on the unit. The use of the
WRITE command is inhibited while these calibrations are running.
\end{itemize}
\section{EXIT}
The EXIT\Index{EXIT} command terminates the PARAMS local program. The text
``Exiting...'' appears on the screen.
The EXIT command is executed by typing either EXIT or \keystroke{CTRL/Z}.
\newpage
\printindex[MyIndex]
\end{document}

BIN
EK-VAXAA-4P-001.pdf
View File

Binary file not shown.

1
EK-VAXAA-4P-001.tex
View File

@@ -1,4 +1,5 @@
\documentclass{dec}
\usepackage[a5paper,inner=0.8in,outer=0.5in,top=0.8in,bottom=0.8in]{geometry}
\product{VAXstation 2000}
\title{Hardware Option Guide for the 4-Plane Graphics Coprocessor}
\ordernumber{EK-VAXAA-4P-001}

242
EK-VSTAA-MG-001-ch2.tex
View File

@@ -50,6 +50,7 @@ and monitor (VR260) connected to the video port. The keyboard inputs
commands at 4800 baud and the monitor displays output from the video
circuits.
\Index{Baud Rate!Console Device}
The console device for a MicroVAX 2000 system is the terminal (VT220 or
similar terminal) connected to connector 1 on the DEC423 converter. The
terminal operates at 9600 baud.
@@ -71,6 +72,7 @@ following methods.
\item HALT button -- Press the halt button. It is located next to the printer port
on the back of the system box. The \console prompt is displayed when
ready for console commands.
\Index{BCC08 Cable}
\item BREAK key -- Press the BREAK key on the diagnostic console device
that is connected to the printer port with the BCC08 cable. The \console
prompt is displayed when ready for console commands.
@@ -79,10 +81,10 @@ The system automatically halts the CPU for the following reasons.
\begin{itemize}
\item After power-up testing -- If the default recovery action is halt, the system
automatically halts the CPU and enters console mode after power-up
tests are complete. See Section 2.5.4 for information on setting the
tests are complete. See \para{2.5.4} for information on setting the
default recovery actions.
\item For a boot failure -- If the system fails to boot properly, the system
automatically halts the CPU and enters console mode. See Section 2.5.2
automatically halts the CPU and enters console mode. See \para{2.5.2}
for information on setting the default boot device.
\item On a system error -- If the CPU detects a severe corruption of its
operating environment, it halts and reads the default recovery action in the
@@ -150,6 +152,8 @@ to start the operating system software.
There is a diagnostic console device available on the VAXstation 2000. The
MicroVAX 2000 can use this device if the DEC423 Converter is removed.
\Index{Baud Rate!Diagnostic Console}
\Index{BCC08 Cable}
The diagnostic console device can be utilized by connecting a terminal (such
as the VT100 or VT220) to the printer port with the special BCC08 cable.
The terminal operates at 9600 baud. Field service technicians can use this
@@ -356,6 +360,7 @@ numbers. \figref{2-5} shows an example of running self-test successfully on
the disk controller.
\begin{ttfig}{Example of Running Self-test on the Disk Controller}
>>> TEST 7
7...
>>>
@@ -371,9 +376,14 @@ pick and choose which devices to test between C and 4, all tests between
C and 4 are tested when entered as a group.
\begin{ttfig}{Example of Running a Series of Self-tests}
>>> TEST C 4
C...B...A...9...8...7...6...5...4_..
>>>
\end{ttfig}
To test all devices, enter TEST F 1. The MicroVAX 2000 skips over the
@@ -382,23 +392,24 @@ MONO video test (TEST F) since it does not use the video circuits.
\begin{tbl}{Self-test Commands}{c X}
\raggedright\textbf{Test\newline Number} & \textbf{Device\newline Tested} \\
\hline
1 & Option module (Network Interconnect module) (NI) \\[0.5em]
2 & Option module (not available) \\[0.5em]
3 & Option module (not available) \\[0.5em]
4 & Option module (not available) \\[0.5em]
5 & Interrupt Controller and ThinWire Ethernet ID ROM (SYS) \\[0.5em]
6 & Tape Controller. (TPC) \\[0.5em]
7 & Disk conroller. (HDC) \\[0.5em]
8 & Interval timer. (IT) \\[0.5em]
9 & Floating point unit. (FP) \\[0.5em]
A & Memory management unit. (MM) \\[0.5em]
B & Memory. (MEM) \\[0.5em]
C & DZ Controller. (DZ) \\[0.5em]
D & Non-volatile RAM. (NVR) \\[0.5em]
E & Time-of-year dock. (CLK) \\[0.5em]
F & Base video (MONO) (VAXstation 2000 only) \\[0.5em]
1 & Option module (Network Interconnect module) (NI) \\
2 & Option module (not available) \\
3 & Option module (not available) \\
4 & Option module (not available) \\
5 & Interrupt Controller and ThinWire Ethernet ID ROM (SYS) \\
6 & Tape Controller. (TPC) \\
7 & Disk conroller. (HDC) \\
8 & Interval timer. (IT) \\
9 & Floating point unit. (FP) \\
A & Memory management unit. (MM) \\
B & Memory. (MEM) \\
C & DZ Controller. (DZ) \\
D & Non-volatile RAM. (NVR) \\
E & Time-of-year dock. (CLK) \\
F & Base video (MONO) (VAXstation 2000 only) \\
\end{tbl}
\newpage
\subsubsection{Self-test with Loopback Connectors}
Customer mode self-test does not test the drivers or the lines of the serial
@@ -958,6 +969,7 @@ you replace one of the disks to fix an error code and the error still exists,'
replace the system module. If the system module does not fix the problem
replace the disk interface module.
\newpage
\subsubsection{System Exerciser}
Start the system exerciser by entering TEST 0 for customer mode or install
@@ -1282,7 +1294,7 @@ as described below.
and \tabref{2-10} lists the system exerciser error codes for the tape drives error
line.
\begin{tbl}{TPC Tape Controller System Exerciser Error Codes}{l X X}
\begin{tbl}{TPC Tape Controller System Exerciser Error Codes}{l p{0.25\textwidth} X}
\textbf{Error Codes} & \textbf{Possible Cause} & \textbf{Corrective Action}\\
\hline
@@ -1800,22 +1812,22 @@ module is faultly according to the last digit in the second 8-digit number.
\textbf{Error Codes} & \textbf{System Module} & \textbf{Option Module} \\
\hline
0 & & \\[0.5em]
1 & X & \\[0.5em]
2 & X & \\[0.5em]
3 & X & \\[0.5em]
4 & & X \\[0.5em]
5 & X & X \\[0.5em]
6 & X & X \\[0.5em]
7 & X & X \\[0.5em]
8 & & X \\[0.5em]
9 & X & X \\[0.5em]
A & X & X \\[0.5em]
B & X & X \\[0.5em]
C & & X \\[0.5em]
D & X & X \\[0.5em]
E & X & X \\[0.5em]
F & X & X \\[0.5em]
0 & & \\
1 & X & \\
2 & X & \\
3 & X & \\
4 & & X \\
5 & X & X \\
6 & X & X \\
7 & X & X \\
8 & & X \\
9 & X & X \\
A & X & X \\
B & X & X \\
C & & X \\
D & X & X \\
E & X & X \\
F & X & X \\
\end{tbl}
\newpage
@@ -2030,27 +2042,27 @@ shown in \figref{2-32} and enter the sum into NVR (TEST 52).
\textbf{Flag} & \textbf{Definition}\\
\hline
00000008 & RPB\$V\_BBLOCK -- This skips the files-11 boot and performs only the boot block type boot. \\[0.5em]
00000008 & RPB\$V\_BBLOCK -- This skips the files-11 boot and performs only the boot block type boot. \\
00000010 & RPB\$V\_DIAG -- Diagnostic boot. Secondary bootstrap is image called [SYSMAINT]DIAGBOOT.EXE. \\[0.5em]
00000010 & RPB\$V\_DIAG -- Diagnostic boot. Secondary bootstrap is image called [SYSMAINT]DIAGBOOT.EXE. \\
00000020 & RPB\$V\_BOOBPT -- Bootstrap breakpolnt. Stops the primary and secondary bootstraps with a breakpoint instruction before testing memory. \\[0.5em]
00000020 & RPB\$V\_BOOBPT -- Bootstrap breakpolnt. Stops the primary and secondary bootstraps with a breakpoint instruction before testing memory. \\
00000040 & RPB\$V\_HEADER -- Image header. Takes the transfer address of the secondary bootstrap image
from that file's image header. If RPB\$V\_HEADER is not set, transfers control to the first byte of the secondary boot file. \\[0.5em]
from that file's image header. If RPB\$V\_HEADER is not set, transfers control to the first byte of the secondary boot file. \\
00000100 & RPB\$V\_SOLICT -- File name. Prompt for the name of a secondary bootstrap file. \\[0.5em]
00000100 & RPB\$V\_SOLICT -- File name. Prompt for the name of a secondary bootstrap file. \\
\end{tbl}
\begin{tblcont}{Boot Flags Used by VMB for Booting All Operatlng System Software}{l X}
\textbf{Flag} & \textbf{Definition}\\
\hline
00000200 & RPB\$V\_HALT -- Halt before transfer. Executes a halt instruction before transferring control to the secondary bootstrap. \\[0.5em]
00000200 & RPB\$V\_HALT -- Halt before transfer. Executes a halt instruction before transferring control to the secondary bootstrap. \\
00001000 & RPB\$V\_PFILE -- (overlays RPB\$V\_USEMPM) File name. Prompt for the name of the parameters file on a network bootstrap operation. \\[0.5em]
00001000 & RPB\$V\_PFILE -- (overlays RPB\$V\_USEMPM) File name. Prompt for the name of the parameters file on a network bootstrap operation. \\
X0000000 & RPB\$V\_TOPSYS -- The X position specifies the top level directory number for system disks with multiple systems.\\[0.5em]
X0000000 & RPB\$V\_TOPSYS -- The X position specifies the top level directory number for system disks with multiple systems.\\
\end{tblcont}
\begin{tbl}{Specific Boot Flags Used by VMS}{l X}
@@ -2060,36 +2072,36 @@ X0000000 & RPB\$V\_TOPSYS -- The X position specifies the top level directory nu
00000001 & RPB\$V\_CONV -- Conversational boot. At various points in the system
boot procedure, the bootstrap code solicits parameters and other input
from the console terminal. If the DIAG is also on, the diagnostic supervisor
then enters "MENU" mode and prompts the user for devices to test. \\[0.5em]
then enters "MENU" mode and prompts the user for devices to test. \\
00000002 & RPB\$V\_DEBUG -- Debug. If this flag is set, VMS maps the code for the
XDELTA debugger into the system page tables of the running system. \\[0.5em]
XDELTA debugger into the system page tables of the running system. \\
00000004 & RPB\$V\_INIBPT -- Initial breakpoint. If RPB\$V\_DEBUG is set, VMS executes
a BPT instruction immediately after enabling mapping. \\[0.5em]
a BPT instruction immediately after enabling mapping. \\
00000080 & RPB\$V\_NOTEST -- Memory test inhibit. Sets a bit in the PFN bit map
for each page of memory present. Does not test the memory. \\[0.5em]
for each page of memory present. Does not test the memory. \\
00000400 & RPB\$V\_NOPFND -- No PFN deletion (not implemented; intended to tell
VMB not to read a file from the boot device that identifies bad or reserved
memory pages, so that VMB does not mark these pages as valid in the PFN
bitmap). \\[0.5em]
bitmap). \\
00000800 & RPB\$V\_MPM -- Specifies that multiport memory is to be used for the
total exec memory requirement. No local memory is to be used. This
is for tightly-coupled multiprocessing. If the DIAG is also on, then the
diagnostic supervisor enters "AUTOTEST" mode. \\[0.5em]
diagnostic supervisor enters "AUTOTEST" mode. \\
00002000 & RPB\$V\_MEMTEST -- Specifies that a more extensive algorithm be used
when testing main memory for hardware uncorrectable (RDS) errors. \\[0.5em]
when testing main memory for hardware uncorrectable (RDS) errors. \\
00004000 & RPB\$V\_FINDMEM — Requests use of MA780 memory if MS780 is insufficient
for booting. Used for 11/782 installations. \\[0.5em]
for booting. Used for 11/782 installations. \\
00008000 & RPB\$V\_AUTOTEST - Used by diagnostic supervisor. \\[0.5em]
00008000 & RPB\$V\_AUTOTEST - Used by diagnostic supervisor. \\
00010000 & RPB\$V\_CRDTEST — Request pages with CRD errors to be removed from bitmap. \\[0.5em]
00010000 & RPB\$V\_CRDTEST — Request pages with CRD errors to be removed from bitmap. \\
\end{tbl}
\newpage
@@ -2109,9 +2121,9 @@ lists the recovery flags available.
\textbf{Number} & \textbf{Recovery Action Flag}\\
\hline
1 & RESTART \\[0.5em]
2 & BOOT \\[0.5em]
3 & HALT \\[0.5em]
1 & RESTART \\
2 & BOOT \\
3 & HALT \\
\end{tbl}
To change the NVR recovery action flag, enter TEST 53. \figref{2-33} shows
@@ -2136,7 +2148,7 @@ setup procedures.
\newpage
\subsection{Circle Cross-Hatch Alignment Pattern}
\Index{Alignment Pattern!Circle Cross-hatch}
This utility is only available on the VAXstation 2000. This utility sends the
circle cross-hatch alignment pattern to the monitor connected to the video
port. Enter TEST 60 to display the circle cross-hatch alignment pattern. A
@@ -2144,12 +2156,14 @@ loopback (p/n 29-24795) must be attached to the 25-pin communication port
to run this utility. Hit the carriage return to stop the display.
\subsection{Screen of E's Pattern}
\Index{Alignment Pattern!Screen of E's}
This utility is only available on the VAXstation 2000. This utility sends a full
screen of E's to the monitor connected to the video port. Enter TEST 61 to
display the screen of E's pattern. Hit the carriage return to stop the display.
\subsection{White Screen}
\Index{Alignment Pattern!White Screen}
This utility is only available on the VAXstation 2000. This utility sends a full
white screen to the monitor connected to the video port. Enter TEST 62 to
@@ -2297,44 +2311,44 @@ an explanation for each.
\textbf{Formatter Message} & \textbf{Explanation}\\
\hline
VSfmt\_STS\_ChkPss & A check pass is being done on the disk. \\[0.5em]
VSfmt\_STS\_ChkPss & A check pass is being done on the disk. \\
VSfmt\_STS\_CkRXfmt & The RX33 diskette format is being checked. \\[0.5em]
VSfmt\_STS\_CkRXfmt & The RX33 diskette format is being checked. \\
VSfmt\_STS\_EntUIB & The formatter has sized an unknown disk and will
prompt you to input information about the disk. \\[0.5em]
prompt you to input information about the disk. \\
VSfmt\_STS\_FMTing & The disk is being formatted. \\[0.5em]
VSfmt\_STS\_FMTing & The disk is being formatted. \\
VSfmt\_STS\_RdMbb & The manufacturer's bad block is being located. \\[0.5em]
VSfmt\_STS\_RdMbb & The manufacturer's bad block is being located. \\
VSfmt\_STS\_RXfmt & The RX33 diskette is being formatted. \\[0.5em]
VSfmt\_STS\_RXfmt & The RX33 diskette is being formatted. \\
VSfmt\_STS\_Siz & The hard disk selected is being sized. \\[0.5em]
VSfmt\_STS\_Siz & The hard disk selected is being sized. \\
VSfmt\_QUE\_RUsure (DUA\# 1/0) ? & The formatter uses this question as a safety check.
If you want to format the disk or diskette that is
indicated by the \#, enter 1 for yes. Otherwise,
enter any character other than 1 to abort the formatter. \\[0.5em]
enter any character other than 1 to abort the formatter. \\
VSfmt\_QUE\_SerNbr (0-999999999) ? & Enter a number for the hard disk you are
formatting. The number can be any number from
0 to 999999999. This number should be the serial
number of the drive, but does not have to be. You
can enter a 0 for DUA0 and a 1 for DUA1, but any
number will do. \\[0.5em]
number will do. \\
VSfmt\_QUE\_unitno (0-2) ? & Enter the drive that needs formatting. Enter 0 for
DUA0, 1 for DUA1, and 2 for DUA2. Any other
character aborts the formatier. \\[0.5em]
character aborts the formatier. \\
VSfmt\_RES\_Succ & The disk has been successfully formatted. \\[0.5em]
VSfmt\_RES\_Succ & The disk has been successfully formatted. \\
VSfmt\_RES\_Abtd & The RDRX formatter has been aborted. \\[0.5em]
VSfmt\_RES\_Abtd & The RDRX formatter has been aborted. \\
VSfmt\_RES\_ERR \# & The formatter has been stopped because of the error
code indicated by the \#. \tabref{2-18} lists the
error codes. \\[0.5em]
error codes. \\
\end{tbl}
@@ -2342,17 +2356,17 @@ VSfmt\_RES\_ERR \# & The formatter has been stopped because of the error
\textbf{Code} & \textbf{Description}\\
\hline
1 & Illegal unit number entered. \\[0.5em]
1 & Illegal unit number entered. \\
2 & Error occurred during the RD autosizer. Either a disk is not a Digital disk or the disk is bad. \\[0.5em]
2 & Error occurred during the RD autosizer. Either a disk is not a Digital disk or the disk is bad. \\
3 & Error occurred during formatting. \\[0.5em]
3 & Error occurred during formatting. \\
4 & Error occurred during the hard disk check pass. \\[0.5em]
4 & Error occurred during the hard disk check pass. \\
5 & Error occurred during the floppy disk check pass. \\[0.5em]
5 & Error occurred during the floppy disk check pass. \\
6 & No diskette loaded in the floppy drive or the diskette is not RX33 media. \\[0.5em]
6 & No diskette loaded in the floppy drive or the diskette is not RX33 media. \\
\end{tbl}
@@ -2404,34 +2418,34 @@ an explanation for each.
\hline
VSmsv\_STS\_NBBcnt & The verifier lists the new bad block count since
the last time the disk was formatted. \\[0.5em]
the last time the disk was formatted. \\
VSmsv\_STS\_NBBpo3 & The verifier lists the new bad block locations if
any new bad blocks are found. It lists the cylinder
number, surface, and the sector. \\[0.5em]
number, surface, and the sector. \\
VSmsv\_STS\_OBBcnt & The verifier lists the old bad block count. \\[0.5em]
VSmsv\_STS\_OBBcnt & The verifier lists the old bad block count. \\
VSmsv\_STS\_RDing & The verifier is reading the disk. \\[0.5em]
VSmsv\_STS\_RDing & The verifier is reading the disk. \\
VSmsv\_STS\_Siz & The hard disk selected is being sized. \\[0.5em]
VSmsv\_STS\_Siz & The hard disk selected is being sized. \\
VSmsv\_QUE\_RUsure (DUA\# 1/0) ? & The verifier uses this question as a safety check.
If you want to verify the disk indicated by the \#,
enter 1 for yes. Otherwise, enter any character
other than 1 to abort the verifier. \\[0.5em]
other than 1 to abort the verifier. \\
VSmsv\_QUE\_unitno (0-1) ? & Enter the drive that you are verifying. Enter 0
for DUA0 or a 1 for DUA1. Any other character
aborts the verifier. \\[0.5em]
aborts the verifier. \\
VSmsv\_RES\_Succ & The disk has been successfully verified. \\[0.5em]
VSmsv\_RES\_Succ & The disk has been successfully verified. \\
VSmsv\_RES\_Abtd & The RD verifier has been aborted. \\[0.5em]
VSmsv\_RES\_Abtd & The RD verifier has been aborted. \\
VSmsv\_RES\_ERR \# & The verifier has been stopped because of the error
code indicated by the \#. \tabref{2-20} lists the error
codes. \\[0.5em]
codes. \\
\end{tbl}
@@ -2439,11 +2453,11 @@ VSmsv\_RES\_ERR \# & The verifier has been stopped because of the error
\textbf{Code} & \textbf{Description} \\
\hline
1 & Illegal unit number entered. \\[0.5em]
1 & Illegal unit number entered. \\
2 & Error occurred during the RD autosizer. The disk may not be formatted. \\[0.5em]
2 & Error occurred during the RD autosizer. The disk may not be formatted. \\
3 & Error reading the revectored block control table (RCT) \\[0.5em]
3 & Error reading the revectored block control table (RCT) \\
\end{tbl}
@@ -2564,30 +2578,30 @@ s_miss - 0 s_raerr - 0
\textbf{Item} & \textbf{Definition}\\
\hline
req\$\_num & System ID request response sent \\[0.5em]
sysid\$\_cnt & Unsolicited system ID's sent \\[0.5em]
tx\$\_cnt & Packeis transmitted \\[0.5em]
rx\$\_cnt & Packets received \\[0.5em]
mxcst\$\_cnt & Multicast or broadcast packets received \\[0.5em]
jnk\$\_pkts & Packets received with bad format \\[0.5em]
r\_err & Total receive errors detected by lance \\[0.5em]
r\_fram & Receive framing error \\[0.5em]
r\_oflo & Receive FIFO overflow error \\[0.5em]
r\_crc & Receive crc error \\[0.5em]
r\_buff & Receive buffer in chain not available error \\[0.5em]
t\_err & Total transmit errors detected by lance \\[0.5em]
t\_more & Transmits with more than one collision \\[0.5em]
t\_one & Transmits with one collision \\[0.5em]
t\_def & Transmits deferred \\[0.5em]
t\_buff & Transmit buffer not available error \\[0.5em]
t\_uflo & Transmit FIFO underflow error \\[0.5em]
t\_lcol & Transmits with late collision error \\[0.5em]
t\_lcar & Transmit loss of carrier error \\[0.5em]
t\_rtry & Transmit maximum retry error \\[0.5em]
hng\$\_tx & Transmit failed to complete error \\[0.5em]
s\_err & Total errors reported in CSR0 of lance \\[0.5em]
s\_babl & Babble error \\[0.5em]
s\_cerr & Collision check (heartbeat) error \\[0.5em]
s\_miss & Missed packet, no buffer available \\[0.5em]
s\_merr & DMA memory access or memory parity error \\[0.5em]
req\$\_num & System ID request response sent \\
sysid\$\_cnt & Unsolicited system ID's sent \\
tx\$\_cnt & Packeis transmitted \\
rx\$\_cnt & Packets received \\
mxcst\$\_cnt & Multicast or broadcast packets received \\
jnk\$\_pkts & Packets received with bad format \\
r\_err & Total receive errors detected by lance \\
r\_fram & Receive framing error \\
r\_oflo & Receive FIFO overflow error \\
r\_crc & Receive crc error \\
r\_buff & Receive buffer in chain not available error \\
t\_err & Total transmit errors detected by lance \\
t\_more & Transmits with more than one collision \\
t\_one & Transmits with one collision \\
t\_def & Transmits deferred \\
t\_buff & Transmit buffer not available error \\
t\_uflo & Transmit FIFO underflow error \\
t\_lcol & Transmits with late collision error \\
t\_lcar & Transmit loss of carrier error \\
t\_rtry & Transmit maximum retry error \\
hng\$\_tx & Transmit failed to complete error \\
s\_err & Total errors reported in CSR0 of lance \\
s\_babl & Babble error \\
s\_cerr & Collision check (heartbeat) error \\
s\_miss & Missed packet, no buffer available \\
s\_merr & DMA memory access or memory parity error \\
\end{tbl}

70
EK-VSTAA-MG-001-ch3.tex
View File

@@ -12,20 +12,20 @@ the procedures to replace the FRU.
\textbf{FRU} & \textbf{Section} & \textbf{Page} \\
\hline
Battery pack & \npara{3.10} & 3-33 \\[0.5em]
DEC423 Converter (MicroVAX 2000 only) & \npara{3.15.1} & 3-53 \\[0.5em]
Expansion adapter & \npara{3.16} & 3-54 \\[0.5em]
Expansion adapter disk interface module & \npara{3.16.1} & 3-56 \\[0.5em]
Hard disk expansion box & \npara{3.17.1} & 3-58 \\[0.5em]
Keyboard (VAXstation 2000 only) & \npara{3.13} & 3-51 \\[0.5em]
Memory module & \npara{3.5} & 3-17 \\[0.5em]
Mouse (VAXstation 2000 only) & \npara{3.14} & 3-52 \\[0.5em]
Network interconnect module & \npara{3.6} & 3-18 \\[0.5em]
Power supply in hard disk expansion box & \npara{3.17.1.2} & 3-66 \\[0.5em]
Power supply in system box & \npara{3.11} & 3-64 \\[0.5em]
Power supply in tape drive expansion box & \npara{3.17.2.3} & 3-79 \\[0.5em]
RD32 disk drive & \npara{3.8} & 3-24 \\[0.5em]
RD32 disk drive device electronics board & \npara{3.8.1} & 3-27 \\[0.5em]
Battery pack & \npara{3.10} & 3-33 \\
DEC423 Converter (MicroVAX 2000 only) & \npara{3.15.1} & 3-53 \\
Expansion adapter & \npara{3.16} & 3-54 \\
Expansion adapter disk interface module & \npara{3.16.1} & 3-56 \\
Hard disk expansion box & \npara{3.17.1} & 3-58 \\
Keyboard (VAXstation 2000 only) & \npara{3.13} & 3-51 \\
Memory module & \npara{3.5} & 3-17 \\
Mouse (VAXstation 2000 only) & \npara{3.14} & 3-52 \\
Network interconnect module & \npara{3.6} & 3-18 \\
Power supply in hard disk expansion box & \npara{3.17.1.2} & 3-66 \\
Power supply in system box & \npara{3.11} & 3-64 \\
Power supply in tape drive expansion box & \npara{3.17.2.3} & 3-79 \\
RD32 disk drive & \npara{3.8} & 3-24 \\
RD32 disk drive device electronics board & \npara{3.8.1} & 3-27 \\
\end{tbl}
@@ -33,26 +33,26 @@ RD32 disk drive device electronics board & \npara{3.8.1} & 3-27 \\[0.5em]
\textbf{FRU} & \textbf{Section} & \textbf{Page} \\
\hline
RD53 disk drive & \npara{3.7} & 3-19 \\[0.5em]
RD53 disk drive device electronics board & \npara{3.7.1} & 3-21 \\[0.5em]
RD53 disk drive in hard disk expansion box & \npara{3.17.1.1} & 3-60 \\[0.5em]
Resistor load board in hard disk expansion box & \npara{3.17.1.3} & 3-70 \\[0.5em]
Resistor load board in system box & \npara{3.9} & 3-31 \\[0.5em]
Resistor load board in tape drive expnnsion box & \npara{3.17.2.4} & 3-81 \\[0.5em]
RX33 floppy disk drive & \npara{3.8} & 3-24 \\[0.5em]
System module & \npara{3.4} & 3-13 \\[0.5em]
Tablet (VAXstation 2000 only) & \npara{3.14} & 3-52 \\[0.5em]
Tape drive expansion box & \npara{3.17.2} & 3-72 \\[0.5em]
Terminal disconnection from MicroVAX 2000 & \npara{3.15} & 3-53 \\[0.5em]
TK50 tape drive in tape drive expansion box & \npara{3.17.2.2} & 3-76 \\[0.5em]
TZK50 Controller board in tape drive expansion box & \npara{3.17.2.1} & 3-73 \\[0.5em]
VR260 deflection board & \npara{3.12.2} & 3-39 \\[0.5em]
VR260 monochrome monitor & \npara{3.12} & 3-35 \\[0.5em]
VR260 power LED & \npara{3.12.7} & 3-50 \\[0.5em]
VR260 rear bulkhead assembly & \npara{3.12.3} & 3-42 \\[0.5em]
VR260 transformer assembly & \npara{3.12.5} & 3-45 \\[0.5em]
VR260 video board & \npara{3.12.4} & 3-44 \\[0.5em]
VR260 tube/yoke/bezel assembly & \npara{3.12.6} & 3-47 \\[0.5em]
RD53 disk drive & \npara{3.7} & 3-19 \\
RD53 disk drive device electronics board & \npara{3.7.1} & 3-21 \\
RD53 disk drive in hard disk expansion box & \npara{3.17.1.1} & 3-60 \\
Resistor load board in hard disk expansion box & \npara{3.17.1.3} & 3-70 \\
Resistor load board in system box & \npara{3.9} & 3-31 \\
Resistor load board in tape drive expnnsion box & \npara{3.17.2.4} & 3-81 \\
RX33 floppy disk drive & \npara{3.8} & 3-24 \\
System module & \npara{3.4} & 3-13 \\
Tablet (VAXstation 2000 only) & \npara{3.14} & 3-52 \\
Tape drive expansion box & \npara{3.17.2} & 3-72 \\
Terminal disconnection from MicroVAX 2000 & \npara{3.15} & 3-53 \\
TK50 tape drive in tape drive expansion box & \npara{3.17.2.2} & 3-76 \\
TZK50 Controller board in tape drive expansion box & \npara{3.17.2.1} & 3-73 \\
VR260 deflection board & \npara{3.12.2} & 3-39 \\
VR260 monochrome monitor & \npara{3.12} & 3-35 \\
VR260 power LED & \npara{3.12.7} & 3-50 \\
VR260 rear bulkhead assembly & \npara{3.12.3} & 3-42 \\
VR260 transformer assembly & \npara{3.12.5} & 3-45 \\
VR260 video board & \npara{3.12.4} & 3-44 \\
VR260 tube/yoke/bezel assembly & \npara{3.12.6} & 3-47 \\
\end{tblcont}
\newpage
@@ -271,7 +271,7 @@ an entire RD53 disk drive.
the connectors or cables, and tilt the board up and back until it rests
against the outer frame.
\caution{Flexible cirant material is fragile and requires careful handling to
\caution{Flexible circuit material is fragile and requires careful handling to
avoid damage.}
\fig{SHR-0134-85}{RD53 Device Electronics Board Removal}

BIN
EK-VSTAA-MG-001.pdf
View File

Binary file not shown.

15
EK-VSTAA-MG-001.tex
View File

@@ -1,4 +1,5 @@
\documentclass{decsectional}
\usepackage[a5paper,inner=0.8in,outer=0.5in,top=0.8in,bottom=0.8in]{geometry}
\product{VAXstation 2000 and MicroVAX 2000}
\title{Maintenance Guide}
\ordernumber{EK-VSTAA-MG-001}
@@ -8,11 +9,25 @@
\pubyear{1987}
\titlepicture{titles/EK-VSTAA-MG-001}
\renewcommand\seename{See}
\renewcommand\see[2]{\par\hspace*{1em}\seename #1}
\makeatletter
\newcommand{\Index}[1]{\imki@wrindexentry{MyIndex}{#1}{\thechapter-\thepage}}
\makeatother
\makeindex[name=MyIndex, columns=2, title=Index, options= -s dec_2column.ist]
\begin{document}
\Index{Battery Testing|see{Troubleshooting, NVR}}
\input{EK-VSTAA-MG-001-preamble}
\input{EK-VSTAA-MG-001-ch1}
\input{EK-VSTAA-MG-001-ch2}
\input{EK-VSTAA-MG-001-ch3}
\input{EK-VSTAA-MG-001-ch4}
\printindex[MyIndex]
\end{document}

9
Makefile
View File

@@ -1,4 +1,4 @@
SOURCES=README.tex EK-VAXAA-4P-001.tex EK-VSTAA-MG-001.tex
SOURCES=README.tex EK-VAXAA-4P-001.tex EK-VSTAA-MG-001.tex EK-RF71D-IM-001.tex
@@ -10,14 +10,17 @@ all: ${PDFS} README.md
watch:
ls *.tex *.cls | entr -c -s 'make'
ls *.tex *.cls *.ist | entr -c -s 'make'
README.md: README.tex
pandoc -s README.tex -o README.md
.SECONDEXPANSION:
%.pdf: %.tex $$(wildcard %-*.tex) dec.cls decsectional.cls
%.pdf: %.tex $$(wildcard %-*.tex) dec.cls decsectional.cls dec_2column.ist decsectionalv2.cls decv2.cls
pdflatex ${basename $@ .pdf} < /dev/null
pdflatex ${basename $@ .pdf} < /dev/null
clean:
rm -rf *.toc *.ilg *.idx *.aux *.lof *.log *.out *.lot *.ind

BIN
README.pdf
View File

Binary file not shown.

26
dec.cls
View File

@@ -3,10 +3,10 @@
\usepackage{ragged2e}
\LoadClass[9pt,twoside]{extbook}
\usepackage[T1]{fontenc}
\usepackage[a5paper,inner=0.8in,outer=0.5in,top=0.8in,bottom=0.8in]{geometry}
\usepackage{fancyhdr}
\usepackage[none]{hyphenat}
\usepackage{array}
\usepackage{mfirstuc}
\usepackage{palatino}
\usepackage{graphicx}
\usepackage{titlesec}
@@ -26,6 +26,9 @@
\usepackage{xparse}
\usepackage{xstring}
\usepackage{rotating}
\usepackage{imakeidx}
\newcommand{\tablesize}{\fontsize{7.5}{7.5}\selectfont}
\setlist{nosep}
@@ -44,7 +47,7 @@
}
\raggedbottom
\renewcommand{\arraystretch}{1.3}
\renewcommand{\arraystretch}{1.6}
\DeclareCaptionFormat{default}{\raggedright\fontfamily{phv}\selectfont\textbf{#1#2#3}\par}
@@ -183,7 +186,7 @@
DELNI & Q-bus & VMS \\
DEMPR & Rainbow & VT \\
DEQNA & RSTS & Work Processor \\
DESTA & RSX & \\
DESTA & RSX & \\Reverse the procedure in Paragraph 3.12.1.
DEUAN & RT & \raisebox{-0.35\height}{\includegraphics[height=10pt]{logos/digital}} \textsuperscript{TM} \\
\end{tabular}
@@ -237,7 +240,7 @@ required to take measures to correct the interference.
\newcommand{\sfig}[3][1.0]{\begin{sideways}
\begin{minipage}{#1\textheight}
\begin{figure}[H]
\begin{figure}[H]Reverse the procedure in Paragraph 3.12.1.
\caption{#3}
\begin{center}
%\makebox[\textwidth][c]{%
@@ -341,6 +344,12 @@ required to take measures to correct the interference.
\end{figure}
}
\newenvironment{ttfig*}{%
\VerbatimEnvironment
\begin{Verbatim}
}{%
\end{Verbatim}
}
@@ -351,7 +360,7 @@ required to take measures to correct the interference.
\captionsetup{font=Large}
\caption{#1}
}
\small
\tablesize
\begin{tabularx}{\textwidth}{#2}
\hline
\BODY
@@ -368,7 +377,7 @@ required to take measures to correct the interference.
\captionsetup{font=Large}
\caption{#1}
}
\small
\tablesize
\begin{tabularx}{\textwidth}{#2}
\hline
\BODY
@@ -381,8 +390,9 @@ required to take measures to correct the interference.
\newcommand{\figref}[1]{\hyperref[figure:#1]{Figure #1}}
\newcommand{\tabref}[1]{\hyperref[table:#1]{Table #1}}
\newcommand{\caution}[1]{{\fontfamily{phv}\selectfont\textbf{CAUTION:}}\hspace*{1em}\textit{#1}}
\newcommand{\note}[1]{{\fontfamily{phv}\selectfont\textbf{NOTE:}}\hspace*{1em}\textit{#1}}
\newcommand{\warning}[1]{\par\vspace{1em}{\fontfamily{phv}\selectfont\textbf{WARNING:}}\hspace*{1em}\textit{#1}\vspace{1em}}
\newcommand{\caution}[1]{\par\vspace{1em}{\fontfamily{phv}\selectfont\textbf{CAUTION:}}\hspace*{1em}\textit{#1}\vspace{1em}}
\newcommand{\note}[1]{\par\vspace{1em}{\fontfamily{phv}\selectfont\textbf{NOTE:}}\hspace*{1em}\textit{#1}\vspace{1em}}
\newcommand{\para}[1]{%
\StrCount{#1}{.}[\@s]%

10
dec_2column.ist Normal file
View File

@@ -0,0 +1,10 @@
headings_flag 1
heading_prefix "\n{\\Large\\fontfamily{phv}\\selectfont\\bfseries%
\\noindent\\textbf{"heading_suffix "}}\\par\\nopagebreak\n\\hspace{0.2em}\\hrule\n\\hspace{0.2em}\n"
item_0 "\n \\item \\small "
delim_0 " \\hfill "
delim_1 " \\hfill "
delim_2 " \\hfill "

4
decsectional.cls
View File

@@ -99,7 +99,7 @@ DIBOL & Rainbow & \\
\captionsetup{font=Large}
\caption{#1}
}
\small
\tablesize
\begin{tabularx}{\textwidth}{#2}
\hline
\BODY
@@ -116,7 +116,7 @@ DIBOL & Rainbow & \\
\captionsetup{font=Large}
\caption[]{#1}
}
\small
\tablesize
\begin{tabularx}{\textwidth}{#2}
\hline
\BODY

16
decsectionalv2.cls
View File

@@ -4,8 +4,8 @@
\setcounter{secnumdepth}{5}
\titleformat{\chapter}[display]{\raggedleft\fontfamily{phv}\selectfont\bfseries\Large}{\huge \thechapter}{-0.5em}{}[\hrule]
\titlespacing{\chapter}{0pc}{0pc}{0pc}
\titleformat{\chapter}[display]{\raggedleft\fontfamily{phv}\selectfont\bfseries\huge}{\Huge \thechapter}{-0.5em}{}[\hrule]
\titlespacing{\chapter}{0pc}{10em}{2em}
\titleformat{\section}{\raggedright\fontfamily{phv}\selectfont\bfseries\huge}{\thesection \hspace{1em}}{0.0em}{}[]
@@ -128,3 +128,15 @@ DIBOL & Rainbow & \\
\renewcommand{\figlabel}{\thechapter-\arabic{figure}}
\renewcommand{\tbllabel}{\thechapter-\arabic{table}}
\fancypagestyle{preface} {
\fancyhf{}
\fancyhead[LE]{\small\fontfamily{phv}\selectfont \textbf{\thepage}}
\fancyhead[RO]{\small\fontfamily{phv}\selectfont \textbf{\thepage}}
}
\fancypagestyle{main} {
\fancyhf{}
\fancyhead[LE]{\small\fontfamily{phv}\selectfont \textbf{\thechapter-\thepage} \hspace{1em} \Chaptername}
\fancyhead[RO]{\small\fontfamily{phv}\selectfont \Chaptername \hspace{1em} \textbf{\thechapter-\thepage}}
}

20
decv2.cls
View File

@@ -2,6 +2,7 @@
\ProvidesClass{decv2}[2025/03/24 Digital Equipment Corporation]
\LoadClass{dec}
\renewcommand{\warning}[1]{\par\vspace{1em}{\fontfamily{phv}\selectfont\textbf{WARNING}\\}\textbf{#1}\vspace{1em}}
\renewcommand{\caution}[1]{\par\vspace{1em}{\fontfamily{phv}\selectfont\textbf{CAUTION}\\}\textbf{#1}\vspace{1em}}
@@ -25,3 +26,22 @@
\label{figure:\figlabel}
}
\renewcommand{\maketitle}{
\pagenumbering{roman}
\raggedright
\thispagestyle{empty}
\vspace*{10em}
{\fontfamily{phv}\selectfont
\Huge
\textbf{\@product}\\
\textbf{\@title}\par
\vspace{20pt}
\large
Order Number \@ordernumber\par
\vspace{30em}
\textbf{\@author}\\
\textbf{\@address}
}
\newpage
\boilerplate
}