DS8000 Service Documentation Version 8.5.1

Service request numbers

Service request numbers (SRNs) serve as diagnostic aids to help users determine the source of a hardware problem. Diagnostic applications report problems by using SRNs. The SRN identifies the component that detected the error code and describes the error condition. Use this information to identify a list of possible failing items and to find information about any additional isolation procedures.

If your System reference code (SRC) is a five-digit hexadecimal number or contains a hyphen in the following formats (xxxxx, xxx-xxx, xxx-xxxx, xxxx-xxx, xxxx-xxxx), it is an SRN.

How to use the service request numbers

The list of SRNs is in numeric order. The SRNs in each range can include codes that consist of 6 to 8 digits. When the SRN you are looking for contains 3 digits before the dash, select the link that contains the first 3 digits followed by the dash of that SRN. Use the same process when the SRN you are looking for contains 4 digits before the dash.

The SRN tables use the following format:

  • The first column, Service Request Number (SRN), contains numbers that represent specific failures of specific functions.
  • The second column, SRN SRC. (SRN source code), contains the code that identifies the program or procedure that produced the SRN. For more information about using SRN SRC codes, see SRN source code.
  • SRNs contain Failing Function Codes (FFCs). The FFC represents field replaceable units (FRUs) of the system unit. When available, the FFC links to the FRU that contains this function for each specific system unit.
  • The SRN also contains an action or servicer response. Typically it is brief description of the failure that this SRN represents and an isolation procedure that should be used when servicing the system.
Do the following when you attempt to locate your specific SRN information:
  1. Use the online reference code finder. Go to Reference code finder.
  2. Record the failing function codes in the order listed. Service or replace the possible failing FRU in the order listed.
  3. Perform the isolation procedures that are listed in the servicer response area of the SRN.
    Note: If your SRN is not listed, check to see whether xxx or xxxx has been used. The -xxx or -xxxx should always be the last SRN identified within a specific prefix. For example, for SRN 950-xxxx, the xxxx represents the last entry within the 950 prefix.

SRN source code

When using SRNs to identify a problem and its resolution, you might need to refer to the source code of the SRN. The SRN source code identifies the program or procedure that produced the SRN. SRN source codes include the following:
SRN source code Description
A The SRN is from a steady number in the control (operator) panel display
B The SRN is from a MAP (problem isolation procedure) callout.
C The SRN was due to a missing resource at configuration time.
D The SRN is from a diagnostic test after complete isolation testing.
E The SRN is from a POST failure.
F The SRN is from a diagnostic test after partial isolation testing.

Reference code finder

Use the online documentation search function to find System reference management console error codes and messages, AIX diagnostic messages, symbolic field replaceable units (FRUs), failing function codes, failing item codes, and isolation procedures.
  • The asterisk (*) is an accepted wildcard.
  • SRCs are strings of either 6 or 8 alphanumeric characters in the formats ΧΧΧΧΧΧ or ΧΧΧΧΧΧΧΧ. Examples: 110000AD, C6003900, B7*988
  • Progress codes are strings of 8 characters that begin with a C (except CB) or D (except DA). Examples: C1001F0D, D101C00F, D11A1xxx, D11A1*, D1*B0FF
  • HMC error codes and messages are strings of 8 characters that begin with an H or strings of 6 characters that begin with a zero (0), and they do not include a hyphen. Examples: HSCL0003, HSCP0021, HSCI0104, 0x0007, 0*0104
  • AIX diagnostic messages are strings of 3 or 4 characters. Examples: 887, 2621, c33, c54, 0c0, 700, 558
  • SRNs are either strings of five hexadecimal numbers or numeric strings in the following formats xxxxx, xxx-xxx, xxx-xxxx, xxxx-xxx, xxxx-xxxx. Examples: 301C0, 733-120, 2502-3010
  • Symbolic FRUs are procedures that are used to diagnose problems with features and parts. Examples: ACMODUL, AIRMOVR, CAPACTY, LPARCFG, FWNIM, PWRSPLY, UC235
  • Failing function codes represent functions within the system unit. Examples: 11A, 201, 2E01, E30, B71
  • Failing item codes indicate which is the failing item. Examples: FI00021, FI00090, FI00718, FI01140
  • Isolation procedures are used together with diagnostic programs to isolate problem. Examples: RIOIP11, MABIP51, COMPIP1, PWR1905, FSPSP23, FSPSP33