RIOS 3-DIGIT-DISPLAY CODES WGT 11/03/92 Version : 1.08 0c0 User Requested Dump completed successfully. You requested a dump using the sysdumpstart command, a dump key-sequence, or the RESET button. ACTION: Examine dump now or save dump for later examination. 0c2 User Requested Dump started. You requested a dump using the sysdumpstart command, a dump key-sequence, or the RESET button. ACTION: Wait 1 minute for dump to complete and the 3-Digit Display code to change. If the the 3-Digit Display code is still '0c2' after 1 minute, the dump has failed to complete, a partial dump may be present. Examine dump now or save dump for later examination. Request dump to alternate dump device. 0c3 The dump is inhibited. 0c4 The dump did not complete. A partial dump may be present. ACTION: Examine partial dump now or save partial dump for later examination. Request dump to alternate dump device. Increase size of dump media to prevent recurrence. 0c5 Dump failed to start. An unexpected error occurred while attempting to write to the dump media. ACTION: Request dump to alternate dump device. 0c6 User Requested Dump to the secondary dump device requested. You requested a dump using the sysdumpstart command or the Ctrl-Alt-Numpad2 key sequence. ACTION: Make sure that the device assigned as the secondary dump device is ready to receive the dump, then key Ctrl-Alt-Numpad2 again. 0c7 Remote dump in progress. 0c8 Dump disabled. The system configuration did not include a dump device for the requested dump. ACTION: Request dump to alternate dump device. 0c9 System initiated dump started. An unexpected system halt has occurred, dump was started automatically. ACTION: Wait for dump to complete, 3-digit-display will change to flashing 888. 100 BIST completed successfully, control was passed to IPL ROS. 101 Initial BIST started following RESET or POR 102 BIST started following Power-On-RESET or push button pressed. 103 BIST could not determine the system model number. 104 BIST could not find the CBA. 105 BIST could not read from the OCS EPROM. 106 BIST detected a module failure. 111 BIST detected a module failure. 112 Checkstop occurred during BIST and checkstop results could not be logged out. 113 The BIST checkstop count was greater than 1. 120 BIST started CRC check on 875X EPROM 121 BIST detected a bad CRC on the OCS EPROM. 122 BIST started CRC check on the OCS EPROM. 123 BIST detected a bad CRC on the OCS NVRAM. 124 BIST started CRC check on the OCS NVRAM space. 125 BIST detected a bad CRC on the time of day NVRAM. 126 BIST started CRC check on the time of day NVRAM. 127 BIST detected a bad CRC on the 8752 EPROM 130 BIST presence test started or push button stuck. 140 BIST Failed, Box Manufacturing BIST bypass - run BIST anyway. 142 BIST Failed, Box Manufacturing normal mode of operation. 144 BIST Failed. 151 BIST started AIPGM test code (array initialiation on all chips). 152 BIST started DCLST test code (DC logic self test on all chips). 153 BIST started ACLST test code (AC logic self test on all chips). 154 BIST started AST test code (arry self test on all chips). 160 BIST detected a missing EPOW (Early Power On Warning) connector. 164 BIST encountered an error while reading low NVRAM. 165 BIST encountered an error while writing low NVRAM. 166 BIST encountered an error while reading high NVRAM. 167 BIST encountered an error while writing high NVRAM. 168 BIST encountered an error while reading the SIO (Serial I/O) register. 168 BIST encountered an error while writing the SIO (Serial I/O) register. 180 BIST logout failed or logout complete (displayed for 1 minute). 185 Checkstop occurred during BIST, 10 sec to hook up ESP befor logout. 187 BIST was unable to identify the chip release level in the checkstop logout data. 195 BIST logout completed. ********************************************************************* * POST POST POST POST POST POST POST POST POST POST POST * ********************************************************************* 200 You tried to boot the system with the Mode Switch in the SECURE position 201 Checkstop occurred during IPL. FATAL 202 Machine_check_handler FATAL 203 Data_Storage_Interrupt_handler FATAL 204 Instruction_Storage_Interrupt_handler FATAL 205 External_Interrupt_handler FATAL 206 Alignment_Interrupt_handler FATAL 207 Program_Interrupt_handler FATAL 208 Floating_Point_Unavailable_handler FATAL 209 Reserved_900_handler FATAL 209 RSC2 POST - same LED value as Reserved_900_hdlr 210 SVC_1000_handler FATAL 211 IPL ROM CRC miscompare during IPL. FATAL 212 Processor Planar Bad FATAL 212 RAMPOST Memory Configuration Reisters failure FATAL 213 Memory Card failure or Processor Planar Bad. FATAL 213 RAMPOST full/hfwd & byte Load & Store failure FATAL 214 Power status register failed (irrecoverable). 214 RAMPOST PIO Load and Store circuitry failure FATAL 215 A low voltage condition is present (irrecoverable). 215 RAMPOST ECC Generation circuitry failure FATAL 216 RAMPOST ECC Correction circuitry failure FATAL 216 | IPL ROM code being uncompressed into memory 217 RAMPOST Bit Steering Logic failure FATAL 217 End of Bootlist - same LED as Bit Steer Logic Fail 218 RAM POST testing for 1 MB of good memory 218 RAMPOST 1 Meg of good memory not found, address/remap fail FATAL 219 RAMPOST bit_map_generation FATAL /* Normal mode Default path selection from NVRAM IPL Device List 220 ROM scan selected for ipl 220 IPL Control Block being initialized. 221 NVRAM CRC miscompare occurred while trying to boot the AIX Operating (Mode Switch in NORMAL position.) For systems with an internal direct attached hard file, IPL ROM attempted to boot from this hardfile before halting with this 3-Digit Display code. ACTION: If the system halts with this value in the 3-Digit Display, boot and run diagnostics to determine if there is an NVRAM failure. The system automatically reinitializes NVRAM when you boot diagnostics (or AIX Install/ Maintenance, or AIX Maintenance Mode) so a subsequent attempt to boot the AIX Operating System should not result in the system halting with this 3-Digit Display code. The system does not automatically restore the contents of NVRAM which you may have added, e.g. IPL device lists, you will need to restore this information using whatever means you originally used to create it. 222 Native I/O selected for ipl 223 SCSI devices selected for ipl 224 SLA selected for ipl 225 SJL or DBA (esdi hardfile) selected for ipl 226 Ethernet selected for ipl 227 Token Ring selected for ipl 228 expansion code selected for ipl 229 a normal mode device list is present but has no entries (null list) or none of the valid entries succeeded in ipl ACTION: If the system halts with this value in the three digit display, either the NVRAM device list is empty, the devices specified in the list are not valid boot devices, or there is a problem with the devices in the list. To determine if there is a problem with the devices in the list, refer to the hardware problem determination procedures in the RIOS Diagnostics Programs Operators Guide. To modify the NVRAM device list, boot the AIX Operating System and use the iplist command. /* Normal mode Default path selection from ROM IPL Device List 230 ROM scan selected for ipl 231 Ethernet chosen from menus 232 Native I/O selected for ipl 233 SCSI devices selected for ipl 234 SLA selected for ipl 234 | 9333 subsystem device selected for ipl 235 SJL or DBA (esdi hardfile) selected for ipl 236 Ethernet selected for ipl 237 Token Ring selected for ipl 238 Token Ring selected for ipl from menus 239 Menu selected device (Ethernat or Token Ring) failed to boot. /* Service mode Default path selection from NVRAM IPL Device List 240 ROM scan selected for ipl 241 devices specified in NVRAM IPL Devices List 242 Native I/O selected for ipl 243 SCSI devices selected for ipl 244 SLA selected for ipl 244 | 9333 subsystem device selected for ipl 245 SJL or DBA (esdi hardfile) selected for ipl 246 Ethernet selected for ipl 247 Token Ring selected for ipl 248 expansion code selected for ipl 249 a service mode device list is present but has no entries (null list) or none of the valid entries succeeded in ipl ACTION: See action for error code 229 /* Service mode Default path selection from ROM IPL Device List 250 ROM scan selected for ipl 251 Ethernet chosen from menus 252 Native I/O selected for ipl 253 SCSI devices selected for ipl 254 SLA selected for ipl 254 | 9333 subsystem device selected for ipl 255 SJL or DBA (esdi hardfile) selected for ipl 256 Ethernet selected for ipl 257 Token Ring selected for ipl 258 Token Ring selected for ipl from menus 260 Attempting Network IPL, menus and information present on screen 260 call to the user interface 260 NVRAM not initialized with bootlist, keyboard type and language type even tho keyboard / display or tty connected to system 261 Attempting Network IPL, menus, no console display detected 261 Console handlers request led value 261 NVRAM not initialized with bootlist, keyboard type and language type with no keyboard / display or tty connected to system 262 Attempting Network IPL, menus, no console keyboard detected 262 Console handlers request led value 263 Attempting Normal mode system restart from Family 2 feature ROM specified in the NVRAM boot device list 281 Keyboard POST 282 Parallel POST 283 Serial POST 284 7011/220 (SGA) POST 284 | POWER Gt1 graphics adapter POST 285 POWER Gt3 (LEGA) graphics adapter POST 286 Token Ring POST in progress (Power On Self Test == POST) 287 Ethernet POST in progress 288 Microchannel POST in progress 288 Family 2 bus scan 289 Diskette POST 290 IO Planar Bad. 290 IOCC POST 291 NIO POST being executed. 292 SCSI POST being executed. 293 SJL or Bus Attached Internal Hard File POST being executed. 294 SLA POST 295 XX3 POST (Ethernet) 296 XX2 POST (Tolkenring) 297 XX1 POST 297 System model number could not be determined. 298 Attempting warm IPL. 299 IPL ROS has completed loading and has passed control to passed control to the loaded code ********************************************************************* * LPOST LPOST LPOST LPOST LPOST LPOST LPOST LPOST LPOST LPOST LPOST * ********************************************************************* 500 Querying Native I/O card (NIO or SIO). 501 Querying card in slot 1. 502 Querying card in slot 2. 503 Querying card in slot 3. 504 Querying card in slot 4. 505 Querying card in slot 5. 506 Querying card in slot 6. 507 Querying card in slot 7. 508 Querying card in slot 8. 510 Starting device configuration. 511 Device configuration completed. 512 Restoring device configuration files from media. 513 Restoring basic operating system installation files from media. 516 Contacting server during network boot. 517 Mount all the boot file systems of "type=bootfs" in /etc/filesystems or Mounting network file systems (/mnt, /usr) 518 Mount failed, one or more of the file systems did not mount 520 bus configuration running. 521 /etc/init invoked cfgmgr with invalid options, /etc/init has been corrupted or incorrectly modified. FATAL 521 The /etc/inittab file has been incorrectly modified or corrupted. 522 The configuration manager has been invoked with conflicting options. FATAL 522 The /etc/inittab file has been incorrectly modified or corrupted. 523 The configuration manager is unable to access the ODM data base. FATAL 523 The /etc/objrepos file is missing or inacessable. 524 The configuration manager is unable to access the config rules object in the ODM data base. FATAL 524 The /etc/objrepos/Config_Rules file is missing or inacessable. 525 The configuration manager is unable to get data from customized device object in the ODM data base. FATAL 525 The /etc/objrepos/CuDv file is missing or inacessable. 526 The configuration manager is unable to get data from customized device driver object in the ODM data base. FATAL 526 The /etc/objrepos/CuDvDr file is missing or inacessable. 527 The configuration manager was invoked with the Phase 1 flag, however, running Phase 1 at this point is not permitted. FATAL 527 The /sbir/rc.boot file has been incorrectly modified or corrupted. 528 The configuration manager can't find sequence rule or no program name was specified in the ODM data base. FATAL 528 The /etc/objrepos/Config_Rules file has been incorrectly modified, corrupted, or a program specified in the file is missing. 529 The configuration manager is unable to update ODM data or the root file system is full. 530 The program 'savebase' returned an error. 531 The configuration manager is unable to access the PdAt object class. FATAL 531 The /usr/lib/objrepos/PdAt file is missing or inacessable. 532 There is not enough memory for the configuration manager to continue (malloc failure). FATAL 533 The configuration manager could not find a configure method for a device. 533 The /usr/lib/objrepos/PdDv file has been incorrectly modified, corrupted, or a program specified in the file is missing. 534 The configuration manager is unable to acquire data base lock. FATAL 536 The configuration manager encountered more than one sequence rule specified in the same phase. FATAL 536 The /etc/objrepos/Config_Rules has been incorrectly modified or corrupted. 537 The configuration manager encountered an error when invoking the program in the sequence rule. 537 The /etc/objrepos/Config_Rules has been incorrectly modified, corrupted, or a program specified in the file is missing. 538 The configuration manager is passing control to a configuration method. 539 The configuration method has ended and control has returned to the configuration manager. 551 IPL Varyon of the root volume group is running. 552 IPL Varyon of the root volume group failed. 553 IPL Phase 1 is complete. (/etc/(un)mount missing or / or /tmp full 553 The /etc/inittab file has been incorrectly modified or corrupted. 554 Unable to define NFS swap device during network boot. 555 Unable to create NFS swap device during network boot. 556 Unable to configure NFS swap device during network boot. 557 | Unable to fsck or mount thr root (/) filesystem 558 There is not enough memory available to continue the IPL. 581 Configuring TCPIP. 582 Configuring a token ring data link control. 583 Configuring a ethernet data link control. 584 Configuring a IEEE ethernet data link control (802.3). 585 Configuring a SDLC MPQP data link control. 586 Configuring a QLLC X.25 data link control. 587 Configuring a NETBIOS. 588 Configuring a BSCRW. 590 Configuring diskless remote paging device. 591 Configuring LVM Device Driver (Logical Volume Manager). 592 Configuring HFT Device Driver (High Function Terminal). 593 Configuring SNA Device Drivers. 595 | Configuring X.31 pseudo device (X.25 over ISDN) 596 | Configuring SNA DLC/LAPE device 597 | Configuring OCS (Outboard Communication Server) 711 Unknown adapter being identified/configured. 721 Unknown SCSI device being identified/configured. 722 Unknown Disk being identified/configured. 723 Unknown CDROM being identified/configured. 724 Unknown Tape being identified/configured. 725 Unknown Display being identified/configured. 726 Unknown Input device being identified/configured. 727 Unknown Async device being identified/configured. 728 Parallel Printer being identified/configured. 729 Unknown Parallel device being identified/configured. 730 Unknown diskette drive type being identified/configured. 731 PTY being identified/configured. 732 | Unknown SCSI Initiator 811 Processor Complex being identified/configured. 812 Common Standard Adapter Logic being identified/configured. 812 Memory being identified/configured. 813 Battery for Time-of-Day, NVRAM, etc. being identified/configured. 813 System I/O Control Logic being identified/configured. 814 NVRAM being identified/configured. 815 Floating Point Processor being identified/configured. 816 Operator Panel Logic being identified/configured. 817 Time of Day Logic being identified/configured. 818 | Used by DA to report checkstop / machine checks 819 Graphics Input Device adapter being identified/configured. 821 Standard Keyboard adapter being identified/configured. 823 Standard Mouse adapter being identified/configured. 824 Standard Tablet adapter being identified/configured. 825 Standard Speaker adapter being identified/configured. 826 Serial Port 1 adapter being identified/configured. 827 Parallel port adapter being identified/configured. 828 Standard Diskette adapter being identified/configured. 831 3151 adapter being identified/configured. 831 Serial Port 2 being identified/configured. 834 64-Port Async Controller being identified/configured. 835 16-Port Async Concentrator being identified/configured. 836 | 128-Port Async Controller being identified/configured. 837 | 16-Port Remote Async Node (EIA-232) being identified/configured. 841 8-Port Async adapter (EIA-232) being identified/configured. 842 8-Port Async adapter (EIA-422A) being identified/configured. 843 8-Port Async adapter (MIL-STD 188) being identified/configured. 847 16-Port Serial adapter (EIA-232) being identified/configured. 848 16-Port Serial adapter (EIA-422) being identified/configured. 849 X.25 Communications adapter being identified/configured. 850 Token-Ring Network adapter being identified/configured. 852 Ethernet adapter being identified/configured. 854 3270 Connection being identified/configured. 855 4-Port Multiprotocol Controller being identified/configured. 857 FSLA adapter being identified/configured. 858 5085/86/88 adapter being identified/configured. 859 FDDI adapter being identified/configured. 860 | Twin Tailed (Harrier) adapter being identified/configured. 861 Serial Optical Channel converter being identified/configured. 862 Block Multiplexer Channel adapter being identified/configured. 862 370 Parallel Channel adapter being identified/configured. 863 | MAP adapter being identified/configured. 864 | Serial Channel adapter being identified/configured. 865 | 370 Serial Channel adapter being identified/configured. 866 | SCSI adapter being identified/configured. 867 Async Expansion adapter being identified/configured. 868 SCSI adapter being identified/configured. (Spock) 869 SCSI adapter being identified/configured. 870 Serial Disk adapter being identified/configured. 870 | Harrier 2 adapter being identified/configured. 871 Graphics Subsystem adapter being identified/configured. 872 Grayscale Graphics adapter being identified/configured. 873 | Skyway 16 Graphics adapter being identified/configured. 874 Color Graphics adapter being identified/configured. 875 | Skyway 256 Graphics adapter being identified/configured. 876 8-Bit Color Graphics Processor being identified/configured. 877 Power Gt3/Gt4 being identified/configured. 877 | LEGA Display adapter being identified/configured. 878 | Pedernales Graphics adapter being identified/configured. 879 | 24-bit Color Graphics Processor being identified/configured. 880 7011/220 Graphics adapter being identified/configured. (SGA) 881 | Channel Attached Printer being identified/configured. 882 | Serial Attached Printer being identified/configured. 883 | Pegasus Support (Japan) 884 | 3117 Scanner adapter being identified/configured. 885 | 3118 Scanner adapter being identified/configured. 886 | 3119 Scanner adapter being identified/configured. 887 Integrated Ethernet adapter being identified/configured. 888 (flashing) unexpected halt. FATAL 889 | SCSI adapter being identified/configured. 891 Vendor SCSI adapter being identified/configured. 892 Vendor Display adapter being identified/configured. 893 Vendor LAN adapter being identified/configured. 894 Vendor Async/Communications adapter being identified/configured. 895 Vendor IEEE 488 adapter being identified/configured. 896 Vendor VME buss adapter being identified/configured. 900 ??? Attempting to boot from tape but mksysb missing after /bootrec 901 Vendor SCSI device being identified/configured. 902 Vendor Display being identified/configured. 903 Vendor Async device being identified/configured. 904 Vendor Parallel device being identified/configured. 905 Vendor other device being identified/configured. 920 Bridge Box being identified/configured. 921 Keyboard 101 being identified/configured. 922 Keyboard 102 being identified/configured. 923 Keyboard Kanji being identified/configured. 924 Two-Button Mouse being identified/configured. 925 Three-Button Mouse being identified/configured. 926 Tablet 5083 Model 21 being identified/configured. 927 Tablet 5083 Model 22 being identified/configured. 928 Standard Speaker being identified/configured. 929 Dials being identified/configured. 930 Lighted Program Function Keys (LPFK) keyboard being 931 IP Router being identified/configured. 931 | 5086 Keyboard being identified/configured. 932 | IP Router being identified/configured. 933 Async Planar being identified/configured. 934 Async Expansion Drawer being identified/configured. 935 1.44 MB 3.5-Inch Diskette Drive being identified/configured. 936 1.2 MB 5.25-Inch Diskette Drive being identified/configured. 937 | HIPPI adapter being identified/configured. 938 | 122 Keyboard being identified/configured. 939 | Tablet for 6 button cursor being identified/configured. (delete)940 7372 Plotter being identified/configured. 940 | Used by memory DA 941 | 6180 Plotter being identified/configured. (delete)942 6184 Plotter being identified/configured. (delete)943 6186 Plotter being identified/configured. (delete)944 6180 Plotter Model 11 being identified/configured. (delete)945 5084 Plotter Model 1 being identified/configured. (delete)946 5084 Plotter Model 2 being identified/configured. (delete)947 5084 Plotter Model 3 being identified/configured. 948 Portable Disk Drive being identified/configured. 949 Unknown direct buss-attached device being identified/configured. 950 Missing SCSI Options being identified/configured. 951 670 MB SCSI Disk Drive being identified/configured. 952 355 MB SCSI Disk Drive being identified/configured. 953 320 MB SCSI Disk Drive being identified/configured. 954 400 MB SCSI Disk Drive being identified/configured. 955 857 MB SCSI Disk Drive being identified/configured. 956 670 MB SCSI Disk Drive electronics card being identified/configured. 957 Direct Bus Attached Disk Drive being identified/configured. 957 | 120 MB Bus Attached Disk Drive being identified/configured. 958 | 160 MB Bus Attached Disk Drive being identified/configured. 959 | 160 MB SCSI Disk Drive being identified/configured. 960 | 1.37 GB SCSI Disk Drive being identified/configured. (Wannamingo (delete)961 ASCII 14-Inch Terminal being identified/configured. 961 | Route 66 - 2 Port Serial adapter being identified/configured. (delete)962 3161 Terminal being identified/configured. 962 | Route 66 - Ethernet adapter being identified/configured. (delete)963 3163 Terminal being identified/configured. 963 | SCSI Scanner (2456) adapter being identified/configured. 965 | Route 66 - Token Ring adapter being identified/configured. 968 | 1.2 GB SCSI Disk Drive being identified/configured. (Corsair) 968 | 160 MB Disk Drive being identified/configured. 970 .5-Inch 9-Track Tape drive being identified/configured. 971 150 MB .25-Inch Tape drive being identified/configured. 972 8mm SCSI Tape drive being identified/configured. 973 | Other SCSI Tape drive being identified/configured. 974 CDROM drive being identified/configured. 975 | ERIMO R/W Optical drive being identified/configured. 976 | RISC System 6000 SCSI I/O Controller Initiator 977 M-Audio capture and playback adapter being identified/configured. 977 | ACPA adapter being identified/configured. 978 | IEEE 488 adapter being identified/configured. 979 | 7246 SBS Frame Buffer adapter being identified/configured. (delete)980 4216 Printer being identified/configured. 980 | ISDN Basic adapter being identified/configured. (Athens/Pegasus) (delete)981 3812 Printer being identified/configured. 981 | ISDN Primary adapter being identified/configured. (Athens/Sparta) (delete)982 3852 Printer being identified/configured. 982 | Graphics Visulation Server adapter being identified/configured . (delete)983 4201 Printer being identified/configured. (delete)984 4202 Printer being identified/configured. 984 | ISDN port being identified/configured. (delete)985 4207 Printer being identified/configured. 985 | M-Video adapter being identified/configured. (VCA) (delete)986 4208 Printer being identified/configured. 986 | 2.4 GB SCSI Disk Drive being identified/configured. (Wildcat) (delete)989 4224 Printer being identified/configured. 989 | 200 MB SCSI Disk Drive being identified/configured. (KAI) (delete)990 4234 Printer being identified/configured. 990 | 5 GB 8mm SCSI Tape Drive being identified/configured. (delete)991 Tryon Printer being identified/configured. 991 | 525 MB 1/4" SCSI Tape Drive being identified/configured. (Tundra) (delete)992 5202 Printer being identified/configured. 992 | 4755 Crytographic adapter being identified/configured. (delete)993 5204 Printer being identified/configured. 995 | 1/4" Tape Drive being identified/configured. 996 | 1.0 GB SCSI Tape Drive being identified/configured. 997 | FDDI adapter being identified/configured. (delete)998 Chief Printer being identified/configured. 998 | 4mm Tape Drive being identified/configured. (delete)999 Raintree Printer being identified/configured. c00 AIX Install / Maintance loaded correctly. c01 Insert the first diagnostics diskette. c02 | Wrong diskette sequence used. REBOOT !!! c03 The wrong diskette is in the diskette drive. c04 The loading stopped with an irrecoverable error. c05 A diskette error occured. c06 The rc.boot configuration script is unable to determine type of boot. c07 Insert the next diskette. c08 RAM file system started incorrectly. c09 The diskette drive is reading or writing a diskette. c20 Low Level Debugger activated. An unexpected system halt has occurred, and you have configured the system to activate the low level debugger instead of doing a dump. ACTION: You can run debugger commands, including requesting a dump. When you exit the debugger, the LED code will change, find the new LED code in this list. c21 | The ifconfig command was unable to configure the network for the client network host to boot. c22 The tftp command was unable to read the client's ClientHostName.info file during a client network boot. c23 | NFS qfsinstall failed for client network boot. c24 Unable to read the client's ClientHostName.info file during client network boot. c25 Client did not mount miniroot during network install. c26 Client did not mount the /usr file system during network boot. c31 If no console has been configured, the system halts with this value in the three-digit-display and the system displays instructions for choosing a console on the native display. System initialization and configuration will continue after you choose a console. If you are starting the system in SERVICE mode and the system does not have a display or the display is not working and you are unable to choose a console, system initialization and configuration will complete without a console configured if you turn the keyswitch to the NORMAL position. c32 The console is a HFT. (Informational only) c33 The console is a TTY. (Informational only) c34 The console is a file. (Informational only) c99 Diagnostics have completed. This code is only used when there is no console. EEE (hex 14 14 14) reserved for FAA to do a reset to control pqnel This displays as a big E with the top bar missing ----------------------------------------------------------------------- SYSTEM_HALT_SYSTEM_HALT_SYSTEM_HALT_SYSTEM_HALT_SYSTEM_HALT_SYSTEM_HALT ----------------------------------------------------------------------- 888 The system has halted A flashing 888 is displayed in the 3-Digit Display by the system to indicate that there is a message to be displayed in the 3-Digit Display. You will use the RESET button to display the message which is encoded as a string of 3-Digit Display codes. (Pressing the RESET button under these circumstances WILL NOT IPL the system). Turn the Mode Switch to the NORMAL position or the SERVICE position and press the RESET button to display the first code in the string, record this code in the space provided on the Problem Summary Form and then press the RESET button again to display the next code. Continue displaying and recording codes in this manner until flashing 888 is displayed again. You may display the error information again if necessary. The first code following the 888 indicates what type of information is contained in the remainder of the string. Find this code in the following table: CODE TYPE OF MESSAGE ---- ----------------------------------------------------- 102 Unexpected System Halt during normal operation. | System Crash Codes For unexpected system halts the string of 3-Digit Display codes has the following format: 888 102 mmm ddd Where mmm is a code indicating the cause of the halt and ddd is a code indicating whether a system dump was obtained. The following table lists possible values for 'mmm' and their causes. If the system halts with one of the following values in the 3-Digit Display, perform the hardware problem determination procedures in the IBM RIOS Diagnostics Programs Operators Guide. If the hardware problem determination procedures return an SRN, record that SRN on item 4 of the Problem Summary Form. If hardware problem determination procedures do not return an SRN, record SRN 101-mmm on item 4 of the Problem Summary Form. Report the problem to your service organization. If a dump was obtained, copy the dump to removeable media and be prepared to make it available to your service organization. mmm cause of halt --- --------------------------------- 000 Unexpected system interrupt. 200 Machine check due to Memory Bus Error (RAS/CAS Parity) 201 Machine check due to Memory Timeout. 202 Machine check due to Memory Card Failure. 203 Machine check due to Address Exception (Address out of range). 204 Machine check due to Attempted Store into ROS. 205 Machine check due to Uncorrectable ECC due to Address Parity. 206 Machine check due to Uncorrectable ECC. 207 Machine check due to Undefined Error. 300 Data Storage Interrupt - Processor Type. 32x Data Storage Interrupt - I/O Exception - IOCC. The number represented by 'x' is the BUID. 38x Data Storage Interrupt - I/O Exception - SLA. The number represented by 'x' is the BUID. 400 Instruction Storage Interrupt. 500 External Interrupt - Scrub - Memory Bus Error (RAS/CAS Parity) 501 External Interrupt - Undefined Error 51x External Interrupt - DMA - Memory Bus Error (RAS/CAS Parity) 52x External Interrupt - IOCC Type - Channel Check. 53x External Interrupt - IOCC Type - Bus Timeout. 54x External Interrupt - IOCC Type - Keyboard External. The number represented by 'x' is the IOCC number. 558 There is not enough memory available to continue the IPL. 700 Program Interrupt 800 Floating Point Unavailable. The following table lists possible values for 'ddd'. ddd dump status --- --------------------------------- 0c0 User requested dump completed successfully. 0c2 User requested dump started. 0c3 The dump is inhibited. 0c4 The dump did not complete. A partial dump may be present. 0c5 The dump program could not access the dump device. 0c6 User Requested Dump to the secondary dump device requested. 0c7 Reserved. 0c8 The dump function is disabled, no primary dump device configured 0c9 A dump is in process. c20 Low Level Debugger started. 103 Diagnostic Message Diagnostic messages are displayed in the 3-Digit Display in the following circumstances: When a failure is detected that prevents the completion of IPL. When the console display is not present or it is unavailable because of a display or adapter failure. The string of 3-Digit Display codes identifies the SRN (Service Request Number) and up to four FRUs (Field Replaceable Units). The string of 3-Digit Display codes has the following format: 888 103 sss rrr c01 1xx 2xx 3xx 4xx 5xx 6xx 7xx 8xx c02 1yy ... sss rrr is the Service Request Number, record this number on item 4 of the Problem Summary Form. A B | C D | E F | G H Eight-digit location code c01 1xx 2xx 3xx 4xx 5xx 6xx 7xx 8xx First FRU location code c02 1xx 2xx 3xx 4xx 5xx 6xx 7xx 8xx Second FRU location code c03 1xx 2xx 3xx 4xx 5xx 6xx 7xx 8xx Third FRU location code c04 1xx 2xx 3xx 4xx 5xx 6xx 7xx 8xx Fourth FRU location code if a ccx (x is between 2 thru 9) then the next display code(s) following are the diferences from the previous c01 ... code. c01 100 200 300 401 500 601 700 800 cc2 602 ... ... is the same as c01 100 200 300 401 500 601 700 800 c02 100 200 300 401 500 602 700 800 ... where the above xx locations correspond to xx - value xx - value xx - value xx - value 00 = 0 11 = A 21 = K 31 = U 01 = 1 12 = B 22 = L 32 = V 02 = 2 13 = C 23 = M 33 = W 03 = 3 14 = D 24 = N 34 = X 04 = 4 15 = E 25 = O 35 = Y 05 = 5 16 = F 26 = P 36 = Z 06 = 6 17 = G 27 = Q 07 = 7 18 = H 28 = R 08 = 8 19 = I 29 = S 09 = 9 20 = J 30 = T Location code format for non-SCSI devices AB - CD - EF - GH || | | | || | | +- Async port number or FRU location on a card or || | | planar. || | | || | +------ Connector number on an adapter or planar. || | || +----------- Slot number of the adapter, memory card, or || adapter for an identified device. || |+--------------- Always 0 on workstations. Drawer ID or slot | number of the adapter that drives the drawer | in a rack-type system. | +---------------- Always 0 Location code format for SCSI devices AB - CD - EF - GH | || | || | || | |+ Always 0 | || | | | || | +- SCSI address of the device. See Service | || | Guide for physical location of device. | || | | || +------ Always 00 | || | |+---------- Slot number of the SCSI controller. For IBM | | 7012 Direct Buss Attached Disk, 7 denotes rear | | drive location and 8 denotes front location. | | | +----------- Always 0 | +---------------- Always 00 Location code format for IBM 9333 High Performance Disk Drive Subsystems AB - CD - EF - GH | || || || | || || |+ Compartment number 0 through 3 | || || +- Always 0 | || || | || |+----- Adapter connector 0 through 3 | || +------ Always 0 | || | |+---------- Adapter slot 1 through 8 in CPU drawer or system unit. | +----------- Always 0 | +---------------- Always 00 Location code table Pair Value Description AB 00 Workstation-type unit 00 CPU drawer in a rack-type system unit 00 SCSI device drawer in a rack-type system unit 00 SCSI disk drawer in a rack-type system unit 01 Async expansion adapter in slot 1 of CPU drawer 02 Async expansion adapter in slot 2 of CPU drawer 03 Async expansion adapter in slot 3 of CPU drawer 04 Async expansion adapter in slot 4 of CPU drawer 05 Async expansion adapter in slot 5 of CPU drawer 06 Async expansion adapter in slot 6 of CPU drawer 07 Async expansion adapter in slot 7 of CPU drawer 08 This is invalid. Slot 8 should contain SCSI adpt. CD 00 CPU planar 00 Standard I/O planar 00 A device attached to the standard I/O planar 01 Adapter in slot 1 of the I/O planar 02 Adapter in slot 2 of the I/O planar 03 Adapter in slot 3 of the I/O planar 04 Adapter in slot 4 of the I/O planar 05 Adapter in slot 5 of the I/O planar 06 Adapter in slot 6 of the I/O planar 07 Adapter in slot 7 of the I/O planar 08 Adapter in slot 8 of the I/O planar 07 Read Direct Buss Attached Disk Drive (IBM 7012) 08 Front Direct Buss Attached Disk Drive (IBM 7012) 0A Memory card in slot A on the CPU planar 0B Memory card in slot B on the CPU planar 0C Memory card in slot C on the CPU planar 0D Memory card in slot D on the CPU planar 0E Memory card in slot E on the CPU planar 0F Memory card in slot F on the CPU planar 0G Memory card in slot G on the CPU planar 0H Memory card in slot H on the CPU planar AA Serial Optic Converter in slot AA of system/CPU planar AB Serial Optic Converter in slot AB of system/CPU planar EF 00 Does not have a connector or software was not able to identify the connector number 01 The number of the connector on an adapter card, thru 04 distribution box, or planar 0D Internal diskette connector on the std. I/O planar 0K Keyboard connector on the std. I/O planar 0M Mouse connector on the std. I/O planar 0P Parrallel printer connector on the std. I/O planar 0T Tablet connector on the std. I/O planar S1 Serial port 1 connector on the std. I/O planar S2 Serial port 2 connector on the std. I/O planar 1A Port A of the Serial Optic Converter in slot AA of the CPU 1B Port B of the Serial Optic Converter in slot AA of the CPU 2A Port A of the Serial Optic Converter in slot AB of the CPU 2B Port B of the Serial Optic Converter in slot AB of the CPU GH 00 For devices other than those listed here 00 Port addresses for 8 port async, 16 port async, thru 15 and 16 port concentrator boxes 01 Diskette drive 1 attached to standard I/O planar 02 Diskette drive 2 attached to standard I/O planar 01 Memmory SIMM in location 1 on memory card 02 Memmory SIMM in location 2 on memory card 03 Memmory SIMM in location 3 on memory card 04 Memmory SIMM in location 4 on memory card 05 Memmory SIMM in location 5 on memory card 06 Memmory SIMM in location 6 on memory card 07 Memmory SIMM in location 7 on memory card 08 Memmory SIMM in location 8 on memory card 00 SCSI device set to address 0 10 SCSI device set to address 1 20 SCSI device set to address 2 30 SCSI device set to address 3 40 SCSI device set to address 4 50 SCSI device set to address 5 60 SCSI device set to address 6 ----------------------------------------------------------------------- | New Release 4 Location Identification Information | | | RISC/6000 product family is a family of systems that consists of a rack | configuration, a tower configuration, and a table-top configuration... | External boxes, rack drawers, portable files, etc. can be attached to | the system. FRUs can be located in any of these units. To locate a FRU | the CE needs to know the following information: | | | * For rack the following are needed: | | - rack | - drawer | - slot if adapter, memory card, or SLA | - I/O planar | - physical location if a device such as a hard file or diskette | - location on card for memory simms. | | * For a tower and table-top the following are needed: | | - slot if adapter, memory card, or SLA | - physical location if a device such as a hard file or diskette | - location on card for memory simms. | | * For external boxes and devices the following are needed: | | - external box or device | - slot if adapter | - physical location if a device such as a hard file or diskette | | | Software can identify the following location information: | | * the system type | | * adapter slot | | * I/O planar | | * memory slot | | * SLA slot | | * SCSI Address | | * The adapter an external device or external box is attached to. | | Software can NOT identify the following location information: | | * rack | | * drawer | | * SCSI device's physical location | | * Diskette Drive physical location | | | The Location Code is defined as: | | | AB-CD-EF-GH | | | For planars, cards, and non-SCSI devices | the Location Code is defined as: | | | AB-CD-EF-GH | | || | | | | || | Device/FRU/Port ID | | || Connector ID | | |Slot ID | | Channel/Bus | Drawer ID | | | where: | | * AB is the Drawer ID | | It is used to identify CPU and Async Drawers. | | For CPU Drawers and non-rack systems AB is 00. | | For Async Drawers, A identifies the Channel/Bus (I/O Planar) and B | identifies the Slot ID of the Async Adapter that attaches to the drawer. | This corresponds to the CD value of the Async Adapter Location Code. | | * CD is the Channel/Bus and Slot ID. | | It is used to identify the location of an adapter, memory card, or SLA | | - For microchannel adapters, C identifies the Channel/Bus (I/O Planar) | and D identifies the Slot ID.For systems with 2 planars, C is equal | to 0 for the first I/O Planar and 1 for the second I/O Planar. | | | - For integrated adapters, C identifies the planar and D is 0. | | - For memory, C (Channel/Bus) is equal to 0 and D is equal to the slot | number (A to H) for cards on non-Salmon systems and SIMMs on Salmon | systems. | | - For devices, CD is equal to the CD value of the adapter which the | device attaches too. | | - For a SLA card, C identifies the Channel/Bus (1) and D identifies | the slot (A or B). | | * EF is the Connector ID. | | It is used to identify the adapter connector that a resource is attached | too. | | If the external connectors are not labeled, then they should be numbered | from 1 to n starting at the top of the card. The top of the card is | defined as the side opposite the connector that plugs into the bus. | | Some examples of connectors are: | | - The 64 port connectors should be 01 to 04. | | - The GIO connectors should be 01 and 02. | | - The 8 port and 16 port connector should be 01. | | - S1 and S2 should be used for the NIO Serial connectors. | | - 0P should be used for the NIO parallel connector. | | - 0K should be used for the NIO keyboard connector. | | - 0M should be used for the NIO mouse connector. | | - 0T should be used for the NIO tablet connector. | | - 0D should be used for the NIO diskette connector. | | - The SLA connectors should be 01 and 02. | | * GH is the Port/Device/FRU ID | | It is used to identify a port, device, or a FRU. GH has several meanings | depending upon the resource type. They are: | | * For memory cards H defines a memory SIMM. | Values for H are 1, 2...or 8. G is always 0. | | * For async devices GH defines the port on the fanout box. | Values are 00 to 15. | | * For a diskette drive H defines which diskette drive 1 or 2. G is always 0. | | * For all other devices GH is equal to 00. | | | For SCSI devices (including Harrier disks) the Location Code is defined as: | | | AB-CD-EF-GH | | || | || | | || | |Logical Unit Address of SCSI Device | | || | Control Unit Address of SCSI Device | | || Connector ID | | |Slot ID of SCSI Controller or Serial Disk Adapter | | Channel/Bus of SCSI Controller or Serial Disk Adapter | Drawer ID of SCSI Controller | | where: | | * AB is the Drawer ID that contains the adapter. | | AB is always equal to 00 at release 1 and 2. | | * C is the Channel/Bus (I/O Planar) for the adapter and D is the Slot ID | for the adapter. If the SCSI Controller is integrated, then CD is 00. | | * EF is the Connector ID that the Device is attached too. | | * CD-EF can be used as the Drawer ID. | | * G defines the Control Unit address of the device. | | * H defines the Logical Unit address of the device. | | SCSI device drawers should be labeled with the CD-EF value of the device | location code. | | | Some examples of Location Codes are: | | * A CPU drawer is: | | 00 | | * An async drawer attached to the async adapter in slot 1 of the first | I/O Planar is: | | 01 | | The drawer should be labeled 01. | | * An async drawer attached to the async adapter in slot 4 of the second | I/O Planar is: | | 14 | | The drawer should be labeled 14. | | * A TTY device attached to port 13 of a fanout box attached to the second | connector of a 64 port card in slot 5 of an async drawer attached to the | async adapter in slot 3 of the second I/O Planar is: | | 13-05-02-13 | | The TTY device should be labeled 13-05-02-13. | | * A TTY device attached to port 5 of a fanout box attached to an 8-port | card in slot 6 of a deskside system is: | | 00-06-01-05 | | * A fanout box attached to second connector of a 64 port card in slot 8 | of an async drawer attached to the async adapter in slot 3 of the first | I/O Planar is: | | 03-08-02 | | The fanout box should be labeled 03-08-02. | | * A 64 port card in slot 5 of an async drawer attached to the async adapter | in slot 7 of the second I/O Planar is: | | 17-05 | | * An internal SCSI device attached to SCSI adapter in slot 2 of a desktop | system with a Control Unit Address of 3 and a Logical Unit address of 1 is: | | 00-02-00-31 | | The device should be labeled 00-02-00-31. | | * An external SCSI device in a drawer attached to SCSI adapter in slot 2 of | the second I/O Planar with a Control Unit Address of 3 and a Logical | Unit address of 1 is: | | 00-12-00-31 | | The drawer should be labeled 00-12-00-31. | | * An external SCSI device in a drawer attached to SCSI adapter in slot 2 | of the second I/O Planar with a Control Unit Address of 3 and a Logical | Unit address of 1 is: | | 00-12-00-31 | | The drawer should be labeled 00-12-00-31. | | * An external device in a drawer attached to the third port of a Serial | Disk Adapter in slot 6 of the second I/O Planar with a Control Unit | Address of 3 and a Logical Unit address of 1 is: | | 00-16-02-31 | | The drawer should be labeled 16-02. | | * The first diskette drive attached to the NIO is | | 00-00-0D-01 | | * The second diskette drive attached to the NIO is | | 00-00-0D-02 | | * The keyboard attached to the NIO is | | 00-00-0K | | * A display attached to the display adapter in slot 2 of the CPU drawer is: | | 00-02-01 | | * The fourth memory SIMM on the memory card in slot D of the CPU is | | 00-0D-00-04 ----------------------------------------------------------------------- New Release 2 and Release 3 '105' error codes 105 Diagnostic Message Diagnostic messages are displayed in the 3-Digit Display in the following circumstances: 888 105 1xx 2xx 3xx 4xx ==> encoded SRN (Service Request Number) c01 1xx 2xx 3xx 4xx 5xx 6xx 7xx 8xx c02 1yy ... (failure(s)) The 105 error codes are decoded using the 103 xx location translate table from the previous section. The c01 ..., c02 ..., error codes are decoded the same as 103 codes note that the main diference between 103 and 105 errors are that 105 errors are encoded SRN's and 103 errors are not. 888 103 sss rrr ==> SRN c01 1xx 2xx 3xx 4xx 5xx 6xx 7xx 8xx c02 1yy ... (failure(s)) ----------------------------------------------------------------------- | New Release 2 and Release 3 '103' error codes for SRN's The new service request numbers are of the form 120 000 to 129 999 displayed as 12x xyy. Where xx provides 100 numbers to uniquely identify the planar type and yy provides 100 numbers to uniquely identify the test that failed. For the definition of xx, please refer MODEL ID definitions. xx will identify a failing CPU planar or a failing IO planar. If it is not clear which planar is causing the problem, the OCS will identify the FRU with the highest probability of causing the known error. The definition of xx is as follows: xx System 39 340 38 350 60 Sacasil ??? 86 Sacasil ??? 65 Porcupine ??? The definition of yy is as follows: yy FRU Description 60 I/O Missing EPOW connector 27 CPU Bad CRC on 87C51FC Eprom 23 I/O Bad CRC on OCS NVRAM space 25 I/O Bad CRC on the Time of Day (TOD) RAM 03 CPU Model ID not found 04 CPU COP Buss Address (CBA) not found 06 CPU COP Buss Address (CBA) not found in Seed / Signature area 11 CPU Fatal Built In Self Test (BIST) error 87 CPU Can't find DD level of chip in logout area 12 CPU Checkstop occured, but can't logout state of machine 13 CPU 3 Checkstops have occured If a BIST error occurs, the SRN will be followed by a 'ccc 104'. The 'ccc' indicates that there is more information available, and the '104' indicates that the information that follows relates to an OCS BIST failure. Bist failures are indicated by the chip COP Buss Address followed by the failure code. The format for each chip that fails BIST operation is as follows: xxx cyy... where xxx is the Cop Buss Address of the failing chip and yy is the actual failure encountered. The 'c' has no meaning presently. COP BUSS ADDRESSES (xxx): The chips supported are: DCU0 = 010 COMBO1 = 029 FPU = 001 SLA1 = 077 DCU1 = 042 COMBO2 = 061 FXPT = 002 SLA2 = 109 DCU2 = 074 IOCC1 = 093 ICU = 003 DCU3 = 106 IOCC2 = 125 SCU = 004 XIO1 = 205 XIO2 = 237 BIST FAILURES (cyy): The following failures that can occure are: 0 No failure at all 1 DC Logic Self Test failed 2 AC logic self test failed 4 Array self test failed 8 The DD level could not be determined 16 The chip is not present or responding on the COP Buss 32 An equipment incompatibility exists between this chip and another Any combination of these failures are possible and are displayed in the decimal radix by the OCS as a BIST failure. For example, suppose a chip passes AC Logic Self Test (ACLST) but failed Array Self Test (AST), then the fail code displayed would be a 04. If the chip failed both ACLST and AST, then the fail code would be 06. EXAMPLES: 1) Error: Missing EPOW connector on 350 Sequence of numbers : 888 103 123 860 888 103 123 860 ... 2) Error: Bad CRC on Time of Day (TOD) RAM of Sacasil Sequence of numbers : 888 103 128 625 888 103 128 625 ... 3) Error: BIST failures on Porcupine ICU chip failed AST (003 c04) FPU chip failed ACLST and DD level could not be determined (001 c10) DCU1 chip not responding on the COP Buss (042 c16) Sequence of numbers : 888 103 126 511 ccc 104 003 c04 001 c10 042 c16 ... 888 ... ----------------------------------------------------------------------- The new service request numbers are of the form 140 000 to 149 999 displayed as 14x xyy. Where xx provides 100 numbers to uniquely identify the planar type and yy provides 100 numbers to uniquely identify the test that failed. For the definition of xx, please refer MODEL ID definitions. xx will identify a failing CPU planar or a failing IO planar. If it is not clear which planar is causing the problem, the OCS will identify the FRU with the highest probability of causing the known error. The definition of xx is as follows: xx System 39 340 38 350 60 Sacasil ??? 86 Sacasil ??? 65 Porcupine ??? The definition of yy is as follows: Release 1 LED's Revised Flashing "888" LED's 211 888 103 14x x11 c01 100 200 212 888 103 14x x12 c01 100 200 214 888 103 14x x14 c01 100 200 300 400 c02 100 200 215 888 103 14x x15 c01 100 200 c02 100 200 300 400 290 888 103 14x x90 c01 100 200 c02 100 200 300 400 297 888 103 14x x97 c01 100 200 TCW SIMM FRU failure 888 103 14x x94 c01 100 200 300 420 ----------------------------------------------------------------------- INSTALL LED SEQUENCE -- AIX 3.2 -- Manufacturing Test During the boot-up and installation of AIX during the manufacturing test process, the 3-digit LED is used to indicate process status. This guide explains what the LEDs indicate. DISKETTE BOOT PROCESS Boot off the diskette :u: This LED indicates a catastrophic failure. During diskette boot, it is probably indicative of a memory, CPU, or I/O slot problem. U3 This is indicative of an unknowen or unexpected failure. On early 340 models, it has been caused by corruption of data during parallel port transfer. ********************************************************************* U1 Running preconfiguration 01C - CFGMGR -f -d successful 02C - CFGMGR -f -d failure This step sets up the database that AIX uses to keep track of which devices are in the system. 010 - Swap out 1st boot diskette, insert 2nd boot diskette 0C0 - Wrong diskette inserted C03 - Reading 2nd boot diskette C04 - Setting up base devices 3C - ODMADD successful 4C - ODMADD failure This step sets up the serial and parallel ports in the device database. 5C - CFGMGR -s -d successful 6C - CFGMGR -s -d failure This step runs the configuration manager so that the serial and parallel ports runs as required. 7C - mkdev of tty0 successful 8C - mkdev of tty0 failed This step sets up serial port #1. 9C - mkdev of tty1 successful 10C - mkdev of tty1 failed This step sets up serial port #2. Serial port #2 is used to communicate with the tester. 11C - MFGCONF successful 12C - MFGCONF failure This step configures the parallel port for AIX download. 13C - SYSINFO.MFG file made successfully 14C - STSINFO.MFG file make failed CCC - Attempt to send message 0 to the tester Message 0 is a message from the system which says to the tester, "Hey, I'm alive! What do you want me to do?". C00 - Message 0 acknowledge received from tester A C00 on the LED display indicates that the system received an acknowledge from the tester. C11 - Received message 11 from tester A C11 means that the system received a message 11 from the tester. This means that the tester is ready to send the AIX2 file to the system. C01 - Attempt to send message 01 to tester A C01 led means that the system is sending a message 01 to the tester. Message 01 means "go ahead, send me that AIX file". C02 - Running the AIX install program 19C - Configuring hardfiles 20C - Cannot "find" any hardfiles 21C - MKROOTVG successful 22C - MKROOTVG failure This step sets up the root logical volume. In other words, the install code is setting up the initial subdirectories on the primary hardfile. 23C - DELETELVS successful 24C - DELETELVS failure This step cleans up the hardfiles in preparation for the AIX load. 25C - CREATELVS successful 26C - CREATELVS failure This step creates the logical volume system. In other works, other subdirectories are being set up on one or more hardfiles. 27C - POPLVS successful 28C - POPLVS failure This step sets up the file system. In other words, set up some parameters for the newly built subdirectories. CCC - Attempt to send message 0 to the tester Message 0 is a message from the system which says to the tester, "Hey, I'm alive! What do you want me to do?". C00 - Message 0 acknowledge received from tester A C00 on the LED display indicates that the system received an acknowledge from the tester. C11 - Received message 11 from tester A C11 means that the system received a message 11 from the tester. This means that the tester is ready to send the AIX3 file to the system. C01 - Attempt to send message 01 to tester A C01 led means that the system is sending a message 01 to the tester. Message 01 means "go ahead, send me that AIX file". C02 - Running the AIX install program 29C - MKBOOT successful 30C - MKBOOT failure This step creates the section of code which will allow the system to reboot off the hardfile after the yellow button is pushed. 31C - DD wrote boot image to boot logical volume 32C - DD failure This step writes the bootable section of code to the primary hardfile. 33C - MKBOOT updated NORMAL IPL list successfully 34C - MKBOOT failed to update NORMAL IPL list This step updates information on the primary hardfile required for the hardfile reboot when the keylock is in the normal position 35C - MKBOOT updated SERVICE IPL list successfully 36C - MKBOOT failed to update SERVICE IPL list This step updates information on the primary hardfile required for the reboot when the keylock is in the service position 37C - BOOTLIST updated NORMAL NVRAM IPL list successfully 38C - BOOTLIST failed to update NORMAL NVRAM list This step updates information in the NVRAM required for the hardfile reboot when the keylock is in the normal position 39C - BOOTLIST updated SERVICE NVRAM IPL list successfully 40C - BOOTLIST failed to update SERVICE NVRAM list This step updates information in the NVRAM required for the hardfile reboot when the keylock is in the normal position CCC - Attempt to send message 0 to the tester Message 0 is a message from the system which says to the tester, "Hey, I'm alive! What do you want me to do?". C00 - Message 0 acknowledge received from tester A C00 on the LED display indicates that the system received an acknowledge from the tester. C12 - Received message 12 from tester A C12 means that the system received a message 12 from the tester. This means that the tester is telling the system to prepare for a reboot. 666 - Ready for reboot HARDFILE BOOT PROCESS Boot off the primary hardfile LY Note: Many of these steps are identical to the diskette boot process 01C - ODMCREATE successful (Same as diskette boot) 02C - ODMCREATE failure (Same as diskette boot) 03C - ODMADD successful (Same as diskette boot) 04C - ODMADD failure (Same as diskette boot) 05C - CFGMGR -f -d successful (Same as diskette boot) 06C - CFGMGR -f -d failure (Same as diskette boot) 07C - Found the boot disk 08C - Can't find boot disk 09C - IMPORTVG successful Define the hardfile logical 10C - IMPORTVG failure characteristics to the LVM. 11C - VARYONVG successful "Turn on" the hardfile 12C - VARYONVG failure 13C - FSCK successful Check the file system 14C - FSCK failure 15C - ODMADD TTY successful Add the serial device to the 16C - ODMADD TTY failure device database. 17C - CFGMGR -s -d successful Configure the serial device 18C - CFGMGR -s -d failure 19C - CHGCONS tty0 successful Further configure the TTY device 20C - CHGCONS tty0 failure 21C - CFGCON successful More serial port 22C - CFGCON failure configuration 23C - MKDEV tty successful Create the TTY device 24C - MKDEV tty failure 25C - MFGCONF successful Configure other devices 26C - MFGCONF failure 33C - ODMDELETE successful Delete previous hardfile 34C - ODMDELETE failure information 31C - ODMADD scsidev successful Set up hardfiles 32C - ODMADD scsidev failure ----------------------------------------------------------------------- The following was extracted from AIXTIPS and totally copied here. To obtain AIXTIPS on VNET use the TOOLS command such as: TOOLS SENDTO MUNIVM4 AIXTOOLS AIXDOC GET AIXTIPS NEWSLOG TOOLS SENDTO MUNIVM4 AIXTOOLS AIXDOC GET AIXTIPS NEWS90T TOOLS SENDTO MUNIVM4 AIXTOOLS AIXDOC GET AIXTIPS NEWS91T To subscribe to AIXTIPS updates use: TOOLS SENDTO MUNIVM4 AIXTOOLS AIXDOC SUB AIXTIPS NEWS >(U)92039. LED Codes on the /6000 Another good one from the internet (comp.unix.aix). The text is a lot more than 80 columns wide at the end| >From richard@kunikpok.UUCP (Richard A. Hasting Jr) Newsgroups: comp.unix.aix Subject: LED 552 INFO Date: 28 Jan 92 19:56:54 GMT Organization: Kunikpok Kennels & Komputers I got over a dozen requests for this, and since I would prefer that everyone have _ALL_ the facts, I will post this. I have seen an awful lot of misinformation, and some good and poor assumptions on what causes the machine to fail on booting up with whatever LED codes. The Table of contents are as follows LED 201 LED 223-229 LED 551 LED 552 LED 553 LED C99 LED C31 Article on using /etc/continue from the bosboot diskettes and bootable tapes Print it out because you won't be able to get to it when you need it otherwise. Changed 12/03/91 LED 201 Procedures verified on AIX 3.1.5 If a 6000 stops at led 201 during boot it may be due to either a software problem or a hardware problem. Most likely a software problem. If the leds first go past 299, and then back to 201 -- it's most likely a corrupted boot logical volume (a software problem). If the leds never get to 299 - it can't be software because the boot process hasn't yet loaded any software, so it's time to suspect hardware. Resolution to SOFTWARE problem: The corruption of the boot logical volume will usually occur if the /(root) or /tmp filesystems are full when the bosboot command is run. Bosboot is run during installation of updates. The following procedure can be used to correct this problem. - With the key in the 'SERVICE' position, boot from your installation media - Select option 5 from the installation menu - Type the following commands to vary on the root volume group /etc/continue hdisk0 - Correct the out of space condition Use 'df' to check for free space in /dev/hd4 and /dev/hd3. Erase files as necessary to correct the problem. - Create the new boot image. bosboot -a -d /dev/hdisk0 - Place the key in 'NORMAL', execute the following command shutdown -Fr Resolution to HARDWARE problem: The hardware problem of the led 201 is commonly due to a hardware problem with the system planar. The hardware issued a check stop error during boot because of a detected hardware problem. Usually the error log will contain an entry for the check stop. You should go ahead and try the software procedures just in case but be prepared to have a CE brought into the picture. The CE should contact L2 hardware support. The hardware guys are supposed to be aware of the problem. LED 223 - 229 1. boot in service mode off bosboot diskettes 2. choose option 5 3. run /etc/continue hdisk0 4. run bootlist -m normal hdisk0 5. reboot in normal mode with the "shutdown -Fr" command June 13, 1991 LED 551 SYSTEM RECOVERY There are several reasons for an LED 551: PROBLEM Solution _____________________________________________________________________________ /dev missing, or corrupted - mkdir /dev /bin empty or missing - reinstall bad boot logical volume - bosboot -a /etc problems - restore selective files if possible, or reinstall corrupted filesystems - fsck /dev/hd4 as per LED552 a bad install of the system - install AIX properly ********************************************************************** LED 552 SYSTEM RECOVERY There are, so far, several known causes, of the 552 LED upon IPL. One is bad savebase information. The second is the the log logical volume (hd8) has somehow gotten corrupted. The third is that the odm may be corrupted. To diagnose and fix a 552, I recommend these not always so simple steps: 1) Boot from bosboot diskette or tape and get to install/maint menu - Key in service position 2) choose option 5 3) run "/etc/continue hdisk#" - Check out the article on "running /etc/continue" 4) If there are any mounted filesystems (whether /etc/continue ran cleanly or not) unmount them. To check for mounted filesystems, issue the following command. # mount If /dev/ram0 is the only mounted filesystem, then goto step 5. If /dev/hd4 is mounted onto /mnt then # umount all # mount If /dev/hd4 is still mounted, then execute the following instructions # exit; # umount all # mount (The only mounted filesystem should be /dev/ram0 on /) 5) Now run fsck on the following filesystems: # fsck -y /dev/hd1 # fsck -y /dev/hd2 # fsck -y /dev/hd3 # fsck -y /dev/hd4 If this fails, or the logredo process fails, or indicates any filesystems with unknown log record type then go to step 6, else go to step 7. 6) run "/etc/aix/logform /dev/hd8" Answer YES to the question asking if you want to destroy your LOG. Logform will reformat the log logical volume. repeat step 5. 7) reboot - Key in normal position 8) If LED 552 still persists, then repeat steps 1-3, and make certain that you have chosen the proper drive that has hd5 on it. Then, goto Step 9. 9) execute the # mount command, and you should have /dev/ram0, /dev, /dev/hd4, /dev/hd2 and /dev/hd3 all mounted. If they are all there, goto step 10. If not, then run # fsck -y /dev/hd# where # is the number that matches the missing filesystem. If it gives you an error message that it could not read block 8, then the filesystem is most likly unrecoverable. If you get a bad argument error, then run # dd count=1 bs=4k skip=31 seek=1 < /dev/hd[N] > /dev/hd[M] where [N] is a working logical volume number, and [M] is the LV that fsck is failing on. then run # fsck /dev/hd# again. if it still fails, then that filesystem is unrecoverable, and needs to be recreated. hd2 and hd3 can be recreated, hd4 will require a reinstall. If hd3 is missing, then run * # lsvg -l rootvg * NOTE the number of PP's on the /dev/hd3 * # rmlv -f /dev/hd3 * # mklv -y'hd3' rootvg N * (N is the number of PP's in the Logical volume) If hd2 is the volume missing then you will need to have a backup of /usr handy. run % # lsvg -l rootvg % NOTE the number of PP's on the /dev/hd2 * # rmlv -f /dev/hd2 * # mklv -y'hd3' rootvg N * (N is the number of PP's in the Logical volume) * # mount /dev/hd2 /usr * # restore -xvdf/dev/rmt0 ./usr * (This assumes that there are no filesystems under /usr. Your milage may * differ) If /dev/hd4 has the bad super block, then you will need to install AIX on that system again. 10) set the TERM variable to the proper terminal type for your console. # export TERM=hft (or ibm3151 or vt100... whatever you happen to be running) Using your favorite editor, modify the /etc/rc.boot4 file. Change # bring up the root volume group /etc/ipl_varyon -v if $? ^= 0 then while : do showled 0x552 done fi ----- TO # bring up the root volume group /etc/ipl_varyon -v RC=$? if $RC ^= 0 then while : do showled 0x552 sleep 1 showled $RC sleep 1 done fi 11) Save the file, and run # bosboot -a 12) Next, if you don't have a lot of system configuration (tty's really), then run # mkdir /etc/objrepos/bak # cp /etc/objrepos/Cu* /etc/objrepos/bak # cp /etc/objrepos/boot/Cu* /etc/objrepos # savebase 13) Reboot in Normal mode again. 14) If LED 552 persists you should also have the return code from ipl_varyon in the LED. If that value is 2, 3, 4, 8, or 9 and you did not perform step #12, then do so. If you get a value of 6, 7, 8, or C, then go to step 15 If you get a value of A, then check /etc/drivers/hd_pin because it cannot be loaded. If the value is B, then the IPL record is bad, and this may be unrecoverable, we haven't figured out how to fix that one yet. Call us up, and we'll work on it with you. It is caused by an invalid IPL record on the volume group. 15) You got here because ipl_varyon failed to either open, or modify the /dev/ipldevice entry. This may be due to a bad boot LV, or because of a bad ODM. Most likly, it is a problem with the ODM. Perform step 12, if you haven't yet done so. ********************************************************************** LED 553 The system will stop during IPL with 553 in the LEDs if init has a problem running or in reading the inittab file. This will often occur when the /tmp or the / filesystem is full. The following procedure can be used to correct this problem. - With the key in the 'SERVICE' position, boot from your installation media - Select option 5 from the installation menu - Type the following command to vary on the root volume group /etc/continue hdisk0 - check for and correct an out of space condition Use 'df' to check for free space in /dev/hd4 and /dev/hd3. Erase files as necessary to correct the problem. Suspect /smit.log and /smit.script as being the problem. - Check the /etc/inittab for corruption: Usually it will be empty, or missing or have an entry in it that is not correct: - If inittab is corrupted then do the following: - Create the /etc/inittab file using your favorite editor. You must set your TERM environment variable using commands similar to the following prior to starting the editor. # export TERM=hft - if the inittab file was ok, then check the following files for any modification or permissions problem: /etc/environment /bin/sh /bin/bsh /etc/fsck missing or corrupted. This can be copied from the ram filesystem /etc/brc /etc/profile /.profile - Place the key in 'NORMAL', execute the following command shutdown -Fr Sample inittab : (#)inittab 1.22 com/cfg/etc,3.1,9021 4/6/90 17:18:07 init:2:initdefault: brc::sysinit:/etc/brc >/dev/console 2>&1 # Phase 2 of system boot rc:2:wait:/etc/rc > /dev/console 2>&1 # Multi-User checks srcmstr:2:respawn:/etc/srcmstr # System Resource Controller rctcpip:2:wait:/etc/rc.tcpip > /dev/console 2>&1 # Start TCP/IP daemons cons:0123456789:respawn:/etc/getty /dev/console piobe:2:once:/bin/rm -f /usr/lpd/pio/flags/* # Clean up printer flags files cron:2:respawn:/etc/cron qdaemon:2:once:/bin/startsrc -sqdaemon writesrv:2:once:/bin/startsrc -swritesrv It has been found that at times, fsck will show a problem with /dev/hd4 (root), following the fsck procedure outlined in the 552 fix has worked to fix the problem when the more obvious items concerning inittab and a full filesystems, etc do not appear to be the problem. (Thanks to Per Schwensen for the update) LED C99 The LED C99 is usually caused by a bad /usr/bin/odmget command. /usr may be missing, or the /etc/filesystems file may be corrupted. 1) Boot from bosboot diskette or tape and get to install/maint menu - Key in service position 2) choose option 5 3) run "/etc/continue hdisk#" - Check out the article on "running /etc/continue" 4) Check to see if /etc/filesystems has the /usr filesystem in it. 5) use the mount command to check to see if /usr is mounted. 6) # cd /usr/bin If the command fails, then /usr/bin needs to be restored. 7) # ls -l /usr/bin/odmget If there is no odmget, then check to see if other files are missing from /usr/bin. LED C31 1) Boot from bosboot diskette or tape and get to install/maint menu - Key in service position 2) choose option 5 3) run "/etc/continue hdisk#" - Check out the article on "running /etc/continue" 4) chcons -a login=enable /dev/hft/0 5) reboot in normal mode. 6) If you still have LED C31, then repeat step 1-3, and goto step 7. 7) Next, # mkdir /etc/objrepos/bak # cp /etc/objrepos/Cu* /etc/objrepos/bak # cp /etc/objrepos/boot/Cu* /etc/objrepos # savebase Article on /etc/continue: 1) lqueryvg -? : Provides you the valid options and syntax 2) lqueryvg -p hdisk? -At : Provides you LV names, numbers and LV STATES 3) getlvodm -P : To aquire the association of the hdisk_name with the hdisk PVID 4) lquerypv -p PVID -N hdisk# -At grep LVID : Lists in column format (from L to R) PVID STATUS LVID EXTENSION LP# ----------------------------------------------------------------------------- The above commands should be run PRIOR to executing /etc/continue from maintenance mode if you find that you are having problems getting filesystems to mount or are getting error messages executing /etc/continue that may be related. The reason for this is that the Installation/Maintenance Diskettes will assign an hdisk name to a PV that may/will be different from the names the customer is familiar with when booted in Multi User Mode. I will illistrate the command and its output providing information that will be needed to help determining many things prior to executing /etc/continue. The order in which the illistration is given should be the order in which the commands should be executed, Most of the time. NOTE: that if you are working with a 552 LED then this procedure will provide you with the hdisk name for the command 'bosboot -a -d hdisk?' START: 1) Your first step is to locate PV's that are part of the rootvg. To do this GOTO step 2. *) After issuing the command 'getlvodm -P' write down all the hdisk_names associated with the rootvg. This command will show the VG's the hdisk(s) with the rootvg. This command will show the the VG's the hdisk(s) are associated with only if importvg and varyonvg have already been run. (ie. after /etc/continue) Otherwise this command is good to see if the system recognizes any hard drives. 2) Now you will need to find out which PV contains hd5 (blv) GOTO step 3 * ) After issuing the command 'lqueryvg -p hdisk? -At' look for hd5 and write down the LVID number (ie. 00000503b567e4.3). Its this number you the LVID number (ie. 00000503b567e4.3). Its this number you will have to will have to search for in the next step. 3) Now the goal is to find out which PV the hd5 LV resides on. Once you find this you, will know which Hdisk_name to supply the /etc/continue command GOTO step 4 * ) NOTE: You do not have use of the 'pg' command. Use Ctrl-s and Ctrl-q to scroll. You will issue the 'lquerypv -p PVID -N hdisk_name -At' once for each hdisk associated with the rootcg until you spot the LVID for hd5 on the output. ----------------------------------------------------- First: # lqueryvg -? lqueryvg: illegal option -- ? Usage: lqueryvg -g VGid -p PVname -NsFncDaLPAvt ----------------------------------------------------- Second: # getlvodm -P +------------------------------------------- hdisk_name | +----------------------- PVID | | +-------- VG_Name +--+--+ +-------+------+ +--+--+ hdisk0 00000305b28a03e1 rootvg hdisk1 00000305b23ff460 rootvg ----------------------------------------------------- Third: # lqueryvg -p hdisk0 -At Max LVs: 256 PP Size: 22 Free PPs: 43 LV count: 11 PV count: 2 Total VGDAs: 3 +----------------------- Logical Volume Identifier (LVID) | +------------- Minor device number (see /dev) | | +-------- Logical Volume Name (LVN) | | | +----- LV state | | | | C ( 0 indicates LV is not defined | | | | to a VG ) | | | | C ( 1 indicates LV is defines to a | | | | VG ) | | | | \ ( 2 indicates LV has stale | | | | logical partitions ) +------+-------+ Logical: 00000305b2403191.1 hd6 1 00000305b2403191.2 hd61 1 00000305b2403191.3 hd5 1 00000305b2403191.4 hd7 1 00000305b2403191.5 hd8 1 00000305b2403191.6 hd4 1 00000305b2403191.7 hd2 1 00000305b2403191.8 hd3 1 00000305b2403191.9 hd1 1 00000305b2403191.10 paging00 1 00000305b2403191.11 lv00 1 +-------------- Number of VGDA's | +---------- State Physical: 00000305b28a03e1 2 0 00000305b23ff460 1 0 +---+--+ | +--------------------------------------- Type of H.W. (See uname -m) ----------------------------------------------------- Fourth: /* Note this command is run once for each PVID the customer has */ /* Make sure you change the hdisk_name to match the PVID number */ /* See the "getlvodm -P" command for PVID's and hdisk_names */ /* See "lqueryvg -p hdiskX -At" for LVID's */ # lquerypv -p PVID -N hdisk_name -At grep LVID PP Size: 22 PV State: 0 Total PPs: 76 Alloc PPs: 38 Total VGDAs: 2 +---------------------------------- PVID | +------------------------- Minor Device number of a LV | | +------------------BD (0 indicates PP is free) | | | | | | CD (1 indicates PP is | | | allocated) | | | CD (2 indicates PP has stale | | | data) | | | D (4 indicates PP is being | | | resynced) | | | ( See lvm.h ; PP STATES ) | | | +----------------------------- ---------- LVID.VGID | | | | +-------------------- ---------- Minor Device number of a LV | | | | | +---------------- ---------- LV number | | | | | | +-- ---------- 1st Alt Volume ID's | | | | | | | +--- Minor Device number of a LV | | | | | | | | 2nd Alt Volume ID's | | | | | | | | | +-------+------+ +-------+------+ +-------+-- ----+ +-------+------+ PVMAP: 00000305b28a03e1:1 1 ODMtype 00000305b2403191.3 1 00000000000 00000:0 0000000000000000:0 PVMAP: 00000305b28a03e1:2 1 ODMtype 00000305b2403191.3 2 00000000000 00000:0 0000000000000000:0 PVMAP: 00000305b28a03e1:3 1 ODMtype 00000305b2403191.4 1 00000000000 00000:0 0000000000000000:0 PVMAP: 00000305b28a03e1:4 1 ODMtype 00000305b2403191.4 2 00000000000 00000:0 0000000000000000:0 PVMAP: 00000305b28a03e1:5 0 ODMtype 0000000000000000.0 0 00000000000 00000:0 0000000000000000:0 PVMAP: 00000305b28a03e1:6 0 ODMtype 0000000000000000.0 0 00000000000 00000:0 0000000000000000:0 PVMAP: 00000305b28a03e1:7 0 ODMtype 0000000000000000.0 0 00000000000 00000:0 0000000000000000:0 PVMAP: 00000305b28a03e1:8 0 ODMtype 0000000000000000.0 0 00000000000 00000:0 0000000000000000:0 PVMAP: 00000305b28a03e1:9 0 ODMtype 0000000000000000.0 0 00000000000 00000:0 0000000000000000:0 PVMAP: 00000305b28a03e1:10 0 ODMtype 0000000000000000.0 0 00000000000 00000:0 0000000000000000:0 PVMAP: 00000305b28a03e1:11 0 ODMtype 0000000000000000.0 0 00000000000 00000:0 0000000000000000:0 ====================================================================== | >(U)92372. How can I find out which model of RS/6000 am I logged on ?? | | Yet another list of model numbers :-) | | Here's all the current model numbers as decoded from: | | uname -m | cut -c7-8 | | Thanks to D. Ranz from IBM Detroit for all the real work to collect the | model/id pairs. | | Product/Model Model ID | Number | | 7016/730 10 | 7013/530 10 | 7013/540 11 or 14 | 7013/530H 18 | 7013/550 1C | 7015/930 20 | 7015/950 2E | 7015/950E 2E | 7013/520 30 | 7012/320 31 | 7012/320H 35 | 7012/340 37 | 7012/350 38 | 7011/220 41 | 7013/560 5C | 7015/970 63 | 7015/980 64 | 7015/580 66 | | ---- | | From the numbers Marc Pawliger gave (thank you) I wrote a little | shell script (using awk associative arrays) that will print | the machine type if it is in the list Marc gave. | Otherwise will return "Unknown Machine". | | I tried it on 220, 520, 530, 530H, 550, 950E and it works. | | You can update this script if you will know a new machine | will born (or if something in the list is wrong) just adding lines | like: | | m "code"Y="MachineType"; | | to the end of the list. | | Hope this will help, G.Vitillaro | | ==== cut here ======================================================== | #!/bin/sh | # | # Author G. Vitillaro (peppe@ipgaix.unipg.it) | # from an idea of Marc Pawliger (marc@ibmpa.awdpa.ibm.com) | # | # 10/12/92 GVT First (and last) implementation | # | # machine : will get machine type on RISC/6000 | # | # | awk ' | BEGIN { | m "10"Y="7013/530 or 7016/730"; | m "11"Y="7013/540"; | m "14"Y="7013/540"; | m "18"Y="7013/530H"; | m "1C"Y="7013/550"; | m "20"Y="7015/930"; | m "2E"Y="7015/950"; | m "2E"Y="7015/950E"; | m "30"Y="7013/520"; | m "31"Y="7012/320"; | m "35"Y="7012/320H"; | m "37"Y="7012/340"; | m "38"Y="7012/350"; | m "41"Y="7011/220"; | m "5C"Y="7013/560"; | m "63"Y="7015/970"; | m "64"Y="7015/980"; | m "66"Y="7015/580"; | if ( m codeY != "" ) | print "This RISC/6000 is a " m codeY; | else | print "Unknown Machine"; | } | ' code=`uname -m | cut -c9-10` < /dev/null | ==== cut here ======================================================== | ====================================================================== Subject: Checkstop This note is to inform all of the necessary people of an option that is available when a machine gets a checkstop. During the EVT Acceptance test of the Candy and Porcupine systems, several machines exhibited checkstop problems. One option to determining what causes a checkstop is to take a failing system and connect an ESP to it and try to recreate the problem. This can be time consuming and may prove nothing. The checkstop may not be easily reproduceable. Another option is to use an existing file on the system that obtained the checkstop. The file is "/usr/lib/ras/checkstop.A". The scenerio that occurs is this: 1) A system gets a checkstop. 2) The information that caused the checkstop is dumped into NVRAM. 3) The system re-IPL's. 4) The information from NVRAM is dump into the checkstop.A file. If multiple checkstops have occurred on the system, there is the possibility of having a second file "/usr/lib/ras/checkstop.B". There are only two possible files: checkstop.A and/or checkstop.B. This is a binary file that can be backed up to a diskette, etc. During RIOS Release 1, there was a program that existed that could decode this checkstop file to a useable format. Milton Miller has taken this program and revised it to support XIO based machines. The following steps have to be taken to use this program successfully. For example, a Porcupine machine gets a checkstop and re-IPL's. 1) Backup the /usr/lib/ras/checkstop.A file to diskette. 2) Have access to an ESP. 3) Connect the ESP to a similiar machine as the one that obtained the checkstop. In this example, a Porcupine. 4) Restore the file from diskette to a machine that has the program to decode it. 5) Decode the file. 6) Use the ESP to load the decoded information. My understanding is that the ESP loads the information back into the Porcupine system that is connected to the ESP. 7) Use the ESP to read the necessary information just as if the system attached to the ESP was the one that obtained the checkstop. This technique was used to determine that the Candy and Porcupine checkstops were caused by either DCU0 or DCU1. Milton Miller (at ext. 8-6025) has a much better understanding of this than I do. He has used this technique and even revised the program to accept XIO. I feel that any questions regarding how to obtain this program and/or use it, should be directed to him. Please forward this information on to anyone who you feel might need to know this. I hope this will help. Regards, Ken Pearson ext. 8-1418 Austin, Texas ====================================================================== This list was mainly stolen from numerous documents, modified to be sequential, and added from personal notes. Many thanks to those people that sent me soft and hard copies to collate into this one. To the best of my knowledge, the information here is accurate but not necessarially the latest, up to date version. This document should be considered IBM Internal Use Only because of internal code names and acronyms used. Interesting manuals to have on hand: SC23-2204-02 Problem Solving Guide SA23-2631-05 Diagnostic Programs : Operator Guide SA23-2632-05 Diagnostic Programs : Service Guide | SA23-2629-07 Service Request Number / Cross Reference / Ver 2.2 SA23-2643-01 Hardware Technical Reference / General Information SA23-2646-01 Hardware Technical Reference / OPtions and Devices Wally Tuten, TUTEN at AUSVM6 3.8.5 Location Identification