- HELP
EVDMB
The DMP11 Functional diagnostic (EVDMB) is a level 2R diagnostic
program which will provide the user with an on-line mechanism for
verifying the operation of a VAX/DMP11. This program runs under the
control of the Diagnostic Supervisor under the VMS operating system.
- Configurations
This diagnostic can test a DMP11 in several configurations:
- DMP11 to DMP11 in DDCMP point to point mode
- DMP11 to multiple DMP11s in multipoint mode
- DMP11 to DMC11 in DDCMP point to point compatibility mode. To
run this configuration the DMC11 must be run using ESDCA.EXE's
DTR or DTS sections.
Furthermore, if the DMP parameters are software selectable
(M8203, E121, switch 8 in the on position), the DMP network can be
configured for just about any mode of operation by using the
appropriate attach sequence. Of course one must consider device and
cabling configurations. A DMP to DMC configuration cannot be put in
multipoint mode, and the cabling must be correct for DMP multipoint
mode. Cabling is explained in the "DMP11 Synchronous Controller
Technical Manual" in chapter 2.
- ATTACH
The following is a breakdown of the attach prompts, the
possible responses, and what those responses mean.
DS> LOAD EVDMB ; ALLOWS DS> TO ACCESS DMP11 P_TABLE DESCRIPTOR
DS> ATT DMP11 ; MAKES THE DMP11 KNOWN TO DS>
DEVICE LINK? ; LINK BETWEEN DMP11 AND THE REST OF THE SYSTEM
DEVICE NAME? ; MUST USE VMS GENERIC NAME (XDA through XDZ)
CSR? ; UNIBUS ADDRESS BETWEEN 760000 AND 777776 OCTAL
VECTOR? ; UNIBUS VECTOR ADDRESS BETWEEN 2 AND 776 OCTAL
BR? ; UNIBUS INTERRUPT REQUEST LEVEL
CONTROL STATION? ; YES - DEVICE IS A CONTROL STATION IN A MULTIPOINT
; NETWORK CONFIGURATION
; NO - DEVICE IS NOT A CONTROL STATION IN A MULTIPOINT
; NETWORK
TRIB? ; YES - DEVICE IS A TRIBUTARY STATION IN A MULTIPOINT
; NETWORK
; NO - DEVICES IS NOT A TRIBUTARY STATION IN A
; MULTIPOINT NETWORK
COMPATIBILITY MODE? ; YES - THERE IS A DMC11 CONNECTED TO THIS DEVICE
; NO - THERE IS NOT A DMC11 CONNECTED TO THIS DEVICE
HALF DUPLEX? ; YES - THE LINE IS A HALF DUPLEX LINE
; NO - THE LINE IS A FULL DUPLEX LINE
- 11/780
The following attach sequence is for the Unibus to system
bus interface:
DS> ATT DW780 HUB DW0 3 4
The attach sequence for the DMP11 is the same for all
processors. See the the appropriate section (point to point,
multipoint, etc.) to attach a particular configuration.
- 11/750
DS> ATT DW750 HUB DW0
The attach sequence for the DMP11 is the same for all
processors. See the the appropriate section (point to point,
multipoint, etc.) to attach a particular configuration.
- 11/730
DS> ATT DW730 HUB DW0
The attach sequence for the DMP11 is the same for all
processors. See the the appropriate section (point to point,
multipoint, etc.) to attach a particular configuration. For
definitions of the DMP11 attach prompts see the section "Attach
Prompt Definitions":
- Point To Point
Only one tributary should be attached, and its address
should always be one.
DS> LOAD EVDMB
DS> ATTACH DMP11 DW0 XDA 760160 360 5 NO NO NO NO
DS> SELECT XDA
After starting the diagnostic the user will be prompted for the number
of tributaries that are connected to this device and their addresses.
Simply type carriage return to use the default values of one tributary with
an address of one.
- Multipoint
- Control Station
The tributary addresses in the following attach sequence
should be the same as the addresses of the tributaries to be
tested. Along with the other tests, the DTM test (data test
multipoint) can be used in conjunction with the DTR test
running on the tributary station that this device will test.
DS> LOAD EVDMB
DS> ATTACH DMP11 DW0 XDA 760160 360 5 YES NO NO NO
DS> SELECT XDA
After starting the diagnostic the user will be prompted for the number
of tributaries that are connected to this device and their addresses. Be
sure that the the control station's address for the tributary, and the
tributary's station address is the same.
- Tributary Station
The tributary address used should be the same as this
device's DDCMP address. Along whith the other tests, section
DTR should be used on this device while section DTM is used on
this device's control station.
DS> LOAD EVDMB
DS> ATTACH DMP11 DW0 XDA 760160 360 5 NO YES NO NO
DS> SELECT XDA
After starting the diagnostic the user will be prompted for the number
of tributaries that are connected to this devic and their addresses.
Simply type carriage return to use the default values of one tributary with
an address of one. Be sure that the control station's address for the
tributary, and the tributary's address is the same.
- DMP11 To DMC11
In order to run this configuration, the diagnostic ESDCA
must be run on the DMC11 using either the DTR or DTS tests in
that diagnostic, and the appropriate counterpart in EVDMB (i.e.
DTS on DMC and DTR on DMP and vice versa). This mode of
operation is point to point.
DS> LOAD EVDMB
DS> ATTACH DMP11 DW0 XDA 760160 360 5 NO NO YES NO
DS> SELECT XDA
After starting the diagnostic the user will be prompted for
the number of tributaries that are connected to this device and
their addresses. Simply type carriage return to use the default
values of one tributary with an address of one.
- SECTIONS
The diagnostic is divided into several sections. The tests
that are executed in each section,and to configuration that can be
tested are also listed:
- Default
Executable in all configurations
- Test 1 - Maintenance Wrap Test
- Test 6 - Read/Write the Modem Register
- Test 7 - Send/Receive 256 Bytes Point to Point
- Test 8 - Send/Receive 255 Bytes Multipoint
- Test 9 - Short Message
- Test 10 - Latch/Unlatch Polling
- Test 11 - Mop Mode Test
- Test 12 - Polling State Degradation Test
- Maintenance
Executable in all configurations
- Test 1 - Maintenance Wrap Test
- Cable
Executable in all configurations
- Test 2 - Cable Wrap Test
- Modem
Executable in all configurations
- Test 3 - Modem Wrap Test
- DTR
Data Test Receiver - executable in all configurations
UNLESS the DMP11 is a control station in a multipoint network.
The DMP can be a tributary in a multipoint network.
- Test 5 - System Wrap Receiver
- DTS
Data Test Sender - executable in point to point mode only.
This includes DMP to DMC configurations.
- Test 4 - System Wrap Sender
- Functional
Executable in all configurations
- Test 6 - Read/Write the Modem Register
- Test 7 - Send/Receive 256 Bytes Point to Point
- Test 8 - Send/Receive 255 Bytes Multipoint
- Test 9 - Short Message
- Test 10 - Latch/Unlatch Polling
- Test 11 - Mop Mode Test
- Test 12 - Polling State Degradation Test
- Manufacturing
Executable in all configurations
- Test 1 - Maintenance Wrap Test
- Test 2 - Cable Wrap Test
- Test 6 - Read/Write the Modem Register
- Test 7 - Send/Receive 256 Bytes Point to Point
- Test 8 - Send/Receive 255 Bytes Multipoint
- Test 9 - Short Message
- Test 10 - Latch/Unlatch Polling
- Test 11 - Mop Mode Test
- Test 12 - Polling State Degradation Test
- ITEP
Executable only in the DMP to DMC configuration with the
DMC running ITEP's receive section.
- Test 13 - Send ITEP Message 1
- DTM
Data Test Multipoint - executable only if the DMP is a
control station in a multipoint network.
- Test 14 - Data Test Multipoint
- ERRORS
- IOSB
When a fault occurs several pieces of information are returned
one of them being an IOSB (I/O status block). The I/O status block
(IOSB) usage for al DMP11 QIO functions is shown below:
+---------------------+--------------------+
| transfer size | completion status |
+----------+----------+----------+---------+
| error nr | err bits | status | char |
+----------+----------+----------+---------+
- Status
I/O completion status returns are as follows:
Value (hex) Completion Status Meaning
2C SS$_ABORT - fatal hardware error or I/O cancelled.
870 SS$_ENDOFFILE - no data available when IO$M_NOW was
specified.
01 SS$_NORMAL - operation was successfully completed.
84 SS$_DEVOFFLINE - protocol not started on specified
tributary.
2C4 SS$_DEVACTIVE - function is inconsistent with the
current state of the tributary.
20D4 SS$_DEVINACT - controller not started before tributary
was started.
14 SS$_BADPARAM - bad parameter given in parameter list.
860 SS$_DEVICEFULL - no more tributaries allowed. Only one
tributary allowed for point-to-point
or tributary station.
601 SS$_BUFFEROVF - user buffer not large enough to hold
all info from IO$_SENSEMODE.
24 SS$_NOPRIV - user does not have enough priveleges for
attempted operation.
908 SS$_NOSUCHDEV - there is no device with the given logical
name. Must be XDc for DMP11 where XD is
the VMS software name for DMP11s, and c is
the controller (letter value between A and Z)
- Char
The following bits may be set in the second longword:
Value (hex) Characteristic Meaning
01 XM$M_CHR_MOP - DDCMP maintenance mode
02 XM$M_CHR_LOOPB - loop back mode
04 XM$M_CHR_HDPLX - half-duplex operation
80 XM$M_CHR_TRIB - tributary station
40 XM$M_CHR_CTRL - control station
20 XM$M_CHR_DMC - line is in DMC compatible mode
- Status
Status bits:
0800 XM$M_STS_ACTIVE - DDCMP protocol is active
4000 XM$M_STS_DISC - modem line went from on
to off
2000 XM$M_STS_RUNNING - tributary is responding
- Error Bits
Error bits:
080000 XM$M_ERR_MAINT - DDCMP maintenance message
received
800000 XM$M_ERR_START - DDCMP START message received
010000 XM$M_ERR_FATAL - unexpected hardware/software
error occurred on controller
400000 XM$M_ERR_TRIB - unexpected hardware/software
error occurred on tributary
100000 XM$M_ERR_LOST - data lost when a message was
too big for buffer
020000 XM$M_ERR_THRESH - rcv/xmit/select threshold
errors
- Error nr Error nr:
Value (hex) Error Type Meaning
02000000 Receive threshold error - Indicates the number of receive
errors has exceeded seven. Reset
to zero on reporting error.
04000000 Transmit Threshold Error - Indicates the number of transmit
errors has exceeded seven. Reset
to zero on reporting error
06000000 Select Threshold Error - Indicates the selection timer has
timed out seven times. Reset to
zero on reporting error
08000000 Start Message and Running - Indicates that a DDCMP Start
message was received while in
the DDCMP run state.
0A000000 Maint Message and Running - Indicates that a maintenance
message was received while in the
DDCMP run state.
0C000000 Maint Message and Halted - Indicate that a maintenance
message was received whil in the
DDCMP halt state.
0E000000 Start Message and Maint - Indicate that a start message was
received while in the DDCMP
maintenance state.
12000000 Tributary in Dead State - Indicates that a tributary station
has not responded to polling for
a while and has been put in the
dead state.
14000000 Tributary in Run State - Indicates that the DDCMP run state
has been entered.
16000000 Babbling Tributary - Indicates that a tributary keeps
on transmitting valid DDCMP
messages even after its allotted
transmit time has expired.
18000000 Streaming Tributary - Indicates that a station has not
given up the link (carrier still
on line) even though no data is
being transmitted be the station.
1A000000 Modem Ring Detected - Indicates that an off to on
transition of ring occured.
C4000000 Modem Disconnect - Indicate that an on to off
transition of Data Terminal Ready
occured.
C8000000 Modem Carrier Loss - Indicates that an on to off
transition of Carrier Detect has
occurred
- Messages
Standard Message Formats
The following error messages may result for the indications
shown. Some of these failures may result from VMS system
interaction in which case the system manager or local software
specialist should be consulted. The relation of failure and cause
will not always be obvious, these examples are intended to present
the most obvious failures with the most likely cause.
******** ZZ-EVDMB VAX/DMP11 FUNCTIONAL DIAGNOSTIC - 3.0 ********
PASS 1 TEST 1 SUBTEST 0 ERROR 2 4-SEP-1980 09:14:41.71
SYSTEM FATAL WHILE TESTING XDA0: SYSTEM SERVICE FAILURE
COMPLETION CODE: [00000024(X)]; no privilege for attempted operation
COULD NOT ISSUE A SETMODE QIO
.. ABORTED PROGRAM AT PASS 1 TEST 1 SUBTEST 0 PC 0000C31F.
EVDMB requires the DIAGNOSE and PHYIO privilege, the System
manager should be contacted to obtain this privilege. Also, if
a $CANCEL or $DASSGN system service is used and the device is
not assigned to the program this error will occur. It is
uneccessary to allocate the device before running the diagostic.
******** ZZ-EVDMB VAX/DMP11 FUNCTIONAL DIAGNOSTIC - 3.0 ********
PASS 0 INITIALIZATION SECTION ERROR 4 4-sep-1980 12:14:41.71
SYSTEM FATAL WHILE TESTING T0: SYSTEM SERVICE FAILURE
COMPLETION CODE: [00000908(X)] ; no such device available
.. ABORTED PROGRAM AT PASS 0 INITIALIZATION SECTION PC 0000BD19
This means that probably the logical name given to the
device (i.e. XDA0) in the attach sequence is incorrect. Please
note that this error cannot occur as a result of the tributary
attach sequence, only the DMP11 attach sequence.
******** ZZ-EVDMB VAX/DMP11 FUNCTIONAL DIAGNOSTIC - 3.0 ********
PASS 1 TEST 5 SUBTEST 0 ERROR 14 27-OCT-1980 10:04:06.23
SYSTEM FATAL WHILE TESTING XDA0: I/O COMPLETION ERROR
AST PARAMETER:[04020000(X)] ; Error number =004(O),ERRTHRESH
ERROR NUMBER [004(O)] ; XMIT THRESHOLD ERROR
..ABORTED PROGRAM AT PASS 1 TEST 4 SUBTEST 0 PC 0000A19C.
Threshold error counters are used to determine when certain
error conditions have occured. After so many consecutive error
a persistant fault probably exists and the DMP11 notifies
software, resulting in this error.
******** ZZ-EVDMB VAX/DMP11 FUNCTIONAL DIAGNOSTIC - 3.0 ********
PASS 1 TEST 4 SUBTEST 0 ERROR 14 27-OCT-1980 10:04:06.23
SYSTEM FATAL WHILE TESTING XDA0: I/O COMPLETION ERROR
FULL DUPLEX
PATTERN NUMBER = 1
A TRANSMIT FAILED
IOSB1: [0000002C(X)] ; QIO TIMED OUT - I/O CANCELED
IOSB2: [04000000(X)] ; Error number =004(O)
ERROR NUMBER [004(O)] ; XMIT THRESHOLD ERROR
.. ABORTED PROGRAM AT PASS 1 TEST 4 SUBTEST 0 PC 0000A19C.
A data message was transmitted and a reply was not received
within the timeout period.
******** ZZ-EVDMB VAX/DMP11 FUNCTIONAL DIAGNOSTIC - 3.0 ********
PASS 0 INITIALIZATION SECTION ERROR 6 27-OCT-1980 10:04:06.23
SYSTEM FATAL WHILE TESTING UNKNOWN DEVICE: THERE ARE NO DEVICES TO TEST
.. ABORTED PROGRAM AT PASS 0 INITIALIZATION SECTION PC 00007CC6.
Device was attached but not selected - select device.
******** ZZ-EVDMB VAX/DMP11 FUNCTIONAL DIAGNOSTIC - 3.0 ********
PASS 1 TEST 1 SUBTEST 0 ERROR 16 27-OCT-1980 10:04:06.23
HARD ERROR WHILE TESTING XDB0: DATA COMPARE ERROR
BEGINNING ADDRESS OF RECEIVE BUFFER IS: 000031CE
ADDRESS GOOD BAD XOR
000031CE: 12 00 12 ; BIT4,BIT1
000031CF: 43 00 43 ; BIT6,BIT1,BIT0
Data compare error encountered.
- TRIBS
Tributary is the name given to a DMP11 in a multipoint network when it is
not controlling (control station) the network. A DMP11 must always have
at least one tributary established, even if the network is point to point,
for the microcode to communicate with another device.