Digital PDFs

AH-F406B-MC

June 1980

16 pages

Original

5.8MB

view download

OCR Version

7.2MB

view download

Document:	CZKMPB0 DPM50 DIS DIAG MON JUN 1980 bw
Order Number:	AH-F406B-MC
Revision:	000
Pages:	16
Original Filename:	CZKMPB0__DPM50__DIS_DIAG_MON__AH-F406B-MC__JUN_1980_gray.pdf

OCR Text

DP30

82K PBO

AH-F406B - MC

FICHE 1 OF - 1

o 1580

COPYRIGHTE

MADE IN USA

78,80

ART
ANRN
it
guaduEl

IDENTIFICATION
PRODUCT CODE:

AC-F405B-MC

PRODUCT NAME:

CZKMPBO DIS DIAG MON

DAiE:

JANUARY 1979

REVISED:

APRIL 1980

MAINTAINER:

MDC DIAGNOSTIC GROUP

AUTHOR:

JOHN CROLL

REVISED BY:

PATRICK N. MCKEE

SEQ 0001

REVISION HISTORY:
APRIL 1980
UPDATED TO DESCRIBE COMMUNICATIONS MODE,
ROM IDENTIFICATION OPTION AND APPENDIX A
WHICH COVERS DIS OPTIONS WITH THE NAMES OF
THE RESPECTIVE DIAGNOSTICS.
' THE

INFORMATION IN THIS DOCUMENT

IS SUBJECT TO CHANGE WITHOUT NOTICE

. AND SHOULD NOT BE CONSTRUED AS A COMMITMENT BY DIGITAL EQUIPMENT
. CORPORATION.

DIGITAL EQUIPMENT CORPORATION ASSUMES NO RESPONSIBILITY

¢ FOR ANY ERRORS THAT MAY APPLAR

IN THIS DOCUMENT.

THE SOFTWARE DESCRIBED IN THIS DOCUMENT 1S FURNISHED UNDER A LICENSE
A?gezgg ONLY BE USED OR COPIED IN ACCORDANCE WITH THE TERMS OF SUCH
L

DIGITAL EQUIPMENT CORPORATION ASSUMES NO RESPONSIBILITY FOR THE USE OR

»S?t%?glLlTV OF

ITS SOFTWARE ON EQUIPMENT

THAT

IS NOT

SUPPLIED BY

(C)

1978,1980 BY DIGITAL EQUIPMENT CORPORATION

SEQ 0002
TABLE OF

1.0

ABSTRACT

2.0

REQUIREMENTS
2.1

Environment - Hardware Requirements

2.2

Environment - Software Requirements
2.2.1

RSX=11M Operating System

R8-1«1
2.8.1.2
2.2.1.3
2.2.2
3.0

CONTENTS

VLB
(3}
Others

MDC Software Package

FUNCTIONAL DEFINITION
3.1

DIS 'On-Line' Diagnostic
3.1.1 Local Mode
3.1.2 Host Mode
3.1.3 Communication mode

4.0

STARTING PROCEDURE

5.0

OPERATING PROCEDURE

,
:
]
!
'

5.1
5.2
5.3

5.4

Initialization
Local Mode
Host Mode
5.3.1
Single Diagnostic
5.3.2
Script
5.3.3 Auto-Script
Communication Mode

' 6.0

ERROR REPORTING

' 7.0

MISCELLANEOUS

SEQ 0003
1.0 ABSTRACT

. The purpose of the RSX tasks is the selection and control of

Distributive lntell\ggnt Subsystem (DIS) diagnostics through a host
system task.
These
diagnostics are down-lLine Loaded thru an ISB1i/ISv11

to an LSI11 or KDF11, run in a stand-alone environment and monitored
by the host task in a real-time environment.
The tasks will provide utilities to allow a Field Service Engineer

perform first Level diagnosis from the host system, or at a remote

subsystem, to call and execute stand-alone type diagnostics
utilizing the complete RSX11M/Dataway hardware as though it
were merely an XXDP media.
Additionally, the tasks will allow an operator to perform
Limited modifications to diagnostic '‘image'’ files.

2.0

REQUIREMENTS

2.1

ENVIRONMENT

HARDWARE REQUIREMENTS

RSX11M System
DEC Dataway
DIS
96K

2.2

ENVIRONMENT
2.2.1

SOFTWARE REQUIREMENTS

RSX=11M Operating System
The following macros are required:

FSRSZS, FINITS, FDBDF$, FDATSA, FDOPSA,
FDRCSA, FDBFSA, NMBLKS, OPENSR, OPENSW,
CLOSES, GETS, PUTS

2.2.1.2

