idiary
ithout
Your comments are welcome. They can assist us in improving our products. Please address your comments to [email protected].
Lucent Technologies Inc.1001 Murphy Ranch RoadMilpitas, CA 95035-79121-800-444-5590
www.lucent.com
Lucent Technologies, USA +408 324-2000Lucent Technologies, Canada +1 416 730-8700Lucent Technologies, Europe, Middle East, Africa +44 (0)1252 303 000Lucent Technologies, Central America, Latin America +1 408 324-3372 (USA)Lucent Technologies, Asia pacific +65 430 2100
© Copyright 1999 Octel Communications Corporation, a subsidiary of Lucent Technologies, Inc.All rights reserved. All trademarks identified by the ® and (™) are registered trademarks or trademarks respectively of Octel Communications Corporation, a subsof Lucent Technologies. All other trademarks are properties of their respective owners. The above information is based on knowledge available at the time of publication and is subject to change wnotice. Printed in the USA.
P/N 001-11368-00 1999
Printed on recycled paper.
Contents
USING THIS MANUAL viiREADING THE STATUS LOG 1OVERVIEW OF THE STATUS LOG 1Contents of the Status Log 1Structure 2CHECKING THE STATUS LOG 4When to Check the Status Log 4How to Check the Status Log 4DISPLAYING THE STATUS LOG 7Display from Menu 13 8Display from Menu 20 While Off-Line 10Display from Disk Utilities 12Display from Datafile Utilities 14Display from Dump 16READING A STATUS CODE DESCRIPTION 18STANDARD FIELD GROUPS 21Entry Header 22IORB Header 28Control Bus Messages 35STATUS CODES 37FILE SYSTEM MESSAGES 347MESSAGE DESCRIPTIONS 352COMMON CODES 519Drive Action and Status Codes 519Read and Write Data Types 520File Numbers 522Internal File Card Status Codes 524File Card Return Codes 535FILE CARD STATUS FOR OVERTURE 250 AND OVERTURE 350 538File Card Status Fields 539LINE CARD MESSAGES 541
i STATUS LOG
Status Log Interpretation, Aria 3.0
ACP MESSAGES 623PIC MESSAGES 663LAN CARD MESSAGES 701OTHER CODES 731STANDARD ASCII CODE SET 732HEX/BINARY CONVERSION TABLE 733DRIVE TEST STATUS CODES 733START-UP DIAGNOSTICS 734IPL/PIPL STATUS CODES 736GLOSSARY 739
ii STATUS LOG
STATUS LOG
List of Tables
Table 1-1. How to Check the Status Log . . . . . . . . . . . . . . . . . . . . 5
Table 1-2. Easiest Display Methods. . . . . . . . . . . . . . . . . . . . . . . . 7
Table 1-3. Status Log Locations . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Table 1-4. Status Log Locations in Datafile Format . . . . . . . . . . .15
Table 1-5. Task IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Table 1-6. Task ID to Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Table 1-7. Reading the Time Stamp. . . . . . . . . . . . . . . . . . . . . . . . 26
Table 1-8. Bank and Slot of the Peripheral Address . . . . . . . . . . .30
Table 1-9. Channel of the Peripheral Address . . . . . . . . . . . . . . . .31
Table 1-10. IORB Function and Status Codes . . . . . . . . . . . . . . . .33
Table 2-1. Routine IDs (offset 10-11) . . . . . . . . . . . . . . . . . . . . . . 80
Table 2-2. Supplemental Error Codes (Offset 12) . . . . . . . . . . . . . 82
Table 2-3. Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Table 3-1. Drive Action Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . 519
Table 3-2. Drive Status Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519
Table 3-3. Data and Parameter Types . . . . . . . . . . . . . . . . . . . . . . 520
Table 3-4. File Numbers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522
Table 3-5. Internal File Card Status Codes . . . . . . . . . . . . . . . . . . 524
Table 3-6. File Card Return Codes. . . . . . . . . . . . . . . . . . . . . . . . .535
Table 3-7. Boot Status Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
Table 3-8. Standby Redundancy Status Bits (Overture 350) . . . . . 539
A-1. ASCII Code Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 732
Table A-2. Hex/Binary Conversion . . . . . . . . . . . . . . . . . . . . . . . . 733
Table A-3. Drive Test Status Codes. . . . . . . . . . . . . . . . . . . . . . . . 733
Table A-4. Start-Up Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . 734
LOT-iii
Status Log Interpretation, Aria 3.0
Table A-5. IPL/PIPL Status Codes . . . . . . . . . . . . . . . . . . . . . . . . 736
LOT-iv STATUS LOG
STATUS LOG
List of Figures
1-1. Ring Buffer Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1-2. Status Log Entry Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1-3. Transposing Intel Order to Normal Order . . . . . . . . . . . . . . . 3
1-4. Status Code Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1-5. Menu 13 Display Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1-6. Menu 20 Display Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1-7. Disk Utilities Display Example . . . . . . . . . . . . . . . . . . . . . . . 12
1-8. Datafile Utilities Display Example . . . . . . . . . . . . . . . . . . . .14
1-9. Dump Display Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1-10. Example Status Code Explanation . . . . . . . . . . . . . . . . . . . . 18
1-11. Entry Header Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
1-12. Entry Header with Time Stamp Detail . . . . . . . . . . . . . . . . .26
1-13. IORB Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
1-14. Peripheral Address Detail . . . . . . . . . . . . . . . . . . . . . . . . . . 29
1-15. IORB Header with Peripheral Address Detail . . . . . . . . . . . 31
1-16. IORB Header with Function and Status Code Detail . . . . . 34
1-17. Control Bus Message Format . . . . . . . . . . . . . . . . . . . . . . . . 35
3-1. Screen at End of Power-On for Overture 250 . . . . . . . . . . . .530
3-2. Screen at End of Power-On for Overture 350 . . . . . . . . . . . .530
3-3. File Card Status Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531
Ring Buffer Operation 2Status Log Entry Example 3Transposing Intel Order to Normal Order 3Status Code Location 5Menu 13 Display Example 8
LOF-v
Status Log Interpretation, Aria 3.0
Menu 20 Display Example 10Disk Utilities Display Example 12Datafile Utilities Display Example 14Dump Display Example 16Example Status Code Explanation 18Entry Header Format 22Entry Header with Time Stamp Detail 26IORB Header 28Peripheral Address Detail 29IORB Header with Peripheral Address Detail 31IORB Header with Function and Status Code Detail 34Control Bus Message Format 35Screen at End of Power-On for Overture 250 538Screen at End of Power-On for Overture 350 538File Card Status Fields 539 539
LOF-vi STATUS LOG
PREFACE: USING THIS MANUAL
The status log of Octel® Overture™ 250 and 350 message servers is anautomatic record of exception events. Reading the status log is essential tomonitoring a message server’s use and, especially, for troubleshooting.
This manual provides all the information needed for reading status logentries. It can also be used for reading control bus messages independentof the status log. In addition, this manual contains explanations of a varietyof other codes that are also helpful in troubleshooting.
First-time users of this manual should read Chapter One to become familiarwith the status log, where reference information is located and how informa-tion is presented in this manual.
This manual applies to the Octel® Aria™ 2.0 user interfaces. For otherreleases, use the status log interpretation manual for that release.
Organization
Chapter One: Reading the Status Log provides an overview of the statuslog, instructions for displaying the log in various ways and instructions forreading the entries.
Chapter Two: Status Codes describes all status codes with associatedsubcodes and entry formats.
Chapter Three: File System Messages describes all control bus mes-sages used with file systems.
Chapter Four: Line Card Messages describes all control bus messagesused with line cards.
Chapter Five: ACP Messages describes all control bus messages usedwith ACP cards.
Chapter Six: PIC Messages describes all control bus messages used withPIC cards.
Chapter Seven:LAN Messages describes all contorl bus messages usedwith LAN cards.
Appendix: Other Codes describes some troubleshooting codes that arenot used in the status log.
Glossary defines many terms as used in this manual.
Assumptions About the Reader
This manual assumes that you are familiar with Octel Overture 250 and 350message servers, including the basic software and hardware configura-tions, and terminology. Check the appropriate service manual if more infor-mation is needed.
STATUS LOG vii
USING THIS MANUAL
You should also be familiar with the hexadecimal numbering system. It isused routinely throughout this manual. Skill in doing arithmetic with hexnumbers—with or without a hex calculator—is occasionally helpful, but notnecessary.
Conventions in the Manual
The main use for this manual is interpreting codes in status log entries. Thelocations of the codes are given as offsets. An offset is a count of bytes(with two hex digits per byte) from the beginning of some data structure,such as a status log entry or a control bus message. The count begins withzero. Offsets are always given as hexadecimal numbers. In the figures, thevalues shown are the offsets of each byte, instead of real data. For exam-ple, the figure below shows the task ID at offset 02 (the third byte) of a sta-tus log entry.
Status log entries and other data structures are broken down into fields thatcarry a specific piece of information. In the illustrations in this manual, eachfield is boxed to show its location and length. It is labelled (inside the box orout, as convenient) to explain its content. The figure above shows that thefield holding the task ID information starts at offset 02 and is one byte (ortwo hex digits) long. The AX field starts at offset 20 and is two bytes long.
Key fields are shaded. These are the fields most commonly referred to andthe first ones to check. The task ID is marked as a key field in the figure.
All values for fields are given as hex numbers unless stated otherwise.
Task ID
00010 10111213 14151617 18191A1B 1C1D1E1F
AX IP CS
00000 00010203 04050607 08090A0B 0C0D0E0F
00020
Offsetcount
Offsets ofeach byte
viii STATUS LOG
CHAPTER 1: READING THE STATUS LOG
The status log is a key troubleshooting tool for Octel® Overture™ 250 and350 message servers. With it, the causes of problems, hardware and soft-ware, can be tracked down. Some problems can even be spotted beforethey happen and prevented.
This chapter provides instructions for interpreting the status log, startingwith what the log is and when to use it. The instructions include how to viewthe status log and how to find an explanation of a status log entry. Thechapter ends with details of data structures commonly used in entries,including reference tables.
If you are unfamiliar with the status log, you should read the whole chapterbefore starting work.
If you are experienced with the status log, you should at least skim thechapter to locate reference information and to see how information is pre-sented.
1.1 OVERVIEW OF THE STATUS LOG
This section describes what is in the status log and how the operating sys-tem maintains the log. The next section describes how to use the status log.
1.1.1 Contents of the Status Log
The status log keeps a running record of significant events occurringthroughout the message server. This includes events such as:
• The message server booting
• An error reading or writing to a data file
• A task timing out
• A network message not being delivered
Each status log entry holds information about the event and the status ofthe message server at the time the event occurred. This information fre-quently includes:
• When the event occurred
• The task involved
• The boards involved
• The control bus messages involved
STATUS LOG 1
READING THE STATUS LOG
Wrap-aroundon overflow
An entry may also include special information about the event, such as anassociated IUN, mailbox number, file name or Tree location. All the infor-mation in an entry is intended to help establish what happened and why.
1.1.2 Structure
Of course, there is a limit to how many entries can be stored in the log. Thestatus log operates as a ring buffer. When entries overflow the top of thebuffer space, they wrap around to the bottom and overwrite the oldestentries. See Figure 1-1. The status log holds almost two kilobytes (six bytesare used for pointers and flags) of the most recent entries.
The status log is stored in two places: as part of the system status table andas part of Record 50. These are in files 04 and 2D, respectively.
Figure 1-2 shows a typical status log entry as displayed with Menu 13.2 (theusual way of viewing the status log). Entries are from 16 to 255 bytes long.The first row of every entry is the entry header (formally known as the errorcontrol block common header). It contains the status code and subcode,which identify the event, and other routine information. After the headerthere is usually a body with more information. What fields are in the bodyand how they are coded depends on the status code and subcode. For veryextensive descriptions, two or three entries are produced for a single event,but these are rare.
Oldest entry
Next entry
Figure 1-1. Ring Buffer Operation
Oldest entry
Next entry
New entrieswritten overold entries
BEFORE OVERFLOW AFTER OVERFLOW
Unusedspace
2 STATUS LOG
READING THE STATUS LOG
...B..*
. *
Most of the fields are loaded in Intel order: the most-significant byte at theright and the least-significant byte at the left (this is a side-effect of the waythe Intel microprocessor operates). These values need to be transposed(see Figure 1-3) before they are interpreted. Fields coded in ASCII—usuallynames and phone numbers—do not need to be transposed.
16 APR 92 06:49:14PM*** System Restarted>>> INVESTIGATE SYSTEM ENVIRONMENT00000 1BC09500 00000000 00000EE9 8C420100 *..........00010 30041609 8C420091 C31F00 *0....B....
Entry header
Body with event-specific information
Figure 1-2. Status Log Entry Example
76 54 32 10
10 32 54 76
Figure 1-3. Transposing Intel Order to Normal Order
32 10
10 32
Two-Byte Data Four-Byte Data
STATUS LOG 3
READING THE STATUS LOG
1.2 CHECKING THE STATUS LOG
This section describes when and how to check the status log. Followingsections give details of the process.
1.2.1 When to Check the Status Log
Check any time there is a problem with the system’s operation. Manyof the status codes are for errors (though not necessarily ones caused bythe message server).
Check as a part of routine maintenance. Some of the codes are forevents that are just unusual or possibly significant, such as the messageserver booting or the AMIS directory becoming 90% full. Even systems thatare running perfectly well log entries. But the entries may reveal an unno-ticed problem (the message server rebooted for no known reason) or indi-cate a problem developing (if the AMIS directory reaches 100%, somenetwork messages may not be sent).
Check periodically and frequently. The system manager normally doesthis. When the log fills up, it starts overwriting the oldest entries. If thoseentries have not already been checked, their information is lost.
1.2.2 How to Check the Status Log
Following is a list of steps for interpreting the status log using this manual.The first part finds what event caused the entry. This may be all the informa-tion needed. If not, work through the second part until enough informationhas been found. It is rarely necessary to translate the whole entry. Then,with the third part, analyze the rest of the entries and do maintenance onthe log.
4 STATUS LOG
READING THE STATUS LOG
For Details,See Section:
1.3 on page 74.
1.3.1 on page 8
find 1.4 on page 18
for 1.4 on page 18
nd 1.5.1 on page 22
RB 1.5.2 on page 28
. 1.5.3 on page 35ed.2 of
.
1.5.3 on page 35
ord
th-
1.3.1 on page 8
..* *
Table 1-1. How to Check the Status Log
Step#
Step Description
Find the Event Description
1 Get a printout of the status log, usually from Menu 13.2.2 Identify entries of interest with the English status codes. See Figure 1-
Include any entry missing the English code. This is all entries if Menus13.2 or 13.3 were not used to display the status log.
3 Get the status code from offset 04-05 of the entry (see Figure 1-4) and the description for the code in Chapter 2.
4 Get the subcode, if there is one, from offset 08-09. Find the descriptionthe subcode, including the format illustration, under the status code’s description in Chapter 2.
Get More Information as Needed
5 Translate the task ID in offset 02. This tells what part of the software apossibly what board was involved.
6 If there are control bus messages:• Translate the peripheral address in offsets 04-05 of the IO
header.• Translate the task ID in offset 00 of each control bus message
The task ID and peripheral address indicate which boards were involv7 If there are control bus messages, get the message type from offset 0
each control bus message.Find the descriptions: Chapters 3 through 6 for a control bus messageMessage type and contents give detailed information about the event.
8 Examine other fields as needed.
Continue Through the Log
9 If there are more entries of interest, repeat steps 3-8.10 File the printout of the status log. These printouts form a long-term rec
of the system’s operation.11 Clear the status log after all entries have been accounted for. Press C
while in Menu 13.2. This makes the log easier to read. There will be noing but new entries the next time.
16 APR 92 06:49:14PM*** System Restarted>>> INVESTIGATE SYSTEM ENVIRONMENT00000 1BC09500 00000000 00000EE9 8C420100 *.............B00010 30041609 8C420091 C31F00 *0....B.....
Status code in offset 04-05
Figure 1-4. Status Code Location
English status code
STATUS LOG 5
READING THE STATUS LOG
e 10
1.3 DISPLAYING THE STATUS LOG
There are several ways to see the status log. Which one you should use willdepend on the situation.
The SST holds the original and preferred copy of the status log. Record 50also has a copy of the log, but it is updated only during a system crash andso is useful only for diagnosing the crash.
This section has instructions for getting each display and shows how toread it. In these instructions, a ^ by a letter (^C for example) means holddown the Ctrl key and press that letter.
Table 1-2. Easiest Display Methods
Situation Method
Online Status Log: “Display from Menu 13” on page 8Record 50: “Display from Datafile Utilities” on page 14
Off-line and can boot fully
Status Log: “Display from Menu 20 While Off-Line” on pagRecord 50: “Display from Disk Utilities” on page 12
Off-line and can boot partially
“Display from Disk Utilities” on page 12
System shutdown “Display from Dump” on page 16
STATUS LOG 7
READING THE STATUS LOG
.. A1.51: 85.03 CPU B: 85.09: 1 - North AmericanL Extension .... 32.36
.......... 92.32.05
.......... 92.32.06
.......... 92.32.05
.......... 92.32.02
.......... 92.32.02
.......... 92.32.02
..kSB..* *
..kSB..* *
....B..*
.. *
ASCII
1.3.1 Display from Menu 13
The most common way to check the status log is by entering Menu 13.2.This display is the easiest to read: the entries are separated from eachother, ordered from oldest to newest and partially translated.
Menu 13.3 is used to watch the log while the system operates. After theentries have been shown, the system waits for more to be logged. The sta-tus log cannot be printed or cleared from Menu 13.3.
To get the Menu 13 display:
1. Log onto the system manager terminal.
2. From the Main Menu, select option 13 - System Maintenance.
3. From Menu 13, select option 2 - Review Status Log or option3 - Scroll Status Log.
4. The status log, plus an inventory of the message server’s software,starts scrolling on the screen. To pause, press any key. To resumescrolling, press any key. To end the scrolling, press ^C.
5. Print a copy of the log by pressing P (Menu 13.2 only).
The beginning of the printout will resemble Figure 1-5.
21 APR 92 11:39:43AM 1.51 MASTERVPMOD Serial # ........ 1234 Software Release ....Card 0 F Prom: 91.03 Disk: 91.54 Card 7 L CPU ALine Card Digitization Rate: B Telephone System TypeScanner Card Prom 88.03 Boot Prom ........ 91.13 IPMenus ............ 32.35 Termcap .......... 32.22Operating System .......... 92.32.06 System Services .System Manager ............ 92.32.07 Trees ...........Purge Task ................ 92.32.04 Line Tasks ......X25 Operation ............. 92.32.02 ACL Task ........ASA Task .................. 92.32.03 IMSO Task .......IMSI Task ................. 92.32.02 OET Task ........
06 APR 92 01:31:01PM*** Error Log Cleared By System Manager>>> INFORMATION ONLY00000 14C09500 05000000 0000016B 53420100 *.........00010 77D31F00 *w...
06 APR 92 01:31:10PM*** Software Alarms Cleared By System Manager>>> INFORMATION ONLY00000 14C09500 08000000 00000A6B 53420100 *.........00010 B8E31F00 *....
16 APR 92 06:49:14PM
*** System Restarted>>> INVESTIGATE SYSTEM ENVIRONMENT
00000 1BC09500 00000000 00000EE9 8C420100 *.........00010 30041609 8C420091 C31F00 *0....B...
When status logwas displayed
Softwareinventory
When entrywas logged
Recommended
Offsetcount
Entry in hexadecimal Entry in
Figure 1-5. Menu 13 Display Example
action forsystem manager
English status code
8 STATUS LOG
READING THE STATUS LOG
Selected Parts of Figure
Recommended action for system manager. These recommendations areintended for the system manager. There are four possible: InformationOnly, Monitor Closely, Investigate System Environment, Notify SupportRepresentative.
Entry in hexadecimal. This is the raw data of the status log entry. Theseare the codes that this manual explains.
Entry in ASCII. This is also the raw data of the status log entry, butexpressed as ASCII characters. Periods are substituted for non-printablecharacters (00-1F, 7F-FF). This form of the entry helps in reading thosedata fields that are written in ASCII. Also, patterns can be more easily rec-ognized in this form.
STATUS LOG 9
READING THE STATUS LOG
.. A1.51: 85.03 CPU B: 85.09: 1 - North AmericanL Extension .... 32.36
.......... 92.32.05
.......... 92.32.06
.......... 92.32.05
.......... 92.32.02
.......... 92.32.02
.......... 92.32.02
..kSB..* *
..kSB..* *
....B..*
.. *
ASCII
1.3.2 Display from Menu 20 While Off-Line
The easiest way to check the status log while off-line is through Menu 20.This display is the same as with Menu 13.2: the entries are separated fromeach other, ordered from oldest to newest and partially translated.
To get the Menu 20 display:
1. Activate the service option.
2. At the ENTER BOOT COMMAND: prompt, press ^DU. The systemwill continue with most of the boot process.
3. From Menu 20, select the Display Status Log option.
4. The status log, plus an inventory of the message server’s software,starts scrolling on the screen. To pause, press any key. To resumescrolling, press any key. To end the scrolling, press ^C.
5. Print a copy of the log by pressing P.
The beginning of the printout will resemble Figure 1-6.
21 APR 92 11:39:43AM 1.51 MASTERVPMOD Serial # ........ 1234 Software Release ....Card 0 F Prom: 91.03 Disk: 91.54 Card 7 L CPU ALine Card Digitization Rate: B Telephone System TypeScanner Card Prom 88.03 Boot Prom ........ 91.13 IPMenus ............ 32.35 Termcap .......... 32.22Operating System .......... 92.32.06 System Services .System Manager ............ 92.32.07 Trees ...........Purge Task ................ 92.32.04 Line Tasks ......X25 Operation ............. 92.32.02 ACL Task ........ASA Task .................. 92.32.03 IMSO Task .......IMSI Task ................. 92.32.02 OET Task ........
06 APR 92 01:31:01PM*** Error Log Cleared By System Manager>>> INFORMATION ONLY00000 14C09500 05000000 0000016B 53420100 *.........00010 77D31F00 *w...
06 APR 92 01:31:10PM*** Software Alarms Cleared By System Manager>>> INFORMATION ONLY00000 14C09500 08000000 00000A6B 53420100 *.........00010 B8E31F00 *....
16 APR 92 06:49:14PM*** System Restarted
>>> INVESTIGATE SYSTEM ENVIRONMENT00000 1BC09500 00000000 00000EE9 8C420100 *.........
00010 30041609 8C420091 C31F00 *0....B...
When status logwas displayed
Softwareinventory
When entrywas logged
Recommended
Offsetcount
Entry in hexadecimal Entry in
Figure 1-6. Menu 20 Display Example
action forsystem manager
English status code
10 STATUS LOG
READING THE STATUS LOG
Selected Parts of Figure
Recommended action for system manager. These recommendations areintended for the system manager. There are four possible: InformationOnly, Monitor Closely, Investigate System Environment, Notify SupportRepresentative.
Entry in hexadecimal. This is the raw data of the status log entry. Theseare the codes that this manual explains.
Entry in ASCII. This is also the raw data of the status log entry, butexpressed as ASCII characters. Periods are substituted for non-printablecharacters (00-1F, 7F-FF). This form of the entry helps in reading thosedata fields that are written in ASCII. Also, patterns can be more easily rec-ognized in this form.
STATUS LOG 11
READING THE STATUS LOG
1.3.3 Display from Disk Utilities
An alternative way to read the status log is through the disk utilities. In thiscase, only the raw data is displayed. Entries must be located and separatedfrom the log before they can be interpreted.
To get the disk utilities display:
1. Activate the service option.
2. At the ENTER BOOT COMMAND: prompt, press ^DI.
3. From the Install Options menu, select option I - Disk Utility.
4. From the Disk Utility Options menu, select option A - Read DiskRecord.
5. At ENTER READ DRIVE NUMBER:, enter 0 or, if reading Drive 0fails and if there are two system drives, enter 1.
6. At ENTER FILE NUMBER (HEX):, enter the file number fromTable 1-3; at ENTER RECORD NUMBER (HEX):, enter 0; atENTER NUMBER OF RECORDS (HEX):, enter 1.
7. Press any key to return to the Disk Utility menu.
8. Select option D - Display Record Buffer.
9. For a printout, make sure the printer is connected and turned on.On a Wyse 50 terminal, press Shift-Ctrl-Print simultaneously. Onan HP 700/43 terminal, press the Copy Pr key.
10. At ENTER RECORD DISPLACEMENT (0-0x27ff):, enter thebeginning offset of the status log from Table 1-3.
11. The log starts scrolling on the screen. To pause, press any key. Toresume scrolling, press any key. To end the scrolling, press ^C.
The beginning of the printout will resemble Figure 1-7.
Status log in hexadecimalOffsetcount
Overflow flagOffset ofoldest entry
Offset ofnext entry
Figure 1-7. Disk Utilities Display Example
End-of-entrycharacter
ENTER RECORD DISPLACEMENT (0-0x27ff): 2DB
002E0 = 3E 14 C0 95 00 05 00 00 00 00 00 01 6B 53 42 01002F0 = 00 77 D3 1F 00 3E 14 C0 95 00 08 00 00 00 00 0000300 = 0A 6B 53 42 01 00 B8 E3 1F 00 3E 1B C0 95 00 0000310 = 00 00 00 00 00 0E E9 8C 42 01 00 30 04 16 09 8C00320 = 42 00 91 C3 1F 00 3E 1B C0 95 00 00 00 00 00 0000330 = 00 10 41 A7 42 01 00 30 FF FF FF FF FF FF 91 C300340 = 1F 00 3E 1B C0 95 00 00 00 00 00 00 00 36 5A A700350 = 42 01 00 30 FF FF FF FF FF FF 91 C3 1F 00 3E 3E00360 = 3E 3E 3E 3E 3E 3E 3E 3E 3E 3E 3E 3E 3E 3E 3E 3E
002DB = 06 00 84 00 00
12 STATUS LOG
READING THE STATUS LOG
Selected Parts of Figure
Offset of oldest entry. The first two bytes of the status log are a pointer tothe oldest entry. In this example, the first entry is at offset 06 in the statuslog, or offset 02E1 in record 29. This is always the case when the ring bufferhas not overflowed.
Offset of next entry. The next two bytes are a pointer to where the nextentry will go. The entry preceding this point is the most recent one. In thisexample, the next entry will start at offset 84 in the status log, or offset 035Fin record 29. The unused portion of the status log is filled with the end-of-entry character when the ring buffer has not overflowed.
Overflow flag. A 00 in this byte means the ring buffer has not overflowed. A01 means it has overflowed and entries have been lost.
End-of-entry character. Offset 05 in the status log always holds the end-of-entry character: 3E. This character is copied onto the end of every entry.In the example, the end-of-entry characters have been highlighted to showhow they set off the individual entries.
Status log in hexadecimal. This is the raw data of the status log entries.To interpret these codes with this manual, copy the numbers from betweena pair of end-of-entry characters. Arrange the numbers in rows 16 bytes (32digits) long and similar to the entries in the Menu 13.2 display, (seeFigure 1-5, “Menu 13 Display Example,” on page 8). This is the format usedby the descriptions in Chapter 2.
Table 1-3. Status Log Locations
File Type Location
SSTFile 04Offset 02DB - 0ADA
Record 50File 2DOffset 18B0 - 20AF
STATUS LOG 13
READING THE STATUS LOG
1.3.4 Display from Datafile Utilities
An alternative way to read the status log is through the datafile utilitiesunder Menu 20. In this case, only the raw data is displayed. Entries must belocated and separated from the log before they can be interpreted.
To get the datafile utilities display:
1. Log onto the system manager terminal. Or, at the ENTER BOOTCOMMAND: prompt, press ^DU and then skip to step 3.
2. From the Main Menu, select option 20 - Service Operations.
3. From Menu 20, select the Datafile Utilities option.
4. From the Datafile Utilities menu, select option 1 - Read DatafileRecord.
5. At Enter position of source drive:, enter 0 or, if reading Drive 0fails and if there are two system drives, enter 1.
6. As prompted, enter the parameters from Table 1-4.
7. At Enter record half (1-2):, enter 1 or 2 as desired.
8. The Datafile Utilities menu re-appears. Select option 3 - DisplayRecord.
9. For a printout, make sure the printer is connected and turned on.On a Wyse 50 terminal, press Shift-Ctrl-Print simultaneously. Onan HP 700/43 terminal, press the Copy Pr key.
10. At Enter start address (0-27FF)[hex]:, enter the beginning offsetof the status log from Table 1-4.
11. The log starts scrolling on the screen. To pause, press any key. Toresume scrolling, press any key. To end the scrolling, press ^C.
The beginning of the printout will resemble Figure 1-8.
Enter start address(0-27FF)[hex]: 02DB
000002E0 3E 14 C0 95 00 05 00 00 00 00 00 01 6B 53 42 01 *>...........kSB.*000002F0 00 77 D3 1F 00 3E 14 C0 95 00 08 00 00 00 00 00 *.w...>..........*00000300 0A 6B 53 42 01 00 B8 E3 1F 00 3E 1B C0 95 00 00 *.kSB......>.....*00000310 00 00 00 00 00 0E E9 8C 42 01 00 30 04 16 09 8C *........B..0....*00000320 42 00 91 C3 1F 00 3E 1B C0 95 00 00 00 00 00 00 *B.....>.........*00000330 00 10 41 A7 42 01 00 30 FF FF FF FF FF FF 91 C3 *..A.B..0........*00000340 1F 00 3E 1B C0 95 00 00 00 00 00 00 00 36 5A A7 *..>..........6Z.*00000350 42 01 00 30 FF FF FF FF FF FF 91 C3 1F 00 3E 3E *B..0..........>>*00000360 THRU 00000AD0 CONTAIN 3E00000AD0 3E 3E 3E 3E 3E 3E 3E 3E 3E 3E 3E EF F7 8C F6 4F *>>>>>>>>>>>....O*
End-of-entrycharacter Overflow flag
Offset ofoldest entry
Offset ofnext entry
Figure 1-8. Datafile Utilities Display Example
Display Record
000002D0 06 00 84 00 00 * .....*
Offsetcount
Status log in hexadecimal Status login ASCII
14 STATUS LOG
READING THE STATUS LOG
Selected Parts of Figure
Offset of oldest entry. The first two bytes of the status log are a pointer tothe oldest entry. In this example, the first entry is at offset 06 in the statuslog, or offset 02E1 in record 29. This is always the case when the ring bufferhas not overflowed.
Offset of next entry. The next two bytes are a pointer to where the nextentry will go. The entry preceding this point is the most recent one. In thisexample, the next entry will start at offset 84 in the status log, or offset 035Fin record 29. The unused portion of the status log is filled with the end-of-entry character when the ring buffer has not overflowed.
Overflow flag. A 00 in this byte means the ring buffer has not overflowed. A01 means it has overflowed and entries have been lost.
End-of-entry character. Offset 05 in the status log always holds the end-of-entry character: 3E (> in ASCII). This character is copied onto the end ofevery entry. In the example, the end-of-entry characters have been high-lighted to show how they set off the individual entries.
Status log in hexadecimal. This is the raw data of the status log entries.To interpret these codes with this manual, copy the numbers from betweena pair of end-of-entry characters. Arrange the numbers in rows 16 bytes (32digits) long and similar to the entries in the Menu 13.2 display, (seeFigure 1-5, “Menu 13 Display Example,” on page 8). This is the format usedby the descriptions in Chapter 2.
Status log in ASCII. This is also the raw data of the status log entries, butexpressed as ASCII characters. Periods are substituted for non-printablecharacters (00-1F, 7F-FF). This form of the status log helps in reading thosedata fields that are written in ASCII. Also, patterns can be more recogniz-able in this form. It is especially helpful in spotting the end-of-entry charac-ters (>) between entries.
Table 1-4. Status Log Locations in Datafile Format
Parameter …in SST …in Record 50
Datafile Type 2 - System 3 - UtilityDatafile Subtype 0 - SST 0 - Dump RecordsRecord Number 0 0Offset (Start Address) 02DB-0ADA 18B0-20AF
STATUS LOG 15
READING THE STATUS LOG
..............G. ..............G.OK
..4.....(....T.. ..6...........W#
FL=00003202
0003B4
B..w...>..... ......kSB......>
...B.....>....
........
>>>>>>>>>
Status login ASCII
.....
1.3.5 Display from Dump
When a message server is shut down using Menu 13.1, it does an exten-sive dump that includes the status log. As with the Disk Utilities, this displayis raw data and must be interpreted in the same way.
To get the dump display:
1. Log onto the system manager terminal.
2. From the Main Menu, select option 13 - System Maintenance.
3. From Menu 13, select option 1 - Shut Down with Dump.
4. From Menu 13.1, select option 1 - allow lines to clear.
5. The dump starts scrolling on the screen and on the printer. Topause, press any key. To resume scrolling, press any key. To endthe scrolling, press ^C.
The printout will resemble Figure 1-9. The status log is almost the last thingin the dump, coming after several pages of the execution trace and the CBtrace buffer.
CLEANUP OF PRIMARY FILE CARD:FF800037 18 00 A8 00 00 00 00 00 00 00 00 00 00 AC 47 95 FF800047 18 00 B8 00 00 00 00 00 00 00 00 00 00 AC 47 A5
** SST VALIDITY CHECK PASSED **
FF800037 18 00 34 00 0C 00 00 00 28 B8 90 CE EF 54 E5 17 FF800047 18 00 36 00 00 00 00 00 00 00 10 00 11 BD 57 23 FF800047 18 00 35 00 00 00 00 00 00 00 00 00 00 AC 47 22 ..5...........G”
SHUT-DOWN : Task ID: 0095 INT Nesting: 0000 Clock: 00B015C1CS:EIP=0089:000036C5 DS=0064 ES=01D8 FS=0000 GS=0000 SS=009D E EAX EBX ECX EDI EDX ESI ESP EBP00000000 00006D17 0000001F 000038A7 00000000 00000000 000003A4 00
1992-04-21 11:44:10
Execution Trace:CB Trace Buffer:SC Trace Buffer:
Status Log:
00000010 01 6B 53 42 01 00 77 D3 1F 00 3E 14 C0 95 00 08 .kS00000020 00 00 00 00 00 0A 6B 53 42 01 00 B8 E3 1F 00 3E 00000030 1B C0 95 00 00 00 00 00 00 00 0E E9 8C 42 01 00 .............B..00000040 30 04 16 09 8C 42 00 91 C3 1F 00 3E 1B C0 95 00 0.00000050 00 00 00 00 00 00 10 41 A7 42 01 00 30 FF FF FF .......A.B..0...00000060 FF FF FF 91 C3 1F 00 3E 1B C0 95 00 00 00 00 00 .......>00000070 00 00 36 5A A7 42 01 00 30 FF FF FF FF FF FF 91 ..6Z.B..0.......00000080 C3 1F 00 3E 3E 3E 3E 3E 3E 3E 3E 3E 3E 3E 3E 3E ...>>>>
End-of-entry character
Overflow flag
Offset of next entry
Offset ofoldest entry
Offsetcount
Status log in hexadecimal
When status logwas displayed
Figure 1-9. Dump Display Example
00000000 06 00 84 00 00 3E 14 C0 95 00 05 00 00 00 00 00 .....>.....
16 STATUS LOG
READING THE STATUS LOG
Selected Parts of Figure
Offset of oldest entry. The first two bytes of the status log are a pointer tothe oldest entry. In this example, the first entry is at offset 06 in the statuslog. This is always the case when the ring buffer has not overflowed.
Offset of next entry. The next two bytes are a pointer to where the nextentry will go. The entry preceding this point is the most recent one. In thisexample, the next entry will start at offset 84 in the status log. The unusedportion of the status log is filled with the end-of-entry character when thering buffer has not overflowed.
Overflow flag. A 00 in this byte means the ring buffer has not overflowed.A 01 means it has overflowed and entries have been lost.
End-of-entry character. The byte at offset 05 always holds the end-of-entry character: 3E (> in ASCII). This character is copied onto the end ofevery entry. In the example, the end-of-entry characters have been high-lighted to show how they set off the individual entries.
Status log in hexadecimal. This is the raw data of the status log entries.To interpret these codes with this manual, copy the numbers from betweena pair of end-of-entry characters. Arrange the numbers in rows 16 bytes (32digits) long and similar to the entries in the Menu 13.2 display, (seeFigure 1-5, “Menu 13 Display Example,” on page 8). This is the format usedby the descriptions in Chapter 2.
Status log in ASCII. This is also the raw data of the status log entries, butexpressed as ASCII characters. Periods are substituted for non-printablecharacters (00-1F, 7F-FF). This form of the status log helps in reading thosedata fields that are written in ASCII. Also, patterns can be more recogniz-able in this form. It is especially helpful in spotting the end-of-entry charac-ters (>) between entries.
STATUS LOG 17
READING THE STATUS LOG
Fieldgroups
n
y header
isters during eventnner input message
Entry header
IORB header
CB-out messageCB-in messageRegistersduring event
1.4 READING A STATUS CODE DESCRIPTION
Descriptions for status log entries are in Chapter Two. They are listed innumerical order, based on the status code in offset 04-05. Adjacent statuscodes using the same format may be grouped together. A typical descrip-tion is shown in Figure 1-10.
1A Scanner Task Protocol Error
01 Could not attach scanner. AX contains the return code from the attachment routine.
02 Invalid channel referenced by scanner. The channel number is in the scanner input message.
03 Invalid scanner message.
04 Invalid type sent from scanner in line status message. The type is defined in the scanner input message.
05 Bad return code from system partition.
06 Bad return code in control bus message from file card.
Status code
Subcodes using
Key fields
Fields of anon-standard group
Subcodes usingone format
another format
Figure 1-10. Example Status Code Explanatio
Entry format
00020
Entr
Reg
Task ID
AX IP CS
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F ScaSC messagetype & port
00020 20212223 24252627 28292A2B 2C2D2E2F
Task ID
CS IPAX BX CX DX SI DI DS ES
Peripheraladdress
00000 00010203 04050607 08090A0B 0C0D0E0F00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
CB task ID
Control busmessage types
18 STATUS LOG
READING THE STATUS LOG
Selected Parts of Figure
Subcodes using one or another format. The subcodes, in offset 08-09,provide the specific meaning of the entry. Typically, only offset 08 is high-lighted in the illustrations. Subcodes rarely extend to using offset 09, so it isusually zero. Subcodes using the same format are grouped together.
Entry format. The entries are illustrated with a format similar to Menu13.2’s display. Other displays can be used by keeping track of the offsetswithin each entry. The values shown in the illustrations are the offsets. Thatis, offset 02 of an illustration shows “02”; offset 3C shows “3C”.
Key fields. Fields that are of frequent interest are shaded.
Field groups. The fields of an entry can usually be grouped together. Thegroups are labelled on the illustration’s right side. Three standard groupsare detailed in the next section: entry header, IORB header and control busmessage.
Fields of a non-standard group. Fields that are not part of a standardgroup are explained in a table below the format illustration.
STATUS LOG 19
READING THE STATUS LOG
1.5 STANDARD FIELD GROUPS
There are three standard groups used in status log entries:
• The entry header is the first part of every entry.
• The IORB (Input/Output Request Block) header gives informationabout an exchange of control bus messages.
• Control bus messages carry instructions and data between the CPand other parts of the message server.
These structures are not detailed in the status code descriptions (except foridentifying key fields). Instead, they are explained here.
There is one other commonly occurring group: “Registers during event”.This group shows the contents of various registers of the microprocessor ofthe CP at the time the status event was recognized. The register contentsare used in high-level troubleshooting. The format of the register group var-ies from status code to status code. For more information about the regis-ters, see the data sheet of the microprocessor.
STATUS LOG 21
READING THE STATUS LOG
1.5.1 Entry Header
The entry header is the first part of every status log entry. It is formallyknown as the error control block common header. Besides defining whatthe entry is about, the header provides some standard information. SeeFigure 1-11.
Figure 1-11. Entry Header Format
00010203 04050607 08090A0B 0C0D0E0F
Entrylength
Flags
Task ID
Severitycode
Statuscode
Device
Subcode
Time stamp CountID
22 STATUS LOG
READING THE STATUS LOG
Key Fields
Task ID. Identifies the software task that generated the entry. This is astrong clue to what operation or board is having a problem. Line tasks alsoindicate a particular port. Translate the task ID with Table 1-5 and Table 1-6on the following pages.
Status code. This code identifies the event or class of events that causedthe entry. The status codes are listed in numerical order in Chapter Two.
Subcode. This code, when used, identifies the event more precisely thanthe status code. Although the subcode is a two-byte field, the descriptions inChapter Two usually highlight only one byte, offset 08. In these cases, off-set 09 is always zero and can be ignored.
Other Fields
Entry length. The number of bytes in the total entry.
Flags. The bits of this field are independently-set flags. The following val-ues add together to form the value in the field:
01 (Bit 0 set.) The message server terminated the task and restarted.
02 (Bit 1 set.) New, expanded EDB format.
20 (Bit 5 set.) OS related.
40 (Bit 6 set.) Request from an application task instead of an OS rou-tine.
80 (Bit 7 set.) Task related.
Severity code. Indicates how severely the event affected system opera-tion. The codes are:
00 Possibly significant event.
01 Recovered from error.
02 Degraded session.
03 User interaction terminated.
04 Line restarted.
05 Single user long-term error.
06 Multiple user long-term error.
07 System reset occurred.
08 Task terminated.
09 Task restarted.
Device ID. The meaning of the code depends on what task or module gen-erated the entry. Generally, the value will be 0000.
Time stamp. This field records when the entry was logged. The three bytesfrom offset 0B-0D are the count of minutes since midnight, January 1, 1984.The first byte of the time stamp, offset 0A, is the count of seconds within theminute. Translate with “Reading the Time Stamp” on page 26.
Count. The occurrence count is 00 or 01 depending on the task.
STATUS LOG 23
READING THE STATUS LOG
Table 1-5. Task IDs
Task ID
Task Name
00-8F Line Tasks—To find the port, use Table 1-6.90 Root Task91 Scan Task 092 Scan Task 193 Scan Task 294 File Task 0
95-9C System Management Tasks 0-7 respectively9D Purge Task9E Minute Task9F File Task 1
A0 File Task 2A1 File Task 3A2 X.25 TaskA3 OCL Task
A4 ASA TaskA5 SMDI Task StartA6 UnusedA7 SMDI Task End
A8 IMS TaskA9 IMS TaskAA Overflow Evaluation TaskAB Simplified Protocol Task
AC SMS TaskAD Background TaskAE Modem TaskAF SBR Task
B0 Administrative Task (unused in Aria 1.0)B1 ABCA Communications Handler Task
(unused in Aria 1.0)B2 Unused
B3-C3 Digital-networking mail tasksC4-E8 Unused
E9 Poll Daemon TaskEA Modem Daemon TaskEB Test Daemon TaskEC File System Cleanup Daemon TaskED SCSI TaskEE Debug TaskEF Idle Task
F0-FF Unused
24 STATUS LOG
READING THE STATUS LOG
Table 1-6. Task ID to Port
TaskID
350Port
250Port
TaskID
350Port
250Port
TaskID
350Port
TaskID
350Port
00 1A 1A 24 4A 5E 48 7A 6C 10A01 1B 1B 25 4B 5F 49 7B 6D 10B02 1C 1C 26 4C 5G 4A 7C 6E 10C03 1D 1D 27 4D 5H 4B 7D 6F 10D
04 1E 1E 28 4E 6A 4C 7E 70 10E05 1F 1F 29 4F 6B 4D 7F 71 10F06 1G 1G 2A 4G 6C 4E 7G 72 10G07 1H 1H 2B 4H 6D 4F 7H 73 10H
08 1I 2A 2C 4I 6E 50 7I 74 10I09 1J 2B 2D 4J 6F 51 7J 75 10J0A 1K 2C 2E 4K 6G 52 7K 76 10K0B 1L 2D 2F 4L 6H 53 7L 77 10L
0C 2A 2E 30 5A 7A 54 8A 78 11A0D 2B 2F 31 5B 7B 55 8B 79 11B0E 2C 2G 32 5C 7C 56 8C 7A 11C0F 2D 2H 33 5D 7D 57 8D 7B 11D
10 2E 3A 34 5E 7E 58 8E 7C 11E11 2F 3B 35 5F 7F 59 8F 7D 11F12 2G 3C 36 5G 7G 5A 8G 7E 11G13 2H 3D 37 5H 7H 5B 8H 7F 11H
14 2I 3E 38 5I 8A 5C 8I 80 11I15 2J 3F 39 5J 8B 5D 8J 81 11J16 2K 3G 3A 5K 8C 5E 8K 82 11K17 2L 3H 3B 5L 8D 5F 8L 83 11L
18 3A 4A 3C 6A 8E 60 9A 84 12A19 3B 4B 3D 6B 8F 61 9B 85 12B1A 3C 4C 3E 6C 8G 62 9C 86 12C1B 3D 4D 3F 6D 8H 63 9D 87 12D
1C 3E 4E 40 6E 9A 64 9E 88 12E1D 3F 4F 41 6F 9B 65 9F 89 12F1E 3G 4G 42 6G 9C 66 9G 8A 12G1F 3H 4H 43 6H 9D 67 9H 8B 12H
20 3I 5A 44 6I 9E 68 9I 8C 12I21 3J 5B 45 6J 9F 69 9J 8D 12J22 3K 5C 46 6K 9G 6A 9K 8E 12K23 3L 5D 47 6L 9H 6B 9L 8F 12L
STATUS LOG 25
READING THE STATUS LOG
Example
.083328r of day = 18
ute of hour = 5
ond of minute = 455:45 or 6:05:45 PM
65D 4961885⇒
61885440--------------- 3445.753472=
3445.753472
teger Fractional
53472 24×
83328 60× 4.99968=
45⇒
Reading the Time Stamp
The time stamp is decoded into a regular date and time as part of the Menu13 display. But when displaying the status log with the disk utilities or theshutdown dump use the following method to find when an entry was logged.
These instructions are designed for use with a calculator that has a hex-to-decimal conversion function. In most cases you will already know the dateand can stop after finding the time. The example column shows the resultsof the steps on a time stamp of 2D5DB64B.
Table 1-7. Reading the Time Stamp
Step#
Step Description
Find the Time1 Transpose the minutes value and convert it to decimal.
2 Divide by the number of minutes per day: 1440.
3 Note the integer portion and subtract it.
4 Multiply the fractional portion by the number of hours per day: 24. =18
5 Note the integer portion and subtract it. The integer portion is the hour of the day on a 24-hour clock.
Hou
6 Multiply the fractional portion by the number of minutes per hour: 60. Round to the nearest minute and note the result. (Any frac-tional portion is due to the calculator’s round-off error in step 2.)
Min
7 Convert the seconds value to decimal.Sec
8 Combine the results from steps 5, 6 and 7. This is the time on a 24-hour clock.
18:0
Figure 1-12. Entry Header with Time Stamp Detail
00010203 04050607 08090A0B 0C0D0E0F
Seconds Minutes
4BB
491
------
In
0.7
0.0
2D
26 STATUS LOG
READING THE STATUS LOG
ear4 + 9 = 1993
9.9999999 of the year = 160 - 3 = 157
y of the year = 1, then: = -2; -2 + 32 = 30;
3 -1 = 1992 is 30 December 1992th is June
- 151 +1 = 7 of the month = 7ne 1993
d)
Example
4565-------- 9.4383562=
3835616 365×
Find the Date9 Divide the integer portion from step 2 by the number of days per
year: 365.
10 Note the integer portion and subtract it. 9th y11 Mentally, add the integer portion to 1984 and note it. This is the
year the entry was logged.198
12 Multiply the fractional portion from step 10 by the number of days per year: 365. Round to the nearest day. (Any fractional portion is due to the calculator’s round-off error in step 9.)
= 15Day
13 Subtract the number of leap days from 1984 to the year before the entry was logged. (Leap years through 2000 are: 1984, 1988, 1992, 1996, 2000.)
160
If the result is negative, add 32 to it. Subtract 1 from the year found in step 11. The month is December. Skip the rest of the steps.
If da1 - 3199Date
14 Determine the month with the table below. Use the regular or leap year column depending on the year the entry was logged.
Mon
15 Subtract the lower value of the month’s range. Add 1. 157Day
16 Combine the results from steps 11, 14 and 15. 7 Ju
Table 1-7. Reading the Time Stamp (Continue
Step#
Step Description
343----
0.4
RegularYear
MonthLeapYear
0-30 January 0-3031-58 February 31-5959-89 March 60-9090-119 April 91-120120-150 May 121-151151-180 June 152-181181-211 July 182-212212-242 August 213-243243-272 September 244-273273-303 October 274-304304-333 November 305-334334-364 December 335-365
STATUS LOG 27
READING THE STATUS LOG
1.5.2 IORB Header
The IORB (Input/Output Request Block) header gives information about anexchange of control bus messages. The header is 32 bytes long. SeeFigure 1-16.
Figure 1-13. IORB Header
00010203 04050607 08090A0B 0C0D0E0F10111213 14151617 18191A1B
Initialevent
Peripheraladdress
Terminal mode
Function
EventStatuscode
Data transfercount
Data transferaddress
Priority Time-out
Unused
period, in ms
28 STATUS LOG
READING THE STATUS LOG
Key Field
Peripheral address. This field identifies the peripheral, or destination, cardthat the CP was communicating with through the CB messages. Theperipheral is identified in terms of a bank, slot and channel. Each of these isexpressed as a four-bit number (one hex digit) as shown in Figure 1-14.Translate the peripheral address with Table 1-8 and Table 1-9 on the fol-lowing pages.
• Bank identifies a collection of slots.
• Slot identifies a card within a bank. The type of card in a particularslot depends on the message server configuration.
• Channel identifies a port on a line card.
Other Fields
Terminal mode.
00 Normal terminal channel
01 Simplified Transfer Protocol channel
Function. The meaning depends on the type of operation, as shown inTable 1-10, “IORB Function and Status Codes,” on page 33.
Status code. The meaning depends on the type of operation, as shown inTable 1-10, “IORB Function and Status Codes,” on page 33. With the Sys-tem Manager Console operation, the meaning also depends on the functioncode.
Figure 1-14. Peripheral Address Detail
00010203 04050607 08090A0B 0C0D0E0F10111213 14151617 18191A1B 1C1D1E1F
Peripheraladdress
0405BankChannel Slot
System ID
STATUS LOG 29
READING THE STATUS LOG
Table 1-8. Bank and Slot of the Peripheral Address
Bank Slot 350 Card 250 Card
0
0 Not used File card portion of CCF1 Card 2 Line TIC2 Card 3 Line TIC3 Card 4 Line TIC
4 Card 5 Line TIC5 Card 6 Line TIC6 Card 1 Line TIC7 Not used Line TIC
1
0 Card 8 Not used1 Card 9 Line TIC2 Card 10 Line TIC3 Card 12 Not used
4 Card 13 Not used5 Card 14 Not used6 Card 7 Not used7 Card 11 Not used
2
0 Card 161 Card 172 Card 183 Card 26
4 Card 275 Card 286 Card 257 Card 29
3
0 Card 301 Card 312 Card 323 Card 34
4 Card 355 Card 366 Not used7 Card 15
30 STATUS LOG
READING THE STATUS LOG
4
0 Not used1 Card 202 Card 213 Card 22
4 Card 235 Card 246 Card 197 Card 33
Table 1-9. Channel of the Peripheral Address
Channel350 Line Card
Port250 Line TIC
Port
0 A A1 B B2 C C3 D D
4 E E5 F F6 G G7 H H
8 I
Table 1-8. Bank and Slot of the Peripheral Address
Bank Slot 350 Card 250 Card
Figure 1-15. IORB Header with Peripheral Address Detail
00010203 04050607 08090A0B 0C0D0E0F10111213 14151617 18191A1B 1C1D1E1F
Peripheraladdress
0405BankChannel Slot
STATUS LOG 31
READING THE STATUS LOG
9 JA KB L
Table 1-9. Channel of the Peripheral Address
Channel350 Line Card
Port250 Line TIC
Port
32 STATUS LOG
READING THE STATUS LOG
s
us Codes
Description
failedmessage lost cancelledd incoming message temessage after writeutted by daemon
turnmessage lostmessage available, not donege availableration
failed
uestime-out
FIFO underrunFIFO overrunum (CRC error)
turnueue empty
faileduestonnected
, RX = 1200, RX = 9600, RX = 75
ode offode on
Table 1-10. IORB Function and Status Code
OperationFunction Codes Stat
Code Description Code
Control Bus
00 Read 00 OK01 Write, then read 01 Operation02 Cancel current operation 02 Incoming 03 Write 03 Operation04 Reset peripheral device 04 Unsolicite
before wri05 Special post operation 05 Incoming
08 I/O time-o09 Task abor
Scanner Card
00 Read 00 Normal re01 Write 01 Incoming 02 Read conditional 02 Incoming
write was 03 Cancel read 03 No messa04 Unconditional write 04 Invalid ope
05 Operation
Data Bus
00 FS from/to LC 00 OK01 CP from/to FS 01 Invalid req02 CP from/to LC 02 DB/DMA t
03 SBI DMA 04 SBI DMA 05 DB checks
System Manager Console
(Status code depends on
function code)
00 Read 00 Normal re01 Write 01 Receiver q03 Write unconditional 02 Operation04 Cancel write 03 Invalid req05 Connect terminal 04 Task not c
06 Disconnect terminal07 Read block08 Get input count0A Open physical terminal channel
02 Set baud rate 00 TX = 120001 TX = 960002 TX = 1200
09 Set/reset raw input mode 00 Set raw m01 Set raw m
STATUS LOG 33
READING THE STATUS LOG
message lostmessage is available failed
lunchion aborted by OSX write doneait done
ACP event time-out
tinued)
us Codes
Description
il
ACP
00 ACP card read 00 OK01 ACP card write 01 Incoming 02 ACP post 02 Incoming 03 ACP get buffer 03 Operation
04 ACP wait on timer 04 ACP out to05 Set up multiple wait 05 ACP funct06 Write to serial port 06 Serial port
07 Multiple w
08 LC postedFF Operation
Table 1-10. IORB Function and Status Codes (Con
OperationFunction Codes Stat
Code Description Code
Figure 1-16. IORB Header with Function and Status Code Deta
00010203 04050607 08090A0B 0C0D0E0F10111213 14151617 18191A1B 1C1D1E1F
FunctionStatuscode
34 STATUS LOG
READING THE STATUS LOG
1.5.3 Control Bus Messages
The CP uses control bus messages to exchange instructions and data withother parts of the message server. The messages usually appear in the sta-tus log as request/response pairs (CB-out and CB-in, respectively). Usually,requests come from the CP and responses go to the CP. Each message is16 bytes long. See Figure 1-17.
The response message echoes the task ID and peripheral address (offset00-01) of the request. Offset 03 of the response is usually a return code.
Sometimes, the message type of the request message does not match upwith that of the response message, perhaps showing a nonsensical typesuch as 00 or FF. Offsets 03 and 04 of the request are sometimes overwrit-ten in the course of logging the entry. This does not interfere with the sys-tem’s operation but does make interpreting the status log entry moredifficult. In such a case, assume the request was appropriate to theresponse. If this is not adequate, check the CB Trace Buffer. The mostrecent messages are saved in offset 10A0-189F of Record 50, and can beread there or in the CB Trace Buffer portion of the shutdown dump.
000102
Task IDMessage
Peripheral
Packet Data
Figure 1-17. Control Bus Message Format
address
type
STATUS LOG 35
READING THE STATUS LOG
Key Fields
Task ID. Also known as the source ID, it identifies the task that producedthe request message. Line tasks can also be associated with a particularport. Translate the task ID with Table 1-5, “Task IDs,” on page 24.
Message type. Indicates the meaning of the message and how to interpretits packet data. The message type depends on the kind of card that the CPwas communicating with. Determine that with the peripheral address (seebelow). Find descriptions of the control bus message types for:
File cards in Chapter 3
Line cards in Chapter 4
ACPs in Chapter 5
PIC cards in Chapter 6
LAN cards in Chapter 7
Since control bus messages are usually logged in request/response pairs,the descriptions are organized by the message type of the request. Theresponse is described immediately after the request.
Other Fields
Peripheral address. Also known as the destination ID, it indicates the cardthe CP is communicating with. This is the same value as in offset 04 of theIORB header. Since the bank value is missing, the field’s usefulness is lim-ited. Check offsets 04-05 of the IORB header for full destination information.See Section 1.5.2, “IORB Header,” on page 28.
Packet data. Thirteen bytes of data whose interpretation depends on themessage type. Packet data formats for each message type are described inChapters 3 through 6.
36 STATUS LOG
CHAPTER 2: STATUS CODES
This chapter describes all status codes. They are listed in numerical order, based on the status code inoffset 04-05 (after transposing):
All values in the illustrations are the bytes’ offsets, not sample data. Adjacent status codes using thesame format may be grouped together.
See Section 1.4, “READING A STATUS CODE DESCRIPTION,” on page 18 and Section 1.5, “STAN-DARD FIELD GROUPS,” on page 21.
To link to the description of a status code, click on the entry for it in the index below.
Index
00 Boot Reason and Time 4401 Failed SST Validity Check During Boot Process 4502 Scanner Wrong Incoming Message 4503 Scanner No Carrier After Ring 4604 RS-232 Integration Link Reset 4605 Status Log Cleared 4706 Error During Garbage Collect 4707 SMT Internal Error 4708 SMT Software Alarms Cleared 4709 Software Download Utility Error 480A SMT Invalid User Record Lock State 480B SMT File System I/O Error 480C SMT-Related OCL Error 490D SMT-Related File Management Error 500E SMT-Related X.25 Line Error 520F File Creation Informational Entry 5410 SMT-Related AMIS Internal Error 5511 Error During Upgrade Performed by SMT 5512 SMT Could Not Get a New User Record 5713 SMT Could Not Find the ICN in the AMT 5714 IRN Usage Report 5815 MDS File Creation Problem 5816 LAN Initialization Failed 5817 IP Address Netmask Not Sent 5818 Error Sending Configuration Update to LAN Card 5819 Scanner Task Internal Error 591A Scanner Task Protocol Error 59
16 APR 92 06:49:14PM*** System Restarted>>> INVESTIGATE SYSTEM ENVIRONMENT00000 1BC09500 00000000 00000EE9 8C420100 *.............B..*00010 30041609 8C420091 C31F00 *0....B..... *
Status code in offset 04-05 (transpose)
STATUS LOG # 5331, REV. C 37
1B Scanner Task Message Waiting Error 601C Message Waiting, Illegal Extension 621D Error Counters Reported by Scanner 631E Error Information from PID 641F RS-232 Link Down 7320 SMDI Internal Error 7421 SMDI Protocol Error 7522 Internal Error in the X-Interface Code 7623 Internal Error in the OCL Interface Code 8424 EAP-Related Error 8525 Error in the OCL System Utility Routin 9026 Internal Error Occurred During IVR Application 9127 Internal Error Occurred During ASA Application 9328 Internal Error in the OCL Task 9429 Internal Error in the Router Code 992E Debug Messages in X.2 1012F OCL Debug Error 10230 SP-Related OCL Error 10331 Task Loop 10432 Task Locked Out 10433 Fatal Inconsistency in the OS 10534 Fatal Inconsistency for Requestor in Application Task 10535 Control Bus Error—Minor 10536 Control Bus Error—Major 10537 Control Bus Error—Indeterminate 10538 Privilege Violation Interrupt 10539 Spurious Interrupt 1053A Data Bus Error—Unsolicited Device Interrupt 1053B Data Bus Error—Unsolicited Software Timer Interrupt 1053C Data Bus Error—Device Time-out 1053D DMA Error—Unsolicited Device Interrupt 1053E DMA Error—Unsolicited Software Timer Interrupt 1053F DMA Error—Device Time-out 10540 Scanner Card Error—Minor 10641 Scanner Card Error—Major 10642 Scanner Card Error—Indeterminate 10643 System Manager I/O Error (Transmission Error) 10644 DUART-0 Spurious Device Interrupt 10645 Scanner Card Error—Acknowledgment Bad Channel 10646 Scanner Card Error—Acknowledgment Not Expected 10647 Scanner Card Error—Bad Checksum 10748 Scanner Card Error—Transmit Time-out 10849 Scanner Card Error—Transmit Time-out Maximum 1084A Scanner Card Error—Duo Errors 1094B Scanner Card Error—Parity Error 1094C Scanner Card Error 110
38 # 5331, REV. C STATUS LOG
4D ACP-Related Error 1104E PIPL Flash Upgrade Error 11250 Control Bus Error—Checksum Error 11351 Control Bus Error—Checksum Errors Exceeded Limit 11552 Control Bus Error—Checksum-Nak On Response 11553 Control Bus Error—Checksum-Nak On Transmission 11554 Control Bus Error—Checksum-Naks Exceeded Limit 11655 Control Bus Error—Invalid Channel Reference 11756 Control Bus Error—Empty Control Bus Slot 11757 Control Bus Error—Reset Peripheral 11858 Control Bus Error—Transmit Error 11859 SBI DMA FIFO Underrun 1185A SBI DMA FIFO Overrun 1185B SBI Failed to Cycle in Control Bus Input Read 1195C SBI Failed to Cycle in Control Bus Output Write 1195D Soft Reset of Control Bus Peripheral 1195E SBI DMA CRC Error 1195F X.25 Task Crashed 12060 Logic Card Status 12261 Incomplete Standby Redundant Card Set 12462 Invalid Leading Digit Dialed for Automated Attendant Transfer 12463 Channel Reset Was Successful 12564 FS/CP Software Error 12565 LC Protocol Error 12666 Line Task Internal Error 12767 Tree Invalid Parameter to Action 12968 Tree Invalid Action Sequence 13069 Tree Invalid UR Lock State 1306A Tree Missing Event 1306B Interpreter Temporary Area Overflow 1306C Bad User Record at Read 1306D Bad User Record During Processing 1306E Bad User Record at Write 1306F Tree Internal Error (Error Action) 13070 File System Drive I/O Error During a Write Operation 13171 File System DMA Time-Out 13272 Scramble Code or I/O Error During Message-Read Operation 13373 Scanner Unexpected Error Acknowledgment 13474 Scanner Wrong Incoming Message 13475 Line Task Seize Line Time-out 13476 Scanner Incoming Message at Write 13477 Scanner Incoming Queue Overflow 13478 Scanner Error Request Prior to Reset 13479 Scanner/ITIC Line Failure 1357A Message Waiting Bad Extension 1357B Data Bus Checksum Error 136
STATUS LOG # 5331, REV. C 39
7C File System Out of Synch 1367D Batch Network Transmit Error 1377E Batch Network Receive Error 1387F Batch Network File System I/O Error 13980 Batch Network Internal Error 14081 Debug Information Message 14282 Error Status from OS Scanner Drive 14383 Catastrophic Error Signalled by Scanner 14384 Bad Password Disconnect 14485 Subscriber Exited with Unheard Messages 14486 Line Task Read or Response Time-out 14587 Batch Network Returned Message—Sender’s Box Full 14688 Bad Community Record at Read 14789 Batch Network Informational Error 1488A SMDI Integration-Related Error 1488B Bad Command Code for AspenTex 1498C AMIS-Related Error 1508D AMIS EAR Array at Least 90% Full 1528E AMIS Directory at Least 90% Full 15290 Outcalling Attempted but No Outcalling Phone Number Found in User Record 15391 Message Waiting on Denied Extension for DMID—COS Does Not Allow
Message Waiting 15492 AspenNet Scheduler Error 15593 Fax Queue is Full 15694 Returned Fax—Sender’s Mailbox is Full 15695 Returned Fax—Sender’s Mailbox Does Not Exist 15696 FS/CP Software Error 15797 Purge Task Internal Error 15798 Bad User Record at Read 15799 Bad User Record During Processing 1579A Bad User Record at Write 1579B File System Drive I/O Error 1579C File System DMA Time-out 1579D Data Checksum Mismatch 1579E Data Bus Error Return Code 1579F Scramble Code Error or I/O Error 157A0 SST Bad at Write 158A1 User Record Message Directory Out of Order 158A2 Invalid User Record Lock State 158A3 Unknown Network Prefix in Group List Member 158A4 Purge Task Encountered an Error While Accessing the IVR Message Directory 159A5 Bad Member Found in Personal Group List 160A6 Error Detected by MDS Functions 160A8 SP General Error 161AA EDBN Directory Not Clean After Two Passes 163B0 Error Detected by Batch Network Node Management Functions (BNR) 164
40 # 5331, REV. C STATUS LOG
File
B1 Error Detected by Batch Network Node Management Functions (BNQ) 166B2 Error with Bulletin Mailbox (IFS) 167B3 Bad Mailbox Name Found or Software Error 168B4 Bad Network Alias Found or Software Error 175B5 Failed to Read Network Alias Record from Disk 176B6 Failed to Write Network Alias Record to Disk 176B7 System Restarted by Software—Failed to Allocate Memory for Alias Data 176B8 Failed to Write Company Record to Dis 177B9 Error in Notification Library 178BA Error in Queuing Module of Notification Library 181BC Error in the Lock Module of the Notification Library 182BD Bad Company Record Found During Start-up Process 183BE Bad User Records Found While Building AMT/NMT During System Start-up 184BF Bad INN or Function Code Found 186C1 Bad AMIS Transmission Table Found or Software Error 187C2 Failed to Write AMIS Transmission Table to Disk 187C3 Bad AMIS EAR Found or Software Problem 188C4 Failed to Write AMIS EAR Record to Disk 188C5 Bad AMIS DIR Found or Software Error 189C6 Failed to Write AMIS DIR Back to Disk 189C7 T1 Error Counters 190C8 Unable to Read Clock Chip (Continuous Ripple Status Set) 191C9 Clock Chip Went Bad While Running (After Boot) 191CA System Timer Drifted Too Far From Clock Chip Date/Time 191CB Clock Chip Bad or Too Different From SST Timer at Boot 191CC Minute Task Internal Error 191CD Hard Error on Disk Detected by Minute Task Alarm 191CE Drive Not Running Detected by Minute Task Alarm 192CF T1 Alarms 192D0 CP/FS Protocol Out of Sequence 194D1 Data Bus Operation With File System or Cluster Card Failed 195D2 Data Bus Checksum Error Between CP and File System 196D3 Control Bus Operation Failed While Preparing or Checking Data Bus Operation with
System or Cluster Card 197D4 Inconsistent or No Status from OS on Control Bus/Data Bus Operation 198D5 OS Reported Control Bus Error 199D6 File System Returned Bad Status in Control Bus Message 200D7 File System Reported Drive Error in Returned Control Bus Message 208D8 File System Reported DMA Failure on Some Previous Operation 209D9 File System Failed to Respond Within Time-out Period 210DA General File System Control Bus Status Log 211DB General File System Data Bus Status Log 213DC General Directory-Related Error 214DD Failed to Read User Record from Disk 219DE Failed to Read Company Record From Disk 220DF Failed to Write User Record to Disk 221
STATUS LOG # 5331, REV. C 41
E0 System Error 222E1 Failed to Start Application, Application Not Found, Partition Header Damaged or Cold Start
Not Available 224E2 AMT Error 225E3 Phrase Concatenation Library Failure 235E4 ASA SP Routine General Error 236E5 ASA SP Routine I/O Error 238E6 Line Card Control Bus Error 239E7 Line Card Message Contains Unexpected Value 240E8 CP/LC Protocol (Low-Level) Error 241E9 Line Card Failed to Respond Within Time-out Period 242EA Line Card Data Bus Error 243EB Message Library Failur 244EC IVR Message Directory Error 245ED Phrase Library Error 247EE Mailbox Library Error 248EF Name Announcement Library Error 249F0 System Name Annoucement Library Failure 250F1 System MID Library Failure 251F2 System MIDG Library Failure 252F4 Bad AMIS Message Array Found or Software Error 253F5 Failed to Write AMIS Message Array Back to Disk 253F6 Bad AMIS Dialing Sequence Table Found or Software Error 254F7 Failed to Write AMIS Dialing Sequence Table Back to Disk 254F8 SP AMIS I/O Error 255F9 Integration General Error 256FA IMS Error-Voice Processor-to-Host Task 266FB IMS Error—Host-to-Voice Processor Tas 268FC Error in Overflow Event Tas 270FD File Access Erro 273100 CDR RAM Buffer Overflowed 274101 CDR Disk Write Error 275102 Short Message Service (SMS) Error 276104 LAN Router Task Non-Service Errors 277105 LAN Router Task Service Error 278106 LAN API Error 279107 CP/LAN Protocol Out of Sequence 289108 LAN Timeout 290110 Control Bus Error in Getting New IUN 291111 No IUN Available 291112 Error Reading MDS Record 292113 MDS-Record Validity Check Error 292114 Error Writing MDS Record 293115 Error in AMT Search for MDS 293116 MDS File Validity Check Error 29311B Fax Queue Error 294
42 # 5331, REV. C STATUS LOG
120 DMD Entry Read Error 297121 DMD Entry Write Error 298130 SBP/SCSI Security Checksum Bad 299131 SBP/SCSI Configuration Checksum Revalidate 301132 SBP Internal Error 302141 System Backup and Recovery (SBR) General Error 303148 RMM General Error Code 313150 MDS File Access Failure for Port Testing 315151 Possible Bad Port(s) Found during Port Testing-NSA 316152 Possible Bad Port(s) Found during Port Testing-SA 316154 CDR Review Utility Error 317155 CIP MDS File Error 317156 NWPL MDS Access Error 319157 NER MDS Access Error 321158 NER Memory Access Error 322160 Digital Networking System Error 323161 Digital Networking Operational Error 323162 Digital Networking Warning Message 323163 Digital Networking Informative Message 323164 Digital Networking Internal Error 323165 Digital Networking Connect Retries Exhausted 3271C0 OPI SP Error 3281C1 OPI LP Error 3291C2 OPI Arbitration Master Error 3291E0 Network Directory Error 3301E1 Network Directory Input/Output Error 3341E2 Number of Network Directory Entries Exceeds Critical Space Threshold 3341E3 Number of Network Directory Entries Exceeds Directory Full Alarm Threshold 3361E4 Network Directory Full 3361E5 Aspenet Admin Protocol Error 3371E6 EDBN Administrative Message Status 3381E7 EDBN Network Directory Access Error 3391E8 Debug Logs Snapshot 3411FC Local Lock Error 3421FF Protocol Out of Sequence 343200 Abnormal System Shutdown 344228 Background Task Error 345
STATUS LOG # 5331, REV. C 43
STATUS CODES00
Entry headerRegistersduring event
000000
00 Boot Reason and Time
* SST will dump and write to record 50.
Offset Label Field Description
10 Boot character Character the voice processing module was booted with, in ASCII:
30 Booted with 041 Booted with A42 Booted with B
11 Reason Why the system was down:00 Input power failure (brown out)01 Input power failure (long)02* Interrupt 3 (major system error)03* Memory parity error
04* System manager shutdown05 Red temperature NMI06 Watchdog timer NMI07 OPI ready error08 CP was reset, or, undetermined
error (power failure)20 DS is not Task State Segment.40 System crash routine entered—
SRAM considered to be OK.50 Unable to write SST.60 Unable to write Rec 50.
Task ID
CSIP00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 141516
ReasonBoot character
Unused
44 STATUS LOG
STATUS CODES 02
type g, a m.
call.
Entry header
IORB header
CB-out messageCB-in messageRegistersduring event
Entry header
IORB header
CB-out messageCB-in messageRegistersduring event
01 Failed SST Validity Check During Boot Process
The format of the system status table is bad.
02 Scanner Wrong Incoming Message
The scanner has probably received a message that is not valid from eitherthe RS-232 port or the remote access port.
Offset Label Field Description
50-56 Queued incoming scanner message
Check offsets 50 and 51 first for the message and port. Since the field is only seven bytes lonnine-byte message will be missing its checksu
57 *Scanner switches Value is the sum of the following:20 (Bit 5 set.) Bypass on-hook.40 (Bit 6 set.) Off-hook issued for incoming80 (Bit 7 set.) Incoming message queued.
00020 20212223 24252627 28292A2B 2C2D2E2F
Task ID
CS IPAX BX CX DX SI DI DS ES
Peripheraladdress
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
CB task ID
Control busmessage types
00020 20212223 24252627 28292A2B 2C2D2E2F
Task ID
CS IPAX BX CX DX
SI DI DS ES
Peripheraladdress
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050 50515253 545556
00060
CB task ID
Control busmessage types
*
Queued incomingscanner message
STATUS LOG 45
STATUS CODES03
ype g, a m.
call.
Entry header
Entry header
IORB header
CB-out messageCB-in messageRegistersduring event
03 Scanner No Carrier After Ring
Indicates that someone called the modem port and hung up without enter-ing the system. If this status code frequently occurs, try changing the tele-phone number assigned to the modem port. Also, ensure that the remote-access number is not part of the system’s hunt group.
04 RS-232 Integration Link Reset
Information only. Indicates that the link was reset in Menu 13.6.
Offset Label Field Description
50-56 Queued incoming scanner message
Check offsets 50 and 51 first for the message tand port. Since the field is only seven bytes lonnine-byte message will be missing its checksu
57 *Scanner switches Value is the sum of the following:20 (Bit 5 set.) Bypass on-hook.40 (Bit 6 set.) Off-hook issued for incoming80 (Bit 7 set.) Incoming message queued.
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00020 20212223 24252627 28292A2B 2C2D2E2F
Task ID
CS IPAX BX CX DX
SI DI DS ES
Peripheraladdress
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050 50515253 545556
00060
CB task ID
Control busmessage types
*
Queued incomingscanner message
46 STATUS LOG
STATUS CODES 08
Entry headerRegistersduring event
Entry header
IORB header
CB-out messageCB-in messageRegistersduring event
Entry headerRegistersduring event
05 Status Log Cleared
06 Error During Garbage Collect
This error is usually due to the number of drives running being less than thenumber of drives installed while attempting to run garbage collect.
07 SMT Internal Error
08 SMT Software Alarms Cleared
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 CS IP
00020 20212223 24252627 28292A2B 2C2D2E2F
Task ID
CSIP
AX BX CX DX SI DI DS ES
Peripheraladdress
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
CB task ID
Control busmessage types
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 CS IP
STATUS LOG 47
STATUS CODES09
Entry header
IORB header
CB-out messageCB-in messageRegistersduring event
09 Software Download Utility Error
0A SMT Invalid User Record Lock State
This error is usually logged when a system management task attempts forthirty minutes to access a user record that is locked. Possible bad line card.
0B SMT File System I/O Error
Two reasons why this error is logged are:
• The system manager has deleted a node and then calls the system man-ager mailbox to retrieve messages during the 4-hour period needed bythe system to delete the node. An external address record message isplayed.
• A bad CDR block is downloaded.
Possible bad file card.
00020 20212223 24252627 28292A2B 2C2D2E2F
Task ID
CSIP
AX BX CX DX SI DI DS ES
Peripheraladdress
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
CB task ID
Control busmessage types
48 STATUS LOG
STATUS CODES 0C
Entry headerRegistersduring event
0C SMT-Related OCL Error
10 Problem sending application status command to OCL.Offset 10-11: return code from X_SIGNAL_32.
14 OCL initialization error, ACACLLIB_INIT_16 failed.Offset 10-11: return code from ACACLLIB_INIT_16.
15 Bad response to OCL start line command.Offset 10-11: response type returned from OCL.
16 Bad response to OCL stop line command.Offset 10-11: response type returned from OCL.
17 Bad response to OCL line status query.Offset 10-11: response type returned from OCL.
18 Bad OCL signal—line status error.
19 Problem sending application status command to OCL.Offset 10-11: return code from X_SIGNAL_16.
1A Bad OCL signal—application add error.
1B Bad OCL signal—application delete error.
1C Bad OCL signal—application modify error.
1D Bad OCL signal—LUN status error.
1E Bad OCL signal—clear LUN error.
1F Bad OCL signal—EAP add error.
20 Bad OCL signal—EAP delete error.
21 Bad OCL signal—EAP modify error.
22 Bad OCL signal—line configuration error.
23 Bad X.25 LUN open error.
24 Bad X.25 LUN read error.
25 Bad X.25 LUN write error.
26 Bad X.25 LUN IOCTL error.
27 Bad X.25 LUN close error.
28 Bad X.25 LUN I/O abort error.
29 Bad return from priority queue.Offset 10-11: return code from ACOS_RCVPQ_16.
2A Wrong item number (line, application, LUN, etc.) returned by OCL. Offset 10-11: ID number returned from OCL.
2B Wrong response to OCL queue entry.Offset 10-11: response type returned from OCL.
2C SMT/OCL application states out of synch.Offset 10-11: file ID.
Task ID
CS00000 00010203 04050607 08090A0B 0C0D0E0F
00010 1011 EBP EIP
Data dependingon subcode
STATUS LOG 49
STATUS CODES0D
Entry header
Registersduring event
Entry headerRegistersduring event
Entry header
Registersduring event
0D SMT-Related File Management Error
01 X.25 configuration file does not exist.
02 Creation of X.25 configuration file failed.
03 Opening X.25 configuration file failed.
04 Closing X.25 configuration file failed.
05 Error reading X.25 configuration file.
06 Error writing X.25 configuration file.
09 Application number—file does not exist.
0A Application number—file creation failed.
0B Application number—file open failed.
Task ID
00020 2021
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1FFile name, in ASCII EBPCS
EIP
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1DEBP CSEIP
File ID pointer
Task ID
00020 2021
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1FFile name, in ASCII EBPCS
EIP
50 STATUS LOG
STATUS CODES 0D
Entry headerRegistersduring event
Entry headerRegistersduring event
0C Application number—file close failed.
0D Application number—file read error.
0E Application number—file write error.
23 Unable to allocate memory for the file record buffer.
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1DEBP CSEIP
File ID pointer
Task ID
CS
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 1011 EBP EIP
Address pointer,probably 0000
STATUS LOG 51
STATUS CODES0E
Entry header
Entry header
Registersduring event
(repeated)
0E SMT-Related X.25 Line Error
07 Problem sending the start X.25 physical interface command to OCL.
00010 10111213 14151617 1819
SECOND ENTRY
WHOLE “ENTRY” USES TWO STATUS LOG ENTRIES
FIRST ENTRY
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050 50515253 54555657 58595A5B 5C5D5E5F
00060 60616263 64656667 68696A6B 6C6D6E6F
00070 70717273 74757677 78797A7B 7C7D7E7F
00080 80818283 84858687 88898A8B 8C8D8E8F
00090 90919293 94959697 98999A9B 9C9D9E9F
000A0 A0A1A2A3 A4A5A6A7 A8A9AAAB ACADAEAF
000B0 B0B1B2B3 B4B5B6B7 B8B9BABB BCBDBEBF
000C0 C0C1C2C3 C4C5C6C7 C8C9CACB CCCDCECF
000D0 D0D1D2D3 D4D5D6D7 D8D9DADB DCDDDEDF
000E0 E0E1E2E3 E4E5E6E7 E8E9EAEB ECEDEEEF
000F0 F0F1F2F3 F4F5F6F7 F8F9FAFB FCFDFEFF
Physical interfaceinitialization record
00000 00010203 04050607 08090A0B 0C0D0E0F
EBP CSEIP
52 STATUS LOG
STATUS CODES 0E
S
Entry header
Registersduring event
Entry header(repeated)
Entry header(repeated)
0F Problem putting an entry on the OCL signal queue.
000B0 B0B1B2B3 B4B5B6B7 B8B9BABB BCBDBEBF
000C0 C0C1C2C3 C4C5C6C7 C8C9CACB CCCDCECF
000D0 D0D1D2D3 D4D5D6D7 D8D9DADB DCDDDEDF
000E0 E0E1E2E3 E4E5E6E7 E8E9EAEB ECEDEEEF
000F0 F0F1F2F3 F4F5F6F7 F8F9FAFB FCFDFEFF
SECOND ENTRY
WHOLE “ENTRY” USES THREE STATUS LOG ENTRIE
FIRST ENTRY
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050 50515253 54555657 58595A5B 5C5D5E5F
00060 60616263 64656667 68696A6B 6C6D6E6F
00070 70717273 74757677 78797A7B 7C7D7E7F
00080 80818283 84858687 88898A8B 8C8D8E8F
00090 90919293 94959697 98999A9B 9C9D9E9F
000A0 A0A1A2A3 A4A5A6A7 A8A9AAAB ACADAEAF
000B0 B0B1B2B3 B4B5B6B7 B8B9BABB BCBDBEBF
000C0 C0C1C2C3 C4C5C6C7 C8C9CACB CCCDCECF
000D0 D0D1D2D3 D4D5D6D7 D8D9DADB DCDDDEDF
000E0 E0E1E2E3 E4E5E6E7 E8E9EAEB ECEDEEEF
000F0 F0F1F2F3 F4F5F6F7 F8F9FAFB FCFDFEFF
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
. . .
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050 50515253 54555657 58595A5B 5C5D5E5F
00060 60616263 64656667 68696A6B 6C6D6E6F
00070 70717273 74757677 7879EBP CSEIP
Application initializationblock 3
THIRD ENTRY
Application initializationblock 1
Application initializationblock 2
STATUS LOG 53
STATUS CODES0F
Entry headerRegistersduring event
Entry header
Registersduring event
Fileparameters
23 X.25 open failure (normally LMS LUN).
24 X.25 read failure (normally associated with LMS).
25 X.25 write failure (normally associated with LMS).
26 X.25 IOCTL failure (normally associated with LMS).
27 X.25 close failure (normally associated with LMS).
29 Priority queue receive error (normally associated with LMS, but this can also mean an unexpected receive type).
0F File Creation Informational Entry
00 System created X.25 configuration file. This entry should be seen only if this is a first-time installation. If this code is seen at any other time, the file had to be recreated and any previous X.25 configuration information was lost.
02 Creation of X.25 configuration file failed.
08 System created application configuration file. This entry should be seen only if this is a first-time installation or right after the system has been initialized. If this code is seen at any other time, the file had to be recreated and any previous application configuration information was lost.
0A Creation of application configuration file failed.
Task ID
CS00000 00010203 04050607 08090A0B 0C0D0E0F
00010 1011 EBP EIP
Result of call
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B
File name, in ASCII
CSEBP EIP CS
1 2 3 4 5 6 7 8
9
1File type2Locking definitions3Access definitions4Creator5Super record size
6Record size7Super field size8Field size9Record count
54 STATUS LOG
STATUS CODES 11
Entry header
Registersduring event
Entry headerRegistersduring event
10 SMT-Related AMIS Internal Error
01 Bad AMIS EAR number.
02 AMIS EAR Array is full.
03 AMIS EAR Entry is full.
04 Failed to delete AMIS EAR number.
06 Garbage Collect failed to remove unused AMIS EAR numbers.
11 Error During Upgrade Performed by SMT
01 Error reading user record or invalid user record. Not upgraded.
02 Allowed length exceeded during upgrade. Group lists or messages omitted.
03 Error during follow-me-forward upgrade.
04 Error during personal group list upgrade.
05 Error during message descriptor upgrade.
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 20212223 24252627 28292A2B 2C2D2E2F
EAX EBX ECX EDIEDX ESI ESP DS ES
00040 20212223 24252627 28292A2B 2C2D2E2FFS GS SS * EBP EIP00050 20CS
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1DEBP CSEIP
Internal record number(IRN) in error
Offset, in user record,in error
STATUS LOG 55
STATUS CODES11
Entry headerRegistersduring event
Entry headerRegistersduring event
Entry headerRegistersduring event
Entry headerRegistersduring event
11 Error reading, writing or adding the system distribution list. The list was not converted.
12 Error found in a member of the system distribution list. The member was not converted.
13 Error reading, writing or adding a company record. The record was not converted.
14 Error reading, writing or adding an attendant record. The record was not converted.
Task ID
CS00000 00010203 04050607 08090A0B 0C0D0E0F
00010 1011 EBP EIP
System grouplist number
Task ID
CS00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 1415 EBP EIP
System grouplist number
Number of membersin the group list
IUN of bad member,as found in the group list
Task ID
CS00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 1415 EIP
Company #Unused
EBP
Task ID
CS00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 1415 EIP
UnusedAttendant schedule #
EBP
56 STATUS LOG
STATUS CODES 13
Entry header
IORB header
CB-out messageCB-in messageRegistersduring event
Entry header
IORB header
CB-out messageCB-in messageRegistersduring event
12 SMT Could Not Get a New User Record
All of the user records initially configured in the system are in use. If the sys-tem attempts to create a new mailbox, company record, attendant record,etc., “system full or capacity reached” is displayed on the system manager’sscreen.
To correct this problem: get a bigger system, increase the system capacityor delete unused mailboxes.
13 SMT Could Not Find the ICN in the AMT
The ICN used to look up the AMT is not valid. The expected AMT entrymight either be corrupted or it never existed. If a bad company record islogged, the corresponding AMT entry was never created. If the bad com-pany record is known, it can be fixed and the AMT can be rebuilt by reboot-ing the system. Otherwise, find which company record the ICN isassociated with, and determine if the AMT entry is corrupted or if the ICN issimply invalid.
00020 20212223 24252627 28292A2B 2C2D2E2F
Task ID
CS IPAX BX CX DX SI DI DS ES
Peripheraladdress
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
CB task ID
Control busmessage types
00020 20212223 24252627 28292A2B 2C2D2E2F
Task ID
CS IPAX BX CX DX SI DI DS ES
Peripheraladdress
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
CB task ID
Control busmessage types
STATUS LOG 57
STATUS CODES14
Entry header
ordsive
Registersduring event
Entry header
IORB header
CB-out messageCB-in messageRegistersduring event
14 IRN Usage Report
This entry is logged on completion of Reformat Option 0, User RecordValidity Check.
15 MDS File Creation Problem
16 LAN Initialization Failed
17 IP Address Netmask Not Sent
18 Error Sending Configuration Update to LAN Card
Task ID
00020 20212223 24252627 28292A2B 2C2D
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1FCommunityrecords
# Recordsavailable
Percentfree
# Attendantrecords
# Mailboxrecords
# MDSrecords
# Damagedrecords
# Networknodes
# Recordsassigned
# Recact
CSEIPEBP
00020 20212223 24252627 28292A2B 2C2D2E2F
Task ID
CSIP
AX BX CX DX SI DI DS ES
Peripheraladdress
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
CB task ID
Control busmessage types
58 STATUS LOG
STATUS CODES 1A
Entry headerRegistersduring event
Entry header
Registersduring event
19 Scanner Task Internal Error
This error could be logged because of an inconsistency in the systemtables, or an invalid response from the scanner to the CPU.
01 Bad user record.
02 No priority queue assigned to message-waiting link number.
03 Bad link number in user record (with ACP integration only).
04 Could not lock user record.
05 Could not refresh user record.
06 CDR buffer not available.
1A Scanner Task Protocol Error
This error could be logged because of an inconsistency in the systemtables, or an invalid response from the scanner to the CPU.
01 Could not attach scanner. AX, in offset 20-21, contains the return code from the attachment routine.
02 Invalid channel referenced by scanner. The channel number is in the scanner input message.
03 Invalid scanner message.
04 Invalid type sent from scanner in line status message. The type is in the scanner input message.
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 1415
Internal user number (IUN)for subcodes 01-05
IP CSAX
00020
Task ID
AX IP CS
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1FUnused
Header of scanner inputmessage
STATUS LOG 59
STATUS CODES1B
Entry header
IORB header
CB-out messageCB-in message
Registersduring event
Entry header
IORB header
CB-out messageCB-in messageRegistersduring event
05 Bad return code from system partition (file read/write).
06 Bad return code in control bus message from file card (file read/write).
1B Scanner Task Message Waiting Error
A switch or PID device sent a block message to the Scanner Task. Thismeans that the message-waiting operation could not be performed andshould be tried again.
01 Message waiting time-out. The scanner did not respond in time.
02 Queue overflow during message waiting. Two messages were received that were not the correct response from the scanner.
00020 20212223 24252627 28292A2B 2C2D2E2F
Task ID
CS IPAX BX CX DX SI DI DS ES
Peripheraladdress
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
CB task ID
Control busmessage types
00020 20212223 24252627 28292A2B 2C2D2E2F
Task ID
CS IPAX BX CX DX
SI DI DS ES
Peripheraladdress
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050 50515253 545556
00060
CB task ID
Control busmessage types
*
Queued incomingscanner message
60 STATUS LOG
STATUS CODES 1B
ype g, a m.
call.
Entry headerCB-in messageRegistersduring event
Entry header
IORB header
CB-out message
CB-in messageRegistersduring event
03 Message waiting busy. The extension number in the block message did not match an extension in the AMT. This can happen when the message-waiting extension is different than the mailbox extension.
05 Unexpected negative acknowledgment from scanner. This is usually seen while installing a new DMID integration or changing the PBX type specification to DMID from something else.
Offset Label Field Description
50-56 Queued incoming scanner message
Check offsets 50 and 51 first for the message tand port. Since the field is only seven bytes lonnine-byte message will be missing its checksu
57 *Scanner switches Value is the sum of the following:20 (Bit 5 set.) Bypass on-hook.40 (Bit 6 set.) Off-hook issued for incoming80 (Bit 7 set.) Incoming message queued.
Task ID
00020 20212223 2425
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
AX IP CSCB task ID
Message-waiting extension
Control busmessage type =ACP message 86
00020 20212223 24252627 28292A2B 2C2D2E2F
Task ID
CS IPAX BX CX DX
SI DI DS ES
Peripheraladdress
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050 50515253 545556
00060
CB task ID
Control busmessage types
*
Queued incomingscanner message
STATUS LOG 61
STATUS CODES1C
ype g, a m.
call.
ype g, a m.
call.
Entry header
IORB header
CB-out message
CB-in messageRegistersduring event
1C Message Waiting, Illegal Extension
This error would be logged during problems with 1AESS, 5AESS, DMS100and SL100 SMDI integrations using RS-232. To resolve this error, perhapscheck the mailbox profile to assure that the extension field is correct andthat the number is seven digits long. If the profile is correct, try having theextension validity checked in the CO database and the COS for messagewaiting ability.
01 Bad extension.
02 Extension does not have message waiting.
Offset Label Field Description
50-56 Queued incoming scanner message
Check offsets 50 and 51 first for the message tand port. Since the field is only seven bytes lonnine-byte message will be missing its checksu
57 *Scanner switches Value is the sum of the following:20 (Bit 5 set.) Bypass on-hook.40 (Bit 6 set.) Off-hook issued for incoming80 (Bit 7 set.) Incoming message queued.
Offset Label Field Description
50-56 Queued incoming scanner message
Check offsets 50 and 51 first for the message tand port. Since the field is only seven bytes lonnine-byte message will be missing its checksu
57 *Scanner switches Value is the sum of the following:20 (Bit 5 set.) Bypass on-hook.40 (Bit 6 set.) Off-hook issued for incoming80 (Bit 7 set.) Incoming message queued.
00020 20212223 24252627 28292A2B 2C2D2E2F
Task ID
CS IPAX BX CX DX
SI DI DS ES
Peripheraladdress
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050 50515253 545556
00060
CB task ID
Control busmessage types
*
Queued incomingscanner message
62 STATUS LOG
STATUS CODES 1D
pe
Centrex
er of bad (false) LTNs ed.
d
d
er of integration link received.
er of incomplete mes- received.
Entry header
Registers during event
1D Error Counters Reported by Scanner
Offset
Peg Counter Description—depends on integration ty
NEC, PID/R, APID75, APID85, DMID
IVMS, MID
12 Number of bad (false) LTNs received.
Number of bad (false) LTNs received.
Numbreceiv
13 Number of incomplete mes-sages received.
Number of incomplete mes-sages received or time-outs while waiting for an acknowl-edgment.
Unuse
14 Number of times the wrong number of characters was in a message before the end-of-text character was found.
Number of messages received out of sequence.
Unuse
15 Number of integration link errors received.
Number of integration link errors received.
Numberrors
16 Number of times an integra-tion message had an illegal character.
Number of messages of the wrong length received.
Numbsages
00020
Task ID
AX IP CS
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
Scanner
5 peg counters,
Unused
inputmessage
1 byte each
header
STATUS LOG 63
STATUS CODES1E
Entry header
Registers during event
1E Error Information from PID
Note that the subcode is in offset 12. Offset 08-09 is unused.
Also, the subcode meaning depends on the PID type. Below are the sub-codes for DMID integrations. For MID subcodes, see “MID Integration” onpage 71.
DMID Integration
The DMID data field in offset 13-16 varies with the subcode in offset 12.
00 DMID firmware revision number. Logged when the DMID is powered up, even if error logging is disabled. DMID data is:
Offset 13-14: firmware revision number.Offset 15-16: unused.
01 RS232 serial interface error. Service affecting, fatal. Notify Product Support Engineering. DMID data is:
Offset 13: number of no RS-232 buffer errors.Offset 14: number of bad RS-232 message length errors.Offset 15: number of RS-232 message time (100 ms) expired errors.Offset 16: number of bad RS-232 header errors.
02 Interrupt 0 or 1 error. Service affecting, fatal. Notify Product Support Engineering. DMID data is:
Offset 13: number of interrupt 0 errors.Offset 14: number of interrupt 1 errors.Offset 15: number of watchdog interrupt errors.Offset 16: unused.
03 MPDA-A serial interface error. Service affecting, fatal. Notify Product Support Engineering. DMID data is:
Offset 13: number of MPDA I/F parity errors.Offset 14: number of MPDA I/F overflow errors.Offset 15: number of MPDA I/F bad header errors.Offset 16: number of MPDA I/F message time (100 ms) expired errors
00020
Task ID
AX IP CS
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1FUnused
Scannerinputmessage
DMID data,depends on subcodein offset 12
header
64 STATUS LOG
STATUS CODES 1E
Entry header
Registers during event
04 MPDA-B serial interface error. Service affecting, fatal. Notify Product Support Engineering. DMID data is:
Offset 13: number of MPDA I/F parity errors.Offset 14: number of MPDA I/F overflow errors.Offset 15: number of MPDA I/F bad header errors.Offset 16: number of MPDA I/F message time (100ms) expired errors.
05 MPDA-C serial interface error. Service affecting, fatal. Notify Product Support Engineering. DMID data is:
Offset 13: number of MPDA I/F parity errors.Offset 14: number of MPDA I/F overflow errors.Offset 15: number of MPDA I/F bad header errors.Offset 16: number of MPDA I/F message time (100ms) expired errors.
06 DMID received unknown transparency message. It reset the phone and re-established transparency. When the PBX initialized, it sent this message. Service affecting, fatal. DMID data is:
Offset 13-14: received message.Offset 15-16: unused.
07 DMID received unknown transparency message. It reset the phone and re-established transparency. When the PBX initialized, it sent this message. Service affecting, fatal. DMID data is:
Offset 13-14: received message.Offset 15-16: unused.
15 Pilot number download time-out. DMID data is unused.
16 MPDA-A/B/C power up warning. Not service affecting. DMID data is:
Offset 13: MPDA A, B or C.Offset 14: A/B/C state.Offset 15: A/B/C timer.Offset 16: data.
17 MPDA-A/B/C power up warning. Not service affecting. DMID data is:
Offset 13: MPDA A, B or C.Offset 14-16: data.
18 MPDA-A/B/C power up warning. Not service affecting. DMID data is:
Offset 13: MPDA A, B or C.Offset 14: A/B/C state.Offset 15: A/B/C timer.Offset 16: data.
00020
Task ID
AX IP CS
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1FUnused
Scannerinputmessage
DMID data,depends on subcodein offset 12
header
STATUS LOG 65
STATUS CODES1E
Entry header
Registers during event
19 MPDA-A/B/C power-up warning. Not service affecting. DMID data is:
Offset 13: MPDA A, B or C.Offset 14: A/B/C state.Offset 15: A/B/C timer.Offset 16: data.
1A MPDA-A/B/C power-up warning. Not service affecting. DMID data is:
Offset 13: MPDA A, B or C.Offset 14: A/B/C state.Offset 15: A/B/C timer.Offset 16: data.
20 DMID received LED wink message and did not know what to do with it. Not service affecting. Notify Product Support Engineering. DMID data is:
Offset 13: LTN number.Offset 14: LTN state.Offset 15: LTN timer.Offset 16: unused.
22 DMID received LED flash message when the channel was in the wrong state. Not service affecting. The PBX can send multiple lamp flash messages. If too many errors are logged, notify Product Support Engineering. DMID data is:
Offset 13: LTN number.Offset 14: LTN state.Offset 15: LTN timer.Offset 16: unused.
27 DMID received a digit but the channel was in the wrong state. Not ser-vice affecting. If too many errors are logged, notify Product Support Engineering. DMID data is:
Offset 13: LTN number.Offset 14: LTN state.Offset 15: LTN timer.Offset 16: unused.
00020
Task ID
AX IP CS
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1FUnused
Scannerinputmessage
DMID data,depends on subcodein offset 12
header
66 STATUS LOG
STATUS CODES 1E
Entry header
Registers during event
29 DMID received an ASCII message but the channel was in the wrong state. Not service affecting. If too many errors are logged, notify Prod-uct Support Engineering. DMID data is:
Offset 13: LTN number.Offset 14: LTN state.Offset 15: LTN timer.Offset 16: unused.
2C Bad LTN message from scanner. Service affecting, non-fatal. If too many errors are logged, notify Product Support Engineering. DMID data is:
Offset 13: message type from scanner.Offset 14-15: LTN number.Offset 16: unused.
2D Got off-hook response message from scanner when the channel was in the wrong state. Service affecting. Notify Product Support Engi-neering. DMID data is:
Offset 13: LTN number.Offset 14: LTN state.Offset 15: LTN timer.Offset 16: unused.
2E Off-hook response from scanner expired. The caller might get an open tree greeting or get dropped. Service affecting, non-fatal. DMID data is:
Offset 13: LTN number.Offset 14: LTN state.Offset 15: LTN timer.Offset 16: A/B counter.
30 Bad RS-232 message from scanner. Service affecting, non-fatal. If too many errors are logged, notify Product Support Engineering. DMID data is:
Offset 13: message type from scanner.Offset 14-15: LTN number.Offset 16: unused.
00020
Task ID
AX IP CS
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1FUnused
Scannerinputmessage
DMID data,depends on subcodein offset 12
header
STATUS LOG 67
STATUS CODES1E
Entry header
Registers during event
31 Off-hook or Call ID message pending expired. The caller gets an open tree greeting. Service affecting, non-fatal. If too many errors are logged, notify Product Support Engineering. DMID data is:
Offset 13: LTN number.Offset 14: LTN state.Offset 15: LTN timer.Offset 16: unused.
32 Timed-out after 18 seconds in answer pending state. The caller gets an open tree greeting. Service affecting, non-fatal. If too many errors are logged, notify Product Support Engineering. DMID data is:
Offset 13: LTN number.Offset 14: LTN state.Offset 15: LTN timer.Offset 16: A/B state.
35 MPDA-A/B/C response time-out for idle poll message. Transparency is re-established. Service affecting, fatal. Check DMID channels A, B and C connections, and check internal cables. Notify Product Support Engineering. DMID data is:
Offset 13: A, B or C.Offset 14: A/B/C state.Offset 15: A/B/C timer.Offset 16: unused.
36 Timed-out after five seconds in phone session state. Not service affecting. If too many errors are logged, notify Product Support Engi-neering. DMID data is:
Offset 13: A or B.Offset 14: A/B state.Offset 15: A/B timer.Offset 16: processing LTN.
37 DSP enable time expired. Not service affecting. If too many errors are logged, notify Product Support Engineering. DMID data is:
Offset 13: A or B.Offset 14: A/B state.Offset 15: A/B timer.Offset 16: processing LTN.
00020
Task ID
AX IP CS
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1FUnused
Scannerinputmessage
DMID data,depends on subcodein offset 12
header
68 STATUS LOG
STATUS CODES 1E
Entry header
Registers during event
38 DSP enable time expired. Not service affecting. If too many errors are logged, notify Product Support Engineering. DMID data is:
Offset 13: A or B.Offset 14: A/B state.Offset 15: A/B timer.Offset 16: processing LTN.
39 Scanner sent non-digit extension for message waiting. Message wait-ing will have problems. Service affecting, can be fatal. If too many errors are logged, notify Product Support Engineering. DMID data is:
Offset 13: LTN number.Offset 14: LTN state.Offset 15: LTN timer.Offset 16: received digit.
3A DMID received MIK LED on message when not in this state. Not ser-vice affecting. If too many errors are logged, notify Product Support Engineering. DMID data is:
Offset 13-16: received message.
3B DMID received MIK LED on message when not in this state. Not ser-vice affecting. If too many errors are logged, notify Product Support Engineering. DMID data is:
Offset 13-16: received message.
3C MIK/MCK release expired. Transparency mode will be re-established. Message waiting will not work until transparency is re-established. Service affecting, non-fatal. If too many errors are logged, notify Prod-uct Support Engineering. DMID data is:
Offset 13: C.Offset 14: C state.Offset 15: C timer.Offset 16: C counter.
3D Received type 1 off-hook message from PBX. The system may log this if the phone is being programmed in overlay 11 or if the hook switch is toggled. Not service affecting. DMID data is:
Offset 13-14: received message.Offset 15: A,B or C.Offset 16: unused.
00020
Task ID
AX IP CS
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1FUnused
Scannerinputmessage
DMID data,depends on subcodein offset 12
header
STATUS LOG 69
STATUS CODES1E
Entry header
Registers during event
3E Received type 2 off-hook message from PBX. The system may log this if the phone is being programmed in overlay 11 or if the hook switch is toggled. Not service affecting. DMID data is:
Offset 13-14: received message.Offset 15: A,B or C.Offset 16: unused.
3F Received type 3 off-hook message from PBX. The system may log this if the phone is being programmed in overlay 11 or if the hook switch is toggled. Not service affecting. DMID data is:
Offset 13-14: received message.Offset 15: A,B or C.Offset 16: unused.
40 Received type 1 on-hook message from PBX. The system may log this if the phone is being programmed in overlay 11 or if the hook switch is toggled. Not service affecting. DMID data is:
Offset 13-14: received message.Offset 15: A,B or C.Offset 16: unused.
41 Received type 2 on-hook message from PBX. The system may log this if the phone is being programmed in overlay 11 or if the hook switch is toggled. Not service affecting. DMID data is:
Offset 13-14: received message.Offset 15: A,B or C.Offset 16: unused.
42 Received unknown message from MPDA. Emulates Meridian Tele-center Software and re-establishes transparency mode. Service affecting and fatal. Notify Product Support Engineering. Unknown MPDA interface messages will not cause this error. DMID data is:
Offset 13-14: received message.Offset 15: A,B or C.Offset 16: unused.
43 Received MSB LED-on message. DMID data is unused.
00020
Task ID
AX IP CS
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1FUnused
Scannerinputmessage
DMID data,depends on subcodein offset 12
header
70 STATUS LOG
STATUS CODES 1E
Entry header
Registers during event
MID Integration
00 Display revision numbers of 651/751 EPROMs.
03 751 internal RAM error. Replace the 751.
04 751 overwrote its incoming message buffers. Service affecting, but not fatal. Notify engineering.
05 751 detected a checksum error while communicating with the 652. Not fatal, unless occurring repeatedly.
06 751 detected an interrupt on the IIC bus. Service affecting, but not fatal. If there are more than a few occurrences, replace the MID (all six channels associated with the particular bus will be bad).
07 751 detected a line input overrun. Service affecting, but not fatal. Notify engineering.
08 751 detected an unrecognized command. Notify engineering.
30 652 detected an incorrect message from a 751. Service affecting, but not fatal.
31 652 detected an unmatched message from a 751. Service affecting, but not fatal.
32 652 detected a checksum error on the IIC bus from a 751. Service affecting, but not fatal.
33 652 detected no response from a 751. Service affecting, but not fatal.
40 652 internal RAM error. Replace the 652.
41 652 external RAM error. Replace the 652.
42 652 detected that the 188 sent wrong message. Service affecting, but not fatal.
43 652 detected that the 188 sent a bad checksum. Service affecting, but not fatal.
44 652 detected that the 188 sent a bad serial number. Service affecting, but not fatal.
45 652 detected that the 188 sent an unmatched message. Service affecting, but not fatal.
46 652 detected that the 188 sent an unmatched general message. Ser-vice affecting, but not fatal.
47 652 detected that the 188 sent a message that was too long.
49 652 detected that the 188 message was not processed.
50 652 detected no digits in buffer during an incall. Service affecting, but not fatal.
00020
Task ID
AX IP CS
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1FUnused
Scannerinputmessageheader
STATUS LOG 71
STATUS CODES1E
Entry header
Registers during event
51 652 detected too few digits in buffer during an incall. Service affect-ing, but not fatal.
52 652 detected more than 16 digits in buffer during an incall. Service affecting, but not fatal.
53 652 detected a condition where the state is longer than 60 seconds. Service affecting, but not fatal.
54 652 big transmit buffer overrun error. Service affecting, but not fatal.
55 Bad or blocked extension for transfer. Service affecting, but not fatal.
56 No message waiting indication DN found. Service affecting, but not fatal.
57 No message waiting clear DN found. Service affecting, but not fatal.
58 No digit echo during message waiting indication. Service affecting, but not fatal.
59 No digit echo during message waiting clear. Service affecting, but not fatal.
5A Bad or blocked extension for message waiting indication. Service affecting, but not fatal.
5B Bad or blocked extension for message waiting clear. Service affect-ing, but not fatal.
5C Outcall failed. Service affecting, but not fatal.
5D During transfer, no digits found.
5E During transfer, no message from SL-1 for approximately 12 seconds.
5F During incall, no volume message from SL-1 for approximately 12 seconds.
60 No digit information received from PBX on incoming call. Check if ADD feature in SL-1 programming is enabled for that particular TN.
61 No dial digit message from VPM.
80 Display revision numbers of the 188 EPROM.
81 652 processor bad. Fatal error. Replace the MID.
00020
Task ID
AX IP CS
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1FUnused
Scannerinputmessageheader
72 STATUS LOG
STATUS CODES 1F
Entry headerRegistersduring event
1F RS-232 Link Down
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 1415IP CSAX
STATUS LOG 73
STATUS CODES20
Registersduring event
Entry header
Entry headerIT messageRegistersduring event
000000
20 SMDI Internal Error
00 Integration port transmit fault error.
01 System call wait on multiple events error. The system restarted.
03 Invalid message waiting message error.
Offset Label Field Description
10-25 IT message Integration Task mes-sage
12 1Message type
13 2Digits
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
Task ID
00020
00000 00010203 04050607 08090A0B 0C0D0E0F
00010
00030
00040
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0*Unused
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
EBP EIP CSCallee ID
Caller IDMD LTN
Message error
Call typePort
1 2
74 STATUS LOG
STATUS CODES 21
Entry headerRegistersduring event
Entry header
06 System call event create error.Offset 10-13: Integration Task initial event ID.
07 System call queue create error.Offset 10-13: priority queue ID.
21 SMDI Protocol Error
00 Integration link 0.
0F Integration link 15.
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1DEBP EIP CS
Event or queue ID, depending on subcode
…
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1FUnused
Fault LTNcorrelationcount number
Ring on port,no integrationmessage
Incomplete message Parity error count
Overrun error
Framing error
STATUS LOG 75
STATUS CODES22
e IDs (offset 10-11),”
pplemental Error
field. See Table 2-3,
Entry header
Registersduring event(in last 10 bytesof entry)
Data type & value(number of pairsvaries with thesituation)
,ubcode
22 Internal Error in the X-Interface Code
The entry formats for status code 22 are unusual in a couple of ways. First,they (with two exceptions) are variable length. Second, they (with oneexception) use data type and value pairs: the data-type field holds a codeidentifying the kind of data in the following data-value field.
The following fields are used in all but one of the subcodes:
20 X-interface routine attempted to send an incorrect IOCTL command to D-queue. Offset 18-1B holds the IOCTL code that is in error.
21 X.25 SP code detected an invalid subcode for reporting an EAP-related error (status code 24). Offset 18-1B holds the subcode that is in error. This entry is always followed by an entry for subcode 22 (see below).
Offset Label Field Description
10-11 Routine ID Routine that logged the event. See Table 2-1, “Routinon page 80.
12 Supplementalstatus code
Extra information about the event. See Table 2-2, “SuCodes (Offset 12),” on page 82.
13 Unused
Varies Data type Identifies the kind of data in the following data-value “Data Types,” on page 82.
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1FData type Data typeData value
Routine ID 21
Data type Data value Data type
Data value Data type Data value Data typeData value EBP EIP CS
… … … … …
1Supplemental status code2Unused
Code in errordepends on s
76 STATUS LOG
STATUS CODES 22
Entry header
Registersduring event(in last 10 bytesof entry)
Data type & valuepairs
Entry header
Registersduring event
Data type & valuepairs
22 Extension of subcode 21. The body of the entry is what would have been logged in status code 24 (EAP-related error) if the subcode had been legal.
23 Unable to create a GDT alias to either the D-queue or Z-queue during initialization. Reported by SP router code.
Offset Label Field Description
12 1Supplemental status code 22 Alias of the D-queue failed.23 Alias of the Z-queue failed.
13 2Unused
00010 10111213 14151617 18191A1B 1C1D1E1F
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
Type = 4D Type = 4ERoutine ID
21
Type = 4F Length Type = 50
EBP EIP CS
…
Error valueEAP applicationnumber (>0)
Packet data that caused the error(length varies and is in offset 28-2B)
00030
1Supplemental status code2Unused
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1FData type Data typeRoutine ID
21
EBP EIPCS
Task ID ofthe X.25 task
00030FAR pointer thatfailed the alias
STATUS LOG 77
STATUS CODES22
iled.
Entry header
Registersduring event(in last 10 bytesof entry)
Data type & value(number of pairsvaries with thesituation)
Entry headerRegistersduring event
30 D-queue overflow. The data value field in offset 18-1B holds the lost command code.
34 X-interface reported it could not create one of the semaphore locks needed to control access to critical data structures and code.
37 X.25 subsystem is being suspended. The preceding status log entry should help determine the cause of this entry.
Offset Label Field Description
12 1Supplemental status code Used only in subcode 34:20 Creation of LOG lock failed.21 Creation of critical section lock fa
13 2Unused
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1FData type Data typeData value
Routine ID21
Data type Data value Data type
Data value Data type Data value Data typeData value EBP EIP CS
… … … … …
Data value
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 1819EBP CSEIP
78 STATUS LOG
STATUS CODES 22
Entry header
Registersduring event(in last 10 bytesof entry)
Data type & value(number of pairsvaries with thesituation)
ubcode
Entry header
Registersduring event
Data type & value
riorityer
(number of pairs
(in last 10 bytesof entry)
varies with thesituation)
6B Invalid flag type was used in TEST_AND_SET call. The data value field in offset 18-1B holds the flag type value.
72 Router in SP was not able to allocate memory for an internal table. If the supplemental status code in offset 12 is 0C, the table was the router’s X.25 LUN table. The data value field in offset 18-1B holds the number of bytes that were requested.
73 Router in SP had a problem creating the OCL signal queue. The data value field in offset 18-1B holds the return code from CREATPQ call; the field in offset 20-23 holds the number of entries requested for the priority queue.
74 Failed to place an entry in a priority queue.
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1FData type Data typeData value
Routine ID 21
Data type Data value Data type
Data value Data type Data value Data typeData value EBP EIP CS
… … … … …
Data value,depends on s
1Supplemental status code2Unused
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
Task ID
Data type Data typeRoutine ID
21
3 Data value
Destination pqueue identifi
FAR pointer toqueue entry
Data type Data typeData value Data value
Data type Data typeData value Data valueEBP EIP CS
1Supplemental status code2Unused3Result returned from SENPQ call
… … … … …
STATUS LOG 79
STATUS CODES22
utinee Routines
Routines
Routines
e Routines
Table 2-1. Routine IDs (offset 10-11)
ID Routine ID Ro00 A routine with no ID Router Cod
OCL Task Routines 64 Xint zclosed01 Process action list (aclmain.c) 65 Xint zread02 OCL main 66 Xint zreadd03 Do init 67 Xint zwrite04 Get OCL sig queue ID 68 Xint zwrited05 Do server open 69 Xint zioctlrw06 Do signal 6A Xint zioctld07 Do IO response 6B Xint zsignal08 Send queue entry 6
CRun router
09 Phase 1 startup 6D
Do ZQ ent
0A Do clear X.25 mem (aclclram.c ) 6E Xint zopend10 Init App Table (aclapptb.c ) 6F Xint put DQ ent11 Add app 70 Xint call12 App signon LUN X Interface13 App signoff LUN 71 Xopen14 App ready LUN 72 Xclose15 App end ready LUN 73 X IOCTL16 App req LUN 74 XIOabort17 App can req LUN 75 Xread20 Init act list (aclactls.c ) 76 Xwrite21 Add action entry 77 Xsignal22 Del cur act entry 78 X log
Miscellanious 79 Xfootprint23 Line act comp 80 Xget LUN30 LS 0 DLD init (acllines.c ) 81 XRETLUN31 LS 22 DLD line 82 Xrwstat32 LS 23 start line 83 Xset STATE33 LS 24 wait L1 start 84 Xclear34 LS 25 L2 start OCL Utilitiy35 LS 26 wait L2 up 87 Test and set36 LS 27 line up OCL Interfac37 LS 28 ref new calls 90 OCL init38 LS 29 wait for LUNs to clear 91 OCL open39 LS 30 L2 down 92 OCL close3A LS 31 stop L1 93 OCL read40 LS 32 clram 94 OCL write41 LS bring L2 down 95 OCL set state42 Start line 96 OCL get state43 Stop line 97 OCL footprint44 Handle line state signal 98 OCL errlog
80 STATUS LOG
STATUS CODES 22
meanings, see next
aniousx25init_16 routine )t_lun_table routine ) routine )ignal routine )
ess
utinesuery)ery routine)
ear routine)ear routine)omp routine)mp routine)e routine)
aniousall state state
d)
utine
45 Init line table 99 OCL open OC (twoitem below)46 Line LUN open Miscell47 Line LUN close 99 X X.25 init (sys_x_48 LUN line stop 9A Get LUN table (ge49 LUN act comp 9B (lun_line_shutdown4A LUN ck ready LUN 9
C(handle_sigband_s
50 Pkey decrypt (aclpcryp.c ) 9D
Set translated addr
51 Pkey encrypt Stats Ro52 LUNs 0 init LUN (aclluns.c ) A0 (stats_line_stats_q53 LUNs 1 open LUN A1 (stats_drv_stats_qu54 LUNs 2 XIOmode LUN A2 (stats_drv_stats_cl55 LUNs 3 XIOopn LUN A3 (stats_line_stats_cl56 LUNs 4 rd incall A4 (stats_query_act_c57 LUNs 5 call acc LUN A5 (stats_clear_act_co58 LUNs 6 rd signon LUN A6 (stats_get_clear_tim59 LUNs 7 wr signon resp Miscell5A LUNs 8 rd ready rec A7 LUNs 12 ready outc5B LUNs 9 ready state5C
LUNs 10 in use
5D
LUNs 254 clear LUN
5E LUNs shutdown LUN5F LUN handle call req signal60 LUN app stop61 Parms parm buf62 Build parm buf63 Interp num
Table 2-1. Routine IDs (offset 10-11) (Continue
ID Routine ID Ro
STATUS LOG 81
STATUS CODES22
Value
buffer length buffer pointer
return
Table 2-2. Supplemental Error Codes (Offset 12)
Code Meaning Code Meaning01 App queue 10 Unknow serial number02 OCL queue 11 No serial number03 Dummy queue 12 Rec to short04 App table 13 Bad header command05 LUN table 14 Bad header06 Line table 15 Bad command parameter07 Act table 16 Bad signon08 LCL app table 17 Bad ready command09 LCL line table 18 Unknow version number0A Add app 20 Log lock related0B Add line 21 Crit. sect. lock related0C XLUN table 22 DQ address related
23 ZQ address related24 User addr related
Table 2-3. Data Types
Type
Following Data ValueTyp
eFollowing Data
00 Undefined field 30 RW length SD01 Number entry 31 Wait time02 Return value 32 Minor error code03 Task ID 33 Release code04 Local User Number (LUN) 34 Reason code05 LUN flag 35 Serial number06 LUN OCL state 36 Header command07 LUN app state 37 Header cer08 Line state 38 Header buffer length09 LUN state 39 Command parameter0A LUN d-type 3A Command parameter0B LUN d-item 3B Build parameter return0C Line d-type 3C Chk signon return0D Line d-item 3D Chk ready command 0E LUN SD 3E Buffer pointer0F LUN flag SD 3F Buffer length10 LUN OCL state SD 40 Line stop opt
82 STATUS LOG
STATUS CODES 22
Value
11 LUN app state SD 41 Line shut mode12 Line state SD 42 Line number13 LUN state SD 43 Parameter ent14 LUN d-type SD 44 Parameter type15 LUN d-item SD 45 Interp number16 Act OCL state 46 Line command17 Act op 47 IOCTL status18 Act op SD 48 Step path19 Act status 49 DQ command1A FP index 4A ZQ command1B FP buffer pointer 4B Function number1C App number 4C Flag type1D App number SD 4D Ext type error1E App state 4E Ext type app1F App stop opt 4F Ext pack length20 Appl cur rdy 50 Ext type data21 Appl stats 51 Ext cal req pack22 Queue ID 52 Ext income call pack23 Queue response app numumber 53 Ext signon rec 24 Queue response app status 54 Ext ready rec 25 Queue response status 55 Ext called address26 Queue response LUN number 56 Ext calling address27 Queue IO type 60 Bad stats type28 Queue ent type 61 Far ptr29 Queue ent type SD 63 Ext TID2A Queue ent pointer 64 Number of bytes2B IOCTL command2C IOCTL command SD2D IOCTL SL type2E Signal value2F RW length
Table 2-3. Data Types (Continued)
Type
Following Data ValueTyp
eFollowing Data
STATUS LOG 83
STATUS CODES23
ine IDs (offset 10-11),”
upplemental Error
field. See Table 2-3,
Entry header
Registersduring event(in last 10 bytesof entry)
Data type & value(number of pairsvaries with thesituation)
23 Internal Error in the OCL Interface Code
The entry format for status code 23 is unusual in a couple of ways. First, it isvariable length. Second, it uses data type and value pairs: the data-typefield holds a code identifying the kind of data in the following data-valuefield.
10 Bad return value from XRETLUN routine.
11 Bad return value from XREAD routine.
12 Bad return value from XIOABORT routine.
13 Bad return value from XWRITE routine.
14 Bad return value from XSETSTATE routine.
15 Bad return value from XCLOSE routine.
70 Bad return value from XGETLUN routine.
71 Bad return value from XGETBUF routine.
73 ACL_INIT routine failed to create a priority queue for a caller. If the supplemental status code in offset 12 is 01, the application queue could not be created. The data value field in offset 18-1B holds the number of bytes that were requested.
77 Bad response status received from a priority queue entry.
78 Incorrect application number found when OCL interface routines received an application queue entry.
79 Incorrect entry type found when OCL interface routines received an application queue entry.
7A Incorrect LUN number found when OCL interface routines received an application queue entry.
Offset Label Field Description
10-11 Routine ID Routine that logged the event. See Table 2-1, “Routon page 80.
12 1Supplementalstatus code
Extra information about the event. See Table 2-2, “SCodes (Offset 12),” on page 82.
13 2Unused
Varies Data type Identifies the kind of data in the following data-value“Data Types,” on page 82.
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1FData type Data typeData value
Routine ID21
Data type Data value Data type
Data value Data type Data value Data typeData value EBP EIP CS
… … … … …
Data value
1Supplemental status code2Unused
84 STATUS LOG
STATUS CODES 24
e IDs (offset 10-11),”
pplemental Error
field. See Table 2-3,
24 EAP-Related Error
The entry formats for status code 24 are unusual in a couple of ways. First,they are variable length. Second, they use data type and value pairs: thedata-type field holds a code identifying the kind of data in the following data-value field.
The following fields are used in all of the subcodes:
Offset Label Field Description
10-11 Routine ID Routine that logged the event. See Table 2-1, “Routinon page 80.
12 Supplementalstatus code
Extra information about the event. See Table 2-2, “SuCodes (Offset 12),” on page 82.
13 Unused
Varies Data type Identifies the kind of data in the following data-value “Data Types,” on page 82.
STATUS LOG 85
STATUS CODES24
Entry header
Registersduring event(in last 10 bytesof entry)
Data type & valuepairs
01 Data exception error.
02 Function error.
Offset Label Field Description
12 1Supplementalstatus code
13 2Unused
18-1B Error value Used only with subcode 01:05 Illegal parameter type.06 Parameter not valid with this command.07 Required parameter missing.
08 Parameter value out of range.09 String length incorrect.0A Variable length value incorrect.0B Non-digit found in digit string.
0C Inconsistent data.0D Not an ASCII string.0E Conflicting parameters.0F Illegal string.10 Duplicate parameter.
00010 10111213 14151617 18191A1B 1C1D1E1F
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
Type = 4D Type = 4ERoutine ID
21
Type = 4F Length Type = 50
EBP EIP CS
…Error value
EAP applicationnumber (>0)
Packet data that caused the error(length varies and is in offset 28-2B)
00030
86 STATUS LOG
STATUS CODES 24
are busy.r.
d first.
g.
d...
Entry header
Registersduring event(in last 10 bytesof entry)
Data type & valuepairs
03 Protocol error.
Offset Label Field Description
12 1Supplementalstatus code
00 No specific value is logged.C3 Application number does not exist.
C4 OCL is not up.C5 OCL interface routine internal error.C6 All LUN’s for the requested application number C7 Low LUN’s for the requested application numbe
C8 Buffer overflow—LUN will be cleared.C9 LUN is cleared.CA Operation time-out—LUN will be cleared.CB LUN already open—ACL_CLOSE must be calle
CC ACL_INIT already performed.CD Successful ACL_OPEN call not performed.CE ACL_INIT call not performed.
13 2Unused
18-1B Error value 00 No specific value is logged.01 Incorrect command header length.02 Unknown command type.03 Unexpected command modifier.04 An invalid command was received.
10 LUN does not exist, or, incorrect LUN status fla11 Failure of read inquiry from EAP.13 Could not write buffer back to EAP.70 Failed LUN request.
FC Completion code from ACL_WRITE not receiveFD Completion code from ACL_READ not receivedFE Completion code from ACL_OPEN not received
00010 10111213 14151617 18191A1B 1C1D1E1F
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
Type = 4D Type = 4ERoutine ID
21
Type = 4F Length Type = 50
EBP EIP CS
…
Error valueEAP applicationnumber (>0)
Packet data that caused the error(length varies and is in offset 28-2B)
00030
STATUS LOG 87
STATUS CODES24
r.
ord in SIGNON.Y record.
Entry header
Registersduring event(in last 10 bytesof entry)
Data type & valuepairs
04 Session error.
Offset Label Field Description
12 1Supplemental status code 10 Unknown serial number received.11 Missing serial number.12 Record length too short.13 Bad command within packet heade
14 Bad packet header received.15 Bad parameter received.16 Invalid application number or passw17 Invalid application number in READ
13 2Unused
28-2F,34-3B
Network address Network address in call request packet.
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
Task ID
Type = 4D Type = 4ERoutine ID
21
Type = 55 Network address
EBP EIP CS
…
Error valueEAP applicationnumber (>0)
Packet data that caused the error(length varies and is in offset 40-43)
Network address Type = 4FType = 50
Type = 56Length
88 STATUS LOG
STATUS CODES 24
holds the number of
s logged at offset 12.gged at offset 12.
Entry header
Registersduring event(in last 10 bytesof entry)
Data type & valuepairs
Entry header
Registersduring event(in last 10 bytesof entry)
Data type & valuepairs
05 Time-out error. The error value in offset 18-1B is 76.
06 EAP non-service affecting (NSA) error.
07 EAP service affecting (SA) error.
08 Facility error.
22 Unexpected or invalid minor error code.
Offset Label Field Description
12 1Supplementalstatus code
If the error value, offset 18-1B, is 80 or 81, this field the communication line.
13 2Unused
18-1B Error value 6E X.25 task is not ready.6F OCL task is not ready.80 Communication line is down. The line number i81 Communication line is up. The line number is loFF Internal error.
Subcode 08 only:9F ASA read operation aborted.A0 ASA write operation aborted.FF82 X.25/ACL subsystem crash.FF86 X.25/ACL subsystem no yet up.FF95 No LUNs of that type available.
00010 10111213 14151617 18191A1B 1C1D1E1F
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
Type = 4D Type = 4ERoutine ID
21
Type = 4F Length Type = 50
EBP EIP CS
…Error value
EAP applicationnumber (>0)
Packet data that caused the error(length varies and is in offset 28-2B)
00030
00010 10111213 14151617 18191A1B 1C1D1E1F
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
Type = 4D Type = 4ERoutine ID
21
Type = 4F Length Type = 50
EBP EIP CS
…
Error valueEAP applicationnumber (>0)
Packet data that caused the error(length varies and is in offset 28-2B)
00030
STATUS LOG 89
STATUS CODES25
e IDs (offset 10-11),”
pplemental Error
field. See Table 2-3,
Entry header
Registersduring event(in last 10 bytesof entry)
Data type & value(number of pairsvaries with thesituation)
25 Error in the OCL System Utility Routine
The entry format for status code 25 is unusual in a couple of ways. First, it isvariable length. Second, it uses data type and value pairs: the data-typefield holds a code identifying the kind of data in the following data-valuefield.
6B OCL utility routine reported invalid flag type in TEST_AND_SET rou-tine. The data value field in offset 18-1B holds the flag type.
74 OCL utility routine failed to send a priority queue entry.
Offset Label Field Description
10-11 Routine ID Routine that logged the event. See Table 2-1, “Routinon page 80.
12 Supplementalstatus code
Extra information about the event. See Table 2-2, “SuCodes (Offset 12),” on page 82.
13 Unused
Varies Data type Identifies the kind of data in the following data-value “Data Types,” on page 82.
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1FData type Data typeData value
Routine ID21
Data type Data value Data type
Data value Data type Data value Data typeData value EBP EIP CS
… … … … …
1Supplemental status code2Unused
Data value
90 STATUS LOG
STATUS CODES 26
Registersduring event
Entry header
26 Internal Error Occurred During IVR Application
01 Programming logic error.
02 Logic error in Trees.
03 Unknown return code received.
04 Value from Trees is out of range.
05 Wrong number of parameters from Trees.
06 Bad digit string.
07 Error when attempting to acquire called ID.
08 Error when attempting to acquire caller’s ID.
E4 Error in message send command.
E5 Error in outcall (LT-IVR).
E6 Error in ready outcall.
E7 Error in transfer reconnect.
E8 Error in phrase evaluate return code.
E9 Error in message record command.
EA Error in message play command.
EB Error in message inquiry command.
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
Task ID
00020
00000 00010203 04050607 08090A0B 0C0D0E0F
00010
00030
00040
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0*Unused
STATUS LOG 91
STATUS CODES26
Registersduring event
Entry header
EC Error in message delete command.
ED Error in message save command.
EE Error in IVR_ACL_IO routine.
EF Error in IVR error parameter routine.
F0 Error in visit mailbox command.
F1 Error in exit subscriber mailbox command.
F2 Error in exit destination mailbox command.
F3 Error in transfer blind command.
F4 Error in transfer command.
F5 Error in time/date command.
F6 Error in time-out default command.
F7 Error in port disconnect command.
F8 Error in super session command.
F9 Error in key purge command.
FA Error in key cutoff command.
FB Error in key action command.
FC Error in digit play command.
FD Error in digit collect command.
FE Error in ready response command.
FF Error in phrase play command.
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
Task ID
00020
00000 00010203 04050607 08090A0B 0C0D0E0F
00010
00030
00040
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0*Unused
92 STATUS LOG
STATUS CODES 27
Entry headerRegistersduring event
27 Internal Error Occurred During ASA Application
4D Incorrect LUN state returned from OCL when the ASA task sent a request to OCL.
5C Unknown parameter type received.
72 Status code returned by MEM_GDT_GET_16 routine when attempt-ing to allocate memory space for the ASA task.
73 Status code returned by ACOS_CREATPQ_16 routine when attempt-ing to create a priority queue for the ASA task.
75 Status code returned by ACOS_RCVPQ_16 routine when attempting to receive data from a priority queue.
77 Error response status returned from ACOS_RCVPQ_16 routine.
79 Unexpected response received from ACOS_RCVPQ_16 routine.
9D Status code generated by SYS_ENT_FDIR_FACCESS routine when attempting a file access from the voice processor.
9E Cannot find corresponding entry in ASA application table.
A1 ASA could not create an event.
A2 Invalid upload/download index detected in the ASA task.
A3 ASA passed an invalid upload/download request block to an SP rou-tine and the routine returned an error to the ASA task.
A4 ASA detected an invalid upload/download type in the ASA internal table.
A5 ASA task detected an invalid upload/download status in the ASA internal table.
Task ID
CS
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 1011 EBP EIP
Data dependingon subcode
STATUS LOG 93
STATUS CODES28
e IDs (offset 10-11),”
pplemental Error
field. See Table 2-3,
28 Internal Error in the OCL Task
The entry formats for status code 28 are unusual in a couple of ways. First,they are variable length. Second, they use data type and value pairs: thedata-type field holds a code identifying the kind of data in the following data-value field.
The following fields are used in all of the subcodes:
Offset Label Field Description
10-11 Routine ID Routine that logged the event. See Table 2-1, “Routinon page 80.
12 Supplementalstatus code
Extra information about the event. See Table 2-2, “SuCodes (Offset 12),” on page 82.
13 Unused
Varies Data type Identifies the kind of data in the following data-value “Data Types,” on page 82.
94 STATUS LOG
STATUS CODES 28
Entry header
Registersduring event(in last 10 bytesof entry)
Data type & value(number of pairsvaries with thesituation)
11 Bad return code from XREAD routine.
15 Bad return code from XCLOSE routine.
16 Bad return code from XOPEN routine.
17 Bad return code from XIOCTL routine.
18 Invalid LUN number detected.
20 Incorrect IOCTL command found in line state machine.
40 Application number not found in application table.
42 Unrecognized signal value received by OCL task.
43 Inconsistent or illegal action operation found within either the line state machine or the LUN state machine.
44 Bad status value found in action list entry.
45 Incorrect state entered in line state machine.
46 Incorrect parameter passed to a specific state of the line state machine.
47 Invalid IOCTL type value found when the OCL task attempted to invoke XIOCTL.
48 Bad result value from X.25 XIOLST level 1 status detected.
49 Bad result value from X.25 XIOLST level 2 status detected.
4B Action entry address missing in LUN state machine.
4C Unrecognized command type detected in LUN state machine.
4D Inconsistent OCL state in OCL LUN table detected.
4E Invalid shutdown option detected when the OCL task attempted to stop an application.
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1FData type Data typeData value
Routine ID21
Data type Data value Data type
Data value Data type Data value Data typeData value EBP EIP CS
… … … … …
1Supplemental status code2Unused
Data value
STATUS LOG 95
STATUS CODES28
Entry header
Registersduring event(in last 10 bytesof entry)
Data type & value(number of pairsvaries with thesituation)
4F Unrecognized command in line state machine.
50 Invalid shutdown option detected when LUN state machine attempted to shutdown an LUN for a physical interface.
51 Invalid shutdown mode detected when LUN state machine attempted to shutdown a line.
52 Ready application count in application table does not match ready count in OCL LUN table.
53 Invalid application status detected.
55 Matching action was not in progress when the OCL task received an I/O response from a priority queue.
56 Unknown action operation value detected in an entry of the action list.
57 Action table full.
58 No matching action list entry found for an I/O response from a priority queue.
59 OCL task reported key pointer passed to public key encryption/decryption is not NULL.
62 Action list initialization routine called more than once.
63 No current action entry when requesting deletion of current action.
66 OCL task tried to write on the server LUN.
67 OCL task attempted to write a CLEAR packet on the server LUN.
69 Line number out of range. The data value field in offset 18-1B holds the line number.
6C Bad return value received when the OCL task requested to build a parameter buffer.
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1FData type Data typeData value
Routine ID21
Data type Data value Data type
Data value Data type Data value Data typeData value EBP EIP CS
… … … … …
Data value
1Supplemental status code2Unused
96 STATUS LOG
STATUS CODES 28
Entry header
Registersduring event(in last 10 bytesof entry)
Data type & value(number of pairsvaries with thesituation)
tries
Entry header
Registersduring event
Data type & value(number of pairs
(in last 10 bytesof entry)
varies with thesituation)
72 OCL task attempted to allocate dynamic memory for the internal tables.
74 OCL task failed to send a queue entry.
Offset Label Field Description
12 1Supplemental status code
04 Application table cannot be allocated.05 LUN table cannot be allocated.06 Line table cannot be allocated.07 Action table cannot be allocated.08 Local action table cannot be allocated.09 Local line table cannot be allocated.
13 2Unused
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1FData type Data typeRoutine ID
21
Data type Data value Data type
Data value Data type Data value Data typeData value EBP EIP CS
… … … … …
Number of enin table
Table size,in bytes
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
Task ID
Data type Data typeRoutine ID
21
3 Data valueQueue ID
FAR pointer toqueue entry
Data type Data typeData value Data value
Data type Data typeData value Data valueEBP EIP CS
1Supplemental status code2Unused3Result returned from SENPQ call
… … … … …
STATUS LOG 97
STATUS CODES28
Entry header
Registersduring event(in last 10 bytesof entry)
Data type & value(number of pairsvaries with thesituation)
75 Bad status value returned when the OCL task attempted to receive a queue entry from a priority queue.
79 Unrecognized or unexpected entry type found when the OCL task received a priority queue entry.
7A Invalid LUN number detected when the OCL task received a priority queue entry.
7D Server LUN failed to open properly. The data value field in offset 18-1B holds the status code for the open action.
90 Bad OCL stats request. The data value field in offset 18-1B holds the incorrect value for the request.
Offset Label Field Description
12 1Supplemental status code
01 Application queue.02 OCL signal queue.
13 2Unused
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1FData type Data typeData value
Routine ID 21
Data type Data value Data type
Data value Data type Data value Data typeData value EBP EIP CS
… … … … …
Data value
98 STATUS LOG
STATUS CODES 29
e IDs (offset 10-11),”
pplemental Error
field. See Table 2-3,
29 Internal Error in the Router Code
The entry formats for status code 29 are unusual in a couple of ways. First,they are variable length. Second, they use data type and value pairs: thedata-type field holds a code identifying the kind of data in the following data-value field.
The following fields are used in all of the subcodes:
Offset Label Field Description
10-11 Routine ID Routine that logged the event. See Table 2-1, “Routinon page 80.
12 Supplementalstatus code
Extra information about the event. See Table 2-2, “SuCodes (Offset 12),” on page 82.
13 Unused
Varies Data type Identifies the kind of data in the following data-value “Data Types,” on page 82.
STATUS LOG 99
STATUS CODES29
Entry header
Registersduring event(in last 10 bytesof entry)
Data type & value(number of pairsvaries with thesituation)
18 X.25 router detected invalid LUN.
Offset 18-1B: the LUN.
30 Router attempted to put a new entry in the D-queue but the D-queue had no more room.
31 Requested transfer length is greater than actual packet length when X.25 packet WRITE operation is performed.
Offset 18-1B: LUN.Offset 20-23: packet length.
32 Router reported it received an unrecognized ZQ entry type.
Offset 18-1B: command code.Offset 20-23: related LUN.
33 Unexpected or invalid status in the ZQ entry picked up from the TITN code.
Offset 18-1B: LUN.Offset 20-23: the status.
6A Unrecognized X interface routine called.
72 X.25 attempted to allocate dynamic memory for the internal tables. If the supplemental status code at offset 12 is 0C, the X.25 LUN table could not be allocated.
7B Router in SP reported that the task trying to process a Z-queue entry is not an X.25 task.
Offset 18-1B: ID of the task processing the entry.Offset 20-23: X.25 task ID.
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1FData type Data typeData value
Routine ID21
Data type Data value Data type
Data value Data type Data value Data typeData value EBP EIP CS
… … … … …
Data value
1Supplemental status code2Unused
100 STATUS LOG
STATUS CODES 2E
Entry header
Registersduring event
Data type & value(number of pairs
(in last 10 bytesof entry)
varies with thesituation)
Entry header
)t)
t
7C OS failed to alias application task address to the X.25 task.
2E Debug Messages in X.25
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
Task ID
Data type Data typeRoutine ID
21
Data type Data valueFAR pointerbeing aliased
Data type Data typeData value Data value
Data type Data typeData value Data valueEBP EIP CS
1Supplemental status code2Unused
… … … … …
Applicationtask ID
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050 50515253 54555657 58595A5B 5C5D5E5F
00060 60616263 64656667 68696A6B 6C6D6E6F
00070 70717273 74757677 78797A7B 7C7D7E7F
00080 80818283 84858687 88898A8B 8C8D8E8F
00090 90919293 94959697 98999A9B 9C9D9E9F
000A0 A0A1A2A3 A4A5A6A7 A8A9AAAB ACADAEAF
Footprint buffer - entry 1 *
Footprint buffer - entry 5 *Footprint buffer - entry 6 *Footprint buffer - entry 7 *
Footprint buffer - entry 9 *Footprint buffer - entry 8 *
Footprint buffer - final entry *
Footprint buffer - entry 2 *Footprint buffer - entry 3 *Footprint buffer - entry 4 *
Byte 0: footprint operation code **Byte 1: operation statusByte 2: lun_acl_state value when entry was made (operation dependantByte 3: lun_app_state value when entry was made (operation dependanByte 4 - 0F: operation dependant buffer (12 bytes)
*
Footprint operation codes:**1 Open operation footprint2 Close operation footprint3 Read operation footprint4 Write operation footprint5 IOCTL operation footprint6 Signal received footprint7 Application footprint operation
8 Get application LUN footprint9 Return application LUN footprin10 Abort an I/O in progress11 Set encryption key in router12 Change I/O user for LUN13 Get outcall LUN footprint
STATUS LOG 101
STATUS CODES2F
e IDs (offset 10-11),”
pplemental Error
field. See Table 2-3,
Entry header
Registersduring event
Data type & value
5
2F OCL Debug Error
The entry format for status code 2F is unusual in one way. It uses data typeand value pairs: the data-type field holds a code identifying the kind of datain the following data-value field.
Offset Label Field Description
10-11 Routine ID Routine that logged the event. See Table 2-1, “Routinon page 80.
12 Supplementalstatus code
Extra information about the event. See Table 2-2, “SuCodes (Offset 12),” on page 82.
13 Unused
Varies Data type Identifies the kind of data in the following data-value “Data Types,” on page 82.
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 3435
Type = 04 Type = 06Data value
Routine ID21
Type = 10 Data value EBPData value
EIP CS
LUN OCL state
LUN OCL state SD =LUN clear VC state
Logical user number for X.2
1Supplemental status code2Unused
102 STATUS LOG
STATUS CODES 30
Entry headerRegistersduring event
30 SP-Related OCL Error
01 Problem sending application status command to OCL.Offset 10-11: return code from X_SIGNAL_32.
02 Bad OCL initialization error.
03 Bad response to OCL start line command.Offset 10-11: response type returned from OCL.
04 Bad response to OCL stop line command.Offset 10-11: response type returned from OCL.
05 Bad response to OCL line status query.Offset 10-11: response type returned from OCL.
06 Bad OCL signal—line status error.
07 Bad OCL signal—application status error.
08 Bad OCL signal—application add error.
09 Bad OCL signal—application delete error.
0A Bad OCL signal—application modify error.
0B Bad OCL signal—LUN status error.
0C Bad OCL signal—clear LUN error.
0D Bad OCL signal—EAP add error.
0E Bad OCL signal—EAP delete error.
0F Bad OCL signal—EAP modify error.
10 Bad OCL signal—line configuration error.
11 Bad X.25 LUN open error.
12 Bad X.25 LUN read error.
13 Bad X.25 LUN write error.
14 Bad X.25 LUN IOCTL error.
15 Bad X.25 LUN close error.
16 Bad X.25 LUN I/O abort error.
17 Bad return from priority queue.Offset 10-11: return code from RCVPQ.
18 Wrong item number (line application, LUN, etc.) returned by OCL.Offset 10-11: ID number returned from OCL.
19 Wrong response to OCL queue entry.Offset 10-11: response type returned from OCL.
1A SMT/OCL application states out of syncOffset 10-11: file ID.
Task ID
CS00000 00010203 04050607 08090A0B 0C0D0E0F
00010 1011 EBP EIP
Data dependingon subcode
STATUS LOG 103
STATUS CODES31
Entry headerRegisters oftask in error
31 Task Loop
Task running for more than four seconds without performing I/O.
32 Task Locked Out
Task has not run for more than five minutes although in a ready state.
Task ID
CS00000 00010203 04050607 08090A0B 0C0D0E0F
00010 1011 EIP
ID of task in error
104 STATUS LOG
STATUS CODES 3F
Entry headerRegistersduring event
33 Fatal Inconsistency in the OS
34 Fatal Inconsistency for Requestor in Application Task
35 Control Bus Error—Minor
36 Control Bus Error—Major
37 Control Bus Error—Indeterminate
38 Privilege Violation Interrupt
39 Spurious Interrupt
3A Data Bus Error—Unsolicited Device Interrupt
3B Data Bus Error—Unsolicited Software Timer Interrupt
3C Data Bus Error—Device Time-out
3D DMA Error—Unsolicited Device Interrupt
3E DMA Error—Unsolicited Software Timer Interrupt
3F DMA Error—Device Time-out
CS
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 1011AX
STATUS LOG 105
STATUS CODES40
Entry headerRegistersduring event
000000
40 Scanner Card Error—Minor
41 Scanner Card Error—Major
42 Scanner Card Error—Indeterminate
43 System Manager I/O Error (Transmission Error)
44 DUART-0 Spurious Device Interrupt
45 Scanner Card Error—Acknowledgment Bad Channel
46 Scanner Card Error—Acknowledgment Not Expected
CS
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 1011AX
106 STATUS LOG
STATUS CODES 47
d together to form the
cted from the scanner.
the scanner.
rom the scanner.
, to be transmitted.
age buffer.
Registersduring event
Entry header
s
47 Scanner Card Error—Bad Checksum
Offset Label Field Description
20 Supplemental code Carries four flags. The following values advalue in the field:
10 (Bit 4 set.) Overrun.20 (Bit 5 set.) Parity.40 (Bit 6 set.) Framing.80 (Bit 7 set.) Break.
21 1Transmit retry counter
22-23 2Next acknowledgment Header of the next acknowledgment expe
24-25 3Send acknowledgment Header of the acknowledgment to send to
26 4Incoming characters Number of characters yet to be received f
27-2A 5Incoming pointer Pointer to the incoming-message buffer.
2B 6Outgoing characters Number of characters left to transmit.
2C-2F 7Outgoing pointer Pointer to the outgoing-message buffer.
39-3B 8Whole acknowledgment The acknowledgment, including checksum
3C-3F 9Outgoing origin Pointer to the origin of the outgoing mess
41-44 Head Head of the scanner queue.
45-48 Tail Tail of the scanner queue.
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050 50515253 54555657 58595A5B 5C5D5E5F
00060 60616263 64656667 68696A6B 6C6D6E6F
00070 70717273 74757677 78797A7B 7C7D7E7F
00080 80818283 84858687 88898A8B 8C8D8E8F
00090 90919293 94959697 98
IP DI SI DX CX BX AX
Scanner queue
Incoming message buffer
Flag byte
Supplementalcode
Number of itemsin scanner queue Head Tail
1 2 3 4 65 7
8 9
STATUS LOG 107
STATUS CODES48
Entry headerRegistersduring event
48 Scanner Card Error—Transmit Time-out
49 Scanner Card Error—Transmit Time-out Maximum
Fatal error.
CS
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 1011AX
108 STATUS LOG
STATUS CODES 4B
d together to form the
cted from the scanner.
the scanner.
rom the scanner.
, to be transmitted.
age buffer.
Registersduring event
Entry header
s
4A Scanner Card Error—Duo Errors
4B Scanner Card Error—Parity Error
Offset Label Field Description
20 Supplemental code Carries four flags. The following values advalue in the field:
10 (Bit 4 set.) Overrun.20 (Bit 5 set.) Parity.40 (Bit 6 set.) Framing.80 (Bit 7 set.) Break.
21 1Transmit retry counter
22-23 2Next acknowledgment Header of the next acknowledgment expe
24-25 3Send acknowledgment Header of the acknowledgment to send to
26 4Incoming characters Number of characters yet to be received f
27-2A 5Incoming pointer Pointer to the incoming-message buffer.
2B 6Outgoing characters Number of characters left to transmit.
2C-2F 7Outgoing pointer Pointer to the outgoing-message buffer.
39-3B 8Whole acknowledgment The acknowledgment, including checksum
3C-3F 9Outgoing origin Pointer to the origin of the outgoing mess
41-44 Head Head of the scanner queue.
45-48 Tail Tail of the scanner queue.
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050 50515253 54555657 58595A5B 5C5D5E5F
00060 60616263 64656667 68696A6B 6C6D6E6F
00070 70717273 74757677 78797A7B 7C7D7E7F
00080 80818283 84858687 88898A8B 8C8D8E8F
00090 90919293 94959697 98
IP DI SI DX CX BX AX
Scanner queue
Incoming message buffer
Flag byte
Supplementalcode
Number of itemsin scanner queue Head Tail
1 2 3 4 65 7
8 9
STATUS LOG 109
STATUS CODES4C
Entry headerRegistersduring event
Entry header
Registersduring event
4C Scanner Card Error
4D ACP-Related Error
01 Failed to send SBI message.
02 Illegal function code in message.
03 Illegal function code received.
04 Bad CIP message received.
05 Message buffer fouled up.
06 Invalid request type.
07 Invalid buffer length.
08 Invalid buffer count.
09 Invalid message count.
0A Message lost.
0B Out of buffers.
0C Invalid serial port state.
0D No serial port task defined.
0E Invalid link for write to serial port.
0F Invalid message waiting length for Intecom.
10 Invalid bank specified in write request.
11 Buffer not allocated for serial port write.
12 Error rechaining buffer.
13 Error releasing buffer.
CS
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 1011AX
Task ID
00020 20212223 24252627 2829
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1FEAX EBX ECX EDXESI EDI
Offset
110 STATUS LOG
STATUS CODES 4D
Entry header
Registersduring event
14 Error getting new buffer.
15 Invalid length in transmit message.
16 No transmit routine defined.
17 Invalid serial port write message type.
18 Invalid PBX type in control block.
19 Invalid MID message length.
1A MID transmit failed.
1B Timer not running but it should be.
1C Invalid timer.
1D Timer error—acknowledgment arrival not being timed.
1E Illegal channel in message.
1F Illegal station number in CIP message.
20 Serial receive buffer error.
21 Error getting buffer.
22 Serial transmit error.
Task ID
00020 20212223 24252627 2829
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1FEAX EBX ECX EDXESI EDI
Offset
STATUS LOG 111
STATUS CODES4E
Entry header
4E PIPL Flash Upgrade Error
01 Switch 3 of the master CCF dip switch is set (that is, ON). This invoked the inactive core code of the CCF flash EPROM.
02 Unable to synchronize with all detected cards.
03 Identification (or CB WHO-R-U) error at slot nn.
04 Unable to read OS record 0.
05 Unable to find the xxx file.
06 Unable to open the xxx file.
07 Unable to read the xxx file.
08 Unable to upload the xxx file.
09 CB PROM start upload error at slot nn.
0A CB PROM end upload error at slot nn.
0B CB PROM diagnostics status error at slot nn.
0C CB PROM DMA status error at slot nn.
0D CB PROM start DMA error at slot nn.
0E DMA error at slot nn.
Task ID
00010 FFFFFFFF
Not used
00000 00010203 04050607 08090A0B 0C0D0E0F
112 STATUS LOG
STATUS CODES 50
sages with. The PID is
essage in the status of the entry (which is e). Refer to Table 1-9,
Entry headerCB-in messageRegistersduring event
0
50 Control Bus Error—Checksum Error
The CP read an incoming control bus message and:
• the checksum in the message does not match the calculatedchecksum, or
• the slot in the peripheral address of the message does not matchthe slot value from the interrupt handler (shown in offset 07, bits0-2, of the entry header).
This is a failure in transmitting the message. The CP responds by sendingcontrol bus message 04, Checksum Error, to the peripheral and logging thisentry. Normally, the peripheral sends the original message again. But, if theChecksum Error message cannot be transmitted, the status code 50 entryis immediately followed by status code 58 and 5D entries.
The status code 50 entry contains the control bus message as the CPreceived it.
If there is only one control bus error logged, monitor the system for a fewdays. If there are several errors pointing to the same peripheral, replacethat card. If there are several errors pointing to different peripherals, replacethe CP.
Offset Label Field Description
07 Peripheral ID(PID)
The card that the CP was exchanging control bus mesmade of two fields:
Read with the table on the next page.For channel or port information, see if there is a CB mentry. If there is, get the high-order digit from offset 11the peripheral address field of the control bus messag“Channel of the Peripheral Address,” on page 31.
Peripheral ID (PID)
00020
Task ID is unused
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1FCB task ID
Control Busmessage type
CSIP
0607 08
0000 01117Bit count 23
Bank Slot
STATUS LOG 113
STATUS CODES50
PID Bank Slot 350 Card 250 Card
00
0
0 Not used File card portion of CCF
01 1 Card 2 Line TIC
02 2 Card 3 Line TIC
03 3 Card 4 Line TIC
04 4 Card 5 Line TIC
05 5 Card 6 Line TIC
06 6 Card 1 Line TIC
07 7 Not used Line TIC
08
1
0 Card 8 Not used
09 1 Card 9 Line TIC
0A 2 Card 10 Line TIC
0B 3 Card 12 Not used
0C 4 Card 13 Not used
0D 5 Card 14 Not used
0E 6 Card 7 Not used
0F 7 Card 11 Not used
10
2
0 Card 16
11 1 Card 17
12 2 Card 18
13 3 Card 26
14 4 Card 27
15 5 Card 28
16 6 Card 25
17 7 Card 29
18
3
0 Card 30
19 1 Card 31
1A 2 Card 32
1B 3 Card 34
1C 4 Card 35
1D 5 Card 36
1E 6 Not used
1F 7 Card 15
20
4
0 Not used
21 1 Card 20
22 2 Card 21
23 3 Card 22
24 4 Card 23
25 5 Card 24
26 6 Card 19
27 7 Card 33
114 STATUS LOG
STATUS CODES 53
Entry headerCB messageRegistersduring event
51 Control Bus Error—Checksum Errors Exceeded Limit
Four attempts to send a control bus message to the CP failed with check-sum errors. On the fourth failure, the CP does not send a Checksum Errormessage. Instead, the CP does a soft reset for the peripheral: it clears thechecksum error and checksum-nak counters, and sets the messageexchange disposition to response mode. A status code 51 entry is immedi-ately followed by a status code 5D entry.
The status code 51 entry contains the control bus message as the CPreceived it in the last attempt.
If there is only one control bus error logged, monitor the system for a fewdays. If there are several errors pointing to the same peripheral, replacethat card. If there are several errors pointing to different peripherals, replacethe CP.
52 Control Bus Error—Checksum-Nak On Response
If there is only one control bus error logged, monitor the system for a fewdays. If there are several errors pointing to the same peripheral, replacethat card. If there are several errors pointing to different peripherals, replacethe CP.
53 Control Bus Error—Checksum-Nak On Transmission
The CP received a control bus message 04, Checksum Error, from aperipheral. This indicates that the peripheral found a checksum error whenit tried to read a control bus message from the CP. Normally, the CP sendsthe original message again.
The status entry contains the original control bus message.
If there is only one control bus error logged, monitor the system for a fewdays. If there are several errors pointing to the same peripheral, replacethat card. If there are several errors pointing to different peripherals, replacethe CP.
00020
Task ID is unused
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1FCB task ID
Control Busmessage type
CSIP
Peripheral ID (PID), seetables with status code 50.
STATUS LOG 115
STATUS CODES54
Entry headerRegistersduring event
54 Control Bus Error—Checksum-Naks Exceeded Limit
Four attempts to send a control bus message to a peripheral failed withchecksum errors. On the fourth failure, the CP does not re-send the originalmessage. Instead, the CP does a soft reset for the peripheral: it clears thechecksum error and checksum-nak counters, and sets the messageexchange disposition to response mode. A status code 54 entry is immedi-ately followed by a status code 5D entry.
If there is only one control bus error logged, monitor the system for a fewdays. If there are several errors pointing to the same peripheral, replacethat card. If there are several errors pointing to different peripherals, replacethe CP.
CS00000 00010203 04050607 08090A0B 0C0D0E0F
00010 1011IP
Task ID is unusedPeripheral ID (PID), see
tables with status code 50.
116 STATUS LOG
STATUS CODES 56
Entry headerCB-in messageRegistersduring event
55 Control Bus Error—Invalid Channel Reference
An incoming control bus message has an illegal peripheral address:
• The PID points to an unused slot or to the spare CB peripheral.
• The PID points to a PIC in the Control Bus Assignment table (CBA)but not in the PIC/TIC table.
• The channel in the peripheral address of the control bus messageis out-of-range for the peripheral’s channels.
• For a file system or a line card, the CB task ID is out-of-range fortask IDs. The channel is not checked for these cards.
The CP ignores the message.
The entry contains the control bus message as the CP received it.
If there is only one control bus error logged, monitor the system for a fewdays. If there are several errors pointing to the same peripheral, replacethat card. If there are several errors pointing to different peripherals, replacethe CP.
56 Control Bus Error—Empty Control Bus Slot
The CP received a control bus message interrupt from an unused slot or thespare CB peripheral.
The CP ignores the message.
The entry contains the control bus message as the CP received it. ThePeripheral ID, offset 07, has the bad slot information.
If there is only one control bus error logged, monitor the system for a fewdays. If there are several errors pointing to the same peripheral, replacethat card. If there are several errors pointing to different peripherals, replacethe CP.
00020
Task ID is unused
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1FCB task ID
Control Busmessage type
CSIP
Peripheral ID (PID), seetables with status code 50.
STATUS LOG 117
STATUS CODES57
Entry headerRegistersduring event
57 Control Bus Error—Reset Peripheral
A CB peripheral was reset including:
• clear the checksum error counter
• clear the checksum-nak counter
• set the message exchange disposition to response mode
If there is only one control bus error logged, monitor the system for a fewdays. If there are several errors pointing to the same peripheral, replacethat card. If there are several errors pointing to different peripherals, replacethe CP.
58 Control Bus Error—Transmit Error
The CP failed in sending a control bus message because:
• the peripheral took too long getting ready to receive a message.
• the SBI or the peripheral took too long acknowledging that the mes-sage had been delivered.
• a CRC error occurred during delivery.
If the Task ID (offset 02) = FF then there is no task ID: the field is unused.
If there is only one control bus error logged, monitor the system for a fewdays. If there are several errors pointing to the same peripheral, replacethat card. If there are several errors pointing to different peripherals, replacethe CP.
59 SBI DMA FIFO Underrun
5A SBI DMA FIFO Overrun
CS
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 1011IP
Peripheral ID (PID), seetables with status code 50.
118 STATUS LOG
STATUS CODES 5E
Entry headerRegistersduring event
5B SBI Failed to Cycle in Control Bus Input Read
If there is only one control bus error logged, monitor the system for a fewdays. If there are several errors pointing to the same peripheral, replacethat card. If there are several errors pointing to different peripherals, replacethe CP.
5C SBI Failed to Cycle in Control Bus Output Write
The CP failed in sending a control bus message because the SBI or theperipheral took too long acknowledging that the message had been deliv-ered.
This entry is always followed by a status code 58 entry.
The Task ID field, offset 02, is unused.
If there is only one control bus error logged, monitor the system for a fewdays. If there are several errors pointing to the same peripheral, replacethat card. If there are several errors pointing to different peripherals, replacethe CP.
5D Soft Reset of Control Bus Peripheral
A CB peripheral was reset including:
• clear the checksum error counter
• clear the checksum-nak counter
• set the message exchange disposition to response mode
This reset is usually done after the CP fails in sending a control bus mes-sage.
The Task ID field, offset 02, is unused.
If there is only one control bus error logged, monitor the system for a fewdays. If there are several errors pointing to the same peripheral, replacethat card. If there are several errors pointing to different peripherals, replacethe CP.
5E SBI DMA CRC Error
CS
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 1011IP
Peripheral ID (PID), seetables with status code 50.
STATUS LOG 119
STATUS CODES5F
Entry headerRegisters
5F X.25 Task Crashed
00 Invalid state in driver.
Offset Label Field Description
10 Location of error Where error was detected:00 DMA_CHAIN_INT_RX01 DMA_CHAIN_INT_TX02 DU1_INT_RX03 RX_ASYNC_INT
04 SCC_INT_SIES05 SCC_INT_RX06 SCC_INT_TX07 TX_ASYNC_INT
08 Timer Tick, RX09 Timer Tick, TX0A VXD_ASM_SEND0B VXD_ENABLE_RX0C VXD_START_LINK
11 Line number Physical interface line number.
15 RR0 RR0 value, for SCC lines only.
16 RR1 RR1 value, for SCC lines only.
17 SRx SRx value, for DUART lines only.
18-19 IP Location where error was detected.
1A-1B CS Location where error was detected.
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1BIP CSLocation of error
Line number SRx
Line configuration RR1RR0
TransmitterReceiverstatestate
120 STATUS LOG
STATUS CODES 5F
Entry header
Entry headerParameters in callto X.25 task
Entry header
01 C variables too large for data area.
02 X.25 task panic. To find where the task panicked, grep for m_crash.
03 X.25 reboot routine called.
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
Body Unknown
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 101112
1st parameter *
2nd parameter *
3rd parameter *
* the relative number byte in the crash identifier
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
Body Unknown
STATUS LOG 121
STATUS CODES60
Entry header
Entry header
Entry header
000000
60 Logic Card Status
00 Dead logic card detected.
01 Logic card uploaded and running.
02 Line task was aborted by Daemon Task because of card failure.
03 Logic card diagnostic test failed. The length of this entry varies with the number of tests that failed.
Offset Label Field Description06 Card type The type of card being tested:
00 Primary file system01 Secondary file system02 EPU board03 BMU board04 Phrase file system05 Router ACP06 MSLU ACP07 Cluster card08 UDLC09 PIC card0A LAN card10 Line card15 Fax LT card, 4 port, ground/loopstart16 Fax LT card, 8 port, ground/loop start17 Fax LT card, 4 port, E & M
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
Physical slot of the card
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
Task ID of aborted task
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 1011…Physical slotof the cardIDs of failed tests
(number of IDs dependson how many tests failed)
Card type
122 STATUS LOG
STATUS CODES 60
Entry headerCB-out messageCB-in message
Entry header
04 Logic card failed to upload. The control bus messages are the last outgoing and the last incoming messages.
05 No DLC found in the system.
06 Card Type The type of card being tested:18 Fax LT card, 8 port, E & M19 Voice LT card, 4 port, ground/loop
start1A Voice LT card, 8 port, ground/loop
start1B Voice LT card, 4 port, E & M1C Voice LT card, 8 port, E & M1F Fax LT card, 8 port, VTIC20 FLT Mitel 8 port
Offset Label Field Description
CB task ID
Control busmessage types
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 303132
Physical slotof the card
Uploaderror
Physical slotof the card
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
STATUS LOG 123
STATUS CODES61
Entry header
Entry header
Entry header
Entry headerOutcall number(in offset 1A-24)
61 Incomplete Standby Redundant Card Set
00 Incomplete standby card set found. Offset 11 appears only if a sec-ond card was found.
01 No standby redundant cards found.
02 Standby redundant card was removed.
62 Invalid Leading Digit Dialed for Automated Attendant Transfer
The first digit of an extension number cannot be the trunk-level extensionnumber.
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 1011
Physical slotof 1st standbycard found
Physical slotof 2nd standbycard found
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
Physical slotof the card
00020 …20212223 24
Task ID
00000 0001 0203 04050607 08090A0B 0C0D0E0F00010 10111213 14151617 18191A1B 1C1D1E1F…
Tree locationMailbox number
124 STATUS LOG
STATUS CODES 64
Entry header
IORB header*
CB-out message*CB-in message*Registersduring event
Entry header
IORB header
CB-out messageCB-in message
Registersduring event
63 Channel Reset Was Successful
64 FS/CP Software Error
System or session/task restarted.
The format of the entry varies with the exact cause. Check the entry size.
68-Byte Entry
82-Byte Entry
00020 20212223 24252627 28292A2B 2C2D2E2F
Task ID
CSIP
AX BX CX DX SI DI
DS ES
Peripheraladdress
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050 50515253
00060
CB task ID
Control busmessage types
Tree location
…
…
…
…
*Note the unusual position of the IORB:Header is in offset 14-33CB-out message is in offset 34-43CB-in message is in offset 44-53
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0
Peripheraladdress
CB task ID
Control busmessage types
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
*Unused
STATUS LOG 125
STATUS CODES65
Entry header
IORB header*
CB-out message*CB-in message*Registersduring event
Entry header
IORB header
CB-out messageCB-in message
Registersduring event
65 LC Protocol Error
System or session/task restarted.
The format of the entry varies with the exact cause. Check the entry size.
68-Byte Entry
82-Byte Entry
00020 20212223 24252627 28292A2B 2C2D2E2F
Task ID
CSIP
AX BX CX DX SI DI
DS ES
Peripheraladdress
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050 50515253
00060
CB task ID
Control busmessage types
Tree location
…
…
…
…
*Note the unusual position of the IORB:Header is in offset 14-33CB-out message is in offset 34-43CB-in message is in offset 44-53
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0
Peripheraladdress
CB task ID
Control busmessage types
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
*Unused
126 STATUS LOG
STATUS CODES 66
Entry header
Registersduring event
Entry header
IORB header*
CB-out message*CB-in message*Registersduring event
66 Line Task Internal Error
System or session/task restarted.
00 The format of the entry varies with the exact cause. Check the entry size.
42-Byte Entry
Caused by:
• network directory lookup failure
• batch network transmission failure
• failure of DMA data transfer between CP and DLC
• problem with logging EDBN error code
68-Byte Entry
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 4041
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS EBP EIPCS
Unused
Subcode = 00
Subcode = 00
00020 20212223 24252627 28292A2B 2C2D2E2F
Task ID
CSIP
AX BX CX DX SI DI
DS ES
Peripheraladdress
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050 50515253
00060
CB task ID
Control busmessage types
Tree location
…
…
…
…
*Note the unusual position of the IORB:Header is in offset 14-33CB-out message is in offset 34-43CB-in message is in offset 44-53
STATUS LOG 127
STATUS CODES66
ets 54 and 55 first for ly seven bytes long, a .
all.
Entry header
IORB header*
CB-out message*CB-in message*Registersduring event
Entry header
Registersduring event
6F-Byte Entry
Scanner task error.
01 Not an XMD entry.
02 XMD format error.
03 Phrase error.
04 Not an XMD entry (networking).
05 XMD format error (networking).
06 Phrase error (networking).
07 Type error (networking).
08 Error in converting node record value to user record value.
Offset Label Field Description
54-5A Scanner message Queued incoming scanner message. Check offsthe message type and port. Since the field is onnine-byte message will be missing its checksum
5B 1Scanner switches Value is the sum of the following:20 (Bit 5 set.) Bypass on-hook.40 (Bit 6 set.) Off-hook issued for incoming c80 (Bit 7 set.) Incoming message queued.
Subcode = 00
00020 20212223 24252627 28292A2B 2C2D2E2F
Task ID
CSIP
AX BX
CX DX SI DI DS ES
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050 50515253
00060
CB task ID
Control busmessage types
Tree location
…
…
…
…
*Note the unusual position of the IORB:Header is in offset 14-33CB-out message is in offset 34-43CB-in message is in offset 44-53
Scanner message 1
Peripheraladdress
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 4041
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS EBP EIPCS
Unused
128 STATUS LOG
STATUS CODES 67
Entry header
Registersduring event
Entry header
IORB header*
CB-out message*CB-in message*Registersduring event
Entry header
Registersduring event
67 Tree Invalid Parameter to Action
System or session/task restarted.
00 The format of the entry varies with the exact cause. Check the entry size.
42-Byte Entry
68-Byte Entry
Reported by Line Task.
03 Wrong IRN.
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 4041
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS EBP EIPCS
Unused
Subcode = 00
Subcode = 00
00020 20212223 24252627 28292A2B 2C2D2E2F
Task ID
CSIP
AX BX CX DX SI DI
DS ES
Peripheraladdress
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050 50515253
00060
CB task ID
Control busmessage types
Tree location
…
…
…
…
*Note the unusual position of the IORB:Header is in offset 14-33CB-out message is in offset 34-43CB-in message is in offset 44-53
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 4041
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS EBP EIPCS
Unused
STATUS LOG 129
STATUS CODES68
Entry header
IORB header*
CB-out message*CB-in message*Registersduring event
r contains
68 Tree Invalid Action Sequence
System or session/task restarted.
69 Tree Invalid UR Lock State
System or session/task restarted.
6A Tree Missing Event
6B Interpreter Temporary Area Overflow
6C Bad User Record at Read
Session/task restarted.
6D Bad User Record During Processing
Session/task restarted.
6E Bad User Record at Write
Session/task restarted.
6F Tree Internal Error (Error Action)
00020 20212223 24252627 28292A2B 2C2D2E2F
Task ID
CSIP
AX BX CX DX SI DI
DS ES
Peripheraladdress
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050 50515253
00060
CB task ID
Control busmessage types
Tree location
…
…
…
…
*Note the unusual position of the IORB:Header is in offset 14-33CB-out message is in offset 34-43CB-in message is in offset 44-53
Status Code 6C: AX registethe User Record number
130 STATUS LOG
STATUS CODES 70
lly, this digit is part of athe CB-out message).
Entry header
IORB header*
CB-out message*CB-in message*Registersduring event
70 File System Drive I/O Error During a Write Operation
Session/task restarted. The subscriber heard a deletion notification or anarea-of-interest message when the error occurred.
If there are several status code 70 or 72 entries pointing to different drives,replace the CCF card.
If there are several entries pointing to one drive, run validity checks, gar-bage collect and then the long test from the drive-test utility menu. If the testfails, replace the drive.
Offset Label Field Description
37 Failing drive The left digit is the number of the effected drive. Actuamessage ID occupying offset 37-38 (offset 03-04 of See the description for the control bus message type.
00020 20212223 24252627 28292A2B 2C2D2E2F
Task ID
CSIP
AX BX CX DX SI DI
DS ES
Peripheraladdress
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050 50515253
00060
CB task ID
Control busmessage types
Tree location
…
…
…
…
*Note the unusual position of the IORB:Header is in offset 14-33CB-out message is in offset 34-43CB-in message is in offset 44-53
Failing drive
STATUS LOG 131
STATUS CODES71
Entry header
IORB header*
CB-out message*CB-in message*Registersduring event
71 File System DMA Time-Out
System restarted.
00020 20212223 24252627 28292A2B 2C2D2E2F
Task ID
CSIP
AX BX CX DX SI DI
DS ES
Peripheraladdress
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050 50515253
00060
CB task ID
Control busmessage types
Tree location
…
…
…
…
*Note the unusual position of the IORB:Header is in offset 14-33CB-out message is in offset 34-43CB-in message is in offset 44-53
132 STATUS LOG
STATUS CODES 72
e). If the value is X080 the message is undered. Refer also to the
Entry header
IORB header*
CB-out message*CB-in message*Registersduring event
72 Scramble Code or I/O Error During Message-Read Operation
The subscriber heard a deletion notification or an area-of-interest messagewhen the error occurred.
If the return code of the CB-in message (offset 47) is 01 (unrecoverable diskerror), examine the file card status log for more information.
If there are several status code 70 or 72 entries pointing to different drives,replace the CCF card.
If there are several entries pointing to one drive, run validity checks, gar-bage collect and then the long test from the drive-test utility menu. If the testfails, replace the drive.
Offset Label Field Description
37-38 Failing drive(read Field Description)
Message ID (also offsets 03-04 of the CB-out messagor X081, X is the drive number. If the value is 0100,deletion and the drive number cannot be determindescription for the control bus message type.
00020 20212223 24252627 28292A2B 2C2D2E2F
Task ID
CSIP
AX BX CX DX SI DI
DS ES
Peripheraladdress
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050 50515253
00060
CB task ID
Control busmessage types
Tree location
…
…
…
…
*Note the unusual position of the IORB:Header is in offset 14-33CB-out message is in offset 34-43CB-in message is in offset 44-53
Failing drive
STATUS LOG 133
STATUS CODES73
ets 54 and 55 first for ly seven bytes long, a .
all.
Entry header
IORB header*
CB-out message*CB-in message*Registersduring event
73 Scanner Unexpected Error Acknowledgment
The system logged the error and continued.
74 Scanner Wrong Incoming Message
The system logged the error and continued.
75 Line Task Seize Line Time-out
The system logged the error and continued.
76 Scanner Incoming Message at Write
The system logged the error and continued.
77 Scanner Incoming Queue Overflow
The system logged the error and continued.
78 Scanner Error Request Prior to Reset
The system logged the error and continued.
Offset Label Field Description
54-5A Scanner message Queued incoming scanner message. Check offsthe message type and port. Since the field is onnine-byte message will be missing its checksum
5B 1Scanner switches Value is the sum of the following:20 (Bit 5 set.) Bypass on-hook.40 (Bit 6 set.) Off-hook issued for incoming c80 (Bit 7 set.) Incoming message queued.
00020 20212223 24252627 28292A2B 2C2D2E2F
Task ID
CSIP
AX BX
CX DX SI DI DS ES
Peripheraladdress
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050 50515253
00060
CB task ID
Control busmessage types
Tree location
…
…
…
…
*Note the unusual position of the IORB:Header is in offset 14-33CB-out message is in offset 34-43CB-in message is in offset 44-53
Scanner message 1
134 STATUS LOG
STATUS CODES 7A
ets 54 and 55 first for ly seven bytes long, a .
all.
Entry header
IORB header*
CB-out message*CB-in message*Registersduring event
Entry header
Registersduring event
79 Scanner/ITIC Line Failure
The system logged the error and continued.
7A Message Waiting Bad Extension
The system logged the error and continued. Offset 37-3B contains theextension that the PBX did not recognize. (Except for FLT-M Integration onMitel PBX—see below.)
FLT-M Integration on Mitel PBX
Offset Label Field Description
54-5A Scanner message Queued incoming scanner message. Check offsthe message type and port. Since the field is onnine-byte message will be missing its checksum
5B 1Scanner switches Value is the sum of the following:20 (Bit 5 set.) Bypass on-hook.40 (Bit 6 set.) Off-hook issued for incoming c80 (Bit 7 set.) Incoming message queued.
00020 20212223 24252627 28292A2B 2C2D2E2F
Task ID
CSIP
AX BX
CX DX SI DI DS ES
Peripheraladdress
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050 50515253
00060
CB task ID
Control busmessage types
Tree location
…
…
…
…
*Note the unusual position of the IORB:Header is in offset 14-33CB-out message is in offset 34-43CB-in message is in offset 44-53
Scanner message 1
00010
00020
Task ID
CSIP
AX BX
CX DX SI DI DS ES
00000 00010203 04050607 08090A0B 0C0D0E0F
00050
00060
Unused
User Record is stored in the DX register.
00020
00020
STATUS LOG 135
STATUS CODES7B
Entry header
IORB header*
CB-out message*CB-in message*Registersduring event
7B Data Bus Checksum Error
7C File System Out of Synch
00020 20212223 24252627 28292A2B 2C2D2E2F
Task ID
CSIPAX BX CX DX SI DI
DS ES
Peripheraladdress
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050 50515253
00060
CB task ID
Control busmessage types
Tree location
…
…
…
…
*Note the unusual position of the IORB:Header is in offset 14-33CB-out message is in offset 34-43CB-in message is in offset 44-53
136 STATUS LOG
STATUS CODES 7D
Entry headerRegistersduring event
Entry headerRegistersduring event
Entry headerRegistersduring event
Entry headerRegistersduring event
8
7D Batch Network Transmit Error
01 Sender mailbox was deleted. The IUN in the network message can-not be translated into a mailbox number.
02 Bad priority level.Offset 12-13: priority level.
03 Incorrect message type.Offset 12-13: message type.
09 Miscellanious problem with sending message.Offset 12-13: return code identifying problem, see table on page 158.
10 Illegal mailbox type found during return-to-sender operation.
11 Software error during return-to-sender operation.
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1DEBP EIP CS
Node number Sender’s IUN
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1DEBP EIP CS
Node number Data, dependson subcode
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D
Mailbox type IUN
EBP EIP CS
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1DEBP EIP CS
Node number Return code, see table on page 15
STATUS LOG 137
STATUS CODES7E
Entry header
IORB header*
CB-out message*CB-in message*Registersduring event
7E Batch Network Receive Error
00020 20212223 24252627 28292A2B 2C2D2E2F
Task ID
CSIPAX BX CX DX SI DI
DS ES
Peripheraladdress
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050 50515253
00060
CB task ID
Control busmessage types
Tree location
…
…
…
…
*Note the unusual position of the IORB:Header is in offset 14-33CB-out message is in offset 34-43CB-in message is in offset 44-53
138 STATUS LOG
STATUS CODES 7F
f the error:e failed on file system
ew message.
O operation while exe-t.
l. estination.
O operation while exe-
T46). (FS).
Entry header
IORB header*
CB-out message*CB-in message*Registersduring event
7F Batch Network File System I/O Error
Offset Label Field Description
54-55 AX The AX register at the time of the event identifies the cause o01 Get new message, new segment or close old messag
protocol. 02 Illegal message type returned from file system in get n03 Drive error in get new message. 04 File system detected a DMA error from the previous I/
cuting get new message or get new message segmen05 Drive error on get new message segment. 06 Get message destination failed on file system protoco07 Illegal message type returned from file system in get d08 Drive error in get destination. 09 File system detected a DMA error from the previous I/
cuting get new message destination. 0B Unknown error return in get message segment.0D I/O error in start message search (ACT46).0E File system protocol error in start message search (AC0F Get new destination returned an unknown return code
00020 20212223 24252627 28292A2B 2C2D2E2F
Task ID
CSIP
AX BX CX DX SI DI
DS ES
Peripheraladdress
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050 50515253
00060
CB task ID
Control busmessage types
Tree location
…
…
…
…
*Note the unusual position of the IORB:Header is in offset 14-33CB-out message is in offset 34-43CB-in message is in offset 44-53
STATUS LOG 139
STATUS CODES80
Entry header
IORB header*
CB-out message*CB-in message*Registersduring event
000000
80 Batch Network Internal Error
00020 20212223 24252627 28292A2B 2C2D2E2F
Task ID
CSIPAX BX CX DX SI DI
DS ES
Peripheraladdress
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050 50515253
00060
CB task ID
Control busmessage types
Tree location
…
…
…
…
*Note the unusual position of the IORB:Header is in offset 14-33CB-out message is in offset 34-43CB-in message is in offset 44-53
140 STATUS LOG
STATUS CODES 80
f the error:s message was active. ecord area definition. rity.ser record (or no
essage action. ssage search. tring returned from the
ction. message segment
out a message search. “no more segments.” ement the use count in
n from the file system. nvalid record area defi-
th illegal priority. the wrong node record
n action. message destination. t a message search. tion action). string returned from
arch was not active. search was not active.ed by MDS.try in MDS.
Offset Label Field Description
54-55 AX The AX register at the time of the event identifies the cause o01 Get new message action was executed while a previou02 Get new message action was entered with an invalid r03 Get new message action was executed with illegal prio04 Get new message action was entered with the wrong u
record) in area A or B.05 Level or INN mismatch in get new message action.06 Message/segment pending while executing get new m07 Get new message action was attempted without a me08 Get new message action failed on a garbled mailbox s
file system.09 Level or INN mismatch in get new message segment a0A Message/segment pending while executing a get new
action. 0B Get new message segment action was attempted with0C Get new message segment action attempted following0D No message/segments found when attempting to decr
get new message destination action.0E No message active when attempting to get a destinatio0F Get new message destination action entered with an i
nition.10 Get new message destination action was executed wi11 Get new message destination action was entered with
(or no record) in area A or B. 12 Level or INN mismatch in get new message destinatio13 Message/segment pending while executing a get new14 Get new message destination action attempted withou15 “No more destinations” on first destination (get destina16 Get new destination action failed on a garbled mailbox
the file system. 17 Get new message action executed while file system se18 Get new destination action executed while file system 19 Get new destination error from low level routine detect1A Get new destination error from low level routine. No en
STATUS LOG 141
STATUS CODES81
Entry header
IORB header*
CB-out message*CB-in message*Registersduring event
81 Debug Information Message
00020 20212223 24252627 28292A2B 2C2D2E2F
Task ID
CSIPAX BX CX DX SI DI
DS ES
Peripheraladdress
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050 50515253
00060
CB task ID
Control busmessage types
Tree location
…
…
…
…
*Note the unusual position of the IORB:Header is in offset 14-33CB-out message is in offset 34-43CB-in message is in offset 44-53
142 STATUS LOG
STATUS CODES 83
sets 54 and 55 first s only seven bytes ecksum.
call.
Entry header
IORB header*
CB-out message*CB-in message*Registersduring event
82 Error Status from OS Scanner Driver
83 Catastrophic Error Signalled by Scanner
Offset Label Field Description
54-5A Scanner message Queued incoming scanner message. Check offfor the message type and port. Since the field ilong, a nine-byte message will be missing its ch
5B *Scanner switches Value is the sum of the following:20 (Bit 5 set.) Bypass on-hook.40 (Bit 6 set.) Off-hook issued for incoming 80 (Bit 7 set.) Incoming message queued.
00020 20212223 24252627 28292A2B 2C2D2E2F
Task ID
CSIPAX BX
CX DX SI DI DS ES
Peripheraladdress
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050 50515253
00060
CB task ID
Control busmessage types
Tree location
…
…
…
…
*Note the unusual position of the IORB:Header is in offset 14-33CB-out message is in offset 34-43CB-in message is in offset 44-53
Scanner message 1
STATUS LOG 143
STATUS CODES84
e user record. For d is 0000.
the user record. For d is 0000.
t transpose. This igits in the mailbox
Entry header
Registersduring event
84 Bad Password Disconnect
This error entry is logged if a caller tries to access a mailbox and enters theincorrect password a number of times during one session. The system dis-connects the caller after a predetermined number of attempts (set by thesystem manager in menu 1.1). This status code helps the system managerdetect unauthorized activity in the system.
85 Subscriber Exited with Unheard Messages
Offset Label Field Description
16-17 Number of disconnects Number of bad password disconnects in thstatus code 85, this field does not apply an
18-19 Disconnect threshold Threshold for bad password disconnects instatus code 85, this field does not apply an
1B-1F Mailbox # Mailbox number as a decimal string. Do nofield can be read directly. The number of dnumber is given in offset 1A.
00020 20212223CSIP
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
Tree location
IUN Mailbox #
Number ofdisconnects
Disconnectthreshold
Number of digitsin Mailbox #
144 STATUS LOG
STATUS CODES 86
Entry header
IORB header*
CB-out message*CB-in message*Registersduring event
86 Line Task Read or Response Time-out
This entry is often logged because there was no response to the CB-outmessage. In that case the field for the CB-in message will hold garbage.This garbage data is usually clearly inappropriate as a response; forinstance, a File System 38 message in response to a Line Card A2.
This error is followed by a reset command to the port. This usually worksbut is a fatal condition if it fails.
00060 60616263 64656667 68696A6B 6C6D6E6F
00020 20212223 24252627 28292A2B 2C2D2E2F
Task ID
AX BX CX DX SI DI
Peripheraladdress
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050 50515253
CB task ID
Control busmessage types
Tree location
…
…
…
…
*Note the unusual position of the IORB:Header is in offset 14-33CB-out message is in offset 34-43CB-in message is in offset 44-53
00070 70717273 74757677 78797A7B 7C7D7E7F
00080 80818283 84858687 88898A8B 8C8D8E8F
00090 90919293 94959697 98999A9B 9C9D9E9F
000A0 A0A1A2A3 A4A5A6A7 A8A9AAAB ACADAEAF
000B0 B0B1B2B3 B4B5B6B7 B8B9BABB BCBDBEBF
000C0 C0C1C2C3 C4C5C6C7 C8C9CACB CCCDCE
CSIPDS ES
Line card data
1
1Line card data address
STATUS LOG 145
STATUS CODES87
s a decimal string. The et 10.
g destination mailbox, read directly. The num-.
d.
essages.
e system.se system.
Entry header
Registersduring event
forery
87 Batch Network Returned Message—Sender’s Box Full
Offset Label Field Description
11-15 Sender Mailbox number of the sender or forwarding mailbox, anumber of digits in the mailbox number is given in offs
16-17 Node Node number of the original destination.
19-1D Destination Mailbox number of the original destination or forwardinas a decimal string. Do not transpose; this field can beber of digits in the mailbox number is given in offset 18
1E-1F Reason fornon-delivery
01 Mailbox at remote (destination) node was not foun02 Invalid mailbox type for the network message.03 Mailbox at remote node is full.
04 Mailbox at remote node is full with future delivery m05 Remote node file system is full.06 System manager has deleted the node on the bas07 System manager has disabled the node on the ba
08 Bad message detected during transmission.09 Remote node busy—message returned.0A Receiving node did not answer network call.0B Bad line conditions—message returned.0D ASCII name doesn’t match—message returned.0E Mailbox blocking—message returned.0F User had extended absence greeting.10 No fax-capable mailbox to receive message.11 No fax-capable port to receive message.12 No fax-capable node to receive message.13 No fax-capable port to receive message.29 Remote is not supporting AMIS.2A Remote does not support version sent.2B Remote has blacklisted us.2C Cannot access AMIS.2D Remote says message is too long.2F Remote mailbox not accepting this message.31 Remote sent cutoff.32 Bad message.
00010 10111213 14151617 18191A1B 1C1D1E1F
00020 20212223CSIP
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0FNumber of digits
Number of digitsin Destination
Sender DestinationNode
in Sender
Reason non-deliv
146 STATUS LOG
STATUS CODES 88
nt with status code 88. the packet data (offset message type is actu-le system message 28,
ponse.
the cause of the error:
r
Entry header
IORB header*
CB-out message*CB-in message*Registersduring event
88 Bad Community Record at Read
Offset Label Field Description
34-43 CB-out message The output control bus message is slightly differeThe message type (offset 36) and the first byte of37) are overwritten with the value FFFF—but theally 28. To decode the CB-out message, refer to fiRead Data.
44-53 CB-in message Read as file system message 29, Read Data Res
5A-5B DX The DX register at the time of the event identifies 01 Inactive community record02 Bad community record level03 Bad community ICN
04 Bad community number length05 Bad community ASCII name length06 Bad abbreviated address length07 Bad community bulletin mailbox IUN
08 Bad community extension length09 Bad community attendant number0A Bad community attendant schedule numbe0B Bad community after hours mailbox IUN
0C Bad group ASCII name length0D Bad group bulletin mailbox IUN0E Bad group after hours mailbox IUN0F Bad group extension length
10 Bad group attendant number11 Bad group attendant schedule number
00020 20212223 24252627 28292A2B 2C2D2E2F
Task ID
CSIPAX BX CX DX SI DI
DS ES
Peripheraladdress
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050 50515253
00060
CB task ID
Tree location
…
…
…
…
*Note the unusual position of the IORB:Header is in offset 14-33CB-out message is in offset 34-43CB-in message is in offset 44-53
STATUS LOG 147
STATUS CODES89
e of the error:
destination.
Entry header
IORB header*
CB-out message*CB-in message*Registersduring event
Entry header
IORB header*
CB-out message*CB-in message*Registersduring event
89 Batch Network Informational Error
8A SMDI Integration-Related Error
Offset Label Field Description
54-55 AX The AX register at the time of the event identifies the caus01 Failed to close old message in get new message.02 I/O error when decrementing use count in get new
00020 20212223 24252627 28292A2B 2C2D2E2F
Task ID
CSIPAX BX CX DX SI DI
DS ES
Peripheraladdress
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050 50515253
00060
CB task ID
Control busmessage types
Tree location
…
…
…
…
*Note the unusual position of the IORB:Header is in offset 14-33CB-out message is in offset 34-43CB-in message is in offset 44-53
00020 20212223 24252627 28292A2B 2C2D2E2F
Task ID
CSIPAX BX CX DX SI DI
DS ES
Peripheraladdress
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050 50515253
00060
CB task ID
Control busmessage types
Tree location
…
…
…
…
*Note the unusual position of the IORB:Header is in offset 14-33CB-out message is in offset 34-43CB-in message is in offset 44-53
148 STATUS LOG
STATUS CODES 8B
r
age count confirma-
ationion for deletion
eletionmation
ation
mailbox. Problem with te a nonexisting mes-.
maximum recording
sing module due to a
this field can be read given in offset 1A.
Entry header
Registersduring event
8B Bad Command Code for AspenTex
Offset Label Field Description
16-17 Reason for error
Reason the command was bad:02 Bad distribution mailbox password03 Bad command at type 41 main menu
04 Time-out at type 41 main menu05 Error when collecting review mailbox number06 Time-out when collecting review mailbox numbe07 Invalid review mailbox number
08 Invalid review mailbox type09 Invalid command received while waiting for mess
tion0A Time-out while waiting for message count confirm0B Invalid command while collecting message posit
0C Time-out while collecting message position for d0D Invalid command while waiting for deletion confir0E Time-out while waiting for deletion confirmation0F Invalid command while waiting for deposit confirm
10 Time-out while waiting for deposit confirmation12 Tried to deliver more than one message to ECP
review mailboxes. The system either tried to delesage or attempts to deposit new messages failed
13 Disk full while trying to record message14 Recording terminated by invalid keys, silence or
length allowed1E Data module could not log onto the voice proces
bad password1F Password already in use
1B-1F Mailbox # Mailbox number as a decimal string. Do not transpose;directly. The number of digits in the mailbox number is
00020 20212223CSIP
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
Tree location
IUN Mailbox #
Reasonfor error
Unused
Number of digitsin Mailbox #
STATUS LOG 149
STATUS CODES8C
Registersduring event
Entry header
8C AMIS-Related Error
01 Phone number in unknown format.
02 Phone number length error.
03 Access phone number for AMIS not entered.
04 Access phone number for AMIS too long.
05 Could not add an AMIS EAR.
06 Could not delete an AMIS EAR.
07 Could not get dialing sequence from SST.
08 Tree parameter count error.
09 Internal coding error.
0A Mailbox gone, could not return message.
0B Data length in make_fr invalid.
0C Function code in make_fr invalid.
0D Frame length in make_fr invalid.
0E Data in make_fr invalid.
0F Checksum in make_fr invalid.
10 Error in received checksum.
11 Error in received frame length.
12 Error in time-out rules.
13 Error in received data.
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
Task ID
00020
00000 00010203 04050607 08090A0B 0C0D0E0F
00010
00030
00040
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0*Unused
150 STATUS LOG
STATUS CODES 8C
Registersduring event
Entry header
Entry headerRegistersduring event
14 Error in received function code.
15 Disconnect received.
16 Start digit not received.
17 Transmitted frame three times but remote asked for it again.
1E Could not get dialing sequence from dialing-sequence table.
1F Error in message type.
20 Error in NDN field.
21 Error in sending-mailbox field.
22 Error in receiving-mailbox field.
23 Data longer than it should be.
24 Recording error at receiving end.
29 More destinations, but no active message.
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
Task ID
00020
00000 00010203 04050607 08090A0B 0C0D0E0F
00010
00030
00040
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0*Unused
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1BEBP EIP CS
Node
STATUS LOG 151
STATUS CODES8D
Entry headerRegistersduring event
Registersduring event
Entry header
2A No more destinations, no more messages, but bad return code from sys_ent_bnq_get_dest.
2B No more destinations, no more messages, but bad return code from lt_bn_get_message_32.
2C Priority returned by BNQ higher than allowed.
2D Message type other than voice.
2E Unknown return code; Internal error.
2F Unknown return code; Internal error (EOM).
8D AMIS EAR Array at Least 90% Full
8E AMIS Directory at Least 90% Full
00010 10111213 14151617 18191A1B 1C1D
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
EBP EIP CS
Node Return Code
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
Task ID
00020
00000 00010203 04050607 08090A0B 0C0D0E0F
00010
00030
00040
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0*Unused
152 STATUS LOG
STATUS CODES 90
Entry headerRegistersduring event
90 Outcalling Attempted but No Outcalling Phone Number Found in User Record
This error occurs when an outcalling command is generated, but no outcall-ing telephone number existed in menu 9.1. For example, if subscribersenable the outcalling feature in their mailboxes but the system manager hasdeleted the outcalling telephone number in menu 9.1, this error entry willappear.
To correct this problem, the following are possible solutions:
• Instruct the subscriber to disable outcalling in his/her mailbox.
• Instruct the subscriber to enter a telephone number for outcalling in themailbox.
• Enter an outcalling number in menu 9.1 for the subscriber’s mailbox.
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1DIUN
Number of digitsin Mailbox #
Mailbox # CSIP
Outcalling location(schedule number)
STATUS LOG 153
STATUS CODES91
fsets 54 and 55 first is only seven bytes hecksum.
call.
Entry header
IORB header*
CB-out message*CB-in message*Registersduring event
91 Message Waiting on Denied Extension for DMID—COS Does Not Allow Message Waiting
Offset Label Field Description
54-5A Scanner message Queued incoming scanner message. Check offor the message type and port. Since the field long, a nine-byte message will be missing its c
5B 1Scanner switches Value is the sum of the following:20 (Bit 5 set.) Bypass on-hook.40 (Bit 6 set.) Off-hook issued for incoming80 (Bit 7 set.) Incoming message queued.
00020 20212223 24252627 28292A2B 2C2D2E2F
Task ID
CSIPAX BX
CX DX SI DI DS ES
Peripheraladdress
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050 50515253
00060
CB task ID
Control busmessage types
Tree location
…
…
…
…
*Note the unusual position of the IORB:Header is in offset 14-33CB-out message is in offset 34-43CB-in message is in offset 44-53
Scanner message 1
154 STATUS LOG
STATUS CODES 92
Entry header
IORB header
CB-out messageCB-in message
Registersduring event
92 AspenNet Scheduler Error
01 Error in update algorithm.
02 Interval is greater than four hours.
03 Window not defined.
04 Next evaluation time not set.
05 Could not get a semaphore.
06 Evaluation interval is zero.
0A Bad input parameters.
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
00070 70717273 74757677
00080
Peripheraladdress
CB task ID
Control busmessage types
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS EBP EIPCS
Unused
STATUS LOG 155
STATUS CODES93
queue number.
of the sender.
Entry header
IORB header*
CB-out message*CB-in message*Registersduring event
Entry header
IORB header*
CB-out message*CB-in message*Registersduring event
93 Fax Queue is Full
94 Returned Fax—Sender’s Mailbox is Full
95 Returned Fax—Sender’s Mailbox Does Not Exist
Offset Label Field Description
54-55 AX The AX register at the time of the event contains the print
Offset Label Field Description
54-55 AX The AX register at the time of the event contains the IUN
00020 20212223 24252627 28292A2B 2C2D2E2F
Task ID
CSIPAX BX CX DX SI DI
DS ES
Peripheraladdress
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050 50515253
00060
CB task ID
Control busmessage types
Tree location
…
…
…
…
*Note the unusual position of the IORB:Header is in offset 14-33CB-out message is in offset 34-43CB-in message is in offset 44-53
00020 20212223 24252627 28292A2B 2C2D2E2F
Task ID
CSIPAX BX CX DX SI DI
DS ES
Peripheraladdress
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050 50515253
00060
CB task ID
Control busmessage types
Tree location
…
…
…
…
*Note the unusual position of the IORB:Header is in offset 14-33CB-out message is in offset 34-43CB-in message is in offset 44-53
156 STATUS LOG
STATUS CODES 9F
Entry header
IORB header
CB-out messageCB-in messageRegistersduring event
96 FS/CP Software Error
97 Purge Task Internal Error
98 Bad User Record at Read
99 Bad User Record During Processing
9A Bad User Record at Write
9B File System Drive I/O Error
9C File System DMA Time-out
9D Data Checksum Mismatch
9E Data Bus Error Return Code
9F Scramble Code Error or I/O Error
00020 20212223 24252627 28292A2B 2C2D2E2F
Task ID
CSIPAX BX CX DX SI DI DS
ES
Peripheraladdress
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050 5051
00060
CB task ID
Control busmessage types
User recordnumber
STATUS LOG 157
STATUS CODESA0
Entry header
Registersduring event
000000
A0 SST Bad at Write
A1 User Record Message Directory Out of Order
A2 Invalid User Record Lock State
A3 Unknown Network Prefix in Group List Member
This error indicates that the prefix is not valid. If the prefix was deleted byaccident, add it back to the original node. If the prefix is not valid in the sys-tem, an SMT garbage collect may clear up the problem.
00020 20212223 2425
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1Fprefix/mailbox number
IUN of mailbox where group member resides
EBPEIP CS
Tag network address
# of digits
158 STATUS LOG
STATUS CODES A4
Registersduring event
Entry header
A4 Purge Task Encountered an Error While Accessing the IVR Message Directory
01 Unknown return code from sys_ent_imd_delete.
02 Unknown return code from sys_ent_imd_search.
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
Task ID
00020
00000 00010203 04050607 08090A0B 0C0D0E0F
00010
00030
00040
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0*Unused
STATUS LOG 159
STATUS CODESA5
Entry header
Registersduring event
Entry header
IORB header
CB-out messageCB-in messageRegistersduring event
A5 Bad Member Found in Personal Group List
This status code is caused by an invalid IRN or incorrect length.
A6 Error Detected by MDS Functions
MDS detected an error code returned by a low-level routine. The noderecord to be purged might not have been deleted from the system. A “failedto remove network node” error will be returned.
00020 20212223 2425
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1Fprefix/mailbox number
IUN of mailbox where group member resides
EBPEIP CS
Tag network address
# of digits
00020 20212223 24252627 28292A2B 2C2D2E2F
Task ID
CSIPAX BX CX DX SI DI DS
ES
Peripheraladdress
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050 5051
00060
CB task ID
Control busmessage types
User recordnumber
160 STATUS LOG
STATUS CODES A8
Entry headerRegistersduring event
Entry header
IORB header
CB-out messageCB-in messageRegistersduring event
A8 SP General Error
00 Attempt to put invalid (zero) IUN on PT queue. Offsets 10 - 13 con-tains the number of zero entries that a task attempted to put onto the purge task queue.
01 Error updating ACP statistics on ACP home station. While an ACP is used on a station, the software tracks the # of calls arriving with no RS232 integration (i.e., phone rings but switch does not say who is calling), the # of calls that get integration but no ringing (i.e., the switch indicates an incoming call but there is no ringing, the # of parity errors, framing errors, incomplete messages, overruns, and no responses from the ACP card to verify that the ACP card is functioning properly. This error is logged when in a cluster, a problem occurs in transmitting these statistics to the station which contains the ACP card. Hence, there is one of two possible situations: (1) it is not possible to determine which station contains the ACP card (very unlikely), or (2) there is an error in transmitting the message across the FDDI.
03 Mapped ports control bus error. Error occurred during transmission of a single control bus message between stations in a cluster. The station reporting the error was attempting to assign another station to perform an outcall.
Task ID
00010 10111213 14151617 18191A1B 1C1DEBP EIP CS# of bad
IUNs00000 00010203 04050607 08090A0B 0C0D0E0F
00020 20212223 24252627 28292A2B 2C2D2E2F
Task IDPeripheraladdress
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050 5051
CB task ID
Control busmessage types
EBP EIP CS
00000 00010203 04050607 08090A0B 0C0D0E0F
STATUS LOG 161
STATUS CODESA8
nment (range 0-3)
ssignment
Entry headerRegistersduring event
Entry header
IORB header
CB-out messageCB-in messageRegistersduring event
04 Outcalls have been mapped to nonexistent phone lines. With mapped ports, outcalls may be assigned to be performed by only a specific set of ports. This error is reported when a port has been assigned to a company for outcalls, but that port does not exist.
05 Mapped ports control bus error during DMA transmission. Error occurred during DMA transmission of data between stations. When a single station boots in a cluster, it must obtain the memory resident mapped ports database from a machine that is already up and running, since a single VPMOD does not have enough information to build the mapped ports database by itself. During the boot procedure, immediately after the AMT is built, the single booting station will request the mapped ports database from its backup VPMOD. This error is logged when the station is unable to successfully copy the mapped port database.
Offset Label Field Description
10-11 Mapped port range Mapped port range that contains bad port assig
12-13 ICN Company number (ICN) that contains bad port a
Task ID
00010 10111213 14151617 18191A1B 1C1DEBP EIP CS
Mapped port
00000 00010203 04050607 08090A0B 0C0D0E0F
range ICN
00020 20212223 24252627 28292A2B 2C2D2E2F
Task IDPeripheraladdress
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050 5051
CB task ID
Control busmessage types
EBP EIP CS
00000 00010203 04050607 08090A0B 0C0D0E0F
162 STATUS LOG
STATUS CODES AA
Entry header
Registersduring event
mber within the file
ord length
used
try
record
record
Entry header
08 Error reading MDS record; computed address is beyond end of record. Probable cause: problem in allocated bit map.
09 Error writing to MDS record; computed addres is beyond end of record. Probable cause: problem in allocated bit map.
0A Attempted MDS read/write on a non-MDS record.
AA EDBN Directory Not Clean After Two Passes
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 3435EAX
EIP CS
MDS file number
MDS record nu
User Rec
Un
IUN of MDSrecord read from
IUN of MDSrecord read fromdisk/caches
Index ofmessage withinMDS record Offset of first en
Size of entry in MDS
Size of message within MDS
in MDS record
AMT lookup
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
Body Unknown
STATUS LOG 163
STATUS CODESB0
Entry header
Registersduring event
B0 Error Detected by Batch Network Node Management Functions (BNR)
01 Failed to create MDS file.
02 BNR index out of range.
03 Failed to create an event.
04 Bad node prefix.
05 Bad node record data.
06 Synchronization error.
07 Duplicate BNR in cache.
08 Software error.
09 Error in scanning BN queue.
0A Prefix table is full.
0B Bad data for OS_NWOP.
0C Failed to generate NRT.
0D Node does not exist.
0E Duplicate prefix in BNR.
0F Failed to convert NR.
10 Failed to remove old NR.
11 Bad message table is full.
12 Failed to delete NR.
13 Failed to read node record.
14 Failed to save node record.
15 Bad BN message count.
16 Error putting in NDEL PQ.
17 Bad locking sequence.
40 Cluster error.
Offset Label Field Description
14-17 Return Return code:0000 No errorsFFD0 AMT is fullFFD1 Station is downFFD2 Failed to load FC messagesFFD3 No such entry in MDS file
(Return codes continue on next page.)
Task ID
00020 20212223 24252627 2829
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
EBPEAX
CSEDX
Node numberReturn
EIP
164 STATUS LOG
STATUS CODES B0
14-17 Return Return code (continued):FFD4 No more space availableFFD5 Error detected by priority queueFFD6 Node is disabledFFD7 Queue overflow
FFD8 Unknown destinationFFD9 Unknown messageFFDA Error detected by CCCFFDB No destination in destination list
FFDC Sequence error during retrievalFFDD Node is in serviceFFDE Error detected by FSFFDF Node is not under deletion
FFE0 Node is under deletionFFE1 Bad forward messageFFE2 Out of system buffersFFE3 Record is not in cache
FFE4 Old NR is not in FCFFE5 Not a voice messageFFE6 No more messages in queueFFE7 More destinations for message
FFE8 Duplicate destinationFFE9 Message is in 4k bufferFFEA Message is in bufferFFEB Message is in queue
FFEC Message is not in 4k bufferFFED Message is not in bufferFFEE Message/entry is not in queueFFEF Message queue is full
FFF0 Not allowed by error historyFFF1 Task limit exceededFFF2 CIP table is fullFFF3 Task ID is not in CIP table
FFF4 Task ID is in CIP tableFFF5 Not home station of this nodeFFF6 Bad message is not in tableFFF7 Bad message table is full
FFF8 Prefix not foundFFF9 Prefix table is fullFFFA Duplicate prefixFFFB TX is always bad
FFFC Node existsFFFD Node does not existFFFE Error detected by MDSFFFF Bad input data
Offset Label Field Description
STATUS LOG 165
STATUS CODESB1
Entry header
Registersduring event
B1 Error Detected by Batch Network Node Management Functions (BNQ)
20 Failed to create an event.
21 Failed to read entry.
22 Failed to write entry.
23 Failed to put entry.
24 Failed to delete entry.
25 Failed to search an entry.
26 Failed to mark an entry.
27 Failed to unmark an entry.
28 Failed to lock file.
29 Failed to unlock file.
2A Error in putting message.
2B Error in getting message.
2C Error in putting destination.
2D Error in getting destination.
2E No 4k buffer available.
2F Software error.
30 Error in scanning destination.
31 Error in closing message.
32 Failed to get next entry.
33 Failed to delete a queue.
34 Bad sequence of entries.
35 Bad entry type.
36 Bad entry priority.
37 Error in scanning data.
38 Invalid entry address.
39 Failed to collect bad message.
3A Failed to lock BN queue.
3B Failed to get message length.
Task ID
00020 20212223 24252627 2829
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
EBPEAX
CSEDX
Node numberReturn*
*See table with status code B0.
EIP
166 STATUS LOG
STATUS CODES B2
Entry header
Registersduring event
Entry header
Registersduring event
3C Failed to mark (lock) message.
3D Failed to seek an entry.
3E Message conversion errors.
3F NRT synchronization error.
41 Cluster error.
B2 Error with Bulletin Mailbox (IFS)
43 Failed to create an event.
Task ID
00020 20212223 24252627 2829
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
EBPEAX
CSEDX
Node numberReturn*
*See table with status code B0.
EIP
Task ID
00020 2021
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
CSEBP EIP EBP EIP
Caller’smodule
Systemmodule
STATUS LOG 167
STATUS CODESB3
Entry header
Registersduring event
Entry headerRegistersduring event
B3 Bad Mailbox Name Found or Software Error
40 Bad data for NMT entry.
41 Bad type in NMT entry.
42 Bad IRN in NMT entry.
43 Failed to create an event.
44 Bank address out of range.
45 Offset address out of range.
46 NMT index out of range.
47 Bad address to NMT entry.
48 Bad length for name string.
49 Bad digit in dial name.
4A Too many index entries.
4B No index entry to delete.
4C Entry is in use.
4D Entry not found in NMT.
4E Duplicates names for NMT.
4F No delimiter in name field.
50 NMT is full.
51 Too many NMT entries.
52 Bad dial name.
53 Infinite loop in NMT seek.
In Response to sys_nmt_ent_nxt
54 Returned error status from sys_nc_amt_lin_ser.
55 Error in return code of second control bus message.
56 AP for linear search returned an undefined status.
Task ID
00020 2021
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
CSEBP EIP EBP EIP
Caller’smodule
Systemmodule
CSEBP EIP
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010
168 STATUS LOG
STATUS CODES B3
Entry headerRegistersduring event
Entry header
Registersduring event
Entry header
Registersduring event
In Response to sys_nmt_addr_seek
57 Returned error status from sys_nc_amt_dbn_search.
58 AP for binary search returned an undefined status.
59 AP returned too many status values.
5A Too many matched entries.
CSEBP EIP
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010
Task ID
00020 2021
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
CSEBP EIP EBP EIP
Caller’smodule
Systemmodule
Task ID
00020 20212223 2425
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
EIP CSEBPName
Number of digitsin name
STATUS LOG 169
STATUS CODESB3
Entry header
Registersduring event
Entry header
Registersduring event
Entry header
Registersduring event
Entry header
Registersduring event
5B NMT index out of range in nmt_addr_seek.
In Response to nmt_compare
5C Bad length.
In Response to nmt_index_seek
5D Bad length.
5E Infinite loop.
In Response to nmt_index_ins
5F NMT index out of range.
Task ID
00020 2021
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
CSEBP EIP EBP EIP
Caller’smodule
Systemmodule
Task ID
00020 2021
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
CSEBP EIP EBP EIP
Caller’smodule
Systemmodule
Task ID
00020 2021
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
CSEBP EIP EBP EIP
Caller’smodule
Systemmodule
Task ID
00020 2021
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
CSEBP EIP EBP EIP
Caller’smodule
Systemmodule
170 STATUS LOG
STATUS CODES B3
Entry header
Registersduring event
Entry header
Registersduring event
Entry headerRegistersduring event
In Response to sys_nmt_seek
60 Name is not valid.
61 Type is not valid.
62 Bad digit in dial name.
63 Bad length for name string.
64 Index out of range.
In Response to sys_nmt_put
65 Name is not valid.
66 Type is not valid.
67 Bad IRN in NMT entry.
Task ID
00020 2021
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
CSEBP EIP EBP EIP
Caller’smodule
Systemmodule
Task ID
00020 2021
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
CSEBP EIP EBP EIP
Caller’smodule
Systemmodule
CSEBP EIP
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 IRN
STATUS LOG 171
STATUS CODESB3
Entry header
Registersduring event
Entry header
Registersduring event
Entry headerRegistersduring event
68 Bad digit in dial name.
69 Length of zero given for name string.
6A Bad length for name string.
6B Too many index entries.
6C NMT is full.
In Response to sys_nmt_add
70 Name is not valid.
71 Type is not valid.
72 Bad IRN in NMT entry.
Task ID
00020 2021
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
CSEBP EIP EBP EIP
Caller’smodule
Systemmodule
Task ID
00020 2021
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
CSEBP EIP EBP EIP
Caller’smodule
Systemmodule
CSEBP EIP
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 IRN
172 STATUS LOG
STATUS CODES B3
Entry header
Registersduring event
Entry header
Registersduring event
73 Bad digit in dial name.
74 Zero digits in name string.
75 Bad length for name string.
76 Index out of range.
77 Entry is in use.
78 Found name already in NMT. Not added.
79 Too many index entries.
7A NMT is full.
7B NMT on CC full.
In Response to sys_nmt_del
80 Zero digits in name string.
81 Infinite loop in NMT seek.
82 No index entry to delete.
83 Entry not found. Cannot delete.
84 Entry not found. Cannot delete.
Task ID
00020 2021
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
CSEBP EIP EBP EIP
Caller’smodule
Systemmodule
Task ID
00020 2021
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
CSEBP EIP EBP EIP
Caller’smodule
Systemmodule
STATUS LOG 173
STATUS CODESB3
Entry header
Registersduring event
Entry header
Registersduring event
Entry header
Registersduring event
In Response to sys_nmt_match
90 Name is not valid.
91 Bad length for name string.
92 Bad digit in dial name.
94 Entry not found after one match.
In Response to sysnmta.asm
A0 Bad address to NMT entry.
A1 Too many index entries.
A2 Bad address to NMT entry.
A3 No delimiter in name field.
A4 Entry is in use.
A5 Bad length for name string when comparing two entries.
A6 Bad length for name string when allocating a new entry.
Task ID
00020 2021
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
CSEBP EIP EBP EIP
Caller’smodule
Systemmodule
Task ID
00020 2021
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
CSEBP EIP EBP EIP
Caller’smodule
Systemmodule
Task ID
00020 2021
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
CSEBP EIP EBP EIP
Caller’smodule
Systemmodule
174 STATUS LOG
STATUS CODES B4
Entry header
Registersduring event
B4 Bad Network Alias Found or Software Error
90 Bad alias super record.
91 Bad alias track for alias read/write.
92 Bad alias data file. Detected at low levels of alias processing.
93 Failed to read alias record.
94 Failed to write alias record.
95 Failed to open alias file.
96 Detected alias super record damage while checking for a power-fail-ure recovery.
97 Failed to create a file for the node aliases.
98 Bad alias record number to write.
99 Bad alias record to de-allocate.
9A Bad alias record to remove.
A0 Failed to add alias entry.
A1 Failed to remove alias entry.
A2 Bad data for ALS_INSERT.
A3 Invalid alias entry type.
A4 Cannot allocate alias record.
A5 Too many aliases to record.
A6 Cannot allocate alias record.
A7 Cannot load alias record.
A8 Cannot save alias record.
A9 Cannot locate alias record.
80 Bad data for AMT_INSERT.
Task ID
00020 2021
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
CSEBP EIP EBP EIP
Caller’smodule
Systemmodule
STATUS LOG 175
STATUS CODESB5
Entry header
Registersduring event
Entry header
Registersduring event
B5 Failed to Read Network Alias Record from Disk
B6 Failed to Write Network Alias Record to Disk
Note that offset 08-09 holds a track number, not a subcode.
B7 System Restarted by Software—Failed to Allocate Memory for Alias Data
01 Restarted by software break.
02 Restarted by operator.
03 Out of free memory.
Task ID
00020 2021
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
CSEBP EIP EBP EIP
Track number
Caller’smodule
Systemmodule
Task ID
00020 2021
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
CSEBP EIP EBP EIP
Caller’smodule
Systemmodule
176 STATUS LOG
STATUS CODES B8
Entry header
Registersduring event
Entry header
IORB header
CB-out messageCB-in messageRegistersduring event
B8 Failed to Write Company Record to Disk
1B Bad ICN for company record write.
20 Failed to write company record to disk.
Task ID
00020 2021
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
CSEBP EIP EBP EIP
Caller’smodule
Systemmodule
CSEBP EIP EBP EIP
00020 20212223 24252627 28292A2B 2C2D2E2F
Task IDPeripheraladdress
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
CB task ID
Control busmessage types
Caller’smodule
Systemmodule
STATUS LOG 177
STATUS CODESB9
Entry header
Registersduring event
B9 Error in Notification Library
01 Not enough memory available to satisfy a request made by the Notifi-cation Subsystem. The CP may need more memory added or another task may need to reduce the amount of memory it uses.Offset 20-23: the amount of memory requested, in bytes.
04 Problem creating the background queue. Possible coding error, or another task is using a large number of events or priority queues. The Subsystem can only be restarted by rebooting the voice module.Offset 20-23: size value.
06 Unknown statistics function. Possible coding error.Offset 20-23: unknown statistics function requested.
10 Unknown system type. Internal error or possible coding error.Offset 20-23: system type from sys_sst_systype that was not recog-nized.
11 Unable to create broadcast RPC queue. Possible coding error, or another task is using a large number of events or priority queues.Offset 20-23: size value.
12 Error with the initialization of the statistics table lock. Possible coding error, or another task is using a large number of events or priority queues.Offset 20-23: size value.
13 Error with the initialization of the task table lock. Possible coding error, or another task is using a large number of events or priority queues.Offset 20-23: size value.
14 No task currently able to receive entries placed on a particular service queue. Each service queue logs one entry for each purge task cycle. This is usually the result of the system manager failing to configure at least one port to handle a specific service queue.
Offset 16-17: service queue/group number.Offset 20-23: result flags of the queuing operation:
01 (Bit 0 set.) Entry placed in a service queue.02 (Bit 1 set.) A station in the cluster is down.04 (Bit 2 set.) Destination service queue is full.08 (Bit 3 set.) No service queue of this type is on the local station.
15 Error with the initialization of the service base lock. Possible coding error, or another task is using a large number of events or priority queues.Offset 20-23: size value.
00010 10111213 14151617 18191A1B 1C1D1E1F
Task ID
00020 20212223 24252627 2829
00000 00010203 04050607 08090A0B 0C0D0E0F
EBP CSFile Line Serv.
Group
IRN ResultEIP
Data, varieswith subcode
178 STATUS LOG
STATUS CODES B9
Entry header
Registersduring event
16 Error with the initialization of the table area lock. Possible coding error, or another task is using a large number of events or priority queues.Offset 20-23: size value.
18 Error with the initialization of the queue area lock. Possible coding error, or another task is using a large number of events or priority queues.Offset 20-23: size value.
19 Table control array overflow. This is usually logged once for each purge task cycle. Possible coding error.Offset 20-23: size value.
1A Error with the initialization of the run state lock. Possible coding error, or another task is using a large number of events or priority queues.Offset 20-23: size value.
1B Not enough memory to allocate a new table. Possible coding error or the CP needs more memory.Offset 20-23: size value.
1E Notification subsystem detected the use of a full table operation code with a notification table ID that it cannot handle. Logged once for each purge task cycle. Possible coding error.
Offset 20-23: the full table operation code:00 Count non-zero values in table.01 Set high bit in IRN port table.02 Clear the values in the port table.03 Search for IRNs using a port.04 Clear all locks set at boot.05 Get list of all ports in port table.
00010 10111213 14151617 18191A1B 1C1D1E1F
Task ID
00020 20212223 24252627 2829
00000 00010203 04050607 08090A0B 0C0D0E0F
EBP CSFile Line Serv.
Group
IRN ResultEIP
Data, varieswith subcode
STATUS LOG 179
STATUS CODESB9
:
Offset Label Field Description
10-11 File Source file ID:01 notasm.c 02 notglob.c 03 notlock.c
04 notpmap.c 05 oetglob.c 06 notconf.c 07 notims.c
08 notmisc.c09 notque.c0A oetmain.c0B noteval.c
0C notinit.c0D notomap.c0E notstat.c0F notitbl.c
11 sysntask.c12 sysntbl.c13 sysncb.c
14 sysnckpt.c15 sysnserv.c16 sysnfut.c17 sysnovfl.c18 sysfaxq.c
12-13 Line Source file line number.
14-15 Serv. For subcodes 01-18 and 1A: service type:00 Octel Integrated Messaging (IMS)01 Fax outcall02 Message waiting indication03 Normal mailbox outcall
04 Pager outcall05 AspenNet outcall06 AMIS network outcall07 Transact (IVR) outcall
For subcodes 19, 1B and 1E: table ID for the new table00 Overflow table index01 Future evaluation table index02 IMS message count and flag table03 Message waiting indicator table
04 Message waiting port used table05 Message waiting time stamp table
16-17 Group Service group number.
18-1B IRN Internal Reference Number. When not applicable to thesubcode, this field holds 0000.
180 STATUS LOG
STATUS CODES BA
Entry header
Registersduring event(in last 10 bytesof entry)
tion result only)
BA Error in Queuing Module of Notification Library
03 Unknown service.
07 Unknown partition number.
08 Attempt to add entry to non-existent queue.
09 Attempt to add entry to queue failed.
Offset Label Field Description
10-11 File Source file ID:01 notasm.c 02 notglob.c 03 notlock.c
04 notpmap.c 05 oetglob.c 06 notconf.c 07 notims.c
08 notmisc.c09 notque.c0A oetmain.c0B noteval.c
0C notinit.c0D notomap.c0E notstat.c0F notitbl.c
12-13 Line Source file line number.
14-15 Serv. Service number.
16-17 Part. Partition number.
18-19 IRN When not applicable to the subcode, this field holds 0000.
1A-1B Queuefunctionresult
Used only in subcode 09, as the queue function result:FEFF PQERRUSRFDFF PQERROUT
With other subcodes, this field holds 0000.
Task ID
00020
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
EBP EIP CS
File Line Serv. Part. IRN Len.
…
Queue entry(length varies and is in offset 1C-1D)
Queue func(subcode 09
STATUS LOG 181
STATUS CODESBC
d the error.
e lock to be
t 20-23. If the task ss it went to. This lled from.
0-33. If the task ss it went to. This lled from.
Entry header
Registersduring event
BC Error in the Lock Module of the Notification Library
04 Time-out waiting for lock to clear. Possible deadlock condition.
05 Attempt to unlock another’s lock. Possible coding error.
06 Bad return from OS_ENT_EVT_POST. Possible coding error in lock routines or possible problem in OS.
07 Bad return from OS_ENT_EVT_WAIT. Possible coding error in lock routines or possible problem in OS.
08 Magic number not correct (someone stomped on the structure?).
Offset Label Field Description
12-13 Line Source file line number (currently 0000).
14-17 Result of system call Result of system call it the system call cause
18-1B Event ID Event ID used when tasks need to wait for threleased.
20-23 Active task ID of the active task that found the error.
24-2B FAR pointer, active FAR return pointer for the active task in offsereturned to the calling code, this is the addrecan be used to find where the routine was ca
30-33 Lock task ID of the task holding the lock.
34-3B FAR pointer, lock FAR return pointer for the lock task in offset 3returned to the calling code, this is the addrecan be used to find where the routine was ca
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 4849
Internal file IDLine(currently 0000)
EBP EIP CS
UnusedUnused
Event ID Lock countActive taskLock task
FAR pointer, activeFAR pointer, lock
Result ofsystem call
182 STATUS LOG
STATUS CODES BD
from ICN1 in offset
268-432F.
e 10 company
me as the subcode
Entry header
Registersduring event
BD Bad Company Record Found During Start-up Process
01 Bad company record length.
02 Bad company record level.
03 Bad internal company number (ICN).
04 Bad company number length.
05 Bad company name length.
06 Bad contact number length.
07 Bad phone number length.
08 Bad bulletin IUN.
09 Bad after hours IUN.
0A Bad attendant schedule.
0B Bad attendant extension number.
0C Bad attendant phone number.
0D Bad password length.
0E Bad department name.
0F Bad department bulletin IUN.
10 Bad department after hours IUN.
11 Bad department extension number.
12 Bad department attendant number.
13 Bad department attendant schedule.
B5 Bad digit in company number.
Offset Label Field Description
10-11 ICN0 ICN of damaged company record. This may be different 12-13 due to corrupted data.
12-13 ICN1 ICN of damaged company record. Values may be from 4
16-17 Index Index of damaged company record within track. There arrecords per track.
18-19 Offset Offset to damaged data field within the company record.
1A-1B Valid. Subcode from validity check. The value should be the sain offset 08-09.
00010 10111213 14151617 18191A1B 1C1D1E1F
Task ID
00020 20212223 24252627 2829
00000 00010203 04050607 08090A0B 0C0D0E0F
EBP EIP CSICN0 ICN1 * Index OffsetValid. *Unused
STATUS LOG 183
STATUS CODESBE
Entry header
Registersduring event
in
BE Bad User Records Found While Building AMT/NMT During System Start-up
00 No error detected.
01 Mailbox number length is invalid.
02 User record is not assigned.
03 Bad internal logic number (ILN).
04 Bad prompt level.
05 Bad class of service.
06 Bad mailbox length.
07 Bad mailbox ASCII name.
08 Bad extension number length.
09 Bad password length.
0A Bad group member index.
0B Bad group member total.
0C Conflict of message directory or record length.
0D Bad user record revision level.
0E Bad outcall phone number length.
0F Bad department address length.
10 Bad attendant number.
11 Invalid from/to value in message directory entry.
12 Message directory entries out of chronological order.
13 Bad company number
14 Bad department number.
15 Bad abbreviated address length.
16 Bad mailbox alias length.
17 Invalid mailbox forwarding address.
18 Invalid FAX printer extension.
19 Bad attendant schedule number.
1A Bad MDS record.
1B Bad mailbox type.
29 Bad company record length of company record.
2A Bad company record level of company record.
00010 10111213 14151617 18191A1B 1C1D1E1F
Task ID
00020 20212223 24252627 2829
00000 00010203 04050607 08090A0B 0C0D0E0F
EBP EIP CSIUN ILN *Unused
Physical diskaddress
Offset in UR
ith entry inAMT/NMT
subcode (as offset 08)
184 STATUS LOG
STATUS CODES BE
Entry header
Registersduring event
in
2B Bad internal company number (ICN) of company record.
2C Bad company number length of company record.
2D Bad company name length of company record.
2E Bad abbreviated address length of company record.
2F Bad phone number length of company record.
30 Bad bulletin IUN of company record.
31 Bad after-hours IUN of company record.
32 Bad attendant schedule of company record.
33 Bad attendant extension number of company record.
34 Bad attendant phone number of company record.
35 Bad password length of company record.
36 Bad department name of company record.
37 Bad department bulletin IUN of company record.
38 Bad department after-hours IUN of company record.
39 Bad department extension number of company record.
3A Bad department attendant number of company record.
3B Bad department attendant schedule of company record.
3C Bad user record level of company record.
3D Bad company flag in company record.
3E Bad UR flag in company record.
3F Bad IUN peg count in company record.
51 Bad user record length of attendant record.
52 Bad user record level of attendant record.
53 Bad IUN of attendant record.
54 Bad length of attendant schedule number of attendant record.
B0 Bad digit in mailbox number.
B1 Bad digit in mailbox name.
B2 Bad digit in mailbox alias.
B3 Bad digit in abbreviated address.
B4 Bad abbreviated address length.
B5 Bad digit in company number.
00010 10111213 14151617 18191A1B 1C1D1E1F
Task ID
00020 20212223 24252627 2829
00000 00010203 04050607 08090A0B 0C0D0E0F
EBP EIP CSIUN ILN *Unused
Physical diskaddress
Offset in UR
ith entry inAMT/NMT
subcode (as offset 08)
STATUS LOG 185
STATUS CODESBF
Entry header
Registersduring event
in
Entry header
Registersduring event
in
Entry header
Registersduring event
B6 Duplicate mailbox number in AMT.
B7 Duplicate mailbox name in name table.
B8 AMT is full.
B9 NMT is full.
BA Bad digit in attendant schedule number.
BE Damaged user record.
C0 Bad network node prefix.
BF Bad INN or Function Code Found
The error was found while building network maps for node serial numberand mailbox length.
00010 10111213 14151617 18191A1B 1C1D1E1F
Task ID
00020 20212223 24252627 2829
00000 00010203 04050607 08090A0B 0C0D0E0F
EBP EIP CSIUN ILN *Unused
Physical diskaddress (contains 0)
ith entry inAMT/NMT
subcode (as offset 08)
*
00010 10111213 14151617 18191A1B 1C1D1E1F
Task ID
00020 20212223 24252627 2829
00000 00010203 04050607 08090A0B 0C0D0E0F
EBP EIP CSIUN ILN *Unused
Physical diskaddress
Offset in UR
ith UR inbuffer
subcode (as offset 08)
Task ID
00020 2021
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
CSEBP EIP EBP EIP
Caller’smodule
Systemmodule
186 STATUS LOG
STATUS CODES C2
Entry header
Registersduring event
Entry header
Registersduring event
000000
C1 Bad AMIS Transmission Table Found or Software Error
58 Failed to open ATXT file.
59 Failed to create a file for the AMIS Transmission Acceptance Table.
5A Failed to read ATXT file.
5B Failed to create an event.
C2 Failed to Write AMIS Transmission Table to Disk
Note that offset 08-09 holds a track number, not a subcode.
Task ID
00020 2021
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
CSEBP EIP EBP EIP
Caller’smodule
Systemmodule
Task ID
00020 2021
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
CSEBP EIP EBP EIP
Track number
Caller’smodule
Systemmodule
STATUS LOG 187
STATUS CODESC3
Entry header
Registersduring event
Entry header
Registersduring event
C3 Bad AMIS EAR Found or Software Problem
54 Failed to open AEAR file.
55 Failed to create a file for the AEAR.
56 Failed to read AEAR file.
57 Failed to create an event.
C4 Failed to Write AMIS EAR Record to Disk
Note that offset 08-09 holds a track number, not a subcode.
Task ID
00020 2021
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
CSEBP EIP EBP EIP
Caller’smodule
Systemmodule
Task ID
00020 2021
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
CSEBP EIP EBP EIP
Track number
Caller’smodule
Systemmodule
188 STATUS LOG
STATUS CODES C6
Entry header
Registersduring event
Entry header
Registersduring event
C5 Bad AMIS DIR Found or Software Error
5C Failed to open AMIS_DIR file.
5D Failed to create a file for the AMIS_DIR.
5E Failed to read AMIS_DIR file.
5F Failed to create an event.
C6 Failed to Write AMIS DIR Back to Disk
Note that offset 08-09 holds a track number, not a subcode.
Task ID
00020 2021
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
CSEBP EIP EBP EIP
Caller’smodule
Systemmodule
Task ID
00020 2021
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
CSEBP EIP EBP EIP
Track number
Caller’smodule
Systemmodule
STATUS LOG 189
STATUS CODESC7
Entry headerRegistersduring event
inF-20)
Entry headerRegistersduring event
Entry headerRegistersduring event
Entry headerRegistersduring event
inF-20)
C7 T1 Error Counters
01 Report of error counters.
02 Error in control bus message to DLC. If the error code in offset 13-14 is FF, the DLC returned the wrong operation code.
03 Invalid operation code for MTT1_CODE.
41 Report of E1/CEPT error counters.
Task ID
00020 …20
00000 0001 0203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F…DLC banknumber (0-5) EBP EIP
BPVcounter
OOFcounter
EEScounter
CS (offset 1
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1EDLC banknumber (0-5)
DLCnumber
Error code(CB code)
EBP EIP CS
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191AInvalid operationcode EBP EIP CS
Task ID
00020 …20
00000 0001 0203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F…CEPT (E1) groupnumber (0-3) EBP EIP
BPVcounter
OOFcounter
CRC-4 errorcounter
CS (offset 1
190 STATUS LOG
STATUS CODES CD
Entry header
Registersduring event
er/drift
Entry header
IORB header
CB-out messageCB-in messageRegistersduring event
C8 Unable to Read Clock Chip (Continuous Ripple Status Set)
C9 Clock Chip Went Bad While Running (After Boot)
CA System Timer Drifted Too Far From Clock Chip Date/Time
CB Clock Chip Bad or Too Different From SST Timer at Boot
CC Minute Task Internal Error
CD Hard Error on Disk Detected by Minute Task Alarm
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050 50515253 54555657 58595A5B 5C5D
Clock chip image
Control bus messages
AX BX CXDX SI DI DS ES IP CS
8253 timerinterval
System timclock chip
00020 20212223 24252627 28292A2B 2C2D2E2F
Task ID
CSIPAX BX CX DX SI DI DS ES
Peripheraladdress
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
CB task ID
Control busmessage types
STATUS LOG 191
STATUS CODESCE
Entry header
IORB header
CB-out messageCB-in messageRegistersduring event
Entry header
CE Drive Not Running Detected by Minute Task Alarm
CF T1 Alarms
Alarms are handled by the Minute Task.
01 Received yellow alarm.
02 Received LOS (red) alarm.
03 Received OOF alarm.
04 Received FFER (blue) alarm.
05 Received AIS alarm.
06 Received EBPV alarm.
07 Received EES alarm.
00020 20212223 24252627 28292A2B 2C2D2E2F
Task ID
CSIPAX BX CX DX SI DI DS ES
Peripheraladdress
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
CB task ID
Control busmessage types
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10T1 groupnumber (0-3)
card # (1-36)
192 STATUS LOG
STATUS CODES CF
Entry header
41 Loss of carrier on.
42 All 1s unframed on.
43 Loss of frame synchronization on.
44 All 1s TS 16 on.
45 Loss of CAS MF synchronization on.
46 One in 1,000 bit errors on.
47 Loss of CRC-4 frame synchronization on.
48 Remote alarm (framed) on.
49 Remote alarm (MF) on.
4A One in 10,000 bit errors on.
4B One in 100,000 bit errors on.
81 Yellow alarm cleared.
82 LOS (red) alarm cleared.
83 OOF alarm cleared.
84 FFER (blue) alarm cleared.
85 AIS alarm cleared.
86 EBPV alarm cleared.
87 EES alarm cleared.
C1 Loss of carrier off.
C2 All 1s unframed off.
C3 Loss of frame synchronization off.
C4 All 1s TS 16 off.
C5 Loss of CAS MF synchronization off.
C6 One in 1,000 bit errors off.
C7 Loss of CRC-4 frame synchronization off.
C8 Remote alarm (framed) off.
C9 Remote alarm (MF) off.
CA One in 10,000 bit errors off.
CB One in 100,000 bit errors off.
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10CEPT (E1) groupnumber (0-3)
card # (1-36)
STATUS LOG 193
STATUS CODESD0
Entry header
IORB header
CB-out messageCB-in message
Registersduring event
D0 CP/FS Protocol Out of Sequence
01 OS reported one or more lost control bus messages when attempting to read the control bus from the file system.
02 OS reported control bus operation cancelled when attempting to read the control bus from the file system.
03 OS received incoming message from the file system for a task, but the task was not expecting a message.
04 OS reported control bus operation cancelled when trying to read, then write, the control bus from the file system.
05 OS reported control bus operation cancelled when trying to read, then write, the control bus from the file system.
06 OS received an incoming message from the file system for a task, but the task was not expecting a message (send/receive routine).
07 Wrong response to file system message 28, Read Data.
08 Wrong response to file system message 34, Write Data.
09 Wrong response to a CP-to-file-system data bus DMA. File system message 35, Write Data Complete was expected.
0A Wrong response to file system message A6, General Utility.
0B Wrong response to a command.
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0
Peripheraladdress
CB task ID
Control busmessage types
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
*Unused
194 STATUS LOG
STATUS CODES D1
Entry header
IORB header
CB-out messageCB-in message
Registersduring event
D1 Data Bus Operation With File System or Cluster Card Failed
01 OS reported data bus DMA operation failed when reading data from the file system to the CP.
02 OS reported data bus DMA operation failed when writing data from the CP to the file system.
03 Data bus DMA operation failed when reading or writing between the CP and the cluster card.
04 Data bus DMA operation failed when reading or writing between a peripheral and the cluster card.
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0
Peripheraladdress
CB task ID
Control busmessage types
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
*Unused
STATUS LOG 195
STATUS CODESD2
Entry header
IORB header
CB-out messageCB-in message
Registersduring event
D2 Data Bus Checksum Error Between CP and File System
01 OS reported data checksum error when reading data from the file sys-tem to the CP.
02 OS reported data checksum error when writing data from the CP to the file system.
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0
Peripheraladdress
CB task ID
Control busmessage types
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
*Unused
196 STATUS LOG
STATUS CODES D3
Entry header
IORB header
CB-out messageCB-in message
Registersduring event
D3 Control Bus Operation Failed While Preparing or Checking Data Bus Operation with File System or Cluster Card
01 Control bus operation failed while attempting to set up file system for Data Read operation.
02 Control bus operation failed while setting up for Write Data operation (after sending file system message 34, Write Data).
03 Control bus operation failed while waiting for file system message 35, Write Data Complete during the Write Data operation.
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0
Peripheraladdress
CB task ID
Control busmessage types
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
*Unused
STATUS LOG 197
STATUS CODESD4
Entry header
IORB header
CB-out messageCB-in message
Registersduring event
D4 Inconsistent or No Status from OS on Control Bus/Data Bus Operation
01 Inconsistent or no status from OS when attempting to read a control bus message from the file system.
02 Inconsistent or no status from OS when attempting to send, then read, a control bus message from the file system.
03 Inconsistent or no status from OS when attempting to send, then read a control bus message from a line card.
04 Inconsistent or no status from OS when attempting to send, then read with time-out, a control bus message from a line card.
05 Inconsistent or no status from OS when attempting to send, then read a control bus message from the LAN card.
06 Inconsistent or no status from OS when attempting to read a control bus message from the LAN card.
07 Inconsistent or no status from OS when attempting to send a control bus message to the LAN card.
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0
Peripheraladdress
CB task ID
Control busmessage types
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
*Unused
198 STATUS LOG
STATUS CODES D5
Entry header
IORB header
CB-out messageCB-in message
Registersduring event
D5 OS Reported Control Bus Error
01 OS reported control bus failure when attempting to read a control bus message from the file system.
02 OS reported control bus failure when attempting to send, then read a control bus message from the file system.
03 OS buffering system reported control bus failure when attempting to send and then read a control bus message from a line card.
04 OS reported control bus failure when attempting to read, then send a control bus message to the LAN card.
05 OS reported control bus failure when attempting to read a control bus message from the LAN card.
06 OS reported control bus failure when attempting to send a control bus message to the LAN card.
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0
Peripheraladdress
CB task ID
Control busmessage types
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
*Unused
STATUS LOG 199
STATUS CODESD6
Entry header
IORB header
CB-out messageCB-in message
Registersduring event
D6 File System Returned Bad Status in Control Bus Message
01 Bad return code in response to file system message 28, Read Data.
02 DMA byte count is greater than original CP byte count.
03 Bad return code in response to file system message 34, Write Data.
04 Bad return code in response to data bus DMA operation when attempting to write data from CP.
05 Bad return code in response to data directory size request during ini-tial directory build.
06 File system returned a value of less than 10 in response to directory size check during initial directory build.
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0
Peripheraladdress
CB task ID
Control busmessage types
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
*Unused
200 STATUS LOG
STATUS CODES D6
Entry header
Registersduring event
Entry header
IORB header
CB-out messageCB-in message
Registersduring event
07 File system accepted a read operation past the indicated end of the data directory during the initial build.
08 Directory entry found to be damaged during initial directory creation.
09 Bad return code in response to data directory size during a directory check.
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050 50515253 54555657 58595A5B 5C5DEBP EIP CS
Blocknumber
Track number
Filemarker
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0
Peripheraladdress
CB task ID
Control busmessage types
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
*Unused
STATUS LOG 201
STATUS CODESD6
Registersduring event
Entry header
Entry header
Registersduring event
0A File system inconsistency.
0B File system returned a value of less than 10 in response to directory size check during a directory check.
0C File system accepted a read operation past the indicated end of the data directory during a directory check.
0D Damaged directory track found during data directory power-up check.
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
Task ID
00020
00000 00010203 04050607 08090A0B 0C0D0E0F
00010
00030
00040
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0*Unused
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050 50515253 54555657 58595A5B 5C5DEBP EIP CS
Blocknumber
Track number
Filemarker
202 STATUS LOG
STATUS CODES D6
Entry headerRegistersduring event
Entry header
Registersduring event(EIP is inoffset EE-F1)
Entry header(repeated)
Super field size
0E Error while file system attempted to read a track from the data direc-tory.
0F Error while file system attempted to write a track to the data directory.
10 Damaged directory entry found while building data directory.
11 Damaged directory entry found during power-up directory check.
CSEBP EIP
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050 50515253 54555657 58595A5B 5C5D5E5F
00060 60616263 64656667 68696A6B 6C6D6E6F
00070 70717273 74757677 78797A7B 7C7D7E7F
00080 80818283 84858687 88898A8B 8C8D8E8F
00090 90919293 94959697 98999A9B 9C9D9E9F
000A0 A0A1A2A3 A4A5A6A7 A8A9AAAB ACADAEAF
000B0 B0B1B2B3 B4B5B6B7 B8B9BABB BCBDBEBF
000C0 C0C1C2C3 C4C5C6C7 C8C9CACB CCCDCECF
000D0 D0D1D2D3 D4D5D6D7 D8D9DADB DCDDDEDF
000E0 E0E1E2E3 E4E5E6E7 E8E9
000F0
Directory entrynumber
Track number
…EIPEBP
CSEIP…
00020
00000 00010203 04050607 08090A0B 0C0D0E0F
00010
00030 30313233 34353637 38393A3B 3C3D3E3F
Directory entry(second part)
Record sizeSuper record size
SECOND ENTRY
WHOLE “ENTRY” USES TWO STATUS LOG ENTRIES
FIRST ENTRY
Directory entry(first part)
STATUS LOG 203
STATUS CODESD6
Entry header
IORB header
CB-out messageCB-in message
Registersduring event
12 Bad return code in file system message 11, Abandon New Message Response.
13 Bad message ID according to file system message 11.
14 No new message according to file system message 11.
15 Bad return code in file system message 23, Open New Message Response.
16 Disk full according to file system message 23.
17 Message already open according to file system message 23.
18 Bad return code in file system message 15, Close New Message Response.
19 Bad message ID or scramble code according to file system message 15.
1A No messages open according to file system message 15.
1B Message length is 0 according to file system message 15.
1C Bad return code in file system message 25, Open Old Message Response.
1D Bad message ID or scramble code according to file system message 25.
1E Message already open according to file system message 25.
1F Use count at 0 according to file system message 25.
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0
Peripheraladdress
CB task ID
Control busmessage types
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
*Unused
204 STATUS LOG
STATUS CODES D6
Entry header
IORB header
CB-out messageCB-in message
Registersduring event
20 Bad return code in file system message 17, Close Old Message Response.
21 Bad message ID or scramble code according to file system message 17.
22 No message open according to file system message 17.
23 Bad return code in file system message 1B, Decrement Use Count.
24 Bad scramble code or message ID according to file system message 1B.
25 Use count already at zero according to file system message 1B.
26 Bad return code in file system message 2B, Read Message Buffer Response.
27 Bad scramble code or message ID according to file system message 2B.
28 Past end of message according to file system message 2B.
29 Message not open according to file system message 2B.
2A Position or length incorrect according to file system message 2B.
2B Bad return code in file system message 39, Write Message Buffer Response.
2C Bad scramble code or message ID according to file system message 39.
2D Message not open according to file system message 39.
2E Position past EOM according to file system message 39.
2F Disk space full according to file system message 39.
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0
Peripheraladdress
CB task ID
Control busmessage types
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
*Unused
STATUS LOG 205
STATUS CODESD6
Entry header
IORB header
CB-out messageCB-in message
Registersduring event
30 Bad return code in file system message 38, Write Message Buffer Complete.
31 Bad return code (bad ID, etc.) in file system message 1F, Load Prompt Response.
32 Unknown return code in file system message 1F.
33 Bad FPT entry according to file system message B6, General Utility Command Response.
34 Illegal phrase ID according to file system message B6.
35 Phrase not recorded according to file system message B6.
36 Illegal language area according to file system message B6.
37 Unknown return code in file system message B6.
38 Invalid action code according to file system message B6.
39 Invalid language code according to file system message B6.
3A Uninitialized phrase table according to file system message B6.
3B Invalid phrase number according to file system message B6.
3C Phrase does not exist according to file system message B6.
3D Unknown return code according to file system message B6.
3E Phrase not recorded according to file system message 1F, Load Prompt Response.
3F Bad return code; file system increment use count.
40 Bad scramble code or message ID; file system increment use count.
41 Use count already at zero; file system increment use count.
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0
Peripheraladdress
CB task ID
Control busmessage types
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
*Unused
206 STATUS LOG
STATUS CODES D6
Entry header
IORB header
CB-out messageCB-in message
Registersduring event
42 Bad scramble code or bad message ID, reported by file system con-trol bus message 21 (Open Name/Announcement Response).
43 Use count already at zero, reported by file system control bus mes-sage 21 (Open Name/Announcement Response).
44 Bad return code, reported by file system control bus message 21 (Open Name/Announcement Response).
45 Bad scramble code or bad message ID, reported by file system con-trol bus message 2D (Read Name/Announcement Buffer Response).
46 Message damaged on disk, reported by file system control bus mes-sage 2D (Read Name/Announcement Buffer Response).
47 Bad return code, reported by file system control bus message 2D (Read Name/Announcement Buffer Response).
48 Bad scramble code or message ID, reported by file system control bus message 13 (Close Name/Annoucement Response).
49 Bad return code, reported by file system control bus message 2D (Read Name/Announcement Buffer Response).
50 IRN configuration failed.
51 Already open, reported by file system control bus message 21 (Open Name/Annoucement Response).
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0
Peripheraladdress
CB task ID
Control busmessage types
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
*Unused
STATUS LOG 207
STATUS CODESD7
Entry header
IORB header
CB-out messageCB-in message
Registersduring event
D7 File System Reported Drive Error in Returned Control Bus Message
01 Bad drive reported in file system message 29, Read Data Response.
02 Bad drive reported in file system message 36, Write Data Response.
03 Bad drive reported in file system message 35, Write Data Complete.
04 Bad drive reported in file system message 1B, Decrement Use Count Response.
05 Bad drive reported in file system message 2B, Read Message Buffer Response.
06 Bad drive reported in file system message 39, Write Message Buffer Response.
07 Bad drive reported in file system message 38, Write Message Buffer Complete.
08 Bad drive reported in file system message 11, Abandon New Mes-sage Response.
09 Bad drive reported in file system message 25, Open Old Message Response.
0A Bad drive reported in file system message 15, Close New Message Response.
0B Bad drive reported in file system message B6, General Utility Response, for the delete phrase action.
0C Bad drive reported in file system message B6, General Utility Response, for the update FPT action.
0D Bad drive reported in file system message 1D, Increment Use Count Response.
0E Bad drive reported in FS message 21 (Open Name/Announce. Rsp).
0F Bad drive reported in FS message 2D (Read Name/Announce. Rsp).
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0
Peripheraladdress
CB task ID
Control busmessage types
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
*Unused
208 STATUS LOG
STATUS CODES D8
Entry header
IORB header
CB-out messageCB-in message
Registersduring event
D8 File System Reported DMA Failure on Some Previous Operation
01 Previous DMA error reported in file system message 29, Read Data Response.
02 Previous DMA error reported in file system message 36, Write Data Response.
03 Previous DMA error reported in file system message 35, Write Data Complete.
04 Bad drive reported in file system message 1B, Decrement Use Count Response.
05 DMA error reported in file system message 2B, Read Message Buffer Response.
06 DMA error reported in file system message 39, Write Message Buffer Response.
07 DMA error reported in file system message 38, Write Message Buffer Complete.
08 DMA error reported in file system message 11, Abandon New Mes-sage Response.
09 DMA error reported in file system message 25, Open Old Message Response.
0A DMA error reported in file system message 15, Close New Message Response.
0B DMA error reported in file system message B6, General Utility Response.
0C Bad drive reported in file system message 1D, Increment Use Count Response.
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0
Peripheraladdress
CB task ID
Control busmessage types
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
*Unused
STATUS LOG 209
STATUS CODESD9
Entry header
IORB header
CB-out messageCB-in message
Registersduring event
D9 File System Failed to Respond Within Time-out Period
01 Time-out when attempting to read a control bus message from the file system.
02 Time-out when attempting to send, then read, a control bus message from the file system.
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0
Peripheraladdress
CB task ID
Control busmessage types
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
*Unused
210 STATUS LOG
STATUS CODES DA
Entry headerRegistersduring event
DA General File System Control Bus Status Log
01 Control bus operation with file system failed while attempting to get the size of a data directory during initial directory creation.
02 Control bus operation with file system failed while attempting to get the size of a data directory during directory check.
03 Control bus operation failed with file system message B6, General Utility Command Response.
04 Control bus operation failed with file system message 1A, Decrement Use Count.
05 Control bus operation failed with file system message 37, Write Mes-sage Buffer.
06 Control bus operation failed with file system message 38, Write Mes-sage Buffer Complete.
07 Control bus operation failed with file system message 10, Abandon New Message.
08 Control bus operation failed with file system message 16, Close Old Message.
09 Control bus operation failed with file system message 22, Open New Message.
0A Control bus operation failed with file system message 14, Close New Message.
0B Control bus operation failed with file system message 2B, Read Mes-sage Buffer Response.
0C Control bus operation failed with file system message 25, Open Old Message Response.
0D Control bus operation failed with file system message, Load Phrase Response.
0E Control bus operation failed with file system message, Receive Phrase Buffer Response.
0F Control bus operation failed with file system message 74, Add Mes-sage Segment Response.
10 Control bus operation failed with file system message 1C, Increment Use Count.
11 Control bus operation failed with file system: FS Space Available Request.
12 Control bus operation failed with file system: FS Open Name/Announcement.
13 Control bus operation failed with file system: Control bus operation failed with file system: FS Read Name/Announcement BUffer.
CSEBP EIP
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010
STATUS LOG 211
STATUS CODESDA
Entry headerRegistersduring event
14 Control bus operation failed with file system: FS Close Name/Announcement.
15 Control bus operation failed with file system: FS Read Message Buffer Response.
16 Control bus operation failed with file system: FS Write Message Buffer Response.
18 Control bus operation failed while attempting to get the response from the file system for CB_TYPE_FCP command.
19 Control bus operation error logged in the response from the file sys-tem for CB_TYPE_FCPR stat.
1E Control bus operation failed while attempting to get the response from the file system for CB_TYPE_FLP command.
1F Control bus operation error logged in the response from the file sys-tem for CB_TYPE_FLPR stat.
26 Control bus operation failed while attempting to get the response from the file system for CB_TYPE_FOP command.
27 Control bus operation error logged in the response from the file sys-tem for CB_TYPE_FOPR stat.
28 Control bus operation failed while attempting to get the response from the file system for CB_TYPE_FRD command.
29 Control bus operation error logged in the response from the file sys-tem for CB_TYPE_FRDR stat.
2E Control bus operation failed while attempting to get the response from the file system for CB_TYPE_FRPB command.
2F Control bus operation error logged in the response from the file sys-tem for CB_TYPE_FRPBR stat.
30 Control bus operation failed while attempting to get the response from the file system for CB_TYPE_FSPL command.
3A Control bus operation failed while attempting to get the response from the file system for CB_TYPE_FWPB command.
3B Control bus operation error logged in the response from the file sys-tem for CB_TYPE_FWPBR stat.
3C Control bus operation error logged in the completion response from the file system for CB_TYPE_FWPBC stat.
A6 Control bus operation failed while attempting to get the response from the file system for CB_TYPE_FSGUC command.
B6 Control bus operation error logged in the response from the file sys-tem for CB_TYPE_FSGUCR stat.
CSEBP EIP
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010*
*Subcodes 18-B6 have CB in offset 09.It stands for Control Bus; ignore it.
212 STATUS LOG
STATUS CODES DB
Entry headerRegistersduring event
DB General File System Data Bus Status Log
01 Failed to write a track to the file system during the creation of a data directory.
02 Failed to read a track from the file system during the creation of a data directory.
03 Failed to read a track from the file system during a directory check.
04 Failed to write first directory track to the file system during directory revision setup.
05 Failed to write first directory track to the file system during directory revision setup.
06 Failed to write first directory track to the file system during a directory update or update check.
07 Failed to write first directory track to the file system during a directory update or update check.
CSEBP EIP
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010
STATUS LOG 213
STATUS CODESDC
Entry header
Entry header
Entry headerRegistersduring event
DC General Directory-Related Error
01 SST/data directory mismatch.
02 Directory internal error.
03 Directory internal error.
04 Internal damage to CP while processing directory algorithms.
05 Damage to internal (in-RAM) data tables used for directory process-ing was detected.
06 Negative or no confirmation to the request for an upgrade to the new directory and AMT.
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050 50515253 54555657 58595A5B 5C5D5E5F
00060 60616263 64656667 68696A6B 6C6D6E6F
00070 70717273 74757677 78797A7B 7C7D7E7F
00080 80818283 84858687 88898A8B 8C8D8E8F
00090 90919293 94959697 98999A9B 9C9D9E9F
000A0 A0A1A2A3 A4A5A6A7 A8A9AAAB ACADAEAF
000B0 B0B1B2B3 B4B5B6B7 B8B9BABB BCBDBEBF
000C0 C0C1C2C3 C4C5C6C7 C8C9CACB CCCDCECF
000D0 D0D1D2D3 D4D5D6D7
Track buffercontents
00020 20212223 24252627 28292A2B 2C2D2E2F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
Directory entry(first part)
CSEBP EIP
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010
214 STATUS LOG
STATUS CODES DC
Registersduring event
Entry header
Entry header
Registersduring event
07 Damaged directory. Directory entry bitmap/filemarker bitmap mis-match.
08 Bad filemarker checksum detected at beginning of track before write operation.
09 Bad filemarker checksum detected at beginning of track after read operation.
0A Bad file type detected in filemarker of a directory track before write operation.
0B Bad file type detected in filemarker of a directory track after read operation.
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
Task ID
00020
00000 00010203 04050607 08090A0B 0C0D0E0F
00010
00030
00040
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0*Unused
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050 50515253 54555657 58595A5B 5C5DEBP EIP CS
Blocknumber
Track number
Filemarker
STATUS LOG 215
STATUS CODESDC
Entry header
Registersduring event(EIP is inoffset EE-F1)
Entry header(repeated)
Super field size
0C Bad checksum for directory entry detected before write operation.
0D Bad checksum for directory entry detected after read operation.
0E Damaged directory node detected before write operation.
0F Damaged directory node detected after read operation.
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050 50515253 54555657 58595A5B 5C5D5E5F
00060 60616263 64656667 68696A6B 6C6D6E6F
00070 70717273 74757677 78797A7B 7C7D7E7F
00080 80818283 84858687 88898A8B 8C8D8E8F
00090 90919293 94959697 98999A9B 9C9D9E9F
000A0 A0A1A2A3 A4A5A6A7 A8A9AAAB ACADAEAF
000B0 B0B1B2B3 B4B5B6B7 B8B9BABB BCBDBEBF
000C0 C0C1C2C3 C4C5C6C7 C8C9CACB CCCDCECF
000D0 D0D1D2D3 D4D5D6D7 D8D9DADB DCDDDEDF
000E0 E0E1E2E3 E4E5E6E7 E8E9
000F0
Directory entrynumber
Track number
…EIPEBP
CSEIP…
00020
00000 00010203 04050607 08090A0B 0C0D0E0F
00010
00030 30313233 34353637 38393A3B 3C3D3E3F
Directory entry(second part)
Record sizeSuper record size
SECOND ENTRY
WHOLE “ENTRY” USES TWO STATUS LOG ENTRIES
FIRST ENTRY
Directory entry(first part)
216 STATUS LOG
STATUS CODES DC
Entry header
Registersduring event
10 Bad checksum detected on filemarker (not first filemarker in track) before write operation.
11 Bad checksum detected on filemarker (not first filemarker in track) after read operation.
12 Bad block links detected in filemarker before write operation.
13 Bad block links detected in filemarker after read operation.
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050 50515253 54555657 58595A5B 5C5DEBP EIP CS
Blocknumber
Track number
Filemarker
STATUS LOG 217
STATUS CODESDC
Entry header
Registersduring event(EIP is inoffset EE-F1)
Entry header(repeated)
Super field size
14 Damaged update record in directory track 1 detected during power-up.
15 Damaged update record in directory track 2 detected during power-up.
16 Failed in putting a request for file services on the queue. The queue should be deep enough to hold all possible requests.
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050 50515253 54555657 58595A5B 5C5D5E5F
00060 60616263 64656667 68696A6B 6C6D6E6F
00070 70717273 74757677 78797A7B 7C7D7E7F
00080 80818283 84858687 88898A8B 8C8D8E8F
00090 90919293 94959697 98999A9B 9C9D9E9F
000A0 A0A1A2A3 A4A5A6A7 A8A9AAAB ACADAEAF
000B0 B0B1B2B3 B4B5B6B7 B8B9BABB BCBDBEBF
000C0 C0C1C2C3 C4C5C6C7 C8C9CACB CCCDCECF
000D0 D0D1D2D3 D4D5D6D7 D8D9DADB DCDDDEDF
000E0 E0E1E2E3 E4E5E6E7 E8E9
000F0
Directory entrynumber
Track number
…EIPEBP
CSEIP…
00020
00000 00010203 04050607 08090A0B 0C0D0E0F
00010
00030 30313233 34353637 38393A3B 3C3D3E3F
Directory entry(second part)
Record sizeSuper record size
SECOND ENTRY
WHOLE “ENTRY” USES TWO STATUS LOG ENTRIES
FIRST ENTRY
Directory entry(first part)
218 STATUS LOG
STATUS CODES DD
Entry header
Registersduring event
Entry header
IORB header
CB-out messageCB-in messageRegistersduring event
DD Failed to Read User Record from Disk
17 Too many bad user records on disk.
1A Bad IUN for user record.
1D Failed to read user record.
Task ID
00020 2021
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
CSEBP EIP EBP EIP
Caller’smodule
Systemmodule
CSEBP EIP EBP EIP
00020 20212223 24252627 28292A2B 2C2D2E2F
Task IDPeripheraladdress
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
CB task ID
Control busmessage types
Caller’smodule
Systemmodule
STATUS LOG 219
STATUS CODESDE
Entry header
Registersduring event
Entry header
IORB header
CB-out messageCB-in messageRegistersduring event
DE Failed to Read Company Record From Disk
1B Bad internal company record for company record read.
1C Failed to read company record from disk.
Task ID
00020 2021
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
CSEBP EIP EBP EIP
Caller’smodule
Systemmodule
CSEBP EIP EBP EIP
00020 20212223 24252627 28292A2B 2C2D2E2F
Task IDPeripheraladdress
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
CB task ID
Control busmessage types
Caller’smodule
Systemmodule
220 STATUS LOG
STATUS CODES DF
Entry header
Registersduring event
Entry header
IORB header
CB-out messageCB-in messageRegistersduring event
DF Failed to Write User Record to Disk
1A Bad IUN for user record write.
1E Failed to write user record to disk.
Task ID
00020 2021
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
CSEBP EIP EBP EIP
Caller’smodule
Systemmodule
CSEBP EIP EBP EIP
00020 20212223 24252627 28292A2B 2C2D2E2F
Task IDPeripheraladdress
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
CB task ID
Control busmessage types
Caller’smodule
Systemmodule
STATUS LOG 221
STATUS CODESE0
Entry headerRegistersduring event
Entry header
Entry headerRegistersduring event
000000
E0 System Error
01 Stack expanded over threshold limit.
02 Stack overflow. Format varies and includes register information.
08 System failed to allocate event during Root Task start-up at system initialization.
09 File system 0 not found during Root Task start-up sequence.
0A Failed to allocate queue during Root Task start-up sequence. Dumps the system.
0C System failed to create queue during start-up of user support module in system partition.
10 System failed to allocate enough RAM for file/directory management during system start-up.
CSEBP EIP
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
…
CSEBP EIP
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010
222 STATUS LOG
STATUS CODES E0
Entry headerRegistersduring event
20 System could not create a task because that task was reported to be already active.
21 System could not create a task because the system is out of resources.
22 System could not create task because of an invalid creation request or parameter.
23 System could not create task because OS returned an unknown return code.
24 Could not get dial tone for batch network outcalling.
25 SST level higher than the software can recognize.
26 Number of bad user records is over the threshold (PT and LT are dis-abled).
27 CC not found during Root Task start-up sequence. Dumps the sys-tem.
28 Failed to perform SMT garbage collect.
00010 10111213 14151617 18191A1B 1C1D1E1F
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00020EBP EIP CS
Task definition block…
STATUS LOG 223
STATUS CODESE1
Entry headerRegistersduring event
E1 Failed to Start Application, Application Not Found, Partition Header Damaged or Cold Start Not Available
01 System failed to start AC partition.
02 System failed to start SMT partition.
03 System failed to start X.25 partition.
04 System failed to start OCL partition.
05 System failed to start ASA partition.
06 System failed to start IMS A->H partition.
07 System failed to start IMS H->A partition.
08 System failed to start OET partition.
09 System failed to start CST partition.
CSEBP EIP
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010
224 STATUS LOG
STATUS CODES E2
Entry headerRegistersduring event
Entry headerRegistersduring event
E2 AMT Error
Address Mapping Table error. Possible bad memory.
01 Bad address calculated when attempting to reference AMT entry in memory.
02 Bad index received by AMT in-RAM access routine.
03 Corrupted AMT in-RAM data tables.
04 System failed to read an AMT record.
05 System failed to write an AMT record.
06 System failed to create event for AMT during system start-up.
07 System failed to open the AMT file.
08 System detected damaged AMT super record while attempting power-fail recovery check.
09 A duplicate AMT entry found while building in-RAM tables.
0A System failed to create a file for AMT during initial build.
0B Cannot downrev the AMT.
0C Unable to obtain file status for AMT while attempting to expand AMT’s size.
0D System detected damaged AMT super record while attempting to expand AMT.
0E Digit count in AMT entry exceeds AMT_MAX_DIGITS.
0F Returned error status from sys_nc_amt_lin_ser.
CSEBP EIP
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1BEBP EIP CS
Bad status
STATUS LOG 225
STATUS CODESE2
Entry headerRegistersduring event
Entry headerRegistersduring event
Entry headerRegistersduring event
Entry headerRegistersduring event
10 Bad return code in second control bus message.
11 Undefined status returned by AP for linear search.
12 Returned error status from sys_nc_amt_lin_ser.
13 Bad return code in second control bus message.
14 Undefined status returned by AP for linear search.
15 Returned error status from sys_nc_amt_lin_ser.
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191AEBP EIP CS
Bad status
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1BEBP EIP CS
Bad status
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191AEBP EIP CS
Bad status
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1BEBP EIP CS
Bad status
226 STATUS LOG
STATUS CODES E2
Entry headerRegistersduring event
Entry headerRegistersduring event
Entry headerRegistersduring event
Entry headerRegistersduring event
16 Bad return code in second control bus message.
17 Undefined status returned by AP for linear search.
18 Returned error status from sys_nc_amt_lin_ser.
19 Bad return code in second control bus message.
1A Undefined status returned by AP for linear search.
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191AEBP EIP CS
Bad status
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1BEBP EIP CS
Bad status
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191AEBP EIP CS
Bad status
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1BEBP EIP CS
Bad status
STATUS LOG 227
STATUS CODESE2
Entry headerRegistersduring event
Entry headerRegistersduring event
Entry headerRegistersduring event
Entry headerRegistersduring event
1B Returned error status from sys_nc_amt_dbn_search.
1C Bad return code.
1D Undefined status returned by AP for ADD.
1E Undefined status returned by AP for REM.
20 Undefined status returned by AP for sys_amt_addr_to_int.
22 Undefined status returned by AP for sys_amt_addr_seek.
23 Returned error status from sys_nc_irn_to_addr.
CSEBP EIP
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191AEBP EIP CS
Bad status
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1BEBP EIP CS
Bad status
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191AEBP EIP CS
Bad status
228 STATUS LOG
STATUS CODES E2
Entry headerRegistersduring event
Entry headerRegistersduring event
Entry headerRegistersduring event
Entry headerRegistersduring event
24 Returned error status from sys_nc_amt_lin_ser.
25 Bad return code in second control bus message.
26 Undefined status returned by AP for sys_nc_amt_lin_ser.
27 Returned error status from sys_nc_amt_dbn_search.
28 Undefined status returned by AP at sys_nc_amt_dbn_search.
29 Returned error status from sys_nc_amt_den_search.
2A Undefined status returned by AP at sys_nc_amt_dbn_search.
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1BEBP EIP CS
Bad status
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191AEBP EIP CS
Bad status
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1BEBP EIP CS
Bad status
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191AEBP EIP CS
Bad status
STATUS LOG 229
STATUS CODESE2
Entry headerRegistersduring event
Entry headerRegistersduring event
Entry headerRegistersduring event
Entry headerRegistersduring event
2B Returned error status from sys_nc_amt_lin_ser.
2C Bad return code in second control bus message.
2D Undefined status returned by AP for linear search.
2E Returned error status from sys_nc_amt_lin_ser.
2F Bad return code in second control bus message.
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1BEBP EIP CS
Bad status
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191AEBP EIP CS
Bad status
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1BEBP EIP CS
Bad status
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191AEBP EIP CS
Bad status
230 STATUS LOG
STATUS CODES E2
Entry headerRegistersduring event
Entry headerRegistersduring event
Registersduring event
Entry header
30 Undefined status returned by AP for linear search.
31 Undefined status returned by AP for binary search.
32 AMT is full.
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1BEBP EIP CS
Bad status
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191AEBP EIP CS
Bad status
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
Task ID
00020
00000 00010203 04050607 08090A0B 0C0D0E0F
00010
00030
00040
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0*Unused
STATUS LOG 231
STATUS CODESE2
Entry headerRegistersduring event
Entry headerRegistersduring event
Entry headerRegistersduring event
Entry headerRegistersduring event
33 Returned error status from sys_nc_amt_lin_ser.
34 Bad return code in second control bus message.
35 Undefined status returned by AP for linear search.
38 Error returned from os_malloc. Tried to allocate a temporary buffer for reading an AMT file for a PMOS upgrade.
39 Error returned from os_free. Tried to free a temporary buffer for read-ing an AMT file for a PMOS upgrade.
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1BEBP EIP CS
Bad status
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191AEBP EIP CS
Bad status
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1BEBP EIP CS
Bad status
CSEBP EIP
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010
232 STATUS LOG
STATUS CODES E2
Registersduring event
Entry header
Entry header
Registersduring event
d word
AMT entry
(EBP is inoffset 1E-21)
40 AMT on CC is full.
41 AMT on CC duplicate name.
42 AMT on CC entry not found.
43 AMT on CC is empty.
45 CC update ADD error.
46 Cannot delete entry on CC. The CC may have a problem.
47 Local AMT is full.
48 Local AMT, duplicate name.
49 Local AMT, delete bad IRN in entry. The IRN in the entry did not match the input prm to the routine.
4A Local AMT, delete bad digit count in entry. The number of digits in the entry key and the total number of digits in the entry did not match the number of additional digits in the input prm to the routine.
4B Local AMT, name not found.
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
Task ID
00020
00000 00010203 04050607 08090A0B 0C0D0E0F
00010
00030
00040
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0*Unused
Task ID
00020 20212223 24252627
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1FEBP……EBP EIP CS
Entry key IRN
Entry type
Number ofdigits in key
Used define
STATUS LOG 233
STATUS CODESE2
Entry headerRegistersduring event
80 Bad data for amt_insert.
81 Invalid AMT entry type.
82 AMT is full.
CSEBP EIP
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010
234 STATUS LOG
STATUS CODES E3
Entry header
IORB header
CB-out messageCB-in message
Registersduring event
E3 Phrase Concatenation Library Failure
01 Error on FLPR.
02 Error on FLPR—phrase not there.
03 Error on FLPR—phrase overflow
04 Error on FRPBR .
05 DMA set-up error (FS->CP).
06 DMA set-up error (CP->FS).
07 Error on FWMBR.
08 Error on FWMBR—disk full.
09 Error on FWMBC—protocol error.
0A Error on FWMBC.
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
00070 70717273 74757677
00080
Peripheraladdress
CB task ID
Control busmessage types
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS EBP EIPCS
Unused
STATUS LOG 235
STATUS CODESE4
Entry headerRegistersduring event
E4 ASA SP Routine General Error
The use of offsets 10-11 and 12-13 varies with the subcode.
01 User record not active when reading.
Offset 10-11: IUN of the user record.Offset 12-13: unused.
02 User record validity check error when reading.
Offset 10-11: IUN of the user record.Offset 12-13: validity check error number.
03 IUN out of range when reading.
Offset 10-11: IUN of the user record.Offset 12-13: unused.
04 User record validity check error when writing.
Offset 10-11: IUN of the user record.Offset 12-13: validity check error number.
05 User record lock fails.
Offset 10-11: IUN of the user record.Offset 12-13: unused.
06 IUN out of range when locking.
Offset 10-11: IUN of the user record.Offset 12-13: unused.
07 System group number out of range when reading.
Offset 10-11: system group number.Offset 12-13: unused.
08 System group number out of range when writing.
Offset 10-11: system group number.Offset 12-13: unused.
09 ICN out of range when company reading.
Offset 10-11: ICN.Offset 12-13: unused.
0A Company validity check error when company writing.
Offset 10-11: ICN.Offset 12-13: unused.
0B No event. Offset 10-13: unused.
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1DEBP EIP CS
Validity check error number(subcodes 02 and 04 only)
Data (dependson subcode)
236 STATUS LOG
STATUS CODES E4
Entry headerRegistersduring event
Entry header
Registersduring event
0C No IORB. Offset 10-13: unused.
0D Fail on waiting the critical region event. Offset 10-13: unused.
0E Name table is full. Offset 10-13: unused.
0F System is full and cannot add mailboxes. Offset 10-13: unused.
10 Abandon user record failed.Offset 10-11: IUN of the user record.Offset 12-13: unused.
11 Attendant schedule number out of range.Offset 10-11: Attendant schedule number.Offset 12-13: unused.
16 Error detected by priority queueOffset 10-11: IUN of the user record.Offset 12-13: unused.
17 Failed to remove an entry from the AMT.
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1DEBP EIP CS
Validity check error number(subcodes 02 and 04 only)
Data (dependson subcode)
00010 10111213 14151617 18191A1B 1C1D1E1F00020 20212223 24252627 28292A2B 2C
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
CSEIPEBP
Digit string of the failed entry
STATUS LOG 237
STATUS CODESE5
Entry header
IORB header
CB-out messageCB-in message
Registersduring event
E5 ASA SP Routine I/O Error
40 Control bus operation return code bad. The system dumped.
41 Bad return code for control bus message. The return code is in the IORB buffer.
42 I/O critical region was blocked for too long.
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0
Peripheraladdress
CB task ID
Control busmessage types
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
*Unused
238 STATUS LOG
STATUS CODES E6
Entry header
IORB header
CB-out messageCB-in message
Registersduring event
E6 Line Card Control Bus Error
01 Return code bad or unknown.
02 Failed with line card message 85, Receive Speech.
03 Failed with line card message 83, Read Speech Buffer Response.
04 Failed with line card message 84, Read Speech Buffer Done.
05 Failed with line card message 86, Write Speech Buffer Response.
06 Failed with line card message 87, Write Speech Buffer Done.
07 Failed with line card message 94, Transmit Speech End.
08 Failed with line card message 0x0A9, Read Fax Buffer Response.
09 Failed with line card message 0x0AB, LC Fax ID.
0A Failed with line card message 0x0AA, LC Read Fax Cover Sheet Done.
0B Failed with line card message 0x094, Transmit Speech End.
0C Failed with line card message 0x097, Receive Speech End.
0D Failed with line card message 0x0DF, Message Interrupt.
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0
Peripheraladdress
CB task ID
Control busmessage types
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
*Unused
STATUS LOG 239
STATUS CODESE7
Entry header
IORB header
CB-out messageCB-in message
Registersduring event
E7 Line Card Message Contains Unexpected Value
01 Bad return code in line card message 97, Receive Speech End.
02 Unexpected retry reported in line card message 92, Read Speech Buffer.
03 Bad return code in line card message 94, Transmit Speech End.
04 Damaged message reported in line card message 94, Transmit Speech End.
05 Message canceled reported in line card message 94, Transmit Speech End.
06 Flag error in line card message 92, Read Speech Buffer.
07 Invalid speech type reported in line card message 94, Transmit Speech End.
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0
Peripheraladdress
CB task ID
Control busmessage types
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
*Unused
240 STATUS LOG
STATUS CODES E8
Entry header
IORB header
CB-out messageCB-in message
Registersduring event
E8 CP/LC Protocol (Low-Level) Error
01 OS reported one or more lost control bus messages when attempting to read messages from a line card.
02 OS reported control bus operation cancelled when attempting to read control bus messages from a line card.
03 OS reported control bus operation cancelled when attempting to read control bus messages from a line card.
04 OS reported one or more lost control bus messages when attempting to read, then write, messages with a line card.
05 OS reported control bus operation cancelled when attempting to read, then write, control bus messages with a line card.
06 OS reported control bus operation cancelled when attempting to read, then write, control bus messages with a line card.
07 CB response indicates zero pages counted in fax record.
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0
Peripheraladdress
CB task ID
Control busmessage types
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
*Unused
STATUS LOG 241
STATUS CODESE9
Entry header
IORB header
CB-out messageCB-in message
Registersduring event
E9 Line Card Failed to Respond Within Time-out Period
01 Time-out when attempting to send, then read, control bus messages with a line card. Time-out value is SYS_TIMEOUT_LC.
02 Time-out when attempting send, then read, control bus messages with a line card. Time-out value is user-defined.
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0
Peripheraladdress
CB task ID
Control busmessage types
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
*Unused
242 STATUS LOG
STATUS CODES EA
Entry header
IORB header
CB-out messageCB-in message
Registersduring event
EA Line Card Data Bus Error
01 Data bus operation with a line card failed. Maximum number of retries has occurred.
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0
Peripheraladdress
CB task ID
Control busmessage types
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
*Unused
STATUS LOG 243
STATUS CODESEB
Registersduring event
Entry header
EB Message Library Failure
01 Message record library error—unexpected state.
02 Message open library error—message ID is out of range.
03 Decrement use count.
04 Play message.
05 Record message.
06 Save message.
07 Open message.
08 Initialize message.
09 Abandon message.
0A Close message.
0B Increment use count.
0C Send message.
0D Wrong state.
0E Send destination.
0F Fax record message.
10 Fax transmit.
11 Message close library error: Message never opened.
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
Task ID
00020
00000 00010203 04050607 08090A0B 0C0D0E0F
00010
00030
00040
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0*Unused
244 STATUS LOG
STATUS CODES EC
Registersduring event
Entry header
EC IVR Message Directory Error
01 Delete message.
02 Read message.
03 Write message.
04 Failed to create event semaphore for IMD.
05 Failed to create IMD file.
06 Failed to open IMD file.
07 Failed to read IMD file.
08 Failed on write to IMD file.
09 Illegal operation attempted.
0A Conflict on bitmap write table.
0B Bad return code while trying to determine file status.
0C Not enough memory for IMD data area.
0D Not enough memory for “old” IMD directory.
0E Creation of the IVRMD file.
10 Creation of the IVRMD file.
11 Unsuccessful return code from MDS file_create.
12 Unsuccessful return code from MDS get_usr_data.
13 Unsuccessful return code from MDS upd_usr_data.
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
Task ID
00020
00000 00010203 04050607 08090A0B 0C0D0E0F
00010
00030
00040
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0*Unused
STATUS LOG 245
STATUS CODESEC
Registersduring event
Entry header
14 Unsuccessful return code from MDS get_direct.
15 Unsuccessful return code from MDS write_entry.
16 Unsuccessful return code from MDS update_entry.
17 Unsuccessful return code from MDS del_entry.
18 Unsuccessful return code from MDS scan_entry.
19 Unsuccessful return code from MDS entries full.
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
Task ID
00020
00000 00010203 04050607 08090A0B 0C0D0E0F
00010
00030
00040
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0*Unused
246 STATUS LOG
STATUS CODES ED
Registersduring event
Entry header
ED Phrase Library Error
00 Phrase library error.
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
Task ID
00020
00000 00010203 04050607 08090A0B 0C0D0E0F
00010
00030
00040
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0*Unused
STATUS LOG 247
STATUS CODESEE
Registersduring event
Entry header
EE Mailbox Library Error
01 Mailbox library failure.
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
Task ID
00020
00000 00010203 04050607 08090A0B 0C0D0E0F
00010
00030
00040
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0*Unused
248 STATUS LOG
STATUS CODES EF
Registersduring event
Entry header
EF Name Announcement Library Error
01 Get name announcement message ID/SC pointers.
02 Unknown name announcement destination code.
03 Error from decrement use count.
04 Unknown return code from delete.
05 Error from increment use count.
06 Internal error.
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
Task ID
00020
00000 00010203 04050607 08090A0B 0C0D0E0F
00010
00030
00040
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0*Unused
STATUS LOG 249
STATUS CODESF0
Registersduring event
Entry header
F0 System Name Annoucement Library Failure
01 Get name announcement message ID/SC pointers.
02 Error return from decrement use count.
03 Unknown return from delete.
04 Error return from increment use count.
05 Error writing SST to disk.
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
Task ID
00020
00000 00010203 04050607 08090A0B 0C0D0E0F
00010
00030
00040
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0*Unused
250 STATUS LOG
STATUS CODES F1
Registersduring event
Entry header
F1 System MID Library Failure
01 Bad return code from rd_ur_and_find_mid.
02 Bad msg_type field detected in MID.
03 Bad return code from ac_nanlb_nan_get.
04 Bad return code from ac_snanlb_snan_get.
05 Bad return code from sys_ent_imd_read
06 Bad entry_type detected in MID.
07 Bad msgid in MID.
08 Unexpected return code from ac_msglb_open.
09 Bad return code from ac_msglb_open.
0A Bad return code from ac_msglb_msg_search.
0B Bad return code from ac_midlb_get_next_md_cmpnt.
0C Bad return code from ac_midlb_md2active_seg.
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
Task ID
00020
00000 00010203 04050607 08090A0B 0C0D0E0F
00010
00030
00040
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0*Unused
STATUS LOG 251
STATUS CODESF2
Registersduring event
Entry header
F2 System MIDG Library Failure
01 Unexpected return code from library routine.
02 Bad entry_type field detected in MID.
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
Task ID
00020
00000 00010203 04050607 08090A0B 0C0D0E0F
00010
00030
00040
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0*Unused
252 STATUS LOG
STATUS CODES F5
Entry header
Registersduring event
Entry header
Registersduring event
F4 Bad AMIS Message Array Found or Software Error
60 Failed to open AEAR file.
61 Failed to create a file for the AEAR.
62 Message not found.
63 Failed to read AEAR file.
64 Failed to create an event.
F5 Failed to Write AMIS Message Array Back to Disk
Note that offset 08-09 holds a track number, not a subcode.
Task ID
00020 2021
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
CSEBP EIP EBP EIP
Caller’smodule
Systemmodule
Task ID
00020 2021
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
CSEBP EIP EBP EIP
Track number
Caller’smodule
Systemmodule
STATUS LOG 253
STATUS CODESF6
Entry header
Registersduring event
Entry header
Registersduring event
F6 Bad AMIS Dialing Sequence Table Found or Software Error
65 Failed to open ADST file.
66 Failed to create a file for the ADST.
67 Failed to read ADST file.
68 Failed to create an event.
F7 Failed to Write AMIS Dialing Sequence Table Back to Disk
Note that offset 08-09 holds a track number, not a subcode.
Task ID
00020 2021
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
CSEBP EIP EBP EIP
Caller’smodule
Systemmodule
Task ID
00020 2021
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
CSEBP EIP EBP EIP
Track number
Caller’smodule
Systemmodule
254 STATUS LOG
STATUS CODES F8
Entry header
IORB header
CB-out messageCB-in message
Registersduring event
F8 SP AMIS I/O Error
69 Control bus operation return code bad. System dumped.
6A Control bus message return code bad. The return code is in the IORB buffer.
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0
Peripheraladdress
CB task ID
Control busmessage types
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
*Unused
STATUS LOG 255
STATUS CODESF9
Entry header
IORB header
CB-out messageCB-in message
Registersduring event
F9 Integration General Error
01 Error reported by DLC.
02 Unrecognized response from DLC.
03 Wrong incoming message.
04 Bad digit in ACP message.
05 Error code in IORB from OS.
06 Unexpected message received.
07 Bad return from ACIO.
08 No dial tone detected for PID/R.
09 Time-out waiting for response.
0A Continuous incoming message.
0B Incoming queue overflow.
0C Too many digits in dial request.
0D Non-zero return code in CIP message.
0E Incoming integration message on port marked “NO” for incoming calls in Menu 4.
0F Incoming integration message on non-integrated port (non-integrated line type).
10 Bad return from line card.
11 Error writing to line card.
12 APID 85 failed to send incoming call after sending alerting message.
13 APID 85 message waiting queue failure.
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
00070 70717273 74757677
00080
Peripheraladdress
CB task ID
Control busmessage types
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS EBP EIPCS
Unused
256 STATUS LOG
STATUS CODES F9
Entry headerRegistersduring event
Entry header
IORB header
CB-out messageCB-in message
Registersduring event
Entry headerRegistersduring event
14 Failed to get inband dial tone.
15 Wrong response to configuration message.
16 Unrecognizable response to configuration message.
17 Error returned from DLC for special on-hook.
18 Error returned from DLC for special off-hook.
19 Unrecognized return from special on-hook.
1A Unrecognized return from special off-hook.
1B No buffer available.
1C Seize line failed.
1D Time-out collecting inband digit.
1E Invalid digit count for inband digits.
1F Invalid return from digit collect.
20 Error collecting inband digits.
21 Failed message waiting retry.
22 Message waiting resumes operational.
00010 10111213 14151617 18191A1B 1C00020
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
CSEIP
Mailbox number
Extension number...EBP
EBP...Retry count
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
00070 70717273 74757677
00080
Peripheraladdress
CB task ID
Control busmessage types
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS EBP EIPCS
Unused
00010 10111213 14151617 18191A1B 1C00020
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
CSEIP
Mailbox number
Extension number...EBP
EBP...Retry count
STATUS LOG 257
STATUS CODESF9
11 (Report ID):
port ID):
Entry headerRegistersduring event
Entry header
Registersduring event
...
23 Maximum error retry count reached.
24 VTIC/MTIC report error.
25 VTIC/MTIC line status change.
Offset Label Description
10 Report type 01 = Line Status Report. Meaning of value at offset
00 Link/line idle/up/connected.01 Link/line make set busy (MSB—NT only).02 Link/line disable/down/disconnected.03 Link/line not ready (NRDY—NT only).
02 = Error Report. Meaning of value at offset 11 (Re
00 Protocol converter error report.01 Link processor error report.02 MITIC error report.03 DLC error report.
0001000020
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
CSEIPEBPMailbox Extension IUN
00020 2021 00010 10111213 14151617 1819
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
CSEBP
...EIP
Report type
Report ID
Data
EIP
258 STATUS LOG
STATUS CODES F9
Entry header
IORB header
CB-out messageCB-in message
Registersduring event
Entry headerRegistersduring event
Entry header
IORB header
CB-out messageCB-in message
Registersduring event
26 Timed-out waiting for onhook.
27 Invalid extension for transfer.
28 Port login/logout to PBX failed.
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
00070 70717273 74757677
00080
Peripheraladdress
CB task ID
Control busmessage types
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS EBP EIPCS
Unused
00020
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
CSEIPEBP
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
00070 70717273 74757677
00080
Peripheraladdress
CB task ID
Control busmessage types
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS EBP EIPCS
Unused
STATUS LOG 259
STATUS CODESF9
Registersduring event
Entry header
Entry header
IORB header
CB-out messageCB-in message
Registersduring event
29 Invalid link number for DMID.
30 Error code in INT response.
31 ACP card time-out.
32 Unexpected message.
51 Length of variable error.
60 Unexpected integration message.
61 Time-out waiting for poll response.
62 Unknown return code from ACIO routine.
63 Continuous incoming message.
64 Operating system error.
65 Integration status message.
66 Error code in INT response message.
67 Queue overflow.
68 Line status error from MID.
69 Line disabled by MID.
EBP EIP CS
Task ID
00020
00010
00030
00040
00050
00060
00070
00080
00090
00000 00010203 04050607 08090A0B 0C0D0E0F
Trace bufferTrace bufferTrace bufferTrace bufferTrace bufferTrace bufferTrace bufferTrace buffer
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
00070 70717273 74757677
00080
Peripheraladdress
CB task ID
Control busmessage types
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS EBP EIPCS
Unused
260 STATUS LOG
STATUS CODES F9
Entry headerRegistersduring event
Entry header
IORB header
CB-out messageCB-in message
Registersduring event
6A Link number in user record does not exist. Invalid SMDI port number for mailbox.
6B Stack error. The primary, secondary or active stack does not match the primary, secondary or active stack in the system partition.
90 Invalid link number passed to SP.
91 Invalid serial port number passed to SP.
92 ACP board is not responding.
93 Illegal request.
94 Error creating integration file.
95 Error in integration file status.
96 Error creating event for port request.
97 Unknown table operation type.
98 Error creating an event for SS7 buffer locking.
99 Error creating MDS record.
9A Error getting user data from MDS record.
9B Reading or writing non-existent MDS record.
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14 EBP EIP CS
Mailbox number,padded with F
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
00070 70717273 74757677
00080
Peripheraladdress
CB task ID
Control busmessage types
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS EBP EIPCS
Unused
STATUS LOG 261
STATUS CODESF9
Entry header
IORB header
CB-out messageCB-in message
Registersduring event
C0 Abort signaled from OS.
C1 Invalid return code from SP.
C2 Bad return code from OS.
D0 Cannot create an event.
D1 Cannot create timer.
D2 Cannot start timer.
D3 Failed to send batched messages.
D4 Failed to get buffers from OS.
D5 Error setting task ID.
D6 Unexpected return in IORB status word.
D7 Error stopping timer.
D8 Error in return from multiple wait.
D9 Invalid message waiting queue length.
DA Invalid serial port message from OS driver.
DB Invalid CIP message received from another task.
DC Invalid port ID received from PIDR.
DD Control bus response message with wrong message type or the return code was not OK.
DE Length for DMA from cluster card to local segment is too big.
DF DMA failure.
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
00070 70717273 74757677
00080
Peripheraladdress
CB task ID
Control busmessage types
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS EBP EIPCS
Unused
262 STATUS LOG
STATUS CODES F9
Entry header
IORB header
CB-out messageCB-in message
Registersduring event
E0 A CIP message for the local station was sent to the wrong station.
E1 Exceeds maximum number of messages in the ACP buffer.
E2 Failed to pass an event to the OS. Return code not OK.
E3 Checksum mismatch on batch of CIP messages.
E4 Invalid station number received.
E5 Out-of-sequence buffer received.
E6 Time-out waiting for DMA request from receive task.
E7 Error on getting DMA buffer.
E8 Error reading MDS (PIC configuration) record.
E9 Time-out receiving message from cluster receive task.
EA Unrecognized return code from AC.
EB SS7 error during DMA to PIC.
EC Invalid peripheral address for PIC. The PIC is configured in software but no card is actually present.
ED DMA request queue overflow. DMA request lost.
EE Time-out waiting for response from PIC.
EF Error getting DMA request from queue.
F0 Error verifying lock on DMA buffer.
F1 The DMA length is greater than the DMA buffer or is zero.
F2 Not able to access PIC. Card dead.
F3 Invalid information in CIP message from PIC.
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
00070 70717273 74757677
00080
Peripheraladdress
CB task ID
Control busmessage types
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS EBP EIPCS
Unused
STATUS LOG 263
STATUS CODESF9
Entry header
IORB header
CB-out messageCB-in message
Registersduring event
Registersduring event
Entry header
F4 Invalid integration message.
There are 3 message formats: a 0x82 byte format, a 0x67 byte for-mat, and a variable length format.. Compare entry size to pick a for-mat.
0x82 Byte Format
0x67 Byte Format
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
00070 70717273 74757677
00080
Peripheraladdress
CB task ID
Control busmessage types
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS EBP EIPCS
Unused
Subcode = F4
00060 60616263 646566
00050 5D5E5F
Task ID
00020
00000 00010203 04050607 08090A0B 0C0D0E0F
00010
00030
EBP
Subcode = F4
EIP CS
Msg rec’d from/xmitted to OS/MID/DMID/SMDI
00040
264 STATUS LOG
STATUS CODES F9
Entry headerRegistersduring event
Entry header
IORB header
CB-out messageCB-in message
Registersduring event
Variable Length Format
F5 Serial port transmit error.
F6 Error queuing message for transmit.
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 1011... EBP EIP CS
Length of link message,in bytes
Link message,length varies
Subcode = F4
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
00070 70717273 74757677
00080
Peripheraladdress
CB task ID
Control busmessage types
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS EBP EIPCS
Unused
STATUS LOG 265
STATUS CODESFA
r are busy.r.
called first.
d.
Entry header
Registersduring event
FA IMS Error—Voice Processor-to-Host Task
11 Failure on ACL_INIT call.
12 Virtual circuit already open on ACL_OPEN call.
13 Failure on ACL_OPEN call.
14 Failure on ACL_READ call.
15 Failure on ACL_WRITE call.
19 Problem with user record update.
1A EAP requested update for non-host-to-voice processor user record.
1B Failure on PQ_INIT call.
Offset Label Field Description
10-11 Source file ID 01 IMS_FID_IMSIMAIN (imsimain.c)02 IMS_FID_IMSITBL (imsitbl.c)03 IMS_FID_IMSOMAIN (imsomain.c)04 IMS_FID_PQ (imsopq.c)
14-15 Data Usually an IUN if non-zero.
16-17 Return code Usually an OCL library return code:C2FF Operation aborted.C3FF Application number does not exist.
C4FF OCL is not up.C5FF OCL interface routine internal error.C6FF All LUNs for requested application numbeC7FF No LUNs for requested application numbe
C8FF Buffer overflow. LUN will be cleared.C9FF LUN cleared.CAFF Operation time-out. LUN will be cleared.CBFF LUN already open. ACL_CLOSE must be
CCFF ACL_INIT already performed.CDFF Successful ACL_OPEN call not performeCEFF ACL_INIT call not performed.
Task ID
00020 2021
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1FEBP EIPCS
Source file ID
Source fileline number
Return codeData (usuallyan IUN)
266 STATUS LOG
STATUS CODES FA
r are busy.r.
called first.
d.
Entry header
Registersduring event
1C Priority queue overflow.
1D Problem with priority queue receive.
1E Problem with IMS priority queue.
1F Problem with voice processor-to-host OCL command header.
20 Failure on UR lock.
22 Failure on UR write.
24 Problem with entry from queue.
25 Problem registering task with notify.
26 Problem monitoring service group.
27 Problem accepting service type.
Offset Label Field Description
10-11 Source file ID 01 IMS_FID_IMSIMAIN (imsimain.c)02 IMS_FID_IMSITBL (imsitbl.c)03 IMS_FID_IMSOMAIN (imsomain.c)04 IMS_FID_PQ (imsopq.c)
14-15 Data Usually an IUN if non-zero.
16-17 Return code Usually an OCL library return code:C2FF Operation aborted.C3FF Application number does not exist.
C4FF OCL is not up.C5FF OCL interface routine internal error.C6FF All LUNs for requested application numbeC7FF No LUNs for requested application numbe
C8FF Buffer overflow. LUN will be cleared.C9FF LUN cleared.CAFF Operation time-out. LUN will be cleared.CBFF LUN already open. ACL_CLOSE must be
CCFF ACL_INIT already performed.CDFF Successful ACL_OPEN call not performeCEFF ACL_INIT call not performed.
Task ID
00020 2021
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1FEBP EIPCS
Source file ID
Source fileline number
Return codeData (usuallyan IUN)
STATUS LOG 267
STATUS CODESFB
are busy..
alled first.
Entry header
Registersduring event
FB IMS Error—Host-to-Voice Processor Task
11 Failure on ACL_INIT call.
12 Virtual circuit already open on ACL_OPEN call.
13 Failure on ACL_OPEN call.
14 Failure on ACL_READ call.
15 Failure on ACL_WRITE call.
16 Problem with host-to-voice processor OCL command header.
17 Too many host-to-voice processor updates—exceeds maximum.
18 IUN out of range.
19 Problem with user record update.
Offset Label Field Description
10-11 Source file ID 01 IMS_FID_IMSIMAIN (imsimain.c)02 IMS_FID_IMSITBL (imsitbl.c)03 IMS_FID_IMSOMAIN (imsomain.c)04 IMS_FID_PQ (imsopq.c)
14-15 Data Usually an IUN if non-zero.
16-17 Return code Usually an OCL library return code:C2FF Operation aborted.C3FF Application number does not exist.
C4FF OCL is not up.C5FF OCL interface routine internal error.C6FF All LUNs for requested application number C7FF No LUNs for requested application number
C8FF Buffer overflow. LUN will be cleared.C9FF LUN cleared.CAFF Operation time-out. LUN will be cleared.CBFF LUN already open. ACL_CLOSE must be c
CCFF ACL_INIT already performed.CDFF Successful ACL_OPEN call not performed.CEFF ACL_INIT call not performed.
Task ID
00020 2021
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1FEBP EIPCS
Source file ID
Source fileline number
Return codeData (usuallyan IUN)
268 STATUS LOG
STATUS CODES FB
are busy..
alled first.
Entry header
Registersduring event
1A EAP requested update for non-host-to-voice processor user record.
1B Failure on PQ_INIT call.
1C Priority queue overflow.
1D Problem with priority queue receive.
20 Failure on UR lock.
21 Failure on UR read.
22 Failure on UR write.
23 Problem with message waiting evaluation.
Offset Label Field Description
10-11 Source file ID 01 IMS_FID_IMSIMAIN (CYP_ASP.C)02 IMS_FID_IMSITBL (IMSITBL.C)03 IMS_FID_IMSOMAIN (IMSOMAIN.C)04 IMS_FID_PQ (IMSIPQ.C)
14-15 Data Usually an IUN if non-zero.
16-17 Return code Usually an OCL library return code:C2FF Operation aborted.C3FF Application number does not exist.
C4FF OCL is not up.C5FF OCL interface routine internal error.C6FF All LUNs for requested application number C7FF No LUNs for requested application number
C8FF Buffer overflow. LUN will be cleared.C9FF LUN cleared.CAFF Operation time-out. LUN will be cleared.CBFF LUN already open. ACL_CLOSE must be c
CCFF ACL_INIT already performed.CDFF Successful ACL_OPEN call not performed.CEFF ACL_INIT call not performed.
Task ID
00020 2021
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1FEBP EIPCS
Source file ID
Source fileline number
Return codeData (usuallyan IUN)
STATUS LOG 269
STATUS CODESFC
Entry header
Registersduring event
10)
FC Error in Overflow Event Task
03 Unable to get background evaluation priority queue ID. Possible cod-ing error.
04 Unexpected result when getting IRN type. Possible coding error.
05 Write failed or returned an unexpected value. Possible bad value in the record, station in a cluster down, timing problem or coding error.
06 Read failed or returned an unexpected value. Possible bad value in the record, station in a cluster down, timing problem or coding error.
Offset Label Field Description
10-11 File File ID (from oetlog.h):01 oetmain.c02 oetmisc.c03 oetbg.c04 oetfut.c05 oeteval.c06 oetovfl.c07 oetlog.c
14-17 Serv. type Service type/limit (from sysnequ.inc):00 Octel integrated messaging01 Fax outcall02 Message waiting indication03 Normal mailbox outcall04 Pager outcall05 AspenNet outcall06 AMIS network outcall07 Transact (IVR) outcall
18-1B Serv. group
Service queue/group number.
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 3031
Source fileline number
CSEBP EIP
File Serv. type Serv. group
Return value(except subcode
IRN
Evaluation event
270 STATUS LOG
STATUS CODES FC
Entry header
10)
09 Attempt to add entry to queue failed
Offset Label Field Description
10-11 File File ID (from sysnottyp.h):01 notasm.c02 notglob.c03 notlock.c04 notpmap.c05 oetglob.c06 notconf.c07 notims.c08 notmisc.c09 notque.c0A oetmain.c0B noteval.c0C notinit.c0D notomap.c0E notstat.c0F notitbl.c11 sysntask.c12 sysntbl.c13 sysncb.c14 sysnckpt.c15 sysnserv.c16 sysnfut.c17 sysnovfl.c18 sysfaxq.c
14-17 Serv. type Service type/limit (from sysnequ.inc):00 Octel integrated messaging01 Fax outcall02 Message waiting indication03 Normal mailbox outcall04 Pager outcall05 AspenNet outcall06 AMIS network outcall07 Transact (IVR) outcall
Task ID
00020 20212223 24252627 28292A2B 2C2D
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
Source fileline number
File Serv. type IRN
Return value(except subcode
size = 0 CSEBP EIP
STATUS LOG 271
STATUS CODESFC
Entry header
Registersduring event
10)
Entry header
10)
Registersduring event
0D Error from CREATEVT.
0E Unable to get broadcast priority queue ID. Possible coding error.
0F Unexpected return code from WAITM call. Possible coding error.
10 Unknown queue entry type on the BG queue. Logged on first occur-rence and every fifth occurrence thereafter. Possible coding error or failure to recompile all of the notification subsystem.
Offset 1C-1F: queue type code that caused the error.
11 Unexpected return code from search of future evaluation table. Possi-ble coding error or the notification subsystem suspended operations.
12 Problem forcing time stamp onto future evaluation table. Possible coding error or a station is down in a cluster.
13 Evaluation call failed. Possible coding error.
14 Abandoned record failed or returned an unexpected value. Possible coding error or a station in a cluster is down.
15 Evaluation requested on an MDS record that is not the primary record. Possible coding error.
16 Problem getting the MDS record number. Possible coding error or timing problem (the file may have been deleted before the evaluation request was processed).
1C Error in MDS search function.
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 3031
Source fileline number
CSEBP EIP
File* Serv. type* Serv. group
Return value(except subcode
IRN
Evaluation event
* Refer to subcodes 01-06 for specific values
Task ID
00020 20212223 24252627 28292A2B 2C2D
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
Source fileline number
File* Serv. type* IRN
Return value(except subcode
size = 0 CSEBP EIP
* Refer to subcode 09 for specific values
272 STATUS LOG
STATUS CODES FD
ry space.
Entry headerRegistersduring event
FD File Access Error
01 File open error.
02 File close error.
03 File read error.
Offset Label Field Description
1A-1B Reason Reason for the error:FFFC File does not exist.FFFD Illegal request.FFFE For subcodes 01 and 02: directory fragmented.
For subcode 03: illegal request.FFFF For subcodes 01 and 02: not enough disk/directo
For subcode 03: insufficient buffer.
Task ID
00020 20212223 2425
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
EIP CSFile name EBP
Reason
STATUS LOG 273
STATUS CODES100
Registersduring event
Entry header
000000
100 CDR RAM Buffer Overflowed
Can be caused by tasks logging events faster than the purge task can writethem to disk. Possible solutions include decreasing the system load, afaster CPU and selecting fewer events for logging.
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
Task ID
00020
00000 00010203 04050607 08090A0B 0C0D0E0F
00010
00030
00040
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0*Unused
274 STATUS LOG
STATUS CODES 101
Entry header
IORB header
CB-out messageCB-in message
Registersduring event
101 CDR Disk Write Error
Can be caused by a drive write error when trying to write CDR informationfrom the RAM buffer to disk. Check the system drives.
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0
Peripheraladdress
CB task ID
Control busmessage types
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
*Unused
STATUS LOG 275
STATUS CODES102
Entry headerRegistersduring event
102 Short Message Service (SMS) Error
The following information applies to all the subcodes.
90 Relay layer open attempt failed.
91 Relay layer close attempt failed.
92 Relay layer read attempt failed.
A0 Register with Notification Subsystem failed.
A1 Notification Subsystem monitor request failed.
A2 Notification Subsystem acceptance request failed.
A3 Attempt to receive queue entry failed.
B0 Attempt to read SMS configuration file failed.
B1 Attempt to write SMS configuration file failed.
B2 Attempt to create SMS configuration file failed.
C0 Transport library received invalid subfunction code in CIP (compact interface protocol).
C1 Transport library received invalid function code in CIP (compact inter-face protocol).
Offset Label Field Description
10-11 Source file ID IMS file that logged the status entry:01 smsmain.c: start up and main loop.02 smsnotq.c: notification subsystem queue.03 syssmcfg.c: SMS configuration file handling.
14-15 Data value 1 Typically an IUN. Zero otherwise.
16-17 Data value 2 Typically a return code.
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
Data value 2
Data value 1
Source file ID
Source fileline number
00020 2021EBP EIP
CS
276 STATUS LOG
STATUS CODES 104
Registersduring event
Entry header
104 LAN Router Task Non-Service Errors
01 Read error.
02 Get QID from connection table.
03 Application priority queue send.
04 Add entry to router table.
05 Get QID from router table.
FF Halt the system.
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
Task ID
00020
00000 00010203 04050607 08090A0B 0C0D0E0F
00010
00030
00040
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0*Unused
STATUS LOG 277
STATUS CODES105
Registersduring event
Entry header
105 LAN Router Task Service Error
FF Halt the system.
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
Task ID
00020
00000 00010203 04050607 08090A0B 0C0D0E0F
00010
00030
00040
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0*Unused
278 STATUS LOG
STATUS CODES 106
Entry header
IORB header
CB-out messageCB-in message
Registersduring event
Registersduring event
Entry header
106 LAN API Error
01 Error from SR routine.
02 Protocol error.
03 Unable to get queue ID from LAN connection table.
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0
Peripheraladdress
CB task ID
Control busmessage types
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
*Unused
00000 00010203 04050607 08090A0B 0C0D0E0F
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
Task ID
00020
00000 00010203 04050607 08090A0B 0C0D0E0F
00010
00030
00040
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0*Unused
STATUS LOG 279
STATUS CODES106
Entry header
IORB header
CB-out messageCB-in message
Registersduring event
14 Error setting-up DMA (application read operation).
15 Protocol error (application read operation).
16 Read error reported from LAN card (application read operation).
17 Read complete error (application read operation).
18 DMA error (application read operation).
28 Error setting-up DMA (LAN card-to-File System read operation).
29 Protocol error (LAN card-to-File System read operation).
2A Error sending Write Message Buffer command to File Card.
2B Error in response to read/write operation (LAN card-to-File Card).
2C Read Complete from File Card error.
2D Read error reported from LAN card (LAN card-to-File Card).
2E DMA error reported from LAN card (LAN card-to-File Card).
2F Error sending Read Complete to LAN card.
3C Error setting-up DMA (CP-to-LAN card write operation).
3D Protocol error (CP-to-LAN card write operation).
3E Write Complete error (CP-to-LAN card write operation).
3F Write error reported form LAN card (CP-to-LAN card write operation).
40 DMA error (CP-to-LAN card write operation).
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0
Peripheraladdress
CB task ID
Control busmessage types
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
*Unused
00000 00010203 04050607 08090A0B 0C0D0E0F
280 STATUS LOG
STATUS CODES 106
Entry header
IORB header
CB-out messageCB-in message
Registersduring event
50 Error on Read Buffer command (FS-to-LAN card write operation).
51 Protocol error (FS-to-LAN card write operation).
52 Error setting-up DMA (FS-to-LAN card write operation).
53 Write error reported from LAN card (FS-to-LAN card write operation).
54 DMA error (FS-to-LAN card write operation).
55 Write Complete error (FS-to-LAN card write operation).
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0
Peripheraladdress
CB task ID
Control busmessage types
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
*Unused
00000 00010203 04050607 08090A0B 0C0D0E0F
STATUS LOG 281
STATUS CODES106
Entry header
IORB header
CB-out messageCB-in message
Registersduring event
Registersduring event
Entry header
64 Error from SR routine (application accept/reject of connection).
65 Protocol error (application accept/reject of connection).
66 Error from router table call (application accept/reject of connection).
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0
Peripheraladdress
CB task ID
Control busmessage types
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
*Unused
00000 00010203 04050607 08090A0B 0C0D0E0F
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
Task ID
00020
00000 00010203 04050607 08090A0B 0C0D0E0F
00010
00030
00040
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0*Unused
282 STATUS LOG
STATUS CODES 106
Entry header
IORB header
CB-out messageCB-in message
Registersduring event
Registersduring event
Entry header
78 Error from SR routine (application disconnect).
79 Protocol error (application disconnect).
7A Error from router table call (application disconnect).
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0
Peripheraladdress
CB task ID
Control busmessage types
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
*Unused
00000 00010203 04050607 08090A0B 0C0D0E0F
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
Task ID
00020
00000 00010203 04050607 08090A0B 0C0D0E0F
00010
00030
00040
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0*Unused
STATUS LOG 283
STATUS CODES106
Entry header
IORB header
CB-out messageCB-in message
Registersduring event
Registersduring event
Entry header
7B Error from LAN card (application disconnect).
A0 Error from SR routine (application connect).
A1 Protocol error (application connect).
A2 Error from router table call (application connect).
B4 Error from router table call (switch active connection from one appli-cation to another).
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0
Peripheraladdress
CB task ID
Control busmessage types
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
*Unused
00000 00010203 04050607 08090A0B 0C0D0E0F
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
Task ID
00020
00000 00010203 04050607 08090A0B 0C0D0E0F
00010
00030
00040
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0*Unused
284 STATUS LOG
STATUS CODES 106
Entry header
IORB header
CB-out messageCB-in message
Registersduring event
C8 Error from SR routine (ping function).
C9 Protocol error (ping function).
D2 Error setting-up DMA (write network service data to LAN card).
D3 Protocol error (write network service data to LAN card).
D4 Write Complete error (write network service data to LAN card).
D5 Write error reported from LAN card (write network service data to LAN card).
D6 DMA error (write network service data to LAN card).
DC Protocol error (get IP address for system name).
DD Error from LAN card (get IP address for system name).
DE DMA error (get IP address for system name).
DF Error from SR routine (get IP address for system name).
F0 Error from SR routine (reset notification to LAN card).
F1 Protocol error (reset notification to LAN card).
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0
Peripheraladdress
CB task ID
Control busmessage types
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
*Unused
00000 00010203 04050607 08090A0B 0C0D0E0F
STATUS LOG 285
STATUS CODES106
Entry header
IORB header
CB-out messageCB-in message
Registersduring event
ere haventel order.
104 Error from SR routine (write initial configuration to LAN card).
105 Protocol error (write initial configuration to LAN card).
118 Error setting-up DMA (write configuration to LAN card).
119 Protocol error (write configuration to LAN card).
11A Write Complete error (write configuration to LAN card).
11B Write error reported from LAN card (write configuration to LAN card).
11C DMA error (write configuration to LAN card).
12C Read Message Buffer command error (FS-to-LAN card write phrase data).
12D Read Message Buffer Response error (FS-to-LAN card write phrase data).
12E Protocol error (FS-to-LAN card write phrase data).
12F Error setting-up DMA (FS-to-LAN card write phrase data).
130 Write error reported from LAN card (FS-to-LAN card write phrase data).
131 DMA error (FS-to-LAN card write phrase data).
132 Write Complete error (FS-to-LAN card write phrase data).
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0
Peripheraladdress
CB task ID
Control busmessage types
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
*Unused
00000 00010203 04050607 08090A0B 0C0D0E0F
Note: subcodes listed hbeen transposed from I
286 STATUS LOG
STATUS CODES 106
Registersduring event
Entry header
re hasntel order.
Entry headerRegistersduring event
re hasntel order.
258 Error in LAN card router table initialization.
294 API crash routine.
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
Task ID
00020
00000 00010203 04050607 08090A0B 0C0D0E0F
00010
00030
00040
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0*Unused
Note: subcode listed hebeen transposed from I
CSEBP EIP
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010
Note: subcode listed hebeen transposed from I
STATUS LOG 287
STATUS CODES106
Registersduring event
Entry header
ere haventel order.
295 Crash in module for debugging purposes.
2A8 Error when getting LAN card/API status.
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
Task ID
00020
00000 00010203 04050607 08090A0B 0C0D0E0F
00010
00030
00040
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0*Unused
Note: subcodes listed hbeen transposed from I
288 STATUS LOG
STATUS CODES 107
Entry header
IORB header
CB-out messageCB-in message
Registersduring event
107 CP/LAN Protocol Out of Sequence
01 CB message(s) lost (while reading CB msg from LAN card).
02 CB operation cancelled (while reading CB msg from LAN card).
03 Rec’d unsolicited CB msg (while reading CB msg from LAN card).
04 CB message(s) lost (during receive/send of CB msg).
05 CB operation cancelled (during receive/send of CB msg).
06 Rec’d unsolicited CB msg (during receive/send of CB msg).
07 CB message(s) lost (while sending CB msg to LAN card).
08 CB operation cancelled (while sending CB msg to LAN card).
09 Rec’d unsolicited CB msg (while sending CB msg to LAN card).
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0
Peripheraladdress
CB task ID
Control busmessage types
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
*Unused
00000 00010203 04050607 08090A0B 0C0D0E0F
STATUS LOG 289
STATUS CODES108
Entry header
IORB header
CB-out messageCB-in message
Registersduring event
108 LAN Timeout
LAN failed to respond within timeout period
01 Timeout while reading CB message from LAN card.
02 Timeout while sending/receiving CB message to/from LAN card.
03 Timeout while sending CB message to LAN card.
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0
Peripheraladdress
CB task ID
Control busmessage types
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
*Unused
00000 00010203 04050607 08090A0B 0C0D0E0F
290 STATUS LOG
STATUS CODES 111
Entry header
IORB header
CB-out messageCB-in message
Registersduring event
Entry headerRegistersduring event
110 Control Bus Error in Getting New IUN
When a MDS (Message Delivery System) file is created or expanded, MDSrequests a new IUN from the file system. This error is logged when the CP ---> FS control bus command fails.
111 No IUN Available
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0
Peripheraladdress
CB task ID
Control busmessage types
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
*Unused
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1DEBP EIP CSUnused
STATUS LOG 291
STATUS CODES112
Entry headerRegistersduring event
Entry headerRegistersduring event
112 Error Reading MDS Record
The disk-read function failed while trying to read an MDS record via theMDS cache buffer. The system will restart.
113 MDS-Record Validity Check Error
The validity check failed after reading an MDS record from the disk. Thevalidity check looks at only the record header and the mailbox type. Exam-ine the mailbox’s user record for a corrupted field.
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1DEBP EIP CS
Record IUN Read-functionerror code
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1DEBP EIP CS
Record IUN Unused (zero)
292 STATUS LOG
STATUS CODES 116
Entry headerRegistersduring event
Entry headerRegistersduring event
Entry header
Registersduring event
114 Error Writing MDS Record
The disk-write function failed while trying to write an MDS record via theMDS cache buffer. The system will restart.
115 Error in AMT Search for MDS
The CS:EIP instruction pointer should tell which AMT search function failed.The error code in offset 12-13 tells how the search failed.
116 MDS File Validity Check Error
Mailbox length or phone number invalid.
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1DEBP EIP CS
Record IUN Write-functionerror code
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1DEBP EIP CS
Unused (zero) AMT-searcherror code
Task ID
00020 20212223 24252627 2829
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
EBPEAX
CSEDX
EIP
Subcode = 0
File NumberUndefined(Set to 0)
STATUS LOG 293
STATUS CODES11B
.
Entry header
Registersduring event
11B Fax Queue Error
01 MDS error.
Offset Label Field Description
10-11 File ID 01 = ltnfaxq.c
18-1B Return Code 02 Entry number exceeds maximum.03 Area supplied by user is too big.08 Can’t get a new IORB.0F Can’t lock the user record.10 Can’t unlock file.11 User record read error.13 Can’t abandon the record.16 Too many signature errors during search.18 AMT search error.19 No entry available for retrieval.1A Record deleted.1B Empty user record cannot be deleted.1C Can’t remove MDS record entry from AMT20 Current entry is not allocated.22 File is not direct access type.
Task ID
00020 20212223
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
CSEBP EIP…
…EIP
Line numberin file
Return codeFax/MDSfile number
File ID
294 STATUS LOG
STATUS CODES 11B
Entry header
Registersduring event
Entry header
Registersduring event
02 Notification subsystem error.
03 Action error: fatal software error.
Offset Label Field Description
10-11 File ID 01 = ltnfaxq.c
18-1B Return Code FD Bad service type.F3 IRN cannot be used.E9 Wrong state to try operation.D9 Invalid event code.
Offset Label Field Description
10-11 File ID 01 = ltnfaxq.c
Task ID
00020 20212223
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
CSEBP EIP…
…EIP
Line numberin file
Return codeFax/MDSfile number
File ID
Task ID
00020 20212223
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
CSEBP EIP…
…EIP
Line numberin file
Return codeFax/MDSfile number
File ID
STATUS LOG 295
STATUS CODES11B
h in additional number
Entry header
Registersduring event
e numberile
Smber
Number of Fax/MDS entries
04 AMT error.
14
Offset Label Field Description
1C-1D File ID 01 = ltnfaxq.c
22-25 Return code 00 IUN mismatch, entry not in AMT or mismatcof digits.
FE AMT is full.FD Input parameter error.
Fax phone number from AMTReturn code
Task ID
00020 2021
00000 00010203 04050607 08090A0B 0C0D0E0F
00030 30313233 34353637 38393A3B 3C3DEBP EIP CS
Number ofdigits in faxphone number
Fax/MDSfile number
MDS IUN Unused
Linin f
Unused
Fax/MDSrecord number
Fax/MDentry nu
Fax phone number from AMT00010 10 1C1D1E1F
File ID
296 STATUS LOG
STATUS CODES 120
Entry headerRegistersduring event
120 DMD Entry Read Error
00 OK.
08 Pool of IORBs exhausted.
0F Cannot lock the file or user record.
10 Cannot unlock the file or user record.
11 Error reading user record.
12 Error writing user record.
13 MDS file could not abandon user record.
14 MDS file doesn’t exist.
15 End of AMT reached when searching for an entry.
17 Reached MDS end of file in AMT when searching for an entry.
19 No entry available inside MDS record.
1A MDS record does not exist.
1B Cannot delete user record.
1C Cannot remove MDS entry from AMT.
22 File is not a direct access type.
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
Scramble code
Use count
Message ID
CSEIPEBP
STATUS LOG 297
STATUS CODES121
Entry headerRegistersduring event
121 DMD Entry Write Error
00 OK.
02 Maximum number of records is too big.
03 User area size does not fit.
04 Number of messages does not fit.
05 Size of messages does not fit.
06 File exists; do not create a new one
07 Could not get new IUN.
08 Pool of IORBs exhausted.
09 Pool of buffers exhausted.
0A AMT address insert error.
0E All record numbers within the MDS file are allocated; cannot create new record.
0F Cannot lock the file or user record.
10 Cannot unlock the file or user record.
11 Error reading user record.
12 Error writing user record.
13 MDS file could not abandon user record.
14 MDS file doesn’t exist.
15 End of AMT reached when searching for an entry.
16 AMT signature error time-out while searching MDS file.
17 Reached MDS end of file in AMT when searching for an entry.
18 Error in AMT entry search.
21 Entry cannot be stored because entry size equals zero.
24 File number too big.
26 Cannot insert MDS record because AMT is full.
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
Scramble code
Use count
Message ID
CSEIPEBP
298 STATUS LOG
STATUS CODES 130
Registersduring event
Entry header
130 SBP/SCSI Security Checksum Bad
There are two likely causes for the security check to fail:
• One, a problem reading the hardware serial number. This statuscode combined with file system errors indicates a problem with thefile card.
• Two, corruption of the system configuration data. This may indicatean attempt to get more features or capacity than the operator isentitled to.
The subcodes use two bytes and are presented below as seen in a printout( that is, without transposing).
0000 The security check failed during bootup. The system was dumped and restarted.
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
Task ID
00020
00000 00010203 04050607 08090A0B 0C0D0E0F
00010
00030
00040
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0*Unused
STATUS LOG 299
STATUS CODES130
dated based on its pre-e states are:
switches to read-only
g messages are ated.
Entry headerRegistersduring event
0001 The calculated checksum did not match the expected value.
0100 Could not read the hardware serial number.
Offset Label Field Description
10-11 New security state The security state of the voice processor was upvious state and the results of the check. Possibl
00 Security valid.01-0F The number of days before the system
unless the security is revalidated.FF Read-only state. All features except playin
blocked until the system security is revalid
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1BEBP EIP CS
New security state
300 STATUS LOG
STATUS CODES 131
dated based on its pre- states are:
switches to read-only
g messages are evalidated.
Entry headerRegistersduring event
Entry headerRegistersduring event
131 SBP/SCSI Configuration Checksum Revalidated
The configuration was changed to valid.
Check why the change occurred. It should occur only when Octel Communi-cations acts to revalidate the configuration of a system.
There are two zero subcodes. If offset 08 is 00, check the entry size.
26-Byte Entry
00 Configuration check succeeded either during bootup or during a mid-night check. The configuration had been invalid.
28-Byte Entry
00 The configuration checksum was updated with a new value.
01 Either the configuration chip is missing or a read command sent to the chip failed.
02 The system is a non-SCSI system and does not have the hardware for Software Based Pricing.
Offset Label Field Description
10-11 New configuration The configuration of the voice processor was upvious state and the results of the check. Possible
00 Configuration valid.01-0F The number of days before the system
unless the configuration is revalidated.FF Read-only state. All features except playin
blocked until the system configuration is r
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 1819CSEBP EIP
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1BEBP EIP CS
New configuration(always 0000=security valid)
STATUS LOG 301
STATUS CODES132
Registersduring event
Entry header
132 SBP Internal Error
01 Type of information does not exist in Authorized Used Table.
02 Requested COS from Authorized Used Table is out of range.
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
Task ID
00020
00000 00010203 04050607 08090A0B 0C0D0E0F
00010
00030
00040
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0*Unused
302 STATUS LOG
STATUS CODES 141
on page 308.
re
ber
Entry header
Registersduring event
141 System Backup and Recovery (SBR) General Error
The format depends on the software release.
Aria 1.1
Offset Label Field Description
08-09 Procedure number SBR procedure that logged the error. See table
10-E0 Stack dump Individual fields are described below.
10 which_proc Flag that indicates if process is backup or resto
11-14 response Driver -> OS return code
15-18 rflags Driver -> OS return flags
19-1C status Status code
1D sense_key SCSI drive sense code
1E-1F sbr_rc System backup return code
20-21 scsi_rc SCSI driver return code
22-23 fcp_rc Filecard primitives return code
24-25 cif_rc Client interface return code
26-27 bmi_rc Backup media interface return code
28-29 fsi_rc File system return code
2A-2B vfs_rc Voice file error return code
2C-2D mfc_rc Message conversion return code
2E-2F drc_rc Data conversion return code
30-31 fnc_rc Function layer return code
Procedure numTask ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050 50515253 54555657 58595A5B 5C5D5E5F
00060 60616263 64656667 68696A6B 6C6D6E6F
00070 70717273 74757677 78797A7B 7C7D7E7F
00080 80818283 84858687 88898A8B 8C8D8E8F
00090 90919293 94959697 98999A9B 9C9D9E9F
000A0 A0A1A2A3 A4A5A6A7 A8A9AAAB ACADAEAF
000B0 B0B1B2B3 B4B5B6B7 B8B9BABB BCBDBEBF
000C0 C0C1C2C3 C4C5C6C7 C8C9CACB CCCDCECF
000D0 D0D1D2D3 D4D5D6D7 D8D9DADB DCDDDEDF
000E0 E0E1E2E3 E4E5E6E7 E8E9EAEBP EIP CS
Stack dump
STATUS LOG 303
STATUS CODES141
ror.)
32-33 ivr_rc IVR phrase backup/restore return code
34-35 tape_rc Tape device return code00 OK.02 Tape not ready.03 No tape in device.
04 Tape is unusable.05 Tape is full.06 Tape drive error.07 Tape or tape drive problem.
08 Tape internal error. (This is the default er09) Tape reset.FE Process cancelled.FF Process never completed.
36 bus SCSI bus ID
37 devID Backup device ID
38-39 reqID I/O request sequence number
3A a_scode Additional sense code
3B a_scode_quaf Additional sense code qualifier
3C-41 FAR *sense Pointer to SENSE buffer
42-43 proc_num Current procedure number
44-45 fun_num Current function flag
46-49 msgid Message ID and scramble code (backup)
4A-4D rmsgid Message ID and scramble code (restore)
4E-4F msgoff Message offset within the user record
50 msgtyp Message type name/greeting/vmsg/etc.
51 msgdsize Message descriptor size
52-93 msgdir Message descriptor (directory)
94-95 mbxirn Mailbox IRN containing the message
96-9B mbxnum Mailbox number (tree digit string)
9C-9D mbxtyp Mailbox type
9E-9F mbxcnt Mailbox count
A0-A1 mdscnt MDS count
A2-A3 mds_ent_cnt MDS entry count
A4 systbl_num System table count
A5-A6 fileno MDS file number
A7-A8 usect Message use count
A9-AA sysvfcnt System voice files count
AB-AE namecnt Name/greeting message count
AF-B0 nmdscnt MDS name count
B1-B2 nmbxcnt Name/greeting mailbox count
B3-B6 vmsgcnt Total destinations message count
Offset Label Field Description
304 STATUS LOG
STATUS CODES 141
B7-B8 mmbxcnt Voice and fax mailbox count
B9-BA bad_sysvf Total bad system table voice files
BB-BC bad_nname Total number of bad node name
BD-BE bad_name Total number of bad name/greeting
BF-C0 bad_msgs Total number of bad user messages
C1-C2 bad_mbx Number of bad mailboxes (I/O error)
C3-C4 bad_mds Number of bad MDS (I/O error)
C5-C6 bad_mds_ent Number of bad MDS entries (I/O error)
C7-C8 ivr_lang_area IVR phrase language area
C9-CA ivr_phrase_num IVR phrase number
CB-CC bad_phr_cnt Number of bad phrases per language area
CD-CE tot_bad_phr_cnt Total number of bad phrases
CF-D0 map_tbl_entry Phrase map table entry number
D1-D2 map_tbl_lang Phrase map table language area
D3-D4 mbxcos Mailbox class of service
D5-D6 node IDBN node number
D7-D8 edbn_name_ct Namenet name count
D9-DA bad_edbn_name Number of bad EDBN name entries
DB-DC cos_min Minimum class of service value
DD-DE cos_max Maximum class of service value
DF-E0 sbr_opt Process option:00 Partial backup or restore01 Full backup or restore
Offset Label Field Description
STATUS LOG 305
STATUS CODES141
on page 308.
re
ber
Entry header
Registersduring event(EBP is inoffset CD-D0)
Aria 1.0
Offset Label Field Description
08-09 Procedure number SBR procedure that logged the error. See table
10-CC Stack dump Individual fields are described below.
10 which_proc Flag that indicates if process is backup or resto
11-14 response Driver -> OS return code
15-18 rflags Driver -> OS return flags
19-1C status Status code
1D sense_key SCSI drive sense code
1E-1F sbr_rc System backup return code
20-21 scsi_rc SCSI driver return code
22-23 fcp_rc Filecard primitives return code
24-25 cif_rc Client interface return code
26-27 bmi_rc Backup media interface return code
28-29 fsi_rc File system return code
2A-2B vfs_rc Voice file error return code
2C-2D mfc_rc Message conversion return code
2E-2F drc_rc Data conversion return code
30-31 fnc_rc Function layer return code
32-33 ivr_rc IVR phrase backup/restore return code
34 bus SCSI bus ID
35 devID Backup device ID
36-37 reqID I/O request sequence number
38 a_scode Additional sense code
39 a_scode_quaf Additional sense code qualifier
Procedure numTask ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050 50515253 54555657 58595A5B 5C5D5E5F
00060 60616263 64656667 68696A6B 6C6D6E6F
00070 70717273 74757677 78797A7B 7C7D7E7F
00080 80818283 84858687 88898A8B 8C8D8E8F
00090 90919293 94959697 98999A9B 9C9D9E9F
000A0 A0A1A2A3 A4A5A6A7 A8A9AAAB ACADAEAF
000B0 B0B1B2B3 B4B5B6B7 B8B9BABB BCBDBEBF
000C0 C0C1C2C3 C4C5C6C7 C8C9CACB CCCDCECF
000D0 D0D1D2D3 D4D5D6EIP CSEBP…
Stack dump
306 STATUS LOG
STATUS CODES 141
3A-3F FAR *sense Pointer to SENSE buffer
40-41 proc_num Current procedure number
42-43 fun_num Current function flag
44-47 msgid Message ID and scramble code (backup)
48-4B rmsgid Message ID and scramble code (restore)
4C-4D msgoff Message offset within the user record
4E msgtyp Message type name/greeting/vmsg/etc.
4F msgdsize Message descriptor size
50-91 msgdir Message descriptor (directory)
92-93 mbxirn Mailbox IRN containing the message
94-99 mbxnum Mailbox number (tree digit string)
9A-9B mbxtyp Mailbox type
9C-9D mbxcnt Mailbox count
9E-9F mdscnt MDS count
A0-A1 mds_ent_cnt MDS entry count
A2 systbl_num System table count
A3-A4 fileno MDS file number
A5-A6 usect Message use count
A7-A8 sysvfcnt System voice files count
A9-AA namecnt Name/greeting message count
AB-AC nmdscnt MDS name count
AD-AE nmbxcnt Name/greeting mailbox count
AF-B0 vmsgcnt Total destinations message count
B1-B2 mmbxcnt Voice and fax mailbox count
B3-B4 bad_sysvf Total bad system table voice files
B5-B6 bad_nname Total number of bad node name
B7-B8 bad_name Total number of bad name/greeting
B9-BA bad_msgs Total number of bad user messages
BB-BC bad_mbx Number of bad mailboxes (I/O error)
BD-BE bad_mds Number of bad MDS (I/O error)
BF-C0 bad_mds_ent Number of bad MDS entries (I/O error)
C1-C2 ivr_lang_area IVR phrase language area
C3-C4 ivr_phrase_num IVR phrase number
C5-C6 bad_phr_cnt Number of bad phrases per language area
C7-C8 tot_bad_phr_cnt Total number of bad phrases
C9-CA map_tbl_entry Phrase map table entry number
CB-CC map_tbl_lang Phrase map table language area
Offset Label Field Description
STATUS LOG 307
STATUS CODES141
Area
Functional Layer
First, transpose the procedure number and convert it to decimal. Decimal numbers 901-912 have two definitions; be careful interpreting them.
Procedure Number (offset 08-09)
Number Procedure
501 FNC_BACKUP_DATA_PN
502 FNC_BACKUP_PROCESS_PN
503 FNC_INIT_MEDIA_PN
504 FNC_WRITE_DB_HDR_PN
505 FNC_BACKUP_GET_RCB_PN
506 FNC_BLD_BKP_HDR_PN
507 FNC_BACKUP_SYS_TBLS_PN
508 FNC_MBX_NM_GRTG_REQUEST_PN
509 FNC_MBX_MSG_REQUEST_PN
510 FNC_BITMAP_SET_PN
511 FNC_TEST_BMI_OVERFLOW_PN
512 FNC_BACKUP_MBOXS_PN
513 FNC_BACKUP_MDS_PN
514 FNC_BACKUP_SYS_VFILES_PN
515 FNC_BACKUP_MBOXS_VFILES_PN
516 FNC_INIT_DATA_PN
517 FNC_ERRORLOG_PN
518 FNC_SET_FSI_PN
519 FNC_RESET_FSI_PN
520 FNC_OPEN_MEDIA_PN
521 FNC_CLOSE_MEDIA_PN
522 FNC_GLOBAL_RESTORE_PN
523 FNC_GLOBAL_RESTORE_PROCESS_PN
524 FNC_READ_DB_HDR_PN
525 FNC_RESTORE_SYS_TBLS_PN
526 FNC_RESTORE_MBOXS_PN
527 FNC_RESTORE_MDS_PN
528 FNC_RESTORE_SYS_VFILES_PN
529 FNC_RESTORE_MBOXS_VFILES_PN
530 FNC_RESTORE_GET_RCB_PN
531 FNC_RESTORE_FREE_BUF_PN
532 FNC_PROC_BKP_HDR_PN
308 STATUS LOG
STATUS CODES 141
Functional Layer
Client Interface
Area
533 FNC_BACKUP_MBOXS_NAME_PN
534 FNC_BACKUP_MBOXS_MSGS_PN
535 FNC_RESTORE_MBOXS_NAME_PN
536 FNC_RESTORE_MBOXS_MSGS_PN
537 FNC_BACKUP_MBOXS_APPL_MSGS_PN
538 FNC_RESTORE_MBOXS_APPL_MSGS_PN
700 SBR_MAIN_PN
701 CIF_COMM_CHNLS_GET_PN
702 CIF_PROCESS_CMD_PN
703 CIF_START_COMMAND_PN
704 CIF_ACTION_COMMAND_PN
705 CIF_SET_COMMAND_PN
706 CIF_SUSPEND_COMMAND_PN
707 CIF_ABORT_COMMAND_PN
708 CIF_RESUME_COMMAND_PN
709 CIF_READ_COMMAND_PN
710 CIF_DELETE_COMMAND_PN
711 CIF_CANCEL_COMMAND_PN
712 CIF_SYS_ADMIN_COMMAND_PN
713 CIF_INIT_PN
714 CIF_POLL_CLIENT_REQUEST_PN
715 CIF_SND_RCV_MSG_PN
716 CIF_SEND_RESPONSE_PN
717 CIF_VALIDATE_BACKUP_PARMS_PN
718 CIF_VALIDATE_RESTORE_PARMS_PN
719 CIF_VALIDATE_BKUP_DEVICES_PN
720 CIF_VALIDATE_MB_PROFILES_PN
721 CIF_RUN_BACKUP_PN
722 CIF_FILL_IN_PROFILE_PN
723 CIF_FILL_IN_DEFAULTS_PN
724 CIF_GET_HISTORY_PN
725 PSC_SET_SCHEDULED_PROC_PN
726 PSC_CLEAR_SCHEDULE_PN
727 PSC_SCHEDULED_TIME_PN
Procedure Number (offset 08-09) (Continued)
Number Procedure
STATUS LOG 309
STATUS CODES141
Client Interface
Data Representation
Converter
Area
728 PSC_RESCHEDULE_JOB_PN
729 PSC_GET_DEFAULT_RESP_PN
730 CIF_PARSE_PARMS_PN
731 CIF_BUILD_PARMS_PN
732 CIF_BUILD_RESPONSE_PN
733 CIF_BUILD_PARM_ERROR_RESP_PN
734 CIF_MAP_Q_ERROR_TO_SBR_PN
735 CIF_LOG_ERROR_PN
736 CIF_CHECK_WHATS_RUNNING_PN
737 CIF_TOGGLE_PT_PN
738 CIF_SAVE_PROC_HISTORY_PN
739 CIF_LOCK_SMT_PN
740 CIF_UNLOCK_SMT_PN
741 CIF_LOCK_ASA_PN
742 CIF_UNLOCK_ASA_PN
743 CIF_CHECK_ASA_STATUS_PN
744 SBR_ATOI_PN
745 SBR_CHECK_MDS_FILE_EXIST_PN
800 SBR_DRC_MFC_TEST_PN
801 SBR_DRC_MFC_TEST_ONE_PN
802 SBR_DRC_MFC_TEST_TWO_PN
803 SBR_DRC_GET_NEXT_ASPEN_INTERVAL_PN
804 SBR_DRC_INSERT_SIERRA_INTERVAL_PN
805 SBR_DRC_CONVERT_ASPEN_TO_SIERRA_INTERVAL_PN
806 SBR_DRC_ASPEN_TO_SIERRA_VOICE_PN
807 SBR_DRC_INIT_VFCCB_PN
808 SBR_DRC_INIT_SIERRA_VOISEG_PN
809 SBR_DRC_CHECK_VOISEG_FOR_AVALIABLE_PN
810 SBR_DRC_GET_NEXT_SIERRA_VOISEG_PN
811 SBR_DRC_INSERT_SIERRA_VOICE_PN
812 SBR_DRC_SIERRA_TO_SIERRA_VOICE_PN
813 SBR_DRC_CHECK_IF_MSGID_PRESENT_PN
814 SBR_DRC_UPDATE_MSGID_TABLE_PN
815 SBR_DRC_ADD_MSGID_TO_TABLE_PN
Procedure Number (offset 08-09) (Continued)
Number Procedure
310 STATUS LOG
STATUS CODES 141
Voice Files Backup
Message File Conversion
Area
Decimal numbers 901-912 have two definitions; be careful interpreting them.
901 VFS_BACKUP_SYS_TBLS
902 VFS_BACKUP_NNAME
903 VFS_BACKUP_NAME
904 VFS_BACKUP_MSGS
905 VFS_BMSG_RCBS
906 VFS_RMSG_RCBS
907 VFS_RESTORE_SYS_TBLS
908 VFS_RESTORE_NNAME
909 VFS_RESTORE_NAME
910 VFS_RIVR_MSG_RCBS
911 VFS_BACKUP_EDBN_NAME
912 VFS_RESTORE_EDBN_NAME
900 SBR_MFC_SETUP_FILE_CONVERSION_PN
901 SBR_MFC_INIT_SIERRA_VOISEG_PN
902 SBR_MFC_INIT_SIERRA_FAXSEG_PN
903 SBR_MFC_CHECK_VOISEG_FOR_AVALIABLE_PN
904 SBR_MFC_CHECK_SIERRA_FOR_AVALIABLE_FAXSEG_PN
905 SBR_MFC_GET_NEXT_SIERRA_VOISEG_PN
906 SBR_MFC_GET_NEXT_SIERRA_FAXSEG_PN
907 SBR_MFC_GET_NEXT_ASPEN_INTERVAL_PN
908 SBR_MFC_GET_NEXT_ASPEN_FAX_INTERVAL_PN
909 SBR_MFC_INSERT_SIERRA_INTERVAL_PN
910 SBR_MFC_INSERT_SIERRA_FAX_INTERVAL_PN
911 SBR_MFC_CONVERT_ASPEN_TO_SIERRA_FAX_INTERVAL_PN
912 SBR_MFC_CONVERT_ASPEN_TO_SIERRA_INTERVAL_PN
913 SBR_MFC_ASPEN_TO_SIERRA_FAX_PN
914 SBR_MFC_ASPEN_TO_SIERRA_VOICE_PN
915 SBR_MFC_SIERRA_TO_SIERRA_FAX_PN
916 SBR_MFC_SIERRA_TO_SIERRA_VOICE_PN
917 SBR_MFC_ASPEN_TO_ASPEN_FAX_PN
918 SBR_MFC_ASPEN_TO_ASPEN_VOICE_PN
Procedure Number (offset 08-09) (Continued)
Number Procedure
STATUS LOG 311
STATUS CODES141
Interactive Voice Response
Area
1000 FNC_BACKUP_IVR_PHR_PN
1001 FNC_RESTORE_IVR_PHR_PN
1002 FNC_BACKUP_IVR_MAP_TBL_PN
1003 FNC_RESTORE_IVR_MAP_TBL_PN
Procedure Number (offset 08-09) (Continued)
Number Procedure
312 STATUS LOG
STATUS CODES 148
ted.
available.
Entry header
148 RMM General Error Code
The contents of the RMM circular error buffer (160 bytes long) starts at off-set 0x10. Current position in the circular buffer is the double word at offset0xB0.
Each entry in the RMM buffer is 16 bytes long; the fields in each entry areas follows:
Here is the format of the error log entry:
MCM Function Return Codes
Offset Label Description
04-05 MCM Return Codes 0x0001 = Requested operation is not suppor
0x0002 = Object search yielded nothing.
0x0003 = Seek first.
0x0004 = After object read, more data is still
00010203 04050607 08090A0B
RMM function #
Return Code ofRMM function
Return Code ofMCM function
Internal RMMfunciton #
Return Code oflatest internal RMM call
Task ID(of calling task)
unused
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050 50515253 54555657 58595A5B 5C5D5E5F
00060 60616263 64656667 68696A6B 6C6D6E6F
00070 70717273 74757677 78797A7B 7C7D7E7F
00080 80818283 84858687 88898A8B 8C8D8E8F
00090 90919293 94959697 98999A9B 9C9D9E9F
000A0 A0A1A2A3 A4A5A6A7 A8A9AAAB ACADAEAF
000B0 B0B1B2B3
Current position in circular buffer
CSEBP EIP
RMM circular error buffer
Subcode = 0
STATUS LOG 313
STATUS CODES148
.
ne.
re open.
object was found.
rmat.
).
t.
count.
B.
irst.
device.
e.
ted.
04-05 MCM Return Codes 0x0021 = End-of-File.
0x0022 = End-of-Media.
0x0023 = End-of-Data.
0x0024 = End-of-File.
0x8000 = Severe internal error—SCSI/MCM
0x8001 = Invalid parameters passed to routi
0x8002 = Attempt to operate on device befo
0x8003 = While reading object data, another
0x8004 = The media is not in a valid RMM fo
0x8005 = Unexpected end-of-media (no data
0x8006 = Device is already open.
0x8007 = Unable to allocate memory.
0x8008 = Failed to seek an “expected” objec
0x8009 = Failed to read the requested byte
0x800A = Too busy; unable to find a free RC
0x800B = Must call ID_SELF before use.
0x800C = Must specify a seek to an object f
0x800D = Not the same task that opened the
0x800E = CRC check on descriptor preambl
0x8020 = Unkown SCSI error detected.
0x8021 = Media is busy/ejecting/rewinding.
0x8022 = No media detected.
0x8023 = Medai may be damaged.
0x8024 = End-of-media reached.
0x8025 = No device detected.
0x8026 = Unable to write. Media write protec
0x8027 = Possible hot-plug detected.
Offset Label Description
314 STATUS LOG
STATUS CODES 150
Entry headerRegistersduring event
150 MDS File Access Failure for Port Testing
This error is logged every time the port test utility fails to access or create itsMDS file. A Service Affecting (SA) alarm is triggered.
One of the following operations failed during port testing:
• Failed SMT operation while creating an MDS file, or
• Failed SMT or LT operation while updating the user area in theMDS file, or
• Failed SMT or LT operation while reading the user area in the MDSfile.
The following subcodes define specifically what failed in the previous opera-tion during port testing.
03 User area specified does not exist/fit.
06 Cannot create an MDS file; already exists.
07 Cannot get a new IUN record allocated from the file system.
0A New MDS record address cannot be added to AMT tab.
0C Cannot write primary user record to disk.
0F Cannot lock the MDS user record file.
10 Cannot unlock the MDS user record file.
12 User record write I/O error.
13 Cannot abandon the user record.
14 File does not exist for this user record number.
26 Cannot add new entry to the AMT; AMT full.
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1BCSEIPEBP
Same value asoffset 08
STATUS LOG 315
STATUS CODES151
Entry headerRegistersduring event
Entry headerRegistersduring event
151 Possible Bad Port(s) Found during Port Testing—NSA
This error is logged if bad port(s) were detected during port testing. Also,the SA/NSA alarm in the Port Testing Administration Menu is equal to 1(NSA). A Non-Service Affection (NSA) alarm is triggered.
152 Possible Bad Port(s) Found during Port Testing—SA
This error is logged if bad port(s) were detected during port testing. Also,the SA/NSA alarm in the Port Testing Administration Menu is equal to 2(SA). A Service Affecting (SA) alarm is triggered.
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1BCSEIPEBP
Number of port(s) thatfailed during port testing
Same value asoffset 08
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1BCSEIPEBP
Same value asoffset 08
Number of port(s) thatfailed during port testing
316 STATUS LOG
STATUS CODES 155
Entry headerRegistersduring event
Entry headerRegistersduring event
154 CDR Review Utility Error
The subcode byte (08) and the field at bytes 10-11 contain the non-zeroreturn code (see table below) from calls to functions that handle MDS files.These functions are called by routines for CDR record/event handling.
155 CIP MDS File Error
01 Could not create CIP MDS file.
02 Could not put user data to MDS file.
03 Could not get user data from MDS file.
Offset Label Description
10-11 Return Code 2 = Maximum number of records exceeded.
3 = User area size too big.
4 = Number of messages won’ t fit.
5 = Size of messages too big.
6 = MDS file exists.
7 = Could not get new IUN.
8 = IORB pool depleted.
9 = Buffer pool depleted.
0A = AMT address insert error.
0B = FS protocol error.
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1BCSEIPEBP
Return Code
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1BEBP EIP CS
Return Code MDS File ID(from call to MDS routine)
STATUS LOG 317
STATUS CODES155
his file.
w.
e area.
10-11 Return Code 0C = IUNs exhausted.
0D = CB I/O error.
0E = Can’t create new record.
0F = Can’t lock the file.
10 = Can’t unlock the file or the user record.
11 = MDS Read error.
12 = MDS Write error.
13 = Can’t abandon error.
14 = File doesn’t exist for this file number.
15 = Ran outside AMT.
16 = AMT signature error timeout.
17 = Passed the last entry in AMT belonging to t
18 = AMT entry search error.
19 = No entry available for retrieval.
1A = Input record number is not in the AMT.
1B = Empty user record cannot be deleted.
1C = Can’t remove MDS record entry from AMT.
1D = No field to convert to, or, conversion overflo
1E = Number does not fit in field length.
1F = Entry is already marked.
20 = Current entry is not allocated.
21 = Entry cannot be stored.
22 = File is not Direct Access type.
23 = AMT backsearch failed.
24 = File number too big.
25 = User supplied buffer is smaller than messag
36 = Can’t insert into AMT.
Offset Label Description
318 STATUS LOG
STATUS CODES 156
Entry headerRegistersduring event
156 NWPL MDS Access Error
01 MDS file creation failure.
02 MDS file UDA update failure.
03 MDS file entry access failure.
04 MD file invalid entry.
Offset Label Description
10-11 Return Code 2 = Maximum number of records exceeded.
3 = User area size too big.
4 = Number of messages won’ t fit.
5 = Size of messages too big.
6 = MDS file exists.
7 = Could not get new IUN.
8 = IORB pool depleted.
9 = Buffer pool depleted.
0A = AMT address insert error.
0B = FS protocol error.
0C = IUNs exhausted.
0D = CB I/O error.
0E = Can’t create new record.
0F = Can’t lock the file.
10 = Can’t unlock the file or the user record.
11 = MDS Read error.
12 = MDS Write error.
13 = Can’t abandon error.
14 = File doesn’t exist for this file number.
15 = Ran outside AMT.
16 = AMT signature error timeout.
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1BEBP EIP CS
Return Code MDS File ID(from call to MDS routine)
STATUS LOG 319
STATUS CODES156
his file.
w.
e area.
10-11 Return Code 17 = Passed the last entry in AMT belonging to t
18 = AMT entry search error.
19 = No entry available for retrieval.
1A = Input record number is not in the AMT.
1B = Empty user record cannot be deleted.
1C = Can’t remove MDS record entry from AMT.
1D = No field to convert to, or, conversion overflo
1E = Number does not fit in field length.
1F = Entry is already marked.
20 = Current entry is not allocated.
21 = Entry cannot be stored.
22 = File is not Direct Access type.
23 = AMT backsearch failed.
24 = File number too big.
25 = User supplied buffer is smaller than messag
36 = Can’t insert into AMT.
Offset Label Description
320 STATUS LOG
STATUS CODES 157
condition).
MT prefix.
gth is too long.
Entry headerRegistersduring event
157 NER MDS Access Error
01 MDS file creation failure.
02 MDS file UDA update failure.
03 MDS file entry access failure.
Offset Label Description
10-11 Return Code -1 = Network exception router full.
-2 = Entry not found.
-3 = Error detected by MDS.
-4 = Network exception router exists.
-5 = Network exception router new update (race
-6 = Network exception router not matched with A
-7 = Network exception router entry exists.
-8 = Network exception router to-node’s mbox len
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1BEBP EIP CS
Return Code MDS File ID(from call to MDS routine)
STATUS LOG 321
STATUS CODES158
Registersduring event
Entry header
158 NER Memory Access Error
01 Event ID of NER memory is corrupted.
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
Task ID
00020
00000 00010203 04050607 08090A0B 0C0D0E0F
00010
00030
00040
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0*Unused
322 STATUS LOG
STATUS CODES 164
Entry header
Registersduring event
160 Digital Networking System Error
161 Digital Networking Operational Error
162 Digital Networking Warning Message
163 Digital Networking Informative Message
164 Digital Networking Internal Error
Note: Status codes 160H through 163H are only logged if theSST flag at 011A (SP_NIC_FLG) is set to 2.
The type of data stored in offsets 0x12-13 (Data1) and 0x14-17 (Data2) var-ies, depending on the context in which the error log entry was made. Thefile ID in offset 0x11 and a location number in offset 0x10 define this contextand therefore are used to identify the data at 0x12-17.
To find the error logging context, you need to search a file for the instanceof a call to an error logging routine where the file ID is used with the locationnumber.
There are two types of error logging routines, one in which the locationnumber is the 4th parameter of the call, and the other in which the locationnumber is added to the file ID and where that sum is the 3rd parameter ofthe call (used in SP files only).
Refer to the File ID Table below to obtain the file name in which the call tothe error logging routine was coded. If the file is not an SP file, search thefile for the instance of the routine that has the location number as its 4thparameter. The 5th parameter is stored at Data1; the 6th parameter isstored at Data2.
If it’s an SP file, the sum of the file ID and location is OR’d with a word ofdata and passed in the 3rd parameter. The contents of that word is stored atData1. The contents of the 4th parameter, a double word, is stored atData2.
01 Required parameter NULL.
02 Fatal software error.
03 Failed to initialize MLT.
04 System shutdown error.
EBP
Task ID
00020
00010 10111213 14151617 EAXCS
EDXEIP
File ID
Location in file
00000 00010203 04050607 08090A0B 0C0D0E0F
Data2Data1
STATUS LOG 323
STATUS CODES164
Entry header
Registersduring event
65 Return code unknown.
66 Protocol error.
67 Unexpected value, software error.
68 Message segment type error.
69 Miscellaneous software error.
6A Message recording type error.
6B Negative ACK from remote system.
6C Bad message.
6D LAN card error.
6E File system error.
6F Timeout.
70 Session aborted.
71 Frame or chesksum error in packet.
72 User record error.
73 Error in setting fallback.
74 Message delete from queue error.
75 Error in decrement use count.
76 Error in increment use count.
77 Skip message in queue error.
78 Unget message in queue error.
79 Error in session setup.
Task ID
00020 20212223 24252627 2829
00010 10111213 14151617 18191A1B 1C1D1E1F
EBPEAX
CSEDX
EIP
File ID
Location in file
00000 00010203 04050607 08090A0B 0C0D0E0F
Data2Data1
324 STATUS LOG
STATUS CODES 164
Entry header
Registersduring event
7A Put message in mailbox failed.
7B Update NameNet directory failed.
7C Queue loopback message failed.
7D Error in connect.
7E Error in disconnect.
7F Error in getting messaaage from BN queue.
80 Error in deleting message from BN queue.
81 Failed to create a PQ for mail task.
82 Failed to unget a message in BN queue.
83 Failed to get a recepient.
84 Failed to delete a recepient.
85 Node record error.
86 Failed to access node reference table.
87 Failed to send/receive sync.
88 SNMP-related error.
89 Error in deleting EDBN entry.
C9 Unexpected value.
Task ID
00020 20212223 24252627 2829
00010 10111213 14151617 18191A1B 1C1D1E1F
EBPEAX
CSEDX
EIP
File ID
Location in file
00000 00010203 04050607 08090A0B 0C0D0E0F
Data2Data1
STATUS LOG 325
STATUS CODES164
Entry header
Registersduring event
ere haventel order.
12D (Transposed from 2D01.) Overridden error information.
12E (Transposed from 2E01.) Returned message undelivered
12F (Transposed from 2F01.) Unexpected packet received.
130 (Transposed from 3001.) Queue loopback message failed—unknown or disabled node.
131 (Transposed from 3101.) Connection error.
132 (Transposed from 3201.) Disconnect error.
133 (Transposed from 3301.) Unable to perform NameNet pull.
File ID Table
Value Filename01 mltmain.c02 mltclient.c03 mltserver.c04 mltsched.c05 mltconnect.c06 mltsession.c07 mltprocess.c08 mltdriver.c09 mltpacket.c0A mltmessage.c0B mltload.c0C mlttime.c0D mltprotlib.c80 sysdnq.c81 sysdnm.c82 sysdnr.c83 sysdnt.c84 sysbnsch.c85 sysdnmret.c86 sysdnmcnf.c87 sysdnmnot.c88 sysdnmedbn.c
Task ID
00020 20212223 24252627 2829
00010 10111213 14151617 18191A1B 1C1D1E1F
EBPEAX
CSEDX
EIP
File ID
Location in fileData2
Data1
00000 00010203 04050607 08090A0B 0C0D0E0F
Note: subcodes listed hbeen transposed from I
326 STATUS LOG
STATUS CODES 165
n.
mode).
Entry header
165 Digital Networking Connect Retries Exhausted
191 (Transposed from 9101.) Retries exhausted—fell back to analog.
192 (Transposed from 9201.) Retries exhausted, node not set to fallback, and messages were returned.
Reason Codes
Offset Label Description
12-13 Reason Code -109 (0xFF93) Failed to assign channel.
-110 (0xFF92) Connect process failed.
-111 (0xFF91) Session process failed.
-112 (0xFF90) Remote system is busy.
-113 (0xFF8F) Connect request is rejected.
-114 (0xFF8E) Transmit mail process failed.
-115 (0xFF8D) Receive mail process failed.
-116 (0xFF8C) Unsolicited disconnect.
-117 (0xFF8B) Invalid protocol version.
-118 (0xFF8A) Invalid capability bitmap.
-119 (0xFF89) Node SN mismatch.
-121 (0xFF87) Failed at session sync.
-122 (0xFF86) Failed at session profile.
-123 (0xFF85) Failed at session key.
-124 (0xFF84) Failed at session authorizatio
-125 (0xFF83) Protocol error.
-126 (0xFF82) Major software failure.
-143 (0xFF71) LAN card shut down (pending
-144 (0xFF70) LAN card is down.
-145 (0xFF6F) No MLT channel is available.
00010 10111213
Task ID
Node number
Reason Code for connection failure
00000 00010203 04050607 08090A0B 0C0D0E0F
STATUS LOG 327
STATUS CODES1C0
header
000000
1C0 OPI SP Error
Error transmitting or receiving a control bus message using the OPI bus.
00 Receive count threshold reached (not an error).
01 Receive byte count error.
02 Receive header CRC error.
03 Receive information CRC error.
04 Receive software timeout reached (not an error).
05 Receive FIFO overrun; FIFO is full. May be a performance issue.
06 Receive bus timeout. Check flow control.
07 Receive transmitter bus timeout. Caused by transmitting card.
08 Receive buffer nearly full (not an error).
09 Transmit buffer empty (not an error).
0A Transmit header error; CRC or byte count error.
0B Transmit information CRC error.
0C Transmit FIFO underrun. FIFO is empty.
0D Alcatel destination slot is out of range (not an error).
0E Transmit receiver bus timeout. Caused by receiving card.
0F Transmit transmitter bus timeout. Caused by this card.
Task ID (= -1)
Entry00000 00010203 04050607 08090A0B 0C0D0E0F
Extra bytes (= 4)
328 STATUS LOG
STATUS CODES 1C2
header
header
1C1 OPI LP Error
Error transmitting or receiving a data bus message using the OPI bus.
00 Receive byte count error.
01 Receive or transmit header error.
02 Receive or transmit information CRC error.
03 Transmit FIFO underrun; FIFO is empty.
04 Receive FIFO overrun; FIFO is full. May be a performance issue.
05 Receiver bus timeout. Caused by receiving card.
06 Transmitter bus timeout. Caused by transmitting card.
1C2 OPI Arbitration Master Error
Error detected by the arbitration master when using the OPI bus.
00 SP receive error. Receiving card caused bus timeout.
01 SP transmit error. Transmitting card caused bus timeout
02 LP receive error. Receiving card caused bus timeout.
03 LP transmit error. Transmitting card caused bus timeout.
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F Entry
Extra bytes (= 4)
Task ID (= -1)
00000 00010203 04050607 08090A0B 0C0D0E0F Entry
Extra bytes (= 4)
STATUS LOG 329
STATUS CODES1E0
Entry header
IORB header
CB-out messageCB-in messageRegistersduring event
Entry header
Entry header
IORB header
CB-out messageCB-in messageRegistersduring event
000000
1E0 Network Directory Error
01 Failed to create Network Directory on the disk.
02 Failed to delete an entry from MDS file.Offsets 10-13: MDS address.Offsets 14-17: return code - see following table.
03 Network directory full.
00020 20212223 24252627 28292A2B 2C2D2E2F
Task ID
CSIPAX BX CX DX SI DI DS
ES
Peripheraladdress
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050 5051
00060
CB task ID
Control busmessage types
User recordnumber
00020 20212223 24252627 2829
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
CSEIP**
* Content depends on subcode
UnusedUnused
00020 20212223 24252627 28292A2B 2C2D2E2F
Task ID
CSIPAX BX CX DX SI DI DS
ES
Peripheraladdress
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050 5051
00060
CB task ID
Control busmessage types
User recordnumber
330 STATUS LOG
STATUS CODES 1E0
Entry header
Entry header
IORB header
CB-out messageCB-in messageRegistersduring event
04 Failed to put EDBN entry in MDS file.Offsets 10-13: node number.Offsets 14-17: return code—see following table.
05 Failed to write EDBN entry to MDS file.Offsets 10-13: MDS address.Offsets 14-17: return code—see following table.
06 Failed to read EDBN entry from MDS file.Offsets 10-13: MDS address.Offsets 14-17: return code—see following table.
07 Failed to read Network Directory date from MDS primary record.Offsets 10-13: zeros.Offsets 14-17: return code—see following table.
08 Failed to write Network Directory date to MDS primary record.Offsets 10-13: zeros.Offsets 14-17: return code—see following table.
09 Software error.Offsets 10-13: node number.Offsets 14-17: zeros.
0A More than 9 same DTMF names exist in the NMT.
00000 00010203 04050607 08090A0B 0C0D0E0F
00020 20212223 24252627 2829
Task ID
00010 10111213 14151617 18191A1B 1C1D1E1F
CSEIP**
* Content depends on subcode
UnusedUnused
00020 20212223 24252627 28292A2B 2C2D2E2F
Task ID
CSIPAX BX CX DX SI DI DS
ES
Peripheraladdress
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050 5051
00060
CB task ID
Control busmessage types
User recordnumber
STATUS LOG 331
STATUS CODES1E0
Entry header
0B Failed to put administrative message in node queue.Offsets: node number.Offsets: return code—see following table.
0C Failed to close administrative message.Offsets: node number.Offsets: return code—see following table.
0D Failed to run Garbage Collect.Offsets: MDS address.Offsets: return code—see following table.
10 Failed to purge usage-based entries.Offsets: zeros.Offsets: return code—see following table.
Offset Label Field Description
14-17 Return Return codes for all subcodes except 0B and 0C:02 Maximum number of records too big.
03 User area specified does not fit.
04 Number of messages does not fit.
05 Size of messages too big for this many entries.
06 Cannot create; already exists.
07 Cannot create new secondary record.
08 Pool of IORBs exhausted.
09 Pool of buffers exhausted for primary record.
0A AMT address insert error.
0B File system protocol error.
0C IUNs exhausted.
0D Control bus I/O error.
0E Cannot add more records.
0F Cannot lock the user record.
10 Cannot unlock the file.
11 User record read error
12 User record write error
13 Cannot abandon the record.
00020 20212223 24252627 2829
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
CSEIP**
* Content depends on subcode
UnusedUnused
332 STATUS LOG
STATUS CODES 1E0
ued:
.
ly.
14-17 Return Return codes for all subcodes except 0B and 0C—contin
14 File does not exist for this filename.
15 Ran outside AMT.
16 AMT signature error time-out.
17 Passed the last entry in AMT belonging to this file
18 AMT entry search error.
19 No entry available for retrieval.
1A Input record number non-existent.
1B Empty user record cannot be deleted.
1C Cannot remove MDS record entry from AMT.
1D MDS internal error.
1E MDS internal error.
1F MDS entry marked.
20 MDS entry not allocated.
21 Entry cannot be stored.
22 File is not direct access type; for direct access on
23 AMT backsearch failed.
24 File number too big (> 9999)
25 User buffer area less than message area.
26 Cannot add new entry to AMT.
Return codes for subcodes 0B and 0C: see sysbnerr.c
Offset Label Field Description
STATUS LOG 333
STATUS CODES1E1
Entry header
IORB header
CB-out messageCB-in message
Registersduring event
Entry header
Registersduring event
1E1 Network Directory Input/Output Error
0E Control bus message return code not OK; system dump.
0F Control bus message return code not OK; return code is in IORB buffer.
1E2 Number of Network Directory Entries Exceeds Critical Space Threshold
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0
Peripheraladdress
CB task ID
Control busmessage types
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
*Unused
Task ID
00020 20212223 24252627 2829
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
UnusedUnusedCS
EIPNode number
Return*
*See table on following page.
334 STATUS LOG
STATUS CODES 1E2
Offset Label Field Description
14-17 Return Return code:0000 No errorsFFD6 Queue overflowFFD7 Unknown destination
FFD8 Unknown messageFFD9 Error detected by CCCFFDA No destination in destination listFFDB Sequence error during retrieval
FFDC Node is in serviceFFDD Error detected by FSFFDE Node is not under deletionFFDF Node is under deletion
FFE0 Bad forward messageFFE1 Out of system buffersFFE2 Record is not in cacheFFE3 Old NR is not in FC
FFE4 Not a voice messageFFE5 No more messages in queueFFE6 More destinations for messageFFE7 Duplicate destination
FFE8 Message is in 4k bufferFFE9 Message is in bufferFFEA Message is in queueFFEB Message is not in 4k buffer
FFEC Message is not in bufferFFED Message/entry is not in queueFFEE Message queue is fullFFEF Not allowed by error history
FFF0 Task limit exceededFFF1 CIP table is fullFFF2 Task ID is not in CIP tableFFF3 Task ID is in CIP table
FFF4 Not home station of this nodeFFF5 Bad message is not in tableFFF6 Bad message table is fullFFF7 Prefix not found
FFF8 Prefix table is fullFFF9 Duplicate prefixFFFA TX is badFFFB Node exists
FFFC Node does not existFFFD Error detected by MDSFFFE Bad input data
STATUS LOG 335
STATUS CODES1E3
Entry header
Registersduring event
Entry header
Registersduring event
1E3 Number of Network Directory Entries Exceeds Directory Full Alarm Threshold
1E4 Network Directory Full
Task ID
00020 20212223 24252627 2829
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
UnusedUnusedCS
EIPNode number
Return*
*See table for 1E2 error.
Task ID
00020 20212223 24252627 2829
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
UnusedUnusedCS
EIPNode number
Return*
*See table for 1E2 error.
336 STATUS LOG
STATUS CODES 1E5
Registersduring event
Entry header
1E5 Aspenet Admin Protocol Error
Usually caused by a bad line condition, a line disconnect or a data formaterror. In the cases of subcodes 01 and 02, the system should automaticallyadapt to the appropriate signalling level. Subcodes 03 and 04 indicate soft-ware errors.
01 Aspenet transmit error.
02 Aspenet receive error.
03 Aspenet encoding error.
04 Aspenet decoding error.
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
Task ID
00020
00000 00010203 04050607 08090A0B 0C0D0E0F
00010
00030
00040
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0*Unused
STATUS LOG 337
STATUS CODES1E6
ontent is garbage.
Entry header
Registersduring eventr
1E6 EDBN Administrative Message Status
The subcode for these status log entries consists of the combined high andlow nibbles (digits), as defined below:
High nibble (left-most digit): Message type
1 Administrative retrieval of ASCII spoken name, transmit.
2 Administrative retrieval of full name, transmit.
3 Administrative retrieval of ASCII spoken name, receive.
4 Administrative retrieval of full name, receive.
5 Administrative change mode.
6 Administrative name confirmation
7 Administrative retrieval of full name from the hub.
Low nibble (right-most digit): Error reason
0 OK.
1 Mailbox type in not allowed in Network Directory.
2 Mailbox does not exist.
3 Mailbox exists, but ASCII name does not match.Offset 10-24: mailbox ASCII name.
4 Mailbox exists, but has no ASCII name.
5 Spoken name not recorded.
6 Cannot access Network Directory.
7 Feature not supported.
8 Spoken name is corrupted.
9 Name added to Network Directory.
A Syntax error in name; name not added.
B More than nine same names in NMT; name not added.
C Cannot update Network Directory.
D Stop protocol; name already exists.
E System full.
Offset Label Field Description
10-24 Mailbox ASCII name Used with subcode X3 only. Otherwise, the c
00020 20212223 24252627 28292A2B 2C2D2E2F
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 343536
Mailbox ASCII name (with subcode X3 only)...... ASCII name
Node numberof destination
Mailbox numbe
UnusedIP CS
Unused of destination
338 STATUS LOG
STATUS CODES 1E7
Entry header
Registersduring eventr
1E7 EDBN Network Directory Access Error
This error is logged when an administrative message fails to access theNetwork Directory (i.e., while the ASCII name or spoken name is updated)or to inform the system administrator of the deletion of a permanent entry inthe Network Directory.
If the subcode’s high nibble is 2 or 3, refer to the subcode’s low nibble todetermine the actual problem; refer to the rest of the status log entry todetermine the specific mailbox causing the error.
If the subcode’s high nibble is 1, then nothing needs to be done becausethe logged entry is informational only.
High nibble (left-most digit): Message type
1 Delete a permanent entry. This is a routine information only opera-tion.
2 Update ASCII name in Network Directory.
3 Update spoken name in Network Directory.
Low nibble (right-most digit): Error reason
0 OK.
1 Mailbox type in not allowed in Network Directory.
2 Mailbox does not exist.
3 Mailbox exists, but ASCII name does not match.Offset 10-24: mailbox ASCII name.
4 Mailbox exists, but has no ASCII name.
5 Spoken name not recorded.
6 Cannot access Network Directory. Call service.
7 Feature not supported.
8 Spoken name is corrupted.
9 Name added to Network Directory.
A Syntax error in name; name not added.
B More than nine same names in NMT; name not added.
C Cannot update Network Directory.
D Stop protocol; name already exists.
00020 20212223 24252627 28292A2B 2C2D2E2F
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 343536
Mailbox ASCII name (with subcode X3 only)...... ASCII name
Node numberof destination
Mailbox numbe
UnusedIP CS
Unused of destination
STATUS LOG 339
STATUS CODES1E7
ontent is garbage.
Offset Label Field Description
10-24 Mailbox ASCII name Used with subcode X3 only. Otherwise, the c
340 STATUS LOG
STATUS CODES 1E8
Entry header
IORB header
CB-out messageCB-in messageRegistersduring event
1E8 Debug Logs Snapshot
01 Snapshot of CP beginning.
02 Snapshot of CP ending.
03 Previous snapshot incomplete; ignore the current snapshot.
04 Control bus error between CP and CC.
05 Control bus error between CP and SFC.
06 Control bus error between CP and MFC.
07 Invalid request to gate call send_snp.
08 Error while writing the debug file.
09 Error while reading the debug file.
0A Error while reading the MFC debug file.
0B Error while reading Record 50.
Offset Label Field Description
10 Flag Possible bit values:0 Not used1 Missing cable2 Local readback failed3 Bad latch value4 Short cable5 Remote station bypassed the latch test6 Remote communication failure
00020 20212223 24252627 28292A2B 2C2D2E2F
Task ID
CS IPAX BX CX DX SI DI DS ES
Peripheraladdress
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
CB task ID
Control busmessage types
STATUS LOG 341
STATUS CODES1F
Entry headerRegistersduring event
Entry headerRegistersduring event
Entry headerRegistersduring event
Entry header
urned _get
1FC Local Lock Error
01 Error in obtaining lock on record in sys_ur_io_read.
02 Error in obtaining lock on record in sys_ur_io_write.
03 Error when abandoning user record (return code from os_ref_rec).
06 Error when locking user record (return code from os_lock).
08 Error in setting the signature (return code from os_ref_rec).
0A Check of lock ownership failed at write (ret code from os_lock_stat).
0B Invalid signature (return code from os_ref_rec).
11 Sequence error.
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B CSEBP EIP
IRN Status (return code from os_rec_ref)
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B CSEBP EIP
Status (return code from os_rec_ref or os_lock)
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B CSEBP EIP
IRN Status (return code from os_rec_ref or os_lock_stat)
00020
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D
CSEIP...EBP
...EIP
IRN
Sequence # retby sys_lur_seqSequence #
from LUR
342 STATUS LOG
STATUS CODES 1FF
Entry header
Registersduring event
Entry header
IORB header
CB-out messageCB-in message
Registersduring event
1FF Protocol Out of Sequence
00 User record sequence error.
07 Wrong response to file system message 28, Read Data.
Task ID
00020 20212223
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
CS
Local memory resident sequence #
EBPIUN UR seq. #EIP
Task ID
00020 20212223 24252627 28292A2B 2C2D2E2F
00000 00010203 04050607 08090A0B 0C0D0E0F
00010 10111213 14151617 18191A1B 1C1D1E1F
00030 30313233 34353637 38393A3B 3C3D3E3F
00040 40414243 44454647 48494A4B 4C4D4E4F
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0
Peripheraladdress
CB task ID
Control busmessage types
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
*Unused
STATUS LOG 343
STATUS CODES200
Entry header
Registersduring event
200 Abnormal System Shutdown
00 System shutdown.
01 Interrupt 3.
02 Divide error.
03 Overflow fault.
04 Bounds check.
05 Illegal Instruction.
06 No co-processor.
07 Double fault.
08 Co-processor segment overrun.
09 Invalid TSS.
0A Segment not present.
0B Stack fault.
0C General protection fault.
0D Page fault.
0E Task crash.
0F Watchdog timer.
10 DRAM parity error.
11 Privilege violation.
12 System crash.
13 Debug register breakpoint.
14 Software breakpoint.
15 Task breakpoint.
16 Snapshot breakpoint.
17 Single-step breakpoint.
Task ID
00020
00000 00010203 04050607 08090A0B 0C0D0E0F
00010
00030
00040
00050
00060
00070
00080
EBP EBX ECXEDX ESI
DS ES FSESP
CSEIPGS
Cause of crash, in ASCII—same as subcodeUnused
EDIEAX
SS
Unused
344 STATUS LOG
STATUS CODES 228
Registersduring event
Entry header
228 Background Task Error
01 Error in creating node queue.
02 Error in waiting on waitm.
03 Error in returned node PQID.
04 Error in getting IVR/BGT privilege.
05 Error in returned mailbox PQID.
06 Invalid request for send to node queue.
07 Node queue full, could not send.
08 Unknown response to send node queue.
09 Error in returned mailbox change PQID.
0A Echo server protocol error.
0B Echo server received unknown event in connection queue.
0C Echo server received unknown event in application queue.
EAX EBX ECX EDIEDX ESI ESP DS ES
FS GS SS * EBP EIPCS
Optional stack dump
Task ID
00020
00000 00010203 04050607 08090A0B 0C0D0E0F
00010
00030
00040
00050
00060
00070
00080
00090
000A0
000B0
000C0
000D0
000E0
000F0*Unused
STATUS LOG 345
CHAPTER 3: FILE SYSTEM MESSAGES
This chapter provides descriptions of all control bus messages used with file cards. For information onreading these descriptions, see “Control Bus Messages” on page 35. All values in the illustrations arethe bytes’ offsets, not sample data.
Request and response messages are grouped together and organized by the message type of therequest. These can be found by checking the numbers in the upper-outer corners of the pages whileflipping through the chapter. Or, message descriptions can be found by checking the index below.
Index
Numerics10 Abandon New Message, 35211 Abandon New Message Response, 35212 Close Name/Announcement, 35313 Close Name/Announcement Response, 35314 Close New Message, 35415 Close New Message Response, 35416 Close Old Message, 35517 Close Old Message Response, 35518 Close Phrase, 35619 Close Phrase Response, 3561A Decrement Use Count, 3571B Decrement Use Count Response, 3571C Increment Use Count, 3581D Increment Use Count Response, 3581E Load Prompt IDs, 3591F Load Prompt IDs Response, 36020 Open Name/Announcement, 36121 Open Name/Announcement Response, 36122 Open New Message, 36223 Open New Message Response, 36224 Open Old Message, 36325 Open Old Message Response, 36326 Open Phrase, 36427 Open Phrase Response, 36428 Read Data, 36529 Read Data Response, 3662A Read Message Buffer, 3672B Read Message Buffer Response, 3682C Read Name/Announcement Buffer, 3692D Read Name/Announcement Buffer Response, 3702E Read Prompt Buffer, 3712F Read Prompt Buffer Response, 371
STATUS LOG 347
30 Set Prompt Level, 37231 Set Prompt Level Response, 37232 Skip to Old Message End, 37333 Skip to Old Message End Response, 37334 Write Data, 37435 Write Data Complete, 37636 Write Data Response, 37537 Write Message Buffer, 37738 Write Message Buffer Complete, 37739 Write Message Buffer Response, 3783A Write Phrase Buffer, 3793B Write Phrase Buffer Complete, 3793C Write Phrase Buffer Response, 3803D Reset A Channel, 3813E Reset A Channel Response, 3813F Install Drive, 38240 Install Drive Response, 38341 General Configuration Response for Primary and Third File Cards, 43142 Checkpoint, 38543 Checkpoint Response, 38544 Space Available Request, 38645 Space Available Request Response, 38746 Garbage Collect Begin, 38947 Garbage Collect Begin Response, 38948 Garbage Collect End, 39149 Garbage Collect End Response, 3914A Garbage Collect Mark Message, 3924B Garbage Collect Mark Message Response, 3924C Check RAM Status, 3934D Check RAM Status Response, 39352 Drive Test, 39453 Drive Test Response, 39454 Drive Verify, 39555 Drive Verify Response, 39656 Drive Copy, 39757 Drive Copy Response, 39858 Return Error Counters, 39959 Return Error Counters Response, 3995A Read Half Record, 4015B Read Record Response, 4015C Write File Record, 4025D Write Record Response, 4025E Write Record Complete, 4035F Get Length Of Old Message, 40460 Get Length Of Old Message Response, 40461 Assign Internal Record Number, 405
348 STATUS LOG
61 General Configuration Response for Secondary File Card, 43162 Assign IRN Response, 40563 Release IRN, 40664 Release IRN Response, 40665 Assign EAR, 40766 Assign EAR Response, 40767 Return EAR, 40868 Return EAR Response, 40869 Release EAR, 4096A Release EAR Response, 4096B Return NODE and EAR Counter, 4106C Return NODE & EAR Counter Response, 4106D Update IUN/INN Record, 4116E Update IUN/INN Record Response, 4136F Update IUN/INN Record Complete, 41371 New Message, 41472 New Message Response, 41473 Additional Message Segment, 41574 Additional Message Response, 41575 Send/Update Message, 41676 Send/Update Message Response, 41777 Start Message Search, 41878 Start Message Search Response, 41879 Return Next Message, 4197A Return Next Message Response, 4207B Return Next Segment, 4217C Return Next Segment Response, 4217D Return Destinations of the Message, 4227E Return Destination Response, 4237F Partial Read IUN/INN Record, 42480 Partial Read IUN/INN Record Response, 42481 Build XREF Tables, 42582 Build XREF Tables Response, 42583 Check INN, 42684 Check INN Response, 42685 Update Node Field, 42786 Update Node Field Response, 42787 Update Node Field Complete, 42888 Return Number of Messages in Node, 42989 Return Number of Messages in Node Response, 42990 Add Bad Track, 43091 Add Bad Track Response, 430AA1 General Configuration Status Request, 431A2 General Read Memory, 432A3 General Write Memory, 432
STATUS LOG 349
A4 Return Code Level, 433A5 Set DMA Test, 435A6 General Utility Command, 436A7 CDR Utility Command, 461BB2 General Read Memory Response, 432B3 General Write Memory Response, 432B4 Return Code Level Response, 434B5 Set DMA Test Response, 435B6 General Utility Command Response, 446B7 CDR Utility Command Response, 461CC0 New Message Primitives, 462C1 New Message Primitives Response, 464C2 Phrase Table Primitives, 468C3 Language Area Primitives Response, 475C4 New Garbage Collect Primitives, 478C5 New Garbage Collect Primitives Response, 479C6 Miscellaneous Commands, 481C7 Miscellaneous Commands Response, 487C8 New Data File Primitives, 494C9 New Data File Primitives Response, 502CA New Data File Primitives Write Complete, 504CB Get Phrase Table Pointers, 505CC Get Phrase Table Pointers Response, 506CD Put Phrase Table Pointer, 507CE Put Phrase Table Pointer Response, 507DD0 Message Information File Operation, 508D1 Message Information File Operation Response, 508D2 Put Message Information File Entry, 510D3 Put Message Information File Entry Response, 510FFE CP Software Synchronization, 517
350 STATUS LOG
FILE SYSTEM MESSAGES10
tem message 22,
e ID).
000000
3.1 MESSAGE DESCRIPTIONS
10 Abandon New Message
Requests the file system to delete the new message and return to the high-level message protocol.
11 Abandon New Message Response
00 OK.
01 Unrecoverable drive error. The message’s state is unchanged.
02 Scramble code or message ID mismatch (software error). Message state is unchanged.
03 No new message open.
06 DMA time-out on prior operation. System reboot required.
Offset Label Field Description
03-04 Message ID Redundant here. It must match the ID given in file sysOpen New Message.
Offset Label Field Description
0B-0C Miscellaneous Scramble code (least-significant byte of the messag
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Message ID
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Miscellaneous
352 STATUS LOG
FILE SYSTEM MESSAGES 12
em message 20, Open
12 Close Name/Announcement
13 Close Name/Announcement Response
00 OK.
02 Scramble code or message ID mismatch (software error). Name/announcement state is unchanged.
03 No name/announcement open.
Offset Label Field Description
03-04 Message ID Redundant here. It must match the ID given in file systName/Announcement.
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Message ID
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
STATUS LOG 353
FILE SYSTEM MESSAGES14
em message 22, Open
ro.
14 Close New Message
Requests the file system to permanently store the new message (that is,enter it into the message chain and set its use count) and return to the high-level message protocol.
15 Close New Message Response
00 OK.
01 Unrecoverable drive error. Message state is unchanged.
02 Scramble code or message ID mismatch (software error). Message state is unchanged.
03 No new message open.
04 No data written.
06 DMA time-out on prior operation. System re-boot required.
Offset Label Field Description
03-04 Message ID Redundant here. It must match the ID given in file systNew Message.
05-06 Use count Use count to set for message. Must be greater than ze
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Message ID
Use count
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
354 STATUS LOG
FILE SYSTEM MESSAGES 16
em message 24, Open
16 Close Old Message
Requests termination of the Read Old Message protocol and return to thehigh-level message protocol.
17 Close Old Message Response
00 OK.
01 Unrecoverable drive error (FS386 only)
02 Scramble code or message ID mismatch (software error). Message state is unchanged.
03 No old message open..
Offset Label Field Description
03-04 Message ID Redundant here. It must match the ID given in file systOld Message.
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Message ID
FSCP
➤00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
STATUS LOG 355
FILE SYSTEM MESSAGES18
given in file system
1.
1.
18 Close Phrase
19 Close Phrase Response
00 OK. Offset 04-0C are unused.
01 Unrecoverable drive error. Phrase state is unchanged.
02 Phrase ID mismatch (software error). Phrase state is unchanged.
03 No phrase open.
04 No data written. Next phrase operation must be file system message 26, Open Phrase.
06 DMA time-out on prior operation. System re-boot required. Offset 04-0C are unused.
07 Incorrect phrase table.
Offset Label Field Description
03-04 Phrase number Redundant here. It must match the phrase numbermessage 26, Open Phrase.
Offset Label Field Description
05 Drive action See Table 3-1, “Drive Action Codes,” on page 51
08 Drive status See Table 3-2, “Drive Status Codes,” on page 51
0A Language number Used only when working on a phrase record.
0B-0C Phrase number Used only when working on a phrase record.
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Phrase number
FSCP
➤00010203 04050607 08090A0B 0C0D0E0F
Task ID Record IDDrive
number
Driveaction
Drivestatus
Language number
Phrasenumber
*
*Unused
356 STATUS LOG
FILE SYSTEM MESSAGES 1A
is field is only used for
ment the use count.
the message when its
1A Decrement Use Count
Causes the file system to decrement the use count of a message and, if theuse count becomes zero, delete the message from the system. The scram-ble code is included for verification.
1B Decrement Use Count Response
00 OK.
01 Unrecoverable drive error.
02 Scramble code or message ID mismatch (software error or deleted message).
04 Use count is zero (software error or deleted message).
06 DMA time-out on prior operation. System re-boot required.
Offset Label Field Description
07-08 User record in area A Number of the user record in area A, if any. Thtroubleshooting.
09-0A Decrement-count flag If greater than zero, the file system will decre
0B Delete-message flag If greater than zero, the file system will deleteuse count becomes zero.
CP➤FS
Task ID
00010203 04050607 08090A0B 0C0D0E0F
Message ID
Scramble
Delete-message flag
code
User recordin area A
Decrement-count flag
Unused
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
STATUS LOG 357
FILE SYSTEM MESSAGES1C
1C Increment Use Count
1D Increment Use Count Response
00 OK.
01 Unrecoverable drive error.
02 Scramble code or message ID mismatch (software error or deleted message).
04 Use count is zero (software error or deleted message).
06 DMA time-out on prior operation. System reboot required.
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID Message ID
Scramble
Unused
Increment count (if>0)code
Unused
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task IDMessage length,
Unused
in bytes of speech
358 STATUS LOG
FILE SYSTEM MESSAGES 1E
in this request. This is
tem message 2E,
1E Load Prompt IDs
Adds up to four prompt IDs to the list of prompts to be retrieved.
Offset Label Field Description
03 Options A flag field, the value is a sum of:01 (Bit 0 set.) Clear prompt ID list before adding the IDs
the beginning of a prompt request sequence.02 (Bit 1 set.) Last load. The next request will be file sys
Read Prompt Buffer.04 (Bit 2 set.) “Prompt IDs” are really phrase numbers.
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID Options
Number ofprompt IDs
Prompt IDs
STATUS LOG 359
FILE SYSTEM MESSAGES1F
1F Load Prompt IDs Response
Return codes 00-06 are used with prompt IDs (in the request message, bit 2of offset 03 is zero). Return codes 00 and 0A-0F are used with phrase num-bers (in the request message, bit 2 of offset 03 is one).
If there is a problem, run phrase verify/garbage collect to determine whichlanguage area is involved.
00 Meaning depends on bit 2 in offset 03 of the request message.
Bit 2=0: OK.Bit 2=1: Phrase on disk. Continue playback sequence.
01 Too many prompt ID’s (list overflow).
02 Bad prompt ID.
03 Phrase not recorded.
04 Obsolete phrase.
05 Null phrase, cancel playback.
06 Invalid phrase ID in formatted play table.
0A Phrase is in RAM. Continue playback sequence.
0B Phrase not stored. Cancel playback sequence.
0C Phrase is obsolete. Cancel playback sequence.
0D Bad record, full. Cancel playback sequence.
0E Bad record, first half. Cancel playback sequence.
0F Bad record, second half. Cancel playback sequence.
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Prompt ID or phrase number
Language number(values: 01-05)
(return codes 02, 03 and 04 only)
360 STATUS LOG
FILE SYSTEM MESSAGES 20
is field is only used for
is field is only used for
20 Open Name/Announcement
Initiates processing of an old message as a name/announcement (that is,one which will not be repositioned during reading).
21 Open Name/Announcement Response
00 OK.
01 Unrecoverable drive error. Name/announcement state is unchanged.
0 2 Scramble code or message ID mismatch (software error or deleted message). Name/announcement state is unchanged.
03 Name/announcement is already open. Previous one is left open.
04 Use count is zero (software error or deleted message). Name/announcement state is unchanged.
06 DMA time-out on prior operation. System re-boot required.
07 Checksum error.
Offset Label Field Description
07-08 User record in area A Number of the user record in area A, if any. Thtroubleshooting.
09-0A User record in area B Number of the user record in area B, if any. Thtroubleshooting.
CP➤FS
00010203 04050607 08090A0B
Task ID Message ID
Scramble code User record in area B
User record in area A
Unused
FSCP
➤
00010203
Task ID
Unused
STATUS LOG 361
FILE SYSTEM MESSAGES22
when offset 03 holds
22 Open New Message
Initiates the recording of a user message.
23 Open New Message Response
If the return code is 00 (OK), the Write New Message protocol is initiated.Otherwise, control remains in the high-level message protocol.
00 OK.
01 Unrecoverable drive error. Message is not opened.
03 Message is already open. Message state is unchanged.
04 No space left on disk. Message is not opened.
12 Free space table corrupted.
Offset Label Field Description
03 Scramble code source 00 Generate new scramble code.01 Use scramble code in offset 04-05.
04-05 Scramble code Scramble code for new message. Used only01.
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Scramble
Scramble code
code source
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Message ScrambleID code
Used only withreturn code 00
362 STATUS LOG
FILE SYSTEM MESSAGES 24
, if known. This field is
24 Open Old Message
Initiates processing of an old (pre-existing) message.
25 Open Old Message Response
If the return code is 00 (OK), the Read Old Message protocol is initiated.Otherwise, control remains in the high-level message protocol.
00 OK.
01 Unrecoverable drive error. Message state is unchanged.
02 Scramble code or message ID mismatch (software error or deleted message.) Message state is unchanged.
03 Message already open. Message state is unchanged.
04 Use count is zero (software error or deleted message). Message state is unchanged.
06 DMA time-out on prior operation. System re-boot required.
Offset Label Field Description
07-08 User record Number of the user record which contains the messageonly used for troubleshooting.
Offset Label Field Description
04-07 Message length Length of message, in bytes of speech.
08 Forms flag 00 Not a forms message01 Forms message
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Message ID
Scramble code
User record
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID Message length
Forms flag
Scramble code (from voice record)
Unused
STATUS LOG 363
FILE SYSTEM MESSAGES26
26 Open Phrase
27 Open Phrase Response
00 OK.
01 Illegal language number. Phrase state is unchanged.
02 Illegal phrase number. Phrase state is unchanged.
03 Phrase already open. Phrase state is unchanged.
04 Drive error.
05 Drive full.
Offset Label Field Description
04-05 Flags Value is sum of:01 (Bit 0 set.) Phrase is obsolete and is not being stored.02 (Bit 1 set.) Phrase is duplicate and is not being stored.
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Phrase number
Languagenumber (00-04)
(0000-0ED7)
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Flags
364 STATUS LOG
FILE SYSTEM MESSAGES 28
ge 512.
.2,
uffer):
28 Read Data
Sent by the CP to request reading of non-speech information. For multiplerecord requests, as many complete records as will fit on a track are read,starting with the record specified by offset 05-06, which must be on a trackboundary.
For data types 15, 16, and 17, the message will show FFFF instead of 2800at offsets 02 and 03. You can tell that the message type should be inter-preted as 28 because it will be followed by message type 29.
Offset Label Field Description
03 Priority flag 00 High priority01 Low priority
04 Data type See Section 3.2.2, “Read and Write Data Types,” on pa
05-06 Parameter Depends on the data type in offset 04. See Section 3.2“Read and Write Data Types,” on page 512.
07-08 Length Maximum number of bytes to read (that is, size of CP b15 Community number—1k byte16 Attendant schedule—512 bytes17 Multiple community—10k bytes
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task IDPriority
Data type Length
Parameterflag
Unused
STATUS LOG 365
FILE SYSTEM MESSAGES29
ch.
carry add starting with lete ones are filled with
29 Read Data Response
Sent by the file system when it is ready for DMA after reading data, or toindicate an error.
If the data type in offset 04 of the request message is 18 (raw phrase), thereturn code will indicate the last buffer of the phrase (state of phrase isclosed) by setting the high-order digit to 8. For example, 80 would indicatethe last buffer and OK.
00 OK.
01 Unrecoverable drive error.
02 Illegal data type.
03 No changed user record, node not assigned, or not an opened phrase.
04 Bad user or node number.
05 Obsolete data file.
06 DMA time-out on prior operation. System re-boot required.
07 Went past end of file.
08 Invalid length.
09 Sequence number earlier than current block.
0A Not first block to be read.
0B Bad block.
Offset Label Field Description
04-05 Length Length of data read, or length of phrase in bytes of spee
06-09 Checksum Checksum of data read. Checksum is 4-byte end-aroundCA410ABE. The 4-byte words are in Intel order; incomphigh-order zeroes.
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Length
Checksum
366 STATUS LOG
FILE SYSTEM MESSAGES 2A
em message sage 23, Open
ytes of speech.
. This field is
2A Read Message Buffer
Sent by the CP when a line card is ready to receive a buffer of speech.
Offset Label Field Description
03-04 Message ID Redundant here. It must match the ID given in file syst22, Open Old Message or returned by file system mesNew Message Response.
05-08 Position Position to read, relative to beginning of message, in b
09 DMA Flag 00 Perform DMA to line task.01 Do not perform DMA to line task.
0B-0C User record Number of the user record with the message, if knownused only for troubleshooting.
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID Message ID
Position
DMA Flag
Unused
User record
STATUS LOG 367
FILE SYSTEM MESSAGES2B
2B Read Message Buffer Response
Sent by the file system when it is ready for DMA to send a speech buffer orto indicate that an error occurred in reading a speech buffer. The buffer maybegin before the position specified by the request message, but therequested position must be in the buffer. The position of the beginning ofthe buffer is returned so that the offset of the requested position may bedetermined.
00 OK.
01 Unrecoverable drive error. Message state is unchanged.
02 Scramble code or message ID mismatch (software error or deleted message). Message state is unchanged.
03 Requested position is past end of message. Message state is unchanged.
07 Line card checksum error.
11 Drive unavailable.
Offset Label Field Description
04 Flags 01 (Bit 0 set.) Last buffer in message.02 (Bit 1 set.) Forms-marked message buffer.
05-08 Length Length of speech in buffer, in bytes of speech.
09-0C Position Position of beginning of buffer, relative to begin-ning of message, in bytes of speech.
0D-0E Miscellaneous Scramble code (LSB of message ID).
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Flags
Length Position
Miscellaneous
368 STATUS LOG
FILE SYSTEM MESSAGES 2C
ystem mes-
y the system.
is used only
is used only
2C Read Name/Announcement Buffer
Sent to the file system when a line card is ready to receive a speech bufferwith a name or announcement.
Offset Label Description of Packet Data
03-04 Message ID Redundant here. It must match the ID given in file ssage 20, Open Name/Announcement.
05 Reread flag 00 Read next buffer.01 Reread previous buffer.
06-07 Scramble code This is here only for troubleshooting; it is not used b
08-09 User recordin area A
Number of the user record in area A, if any. This fieldfor troubleshooting.
0A-0B User recordin area B
Number of the user record in area B, if any. This fieldfor troubleshooting.
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Message ID Scramblecode
Reread flag User record in area A
User record in area B
Unused
STATUS LOG 369
FILE SYSTEM MESSAGES2D
e ID).
2D Read Name/Announcement Buffer Response
Sent by the file system when it is ready for DMA to send a speech bufferwith a name or announcement to a line card.
00 OK.
01 Unrecoverable drive error. Name/announcement state is unchanged.
02 Scramble code or message ID mismatch (software error or deleted message). Name/announcement state is unchanged.
03 Name/announcement not open.
06 DMA time-out on prior operation. System reboot required.
07 Line card checksum error.
Offset Label Description of Packet Data
04 Last-buffer flag 00 This is not the last buffer.01 This is the last buffer.
09-0A Miscellaneous Scramble code (least-significant byte of the messag
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Last-Length of speech,
Miscellaneous
Unused
bufferflag in bytes of speech
370 STATUS LOG
FILE SYSTEM MESSAGES 2E
2E Read Prompt Buffer
Sent to the file system when a line card is ready to receive a speech buffer.
2F Read Prompt Buffer Response
Sent by the file system when it is ready for DMA to send a speech buffer toa line card.
00 OK.
01 Unrecoverable drive error. Prompt state is unchanged.
02 Past end of prompt list.
03 No prompt list built.
06 DMA time-out on prior operation. System re-boot required.
Offset Label Field Description
03-04 Flags 00 Read next buffer.01 Reread last buffer.
Offset Label Field Description
04-05 Last-buffer flag 00 Not the last buffer.01 Last buffer for all prompts in list.
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Flags
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Last-bufferflag
Length of speech,in bytes of speech
STATUS LOG 371
FILE SYSTEM MESSAGES30
30 Set Prompt Level
31 Set Prompt Level Response
Offset Label Field Description
03 Prompt level 00 Language 1, rapid prompts01 Language 1, standard prompts02 Language 1, extended prompts
03 Language 2, rapid prompts04 Language 2, standard prompts05 Language 2, extended prompts
06 Language 3, rapid prompts07 Language 3, standard prompts08 Language 3, extended prompts
09 Language 4, rapid prompts0A Language 4, standard prompts0B Language 4, extended prompts
0C Language 5, rapid prompts0D Language 5, standard prompts0E Language 5, extended prompts
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID Prompt level
Unused
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
372 STATUS LOG
FILE SYSTEM MESSAGES 32
m message 24, Open
, if known. This field is
32 Skip to Old Message End
33 Skip to Old Message End Response
01 Unrecoverable drive error. Message state is unchanged.
02 Scramble code or message ID mismatch (software error or deleted message). Message state is unchanged.
03 No old message open.
04 Use count is zero (software error or deleted message). Message state is unchanged.
06 DMA time-out on prior operation. System re-boot required.
Offset Label Field Description
03-04 Message ID Redundant here. It must match the ID given in file systeOld Message.
07-08 User record Number of the user record which contains the messageonly used for troubleshooting.
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Message ID
Scramble code
User record
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
STATUS LOG 373
FILE SYSTEM MESSAGES34
e 512.
2,
ffer):
34 Write Data
Sent by the CP to request writing of non-speech information.
Following this request message will be a response message indicating thatthe file system is ready to start writing. Following that will be a “complete”message indicating that the writing is finished.
Offset Label Field Description
03 Options Bit 0 sets the priority. Bit 1 sets the writing method.00 High priority, standard data write01 Low priority, standard data write02 High priority, special XDLD data write03 Low priority, special XDLD data write
04 Data type See Section 3.2.2, “Read and Write Data Types,” on pag
05-06 Parameter Depends on the data type in offset 04. See Section 3.2.“Read and Write Data Types,” on page 512.
07-08 Length Maximum number of bytes to read (that is, size of CP bu15 Community number—1k byte16 Attendant schedule—512 bytes17 Multiple community—10k bytes
09-0C Checksum Checksum of data.
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Data type Length
Parameter ChecksumOptions
374 STATUS LOG
FILE SYSTEM MESSAGES 36
36 Write Data Response
Sent by the file system when it is ready for DMA transfer of data to be writ-ten.
00 OK.
01 Unrecoverable drive error.
02 Illegal data type.
03 Write changed user record or node not assigned error.
04 Bad user or node record number.
06 DMA time-out on prior operation. System re-boot required.
07 Went past end of file.
08 Invalid length.
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
STATUS LOG 375
FILE SYSTEM MESSAGES35
35 Write Data Complete
Sent by the file system at the end of a data transfer and data write.
00 OK.
01 Unrecoverable drive error.
02 Checksum error on data transferred from CP.
03 Not an opened phrase.
04 No more space.
06 DMA time-out on prior operation. System re-boot required.
10 Attempted to write a record 0 or 1 with data of the incorrect format.
11 Illegal attempt to write data on cylinder 0.
12 RAM error was detected when write attempted to get a new record.
13 RAM format was incorrect when attempting to write record 0 or 1.
70 Validity check error.
E1 Invalid data in fifth user record of track.
E2 Invalid data in fourth user record of track.
E3 Invalid data in third user record of track.
E4 Invalid data in second user record of track.
E5 Invalid data in first user record of track.
E7 Invalid SST data.
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
376 STATUS LOG
FILE SYSTEM MESSAGES 37
age ID returned by file
) byte of the length ofo indicates that it is not-marked.
ytes of speech. A posi- the remainder of the ech buffer boundary.
37 Write Message Buffer
Sent by the CP when a line card is ready to send a buffer of recordedspeech.
Following this request message will be a response message indicating thatthe file system is ready to start writing. Following that will be a “complete”message indicating that the writing is finished.
38 Write Message Buffer Complete
Sent when a buffer of speech has been written to disk.
00 OK.
01 Unrecoverable drive error. Message state is unchanged.
06 DMA time-out on prior operation. System re-boot required.
08 Line card checksum error.
10 Attempted to write a record 0 or 1 with data of the incorrect format.
11 Illegal attempt to write data on cylinder 0.
12 RAM error was detected when write attempted to get a new record.
13 RAM format was incorrect when attempting to write record 0 or 1.
Offset Label Field Description
03-04 Message ID The message ID is redundant. It must match the messsystem message 23, Open New Message Response.
05-08 Length Length of buffer, in bytes of speech. The upper (MSBspeech indicates “forms-marked” message buffer. Zerforms-marked; any other value indicates that it is forms
09-0C Position Position to write, relative to beginning of message, in btion prior to the end of the message implies erasure ofmessage before writing. The position must be on a spe
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID Message ID
Length
Position
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
STATUS LOG 377
FILE SYSTEM MESSAGES39
39 Write Message Buffer Response
Sent when the file system is ready for DMA to receive a buffer of speech.
00 OK.
01 Unrecoverable drive error. Message state is unchanged.
02 Scramble code or message ID mismatch (software error). Message state is unchanged.
03 No new message open.
04 Bad position. Message state is unchanged.
05 Disk is full after the current write. Further writes will get return code 07.
06 DMA time-out on prior operation. System re-boot required.
07 Disk full. Current write cannot be done.
08 System is full after the current write.
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
378 STATUS LOG
FILE SYSTEM MESSAGES 3A
pen Phrase.
1.
1.
3A Write Phrase Buffer
Following this request message will be a response message indicating thatthe file system is ready to start writing. Following that will be a “complete”message indicating that the writing is finished.
3B Write Phrase Buffer Complete
Sent when a buffer of speech has been written to disk.
00 OK.
01 Unrecoverable drive error.
06 DMA time-out on prior operation. System re-boot required.
10 Attempt to write a record 0 or 1 with data of the incorrect format.
11 Illegal attempt to write data on cylinder 0.
12 RAM error was detected when write attempted to get a new record.
13 RAM format was incorrect when attempting to write record 0 or 1.
2F Out of space.
Offset Label Field Description
03-04 Phrase number Must match that given in file system message 26, O
Offset Label Field Description
05 Drive action See Table 3-1, “Drive Action Codes,” on page 51
08 Drive status See Table 3-2, “Drive Status Codes,” on page 51
0A Language number Used only when working on a phrase record.
0B-0C Phrase number Used only when working on a phrase record.
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Phrase numberLength of buffer,in bytes of speech
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID Record IDDrive
number
Driveaction
Drivestatus
Language number
Phrasenumber
*
*Unused
STATUS LOG 379
FILE SYSTEM MESSAGES3C
3C Write Phrase Buffer Response
00 OK.
02 Phrase number mismatch. Phrase state unchanged.
03 No phrase open.
04 Half buffer last time (file system software error).
06 DMA time-out on prior operation. System re-boot required
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
380 STATUS LOG
FILE SYSTEM MESSAGES 3D
3D Reset A Channel
The sequence number will be returned in the response message to coordi-nate multiple reset messages (that is, if response is slow).
3E Reset A Channel Response
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Sequence number
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Sequence number
STATUS LOG 381
FILE SYSTEM MESSAGES3F
ith actions B0 and B3. language.
0 and B3.
ns B0 and B3.
3F Install Drive
80 Install drive 0.
97 Install drive 23.
98 De-install drive 0.
AF De-install drive 23.
B0 System initialization (de-install all drives and reinstall 0 and M0).
B1 Install drive 1 for redundant data only.
B2 Make message space available on drive 1 (previously installed for redundant data).
B3 Recover record 0 (same as B0 except that database is not altered).
B4 Replace message drive 0.
C3 Replace message drive 15.
Offset Label Field Description
05 Redundant-message flag Used with actions 80-97 and B0.00 No redundant messages01 Redundant messages
06-07 User record count Used with action B0.
08 Number of languages Set number of languages: 01-05. Used wMust have Maxtor drive for more than one
09 CDR buffer size Set CDR buffer size. Used with actions B01 2 records02 202 records03 7020 records (assumed)
0A Number of group lists Set number of group lists. Used with actio01 5002 2060 (assumed)
CP➤FS…
……
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Unused
User record
Redundant- Number of
CDR buffer size
Number ofmessage flag
count
group listslanguages
382 STATUS LOG
FILE SYSTEM MESSAGES 40
1.
1.
40 Install Drive Response
Offsets 04-0C are used only if the return code in offset 03 is 01 (unrecover-able drive error) or involves phrases. References to primary and secondarydrives are about redundant pairs.
00 OK.
01 Unrecoverable drive error.
02 Illegal drive number.
03 Drive already installed on attempt.
04 Illegal parameter.
05 Attempt to install odd drive as redundant.
06 Could not select primary drive to be installed.
07 Could not read serial number of primary drive.
08 Validity check error on record 1 of primary drive.
09 Insufficient spares on primary drive.
0A Error when writing new spares on record 1 of primary drive.
0B Serial number from primary drive matches serial number of a drive already installed.
0C Could not select secondary drive to be installed.
0D Could not read serial number of secondary drive.
0E Validity check error on record 1 of secondary drive.
0F Insufficient spares on secondary drive.
10 Error when writing new spares on record 1 of secondary drive.
11 Serial number from secondary drive matches serial number of a drive already installed.
14 Attempt to de-install odd drive, which is redundant.
15 Number of users is incorrect.
16 Attempt to de-install drive that is not installed.
17 Write to record 0 or 1 failed.
Offset Label Field Description
05 Drive action See Table 3-1, “Drive Action Codes,” on page 51
08 Drive status See Table 3-2, “Drive Status Codes,” on page 51
0A Language number Used only when working on a phrase record.
0B-0C Phrase number Used only when working on a phrase record.
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID Record IDDrive
number
Driveaction
Drivestatus
Language number
Phrasenumber
*
*Unused
STATUS LOG 383
FILE SYSTEM MESSAGES40
1.
1.
18 Failed on clearing data base 4 = track, 6 = alternate track.
19 (0) Could not get buffer.
1A (1) Illegal qualifier in data type.
1B (2) Copy from 0 to 1 failed—read.
1C (3) Copy from 0 to 1 failed—write.
1D Drive 1 msg control bits invalid.
1E Drive 1 not now installed as data only.
1F No select.
20 Could not read record 0.
21 Could not read used phrase list.
22 Could not read full phrase.
23 Phrase number is wrong—full phrase.
24 Format error—full phrase.
25 Could not write full phrase.
26 Could not write used phrase list.
27 (34) for first half record short phrase.
28 (35) for first half record short phrase.
29 (36) for first half record short phrase.
2A (37) for first half record short phrase.
2B (34) for second half record short phrase.
2C (35) for second half record short phrase.
2D (36) for second half record short phrase.
2E (37) for second half record short phrase.
2F Out of space.
Offset Label Field Description
05 Drive action See Table 3-1, “Drive Action Codes,” on page 51
08 Drive status See Table 3-2, “Drive Status Codes,” on page 51
0A Language number Used only when working on a phrase record.
0B-0C Phrase number Used only when working on a phrase record.
00010203 04050607 08090A0B 0C0D0E0F
Task ID Record IDDrive
number
Driveaction
Drivestatus
Language number
Phrasenumber
*
*Unused
384 STATUS LOG
FILE SYSTEM MESSAGES 42
42 Checkpoint
43 Checkpoint Response
01 Unrecoverable drive error.
02 File card RAM fail. Re-boot required.
06 DMA time-out on prior operation. System re-boot required.
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Checksum flag(>00: OK to checksum)
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
STATUS LOG 385
FILE SYSTEM MESSAGES44
44 Space Available Request
Offset Label Field Description
03 Action 00 Get space for messages (pre-FCP command).02 Get space for phrases.03 Get used message space.04 Get drive state.
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID Action
Unused
386 STATUS LOG
FILE SYSTEM MESSAGES 45
us of drives 0-7 respec-stalled drives.
s of drives 0-7 respec-nning drives.
including overhead. To 8 07.
essages or phrases the bytes in the follow-
tus of drives 8-15 icate installed drives.
tus of drives 8-15 icate running drives.
es disabledy user
45 Space Available Request Response
The format depends on the option setting in offset 03 of the request mes-sage.
Actions 00 and 02
Offset Label Field Description
03 Map fordrives installed (drives 0-7)
Bitmap of installed drives. Bits 0-7 indicate the stattively. To read, convert to binary. Set bits indicate in
04 Map fordrives running (drives 0-7)
Bitmap of running drives. Bits 0-7 indicate the statutively. To read, convert to binary. Set bits indicate ru
05,07-08
Total space Total number of 16-kilobyte records in file system, read, arrange the bytes in the following order: 05 0
06,09-0A
Available space Number of 16-kilobyte records available for new m(depending on the option setting). To read, arrangeing order: 06 0A 09.
0B Map fordrives installed (drives 8-15)
Bitmap of installed drives. Bits 8-15 indicate the starespectively. To read, convert to binary. Set bits ind
0C Map fordrives running (drives 8-15)
Bitmap of running drives. Bits 8-15 indicate the starespectively. To read, convert to binary. Set bits ind
0D-0E Map of drives disabled by user
Bitmap of drives disabled via SMT by the user.
FSCP
➤
Task ID
Map for installed
Map for runningdrives (0-7)
Available space(offset 06 is
Total space(offset 05 is
drives (0-7) most-significant
most-significantbyte)
Map for runningdrives (8-15)
Map for installed
byte) drives (8-15)
Map of drivwith SMT b
00010203 04050607 08090A0B 0C0D0E
Unused
STATUS LOG 387
FILE SYSTEM MESSAGES45
essages.
including overhead.
essages.
d
d
Action 03
Action 04
Offset Label Field Description
03-06 Used message space
Number of 16-kilobyte records currently used for m
07-0A Total space Total number of 16-kilobyte records in file system,
0B-0E Availablemessage space
Number of 16-kilobyte records available for new m
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unuse
Used message space,number of 16 kB records
Available message space,number of 16 kB records
Total space,number of 16 kB records
Task ID
Unuse
Bitmap of Bitmap of devicesrunning drives present on system
Bitmap of Bitmap of drivesdisabled by userinstalled drives
00010203 04050607 08090A
388 STATUS LOG
FILE SYSTEM MESSAGES 46
1.
1.
46 Garbage Collect Begin
47 Garbage Collect Begin Response
The format varies with the return code in offset 03. For return code 01 orreturn codes involving phrases, use the format below. For all other returncodes, use the format on the next page.
01 Unrecoverable drive error.
04 Invalid language number.
05 Verify failed.
Offset Label Field Description
05 Drive action See Table 3-1, “Drive Action Codes,” on page 51
08 Drive status See Table 3-2, “Drive Status Codes,” on page 51
0A Language number Used only when working on a phrase record.
0B-0C Phrase number Used only when working on a phrase record.
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID Drive to garbage collect
Unused
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID Record IDDrive
number
Driveaction
Drivestatus
Language number
Phrasenumber
*
*Unused
STATUS LOG 389
FILE SYSTEM MESSAGES47
set 04 (Lo), bits 0-7 t 06 (Hi), bits 0-3 indi- convert to binary. Set
e installed and usable. 0-7 respectively. Offset spectively. To read,
If offsets 04 and 05 do not match, or if the return code is not 00, the opera-tion did not start.
00 OK.
06 DMA time-out.
07 Installed drives not equal running drives or incorrect free space table.
08 Drive 0 of this file card not installed.
09 Drive 1 of this file card not installed.
0A M2 not installed.
0B M3 not installed.
0C M4 not installed.
0D M5 not installed.
0E M6 not installed.
0F M7 not installed.
10 M8 not installed.
11 M9 not installed.
12 M10 not installed.
13 M11 not installed.
14 M12 not installed.
Offset Label Field Description
04, 06 Map fordrives initialized
Bit map of the drives that have been initialized. Offindicate the status of drives 0-7 respectively. Offsecate the status of drives 8-11 respectively. To read,bits indicate initialized drives.
05, 07 Map fordrives running
Bit map of the drives that the system considers to bOffset 05 (Lo), bits 0-7 indicate the status of drives 07 (Hi), bits 0-3 indicate the status of drives 8-11 reconvert to binary. Set bits indicate running drives.
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Map for drives initialized
Map for drives running
Lo HiLo Hi
390 STATUS LOG
FILE SYSTEM MESSAGES 48
1.
1.
48 Garbage Collect End
49 Garbage Collect End Response
Offsets 04-0C are used only if the return code in offset 03 is 01 (unrecover-able drive error) or involves phrases.
00 OK.
01 Unrecoverable drive error.
Offset Label Field Description
05 Drive action See Table 3-1, “Drive Action Codes,” on page 51
08 Drive status See Table 3-2, “Drive Status Codes,” on page 51
0A Language number Used only when working on a phrase record.
0B-0C Phrase number Used only when working on a phrase record.
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID Record IDDrive
number
Driveaction
Drivestatus
Language number
Phrasenumber
*
*Unused
STATUS LOG 391
FILE SYSTEM MESSAGES4A
ed with two 4-bit num-
nel of the Peripheral
Slot of the Peripheral the peripheral address ssage for help in identi-
000000
4A Garbage Collect Mark Message
4B Garbage Collect Mark Message Response
00 OK.
01 Unrecoverable drive error. Message is not marked.
02 Scramble code or message ID mismatch.
03 Scramble code or message ID mismatch. Message is not marked.
04 Use count is zero. Message is not marked.
05 Message was already marked—should not be counted again.
Offset Label Field Description
04 Port Port on which the message was recorded. The port is identifibers:
Channel. Port on a line card. Interpret with Table 1-9, “ChanAddress,” on page 31.Slot. Card within a bank. Interpret with Table 1-8, “Bank and Address,” on page 30. Since the bank is not identified, checkin offset 04-05 of the IORB header and the task ID of the mefying the card.
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Message ID
Scramble code
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID Port
Number of blocks
Message length,
Number of bytesin message
including silence,in bytes of speech
of speech stored
04Channel Slot
03 0405
392 STATUS LOG
FILE SYSTEM MESSAGES 4C
4C Check RAM Status
Checks location 2D00 in static RAM for the value 5ABC. Then it computes achecksum for data stored in static RAM and checks it with the value storedthere in power down.
4D Check RAM Status Response
00 OK.
02 Bad static RAM: bad checksum or not enough power to hold data.
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
STATUS LOG 393
FILE SYSTEM MESSAGES52
52 Drive Test
Tests only the free spaces on the drive by writing and reading random pat-terns to the record.
53 Drive Test Response
The format of this control bus message depends on the system type andwhether the error is a hard or soft disk error.
00 OK.
>00 Valid entry present.
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID Drive number
Number of records to test
Unused
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID Request
Drive
Cylinder
Head
Sector
Numberof sectorsnumber
Error type, see Table 3-5, “Internal File Card Status Codes,” on page 516
394 STATUS LOG
FILE SYSTEM MESSAGES 54
as a four-bit number
ns all languages.
as a four-bit number
continuation, and 1-5
ses
ates an initial verify. upon continuation.
e
pe
54 Drive Verify
80 Verify software.
81 Verify phrases.
82 Verify system data tables.
83 Verify entire system.
Offset Label Field Description
04 Verify type & language This field is actually two. Each is expressed(one hex digit) as shown below.
Language. Valid values are 1-5, and F meaVerify type:
0 Pre-copy verify1 Post-copy (integrity) verify
05-09 Copy operation No longer used.
0A Phrase information This field is actually two. Each is expressed(one hex digit) as shown below.
Language. Valid values are 0, meaning no for the language area.Phrase type:
0 Both system and IVR application phra1 System phrases only2 IVR application phrases only
0B-0C Beginning location Beginning track address for verify. Zero indicFor phrases, the phrase number to start with
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Verify type& language
Phraseinformation
Beginninglocation
Copyoperation
03 0405
Language Verify typ
090A0B
Language Phrase ty
STATUS LOG 395
FILE SYSTEM MESSAGES55
or is spared (data).
55 Drive Verify Response
The format depends on the action code in offset 03 of the request.
Action Codes 80 and 82
00 All copies good.
0X Bad copy. The first four bits of the code indicate which copies are bad:
Bit 0: Copy on 1st half of record of source bad.Bit 1: Copy on 2nd half of record of source bad.Bit 2: Copy on 1st half of record of destination bad.Bit 3: Copy on 2nd half of record of destination bad.
On a post-copy verify, only bits 0 and 1 could be returned on an error, since only a single drive can be specified for verification.
18 Need to clear bad write table.
Action Code 81
01 Unrecoverable drive error.
02 Unknown.
03 Unknown.
04 Invalid language number.
05 Verify failed.
06 DMA time-out.
07 Incorrect free space table.
Offset Label Field Description
04-05 Record in error Number of the record in error.
06 Drive status See Table 3-2, “Drive Status Codes,” on page 511.
07-08 Spared record Spared record number. Valid if record number in err
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Recordin error
Drive status
Sparedrecord
Unused
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Languagenumber
Phrasenumber
Used only withreturn code 05
396 STATUS LOG
FILE SYSTEM MESSAGES 56
a
opy to. Each is shown below. Valid val-
: 00 - 0B.
py.
56 Drive Copy
The format depends on the action code in offset 03.
80 Copy software.
81 Copy phrases.
82 Copy system data tables.
83 Copy entire system.
Offset Label Description of Packet Dat
04 Language areas Which language area to copy from and which to cexpressed as a four-bit number (one hex digit) as ues are 1-5, and F means all languages.
05-06 Source slot Physical location of the source drive. Valid values
07 Destination drive Logical number of the destination drive.
08 Destination slot Physical location of the destination drive.
09 Source drive Logical number of the source drive.
0A Phrase Which phrases to copy:00 Both system and IVR application phrases.01 System phrases only.02 IVR application phrases only.
0B-0C Track address Track to begin copy at. Zero indicates an initial co
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Languageareas
Sourceslot
Destinationdrive
Destinationslot
Sourcedrive
Phrase
Trackaddress
03 0405
Copy from Copy to
STATUS LOG 397
FILE SYSTEM MESSAGES57
57 Drive Copy Response
Return codes 00-03 and 8B are for action codes 80 and 82. Return codes00, 05-0A are for action codes 86 and 87. Return codes 80-82 are for actioncodes 84, 85 and 88. Return codes 01, 12 and 2F are for action code 81.
00 OK. Offsets 04-0C are not used.
01 Depends on the action code in offset 03 of the request (file system message 56, Drive Copy):
Action code = 80 or 82: error on first half.Action code = 81: unrecoverable drive error.
02 Error on second half.
03 Cannot select drive.
05 Cannot select source drive.
06 Error on first half (source drive).
07 Error on second half (source drive).
08 Cannot select destination drive.
09 Error on first half (destination drive).
0A Error on second half (destination drive).
12 Bad free space table when trying to get new record.
2F Out of space.
80 Invalid message system drive number.
81 No more record left for substitution.
82 Full substitute table.
8B Invalid file length.
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID Record number
Numberof records
Unused
File number, see Table 3-4,“File Numbers,” on page 514
398 STATUS LOG
FILE SYSTEM MESSAGES 58
58 Return Error Counters
Sent to the file system to retrieve the respective counters or error entries.The counters or error entries are cleared after being returned to the CP.
10 Return system wide hard error counters.
12 Return hard error entries from buffer.
59 Return Error Counters Response
The format depends on the function code in offset 03 of the request (filesystem message 58, Return Error Counters).
Function Code 10 (Hard Error Counters)
Offset Label Field Description
03-04 Hard errors Total number of hard errors on all drives.
05-06 Fixes Number of automatic fixes of bad records.
07-08 Failures Number of failures at automatic fixable attempts.
09-0A Successes Number of successful ECC fixes for read failures.
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Hard errors
Fixes
Failures
Successes
STATUS LOG 399
FILE SYSTEM MESSAGES59
Function code 12
00010203 04050607 08090A0B 0C0D0E0F
Task ID Unused
Drive on which
Logical block address for error
Error type. See Table 3-5, “Inter-nal File Card Status Codes,” on page 516.
error occurred
Unused
Truncated 4-byte entry numberin errlog buffer.
400 STATUS LOG
FILE SYSTEM MESSAGES 5A
ith CA410ABE. The 4- filled with high-order
le
5A Read Half Record
For file reads
For system table reads
5B Read Record Response
00 OK.
01 Unrecoverable drive error.
07 Track is flagged.
Offset Label Field Description
06-09 Checksum ofdata read
Checksum is a 4-byte end-around carry add starting wbyte words are in Intel order; incomplete ones arezeroes.
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID Drive number
Record number(high-order byte)
Record number(low-order byte)
Number ofbytes
Number ofrecords
File, see Table 3-4, “FiNumbers,” on page 514
Unused
00010203 04050607 08090A0B 0C0D0E0F
Task ID Drive number
Action Table number (00-06)
Unused
Copy number (00 or 01)
Unused
FSCP
➤
N
Record subtype
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Checksum of Record type
Number ofbytes transferred
data read
Unused
STATUS LOG 401
FILE SYSTEM MESSAGES5C
le
5C Write File Record
Following this request message will be a response message indicating thatthe file system is ready to start writing. Following that will be a “complete”message indicating that the writing is finished.
For file writes
For system table writes
5D Write Record Response
Sent by the file system when it is ready for DMA transfer of the record to bewritten.
00 OK.
01 Unrecoverable drive error.
07 Illegal function code.
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID Drive number
Record number(high-order byte)
Record number(low-order byte)
Number ofbytes
Number ofrecords
File, see Table 3-4, “FiNumbers,” on page 514
Unused
00010203 04050607 08090A0B 0C0D0E0F
Task ID Drive number
Action Table number (00-06)
Unused
Copy number (0 or 1)
Unused
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
402 STATUS LOG
FILE SYSTEM MESSAGES 5E
5E Write Record Complete
Sent by the file system at the end of a record transfer and record write.
00 OK.
01 Unrecoverable drive error.
02 Checksum error on data transferred from CP.
06 DMA time-out on prior operation. System re-boot required.
10 Attempt to write a record 0 or 1 with data of the incorrect format.
11 Illegal attempt to write data on cylinder 0.
12 RAM error was detected when write attempted to get a new record.
13 RAM format was incorrect when attempting to write record 0 or 1.
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
STATUS LOG 403
FILE SYSTEM MESSAGES5F
, if
5F Get Length Of Old Message
60 Get Length Of Old Message Response
00 OK.
01 Unrecoverable drive error. Message state is unchanged.
02 Scramble code or message ID mismatch (software error or deleted message). Message state is unchanged.
03 Message already open. Message state is unchanged.
04 Use count is zero (software error or deleted message). Message state is unchanged.
06 DMA time-out on prior operation; system re-boot required.
Offset Label Field Description
07-08 User record Number of the user record which contains the messageknown. This field is only used for troubleshooting.
Offset Label Field Description
08 Forms flag 00 Not a forms message01 Forms message
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Message ID
Scramble code
User record
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Message length,Forms flagin bytes of speech
404 STATUS LOG
FILE SYSTEM MESSAGES 61
000-4200.
specified IRN type 00.
000000
61 Assign Internal Record Number
There are two file system message 61s, varying with direction. This is 61 asa CB-out message.
62 Assign IRN Response
00 OK.
01 Unrecoverable drive error. State is unchanged.
02 Invalid type.
03 Invalid INN number.
04 No record available.
05 Node already assigned.
06 DMA time-out on prior operation. System reboot required.
Offset Label Description of Packet Data
03 IRN type 00 IUN (Internal User Number)01 INN (Internal Node Number)
Offset Label Description of Packet Data
04-05 IRN IUN or INN. IUNs range from 0080-3B17. INNs range from 4
06-07 IUN This will be the same as the IRN field if the request message
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
IRN type INN number to assign
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
IRN IUN Unused
STATUS LOG 405
FILE SYSTEM MESSAGES63
000-4200.
63 Release IRN
64 Release IRN Response
In the case of an INN, the file system releases all of the EARs correspond-ing to that node.
00 OK.
01 Unrecoverable drive error. State is unchanged.
02 Invalid IRN.
03 IRN is not assigned before. State is unchanged.
04 Type on record header mismatch (example, try to delete a user record that is assigned to node record).
05 Messages pending in that node. State is unchanged.
06 DMA time-out on prior operation. System reboot required.
Offset Label Description of Packet Data
03-04 IRN IUN or INN. IUNs range from 0080-3B17. INNs range from 4
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID
IRN Unused
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
406 STATUS LOG
FILE SYSTEM MESSAGES 65
-FFFF.
65 Assign EAR
66 Assign EAR Response
00 OK.
01 Unrecoverable drive error. State is unchanged.
02 Invalid INN.
03 INN is not assigned before.
04 No record available.
05 No EAR available.
06 DMA time-out on prior operation. System reboot required.
07 Mismatch header on EAR record.
08 Internal file card error.
Offset Label Description of Packet Data
04-05 EAR External Address Reference number. EARs range from 4EA0
06-07 IUN IUN corresponding to this EAR.
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID INN
Mailbox number Unused
Message type
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
EAR IUN Offset
Record number
Unused
STATUS LOG 407
FILE SYSTEM MESSAGES67
67 Return EAR
68 Return EAR Response
00 OK.
01 Unrecoverable drive error. State is unchanged.
02 Invalid or erased EAR (assigned before).
03 EAR is not assigned before. State is unchanged.
04 Invalid user record, node or EAR
06 DMA time-out on prior operation. System reboot required.
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID EAR
Unused
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID INN
Mailbox number
Message type
Unused
408 STATUS LOG
FILE SYSTEM MESSAGES 69
69 Release EAR
6A Release EAR Response
00 OK.
01 Unrecoverable drive error. State is unchanged.
02 Invalid EAR number.
03 EAR is not assigned before. State is unchanged.
06 DMA time-out on prior operation. System reboot required.
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID EAR
Unused
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID INN
Mailbox number
Message type
Unused
STATUS LOG 409
FILE SYSTEM MESSAGES6B
6B Return NODE and EAR Counter
6C Return NODE & EAR Counter Response
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Number of EARs left
Number of nodes left
410 STATUS LOG
FILE SYSTEM MESSAGES 6D
convert to binary.
ed by the position field:
7. INNs range from
nspose the two bytes
mand
01100
etrd
6D Update IUN/INN Record
The format depends on whether the data is being passed in the control busmessage or through a DMA operation. This is indicated in bit 7 of offset 03.
Control Bus Message (offset 03, bit 7 = 0)
Offset Label Description of Packet Data
03 Specifications This byte has three fields, as shown below. To read,
Method. How the data is being passed:0 In the control bus message.1 Through a DMA operation.
Data type. Units of measure for the data:0 Byte1 Word (2 bytes)2 Doubleword (4 bytes)
Command. How to apply the data to the area specifi0 Change data1 Add2 Subtract3 Mask (AND)4 Subtract and return the result5 Mask (OR)
04-05 IRN IUN or INN of the record. IUNs range from 0080-3B14000-4200.
06-07 Position The location in the record to be updated. To read, traand convert to binary as shown:
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID
DataIRN
Specifications Position
0203 04
0000 00117Bit count 0346
ComData typeMethod
0000 0111 000015 1213
050607 08
Bit count
Beginning offsNumber of data units(see data type above) within the reco
STATUS LOG 411
FILE SYSTEM MESSAGES6D
convert to binary.
ed by the position field:
7. INNs range from
pdated.
ied in the data type
mand
DMA (offset 03, bit 7 = 1)
This request is followed by a response message, 6E, and an operation-complete message, 6F.
Offset Label Description of Packet Data
03 Specifications This byte has three fields, as shown below. To read,
Method. How the data is being passed:0 In the control bus message.1 Through a DMA operation.
Data type. Units of measure for the data:0 Byte1 Word (2 bytes)2 Doubleword (4 bytes)
Command. How to apply the data to the area specifi0 Change data1 Add2 Subtract3 Mask (AND)4 Subtract and return the result5 Mask (OR)
04-05 IRN IUN or INN of the record. IUNs range from 0080-3B14000-4200.
06-07 Offset The beginning offset of the area in the record to be u
08-09 Number of data units
Size of the area to be updated, using the units speciffield, offset 03, bits 4-6.
00010203 04050607 08090A0B 0C0D0E0F
Task ID
UnusedIRN
Specifications Offset Number of data units
0203 04
0000 00117Bit count 0346
ComData typeMethod
412 STATUS LOG
FILE SYSTEM MESSAGES 6E
6E Update IUN/INN Record Response
00 OK.
01 Unrecoverable drive error. State is unchanged.
02 Invalid number.
03 IUN or INN is not assigned before. State is unchanged.
04 Invalid offset. Try to modify message area for node.
06 DMA time-out on prior operation. System reboot required.
6F Update IUN/INN Record Complete
This message is sent to the CP after DMA is complete and data has beenwritten to disk.
00 OK.
01 Unrecoverable drive error. State is unchanged.
06 DMA time-out on prior operation. System reboot required.
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
FSCP
➤00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
STATUS LOG 413
FILE SYSTEM MESSAGES71
71 New Message
The format depends on whether the message is part of a remote-notifica-tion operation as specified by a preceding file system message 75, Send/Update Message.
Non-Remote-Notification
Remote-Notification
72 New Message Response
00 OK.
01 Message pending. State of message unchanged.
02 Empty message ID, scramble code and length fields in request mes-sage. State of message unchanged.
06 DMA time-out on prior operation. System reboot required.
07 Open message for that channel.
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Scramble code
Message ID Length
Sender’s IUN
Time stamp
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Sender’s IUN
Time stamp
Origin mailbox #
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
414 STATUS LOG
FILE SYSTEM MESSAGES 73
73 Additional Message Segment
74 Additional Message Response
00 OK.
01 New message (primary) missing.
02 Message ID already assigned.
03 No segment available (max = 86).
06 DMA time-out on prior operation. System reboot required.
07 Open message for that channel.
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Scramble
Message ID Length
Message ID
Scramble code
Length(zero if no moresegments)
code
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
STATUS LOG 415
FILE SYSTEM MESSAGES75
below:
75 Send/Update Message
The format depends on the message type specified in offset 03, bits 4-7.
0X Voice.
1X Remote notification.
2X Special.
3X Time stamp change.
Offset Label Description of Packet Data
03 Message type The type is defined with two 4-bit numbers, as shown
Type. Specifies the action and the message format.Options:
1 Standard, normal2 Standard, urgent3 Priority, normal4 Priority, urgent
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID
INN
Deliveryoption
Destinationmailbox #
Unused
00010203 04050607 08090A0B 0C0D0E0F
Task ID
INN
Destinationmailbox #
Originalserial number
00010203 04050607 08090A0B 0C0D0E0F
Task ID
INN
Destinationmailbox #
Specialbytes
0203 04Type Options
00010203 04050607 08090A0B 0C0D0E0F
Task IDDeliveryoption
Destinationmailbox #
Timestamp
416 STATUS LOG
FILE SYSTEM MESSAGES 76
below:
4X End-of-message.
76 Send/Update Message Response
00 OK.
01 Unrecoverable drive error. State is unchanged.
02 Invalid INN number.
03 INN is not assigned before. State is unchanged.
04 Destination is already assigned.
05 Node is full.
06 DMA time-out on prior operation. System reboot required.
07 Bad node record header.
08 Invalid type.
09 Invalid previous destination.
0A Sequence error.
Offset Label Description of Packet Data
03 Message type The type is defined with two 4-bit numbers, as shown
Type. Specifies the action and the message format.Options:
1 Standard, normal2 Standard, urgent3 Priority, normal4 Priority, urgent
00010203 04050607 08090A0B 0C0D0E0F
Task ID
INN
Deliveryoption
Destinationmailbox #
Unused
0203 04Type Options
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
STATUS LOG 417
FILE SYSTEM MESSAGES77
level (offset 03 of the
77 Start Message Search
78 Start Message Search Response
00 OK.
01 Unrecoverable drive error. State is unchanged.
02 Invalid INN.
03 INN is not assigned before. State is unchanged.
04 Invalid level.
06 DMA time-out on prior operation. System reboot required.
07 Open message for that channel.
Offset Label Field Description
04 Messages-foundflag
Indicates if messages were found in the specified request message) or higher:
00 No messages found.01 One or more messages found.
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID
INN Unused
Level
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Messages-found flag
418 STATUS LOG
FILE SYSTEM MESSAGES 79
ed in offset 03 of file
t Message Search.
message as bad (prior-sage in the node).
79 Return Next Message
Offset Label Field Description
03 Level Must be the same as or greater than the level specifisystem message 77, Start Message Search.
04-05 INN Must be the same as in file system message 77, Star
06 Message-badflag
If equal to 01, the file system is to mark the previous ity 5) by setting offset 23 in the node record (bad mes
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID
INN Unused
Message-bad flagLevel
STATUS LOG 419
FILE SYSTEM MESSAGES7A
7A Return Next Message Response
Offset 03 is split so that the return code is just the least-significant digit.
X0 OK.
X1 Unrecoverable drive error. State is unchanged.
X2 Mismatch INN.
X3 Segment or destination pending.
X4 Start message search needed or invalid level.
X5 No more messages left.
X6 DMA time-out on prior operation. System reboot required.
X7 Open message for that channel.
Offset Label Field Description
03 Offset 03 carries two 4-bit values:
Message type.0 Voice, last segment1 Remote notification 2 Special 3 Voice, more segments to come
Return code. See list above figure.
0B-0C Original serial number In case of remote notification.
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task IDMessage
ID
Scramblecode
Messagelength
IUN ofsender
Originalserial number
0203 04Message Return
type code
420 STATUS LOG
FILE SYSTEM MESSAGES 7B
tem message 77, Start essage.
ge Search.
e.
7B Return Next Segment
7C Return Next Segment Response
00 OK.
02 Mismatch level or INN.
03 Primary message pending.
04 Start message needed.
05 No more segments left.
06 DMA time-out on prior operation. System reboot required.
07 Open message for that channel.
Offset Label Field Description
03 Level Must be the same as the level specified in offset 03 of file sysMessage Search, or file system message 79, Return Next M
04-05 INN Must be the same as in file system message 77, Start Messa
Offset Label Field Description
04 More-segments flag 00 This is the last segment of the message.01 There is at least one more segment to com
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID
INN Unused
Level
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task IDMessage
ID
Scramble code
Messagelength
Unused
More-segments flag
STATUS LOG 421
FILE SYSTEM MESSAGES7D
stem message 77, ext Message.
age Search.
last one, close mes-
rns the first destination
7D Return Destinations of the Message
Offset Label Field Description
03 Level Must be the same as the level specified in offset 03 of file syStart Message Search, or file system message 79, Return N
04-05 INN Must be the same as in file system message 77, Start Mess
06 Option Option:00 Delete previous destination. If old destination was the
sage and remove it from node.01 Do not change state of message. The file system retu
with return code 5 (no more left).
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID
INN Unused
OptionLevel
422 STATUS LOG
FILE SYSTEM MESSAGES 7E
.
7E Return Destination Response
Offset 03 is split so that the return code is just the least-significant digit.
X0 OK. More destinations to come.
X1 Unrecoverable drive error. State is unchanged.
X2 Mismatch level or INN.
X3 Message or segment pending.
X4 Start message search needed.
X5 No more left. The file system closed the message.
X6 DMA time-out on prior operation. System reboot required.
X7 Already send first destination—flag is set.
X9 No more destinations.
XE Sequence error.
XF Empty destination.
Offset Field Description
03 This byte has three fields, as shown below. To read, convert to binary
More-destinations flag. Set if there are more destinations.Level. Level of the message.Return code. See list above figure.
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task IDDeliveryoption
Destinationmailbox #
Timestamp
0203 04
0000 00117Bit count 0346
Return codeLevelMore-destinations flag
STATUS LOG 423
FILE SYSTEM MESSAGES7F
nge from 4000-4200.
e may be up to 03FF.
7F Partial Read IUN/INN Record
80 Partial Read IUN/INN Record Response
00 OK.
01 Unrecoverable drive error. State is unchanged.
02 Invalid count.
03 IUN or INN is not assigned before. State is unchanged.
04 Invalid offset: tried to read message area for node.
05 Invalid IRN.
06 DMA time-out on prior operation. System reboot required.
Offset Label Field Description
03-04 IRN IUN or INN. IUNs range from 0080-3B17. INNs ra
05-06 Offset into record The offset to start reading at. For an INN, the valu
07 Count The number of data to read, a maximum of 09.
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Offset into record
Count
UnusedIRN
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Data from read
424 STATUS LOG
FILE SYSTEM MESSAGES 81
81 Build XREF Tables
82 Build XREF Tables Response
00 OK.
01 Unrecoverable drive error. State is unchanged.
02 Invalid type.
03 Invalid INN.
04 No record available.
05 Node already assigned.
06 DMA time-out on prior operation. System reboot required.
07 Invalid record header.
08 I/O error on disk name table.
09 Invalid disk name table.
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Remainder into
Record numberin error
10kB buffer (00-04)Unknown
STATUS LOG 425
FILE SYSTEM MESSAGES83
83 Check INN
84 Check INN Response
00 OK.
02 Invalid INN.
03 INN is not assigned.
06 DMA time-out on prior operation. System reboot required.
Offset Label Description of Packet Data
03-04 INN INNs range from 4000-4200.
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID
INN Unused
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
426 STATUS LOG
FILE SYSTEM MESSAGES 85
85 Update Node Field
Following this request message will be a response message indicating thatthe file system is ready to start writing. Following that will be a “complete”message indicating that the writing is finished.
86 Update Node Field Response
00 OK.
02 Invalid INN.
03 INN is not assigned.
06 DMA time-out on prior operation. System reboot required.
Offset Label Description of Packet Data
04-05 INN INNs range from 4000-4200.
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID
INN
Numberof entries
Lengthfor DMA
Checksumof data
Unused
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
STATUS LOG 427
FILE SYSTEM MESSAGES87
87 Update Node Field Complete
00 OK.
01 Unrecoverable drive error. State is unchanged.
02 Mismatch checksum.
03 Invalid type.
04 Invalid offset.
06 DMA time-out on prior operation. System reboot required.
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Entry number(in case of error only)
428 STATUS LOG
FILE SYSTEM MESSAGES 88
88 Return Number of Messages in Node
89 Return Number of Messages in Node Response
00 OK.
01 Unrecoverable drive error. State is unchanged.
02 Invalid INN.
03 INN is not assigned.
06 DMA time-out on prior operation. System reboot required.
Offset Label Description of Packet Data
04-05 INN INNs range from 4000-4200.
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID
INN Unused
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Number of messages in the node
STATUS LOG 429
FILE SYSTEM MESSAGES90
90 Add Bad Track
91 Add Bad Track Response
00 OK.
01 Unrecoverable drive error.
02 New bad track already in bad track list.
03 No spare record left.
04 Spare record selected.
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID Record address
Drive number
Unused
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
430 STATUS LOG
FILE SYSTEM MESSAGES A1
configured for standby
stem flag (02)
r 00)
cy system (bitmap)e 350 only)
only)
000000
A1 General Configuration Status Request
Used at power-up for all file cards. This message is also sent to line cards.
41 General Configuration Response for Primary Card
61 General Configuration Response for Secondary File Card
03 System running drives error.
20 Fatal error detected.
22 Drive serial number mismatch.
Offset Label Field Description
0A System redundancy flag (Overture 350 only)
00 Not standby redundancy.43 System is standy redundancy.
0B Status of standby redundancy system(Overture 350 only)
Bit 0: 1 = card is active; 0 = card is standby.Bit 2: 1 = redundant; 0 = non-redundant.Bit 6: 1 = termination error (card is not properlyredundancy).(Bits 1, 3, 4, 5, and 7 are unused).
0C Flag for SCSI 386 File System
Set to 02 to indicate SCSI 386 FIle System.
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
FSCP
➤
FSCP
➤
Task ID
Map fordrives installed
Map fordrives running
Unused
Unused
SCSI 386 File Sy
Standby redundancy flag (0x43 o
Status of standby redundan
Bootstatus
00010203 04050607 08090A0B 0C0D0E0F
(Overtur
(Overture 350
STATUS LOG 431
FILE SYSTEM MESSAGESA2
A2 General Read Memory
B2 General Read Memory Response
A3 General Write Memory
B3 General Write Memory Response
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID Source address
Unused
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID Unused
Data (memory contents)
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID Destination address
Data (memory contents)
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
432 STATUS LOG
FILE SYSTEM MESSAGES A4
7.
A4 Return Code Level
This message is also used with the line card.
Offset Label Field Description
03 Code type 01 Line card EPROM code level (lineop)02 Line card tone processing code level (toneop)03 File card EPROM code level (fileop)
04 File card disk program code level (cbhand)05 Phrase table code level and language information06 In-RAM phrase table code level07 Prompt table code level
0A Number of languages installed
04 Language Language number (01-05) used by code types 05 and 0
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Codetype Language
STATUS LOG 433
FILE SYSTEM MESSAGESB4
B4 Return Code Level Response
This message is also used with the line card.
The format varies with the code type specified in offset 03 of the requestmessage.
Code Types 01-09
00 OK.
01 Invalid type for this card.
02 Phrase table of this language not initialized.
Code Type 0A
00 OK.
01 Invalid type for this card.
Offset Label Field Description
08 Digitization rate Used only by code type 05. In ASCII:30 (0) Indeterminate31 (1) 25k32 (2) 32k
09 Language type Used only by code type 05. Valid values are 01-FF. Zero means the field is not used.
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
UnusedCode level
Language typeDigitization rate
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Number of languagesinstalled (01-05)
434 STATUS LOG
FILE SYSTEM MESSAGES A5
A5 Set DMA Test
00 Return status of DMA complete.
01 DMA to this card.
02 DMA from this card.
B5 Set DMA Test Response
Offset 03 is used only if offset 03 of the request message held 00.
00 DMA complete.
01 DMA in progress.
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Segment number to/fromDMA transfer starts
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
STATUS LOG 435
FILE SYSTEM MESSAGESA6
A6 General Utility Command
For any of the actions, a drive location of 0xFF indicates that the drive is notpresent.
02 Repair record 0 using backup record.
03 Repair record 1 using backup record.
04 Build backup record.
05 Prepare to add track to bad track table.
06 Add sector to bad sector table.
07 Get drive serial number from record 1.
08 Makespace for release 8.
09 Clear bad read table.
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Drive being acted on
Location of drive 1
Location of drive 0
Number of users Track address
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Drive
Cylinder
Head
Sector
Action code= 06
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Drive being acted on
Location of drive 1
Location of drive 0
Number of users Track address
436 STATUS LOG
FILE SYSTEM MESSAGES A6
0A Increase number of users to N.
0B Phrase squash.
0C Prepare for intelligent message copy.
0D Get physical drive level.
0E Get user record status.
0F Check system redundancy.
10 Get system status.
11 Make drive read only.
Offset Label Field Description
04 Expansion type 01 CDR expansion02 System group list expansion
05-06 Number of records Used with expansion type 01 only. In ASCII.32 (2) Expand to 2020 records.33 (3) Expand to 7020 records.
07-08 Number of users Number of users (500, 1000, 2000, 3000).
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Expansion type
Number of records Number of users
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Drive being acted on
Location of drive 1
Location of drive 0
Number of users Track address
STATUS LOG 437
FILE SYSTEM MESSAGESA6
12 Phrase utility. The format depends on the action subcode in offset 04.
Offset 04 = 01
Offset 04 = 02, 03, 04
Offset 08-0C is used with action subcode 04 only.
Offset Label Field Description
04 Action subcode 01 Convert phrase format.
Offset Label Field Description
04 Action subcode 02 Delete a phrase.03 Read phrase ID from phrase table.04 Write phrase ID into phrase table.
06-07 Phrase number Valid values are 0001-0ED7.
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unknown
Action code= 12 Action subcode = 01
00010203 04050607 08090A0B 0C0D0E0F
Task IDAction code= 12
Action subcode = 02, 03, 04
Languagenumber (01-05)
Recordcount
Phrase IDfor drive 1
Phrasenumber
Phrase IDfor drive 0
438 STATUS LOG
FILE SYSTEM MESSAGES A6
umber (ASCII)
Offset 04 = 05, 06, 07, 08
Offset 04 = 09
13 System expansion.
Offset Label Field Description
04 Action subcode 05 Initialize entire phrase table.06 Set phrase table version number.07 Set language type.08 Set digitization rate.
06 Language type Valid values are 01-FF.
08 - 0B Version number ASCII code.
Offset Label Field Description
04 Action subcode 09 Get phrase table information.
Offset Label Field Description
04 Expansion type 01 CDR expansion02 System group list expansion
05-06 Number of records Used with expansion type 01 only. In ASCII.32 (2) Expand to 2020 records.33 (3) Expand to 7020 records.
00010203 04050607 08090A0B 0C0D0E0F
Task ID Language typeAction code= 12
Languagenumber (01-05)
Digitizationrate
Phase table version n
Action subcode = 05, 06, 07, 08
Unused
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unknown
Action code= 12 Action subcode = 09
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Expansion type
Number of records
STATUS LOG 439
FILE SYSTEM MESSAGESA6
14 Get drive status.
15 Reset CDR pointers.
16 Fix spare table.
17 Intelligent phrase copy.
18 Single/multiple phrase copy.
19 Get ready for download.
1A End of download.
1B Status of download.
1C Clear seek time-out count for hard errors on drive.
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Drive being acted on
Location of drive 1
Location of drive 0
Number of users Track address
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Drive number forloading database on reboot
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Drive being acted on
Location of drive 1
Location of drive 0
Number of users Track address
440 STATUS LOG
FILE SYSTEM MESSAGES A6
1D Update IVR formatted play table.
1E Verify drive in physical location is in installed position. Action 1E gets the serial number of the physical drive (offset 06) and compares it against the serial number stored in record 0 of the logical drive (offset 04).
1F Change drive in physical location to phrase management level. Action 1F will mark the designated drive as a phrase management drive and make a null phrase table for the drive. Action 1F also creates a new free space table, without messages, for the drive.
Offset Label Field Description
07 Utility code 00 Backup utility01 Upgrade utility
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Entry number(0ED8-10CB)
Phrase number(0001-0ED7)
Language number(01-05)
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Logical locationof drive (00 or 01)
Physical locationof drive
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Utility code
*Unused
Physical locationof drive to change (00 or 01)
Logical drivenumber (00 or 01)
*
STATUS LOG 441
FILE SYSTEM MESSAGESA6
.
20 Clear records. This action will zero-out the desired records
21 Get system drive’s redundant status. This action will get the status byte from RAM (record 0) and send it back to the CP.
22 Check if D0 and D1 (if present) are a matched pair. This action will pick up serial numbers in record 1 from both drives and then compare them against serial numbers in record 0.
23 Make phrases on target file-card-independent. Action 23 first clears the pointers that point to D1’s phrases on D0, and then clears the pointers that point to D0’s phrases on D1. This includes the pointers in the phrase table and in the phrase itself. This action also zeroes-out half-record pointers of the opposite drive in the phrase table.
24 Set to boot with target drive’s phrases. Action 24 marks the corre-sponding bit in the system status to inform IPL which phrase set (D0 or D1) should be used to boot the system.
25 Set to boot with target drive’s software. Action 25 marks the corre-sponding bit in the system status to inform IPL which software set (D0 or D1) should be used to boot the system.
Offset Label Field Description
04 Language number Valid values are 01-05 and FF for all languages
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Languagenumber
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Drive number(00 or 01)
442 STATUS LOG
FILE SYSTEM MESSAGES A6
h is expressed as a . Valid values are 1-5,
ion
26 Move system’s free space table to record 8. Action 26 copies the free space table of the designated drive from another drive’s record 0 to D8 position in both drive’s record 0.
27 Change drive in physical location to phrase management level. Action 27 marks the designated drive as a phrase management drive and makes a null phrase table for the drive. This action also releases the records used by the old phrases. Action 27 leaves those spaces used by messages unchanged.
28 Ensure D0 and D1 are installed pair and is booted with no errors. In addition to comparing serial number between records 0 and 1, this action checks to see if the system booted up properly.
29 Prepare for redundant software copy.
2A Redundant software copy.
2B End of redundant software copy. Action 2B sets a bit in the status byte to indicate redundant software/phrases.
2C Prepare for redundant phrase copy.
2D Redundant phrase copy.
2E End of redundant phrase copy. Action 2E sets a bit in the status byte to indicate redundant software/phrases.
Offset Label Field Description
05 Language numbers Source and destination language numbers. Eacfour-bit number (one hex digit) as shown belowand F means all languages.
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Physical drivenumber (00 or 01)
Logical drivenumber (00 or 01)
Language numbers(action 27 only)
040506
Source Destinat
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
STATUS LOG 443
FILE SYSTEM MESSAGESA6
2F Set drive in physical location to be a master drive. Action 2F sets the target drive as either a normal drive or a master drive.
30 Make free space table on D0 and D1 become an installed pair. This action merges the free space table of D0 and D1 and writes it back to both drives.
31 Upgrade message drives to phrase management level. This action changes the drive level of messages drives to phrase management level.
Offset Label Field Description
04 Drive type 56 Normal driveA1 Master drive
05 Drive level To make first phrase management level drive.
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Drive type Drive level
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
444 STATUS LOG
FILE SYSTEM MESSAGES A6
32 Prepare destination drive as a replacement drive.Offset 04: logical drive number of replacement drive.Offset 05: physical drive number of original drive.Offset 06: physical drive number of replacement drive.Offset 07: logical drive number of original drive.
33 Recover record 0 if drive replacement fails.
Offset 05: physical drive number of the drive to recover record 0 on.Offsets 04, 05 and 06: unused.
34 Recover drive level on destination drive if upgrade utilities fail.
Offset 04: logical drive number of the drive to recover drive level on.Offset 06: physical drive number.Offsets 05 and 07: unused.
36 Rebuild free space table during the “upgrade to new drive” or “replace drive” utility.
37 Prepare new drive for the “upgrade to new drive” utility.
38 Copy record 0 from source (S) to destination (D) after system data table copy.
Offset Label Field Description
08 Options 00 Install.01 From backup to D0 or D1.
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Physical drivenumber (00 or 01)
Logical drivenumber (00 or 01)
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Physical drivenumber (00 or 01)
Logical drivenumber (00 or 01)
S D S D
Options
STATUS LOG 445
FILE SYSTEM MESSAGESB6
41 Fast FCP upgrade.
B3 Recover record.
B5 Recover install table.
B6 General Utility Command Response
The format and meaning depends on the action code in offset 03 of therequest message, A6. With action 12, the format and meaning also dependon the action subcode in offset 04.
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Sourcedrive
Destinationdrive
File number (see Table 3-4, “FileNumbers,” on page 514)
Number ofrecords
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Drive being acted on
Location of drive 1
Location of drive 0
Number of users Track address
FSCP
➤
446 STATUS LOG
FILE SYSTEM MESSAGES B6
Action 02
Repair record 0 using backup response.
00 Successful.
01 Cannot read backup record.
02 Drive number not installed on backup record.
03 Cannot select write drive when writing record 0.
04 Cannot write 0.
05 Cannot write 2.
Action 03
Repair record 1 using backup response.
00 Successful.
01 Cannot read backup record.
02 Drive number not installed on backup record.
03 Cannot select destination drive.
04 Cannot write record 1 on drive.
Action 04
Build backup record response.
00 Successful.
01 Bad boot.
02 No gen buffer.
03 Cannot select drive 0.
12 Cannot select drive 15.
13 Cannot read serial number from drive 0.
22 Cannot read serial number from drive 15.
23 Error on write.
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
……
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
STATUS LOG 447
FILE SYSTEM MESSAGESB6
Action 05
Prepare to add bad track status response.
00 Record can be updated.
01 System boot is no good (fatal).
02 Drive can not be selected (fatal).
03 Cannot read record 1 from selected drive (fatal).
04 No more room for bad track addition (fatal).
05 Track is already in list (fatal).
06 No spare available and have data track (fatal).
07 Track is a data track.
08 Track is a spare data track.
Action Code 06
Add track/sector to bad track/sector table response.
00 Track added successfully.
05 Track is already in list (fatal).
09 Failure attempting to write record 1 (fatal).
0A Checkpoint on file card RAM failed.
Action 07
Get serial number response.
00 Successful.
01 Bad boot.
02 Cannot select.
03 Cannot read.
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
00010203 04050607 08090A0B 0C0D0E0F
Task ID
UnusedSerial number
448 STATUS LOG
FILE SYSTEM MESSAGES B6
Action 08
Makespace response. Note that the return code is in offset 04.
04 Record 0 offset 03 is 01 (old message type).
0A Drive 0 not running.
0B Drive 1 not running.
0C Drive 2 not running.
0E Drive 0 serial number mismatch.
0F Drive 0, spares messed up.
10 Drive 1, spares messed up.
80 Drive 0, not enough space.
81 Drive 1, not enough space.
82 Illegal request.
83 Validity check on record 1 of drive 0 and drive 1 failed.
84 Illegal request to expand an area that has already been expanded or a request to expand backwards.
85 Unable to update record 3 of drive 0 or drive 1.
86 Unable to update record 0 on drive 0 or drive 1.
87 Error while attempting to clear expansion records.
Action 0A
Increase number of users response.
00 Successful.
80 Not enough space on drive 0.
81 Not enough space on drive 1.
82 Parameter error (not implemented yet).
83 Damage record 1.
84 No need to expand.
85 Cannot write record 3.
86 Cannot update record 0.
87 Disk error on clearing record (CB contents address).
00010203 04050607 08090A0B 0C0D0E0F
Task ID
*Unused*
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
STATUS LOG 449
FILE SYSTEM MESSAGESB6
Action 0D
Get drive level response.
00 OK.
02 Drive is not running.
Action 0E
Get user record status response.
Action 0F
Check system redundancy response. Note that the return code is in offset04.
00 Not a redundant drive.
01 Drive is currently redundant.
Offset Label Field Description
04 Drive level 01 Pre-8.002 Pre-11.003 11.0
05 Master/normal 56 Normal driveA1 Master drive
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Drive level
Master/normal
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Current numberof users
Address offirst user record
00010203 04050607 08090A0B 0C0D0E0F
Task ID
*Unused*
450 STATUS LOG
FILE SYSTEM MESSAGES B6
ve. Bits 0-15 ead, transpose stalled drives.
5 indicate the sta-e the bytes and es.
Action 10
Get system status response.
Action 11
Make drive read-only response.
Offset Label Field Description
04-05 Map fordrives installed
Bit map of the drives that the system expects to haindicate the status of drives 0-15 respectively. To rthe bytes and convert to binary. Set bits indicate in
Offset Label Field Description
06-07 Map fordrives read-only
Bit map of the drives that are read-only. Bits 0-1tus of drives 0-15 respectively. To read, transposconvert to binary. Set bits indicate read-only driv
00010203 04050607 08090A0B 0C0D0E0F
Task IDMap for
drives installed
*Unused*
00010203 04050607 08090A0B 0C0D0E0F
Task IDMap for
drives read-only
UnusedUnused
STATUS LOG 451
FILE SYSTEM MESSAGESB6
Action 12
Phrase utility response. The format and meaning depend on the action sub-code in offset 04 of the request message, A6.
Action 12, Subcode 01
Convert phrase format response.
00 OK.
01 Drive error.
02 Boot not OK.
03 Invalid action code.
04 Invalid format of old phrase table.
05 Verification failed.
06 Get buffer time-out.
Action 12, Subcode 02
Delete a phrase response.
00 OK.
01 Drive error.
02 Boot not OK.
03 Invalid action code.
04 Invalid language number.
05 Phrase table of this language not initialized.
06 Invalid phrase number.
07 Phrase does not exist.
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
452 STATUS LOG
FILE SYSTEM MESSAGES B6
Action 12, Subcodes 03 and 04
Read phrase ID from phrase table response (subcode 03). Write phrase IDinto phrase table response (subcode 04).
00 OK.
01 Drive error.
02 Boot not OK.
03 Invalid action code.
04 Invalid language number.
05 Phrase table of this language not initialized.
06 Invalid phrase number.
Action 12, Subcode 05
Initialize entire phrase table response.
00 OK.
01 Drive error.
02 Boot not OK.
03 Invalid action code.
04 Invalid language number.
Action 12, Subcodes 06, 07 and 08
Set: phrase table version number (subcode 06), language type (subcode 0or digitization rate (subcode 08).
00 OK.
01 Drive error.
02 Boot not OK.
03 Invalid action code.
04 Invalid language number.
05 Phrase table of this language not initialized.
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Record count
Phrase IDof drive 0
Phrase IDof drive 1
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
STATUS LOG 453
FILE SYSTEM MESSAGESB6
Action 12, Subcode 09
Get phrase table information response.
00 OK.
01 Drive error.
02 Boot not OK.
03 Invalid action code.
04 Invalid language number.
05 Phrase table of this language not initialized.
Action 13
System expansion response.
00 Successful.
80 Not enough space on drive 0.
81 Not enough space on drive 1.
82 Parameter error (not implemented yet).
83 Damage record 1.
84 No need to expand.
85 Cannot write record 3.
86 Cannot update record 0.
87 Disk error on clearing record (CB contents address).
Offset Label Field Description
04 Table status 00 Good phrase table01 Bad phrase table
05 Digitization rate Used only if the table status is good.
06 Language type Used only if the table status is good.
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Table status
Digitization rate
Language type
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
454 STATUS LOG
FILE SYSTEM MESSAGES B6
Action 14
Get drive status response. The format for action code 14 depends on thesystem type.
Action 19
Get ready for download response.
00 Successful.
80 Not a two-drive system.
81 All drives installed are not running.
Action 1A
End of download response.
00 Successful.
84 Invalid drive number.
Action 1B
Status of download response.
Action 1C
Clear seek time-out count for hard errors on drive response.
00010203 04050607 08090A0B 0C0D0E0F
Task IDNumber ofcylinders
Number ofheads/cylinders
Unused
Number ofsectors/tracks
Returncode
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
00010203 04050607 08090A0B 0C0D0E0F
Task ID
*Unused
Drive 3 for loading
*
database on rebootNDLDXstate
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
STATUS LOG 455
FILE SYSTEM MESSAGESB6
11.
11.
Actions 1D-20
Action 1D: Update IVR formatted play table response.
Action 1E: Verify drive in physical location is in installed position response.
Action 1F: Change drive in physical location to phrase managementresponse.
Action 20: Clear records response.
The meaning of some of the return codes varies with the action code of therequest message.
Offsets 04-0C are used only if the return code in offset 03 is 01 (unrecover-able drive error) or involves phrases.
00 Successful.
01 Unrecoverable drive error.
02 Action 1D: Illegal entry number.Action 1E-20: Invalid action code.
03 Action 1D: Illegal phrase number.Action 1E: Drive not in correct position.Action 1F: Not enough spare records for bad tracks.
04 Action 1D: Illegal language number.Action 1F: Bad record 1.
05 Action 1D: Phrase not recorded.
Offset Label Field Description
05 Drive action See Table 3-1, “Drive Action Codes,” on page 5
08 Drive status See Table 3-2, “Drive Status Codes,” on page 5
0A Language number Used only when working on a phrase record.
0B-0C Phrase number Used only when working on a phrase record.
00010203 04050607 08090A0B 0C0D0E0F
Task ID Record IDDrive
number
Driveaction
Drivestatus
Language number
Phrasenumber
*
*Unused
Unused
456 STATUS LOG
FILE SYSTEM MESSAGES B6
04 holds the sys-The value is a
ases.tware. D0 and D1.D0 and D1.
d.d...ror) or involves
511.
511.
Action Code 21
Get system drive’s redundant status response. Offsets 05-0C are used onlyif the return code in offset 03 is 01 (unrecoverable drive error) or involvesphrases.
00 OK.
01 Unrecoverable drive error.
02 Invalid action code.
Offset Label Field Description
04 Redundant status If the return code in offset 03 is 00 (OK), offset tem drives’ redundant status as a set of flags. sum of:
01 (Bit 0 set.) If bit 2 = 1, drive used for phr02 (Bit 1 set.) If bit 3 = 1, drive used for sof04 (Bit 2 set.) Set if phrases are different on08 (Bit 3 set.) Set if software is different on
10 (Bit 4 set.) Set if phrases on D0 are goo20 (Bit 5 set.) Set if phrases on D1 are goo40 (Bit 6 set.) Set if software on D0 is good80 (Bit 7 set.) Set if software on D1 is good
If the return code is 01 (unrecoverable drive erphrases, offset 04 holds the drive number.
05 Drive action See Table 3-1, “Drive Action Codes,” on page
08 Drive status See Table 3-2, “Drive Status Codes,” on page
0A Language number Used only if it is a phrase record.
0B-0C Phrase number Used only if it is a phrase record.
00010203 04050607 08090A0B 0C0D0E0F
Task ID Record IDRedundant
status
Driveaction
Drivestatus
Language number
Phrasenumber
*
*Unused
Unused
STATUS LOG 457
FILE SYSTEM MESSAGESB6
511.
511.
Actions 22-2D
Action 22: Check for matched pair response.
Action 23: Make phrases on target file-card-independent response.
Action 24: Set to boot with target drive’s phrases response.
Action 25: Set to boot with target drive’s software response.
Action 26: Move free space table response.
Action 27: Change drive in physical location to phrase managementresponse.
Action 28: Ensure D0 and D1 are installed pair response.
Action 29: Prepare for redundant software copy response.
Action 2A: Redundant software copy response.
Action 2B: End of redundant software copy response.
Action 2C: Prepare for redundant phrase copy response.
Action 2D: Redundant phrase copy response.
The meaning of some of the return codes varies with the action code of therequest message. Offsets 04-0C are used only if the return code in offset 03is 01 (unrecoverable drive error) or involves phrases.
00 OK.
01 Unrecoverable drive error.
02 Invalid action code.
03 Action 22 or 28: Drives are not a pair.Action 27, 2C or 2D: Not enough space on destination drive for phrases.
04 Action 27: Invalid language number.Action 28: System boot not OK.
05 Action 2C: Bad phrase. Check free space table.
Offset Label Field Description
05 Drive action See Table 3-1, “Drive Action Codes,” on page
08 Drive status See Table 3-2, “Drive Status Codes,” on page
0A Language number Used only when working on a phrase record.
0B-0C Phrase number Used only when working on a phrase record.
00010203 04050607 08090A0B 0C0D0E0F
Task ID Record IDDrive
number
Driveaction
Drivestatus
Language number
Phrasenumber
*
*Unused
Unused
458 STATUS LOG
FILE SYSTEM MESSAGES B6
511.
511.
Actions 2E-38
Action 2E: End of redundant phrase copy response.
Action 2F: Set drive in physical location to be a master drive response.
Action 30: Make free space table on D0 and D1 become an installed pairresponse.
Action 31: Upgrade message drives to phrase management level response.
Action 32: Prepare destination drive as a replacement drive response.
Action 33: Recover record 0 if drive replacement fails response.
Action 34: Recover drive level on destination drive if upgrade utilities failresponse.
Action 36: Rebuild free space table during the “upgrade to new drive” or“replace drive” utilities response.
Action 37: Prepare new drive for the “upgrade to new drive” utility response.
Action 38: Copy record 0 from source to destination after copying systemdata tables response.
Offsets 04-0C are used only if the return code in offset 03 is 01 (unrecover-able drive error) or involves phrases. Return codes 03-2F apply only toaction code 32.
00 OK.
01 Unrecoverable drive error.
02 Invalid action code.
03 Not enough spare records for bad tracks.
04 Bad record 1.
2E Replacement drive is smaller than the original drive.
2F Out of space.
Offset Label Field Description
05 Drive action See Table 3-1, “Drive Action Codes,” on page
08 Drive status See Table 3-2, “Drive Status Codes,” on page
0A Language number Used only when working on a phrase record.
0B-0C Phrase number Used only when working on a phrase record.
00010203 04050607 08090A0B 0C0D0E0F
Task ID Record IDDrive
number
Driveaction
Drivestatus
Language number
Phrasenumber
*
*Unused
Unused
STATUS LOG 459
FILE SYSTEM MESSAGESB6
Action 41
Fast FCP upgrade.
Action B3
Recover record response.
Offset Label Field Description
03 Return code Values:0 - OK9D - File not found85 - I/O error95 - Source files not the same length as
destination files
04 File number File number in which the error occurred.
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Return code
File number
00010203 04050607 08090A0B 0C0D0E0F
Task ID Status
Number of errorsfound to recover
Unused
Returncode
460 STATUS LOG
FILE SYSTEM MESSAGES A7
A7 CDR Utility Command
<02 Go to next CDR block.
02 Clear total number of lost CDR counters.
>02 Get next block.
B7 CDR Utility Command Response
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Next block numberto be transmitted
Oldest goodblock number
Number ofblocks lost
Total numberof blocks
STATUS LOG 461
FILE SYSTEM MESSAGESC0
nt.
se or not, and if so,
essage (bit 0 =
ge format struc-trolled value.
000000
C0 New Message Primitives
00 Open old message.
01 Open new message.
Offset Label Field Description
0C Flags Bits 0 - 6: Message type0 Message/new style phrase.2 Old phrase-management style phrase.3 Pre-phrase-management style phrase.
Bit 7: Sequential read flag0 Read message using positional data.1 Read message sequential, as per name/announceme
Offset Label Field Description
04 Phrase indicator This byte indicates whether the message is a phrawhat type of phrase:
00 Message is not a phrase.01 Message is a phrase.02 Old phrase management style phrase.03 Pre-phrase management style phrase.
05-06 Drive # 16-bit identifier specifying which drives to use for mdrive 0...bit 15 = drive 15).
07 Special flag bit 0: use count is > 1.bit 1: used by Z80 to indicate short phrase.
08-09 Scramble code Unused.
0A Redundant flag 00 Message/phrase is not redundant.01 Write message/phrase to two separate drives.
0B Message level This value will be 00 - FF, depending on the messature version level. It is a software release level con
CP➤FS
Task ID
Message/phrase ID
Redundant message/phrase ID(all Fs = unused)
Flags
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Phrase
Drive #
indicatorSpecial
Scramblecode
Messagelevel
Redundant Unusedflag flag
00010203 04050607 08090A0B 0C0D0E0F
462 STATUS LOG
FILE SYSTEM MESSAGES C0
02 Close new message.
03 Read/write message block.
04 Get message data block.
05 Get message ID physical address.
06 Get message use count.
07 Read next IVR phrase.
08 Write IVR phrase.
09 Write old IVR phrase.
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Message/phrase ID
Use count to set formessage (must be > 0)
Unused
Unused
Task ID
Old message ID
New message ID
00010203 04050607 08090A0B 0C0D0E0F
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Message/phrase ID
Record # in message(386 only, otherwise unused)
Message blocklength (386 only)
Task ID
Message/phrase ID
Unused
00010203 04050607 08090A0B 0C0D0E0F
Length
Task ID
Phrases ID
Position
00010203 04050607 08090A0B 0C0D0E0F
STATUS LOG 463
FILE SYSTEM MESSAGESC1
xists.message exists.
C1 New Message Primitives Response
The format varies with the action specified in offset 03 of the request mes-sage (C0).
Action 00
00 OK.
01 Unrecoverable drive error.
02 Scramble code or message ID mismatch.
03 Message already open.
04 Use count is zero.
06 DMA time-out on prior operation.
07 Invalid message/phrase format.
Offset Label Field Description
04-07 Message length Message length in bytes of speech.
08 Forms flag 00 Not a forms message01 Forms message.
0B Drives Drive number of where the message exists:bits 0 - 3: drive number (0-15) where message ebits 4 - 7: drive number (0-15) where redundant
0C Special flag bit 0: use count is > 1.bit 1: used by Z80 to indicate short phrase.
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Message
Forms flag
lengthScramble
code
Drives
Special flag
464 STATUS LOG
FILE SYSTEM MESSAGES C1
exists.
Action 01
00 OK.
01 Unrecoverable drive error.
02 Scramble code or message ID mismatch.
03 Message already open.
04 No space left on disk
06 DMA time-out on prior operation.
07 Invalid message/phrase format.
Action 02
00 OK.
01 Unrecoverable drive error.
02 Scramble code or message ID mismatch.
03 Message already open.
06 DMA time-out on prior operation.
07 Invalid message/phrase format.
Offset Label Field Description
0C Drives Drive number of where the message exists:bits 0 - 3: drive number (0-15) where message exists.bits 4 - 7: drive number (0-15) where redundant message
Offset Label Field Description
04-05 Logical records Number of logical records in message/phrase.
06 Secondary status Secondary status of redundant operations:00 Operation OK.01 Failure on primary drive.02 Failure on secondary drive.
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Message/phrase ID
Redundant message/phrase ID
Drives
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Logical
Secondarystatus
records
Unused
STATUS LOG 465
FILE SYSTEM MESSAGESC1
k, consisting of one of he same value in offset
sage block.
Action 03
00 OK.
01 Unrecoverable drive error.
02 Scramble code or message ID mismatch.
03 Message already open.
06 DMA time-out on prior operation.
07 Invalid message/phrase format.
08 Read error on read/write message block.
09 Write error on read/write message block.
Action 04
00 OK.
01 Unrecoverable drive error.
02 Scramble code or message ID mismatch.
03 Message already open.
06 DMA time-out on prior operation.
07 Invalid message/phrase format.
0A Past end of message.
Offset Label Field Description
04 True return code A secondary return code if data is a message blocthe values listed for offset 03, but not necessarily t03.
05-08 Message ID Message ID of next block in message (Z80 only):00000000 = End of message or not a valid mes
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Reason (returncodes 08 and 09 only)
Flags (bits 0-1: end of message indicator)
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
True return code
Message ID
466 STATUS LOG
FILE SYSTEM MESSAGES C1
Action 05
00 OK.
01 Unrecoverable drive error.
02 Scramble code or message ID mismatch.
03 Message already open.
06 DMA time-out on prior operation.
07 Invalid message/phrase format.
Action 06
00 OK.
01 Unrecoverable drive error.
02 Scramble code or message ID mismatch.
03 Message already open.
06 DMA time-out on prior operation.
07 Invalid message/phrase format.
Action 07
00 OK.
01 Unrecoverable drive error.
02 Scramble code or message ID mismatch.
03 Message already open.
06 DMA time-out on prior operation.
07 Invalid message/phrase format.
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Head
Sector(386 only)
Cylinder
Drive
Task ID
Use count
Number of 16k recordsof the message
Recordingtype
Unused
00010203 04050607 08090A0B 0C0D0E0F
00010203 04050607 08090A0B 0C0D0E0F
Task ID
End of message
flag
Position
Length
STATUS LOG 467
FILE SYSTEM MESSAGESC2
Action 08 and 09
00 OK.
01 Unrecoverable drive error.
02 Scramble code or message ID mismatch.
03 Message already open.
06 DMA time-out on prior operation.
07 Invalid message/phrase format.
C2 Phrase Table Primitives
00 Initialize phrase table.
Offset Label Field Description
04 Language area bit 0: phrase area (0-1)bits 1-3: language number (1-5)
Task ID
Unused00010203
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Language area
Drive
Unused
468 STATUS LOG
FILE SYSTEM MESSAGES C2
ilable (cvxphrase.inc):
01 Set phrase table information.
Offset Label Field Description
04 Language area bit 0: phrase area (0-1)bits 1-3: language number (1-5)
06-09 Phrase tableversion
Version number of phrase table.
0A Language type As of 6/21/93, the following language types are ava01 American English (Jane)02 Australian English03 American Spanish04 Canadian English
05 American English (Marsha)06 Special English/Spanish07 Canadian French08 British English
09 New Zealand English0A European English0B European French0C American English (US West)
0D American English (Nynex)0E European German0F European Italian10 Cantonese
11 Mandarin12 Malay13 Brazilian Portuguese14 Dutch
15 Japanese16 Arabic17 European Portuguese18 Mercury English
0B Digitization rate 00 Indeterminate01 25K phrase digitization02 32K phrase digitization
0C In-ram phrasepriority
A value from 1-9 designating phrase priorities.
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Language
Drive
areaPhrase table
version
Languagetype
Digitizationrate
In-ram phrasepriority
STATUS LOG 469
FILE SYSTEM MESSAGESC2
02 Get language table information.
03 Get formatted play table entry.
Offset Label Field Description
04 Language area bit 0: phrase area (0-1)bits 1-3: language number (1-5)
06 Table type 00 Phrase table.01 Prompt table.02 In-ram table.
Offset Label Field Description
04 Language area bit 0: phrase area (0-1)bits 1-3: language number (1-5)
06-07 Entry number Play table entry number (0-499)
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Language
Drive
areaTable type
Unused
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Language
Drive
areaEntry #
Unused
470 STATUS LOG
FILE SYSTEM MESSAGES C2
, unused area):
04 Put formatted play table entry.
05 Load table.
Offset Label Field Description
04 Language area bit 0: phrase area (0-1)bits 1-3: language number (1-5)
06-07 Entry number Play table entry number (0-499)
08-09 Phrase number Phrase number from 0-5699.
0A Memory flag 00 Do not apply change to memory copy.01 Apply change to memory copy.
Offset Label Field Description
04 Language area bit 0: phrase area (0-1)bits 1-3: language number (1-5)
06 Table type 00 Phrase table.01 Prompt table.
07-08 Start phrase # Phrase table only, 0-5699; otherwise, unused area.
09-0A End phrase # Phrase table only, 0-5699; otherwise, unused area.
0B XREF flag Load XREF table flag (phrase table only; otherwise00 Do not load XREF table.01 Load XREF table.
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Language
Drive
areaEntry #
Phrase #
Memoryflag
Unused
Task ID
Language
Drive
areaTabletype
00010203 04050607 08090A0B 0C0D0E0F
End phrase #
Start phrase # XREF flag
Unused
STATUS LOG 471
FILE SYSTEM MESSAGESC2
06 Clear in-ram phrase table.
07 Load in-ram phrase.
08 Load delay phrase.
09 Get phrase information.
Offset Label Field Description
04 Language area bit 0: phrase area (0-1)bits 1-3: language number (1-5)
Offset Label Field Description
04 Language area bit 0: phrase area (0-1)bits 1-3: language number (1-5)
Task ID
00010203 04050607 08090A0B 0C0D0E0FUnused
Task ID
Language area
Phrase # (0-5699)
00010203 04050607 08090A0B 0C0D0E0FUnused
Task ID
00010203 04050607 08090A0B 0C0D0E0FUnused
Phrase # (0-5699)
Delay (ms)
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Language
Drive
area
Unused
Phrase #(0-5699)
472 STATUS LOG
FILE SYSTEM MESSAGES C2
0A Put phrase version.
0B Move old phrase table.
0C Delete phrase.
Offset Label Field Description
04 Language area bit 0: phrase area (0-1)bits 1-3: language number (1-5)
Offset Label Field Description
06 Phrase table type 02 Old phrase management table.03 Pre-phrase management table.
Offset Label Field Description
06 Phrase table type 02 Old phrase management table.03 Pre-phrase management table.
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Language
Drive
areaPhrase #(0-5699)
Unused
Phrase version
Task ID
Language #
Drive
Phrase table type
00010203 04050607 08090A0B 0C0D0E0FUnused
(1-5)
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Phrase ID drive 0
Phrase ID drive 1
Phrase table type
STATUS LOG 473
FILE SYSTEM MESSAGESC2
e, unused area):
0D Clear phrase table entry.
0E Reset phrase XREF table.
Offset Label Field Description
04 Language area bit 0: phrase area (0-1)bits 1-3: language number (1-5)
06-07 Start phrase # 0-5699.
08-09 End phrase # 0-5699.
0A Bit map entry # bit 0: entry 1bit 1: entry 2
0B XREF flag Search XREF table flag (phrase table only; otherwis00 Do not search XREF table.01 Search XREF table.
Offset Label Field Description
04 Language area bit 0: phrase area (0-1)bits 1-3: language number (1-5)
06 Conditional flag 00 Reset table unconditionally.01 Reset table if default.
07 Memory flag 00 Do not apply changes to memory copy.01 Apply changes to memory copy.
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Language
Drive
areaStart phrase #
End phrase #
Bit mapentry #
Unused
XREF flag
Task ID
Language
Drive
Conditional flag
00010203 04050607 08090A0B 0C0D0E0FUnused
area
Memory flag
474 STATUS LOG
FILE SYSTEM MESSAGES C3
C3 Language Area Primitives Response
The format varies with the action specified in offset 03 of the request mes-sage (C2). The following return codes (offset 03) apply to all actions.
Actions 00 and 01
Offset Label Field Description
03 Return code 00 OK.20 Invalid area.21 Invalid drive number.22 Invalid phrase number.23 Phrase table not initialized.
24 Invalid table type.25 Invalid language area number.26 Phrase entry empty.27 End of active phrases.
28 Phrase length discrepancy.29 Formatted play table entry empty.2A Invalid prompt table.
With action 0E: Invalid in-ram table.2B Invalid phrase ID2C Invalid phrase entry number.2D Phrase table empty.2E Error Initializing phrase table.2F FPT not initialized.
FSCP
➤
Task ID
00010203 04050607 08090A0B 0C0D0E0FUnused
Return code
STATUS LOG 475
FILE SYSTEM MESSAGESC3
ilable (cvxphrase.inc):
Action 02
Offsets 08-0A are used only with phrase tables.
Offset Label Field Description
08 Language type As of 6/21/93, the following language types are ava01 American English (Jane)02 Australian English03 American Spanish04 Canadian English
05 American English (Marsha)06 Special English/Spanish07 Canadian French08 British English
09 New Zealand English0A European English0B European French0C American English (US West)
0D American English (Nynex)0E European German0F European Italian10 Cantonese
11 Mandarin12 Malay13 Brazilian Portuguese14 Dutch
15 Japanese16 Arabic17 European Portuguese18 Mercury English
09 Digitization rate 00 Indeterminate01 25K phrase digitization02 32K phrase digitization
0A In-ram phrasepriority
A value from 1-9 designating phrase priorities.
00010203 04050607 08090A0B 0C0D0E0F
Task IDLanguage
Return code
Table version
Unused
type
Digitization rate
In-ram phrase priority
476 STATUS LOG
FILE SYSTEM MESSAGES C3
Action 03
Actions 04-08
Action 09
Actions 0A-0C
Action 0D
Action 0E
00010203 04050607 08090A0B 0C0D0E0F
Task ID Return code
Phrase number
Unused
(FFFF = FPT not initialized)
Task ID
00010203 04050607 08090A0B 0C0D0E0FUnused
Return code
00010203 04050607 08090A0B 0C0D0E0F
Task ID Return code
Phrase length:
Unused
number of logical records
Phrase version
Task ID
00010203 04050607 08090A0B 0C0D0E0FUnused
Return code
00010203 04050607 08090A0B 0C0D0E0F
Task ID Return code
FPT entry number (0-499)
Unused
(FFFF = no valid entry)
Task ID
00010203 04050607 08090A0B 0C0D0E0FUnused
Return code
STATUS LOG 477
FILE SYSTEM MESSAGESC4
C4 New Garbage Collect Primitives
00 Prepare for garbage collect.
01 End of garbage collect.
02 Read check message.
Offset Label Field Description
05 Option 00 Short garbage collect01 Long garbage collect02 Makespace04 Phrase verify
Offset Label Field Description
04 Update free-spacetables flag
00 Do not update01 Update
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Drive number
Unused
(FF = all drives)
Option
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Update free-space tables flag
00010203 04050607 08090A0B 0C0D0E0F
Task ID Message ID
Unused
478 STATUS LOG
FILE SYSTEM MESSAGES C5
ed. Read like offset 04 er,” on page 28.
C5 New Garbage Collect Primitives Response
If the request message, C4, specified action 02 in its offset 03, the format ofthe response varies depending on the return code and the kind of garbagecollect operation in process. If the return code in offset 03 is 03 (end of mes-sage), see the following section.
00 OK.
01 Invalid drive.
02 Drive error.
03 End of message. If the request message had action 02 in offset 03, the format varies; see below.
04 Message already checked.
05 Message error.
06 Message has to be moved (makespace only).
07 Makespace complete.
08 Inconsistent messages (short garbage collect only).
09 Out of space (makespace only).
Action 02 with Return Code 03
The format depends on the kind of garbage collect operation in process.This was specified by a preceding file system message C4 with action 00,Prepare for Garbage Collect. If the option field, offset 05, of that messageheld:
• 00 or 01, short or long garbage collect, use the first format below.
• 02 or 03, makespace or message ID convert, use the second for-mat below.
• 04, phrase verify, use the format above (that is, there is no packetdata).
During Short or Long Garbage Collect:
Offset Label Field Description
04 Recording port Channel and slot on which the message was recordof the IORB header, see Section 1.5.2, “IORB Head
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Task ID
00010203 04050607 08090A0B 0C0D0E0F
Return code
Recording port
= 03Number of blocksin message
Message length,with silence
Message length,without silence
STATUS LOG 479
FILE SYSTEM MESSAGESC5
During Makespace or Message ID Convert:
Task ID
00010203 04050607 08090A0B 0C0D0E0F
New message ID
Return code = 03
Use count
Unused
(or old ID if unchanged)
480 STATUS LOG
FILE SYSTEM MESSAGES C6
C6 Miscellaneous Commands
00 Start new file card operations.
01 End new file card operations.
02 Get drive message mask.
04 Replace drive.
05 Get physical drive serial number.
06 Get system boot area.
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Drive number
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Old drive number(FF is null)
New drive number(FF is null)
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Drive number
STATUS LOG 481
FILE SYSTEM MESSAGESC6
blocksent system value)
ue)
07 Set system boot area.
08 Initialize drive.
Offset Label Field Description
05 Boot drive Bit map showing new boot drive:01 Drive 002 Drive 103 Both drives
06 Boot area Bit map showing new boot area:01 Area A02 Area B03 Both areas
Offset Label Field Description
05 Drive type 01 System drive02 Phrase drive03 System and phrase drive04 Message drive07 System, phrase and message
06 Drive subtype Used only with Z80-based file card.01 Drive is a copy.02 Drive is to be installed as 0 or 1 on this system
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Drive number(FF = system drives)
Boot drive Boot area
00010203 04050607 08090A0B 0C0D0E0F
Task ID Drive number
Drive type Number of CDR (FFFF = use curr
Drive subtype(used with Z80 only)
Number of backup user records(FFFF = use current system val
Number of user records(FFFF = use current system value)
482 STATUS LOG
FILE SYSTEM MESSAGES C6
09 Get drive type.
0A Change drive type.
0B Get file card type.
0C Get drive message space.
Offset Label Field Description
05 Drive type 01 System drive02 Phrase drive03 System and phrase drive04 Message drive07 System, phrase and message
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Drive number
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Drive number
Drive type
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Drive number
STATUS LOG 483
FILE SYSTEM MESSAGESC6
0D Allocate message space.
0E Free message space.
0F Start copy.
10 End copy.
Offset Label Field Description
04 Copy type 01 Message02 Phrase03 System data filesFF Drive
05 Physical-to-logical type 00 Source01 Destination
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Drive number
Number of logical records
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Drive number
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Copy type
Physical-to-logical type Physical drive number
Logical drive number
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
484 STATUS LOG
FILE SYSTEM MESSAGES C6
11 Upgrade drive.
13 Spin up drive.
14 Spin down drive.
15 Get drive status.
16 Physical to logical translation.
17 Get drive mirrored status (386 file card only).
Offset Label Field Description
04 Drive type 01 System drive02 Phrase drive03 System and phrase drive04 Message drive07 System, phrase and message
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Drive type
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Drive number
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Head
Sector (only with386-based file card)
Cylinder
Drive number
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Drive number
STATUS LOG 485
FILE SYSTEM MESSAGESC6
18 Set mirrored drive status (386 file card only).
19 Get new message open count (386 file card only).
22 Request File Card for status of a specific drive.
Offset Label Field Description
04 Mirrored drive status 00 Reset mirrored drives01 Set mirrored drives
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Mirrored drive status
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Drive number
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Drive number
486 STATUS LOG
FILE SYSTEM MESSAGES C7
).nly).
C7 Miscellaneous Commands Response
The format varies with the action specified in offset 03 of the request mes-sage (C6). The following return codes (offset 03) apply to all actions.
Actions 00 and 01
Action 02
Offset Label Field Description
03 Return code 00 OK.20 New operations in use.21 Invalid drive.22 Invalid parameter.23 Copy drive already active.
24 Copy operation active.25 No active copy.26 Error on record 0 (Z80 only).27 Varies with card type:
386: Invalid drive typeZ80: Error on record 1
28 Error on record 1.29 Error in I/O of DDR.2A Error in bld of DDR.2B Drive not installed.
2C Drive already installed.2D Varies with file card type:
386: Serial number mismatch.Z80: Error building free space table.
2E Serial number not found at Start Copy (Z80 only2F Drive too small to be installed in this pair (Z80 o3B Cannot checkpoint installed drives (Z80 only).3C Cannot build backup record (Z80 only).A7 Drive does not exist.
FSCP
➤
Task ID
00010203 04050607 08090A0B 0C0D0E0FUnused
Return code
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Message bit mask
Expected valueReturn code
Unused
STATUS LOG 487
FILE SYSTEM MESSAGESC7
Action 04
Action 05
Offset Label Field Description
05 Reason for failure Gives more detail when the return code (offset 03) equals 3C, “Cannot build backup record.”
01 Cannot select drive.02 Cannot read record 1.03 Cannot write record 1.04 Failed on write backup record.
Offset Label Field Description
03 Return code Values:02 = Drive error21H = Invalid drive
Return code
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Drive number (only
Reason for failure
with return code 3C)
(only with return code 3C)
00010203 04050607 08090A0B 0C0D0E0F
Task ID Return code Drive serial number
Unused
488 STATUS LOG
FILE SYSTEM MESSAGES C7
Action 06
Action 07
Action 08
Offset Label Field Description
04 Boot drive Bit map showing boot drive:01 Drive 002 Drive 103 Both drives
05 Boot area Bit map showing boot area:01 Area A02 Area B03 Both areas
Offset Label Field Description
03 Return code Values:02 = Drive error27H = Invalid drive type
Return code
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Boot drive Boot area
Task ID
00010203 04050607 08090A0B 0C0D0E0FUnused
Return code
Task ID
00010203 04050607 08090A0B 0C0D0E0FUnused
Return code
STATUS LOG 489
FILE SYSTEM MESSAGESC7
Action 09
Action 0A
Action 0B
Action 0C
Offset Label Field Description
04 Drive type 01 System drive02 Phrase drive03 System and phrase drive04 Message drive07 System, phrase and message
05 Master drive flag 00 Not a master drive01 Is a master drive
Offset Label Field Description
04 File card type The file card’s CPU:00 Z8001 386
Return code
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Drive type Master drive flag
Task ID
00010203 04050607 08090A0B 0C0D0E0FUnused
Return code
Return code
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
File card type
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Used message space
Free message spaceReturn code
(number of logical records)
(number of logical records)
Unused
490 STATUS LOG
FILE SYSTEM MESSAGES C7
rd, both installed and f drives 0-15 respec-
nvert to binary. Set bits
Actions 0D-11
Action 13
Action 14
Action 15
Offset Label Field Description
04-05 Map for drives spinning on file card
Bit map of the drives spinning on the file canot installed. Bits 0-15 indicate the status otively. To read, transpose the bytes and coindicate spinning drives.
Task ID
00010203 04050607 08090A0B 0C0D0E0FUnused
Return code
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Serial number of installed drive (in BCD)
Serial number of physical drive (in BCD)Return code
Unused
Task ID
00010203 04050607 08090A0B 0C0D0E0FUnused
Return code
Return code
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Map for drives spinning on file card
STATUS LOG 491
FILE SYSTEM MESSAGESC7
Action 16
Action 17
Action 18
Action 19
Offset Label Field Description
06 Area Depends on the data file type.Software file: software area 00 or 01Phrase file: language area (in two parts):
Bit 0: phrase area 0 or 1Bits 1-3: language number 1-5
Other files: unused
Offset Label Field Description
04 Mirrored flag Mirrored status:00 Not mirrored01 Mirrored
05-06,07-08,09-0A
Mirrored pairs Each two-byte field defines a mirrored drive pair.FFFF = end of mirrored pairs.
Return code
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Data file type
Area
Data filesubtype
Record number within file
Return code
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Mirrored flag
Mirrored pairs
Task ID
00010203 04050607 08090A0B 0C0D0E0FUnused
Return code
Return code
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Count of open new messages
492 STATUS LOG
FILE SYSTEM MESSAGES C7
Action 22
Offset Label Description
3 Return Code value = 00
4 Running flag 00 = Not running01 = Running
5 Installed flag 00 = Not installed01 = Installed
Return code
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Installed flagRunning flag
STATUS LOG 493
FILE SYSTEM MESSAGESC8
n the next page.
the status of drives 0-7 s of drives 8-15 te the selected drives.
C8 New Data File Primitives
00 Open data file.
Offset Label Field Description
04 Data file type 00 Software01 Phrase02 System data file03 System utilities04 Message (386 file card only)FF Drive (Z80 file card only)
05 Data filesubtype
Depends on data file type in offset 04. See the table o
06 Mode 00 Read01 Read/write02 Write03 Write/verify80 Use relative positioning
07, 0C Map for drive number
Bit map of the drives. Offset 07 (Lo), bits 0-7, indicate respectively. Offset 0C (Hi), bits 0-7, indicate the staturespectively. To read, convert to binary. Set bits indica
08 Area Depends on the data file type in offset 04.Software file: software area 00 or 01Phrase file: language area (in two parts):
Bit 0: phrase area 0 or 1Bits 1-3: language number 1-5
Other files: unused
09-0A Misc. Depends on the subtype.Subtypes 09 and 0A: Number of recordsSubtype 0D: Record numberOther subtypes: Unused
0B What-if flag Used with subtypes 09 and 0A only.00 Actual request01 Space released/used request
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Data file type
Mode
Data file
Area
Map for
What-if flag
subtype
Misc.
Lo Hi
drive number
494 STATUS LOG
FILE SYSTEM MESSAGES C8
04—Message
Messages
ters Message Infor-mation File
igu-0 )
on rd
le
d
t
up
Data File Subtypes
00—Software 01—Phrase02—System
Data File03—System
Utilities
00 File card Phrase table System Status Table
Dump records
01 IPL Prompt table Class of Service table
Drive parame
02 System software In-ram phrase table
Report selection parameters
Filecard Confration File (Z8record 0 and 2
03 Miscellaneous software
Statistic seg-ments
Disk InformatiFile (Z80 reco1)
04 VRTX (386 only) User records
05 IPL1 extension (386 only)
CDR
06 CPU data files
07 Backup user records
08 Port configuration file
09 Bad user record file
40 Z80 DDR
41 Z80 MessageInformation Fi
42 Z80 Backup record
43 Z80 Write-through recor
44 Z80 Spare Lis
80 386 RAT File
81 386 RAT BackFile
82 386 Filecard Error Log
83 386 Network Error Log
STATUS LOG 495
FILE SYSTEM MESSAGESC8
01 Close data file.
02 Read next.
Format 1 (Z80)
Format 2 (SYS_TYPE_SIERRA)
03 Write next.
Format 1 (Z80)
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
File identifier
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Record number
File identifier
(0000 = read next) Offset within record
Number of bytes to read
00010203 04050607 08090A0B 0C0D0E0F
Task IDFile identifier Record number
Offset Length
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Record number
File identifier
(0000 = read next) Number of bytes to DMA
Checksum
496 STATUS LOG
FILE SYSTEM MESSAGES C8
Format 2 (SYS_TYPE_SIERRA)
04 Zero next.
Format 1 (Z80)
Format 2 (SYS_TYPE_SIERRA)
05 Read logical record.
Format 1 (Z80)
00010203 04050607 08090A0B 0C0D0E0F
Task IDFile identifier Record number
Length Checksum
00010203 04050607 08090A0B 0C0D0E0F
Task IDFile identifier Record number
Length Checksum
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Record number
File identifier
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Record number
File identifier
(0000 = read next) Offset within record
Number of bytes to read
STATUS LOG 497
FILE SYSTEM MESSAGESC8
Format 2 (SYS_TYPE_SIERRA)
06 Write logical record.
Format 1 (Z80)
Format 2 (SYS_TYPE_SIERRA)
07 Zero logical record.
Format 1 (Z80)
00010203 04050607 08090A0B 0C0D0E0F
Task IDFile identifier Record number
Offset Length
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Record number
File identifier
(0000 = read next) Number of bytes to DMA
Checksum
00010203 04050607 08090A0B 0C0D0E0F
Task IDFile identifier Record number
Length Checksum
00010203 04050607 08090A0B 0C0D0E0F
Task IDFile identifier Record number
Length Checksum
498 STATUS LOG
FILE SYSTEM MESSAGES C8
Format 2 (SYS_TYPE_SIERRA)
08 Get data file size.
09 Expand data file size.
0A Decrease data file size.
0B Read/write next.
0C Zero user record on all installed system drives.
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Record number
File identifier
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Data file type
Mode
Data file
Area
Map for
What-if flag
subtype
Misc.
Lo Hi
drive number
For field descriptions, see tables with action 00 on page 494.
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
File identifier of input
File identifier of output
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Record number
File identifier
(0000 = read next)
Unused
STATUS LOG 499
FILE SYSTEM MESSAGESC8
0D Translate to physical address.
0E Read record, first half (Z80 file card only).
0F Read record, second half (Z80 file card only).
Format 1 (Z80)
Format 2 (SYS_TYPE_SIERRA)
10 Write record, first half (Z80 file card only).
11 Write record, second half (Z80 file card only).
Format 1 (Z80)
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Data file type
Mode
Data file
Area
Map for
What-if flag
subtype
Misc.
Lo Hi
drive number
For field descriptions, see tables with action 00 on page 494.
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Record number
File identifier
(0000 = read next) Offset within record
Number of bytes to read
00010203 04050607 08090A0B 0C0D0E0F
Task IDFile identifier Record number
Offset Length
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Record number
File identifier
(0000 = read next) Number of bytes to DMA
Checksum
500 STATUS LOG
FILE SYSTEM MESSAGES C8
Format 2 (SYS_TYPE_SIERRA)
12 Zero multiple logical records.
13 Zero multiple next records.
Format 1 (Z80)
Format 2 (SYS_TYPE_SIERRA)
00010203 04050607 08090A0B 0C0D0E0F
Task IDFile identifier Record number
Length Checksum
00010203 04050607 08090A0B 0C0D0E0F
Task IDFile identifier Record number
Length Checksum
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Record number
File identifier
STATUS LOG 501
FILE SYSTEM MESSAGESC9
).
).
C9 New Data File Primitives Response
The format varies with the action specified in offset 03 of the request mes-sage (C8). The following return codes (offset 03) apply to all actions exceptas noted.
Action 00
Offset Label Field Description
03 Return code 00 OK.09 Out of space (action 09, Z80).0A Cannot read record 1, drive 0 (action 09, Z80).0B Cannot generate spares drive 0 (action 09, Z800C Cannot read record 1, drive 1 (action 09, Z80).0D Cannot generate spares drive 1 (action 09, Z80
20 Invalid file type.21 Invalid subtype.22 Invalid drive number.23 Invalid copy number.
24 Invalid language number.25 Read/write past end of file.26 Drive error.27 Move messages.
28 Out of file descriptors.29 Invalid file mode.2A Invalid file.2B File not open.
2C Invalid task ID.2D File too fragmented.2E Read error on read/write command.2F Write error on read/write command.3C Cannot write backup record (Z80).
Offset Label Field Description
07 Duplexed file indicator 0-simplex file, 1-duplex file (Z80 only)0-386
FSCP
➤
Return code
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
File identifier
Record length
Duplexed file indicator
502 STATUS LOG
FILE SYSTEM MESSAGES C9
Action 01
Action 02
Actions 03 and 04
Action 05
Actions 06 and 07
Action 08
Actions 09 and 0A
What-if flag set.
Task ID
00010203 04050607 08090A0B 0C0D0E0FUnused
Return code
Return code
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Length of data read
Checksum of data read
Task ID
00010203 04050607 08090A0B 0C0D0E0FUnused
Return code
Return code
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Length of data read
Checksum of data read
Task ID
00010203 04050607 08090A0B 0C0D0E0FUnused
Return code
Return code
00010203 04050607 08090A0B 0C0D0E0F
Task ID
UnusedNumber of records in file
Logical recordlength in bytes
Number of spare recordsin file
Fragmentation count
Return code
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Number of 20-kilobyte records that would beused/freed by what-if request
STATUS LOG 503
FILE SYSTEM MESSAGESCA
Action 0B
Action 0C
Action 0D
Actions 0E and 0F
CA New Data File Primitives Write Complete
This message is sent when a file system message C8 data transfer anddata write operation is done.
00 OK.
01 Drive error.
02 Checksum error.
03 No more space.
04 DMA time-out.
Return code
00010203 04050607 08090A0B 0C0D0E0FTask ID
Head
Sector (386)
Cylinder
Unused
Task ID
00010203 04050607 08090A0B 0C0D0E0FUnused
Return code
Return code
00010203 04050607 08090A0B 0C0D0E0FTask ID
Head
Sector (386)
Cylinder
Unused
Return code
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Length of data read
Checksum of data read
FSCP
➤
Task ID
00010203 04050607 08090A0B 0C0D0E0FUnused
504 STATUS LOG
FILE SYSTEM MESSAGES CB
CB Get Phrase Table Pointers
Offset Label Field Description
03 Language area bit 0: phrase area (0-1)bits 1-3: language number (1-5)
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Language area
Drive
Unused
Phrase number (0-5699)
STATUS LOG 505
FILE SYSTEM MESSAGESCC
t driveist)
CC Get Phrase Table Pointers Response
First, check the value of offset 04. If offset 04 = FF, offset 03 holds a returncode from the following list. If offset 04 does not equal FF, offset 03-04holds the phrase number.
00 OK.
20 Invalid area.
21 Invalid drive number.
22 Invalid phrase number.
23 Phrase table not initialized.
24 Invalid table type.
25 Invalid language area number.
26 Phrase entry empty.
27 End of active phrases.
28 Phrase length discrepancy.
29 Formatted play table entry empty.
2A Invalid prompt table.
2B Invalid phrase ID.
2C Invalid phrase entry number.
2D Phrase table empty.
2E Error Initializing phrase table.
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
If offset 04 is not FF,offset 03-04 is the phrase number.
Phrase pointer for this drive(all Fs if phrase does not exist)
Phrase pointer for redundan(all Fs if phrase does not ex
Else, offset 03 is the return code.
506 STATUS LOG
FILE SYSTEM MESSAGES CD
records
CD Put Phrase Table Pointer
CE Put Phrase Table Pointer Response
00 OK.
20 Invalid area.
21 Invalid drive number.
22 Invalid phrase number.
23 Phrase table not initialized.
24 Invalid table type.
25 Invalid language area number.
26 Phrase entry empty.
27 End of active phrases.
28 Phrase length discrepancy.
29 Formatted play table entry empty.
2A Invalid prompt table.
2B Invalid phrase ID.
2C Invalid phrase entry number.
2D Phrase table empty.
2E Error Initializing phrase table.
Offset Label Field Description
03 Language area bit 0: phrase area (0-1)bits 1-3: language number (1-5)
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Language area
Drive
Phrase number
Entry number (1-2)
(0-5699)Phrase ID
Number of logical
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
STATUS LOG 507
FILE SYSTEM MESSAGESD0
.
nly.
D0 Message Information File Operation
00 Open file for read.
01 Open file for write.
02 Clear file.
03 Get next entry.
04 Get next phrase entry.
05 Close file.
D1 Message Information File Operation Response
The format varies with the action specified in offset 03 of the request mes-sage (D0). The following return codes (offset 03) apply to all actions exceptas noted.
Offset Label Field Description
05 Flag Meaning when set (01) varies with the action in offset 03:Action 00, open file for read: Open file with random accessAction 05, close file: Do not reset file position.
Offset Label Field Description
03 Return code 00 OK.01 Invalid drive. Used with actions 03 and 04 only.02 Drive error. Used with actions 03 and 04 only.03 No more entries. Used with actions 03 and 04 o
30 Invalid mode.31 File already open.32 File not open.33 Bad MIF record address.
34 End of file.35 Invalid use count.36 Invalid drive.37 Bad MIF file.38 No active MIF.
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID Flag
Unused
Drive number
FSCP
➤
508 STATUS LOG
FILE SYSTEM MESSAGES D1
Action 00
Actions 01 and 02
Action 03
First, check the value of offset 04. If offset 04 = FF, offset 03 holds a returncode. If offset 04 does not equal FF, offset 03-04 holds the use count.
Action 04
First, check the value of offset 04. If offset 04 = FF, offset 03 holds a returncode. If offset 04 does not equal FF, offset 03-04 holds the phrase number.
Offset Label Field Description
04 Type of entries 00 None01 Messages02 Old phrase-management phrase pointers03 Pre-phrase-management phrase pointers
05 Status flags Bit 0: File not closed.Bit 1: Not at beginning of file.
00010203 04050607 08090A0B 0C0D0E0F
Task ID Status flags
Unused
Type of entries
Return code
Return code
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
00010203 04050607 08090A0B 0C0D0E0F
Task ID
If offset 04 is not FF,offset 03-04 is the use count.
Old message ID
New message ID
Else, offset 03 is the return code.
00010203 04050607 08090A0B 0C0D0E0F
Task ID
If offset 04 is not FF,offset 03-04 is the phrase number.
Phrase ID, drive 0
Phrase ID, drive 1
Else, offset 03 is the return code.
STATUS LOG 509
FILE SYSTEM MESSAGESD2
D2 Put Message Information File Entry
D3 Put Message Information File Entry Response
00 OK.
30 Invalid mode.
31 File already open.
32 File not open.
33 Bad MIF record address.
34 End of file.
35 Invalid use count.
36 Invalid drive.
37 Bad MIF file.
38 No active MIF.
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID Old message ID
New message IDUse count
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
510 STATUS LOG
FILE SYSTEM MESSAGES D4
D4 Miscellaneous Security Functions
00 Allow/disallow message recording.
01 Get security serial number.
D5 Miscellaneous Security Functions Response
00 OK.
01 Not OK.
Offset Label Field Description
04 Feature 0 = Software based pricing Message Hours1 = SCSI security
05 Flag 0 = Allow record 1 = Disallow record
CP➤FS
00010203 04050607 08090A0B 0C0D0E0F
Task ID Flag
Unused
Feature
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task IDSerial Number
Unused
STATUS LOG 511
FILE SYSTEM MESSAGESD6
D6 Fast Disk Copy Intra-Filecard
This command can be used to install a drive, to create a backup drive, toreplace a drive on the same filecard, or to copy a file or a set of files (soft-ware, phrase, etc.) from one drive to another on the same filecard.
When installing, replacing and creating a backup drive, the filecard will alsoinitialize the destination drive before copying the files, and set/reset theDCM/MF bits if necessary after all of the files have been copied.
Offset Label Field Description
03 Subtype 00 Install drive01 Backup drive02 Replace drive03 Copy files04 unused05 unused06 unused07 Read error buffer
06 File type Applies to subtype 03 only:bit 0: software filesbit 1: phrase filesbit 2: system data filesbit 3: message files0xFF: single file
07 File number Applies to subtype 03, file type 0xFF only
00010203 04050607 08090A0B 0C0D0E0F
Task IDSerial Number
Unused
➤ FSCP
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Subtype
Source drive
Destination drive
File type File number
512 STATUS LOG
FILE SYSTEM MESSAGES D7
D7 Fast Disk Copy Intra-Filecard Response
If return code is not 00 and not 02:
Offset Label Field Description
03 Return code 00 Okay02 Errors detected; read error buffer2F Failed to write to destination drive
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID Return code
00010203 04050607 08090A0B 0C0D0E0F
Task ID Return code
Drive number
Buffer sizeFile number
Record number
STATUS LOG 513
FILE SYSTEM MESSAGESD8
D8 Fast Disk Copy Across Filecard
This command can be used to replace a message drive, to convert an ESDIsystem to a SCSI system, or to copy a file or a set of files from one drive toanother on a different filecard.
If subtype = 0, 1, 2 or 3:
Offset Label Field Description
03 Subtype 00 Start replace message drive01 Start ESDI to SCSI conversion for system drive02 Start ESDI to SCSI conversion for message drive03 Start copy file(s)04 Read data05 Write data06 End operations07 Read error buffer
Offset Label Field Description
04 Destination 00 Source filecard01 Destination filecard
07 File type Applies to subtype 03 only:bit 0: software filesbit 1: phrase filesbit 2: system data filesbit 3: message files0xFF: single file
08 File number Applies to subtype 03, file type 0xFF only
➤ FSCP
00010203 04050607 08090A0B 0C0D0E0F
Task ID Subtype
00010203 04050607 08090A0B 0C0D0E0F
Task ID Subtype
Destination
Destination drive
Source drive
File number
File type
Unused
514 STATUS LOG
FILE SYSTEM MESSAGES D9
mand subtype 6 only)
If subtype = 5 (Write Data) or 8 (Write Verify):
D9 Fast Disk Copy Across Filecard Response
If command subtype = 4:
Offset Label Field Description
03 Return code 00 Okay01 End of data02 Errors detected. Read error buffer (applies to com2B Drive not installed2D Serial number mismatch
00010203 04050607 08090A0B 0C0D0E0F
Task ID Subtype
Opcode
Buffer size in bytes
Record number
File number
Number of recordsto write
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID Return code
00010203 04050607 08090A0B 0C0D0E0F
Task ID Return code
Opcode
Buffer size in bytes
Record number
File number
Number of recordsto write
STATUS LOG 515
FILE SYSTEM MESSAGESDA
DA Read File Characteristic
This command will tell the destination drive the file (one file per command)whose length needs to be adjusted.
If subtype = 1:
DB Read File Characteristic Response
If command subtype = 0:
Offset Label Field Description
03 Subtype 00 Read file characteristic01 Configure file characteristic
Offset Label Field Description
03 Return code 00 Okay01 End of directory
00010203 04050607 08090A0B 0C0D0E0F
Task ID Subtype
00010203 04050607 08090A0B 0C0D0E0F
Task ID Subtype
File lengthFile number
Unused
FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID Return code
00010203 04050607 08090A0B 0C0D0E0F
Task ID Return code
File lengthFile number
Unused
516 STATUS LOG
FILE SYSTEM MESSAGES FE
FE CP Software Synchronization
This message can be either CB-in or CB-out. The direction is indicated inoffset 04. There is no response message. This message is also used withdigital line cards.
Offset Label Field Description
03 Status 00 Software initializedFF Initializing, not ready
04 Direction 00 CP to slaveFF Slave to CP
05-08 System signature System serial number.
➤FSCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Status
Direction
System signature
STATUS LOG 517
FILE SYSTEM MESSAGES
000000
3.2 COMMON CODES
Several codes used in multiple file system messages are described here:
• Drive action and status codes
• Read and write data types
• File numbers
• Internal file card status codes
• File card return codes
3.2.1 Drive Action and Status Codes
Table 3-1. Drive Action Codes
Action Code Description
05 Read duplexed record from selected drive.06 Write duplexed record on selected drive.08 Write half record on second half of selected drive.09 Read half record from second half of selected drives.
10 Write half record on first half of D0 and D1.11 Read half record from first half of D0 or D1.12 Write record on D0 and D1.13 Read record from D0 and D1.
15 Read duplexed record on D0 and D1.16 Write duplexed record on D0 and D1.18 Write half record on second half of D0 and D1.19 Read half record from second half of D0 or D1.
20 Write half record on first half of selected drive.21 Read half record from selected drive.22 Write record on selected drive.23 Read record from selected drive.
Table 3-2. Drive Status Codes
Status Code Description
0A Seek time out.0B Step time out.0C Cannot home the drive.0D Operation time out.
0E Address verify error.0F ECC error.10 Address verify sequence.11 Drive fault error.
STATUS LOG 519
FILE SYSTEM MESSAGES
—depends on data et 05-06)
r node numberer of group (0080,
(0, 20, 40)
hin base
r
(0-49)
yte values:bere:
- 2
list
two records)t
ue on next page.)
3.2.2 Read and Write Data Types
These codes are used in file system messages 28, Read Data, and 34,Write Data. They appear in offset 04 and describe not only the data type,but the type of parameter in offset 05-06.
Table 3-3. Data and Parameter Types
Data Type (offset 04) Parameter Descriptiontype (offsCode Description
00 Any data on track Track number01 Available user number bit map Unused02 Local AMT table, third track Unused03 Local user or node record, single User record number o04 Local user or node records, multiple First user record numb
0085, 008A, …)05 System group lists, multiple System group number06 Local AMT table, first track Unused07 Local AMT table, last track Unused
08 Program overlays Number of records wit09 Class-of-service tables Unused0A Statistics segments (256 byte entries) Starting record numbe0B Local AMT table, second track Unused
0C System status table Unused0D System group list System group number0E Menus Menu number, 0 - ?0F Download code or phrase table The field holds two 1-b
Offset 05: record numOffset 06: data sub-typ
00 OS - 301 AC - 702 Trees - 703 SMT - 7
04 RPT OVLY MGR05 IPL - 606 Phrase tables07 In-RAM phrase
08 File card code (09 Used phrase lis
(Data sub-types contin
520 STATUS LOG
FILE SYSTEM MESSAGES
only)6 only)
r
trieved the data area
the software area77
the data area: 0000-
ed)
—depends on data et 05-06)
0F Download code or phrase table (continued) 80 Z80 CBB (FS 1681 Z80 CBO (FS 182 FS 38683 CP IPL2x
84 CP IPL385 EPU86 TCAP87 Menus
88 VRTX 3289 RTSCOPE8A VMM8B NMI (IPL4)
8C Global software8D DLC8E FS IPL191 T1 software
10 Report selection parameters Starting record numbe11 Record type Unused12 CDR Block number to be re13 New addition to CPU data records (AMT, …) Record number within
14 New addition to CPU software area Record number within15 Community number Valid values are: 00-C16 Attendant schedule number Valid values are: 00-C17 Multiple community number 00, 0A, 14, … BE18 Raw phrase Phrase number26 Record 50 Record number within
0063
Table 3-3. Data and Parameter Types (Continu
Data Type (offset 04) Parameter Descriptiontype (offsCode Description
STATUS LOG 521
FILE SYSTEM MESSAGES
3.2.3 File Numbers
File numbers appear in some of the file system messages.
Table 3-4. File Numbers
File Number Description
00 Users01 Company records03 Attendant records
04 System status table (SST)05 Class of service (COS)06 Statistics07 Call detail record (CDR)
08 System groups09 Name table0A Software file system 3860B Software Z80 control bus overlays (CBO)
0C Software Z80 control bus base (CBB)0D Software menus0E Software overlays0F Software central processor initial program load 2 (IPL2)
10 Software central processor initial program load 3 (IPL3)11 Software central processor operating system12 Software central processor system manager task (SMT)13 Software central processor application code (AC)
14 Software central processor trees15 Software extended processing unit (EPU)16 Software VRTX32 operating system17 RTSCOPE
18 Termcap (TCAP)19 Record 3 (REC3)1A Phrase record numbers1B Phrase record number allocation bitmap
1C Prompt master list1D Prompt-to-phrase table, language 01E Prompt-to-phrase table, language 11F Prompt-to-phrase table, language 2
20 Phrase in-RAM list, language 021 Phrase in-RAM list, language 122 Phrase in-RAM list, language 223 Phrase used list, language 0
522 STATUS LOG
FILE SYSTEM MESSAGES
24 Phrase used list, language 125 Phrase used list, language 226 Z80 prompt table file27 CPU file system data area
28 CPU file system software area29 System configuration file2A Software virtual machine monitor (VMM) file2B Software non-maskable interrupt (NMI) handler file
2C Global software (SP)2D CP dump record (record 50)2E Report parameters2F File system status log
30 System performance log31 Record allocation table32 Message file space33 Translation tables
34 Software DLC35 Record allocation table backup36 Network card application software37 FDDI software
38 T1 software39 ISDN software3A Network card error log file3B 16 nodes, 16 AMT’s4B 16 nodes, 16 NMT’s
5C ACP 386 file5D ACP 188 file5E Temporary file5F Port configuration
Table 3-4. File Numbers (Continued)
File Number Description
STATUS LOG 523
FILE SYSTEM MESSAGES
3.2.4 Internal File Card Status Codes
These codes are reported in certain file system messages. These codesare also logged into file 2F, the file system status log.
Table 3-5. Internal File Card Status Codes
Area Code Description
0000 Old assert type0FFF ASM assertion
SRAM and IPL
1000 ‘Assert’ failed1001 Error type not found in error table
1101 SRAM validity error1102 SRAM I/O status read error1103 SRAM I/O status write error1104 SRAM I/O status recovery error
1201 IPL system table error1202 IPL system table warning1203 IPL boot error1204 IPL disk level error
DCM
2001 DCM I/O error2002 DCM drive error2003 DCM write verify error
2004 DCM system table write warning2005 DCM system table write error2008 DCM tempfile failure2009 DCM SST write error
AT3001 AT bad drive3002 AT RAM full3003 AT record validity check
524 STATUS LOG
FILE SYSTEM MESSAGES
ation table) to disk
ion timenitialization time
failedew recordcking problem in
nds: not all file card
ve been cleared. Error a crash.ve been overwritten
rror and abortedonciliation. After recon-d.g alloc bitsetting alloc bits
xtended address
nued)
MF
4000 Update of primary copy of RAT (record allocfailed
4001 Update of backup copy of RAT failed4002 RAT could not be read from disk at initializat4003 RAT backup could not be read from disk at i
4004 Recovery of primary RAT from backup copy4005 Speech buffer write failed, must allocate a n4006 Record appears to be already allocated: a lo
record allocation mapping4007 Translated error to one that the CP understa
internal errors can be sent directly to the CP4008 SRAM check-byte corrupted: SRAM may ha
occured while recovering record space after4009 SRAM entry count corrupted: SRAM may ha400A RAT/SRAM reconciliation encountered an e400B SRAM cleared by MF code after error or rec
cilliation, the SRAM data is no longer neede400C MF bit-set failed: locking problem with settin400D MF bit-reset failed: locking problem with res400E MF de-allocation of unneeded records failed400F MF writing failed4010 MF reset channel
Network5000 Batch network message with no destination6000 Batch network message with invalid EAR (e
record)
Table 3-5. Internal File Card Status Codes (Conti
Area Code Description
STATUS LOG 525
FILE SYSTEM MESSAGES
d
lized the logs wrong
are procedure exe-
nued)
General System Hardware
A000 Exception: divide errorA001 Exception: debug exceptionA002 Exception: ??A003 Exception: breakpoint
A004 Exception: overflowA005 Exception: bounds checkA006 Exception: invalid opcodeA007 Exception: coprocessor not available
A008 Exception: double faultA009 Exception: coprocessor segment overrunA00A Exception: invalid TSSA00B Exception: segment not present
A00C Exception: stack exceptionA00D Exception: General protectionA00E Exception: page faultA00F Exception: ???A010 Exception: coprocessor error
General System
A020 Invalid interrupt occurredA021 ISR_BAD encounteredA022 NMI with no sourceA023 The watchdog barked
A024 Parity error NMIA025 Power fail NMI occurredA026 Received a NULL segment selectorA027 Software problem—data structure misaligne
A028 NVRAM status log vars messed up, re-initiaA029 DRAM pointer to status logging area/size waA02D Default interrupt occurred
A030 Drive 5V power faultA031 Drive write violationADDD File card warm boot performed, restart softw
cutedAEEE File card initialization occurredAFFF General error
Table 3-5. Internal File Card Status Codes (Conti
Area Code Description
526 STATUS LOG
FILE SYSTEM MESSAGES
ot zero
le
ndexecute a command
rmational only)
n disabled.
nued)
SBI-Related
B000 SBI in wrong modeB002 SBI DMA buffer not within data segment
B004 I380’s DMA byte count for SBI not expiredB005 Bad SBI INT source bitsB006 SBI DMA data under rangeB007 SBI DMA data over range
B008 SBI CRC errorB009 CB checksum calculation failedB00A CRC error in transmitted control packetB00B CRC error in received control packet
B00C SBI DMA byte count is MAX_SBI_DMAB00D SBI DMA not allowed at presentB00E SBI DMA error, alf not zero, but byte count nBEEE SBI re-initialization occurredBEEF SBI clear occurred
SCSI Disk-RelatedC000 SCSI mode select data mismatch in boot tabC001 SCSI drive failed security test
SCSI Drive
C101 Device present but failed to execute commaC102 Device present but timed out while trying to C103 Device is taken out of serviceC130 Check-condition status received from driveC131 Requested drive module does not existC132 Requested drive module does not exist (info
C140 Medium or hardware error on driveC141 No spare blocks availableC142 Unknown G-list formatC143 Information-only disk error
C144 Serious disk errorC145 G-list exceeds the thresholdC146 Tempfile-A not recoverableC147 Tempfile-B not recoverable. Crash protectio
C148 Error reassigning the bad blockC149 Error reading G-listC150 Write/verify miscompare
Table 3-5. Internal File Card Status Codes (Conti
Area Code Description
STATUS LOG 527
FILE SYSTEM MESSAGES
een completed expectedexpectedet were less than
t were more than
less than expectedore than expected
nd
existent initiator, target
d out.rming request sense
nued)
SCSI Firmware
C201 SCSI driver not ready: initialization has not bC230 Data underrun: data received was less thanC231 Data overrun: data received was more than C232 CDB underrun: command bytes sent to targ
expectedC233 CDB overrun: command bytes sent to targe
expectedC234 Status underrun: status bytes received wereC235 Status overrun: status bytes received were mC236 Illegal command: target rejected the comma
SCSI Bus
C330 Parity errorC331 Unexpected bus freeC332 Cannot communicate with requested deviceC333 Unexpected SCSI-bus reset
C334 Illegal phase detectedC335 Message rejected by targetC336 Reselection abortedC337 Reselection from target has selected a non-
or logical unit numberC338 Reset command failedC339 Selection abortedC33A Unknown message bytesC33B Selection timeout
SCSI Chip
C401 SCSI chip initialization failedC402 SCSI chip malfunctionC430 Selected device not busy but command timeC431 Received check-condition status while perfo
Table 3-5. Internal File Card Status Codes (Conti
Area Code Description
528 STATUS LOG
FILE SYSTEM MESSAGES
d ID
ata
thte
nued)
SCSI Request
C501 Request queue fullC502 Invalid bus ID specifiedC503 Invalid target ID specified
C504 Invalid LUN specifiedC505 Invalid LBA specifiedC506 Invalid LBA length specifiedC507 Invalid request code specified
C508 Invalid request flag specifiedC509 Invalid data buffer specifiedC50A Specified buffer size too smallC50B Invalid event ID specified
C50C Invalid event ID flag specifiedC50D Request is invalid for device type at specifieC50E Device at specified ID is present but offlineC50F NULL DIOS pointer encountered
C510 Wrong special requestC511 Invalid queue element pointerC512 Invalid queue nameC513 Invalid type of queue operation
C514 Queue is emptyC515 Queue head/tail pointer is NULLC516 Queue element was not foundC517 Invalid queue element number specified
C518 Wrong queue element found during searchC519 RRQ error: unable to reset bus
C520 RRQ error: bus device reset failedC521 RRQ error: test unit ready failedC522 RRQ error: inquiry failedC523 RRQ error: request sense failed
C524 RRQ error: rezero unit failedC525 RRQ error: enable drive failedC526 RRQ information: log of reset and requeue dC527 Queue warning: queued with no req in simC528 No IOS pointer found in CCBC529 Attempting to set up for DMA with zero lengC52A Received report with posted rflag already seC52B Attempting to double post a request respons
C530 Request abortedC531 Request aborted due to resetC532 Auto request sense failure
Table 3-5. Internal File Card Status Codes (Conti
Area Code Description
STATUS LOG 529
FILE SYSTEM MESSAGES
ware
re
h no sense
ium
nued)
SCSI Request (cont) C533 Open request already activeC534 Request rejected by the driver
SCSI Drive Module
C630 False alarm from remote terminator fail hardC631 Remote terminator failedC632 Remote terminator setup failedC633 False alarm from local terminator fail hardwa
C634 Local terminator failedC635 Local terminator setup failedC636 False alarm from logic violation hardwareC637 Hardware logic violation
C638 Hot plug errorC639 Drive module 5V errorC640 Hot Plug interrupt notificationC641 Open online command completeC642 Drive module 5V failed int notificationC643 Drive module removed from service
C644 Open Online command failedC645 Hot Plug event forced reset and requeueC646 Hot Plug event module statusC647 Close Online command in progress
C648 Close Online command completedC649 Close Online command failed
C730 Unknown type errorC731 Tape drive caused a bus resetC732 Tape drive was active during a bus resetC733 Tape drive was idle during a bus reset
C734 Tape drive status was in check condition witC735 Tape drive is not ready
Tape Drive
C736 Medium error on tape driveC737 Hardware error on tape driveC738 Illegal parameter in the command descriptorC739 Device reset or tape changed
C73A Write protected block encounteredC73B Tape drive encountered blank tape or EODC73C Tape drive encountered end-of-partition/medC73D Tape drive encountered a file or set markC73E Tape drive encountered early warning markC73F No cartridge found in tape drive
C740 Tape changedC741 Tape drive reset occurred
Table 3-5. Internal File Card Status Codes (Conti
Area Code Description
530 STATUS LOG
FILE SYSTEM MESSAGES
it
Q status bit=1
iteon
tss
tor maximum sector count
nued)
Tape Drive (cont)C742 Tape drive mode page data changedC743 Tape drive configuration failedC744 Tape data received was less than expected
SCSI Miscellaneous
CF00 Unknown resultCF01 DMA initialization failedCF02 NULL CCB pointer foundCF03 Cannot allocate memory for a CCB
CF04 Host basher errorCF05 Host basher entry number exceeded the lim
ESDI Disk-Related
E001 Disk was not presentE002 Request DRB not in initial state upon entryE003 Aborted seek command
E004 Before seek command the ESDIC got an SRE005 Read or write completion errorE006 DMA byte count did not expire after read/wrE007 CMD-complete received after seek completi
E008 DMA channel release errorE009 Request DMA byte count greater than 24 biE00A Could not convert logical to physical addresE00B Seek operation unsuccessful
E00C .Chk1 or .Chk2—bad check bytesE00D .STATE—not in proper stateE00E .LMEM_Ptr address not doubleword alignedE00F Utility command execution failed
E010 Bad value for .REQUEST fieldE011 Seek address out of boundsE012 Read/write failure; cannot find specified secE013 Sector count field in the DRB is greater than
Table 3-5. Internal File Card Status Codes (Conti
Area Code Description
STATUS LOG 531
FILE SYSTEM MESSAGES
station
d
ero
rted. No retries after t a reset ESDIC and
f servicereturnednd restart drive chain se the problem. It is .
uest. Reset ESDIC st probably did not
nued)
ESDI Disk-Related (cont)
E014 DMA data overrun errorE015 Bad drive number or status recordE016 DRB’s .SCT field exceeds allowed sizeE017 Function can only be performed on a format
E018 Buffer not contained in data segmentE019 ECC error on single sector correctedE01A Requested drive is out of serviceE01B This drive caused previous reset request
E01C Command response took longer than alloweE01D DRB linked list is full for this driveE01E DRB’s .SCT (sector count) field is equal to zE01F Seek failure: drive busy
E020 Read/write failure: ID/data error (STR=24)E021 Read/write failure: Missing byte sync patternE022 ESDI command failure: drive attention asse
this error because the drive is locked up. Burestart will occur.
E023 Verify failure
E024 ECC error, correctableE025 Request returned because the drive is out oE026 Reset-request logic had a problem, request E027 ESDIC command locked up. Reset ESDIC a
will occur. This request probably did not cauoften caused by a drive power-supply failure
E028 ESDIC reset requestE029 Spinup failedE02A Drive 5V-power fault detected during this req
and restart drive chain will occur. This requecause the problem, so it will be restarted.
E080 Servicing of this request has not started
Table 3-5. Internal File Card Status Codes (Conti
Area Code Description
532 STATUS LOG
FILE SYSTEM MESSAGES
Logged when a
ration outstanding
reater than MAXay_bufive stat)anyway
ing sent
equests in LLB
uffer
very
nued)
ESDI General
E100 Last request was already retried after RRQ.request causes a RRQ a second time.
E101 Bad software stateE102 Cannot have more than one non-VRTX opeE103 Bad logical to physical conversion
E104 Drive number parameter passed is zero or gE105 Excessive command parameters in cmd_arrE106 Motor control option is not enabled (buf = drE107 Aborted seek command is being processed
E108 Disk DMA size greater than 65 kilobytesE109 DRBptrs_tobe_requeued structure is fullE110 DMA buffer not doubleword aligned
ESDI Drive and DRB
E200 ESDIC busy when new ESDIC command beE201 Posting response to an already posted DRBE202 Command response indicated drive busyE203 LDRB_Ptr pointing to unposted DRB
E27A Incorrect drive numberE27B DRBQ was about to dequeue over existing r
E27C Drive’s statistics invalid, bad ChkbytNE27D Attempt to read DRB pointer past end of LLbE27E DRB pointer has been corruptedE27F DRB being serviced has been ‘reused’
E280 Bad event flag address/maskE281 Error setting drive select mapE282 Drive stat error: null .LDRB_PtrE283 DRB at .LDRB is bad
E284 Bad start_request, .LDRB_Ptr not loadedE285 Drive init from statistics failsE286 Cylinder number is badE287 No drives found during error recovery
E288 Attempts to group-assign failed in error recoE289 Failure occurred in error recovery routine
ESDI Disk VRTXE300 Bad VRTX return codeE301 Bad return from event flag posting
Table 3-5. Internal File Card Status Codes (Conti
Area Code Description
STATUS LOG 533
FILE SYSTEM MESSAGES
done
ed from RnRery
.RCODE set to error
andseek commanday occur during for-
ne secondrvice
one secondESDICmandests returned
Statusses an ESDIC reset. m.r seeks in progressp
nued)
ESDI Drive Monitoring
E401 High soft error rateE402 Log the drive status that caused RRQ to be E403 Group assignment failed
E404 Drive should be readyE405 Spinup request restarted after being requeuE410 Information collected during new error recov
ESDI Setup_Next_Request
E500 Trying to ‘lose’ a request. May be caused bywithout RNC-bit before finished.
E501 Switched buffer, but no requests are in it
ESDI Drive Execution
E600 ESDIC command execution failsE601 Time-out on wait for INT from ESDIC commE602 Time-out on completion of INT from ESDIC E603 Both copies of heads’ defect list were bad. M
matting of a bad drive.E604 ESDIC command time-out took more than oE605 Spinup taking too long; drive taken out of seE606 More than three drive varietiesE607 Drive init from statistics fails
E608 Recalibration taking too longE609 Seek taking too longE60A Seek command execution failedE60B Bad seek status
E60C Bad response from Rd commandE60D 80380’s DMA byte count did not expireE60E ESDIC busy for too longE60F Drive should be ready and is not
E610 Wait_for_return_from_isr waited more than E611 Received a reset request as response from E612 Isr_tick (Disk_WDog) found a hung disk comE613 Drive has been taken out of service, all requ
E614 Drive gave a bad response to a Sense Unit E615 Too many consecutive hard disk errors. Cau
The reset and requeue may clear the probleE616 Spurious ESDIC INT when no commands oE617 More than three drive varieties during spinu
ESDI Drive I/O EFFF For testing ERRHAND
Table 3-5. Internal File Card Status Codes (Conti
Area Code Description
534 STATUS LOG
FILE SYSTEM MESSAGES
3.2.5 File Card Return Codes
These codes are reported in most file system messages.
Table 3-6. File Card Return Codes
Return Code Description
81 End of file82 Extent not found83 Request too long
84 Not implemented85 I/O error86 Invalid record number87 Invalid transfer length
88 Invalid buffer pointer89 No free buffer8A Invalid file allocation8B Invalid file length
8C Invalid file attribute8D File already exists8E Bad record8F Table limit reached
90 Invalid drive number91 Invalid file number92 Not found93 Record already exists
94 Invalid record95 Fatal error96 Static RAM validity error97 Invalid drive state
98 Drive error99 Drive not formatted9A Drive not installed9B Drive already installed
9C Serial number mismatch9D File not found9E Drive not initialized9F Write verify error
A0 System table errorA1 DCM invalid parameter listA2 DCM invalid requestA3 DCM invalid disk address
STATUS LOG 535
FILE SYSTEM MESSAGES
A4 Invalid drive typeA5 Drive 0 errorA6 Invalid file record sizeA7 Failed Spin Up ControlF1 Attempt to set message
position beyond EOM.F2 Consistency check failed.F3 AT_Get_Buffer failed.F4 Message IDs (less stn #)
mismatch.F5 System signature mis-
match.F6 Message header check-
sum mismatch.F7 Use count 0 in message
header.FF Bug in message file soft-
ware.
Table 3-6. File Card Return Codes (Continued)
Return Code Description
536 STATUS LOG
FILE SYSTEM MESSAGES
re 250
00 02
re 350
0 00 00 00
3.3 FILE CARD STATUS FOR OVERTURE 250 AND OVERTURE 350
The status of the primary file card is conveyed in a 10-byte string thatappears at the end of the power-on sequence, as shown in Figures 3-1 and3-2, and in file system messages 41 and 61 (General ConfigurationResponse for File Cards). In general, the file card status shows the resultsof the booting process. Fields in the file card status string are identified inFigure 3-3.
Figure 3-1. Screen at End of Power-On for Overtu
PIPL ROOT VERSION 2005
System Type: 250
SYSTEM FILE RAM: 00
ENTER BOOT COMMAND:
Board type is: CCF
SYSTEM BOOT AREA B
Looking for Combo File System...
SYSTEM FILE STATUS: 00 01 00 01 00 00 00 00
Figure 3-2. Screen at End of Power-On for Overtu
IPL ROOT VERSION 910000.0System Type: 350
PRIMARY FILE CARD STATUS: 00 03 00 03 00 00 0 BOOTED FROM SYSTEM DRIVE PAIR FILE SYSTEM RAM: 00
ENTER BOOT COMMAND:
538 STATUS LOG
FILE SYSTEM MESSAGES
3.3.1 File Card Status Fields
Byte 0 contains boot status; Table 3-7 describes valid boot status values.Byte 7 is set to 0x43 if the system is a standby redundancy system, other-wise it is set to 0 (Overture 350 only). Byte 8 indicates the status of thestandby redundancy system; Table 3-8 identifies the bits that map tostandby redundancy status (again, only applies to Overture 350). Byte 09 isset to 02, indicating a SCSI 386 file system.
Table 3-7. Boot Status Codes
Code Description0x03 System running drives error.0x20 Fatal error detected.0x22 Drive serial number mismatch.
Table 3-8. Standby Redundancy Status Bits (Overture 350)
Bit Status0 1 = card is inactive
0 = card is standby2 1 = redundant
0 = non-redundant6 1 = termination error (card is not properly configured for
standby redundancy)
Bootstatus
Map fordrives installed
Map fordrives running
Unused
Unused
Status of standby redundancy system
Standby redundancy flag (0x43 or 00)
Figure 3-3. File Card Status Fields
SCSI 386 File System (02)
00 01020304 05060708 09(Overture 350 only)
(Overture 350 only)
STATUS LOG 539
CHAPTER 4: LINE CARD MESSAGES
This chapter provides descriptions of all control bus messages used with line cards. For information onreading these descriptions, see “Control Bus Messages” on page 35. All values in the illustrations arethe bytes’ offsets, not sample data.
Request and response messages are grouped together and organized by the message type of therequest. These can be found by checking the numbers in the upper-outer corners of the pages whileflipping through the chapter. Or, message descriptions can be found by checking the index below.
Index
Numerics01 DLC Answer Call, 54502 DLC Answer Supervision, 54703 DLC Go On-Hook, 54804 DLC Flash Hook, 54905 DLC Seize Line, 55006 DLC Return TIC Port Type, 55107 DLC Configure TIC Port, 55308 DLC Get Pulse Digit, 55509 DLC Set Incoming Dial Pulses, 5560A DLC Set Outgoing Wink, 5570C DLC Special Off-Hook, 5580D DLC Special On-Hook, 55910 Second Level SW Download Query, 56011 DLC TIC Diagnostics, 56112 Begin Second Level Download, 56313 Second Level Download DMA Setup, 56414 Second Level Download DMA Done, 56515 Second Level Download Complete, 56616 Second Level SW Download Sync, 56717 Clear Second Level Alarms, 56818 Download Data Start, 56919 Download Data Done Query, 5701A Set Number of Digits, 57120 Auto Answer Command, 57221 Go Off Hook, 57322 Return Called Party ID, 57423 TIC Event Poll Command, 57524 Reconnect Call Command, 57725 Message Waiting Command, 57826 Dial Digit Comman, 57927 Datacom & Error Command, 58028 Set Pilot Number, 582
STATUS LOG 541
41 DLC Answer Call Response, 54642 DLC Answer Supervision Response, 54743 DLC Go On-Hook Response, 54844 DLC Flash Hook Response, 54945 DLC Seize Line Response, 55046 DLC Return TIC Port Type Response, 55147 DLC Configure TIC Port Response, 55448 DLC Get Pulse Digit Response, 55549 DLC Set Dial Pulses Response, 5564A DLC Set Outgoing Wink Response, 5574C DLC Special Off-Hook Response, 5584D DLC Special On-Hook Response, 55950 Second Level SW Download Response, 56051 DLC TIC Diagnostics Response, 56152 Begin Second Level Download Response, 56353 Second Level Download DMA Setup Response, 56454 Second Level Download DMA Done Response, 56555 Second Level Download Complete Response, 56656 Second Level SW Download Sync Response, 56757 Clear Second Level Alarms Response, 56858 Download Data Start Response, 56959 Download Data Done Response, 5705A Set Number of Digits Response, 57160 Auto Answer Command Response, 57261 Go Off Hook Response, 57362 Return Called Party ID Response, 57463 TIC Event Poll Command Response, 57664 Reconnect Call Respons, 57765 Message Waiting Response, 57866 Dial Digit Command Response, 57967 Datacom & Error Response, 58168 Set Pilot Number Response, 58280 Purge Event Queue, 58381 Get Input Event, 58482 Transmit Speech, 58583 Read Speech Buffer Response, 58884 Read Speech Buffer Done, 59085 Receive Speech, 59286 Write Speech Buffer Response, 59487 Write Speech Buffer Done, 59588 Reset Channel, 59789 Dial, 5998A Get Signal Transition, 6008B Signal Detect Begin, 6018C Signal Detect End, 6028D Set Dial Tone, 603
542 STATUS LOG
8E Enable Autovon Keys, 6048F Stop Special Phrase, 60590 Purge Event Queue Response, 58391 Get Input Event Response, 58492 Read Speech Buffer, 58793 Read Speech Buffer Set Response, 58894 Transmit Speech End, 59095 Write Speech Buffer, 59396 Write Speech Buffer Set, 59497 Receive Speech End, 59698 Reset Response, 59799 Dial Response, 5999A Get Signal Transition Response, 6009B Signal Detect Begin Response, 6019C Signal Detect End Response, 6029D Set Dial Tone Response, 6039E Enable Autovon Keys Response, 6049F Stop Special Phrase Response, 605AA0 TIC Detect, 606A1 General Configuration Status Request, 607A2 General Read Memory, 608A3 General Write Memory, 609A4 Return Code Level, 610A9 Read FAX Buffer Set, 611AA Read Cover Sheet Done, 613AB Get FAX ID, 614BB0 Detect Response, 606B4 Return Code Level Response, 610CC4 DLC Set Dial Tone, 616C5 DLC Monitor Call, 617CA Read Cover Sheet Done Response, 613CB Get FAX ID Response, 615DD4 DLC Set Dial Tone Response, 616D5 DLC Monitor Call Response, 617EE1 DLC Set ID Response, 607E2 General Read Memory Response, 608E3 General Write Memory Response, 609FFD DSP Second Level Download, 618FE DLC or DSP Ready, 620
STATUS LOG 543
LINE CARD MESSAGES 01
e ring-down he desired swer” is in effect).
000000
01 DLC Answer Call
Tells the DLC to go off-hook to answer an incoming call, if any, on thischannel; requests VTIC to report an incoming call.
Offset Label Field Description
03 Number of rings Number of rings (only on trunks that provide thindication). DLC answers incoming call when tnumber of rings are detected (unless “force an
06 Force-answer flag
Bit 0:00 Do not force answer.01 Force answer.
Bit 1:01 Reset ring counter
CP➤DLC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Number of rings
Time-out interval,in 25 ms units
Force-answer flag(not used by VTIC)(not used by VTIC)
STATUS LOG 545
LINE CARD MESSAGES41
41 DLC Answer Call Response
00 Enough rings detected, incoming call answered.
01 None or not enough rings detected, but call answered due to forced answer.
10 None or not enough rings detected—timeout.
F0 Call not answered—line error, no line.
Offset Label Field Description
04 Call type 00 No incoming call01 Direct02 Ring-no-answer03 Busy04 ForwardFF Unknown
05 Calling party ID status
00 OK10 No incoming callF0 Bad
DLCCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Call type
Calling party ID status
Calling part ID
546 STATUS LOG
LINE CARD MESSAGES 02
02 DLC Answer Supervision
Tells the DLC to return answer supervision to a trunk (E&M and T1).
42 DLC Answer Supervision Response
00 OK.
01 DLC not answering an incoming call—disconnect.
F0 No line.
CP➤DLC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
DLCCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
STATUS LOG 547
LINE CARD MESSAGES03
03 DLC Go On-Hook
Tells the DLC or VTIC to go on-hook on this channel.
43 DLC Go On-Hook Response
00 OK.
10 Near-end on-hook time-out.
F0 Line error, no line.
Offset Label Field Description
04 Subcode VTIC subcodes:00 Link up01 MSB02 Link down03 Link not ready
CP➤DLC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Time-out interval,in 25 ms units
DLCCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Subcode (VTIC)
548 STATUS LOG
LINE CARD MESSAGES 04
04 DLC Flash Hook
Tells the DLC or VTIC to flash on this channel.
44 DLC Flash Hook Response
01 OK
F0 Failed
Offset Label Field Description
04 Subcode VTIC subcodes:00 Link up01 MSB02 Link down03 Link not ready
CP➤DLC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Length of flash,in 25 ms units
DLCCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Subcode (VTIC)
STATUS LOG 549
LINE CARD MESSAGES05
til
05 DLC Seize Line
Tells the DLC or VTIC to seize the line for outcall or for message waiting.
45 DLC Seize Line Response
Tells the CP that the line is either secured or there is an incoming call.
00 OK.
01 Glare (call collision); CP will send 0x03 (on-hook).
02 Glare (call collision); CP will no send 0x03 (on-hook).
10 Timeout.
F0 Line error, no line.
Offset Label Field Description
03-04 Time-out interval
Time-out interval, in 25 ms units. Time to wait uneither the line is seized or a “glare” is detected.
Offset Label Field Description
04 Subcode VTIC subcodes:00 Link up01 MSB02 Link down03 Link not ready
CP➤DLC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Time-out interval,in 25 ms units
DLCCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Subcode (VTIC)
550 STATUS LOG
LINE CARD MESSAGES 06
)
06 DLC Return TIC Port Type
This message gets the type of a TIC port from the DLC if possible.
46 DLC Return TIC Port Type Response
Offset Label Field Description
03 Port type TIC port type:0H Loop-start trunk1H Ground-start trunk2H DID trunk3H E&M trunk4H T1 trunk, E&M signalling5H T1 trunk, loop-start6H T1 trunk, ground-start7H CEPT trunk, R2 signalling8H LS/GS ATIC, port ignores signalling (MID0E VTICF0H No hybrid/TIC present
CP➤DLC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
DLCCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Port type Specification
STATUS LOG 551
LINE CARD MESSAGES46
04 Specification If loop-start or ground-start analog trunk:0H 600 ohm1H 900 ohm
If DID trunk:00H Normal use, short loop01H Loopback mode, short loop02H Normal use, long hoop03H Loopback mode, long hoop
If E&M analog trunk:00H 600 ohm, 4 wire voice01H 900 ohm, 4 wire voice02H 600 ohm, 2 wire voice03H 900 ohm, 2 wire voice
If T1 trunk (E&M, LS or GS):Not used
If VTIC01 VTIC/A for AT&T02 VTIC/N for NT03 VTIC/R for ROLM
Offset Label Field Description
552 STATUS LOG
LINE CARD MESSAGES 07
M may use DTMF or
07 DLC Configure TIC Port
Configures a TIC through the DLC.
Offset Label Field Description
03 Trunk type Trunk type:0H Loop-start trunk1H Ground-start trunk2H DID trunk3H E&M trunk4H T1 trunk, E&M signalling5H T1 trunk, loop-start6H T1 trunk, ground-start7H CEPT trunk, R2 signalling8H LS/GS ATIC, port ignores signalling (MID)F0H Illegal trunk
04 Specification If loop-start or ground-start analog trunk:0H 600 ohm1H 900 ohm
If DID trunk:00H Normal use, short loop01H Loopback mode, short loop02H Normal use, long hoop03H Loopback mode, long hoop
If E&M analog trunk:00H 600 ohm, 4 wire voice01H 900 ohm, 4 wire voice02H 600 ohm, 2 wire voice03H 900 ohm, 2 wire voice
If T1 trunk (E&M, LS or GS):Not used
If E1 (CEPT) R2:00H Do not use CRC401H Use CRC4
05 E&M option If DID or E&M trunk (analog or T1):00 Pulse input, immediate start 01 Pulse input, wink start 02 DTMF input, immediate start 03 DTMF input, wink start04 MF input, immediate start 05 MF input, wink start
(MF input is supported on E&M only. Both DID and E&Pulse input.)
CP➤DLC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Trunk type
Specification
E&M option
UDLC option
STATUS LOG 553
LINE CARD MESSAGES47
47 DLC Configure TIC Port Response
00 OK.
01 Illegal/conflicting parameters.
F0 No TIC.
06 UDLC option UDLC only:0 Selects u-law PCM encoding for ATIC1 Selects A-law PCM encoding for ATIC
Offset Label Field Description
DLCCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
554 STATUS LOG
LINE CARD MESSAGES 08
or
igits field
08 DLC Get Pulse Digit
This message gets the pulse digit from DID and E&M trunks.
48 DLC Get Pulse Digit Response
This message returns the incoming dial pulse digits (if any).
Offset Label Field Description
03-04 Timeout Timeout interval in 25 msec units. Time to wait fincoming dial pulses.
Offset Label Field Description
03 Return code Return codes:1H-9H Length of pulse digits in the following d10H Timeout (no pulse digits were received)
04-0C Pulse digits Incoming pulse digits (up to 9 digits)00H-09H = ‘0’ - ‘9’FFH = Padding character
CP➤DLC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Timeout
DLCCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID Return code Pulse digits
STATUS LOG 555
LINE CARD MESSAGES09
.
.
= 300 ms.
09 DLC Set Incoming Dial Pulses
This message sets the widths of the incoming dial pulse and inter-digit gap(valid only on DID and E&M trunks). The default or current settings will bechanged to the new values indicated in the message.
49 DLC Set Dial Pulses Response
This message returns the result of setting the dial pulse.
Offset Label Field Description
03 Break width Minimum width of break in 5 ms units. Default = 60 ms
04 Make width Minimum width of make in 5 ms units. Default = 40 ms
05 Gap width Minimum width of inter-digit gap in 5 ms units. Default
Offset Label Field Description
03 Return code Return codes:0H Okay1H Illegal or conflicting parameter(s)
CP➤DLC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Break width Gap width
Make width
DLCCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID Return code
Unused
556 STATUS LOG
LINE CARD MESSAGES 0A
ec.
0A DLC Set Outgoing Wink
This message changes the length of the outgoing wink from the default orcurrent setting to the new value.
4A DLC Set Outgoing Wink Response
This message returns the result of setting the wink.
Offset Label Field Description
03 Wink length Length of wink in 5 msec units. Default = 180 ms
Offset Label Field Description
03 Return code Return code:0H Okay1H Illegal or conflicting parameter(s)
CP➤DLC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Wink length
DLCCP
➤00010203 04050607 08090A0B 0C0D0E0F
Task ID Return code
Unused
STATUS LOG 557
LINE CARD MESSAGES0C
0C DLC Begin MTEST
Tells the DLC to begin execution of the manufacturing test (MTEST).
4C DLC Begin MTEST Response
Acknowledges receipt of the Begin MTEST command.
00 OK.
XX Other than 00—error.
CP➤DLC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
DLCCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
558 STATUS LOG
LINE CARD MESSAGES 0D
0D DLC End MTEST
Tells the DLC to terminate the manufacturing test (MTEST).
4D DLC End MTEST Response
Acknowledges receipt of the End MTEST command.
00 OK.
XX Other than 00—error.
CP➤DLC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
DLCCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
STATUS LOG 559
LINE CARD MESSAGES10
quired.
10 Second Level SW Download Query
This message asks the DLC whether it wishes to get software downloadedfor an intelligent TIC card or for DSP cells.
50 Second Level SW Download Response
The DLC responds that it does or does not want any second level software(such as T1 TIC, DSP, or VTG code) to be downloaded.
00 Download target exists
F0 No download target
Offset Label Field Description
03 Software type Type of downloaded software:00 (Reserved)01 Converter02 LCA Module03 VTG Module
Offset Label Field Description
04 Return code Return code:00 No second level software download is re01 Download T1 TIC software.02 Download E1 TIC software.03 Download converter software.04 Download LCA module software.05 Download VTG module software.
CP➤DLC
Task ID
Unused
Software type
00010203
DLCCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Return code
560 STATUS LOG
LINE CARD MESSAGES 11
11 DLC TIC Diagnostics
Requests the DLC to report the diagnostic results of an intelligent TIC card.
51 DLC TIC Diagnostics Response
00 Intelligent TIC present.
F0 No intelligent TIC.
Offset Label Field Description
03 Software type Type of downloaded software:00 (Reserved)01 Converter02 LCA Module03 VTG Module
Offset Label Field Description
04 Diagnostic result Result codes:00H OK - no failures.XXH Diagnostics failures detected.
05 TIC type Type codes:00 ATIC 01 E&M02 T1 TIC03 CEPT (E1) TIC04 PIC_T1 TIC05 PIC_CEPT (E1) TICF0 No TIC
06-07 Bipolar errors For T1: Bipolar Violation error count
08-09 OOF errors For T1: Out Of Frame error count
CP➤DLC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Software type
DLCCP
➤
Task IDDiagnostic result
Bipolar errors Seconds errors
TIC type OOF errors Alarm word
00010203 04050607 08090A0B 0C0D0E0F
STATUS LOG 561
LINE CARD MESSAGES51
0A-0B Seconds errors For T1: Excessive Errored Seconds error count
0C Alarm word For T1: Alarm summary word
Offset Label Field Description
562 STATUS LOG
LINE CARD MESSAGES 12
12 Begin Second Level Download
This message tells the DLC to prepare to receive the first packet of thedownload software for an intelligent TIC card. It specifies the start addressfor program execution.
52 Begin Second Level Download Response
00 OK.
F0 DLC was not expecting a software download; abort.
Offset Label Field Description
03 Flag Flags:FFH - A valid starting address followsXXH - Use the default starting address
04-05 Segment # Starting address segment number
06-07 Offset # Starting address offset number
CP➤DLC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Flag Offset #
Segment #
DLCCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
STATUS LOG 563
LINE CARD MESSAGES13
13 Second Level Download DMA Setup
This message specifies the target address of where the software is to bedownloaded and the length of the download software DMA packet.
53 Second Level Download DMA Setup Response
00 OK.
01 DMA packet number sequence error.
F0 DLC was not expecting a DMA transfer; abort.
Offset Label Field Description
03 Sequence # Download packet sequence number
06-07 Length Length (in bytes) of DMA packet
08-09 Segment # Segment number of target address
CP➤DLC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Sequence # Length
Unused Segment #
DLCCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
564 STATUS LOG
LINE CARD MESSAGES 14
uence number is out of
14 Second Level Download DMA Done
This message asks the DLC if it is done downloading the last packet and isready to receive the DMA transfer of the next packet.
54 Second Level Download DMA Done Response
00 OK.
01 Retransmit requested - SBI/OPI checksum error.
F0 Not downloading.
Offset Label Field Description
04 Response code 1 Status response code 1:0H OK; ready for next packet1H Download is still in progressF0H Download has failed. Possible packet seq
order, second level card failure; abort.
CP➤DLC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Timeout value,in 25 msec units
DLCCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Response code 1
STATUS LOG 565
LINE CARD MESSAGES15
15 Second Level Download Complete
This message tells the DLC that the software download is complete.
55 Second Level Download Complete Response
00 OK.
F0 DLC was not doing a software download—error.
CP➤DLC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
DLCCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
566 STATUS LOG
LINE CARD MESSAGES 16
16 Second Level SW Download Sync
This message asks the DLC if the second level software download worked.
56 Second Level SW Download Sync Response
00 OK.
01 Checksum failed.
10 Timeout response (probably not a good thing).
F0 No target, no download.
Offset Label Field Description
04 Response code 1 Sync response code 1:00H OK; successF0H Download failed.
CP➤DLC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Timeout value,in 25 msec units
DLCCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Response code 1
STATUS LOG 567
LINE CARD MESSAGES17
17 Clear Second Level Alarms
This message initializes the error counts and alarm status in the secondlevel TIC card.
57 Clear Second Level Alarms Response
00 OK.
F0 Command not supported by this TIC card.
CP➤DLC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
DLCCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
568 STATUS LOG
LINE CARD MESSAGES 18
18 Download Data Start
This message tells the DLC to set up to receive a DMA transfer of someconfiguration data.
58 Download Data Start Response
This message tells the CP that the DMA is set up and that the DLC is readyto receive data.
Offset Label Field Description
03 Type of data Type of data to be downloaded:0H R2 configuration data
04 Bytes Number of bytes to be DMAed
Offset Label Field Description
03 Response code Possible values:00 OK01 Number of DMA bytes is incorrectF0 Command failed
CP➤DLC
Task ID Type of data
Bytes
00010203 04050607 08090A0B 0C0D0E0FUnused
DLCCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Response Code
STATUS LOG 569
LINE CARD MESSAGES19
19 Download Data Done Query
The CP uses this message to ask the DLC for the status of the datadownload operation.
59 Download Data Done Response
The DLC returns the status of the download.
Offset Label Field Description
03 Response code Possible values:00 Download completeF0 Download was unsuccessful
CP➤DLC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
DLCCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Response code
570 STATUS LOG
LINE CARD MESSAGES 1A
1A Set Number of Digits
This message tells the DLC the number of digits to expect in an incomingcall.
5A Set Number of Digits Response
The DLC responds, indicating whether the Set Digits command wasproperly received.
Offset Label Field Description
03 Digit type Type of collected digits:01 called party digits02 calling party digits
Offset Label Field Description
03 Response code Possible values:00 OK01 Digits type error
This type not supported on this DLC;unrecognized type.
F0 Error
CP➤DLC
Task ID
Unused
Digit type
Number of digits
00010203 04
DLCCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Response Code
STATUS LOG 571
LINE CARD MESSAGES20
20 Auto Answer Command
Tells the VTIC port to be in auto answer on or auto answer off mode.
60 Auto Answer Command Response
00 OK
F0 Failed
Offset Label Field Description
03 On/off flag 00 Auto answer OFF01 Auto answser ON
04 Type of agent pilot.
00 Linear hunt.01 ACD position.02 ACD agent.
05-0C Agent ID Each byte initialized to 0xFF
Offset Label Field Description
04 Subcode VTIC subcodes:00 Link up01 MSB02 Link down03 Link not ready
CP➤DLC➤VTIC
Task ID On/off flag Agent ID
Unused
Type of agent pilot
00010203 04050607 08090A0B 0C
DLCCP
➤ ➤
VTIC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Subcode
572 STATUS LOG
LINE CARD MESSAGES 21
21 Go Off Hook
Tells the VTIC to go off hook on this channel for answering incoming call.
61 Go Off Hook Response
00 OK.
F0 Line error; no line.
Offset Label Field Description
04 Subcode VTIC subcodes:00 Link up01 MSB02 Link down03 Link not ready
CP➤DLC➤VTIC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
DLCCP
➤ ➤
VTIC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Subcode
STATUS LOG 573
LINE CARD MESSAGES22
22 Return Called Party ID
Requests VTIC to return Called Party ID.
62 Return Called Party ID Response
00 OK
F0 Bad
CP➤DLC➤VTIC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
DLCCP
➤ ➤
VTIC
Task ID
Called Party ID
Unused00010203 04050607 08090A0B 0C
574 STATUS LOG
LINE CARD MESSAGES 23
23 TIC Event Poll Command
CP polls for VTIC asynchronous event.
Offset Label Field Description
03 Action 00 Disconnect event poll01 Link up event pollFF All events poll
CP➤DLC➤VTIC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Action
STATUS LOG 575
LINE CARD MESSAGES63
63 TIC Event Poll Command Response
00 Disconnect event
01 Line status event
02 Error report event
03 Raw display of information
04 Frame sync path selection
FF No event
Offset Label Field Description
04 Type Line status event:00 Link idle (line up)01 Link (line) make set busy (N.T. only)02 Link disable (line down)03 Link (line) not ready (N.T. only)
Error report event:00 Converter01 VTG02 Mitic03 DLC
Raw display of information:00 Start or display01 Middle of display03 End of display
Frame sync:00 OKF0 Fail
05 Level of error For error report only:00 Level 001 Level 102 Level 203 Level 3
DLCCP
➤ ➤
VTIC
00010203 04050607 08090A0B 0C
Task ID
Unused
Type
Level of error
Error report or
(error report only)
line status event data
576 STATUS LOG
LINE CARD MESSAGES 24
24 Reconnect Call Command
Asks the VTIC to reconnect the call that was on hold during a transfer.
64 Reconnect Call Response
00 OK
F0 Failed
Offset Label Field Description
04 Subcode 00 Link up01 MSB02 Link down03 Link not ready
CP➤DLC➤VTIC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
DLCCP
➤ ➤
VTIC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Subcode
STATUS LOG 577
LINE CARD MESSAGES25
fied.
25 Message Waiting Command
Tells the VTIC to set message waiting on an extension.
65 Message Waiting Response
00 OK
01 MWI denied/blocked; CP wil not retry.
10 MWI invalid extension number; CP will not retry.
F0 MWI failed; CP will retry.
Offset Label Field Description
03 Type 00 Clear MWI01 Set MWI
04 Extension number
Each byte initialized to 0xFF; number is left-justi
Offset Label Field Description
04 Subcode 00 Link up01 MSB02 Link down03 Link not ready
CP➤DLC➤VTIC
Task ID
Extension number, 0xFF filler, left-justified
00010203 04050607 08090A0B 0C0D0E0FUnused
DLCCP
➤ ➤
VTIC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Subcode
578 STATUS LOG
LINE CARD MESSAGES 26
26 Dial Digit Command
Tells the VTIC to dial digit on this channel.
66 Dial Digit Command Response
00 OK
F0 Failed
Offset Label Field Description
04 Subcode 00 Link up01 MSB02 Link down03 Link not ready
CP➤DLC➤VTIC
Task ID
Unused00010203 04050607 08090A0B 0C
Digits (in BCD)
DLCCP
➤ ➤
VTIC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Subcode
STATUS LOG 579
LINE CARD MESSAGES27
om
27 Datacom & Error Command
Requests the VTIC to start datacom on this channel/card.
Offset Label Field Description
03 Subcommand 00 Start datacom01 Return datacom02 End datacom03 Enable error logging04 Disable error logging05 Write memory06 Read memory07 Frame sync
04 More info on datacom/frame sync
If return datacom:00 Transmitted datacom01 Received datacom02 Both transmitted and received datac
If frame sync:00 Disable primary and secondary sync01 Enable primary sync02 Enable secondary sync03 Enable primary and secondary sync
05 Datacom type 00 Host I/F datacom01 VTG trace datacom
CP➤DLC➤VTIC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Subcommand Datacom type
More info onDatacom/FrameSync
TDC port number
580 STATUS LOG
LINE CARD MESSAGES 67
ceive:
67 Datacom & Error Response
00 Start datacom
01 Return datacom
02 End datacom
03 Enable error logging
04 Disable error logging
05 Write memory
06 Read memory
Offset Label Field Description
04 Datacom/error logging info
If datacom, upper nibble is flag for xmit or re00 Transmit01 ReceiveLower nibble is data field length:00 No datann Number of bytes in data field
If error logging enable/disable:00 OKF0 Invalid
DLCCP
➤ ➤
VTIC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
More info ondatacom or error loggingenable/disable
Port number(Return datacom only)
Data (if any); padded with bytes of 7F
STATUS LOG 581
LINE CARD MESSAGES28
28 Set Pilot Number
68 Set Pilot Number Response
00 OK.
F0 Failed.
CP➤DLC➤VTIC
Task ID
Pilot number
Unused
Length of pilot number
00010203 04050607 08090A0B 0C
DLCCP
➤ ➤
VTIC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
582 STATUS LOG
LINE CARD MESSAGES 80
ect messages) in the
t queue.
80 Purge Event Queue
This command does a normal purge or a complete purge on the DLC.
90 Purge Event Queue Response
Offset Label Field Description
03 Purge flag Possible values:00 Normal purge. Purge messages (except disconn
event queue to the CP.01 Complete purge. Purge all messages in the even
CP➤DLC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Purge flag
LCCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
STATUS LOG 583
LINE CARD MESSAGES81
81 Get Input Event
91 Get Input Event Response
Returns the first message in the event queue if the queue is not empty.
Offset Label Field Description
03-04 Timeout interval Time to wait for an event (key or disconnect), in 25 msec units.
Offset Label Field Description
03 Event code Event code:00-09 Keys 0-90A ✻
0B #0C-0F Keys A-D10 Disconnect11 Timeout12 R1 MF KP13 R1 MF ST14 Fax calling tone CNG (fax cards only)
04 Flag Bit 0:0 Not double key1 Double key
05-06 High tone High tone energy level during DTMF detect (not valid on fax cards).
07-08 Low tone Low tone energy level during DTMF detect (not valid on fax cards).
CP➤LC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Timeout interval
LCCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Flag
Event code High tone
Low tone
584 STATUS LOG
LINE CARD MESSAGES 82
82 Transmit Speech
This message indicates the beginning of the transmission of systemprompts, pre-recorded subscriber personal greetings, or recorded voicemessages to the DLC.
Normal speech and system special phrases use the same playbackmessage sequence. The flags in the messages tell the DLC how to treatthis speech buffer.
CP➤LC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Key actions
Volume & speed Tone & playback (only)
STATUS LOG 585
LINE CARD MESSAGES82
ingly louder play.
andled during the
P. P.
P. P. s key to CP.
tone every second. every second).
10
d
A0B 0CB C D
yback
Offset Label Field Description
03 Volume & speed
The speech traits are set with two fields..
Volume. Zero is normal. Other values call for increasSpeed. Read as a signed number.
0 Normal>0 Faster<0 Slower
04-0B Key actions The value of a nibble indicates how the key is to be htransmit operation:
0 Ignore the key (do not pass to CP). 1 Cut off transmit, pass key to CP. 2 Raise volume of speech, do not pass key to C3 Lower volume of speech, do not pass key to C
4 Raise speed of speech, do not pass key to C5 Lower speed of speech, do not pass key to C6 Reset speed of speech to normal, do not pas
0C Tone & playback
This byte has two 4-bit fields:
Speech playback:0 Play normal speech.Bit 0: Play special phrase.The following is valid only if Bit 0 is set:Bit 1: Play tone only. Repeat every second.Bit 2: Play tone after playing phrase once. Repeat Bit 3: Play tone only. Repeat every two second (0 =
0203 04
0000 0017Bit count 2
Volume Spee
3
03 04050607 080900 1 2 3 4 5 6 7 8 9 ✻ # A
0B 0C0DTone to play Speech pla
586 STATUS LOG
LINE CARD MESSAGES 92
92 Read Speech Buffer
This message tells the CP (and FS) to send the next speech buffer.
Note: If the DLC is asked to start at a fax page beyond the end of the current fax image buffer, it will skip the current buffer and request the next image buffer. It will subtract the skipped pages from its internal start page, and continue skipping through buffers until it finds the requested start page number. When a buffer is skipped, the reason code (above) is set to 2, and offset 05 contains the number of page breaks that were skipped. If the DLC encounters the end of the fax data before finding the desired page, it terminates fax playback with the “page limit exceeded” code. Using the DLC-DMA to search through the fax image data for the desired start page is not recommended for system performance reasons.
Offset Label Field Description
03 Read flags Bit 0:00 Read next buffer.01 Reread last buffer.
Bit 1 (fax):01 Resend last command. Reason
code will be set to slow fax data.
04 Reason code Reason for reread. This field is significant only if offset 03 is set.
00 Checksum errorFax:
01 Slow fax data02 Skipping fax buffer for fax start page
positioning
05 Page breaks If Reason Code is 2, this field contains the number of page breaks in the skipped buffer.
DLCCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Read flags
Reason code
Page breaks
STATUS LOG 587
LINE CARD MESSAGES83
g, in
83 Read Speech Buffer Set
This message tells the DLC to set up the DMA channel for data transfer forthe next speech buffer.
93 Read Speech Buffer Set Response
This message indicates that the DLC has set up its DMA channel for datatransfer and is ready for the next speech buffer.
The information supplied in this message is provided for debug purposesonly. It is not intended that this information be used by the CP, but simplythat it be visible in the SMT error log.
Offset Label Field Description
03 Flags Flags:Bit 0: the very last bufferBit 1: cancel transfer, abort playback
08-0A Beginningoffset
Position in buffer to begin transmission or recordinbytes of speech.
CP➤LC
00010203 04050607 08090A0B 0C0D0E0F
Task ID Flags
Length of speech,in bytes
Beginning offset
Scramble code
DLCCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID Voice record type
Disconnect flag
Unused
Fax code
LT stateFax sessions
Msg count
588 STATUS LOG
LINE CARD MESSAGES 93
ok
ata)
ions that n starts egin
t
Offset Label Field Description
04 Voice record type Voice record type (lt_vr_type):0 SBC1 EDLC SBC2 CVSD4 Fax
05 Disconnect flag Line task disconnect flag (lt_2disc):0 Line task state is off hook1 Line task is on hook or about to go on ho
06 LT state LIne task state (lt_state):0 Idle1 Active2 Tone generation3 MF detection4 Begin playback (voice or fax)5 Playback (voice or fax)6 Finish playback (voice or fax)7 Begin record (voice or fax)8 Initialize record (voice only)9 Record (voice or fax)10 Finish record (voice or fax)11 Special phrase12 Play special phrase13 Finish special phrase14 Call progression (C5 command active)15 Call progression + special phrase16 Call progression + finish special phrase17 Tone finish
07 Fax code Fax return code:0 Fax completed, OK1 Fax completed with DCN2 Fax aborted by operator3 Partial fax4 No response from fax machine5 Too many transmission errors6 Page limit (attempt to read past end of d
Defaults to 3 if no fax in current call.
08 Fax sessions Bit mask (lt_fax_session) showing last DSP sessincluded fax operations. Note that a DSP sessiowith a DLC offhook or channel reset (DSP get BActive command).
09-0A Msg count 16 bit count of 84 messages from CP for currenmessage.
STATUS LOG 589
LINE CARD MESSAGES84
ion is distance prior to nsmission ended. That the data bus but was
greater than the size
84 Read Speech Buffer Done
This message indicates the end of the current system prompts, subscriberpersonal greeting or voice messages buffer.
94 Transmit Speech End Response
Response format for Voice:
00 OK.
01 Speech was cut off by a key.
02 Speech was cut off by disconnect.
04 Speech was terminated by cancel flag in control bus message 83, LC Read Speech Buffer Response.
08 Last block bad.
Offset Label Field Description
04-07 Unplayed amount Position of termination, in bytes of speech. Positend of last buffer transmitted at which speech trais, it is the amount of speech that was sent over not played—0 = complete playout.NOTE: Due to double buffering, the value can beof the last buffer transferred.
CP➤LC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
LCCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Unplayedamount
Volume& speed
590 STATUS LOG
LINE CARD MESSAGES 94
or increasingly louder
ta)
page number at which the first page, this field a cover sheet, the unt (that is, the cover l page that is
s occurred. This is set d.
ontains the CP source
10
eed
Response format for Fax:
08 Volume & speed The speech traits are set with two fields:
Volume. Zero means normal. Other values call fplay.Speed. Read as a signed number.
0 Normal>0 Faster<0 Slower
Offset Label Field Description
03 Return code Fax return code:0 Fax completed, OK1 Fax completed with DCN2 Fax aborted by operator3 Partial fax4 No response from fax machine5 Too many transmission errors6 Page limit (attempt to read past end of da
04-05 Fax page number If return code = 3 or 5, this field contains the fax the failure occurred. If the failure occurred duringwill contain 1. Note that if the document includescover sheet will be included in the failure page copage is considered to be page 1, the first physicatransmitted).
06 Self detect flag Set to 1 to indicate aspen-to-aspen self detect haeven when aspen-to-aspen self detect is inhibite
07 Remote task ID If aspen-to-aspen detect has occurred, this field c(task) ID of the remote port.
Offset Label Field Description
0203 04
0000 0017Bit count 2
Volume Sp
3
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Fax pagenumber
Return code
Remote
Self detect flag
task ID
STATUS LOG 591
LINE CARD MESSAGES85
o XOR operation).
ce of this length is
file system, in s before this much ech must be
: no buffer initial-
ult: play tone).
detectetect
e
85 Receive Speech
This message indicates the beginning of the transmission of recorded voicemessages from the DLC. Recording terminates upon detection of an inputevent (key or disconnect), of silence of the duration specified in this mes-sage or upon reaching the specified recording time limit.
If the “initialize buffer before recording” flag is set, line card message 92,Read Speech Buffer, follows to initialize the buffer. Recording then beginsat the position in the buffer indicated in line card message 83, Read SpeechBuffer Response. In this case, at least one buffer must be written to the filesystem, even if the buffer is empty and silence occurs.
Offset Label Field Description
03-04 Scramble code Scramble code to be stored in the private area (n
05-06 Silence cutoff interval
Voice: Silence cutoff interval in 25 ms units. Silento terminate recording.Fax: Maximum page count
07-0A Minimum lengthof speech
Minimum length of recorded speech to transfer tobytes of speech. If termination of recording occurspeech has been sent to the file system, the spepadded with silence to this length.
0B Options Flags:Bit 0: Initialize buffer before recording. (Default
ization).Bit 1: Do not play tone before recording. (DefaBit 2: Record faxBit 3: Reserved (used by analog linecard)Bit 4: Self detect flag
0 = DLC perform fax aspen-to-aspen self1 = Inhibit DLC fax aspen-to-aspen self d
0C Compression type
Compression type:0 16 kbps sub-band coder1 25 kbps CVSD
CP➤LC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Compression typScramblecode
Silence cutoffinterval
Minimum lengthof speech
Options
592 STATUS LOG
LINE CARD MESSAGES 95
95 Write Speech Buffer Response
This message tells the CP (and file system) that the next recorded voicemessage is ready and the size of the message.
Offset Label Field Description
03-06 Length Length of speech buffer in bytes of speechFax: length = 0 means resend last command
LCCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Length
STATUS LOG 593
LINE CARD MESSAGES86
t
86 Write Speech Buffer Set
This message indicates that the CP (and the file system) is ready to receivethe next recorded voice message buffer. It also tells the DLC to set up theDMA channel for the data transfer.
96 Write Speech Buffer Set Response
This message indicates that the DLC has set up its DMA channel for thedata transfer and is ready to transmit the next speech buffer.
Offset Label Field Description
03 Options Value is a sum of:Bit 0: Terminate record after completing the curren
buffer transfer.Bit 1: Sound warning tone.
CP➤LC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Options
LCCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
594 STATUS LOG
LINE CARD MESSAGES 87
87 Write Speech Buffer Done
This message indicates the end of the current voice message buffer.
Offset Label Field Description
03 Return code Return code from write operation. Values to be determined, depending on error handling in FS.
CP➤LC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Return code
STATUS LOG 595
LINE CARD MESSAGES97
occurred. This is set
ntains the CP source
97 Receive Speech End Response
This message indicates the end of the transmission of recorded voicemessages to the CP (actually, to the file system). It closes the “open”message record/receive loop.
Offset Label Field Description
03 Return code For receive speech operation:0 Completed normally (by key or disconnect)1 Silence cut-off detected
For a fax operation:0 Fax completed, OK1 Fax completed with DCN2 Fax aborted by operator (not used)3 Partial fax4 No response from fax machine5 Too many tranmission errors6 Page limit reached
04 Resolution Resolution:0 standard (3.85 line/mm)1 fine (7.7 line/mm)
05 Self detect flag Set to 1 to indicate aspen-to-aspen self detect haseven when aspen-to-aspen self detect is inhibited.
06 Remote task ID If aspen-to-aspen detect has occurred, this field co(task) ID of the remote port.
LCCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Return code Self detect flag
Remote task IDResolution
596 STATUS LOG
LINE CARD MESSAGES 88
ok
88 Reset Channel
This message tells the DLC to reset this channel.
98 Reset Channel Response
The information supplied by this response is provided for debug purposesonly. It is not intended that this information be used by the CP, but simplythat it be visible in the SMT error log.
Offset Label Field Description
04 Voice record type Voice record type (lt_vr_type):0 SBC1 EDLC SBC2 CVSD4 Fax
05 Disconnect flag Line task disconnect flag (lt_2disc):0 Line task state is off hook1 Line task is on hook or about to go on ho
CP➤DLC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
DLCCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID Voice record type
Disconnect flag
Unused
DSP state
Error count
Card typeLT stateLT flag
System clock
STATUS LOG 597
LINE CARD MESSAGES98
state):
p prior to dma)
lt _tmout_err).
k (system_clock).
06 LT state LIne task state (lt_state):0 Idle1 Active2 Tone generation3 MF detection4 Begin playback (voice or fax)5 Playback (voice or fax)6 Finish playback (voice or fax)7 Begin record (voice or fax)8 Initialize record (voice only)9 Record (voice or fax)10 Finish record (voice or fax)11 Special phrase12 Play special phrase13 Finish special phrase14 Call progression (C5 command active)15 Call progression + special phrase16 Call progression + finish special phrase17 Tone finish
07 DSP state The state the line task thinks the DSP is in (dsp_0 Idle1 Active2 Playback3 Record4 MF detection5 Digital loopback6 Boot loader
Fax only:7 Fax active8 Fax playback9 Fax record10 Modem test state254 Abort (DSP halted)
08 LT flag Line task DMA flag (lt_dmafl):0 DMA_NONE (idle)1 DMA_EXCBM (exchange cb msgs with c2 DMA_SETUP3 DMA_TX
09 Error count Line task internal timer mechanism error count (
0A Card type Type of DLC:1 DLC2 UDLC (DLC1231s)3 DLC431A (Aspen fax DLC)4 EDLC
0B-0C System clock Lower 16 bits of DLC internal 32 bit system clocUnits are 25 ms; time runs from DLC initial boot.
Offset Label Field Description
598 STATUS LOG
LINE CARD MESSAGES 89
89 Dial
This message dials the specified DTMF or MF tone on this channel. Thedial MF digit mode is initiated by a dial KP digit command, and is terminatedby a dial ST digit command.
99 Dial Response
Offset Label Field Description
05-0C Digits to dial Each digit is coded as a one-byte value:00-09 are 0-9 respectively.0A ✻
0B #0C A
0D B0E C0F D11 MF KP digit12 MF ST digitFF is the padding character
Offset Label Field Description
03 Return code Return code0 Okay1 Disconnect detected
CP➤LC
00010203 04050607 08090A0B 0C0D0E0F
Task ID Digits to dialTone duration,in 8 ms units
Time between tones,in 8 ms units
LCCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Return code
STATUS LOG 599
LINE CARD MESSAGES8A
.5 millisecond units.
me of transition.
8A Get Signal Transition
9A Get Signal Transition Response
00 Transition detected.
01 No transition (time-out).
Offset Label Field Description
03-04 Time-out interval
Maximum time to wait for signal transition, in 12
Offset Label Field Description
04-05 1/2-millisecond timer
Value of line card’s 1/2-millisecond timer at ti
CP➤LC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Time-out interval,in 12.5 ms units
LCCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
1/2-millisecond timer
600 STATUS LOG
LINE CARD MESSAGES 8B
n transition.
sition.
ff transition.
sition.
imer.
8B Signal Detect Begin
9B Signal Detect Begin Response
Offset Label Field Description
06 Search off-on
Number of samples to take when looking for off-to-o
07 Set off-on Number of on samples required to set off-to-on tran
08 Search on-off
Number of samples to take when looking for on-to-o
09 Set on-off Number of off samples required to set on-to-off tran
Offset Label Field Description
03 Return code Reserved for return code.
04 Signal flag Current state of detected signal:00 Off01 On
05-06 1/2-millisecond timer
Current value of line card’s 1/2 millisecond t
CP➤LCCP➤LC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Filterfrequency divisor
Filter chipcontrol
Set off-onSearchoff-on
Searchon-off
Seton-off
LCCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Return code
Signal flag
1/2-millisecond timer
STATUS LOG 601
LINE CARD MESSAGES8C
8C Signal Detect End
9C Signal Detect End Response
CP➤LC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
LCCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
602 STATUS LOG
LINE CARD MESSAGES 8D
8D Set Dial Tone
9D Set Dial Tone Response
Offset Label Field Description
03 Number of samples
Number of samples to take.
04 Number of hits Number of positive hits for tone presence.
CP➤LC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Number ofsamples
Number ofhits
Filtersetting
Filterfrequency devisor
LCCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
STATUS LOG 603
LINE CARD MESSAGES8E
8E Enable Autovon Keys
This message tells the DLC to enable or disable the autovon tone detect.
9E Enable Autovon Keys Response
Offset Label Field Description
03 Disable/enable Flag:00 Disable autovon key detection.01 Enable autovon key detection.
04 Fax flag Fax only:0 Disable fax calling tone CNG detect1 Enable fax calling tone CNG detect
CP➤DLC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Disable/enable Fax flag
LCCP➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
604 STATUS LOG
LINE CARD MESSAGES 8F
8F Stop Special Phrase
This message tells the DLC to stop playing the special phrase.
9F Stop Special Phrase Response
This message indicates that the special phrase playback is stopped.
CP➤LC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
LCCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
STATUS LOG 605
LINE CARD MESSAGESA0
A0 TIC Detect
DLC TIC Detect is sent by the CP to detect the existence of a TIC, and toget the type and result of a sanity check, if possible, of the TIC.
B0 TIC Detect Response
Reports the DLC TIC check/detect result.
00 TIC present.
F0 No TIC present.
Offset Label Field Description
04 TIC status
Error status of TIC, if present:00 TIC diagnostics OK.0X other than 00: intelligent TIC errors.
05 TIC type TIC board type:00 ATIC01 E&M02 T1 TIC03 CEPT (E1) TIC04 PIC_T1 TIC05 PIC_CEPT (E1) TIC06 VTICF0 No TIC
CP➤LC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
LCCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
TIC status
TIC type
606 STATUS LOG
LINE CARD MESSAGES A1
A1 DLC Set ID Request
The CP uses this message to check the existence and sanity of a DLC.
A1 DLC Set ID Response
This message announces the DLC’s presence and reports the result of thesanity check of the DLC.
Offset Label Field Description
03 Error status Error status:00 Bootup diagnostics OK.0X 386SX diagnostics errors1X DSP diagnostics errors2X PCM ASIC errors (DLC only)3X Other peripherals’ errors.
04 Must be zero
05 Card type Card type (used by fax):4 DLC431A5 DLC1231S
This field is valid only if message return code is A1.
CP➤LC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
LCCP
➤
Error status
00010203 04050607 08090A0B 0C0D0E0FUnused
Task ID
Card type
STATUS LOG 607
LINE CARD MESSAGESA2
A2 General Read Memory
Reads four bytes of memory for diagnostics/debugging.
E2 General Read Memory Response
CP➤LC
00010203 04050607 08090A0B 0C0D0E0F
Task ID Source address on peripheral board
Unused
LCCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Data from specified address on DLC
608 STATUS LOG
LINE CARD MESSAGES A3
A3 General Write Memory
Writes four bytes of memory for diagnostics/debugging.
E3 General Write Memory Response
CP➤LC
00010203 04050607 08090A0B 0C0D0E0F
Task ID Destination address on peripheral board
Data to write
LCCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
STATUS LOG 609
LINE CARD MESSAGESA4
A4 Return Code Level
This message tells the DLC or VTIC to return its code level. The DLC codelevel should be able to identify both the code versions of 386SX and DSPchips.
This message is also used with the file system and the EPU.
B4 Return Code Level Response
This message is also used with the file system and the EPU.
00 OK.
01 Invalid type for this card.
Offset Label Field Description
03 Code type Type indicating the desired component:01 DLC x86 (CPU A) run-time code02 DLC DSP (CPU B) code
VTIC code levels:10 T1 EPROM11 T1 software17 Converter EPROM18 Converter software19 VTG EPROM1A VTG software
CP➤LC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Codetype
LCCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Code level (software or firmware revision levels)
610 STATUS LOG
LINE CARD MESSAGES A9
d by the
ng fax
eceiving
.
se
A9 Read Fax Buffer Set
This message sets up the DMA channel for a fax data buffer transfer.
Message format when flag bit 2 is reset (fax message structure):
Offset Label Field Description
03 Flags Bit 0:0 More buffers to follow1 Last buffer
Bit 1:0 No action1 Cancel
Bit 2 (the remainder of message structure is determinestate of this flag bit):
0 Respond with 0x93H (no cover sheet)1 Respond with 0xCAH (cover sheet follows)
Bit 3:0 At end of fax, send DCN (disconnect) to receivi
machine (this is last document).1 At end of fax, send EOM (end of message) to r
fax machine (more documents are coming).Bit 4:
0 DLC performs Aspen-to-Aspen self detect1 Inhibits DLC Aspen-to-Aspen self detect
Offset Label Field Description
04 Page count Total page count (DLC does not use this data)
05 Start value Start page count (0 = default. DLC does not uthis data.)
CP➤LC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Flags
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Flags Number of pages
Start value
Page count Scramble code
Start page
STATUS LOG 611
LINE CARD MESSAGESA9
field
ll). r of a
e
Message format when flag bit 2 is set (cover sheet structure):
Read Fax Buffer Set response varies depending upon type of processing:
• 93H is returned if processing fax image data.
• CAH is returned if processing cover sheet.
06 Start page Start at page (1-based; 0 is treated as 1). Thisis only valid for the first (image) buffer of a faxdocument.
07 Number of pages
Number of pages to transmit (255 = transmit aThis field is only valid for the first (image) buffefax document.
Offset Label Field Description
04 Page number location
Page number location in top line (0 = no pagnumber required).
05-06 Transfer length DMA transfer length (max = 10K)
Offset Label Field Description
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Flags
Page number location
Transfer length
612 STATUS LOG
LINE CARD MESSAGES AA
age et), this ion:
e image.
AA Read Cover Sheet Done
This message, which is the CP reply to a CA response code, indicates thecompletion of the cover sheet DMA.
CA Read Cover Sheet Done Response
The DLC acknowledges receipt of the A9 command with bit 2 set. Ready toDMA cover sheet.
Offset Label Field Description
04 Resolution If only a cover sheet is being transmitted with no imfollowing (prior A9 command had last buffer flag sfield controls the cover sheet transmission resolut
0 standard (3.85 line/mm) resolution1 fine (7.7 line/mm) resolution
If image follows, the resolution is determined by th
CP➤LC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Resolution
LCCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
STATUS LOG 613
LINE CARD MESSAGESAB
I/CSI). paces).
.
ID.
acters of
formally
CII set.
AB Get Fax ID
The CP uses this message to read or set five characters of the fax ID.
Offset Label Field Description
03 Control Control values:0 Set first 5 characters of outgoing fax ID (TS
This clears the other 15 characters (set to s1 Set second 5 characters of outgoing fax ID2 Set third 5 characters of outgoing fax ID.3 Set last 5 characters of outgoing fax ID.
4 Read first 5 characters of incoming fax ID.5 Read second 5 characters of incoming fax 6 Read third 5 characters of incoming fax ID.7 Read last 5 characters of incoming fax ID.
04-08 Outgoing ID If control is 0, 1, 2, or 3, this field contains five charthe outgoing ID.Note: Data is actually ASCII format, but the CCITT allows only the following codes:
25H ASCII ‘+’20H ASCII ‘ ‘ (space)30H-39H ASCII ‘0’ through ‘9’
In practice, some fax machines support the full AS
CP➤LC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Outgoing IDControl
614 STATUS LOG
LINE CARD MESSAGES CB
racters of
formally
SCII set.
CB Get Fax ID Response
A DLC offhook clears both the incoming and outgoing fax IDs. Once set, theoutgoing fax ID will remain in use until either an offhook occurs or the fax IDis explicitly changed by the CP.
Offset Label Field Description
03 Response Response code:0 OK.1 No ID received yet during this call.
04-08 Incoming ID If control is 4, 5, 6, or 7, this field contains five chathe incoming ID.Note: Data is actually ASCII format, but the CCITTallows only the following codes:
25H ASCII ‘+’20H ASCII ‘ ‘ (space)30H-39H ASCII ‘0’ through ‘9’
In practice, some fax machines support the full A
LCCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Response Incoming ID
STATUS LOG 615
LINE CARD MESSAGESC4
zero
C4 DLC Set Dial Tone
Tells the DLC to start to detect the disconnect tone using the passed callprogress setup table index.
D4 DLC Set Dial Tone Response
Indicates the DLC will detect disconnect tone and the event will be put in theevent queue.
Offset Label Field Description
03-04 Table index Index to the Call Progress Setup Table. (Setup =disables cadence checker.)
05-06 Country code Country code (effective with DLC Release 1xx):00 North America (default)01 Australia02 New Zealand03 United Kingdom04 France05 Germany
07-0B Serial number BCD serial number—fax transmissions
CP➤DLC
00010203 04050607 08090A0B 0C0D0E0F
Task ID Table index
Country code
Serial number
DLCCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
616 STATUS LOG
LINE CARD MESSAGES C5
C5 DLC Monitor Call
Tells the DLC to either monitor the call progression for this channel ordetect the presence of dial tone or special tone on this channel.
D5 DLC Monitor Call Response
Returns the result of call monitoring or tone detection on this channel.
00 Voice detected, call answered.
01 Busy tone detected.
02 No answer, time-out.
03 Re-order tone detected.
04 DTMF key detected.
05 Dial tone detected.
06 Disconnect detected.
07 Ring back detected.
08 Pager initialize low detected.
09 Pager low confirmation detected.
0A Pager initialize high detected.
0B Pager high confirmation detected.
CP➤DLC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Signal detect time-out,in 25 ms units
Index tocall-progress setup table
DLCCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
STATUS LOG 617
LINE CARD MESSAGESFD
tes
FD DSP Second Level Download
NOTE: The DLC responses also use status code FD. The responsedescriptions follow the CP commands.
00 Tells the DLC to prepare to receive the first packet of the download software for the DSP.
01 CP tells the DLC that the download of the DSP is complete.
02 CP asks the DLC if it is done downloading the last packet and is ready to receive the DMA transfer of the next packet.
04 DMA setup command specifies the length of the download software DMA packets and the target addresses of where the software is to be downloaded.
Offset Label Field Description
04 Validity flag The addresses in the following four bytes are valid if this field = FFH
CP➤DLC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Validity flag High memory offset addressLow memory offset address
High memory segment start addressLow memory segment start address
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Unused High memory segment address
Low memory segment address
Length of high memory segment in byLength of low memory segment in bytes
618 STATUS LOG
LINE CARD MESSAGES FD
FD DSP Second Level Download Response
00 Acknowledges receipt of the begin DSP download message.
01 DLC acknowledges receipt of DSP download complete message.
02 DLC responds with the status of the download of the last packet of software.
04 DLC DMA setup is complete.
Offset Label Field Description
03 Response code All FD response codes are zero. If an error occurs, the DLC does not send the response message, which causes a CB timeout.
DLCCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Task ID
Unused
Response code
00010203 04
STATUS LOG 619
LINE CARD MESSAGESFE
FE DLC or DSP Ready
After the 386 DLC or DSP code has been downloaded, the CP askswhether the downloaded processor has successfully started operation.
This message is also used with the file system.
Offset Label Field Description
03 Processor Processor type:0 DLC Processor1 DSP Processor
➤DLCCP
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Processor
620 STATUS LOG
LINE CARD MESSAGES FE
FE DLC or DSP Ready Response
The DLC acknowledges that it is up and running and has completed itssearch for TIC cards; the DSP simply acknowledges that it is up andrunning.
This message is also used with the file system.
Offset Label Field Description
03 Status Processor status:00 Ready01 Not ready
DLCCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Status
STATUS LOG 621
CHAPTER 5: ACP MESSAGES
This chapter provides descriptions of all control bus messages used with ACP cards. For informationon reading these descriptions, see “Control Bus Messages” on page 35. All values in the illustrationsare the bytes’ offsets, not sample data.
Request and response messages are grouped together and organized by the message type of therequest. These can be found by checking the numbers in the upper-outer corners of the pages whileflipping through the chapter. Or, message descriptions can be found by checking the index on the nextpage.
ACP Message Format
The ACP control bus messages are a little different from other types. The Asynchronous Communica-tions Processor (ACP) communicates with other cards with CIP messages. To communicate with theCP, these messages are converted into control bus form by adding the three bytes of the control busmessage header. The resulting format is shown below:
Offset 03 is actually two 4-bit fields. Each hex digit represents one of the ID numbers.
The CIP message’s task ID, in offset 04, is usually the same as the control bus message’s task ID, inoffset 00, but not always. These are normally the SMT or a background task.
Even though a stand-alone system may not actually contain an ACP card, the ACP applications codestill converts integration-related messages to the CIP format.
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Packet data
Peripheraladdress
Messagetype Link/station ID
TaskID
Flags (not usedcurrently)
03Link ID Station ID
STATUS LOG 623
Index
Numerics01 Asynchronous Port Configuration, 62602 Set LTN, 62703 Dial Digits, 62804 Transfer Call, 62905 Set Message Waiting, 63006 Clear Message Waiting, 63107 Reconnect to Call on Hold, 63208 Seize Line, 63309 Start Data Communication, 6340A End Data Communication, 6340B Return Data Communication, 6350C Go On-Hook, 6360D Go Off-Hook, 6370E Reset Channel on ACP, 6380F Alerting Response for APID, PID/R, DMID, 66010 Call Picked (PID/R), 63911 Error Logging On/Off, 63912 Poll Message to ACP, 64013 Set Message Waiting Extension on ACP, 64115 Log-in Agent ID on MID, 64216 Set LTN Internal, 64317 Return Memory from ACP, 64419 Ready to Dial Last Digit for PID/R, 6451A Pilot Number Download Response, 66280 Ring No Answer Incoming Call, 64681 Busy Incoming Call, 64682 All Calls Forwarded Incoming Call, 64783 Direct Incoming Call, 64785 Data Communication Response, 63586 Error, 64887 APID,PID/R,DMID Alerting Message, 66088 Seize Line Response, 63389 Dial Digits Response, 6288A Reconnect Response, 6328B Transfer Response, 6298C Set Message Waiting Response, 6308D Clear Message Waiting Response, 6318E On-Hook Response, 6368F Off-Hook Response, 63790 Reset Response, 63891 Asynchronous Port Configuration Response, 62692 Set LTN Response, 62793 Polling Response, 64094 Disconnect Detected, 661
624 STATUS LOG
96 Set Message Waiting Extension Response, 64197 Log-in Agent ID Response, 64298 Set LTN Internal Response, 64399 Return Memory Response, 6449B Pilot Number Download Request, 662
STATUS LOG 625
ACP MESSAGES01 000000
01 Asynchronous Port Configuration
The asynchronous port configuration command is used to configure theDUART’s on the ACP for various links.
91 Asynchronous Port Configuration Response
00 OK
XX Error
Offset Label Field Description
06-0A Setup information Data bits, stop bit, parity.
CP➤ACP
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Link/station ID
TaskID
Setup information
ACPCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Link/station ID
TaskID
626 STATUS LOG
ACP MESSAGES 02
02 Set LTN
Informs the ACP of the correlation of LTN’s (Menu 4) to ports/tasks.
92 Set LTN Response
00 OK
XX Error
Offset Label Field Description
0B Reset type 02 Link reset03 Power-up
CP➤ACP
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
UnusedLTN
Port
Reset type
ACPCP
➤00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Link/station ID
TaskID
STATUS LOG 627
ACP MESSAGES03
03 Dial Digits
The dial digits command tells the MID to dial digits for outcalling.
89 Dial Digits Response
00 OK
XX Error
CP➤ACP
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
Extension number(BCD, left justified)
ACPCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Link/station ID
TaskID
628 STATUS LOG
ACP MESSAGES 04
04 Transfer Call
Initiates a transfer on the MID.
8B Transfer Response
00 OK
XX Error
CP➤ACP
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
Extension number(BCD, left justified)
ACPCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Link/station ID
TaskID
STATUS LOG 629
ACP MESSAGES05
05 Set Message Waiting
Sent by the CP to have message waiting set on the extension specified.
8C Set Message Waiting Response
00 OK
XX Error
CP➤ACP
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
Extension number(BCD, left justified)
ACPCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Link/station ID
TaskID
630 STATUS LOG
ACP MESSAGES 06
06 Clear Message Waiting
Sent by the CP to have message waiting turned off on the extension speci-fied.
8D Clear Message Waiting Response
00 OK
XX Error
CP➤ACP
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
Extension number(BCD, left justified)
ACPCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Link/station ID
TaskID
STATUS LOG 631
ACP MESSAGES07
07 Reconnect to Call on Hold
Sent by the CP to reconnect with a failed transfer.
8A Reconnect Response
00 OK
XX Error
CP➤ACP
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
Unused
ACPCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Link/station ID
TaskID
632 STATUS LOG
ACP MESSAGES 08
08 Seize Line
The seize line command is used for outcalling. It tells the MID to go off-hook and seize the line.
88 Seize Line Response
00 OK
XX Error
CP➤ACP
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
Unused
ACPCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Link/station ID
TaskID
STATUS LOG 633
ACP MESSAGES09
09 Start Data Communication
Tells the ACP to collect data for a particular link. This data is stored in abuffer.
0A End Data Communication
Sent by the CP to end data collection.
CP➤ACP
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
Unused
CP➤ACP
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
Unused
634 STATUS LOG
ACP MESSAGES 0B
0B Return Data Communication
Used to return whatever data is in the buffer.
85 Data Communication Response
CP➤ACP
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
Data
Lengthof data
ACPCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
Data
Lengthof data
STATUS LOG 635
ACP MESSAGES0C
0C Go On-Hook
Tells the MID to go on-hook and end the call.
8E On-Hook Response
00 OK
XX Error
CP➤ACP
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
Unused
ACPCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Link/station ID
TaskID
636 STATUS LOG
ACP MESSAGES 0D
0D Go Off-Hook
The off-hook command is used to answer the call once the call is detected.
8F Off-Hook Response
00 OK
XX Error
CP➤ACP
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
Unused
ACPCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Link/station ID
TaskID
STATUS LOG 637
ACP MESSAGES0E
0E Reset Channel on ACP
Resets the channel to the idle state.
90 Reset Response
00 OK
XX Error
CP➤ACP
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
Unused
ACPCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Link/station ID
TaskID
638 STATUS LOG
ACP MESSAGES 10
10 Call Picked (PID/R)
Tells the PID/R that the CP has picked the call and the call should go off thePID/R. There is no response message.
11 Error Logging On/Off
Turns error logging on or off. When error logging is turned on, the status logentries will be logged. There is no response message.
00 OK
XX Error
CP➤ACP
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
Unused
CP➤ACP
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Link/station ID
TaskID
STATUS LOG 639
ACP MESSAGES12
12 Poll Message to ACP
Basically checks to see if the ACP is still there. This message is sentapproximately every 30 seconds.
93 Polling Response
CP➤ACP
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
Unused
ACPCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
Unused
640 STATUS LOG
ACP MESSAGES 13
13 Set Message Waiting Extension on ACP
Checks for invalid message waiting.
96 Set Message Waiting Extension Response
00 OK
XX Error
CP➤ACP
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
Extension number(BCD, left justified)
ACPCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Link/station ID
TaskID
STATUS LOG 641
ACP MESSAGES15
15 Log-in Agent ID on MID
At initialization, the log-in agent ID command gets the port logged in by get-ting the agent ID established in Menu 4.
97 Log-in Agent ID Response
00 OK
XX Error
CP➤ACP
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
Agent ID
ACPCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Link/station ID
TaskID
642 STATUS LOG
ACP MESSAGES 16
16 Set LTN Internal
Resets a link. Before, this was accomplished via the SMT—it is now accom-plished via a background task. This is an internal post, where one tasksends the message to another.
98 Set LTN Internal Response
CP➤ACP
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
Unused
ACPCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
Unused
STATUS LOG 643
ACP MESSAGES17
17 Return Memory from ACP
Returns memory off the ACP board so that the contents can be examined.
99 Return Memory Response
CP➤ACP
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
Unused
Offset
Segment
ACPCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
Data
644 STATUS LOG
ACP MESSAGES 19
19 Ready to Dial Last Digit for PID/R
Used as part of the PID/R call progression. There is no response message.
CP➤ACP
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
Unused
STATUS LOG 645
ACP MESSAGES80
80 Ring No Answer Incoming Call
This command is one of several that establishes an incoming call. It pro-vides the ID’s of both the called and calling party. There is no responsemessage.
81 Busy Incoming Call
This command is one of several that establishes an incoming call. It pro-vides the ID’s of both the called and calling party. There is no responsemessage.
ACPCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
Called party ID
Calling party ID
ACPCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
Called party ID
Calling party ID
646 STATUS LOG
ACP MESSAGES 82
82 All Calls Forwarded Incoming Call
This command is one of several that establishes an incoming call. It pro-vides the ID’s of both the called and calling party. There is no responsemessage.
83 Direct Incoming Call
This command is one of several that establishes an incoming call. There isno response message.
ACPCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
Called party ID
Calling party ID
ACPCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
Calling party ID
Unused
of direct call
STATUS LOG 647
ACP MESSAGES86
86 Error
Shows error information from the PID. Interpretation depends on the errortype, which is identified in offset 06:
01 ACP internal error
02 Blocked message waiting
03 Illegal message waiting
04 APID/75 error
05 APID/85 error
06 PID/R error
07 AMID error
08 DMID error
80 Parity error
81 Framing error
82 Overrun error
83 Incomplete message error
84 Link status from ACP
85 False LTN from ACP
86 Line status message from MID
87 XON/XOFF message waiting
The meaning of the remaining bytes depends on the error code. In general, byte 7 is the suberror code field; bytes 8 through 15 may be used for data.
General Format
Definitions of suberror codes and data fields for errors 06, 07, and 08 are described below. Also found below are descriptions of data fields for errors 84 through 87.
ACPCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
Error code
data (varying length, or unused)
Suberror code
648 STATUS LOG
ACP MESSAGES 86
PID/R Error (06)
The PID/R data field in offset 08-0F varies with the error in offset 07.
01 Time-out for port request. Offset 08-0D holds the PID/R extension number with ringing.
04 Time-out for call picked message. Offset 08-0D holds the PID/R extension number with ringing.
08 Peg counters:
Offset 08: message buffer overflow.Offset 09: no extension at ringing port.Offset 0A: not used.Offset 0B: incomplete message time-outs.
09 Pick failed. Offset 08-0D holds the LTN of the VPS doing the pick.
0A Time-out from ready to dial last digit. Offset 08-0D holds the PID/R extension number with ringing.
0B Pick exceeded maximum retries. Offset 08-0F is unused.
20 Report EPROM revision. Offset 08-0D holds the revision number (ASCII).
21 Message waiting already on. Offset 08-0D holds the message waiting extension.
22 Message waiting already off. Offset 08-0D holds the message waiting extension.
23 One of the PID/R phones is reset. Offset 08 identifies which phone:00 for phone 0; 01 for phone 1.
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
PID/R data (depends on
Integration error type = 06
suberror in offset 07)
STATUS LOG 649
ACP MESSAGES86
AMID Error (07)
The errors reported in offset 07 are the same as the subcodes of the 1E sta-tus log entry for the MID.
00 Display rev numbers of 651/751 EPROM’s.
03 751 internal RAM error—bad 751. Replace the 751.
04 751 overwrote its incoming message buffers. Service affecting, but not fatal. Notify engineering.
05 751 detected a checksum error while communicating with the 652. Not fatal, unless occurring repeatedly.
06 751 detected an interrupt on the IIC bus. Service affecting, but not fatal. If more than a few occurrences, replace MID (all 6 channels associated with the particular bus will be bad).
07 751 detected a line input overrun. Service affecting, but not fatal. Notify engineering.
08 751 detected an unrecognized command. Notify engineering.
30 652 detected an incorrect message from a 751. Service affecting, but not fatal.
31 652 detected an unmatched message from a 751. Service affecting, but not fatal.
32 652 detected a checksum error on the IIC bus from a 751. Service affecting, but not fatal.
33 652 detected no response from a 751. Service affecting, but not fatal.
40 652 internal RAM error—bad 652. Replace the 652.
41 652 external RAM error—bad 652. Replace the 652.
42 652 detected that 188 sent wrong message. Service affecting, but not fatal.
43 652 detected that 188 sent a bad checksum. Service affecting, but not fatal.
44 652 detected that 188 sent bad serial number. Service affecting, but not fatal.
45 652 detected that 188 sent unmatched message. Service affecting, but not fatal.
46 652 detected that 188 sent unmatched general message. Service affecting, but not fatal.
47 652 detected that 188 sent a message that was too long.
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
Integration error type = 07
Unused
650 STATUS LOG
ACP MESSAGES 86
49 652 detected that 188 message not processed.
50 652 detected no digits in buffer during incall. Service affecting, but not fatal.
51 652 detected too few digits in buffer during incall. Service affecting, but not fatal.
52 652 detected more than 16 digits in buffer during incall. Service affecting, but not fatal.
53 652 detected a condition where state is longer than 60 seconds. Ser-vice affecting, but not fatal.
54 652 big transmit buffer overrun error. Service affecting, but not fatal.
55 Bad or blocked extension for transfer. Service affecting, but not fatal.
56 No message waiting indication DN found. Service affecting, but not fatal.
57 No message waiting clear DN found. Service affecting, but not fatal.
58 No digit echo during message waiting indication. Service affecting, but not fatal.
59 No digit echo during message waiting clear. Service affecting, but not fatal.
5A Bad or blocked extension for message waiting indication. Service affecting, but not fatal.
5B Bad or blocked extension for message waiting clear. Service affect-ing, but not fatal.
5C Outcall failed. Service affecting, but not fatal.
5D During transfer, no digits found.
5E During transfer, no message from SL-1 for approximately 12 seconds.
5F During incall, no volume message from SL-1 for approximately 12 seconds.
60 No digit information received from PBX on incoming call. Check if ADD feature in SL1 programming is enabled for that particular TN.
61 No dial digit message from VPM.
80 Display rev numbers of 188 EPROM.
81 652 processor bad. Fatal error. Replace MID.
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
Integration error type = 07
Unused
STATUS LOG 651
ACP MESSAGES86
DMID Error (08)
The errors reported in offset 07 are the same as the subcodes of the 1E sta-tus log entry for the DMID.
The DMID data field in offset 08-0B varies with the error in offset 07.
00 DMID firmware revision number. Logged when the DMID is powered up, even if error logging is disabled. DMID data is:
Offset 08-09: firmware revision number.Offset 0A-0B: unused.
01 RS-232 serial interface error. Service affecting, fatal. Notify Product Support Engineering. DMID data is:
Offset 08: no RS-232 buffer error counter.Offset 09: bad RS-232 message length error counter.Offset 0A: RS-232 message time (100 ms) expired error counter.Offset 0B: bad RS-232 header error counter.
02 Interrupt 0 or 1 error. Service affecting, fatal. Notify Product Support Engineering. DMID data is:
Offset 08: interrupt 0 error counter.Offset 09: interrupt 1 error counter.Offset 0A: watchdog interrupt error counter.Offset 0B: unused.
03 MPDA-A serial interface error. Service affecting, fatal. Notify Product Support Engineering. DMID data is:
Offset 08: MPDA I/F parity error counter.Offset 09: MPDA I/F overflow error counter.Offset 0A: MPDA I/F bad header error counter.Offset 0B: MPDA I/F message time (100 ms) expired error counter.
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
DMID data (depends on
Integration error type = 08
suberror in offset 07)
Unused
652 STATUS LOG
ACP MESSAGES 86
04 MPDA-B serial interface error. Service affecting, fatal. Notify Product Support Engineering. DMID data is:
Offset 08: MPDA I/F parity error counter.Offset 09: MPDA I/F overflow error counter.Offset 0A: MPDA I/F bad header error counter.Offset 0B: MPDA I/F message time (100 ms) expired error counter.
05 MPDA-C serial interface error. Service affecting, fatal. Notify Product Support Engineering. DMID data is:
Offset 08: MPDA I/F parity error counter.Offset 09: MPDA I/F overflow error counter.Offset 0A: MPDA I/F bad header error counter.Offset 0B: MPDA I/F message time (100 ms) expired error counter.
06 DMID received unknown transparency message. Service affecting, fatal. Resets phone and re-establishes transparency. When the PBX initialized, it sent this message. DMID data is:
Offset 08-09: received message.Offset 0A-0B: unused.
07 DMID received unknown transparency message. Service affecting, fatal. Resets phone and re-establishes transparency. When the PBX initialized, it sent this message. DMID data is:
Offset 08-09: received message.Offset 0A-0B: unused.
15 Pilot number download time-out. DMID data is unused.
16 MPDA-A/B/C power up warning. Not service affecting. DMID data is:
Offset 08: MPDA A, B or C.Offset 09: A/B/C state.Offset 0A: A/B/C timer.Offset 0B: data.
17 MPDA-A/B/C power up warning. Not service affecting. DMID data is:
Offset 08: MPDA A, B or C.Offset 09-0B: data.
18 MPDA-A/B/C power up warning. Not service affecting. DMID data is:
Offset 08: MPDA A, B or C.Offset 09: A/B/C state.Offset 0A: A/B/C timer.Offset 0B: data.
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
DMID data (depends on
Integration error type = 08
suberror in offset 07)
Unused
STATUS LOG 653
ACP MESSAGES86
19 MPDA-A/B/C power up warning. Not service affecting. DMID data is:
Offset 08: MPDA A, B or C.Offset 09: A/B/C state.Offset 0A: A/B/C timer.Offset 0B: data.
1A MPDA-A/B/C power up warning. Not service affecting. DMID data is:
Offset 08: MPDA A, B or C.Offset 09: A/B/C state.Offset 0A: A/B/C timer.Offset 0B: data.
20 DMID received LED Wink message and did not know what to do with it. Not service affecting. Notify Product Support Engineering. DMID data is:
Offset 08: LTN number.Offset 09: LTN state.Offset 0A: LTN timer.Offset 0B: unused.
22 DMID received LED Flash message when the channel was in the wrong state. Not service affecting. PBX can send multiple lamp flash message. If too many errors are logged, notify Product Support Engi-neering. DMID data is:
Offset 08: LTN number.Offset 09: LTN state.Offset 0A: LTN timer.Offset 0B: unused.
27 DMID received a digit but the channel was in the wrong state. Not ser-vice affecting. If too many errors are logged, notify Product Support Engineering. DMID data is:
Offset 08: LTN number.Offset 09: LTN state.Offset 0A: LTN timer.Offset 0B: unused.
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
DMID data (depends on
Integration error type = 08
suberror in offset 07)
Unused
654 STATUS LOG
ACP MESSAGES 86
29 DMID received an ASCII message but the channel was in the wrong state. Not service affecting. If too many errors are logged, notify Prod-uct Support Engineering. DMID data is:
Offset 08: LTN number.Offset 09: LTN state.Offset 0A: LTN timer.Offset 0B: unused.
2C Bad LTN message from scanner. Service affecting, non-fatal. If too many errors logged, notify Product Support Engineering. DMID data is:
Offset 08: message type from scanner.Offset 09-0A: LTN number.Offset 0B: unused.
2D Got off-hook response message from scanner when the channel was in the wrong state. Service affecting. Notify Product Support Engi-neering. DMID data is:
Offset 08: LTN number.Offset 09: LTN state.Offset 0A: LTN timer.Offset 0B: unused.
2E Off-hook response from scanner expired. Service affecting, non-fatal. Caller might get open tree greeting or get dropped. DMID data is:
Offset 08: LTN number.Offset 09: LTN state.Offset 0A: LTN timer.Offset 0B: A/B counter.
30 Bad RS-232 message from scanner. Service affecting, non-fatal. If too many errors logged, notify Product Support Engineering. DMID data is:
Offset 08: message type from scanner.Offset 09-0A: LTN number.Offset 0B: unused.
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
DMID data (depends on
Integration error type = 08
suberror in offset 07)
Unused
STATUS LOG 655
ACP MESSAGES86
31 Off-hook or Call ID message pending expired. Service affecting, non-fatal. Caller gets open tree greeting. If too many errors are logged, notify Product Support Engineering. DMID data is:
Offset 08: LTN number.Offset 09: LTN state.Offset 0A: LTN timer.Offset 0B: unused.
32 Timed-out after 18 seconds in answer pending state. Service affect-ing, non-fatal. Caller gets open tree greeting. If too many errors are logged, notify Product Support Engineering. DMID data is:
Offset 08: LTN number.Offset 09: LTN state.Offset 0A: LTN timer.Offset 0B: A/B state.
35 MPDA-A/B/C response time-out for idle poll message. Service affect-ing, fatal. Transparency is re-established. Check DMID channels A, B and C connections, and check internal cables. Notify Product Support Engineering. DMID data is:
Offset 08: A, B or C.Offset 09: A/B/C state.Offset 0A: A/B/C timer.Offset 0B: unused.
36 Timed-out after five seconds in Phone Session state. Not service affecting. If too many errors are logged, notify Product Support Engi-neering. DMID data is:
Offset 08: A or B.Offset 09: A/B state.Offset 0A: A/B timer.Offset 0B: processing LTN.
37 DSP enable time expired. Not service affecting. If too many errors are logged, notify Product Support Engineering. DMID data is:
Offset 08: A or B.Offset 09: A/B state.Offset 0A: A/B timer.Offset 0B: processing LTN.
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
DMID data (depends on
Integration error type = 08
suberror in offset 07)
Unused
656 STATUS LOG
ACP MESSAGES 86
38 DSP enable time expired. Not service affecting. If too many errors are logged, notify Product Support Engineering. DMID data is:
Offset 08: A or B.Offset 09: A/B state.Offset 0A: A/B timer.Offset 0B: processing LTN.
39 Scanner sent non-digit extension for message waiting. Service affect-ing, can be fatal. Message waiting will have problems. If too many errors are logged, notify Product Support Engineering. DMID data is:
Offset 08: LTN number.Offset 09: LTN state.Offset 0A: LTN timer.Offset 0B: received digit.
3A DMID received MIK LED on message when not in this state. Not ser-vice affecting. If too many errors are logged, notify Product Support Engineering. DMID data is:
Offset 08-0B: received message.
3B DMID received MIK LED on message when not in this state. Not ser-vice affecting. If too many errors are logged, notify Product Support Engineering. DMID data is:
Offset 08-0B: received message.
3C MIK/MCK release expired. Service affecting, non-fatal. Transparency mode will be re-established. Message waiting will not work until trans-parency is re-established. If too many errors are logged, notify Prod-uct Support Engineering. DMID data is:
Offset 08: C.Offset 09: C state.Offset 0A: C timer.Offset 0B: C counter.
3D Received type 1 off-hook message from PBX. Not service affecting. May log this if the phone is being programmed in overlay 11 or if the hook switch is toggled. DMID data is:
Offset 08-09: received message.Offset 0A: A,B or C.Offset 0B: unused.
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
DMID data (depends on
Integration error type = 08
suberror in offset 07)
Unused
STATUS LOG 657
ACP MESSAGES86
3E Received type 2 off-hook message from PBX. Not service affecting. May log this if the phone is being programmed in overlay 11 or if the hook switch is toggled. DMID data is:
Offset 08-09: received message.Offset 0A: A,B or C.Offset 0B: unused.
3F Received type 3 off-hook message from PBX. Not service affecting. May log this if the phone is being programmed in overlay 11 or if the hook switch is toggled. DMID data is:
Offset 08-09: received message.Offset 0A: A,B or C.Offset 0B: unused.
40 Received type 1 on-hook message from PBX. Not service affecting. May log this if the phone is being programmed in overlay 11 or if the hook switch is toggled. DMID data is:
Offset 08-09: received message.Offset 0A: A,B or C.Offset 0B: unused.
41 Received type 2 on-hook message from PBX. Not service affecting. May log this if the phone is being programmed in overlay 11 or if the hook switch is toggled. DMID data is:
Offset 08-09: received message.Offset 0A: A,B or C.Offset 0B: unused.
42 Received unknown message from MPDA. Emulates Meridian Tele-center Software and re-establishes transparency mode. Service affecting and fatal. Notify Product Support Engineering. Unknown MPDA interface messages will not cause this error. DMID data is:
Offset 08-09: received message.Offset 0A: A,B or C.Offset 0B: unused.
43 Received MSB LED-on message.
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
DMID data (depends on
Integration error type = 08
suberror in offset 07)
Unused
658 STATUS LOG
ACP MESSAGES 86
STATUS LOG 659
Link Status from ACP (0x84)
Up/down status of link in byte 8 (00 = OK, 01 = down).
False LTN from ACP (0x85)
Line Status Message from MID (0x86)
XON/XOFF Message Waiting (0x87)
Byte 8: 00 = XOFF, 01 = XON
Task ID Link/station ID
TaskID
Error code (84)
Unused
Status (00=OK, 01=down)
00010203 0405060708
Task ID Link/station ID
TaskID
Error code (85)Unused
False LTN
00010203 04050607 08090A0B 0C0D
Task ID Link/station ID
TaskID
Error code (86)
Status Message
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
Error code (87)
Unused
(00 = XOFF, 01 = XON)
00010203 0405060708
ACP MESSAGES87
87 APID,PID/R,DMID Alerting Message
Sends an alert that there is a call ringing on one of the peripheral integrationdevices.
0F Alerting Response for APID, PID/R, DMID
ACPCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
Unused
CP➤ACP
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
Unused
660 STATUS LOG
ACP MESSAGES 94
94 Disconnect Detected
Closes a calling session. There is no response message.
ACPCP
➤
ACPCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
Unused
STATUS LOG 661
ACP MESSAGES9B
or others, not
9B Pilot Number Download Request
Used with DMID integration and gets the pilot number as entered in Menu1.1.
1A Pilot Number Download Response
Offset Label Field Description
06-0F Pilot number For DMID, the pilot number as shown in Menu 1.1. Fused.
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
Unused
CP➤ACP
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
Pilot number(DMID only)
662 STATUS LOG
CHAPTER 6: PIC MESSAGES
This chapter provides descriptions of all control bus messages used with PICs (Primary InterfaceCards), which are sometimes referred to as PTICs (Primary Telephone Interface Cards). PICs are ableto communicate directly to the system control/data bus using an SBI (Serial Bus Interface—Octel’sproprietary bus interface ASIC).
For information on reading these descriptions, see the PIC Message Format description below. All val-ues in the illustrations are the bytes’ offsets, not sample data. Request and response messages aregrouped together, when appropriate.
PIC Message Format
PICs communicate directly to the system control/data bus using an SBI with CIP (Compact InterfaceProtocol) messages. To communicate with the CP, these messages are converted into control busform by adding the three bytes of the control bus message header. The resulting format follows:
Destination: Contains channel number to alert PIC about what kind of control bus message to expect. Channel number 01 designates a CIP message; channel number 00 designates a DMA start message.
Function code: This code tells the PIC what to do, and defines the kind of information will be in the cb message packet data.
LID/SID: Two 4-bit fields. Each hex digit represents one of the ID numbers. The Link ID is the link number that the message is from, or being sent on. The value will always be between 0 and 5 for T1, or between 0 and 3 for CEPT. The station ID is the station number that the message is for, or from, will always be between 0 and 15.
Task ID: The CP task ID that the message is for, or from.
Flags: Bit 0 is set if there are other messages to follow that contain additional information. Bit 0 is cleared if there are no other messages to follow.
Index
Numerics03 Dial Digits, 665
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Packet data
Peripheraladdress
Function code Task
ID
Flags
03Link ID (LID) Station ID (SID)
(source)
(destination)
STATUS LOG 663
08 Seize Line, 6660C Go On-Hook, 6670D Go Off-Hook, 66812 Poll Message to ACP, 6691E DMA from CP to PIC Response, 6711F Initiate DMA from CP to PIC Request, 67320 SS7 Configuration Request, 67521 Data Transfer from Another PIC Request, 67722 SMS to PIC Request, 67823 Broadcast DMA from CP to PIC Response, 67924 Get PIC Status Request, 67480 Ring No Answer Incoming Call, 68081 Busy Incoming Call, 68082 All Calls Forwarded Incoming Call, 68183 Direct Incoming Call, 68186 PIC Internal Error, 68288 Seize Line Response, 66689 Dial Digits Response, 6658E On-Hook Response, 6678F Off-Hook Response, 66893 Polling Response, 66994 Disconnect Detected, 6709D DMA from CP to PIC Request, 6719E DMA from CP to PIC Ready, 6729F Initiate DMA from CP to PIC Ready, 673AA1 SS7 Configuration Response, 675A2 Data Transfer To Another PIC Response, 676A3 SMS to PIC Response, 678A5 Broadcast DMA Response, 672A6 Get PIC Status Response, 674
STATUS LOG 664
PIC MESSAGES 03 000000
03 Dial Digits Request
Message to pass dialing information for outcalls.
89 Dial Digits Response
00 OK
01 Error
Offset Label Field Description
07 Reason 00 Outcall OK01 MTP paused02 Outcall Blocked04 Called number fail05 Call fail (from network)06 Ring no answer09 Circuit not seized10 Circuit reset
CP➤PIC
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
Extension number *
* BCD format
PICCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Link/station ID
TaskID
Reason
STATUS LOG 665
PIC MESSAGES08
08 Seize Line Request
Message to come off-hook for outcall.
88 Seize Line Response
00 OK
01 Error
Offset Label Field Description
07 Reason 00 Outcall OK01 MTP paused02 Outcall Blocked03 Originating number fail08 Outgoing not allowed09 Circuit not seized10 Circuit reset11 Parameter error
CP➤PIC
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
*BCD format; fill spare field with FF. OLI means originating line identity
Number to be used as the OLI *
which is the phone number of the calling party (i.e., the voice mail system).
PICCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Link/station ID
TaskID
Reason
666 STATUS LOG
PIC MESSAGES 0C
0C On-Hook Request
Message to put circuit back into an idle condition.
8E On-Hook Response
00 OK
01 Error
CP➤PIC
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
Unused
PICCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Link/station ID
TaskID
STATUS LOG 667
PIC MESSAGES0D
0D Off-Hook (Call Answered) Request
Message to tell the PIC to accept the incoming call.
8F Off-Hook Response
00 OK
01 Error
CP➤PIC
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
Unused
PICCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Link/station ID
TaskID
668 STATUS LOG
PIC MESSAGES 12
12 Idle Polling Request
Message sent approximately every 30 seconds to see if the PIC is still alive.
93 Idle Polling Response
CP➤PIC
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
Unused
PICCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
Unused
STATUS LOG 669
PIC MESSAGES94
94 Disconnect Detected Closes a calling session. There is no response message.
PICCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
Unused
670 STATUS LOG
PIC MESSAGES 9D
9D DMA from PIC to CP Request
1E DMA from CP to PIC Response
Offset Label Field Description
06 DMA type 04 PIC_TCAP_ROUTE (pic to pic TCAP transfer)05 PIC_SCCP_DB (pic to pic SCCP transfer)06 PIC_MTP_DB (pic to pic MTP transfer)
00010203 04050607 08090A0B 0C0E0D0F
Task ID Link/station ID
TaskID
DMA
DMAtype
length
Unused
PICCP
➤
CP➤PIC
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
Unused
DMA Length
STATUS LOG 671
PIC MESSAGES9E
9E DMA from PIC to CP Ready
00 OK
01 Error
A5 Broadcast DMA Response
00 OK
01 Error
Offset Label Field Description
09 Destination PIC FF, if broadcast.
0B Broadcast type 01 Point to point (or, not broadcast).02 Broadcast to all PICs.03 To active stack (or, not broadcast).
PICCP
➤
00010203 04050607 08090A0B 0C0E0D0F
Task ID Link/station ID
TaskID
DMA
Returncode
length
DestinationPIC
Sequence # (fromanother PIC)
Unused
Broadcast type
PICCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Link/station ID
TaskID
672 STATUS LOG
PIC MESSAGES 1F
type)
1F Initiate DMA from CP to PIC Request
9F Initiate DMA from CP to PIC Ready
00 OK
01 Error
Offset Label Field Description
06 DMA type(its7.h)
01 PIC_SS7_CONFIG (pic config DMA 1)02 PIC_MAP_CONFIG (pic config DMA 2)03 PIC_CIC_CONFIG (pic config DMA 3)04 PIC_TCAP_ROUTE (pic to pic TCAP transfer)05 PIC_SCCP_DB (pic to pic SCCP transfer)06 PIC_MTP_DB (pic to pic MTP transfer)07 SMS_TO_PIC (SMS data to CP)0C PIC_XLT_CONFIG10D PIC_XLT_CONFIG20E PIC_XLT_CONFIG30F PIC_XLT_CONFIG4
CP➤PIC
00010203 04050607 08090A0B 0C0E0D0F
Task ID Link/station ID
TaskID
DMA
DMAtype
length
DestinationPIC
Sequence # (whenfrom another PIC)
Unused
PICCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Link/station ID
TaskID
DMA type (should match 1F request’s DMA
DMA length
STATUS LOG 673
PIC MESSAGES24
24 Get PIC Status Request
The 24/A6 message pair will always be sent in a group of two control busmessage sets, one right after the other.
First 24 message format; status = 00 (get measurements status):
Second 24 message format; status = 01 (get PIC status):
A6 Get PIC Status Response
The 24/A6 message pair will always be sent in a group of two control busmessage sets, one right after the other.
First A6 message format; status = 00 (get measurements status):
Second A6 message format; status = 01 (get PIC status):
CP➤PIC
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Link/station ID
TaskID
Status
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Link/station ID
TaskID
Status
PICCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
Unused
D-channel
Physical alarmbit map
Signal Unit error(current 5 min. period)
MTP status
SS7 link state
timeslot #Status
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
Signal Unit errors
5-10 10-15 15-20 20-25 25-30Values are number of minutes ago.
Status
674 STATUS LOG
PIC MESSAGES 20
20 SS7 Configuration Request
Message to start the configuration of the PIC.
A1 SS7 Configuration Response
00 OK
01 Error
Offset Label Field Description
06 PIC Address PIC number | station number format
0D CP boot command 0 Boot system once1 Debug bootA Auto boot, even after a power outageM Manufacturing test
CP➤PIC
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
Unused
Signaling
PICaddress
Task ID
Task IDSMS
1st transferTask ID
2nd transferTask ID
3rd transferTask ID
Task ID for pollingPIC with stack
CP Bootcommand
PICCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Link/station ID
TaskID
STATUS LOG 675
PIC MESSAGESA2
read,
pe
A2 Data Transfer Request To Another PIC
This message will pass up to 10 bytes of data (offsets 06 through 0F) fromanother PIC. The data within the A2/21 control bus message pairs will beidentical. The PICs communicate through the CP as depicted in thefollowing illustration.
Offset Label Field Description
03 Destination PICLink/station ID Link and station ID of the destination PIC.
05 Originating PICLink/station ID Link and station ID of the originating PIC.
06 Protocol byte This byte is split into two parts, as shown below. Toconvert to binary.
Protocol type:0 Echo data Send (Requester_Recipient)1 Echo data Ack (Recipient_Requester)2 SS7 TUP message3 DMA Ack message4 System parameter message5 Debug message
6-8 Spare
PICCP
➤
A2 21
A221
destination
originating
originating
destination
Message pair 1 -->
<-- Message pair 2
anotherCPPIC PIC
00010203 04050607 08090A0B 0C0D0E0F
Task IDOriginating PIC
TaskID
PIC to PIC data
Protocol byteLink/station ID
050607
0000 00117Bit count 0346
Protocol tySequence #Follow-on bitbeginning at 0
676 STATUS LOG
PIC MESSAGES 21
read,
ype
21 Data Transfer Response from Another PIC
This message will pass up to 10 bytes of data (offsets 06 through 0F) fromanother PIC. The data within the A2/21 control bus message pair will beidentical. The Originating PIC enables the Destination PIC to distinguishreceived CIP messages from multiple sources (see A2 message for moreinformation).
Offset Label Field Description
03 Destination PICLink/station ID Link and station ID of the destination PIC.
05 Originating PICLink/station ID Link and station ID of the originating PIC.
06 Protocol byte This byte is split into two parts, as shown below. Toconvert to binary.
Protocol type:0 Echo data Send (Requester_Recipient)1 Echo data Ack (Recipient_Requester)2 SS7 TUP message3 DMA Ack message4 System parameter message5 Debug message
6-8 Spare
CP➤PIC
00010203 04050607 08090A0B 0C0D0E0F
Task IDDestination PIC
TaskID
PIC to PIC data
Protocol byteLink/station ID
Originating PICLink/station ID
050607
0000 00117Bit count 0346
Protocol tSequence #Follow-on bitbeginning at 0
STATUS LOG 677
PIC MESSAGES22
utgoing
o the SM)
oing SMS
o the SM)
s whetherin a HLRs
r) that the
erver’s
r)
22 SMS to PIC Request
A3 SMS to PIC Response
Offset Label Field Description
05 CIP types andextra formats
03 ACK message (acknowledgement to previous o SMS message)
offset 06: Message reference (SMS ref. toffsets 07-0F: Unused
04 Error message (protocol error to a previous outgmessage)
offset 06: Message reference (SMS ref. toffset 07-08: Major error codeoffset 08-09: Minor error code
offset 0A: Message waiting data set (markthe service center is contained message waiting data)
offset 0B-0F: Unused05 Alert message (incoming alert info to SMS serve
offset 06: MSISDN (subscriber’s identifierSM is addressed to.)
offset 07-0F: Unused06 Open/close response (final result code of SMS s open or close requests)
offset 06: Result (00 = success; 01 = errooffset 07-oF: Unused
CP➤PIC
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
Service Center Address
PICCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
Format depends on CIP type
CIP type
678 STATUS LOG
PIC MESSAGES 23
23 Broadcast DMA from CP to PIC Response CP➤PIC
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
Station #
Sequence
sending DMA
DMA resultsBitmap of PIC
Number
Unused
STATUS LOG 679
PIC MESSAGES80
80 Ring No Answer Incoming Call
This message is to send the called party and calling party ID to the CPUwhen a call is forwarded because of ring no-answer. There is no responsemessage.
81 Busy Incoming Call
This message is to send the called party and calling party ID to the CPUwhen a call is forwarded because the extension is busy. There is noresponse message.
PICCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
Called party ID* Calling party ID*
* BCD Format
PICCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
Called party ID* Calling party ID*
* BCD Format
680 STATUS LOG
PIC MESSAGES 82
82 All-Calls-Forwarded Set in Incoming Call
This message is to send the called party and calling party ID to the CPUwhen a call is forwarded because the extension is in all-calls-forward mode.There is no response message.
83 Direct Incoming Call
This message is to send the calling party ID to the CPU when the call is adirect call.There is no response message.
PICCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
Called party ID* Calling party ID*
* BCD Format
PICCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID Link/station ID
TaskID
Called party ID* Calling party ID*
* BCD Format
STATUS LOG 681
PIC MESSAGES86
of error which defines
nes for the Application
ines for the ATH which
Message Dispatching
86 PIC Internal Error
A PIC detected an internal system error or an integration error. Interpreta-tion depends on the integration type, which is identified in offset 06:
09 Non-Service Affecting
0A SCCP/TCAP/MAP stack failed
0B Service Affecting
The structure of offsets 00 through 0F is dependant on whether the error isbeing logged by a PIC 286 or PIC 386. Offset 07 determines which type ofPIC, and the rest of the CB message format.
PIC 286 error (if offset 07 = 0)
Offset Label Field Description
06 PIC error type 09 Non-Service Affecting0A Stack error (SCCP/TCAP/MAP)0B Service Affecting
07 Task ID Task ID = 0 identifies a PIC 286 error.
08 Error type For PIC 286 errors, this offset defines the typethe remainder bytes of the error log entry:
01 Obituary alarms02 Trouble alarms03 Physical alarms04 Link alarms05 Link status
09-0A * * Data depends ontype in offset 08.
For error type = 1 or 2 (obituary or trouble)Module ID (values follow):
0402 ath_utl.c: This module contains routiTrouble Handler (ATH).
0405 ath_ss7.c: This module contains routare unique to the SS7 routine.
0602 ss7_md.c: This module contains the (MD) primitives for a SS7 build.
PICCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID PIC/station ID*
TaskID
data (format depends
PIC error type
on value in offset 07)
* refer to the PIC Messages Index page for breakdown of this byte.
682 STATUS LOG
PIC MESSAGES 86
e functions to insert network management this queue and send plication.
SS7 Application Data
ty routines for the ADL ting the SS7 database.
e routines that process ral Maintenance). gement messages .
he routines that pro-t (SS7 Management).
e Board ID Prom mes-pl_id_bip).
e topmost layer of serves as an interface ther applications.
routines that process
routines that process
routines that process
routines that process
routines that process
routines that process
routines that process
routines that process
routines that process
routines that process
09-0A * * Data depends on type in offset 08.
For error type = 1 or 2 (obituary or trouble)Module ID (values follow - continued):
0603 ss7_l3md.c: This module contains thmessages into the level-3 signalling queue and then get messages from the message to the correct level-3 ap
0701 adl_ss7.c: This module contains the Loader (ADL) functions.
0702 adl_utls.c: This module contains utiliin assisting in downloading and upda
0801 ss7_pmtc.c: This module contains thmessages for appl_id_pmtc (PeripheThese messages include SS7 manareceived from the admin. subsystem
1001 ss7_mgmt.c: This module contains tcess messages for appl_id_ss7_mgm
1201 bip_ss7.c: This module processes thsages sent to the SS7 CAP card (ap
2001 mmd_mgr.c: This module contains thMessage Monitor Debug (MMD) andbetween the internals of MMD and o
2A01 ss7_tlac.c: This module contains themessages for appl_id_tlac.
2B01 ss7_tsfc.c: This module contains themessages for appl_id_tsfc.
2C01 ss7_tcoc.c: This module contains themessages for appl_id_tcoc.
2E01 ss7_tcbc.c: This module contains themessages for appl_id_tcbc.
3201 ss7_tcrc.c: This module contains themessages for appl_id_tcrc.
3301 ss7_tsfc.c: This module contains themessages for appl_id_tsfc.
3401 ss7_llsc.c: This module contains themessages for appl_id_llsc.
3501 ss7_lsac.c: This module contains themessages for appl_id_lsac.
3601 ss7_lsla.c: This module contains themessages for appl_id_lsla.
3701 ss7_lslr.c: This module contains the messages for appl_id_lslr.
PIC 286 error (if offset 07 = 0)
Offset Label Field Description
STATUS LOG 683
PIC MESSAGES86
routines that process
routines that process
routines that process ting Management, Sig-
routines that process
routines that process
e routines that process g Link Message Han-
e routines that process e Distribution).
t deal with the conver-ternal format and inter-essage is one received as been passed up to ernal message is one ing the Message Dis-essage is converted,
put into a system application.
utines for SS7 level-3
e routines for timed t should access the
e.
he messages for
ines that sends signals
ome of the Interrupt ector Initialization rou-
e routines to handle
09-0A * * Data depends on type in offset 08.
For error type = 1 or 2 (obituary or trouble)Module ID (values follow - continued):
3801 ss7_rtpc.c: This module contains themessages for appl_id_rtpc.
3901 ss7_rtac.c: This module contains themessages for appl_id_rtac.
3A01 ss7_rsrt.c: This module contains themessages for appl_id_rsrt (SS7 Rounalling Route-Set Test).
3B01 ss7_rtcc.c: This module contains themessages for appl_id_rtcc.
3D01 ss7_rtrc.c: This module contains themessages for appl_id_rtrc.
3E01 ss7_hmrt.c: This module contains thmessages for appl_id_hmrt (Signallindling, Message Routing).
4801 ss7_hmdt.c: This module contains thmessages for appl_id_hmdt (Messag
4802 ss7_h0h1.c: This file has routines thasion of messages from external-to-innal-to-external format. An external mfrom the remote level-3 node which hMessage Distribution (HMDT). An intthat can be sent to a named entity uspatcher facilities. When an external mthe raw data is repackaged and thenbuffer to be sent to the proper level-3
4803 ss7_hmdc.c: This file contains the roMessage Discrimination.
4901 timedmsg.c: This module contains thmessages and is the only module thaglobal variable g_tmsg_ctrl[] by nam
4902 ss7_mgr.c: This module processes tappl_id_ss7.
4903 ss7signl.c: This module contains routto applications.
4904 ss7_isr.asm: This module contains sService Routines and the Interrupt Vtine.
4905 ss7_dr.asm: This module contains thDMA Receive Interrupts.
PIC 286 error (if offset 07 = 0)
Offset Label Field Description
684 STATUS LOG
PIC MESSAGES 86
e routines for the r for MTP.
ines that are unique to l.
ines that are unique to ol.
tines that deal with the
he routines for the er for MTP.
routines that will pro-
routines for hardware
routines that process mic Data Loader (DDL) s-loads a remote SS7 ta, and 2) hunts for an from. Dynamic data is kset_table [ ], and y the AMS-CAP at ese tables change as failures. As each SS7 copy of another SS7 m is initialized, it can rmally, DDL can er SS7 card.
routines that process Link Test Control).
he MTP remote con- consists of receipt of ngestion test; these rks congestion control
message priorities.
e SS7 measurement on of local/module data to locally manage data structures.
he global SS7 mea-e accessed by other
09-0A * * Data depends on type in offset 08.
For error type = 1 or 2 (obituary or trouble)Module ID (values follow - continued):
4906 ss7_rc.asm: This module contains thReceive Control of the low level drive
4907 ansiss7.c: This module contains routthe ANSI version of the SS7 protoco
4908 ccittss7.c: This module contains routthe CCITT version of the SS7 protoc
4909 ss7_rtbl.c: This module contains rouSS7 routing table.
490A ss7_txc.asm: This module contains tTransmit Control of the low level driv
490B ss7_ds1.c: This module contains thegram the DS1 and CEPT interfaces.
490C ss7_hwc.c: This module contains theinitialization.
4C01 ss7_ddl.c: This module contains the messages for appl_id_ddl. The Dynaprovides two main functions: 1) croscard, upon request, with dynamic daSS7 card to receive its dynamic datathe portion of the routing_table[ ], linlink_table[ ] that can not be loaded bpower-on. The dynamic portions of ththe network incurs and recovers fromcard powers up, it needs to receive acard’s dynamic data. Once the systeoperate normally. While operating noreceive requests to cross-load anoth
4E01 ss7_sltc.c: This module contains themessages for appl_id_sltc (Signalling
4F01 ss7_rcc.c: This module implements tgestion control (RCC) software. ThisTFCs and the signalling route set coprocedures are based on U.S. Netwousing multiple congestion levels with
5201 meas_ss7.c: This module contains thslave code. This includes the allocatistructures and any functions neededthese measurements and access the
5202 meas_s7d.c: This module allocates tsurement data structures that must bapplications (to peg and time).
PIC 286 error (if offset 07 = 0)
Offset Label Field Description
STATUS LOG 685
PIC MESSAGES86
ackground data-sanity en the databases on at each SS7 card’s as another’s database. he System-Debug-Ser-
- if error code is module ID coding):
n from another PIC.
rom bad link on change
on data twice.
n data.
is too large.
anged during the static
g code.
alternate-restricted.
normal-restricted.
inaccessible.
for traffic.
nt code.
oint code for transmis-
ed a loss of messages.
ement.
or is running MTP.
ot itself.
09-0A * * Data depends on type in offset 08.
For error type = 1 or 2 (obituary or trouble)Module ID (values follow - continued):
5E01 snoop.c: This module implements a bcheck on SS7 cards to determine whSS7 cards become different. Note thdatabase must be exactly the same The snooping is implemented using tvice’s-Dump-Memory command.
0B * * Data depends on type in offset 08.
For error type = 1 or 2 (obituary or trouble)Statement ID
0C-0D * * Data depends on type in offset 08.
For error type = 1 or 2 (obituary or trouble)Error code (the most common values followincurred other than what is defined, refer to
0101 Unexpected error code.
0102 MTP failed to get updated informatio
0103 Failed to recover transmit message fover.
0104 MTP was loaded with static applicati
0105 Timed out waiting for static applicatio
0106 Static application data table number
0107 Originating card or transaction ID chapplication data load.
0108 Inconsistency in loading 286 operatin
0109 A destination point code has become
010A A destination point code has become
010B A destination point code has become
010C A destination point code has allowed
010D Cannot determine the status of a poi
010E A route had become prohibited.
010F A route has allowed for traffic.
0110 A route has become restricted.
0112 Routing failed to find the requested psion.
0113 Link/linkset/reroute on-hold has caus
0114 Failed to create timer linked-block el
0115 Link is in change over, change back,
0116 PIC 286 has been instructed to rebo
PIC 286 error (if offset 07 = 0)
Offset Label Field Description
686 STATUS LOG
PIC MESSAGES 86
- if error code is odule ID coding - con-
d.
ve become congested.
.
too large.
have been created.
g data, deleting an ge error.
g table is not in sorted
ot itself.
p link in service.
sage signal units stuck
0C-0D * * Data depends on type in offset 08.
For error type = 1 or 2 (obituary or trouble)Error code (the most common values followincurred other than what is defined, refer to mtinued):
0117 Level 2 queue has overflowed.
0118 Level 3 receive queue has overflowe
0119 Too many destination point codes ha
011A Watchdog expiration.
011B Transfer congestion status is in error
011C Unexpected error code.
011D Static application data link number is
011E Unexpected error code.
011F Unexpected error code.
0120 Routing table search algorithm error.
0121 Configuration error: too many routes
0122 Invalid timer value or user part routinactive link, or general update messa
0123 Configuration error: static data routinin numerical order.
0124 PIC 286 has been instructed to rebo
0125 Lost too many system buffers to kee
0126 Level 2 transmission buffer has mesin it.
01B1 Invalid case selector.
01B2 Invalid else condition.
01B3 Bad code reached.
01B4 Null pointer.
01B5 Invalid pointer.
01B6 Table boundary exceeded.
01B7 Table checksum invalid.
01B8 Invalid card address.
01B9 Invalid subsystem directory.
01BA Invalid application ID.
01BB Invalid function ID.
01BC Invalid application data.
PIC 286 error (if offset 07 = 0)
Offset Label Field Description
STATUS LOG 687
PIC MESSAGES86
- if error code is odule ID coding - con-
f memory resources.
terminal) disabled
0C-0D * * Data depends on type in offset 08.
For error type = 1 or 2 (obituary or trouble)Error code (the most common values followincurred other than what is defined, refer to mtinued):
01BD Invalid message length.
01BE Inconsistent queue status.
01BF Queue elements overwritten.
01C0 Corrupted list.
01C1 Unexpected timer expired.
01C2 Unexpected count value.
01C3 Unexpected value because of lack o
01C4 Out of system buffers.
01C5 Read failed.
01C6 Read invalid in AMT.
01C7 Write failed.
01C8 Write invalid in AMT.
01C9 Open failed.
01CA Close failed.
01CB Delete failed.
01CC Invalid buffer state.
01CD Table entry missing.
01CE Invalid buffer address.
01CF Out of resources.
01D0 Unexpected message.
01D1 Card’s MTC (peripheral maintenance(286 shutdown).
0400 - 04FF Unexpected fatal interrupts.
0E-0F * * Data depends on type in offset 08.
For error type = 1 or 2 (obituary or trouble)Unused (zeros).
PIC 286 error (if offset 07 = 0)
Offset Label Field Description
688 STATUS LOG
PIC MESSAGES 86
been lost.n has been lost.
it in 1,000 bits.it in 10,000 bits.it in 100,000 bits..
times the condition et.
09 * * Data depends on type in offset 08.
For error type = 3 (physical alarms)Alarm condition:
01 Receive carrier has been lost.02 Receiving unframed all 1’s.03 Receiving all 1’s in time slot 16.04 Receive frame synchronization has 05 Receive CRC4 frame synchronizatio06 Receiving a bit error rate of 1 bad b07 Receiving a bit error rate of 1 bad b08 Receiving a bit error rate of 1 bad b09 Receiving an alarm from the far end
0A * * Data depends on type in offset 08.
For error type = 3 (physical alarms)Alarm switch:
00 An alarm condition abatement.01 An alarm condition onset.
0B * * Data depends on type in offset 08.
For error type = 3 (physical alarms)Fail count: This number indicates how manyoccurred in the 5 seconds prior to alarm ons
0C-0F * * Data depends on type in offset 08.
For error type = 3 (physical alarms)Unused (zeros)
09-0A * * Data depends on type in offset 08.
For error type = 4 (link alarms)Link alarm values:00CC SLTM failed or did not run.00F8 Link will not come into service.00F9 Incorrect PC from adjacent node.00FA Incorrect SLS received.00FB SLTM acknowledgment time-out.
00FC Incorrect data received.00FD Management inhibit denied.00FE Inhibit acknowledgment time-out.00FF Management uninhibit denied.0100 Uninhibit acknowledgment time-out.
0B-0F * * Data depends on type in offset 08.
For error type = 4 (link alarms)Unused (zeros)
PIC 286 error (if offset 07 = 0)
Offset Label Field Description
STATUS LOG 689
PIC MESSAGES86
09 * * Data depends on type in offset 08.
For error type = 5 (link status)Previous state code:
00 Internal error.01 In service.02 Locally inhibited.03 Remotely inhibited.04 Remotely blocked.
05 Run signalling test.06 Deactivated.07 No signalling link.08 Abnormal service.09 Locally uninhibited.
0A * * Data depends on type in offset 08.
For error type = 5 (link status)Current state code:
00 Internal error.01 In service.02 Locally inhibited.03 Remotely inhibited.04 Remotely blocked.
05 Run signalling test.06 Deactivated.07 No signalling link.08 Abnormal service.09 Locally uninhibited.
0B-0F * * Data depends on type in offset 08.
For error type = 5 (link status)Unused (zeros)
PIC 286 error (if offset 07 = 0)
Offset Label Field Description
690 STATUS LOG
PIC MESSAGES 86
severity which in turn bus message:
ll be entered in the CP
rrors has been status log.
ible hexadecimal val-
1.
P) task.AP) protocol.
ages from the CP and . The task will then post sk based on the infor-).
IN_LIB).
messages from tasks ssion to the CP
PIC 386 error (if offset 07 > 0)
Offset Label Field Description
05 Error severity For PIC 386 errors, this offset defines the error will define bytes 08 through 0F of the 86 control
01 Fatal error: the PIC will restart.02 Error log: an error has occurred which wi
status log.03 Pack count: a threshold for non-serious e
exceeded; error will be entered in the CP
06 PIC error type 09 Non-Service Affecting0A Stack error0B Service Affecting
07 Task ID Task ID > 0 identifies a PIC 386 error. The possues are as follows:
01 Idle task.02 On-line debug task.03 Control bus receive task (CBIN).04 Control bus transmit task (CBOUT).
05 DMA transmit and receive task.06 PCM highway task.07 Provisioning task.10 System buffer handler task.
11 L3 and L4 router task.12 Queue to MTP L3.13 System Trouble Handler (STH) task.14 System download task.
20-3F Telephone User Part (TUP) tasks 0 - 340 Call Control task50 Signalling Connection Control Part (SCC51 GMSC task -- Mobile Application Part (M
08 * * Module ID - data depends on error severity and Task ID in offsets 05 and 07, respec-tively.
For error severity = 01... Module ID = 0.
For error severity > 01... ... and Task ID = 03 (CB-IN):
01 cbin.c: This task will receive CB messverify that the checksums are correctthe CB message(s) to the required tamation in the CB header (CBIN_MAIN
02 cbinlib.c: Control bus input library (CB
... and Task ID = 04 (CB-OUT):01 cb_send.c: This task will receive CB
and then have the SBI verify transmi(CB_SEND_MAIN).
STATUS LOG 691
PIC MESSAGES86
RTX details from the igh level steps required _INTERF).
tes the DMA state to determine which ommand from the CP
, this module contains sent to and from the
rms all queuing of DMA other PICs in the sys-iting to be transmitted send requests that are DMA transfer are S).
ates all details regard-le completely hides the her layer modules be the DMA Send
messages from the sing is correct. Next,
to the required task er (PCM_MAIN).
d for provision and ails of the remote point he VPS will be commu-
he functionality to he state of the PIC and tionality to move the , turn the stack on or
08 * * Module ID - data depends on error severity and Task ID in offsets 05 and 07, respec-tively.
For error severity > 01......and Task ID = 05 (DMA_SEND):
01 DMA_interf.c: This module hides all Vrest of the DMA task. It performs all hto perform I/O DMA operations (DMA
02 DMA_state.c: This module encapsulamachine. The state machine is used action to take in response to a DMA cand other tasks on the PIC TIC. Alsoall details concerning CIP messagesCIP (DMA_ST_MACH).
03 DMA_send_req.c: This module perfosend requests made by PIC tasks to tem. DMA send requests that are waare stored on the sendQ, while DMA waiting for the result of their previousstored on the wait_list (DMA_QUEUE
04 DMA_bcast.c: This module encapsuling DMA broadcasts. Also, this moduDMA Send Request module from higproviding nearly identical interface toRequest module (DMA_BCAST).
...and Task ID = 06 (PCM):01 pcm.c: This task will receive the PCM
PCM ASIC and verify that the addresthe task will post the PCM message based on the information in the head
...and Task ID = 07 (PROVISION):
01 prov.c: PROV_MAIN02 provmisc.c: PROV_MISC03 prov.c: PROV_DMA
04 prov_sccp.c: This module is designereprovision of the SCCP task with detcodes and subsystem numbers that tnicating with (PROV_SCCP).
05 prov_stack.c: This module provides trespond to a CP poll inquiring about tStack. In addition it provides the funcstack from one PIC to another, that isoff (PROV_STACK).
06 prov_updglb.c: PROV_UPDGLB
PIC 386 error (if offset 07 > 0)
Offset Label Field Description
692 STATUS LOG
PIC MESSAGES 86
e system buffer task of ompletion and when sing
er task of informing the d when the router
cellaneous router task
e system buffer mes- the messages into the END_286_MAIN).
TX details from the TH) task by 1) placing
g, 2) shutting down the ccurs, and 3) de-allo-gnizable message
ils concerning the 286 st of the STH task. e of the structure for L_HDLR_286).
Loader module for ding of application soft-ard and the MASCAM
the SS7 Application R).
s routines for software ADS).
iable definitions and _ADL_UTIL).
08 * * Module ID - data depends on error severity and Task ID in offsets 05 and 07, respec-tively (continued).
For error severity > 01......and Task ID = 10 (SYSTEM_BFR):
01 system_bfr.c: This module defines thinforming the system of initialization cthe system buffer should start proces(SYSTEM_BFR_MAIN).
...and Task ID = 11 (ROUTER):01 router.c: This module defines the rout
system of initialization completion anshould start processing (ROUTER_MAIN).
02 routermisc.c: This module defines misfunctions (ROUTER_MISC).
...and Task ID = 12 (SEND_286):01 send_task.c: This task will receive th
sages from various tasks and will putdual port ram and interrupt the 286 (S
...and Task ID = 13 (SYS_TRBL):01 trbl_interf.c: This module hides all VR
rest of the System Trouble Handler (Sall PIC error logs onto the CP error loentire PIC board when a fatal error ocating all memory buffers with unrecotype IDs (SYS_TRBL_MAIN)
02 286_hdlr.c: This module hides all detaprocessor and MTP code from the reSpecifically, it encapsulates knowledg286 trouble and obituary reports (TRB
...and Task ID = 14 (SW_DNLD):01 sw_dnld.c: SW_DNLD_MAIN
02 sw_sldr_mgr.c: This file is the Systemthe Eagle Platform which controls loaware and data to a peripheral CAPx c(SW_SLDR_MGR).
03 sw_adl_mgr.c: This module containsData Loader functions (SW_ADL_MG
04 sw_adl_loads.c: This module containApplication Data loads (SW_ADL_LO
05 sw_adl_util.c: This file consists of varsoftware download utility routines (SW
06 sw_misc.c: SW_MISC
07 sw_adl_dnld.c: SW_ADL_DNLD
PIC 386 error (if offset 07 > 0)
Offset Label Field Description
STATUS LOG 693
PIC MESSAGES86
achine to process It responds to those n outgoing message ed incoming message hen translated from
ons are defined in this ry personal communi-67 (TUPIN).
ions are defined in this ry personal communi-67 (TUPOUT).
vides primitive func-d receive queue mes-
unctions to build ).
P interface between ).
ol library which has the _qid, cc_qpost,
tines to trace events.
trol primitive which : cc_cip_2_tup_prim.
trol task provision
llowing functions: plete, cc_send_msg.
08 * * Module ID - data depends on error severity and Task ID in offsets 05 and 07, respec-tively (continued).
For error severity > 01......and Task ID = 14 (SW_DNLD):
08 sw_adl_lkmgr.c: SW_ADL_LKMGR
...and Task ID = 20 - 3F (TUPs):01 btup.c: This function is a finite state m
TUP messages and internal events. events with appropriate action and aaccording to current state and receivor internal events. The statement is tSDL progression charts (TUPMAIN).
02 btupin.c: All the incoming state functimodule. The incoming state of Mercucation L4 TUP will conform to BTNR1
03 btupout.c: All the outgoing state functmodule. The incoming state of Mercucation L4 TUP will conform to BTNR1
04 btupmsg.c: The message handler protions call to other modules to send ansages (TUPMSG).
05 btupbld.c: This module contains the frequired TUP messages (TUPBUILD
06 btuplib.c: This library provides the CITUP task and CP line tasks (TUPLIB
...and Task ID = 40:01 cc_main.c: Call control task main.
02 cc_lib.c: This module is the call contrfollowing functions: bcd_cpl, get_tupcc_alloc_tup_prim_buf, and cc_alloc_tup_int_buf.
03 cc_trace.c: This module performs rou
04 cc_prim.c: This module is the call concontains the CIP to primitive function
05 cc_prov.c: This module is the call conupdate.
...and Task ID = 40:06 cc_sprc.c: This library contains the fo
cc_wait_for_msg, cc_await_sys_com
PIC 386 error (if offset 07 > 0)
Offset Label Field Description
694 STATUS LOG
PIC MESSAGES 86
g routines for SCCP m the SCCP task con-ges between SCCP YSMSG).
, performs the transla-s, both of which are (SYSGTT).
e GMSC task input/out-st details concerning TIC and on the CP. It ation procedure by sts and indications
he functions to support intelligence of how to n MSC (GMSC_APP).
s all details involving at a system can com-LR_table database. nctionality for sending
TCAP indication proto-e passed and trans- layer indications can
rotocol aborts, and
e functionality required ia TCAP primitives. It .
ro interface to the pur-INTERF).
08 * * Module ID - data depends on error severity and Task ID in offsets 05 and 07, respec-tively (continued).
For error severity > 01......and Task ID = 50 (TO_SCCP_REQ):
01 sysmem.c: SYSMEM
02 sysmsg.c: This module defines portinIPC and it hides the VRTX details frocerning sending and receiving messaand all other tasks on the 386 PIC (S
03 sysgtt.c: This module, for SCCP onlytion of MSC addresses to DPC valueunique to the Mercury PCN network
...and Task ID = 51 (TO_GMSC):01 GMSC_io.c: This module contains th
put functions. In addition, it hides mothe interaction with tasks on the PIC drives all actions of the GMSC applicchecking the TO_GMSC_Q for reque(GMSC_IO).
02 GMSC_app.c: This module contains tShort Message Service, including thesend a short message to a destinatio
03 HLR_req.c: This module encapsulateHLRS, including all possible HLRs thmunicate with as maintained in the HAlso, this module contains all MAP fuHLRs requests for service(HLR_REQ).
...and Task ID = 51 (TO_GMSC):04 in_traffic.c: This module contains all
col handling. All TCAP indications arlated into MAP layer indications. MAPtake form of ACKs, protocol errors, palerts (IN_TRAFF).
05 out_traffic.c: This module contains thto send a SM to a destination MSC vcontains no database (OUT_TRAFF)
06 tcap_interf.h: This file contains a macchased TCAP protocol layer (TCAP_
PIC 386 error (if offset 07 > 0)
Offset Label Field Description
STATUS LOG 695
PIC MESSAGES86
as in the library and ystem is about to 0
r codes are generic offset 07):
ter during INIT.
present.
onent.
ore ID error.
group/semaphore.
09 * * Data depends on offset 05.
For error severity > 01...Statement ID
For error severity = 01...Statement ID = 0; this means that the error w
was a result of a system exception (the scrash). Module ID = LIB_EXCEPTION =
0A * * Data depends on offset 05.
For error severity = 01...0A - 0B Intel order checksum.
For error severity > 01...Offset 0A is an error code. The following erropossibilities, regardless of the Task ID value (
01 Internal bug; task ID error.
02 Internal bug; no TCBs available.
03 Internal bug; no memory available.
04 Internal bug; not a memory block.
05 Internal bug; mailbox in use.
06 Internal bug; zero message.
07 Internal bug; buffer full.
08 Internal bug; WAITC in progress.
09 Internal bug; invalid system call.
0A Internal bug; time-out.
0B Internal bug; no message present.
0C Internal bug; queue ID error.
0D Internal bug; queue full.
0E Internal bug; partition ID error.
0F Internal bug; fatal initialization error.
10 Internal bug; no character present.
11 Internal bug; invalid configuration parame
12 Internal bug; invalid input parameter,PCREATE/PEXTEND.
20 Internal bug; component vector table not
21 Internal bug; undefined component.
22 Internal bug; undefined op code for comp
30 Internal bug; no control blocks available.
31 Internal bug; event flag group or semaph
32 Internal bug; tasks pending on event flag
PIC 386 error (if offset 07 > 0)
Offset Label Field Description
696 STATUS LOG
PIC MESSAGES 86
r codes are generic offset 07):
ore is deleted.
phore overflow.
buffer problem.
essage buffer problem.
stem buffers.
t up due to task initial-BIN_TASK_INIT_FAIL
figured
SEND_DMA_QFL).
ADD_WAIT).
TCH).
GEN_FAILURE).
A or CP
0A * * Data depends on offset 05.
For error severity > 01...Offset 0A is an error code. The following erropossibilities, regardless of the Task ID value (
33 Internal bug; event flag group or semaph
34 Internal bug; event flag already set/sema
F8 Internal bug; not provisioned.
F9 Internal bug; not implemented.
FA Internal bug; switch default.
FB Internal bug; bad pointer.
FC Internal bug; PIC message type.
FD System overloaded or internal bug; TCAP
FE System overloaded or internal bug; CB m
FF System overloaded or internal bug; no sy
...and Task ID = 03 (CBIN):41 Internal bug; PIC board failed on star
ization failure or CIP transfer (ERR_Cor ERR_CBIN_CIP_XRF).
...and Task ID = 05 (DMA_SEND):41 Internal bug; system not properly con
(ERR_BAD_CONFIG).
42 Send DMA queue overloaded (ERR_
43 Internal bug (ERR_NO_DEQ).
44 Internal bug; no add wait (ERR_NO_
45 Internal VRTX error (ERR_BAD_FLAGS).
46 In DMA time-out; information only (ERR_IN_DMA_TIMEOUT).
...and Task ID = 05 (DMA_SEND):47 Out DMA time-out; information only
(ERR_OUT_DMA_TIMEOUT).
48 Internal bug; invalid state (ERR_INVALID_STATE).
4A Internal bug; invalid buffer (ERR_INVALID_BUFTYPE).
4B Internal bug; no match (ERR_NOMA
4C Internal bug; DMA overloaded (ERR_
4D Internal bug; invalid ACK with the DM(ERR_INVALID_ACK).
PIC 386 error (if offset 07 > 0)
Offset Label Field Description
STATUS LOG 697
PIC MESSAGES86
r codes are specific (offset 07):
munication failure
P_MSG_ASUI_INFO).
0A * * Data depends on offset 05.
For error severity > 01...Offset 0A is an error code. The following erropossibilities, depending on the Task ID value
...and Task ID = 05 (DMA_SEND):4E Internal bug; DMA to self
(ERR_DMA_TO_SELF).
4F Transmit abort due to PIC to CP com(ERR_ABORT_TRANSMIT).
...and Task ID = 07 (PROV):40 ERR_PCDB_OFL
41 ERR_PROV_DMA_TYPE
42 ERR_PROV_CBIN_MSG
43 ERR_PROV_UPDATE
51 ERR_SCCP_PROV_NACK
52 ERR_NOREADER_SYNCH
53 ERR_INVALID_STACK
...and Task ID = 11 (ROUTER):41 ERR_BAD_SCCP_FUNCID
42 ERR_BAD_TUP_FUNCID
...and Task ID = 13 (SYS_TRBL):41 ERR_FAIL_SEND_MSG
42 ERR_NOTA_BUFFER
...and Task ID = 14 (SW_DNLD):41 ERR_ROUTE_ENTRY
...and Task ID = 20-3F (TUP):41 Invalid IRC
(ERR_TUP_MSG_ACI_IRC).
42 Invalid ICC (ERR_TUP_MSG_ACI_ICC).
43 Invalid ASCI message info (ERR_TU
44 Cannot build IFAM message (ERR_TUP_BUILD_IFAM_MSG).
45 Cannot build SASUI message (ERR_TUP_BUILD_SASUI_MSG).
46 Cannot build ASUI1 message(ERR_TUP_BUILD_ASUI1_MSG).
47 Cannot find CIC code (ERR_TUP_CIC_ACCESS).
48 ERR_TUP_DIR_STATE
PIC 386 error (if offset 07 > 0)
Offset Label Field Description
698 STATUS LOG
PIC MESSAGES 86
r codes are specific (offset 07):
).
.
.
0A * * Data depends on offset 05.
For error severity > 01...Offset 0A is an error code. The following erropossibilities, depending on the Task ID value
...and Task ID = 20-3F (TUP):49 Internal bug (ERR_TUP_TIMER_OP
...and Task ID = 50 (TO_SCCP_REQ):41 Internal bug (ERR_GT_FORMAT).
42 Internal bug (ERR_NO_IBLK_DEST)
...and Task ID = 51 (TO_GMSC):41 ERR_GEN_GMSC_BUG
42 ERR_INVALID_HANDLE
43 ERR_INVALID_COMPONENT
44 ERR_UNI_IND
45 ERR_CONTINUE_IND
46 ERR_INVALID_INVOKEID
47 ERR_ILLEGAL_LENGTH
48 ERR_BAD_SCADR
49 ERR_BAD_MSISDN
4A ERR_NOT_VALID_SC
4B ERR_INVALID_CANCEL
4C ERR_BAD_HLR_TABLE
4D ERR_PREMATURE_CLOSE
0B-0F* * Data depends on offset 05.
For error severity = 01...0C - 0F EIP
For error severity > 01...Additional error information, currently unused
PIC 386 error (if offset 07 > 0)
Offset Label Field Description
STATUS LOG 699
CHAPTER 7: LAN CARD MESSAGES
This chapter provides descriptions of all control bus messages used with LAN cards. For informationon reading these descriptions, see Section 1.5.3, “Control Bus Messages,” on page 35. All values inthe illustrations are the bytes’ offsets, not sample data. Request and response messages are groupedtogether.
Request and response messages are grouped together and organized by the message type of therequest. These can be found by checking the numbers in the upper-outer corners of the pages whileflipping through the chapter. Or, message descriptions can be found by checking the index below.
Index
Numerics22 Reset, 70323 Reset Response, 70326 Open Channel, 70427 Open Channel Response, 70428 Read Data, 70529 Read Data Ready, 7052A Read Data Complete, 7062B Write Data, 7072C Write Data Ready, 7072D Write Data Complete, 7082E Outgoing Connect Request, 7092F Outgoing Connection Response, 70930 Outgoing Connection Status, 71031 Incoming Connection, 71132 Incoming Connection Status, 71133 Incoming Connection Status Response, 71234 Disconnect Channel, 71335 Disconnect Channel Response, 71336 Request Network Service, 71437 Request Network Service Response, 7153A Data Message In, 7163B NIC Session Status, 7163D Write Data Network Service, 7183E Write Data Ready Network Service, 7183F Write Data Complete Network Service, 71940 Read Data Network Service, 72041 Read Data Ready Network Service, 72042 Read Data Complete Network Service, 72143 Write Initial Configuration, 72244 Write Initial Configuration Response, 72245 Write Data Configuration, 723
STATUS LOG 701
46 Write Data Ready Configuration, 72347 Write Data Complete Configuration, 72448 SNMP Notification, 72549 Read Trace Buffer, 7264A Read Trace Buffer Response, 7264B Read Error Log, 7274C Read Error Log Response, 7274D Set Time of Day, 7284E Set Time of Day Response, 7284F Set Task Trace, 72950 Set Task Trace Respons, 730
LAN CARD MESSAGES 22
22 Reset
The CP sends this CB message to the LAN card to request that it discon-nect all channels and shutdown.
23 Reset Response
The LAN card sends this CB message to the CP in response to the shut-down (Reset) request .
00 OK.
Offset Label Field Description
03 Code 00 = Immediate shutdown (not orderly).
CP➤LAN
Task ID
Unused
Code
00010203
LANCP
➤Task ID Status Subcode
Unused00010203 0405
Status code
STATUS LOG # 5331, REV. D 703
LAN CARD MESSAGES26
26 Open Channel
The Open Channel request is used by an application to initialize a channelwith the LAN card.
27 Open Channel Response
The LAN card returns this CB message as a reponse to the Open Channelrequest.
00 OK.
01 Failed due to resource problem.
Offset Label Field Description
03-04 Service ID 1024 < Service ID <= 65536
05 Service Type 00 = Packet data interface.01 = Streams data interface.
06 Option Flag 00 = No options.01 = Enable TCP keep alive option.
CP➤LAN
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Service ID Option Flag
Service Type
LANCP
➤
00010203 040506
Task ID
Unused
Status Subcode
Status code
704 # 5331, REV. D STATUS LOG
LAN CARD MESSAGES 28
28 Read Data
The CP sends this CB message to request DMA from the LAN card.
29 Read Data Ready
The LAN card sends this CB message to the CP after setting up the DMArequested by the CP with the Read Data request..
00 OK.
01 Invalid request.
02 Invalid size.
03 No available buffers.
04 Invalid state.
Offset Label Field Description
03-04 Channel ID Socket ID of the connection.
05-06 Data Length Length of the buffer into which DMA will occur.
07-08 Offset Offset within buffer to begin DMA.
09 Flag 01 = Resending request.
CP➤LAN
00010203 04050607 0809
Task ID Channel ID
Data Length
Offset
Flag
Unused
LANCP
➤
Task ID
Unused
Status Subcode
Length of data to transfer
00010203 04050607
Status Code
STATUS LOG # 5331, REV. D 705
LAN CARD MESSAGES2A
2A Read Data Complete
The CP sends this CB message to the LAN card when the DMA is com-plete. When the LAN card receives this message, it can release its buffers.
Offset Label Field Description
03 Status Code 00 = OK.02 = DMA errors.
CP➤LAN
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Status Subcode
Status Code
706 # 5331, REV. D STATUS LOG
LAN CARD MESSAGES 2B
2B Write Data
The CP sends this CB message to request the LAN card to setup for DMA.
2C Write Data Ready
The LAN card sends this CB message to the CP after setting up the DMArequested by the CP with the Write Data request.
00 OK.
01 Invalid request.
02 Invalid DMA size.
03 No available buffers.
04 Invalid state.
Offset Label Field Description
03-04 Channel ID Channel ID of the connection.
05-06 Data Length Length of the buffer into which DMA will occur.
CP➤LAN
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Channel ID
Data Length
LANCP
➤
00010203 0405
Task ID
Unused
Status Subcode
Status Code
STATUS LOG # 5331, REV. D 707
LAN CARD MESSAGES2D
2D Write Data Complete
The LAN card sends this CB message to the CP to let the CP know that itcan release the data buffer.
00 OK.
01 DMA errors.
LANCP
➤
00010203 0405
Task ID
Unused
Status Subcode
Status Code
708 # 5331, REV. D STATUS LOG
LAN CARD MESSAGES 2E
2E Outgoing Connect Request
The CP sends this CB message to the LAN card to request that the LANcard establish an outgoing connection.
2F Outgoing Connection Response
The LAN card sends an Outgoing Connection Response to the CP (inresponse to the Outgoing Connect Request) to let the CP know that therequest to establish an outgoing connection has been made. (When theconnection is actually made, the LAN card will send an unsolicited CB mes-sage of Outgoing Connection Status to notify the CP of the connection.)
00 OK.
01 Failed.
Offset Label Field Description
03-06 IP Address IP Address of node to connect to.
07-08 Port ID Service to request.
CP➤LAN
00010203 04050607 08090A0B 0C0D0E
Task ID IP Address
Unused
Port ID
LANCP
➤
Task ID
Unused
Status Subcode
Channel ID
00010203 04050607
Status Code
STATUS LOG # 5331, REV. D 709
LAN CARD MESSAGES30
30 Outgoing Connection Status
The LAN card sends an Outgoing Connection Status CB message to theCP to notify that the connection, originally requested by the CP, wasaccepted. This is an unsolicited message and requuires no response fromthe CP.
Offset Label Field Description
05 Status Code 00 = Connection established.01 = Connection rejected.
LANCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Channel ID Status Subcode
Status Code
710 # 5331, REV. D STATUS LOG
LAN CARD MESSAGES 31
31 Incoming Connection
The LAN card sends this CB message to the CP to notify the CP of anincoming connection. This is an unsolicited message.
32 Incoming Connection Status
The CP sends this CB message to the LAN card to either accept or rejectthe connection. The connection is that which the LAN card notifies the CPof in an Incoming Connection message.
Offset Label Field Description
05 Status Code 00 = Accept.01 = Reject.
LANCP
➤
00010203 04050607 08090A
Task ID Channel ID IP Address
Unused
Service ID
CP➤LAN
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Channel ID Status Subcode
Status Code
STATUS LOG # 5331, REV. D 711
LAN CARD MESSAGES33
33 Incoming Connection Status Response
The LAN card sends this CB message to the CP (in response to the Incom-ing Connection Status message from the CP) to acknowledge the connec-tion status.
Offset Label Field Description
05 Status Code 00 = OK.
LANCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Channel ID Status Subcode
Status Code
712 # 5331, REV. D STATUS LOG
LAN CARD MESSAGES 34
34 Disconnect Channel
The CP sends this CB message to the LAN card to request a disconnect ofthe connection.
35 Disconnect Channel Response
The LAN card sends this CB message to the CP in response to DisconnectChannel request.
00 OK.
Offset Label Field Description
05-06 Reason Code 0000 = Normal completion of session.0001 = Abnormal completion of session.
CP➤LAN
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Channel ID
Reason Code
LANCP➤
Task ID
Unused
Status Subcode
Channel ID
00010203 04050607
Status Code
STATUS LOG # 5331, REV. D 713
LAN CARD MESSAGES36
rk he
..
ork Service
36 Request Network Service
The CP sends this CB message to the LAN card to request various servicesfrom the LAN card. The type of service is specified in the command subtypefield. If the request requires data that does not fit into the CB message(such as with a Get IP Address Request), then a Write Data Network Ser-vice command must be used to seup a DMA of the data to the LAN cardprior to the use of this command.
01 Ping request.
02 Get IP address.*
*This request requires that the System Name be DMA’d to the LAN card before this request is issued. The Write Data NetwoService CB message (3E) is used to initiate the DMA setup. TSystem Name is a 64-byte ASCII string that is used in the DNS request.
Offset Label Field Description
04-05 Timeout Value Timeout to wait for network response (in seconds)
Offset Label Field Description
04-05 Timeout Value Timeout to wait for DNS response (in seconds).
06-07 Channel ID Channel ID obtained from Write Data Ready Netwrequest (CB message 3E).
CP➤LAN
Task ID
Unused
Timeout Value
IP Address
00010203 04050607 0809
Subtype
Task ID
Unused
Timeout Value
Channel ID
00010203 04050607
Subtype
714 # 5331, REV. D STATUS LOG
LAN CARD MESSAGES 37
37 Request Network Service Response
The LAN card sends this CB message to the CP as a response to RequestNetwork Service. The format varies with the action specified in offset 03 ofthe request message.
Action 01 (Ping Request)
00 OK.
01 Fail.
02 Timeout.
Action 02 (IP Address Request)
00 OK.
01 Fail.
02 Timeout.
03 Invalid request (either timeout on channel after DMA, or no DMA had occured).
LANCP
➤
Task ID Status Subcode
Unused00010203 0405
Status Code
Task ID
Unused
Status Subcode
IP AddressStatus Code
00010203 04050607 0809
STATUS LOG # 5331, REV. D 715
LAN CARD MESSAGES3A
.
3A Data Message In
The LAN card sends this CB message to the CP to notify the CP that thereis an incoming data message. This is an unsolicited message and requiresno response.
3B LAN Session Status
The LAN card sends this CB command to the CP to notify the CP of excep-tion conditions dealing with the session. This is an unsolicited message andrequires no response.
00 Link Closed.
01 Abnormal status. CP to terminate.
Offset Label Field Description
03-04 Channel ID Channel ID of the channel for which data has arrived
05-06 Data Length Length of incoming data.
LANCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Channel ID
Data Length
LANCP
➤
Task ID
Unused
Status Subcode
Channel ID
00010203 04050607
Status Code
716 # 5331, REV. D STATUS LOG
LAN CARD MESSAGES 3C
3C Data Message Out
The LAN card sends this CB message to the CP to notify the CP that it canissue another DMA to the LAN card. This is an unsolicted message andrequires no response.
00 Successful completion.
01 Write failed.
LANCP
➤
Task ID
Unused
Status Subcode
00010203 04050607
Channel IDStatus Code
STATUS LOG # 5331, REV. D 717
LAN CARD MESSAGES3D
rvice com-.
3D Write Data Network Service
The CP sends this CB message to the LAN card to request the LAN card tosetup for the DMA of data required for Request Network Service (CB mes-sage 36H).
3E Write Data Ready Network Service
The LAN card sends this CB message to the CP after setting up the DMArequested by the CP with the Write Data Network Service message.
00 OK.
01 Invalid request.
02 Invalid size.
03 No available buffers.
04 Invalid state.
Offset Label Field Description
04-05 Data Length Length of the buffer to DMA.
Offset Label Field Description
06-07 Channel ID Channel ID to be used in the Request Network Semand, and Read Data Network Service command
CP➤LAN
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Data Length
Subtype
NICCP
➤
Task ID
Unused
Status Subcode
00010203 04050607
Channel IDStatus Code
718 # 5331, REV. D STATUS LOG
LAN CARD MESSAGES 3F
3F Write Data Complete Network Service
The LAN card sends this CB message to let the CP know that it can releasethe data buffer.
00 OK.
01 DMA errors.
LANCP
➤
Task ID Status Subcode
Unused00010203 0405
Status Code
STATUS LOG # 5331, REV. D 719
LAN CARD MESSAGES40
vice CB
40 Read Data Network Service
The CP sends this CB command to request DMA from the LAN card afterfirst sending the Request Network Service CB message, and after receivingthe Request Network Service Response from the LAN card. Only data thatwill not fit in the Request Network Service Response is DMA’d to the CP.
41 Read Data Ready Network Service
The LAN card sends this CB command to let the CP know that the DMA hasbeen set up.
00 OK.
01 Invalid request.
02 Invalid size.
03 No available buffers.
04 Invalid state.
Offset Label Field Description
03-04 Channel ID Channel ID from the Write Data Ready Network Sermessage (3E).
05-06 Data Length Length of the buffer into which DMA will occur.
Offset Label Field Description
06-07 Length Actual length of data to transfer.
CP➤LAN
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Channel ID
Data Length
LANCP
➤
Task ID
Unused
Status Subcode
00010203 04050607
LengthStatus Code
720 # 5331, REV. D STATUS LOG
LAN CARD MESSAGES 42
ervice CB
42 Read Data Complete Network Service
The CP sends this CB message to the LAN card when DMA is complete.After receiving this message, the LAN card can release its buffers.
00 OK.
01 DMA errors.
Offset Label Field Description
06-07 Channel ID Channel ID from the Write Data Ready Network Smessage (3E).
CP➤LAN
Task ID
Unused
Status Subcode
Channel ID
00010203 04050607
Status Code
STATUS LOG # 5331, REV. D 721
LAN CARD MESSAGES43
43 Write Initial Configuration
The CP uses this CB message to send the LAN card’s IP Address and sub-net mask to the LAN card. These items are broken out because they needto be sent to the LAN card before the rest of the information that is sent withWrite Data Configuration.
44 Write Initial Configuration Response
The LAN card sends this CB message to the CP in response to the WriteInitital Configuration request.
00 OK.
CP➤LAN
00010203 04050607 08090A0B 0C0D0E
Task ID IP Address
Unused
Subnet mask
LANCP
➤
Task ID Status Subcode
Unused00010203 0405
Status code
722 # 5331, REV. D STATUS LOG
LAN CARD MESSAGES 45
45 Write Data Configuration
The CP sends this CB message to request the LAN card to setup for theDMA of configuration data.
46 Write Data Ready Configuration
The LAN card sends this CB message to the CP after setting up the DMArequested by the CP with the Write Data Configuration.
00 OK.
01 Invalid request.
02 Invalid size.
03 No available buffers.
04 Invalid state.
Offset Label Field Description
03-04 Data Length Length of the buffer to DMA into.
CP➤LAN
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Data Length
LANCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Status Subcode
Status Code
STATUS LOG # 5331, REV. D 723
LAN CARD MESSAGES47
47 Write Data Complete Configuration
The LAN card send this CB message to the CP to let the CP know that itcan release the data buffer.
00 OK.
01 DMA errors.
LANCP
➤
Task ID Status Subcode
Unused00010203 0405
Status Code
724 # 5331, REV. D STATUS LOG
LAN CARD MESSAGES 48
ived.
48 SNMP Notification
The LAN card sends this CB message to notify the CP that there is anincoming SNMP request. This is an unsolicited message, and requires noresponse.
Offset Label Field Description
03-04 Channel ID Channel ID of the channel on which the data has arr
05-06 Data Length Length of incoming data.
LANCP
➤
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Channel ID
Data Length
STATUS LOG # 5331, REV. D 725
LAN CARD MESSAGES49
49 Read Trace Buffer
The CP sends this CB message to the LAN card.
4A Read Trace Buffer Response
The LAN card sends this CB message to the CP in response to the ReadTrace Buffer request.
00 OK.
01 Trace is not available.
Offset Label Field Description
03-04 Buffer Type 0 = Read LAN card trace buffer.1 = Read gateway trace buffer.2 = Read DNS trace buffer.3 = Read profiling buffer.
CP➤LAN
Task ID
Unused
Buffer Type
00010203
LANCP➤
Task IDLength of trace buffer
Unused00010203 0405
Status Code
726 # 5331, REV. D STATUS LOG
LAN CARD MESSAGES 4B
4B Read Error Log
The CP sends this CB message to the LAN card.
4C Read Error Log Response
The LAN card sends this CB message to the CP in response to the ReadError Log request.
00 OK.
01 Error log is not available.
CP➤LAN
Task ID
Unused000102
LANCP
➤
Task IDLength of error log
Unused00010203 0405
Status Code
STATUS LOG # 5331, REV. D 727
LAN CARD MESSAGES4D
4D Set Time of Day
The CP sends this CB message to the LAN card.
4E Set Time of Day Response
The LAN card sends this CB message in response to the Set Time of Dayrequest.
00 OK.
01 Failed to set real time clock.
CP➤LAN
00010203 04050607 0809
Task ID Month
Day of Month
Year
Hour
Unused
Second
Minute
LANCP
➤
Task ID
Unused00010203
Status Code
728 # 5331, REV. D STATUS LOG
LAN CARD MESSAGES 4F
.
4F Set Task Trace
The CP sends this CB message to the LAN card.
Offset Label Field Description
03 Trace Switch 0 = Off.1 = On.2 = Turn off LAN card profile.3 = Turn on LAN card profile.4 = Clear LAN card profile.
04-07 Trace Type 0xFFFFFFFF = Set all LAN card traces.0x00000001 = Set ISR trace.0x00000002 = Set network trace.0x00000008 = Set SBI/OPI trace.0x00010000 = Set session manager trace.0x00020000 = Set control bus trace.0x00040000 = Set data manager trace.0x00080000 = Set provision trace.0x00100000 = Set task manager trace.0x00200000 = Set domain name server trace.0x00400000 = Set SNMP trace.0x00800000 = Set listen task trace.0x01000000 = Set gateway task trace.0x04000000 = Set interrupt trace.0x10000000 = Set resource manager trace.0x20000000 = Set resource manager buffer trace
CP➤LAN
00010203 04050607 08090A0B 0C0D0E0F
Task ID
Unused
Trace Type
Trace Switch
STATUS LOG # 5331, REV. D 729
LAN CARD MESSAGES50
50 Set Task Trace Response
The LAN card sends this CB message in response to the Set Task Tracerequest.
00 OK.
01 Failed to set real time clock.
LANCP
➤
Task ID
Unused00010203
Return Code
730 # 5331, REV. D STATUS LOG
APPENDIX: OTHER CODES
This appendix describes a variety of codes that, while not appearing in thestatus log, are helpful in troubleshooting:
• ASCII code set
• Hex/binary conversion
• Drive test status codes
• Test ID numbers of the start-up diagnostics
• IPL/PIPL codes
STATUS LOG # 5331, REV. D 731
OTHER CODES
aracter
h
i
j
k
l
m
n
o
p
q
r
s
t
u
v
w
x
y
z
{
|
}
~
A.1 STANDARD ASCII CODE SET
Codes 00 to 1F and 7F represent special control characters that are notprintable.
A-1. ASCII Code Set
ASCII Code
CharacterASCII Code
CharacterASCII Code
CharacterASCII Code
Ch
20 blank 38 8 50 P 68
21 ! 39 9 51 Q 69
22 “ 3A : 52 R 6A
23 # 3B ; 53 S 6B
24 $ 3C < 54 T 6C
25 % 3D = 55 U 6D
26 & 3E > 56 V 6E
27 ‘ 3F ? 57 W 6F
28 ( 40 @ 58 X 70
29 ) 41 A 59 Y 71
2A * 42 B 5A Z 72
2B + 43 C 5B [ 73
2C , 44 D 5C \ 74
2D - 45 E 5D ] 75
2E . 46 F 5E ^ 76
2F / 47 G 5F _ 77
30 0 48 H 60 ‘ 78
31 1 49 I 61 a 79
32 2 4A J 62 b 7A
33 3 4B K 63 c 7B
34 4 4C L 64 d 7C
35 5 4D M 65 e 7D
36 6 4E N 66 f 7E
37 7 4F O 67 g
732 # 5331, REV. D STATUS LOG
OTHER CODES
A.2 HEX/BINARY CONVERSION TABLE
A.3 DRIVE TEST STATUS CODES
These codes are reported during the drive test utility.
Table A-2. Hex/Binary Conversion
Hex Binary
0 00001 00012 00103 0011
4 01005 01016 01107 0111
8 10009 1001A 1010B 1011
C 1100D 1101E 1110F 1111
Table A-3. Drive Test Status Codes
Status Description
F0 Invalid response to drive test messageF1 Soft error status returnedF2 Hard error status returnedF3 ECC soft error
STATUS LOG # 5331, REV. D 733
OTHER CODES
A.4 START-UP DIAGNOSTICS
When the system starts up it runs a set of diagnostics. These tests are dis-played on the monitor as they are run along with whether they passed orfailed. These results are not entered in the status log. Systems run onlythose tests appropriate to the configuration and in the order appropriate tothe configuration. Not running a specific test or running tests out of numeri-cal order are not failures.
Following is a list of the test ID numbers and a brief description of the test.
Table A-4. Start-Up Diagnostics
ID # Description
00 Display self-test status01 Watchdog timer02 Dynamic RAM address/data03 Dynamic RAM data uniqueness
04 CPU cache RAM uniqueness05 CPU cache RAM address stress06 System control registers07 Dynamic RAM parity good
08 Dynamic RAM parity forced bad09 Execute from dynamic RAM0A Test DRAM executing from DRAM0B 82370/380 DMA byte transfer
0C 82370/380 DMA block transfer0D SBI controller RAM0E SBI controller loopback0F SBI controller threshold
10 SBI controller<->RAM DMA11 8530 SCC DMA with loopback12 Inter-card SBI DMA communications13 Drive autoconfigure
14 Recalibrate all drives15 Read bad track list on all drives16 Validate diagnostic cylinders on all drives17 Format track 0 on all drives
18 Format all tracks on all drives19 Seek to all tracks on all drives
734 # 5331, REV. D STATUS LOG
OTHER CODES
1A Verify Sector IDs on all drives1B Write/verify track 0 on all drives
1C Write/verify tracks on all drives1D PCM ASIC registers1E PCM ASIC intra-card1F 7132/42 dual port RAM
20 TI C25 DSP21 Non-volatile serial RAM22 SBI inter-card buffer echo23 SBI inter-card ping-pong
24 SBI inter-card termination2C ACP dual port RAM tests2D ACP SCC2698 octal-UART test2E ACP 80188 cell test2F Write/verify miscellaneous registers
32 DRAM 3-partition doubleword test33 DRAM walking 1s doubleword test36 DRAM data march tests37 DRAM parity good
38 DRAM parity forced bad39 30-second timer test
Table A-4. Start-Up Diagnostics (Continued)
ID # Description
STATUS LOG # 5331, REV. D 735
OTHER CODES
A.5 IPL/PIPL STATUS CODES
The following codes may be reported by IPL (Overture 350) or PIPL (Over-ture 250) systems. They will normally be reported as:
FATAL ERROR x
and the system will reboot.
The most common errors reported will be codes 1, 2 and 22. For releasedboards these will normally be hardware problems (bad or missing boards
Table A-5. IPL/PIPL Status Codes
Status(decimal)
Description
1 Time-out on CB card ready2 Time-out on CB card response3 Checksum error on CB packet4 Error code in received CB packet
5 Wrong response code in packet6 Time-out on DB transfer7 Checksum error on DB transfer8 Data error on download receive9 Memory block compare error
14 Error during card probe19 SST failed validity check
22 No primary file card configured24 Error handling termcap table25 No message file card28 Slave responds with a NAK because the previous CB
message sent was either incorrect or it was damaged in shipment.
29 DMA errors
30 CRC error in last control packet sent by master31 CRC error in last control packet received by the master32 SBI receives DMA data with CRC errors35 DLC could not find any TIC38 DMA Data FIFO overrun39 DMA Data FIFO underrun
40 Invalid card ID43 Invalid software alarm44 Disk error45 S/W image checksum error
736 # 5331, REV. D STATUS LOG
OTHER CODES
etc.). However if new boards are being tested especially with updated(faster) processors then the problem may more likely be software. Both IPL& PIPL use processor loops for time-outs so a change of processor mayeffect system card synchronization.
If the problem is with a file card the system will restart. In general for a linecard the system will attempt to complete the boot process. IPL loads the350 line cards, for the 250 the line TIC cards are downloaded by the OSlater in the boot sequence. With Aria 1.20 PIPL will download updated diag-nostics to all cards in the system.
For CB in/out printouts use the appropriate control bus description fromChapters 3-6.
For SCSI drive test results use the Service Manual description. Test resultsare returned from the file card as an ASCII text buffer which is simply outputto the terminal.
STATUS LOG # 5331, REV. D 737
GLOSSARY
Symbols and Numbers
>. 1. The end-of-entry character displayed as an ASCII character. 2. Com-mand prompt in Debug.
250. See Octel Overture 250.
350. See Octel Overture 350.
3E. The end-of-entry character displayed as a hexadecimal number.
A
ACP. (Asynchronous Communications Processor) 1. Application supportingcommunication with PBXs or Centrex switches, and with multiple systemmanager terminals. 2. Card that supports the ACP application by providingRS-232 ports, and translating and rerouting the information packets.
Aria. The Octel Aria™ user interface software for the Octel Overture 250and 350 message servers. Aria 1.0 was previously known as GBS SoftwareRelease 5.0.
ASCII. (American Standard Code for Information Interchange) Standardmethod of coding letters, numbers, punctuation and other characters inbinary. Each ASCII code is one byte long.
B
Bank. Part of the peripheral address, the low-order 4-bits of offset 05 of theIORB header identifies which set of slots the CP is exchanging control busmessages with. To interpret the bank value, see Table 1-8, “Bank and Slotof the Peripheral Address,” on page 30.
Binary. Base-2 numbering system. Each digit in a binary number is limitedto values 0 and 1, and is worth twice as much as the digit before it. Forexample, the binary number 1011 translates to the usual decimal form by:
Since binary numbers can be represented by switches turned on or off,binary is the natural system for digital computers. A binary digit equals onebit, four binary digits equal one hexadecimal digit and eight binary digitsequal one byte. Convert between binary and hexadecimal numbers withTable A-2, “Hex/Binary Conversion,” on page 723.
1011
1 ✕ 20 = 11 ✕ 21 = 20 ✕ 22 = 01 ✕ 23 = 8
11 (in decimal, or base-10, numbering)
STATUS LOG # 5331, REV. D 739
GLOSSARY
Bit. The smallest unit of data, equal to one binary digit.
Byte. Group of eight bits, the most common unit of measurement for dataand memory space in a digital computer. Byte-sized data is usually dis-played as either two hexadecimal digits or one ASCII character.
C
CB. See Control bus.
CB-in message. Control bus message going into the CP from anothercard. This is usually the response to the accompanying CB-out messageand has the same three-byte header.
CB-out message. Control bus message going out from the CP to anothercard. This is usually a request for some action by the other card.
CCF. (Combo CP and File card) Provides similar functions as the CP andfile cards while occupying only one slot. The CCF still uses the file systemcontrol bus messages, even though the file card portion is not acually onthe control bus.
Channel. Part of the peripheral address, the high-order 4-bits of offset 04 ofthe IORB header identifies which line card port the CP is exchanging controlbus messages with. Interpret the channel value with Table 1-9, “Channel ofthe Peripheral Address,” on page 31.
Checksum. A standard error-detection technique for messages. Both thesender and the receiver add up the values in a message. If the sums do notmatch, there has been an error in transmission. The system responds bytrying to send the message again.
Control bus. (CB) Data and instruction path connecting the CP to the otherparts of the message server. Requests are sent from the CP and responsesreceived by it in the form of control bus messages.
Control bus message. Carries instructions and data between the CP andother parts of the message server using a 16-byte format:
The messages always appear in the status log as request/response pairs.For more information, see Section 1.5.3, “Control Bus Messages,” onpage 35. The message types are described in Chapters 3-6.
0100 11107 0
One byte is an 8-bit field.
Bit count
4E N
Displayed as:
Hex ASCII
➠
000102
Task IDMessage
Peripheral
Packet Data
address
type
740 # 5331, REV. D STATUS LOG
GLOSSARY
CP. (Central Processor card) The master processor in the message server.The CP runs the operating system and applications software, directing theoperations of the rest of the system through the control bus.
D
Data structure. A collection of data fields with a defined organization.While the locations of fields within a structure are fixed relative to eachother, the structure as a whole can be moved and repeated. Data structurescan be nested within other data structures. For example, the entry header isa data structure within a status log entry, which is a data structure within thestatus log which is also a data structure.
Disk utilities. Allow reading and writing the disk drives of the messageservers. They are part of the system utilities available at the ENTER BOOTCOMMAND: prompt. The service option must be activated first. For instruc-tions in reading the status log with the disk utilities, see Section 1.3.3, “Dis-play from Disk Utilities,” on page 12.
DLC. (Digital Line Card) 1. Any of several line cards that process telephonesignals with software instead of hardware. 2. One specific type of digital linecard.
Dump. A record of the message server’s recent operations that is printedout as part of a system shutdown. For instructions in reading the status logfrom the dump, see Section 1.3.5, “Display from Dump,” on page 16.
E
End-of-entry character. A byte-sized code used to separate entries in thestatus log: 3E (> in ASCII). This character is also permanently located at off-set 05 of the status log to separate the status log header from the entries.
English status code. A simple, English description of a status log entry.The English status code is based entirely on the status code in offset 04-05and so is only the beginning of interpreting the entry. However, the Englishstatus code may be enough to decide if further interpretation is needed. TheEnglish status code is available only when the status log is displayed withMenu 13.2, Menu 13.3 or Menu 20’s Display Status Log option.
Entry. A collection of data about an event that is recorded in the status log.While the format of entries varies depending on the status codes and sub-codes, all entries start with a 16-byte entry header and are from 16 to 255bytes long. Because of the space limit, a few events with very extensivedescriptions use two or three consecutive entries. Entry formats aredescribed in Chapter Two.
STATUS LOG # 5331, REV. D 741
GLOSSARY
Entry header. The first 16 bytes of every status log entry holds standarddata in the following format:
This is officially known as the error control block common header. For moreinformation, see Section 1.5.1, “Entry Header,” on page 22.
Error control block common header. See Entry header.
Event. Any occurrence that logs a status log entry.
F
Field. A specified part of a data structure that holds a particular kind of data.The illustrations identify a field by boxing and labelling it:
Whether the label is inside or outside the box is just a matter of conve-nience. The value shown in the field is the offset of that byte, not any kind ofsample data.
Field group. The fields of status log entries can usually be groupedtogether logically. In the illustrations, these groups are labelled on the right:
There are four standard groups: entry header, IORB header and control busmessage. There is also one commonly occurring group that does not havea standard format: registers during event. For more information, seeSection 1.5, “STANDARD FIELD GROUPS,” on page 21.
File. A portion of the disk drives. The file numbers and contents are listed inSection 3.2.3, “File Numbers,” on page 514.
File card. Manages storing and retrieving data on the message server’sdisk drives.
Flag. 1. A single bit used to indicate whether or not a certain thing has hap-pened or a certain condition exists. Usually the flag bit starts with zero andis set to one (the flag is raised) when the thing or condition happens. A
00010203 04050607 08090A0B 0C0D0E0F
Entrylength
Flags
Task ID
Severitycode
Statuscode
Device
Subcode
Time stamp CountID
00010 10111213 14151617IP
Boot character
Scanner input message
Registers during event AX IP CS
Task ID
00000 00010203 04050607 08090A0B 0C0D0E0F Entry header
00020
Messagetype & Port 00010 10111213 14151617 18191A1B 1C1D1E1F
Field group labels
742 # 5331, REV. D STATUS LOG
GLOSSARY
larger field (one or two bytes, for instance) can have several flags in it orjust one. These fields can be read by converting them to binary or by identi-fying the hex numbers that add up to the field’s value. For example, 06 isthe sum of 02 (bit 1 set) and 04 (bit 2 set). 2. A field containing nothing butone flag bit (usually the lowest-order bit, bit 0). The flag bit can be checkedby checking the whole field. There is no need to convert to binary and sepa-rate the bits:
FS. (File System) Portion of a message server including disk drives and theassociated file card.
H
Header. A data structure that is always placed at the beginning of anotherdata structure. Headers hold data that are always (or at least often) neededin the larger structure.
Hex. See Hexadecimal.
Hexadecimal. Base-16 numbering system. Each digit can have valuesfrom 0 to 15, using digits 0-9 and then A (10), B (11), C (12), D (13), E (14)and F (15). Each hexadecimal digit is worth 16 times as much as the digitbefore it. For example, the hexadecimal number 012C translates to theusual decimal form by:
A hexadecimal digit equals four bits and two hexadecimal digits equal onebyte. Hexadecimal is the most popular way of displaying binary databecause it converts so easily with bits and bytes while keeping the numberof symbols at a manageable level. Convert between binary and hexadeci-mal numbers with Table A-2, “Hex/Binary Conversion,” on page 723.
I
Input/output request block. (IORB) A data structure that holds informationabout an exchange of control bus messages. The IORB consists of theIORB header followed by the CB-out message and the CB-in message.
Intel order. The most-significant byte of a field displayed at the right andthe least-significant byte at the left, the opposite of the normal ordering ofdigits in a number. This is a side-effect of the way the Intel microprocessoroperates. These values need to be transposed before they are interpreted.
0000 000X7 0
Flag bit in a 1-byte flag field
001 Flag lowered
01 Flag raised
012C
12 ✕ 160 = 122 ✕ 161 = 321 ✕ 162 = 2560 ✕ 163 = 0
300 (in decimal, or base-10, numbering)
STATUS LOG # 5331, REV. D 743
GLOSSARY
IORB header. (Input/Output Request Block header) A data structure thatsupplies standard information about an exchange of control bus messages:
For more information, see Section 1.5.2, “IORB Header,” on page 28.
K
Key field. A field with data that is frequently referred to. It should be one ofthe first fields checked when interpreting a data structure. In the illustra-tions, key fields are shaded:
L
LC. See Line card.
Line card. (LC) Any of several cards that analyze and process telephonesignals coming into or going out of the message server.
Line TIC. Combination line card and telephone interface card.
Log. 1. See Status log. 2. The act of adding an entry to the status log.
M
Main Menu. The first screen displayed on the system manager terminalafter the correct password has been entered. The Main Menu is a directoryfor all terminal-based system-management functions.
Menu 13. The System Maintenance menu offers several functions dealingwith the status of system operations. It is reached by entering 13 in the MainMenu. For instructions in reading the status log with Menu 13, seeSection 1.3.1, “Display from Menu 13,” on page 8 and Section 1.3.5, “Dis-play from Dump,” on page 16.
Menu 13.1. (Shut Down with Dump) Shuts down the message server andprints a dump of recent system activities, including the status log. It isreached by entering 1 in Menu 13. For instructions in reading the status logwith Menu 13.1, see Section 1.3.5, “Display from Dump,” on page 16.
00010203 04050607 08090A0B 0C0D0E0F10111213 14151617 18191A1B
Initialevent
Peripheraladdress
Terminal mode
Function
EventStatuscode
Data transfercount
Data transferaddress
Priority Time-out
Unused
period, in ms
00010 10111213 14151617IP
Boot character
744 # 5331, REV. D STATUS LOG
GLOSSARY
Menu 13.2. (Review Status Log) Displays the status log and an inventory ofthe message server’s software. Menu 13.2 is the easiest way to read thestatus log because the entries are separated from each other, ordered fromoldest to newest, and partially translated. Menu 13.2 also supports printingand clearing the status log. It is reached by entering 2 in Menu 13. Forinstructions in reading the status log with Menu 13.2, see Section 1.3.1,“Display from Menu 13,” on page 8.
Menu 13.3. (Scroll Status Log) Displays status log entries as they arelogged. Menu 13.3 is used to watch the status log while the system oper-ates. It is reached by entering 3 in Menu 13. For instructions in reading thestatus log with Menu 13.3, see Section 1.3.1, “Display from Menu 13,” onpage 8.
Message server. Equipment designed primarily for processing voice infor-mation, including: Octel Overture 250 and 350.
Message type. Field in a control bus message indicating the meaning ofthe message and how to interpret its packet data. The field is in offset 03and the messages types are described in Chapters 3-6.
N
Non-printable character. ASCII code that does not correspond to any ofthe standard characters on the system manager terminal or printer: 00-1Fand 7F-FF. In ASCII displays, non-printable characters are shown as peri-ods.
O
Octel Overture 250. Octel Overture™ 250 message server.
Octel Overture 350. Octel Overture™ 350 message server. Previouslyknown as Octel XC1000.
Offset. A count of bytes from the beginning of some data structure. The off-set is used to identify the location of a field. The count begins with zero andis always given as a hexadecimal number. Since the offset value dependson where the count begins, it is very important to be clear on which datastructure is being referred to. In the figures, the values shown are the off-sets of each byte, instead of real data.
Offset of next entry. Pointer to where the next entry will go. Located at off-set 02-03 of the status log, the value is an offset within the status log. Theoffset of the next entry can also be thought of as the end of the ring bufferand as a pointer to the most recent entry. The most recent entry is the onepreceding this point.
Offset of oldest entry. Pointer to where the oldest entry is. Located at off-set 00-01 of the status log, the value is an offset within the status log. Thisvalue is always 06 unless the status log has overflowed and wrappedaround. Then it will point to somewhere above the offset of the next entry.The offset of the oldest entry can also be thought of as the beginning of thering buffer.
STATUS LOG # 5331, REV. D 745
GLOSSARY
Overflow. Entries exceeding the space in the status log. After this happens,new entries are written over the oldest entries.
Overflow flag. Located at offset 04 of the status log, it indicates whether ornot the status log has overflowed. Zero is the normal condition; 01 indicatesoverflow.
Overwrite. To write new data in memory space that already has data in it.The old data is erased in the process. This happens when the status logoverflows: new entries overwrite old ones and the old entries are lost.
P
Packet data. The data carried by a control bus message. The format of thedata depends on the message type. The packet data is 10 bytes long andthe formats are described in Chapters Three-Six.
Peripheral address. Identifies the card that the CP was communicatingwith through control bus messages. The peripheral address is located in off-set 04-05 of the IORB header. Offset 04 is duplicated in offset 01 of the con-trol bus message. The peripheral is identified in terms of a bank, slot andchannel:
Translate the peripheral address with Table 1-8, “Bank and Slot of thePeripheral Address,” on page 30 and Table 1-9, “Channel of the PeripheralAddress,” on page 31.
Pointer. A field that points to another location in memory. The field usuallyholds the offset of the location within a data structure. Alternatively, the fieldcan hold the distance (number of bytes) from the pointer to the other loca-tion or the actual address of the other location.
Port. A connection for a communication channel into the message server,usually for one of the telephone lines.
R
Record 50. A file holding a copy of the message server’s most recent oper-ations, similar to that produced by the shutdown dump. However, Record50 is only updated during a system crash. Record 50 is located in file 2D.For instructions in reading the status log from Record 50, see Section 1.3,“DISPLAYING THE STATUS LOG,” on page 7.
00010203 04050607 08090A0B 0C0D0E0F10111213 14151617 18191A1B 1C1D1E1F
Peripheraladdress
0405BankChannel Slot
746 # 5331, REV. D STATUS LOG
GLOSSARY
Wraparoundon overflow
Register. A special-purpose memory space in a processor. Uses of regis-ters include: holding values for a calculation, flags defining the state of theprocessor, pointer to the current instruction and pointers to special memoryspaces.
Registers during event. A group of fields in many status log entries hold-ing selected values from the registers of the CP’s microprocessor. The val-ues are used for high-level troubleshooting.
Request message. See CB-out message.
Response message. See CB-in message.
Return code. Code showing the result of an operation. Control busresponse messages usually have a return code in offset 03. Control busmessages are described in Chapters Three-Six.
Ring buffer. A memory space operated so that when entries overflow thetop of the space, they continue being written at the bottom, working theirway up again:
In this process, the oldest entries are sacrificed to make room for the new-est. Ring buffers normally have a beginning (where the oldest entry is) andan end (where the next entry will go). The status log is operated as a ringbuffer.
S
Service option. Allows use of the system utilities and Debug on the mes-sage servers. The service option can only be activated by an Octel Commu-nications Response Center using remote system access.
Oldest entry
Next entry
Oldest entry
Next entry
New entrieswritten overold entries
BEFORE OVERFLOW AFTER OVERFLOW
Unusedspace
STATUS LOG # 5331, REV. D 747
GLOSSARY
Shutdown. Process of “gracefully” stopping the message server’s func-tions. Current operations are finished and databases are updated. Newoperations are not allowed to start. The system also does a dump ofrecords of recent operations, including the status log. A shutdown is donewith Menu 13.1. For instructions, see Section 1.3.5, “Display from Dump,”on page 16.
Sierra. Octel Sierra™ message server.
Slot. A part of the peripheral address, the slot value indicates the cardwithin a bank. Slot is in bits 0-3 of offset 04 of the IORB header. Translatethe slot value with Table 1-8, “Bank and Slot of the Peripheral Address,” onpage 30.
SST. See System status table.
Status code. 1. Identifies the event or class of events that logged the statuslog entry. Located in offset 04-05 of the entry header. The status codes aredescribed in Chapter Two. 2. See English status code. 3. Field in offset0C-0D of the IORB header. The meaning depends on the kind of operationthat was involved. Translate the IORB’s status code with Table 1-10, “IORBFunction and Status Codes,” on page 33.
Status log. A running record of exceptional events occurring throughout themessage server. The status log is a key troubleshooting tool. For moreinformation, see Section 1.1, “OVERVIEW OF THE STATUS LOG,” onpage 1.
Subcode. When used, it identifies the event that logged the status logentry. The subcode works as an extension of the status code, giving morespecific information. It is in offset 08-09 of the entry header. The subcodesare described in Chapter Two under their status codes.
System manager. Person responsible for operating and maintaining themessage server.
System manager terminal. Terminal the system manager uses to monitorand control the message server.
System status table. (SST) Holds data concerning the system configura-tion and system-level activities, including the status log. For instructions inusing the SST, see Section 1.3, “DISPLAYING THE STATUS LOG,” onpage 7.
T
Task ID. Identifies a software task. Task IDs for line tasks also indicate aparticular port. Task IDs are found in:
• Offset 02 of entry headers, identifying the task that generated orfound the status event.
• Offset 00 of control bus messages, identifying the task that pro-duced the request message.
Translate the task ID with Table 1-5, “Task IDs,” on page 24; and Table 1-6,“Task ID to Port,” on page 25.
748 # 5331, REV. D STATUS LOG
GLOSSARY
Time stamp. 1. Generally, a field recording when something happened. Inthe message servers, time stamps are usually coded as the number of min-utes since 12:01 AM January 1, 1984 (the beginning of the “Octel era”). Addi-tional space may be used for the number of seconds within the minute andfractions of a second within the second. 2. In an entry header, the timestamp records when the entry was logged. Offset 0B-OD holds the count ofminutes and offset 0A holds the count of seconds. For instructions in decod-ing the time stamp, see “Reading the Time Stamp” on page 26.
Transpose. To convert Intel-ordered data to normal, numerical order.Transposing is done by reversing the order of the bytes:
Transposing must be done with full bytes, not individual hexadecimal dig-its.
V
Voice processor. See Message server.
W
Wraparound. What happens when a ring buffer overflows: the buffer con-tinues writing at the bottom of its memory space, overwriting old entries as itworks upward again.
X
XC1000. See Octel Overture 350.
76 54 32 10
10 32 54 76
STATUS LOG # 5331, REV. D 749
STATUS LOG
Index
Numerics00 Boot Reason and Time, 4401 Failed SST Validity Check During
Boot Process, 4502 Scanner Wrong Incoming Message, 4503 Scanner No Carrier After Ring, 4604 RS-232 Integration Link Reset, 4605 Status Log Cleared, 4706 Error During Garbage Collect, 4707 SMT Internal Error, 4708 SMT Software Alarms Cleared, 4709 Software Download Utility Error, 480A SMT Invalid User Record Lock State, 480B SMT File System I/O Error, 480C SMT-Related OCL Error, 490D SMT-Related File Management
Error, 500E SMT-Related X.25 Line Error, 520F File Creation Informational Entry, 5410 SMT-Related AMIS Internal Error, 55100 CDR RAM Buffer Overflowed, 274101 CDR Disk Write Error, 275102 Short Message Service (SMS)
Error, 276104 LAN Router Task Non-Service
Errors, 277105 LAN Router Task Service Error, 278106 LAN API Error, 279107 CP/LAN Protocol Out of Sequence, 289108 LAN Timeout, 290
11 Error During Upgrade Performed by SMT, 55
110 Control Bus Error in Getting New IUN, 291
111 No IUN Available, 291112 Error Reading MDS Record, 292113 MDS-Record Validity Check
Error, 292114 Error Writing MDS Record, 293115 Error in AMT Search for MDS, 293116 MDS File Validity Check Error, 29311B Fax Queue Error, 29412 SMT Could Not Get a New User
Record, 57120 DMD Entry Read Error, 297121 DMD Entry Write Error, 29813 SMT Could Not Find the ICN in the
AMT, 57130 SBP/SCSI Security Checksum
Bad, 299131 SBP/SCSI Configuration Checksum
Revalidate, 301132 SBP Internal Error, 30214 IRN Usage Report, 58141 System Backup and Recovery (SBR)
General Error, 303148 RMM General Error Code, 31315 MDS File Creation Problem, 58150 MDS File Access Failure for Port
Testing, 315
IN-751
Status Log Interpretation Guide
6n
151 Possible Bad Port(s) Found during Port Testing-NSA, 316
152 Possible Bad Port(s) Found during Port Testing-SA, 316
154 CDR Review Utility Error, 317155 CIP MDS File Error, 317156 NWPL MDS Access Error, 319157 NER MDS Access Error, 321158 NER Memory Access Error, 32216 LAN Initialization Failed, 58164 Digital Networking Internal Error, 323165 Digital Networking Connect Retries
Exhausted, 32717 IP Address Netmask Not Sent, 5818 Error Sending Configuration Update to
LAN Card, 5819 Scanner Task Internal Error, 591A Scanner Task Protocol Error, 591B Scanner Task Message Waiting
Error, 601C Message Waiting, Illegal Extension, 621C0 OPI SP Error, 3281C1 OPI LP Error, 3291C2 OPI Arbitration Master Error, 3291D Error Counters Reported by Scanner, 631E Error Information from PID, 641E0 Network Directory Error, 3301E1 Network Directory Input/Output
Error, 3341E2 Number of Network Directory Entries
Exceeds Critical Space Threshold, 3341E3 Number of Network Directory Entries
Exceeds Directory Full Alarm Threshold, 336
1E4 Network Directory Full, 3361E5 Aspenet Admin Protocol Error, 3371E6 EDBN Administrative Message
Status, 3381E7 EDBN Network Directory Access
Error, 3391E8 Debug Logs Snapshot, 3411F RS-232 Link Down, 731FC Local Lock Error, 3421FF Protocol Out of Sequence, 34320 SMDI Internal Error, 7421 SMDI Protocol Error, 75
22 Internal Error in the X-Interface Code, 76228 Background Task Error, 34523 Internal Error in the OCL Interface
Code, 8424 EAP-Related Error, 8525 Error in the OCL System Utility
Routine, 9026 Internal Error Occurred During IVR
Application, 9127 Internal Error Occurred During ASA
Application, 9328 Internal Error in the OCL Task, 9429 Internal Error in the Router Code, 992E Debug Messages in X.2, 1012F OCL Debug Error, 10230 SP-Related OCL Error, 10331 Task Loop, 10432 Task Locked Out, 10433 Fatal Inconsistency in the OS, 10534 Fatal Inconsistency for Requestor in
Application Task, 10535 Control Bus Error—Minor, 10536 Control Bus Error—Major, 10537 Control Bus Error—Indeterminate, 10538 Privilege Violation Interrupt, 10539 Spurious Interrupt, 1053A Data Bus Error—Unsolicited Device
Interrupt, 1053B Data Bus Error—Unsolicited Software
Timer Interrupt, 1053C Data Bus Error—Device Time-out, 1053D DMA Error—Unsolicited Device
Interrupt, 1053E DMA Error—Unsolicited Software Timer
Interrupt, 1053F DMA Error—Device Time-out, 10540 Scanner Card Error—Minor, 10641 Scanner Card Error—Major, 10642 Scanner Card Error—Indeterminate, 1043 System Manager I/O Error (Transmissio
Error), 10644 DUART-0 Spurious Device
Interrupt, 10645 Scanner Card Error—Acknowledgment
Bad Channel, 106
IN-752 STATUS LOG
Index
4
344
3
46 Scanner Card Error—Acknowledgment Not Expected, 106
47 Scanner Card Error—Bad Checksum, 107
48 Scanner Card Error—Transmit Time-out, 108
49 Scanner Card Error—Transmit Time-out Maximum, 108
4A Scanner Card Error—Duo Errors, 1094B Scanner Card Error—Parity Error, 1094C Scanner Card Error, 1104D ACP-Related Error, 1104E PIPL Flash Upgrade Error, 11250 Control Bus Error—Checksum
Error, 11351 Control Bus Error—Checksum Errors
Exceeded Limit, 11552 Control Bus Error—Checksum-Nak On
Response, 11553 Control Bus Error—Checksum-Nak On
Transmission, 11554 Control Bus Error—Checksum-Naks
Exceeded Limit, 11655 Control Bus Error—Invalid Channel
Reference, 11756 Control Bus Error—Empty Control Bus
Slot, 11757 Control Bus Error—Reset
Peripheral, 11858 Control Bus Error—Transmit Error, 11859 SBI DMA FIFO Underrun, 1185A SBI DMA FIFO Overrun, 1185B SBI Failed to Cycle in Control Bus Input
Read, 1195C SBI Failed to Cycle in Control Bus Output
Write, 1195D Soft Reset of Control Bus
Peripheral, 1195E SBI DMA CRC Error, 1195F X.25 Task Crashed, 12060 Logic Card Status, 12261 Incomplete Standby Redundant Card
Set, 12462 Invalid Leading Digit Dialed for
Automated Attendant Transfer, 12463 Channel Reset Was Successful, 125
64 FS/CP Software Error, 12565 LC Protocol Error, 12666 Line Task Internal Error, 12767 Tree Invalid Parameter to Action, 12968 Tree Invalid Action Sequence, 13069 Tree Invalid UR Lock State, 1306A Tree Missing Event, 1306B Interpreter Temporary Area
Overflow, 1306C Bad User Record at Read, 1306D Bad User Record During
Processing, 1306E Bad User Record at Write, 1306F Tree Internal Error (Error Action), 13070 File System Drive I/O Error During a
Write Operation, 13171 File System DMA Time-Out, 13272 Scramble Code or I/O Error During
Message-Read Operation, 13373 Scanner Unexpected Error
Acknowledgment, 13474 Scanner Wrong Incoming Message, 1375 Line Task Seize Line Time-out, 13476 Scanner Incoming Message at Write, 177 Scanner Incoming Queue Overflow, 1378 Scanner Error Request Prior to
Reset, 13479 Scanner/ITIC Line Failure, 1357A Message Waiting Bad Extension, 1357B Data Bus Checksum Error, 1367C File System Out of Synch, 1367D Batch Network Transmit Error, 1377E Batch Network Receive Error, 1387F Batch Network File System I/O
Error, 13980 Batch Network Internal Error, 14081 Debug Information Message, 14282 Error Status from OS Scanner Drive, 1483 Catastrophic Error Signalled by
Scanner, 14384 Bad Password Disconnect, 14485 Subscriber Exited with Unheard
Messages, 14486 Line Task Read or Response
Time-out, 145
IN-753 STATUS LOG
Status Log Interpretation Guide
to
r
87 Batch Network Returned Message—Sender’s Box Full, 146
88 Bad Community Record at Read, 14789 Batch Network Informational Error, 1488A SMDI Integration-Related Error, 1488B Bad Command Code for AspenTex, 1498C AMIS-Related Error, 1508D AMIS EAR Array at Least 90%
Full, 1528E AMIS Directory at Least 90% Full, 15290 Outcalling Attempted but No Outcalling
Phone Number Found in User Record, 153
91 Message Waiting on Denied Extension for DMID—COS Does Not Allow Message Waiting, 154
92 AspenNet Scheduler Error, 15593 Fax Queue is Full, 15694 Returned Fax—Sender’s Mailbox is
Full, 15695 Returned Fax—Sender’s Mailbox Does
Not Exist, 15696 FS/CP Software Error, 15797 Purge Task Internal Error, 15798 Bad User Record at Read, 15799 Bad User Record During Processing, 1579A Bad User Record at Write, 1579B File System Drive I/O Error, 1579C File System DMA Time-out, 1579D Data Checksum Mismatch, 1579E Data Bus Error Return Code, 1579F Scramble Code Error or I/O Error, 157
AA0 SST Bad at Write, 158A1 User Record Message Directory Out of
Order, 158A2 Invalid User Record Lock State, 158A3 Unknown Network Prefix in Group List
Member, 158A4 Purge Task Encountered an Error While
Accessing the IVR Message Directory, 159
A5 Bad Member Found in Personal Group List, 160
A6 Error Detected by MDS Functions, 160
A8 SP General Error, 161AA EDBN Directory Not Clean After Two
Passes, 163
BB0 Error Detected by Batch Network Node
Management Functions (BNR), 164B1 Error Detected by Batch Network Node
Management Functions (BNQ), 166B2 Error with Bulletin Mailbox (IFS), 167B3 Bad Mailbox Name Found or Software
Error, 168B4 Bad Network Alias Found or Software
Error, 175B5 Failed to Read Network Alias Record
from Disk, 176B6 Failed to Write Network Alias Record to
Disk, 176B7 System Restarted by Software—Failed
Allocate Memory for Alias Data, 176B8 Failed to Write Company Record to
Disk, 177B9 Error in Notification Library, 178BA Error in Queuing Module of Notification
Library, 181BC Error in the Lock Module of the
Notification Library, 182BD Bad Company Record Found During
Start-up Process, 183BE Bad User Records Found While Building
AMT/NMT During System Start-up, 184
BF Bad INN or Function Code Found, 186
CC1 Bad AMIS Transmission Table Found o
Software Error, 187C2 Failed to Write AMIS Transmission Ta-
ble to Disk, 187C3 Bad AMIS EAR Found or Software
Problem, 188C4 Failed to Write AMIS EAR Record to
Disk, 188C5 Bad AMIS DIR Found or Software
Error, 189
IN-754 STATUS LOG
Index
C6 Failed to Write AMIS DIR Back to Disk, 189
C7 T1 Error Counters, 190C8 Unable to Read Clock Chip (Continuous
Ripple Status Set), 191C9 Clock Chip Went Bad While Running
(After Boot), 191CA System Timer Drifted Too Far From
Clock Chip Date/Time, 191CB Clock Chip Bad or Too Different From
SST Timer at Boot, 191CC Minute Task Internal Error, 191CD Hard Error on Disk Detected by Minute
Task Alarm, 191CE Drive Not Running Detected by Minute
Task Alarm, 192CF T1 Alarms, 192
DD0 CP/FS Protocol Out of Sequence, 194D1 Data Bus Operation With File System or
Cluster Card Failed, 195D2 Data Bus Checksum Error Between CP
and File System, 196D3 Control Bus Operation Failed While
Preparing or Checking Data Bus Operation with File System or Cluster Card, 197
D4 Inconsistent or No Status from OS on Control Bus/Data Bus Operation, 198
D5 OS Reported Control Bus Error, 199D6 File System Returned Bad Status in
Control Bus Message, 200D7 File System Reported Drive Error in
Returned Control Bus Message, 208D8 File System Reported DMA Failure on
Some Previous Operation, 209D9 File System Failed to Respond Within
Time-out Period, 210DA General File System Control Bus Status
Log, 211DB General File System Data Bus Status
Log, 213DC General Directory-Related Error, 214DD Failed to Read User Record from
Disk, 219
DE Failed to Read Company Record From Disk, 220
DF Failed to Write User Record to Disk, 221
EE0 System Error, 222E1 Failed to Start Application, Application
Not Found, Partition Header Damaged or Cold Start Not Available, 224
E2 AMT Error, 225E3 Phrase Concatenation Library
Failure, 235E4 ASA SP Routine General Error, 236E5 ASA SP Routine I/O Error, 238E6 Line Card Control Bus Error, 239E7 Line Card Message Contains Unexpected
Value, 240E8 CP/LC Protocol (Low-Level) Error, 241E9 Line Card Failed to Respond Within
Time-out Period, 242EA Line Card Data Bus Error, 243EB Message Library Failure, 244EC IVR Message Directory Error, 245ED Phrase Library Error, 247EE Mailbox Library Error, 248EF Name Announcement Library Error, 249
FF0 System Name Annoucement Library
Failure, 250F1 System MID Library Failure, 251F2 System MIDG Library Failure, 252F4 Bad AMIS Message Array Found or
Software Error, 253F5 Failed to Write AMIS Message Array
Back to Disk, 253F6 Bad AMIS Dialing Sequence Table Found
or Software Error, 254F7 Failed to Write AMIS Dialing Sequence
Table Back to Disk, 254F8 SP AMIS I/O Error, 255F9 Integration General Error, 256FA IMS Error-Voice Processor-to-Host
Task, 266
IN-755 STATUS LOG