Trailing-Edge
-
PDP-10 Archives
-
BB-F493Z-DD_1986
-
10,7/703mon/stopcd.mem
Click 10,7/703mon/stopcd.mem to
see without markup as text/plain
There are 16 other files named stopcd.mem in the archive. Click here to see a list.
TOPS-10 STOPCODES SPECIFICATION
April 1986
This document describes stopcodes for
the TOPS-10 monitor, GALAXY, and
DECnet-10 software.
|
|
|
| OPERATING SYSTEM: TOPS-10 Version 7.03
| GALAXY Version 5.1
|
| SOFTWARE: DECnet-10 Version 4.0
1
First Printing, December 1980
Revised, April 1986
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 appear in this document.
The software described in this document is furnished under a license
and may only be used or copied in accordance with the terms of such
license.
No responsibility is assumed for the use or reliability of software on
equipment that is not supplied by DIGITAL or its affiliated companies.
Copyright C , 1980, 1986 Digital Equipment Corporation.
All Rights Reserved.
The postage-prepaid READER'S COMMENTS form on the last page of this
document requests the user's critical evaluation to assist us in
preparing future documentation.
The following are trademarks of Digital Equipment Corporation:
DEC MASSBUS UNIBUS
DECmate PDP VAX
DECsystem-10 P/OS VMS
DECSYSTEM-20 Professional VT
DECUS Rainbow Work Processor
DECwriter RSTS
DIBOL RSX
2
CONTENTS
1.0 MONITOR STOPCODE DEFINITION . . . . . . . . . . . . 4
2.0 TYPES OF STOPCODES . . . . . . . . . . . . . . . . . 5
2.1 DEBUG Stopcodes . . . . . . . . . . . . . . . . . 6
2.2 JOB Stopcodes . . . . . . . . . . . . . . . . . . 6
2.3 STOP Stopcodes . . . . . . . . . . . . . . . . . . 7
2.4 CPU Stopcodes . . . . . . . . . . . . . . . . . . 8
2.5 HALT Stopcodes . . . . . . . . . . . . . . . . . . 9
2.6 INFO Stopcodes . . . . . . . . . . . . . . . . . . 9
3.0 CONTINUABLE STOPCODES . . . . . . . . . . . . . . . 9
4.0 LIST OF MONITOR STOPCODES . . . . . . . . . . . . 11
5.0 LIST OF DECNET-10 STOPCODES . . . . . . . . . . . 112
6.0 LIST OF GALAXY-10 STOPCODES . . . . . . . . . . . 134
3
PREFACE
This document briefly describes the TOPS-10 monitor, GALAXY, and
DECnet-10 stopcodes. This specification was designed to assist the
user in analyzing stopcode messages, to investigate and undertake
corrective action when the TOPS-10 monitor, GALAXY, or DECnet-10
software unexpectedly fails.
Audience Requirements
The following manuals provide additional information for analyzing and
regenerating a TOPS-10 monitor, GALAXY, and DECnet-10 software.
o TOPS-10 Software Installation Guide describes procedures for
generating and installing TOPS-10 and GALAXY software.
o DECnet-10 Network Generation and Installation Procedures
describes the procedures for generating and installing
DECnet-10 software on DECsystems-1090/1091 and
DECSYSTEM-2020.
o DECnet-10 System Manager's and Operator's Guide describes the
operational, control, and monitoring facilities of DECnet-10.
o TOPS-10 Operator's Guide describes the procedure for
reloading a TOPS-10 system.
o TOPS-10 Crash Analysis Guide describes how to analyze a
crash, and how to prevent future monitor errors.
o TOPS-10/TOPS-20 Batch Reference Manual describes user
procedures for the TOPS-10 and TOPS-20 batch systems.
o TOPS-10/TOPS-20 SPEAR Manual describes the SPEAR program,
which provides a dump to help analyze a hardware errors.
|
|
|
| 1.0 MONITOR STOPCODE DEFINITION
|
| This section describes the TOPS-10 monitor stopcodes. A stopcode
| message is generated when the monitor detects a serious error in its
| database. This section describes the types of monitor stopcodes, then
| briefly explains and illustrates continuable stopcodes.
|
| When the TOPS-10 monitor encounters an internal error it issues a one-
4
| to six-character name called a stopcode name. The stopcode is
| displayed on the console terminal (CTY) and alerts you of possible
| system failure, depending on the severity of the error. The stopcode
| message is generated by a stopcode macro when the monitor detects an
| error in the database. This macro prints the following message on the
| CTY:
|
| ?Stopcode xxxyyy, Type=type, on CPUn at <date/time>
|
| Where:
|
| xxxyyy is the stopcode name.
|
| type is the type of stopcode. Stopcode types are listed
| below.
|
| n is the CPU number.
|
| date/time is the time of day and date when the stopcode occurred.
|
2.0 TYPES OF STOPCODES
The stopcodes are divided into categories, depending on the severity
of the error that cause the stopcode, and the portions of the system
that might be affected by the error. The types of monitor stopcodes
are:
1. DEBUG stopcodes indicate internal errors only. These are
continuable stopcodes.
2. JOB stopcodes indicate that the error may endanger a user
job. These are continuable stopcodes. Only the job that was
running when the stopcode occurred will be stopped.
3. STOP stopcodes indicate errors that might endanger system
operation. These are not continuable stopcodes.
4. CPU stopcodes indicate errors that prevent continued
operation of a CPU. In a single-CPU configuration, or if the
CPU that encountered the stopcode was the only CPU running at
the time, the CPU stopcode is equivalent to a STOP stopcode.
If there are other CPUs running in an SMP configuration at
the time of the stopcode, a dump is taken and the affected
CPU halts. Any job that was running on the affected CPU at
the time of the stopcode is stopped.
5. HALT stopcodes indicate fatal errors that halt the system,
and, by definition, are not continuable.
5
6. INFO stopcodes are continuable stopcodes that are generated
to inform the system operator of a system event.
The monitor generates a stopcode using the STOPCD macro. There are
several modules in the monitor, however, that use the BUG. macro to
generate a stopcode. These modules are common to both TOPS-10 and
TOPS-20. They generate three types of BUG. stopcodes, which are
equivalent to the following types of stopcodes:
BUG. Type STOPCD Type
HLT STOP
CHK DEBUG
INF INFO
2.1 DEBUG Stopcodes
A DEBUG stopcode is a stopcode that is not immediately harmful to any
job or to the system. When the monitor encounters an internal error
at the interrupt level, a dump is performed and processing continues.
The following message is printed on the CTY after the stopcode
notification:
|
[Continuing system]
2.2 JOB Stopcodes
A JOB stopcode indicates that an internal error endangers the
integrity of the job that is currently running. The monitor aborts
the current job and continues processing.
The following message is printed on the CTY after the stopcode
notification:
|
[Aborting job]
On the user's terminal, the following message is displayed:
?Monitor error at {user/exec} PC nnnnnn; UUO at {user/exec} PC
mmmmmm
Where:
nnnnnn and mmmmmm are one of the following virtual memory
locations:
6
o User location nnnnnn;
o Exec location nnnnnn; Exec called from exec location mmmmmm
o Exec location nnnnnn; Exec called from user location mmmmmm
2.3 STOP Stopcodes
A STOP stopcode indicates an internal error that endangers the
integrity of the entire system. All jobs are aborted and the
system begins to dump and reload the monitor automatically. The
monitor prints the following message on the CTY after the
stopcode notification:
|
Reload monitor
If the monitor obtains the necessary information, it prints a
supplementary message on the CTY of the form:
JOB jobn on TTYnnn running name
UUO is octal representation at user PC address
File filespec
Where:
jobn is the number of the job causing the error.
nnn is the number of the job controlling the
terminal.
name is the name of the program running for that
job.
octal is the octal representation of the monitor
representation call failing for that job.
address is the value of the program counter for that
job.
filespec is the file specification for the file being
accessed.
7
2.4 CPU Stopcodes
A CPU stopcode is handled differently, depending on the number of CPUs
in the configuration running at the time of the crash. For a
single-CPU system, a CPU stopcode has the same effect as a STOP
stopcode. When a CPU stopcode occurs on the only processor running in
a multiprocessor (SMP) system, the effect is the same as a STOP
stopcode. All user jobs are aborted and the system begins to dump and
reload the monitor automatically. The following message is printed on
the CTY of the CPU that experienced the failure, after the stopcode
notification:
Reload monitor
However, in a SMP system where more than one CPU is running at the
time of the stopcode, the CPU stopcode aborts the job currently
running, a dump is taken, and the CPU that encountered the stopcode
halts.
For SMP systems in which more that one CPU is running, the following
message is displayed on the CTY for the CPU that encountered the
stopcode:
[Stopping CPU]
If the monitor obtains the necessary information, it prints a
supplementary message on the CTY of the form:
Job jobn on TTYnnn Running name
UUO is octal representation at user PC address
File filespec
Where:
jobn is the number of the job causing the error.
nnn is the number of the job controlling the
terminal.
name is the name of the program running for that
job.
octal is the octal representation of the monitor
representation call failing for that job.
address is the value of the program counter for that
job.
filespec is the file specification for the file being
accessed.
8
2.5 HALT Stopcodes
A HALT stopcode indicates a fatal error and affects the entire system.
The monitor cannot automatically reload. The system halts, and you
must manually dump and reload the monitor. (Refer to the TOPS-10
Operator's Guide.)
HALT stopcodes generate the following message:
KL HALTED.
|
|
|
| 2.6 INFO Stopcodes
|
| An INFO stopcode is a report on a system event that may be of interest
| in debugging crashes. These stopcodes are for informational purposes
| only, and do not interrupt system or job execution.
3.0 CONTINUABLE STOPCODES
Continuable stopcodes occur when the monitor executes a STOPCD macro,
dumps the memory image, and continues the system automatically. HALT
and STOP stopcodes are not continuable. A CPU stopcode is continuable
on SMP systems where more than one CPU is running (see Section 2.4).
The following examples illustrate three continuable DEBUG stopcodes
and a JOB stopcode, as displayed on the CTY:
Example 1:
?CPU0 monitor error. Stopcode name is ICN
CPU Status Block on 30-May-86 19:29:21
CONI APR, = 001060,,004102
CONI PI, = 000000,,000777
CONI PAG, = 000000,,020000
DATAI PAG, = 500100,,000002
[Dumping on DSK:CRASH.EXE[1,4]]
[Continuing system]
Example 2:
?CPU1 monitor error. Stopcode name is EUE
Job 5 on TTY1 running DDT User [1,2]
UUO is 0 at user PC 002472
9
CPU Status Block at 4-Oct-86 8:16:36
APRID = 000231,,342002
ERA = 600000,,040513
CONI APR, = 007760,,000003
CONI PI, = 000000,,000377
CONI PAG, = 000000,,620001
DATAI PAG, = 700100,,002255
AR ARX Data Word = 000000,,057000
IO Page Fail Word = 000000,,000000
SBUS Diags:
CNTRLR FNC 0 FNC 1
000004 007040,,040610 000200,,000000
[Dumping on DSK:CRASH.EXE[1,4]]
[Continuing system]
Example 3:
?CPU1 monitor error. Stopcode name is IEZ
File DSKE0:OPSER.LOG[1,2]
Job 1 on CTY running OPSER User [1,2]
[Dumping on DSK:CRASH.EXE[1,4]]
[Continuing system]
The following example illustrates a JOB stopcode message that is
displayed on the CTY:
%DECsystem-10 not running
?CPU0 monitor error. Stopcode name is IME
Job 1 on TTY5 running FH702 User [1,2]
UUO is 47240040770 at user PC 006477
CPU Status Block on 24-Jan-86 15:06:00
APRID = 640336,364654
ERA = 024000,,006451
CONI APR, = 007760,000001
CONI PI, = 000000,,000377
CONI PAG, = 000000,,660001
DATAI PAG, = 700100,,001340
AR ARX Data Word = 000000,,000000
IO Page Fail Word = 000000,,000000
10
SBUS Diags:
CNTRLR FNC 0 FNC 1
000004 001740,,017321 000200,,000000
000010 006160,,006603 000500,,001000
[Dumping on BLUI:CRASH.EXE[1,4]]
[Aborting Job]
[DECsystem-10 Continued]
The same JOB stopcode message would also appear on the job's terminal,
in addition to the following message:
?Monitor error at user PC 006476
4.0 LIST OF MONITOR STOPCODES
A list of stopcodes for all systems that run the TOPS-10 monitor is
presented on the following pages in alphabetical order. The list
shows the name of each stopcode, the calling module, the type of
stopcode, a phrase message (for which the name is a symbol), and a
brief explanation of the containing routine, the error that caused the
stopcode, and any data items that can be helpful in analyzing dumps.
Several stopcodes are generated by both the KSSER and the KLSER
modules. For these types of stopcode, the following list uses the
module name KxSER, to indicate that the stopcode is generated by KLSER
on a KL processor and KSSER on a KS processor.
Name Module Type Message and Explanation
AAD FILFND DEBUG Access Table Already Dormant
ATNLNK unlinks an access table from a name
block (NMB) ring. This stopcode occurs when
an attempt is made to make an access table
dormant, but the table is already dormant.
Data Items: T1 = location of access table
T2 = location of predecessor
T3 = location of next in ring
AAO KxSER JOB Access Allowed Is Off
After paging a job, the monitor converts
11
virtual IOWDs into absolute IOWDs. This
stopcode occurs while checking the access
bits for a page pointed to by the IOWD, and
access to that page is not allowed.
Data Items: T1 = total number of words accumulated so far
T2 = number of words for current page
T3 = current page number within this segment
T4 = next page number within this segment (T4
is the page that was not allowed access)
ADn COMMON CPU Address Parity Error for CPU n
This stopcode occurs when Bit 29 is on in the
CONI APR. This is a serious hardware error.
Call your Field Service representative.
AES FILFND JOB Abnormal End of Search List
SLXAES is called from several places in
FILFND. This stopcode occurs for many
reasons, such as unexpectedly encountering
the end of a search list.
AHS ONCMOD STOP Already Have Structure
DMKSTR sets up structures according to tables
in ONCMOD for the DESTROY option. This
stopcode occurs when a duplicate structure
name is found in the table.
Data Items: T1 = duplicate structure name
P2 = address of structure data block
P3 = address of previous structure data block
or DIFSTR if this is the only structure
P4 = system structure number of this
structure
|
|
| ALW FILUUO JOB ACCESS TABLE LINKED WRONG.
|
|
| ANFAIB NETSER STOP No buffer set up when advancing input
|
| When attempting to finish processing the
| filling of the current user's input buffer,
| no input buffer (DEVAXI) is found to be set
| up.
12
| Data Items: F = address of DDB
|
|
| ANFAOB NETSER STOP No buffer set up when calling NTDAOB
|
| When attempting to finish processing the
| emptying of the current user's output buffer,
| no output buffer (DEVAXO) is found to be set
| up.
|
| Data Items: F = address of DDB
|
|
| ANFBLW NETSER STOP Buffer Length Wrong
|
| On a call to MKNPCB/MKUPCB to allocate an ANF
| Protocol Control Block, the length of the
| data buffer associated with the PCB did not
| match the calculated length. (The PCBs are
| stored in free lists sorted by the PCB data
| buffer size.)
|
| Data Items: U = address of PCB
| T1 = length of PCB data buffer, in words
| T2 = length PCB data buffer should be
|
|
| ANFCGM NETSER STOP Can't Get Message
|
| After a call to PCBECK returned
| "guaranteeing" the availablity of an ANF
| network Protocol Control Block, a subsequent
| call to PCBEGT to get a free PCB failed.
|
|
| ANFCIL NETSER STOP Connect Initiate message too Long
|
| An attempt was made to send a Connect
| Initiate (or possibly a Connect Confirm)
| message that exceeded the maximum
| "reasonable" size of a connect message.
|
| Data Items: F = address of DDB
| W = address of NDB
| P3 = byte count for proposed connect message
|
|
| ANFCLA NETSER STOP LAT still assigned in CLNNDB
|
| CLNNET was called to "clean up" an ANF
| network Device Data Block, but the DDB claims
| to still be connected to a remote node.
13
| (CLNNET should be called only after the
| device has been disconnected.)
|
| Data Items: F = address of network DDB
|
|
| ANFCND NETSER STOP CLNNDB has no DDB
|
| CLNNET was called to "clean up" an ANF
| network Device Data Block, but register F
| contained zero.
|
|
| ANFDDQ NETSER STOP Data Request count went negative
|
| The count of outstanding data requests
| available for a network device went negative.
|
| Data Items: F = address of DDB
|
|
| ANFDLA NETSER STOP No DLA on disconnect
|
| When disconnecting an ANF network device, a
| call to NCSDSC discovered that the DDB's
| Destination Link Address was zero.
|
| Data Items: F = address of DDB
|
|
| ANFDMU NETSER STOP Data buffer Messed Up
|
| On a call to MKNPCB/MKUPCB to allocate an ANF
| Protocol Control Block, a free PCB's data
| buffer check words were found to have been
| corrupted. The memory word immediately
| preceding the data buffer should contain
| SIXBIT/NET/ in its left half, and the memory
| word immediately following the data buffer
| should contain SIXBIT/NETMEM/.
|
| Data Items: U = address of free PCB
| T1 = contents of bottom-end check word
| T2 = contents of top-end check word
|
|
| ANFDRQ NETSER STOP Data Request count negative
|
| When processing a Data Request message for a
| device from a remote node, the current data
| request count was negative.
14
| Data Items: F = address of DDB
|
|
| ANFDRZ NETSER STOP Sending Data Requests to device 'zero'
|
| A call to NCSDRQ to send data requests to a
| remote node discovered that the network
| device's Destination Link Address field was
| zero.
|
| Data Items: F = address of DDB
|
|
| ANFDS1 NETSER STOP Can't send Disconnect message (no PCB?)
|
| After a call to PCBECK returned
| "guaranteeing" the availability of an ANF
| network Protocol Control Block, a subsequent
| call to PCBEGT to get a free PCB failed.
|
|
| ANFFCW NETSER STOP Free PCB Count Wrong
|
| The PCBSEC routine encountered a discrepancy
| in a PCB free list: the free list counter
| claimed there are no free PCBs in this
| particular list, yet the free list chain
| contains at least one free PCB.
|
| Data Items: T2 = index into NTFREC/NTFREF tables
|
|
| ANFFEK NETSER STOP FEK bad, FEKOAD and FEKOCT in conflict
|
| On a call to NETWRT/FRCWRT to queue an output
| network Protocol Control Block to an ANF
| network Front End Kontroller, the FEK output
| queue was found to be inconsistent: the
| count of output PCBs as specified by FEKOCT
| did not match the actual output queue in
| FEKOAD.
|
| Data Items: U = address of PCB
| J = address of FEK
| T3 = actual count of PCBs in FEKOAD queue
|
|
| ANFGFK NETSER STOP Garbage FEK pointer
|
| Some routine attempted to convert an ANF
| network Front End Kontroller (data block)
| address into a logical line number, but the
15
| FEK address in not in the FEK chain (that is,
| the FEK does not exist).
|
| Data Items: J = address for non-existant FEK
|
|
| ANFIFC NETSER STOP Illegal FEKINT function code
|
| An ANF network Front End Kontroller called
| NETSER's FEK interrupt service (FEKINT) with
| an illegal function code in T1.
|
| Data Items: J = address of FEK
| T1 = FEK interrupt function code
|
|
| ANFINP NETSER STOP Input done interrupt with no input buffer
|
| An ANF network Front End Kontroller called
| NETSER's FEK interrupt service (FEKINT) to
| process an "input done" interrupt yet had no
| ANF network Protocol Control Block specified
| in either FEKIDN or FEKIAD (depending on the
| interrupt function code).
|
| Data Items: J = address of FEK
|
|
| ANFLAA NETSER STOP LAT Already Assigned
|
| When attempting to establish a connection to
| a remote device's node, the Device Data Block
| was found to already have a Link Address
| Table entry.
|
| Data Items: F = address of DDB
| T1 = LAT address
|
|
| ANFLAT NETSER STOP DDB and LAT don't agree
|
| When freeing up an ANF network Device Data
| Block, a call to GIVSLA discovered that the
| DDB's link address did not match the network
| Link Address Table. (The LAT entry did not
| point back to the DDB which points to the LAT
| entry.)
|
| Data Items: F = address of DDB
| P2 = DDB's link address (index into LAT)
16
| ANFLCC NETSER STOP Not in confirm wait -- LAT table messed up
|
| While waiting for a Connect Initiate message
| to be answered, the Link Address Table state
| for the device transited into an illegal
| state (a state that was neither success, nor
| failure, nor still-waiting).
|
| Data Items: F = address of DDB
| T1 = LAT state
|
|
| ANFLDD NETSER STOP LAT and DDB disagree
|
| When disconnecting an ANF network device, a
| call to NCSDSC discovered that the DDB's link
| address did not match the network Link
| Address Table. (The LAT entry did not point
| back to the DDB which points to the LAT
| entry.)
|
| Data Items: F = address of DDB
|
|
| ANFMBL NETSER STOP Buffer length wrong
|
| On a call to RMVPCB to free up an ANF network
| Protocol Control Block, the PCB data buffer
| length was found to be too large (larger than
| the maximum allowable data buffer size).
|
| Data Items: U = address of PCB
| T2 = PCB data buffer length, modulo MSGAGW
|
|
| ANFMDL NETSER STOP Must have a DLA assigned
|
| While trying to format an ANF network output
| message header, a device was found to have no
| Destination Link Address set.
|
| Data Items: F = address of DDB
| U = address of PCB
|
|
| ANFMRL NETSER STOP Message Request too Large
|
| A call was made to the MKNPCB/MKUPCB
| routine(s) to allocate an ANF network
| Protocol Control Block (data buffer) which
| exceeded the maximum configured message size.
17
| Data Items: T1 = requested PCB size, in words
|
|
| ANFMSQ NETSER STOP Message queues are screwed up
|
|
| ANFNCT NETSER STOP NCT processors shouldn't skip
|
| An internal-to-NETSER message processing
| routine took a "skip" return, which should
| never happen.
|
| Data Items: U = probably an address of a PCB
|
|
| ANFNFI NETSER STOP Sending Node ID to the null FEK
|
| An attempt was made to send an ANF Node ID
| message to the null Front End Kontroller.
| The null FEK never goes offline, and so
| should never come online, and so should never
| need to be greeted with a Node ID message.
|
| Data Items: J = address of FEK
|
|
| ANFNFK NETSER STOP This is the null FEK
|
| The monitor received and processed a Node ID
| message from the null Front End Kontroller.
| Since NETSER never sends a Node ID over the
| null FEK, it should never receive one.
|
|
| ANFNFP NETSER STOP No free PCBs or no free messages
|
| After a call to PCBECK returned
| "guaranteeing" the availability of an ANF
| network Protocol Control Block, a subsequent
| call to PCBEGT to get a free PCB failed.
|
|
| ANFNIL NETSER STOP Not at Interrupt Level
|
| The main ANF network service loop NETSCN was
| called at a level other than interrupt level.
|
|
| ANFNNT NETSER STOP No NDB for Terminal
|
| In the process of disconnecting a network
| terminal, no Node Data Block can be found to
18
| match the remote node number as specified in
| the terminal's LDB (LDPRNN pointer).
|
| Data Items: U = address of terminal LDB
|
|
| ANFNPL NETSER STOP No PCBs on List
|
| A call was made to CLNFEK to "clean up" and
| reinitialize an ANF network Front End
| Kontroller (data block). The count of queued
| transmit Protocol Control Blocks (contained
| in FEKOCT) did not match the actual output
| PCB chain (starting with FEKOAD).
|
| Data Items: J = address of FEK
|
|
| ANFNUL NETSER STOP Null FEK being "cleaned"
|
| A call was made to CLNFEK to "clean up" and
| reinitialize an ANF network Front End
| Kontroller (data block), but the specified
| FEK was the so-called null FEK, which should
| never go offline.
|
| Data Items: J = address of FEK
|
|
| ANFNWA NETSER STOP Node Went Away
|
| When disconnecting an ANF network device, a
| call to NCSDSC discovered that the device's
| remote node "went away" (the node is no
| longer in communication with the local host).
| In this case, the device service routine
| should have simply destroyed the DDB, rather
| than trying to disconnect it first (for
| example, just call ZAPNET).
|
| Data Items: F = address of DDB
|
|
| ANFOBS NETSER STOP Obsolete feature
|
| On a call to ZAPPCB to deallocate (and return
| to the monitor's general purpose free pool)
| an ANF network Protocol Control Block, a PCB
| was found to own a "secondary" data buffer
| (in addition to the primary data buffer), a
| feature no longer in use.
19
| Data Items: U = address of PCB
|
|
| ANFOUT NETSER STOP Output done interrupt with no PCB
|
| An ANF network Front End Kontroller called
| NETSER's FEK interrupt service (FEKINT) to
| process an "output done" interrupt, yet had
| no ANF network Protocol Control Block address
| in FEKODN.
|
| Data Items: J = address of FEK
|
|
| ANFPCC NETSER STOP Count of PCBs on list is wrong
|
| A call was made to CLNFEK to "clean up" and
| reinitialize an ANF network Front End
| Kontroller (data block). The count of queued
| transmit Protocol Control Blocks (contained
| in FEKOCT) did not match the actual output
| PCB chain (starting with FEKOAD).
|
| Data Items: J = address of FEK
|
|
| ANFPCL NETSER STOP PCB lists screwed up
|
| On a call to MKNPCB/MKUPCB to allocate an ANF
| Protocol Control Block, the PCB "free"
| list(s) were found to be inconsistent. The
| PCB free pool consists of linked lists
| (sorted by PCB size) of unused (and therefore
| available to be re-used) free PCBs. The
| count of free PCBs disagrees with the length
| of the linked list of free PCBs.
|
| Data Items: U = address of (alleged) free PCB
| T2 = index into NTFREC/NTFREF linked list
| table
|
|
| ANFPCM NETSER STOP PCB data buffer check words trashed
|
| On a call to RMVPCB to free up an ANF network
| Protocol Control Block, the PCB data buffer
| check words were found to be corrupted. The
| memory word immediately preceding the data
| buffer should contain SIXBIT/NET/ in its left
| half, and the memory word immediately
| following the data buffer should contain
| SIXBIT/NETMEM/.
20
| Data Items: U = address of PCB
| T1 = contents of bottom-end check word
| T2 = contents of top-end check word
|
|
| ANFPCR NETSER STOP PCB tag word trashed
|
| On a call to RMVPCB to free up an ANF network
| Protocol Control Block, the PCB was found to
| be corrupted, either the PCBTAG word did not
| contain SIXBIT/PCBTAG/, or the PCB data
| buffer length was not a proper size (in
| particular, was not a multiple of the MSGAGW
| allocation "granularity").
|
| Data Items: U = address of PCB
| T1 = contents of PCBTAG word
| T2 = length of PCB data buffer
|
|
| ANFPCT NETSER STOP PCB trashed
|
| On a call to MKNPCB/MKUPCB to allocate an ANF
| Protocol Control Block, an unused PCB removed
| from the PCB free lists was found to contain
| junk in the PCBTAG check word (which should
| contain SIXBIT/PCBTAG/).
|
| Data Items: U = address of unused PCB
| T1 = contents of PCBTAG word
|
|
| ANFPCV NETSER STOP PCB not valid
|
| On a call to NETWRT/FRCWRT to queue an output
| network Protocol Control Block to an ANF
| network Front End Kontroller, the PCB check
| word was found to be corrupted. The PCBTAG
| word of the PCB should contain
| SIXBIT/PCBTAG/.
|
| Data Items: U = address of PCB
| J = address of FEK
|
|
| ANFRDN NETSER STOP Routing header has bad Destination Node
|
| When processing a just-received ANF network
| message, the destination node number (as
| specified in the message) did not match the
| local host node number.
21
| Data Items: U = address of PCB
| W = address of NDB which sent the message
| P1 = current byte pointer into PCB data
| buffer
|
|
| ANFRDT NETSER STOP Releasing DDB twice
|
| ZAPNET was called to release an ANF network
| Device Data Block, but the DDB is already
| marked as having been cleared (and has been
| returned to the monitor free pool).
|
| Data Items: F = address of network DDB
|
|
| ANFRSN NETSER STOP Routing header has bad Source Node
|
| When processing a just-received ANF network
| message, the source node number (as specified
| in the message) did not match the remote node
| number from the ANF network Node Data Block
| from which this message was de-queued.
|
| Data Items: U = address of PCB
| W = address of NDB which sent the message
| P1 = current byte pointer into PCB data
| buffer
|
|
| ANFSBA NETSER STOP Secondary Buffer Allocated ("old feature")
|
| On a call to RMVPCB to free up an ANF network
| Protocol Control Block, a PCB was found to
| own a "secondary" data buffer (in addition to
| the primary data buffer), a feature no longer
| in use.
|
| Data Items: U = address of PCB
|
|
| ANFSLA NETSER STOP SLA on a connect
|
| On a call to NCSCNT to send a Connect
| Initiate message (or possibly from NCSCNC to
| send a Connect Confirm message) to a remote
| node for a device, the network Device Data
| Block had no Source Link Address.
|
| Data Items: F = address of DDB
| W = address of NDB
22
| ANFTLK NETSER STOP W points at NETNDB (talking to itself)
|
| An illegal operation was detected directed at
| the Node Data Block for the local host. For
| example, an attempt was made (in CLNNDB) to
| delete the NDB as no longer reachable on the
| network.
|
| Data Items: W = address of NDB
|
|
| ANFTMF NETSER STOP Too Many FEKs
|
| When rebuilding the neighbor's table (for
| sending Neighbors messages to other nodes),
| there were more than NGHMAX Front End
| Kontrollers (neighbors).
|
| Data Items: J = address of FEK
| T1 = node number of FEK neighbor
|
|
| ANFUBN NETSER STOP Unsent Byte count went Negative
|
| When processing the segmentation of a user
| output buffer, the count of bytes remaining
| to be transmitted (DEVAXO+1) went negative.
|
| Data Items: F = address of DDB
|
|
| ANFUND NETSER STOP Unreasonable Network DDB length
|
| The MAKDDB routine was called to create an
| ANF network Device Data Block with an
| "unreasonable" DDB size (either smaller than
| the minimum DDB length, or much (10 octal
| words) bigger).
|
| Data Items: T2 = requested DDB size, in words
|
|
| ANFWLA NETSER STOP Wrong LAT Assigned
|
| A call to GETSLA to assign a free link
| address from the Link Address Table was made
| with an ANF network Device Data Block or a
| terminal Line Data Block that was already in
| the link address table.
|
| Data Items: T1 = address of DDB or LDB
23
| ANFWLS NETSER STOP Wrong LAT State
|
| When processing a RELEASe monitor call for an
| ANF network device, the device was found to
| already be disconnected when its Link Address
| Table entry state claimed to be "OK".
|
| Data Items: F = address of DDB
| S = DEVIOS flags (IOSCON clear)
| T2 = LAT state
|
|
| ANFWMB NETSER STOP User Wrote in Memory before Block
|
| On a call to GIVZWD to deallocate a block of
| NETSER memory and return it to the monitor's
| general purpose free pool, the top-end check
| word was found to be corrupted. The left
| half of the word immediately preceding the
| memory block should contain SIXBIT/NET/.
|
| Data Items: T1 = LH contents of top-end check word
| T2 = (adjusted) address of memory block
| -1(P) = (adjusted) length of memory block
|
|
| ANFWPE NETSER STOP User Wrote Past the End of the block
|
| On a call to GIVZWD to deallocate a block of
| NETSER memory and return it to the monitor's
| general purpose free pool, the bottom-end
| check word was found to be corrupted. The
| word immediately after the memory block
| should contain SIXBIT/NETMEM/.
|
| Data Items: T1 = LH contents of top-end check word
| T2 = contents of bottom-end check word
| 0(P) = (adjusted) address of memory block
| -1(P) = (adjusted) length of memory block
|
|
| ANFXDS NETSER STOP Can't send Disconnect message (no PCB?)
|
| After a call to PCBECK returned
| "guaranteeing" the availability of an ANF
| network Protocol Control Block, a subsequent
| call to PCBEGT to get a free PCB failed.
|
|
| ANFXMT NETSER STOP No buffer set up when calling NTDXMT
|
| When processing an output buffer from a user
24
| program, NTDXMT found no output buffer
| pointer (DEVAXO) set up.
|
| Data Items: F = address of DDB
|
|
| ANFZFK NETSER STOP Zero FEK pointer
|
| An ANF network Front End Kontroller called
| NETSER's FEK interrupt service (FEKINT) with
| no FEK address in J.
ANU FILIO DEBUG AU Not Owned By Us
UPAU obtains the Alter-UFD (AU) resource.
This stopcode occurs when there is no UFD
data block (UFB) for the given DDB or a job
returns an Alter-UFD (AU) resource that is
already owned by someone else.
Data Items: P1 = 0 if no UFB, otherwise the UFB for DDB
P2 = not applicable if no UFB, otherwise job
number trying to release the AU resource
UFBAUJ(P1) = job owning the AU resource
AOC FILFND DEBUG Already Own CB
GETCB gets the core block (CB) resource.
This stopcode occurs when a job requests the
CB resource, but already owns it.
Data Items: J = job number
APF VMSER DEBUG Allocated Page Free
This stopcode occurs when the monitor finds
an unallocated page of memory in the list of
pages allocated to a segment.
Data Items: P2 = disk address-1
P3 = current physical page allocated
P4 = number of pages
T3 = byte pointer to the map slot
AR1 ONCMOD DEBUG ASKDEC Returned CPOPJ1
CHGASL changes the active swapping list.
This stopcode occurs when the routine to
25
input a decimal number returns POPJ1.
ARF CORE1 STOP Attempt To Return Free Page
GVPAGS returns pages to the free-core list.
This stopcode occurs when the monitor checks
its table of free pages before returning a
page and finds that the page is already
marked as being free.
Data Items: T1 = first page on free-core list
T2 = page being returned to the free-core
list (this is the page that caused the
stopcode)
T3 = number of pages returned so far
T4 = bit being tested in the page table
(400000,,0) PAGTAB(T2) = page-status bits
(status-bit definitions can be found in
module S.MAC)
ARM FILFND DEBUG Access Rings Messed Up
ATNLNK unlinks an access table from a name
block ring. This stopcode occurs when an
access ring is not linked to any access
table.
BAC CORE1 DEBUG Bit Already Clear
SETZRS sets zeros in a table. This stopcode
occurs when the SETZRS routine attempts to
zero bits that are already zero.
Data Items: T2 = still on the stack = AOBJN pointer to
tables
T1 = number of bits to clear
BAD FILFND JOB Block Already Dormant
ATSFR0 puts an access table in the free-core
list. This stopcode occurs when an attempt
is made to make the access table dormant, but
the table is already dormant.
Data Items: T1 = location of access table
BAO FILIO DEBUG Bit Already One
26
TAKBLK allocates blocks from the disk. This
stopcode occurs when the monitor attempts to
allocate a block that is already allocated.
Data Items: PDL = cluster address.
BAZ FILIO DEBUG Bit Already Zero
GIVBLK returns disk blocks. This stopcode
occurs when the monitor attempts to return
blocks that are already free; this can occur
when a damaged file is deleted. If this
stopcode occurs with any frequency, it is
suggest you run DSKRAT on the structure
indicated in the stopcode printout on the
CTY.
BBS D85INT STOP Bad Byte Size
DLBP makes the DL10 the byte pointer for
data. This stopcode occurs when the number
of bytes per word supplied is illegal. The
number of bytes per word must be from 2 to 6.
Data Items: T4 = wrong byte size
| BEC MSCCOM DEBUG Packet with bad end code received
BFC D60SER DEBUG Bad Function Code
The front end controller received a bad
function code. This is a monitor error.
BFO TAPUUO DEBUG Better Find One
INVERT generates a transfer list for a read
backwards. This stopcode occurs when the end
of the original transfer list for a read
backwards is not found.
Data Items: T2 = head of old transfer list
T3 = item number to find
BIN FILIO STOP Block Number is Negative
MONRED reads a block or a series of blocks.
27
This stopcode occurs when this routine is
called with a negative block number.
Data Items: T1 = IOWD for data
T2 = block number
BMR FILUUO JOB Block Missing from RIB
ALLP0A is used to work with a RIB whose
blocks are allocated but not used. This
stopcode occurs when the RIB for a file shows
that the file has more blocks than actually
exist.
Data Items: T3 = missing block
BNR FILUUO JOB Block Not RIB
NOTOLD creates a new name in a directory
block. This stopcode occurs when a pointer
to a block is not found in the RIB.
Data Items: P2 = block that is being looked for
BNT FILFND DEBUG Block Not There
UFORSS gets a UFD or an SFD access block.
This stopcode occurs when a core block (AT or
UFB) that is known to exist is not found.
BNZ CORE1 DEBUG Bit Not Zero
CSETOS sets bits in a table. This stopcode
occurs when one of the bits to be set in a
table is already set.
Data Items: T3 = number of bits to set
T4 = address,,position
BPE CLOCK1 JOB Breakpoint PC EXEC Mode
The user PC on a control-D to a DDT
unsolicited breakpoint trap did not have the
USRMOD bit, although the user was supposed to
be in user mode.
Data Items: T1 = PC word that the user is currently
28
running
BPF CLOCK1 JOB Breakpoint PUTWRD failed
The attempt to store the return PC (in
processing an unsolicited ^D breakpoint) into
the location pointed to by .JBBPT failed even
though the address had been previously
address checked.
BPT FILFND JOB Bad Search List Pointer
SLXBPT is used only for this stopcode and is
called from FILUUO. This stopcode occurs
when an attempt is made to build the search
list, but no search list can be found.
BRC COMCON DEBUG Bad Return from CMPBIT
SAVEXE saves a virtual memory system core
image. This stopcode occurs when the routine
that computes the flag bits for a directory
entry gives an error return.
BSN SEGCON STOP Bad Segment Number
COMIT compares the job number with the right
half of JBTSGN(T1). This stopcode occurs
when the right half of J and the right half
of JBTSGN(T1) are not the same.
Data Items: T1 = high-segment number of job
J = job number
BSY XTCSER DEBUG DA28 Busy
The BUSY bit was (still) on when the DA28
interrupted.
BWA FILIO JOB Block Went Away
SETLST sets up an I/O list block. This
stopcode occurs when NXTBLK, which is used to
return the next block address, gives an error
or a non-skip return that indicates
end-of-file, writing in the middle of a file,
29
or another similar error.
Data Items: J = job number
|
|
| CAM CPNSER CPU CPU accessability mask
|
| A device that can do I/O with only one CPU is
| owned by more than one CPU.
|
|
| CAO FILUUO DEBUG Cluster Address Odd
|
| ADJALC allocates the initial blocks for a
| file. This stopcode occurs when a block
| supercluster address is not an even multiple
| of a block cluster address.
|
| Data Items: T1 = number of blocks in group
| P2 = remainder
|
|
| CAS REFSTR STOP Couldn't Allocate Space
|
| This stopcode is always preceded by one of
| the following messages, which explains why
| space could not be allocated:
|
| Bad block in HOME.SYS space.
|
| File structure full, suggest reducing
| swapping space.
|
|
| CBB COMCON DEBUG Command Block Bad
|
| In copying the program-to-run information
| from a user defined command block to the
| SAVGET locations, it was found that the
| command block was too big to fit.
|
|
| CCR CLOCK1 STOP Can't continue with resource
CDn COMMON CPU Cache Directory Parity Error, CPU n
This is a serious hardware error. Call your
Field Service representative.
CDA FILIO DEBUG In-Core Copy Doesn't Agree
30
DD2MN copies pointers from a DDB to a monitor
buffer to perform monitor I/O. This stopcode
occurs when the cluster pointer from the
structure data block does not agree with the
in-core copy.
Data Items: T1 = in-core copy
T4 = pointer from structure data block
CDD MSGSER DEBUG Can't Disconnect Device
This stopcode occurs when a release call on
MPX fails because the disconnect format is
invalid or the device is not connected.
|
|
| CDRASC NETDEV STOP NTDSIB failed in C.ASCI
|
| After calling NTDIBA to guarantee a user
| input buffer is available, the ANF network
| card reader service routine was unable to set
| up an input buffer to receive a network
| message.
|
| Data Items: F = address of DDB
| U = address of PCB
|
|
| CDRBIN NETDEV STOP NTDSIB failed in C.BIN
|
| After calling NTDIBA to guarantee a user
| input buffer is available, the ANF network
| card reader service routine was unable to set
| up an input buffer to receive a network
| message.
|
| Data Items: F = address of DDB
| U = address of PCB
|
|
| CDRIMG NETDEV STOP NTDSIB failed in C.IMAG
|
| After calling NTDIBA to guarantee a user
| input buffer is available, the ANF network
| card reader service routine was unable to set
| up an input buffer to receive a network
| message.
|
| Data Items: F = address of DDB
| U = address of PCB
31
CFP CLOCK1 JOB Can't Find PDB
SETRUN sets the job-status run bit. This
stopcode occurs when there is no process data
block (PDB) for this job.
Data Items: J = job number
CGS ONCMOD STOP Couldn't Get Structure Data Block
DMKSTR sets up structures according to tables
in ONCMOD in the DESTROY option. This
stopcode occurs when the maximum number of
structures is exceeded.
Data Items: .FSMAX = maximum number of structures allowed
T1 = structure name
P3 = address of last structure data block
P4 = system structure number for this
structure
CI7 UUOCON DEBUG CI7 Continuable Snapshot Dump
A user requested continuable snapshot dump
was requested (CONFIG program SNAPSHOT
command. See TOPS-10 Operator's Guide.)
CIB CLOCK1 CPU CPU Interlocks Broken
APRSUB services common APR interrupts. This
stopcode occurs when the CPU interlock has
been modified. Typically, the stopcode
occurs while trying to continue a CPU that
has stopped due to a fatal error.
Data Items: .CPNBI = CPU interlock that was modified
CIF FHXKON DEBUG RC10 Isn't Fancy
This stopcode occurs when the monitor
attempts an RP04-only function on an
RC10-controlled device.
CIO REFSTR DEBUG CPF Is Odd
COMCFP computes a CFP. This stopcode occurs
when the number of blocks per supercluster is
32
not a multiple of the number of blocks per
cluster.
CL0 SCNSER STOP Chunk Links to 0
DELCHR deletes characters from the user's
input buffers when he presses the RUBOUT or
DELETE key. This stopcode occurs when a TTY
chunk has a backward link to 0.
Data Items: T2 = current chunk
CME FILFND DEBUG CFP Modulo Error
SETCFP computes a CFP. This stopcode occurs
when CFP does not start at an even
supercluster boundary.
Data Items: T2 = supercluster address relative to block 0
of unit
T3 = remainder
CMP LOKCON STOP Can't Move Page
In attempting to move pages out of a block of
memory that is being set off-line, routine
PAGFRE discovered that the free page into
which we were trying to move a page was not
really free.
Data Items: P2 = target (free) page
CMS VMSER DEBUG CORE1 Must Skip
SEGCON returns core allocated to a
nonsharable high segment. This stopcode
occurs when CORE1 gives a nonskip return when
asked for core in use.
CMU SEGCON DEBUG Core Messed Up
CHKTAL compares CORTAL with a value obtained
from various job tables. This stopcode
occurs when the core usage tables are
inconsistent.
Data Items: U = free+idle+dormant
33
CORTAL = bit table
CNA SCHED1 STOP Core Not Available
SWAPI swaps in a job or high segment. This
stopcode occurs when an error return is given
by the core-allocation routine (CORGET),
which indicates that no core is available,
although it has already been verified that
enough core is available.
Data Items: J = job number
CNE FILUUO DEBUG Cluster Not Even
ADJALC allocates the initial blocks for a
file. This stopcode occurs when the block
computed as the start of a supercluster does
not begin at an even supercluster address.
Data Items: T2 = starting block number
|
|
| CQO CLOCK1 STOP Clock queue overflowed at some time.
CRH REFSTR DEBUG Cannot Read Home Blocks
REFSTR refreshes a file structure. This
stopcode occurs when the routine used to read
home blocks (GTHOM) gives an error return.
|
|
| CRM RAXKON DEBUG Command reference number missing
|
|
| CRU MSCCOM DEBUG Command reference number unknown
CSA COMCON DEBUG Couldn't Set Access Allowed
SETAA sets the access-allowed bit for a page.
This stopcode occurs when the PAGE monitor
call function to set access allowed fails.
|
|
| CSB ONCMOD STOP Crosses section boundary
CSE FILIO STOP Checksum Error
34
CHKSUM computes a folded checksum from the
first data word. This stopcode occurs when
the pointer for checksumming points to a word
that is not in the user's address space.
Data Items: RH(M) = address that caused the error; J =
job number
|
|
| CSF RAXKON DEBUG Connect to MSCP server failed
CSP SEGCON JOB Cannot Store Path
STONAM is used during SAVE, GET, R, and RUN
commands to search a path. This stopcode
occurs when there is not enough free core to
store the full path specification.
Data Items: T2 = number of words available
|
|
| CTHBCM NRTSER INFO Bad configuration message
|
|
| CTHIBO NRTSER STOP CTERM host input buffer overflow
|
|
| CTHOCE NRTSER STOP Output count exceeded
|
|
| CTHPED NRTSER INFO Protocol error detected
|
| CTERM protocol is not followed by process at
| source node.
|
|
| CTHPER NRTSER INFO Protocol error reported
|
| CTERM protocol is not followed by process
| running on TOPS-10 node.
|
|
| CTX CTXSER JOB Context skew
|
|
| CTXFWA CTXSER STOP CTXMIG's first context went away
|
|
| CTXMCT CTXSER STOP CTXMIG called twice
35
| CTXNIP CTXSER STOP Context migration not in progress
CU0 NETDEV STOP Can't Use Zero Dispatch
This stopcode occurs when an attempt is made
to use a zero dispatch in the SCNSER dispatch
table. A zero dispatch is illegal.
CWN NETSER DEBUG Core Allocation Went Negative
GIVZWD returns monitor free core. This
stopcode occurs when GIVZWD attempts to
return more free core than it has.
Data Items: core allocation count
-1(P) = number of words returned
|
|
| D78BI D78INT JOB Bad IOWD
|
|
| D78IN0 D78INT JOB Input character count non-0
|
|
| D78NC D78INT JOB Not enough free monitor core
|
|
| D78ON D78INT JOB Output character count is not equal to 0.
|
|
| D78PI D78INT JOB Positive IOWD
|
|
| D78VI D78INT DEBUG Version incorrect
|
|
| DA28B XTCSER DEBUG DA28 is broken
DBZ FILIO DEBUG DEPLPC Bit Zero
USETO0 does a USETO. This stopcode occurs
when the last group of pointers for a file is
not the last group in the RIB; there should
be more file pointers.
Data Items: W = last block allocated
T3 = last pointer in core flag
36
| DC75WE D85INT DEBUG DC75 wrong PDP11 code
|
|
| DC76MS D76INT DEBUG DC76 message is short
|
|
| DC76QF D76INT DEBUG DC76 queue full
DCR FILUUO DEBUG DELRIB CPOPJ Return
CLSDL1 deletes a file. This stopcode occurs
when DELRIB does not skip, even though it
should always give a skip return.
|
|
| DDN MSCCOM DEBUG Driver dispatch address not setup
|
|
| DDPAHB NETDEV DEBUG Already have receive buffer
|
| An ANF DDP "kontroller" dispatch function
| call was made to post a new receive buffer,
| but the DDP already had a buffer pending.
|
| Data Items: F = address of DDB
|
|
| DDPALA NETDEV STOP Destination allocated address is zero
|
| When trying to process an input message from
| a DDP in "kontroller" mode, the DECnet
| message block format was invalid. (The
| Message Segment Descriptor allocated address
| was zero.)
|
|
| DDPBAU NETDEV STOP Being awfully uncooperative!
|
| After making an ANF DDP device into a
| "kontroller", DECnet subsequently rejected
| the new "kontroller".
|
| Data Items: F = address of DDB
|
|
| DDPBBM NETDEV STOP Bad output message block
|
| When trying to process an output message for
| a DDP in "kontroller" mode, the DECnet
| message block format was invalid. (There was
| no first Message Segment Descriptor block.)
37
| Data Items: F = address of DDB
| P1 = address of DECnet message block
|
|
| DDPBCD NETDEV STOP Byte copy didn't
|
| When trying to process an input message from
| a DDP in "kontroller" mode, the EXTEND/MOVSLJ
| instruction to copy the data from the ANF
| Protocol Control Block into the DECnet
| Message Segment Descriptor block failed.
|
|
| DDPFIX NETDEV STOP This needs to be fixed
|
| When servicing an ANF DDP device output
| queue, no Node Data Block could be found for
| the node that owns the DDP device.
|
| Data Items: F = address of DDB
|
|
| DDPFNC NETDEV STOP Illegal kontroller function call
|
| The ANF DDP "kontroller" dispatch routine was
| called with an illegal or unknown kontroller
| function code.
|
| Data Items: T1 = kontroller function code
|
|
| DDPIDV NETDEV STOP Illegal driver number
|
| The DDP service routine tried to dispatch to
| a unknown or illegal higher-level driver
| type.
|
|
| DDPIOT NETDEV DEBUG Illegal Owner Type
|
| The DDP service routine tried to dispatch to
| a unused or illegal higher-level driver type.
|
|
| DDPKON NETDEV STOP Can't make a kontroller out of DDP
|
| The DDPCKN routine was unable to set an ANF
| DDP device into "kontroller" mode on a
| DDP-initiated connect cycle.
|
| Data Items: F = address of DDB
38
| DDPMTB NETDEV STOP DDP Message Too Big for driver
|
| When running in "kontroller" mode, a message
| was received which was too big to give to the
| associated higher-level driver routine.
|
|
| DDPNDA NETDEV STOP No allocated data address
|
| When trying to process an output message for
| a DDP in "kontroller" mode, the DECnet
| message block format was invalid. (A Message
| Segment Descriptor had no data buffer
| address.)
|
| Data Items: F = address of DDB
| P1 = address of DECnet MSD
|
|
| DDPNDT NETDEV STOP No NDT entry
|
| The Network Device Table entry in the system
| NDTTAB table for the DDP-class device was
| zero.
|
|
| DDPRBA NETDEV DEBUG Receive Buffer already Allocated
|
| On an ANF DDP "kontroller" dispatch function
| call to "OPEN" (or initialize) a DDP
| kontroller or circuit, the kontroller (DDP
| device) already had a receive buffer
| outstanding.
|
| Data Items: F = address of DDB
|
|
| DDPRDQ NETDEV STOP NTDRDQ failed
|
|
| DDPSE0 NETDEV STOP Not in Section 1
|
| The DDP service routine was not running in
| Section 1, and thus could not call its
| higher-level driver routine.
|
|
| DDPSIB NETDEV STOP NTDSIB failed after NTDIBA succeeded
|
| After calling NTDIBA to guarantee a user
| input buffer is available, the ANF network
| DDP service routine was unable to set up an
39
| input buffer to receive a network message.
|
| Data Items: F = address of DDB
| U = address of PCB
|
|
| DDPSLJ NETDEV STOP Couldn't move the sludge
|
| When trying to process an output message for
| a DDP in "kontroller" mode, an EXTEND/MOVSLJ
| instruction failed in copying bytes from the
| DECnet message block into an ANF network
| Protocol Control Block.
|
| Data Items: F = address of DDB
|
|
| DDPXMT NETDEV STOP NTDXMT failed, not running out of freecore
|
| A call to NTDXMT to output a user buffer to
| an ANF DDP device failed for some reason
| other than a lack of available network
| Protocol Control Blocks to hold the message.
|
| Data Items: F = address of DDB
DDS FILUUO DEBUG DELRIB Didn't Skip
BADUFD deletes a file. This stopcode occurs
when DELRIB does not skip, even though it
should always give a skip return.
DER FILUUO DEBUG DELRIB Error Return
CLSFUL is used when there is no space on a
structure or all pointer slots are taken.
This stopcode occurs when DELRIB does not
skip, even though it should always give a
skip return.
DFU COMNET DEBUG Device Unrecognized
DSPOBJ dispatches on the object type. This
stopcode occurs when the specified device is
not on the network.
Data Items: T4 = object type
DEVCHR(F) = device characteristics
40
DHA FILIO DEBUG Don't Have AU Resource
DWNAU releases the Alter-UFD resource. This
stopcode occurs when this file attempts to
return the AU resource when it does not own
it.
Data Items: S = should have had IOSAW(200000) set
DHD FILIO DEBUG Don't Have DA
DWNDA returns the DISK ALLOCATION queue.
This stopcode occurs when this file does not
own the DA resource.
Data Items: PJOBN = job number
|
|
| DIEBAD ERRCON STOP Bad PC in DIE
|
|
| DMO COMMON STOP DECnet core and monitor overlap
|
| On a KS10, the core allocated for DECnet data
| base and the monitor low segment overlap.
| Rebuild the monitor, specifying fewer jobs,
| fewer terminals, or both.
|
|
| DN60DD D6SINT DEBUG PDP11 tried to give us to much
|
|
| DN60DI D6SINT DEBUG Not expecting a To-10 done interrupt
|
|
| DN60ID D6SINT DEBUG PDP11 is trying to give
|
|
| DN60VI D6SINT DEBUG DN60 wrong PDP11 code
DNF FILUUO DEBUG DDB Not Found
CLRDDB clears a disk data block (DDB). This
stopcode occurs when an attempt is made to
return a DDB, but no predecessor DDB is
found.
Data Items: F = location of DDB
DNR FILUUO DEBUG DELRIB Non-Skip Return
41
SETEN5 is used when the RIB is set up to
insert constant values and write them out.
This stopcode occurs when DELRIB does not
skip, even though it should always give a
skip return.
DNS FILUUO DEBUG DELRIB Non-Skip Return
CLOSR2 is called by CLRSTS when a rename is
in progress at the time of a delete. This
stopcode occurs when DELRIB does not skip,
even though it should always give a skip
return.
DOC FILFND DEBUG Don't Own CB
GVCBJ returns the CB resource for a job.
This stopcode occurs if GVCBJ is called, but
the job does not own the CB resource.
DOM CORE1 STOP Don't Own MM Resource
On a multiprocessor KL, the processor that
wishes to manipulate pages in memory must own
the memory-management resource before it can
do so. This stopcode occurs when a processor
tries to manipulate memory pages and does not
own the memory-management resource. This
resource can also be owned by a job.
Data Items: If the CPU owns the MM resource, INTLMO is
the APRID of the CPU. If a job owns the
resource, .CPJOB contains the job number (in
this case, MMUSER is the job that owns the MM
resource).
DPL COMCON DEBUG Directory Page Lost
GTSAVP reads in a page that was output
earlier. This stopcode occurs either when
the page already exists or when an I/O error
occurs.
DPN COMCON DEBUG Directory Page Nonexistent
RELDIR gets rid of the directory page and
restores any pages that were written out
42
earlier, after it creates the directory.
This stopcode occurs when a PAGE. monitor
call with a function of 1 fails.
DQR DZINT DEBUG Illegal Queue Routine
The address of the routine to transfer to on
dataset timeout for a DZ-11 line was zero.
|
|
| DSS VMSER DEBUG DLTSP Skipped
|
| CLRSPG clears spy pages from a user's map
| when called by GETMIN. This stopcode occurs
| when CLRSPG cannot clear a spy page.
|
| Data Items: T1 = user virtual page number of page
|
|
| DTEAHB DTESER DEBUG Already have receive buffer
|
|
| DTEARD DTESER STOP Runaway driver
|
|
| DTEBAA DTESER STOP Buffer already there
|
|
| DTEBDN DTESER STOP Bad device number
|
|
| DTEBMB DTESER DEBUG Bad message block pointer
|
|
| DTEBTC DTESER DEBUG Bad transfer count(s)
|
|
| DTECDF DTESER STOP Copy data failed
|
|
| DTECOW DTESER STOP Called for output on wrong CPU
|
|
| DTEDNE DTESER STOP Count not even
|
|
| DTEDNH DTESER STOP Driver not hungry
|
|
| DTEDWA DTESER DEBUG DDB went away?
43
| DTEDWC DTESER DEBUG DTECLR called on wrong CPU
|
|
| DTEEFI DTESER STOP Illegal function code
|
|
| DTEFNG DTESER STOP Illegal function code
|
|
| DTEI1S DTESER DEBUG Illegal To-11 done state for QP2
|
|
| DTEIBA DTESER DEBUG Input buffer already allocated
|
|
| DTEIDS DTESER DEBUG Illegal To-10 done state
|
|
| DTEIDX DTESER STOP Bad index in byte pointer
|
|
| DTEIKF DTESER DEBUG Illegal kontroller function
|
|
| DTEIPA DTESER STOP No post address
|
|
| DTEITM DTESER DEBUG Illegal To-10 transfer mode in QP2
|
|
| DTEITS DTESER DEBUG Illegal To-10 transfer state
|
|
| DTEMDM DTESER STOP No master DTE
|
|
| DTEMDS DTESER JOB MOVSLJ didn't skip
|
|
| DTENFC DTESER STOP No free core
|
|
| DTENFP DTESER STOP No forward pointer in MSD
|
|
| DTENIS DTESER STOP DTE in wrong state
|
|
| DTENOD DTESER STOP No data
|
|
| DTENOM DTESER STOP No message block
44
| DTEOBA DTESER DEBUG Output buffer already allocated
|
|
| DTEPCI DTESER STOP Function code illegal
|
|
| DTEPTL DTESER STOP Packet too large
|
|
| DTEQEF DTESER STOP Queue entry full
|
|
| DTERWC DTESER DEBUG DTERLD called on wrong CPU
|
|
| DTETNI DTESER STOP DTE not idle
|
|
| DTETQP DTESER STOP Found queue point
|
|
| DTEWCN DTESER STOP Wrong CPU number
|
|
| EMS VMSER STOP Exceeding maximum section
|
|
| ENQATA QUESER DEBUG Bad access table address
|
| Code assumes that the access table addresses
| are under 400,000. FRECOR access tables must
| be within 400,000, or you must make
| appropriate code changes to QUESER.
|
|
| ENQAVE QUESER DEBUG Already have EQ
|
| AVESTP is a stopcode-only routine. This
| stopcode occurs when a job has the
| Enqueue/Dequeue Wait resource when it should
| not have it.
|
| Data Items: J = job number
|
|
| ENQCWD QUESER JOB Can't wake job/context after DEQ.
|
| DEQ. process is completed, but WAKE. to
| requesting program or idle context failed,
| for some reason. Make sure the requesting
| program or context handle is valid.
45
| ENQCWJ QUESER JOB Can't wake job/context
|
| DEQ. process is completed, but lock cannot
| be granted. Check the waiting process for
| invalid requesting job or context handle.
|
|
| ENQDNL QUESER DEBUG DEQ not interlocked
|
| DEQIT dequeues one Q-entry. This stopcode
| occurs when the job does not own the DQ
| interlock.
|
| Data Items: J = job number
|
|
| ENQIJC QUESER JOB Illegal job/context handle
|
| Code tried to obtain a q-chain header for a
| particular context, but the attempt failed
| because of internal discrepancies. An
| invalid job or context handle was requested.
|
|
| ENQLNF QUESER DEBUG Lock not found
|
| REDTB fills a user table with data from the
| LOCK-associated table. This stopcode occurs
| when the system cannot find the LOCK block.
|
|
| ENQQFU QUESER JOB Q-blocks fouled up
|
| TSTAAC tries to determine if we need to
| increment the read count in the access table
| to make it stay around. This stopcode occurs
| when a zero entry is found in the link to the
| next queue.
|
|
| ENTMPB ETHUUO DEBUG MISSING USER PORTAL BLOCK
|
| Occurs when attempting to release a user
| portal which doesn't exist in the user portal
| table.
|
|
| ENTPCN ETHUUO DEBUG USER PORTAL COUNT NON-ZERO
|
| Occurs when ETHUUO tries to release an EJB
| (ethernet job block) which hasn't closed all
| user portals.
46
| ENTPTF ETHUUO DEBUG USER PORTAL TABLE FULL
|
| Occurs when the user portal count claims
| there is a free entry in the user portal
| table, but all the entries are used.
|
|
| ENTUUE ETHUUO DEBUG UNEXPECTED ETHSER ERROR CODE
|
| Shouldn't happen. Means ETHUUO got an error
| code back from ETHSER that it didn't expect.
ERB REFSTR DEBUG Error Reading BAT Block
REDBAT reads in BAT blocks and returns a new
unit pointer. This stopcode occurs when an
error is encountered while reading.
Data Items: U = address of current unit
ERD ONCMOD DEBUG Error Refreshing Disk
WUNSTR refreshes a structure. This stopcode
occurs when an I/O error is encountered while
refreshing.
ERF TAPSER STOP Error Recovery Procedure Fouled Up
ERPINT is used when an interrupt is received
while error recovery is in progress. This
stopcode occurs when a pointer that should be
pointing at an I/O request block is pointing
elsewhere.
Data Items: T1 = bad pointer
TKBERB(W) = good pointer
ERH REFSTR DEBUG Error Reading HOME.SYS
This stopcode occurs when the refresher
cannot read the home blocks. (See stopcode
CRH.)
ERM ONCMOD DEBUG Error Reading MFD
SPTSSB creates the SPT table and the swapping
SAT table for a disk unit. This stopcode
47
occurs when an I/O error occurs while reading
the MFD read-in block.
Data Items: P1 = address of first word of MFD RIB (RH)
T2 = logical block number to read
U = unit data block address
F = file data block address
S = (RH) standard error bits
ERP REFSTR STOP Extraneous Retrieval Pointer
HOMRBS stores a retrieval pointer in the
HOME.SYS read-in block. This stopcode occurs
when the byte pointer is confused.
Data Items: T1 = current byte pointer
ERS ONCMOD DEBUG Error Reading SAT
FILMAN finds and sets up all of the
structures on the system. This stopcode
occurs when I/O takes place while reading the
SAT.SYS read-in block for a structure.
Data Items: S = error bits
ESS FILFND JOB Empty System Search List
SLXESS is a stopcode-only routine and is
called throughout FILFND. Examine the stack
for the location.
|
|
| ETHCCC ETHSER DEBUG Can't create channel block
|
|
| ETHCCP ETHSER DEBUG Can't create PORTAL block
|
|
| ETHICN ETHSER DEBUG Invalid Ethernet channel number
|
|
| ETHIFC ETHSER DEBUG Invalid function code
|
|
| ETHIFP ETHSER DEBUG Invalid function for PORTAL
|
|
| ETHIPI ETHSER DEBUG Invalid ethernet PORTAL Id
48
| ETHIPS ETHSER DEBUG Invalid protocol state
|
|
| ETHUDS ETHSER DEBUG Unexpected disable protocol state
|
|
| ETHUES ETHSER DEBUG Unexpected enable protocol state
EUE ERRCON DEBUG Executive UUO Error
EMUERR is called when a monitor call is made
illegally at exec level. This stopcode
occurs when the monitor call occurs at
non-interrupt level.
EWB REFSTR DEBUG Error Writing Block
BLKWRT writes out a block. This stopcode
occurs when the subroutine to do the actual
writing of the block, OWNWRT, gives an error
return that indicates an I/O error.
Data Items: DEVMBF(F) = IOWD
T2 = logical block number
U = address of unit
EWH REFSTR DEBUG Error Writing Home Block
HOMUPD updates the home blocks. This
stopcode occurs when the subroutine used to
do the physical I/O (WRTRUN) gives an error
return.
Data Items: T2 = list of items to be written
S = standard error bits
EWR ONCMOD DEBUG Error While Refreshing
RFRES2 refreshes a structure during the
DESTROY option. This stopcode occurs when an
I/O error is encountered during the refresh.
Data Items: S = error bits
|
|
| EXFCHK SCNSER STOP Exhausted free chunks
49
FAD FILUUO DEBUG File Already Dormant
CLRSTG is used during a CLOSE monitor call to
do general clean-up tasks. This stopcode
occurs when the access-table entry for this
file is mistakenly marked dormant.
Data Items: ACCDOR(T1) = access-table entry for this file
|
|
| FDL VMSER STOP FRDCR lied
|
|
| FDP FILIO DEBUG Fixed-Head Device Position
|
| FREINT handles unsolicited interrupt from a
| device. This stopcode occurs when a
| position-done interrupt occurs for a
| fixed-head device. This may indicate a
| hardware problem.
|
| Data Items: KONPOS(J) = unit positioning flag
|
|
| FEM ERRCON HALT Fatal Error in Monitor
|
| PARHALT halts a CPU when there is a serious
| error in the monitor.
|
|
| FFU NETSER STOP F Fouled Up
|
| NETHIB puts a network job in the HIBER state.
| This stopcode occurs when NETHIB is called
| with F = 0.
|
|
| FLE SCNSER STOP Free List Empty
|
| GETCHK fetches chunks from the SCNSER
| free-chunk chain. This stopcode occurs when
| the pointer to the first chunk (TTFTAK) is
| zero.
|
|
| FON VMSER STOP Funny Address Overlaps Next
|
| GVFWDS returns words acquired by GTFWDC or
| GTFWDU. This stopcode occurs when the size
| of the current chunk plus the the address of
| the current chunk overlaps the first word of
| the next chunk.
50
| Data Items: T1 = words to return
| T2 = address
|
|
| FOP VMSER STOP Funny Address Overlaps Previous
|
| GVFWDS returns words acquired by GTFWDS or
| GTFWDU. This stopcode occurs when the first
| word of the funny address is in the previous
| chunk.
|
| Data Items: T1 = words to return
| T2 = address
|
|
| FPE VMSER DEBUG Funny Page Must Exist
|
| GVFWDS returns words acquired by GTFWDS or
| GTFWDU. This stopcode occurs when the
| monitor tries to get a page map entry, but no
| funny page exists from which to get the page
| map entry.
|
| Data Items: T1 = words to return
| T2 = address
|
|
| FPI CORE1 STOP GTPAGS Free Page In Use
|
| This stopcode occurs when the monitor tries
| to get a page from the free-core list, but
| finds a page marked "in use" on the free
| list.
|
| Data Items: T1 = first page added to or taken from the
| free-core list; T2 = negative number of
| pages to add or take from the free-core list
|
|
| FPN LOKCON STOP SETMFL Free Page Not Found
|
| SETMFL moves monitor pages when its current
| pages are being set off line. This stopcode
| occurs when the target page is not found on
| the free-core list.
|
| Data Items: T1 = current page (being set off line)
| P2 = target page (this is the page that
| caused the stopcode)
|
|
| GNA DATMAN STOP GETWRD not available
51
| GETWRD was called at clock level but the word
| requested was not available.
|
|
| HBE REFSTR DEBUG Home Block Read Error
|
| HOMUPD updates the home blocks. This
| stopcode occurs when the subroutine to read
| in the current home blocks from disk (GTHOM)
| gives an error return, which indicates an I/O
| error.
|
| Data Items: S = standard error bits
|
|
| HIF FILIO DEBUG Hole In File
|
| USETO0 is used to do a USETO. This stopcode
| occurs when the last block of the file
| exists, but some preceding block does not.
|
|
| HSF FILIO JOB HSC50 not fancy
HWU FILIO JOB Hardware Wrong Unit
POSERC is used during disk error recovery.
This stopcode occurs when the wrong unit on a
disk controller interrupts. This is a
hardware problem.
Data Items: P2 = error bits
T1 = retry count
IBI CLOCK1 JOB Intercept Block Illegal
ESTOP stops the user on an error and flags it
as an error stop. This stopcode occurs when
the user-defined intercept block is illegal
for some reason.
IBZ FILIO JOB I/O to Block Zero
UUOPWR performs CALLIs for a disk channel.
This stopcode occurs when Block 0 is
requested, but the file is not HOME.SYS[1,4]
or the drive is not an RP04. An RP04 reads
block 0 to check for format errors.
52
Data Items: T1 = PPN
T2 = file name
|
|
| ICI MSCCOM DEBUG Invalid connect-ID
ICL UUOCON JOB Illegal Channel Number
JDAADR returns the address of a channel in
USRJDA or the extended channel table in T1.
This stopcode occurs when the channel number
is greater than the maximum number allowed.
Data Items: T2 = channel number
HIGHXC# = maximum
ICN SEGCON DEBUG In-Core Count Negative
DECCNT decrements the high-segment in-core
count for a job that has a very high segment,
which must be in core. This stopcode occurs
when the count of the number of jobs in core
sharing a high segment becomes negative.
Data Items: J = job number
JBTSTS(J) = in-core count, which should be
zero now
IDC ONCMOD STOP Impossible Drum Condition
DRMHLT checks for a unit on line and write
protected. This stopcode occurs because a
drum can never give an on-line condition.
IEZ KxSER DEBUG IOWD Equals Zero
After paging a job, the monitor attempted to
convert virtual IOWDs to absolute IOWDs.
This stopcode occurs when this routine is
called with an IOWD of zero.
Data Items: T2 = IOWD
P3 = location of channel data block
P4 = frame count,,characters/word if DX10
channel
IFI TAPSER STOP Illegal Function at Interrupt
53
TAPIFI is a general interrupt error halt. In
one case, for example, the monitor found an
illegal function in an I/O request block
while at interrupt level. Examine the stack
for the specific error address.
IIP FILIO STOP I/O In Progress - Error
MONIO reads a block or series of blocks from
the disk. This stopcode occurs when the
monitor attempts to start I/O for a DDB that
already has I/O active.
Data Items: S = status bits
T1 = IOWD for data
T2 = block number
IME KxSER JOB Illegal Memory Reference from Executive
This stopcode occurs when there is a page
fault while in exec mode that is not an
address break.
Data Items: .CPAPC = page fault PC
.CPPFW = page fault word
IOP COMMON CPU I/O Page Failure
There is usually a serious hardware failure.
Call your Field Service representative.
IPC KxSER CPU Illegal Page Failure Trap Code
SEILM processes page failure traps. This
stopcode occurs when the trap code returned
by the pager after getting a page fail trap
is not in the range 0 through 23 or 25.
Data Items: T1 = page fail code
.CPTCX = page trap context;
.CPTPI = PI state
|
|
| IPE VMSER DEBUG In progress queue empty
IPF VMSER DEBUG In-Use Page Free
SCNPT scans the page table. This stopcode
54
occurs when SCNPT finds a page on the
free-core list that is listed in the page
table as allocated.
IPM VMSER DEBUG Illegal Pointer in MEMTAB
This stopcode occurs when the monitor finds
an inconsistency in the swapping database.
IPN VMSER DEBUG IPCF Page Nonexistent
GVIPCP returns IPCF pages to the free-core
list. This stopcode occurs when GVIPCP swaps
out IPCF pages that are not in the swap list.
IPU LOKCON STOP IPCF Page Unowned
In attempting to swap out an IPCF page,
LOKCON was unable to find a job that
contained the IPCF page in its queue.
ITS DTESER DEBUG Illegal To-10 Transfer State
DTESER received a To-10 interrupt which
specified an illegal state.
|
|
| IUD DTESER DEBUG Illegal user for DTE
|
|
| IUI FILIO DEBUG Illegal use of UPPDC at interrupt level
IUN FILUUO DEBUG Invalid Unit Number
ERRFIN finishes a CLOSE when an error
occurred. This stopcode occurs when the unit
number for the UFD is illegal.
Data Items: UN1PTR = pointer to number in structure of
the unit; T1 = unit of UFD
JAC UUOCON DEBUG Job Data Area Clobbered
IOALL does I/O for all devices assigned to a
job. This stopcode occurs when the highest
channel number in use is greater than 17.
55
Data Items: T2 = highest channel in use
JDJ ONCMOD DEBUG JFFO Didn't Jump
CMPLOG computes the SIXBIT logical unit
number within a structure. This stopcode
occurs after a call to subroutine MSKUNI,
which sets up a search mask for a unit name,
and it returns no mask for the unit name
given.
Data Items: P2 = unit number
STRNAM(P2) = unit name
T2 = should have been the complement of the
search mask
JIT SYSINI HALT Job In Transit
LOKINI initializes LOKCON on location 140
restarts, unlocks all jobs, and frees up the
core they occupy. This stopcode occurs when
a job is locked and is being moved.
Data Items: J = job number
JNC FILIO DEBUG Job Not in Core
ADRINT checks that a job is in core, possibly
at interrupt level. This stopcode occurs
when the job is not in core.
Data Items: T1 = job number
JNE CLOCK1 STOP JBTADR not equal to CORTAL
In cross-checking JBTADR and CORTAL a
mismatch was found.
Data Items: P3 = amount of free-core specified by the sum
of JBTADR entries
KAF COMMON CPU Keep-Alive Failure
This routine/stopcode is executed because the
console front end detected that the KL did
not update the keep-alive counter. This
stopcode occurs when the front end executes a
56
XCT 71.
KCP RNXKON DEBUG KDB Command in Progress
CMDWAT waits for a command to complete and
calls RNXINR to process it before starting a
new command.
KDS DPXKON DEBUG KONEC2 Didn't Skip
POSINT handles positioning interrupts. This
stopcode occurs when the subroutine KONEC2
does not skip, even though it should always
give a skip return.
KID SYSINI HALT Kontroller Is Down
DSKINI, which is called on location 140 and
143 starts and restarts, initializes the
disk. This stopcode occurs when a controller
goes off-line during disk initialization.
Data Items: J = kontroller
|
|
| KIM RAXKON DEBUG Kontroller id mismatch
|
|
| KLPBRC KLPSER INF Bad Read-Counters packet
|
|
| KLPCGN KLPSER CHK Can't get CI node number
|
|
| KLPCKE KLPSER CHK SET-CIRCUIT command error
|
|
| KLPCLB KLPSER INF Close buffer function failed
|
|
| KLPCPE KLPSER INF KLIPA CRAM parity error
|
| A parity error occurred on the CI20, which
| may indicate a hardware condition.
|
|
| KLPCRR KLPSER CHK READ-REGISTER command failed
57
| KLPDED KLPSER INF CI-20 is dead
|
|
| KLPDFQ KLPSER INF Datagram free queue empty
|
|
| KLPEPB KLPSER CHK Received bad error logging packet
|
|
| KLPERQ KLPSER CHK Empty response queue
|
|
| KLPERR KLPSER INF Received packet with error
|
|
| KLPHLT KLPSER INF KLIPA microprocessor halted
|
| The CI20 microprocessor halted for some
| reason.
|
|
| KLPHNG KLPSER INF CI-20 is hung
|
|
| KLPILP KLPSER INF Software response terminated in
| locally-generated packet
|
|
| KLPIPA KLPSER INF Invalid packet arrived
|
|
| KLPIRD KLPSER INF Invalid remotely-generated data request
|
|
| KLPIRP KLPSER INF Software response bit on in
| remotely-generated packet
|
|
| KLPKAF KLPSER INF KLIPA Keep Alive Failed
|
| The KLIPA will reload automatically.
|
|
| KLPKRW KLPSER HLT CI-20 read the wrong register
|
|
| KLPLBF KLPSER INF Loopback failed
|
|
| KLPMBE KLPSER INF MBUS error
58
| KLPMCE KLPSER INF Received an MCNF or an MDATREC with an error
|
|
| KLPMCR KLPSER CHK Received an unexpected MCNF or MDATREC
|
|
| KLPMFQ KLPSER INF Message free queue empty
|
|
| KLPNBD KLPSER HLT No buffer descriptor table
|
|
| KLPNDB KLPSER INF No datagram buffer
|
|
| KLPNDE KLPSER INF Packet with bad node number
|
|
| KLPNEN KLPSER CHK CI-20 not enabled
|
|
| KLPNMG KLPSER INF No message buffer
|
|
| KLPNOD KLPSER HLT Can't get datagram buffers during
| initialization
|
|
| KLPNOR KLPSER INF Remote port is sick
|
|
| KLPNPB KLPSER HLT No path block at PPDOVC
|
|
| KLPOHF KLPSER HLT Internal software inconsistency
|
|
| KLPONC KLPSER HLT Trying to open a virtual circuit which isn't
| closed
|
|
| KLPOPC KLPSER INF Packet with bad opcode
|
|
| KLPPIA KLPSER INF CI-20 has lost its PI assignment
|
|
| KLPPIC KLPSER HLT PCB is Corrupted
|
|
| KLPPPD KLPSER INF Packet with bad PPD byte
59
| KLPPTQ KLPSER INF Queue interlock timeout
|
|
| KLPRCE KLPSER CHK READ-COUNTERS command failed
|
|
| KLPRLF KLPSER INF CI-20 microcode reload failed
|
|
| KLPRMQ KLPSER INF Queue interlock timeout
|
|
| KLPRSF KLPSER INF CI-20 restart failed
|
|
| KLPRSH KLPSER INF Received shutdown message
|
|
| KLPSCR KLPSER CHK SET-CIRCUIT command received
|
|
| KLPSTR KLPSER INF CI-20 started
|
|
| KLPSWO KLPSER INF Received a START when VC was open
|
|
| KLPVIR KLPSER CHK Virtual address in packet is wrong
|
|
| KLPWAB KLPSER INF CI wire A has gone from good to bad
|
|
| KLPWAG KLPSER INF CI wire A has gone from bad to good
|
|
| KLPWBB KLPSER INF CI wire B has gone from good to bad
|
|
| KLPWBG KLPSER INF CI wire A has gone from bad to good
|
|
| KN5 RAXKON INF Kontroller not in 576-byte sector mode
|
|
| KNF XTCSER STOP Kontroller Not Free
|
| XTCSER received a remote interrupt request,
| the the kontroller was not free.
|
|
| KNIARD KNISER INF KLNI auto-reload disabled
60
| KNICAC KNISER DEBUG Can't allocate counters data buffer
|
|
| KNICAM KNISER DEBUG Can't allocate MCAT table
|
|
| KNICAP KNISER DEBUG Can't allocate PTT table
|
|
| KNICCC KNISER DEBUG Cannot create CONSO skip chain entry
|
|
| KNICCK KNISER DEBUG Can't create Ethernet kontroller block
|
|
| KNICCP KNISER DEBUG Cannot create port control block
|
|
| KNICPE KNISER INF KLNI CRAM parity error
|
| A parity error occurred on the NIA20, which
| may indicate a hardware condition.
|
|
| KNICWS KNISER DEBUG KLNI counters buffer is wrong size
|
|
| KNIDPE KNISER INF KLNI data path error
|
|
| KNIEPE KNISER INF KLNI EBUS parity error
|
|
| KNIHLT KNISER INF KLINI microprocessor halted
|
| The NIA20 microprocessor halted for some
| reason.
|
|
| KNIICO KNISER DEBUG Invalid command opcode
|
|
| KNIIFC KNISER DEBUG Illegal function code
|
|
| KNIKAF KNISER INF KLNI Keep Alive failed
|
|
| KNIMBE KLNISER INF KLNI MBUS error
|
|
| KNIMWS KNISER DEBUG KLNI MCAT table is wrong size
61
| KNIPIT KNISER INF PUTQUE interlock timeout
|
|
| KNIPWS KNISER DEBUG KLNI PTT table is wrong size
|
|
| KNIRIT KNISER INF REMQUE interlock timeout
|
|
| KNIWUV KNISER DEBUG Wrong microcode version
KNM TX1KON DEBUG Kontroller Not Mapped
In attempt to uncache a DX10 KDB we found the
KDB was not in the EPMP.
KSW TAPSER DEBUG Kontroller Status Wrong
TAPSIO is used when the upper level wants to
start I/O. This stopcode occurs when the
tape-controller status is wrong.
Data Items: TKBSTS(W) = status
|
|
| LATICB LATSRV CHK LATCBR called from NISRV with illegal
| callback function code
|
| NISRV has called the LATSRV callback routine
| with an invalid function code.
|
|
| LATIMT LATSRV INF LAT Illegal Message Type
|
| LAT virtual circuit message received with
| message type out of range.
|
|
| LATINE LATSRV CHK LATINI failed to initialize
|
|
| LATMEM LATSRV CHK LAT buffer overwritten
|
| While trying to return a buffer, LATSRV
| discovered it had been overwritten.
|
|
| LATNSC LATSRV INF LAT Host node stopped circuit
|
| LAT Host node stopped the circuit.
62
| Look at the Reason Code in T1 and the PC in
| T2. This error, if relatively infrequent is
| nothing to be concerned about. If it occurs
| frequently, use the CODE and PC to determine
| further action.
|
|
| LDBNIU SCNSER DEBUG LDB Not In Use
|
| A call to the FRELDB routine was made, though
| the terminal's LDB does not have the LTLUSE
| bit set in the LDBTTW word. Normally, this
| bit would be set on a return from GETLDB to
| indicate that that LDB is in use.
|
|
| LLMCIF LLMOP CHK Read Channel Info Failed
|
| Attempt to read the Ethernet channel status
| failed when the Data Link Layer was called.
|
| Data items: T1 contains the error code returned from the
| DLL
|
|
| LLMIL1 LLMOP INF Received Invalid Loopback Message
|
| Received a Loopback message that was too
| short or was improperly formatted. This is a
| MOP protocol violation by a remote node.
|
| Data items: T1 contains the received message length.
| T2-T3 contains the Ethernet address of the
| transmitting node.
|
|
| LLMILF LLMOP INF Invalid Loopback Function Code
|
| Received a Loopback message that was neither
| a Loopback reply message or a forward data
| message. This is a MOP protocol violation by
| a remote node.
|
| Data items: T1 contains the function code.
| T2-T3 contains the Ethernet address of the
| transmitting node.
|
|
| LLMIR1 LLMOP INF LLMOP Received Invalid Remote Console Message
|
| Received a Remote Console message that was
| too short, too long or was improperly
63
| formatted. This is a MOP protocol violation
| by a remote node.
|
|
| LLMLXF LLMOP INF Loopback Transmit Failed
|
| LLMOP was unable to transmit a forward data
| message.
|
| Data items: T1 contains the error code returned from the
| DLL
| T2 contains the channel status returned from
| the DLL
| T3 contains the channel on which the failure
| occurred
|
|
| LLMMCF LLMOP CHK Declare Multicast Address Failed
|
| Attempt to declare the Assistant Multi-Cast
| Address failed when the Data Link Layer was
| called.
|
| Data items: T1 contains the error code returned from the
| DLL
|
|
| LLMOPF LLMOP CHK Open Portal Failed
|
| Failed to open an NI portal with the Data
| Link Layer.
|
| Data items: T1 contains the error code returned from the
| DLL.
|
|
| LLMRQC LLMOP CHK RB Queue Corrupted
|
| Attempted to remove an RB queue entry from an
| empty queue or the RB was not on the queue.
|
|
| LLMRRF LLMOP INF Response Transmit Failed
|
| LLMOP was unable to transmit a MOP request
| message.
|
| Data items: T1 contains the error code returned from the
| DLL.
| T3 contains the channel on which the failure
| occurred.
64
| LLMRXF LLMOP CHK Resource Failure
|
| LLMOP was not able to obtain resources from
| the memory manager.
|
|
| LLMSB2 LLMOP CHK Specify Receive Buffer Failure
|
| LLMOP could not post a receive buffer to the
| Data Link Layer.
|
| Data items: T1 contains the error code returned from the
| DLL.
|
|
| LLMSCA LLMOP INF Ethernet Channel Address Change
|
| LLMOP was called by NIDDL on change of state.
|
|
| LLMSTC LLMOP INF Data Link State Change
|
| LLMOP was called by NIDDL on change of state.
| This is for information only. No corrective
| action required.
LN1 ERRCON STOP Line Not Found
EXCALP prints a monitor call PC message for a
job. This stopcode occurs when no terminals
a log line can be found for the job that is
causing the error.
LND FILUUO DEBUG Logical Name Not Found
LNMSTP consists of only the stopcode and its
recovery. LNMSTP is called when the monitor
could not set up the definition of LIB that
was present before an ENTER UUO that could
not find a file.
LNP FILIO DEBUG Last Pointer Not a Pointer
OUTGRP allocates more space for an output
file. This stopcode occurs when an
allocation is made, but a RIB error occurred;
or when the monitor tried to deallocate the
space, but the RIB pointer was invalid.
65
Data Items: T2 = pointer
LNS SCNSER STOP Line Not Set Up
TSETBI clears the input and output buffers
for a line. This stopcode occurs when this
routine is called before the line is set up.
LNT ERRCON STOP Line Not There
HALTI prints the "Halt at ..." message and
stops the job. This stopcode occurs when
there is no controlling terminal line
associated with the job.
LPU FILUUO JOB Last Pointer Unit-Change
ALLP0B writes the redundant RIB in the last
block of the RIB. This stopcode