(Sl
(SIS, CSI$1, CS1s2

2.2.1.3

OTHERS
ALUNS, ALUNSS, GLUNS, DIRS, ASTX$S, EXITSS,

(MKTS$S, MRKTSS, WISESS, WAITS, Ql10%, QlOws

2.2.2

MDC Software Package

3.0

TEST FUNCTIONAL DESCRIPTION

SEQ 0004

Primary DIS testing, diagnosing and verifying will be_
performed
by RSX tasks ut\lizing a series of diagnostic
image'"

files on the system disk.

thekcurrent

The facility to update

image'' files will be provided in the diagnostic

task.

The RSX11 tasks and 8080 monitor will provide the operator
with the ability toc call and execute stand-alone diagnostics
in the remote subsystem under test with calling facilities and
errortrepcrt\ng at either a local terminal or the host system
console.

3.1

DIS "ON-LINE' DIAGNOSTIC

This program/procedure will consist of

- a)

RSX11M

features (i.e.,

three basic pieces

which

are:

non-privileged task with Limited ''user-mode diagnostic''
in respect to the ISB11

driver

only),

small

down-Line
Loadable 8080 based monitor to facilitate communications
between the F.S.
maintenance
console
and
the
host, and
c¢) a set of files on the customer's disk, each of which represents
one stand-alone KDF11/LSI11/1P300 diagnostic task in image format.
The image files described
in "'c'' above will be initially
the same distribution media as the RSX11 DIS tasks and will

provided
on
be capable

- of beigg updated viapatching facilities built into the RSX task in the

host
e. Operation of this DIS task is in essentially three modes, one
of which is selected immediately after the operator '‘calls'’ the DIS
diagnostic task (i.e., > RUN CZKMP).
The three modes of the task
are:
3) LOCAL DIAGNOSIS MODE

~In this

and all

. procedures

b) HOST DIAGNOSIS MOCE and c)

subsequent

initiated and

references

controlied at

''LOCAL''

COMMUNICATION MODE.

infers

diagnostic

the KDF11/LSI111/1P300 subsystem

level and "HOST'' infers operator control exclusively from a host RSX11M

| system,

3.1.2

SEG 0005

Lc.al Diagnosis Mode

(ochpguall‘. this process consists of
three
Llevels
of
abstraction
utilizing
the system QI0 calls and the MD(C software commands
as the threads of communication interlinking the RSX11M host task, the

8080 diagnostic monitor and the LSI11 based stand-alone diagnostic.

3.1.3

Host Diagnosis Mode

The purpose of this type of test is to verify the operation of individual
components on the remote DIS subsystem from the host system.
The

diagnostic grocess is quite similar to the APT '‘quick verify'' process
which,
although it is expected to find most faults, it
is not and cannot
be expected to be as comprehensive a testing process as that conducted in

"local’’ mode.

It does provide, however, an efficient method for Field

Service to verify basic

functionality of the remote subsystems.

The process, which can be

. the testing

methodology

initiated in several ways,

)

always

)

utilizes

analogous to the Automated Process Testing (APT) utilized
in
various
mfg.
plants.
It follows then that for a diagnostic to
be usable, it
must be fully APT-compatible utilizing hooks for controlling the
test
and
reporting end
of
pass
and errors.
It is anticipated that the

“up=line Load”
command will
be utilized for reporting and the '‘down=-Line
load'’ command for test initiation, termination and control.

3.1.4

COMMUNICATION MODE

This mode acts much the same as the Host mode however, when running DIS
tests on 1/0 modules, using the diagnostic CVPCAX, a map of the DI

170 modules

is uploaded to the Host terminal on the first pass and a

full error report

is made enabling the F.S.

address the error occured,
error occured.

on what

type of

personnel

to know at which

