* P/390 Diagnostic Message File
*
* No line should be longer than 80 characters!
*
0000 SUCCESSFULLY PASSED all tests.
0001 P/390 Diagnostic
0002 in slot
0003 version
0004 This may take a few minutes.
0005 number
0006 CODED MESSAGES
0007 EXPANDED MESSAGES
0009 NO MESSAGES
0012 PRESS: any key to return
0013 PRESS: any key to continue
0014 PRESS: Enter to return
0015 PRESS: Enter to continue
0018 Testing adapter in slot
0019 Testing adapter number
0020 S/390 Microprocessor Complex (P/390) Diagnostic Program
0021 P390DIAG     presents the choice of C or E below
0022 P390DIAG C   runs the diagnostic with Coded messages
0023 P390DIAG E   runs the diagnostic with Expanded messages
0025 Select one of the following:
0026   C - to run the diagnostic with Coded messages
0027   E - to run the diagnostic with Expanded messages
0028   X - to eXit the diagnostic program
0036   Diagnostic took
0037 second(s)
0038 Environment information:
0039 DIAGNOSTIC RESULT
0041 P/390 Adapter
0054   Diagnostic Program version
0055   FAILURE CODE:  Phase
0056 , Code
0057 , Test
0060 The P/390 adapter has
0061 MB of ECC memory on the processor card
0062 and an additional
0063 MB on an attached memory daughter card
0064 If this is incorrect, check the seating of the daughter card connector
0098 FAIL, code=
0099 PASS
0100   PHASE 1: CHECKING THE DIAGNOSTIC PROGRAM ENVIRONMENT:
0101     Checking PCI devices for configuration incompatibilities
0102     Looking for the P/390 Diagnostic files
0103     Obtaining addressability to adapter
0104     The adapter is in slot
0105     Checking that the adapter is enabled
0106     Resetting the adapter to get to a known state
0107       Checking the adapter window
0108     This is adapter number
0110     This host bridge chip does not work with the adapter
0111     The host bridge chip is not known to this program
0113       Found host bridge chip with vendorID/deviceID=
0114       Could not find a host bridge chip
0115     Error while accessing host bridge chip information
0198   CONFIGURATION INFORMATION:
0199     Successful completion of phase
0200   PHASE 2: TESTING THE ADAPTER INTERFACE FUNCTIONS:
0202     Testing:
0210       Miami POS Registers
0215       PCI Configuration Space
0220       Miami Control Reg's
0230       Memory Segment Registers
0240       Vital Product Data
0250       PCS Register
0260       CTM Register
0270       PEW Register
0280       RSW Register
0290       Writable Control Store
0291              Failing address=
0299         Switching to portal mode on this machine
0300   PHASE 3: TESTING ADDITIONAL ADAPTER INTERFACE FUNCTIONS:
0301     Opening:
0302     Load and execute the Bootstrap routine:
0303       Time-out limit set to
0304     Waiting for Bootstrap to finish
0305       Exceeded timeout limit!!!
0309     Testing the P/390 Timer
0310     Testing the COMBUF
0311       Bootstrap data:
0312     Testing one page Adapter RAM
0313     Load and execute the interrupt test routine:
0314     Testing Interrupts to the adapter
0315     Testing Alerts from the adapter
0316 , IRQ level=
0317       During initialization, internal routine gave error code
0318       During above test, internal routine gave error code
0319       No interrupts could be passed from routine to diagnostic
0330       RAM at address
0331 was:
0332                  should have been:
0350   DETECTED AN ADAPTER RAM FAILURE, failure code=
0351   RE-TESTING USING AN INTERNAL TEST ROUTINE:
0352 Did not complete!
0353 No error code!
0354 Error not duplicated!
0400   PHASE 4: TESTING THE ADAPTER WITH INTERNAL TEST ROUTINES:
0401     Executing
0500   PHASE 5: TESTING THE ADAPTER AFTER INTERNAL TEST ROUTINES:
0510     Testing the Key Array
0520     Testing aliasing from MSR bits
0521       Using every MSR bit to access memory
0522       Testing the MSR addition
0530     Testing using various lengths and offsets
0531       Read test
0532       Write test
0533         Possible unaligned bursting has been seen by program!
0534         Unaligned bursting has been detected by PAL!  Count
0535         Repeating test using portal
0540     Spot testing Adapter RAM
0541       Using every MSR (each with different contents), offset 0
0542       Using same MSR to access different offsets
0543       Using same offset and all MSR bits
0544       Using various MSR's and pages
0599     Checking for reported errors during above tests:
0900   SPECIAL INSTRUCTIONS:
0901   - NOTE: This error is NOT necessarily caused by a P/390 failure!
0902   - Try re-seating the adapter card and re-run this test.
0903   - Before replacing the daughter card, check that the daughter
0904     card connector is fully seated, and check for bent pins.
0905   - This may indicate a possible motherboard problem.
0906   - This may indicate a possible setup/configuration code problem.
0907   - This may be caused by a lack of 3.3V supplied from the motherboard
0908   - You probably should be running the P/390E diagnostics instead
0910 (The memory daughter card tested OK)
0911 (The memory daughter card (if present) has not yet been tested)
1000 HAS A FAILURE THAT COULD NOT BE ISOLATED
1001 (Service the processor card and the memory daughter card (if present))
2000 HAS A FAILURE ON THE PROCESSOR CARD
3000 HAS A FAILURE ON THE MEMORY DAUGHTER CARD
9000 HAS A UNIQUE SITUATION
F000 ENCOUNTERED A *** PROGRAM EXECUTION ERROR ***
F001 PROGRAM IS UNABLE TO CONTINUE AFTER THIS ERROR AND WILL ABORT
F010     *** This diagnostic program does not operate ***
F011     ***      in an OS/2 (Warp) environment.      ***
F012     ***  Press any key to terminate the program. ***
F013     ************************************************
F014     *** This diagnostic program cannot support   ***
F015     ***  more than 10 P/390 cards in a system.   ***
F040 Unable to open the diagnostics device driver
F041 Unable to access ODM database to determine MCA vs PCI
F042 Unable to switch to diagnostic mode.
F043 Execute 'stop390' and try again.
F044 >>> Error while attempting to re-establish microcode load
F045 >>> Error while attempting to switch off diagnostic mode
F046 >>> Error while attempting to close the diagnostics device driver
F050 Error encountered while attempting to clean up adapter:
F0F2 *** Message file P390DIAG.UMT not found ***
F0F3 *** Message missing in P390DIAG.UMT ***
F0F4 *** Message file P390DIAG.HET not found ***
F0F5 *** Message missing in P390DIAG.HET ***
*
* THE NEXT LINE MUST BE THE LAST MESSAGE!!!!
FFFF *** Message missing in P390DIAG.HMT for this code ***
*
* END OF MESSAGE FILE
