.ps 60,80
.literal
- HELP
EVGAB is the second of two level 3 CI Functional Diagnostics for
a CIBCI, CI780, CI750 or PX780. The diagnostic uses the CI operational
microcode and executes self-directed and loopback commands.
To run EVGAB, boot in the Diagnostic Supervisor, load
EVGAB.EXE, and attach as follows:
For a CIBCI on
a VAX 8800
1. all ATTACHes specifying BI NODE numbers should be documented
to show that node numbers are to be in HEXadecimal
2. BI nodes instead of being attached to HUB should be attached
to NBIBn, i.e.
the following sequence should be added:
ATTACH NBIA HUB NBIAn ! where n 0 or 1
LOGICAL ADAPTER # ? N ! 0 or 1
ATTACH NBIB NBIAn
Device Name ? NBIBn ! where n 0 to 3
BI # ? n ! 0 or 1
BI Node Number (HEX) ? n ! n 0 to F
ATTACH ! Then attach UUT
Device name? CIBCI ! Device to test
Device link? NBIBn ! Same as above
device? PAAn ! Specify the CI
BI Node? n ! BI node #
BR Level? n ! BR level #
CI address? n ! 0 - F
For example:
ATTACH NBIA HUB NBIA0 0 ; logical unit 0
ATTACH NBIB NBIA0 NBIB0 1 0 ; BI #1, BI node 0
ATTACH CIBCI NBIB0 PAA0 2 4 0 ; BI node 2, BR level 4
; CI node 0
SELECT PAA0 ; device to be run
For a CIBCI on
a VAX 8200 :
ATTACH CIBCI HUB PAA0 14 4 0'
where 14 is the BI node number,
4 is the BR level, and
0 is the Node number.
SELECT PAA0
START
For a CI780 on
a VAX 8600 :
'ATTACH SBIA HUB (SI0 or SI1)'
ATTACH CI780 (SI0 or SI1) PAA0 14 4 0'
where 14 is the TR number,
4 is the BR level, and
0 is the Node number.
SELECT PAA0
START
For a CI780 on
a VAX 780,785:
'ATTACH CI780 HUB PAA0 14 4 0'
where 14 is the TR number,
4 is the BR level, and
0 is the node number.
SELECT PAA0
START
For a CI750: 'ATTACH CI750 HUB PAA0 10 4 0'
where 10 is the SLOT number,
4 is the BR level, and
0 is the node number.
SELECT PAA0
START
FOR A PX780
'ATTACH PX780 HUB PXB0 15 4 0
where 15 is the TR number,
4 is the BR level, and
0 is the Node number.
SELECT PXB0
START
For data on attaching, type 'HELP EVGAB ATTACH_CI780' OR CI750
or PX780 or ATTACH_CI780_8600 or ATTACH_CIBCI_8200.
Each time information is desired on the following keywords
it is necessary to type HELP EVGAB 'keyword'.
- ATTACH_CIBCI_8800.
ATTACH NBIA HUB NBIAn ! where n 0 or 1
LOGICAL ADAPTER # ? N ! 0 or 1
ATTACH NBIB NBIAn
Device Name ? NBIBn ! where n 0 to 3
BI # ? n ! 0 or 1
BI Node Number (HEX) ? n ! n 0 to F
ATTACH ! Then attach UUT
Device name? CIBCI ! Device to test
Device link? NBIBn ! Same as above
device? PAAn ! Specify the CI
BI Node? n ! BI node #
BR Level? n ! BR level #
CI address? n ! 0 - F
For example:
ATTACH NBIA HUB NBIA0 0 ; logical unit 0
ATTACH NBIB NBIA0 NBIB0 1 0 ; BI #1, BI node 0
ATTACH CIBCI NBIB0 PAA0 2 4 0 ; BI node 2, BR level 4
; CI node 0
SELECT PAA0 ; device to be run
- ATTACH_CIBCI_8200.
ATTACH CIBCI HUB PAA0 14 4 0 ; attaches CIBCI to VAX 8200
SELECT PAA0 ; selects device to be run
Device: CIBCI
Link: HUB
Recommended generic: PAa0
Additional information:
BI node Number: [decimal 0-15]
BR Level: [4-7] determined by BP jumpers
Node Number: [decimal 0-255] switch select on Link Bd
Note that the node number set on the Link Bd should agree with
the node number used in the Attach Command.
- ATTACH_CI780_8600.
ATTACH SBIA HUB SI0 ; If SBIA1 is used, attach SI1
; instead of SI0
ATTACH CI780 SI0 PAA0 14 4 0 ; attaches CI780 to VAX 8600
SELECT PAA0 ; selects device to be run
Device: CI780
Link: SI0/SI1
Recommended generic: PAa0
Additional information:
TR Number: [decimal 1-15] determined by BP jumpers
BR Level: [4-7] determined by BP jumpers
Node Number: [decimal 0-255] switch select on Link Bd
Note that the node number set on the Link Bd should agree with
the node number used in the Attach Command.
- ATTACH_CI780
; On a VAX 11/785 it is attached in the
; same way as the Vax 11/780
ATTACH CI780 HUB PAA0 14 4 0 ; attaches CI780 to 11/780
SELECT PAA0 ; selects device to be run
Device: CI780
Link: HUB/SBI
Recommended generic: PAa0
Additional information:
TR Number: [decimal 1-15] determined by BP jumpers
BR Level: [4-7] determined by BP jumpers
Node Number: [decimal 0-255] switch select on Link Bd
Note that the node number set on the Link Bd should agree with
the node number used in the Attach Command.
- ATTACH_CI780
ATTACH CI780 HUB PAA0 14 4 0 ; attaches CI780 to 11/780
SELECT PAA0 ; selects device to be run
Device: CI780
Link: HUB/SBI
Recommended generic: PAa0
Additional information:
TR Number: [decimal 1-15] determined by BP jumpers
BR Level: [4-7] determined by BP jumpers
Node Number: [decimal 0-255] switch select on Link Bd
Note that the node number set on the Link Bd should agree with
the node number used in the Attach Command.
- ATTACH_CI750
ATTACH CI750 HUB PAA0 10 4 0 ; attaches CI750 to 11/750
SELECT PAA0 ; selects device to be run
Device: CI750
Link: HUB/CMI
Recommended generic: PAa0
Additional information:
SLOT Number: [decimal 10-15]
BR Level: [4-7] determined by BR Plug
Node Number: [decimal 0-255] switch select on Link Bd
Note that the node number set on the Link Bd should agree with
the node number used in the Attach Command.
- ATTACH_PX780
ATTACH PX780 HUB PXB0 15 4 0 ; attaches PX780 to 11/780
SELECT PXB0 ; selects device to be run
Device: PX780
Link: HUB or SBI
Recommended generic: PXB0
Additional information:
TR Number: [decimal 1-15] determined by BP jumpers
BR Level: [4-7] determined BR plug
Node Number: [decimal 0-255] Attach as node 0 for CINT
- EVENT_FLAGS
EVGAB is affected by Event Flags 1 and 2.
For information on each event flag type
'HELP EVGAB EVENT_FLAGS n' where n is 1 or 2.
- 1. This program expects the ci operational microcode
to be present prior to starting the tests. If the
microcode has not been loaded, or is questionable
then setting EVENT FLAG 1 prior to starting the
diagnostic will cause a copy of the ci microcode
to be loaded from the default load device into the
control store for every start sequence. The
exception to the above is if apt loaded. Then,
the operational microcode will be expected to be
loaded regardless of the setting of event flag 1.
- 2
EVENT FLAG 2 is used to display Queue entry information
before and after the port is enabled to process commands.
The runtimes are greatly increased when this flag is set.
- SECTIONS
There are no section names implemented in this diagnostic.
- QUICK
The QUICK feature is not implemented in this diagnostic.
The diagnostic execution time for EVGAB is 35 seconds
on a CI780, PX780 and 66 seconds on a CI750.
- SUMMARY
No SUMMARY report is issued by this program.
- CI_UCODE
THIS PROGRAM EXPECTS THE CI OPERATIONAL MICROCODE
TO BE PRESENT PRIOR TO STARTING THE TESTS. IT ALSO
EXPECTS THE MICROCODE IN ROM TO COMPATIBLE THE MICROCODE
IN RAM (VERSION 3 TO VERSION 5 ETC..) IF THE MICROCODE
HAS NOT BEEN LOADED, OR IS QUESTIONABLE THEN SETTING
EVENT FLAG 1 PRIOR TO STARTING THE DIAGNOSTIC WILL CAUSE
THE PROGRAM TO CHECK VERSION LEVELS AND TAKE THE
APPROPRIATE ACTION. SEE HELP EVGAB EVENT_FLAGS 1 FOR MORE
INFORMATION.
.end literal