Page 1
Personal Computer Hardware Reference Library IBM RT PC Problem Determination Guide SA23-2604-0 P/N 22F9828...
Page 3
Personal ('anpuler II ardware R ef voice Library IBM RT PC Problem Determination Guide SA 23-2604-0...
Page 4
References in this publication to IBM products, programs, or services do not imply that IBM intends to make these available in all countries in which IBM operates. Any reference to an IBM licensed program in this publication is not intended to state or imply that only IBM's licensed program may be used.
Page 5
Safety CAUTION Before r em o v ing any cover or disco nnecting any signal cable, set the power sw itches on the system unit and all a ttach ed devices to Off; then unplug all external power cables from the outlets. This m anual c o n tain s “DANGER”...
Page 6
Safety Translations Problem D eterm ination Guide...
Page 10
Netzsteckdosen ziehen. Sieten A-12, A-14, A-16 und A-18 Ausbau und Einbau der Batterie beim IBM RT PC - Gefahr. Feuer-, Explosions- und Verbrennungsgefahr. Zelle nicht laden, zerrlegen, ueber 100 , Grad C erhitzen, keine Loetstelle direkt an der Zelle anbringen, Zelle nicht verbrennen oder den Inhalt mit Wasser in Beruehrung bringen.
Page 17
About This Book P u r p o s e This book is used to do problem determination on your IBM RT Personal Computer®. When you suspect there is a problem with the hardware this book should be used to find the failing device.
Page 18
A Reader's Comment Form and Book Evaluation Form are provided at the back of this book. Use the Reader's Comment Form at any time to give IBM information that may improve the book. After you become familiar with the book, use the Book Evaluation Form to give IBM specific feedback about the book.
Page 19
• To order from your IBM representative, use Order Number SBOF-1825. • To order from your IBM dealer, use Part Number 22F9800. A binder, tabs, wrap-plug bag, and diagnostic diskettes are included with the order. About This Book xvii...
Page 21
C om m unication U tilities ..............3-12 D iagnostic D iskette Copy U tility ..........3-13 IBM 9332 U tilities ................3-14 Appendix A. Locations and Examples ......A-l D iagnostic F unction Keys ...............A-2 Types of D isplays ...................A -3 D isplay Test P a tte rn s ................
Page 23
Section 1. Beginning Problem Determination Section 1. Beginning Problem Determination...
Page 24
CONTENTS About This Section ..Step 1. Symptom Index Step 2. System Inactive Problem Determination Guide...
Page 25
If a device or adapter has recently been installed, go to Section 9, “Checking out the Option Installation,” in the IBM R T PC Options to verify that the installation is correct. If the device Installation or adapter still fails, use this manual or the maintenance information provided with the device.
Page 26
S t e p 1. S y m p t o m I n d e x The symptom index is a list of system problems (described in terms of their symptoms) and the action for determining their cause. 1. Find the failure or symptom that most closely resembles your system failure.
Page 27
Symptom Action Obvious machine damage (noise, Go to “Step 1. Obvious Damage” on page 2-6. odor, smoke, heat, broken keys, broken covers, or similar failures) System will not turn on Go to “Step 2. Diagnostics” on page 2-9. You were sent here by the operating Go to “Step 2.
Page 28
Step 2. System Inactive If the system is on, but appears inactive and will not respond to the keyboard: 1. Turn off the system. 2. Wait about 1 minute. 3. Turn on the system. 4. After power-on self-test (POST) has completed, sign on the system.
Step 114. IBM 5151 Personal Computer Display ............. 2-58 Step 115. IBM 5151 Personal Computer Display ............. 2-59 Step 120. IBM 5154 Personal Computer Enhanced Color Display ......2-60 Step 121. IBM 5154 Personal Computer Enhanced Color Display ......2-61 Step 122.
Page 32
Step 161. IBM 5081 Graphics Display ............... 2-95 Step 162. IBM 5081 Graphics Display ............... 2-96 Step 163. IBM 5081 Graphics Display ............... 2-97 Step 164. IBM 5081 Graphics Display ............... 2-98 Step 165. IBM 5081 Graphics Display ............... 2-99 Step 166.
Page 33
About This Section This section provides you with steps for finding the failing hardware in your system. To successfully use this section, you must first use Section 1, “Beginning Problem Determination,” to find the area most likely to cause the problem. Before starting the procedures, make sure no other users are using the system.
Page 35
Dual Sided Diskette Drive in location B 16-66B Mouse 86-790 Keyboard 36-780 Keyboard LEDs 16-780 IBM 5151 Personal Computer Display 26-540 IBM 5154 Personal Computer Enhanced 26-580 Color Display IBM 6153 Advanced Monochrome Graphics 26-600 Display IBM 6154 Advanced Color Graphics...
Page 36
A6-800 IBM 5083 Model 12 Tablet IBM 5083 Model 1 Tablet Stylus A6-8A0 A6-7C0 IBM 5083 Model 11 and 12 Tablet Stylus IBM 5083 Model 1 Tablet Cursor A6-8B0 IBM 5083 Model 11 and 12 Tablet Cursor A6-7D0 Refer to the printer Printer documentation.
Page 37
Step 2. Di agnosti cs D iagnostic D isk ette Handling P rocedures The IBM RT PC Diagnostic Diskettes contain the diagnostic programs used to check out and test the system. Diagnostics 1 (DIAG-1) is the first diskette used. After the diagnostics are loaded, the system may prompt for another diskette to be inserted into a diskette drive.
Page 38
Before the diagnostics are loaded: 1. Check that the system and display power cables are plugged in. 2. Check that the keylock is unlocked. 3. Check that the display Brightness Control is turned up enough to see the screen. See Appendix A for locations. AIZAF002 DID THE ABOVE CHECKS FIND THE PROBLEM? STOP, you have completed these procedures.
Page 39
4. If an IBM 5085 is attached, turn off the 5085 power. 5. Turn off the system unit and wait for about 1 minute. 6. If an IBM 5085 is attached, turn the 5085 power on. Be sure the 5085 system diskette is in the 5085 diskette drive.
Page 40
Notes: a. Do not operate or move any device, unless instructed to do so, while diagnostics are running. b. The IBM Logo screen may display for a short time while the diagnostics are loading and checking the system configuration. 10. Wait about 4 minutes or until the DIAGNOSTIC OPERATING INSTRUCTIONS screen appears.
Page 41
Sw Keybd key. The Sw Keybd status light on the keyboard should now indicate PC mode. For more information on the 5085 see IBM 5080/R T PC Graphics System Operation IS THE “DIAGNOSTIC OPERATING INSTRUCTIONS” SCREEN DISPLAYED WITHOUT ANY OBVIOUS DISPLAY PROBLEMS? Read the screen and press Enter.
Page 42
Step 5. Function Selection After the DIAGNOSTIC OPERATING INSTRUCTIONS screen, the FUNCTION SELECTION menu is displayed. IS THE “FUNCTION SELECTION” MENU DISPLAYED? Press Enter. CONTINUE to the next page. Go to “Step 60. Keyboard” on page 2-43. 2-14 Problem Determination Guide...
Page 43
Step Diagnostic Selection If all options were found, the DIAGNOSTIC SELECTION menu is displayed. IS THE “DIAGNOSTIC SELECTION” MENU DISPLAYED? Go to “Step 11. Diagnostic Selection” on page 2-20. CONTINUE to next page. Section 2. Hardware Problems 2-15...
Page 44
Step 7. Test Option The TEST OPTION menu is displayed when an option that was previously recognized by the system is not found during Power-On Self-Test (POST). The option that was not found is listed in the TEST OPTION menu. IS THE “TEST OPTION”...
Page 45
Step 8. Test Option HAS THE OPTION LISTED ON THE “TEST OPTION” MENU BEEN EITHER REMOVED FROM THE SYSTEM, MOVED TO ANOTHER LOCATION, OR TURNED OFF? Choose ID 2. If the TEST OPTION menu is displayed again, repeat this step. CONTINUE to next page.
Page 46
Step 9. Diagnostic Test List If a new option is found or no fixed disks are found in the system unit, the DIAGNOSTIC TEST LIST menu is displayed. DIAGNOSTIC TEST LIST IS THE “DIAGNOSTIC TEST LIST” MENU DISPLAYED? CONTINUE to next page. Go to “Step 11.
Page 47
Step 10. Updating the Test List Before you can run the diagnostics, you must update the DIAGNOSTIC TEST LIST. 1. Read and follow the instructions as they appear on the screen. 2. If a list of options is displayed, compare your screen with the list of options for your system.
Page 48
S t e p 11. D i a g n o s t i c S e l e c t i o n The DIAGNOSTIC SELECTION menu is displayed after you select Diagnostic Routines or after you update the DIAGNOSTIC TEST LIST.
Page 49
Step 12. Test Method Selection The next menu displayed is the TEST METHOD SELECTION menu. 1. Read the item descriptions carefully. 2. Press Enter to run the test one time or type 2 to run the test multiple times. 3. Follow the instructions as they appear on the display to test the chosen device.
Page 50
Step 13. Completing the Tests When the test completes, you will see either the TESTING COMPLETE or THERE IS A HARDWARE PROBLEM IN YOUR MACHINE screen. If no problem was found, the TESTING COMPLETE screen is displayed. No trouble was found. STOP, you have completed the tests for this device.
Page 51
Step 14. Completing the Tests The diagnostics have found a problem with the system. Note: If a screen similar to the one below does not display or an unexpected error occurs (such as something is displayed in the two-digit display, the system hangs or loops, the keyboard does not respond, you cannot end a test, or a Diagnostic Error message is displayed), report Service Request Number (SRN) 16-986.
Page 52
Step 15. Additional Problems The problem may be one of the following: • Status lights on the keyboard do not work. Note: The lights can be checked by turning on the system unit and watching the lights during the Power-On Self-Test (POST). •...
Page 53
Step 16. Keyboard Lights, Beeper, or Two-Digit Display Failure 1. Get a Problem Summary Form from Appendix B of this manual. 2. Find the failing component in the following table. 3. Write the Service Request Number (SRN) for the failing component on item 4 of the form.
Page 54
Step 20. T w o - D i g i t Di s p l a y Look at the two-digit display. AIZAF005 IS TH E T W O -D IG IT D IS P L A Y B L IN K IN G ? Go to “Step 80.
Page 55
Step 21. Two-Digit Display Compare the number in the two-digit display with the numbers in the table below. IS THE NUMBER IN THE TABLE? Go to the step indicated in the table. CONTINUE to next page. Section 2. Hardware Problems 2-27...
Page 56
Step 22 Two-Digit Display IS THE “DIAGNOSTIC OPERATING INSTRUCTIONS” SCREEN DISPLAYED? CONTINUE to next page. Go to “Step 24. Two-Digit Display” on page 2-30. 2-28 Problem Determination Guide...
Page 58
2. Write the number shown on the two-digit display on item 3 of the form. Appendix B. Problem Summary Form Please complete the following information before calling IBM for service. Save the complete form for your service representative. Appendix B. Problem Summary Form B -l AIZAF007 CONTINUE to next page.
Page 59
S t e p 25. T w o - D i g i t D i s p l a y The tables on pages 2-31 through 2-35 list the numbers you may see in the two-digit display. 1. From the table below, Find the number you wrote on item 3 of the Problem Summary Form.
Page 60
Note that u is displayed in the upper half of the two-digit display. Two-Digit Service Request Unit to be Serviced Display Number or Problem or Problem Solution 11-100-84A-490 System Unit 11-84A System Unit 11-100-19B System Unit System Unit 11-F6C-84A 11-84A-100 System Unit 11-981-F6C-84A System Unit...
Page 61
12-200-240 System Unit 12-19B 12490 System Unit 12-340 System Unit 12-1 DC System Unit System Unit 12-1DD System Unit or IBM 6192 12-3C0 System Unit 11-8EA-100 11-18A-100 System Unit System Unit 12-310 System Unit or IBM 6192 12-230 System Unit...
Page 62
System Unit 12-1ED System Unit 12-100-8EA System Unit 12-100-18A System Unit 12-100 System Unit 32-780 Keyboard 12-100 System Unit 12-210 System Unit 12-800 System Unit 12-300 System Unit 12-3B0 System Unit or IBM 6192 11-F4A-100 System Unit 2-34 Problem Determination Guide...
Page 63
System Unit 11-8EA-100 11-18A-100 System Unit 12-850 System Unit System Unit 93‘ 12-64A-F80 12-FB0-F80 System Unit System Unit or IBM 6192 12-3 E X ) 16-986 System Unit Portable Disk Drive E2-5D0 Enclosure Portable Disk Drive E2-650 Enclosure 12-2E0 System Unit...
Page 64
Step 30. K e y l o c k If the keylock has not been unlocked, 99 is displayed in the two-digit display. AIZAF004 IS TH E K EY LO CK U N LO C K ED ? CONTINUE to next page. Unlock the keylock and go to “Step 3.
Page 66
S t e p 40. D i s k e t t e The diagnostic diskette may not be correctly inserted in the drive. IS TH E D IS K E T T E IN S E R T E D PR O P E R L Y ? CONTINUE to next page.
Page 67
S te p 41. D i s k e t t e 1. Get a Problem Summary Form from Appendix of this manual. 16-F80-64A 2. Write the Service Request Number on item 4 of the form. 3. Have the system unit serviced. Appendix B.
Page 68
S t e p 50. P o w e r AIZAF011 IS TH E P O W E R -O N IN D IC A T O R L IG H T E D ? Go to “Step 70. Diskette” on page 2-44. Y ES CONTINUE to next page.
Page 69
S t e p 51. P o w e r Check that the system is plugged into the wall outlet and power is available at that outlet. You can use a lamp to test the outlet. IS T H E P O W E R -O N IN D IC A TO R LIG H T E D ? STOP.
Page 70
Step 52. P o w e r 1. Get a Problem Summary Form from Appendix B of this manual. 2. Write the Service Request Number 16-880 on item 4 of the form. 3. Have the system unit serviced. Appendix B. Problem Summary Form 2-42 Problem Determination Guide...
Page 71
S t e p 60. K e y b o a r d 1. Get a Problem Summary Form from Appendix B of this manual. 2. Write the Service Request Number 36-780 on item 4 of the form. 3. Have the keyboard serviced. Appendix B.
Page 72
Step 70. Diskette Look at the upper left corner of the display. IS “DCP” DISPLAYED? CONTINUE to next page. Go to “Step 72. Diskette” on page 2-46. 2-44 Problem Determination Guide...
Page 73
S t e p 71. D i s k e t t e 1. Get a Problem Summary Form from Appendix B of this manual. 2. Write the Service Request Number on item 4 of this 16-64A-F80 form. 3. Have the system unit serviced. Appendix B.
Page 74
Step 72. Diskette It is possible that the diagnostic programs could not load from the diskette drive. If the program was unable to load from the diskette, the system may have loaded from the fixed disk. IS THE SCREEN ON YOUR DISPLAY YOUR USUAL OPERATING SYSTEM SIGN-ON SCREEN? CONTINUE to next page.
Page 75
S t e p 73. D i s k e t t e Check that the diagnostic diskette is inserted correctly in the diskette drive. IS TH E D IS K E T T E IN S E R T E D C O RR EC TLY ? CONTINUE to next page.
Page 76
Step 74. D i s k e t t e 1. Get a Problem Summary Form from Appendix B of this manual. 2. Write the Service Request Number 16-64A-F80 on item 4 of the form. 3. Have the system unit serviced. Appendix B.
Page 77
Step 80. Blinking Two-Digit Display 1. Look at the two-digit display. 2. Compare the blinking number in the two-digit display with the numbers in the table below. Two-Digit Go to Step Display Number Go to “Step 81. Blinking Two-Digit Display” on page 2-50.
Page 78
S t e p 81. B l i n k i n g T w o - D i g i t D i s p l a y The diagnostic diskette may be damaged. Try a new diagnostic diskette. If you continue to have problems: 1.
Page 79
S t e p 82. B l i n k i n g T w o - D i g i t Di s p l a y 1. Get a Problem Summary Form from Appendix B of this manual. 2.
Page 80
Note: See Appendix A, “Locations and Examples,” for examples of the displays. Display Type Go to Step IBM 5151 Personal G oto “Step 110. IBM 5151 Computer Display Personal Computer Display” on page 2-54. IBM 5154 Personal Go to “Step 120. IBM 5154...
Page 81
16-490-410 Computer Display IBM 5154 Personal 16-410 Computer Enhanced Color E X splay IBM 6153 Advanced 16-430 Monochrome Graphics Display IBM 6154 Advanced Color 16450 Graphics Display IBM 6155 Extended 16470 Monochrome Graphics Display IBM 5081 Graphics 164A04B0 Display IS YOUR DISPLAY TYPE LISTED IN THIS TABLE? Report the Service Request Number (SRN) for your display.
Step 110. IBM 5151 Personal Computer Display Turn the Brightness and Contrast controls on the display fully clockwise. AIZAF022 DOES THE SCREEN HAVE A LIGHTED BACKGROUND? Go to “Step 112. IBM 5151 Personal Computer Display” on page 2-56. CONTINUE to next page. 2-54 Problem Determination Guide...
Page 83
User S e t u p G u id e , Go to “Step 115. IBM 5151 Personal Computer Display” on page 2-59. STOP. You have found the problem. Section 2. Hardware Problems...
Try to set the brightness and contrast to the desired level. AS06A047 IS THERE A PROBLEM WITH THE BRIGHTNESS OR CONTRAST? Go to “Step 115. IBM 5151 Personal Computer Display” on page 2-59. CONTINUE to next page. 2-56 Problem Determination Guide...
Step 120. IBM 5154 Personal Com puter Enhanced Color Display Check that the display Power control switch is in the on (clockwise) position. AS06A048 IS THE DISPLAY POWER-ON INDICATOR LIGHTED? Go to “Step 122. IB M 5154 Personal Computer Enhanced Color Display”...
Step 121. IBM 5154 Personal Computer Enhanced Color Display Check that the display is securely plugged into the wall outlet and that power is available at the outlet. Use a lamp to check the outlet. AIZAF021 DID YOU FIND THE PROBLEM? STOP, you have found the problem.
Step 122. IBM 5154 Personal Computer Enhanced Color Display 1. Turn off the system unit. 2. Turn the Brightness control fully clockwise. 3. Wait about 1 minute. AIZAF023 DOES THE SCREEN HAVE A LIGHTED BACKGROUND? CONTINUE to next page. Go to “Step 124. IBM 5154 Personal Computer Enhanced Color Display”...
Step 123. IBM 5154 Personal Computer Enhanced Color Display Turn the Brightness control fully counterclockwise. IS THE SCREEN DARK? Go to “Step 125. IBM 5154 Personal Computer Enhanced Color Display” on page 2-65. CONTINUE to next page. Section 2. Hardware Problems 2-63...
Step 124. I B M 5154 P e r s o n a l C o m p u t e r E n h a n c e d Color D i s p l a y 1. Get a Problem Summary Form from Appendix B of this manual. 2.
3. Set the Brightness and Contrast controls to the desired levels. AJZB214 DOES YOUR DISPLAY SCREEN RESEMBLE ANY OF THESE? CONTINUE to next page. Go to “Step 127. IBM .5154 Personal Computer Enhanced Color Display” on page 2-67. Section 2. Hardware Problems 2-65...
S t e p 127. I B M 5154 P e r s o n a l C o m p u t e r E n h a n c e d Color Di spl ay 1. Get a Problem Summary Form from Appendix B of this manual. 2.
Step 130. IBM 6153 Adv an ced Mo n oc h r om e Graphics Display Turn on the Raster Test Control by turning the Brightness and Raster Test control fully clockwise until it clicks. AIZAF028 DOES THE SCREEN HAVE A LIGHTED BACKGROUND? CONTINUE to next page.
Step 131. IBM 6153 Advanced Monochrom e Graphics Display Try to set the brightness to the desired level. AS06A053 IS THERE A PROBLEM WITH THE BRIGHTNESS? Go to “Step 137. IBM 6153 Advanced Monochrome Graphics Display” on page 2-75. Go to “Step 134. IBM 6153 Advanced Monochrome Graphics Display”...
Step 132. IBM 6153 Advanced Monochrom e Graphics Display Check that the display power cable is securely plugged into the system unit. See the for cover removal. User Setup Guide IS THE POWER CABLE SECURELY PLUGGED INTO THE SYSTEM UNIT? CONTINUE to next page.
Step 134. IBM 6153 Advanced Monochrom e Graphics Display Compare your display screen with those shown below. AJZB214 DOES YOUR DISPLAY SCREEN RESEMBLE ANY OF THESE? Go to “Step 137. IBM 6153 Advanced Monochrome Graphics Display” on page 2-75. CONTINUE to next page.
S te p 135. I B M 6153 A d v a n c e d M o n o c h r o m e G r a p h i c s Displ ay Check that the display signal cable is securely plugged into the system unit.
S te p 137. I B M 6153 A d v a n c e d M o n o c h r o m e G r a p h i c s Displ ay 1. Get a Problem Summary Form from Appendix B of this manual. 26-600-430 2.
Step 140. IBM 6154 Advanced Color Graphics Display Check that the display is turned on. AS06A054 IS THE DISPLAY POWER-ON INDICATOR LIGHTED? CONTINUE to next page. Go to “Step 143. IBM 6154 Advanced Color Graphics Display” on page 2-79. 2-76 Problem Determination Guide...
Step 141. IBM 6154 Adv an ced Color Graphics Display 1. Turn off the system unit. 2. Turn the On/Off and Brightness control fully clockwise. 3. Wait about 1 minute. AS06A054 DOES THE SCREEN HAVE A LIGHTED BACKGROUND? CONTINUE to next page.
3. Try to set the On/OfF and Brightness control to the desired level. AS06A054 IS THERE A PROBLEM WITH THE BRIGHTNESS? Go to “Step 148. IBM 6154 Advanced Color Graphics Display” on page 2-84. Go to “Step 145. IBM 6154 Advanced Color Graphics Display” on page 2-81.
Step 143. IBM 6154 Adv anced Color Graphics Display Check that the display ’ - wer cable is securely plugged into the system unit. for cover removal. User Setup Guide IS THE POWER CABLE SECURELY PLUGGED IN? CONTINUE to next page.
Step 144. IBM 6154 A d v a n c e d Color G r a p h i c s D i s p l a y 1. Get a Problem Summary Form from Appendix of this manual. 2. Write the Service Request Number 26-590 on item 4 of the form.
Step 146. IBM 6154 Adv an ced Color G r a p h i c s D i s p l a y Check that the display signal cable is securely plugged into the system unit. for cover removal. User S e t u p G u id e CONTINUE to next page.
Step 150. IBM 6155 Extended Monochrom e Graphics Display Check that the display power switch is on. AS06A055 IS THE DISPLAY POWER-ON INDICATOR LIGHTED? CONTINUE to next page. Go to “Step 153. IBM 6155 Extended Monochrome Graphics Display” on page 2-88.
Step 151. IBM 6155 Extended Mo n och ro me Graphics Display 1. Turn off the system unit. 2. Turn the Brightness and Contrast controls fully clockwise. 3. Wait about 1 minute. DOES THE SCREEN HAVE A LIGHTED BACKGROUND? CONTINUE to next page.
Step 152. IBM 6155 Extended Monochrom e Graphics Display 1. Turn on the system unit. 2. Wait about 4 minutes. 3. Try to set the brightness and contrast to the desired level. AS06A055 IS THERE A PROBLEM WITH THE BRIGHTNESS OR CONTRAST? Go to “Step 158.
Step 153. IBM 6155 Extended Mo no ch r om e Graphics Display Check that the display is plugged into the wall outlet and that power is available at the outlet. Use a lamp to check the outlet. AIZAF040 IS THE POWER CABLE SECURELY PLUGGED IN? CONTINUE to next page.
Step 155. IBM 6155 Extended Monochrom e Graphics Display Compare your display screen with those shown below. AJZB214 DOES YOUR DISPLAY SCREEN RESEMBLE ANY OF THESE? Go to “Step 158. IBM 6155 Extended Monochrome Graphics Display” on page 2-93. CONTINUE to next page.
Check that the display signal cable is securely plugged into the system unit. for cover removal. I B M R T P C User S e t u p G u id e IBM RT PC Extended Monochrome Graphics Display Adapter 16-Pin CONTINUE to next page.
Step 160. IBM 5081 Graphics Display Check that the display Power switch is on. IS THE DISPLAY POWER-ON INDICATOR LIGHTED? Go to “Step 162. IBM 5081 Graphics Display” on page 2-96. CONTINUE to next page. 2-94 Problem Determination Guide...
Page 123
S t e p 161. I B M 5081 G r a p h i c s D i s p l a y Check that the display is plugged into the wall outlet and that power is available at the outlet. Use a lamp to check the outlet. IS THE POWER CABLE SECURELY PLUGGED IN? Go to “Step 169.
1. Pull down the customer access door on the 5081 display. 2. Look at the four red failure indicators. AIZAF049 ARE ANY OF THE FOUR FAILURE INDICATORS LIGHTED? Go to “Step 169. IBM 5081 Graphics Display” on page 2-103. CONTINUE to next page. 2-96 Problem Determination Guide...
2. Press and hold the Brightness Override push button. Brightness Override Push Button AIZAF048 DOES THE SCREEN HAVE A LIGHTED BACKGROUND? Release the push button. CONTINUE to next page. Go to “Step 169. IBM 5081 Graphics Display” on page 2-103. Section 2. Hardware Problems 2-97...
Step 164. IBM 5081 Graphics Display Look at the 5081 display. AIZAF046 DOES THE SCREEN HAVE TEXT, RASTER, OR LIGHTED BACKGROUND? CONTINUE to next page. Go to “Step 168. IBM 5081 Graphics Display” on page 2-102. 2-98 Problem Determination Guide...
Note: Your model may have the Brightness control in a different location than the one shown. AIZAF047 WERE YOU ABLE TO ADJUST THE BRIGHTNESS TO THE DESIRED LEVEL? CONTINUE to next page. Go to “Step 169. IBM 5081 Graphics Display” on page 2-103. Section 2. Hardware Problems 2-99...
Step 166. IBM 5081 Graphics Display Compare your display screen with those shown below AJZB253 DOES YOUR DISPLAY SCREEN RESEMBLE ANY OF THESE? CONTINUE to next page. Go to “Step 168. IBM 5081 Graphics Display” on page 2-102. 2-100 Problem Determination Guide...
S t e p 167. I B M 5081 G r a p h i c s D i s p l a y 1. Get a Problem Summary Form from Appendix B of this manual. 16-610-4B0 2. Write the Service Request Number on item 4 of this form.
Step 168. IBM 5081 G r a p h i c s D i s p l a y 1. Get a Problem Summary Form from Appendix B of this manual. 2. Write the Service Request Number 16-4B0-4A0-610 on item 4 of this form.
S te p 169. I B M 5081 G r a p h i c s D i s p l a y 1. Get a Problem Summary Form from Appendix B of this manual. 2. Write the Service Request Number 16-610 on item 4 of this form. 3.
Step 200. System Attached to 5085 IBM 5085 front panel is shown below. IS YOUR SYSTEM ATTACHED TO A 5085? Go to “Step 202. Power On at 5085” on page 2-106. CONTINUE to next page. 2-104 Problem Determination Guide...
S te p 201. S y s t e m N o t A t t a c h e d to 5085 1. Get a Problem Summary Form from Appendix B of this manual. 2. Write the Service Request Number 32-780 on item 4 of the form. 3.
S t e p 202. P o w e r On at 5085 Check that the 5085 Power On/OfTswitch is on. AIZAF060 IS TH E 5085 P O W E R ON? CONTINUE to next page. Turn on the 5085 and go to “Step 3. Loading Diagnostics”...
S t e p 203. K e y b o a r d C o n n e c t i o n Check the keyboard connection to the Peripheral Connector Assembly (PCA). IS T H E K E Y B O A R D C O R R E C T L Y A T T A C H E D TO TH E PCA? CONTINUE to the next page.
Step 204. Y Cable Connection Be sure the Y cable is properly connected between the Peripheral Connector Assembly (PCA) and the system unit M (mouse) and KBD (keyboard) connectors. IS THE CABLE CORRECTLY ATTACHED? Go to the Problem Determination Guide for the 5085. Connect the Y cable to the PCA and the 6150 System Unit.
Page 137
S e c t i o n 3. U t i l i t i e s Section 3. Utilities 3-1...
Page 138
........Utility Selection ........Show Installed Options Utility ..... Show and Change Diagnostic Test List Utility 3-10 Fixed-Disk Utilities ........3-11 Communication Utilities ........ 3-12 Diagnostic Diskette Copy Utility ....3-13 IBM 9332 Utilities .......... 3-14 3-2 Problem Determination Guide...
This section is divided into seven parts: • Loading the Utilities • Show Installed Options Utility • Show and Change Diagnostic Test List Utility • Fixed-Disk Utilities • Communication Utilities • Diagnostic Diskette Copy Utility • IBM 9332 Utilities. Section 3. Utilities 3-3...
Loading the Utilities Loading the utilities is similar to loading the diagnostic routines. Once you have decided which utility to use, follow the steps in this section to load the utility. This section presents a brief description of each utility. 3-4 Problem Determination Guide...
Loading the Diagnostic D isk ette s 1. Get the Diagnostics 1 (DIAG-1) diskette from the back of this manual. 2. Remove the write-protect tab, if one is present, from the diskette. 3. Turn off the system unit. 4. Wait about 1 minute. 5.
Page 142
6. Wait until the DIAGNOSTIC OPERATING INSTRUCTIONS screen is displayed. Note: A 94 in the two-digit display indicates that the display is not supported by the diagnostics. Refer to the documentation that came with your display and follow those procedures. 7.
F u n c t i o n S e l e c t i o n After reading the DIAGNOSTIC OPERATING INSTRUCTIONS screen and pressing the FUNCTION SELECTION menu is E n t e r , displayed. Type 2. Press E n t e r .
Then type its ID number. Press Enter. 3. Read and follow the instructions as they appear on the display screen. Descriptions of the various RT PC utilities can be found in the following pages. 3-8 Problem Determination Guide...
Show Installed Options Utility The Show Installed Options Utility displays the Configuration List built by the presence tests. The utility is used to check the configuration of the system. Section 3. Utilities 3-9...
Show and Change Diagnostic Test List Utility The Show and Change Diagnostic Test List Utility displays the Diagnostic Test List. This utility allows you to add or delete an adapter or device from the list. Note: The option must be installed in the machine before it can be added to the test list.
Fixed-Disk Utilities Use the Format Fixed-Disk Utility when intermittent read or write errors occur. This test erases all data on the fixed disk and reformats the fixed disk. Before using the test, backup all data on the disk. Section 3. Utilities 3-11...
Page 148
Communication Utilities The Communication Utilities contain the following exercise: Utilities for use with Ethernet1 . The Utilities for use with Ethernet is used to exercise the Baseband Adapter and parts of the Ethernet Network. The utility will work with a wrap plug or with any valid Ethernet Network. Ethernet is a registered trademark of Xerox Corporation.
Diagnostic Diskette Copy Utility The Diagnostic Diskette Copy Utility enables the user to copy diagnostic diskettes. The utility does the following: • Instructs the user to insert a target diskette. • Warns the user that data on the target diskette will be destroyed.
IBM 9332 Utilities The IBM 9332 Utilities provide the following: • A means of down loading microcode to the IBM 9332 from a diskette. • A means of displaying and altering the Vital Product Data on the IBM 9332. • A means of formatting the IBM 9332. This utility erases all data and formats the file.
Page 151
Appendix A. Locations and Examples Comparison drawings for use in locating controls and determining display problems are found in this appendix. Instructions for removing and replacing a defective battery are also found in this appendix. Appendix A. Locations and Examples A-l...
Page 152
Diagnostic Function Keys The following list describes the keys used and their function when running diagnostics: Continues the procedure or performs an action. Enter Stops a test or an action. F 10 Returns to the previous menu and cancels any changes.
Page 153
Typ es of Displays AIZAF055 Appendix A. Locations and Examples A-3...
Page 154
AIZAF056 A-4 Problem Determination Guide...
Page 155
Display Test Patterns Appendix A. Locations and Examples A-5...
Page 156
Test Pattern 2 A-6 Problem Determination Guide...
Page 157
IBM Personal Computer Enhanced Color Display Test Patterns Test Pattern 1 Appendix A. Locations and Examples...
Page 158
Test Pattern 2 A-8 Problem Determination Guide...
Page 159
I B M 5081 C o l o r G r a p h i c s D i s p l a y T e s t P a t t e r n s The color bar pattern used on a color display requires at least four video pixel planes.
Page 160
Test Pattern 2 This crosshatch (grid) test pattern is used to check convergence and alignment. Adjust the vertical convergence, horizontal convergence, and vertical centering controls to correct a crosshatch (grid) pattern that is distorted. AJZB216 A-10 Problem Determination Guide...
Page 161
Battery Re mo v a l and Re pl ac eme nt The following pages provide the steps necessary to remove and replace the battery in the IBM 6150 and IBM 6151 System Units. Appendix A. Locations and Examples A-11...
Page 162
#6299201 only or a battery th a t has been specifically classified by Underwriters Laboratories, Inc. for use with the IBM 6151 and is so m arked to indicate such classification. Use o f anoth er battery m ay present a risk of fire or explosion.
Page 163
Appendix A. Locations and Examples A -13...
Page 164
#6299201 only or a battery tha t has been specifically classified by Underwriters Laboratories, Inc. for use with the IBM 6151 and is so m arked to indicate such classification. Use o f another battery may present a risk of fire or explosion.
Page 165
A-15 Appendix A. Locations and Examples...
Page 166
#6299201 only or a battery that has been specifically classified by Underwriters Laboratories, Inc. for use with the IBM 6150 and is so m arked to indicate such classification. Use o f another battery m ay present a risk of fire or explosion.
Page 167
A-17 Appendix A. Locations and Examples...
Page 168
#6299201 only or a battery th a t has been specifically classified by Underwriters Lab oratories, Inc. for use with the IBM 6150 and is so m a rk ed to indicate such classification. Use o f anoth er battery may present a risk o f fire or explosion.
Page 169
A-19 Appendix A. Locations and Examples...
Page 183
Glossary To describe (to the system) configure. A printed circuit card that adapter. the devices, optional features, and modifies the system unit to allow it to program products installed on a system. operate in a particular way. An electrical part used to connector.
Page 184
A tool (procedure, diagnostic aid. or files. (2) The pattern that determines program, reference manual) used to detect how data is recorded. and isolate a device or program malfunction or error. A diskette on which formatted diskette. control information for a particular A computer diagnostic routine.
Page 185
recovery from, or circumvention of, A small user input device mouse. problem conditions. externally attached to the system unit. A displayed request for prompt (n.). A printing device externally plotter. information or operator action. attached with cables to the system unit, used to print two-dimensional graphs and An action recovery procedure.
Page 186
In data communications, a terminal. to identify the diskette to the user and to device, usually equipped with a keyboard the system. and a display, capable of sending and receiving information over A device at which an work station. communications lines. individual may transmit information to, or receive information from, a computer for Two seven-segment...
Page 187
IBM RT PC Problem SA23-2604-0 Determination Guide Your comments assist us in improving our products. IBM may use and distribute any of the information you supply in any way it believes appropriate without incurring any obligation whatever. You may, of course, continue to use the information you supply.
Page 197
IBM RT AIX Operating System Problem Determination Guide...
Page 198
IBM m ay m ak e im p rovem en ts and/or c h a n g es in th e prod uct(s) an d/or th e program (s) described in th is m anual at any tim e.
Page 199
A bout This Book P u rp ose Use this book to do software problem determination on the IBM RT® system. If the AIX™ Operating System is not installed and working, the tools provided in this book cannot be used. When you suspect a software problem, use this book to find the failure.
Page 200
A Reader's Comment Form and Book Evaluation Form are provided at the back of this book. Use the Reader's Comment Form at any time to give IBM information that may improve the book. After you become familiar with the book, use the Book Evaluation Form to give IBM specific feedback about the book.
Page 201
AIX Operating System commands. • lists messages displayed by the IB M R T Messages Reference IBM RT and explains how to respond to the messages. • is a IB M R T A IX Operating System Technical Reference four-volume set.
Page 202
• To order from your IBM representative, use Order Number SBOF-1825 for all RT systems except model T-25. • To order from your IBM dealer, use Part Number 22F9815 for all RT systems except model T-25. • To order from your IBM representative, use Order Number SBOF-1805 for RT system model T-25.
Page 203
C ontents S e c tio n 1. S oftw are P rob lem s ........... About This Section ..............S e c tio n 2. The D um p U tilities ........... About This Section ..............2-3 Dump Formatter ..............2-18 S e c tio n 3.
Page 204
AIX Operating System Problem Determination Guide viii...
S ectio n 1. Softw are Problem s Section 1. Software Problems 1-1...
Page 206
About This Section ....... . Step 1. Determining Software Problems Step 2. Message Displayed ....Step 3. Failing Program Undetermined VRM and AIX Operating System Dumps Trace ............. AIX Operating System Problem Determination Guide...
About This Section This software problem section describes the tools available for use in software problem determination. These tools will help find the cause of the problem but will not fix the problem. Once you have located the failing program, use your normal problem reporting procedures.
Page 208
Step 1. D eterm in in g S oftw are P rob lem s If you suspect a program has a software problem, you can do several things to determine if the problem is really software. The Symptom Index is a list of system problems or symptoms. The section or step related to the symptom is contained in the action column of the Symptom Index.
Page 209
Sym ptom s A ctions c6 is alternately displayed with Go to “Step 2. VRM a two-digit abend code in the Dump (System two-digit display during normal Started)’’ on operation. page 2-5. XX is blinking in the two-digit Go to display.
Page 210
Step 2. M essage D isp layed If you have a message: 1. Read the message carefully 2. Do the recovery action, if any is given. , Once you have responded to the message: 3. Try the operation again. If the program still fails: 4.
Page 211
S tep 3. F a ilin g P rogram U n d eterm in ed If you are unable to find the failing program in the error log, you may need to gather additional information. This information may consist of one or more of the following: VRM and A IX O perating S y ste m D um ps The dump utilities provide the commands needed to dump the contents of memory.
Page 212
AIX Operating System Problem Determination Guide...
About This Section This section contains instructions for using the VRM, Kernel, and Full Image dump utilities to copy the contents of memory at the time of a program failure. The core file and the crash utility are also described. The data collected by these utilities is intended to help you, or the person servicing the system, determine the cause of the failure.
Step 1. D um p U tilitie s Use the following procedure to determine where to go in this Chapter. Find the dump condition in the table and go to the associated step. Dump Conditions A ctions A c6 and an abend code are Go to “Step 2.
S tep 2. VRM D um p (S y stem S tarted ) The c6 and an abend code alternately displayed in the two-digit display is a prompt to load the dump diskette. The abend codes are described in Appendix C of this book. Blinking error codes that can occur during IPL (without the c6) are described in Chapter 5.
Page 218
When the dump is complete, cO is displayed in the two-digit display. For any other messages displayed, see “Dump Utility Messages” on page 2-17. Press CTRL-ALT-Pause to restart the operating system. Go to “Dump Formatter” on page 2-18 and format the dump diskette.
S tep 3. VRM D um p (U ser S tarted ) If you want to start the dump utility, follow these steps. 1. Remove the dump diskette from the back of this manual. The dump diskette may be any formatted high-capacity Note: diskette.
Page 220
3. Insert the dump diskette into the diskette drive in location A . (The top drive if there are two.) 4. Press the keys again. (Use the left CTRL-ALT-numpad8 key.) appears in the two-digit while the system verifies the diskette A c8 is usable.
S tep 4. VRM D um p (U ser S ta rted F rom VRM D ebugger) Use the following instructions to start a dump from the debugger. 1. Read the debugger message generated from the crash. 2. Enter the command: show 3.
S tep 5. K ernel D um p (S y stem S tarted ) When an error is so severe that the operating system cannot continue, a PANIC message is displayed. For most PANIC messages, a Kernel dump, sometimes called a virtual machine dump, is written on the dump minidisk on the hardfile.
S tep 6. K ern el D um p (U ser S tarted ) If you want to start the Kernel dump utility: 1. Press the CTRL-ALT-END keys. 2. When the dump is written on the dump minidisk on the hardfile, this message is displayed: dump succeeded, xxxx blocks Note: The crash utility can be used to look at the dump.
S tep 7. K ernel D um p (Copy to D isk e tte ) To submit Kernel dump information, the dump must be copied to diskettes. Follow these instructions to copy the information from the dump minidisk on the hardfile to diskettes. Note: The following procedure attempts to dump to one Idevjhd4...
S tep 8. Core F ile A core file is the result of a terminated process when various errors occur. Common errors are: memory violation, illegal instructions, and bus errors. The core file is written in the process's working directory. To examine the core file, use the sdb command.
Step 9. S y stem A ppears to be H ung A system is considered hung when no work can be done or no response is received from commands or interrupt keys. When this condition occurs: 1. Press CTRL-ALT-END to copy the virtual machine to the dump minidisk.
S tep 10. F u ll Im age D um p This step dumps all of your system's real memory and requires multiple (up to four) diskettes. A full image dump takes more time than a VRM dump and you cannot use the dump formatter to inspect the information on the diskettes.
Page 228
If the diskette is good, c9 in the two-digit display indicates the dump is running. Each diskette takes approximately 5 minutes to complete. When a diskette is full, c7 is displayed in the two-digit display. When that happens, remove the full diskette from the diskette drive and insert the next higher numbered diskette.
D um p U tility M essa g es The messages for the dump utility are displayed on the two-digit display. These messages tell you when the dump is complete, when a dump diskette is needed, and if there is a problem found while running the dump utility.
Dump F o rm a tter The Dump Formatter is used to format the information contained on the dump diskette into a readable form. The information can be directed to the display, the printer, or to a file. If the dump program finds a problem, the dump formatter gives header information describing the problem.
About This Section The error log is used to help find the failing area of the system. The failures may be hardware or software. This error log is useful in finding problems when the failures are intermittent. If the Diagnostic Routines are unable to find a suspected hardware problem, the error log may have recorded the error.
Error Log Report Types Two types of error log reports can be produced: a summary report and a detail report. The summary report contains one-line descriptions of system activities and errors. You can specify which error types you are looking for (such as diskette, display, or program errors), and the time the errors occurred.
Error Log Command Format To generate an error log report, enter a command in the form: errpt flags filenam es Note: Flags and filenames are optional parameters. Filenames specifies the error log files. The errpt command accepts the following flags: Ignore all records logged earlier than date date.
Step 1. S um m ary E rror Log Notes: 1. The following command examples are issued from the AIX shell command line. 2. If you are using Usability Services, you may want to run an error log using Usability Services. For more information on running an error log from Usability Services, see IB M R T Usability Services Reference.
S tep 2. S u m m a ry Error L og All of the following steps assume you are using the AIX Shell. If you are not, see the notes on the preceding page. To display a summary error log report: 1.
Page 238
IS THE ERROR LOG REPORT DISPLAYED? CONTINUE to next page. Enter the command again. If the report still does not display, the error log file may not exist. STOP, you have completed these procedures. 3-8 AIX Operating System Problem Determination Guide...
S tep 3. S u m m a ry Error Log The Error Log screen is divided into six areas: Date/Time, Class, Subclass, Type, Device, and Cause. Look at the Date/Time column first. IS THERE A DATE AND TIME THAT CLOSELY MATCHES YOUR TIME OF ERROR? CONTINUE to next page.
Step 4. D eta il Error Log Display a detail error log report using the date and time of the suspected error. 1. Type the command: errpt -a -s M M d d h h m m y y EXAMPLE e r r p t -a-s 0525143585 A detail report for the error...
Page 241
IS A DETAIL ERROR REPORT SHOWN? For hardware errors, read and follow the instruction in the detail report. For software errors, use your normal problem reporting procedures. Enter the command again. If command still fails, report the problem. Section 3. Error Log 3-11...
Page 242
3-12 AIX Operating System Problem Determination Guide...
Using the Trace Utility This trace utility is used to track the system events when a program is running. By tracing, or tracking these events, a report can be made explaining the system's performance and actions. This utility is run in background mode while using a program, to trace the steps and actions of the program.
The Trace Profile Before you can start the trace, you must select the trace profile and the events you wish to trace. The trace profile is a file that contains the areas that can be traced and is provided with the system.
Page 246
4-4 AIX Operating System Problem Determination Guide...
Page 247
S tep 1. S ta r tin g th e T race After the setup of the trace profile has been completed, you can start the trace. 1. Type the command: trace& 2. Press ENTER. The trace is on, now run the program you want to trace. S tep 2.
Creating the Trace Report The trace report program is used to make a readable copy of the trace information. The output can be sent to a file, the display, or a printer. To produce the report: 1. Type the command and if needed, the options: trcrpt The options are: Starting date/time desired in the formatted file.
S ectio n 5. B linking Tw o-D igit D isplay M essages Section 5. Blinking Messages 5-1...
Page 252
CONTENTS About This Section ..... Errors Found at IPL ....Errors Found During VRM Install 5-14 5-2 AIX Operating System Problem Determination Guide...
About This Section This section describes the messages that can appear on the two-digit display during IPL and while the VRM install process is running. The cause and recovery procedures are given for each message. Only blinking two-digit messages are described in this section.
Since the user has the ability to install other software on the VRM minidisk, it is sometimes difficult to tell if the error occurred in IBM code, or in the user's code, if changes have been made to the VRM minidisk. For all errors that indicate a change may have been made to the VRM, the user should again install the VRM from his IBM-supplied diskette.
Page 255
Read error. Cause: A read error occurred on the IPL device (either disk or diskette) during execution. Action: If you were using a diskette to IPL, try again with a backup diskette. If you were using the disk to IPL, install the Virtual Resource Manager (VRM) again, then IPL the system.
Page 256
Not enough space for the Module Index Table (MIT). Cause: The MIT contains an entry for each file that is loaded or mapped. Either there was not enough memory to allocate space for the MIT (see error 03 for more information), or there are more than 128 files in the loadlist (the files in the directory Id list).
Page 257
Not enough space for the m atch list. Cause: There was not enough memory to allocate space for the match list. See error 03 for possible causes and actions for this. Relocation symbol type not supported (non-fatal) Cause: One of the modules being processed by the loadlist processor has a relocation symbol type that is not supported.
Page 258
Invalid device Cause: The information contained in the POST Control Block for the IPL device does not contain a valid value. Since loadable POST routines that execute during IPL have access to the POST Control Block, any of these modules could have written the invalid value to this area of the POST Control Block.
Page 259
File not found. Cause: All files processed by the loadlist processor must be under a directory name A directory file name Idlist. was not found. Id list Action: If the VRM minidisk has been changed so that the directory name has been renamed or removed, Id list correct the problem or install the original VRM again.
Page 260
is made to load the module into memory at the address represented by the origin. If the module cannot be loaded because the required space is not free, the above error occurs. Action: If the VRM minidisk has been changed by adding additional code, find and remove the failing module, or install the original VRM again.
Page 261
Invalid IOCN in the file name (non-fatal) Cause: The field containing the four character IOCN value is invalid for some file name in the loadlist. This field must contain a hexadecimal value from X' 0001' to X' 04001 for any module that has an IOCN. This field must be X' 0000' for any module that does not have an IOCN.
Page 262
Invalid length field in the DDA entry (non-fatal) Cause: A module that has been executed by the loadlist processor (permission bits = 700) has returned an entry for the Define Device Area (DDA) that has an invalid value in the length field. The length must be greater than 0 and less than or equal to 2048 bytes.
Page 263
Bad load module (non-fatal). Cause: A module that was to be loaded by the loadlist processor has invalid information in the TOC header. This module will not be loaded, and the loadlist processor will continue processing after displaying the error. Action: If the VRM minidisk has been changed by adding additional code, find the module that caused the error and remove it.
Errors Found During VRM Install The errors described in this section are those found during the VRM install process. All of the errors are fatal except for number 45 (base device missing) and the numbers continue to blink until you re-IPL the system or take the appropriate action specified. Base device missing.
Page 265
Define code failure. Cause: A define code SVC was attempted for a file on the VTCP command line in the Inst.Batch file. The SVC failed and the code was not defined into the system. Action: Contact the supplier of the "device diskette." No space for file.
Page 266
Device driver define device failed. Cause: A define device SVC was attempted on the device driver specified on the VTCP command line in the Inst.Batch file. The SVC failed and the device driver was not added into the system. Action: Contact the supplier of the "device diskette." VTRM define device failed.
Page 267
A ppendix A. The VRM M ainten ance F acility (VMF) Appendix A. VRM Maintenance Facility A-l...
Page 268
CONTENTS About This Appendix ..............A-3 VRM Maintenance Facility (VMF) Overview ......A-4 Command Format ..............A-5 Help T e x t........Messages ................... A-8 The Batch F a c ility ..............A-8 Commands ................. A-9 amd ....................A-9 ..........A-10 chmod ................... A-11 cpy ..................
About This Appendix This appendix contains a description of the VRM Maintenance Facility (VMF) and its uses as a tool, and also a brief description of each of the commands that are available in the tool. Appendix A. VRM Maintenance Facility A-3...
VRM Maintenance Facility (VMF) Overview VMF is a standalone tool you can use to display and modify data on direct access storage — both fixed disk and diskette. The primary purpose of the tool is to help diagnose problems with the fixed disk when the problem has made the system inoperable.
quit Terminate the VMF Display virtual machine information rem ark Make a batch file comment Delete a file from a file system search Search for a character string setattr Set minidisk attributes Verify (compare) data on different devices IPL a virtual machine. C om m and F orm at You enter all VMF commands on the display command line (line 24).
Page 272
m inidisk-ID This is a minidisk identifier and can be either the minidisk iodn or the minidisk name. For example, hdO is the name for the minidisk containing the AIX root file system and hd6 is the name for the minidisk containing the VRM file system. devaddr This is the device address and can be: •...
identifier for the other minidisk or use the cd command and establish a new default. VMF does not support mounting of file systems onto the system root directory. sec# This is a sector number (decimal). The first sector number on a device is 0.
displays the help text for the delete minidisk command. M essages VMF issues the following three types of messages: • General syntax errors • Specific user errors • Messages on behalf of the VRM. For syntax errors, VMF displays a short message that shows the correct syntax.
B a tc h F iles A batch file is a text file on a DOS diskette that contains VMF commands. When you run a batch file, you must leave the diskette in the drive until all of the commands have completed. You need an operating system such as AIX or PC DOS to create a batch file.
Page 276
Parameters: devaddr This is the device address. block# This is the block number (the first block number is 0). offset This is the hexadecimal offset into block wl w 2 These are the 4-byte words of data to be placed starting at You can enter each word of data without leading offset.
leading / (slash). In this case, the complete becomes A lX n a m e /hdO/usr/bin/my file. ch m od Use chmod to change the read/write permission bits in a file inode. Format: ch m od O O O A lX n a m e Parameters: This is the octal representation of the 9 permission bits.
block# 1 This is the beginning sector number on the source device. block#2 This is the beginning block number on the target device. #b locks This is the number of blocks of data to transfer. crm d Use crmd to create a minidisk on a fixed disk. Format: crm d iodn blksz #blks -dreald -nnam e -ssec# -aattr Flags:...
Page 279
Param eters: iodn This is the iodn for the new minidisk. blksz This is a multiplier digit in the range of 1 through 16 that specifies a block size as a multiple of 512 bytes. For example, if you specified the block size would be 512;...
1, m, h This specifies the low, medium or high starting position for the new minidisk on the real device. These attributes are ignored if the -s option is specified. debug Use debug to invoke the VRM Debugger when the specified virtual machine is next dispatched, debug can only be used when VMF is IPL'ed directly from the fixed disk.
dlmd to delete a minidisk. dlmd Format: dlm d m in id isk-id <reald> Parameters: m inidisk-id This is the iodn or name of the minidisk being deleted. reald This is the fixed disk IODN on which the minidisk resides. If you have more than one minidisk with the same name on different minidisks, you should specify this parameter.
Page 282
Parameters: dosname This is the name of the DOS file being copied including the diskette drive name (such as b:) if other than the first. AlXname This is the path name of the AIX file being created. This is the octal representation of the 9 permission bits for the new AIX file.
ech o Use this batch facility command to turn command echoing on or off, or to display a message on the display. When echoing is on, each command in the file is displayed on the screen as it starts to run.
exec Use this batch facility command to run the commands in a VMF batch file. This command is usually entered on the command line, however, you can use this command in a batch file to transfer control to another file and start running the commands contained there.
fo rm a t Use the form at command to initialize the track format of a new disk. This command is used only for disks that have not been initialized for the RT-PC. Form at: fo rm a t iodn Param eters: iodn This identifies the drive to format.
Use hd to display data residing on a fixed disk or diskette. Format: hd devaddr sec#l sec#2 -p Flags: Use this option to send the data to the printer instead of the display. Param eters: devaddr This specifies the device that contains the data. sec#l This specifies the first sector of data to be displayed.
Parameters: AlXname This is the path name of the AIX file. fromoffset This optional parameter specifies the offset (hexadecimal) from the beginning of the file to start displaying data. If this parameter is not specified, the default is 0. tooffset This optional parameter (if is specified) provides fromoffset...
Flags: When this option is specified, VMF determines the file names in which unrelocated bad blocks reside. help Use the help command without parameters to display the complete list of VMF commands. To get help for a particular command, enter the command name followed by a ? (question mark). Format: help in st...
in s tf Use the instf command to copy an AIX file to a minidisk. The file is copied sequentially starting at sector 0 of the minidisk. The previous contents of the minidisk are destroyed. Format: in stf A lX n a m e m in id isk-id Param eters: AlXname This is an AIX file identifier and must contain a complete...
Page 290
Flags: This flag sends the output to the printer instead of the display. Param eters: AlXname This is the path name of the directory to be listed. If not specified, the current directory is displayed. Use me to copy the entire contents of one minidisk to another. Both minidisks must have the same block size but they can differ in size.
mkfs Use mkfs to create an AIX file system on a minidisk or diskette. Form at: m inidisk-id \ diskette-iodn <#blocks> <#iblocks> m k fs Param eters: minidisk-id This identifies the target if it is a minidisk. diskette-iodn This identifies the target if it is a diskette. #b locks This is the size of the new file system (the default is 540): Minidisk —...
p a u se Use this batch facility command to wait until the operator presses the Enter key. When the batch facility encounters this command in a batch file, it displays the message Press Enter to continue and then waits for the keystroke. There are no parameters for this command.
Use this command to determine the present working directory. Form at: Use qi to display a list of minidisks defined on the fixed disks. If you do not specify one or more minidisk IDs, all the minidisks are listed. If you specify 0 for one of the minidisk IDs, you get a list of all fixed disk free space.
quit Use this command to terminate the VMF. Form at: quit Use the qvm command to display information about the virtual machines running in the system. The command displays the VMID and IPL IODN for the VMID requested on the command line. Form at: <vmid>...
to remove a file from an AIX file system. You can remove files and directories. However, the directories must be empty. An error message is the result if you attempt to remove a directory that is not empty. Format: AlXname Parameters: AlXname This is the path name of the AIX file or directory to be...
minidisk-iodn This is a minidisk, input/output device number. Specify a minidisk IODN when you want to search an entire minidisk for occurrences of a string. Minidisk names cannot be used because minidisk names and AIX names are ambiguous. string This is the search argument. The search command searches for ascii strings or hexadecimal strings.
Use vfy to verify that two areas of data are identical. If the areas are on different minidisks, the minidisks must have the same logical block size. Format: devaddrl sec#l devaddr2 sec#2 #sectors Flags: Send messages to the printer instead of the display. Param eters: devaddrl devaddr2 This identifies the devices that contain the data.
Page 298
Parameters: minidisk-id This identifies the minidisk containing the virtual machine. vmid This is an optional parameter that specifies a VM number for the machine being IPLed. If omitted, the next available VMID is used. A-32 AIX Operating System Problem Determination Guide...
Appendix B. Error Log E ntries Appendix B. Error Log Entries B-l...
Page 300
CONTENTS About This Appendix ..............B-3 Error Log Entry Types ............B-3 Subclass = 02 Abnormal Termination (ABEND) ....B-6 Subclass = 03 AIX Program E r r o r ........B-7 Subclass = 04 AIX Device Driver Program Error ....B-7 Subclass = 07 VRM Component Program Error ....
About This Appendix This appendix lists some of the software entries that you could receive. There is no action you can take with most of the possible error log entries except to report the problem. However, it is thought that with the entries listed here, you might have caused the problem with your program or your operation and you might be able take action to further diagnose and solve the problem.
Page 302
C lass Type S u b class M ask S u b cla ss Type Hardware ROMP program check ABEND Dump taken No dump taken AIX Program Error AIX kernel AIX device driver program error Base LAN device driver 5080 peripherals SSLA device driver AIX device driver program error VRM base program error...
Page 303
IPL/Shutdown Manual IPL Soft IPL Auto IPL Shutdown Maintenance shutdown Multi-user shutdown General Degraded configuration System Set date/time Condi ti on Server no start Cause codes LP0ST results User defined F ig u re B -l (P art 2 o f 2). E rror L og E n try T ypes The following are descriptions of some error log entries.
S u b class = 02 A b n orm al T erm in a tio n (A BEN D ) M ask = 00 VRM A B E N D M essag e A m achine check has occurred. A ROMP machine check occurred that was probably caused by a hardware failure.
An I/O channel error has occurred. This error is probably caused by a bad device on the bus. S u b cla ss = 03 A IX P rogram E rror M ask = 03 AIX K ernel The AIX kernel issues messages that are displayed on the console.
Page 306
• The device was not installed properly. Reinstall the Base PC Network Services program and try again. • Another device in Kernel has attached to the adapter card. Only one attach is allowed per virtual machine. RC = 16 DETACH SVC The DETACH SVC failed.
your program does not close the device with outstanding neb's issued. RC = 259 SIO - neb command = BO There were insufficient resources on the adapter card when the was issued. Issue the again because the resources may now be free. If the condition persists, verify that the number of allowed for the neb's...
Page 308
Module-ID = KDDMAIN RC = 03 D01 = 03 The main entry point was called for a request with an invalid term inate device device ID. Module-ID = KDDMAIN RC = 02 D01 = 04 The main entry point was called with an invalid operation type.
Page 309
Module-ID = KDDMAIN RC = 01 D01 = 11 The sound initialization routine called and received a non-zero return -CHANGE code. Module-ID = KDDINTR RC = 01 D01 = 01 The second level interrupt handler entry point called for the keyboard device driver -DEQUE queue for an empty click buffer and received a non-zero return code.
Page 310
Module-ID = KDDINTR RC = 01 D01 = 07 The second level interrupt handler entry point called for the locator device driver -ENQ queue for sending mouse data and received a non-zero return code. M odule.ID = KDDINTR RC = 01 D01 = 08 The second level interrupt handler entry point called for the locator device driver...
Page 311
Module-ID = KDDIOIN RC = 01 D01 = 03 The keyboard I/O initiate entry point called for the keyboard device driver queue -DEQUE for the command and received a ACT VT non-zero return code. Module-ID = KDDIOINL RC = 01 D01 = 01 The locator I/O initiate entry point called for the locator device driver queue -DEQUE...
Page 312
M ask = 02 VRM co m p o n en t - V irtu a l T erm in al M ode P ro c esso r Module-ID = VTMMAIN RC = 0 D01 = 07 The virtual terminal mode processor received a queue element that it does not recognize.
Page 313
M odule-ID = VTMOUT RC = 6537 This error occurred during a request to change indicators and the LPFKs are not attached, or during a request to change granularities and the dials are not attached. M odule-ID = VTMOUT RC = 6544 The received VTD command is not valid in the current operating mode of the virtual terminal mode processor.
Page 314
Module-ID = VTMQRY RC = 6522 This error occurred because the virtual terminal mode processor received a query SVC with an invalid major type. Module-ID = VTMQRY RC = 6524 This error occurred because the virtual terminal mode processor received a query SVC with an invalid minor type.
Page 315
command with an LINE, FIELD, AREA invalid parameter. Module_ID = VTMUPD RC = 6549 D01 = 04 This error occurred because the virtual terminal mode processor received an ERASE command with an invalid parameter. DISPLAY M odule-ID = VTMUPD RC = 6549 D01 = 05 This error occurred because the virtual terminal mode processor received a control sequence...
Page 316
either the font module symbol is not exported with the correct name or the font structure is incorrect. Module-ID = VTRUTLPF RC = 03 The resource controller tried to add a font to the font table in the resource structure and the ID of the storage segment containing the font was unknown to the VRM.
Page 317
Module-ID = VTRUTLNP RC = 09 The resource controller tried to derive requisite information for an input device and either the IOCN of the device driver exported a structure different from that expected by the screen manager, or the names mismatch. Module-ID = VTRUTLND RC = 10 The resource controller tried to derive requisite information to enter a display into the real...
Page 318
Module-ID = VTRUTLND RC = 27 The resource controller tried to derive requisite information to enter a display into the real screen table of the resource structure and the attempt failed. That error was previously logged. This error occurred when the resource controller received an unexpected return code from while recovering resources from...
Page 319
Module_ID = VTRRCICS RC = 40 During initialization, the resource controller tried to bind the screen manager to the common device utilities and found that either the screen manager expected an entry point different than the one the resource controller exports or that the names mismatch.
Page 320
match. This error can cause unpredictable results. Module-ID = VTTSELD or VTTQRD RC = 05 The size of the define device structure for the requested real display device is larger than the implementation limit for these modules. Module-ID = VTTSELD or VTTQRD RC = 06 An error occurred while obtaining the define device structure.
Page 321
virtual device driver. The return code is in D04. M ask = 03 PC/AT C op rocessor D river Module-ID = CPDSLIH RC = 0 I/O Channel Check — 286 was BUS MASTER — This channel check is usually caused by a parity error on the 512K bus memory card that could indicate a bad module on the board.
You should request less memory for the Coprocessor when the PCSTART command is issued. For example, 512K instead of 640K. S u b cla ss = 08 A p p lication P rogram E rror M ask = 02 In ter a ctiv e W o rk sta tio n Module-ID = ATE RC = 1 routine logs this error during a...
Page 323
Module-ID = ATE RC = 4 routine logs this error during an send file transfer when it has attempted XMODEM to send a sector nine times, but the receiving site has not acknowledged receipt of the data. Verify that both sites are using the XMODEM file transfer protocol.
Page 324
Verify that both the local and remote sites are using the same file transfer protocol and that the remote site is set up to send. Then select receive and try the file transfer again. Module_ID = ATE RC = 8 The session has been disconnected because the system can no longer detect a carrier signal.
Page 325
OPEN system call. Module-ID = pcrctrl RC = 2 IOCTL The IOCTL system call to the network device failed. Restart the RT PC. See A IX Operating System for the IOCTL command. Technical Reference Appendix B. Error Log Entries B-27...
Page 326
B-28 AIX Operating System Problem Determination Guide...
Page 327
Appendix C. Abend Codes Appendix C. Abend Codes C-l...
Page 328
CONTENTS About This Appendix C-2 AIX Operating System Problem Determination Guide...
Page 329
About This Appendix This appendix lists some of the abend codes that you could receive. The abend code alternately displayed in the two-digit display is a prompt to load the dump diskette. Appendix C. Abend Codes C-3...
Page 330
A level-2 hardware interrupt has occurred. A Processor and Memory Management Card Cause: interrupt occurred. The VRM does not handle this type of interrupt. Request a VRM dump, or restart the system. Action: A m achine check has occurred. A Processor and Memory Management Card Cause: machine check error occurred.
Page 331
A trap instruction was encountered. A virtual machine was running when a trap Cause: instruction was issued. Request a VRM dump, or restart the system. Action: A data protection exception has occurred. A data exception program check indicated that a Cause: protection exception occurred.
Page 332
A privileged operation exception has occurred. A privileged operation program check was Cause: detected, but a virtual machine was not running. Request a VRM dump, or restart the system. Action: An illegal operation exception has occurred. An illegal operation program check occurred, Cause: but a virtual machine was not running.
Page 333
A floating point exception has occurred. A floating point exception occurred while the Cause: VRM was running. Request a VRM dump, or restart the system. Action: The VRM encountered an unresolved reference. An internal process attempted to reference or Cause: branch to an unknown name.
Page 334
The VRM> encountered a perm anent I/O error in the paging space. The virtual memory manager received a Cause: permanent I/O error in the disk paging space. Request a VRM dump, or restart the system. Action: The VRM does not have enough real memory to continue.
Page 335
The VRM has received initialization data that is not valid. The VRM initialization routine detected an Cause: invalid load module or an invalid DDS in the data passed to it from the IPL program. The VRM may have been installed incorrectly. Re-install the VRM.
Page 336
error occurred while accessing cylinder a fixed disk. Cause: The VRM tried to access data (such as the bad block map or minidisk directory) on cylinder 0 of a fixed disk and experienced an I/O error. This is probably a fixed-disk hardware or formatting problem.
Page 337
G lossary (1) To detect, locate, and correct debug. A particular task, such as application. mistakes in a program. (2) To find the inventory control or accounts receivable. cause of problems detected in software. A processing method batch processing. An electrical or electronic device.
Page 338
The mechanism used to diskette drive. A file containing a log of history file. read and write information on diskettes. system actions and operator responses. The part of the display display screen. The process initial program load (IPL). device that displays information visually of loading the system programs and on a luminescent screen by use of preparing the system to run jobs.
Page 339
The computer and its associated system . file containing customized profile. (1) A devices and programs. settings for a system or user (2) Data describing the significant features of a A printout of storage system dump. user, program, or device. from all active programs (and their associated data) whenever an error stops A displayed request for...
Page 340
X-4 AIX Operating System Problem Determination Guide...