CHAPTER 4 RSTS VERSION 9 ERROR LOG MESSAGE
4.2 INVOKING RSTS VERSION 9 ERROR LOG UTILITY
4.3.1 RSTS V9 SOl Error Log Message
Example 4-1 shows an SDI error message. The numbers on the right-hand side of the example refer to the list of definitions following the example.
Example 4-1 RSTS SOl Error Message
000000 000000 000002 000000 040403 000353 045504 141722 000201 000406 000004 000003 007151 000000 000000 001005 000406 000000 005424 000000 000000 000000 002013 000200 005000 147000 006004 017043 Command Reference
Drive Status/Error Info 005000 147000 006004 017043 Driver Related Data:
FOR INTERNAL USE ONLY
RSTS VERSION 9 ERROR LOG MESSAGE
O. I/O status (Section 14.1.47).
~. Timeout indicator (Section 14.1.47). In this example, the 110 status and timeout indicator show there is a timeout.
~. Control status register addr'ess. In this example, the address is 172150.
~. Contents of control status register. In this example, the contents are 000000.
~. Decode of low byte of word 4. In this example, it is an SDI error.
rn.
MSCP envelope. The first word indicates the number of bytes in the MSCP packet. If the last two digits of the second MSCP envelope word are 20, as shown here, the MSCP packet contains error information. If the last two digits are 01, the MSCP message is an end packet and contains limited useful information. In this example, the number of bytes is 70 and the MSCP packet contains error information.fj. MSCP packet. Figure 4-1 numbering corresponds to the following list.
O. High word of a command reference number (Section 14.1.1).
1. Low word of a command reference number (Section 14.1.1). In this example, the command reference number is O.
2. Unit number (Section 14.1.2). In this example, the unit number is 2.
3. Sequence number (Section 14.1.3). In this example, the sequence number is O.
4. Format and message flag. The low byte word 4 is a format code (Section 14.1.4). The high byte word 4 is a message flag (Section 14.1.5). In this example, the format is 3, and the flag indicates operation continuing and the sequence number has been reset.
5. Status/Event code (Section 14.1.6). In this example, the status/event code indicates a drive detected error.
6. Low word of a unique controller number (Section 14.1.7).
7. Middle word of a unique controller number (Section 14.1.7).
8. High word of a unique controller number (Section 14.1.7). In this example, the controller serial number is 8877953794800.
9. Controller model and the controller class. The low byte is the controller model (Section 14.1,8). The high byte is the controller class (Section 14.1.9). In this example, the controller class is mass storage and the controller model is UDA50-A.
10. Controller software version and the controller hardware version. The low byte is the controller software version (Section 14~ 1.10). The high byte is the controller hardware version (Section 14.1.11). In this example, the controller hardware version is 0, and the controller software version is 4.
11. Multiunit code (Section 14.1.12). In this example, the path is 3.
12. Low word of the drive serial number (Section 14.1.14).
13. Middle word of the drive serial number (Section 14.1.14).
14. High word of the drive serial number (Section 14.1.14). In this example, the drive serial number is 3689.
15. Drive model and drive class. The low byte is the drive model (Section 14.1.15). The high byte is the drive class (Section 14.1.16). In this example, the drive class is DSA disk and the drive model is RA81.
FOR INTERNAL USE ONLY RSTS VERSION 9 ERROR LOG MESSAGE
16. Drive software and hardware version. The low byte is the drive software version (Section 14.1.17). The high byte is the drive hardware version (Section 14.1.18). In this example, the drive software version is 6, and the drive hardware version is 1.
17. Reserved.
18. Low word of the volume serial number (Section 14.1.21).
19. High word of the volume serial number (Section 14.1.21). In this example, the volume serial number is 2836.
20. Low word of the header code (LBN),. (Section 14.1.22).
21. High word of the header code (LBN), (Section 14.1.22). In this example, the header code is the LBN is 0, and it is good.
22. Mode and request byte. The low byte is the request byte (Section 14.1.34). The high byte is the mode byte (Section 14.1.34). In this example, the drive can be formatted, information is available in the extended status area of drive memory, the drive select switch is pushed in (selected), and the run/stop switch is pushed in (run).
23. Controller and error byte. The low byte is the error byte (Section 14.1.34). The high byte is the controller byte (Section 14.1.34). In this example, a drive error has occurred.
24. Drive status bytes (Section 14.1.34). In this example, R/W Ready was not set while attempting a real-time command.
m.
Command reference number (Section 14.1.1). In this example, the command reference number is O.~. Unit number of the drive being accessed (Section 14.1.2). In this example, the unit number is 2.
ml
Message flag field (Section 14.1.5). In this example, the operation is continuing, and the sequence number has been reset.m.
Status code of packet and a translation of the MSCP packet word 5 (Section 14.1.6). In this example, there is a drive detected error.ifl Drive error code (Section 14.1.34).
iE. Controller class (Section 14.1.9). In this example, the controller class is mass storage.
ill Controller model (Section 14.1.8). In this example, the controller model is UDASO-A.
~. Controller hardware version (Section 14.1.11). In this example, the controller hardware version is O.
ml Controller software version (Section 14.1.10). In this example, the controller software version is 4.
m.
Unit serial number (Section 14.1.14). In this example, the unit serial number is 3689.i(;]. Unit class (Section 14.1.16). In this example, the unit class is DSA disk drive.
m.
Unit model (Section 14.1.15). In this example, the unit model is RA81.~. Drive hardware version (Section 14.1.18). In this example, the drive hardware version is 1.
m.
Drive software version (Section 14.1.17). In this example, the drive software version is 6.~. Volume serial number (Section 14.1.21). In this example, the volume serial number is 2836.
~. LBN given in cylinder, track, and sector. In this example, the cylinder is 0, the track is 0, and the sector is O.
4-5
FOR INTERNAL USE ONLY
RSTS VERSION 9 ERROR LOG MESSAGE
~. Bytes 5 and 4 of the drive status (Section 14.1.34). In this example, the FO, ELPS RU bits are set.
~. Bytes 7 and 6 of the drive status (Section 14.1.34). In this example, the DE bit is set.
~. Words 24 through 27 are the drive status (Section 14.1.34).
~. Software interpretation of the perceived state of communication between the code and the controller, or what is happening between the driver and the controller (Section 14.1.48). In this example, the controller is online and communications are open.
m.
Perceived state between the unit and the driver (Section 14.1.49). In this example, the unit status is O.~. Error code indicates what the driver was doing when the error occurred (Section 14.1.50). In this example, the online command to the controller failed.
mJ. This line describes the current state of BBR process (Section 14.1.51). In this example, there is no BBR action.
5.1 INTRODUCTION
FOR INTERNAL USE ONLY