[1/0 board and what

type of

4.0

STARTING PROCEDURE

SEQ 0006

SET /u1C=[200,270]
This instruction will establish the user code to be the same
as that used when the tasks and image files
of KDF11/LSI11/1P300
diagnostics were originally Loaded on the disk.
RUN CZKMPB

This

instruction will start

5.0

OPERATING PROCEDURE

5.1

INITIALIZATION
CZKMPB VERSION

the RSX diagnostic

task.

2.2

At the beginning of the task, the current
the task will be printed as shown above.

version number of

SELECT MODE:

LOCAL, HOST, AUTO=-MAP, COMMUNICATICN OR EXIT

(L,H,A,C,E)

The mode query enables to user to select which mode of operation
is to be used or to exit the task.
The Auto-map feature is
planned for future development.
Host mode will continually
return the user to this mode query for additional input and it
must be used as the exit medium.
Local mode will terminate the
task normally when the user specifies from the remote subsystem.
A CNTL Z input to any Host mode quer¥ will return the user to

this mode query. Communication mode
is Like the Host but it
uploads more information rather than the quick verify Host.

All_infut values are in octal unless otherwise specified as
decimal. The same is true of numbers used in printed statements.

ENTER NUMBER OF

TERMINALS (D] =

Enter the total number of terminals to be specified as input.
This number will be compared against the number of terminals
specified Later and will generate an error if they are not
equal.
As indicated, this is a decimal number.
ENTER CONTROLLER NUMBER [0] =
Enter the controller number

in a range from 0 - 3.

ENTER TERMINAL NUMBERS (0] =
Enter the terminal numbers to be used associated with the above
controller number within a range from 0-77.
in the following formats:

They may be entered

1.3
1-5

NUMBER OF

ENTERED TERMINALS = 2

This statement will print out

the number of

requested terminals

which were successfully attached to the task.
If both port
addresses of a DIS were specified as input, only the base port
address will be included in the count.
The count is the number
of subsystems not addresses.
Both addresses are attached to the
task.

SEQ 0007

SEQ 0008

UNIT »+ CONTROLLER *+ LOGICAL SB =+
oy
6

0
1

1
1

A table of the successfully attached subsystems will be printed.
The number of entries will match the number of terminals printed
in the statement above.

5.2

LOCAL DIAGNOSIS MODE

The following inputs will be entered on a terminal connected
to the local DIS being diagnosed by the FS Engineer.
>FILE NAME

Enter any LSI11/1P300 diagnostic file name for which there
is an image file on disk. Whenever the prompt character
">'" is printed, enter a file name or a CNTRL Z which will
allow entry of the termination code.
157776
#2006

The memory size and an ''at''sign will be printed when the
diagnostic has been successfu ll downloaded into LSI memory.
The system is in ODT mode and the diagnostic can be started

by entering 200G (the standard diagnostic start-up). The XXDP
diagnostic will operate as though 1t were 1n stand-alone
mode and will print any messages or errors on the terminal.

10 halt the diagnostic and re-enter ODT mode, press the "BREAK"
ey.

017312
87601447000000 1

As the subsystem re-enters ODT mode, the address at which the
break was made will be printed (disregard) and an '‘at'’ sign.
Open loc:tion 760144 (CSR4) and enter
(to terminate the task)

(to request another diagnostic).

Termination will print a message of 3EX.

prompt character will be issue

NOTE:

Alternately, a

for another file name.

THE TASK MUST BE TERMINATED IN THIS MANNER. 1T CANNOT
BE SUCCESSFULLY TERMINATED FROM THE HOST COMPUTER.

5.3

HOST DIAGNOSIS MODE
SEQ 0009
The following messages printed in relation to the running of

the hardcore diagnostics are also printed on the host terminal
following the execution of local mode.
They are the last

procedure run

local mode but

the

first

one

in host

mode.

STARTING HARDCORE DIAG == TERMINAL X WILL GO OFFLINE
This is simple a message warning the user that the terminal
should be expected to go offline during these tests.
TERMINAL X
TERMINAL X

IS OFFLINE
IS BACK ONLINE

These messages indicate that the terminal did go offline and
returned successfully to an online status.
If the hardcore

diagnostics fail, the DIS will not come back onlLine and an
error message will indicate this condition.
f the softcore
tests (which
are the last three tests of the hardcore
diagnostics) fail, the unit will return online but error
messages indicating the softcore failures will be printed.
SYS ID #+ PORT

400

~+« MEM SIZE

157776

This is a printout of the system id, base port address and
memory size of the DIS on which hardcore diagnostics were
just

run.

PRINT ROM ID'S
When a, Y,

(Y,N)

is typed indicating you wish the ROM ID's to be

thed. a hexidecimal number in each Rom is read wihch contains
the Rom number in the upper byte and the version number in the
lower byte.
This number is printed in octal on the Host
terminal,
The least significant digit printed for each Rom is
the version number.

ENTER S OR A FOR SCRIPT OR AUTO-SCRIPT =

A carriage return will skip over the script mode and allow
individual

input of diagnostic file names.

An "'A"" should

be used for auto-scrtgt ogerotwon when the desired script
already exists.
An ''S' should be used when a script is to
be created and then executed.

When an ''A'" is

input, the following message will be printed.

ENTER SCRIPT NAME =
Enter the name of the script already created that
executed.

is to be

When an ''S'"" is input, the following is printed.
TO SAVE

SCRIPT,

If the script

ENTER NAME

is to be saved on disk for future use, enter

the name to be used to recall it later.
If the script
is not
to be saved, enter a carriage return and after the script is

executed it will be destroyed.

ENTER FILE NAMES TO BE SCRIPTED AND NUMBER OF PASSES
FILE NAME =

Enter any KDF11/LS111/1P300 diagnostic
file on disk.

To terminate a script,

after this query.

for which there is an image

type a carriage return

PASSES =

Enter the decimal number of passes to be executed of the

above diagnostic.

The maximum is 32768.

These two queries will be repeated until the script is
terminated by a carriage return.,
The script will then be
executed.

After the execution of a script,
be printed.
ANOTHER SCRIPT?

(Y OR N )

the following query will

SEQ 0010

To run another script, enter "Y'’ and the task «ill

to the script query.

mode query.

Otherwise,

the task will

return

return to the

If script mode is skipped, the task will jump to this point,

SEQ 0011

ENTER FILE NAME =

SEQ 0012

Enter any KDF11/LS111/1P300 diagnostic for which there is an image
file on disk.

HOW MANY PASSES?

Enter the number of passes to be run of the diagnostic up to a
maximum of 32768.
However, unlimited iterations
of the diagnostic
may be run by entering a carrtage return.
The diagnostic will
continue to execute until the RSX task is aborted.
If unlimited
iterations are to be run, the following query will
be
printed.
For & specified number of passes, the pass count will
be printed
as often as it is uploaded from the diagnostic.
ENTER NUMBER OF PASSES BETWEEN PRINT STATEMENTS =
Enter any decimal number to a maximum of 32768.
return will cause a default

ANY PATCHES

to 1000.

A carriage

(Y OR N)?

Enter yes, if there are patches to be made to the diagnostic
before it is downloaded.
OPTIONS ARE:
1

LOAD AND SAVE
This option will patch the diagnostic and save
the new version on disk as well
as execute the
patched version,

2 = LOAD AND GO
This option will patch the diagnostic and
execute it but it will not be saved.

3 = PATCH ONLY
This option will patch the diagnostic and
save it but it will not be executed.
ENTER OPTION CODE =

Enter the option code selected from the List above.
ENTER PATCHES

Enter the patches by.txpina first the address to be patched
followed by a slash '/""
and
then the new value to be stored.
ALL addresses to be patched must be entered although not

necessarily in sequential order.

A line feed will not

retrieye the next address.
Each entry must be on a separate
Line add the List terminated by a Line with only a carriage
returnsas

input.

PATCH TABLE LOADED

This indicates the patches have been successfully accepted.

SEQ 0013

DOWNLOADING DIAGNOSTIC XXYXXX.IMG;1
CN TERMINAL X

SEQ 0014

Since there is a slight pause as the diagnostic
downloaded and started, this message

is being

is to indicate what

is happgning.
After the diagnostic is started, the pass
count will
be continuously printed as shown below.

PASSES COMPLETED = 9999 ON TERMINAL X
A pass count will not be printed after every pass since

more than one pass may be completed of

between uploads from the diagnostic.

the diagnostic

The last pass

count may be greater than the specified number of passes
for the same reason.

CZKMPB ... END OF

DIAGNOSTIC

This message indicates the diagnostic
required number of passes.
ANOTHER DIAGNOSTIC ON THE
It yes,
it will

5.4

SAME

has completed the

TERMINAL

the program will return to the
return to the mode query.

IN HOST MODE?

(Y OR N)

file name query.

1If

no,

COMMUNICATION MODE
This mode has all

not

the same messages as Host mode eccept

allow scripting.

it does

6.0

SEQ 0015

ERRCR REPORTING

Except for the two errors returned under
terminal,

exceptions

all errors will
are:

local mode on the local

be reported on the host

Bad load

Non-existent

terminal.

Local

The errors reported on the host
categories.

two

file

In addition, errors from the LSI11/1P300 diagnostics being

mode will be reported on the

The

terminal

run in Local

as stated earlier.

fall

into the

following

RSX ERRORS
A knowledge of

the RSX operating system would be helpful

in interpreting these errors.
However,
the most common
DSw :;{?r code will be a =65, which indicates the DIS
is

ne.

Controller X Terminal XX is not SYSGENed In
Terminal XX Cannot be Assigned - DSW =
Terminal XX Cannot be Attached - DSW

Lun 99 Cannot be Assigned - DSW =

Download Error on Terminal X = DSW =
Upload Error on Terminal X - DSW =
File Name in Error is XXXXXX
)
x
CZKMPB ... Directive Failure During (operation Listed below)
CZKMPB ... 1/0 Error During (operation Listed below)

Terminal Assign Logical Unit Number

Console Prompt
Console Repl{
Attach Serial
Bus (SB)
Detach §
.
CS1 (Command String Interpreter)

Mark

(ALUN)

File Open
File Read
File Write
Kill Attach
SB ALUN
SB GLUN
SB Already Attached

Time

Clear Mark Time
INPUT DATA ERRORS

CZKMPB
CZKMPB
CIKMPB
CZIKMPB
CIKMPB

... Invalid Controller Number
... Invalid Terminal Numbers
... Invalid Response
... Terminal input Exceeds Total
;
... Huétiple Terminals Cannot be Diagnosed in Local

Terminal X

mode
is the Upper Port of a DIS

(Warning Only)