728
Power Systems System reference codes (Bxxx) IBM

System reference codes (Bxxx)public.dhe.ibm.com/systems/power/docs/hw/p7/p7eai_SRC2.pdf?orig… · Safety notices Safety notices may be printed thr oughout this guide: v DANGER notices

  • Upload
    others

  • View
    4

  • Download
    0

Embed Size (px)

Citation preview

  • Power Systems

    System reference codes (Bxxx)

    IBM

  • Power Systems

    System reference codes (Bxxx)

    IBM

  • NoteBefore using this information and the product it supports, read the information in “Safety notices” on page v, “Notices” onpage 705, the IBM Systems Safety Notices manual, G229-9054, and the IBM Environmental Notices and User Guide, Z125–5823.

    This edition applies to IBM Power Systems™ servers that contain the POWER7 processor and to all associatedmodels.

    © Copyright IBM Corporation 2010, 2017.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

  • Contents

    Safety notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

    System reference codes (Bxxx) overview . . . . . . . . . . . . . . . . . . . . . 1Block replacement of FRUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

    (B002) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

    (B003) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

    (B004) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

    (B005) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

    (B006) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

    (B008) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

    (B009) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

    (B010) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

    (B011) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

    (B012) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

    (B013) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

    (B014) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

    (B015) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

    (B017) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

    (B025) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

    (B026) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

    (B028) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

    (B038) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

    (B040) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

    (B057) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

    (B070) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

    (B075) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

    © Copyright IBM Corp. 2010, 2017 iii

  • (B1xx) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

    (B2xx) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537

    (B3xx) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559

    (B4xx) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567

    (B6xx) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573

    (B7xx) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 639

    (B9xx) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663

    (BAxx) Reference codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . 667

    (BF67) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 691

    (BF75) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 695

    (BF77) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 699

    Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 705Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 706Electronic emission notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 706

    Class A Notices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707Class B Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 710

    Terms and conditions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713

    iv System reference codes (Bxxx)

  • Safety notices

    Safety notices may be printed throughout this guide:v DANGER notices call attention to a situation that is potentially lethal or extremely hazardous to

    people.v CAUTION notices call attention to a situation that is potentially hazardous to people because of some

    existing condition.v Attention notices call attention to the possibility of damage to a program, device, system, or data.

    World Trade safety information

    Several countries require the safety information contained in product publications to be presented in theirnational languages. If this requirement applies to your country, safety information documentation isincluded in the publications package (such as in printed documentation, on DVD, or as part of theproduct) shipped with the product. The documentation contains the safety information in your nationallanguage with references to the U.S. English source. Before using a U.S. English publication to install,operate, or service this product, you must first become familiar with the related safety informationdocumentation. You should also refer to the safety information documentation any time you do notclearly understand any safety information in the U.S. English publications.

    Replacement or additional copies of safety information documentation can be obtained by calling the IBMHotline at 1-800-300-8751.

    German safety information

    Das Produkt ist nicht für den Einsatz an Bildschirmarbeitsplätzen im Sinne § 2 derBildschirmarbeitsverordnung geeignet.

    Laser safety information

    IBM® servers can use I/O cards or features that are fiber-optic based and that utilize lasers or LEDs.

    Laser compliance

    IBM servers may be installed inside or outside of an IT equipment rack.

    © Copyright IBM Corp. 2010, 2017 v

  • DANGER

    When working on or around the system, observe the following precautions:

    Electrical voltage and current from power, telephone, and communication cables are hazardous. Toavoid a shock hazard:v Connect power to this unit only with the IBM provided power cord. Do not use the IBM

    provided power cord for any other product.v Do not open or service any power supply assembly.v Do not connect or disconnect any cables or perform installation, maintenance, or reconfiguration

    of this product during an electrical storm.v The product might be equipped with multiple power cords. To remove all hazardous voltages,

    disconnect all power cords.v Connect all power cords to a properly wired and grounded electrical outlet. Ensure that the outlet

    supplies proper voltage and phase rotation according to the system rating plate.v Connect any equipment that will be attached to this product to properly wired outlets.v When possible, use one hand only to connect or disconnect signal cables.v Never turn on any equipment when there is evidence of fire, water, or structural damage.v Disconnect the attached power cords, telecommunications systems, networks, and modems before

    you open the device covers, unless instructed otherwise in the installation and configurationprocedures.

    v Connect and disconnect cables as described in the following procedures when installing, moving,or opening covers on this product or attached devices.

    To Disconnect:1. Turn off everything (unless instructed otherwise).2. Remove the power cords from the outlets.3. Remove the signal cables from the connectors.4. Remove all cables from the devices.

    To Connect:1. Turn off everything (unless instructed otherwise).2. Attach all cables to the devices.3. Attach the signal cables to the connectors.4. Attach the power cords to the outlets.5. Turn on the devices.

    (D005)

    DANGER

    vi System reference codes (Bxxx)

  • Observe the following precautions when working on or around your IT rack system:

    v Heavy equipment–personal injury or equipment damage might result if mishandled.v Always lower the leveling pads on the rack cabinet.v Always install stabilizer brackets on the rack cabinet.v To avoid hazardous conditions due to uneven mechanical loading, always install the heaviest

    devices in the bottom of the rack cabinet. Always install servers and optional devices startingfrom the bottom of the rack cabinet.

    v Rack-mounted devices are not to be used as shelves or work spaces. Do not place objects on topof rack-mounted devices.

    v Each rack cabinet might have more than one power cord. Be sure to disconnect all power cords inthe rack cabinet when directed to disconnect power during servicing.

    v Connect all devices installed in a rack cabinet to power devices installed in the same rackcabinet. Do not plug a power cord from a device installed in one rack cabinet into a powerdevice installed in a different rack cabinet.

    v An electrical outlet that is not correctly wired could place hazardous voltage on the metal parts ofthe system or the devices that attach to the system. It is the responsibility of the customer toensure that the outlet is correctly wired and grounded to prevent an electrical shock.

    CAUTION

    v Do not install a unit in a rack where the internal rack ambient temperatures will exceed themanufacturer's recommended ambient temperature for all your rack-mounted devices.

    v Do not install a unit in a rack where the air flow is compromised. Ensure that air flow is notblocked or reduced on any side, front, or back of a unit used for air flow through the unit.

    v Consideration should be given to the connection of the equipment to the supply circuit so thatoverloading of the circuits does not compromise the supply wiring or overcurrent protection. Toprovide the correct power connection to a rack, refer to the rating labels located on theequipment in the rack to determine the total power requirement of the supply circuit.

    v (For sliding drawers.) Do not pull out or install any drawer or feature if the rack stabilizer bracketsare not attached to the rack. Do not pull out more than one drawer at a time. The rack mightbecome unstable if you pull out more than one drawer at a time.

    v (For fixed drawers.) This drawer is a fixed drawer and must not be moved for servicing unlessspecified by the manufacturer. Attempting to move the drawer partially or completely out of therack might cause the rack to become unstable or cause the drawer to fall out of the rack.

    (R001)

    Safety notices vii

  • CAUTION:Removing components from the upper positions in the rack cabinet improves rack stability duringrelocation. Follow these general guidelines whenever you relocate a populated rack cabinet within aroom or building:

    v Reduce the weight of the rack cabinet by removing equipment starting at the top of the rackcabinet. When possible, restore the rack cabinet to the configuration of the rack cabinet as youreceived it. If this configuration is not known, you must observe the following precautions:

    – Remove all devices in the 32U position and above.

    – Ensure that the heaviest devices are installed in the bottom of the rack cabinet.

    – Ensure that there are no empty U-levels between devices installed in the rack cabinet below the32U level.

    v If the rack cabinet you are relocating is part of a suite of rack cabinets, detach the rack cabinet fromthe suite.

    v Inspect the route that you plan to take to eliminate potential hazards.v Verify that the route that you choose can support the weight of the loaded rack cabinet. Refer to the

    documentation that comes with your rack cabinet for the weight of a loaded rack cabinet.

    v Verify that all door openings are at least 760 x 230 mm (30 x 80 in.).v Ensure that all devices, shelves, drawers, doors, and cables are secure.v Ensure that the four leveling pads are raised to their highest position.v Ensure that there is no stabilizer bracket installed on the rack cabinet during movement.v Do not use a ramp inclined at more than 10 degrees.v When the rack cabinet is in the new location, complete the following steps:

    – Lower the four leveling pads.

    – Install stabilizer brackets on the rack cabinet.

    – If you removed any devices from the rack cabinet, repopulate the rack cabinet from the lowestposition to the highest position.

    v If a long-distance relocation is required, restore the rack cabinet to the configuration of the rackcabinet as you received it. Pack the rack cabinet in the original packaging material, or equivalent.Also lower the leveling pads to raise the casters off of the pallet and bolt the rack cabinet to thepallet.

    (R002)

    (L001)

    (L002)

    viii System reference codes (Bxxx)

  • (L003)

    or

    All lasers are certified in the U.S. to conform to the requirements of DHHS 21 CFR Subchapter J for class1 laser products. Outside the U.S., they are certified to be in compliance with IEC 60825 as a class 1 laserproduct. Consult the label on each part for laser certification numbers and approval information.

    CAUTION:This product might contain one or more of the following devices: CD-ROM drive, DVD-ROM drive,DVD-RAM drive, or laser module, which are Class 1 laser products. Note the following information:

    v Do not remove the covers. Removing the covers of the laser product could result in exposure tohazardous laser radiation. There are no serviceable parts inside the device.

    v Use of the controls or adjustments or performance of procedures other than those specified hereinmight result in hazardous radiation exposure.

    (C026)

    Safety notices ix

  • CAUTION:Data processing environments can contain equipment transmitting on system links with laser modulesthat operate at greater than Class 1 power levels. For this reason, never look into the end of an opticalfiber cable or open receptacle. (C027)

    CAUTION:This product contains a Class 1M laser. Do not view directly with optical instruments. (C028)

    CAUTION:Some laser products contain an embedded Class 3A or Class 3B laser diode. Note the followinginformation: laser radiation when open. Do not stare into the beam, do not view directly with opticalinstruments, and avoid direct exposure to the beam. (C030)

    CAUTION:The battery contains lithium. To avoid possible explosion, do not burn or charge the battery.

    Do Not:v ___ Throw or immerse into waterv ___ Heat to more than 100°C (212°F)v ___ Repair or disassemble

    Exchange only with the IBM-approved part. Recycle or discard the battery as instructed by localregulations. In the United States, IBM has a process for the collection of this battery. For information,call 1-800-426-4333. Have the IBM part number for the battery unit available when you call. (C003)

    Power and cabling information for NEBS (Network Equipment-Building System)GR-1089-CORE

    The following comments apply to the IBM servers that have been designated as conforming to NEBS(Network Equipment-Building System) GR-1089-CORE:

    The equipment is suitable for installation in the following:v Network telecommunications facilitiesv Locations where the NEC (National Electrical Code) applies

    The intrabuilding ports of this equipment are suitable for connection to intrabuilding or unexposedwiring or cabling only. The intrabuilding ports of this equipment must not be metallically connected to theinterfaces that connect to the OSP (outside plant) or its wiring. These interfaces are designed for use asintrabuilding interfaces only (Type 2 or Type 4 ports as described in GR-1089-CORE) and require isolationfrom the exposed OSP cabling. The addition of primary protectors is not sufficient protection to connectthese interfaces metallically to OSP wiring.

    Note: All Ethernet cables must be shielded and grounded at both ends.

    The ac-powered system does not require the use of an external surge protection device (SPD).

    The dc-powered system employs an isolated DC return (DC-I) design. The DC battery return terminalshall not be connected to the chassis or frame ground.

    x System reference codes (Bxxx)

  • System reference codes (Bxxx) overview

    Reference codes are diagnostics aids that help you find solutions to system problems.

    Reference codes are diagnostic aids that help you determine the source of a hardware or operatingsystem problem. Using a reference code enables you to find the solution to fix the problem. To usereference codes effectively, you must use them in conjunction with other service and support procedures.

    Note: System reference codes (SRCs) often indicate failing items. Some failing items are required to beexchanged in groups until the problem is solved. Other failing items are flagged as mandatory exchangeand must be exchanged before the service action is complete, even if the problem appears to have beenrepaired. For more information, see “Block replacement of FRUs.”

    Block replacement of FRUsSometimes, multiple field replaceable units (FRUs) or procedures are called out for replacement by anSRC listed in the service action log (SAL). Each FRU or procedure has a priority, and procedures arealways in priority order, from highest to lowest priority. Follow the steps below:1. Perform all high priority or mandatory FRU replacements or procedures at the same time (as a block).2. If the problem persists after performing the high priority FRU replacements or procedures, then

    perform the medium priority FRU replacements or procedures one at a time, unless a mediumgrouping priority is associated with the FRUs or procedures that are called out in the SRC. A mediumgrouping priority, shown with an A, B, or C, means that you need to perform all the FRUreplacements or procedures in that group at the same time (as a block).

    3. Finally, if the problem still persists after performing the medium priority FRU replacements orprocedures, then perform the low priority FRU replacements or procedures one at a time.

    The priorities of performing the FRU replacements or procedures are shown in the following ways,depending on how you view the SRC:v Advanced System Management Interface (ASMI): The ASMI shows a priority with each callout in the

    log.v Control panel: The control panel shows one of the following priorities with each callout:

    – H = High– M = Medium– MA = Medium group A– MB = Medium group B– MC = Medium group C– L = Low

    v Management console: The details of the serviceable event display the FRU replacement priority ashigh, medium, and so on.

    v Service action log: In the SAL, the Part Action for the FRU in the view of the event shows thereplacement priority.

    © Copyright IBM Corp. 2010, 2017 1

  • 2 System reference codes (Bxxx)

  • (B002) Reference codes

    B0022321

    Explanation: Procedure error in vertical LicensedInternal Code.

    Failing Item:

    v UJE34

    B0022322

    Explanation: Data-set-ready error on modem interface.

    Failing Item:

    v UJE34

    B0022340

    Explanation: Data-set-ready changed to not active; forinformation only.

    Failing Item:

    v FI00704v UJB35v UJ0E3v FI00701

    B0022651

    Explanation: First call failed, retrying call; no CFIfrom modem.

    Response: The remote answer timer expired withoutthe system detecting either the rise of DSR or a callfailure indication from the modem. The system tries thecall again, up to the number of tries specified in thedial retry parameter of the controller description.

    Failing Item:

    v UJE34v UJB35v FI00704v FI00701

    B0022652

    Explanation: First call failed, retrying call; CFI ABfrom modem.

    Response: After dialing, the system detected a callfailure indication AB from the modem. The system triesthe call again, up to the number of tries specified in thedial retry parameter of the controller description. CFIAB is sent from the modem if the modem#csq;s timerexpires after answer tone was detected and before themodem is ready for data transfer.

    Failing Item:

    v UJ0E3v FI00704v UJB36

    B0022653

    Explanation: First call failed, retrying call; CFI DEfrom modem.

    Response: After dialing, the system detected a callfailure indication DE from the modem. The system triesthe call again, up to the number of tries specified in thedial retry parameter of the controller description. CFIDE is sent from the modem if the modem failed todetect a dial tone when expected or detected a dialtone when another tone was expected. This can occur ifthe telephone cable is not plugged into the back of themodem.

    Failing Item:

    v UJ0E3v FI00704

    B0022654

    Explanation: First call failed, retrying call; CFI ETfrom modem.

    Response: After dialing, the system detected a callfailure indication ET from the modem. The system triesthe call again, up to the number of tries specified in thedial retry parameter of the controller description. CFIET is sent from the modem if the modem detects abusy signal (engaged tone).

    Failing Item:

    v UJ0E3v UJB36

    B0022656

    Explanation: First call failed, retrying call; CFI NTfrom modem.

    Response: After dialing, the system detected a callfailure indication NT from the modem. The system triesthe call again, up to the number of tries specified in thedial retry parameter of the controller description. CFINT is sent from the modem if the modem#csq;s timerexpires without detecting an answer tone or a ringback, and had detected the expected dial tones. Thissituation could result from a person answering thetelephone.

    Failing Item:

    © Copyright IBM Corp. 2010, 2017 3

    http://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/uje34.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/uje34.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00704.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/uj0e3.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00701.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/uje34.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00704.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00701.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/uj0e3.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00704.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb36.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/uj0e3.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00704.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/uj0e3.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb36.htm

  • v UJ0E3v FI00705v UJB36

    B0022657

    Explanation: First call failed, retrying call; CFI RTfrom modem.

    Response: After dialing, the system detected a callfailure indication RT from the modem. The system triesthe call again, up to the number of tries specified in thedial retry parameter of the controller description. CFIRT is sent from the modem if the modem does notdetect the remote answer when the timer expired or themodem is still detecting ring back. This response is alsosent if the modem ends a call because the ring counterreached its limit.

    Failing Item:

    v UJ0E3v UJB36

    B0022660

    Explanation: Call failed, retrying call; Non-standardCFI from modem.

    Response: After dialing, the system detected a callfailure indication from the modem that was notrecognized. The system tries the call again, up to thenumber of tries specified in the dial retry parameter ofthe controller description.

    Failing Item:

    v UJ0E3v FI00704

    B0023200

    Explanation: Clear-to-send state changed; error limitper 256 reached.

    Failing Item:

    v FI00704v UJB35v FI00701v FI00719

    B0023201

    Explanation: Data-set-ready state changed; error limitper 256 reached.

    Failing Item:

    v FI00704v UJB35v FI00701v FI00719

    B0023202

    Explanation: Clear-to-send state changed; error limitper 256 reached.

    Failing Item:

    v FI00704v UJB35v FI00701v FI00719

    B0023203

    Explanation: Carrier-detect state changed; error limitper 256 reached.

    Failing Item:

    v FI00704v UJB35v FI00701v FI00719

    B0023204

    Explanation: Call not completed; error limit per 256reached.

    Failing Item:

    v UJB36v UJ0E3v FI00705v FI00703

    B0023205

    Explanation: Call completed with error; error limit per256 reached.

    Failing Item:

    v UJB35

    B0023206

    Explanation: Data-line-occupied error; error limit per256 reached.

    Failing Item:

    v FI00703v UJB35v UJ0E3v FI00702

    B0023207

    Explanation: Abandon-call-retry error; error limit per256 reached.

    Failing Item:

    B0022657 • B0023207

    4 System reference codes (Bxxx)

    http://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/uj0e3.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00705.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb36.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/uj0e3.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb36.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/uj0e3.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00704.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00704.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00701.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00704.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00701.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00704.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00701.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00704.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00701.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb36.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/uj0e3.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00705.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00703.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00703.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/uj0e3.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00702.htm

  • v FI00703v UJB35v UJ0E3v FI00702v UJB36

    B0023208

    Explanation: Present-next-digit error; error limit per256 reached.

    Failing Item:

    v FI00702v FI00703v UJB35v FI00719

    B0023209

    Explanation: Distant-station-connected error; errorlimit per 256 reached.

    Failing Item:

    v FI00703v UJB35v UJ0E3v FI00702v UJB36

    B002320B

    Explanation: Data-set-ready state changed; error limitper 256 reached.

    Failing Item:

    v FI00704v UJB35v UJ0E3v FI00701

    B002320C

    Explanation: Incorrect number dialed; error limit per256 reached.

    Failing Item:

    v UJB36v UJB35

    B0024200

    Explanation: Wrong data block received; error limitper 256 reached.

    Failing Item:

    v UJ0E3v UJB35

    v FI00719

    B0024201

    Explanation: Wrong data block received; error limitper 256 reached.

    Failing Item:

    v UJ0E3

    B0024202

    Explanation: Temporary text delay block sent; errorlimit per 256.

    Failing Item:

    v UJB35v UJB37

    B0024203

    Explanation: Wait-acknowledge block sent; error limitper 256 reached.

    Failing Item:

    v UJB35v UJB37

    B0024204

    Explanation: Incorrect data block sent; error limit per256 reached.

    Failing Item:

    v FI00730v FI00719v UJB35

    B0024205

    Explanation: Communications IOP cannot receive;limit reached.

    Failing Item:

    v FI00730v FI00719v UJB35

    B0024206

    Explanation: Receive-time-out error; error limit per256 reached.

    Failing Item:

    v FI00730v AJDG301

    B0023208 • B0024206

    (B002) Reference codes 5

    http://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00703.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/uj0e3.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00702.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb36.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00702.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00703.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00703.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/uj0e3.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00702.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb36.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00704.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/uj0e3.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00701.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb36.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/uj0e3.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/uj0e3.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb37.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb37.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htm

  • B0024207

    Explanation: Continuous synchronization on line;error limit reached.

    Failing Item:

    v UJ0E3

    B0024208

    Explanation: No synchronization received; error limitper 256 reached.

    Failing Item:

    v UJ0E3

    B0024209

    Explanation: Synchronous time-out; error limit per 256reached.

    Failing Item:

    v UJ0E3v FI00719v UJB35

    B0024220

    Explanation: Communications line already in use.

    Failing Item:

    v AJDG301v FI00719v UJB35

    B0024240

    Explanation: Adapter not installed.

    Failing Item:

    v AJDG301v FI00719v UJB35

    B0024340

    Explanation: V.25 adapter not installed.

    Failing Item:

    v AJDG301v UJB35v FI00719v FI00702

    B0024376

    Explanation: Automatic call unit already in use.

    Failing Item:

    v AJDG301v UJB35v UJC38

    B0024502

    Explanation: Incorrect command value sent by verticalLIC.

    Failing Item:

    v AJDG301v FI00730

    B0024503

    Explanation: Incorrect command value sent by verticalLIC.

    Failing Item:

    v AJDG301

    B0024504

    Explanation: Incorrect parts installed for BSCcommunications.

    Failing Item:

    v UJB35v AJDG301

    B0024505

    Explanation: Incorrect command value sent by verticalLIC.

    Failing Item:

    v AJDG301v UJB35v FI00730

    B0024506

    Explanation: Incorrect command value sent by verticalLIC.

    Failing Item:

    v AJDG301v UJB35v FI00730

    B0024207 • B0024506

    6 System reference codes (Bxxx)

    http://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/uj0e3.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/uj0e3.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/uj0e3.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00702.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc38.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htm

  • B0024508

    Explanation: Incorrect command value sent by verticalLIC.

    Failing Item:

    v AJDG301v FI00730

    B0024509

    Explanation: Incorrect command value sent by verticalLIC.

    Failing Item:

    v AJDG301v FI00730

    B002450A

    Explanation: Incorrect command value sent by verticalLIC.

    Failing Item:

    v AJDG301v FI00730v UJB35

    B002450B

    Explanation: Incorrect command value sent by verticalLIC.

    Failing Item:

    v AJDG301v FI00730

    B002450E

    Explanation: Call type not permitted.

    Failing Item:

    v AJDG301v FI00730v UJB35

    B0024590

    Explanation: Wrong telephone number specified insystem configuration.

    Failing Item:

    v UJB36v FI00703v UJ0E3v FI00702

    B0024592

    Explanation: No number specified in controllerdescription.

    Failing Item:

    v UJB36

    B0024594

    Explanation: Wrong telephone number specified insystem configuration.

    Failing Item:

    v UJB36v FI00730v AJDG301

    B0025410

    Explanation: Data-set-ready error on modem interface.

    Failing Item:

    v FI00704v UJB35v FI00702v FI00719

    B0025472

    Explanation: Data-line-occupied initially 'on' error.

    Failing Item:

    v FI00703v UJC38v FI00719v FI00702

    B0025474

    Explanation: Automatic call unit hasdata-line-occupied error.

    Failing Item:

    v FI00702v FI00703v FI00719v UJ0E3

    B0025476

    Explanation: Automatic call unit haspresent-next-digit error.

    Failing Item:

    v FI00703v FI00719v FI00702

    B0024508 • B0025476

    (B002) Reference codes 7

    http://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb36.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00703.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/uj0e3.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00702.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb36.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb36.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00704.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00702.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00703.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc38.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00702.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00702.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00703.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/uj0e3.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00703.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00702.htm

  • B0025501

    Explanation: Incorrect command value sent by verticalLIC.

    Failing Item:

    v AJDG301v FI00730

    B0025502

    Explanation: Incorrect command value sent by verticalLIC.

    Failing Item:

    v AJDG301v FI00730

    B0025503

    Explanation: Incorrect command value sent by verticalLIC.

    Failing Item:

    v AJDG301v FI00730

    B0025504

    Explanation: Incorrect command value sent by verticalLIC.

    Failing Item:

    v AJDG301v UJB35

    B0025505

    Explanation: Incorrect command value in I/O cardLIC.

    Failing Item:

    v FI00730

    B0025520

    Explanation: Incorrect command value sent by verticalLIC.

    Failing Item:

    v AJDG301v FI00730

    B0025521

    Explanation: Incorrect command value sent by verticalLIC.

    Failing Item:

    v AJDG301

    v FI00730

    B0025549

    Explanation: Incorrect command value sent by verticalLIC.

    Failing Item:

    v AJDG301v FI00730

    B0025590

    Explanation: Too many dial digits in call setup.

    Failing Item:

    v UJB36

    B0025630

    Explanation: Automatic call unit hasdistant-station-connected error.

    Failing Item:

    v FI00700v UJ0E3v UJB35v FI00701v FI00719

    B0025632

    Explanation: Automatic call unit has data-set-readyerror.

    Failing Item:

    v FI00700v UJB36v FI00703v UJB35v FI00701v FI00719v UJ0E3

    B0025651

    Explanation: Call failed, no Call Failure Indicationfrom modem.

    Response: The remote answer timer expired withoutthe system detecting either the rise of DSR or a callfailure indication from the modem. The system hasreached the number of tries in the dial retry parameterin the controller description.

    Failing Item:

    v UJE34v UJB35

    B0025501 • B0025651

    8 System reference codes (Bxxx)

    http://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb36.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00700.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/uj0e3.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00701.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00700.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb36.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00703.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00701.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/uj0e3.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/uje34.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb35.htm

  • v FI00704v FI00701

    B0025684

    Explanation: Automatic call unit has call-clear error.

    Failing Item:

    v FI00704v FI00701v AJDG301v FI00719

    B0025886

    Explanation: Automatic call unit switched linktime-out; no answer.

    Failing Item:

    v FI00703v FI00719v UJ0E3v FI00702

    B0025A18

    Explanation: Clear-to-send signal failed to drop onmodem interface.

    Failing Item:

    v FI00704v FI00701v FI00719

    B0025A1C

    Explanation: Clear-to-send signal dropped on modeminterface.

    Failing Item:

    v UJ0E3v UJB35v FI00704v FI00701v FI00719

    B0025A20

    Explanation: Clear-to-send not active on modeminterface.

    Failing Item:

    v UJ0E3v UJB35v FI00704v FI00701v FI00719

    B0025A24

    Explanation: Carrier-detect dropped on modeminterface.

    Failing Item:

    v FI00701v FI00704v UJ0E3v FI00719

    B0025A54

    Explanation: Data-set-ready did not drop duringtime-out.

    Failing Item:

    v FI00704v UJB35v FI00701v FI00719

    B0025A58

    Explanation: Data-set-ready did not come up duringtime-out.

    Failing Item:

    v FI00701v FI00704v FI00719v AJDG301

    B0025C68

    Explanation: Too many user connections attempted.

    Failing Item:

    v AJDG301

    B0025E00

    Explanation: Wrong or no external communicationscable installed.

    Failing Item:

    v UJB35v FI00701v FI00719

    B0025E01

    Explanation: Call error; incoming call received duringoutgoing call.

    Failing Item:

    v UJC38v FI00704

    B0025684 • B0025E01

    (B002) Reference codes 9

    http://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00704.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00701.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00704.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00701.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00703.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/uj0e3.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00702.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00704.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00701.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/uj0e3.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00704.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00701.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/uj0e3.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00704.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00701.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00701.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00704.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/uj0e3.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00704.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00701.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00701.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00704.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00701.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc38.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00704.htm

  • v FI00701v FI00719

    B0026210

    Explanation: Communications controller storage notavailable.

    Failing Item:

    v UJB35v FI00730

    B0026212

    Explanation: Storage deallocation error.

    Failing Item:

    v FI00730

    B0026214

    Explanation: Storage allocation error.

    Failing Item:

    v FI00730

    B0026288

    Explanation: Port not operational.

    Failing Item:

    v FI00719v AJDG301v UJB35

    B0026320

    Explanation: Automatic call unit has abandon-callattempt.

    Failing Item:

    v FI00700v UJB36v FI00703v FI00719v FI00702

    B0026322

    Explanation: Abandon call retry error; incorrectnumber length.

    Failing Item:

    v FI00703v UJB36

    B0026870

    Explanation: Automatic call unit power turned off.

    Failing Item:

    v FI00703v FI00702v FI00719

    B0026890

    Explanation: Data-set-ready dropped on modeminterface.

    Failing Item:

    v UJ0E3v FI00701v FI00704v FI00719

    B0026C05

    Explanation: Error in I/O card Licensed InternalCode.

    Failing Item:

    v FI00730v AJDG301

    B0026C0A

    Explanation: Hardware detected failure.

    Failing Item:

    v FI00719v FI00718

    B0027210

    Explanation: Communications controller storage notavailable.

    Failing Item:

    v UJB35v FI00730

    B0027212

    Explanation: Communications program error.

    Failing Item:

    v FI00730v AJDG301

    B0026210 • B0027212

    10 System reference codes (Bxxx)

    http://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00701.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00700.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb36.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00703.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00702.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00703.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb36.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00703.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00702.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/uj0e3.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00701.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00704.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00718.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htm

  • B0027C00

    Explanation: Communications program error.

    Failing Item:

    v FI00730

    B0027C02

    Explanation: Communications program error.

    Failing Item:

    v FI00730

    B0027C03

    Explanation: Resource or storage not available.

    Failing Item:

    v UJB37v FI00730

    B0027C04

    Explanation: Communications program error.

    Failing Item:

    v FI00730

    B0027C05

    Explanation: Incorrect command value in I/O cardLIC.

    Failing Item:

    v FI00730

    B0027C09

    Explanation: Communications program error.

    Failing Item:

    v FI00730

    B002FFFF

    Explanation: User suspected communicationsproblem.

    Failing Item:

    v USER

    B0027C00 • B002FFFF

    (B002) Reference codes 11

    http://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb37.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/user.htm

  • 12 System reference codes (Bxxx)

  • (B003) Reference codes

    B0032321

    Explanation: Procedure error in vertical LicensedInternal Code.

    Failing Item:

    v UJE34

    B0032322

    Explanation: Data-set-ready error on modem interface.

    Failing Item:

    v UJE34

    B0032340

    Explanation: Data-set-ready changed to not active; forinformation only.

    Response:

    Failing Item:

    v FI00704v UJC35v FI00701v FI00719

    B0033200

    Explanation: Clear-to-send state changed; error limitper 256 reached.

    Response:

    Failing Item:

    v FI00704v UJC35v FI00701v FI00719

    B0033201

    Explanation: Data-set-ready state changed; error limitper 256 reached.

    Response:

    Failing Item:

    v FI00704v UJC35v FI00701v FI00719

    B0033202

    Explanation: Clear-to-send state changed; error limitper 256 reached.

    Response:

    Failing Item:

    v FI00704v UJC35v FI00701v FI00719

    B0033203

    Explanation: Carrier-detect state changed; error limitper 256 reached.

    Response:

    Failing Item:

    v FI00704v UJC35v FI00701v FI00719

    B0033204

    Explanation: Call not completed; error limit per 256reached.

    Failing Item:

    v UJC36v UJ0E3v FI00705v FI00703

    B0033205

    Explanation: Call completed with error; error limit per256 reached.

    Failing Item:

    v UJC35

    B0033206

    Explanation: Data-line-occupied error; error limit per256 reached.

    Failing Item:

    v FI00703v UJC35v UJ0E3v FI00702

    © Copyright IBM Corp. 2010, 2017 13

    http://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/uje34.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/uje34.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00704.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00701.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00704.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00701.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00704.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00701.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00704.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00701.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00704.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00701.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc36.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/uj0e3.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00705.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00703.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00703.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/uj0e3.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00702.htm

  • B0033207

    Explanation: Abandon-call-retry error; error limit per256 reached.

    Failing Item:

    v FI00703v UJC35v UJ0E3v FI00702v UJC36

    B0033208

    Explanation: Present-next-digit error; error limit per256 reached.

    Response:

    Failing Item:

    v FI00703v UJC35v FI00702v FI00719

    B0033209

    Explanation: Distant-station-connected error; errorlimit per 256 reached.

    Failing Item:

    v FI00703v UJC35v UJ0E3v FI00702v UJC36

    B003320B

    Explanation: Data-set-ready state changed; error limitper 256 reached.

    Response:

    Failing Item:

    v FI00704v UJC35v FI00701v FI00719

    B003320C

    Explanation: Incorrect number dialed; error limit per256 reached.

    Failing Item:

    v UJC36v UJC35

    B0034200

    Explanation: Break character received; error limit per256 reached.

    Failing Item:

    v UJ0E3v UJC35

    B0034202

    Explanation: Received storage overrun; error limit per256 reached.

    Failing Item:

    v FI00730v UJC35

    B0034203

    Explanation: Incorrect stop bit; error limit per 256reached.

    Failing Item:

    v UJ0E3v UJC35

    B0034204

    Explanation: Receive-time-out error; error limit per256 reached.

    Failing Item:

    v UJC35v UJ0E3

    B0034205

    Explanation: Number of characters discarded; errorlimit per 256 reached.

    Failing Item:

    v UJ0E3v UJC35v UJB37

    B0034206

    Explanation: Procedure error in vertical LicensedInternal Code.

    Failing Item:

    v FI00730v AJDG301

    B0033207 • B0034206

    14 System reference codes (Bxxx)

    http://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00703.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/uj0e3.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00702.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc36.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00703.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00702.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00703.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/uj0e3.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00702.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc36.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00704.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00701.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc36.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/uj0e3.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/uj0e3.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/uj0e3.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/uj0e3.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb37.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htm

  • B0034209

    Explanation: Wrong data received; error limit per 256reached.

    Failing Item:

    v UJ0E3v UJC35

    B0034220

    Explanation: Port already in use.

    Response:

    Failing Item:

    v AJDG301v FI00719v UJC35

    B0034240

    Explanation: Port not installed.

    Response:

    Failing Item:

    v AJDG301v FI00719v UJC35

    B0034340

    Explanation: Automatic call unit port is not installed.

    Response:

    Failing Item:

    v AJDG301v UJC35v FI00719v FI00702

    B0034376

    Explanation: Automatic call unit already in use.

    Failing Item:

    v AJDG301v UJC38v UJC35

    B0034502

    Explanation: Wrong configuration value sent byvertical LIC.

    Failing Item:

    v AJDG301v FI00730

    B0034503

    Explanation: Wrong configuration value sent byvertical LIC.

    Failing Item:

    v AJDG301v FI00730v UJC35

    B0034504

    Explanation: Wrong configuration value sent byvertical LIC.

    Failing Item:

    v AJDG301v UJC35

    B0034505

    Explanation: Wrong configuration value sent byvertical LIC.

    Failing Item:

    v AJDG301v UJC35v FI00730

    B0034506

    Explanation: Wrong configuration value sent byvertical LIC.

    Failing Item:

    v AJDG301v UJC35v FI00730

    B0034507

    Explanation: Wrong configuration value sent byvertical LIC.

    Failing Item:

    v AJDG301v FI00730v UJC35

    B0034508

    Explanation: Wrong configuration value sent byvertical LIC.

    Failing Item:

    v AJDG301v FI00730

    B0034209 • B0034508

    (B003) Reference codes 15

    http://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/uj0e3.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00702.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc38.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htm

  • B0034509

    Explanation: Wrong configuration value sent byvertical LIC.

    Failing Item:

    v AJDG301v UJC35v FI00730

    B003450A

    Explanation: Wrong configuration value sent byvertical LIC.

    Failing Item:

    v AJDG301v FI00730v UJC35

    B003450B

    Explanation: Wrong configuration value sent byvertical LIC.

    Failing Item:

    v AJDG301v FI00730

    B003450C

    Explanation: Wrong configuration value sent byvertical LIC.

    Failing Item:

    v AJDG301v FI00730

    B003450D

    Explanation: Wrong configuration value sent byvertical LIC.

    Failing Item:

    v UJC35v FI00730v AJDG301

    B003450E

    Explanation: Wrong configuration value sent byvertical LIC.

    Failing Item:

    v AJDG301v FI00730v UJC35

    B0034549

    Explanation: Wrong configuration value sent byvertical LIC.

    Failing Item:

    v AJDG301v FI00730

    B0034590

    Explanation: Wrong number specified in controllerdescription.

    Response:

    Failing Item:

    v UJC36v FI00703v FI00701v UJC35v FI00719

    B0034592

    Explanation: No number specified in controllerdescription.

    Failing Item:

    v AJDG301v UJC36

    B0034594

    Explanation: Wrong number specified in controllerdescription.

    Failing Item:

    v UJC36v FI00730v AJDG301v UJC35

    B0035410

    Explanation: Switched line already in use.

    Response:

    Failing Item:

    v FI00704v UJC35v FI00701v FI00719

    B0034509 • B0035410

    16 System reference codes (Bxxx)

    http://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc36.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00703.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00701.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc36.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc36.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00704.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00701.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htm

  • B0035472

    Explanation: Data-line-occupied error at time ofstarting.

    Response:

    Failing Item:

    v FI00703v UJC38v FI00719v FI00702

    B0035474

    Explanation: Automatic call unit line connection error.

    Response:

    Failing Item:

    v FI00702v FI00703v FI00719v UJ0E3

    B0035476

    Explanation: Present-next-digit error.

    Response:

    Failing Item:

    v FI00702v FI00703v FI00719

    B0035501

    Explanation: Wrong configuration value sent byvertical LIC.

    Failing Item:

    v AJDG301v FI00730

    B0035502

    Explanation: Wrong configuration value sent byvertical LIC.

    Failing Item:

    v AJDG301v UJC35v FI00730

    B0035503

    Explanation: Wrong configuration value sent byvertical LIC.

    Failing Item:

    v AJDG301v UJC35v FI00730

    B0035510

    Explanation: Wrong configuration value sent byvertical LIC.

    Failing Item:

    v AJDG301v UJC35v FI00730

    B0035511

    Explanation: Wrong configuration value sent byvertical LIC.

    Failing Item:

    v AJDG301v FI00730

    B0035512

    Explanation: Wrong configuration value sent byvertical LIC.

    Failing Item:

    v AJDG301v FI00730

    B0035513

    Explanation: Wrong configuration value sent byvertical LIC.

    Failing Item:

    v AJDG301v UJC35v FI00730

    B0035514

    Explanation: Wrong configuration value sent byvertical LIC.

    Failing Item:

    v AJDG301v FI00730

    B0035472 • B0035514

    (B003) Reference codes 17

    http://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00703.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc38.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00702.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00702.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00703.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/uj0e3.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00702.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00703.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htm

  • B0035515

    Explanation: Wrong configuration value sent byvertical LIC.

    Failing Item:

    v AJDG301v UJC35v FI00730

    B0035549

    Explanation: Wrong configuration value sent byvertical LIC.

    Failing Item:

    v AJDG301v FI00730

    B0035590

    Explanation: Wrong length for number dialed.

    Failing Item:

    v AJDG301

    B0035630

    Explanation: Automatic call unit distant-station-connected time out.

    Failing Item:

    v FI00700v UJ0E3v UJC35v FI00701v FI00719

    B0035632

    Explanation: Automatic call unit had data-set-readytime out.

    Response:

    Failing Item:

    v FI00700v UJC35v UJC36v FI00703v FI00701v FI00719v UJ0E3

    B0035684

    Explanation: Time-out on call-clear-request.

    Response:

    Failing Item:

    v FI00704v FI00701v AJDG301v FI00719

    B0035886

    Explanation: Automatic call unit line connection error.

    Failing Item:

    v FI00704v FI00719v FI00701

    B0035A18

    Explanation: Clear-to-send signal failed to drop onmodem interface.

    Response:

    Failing Item:

    v FI00704v FI00701v FI00719

    B0035A1C

    Explanation: Clear-to-send signal dropped on modeminterface.

    Response:

    Failing Item:

    v UJ0E3v UJC35v FI00704v FI00701v FI00719

    B0035A20

    Explanation: Clear-to-send not active on modeminterface.

    Response:

    Failing Item:

    v UJ0E3v UJC35v FI00704v FI00701

    B0035515 • B0035A20

    18 System reference codes (Bxxx)

    http://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00700.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/uj0e3.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00701.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00700.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc36.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00703.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00701.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/uj0e3.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00704.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00701.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00704.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00701.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00704.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00701.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/uj0e3.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00704.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00701.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/uj0e3.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00704.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00701.htm

  • v FI00719

    B0035A24

    Explanation: Carrier-detect dropped on modeminterface.

    Response:

    Failing Item:

    v FI00701v FI00704v UJ0E3v FI00719

    B0035A54

    Explanation: Time-out; data-set-ready did not drop.

    Response:

    Failing Item:

    v FI00704v UJC35v FI00701v FI00719

    B0035A58

    Explanation: Time-out; data-set-ready not received.

    Response:

    Failing Item:

    v FI00701v FI00704v FI00719v AJDG301

    B0035C68

    Explanation: Procedure error in vertical LicensedInternal Code.

    Failing Item:

    v AJDG301v FI00730

    B0035E00

    Explanation: Wrong or no external communicationscable installed.

    Response:

    Failing Item:

    v FI00701v UJC35v FI00719

    B0035E01

    Explanation: Call received during dialing procedure.

    Response:

    Failing Item:

    v UJC38v FI00704v FI00701v FI00719

    B0036210

    Explanation: Resource or storage not available.

    Failing Item:

    v UJC35v FI00730

    B0036212

    Explanation: Communications controller error.

    Response:

    Failing Item:

    v FI00730v FI00718

    B0036214

    Explanation: Communications controller error.

    Response:

    Failing Item:

    v FI00730v FI00718

    B0036288

    Explanation: Port not operational.

    Response:

    Failing Item:

    v FI00719v AJDG301v UJC35

    B0036320

    Explanation: Abandon-call-retry.

    Response:

    Failing Item:

    v FI00700v UJC36v FI00703

    B0035A24 • B0036320

    (B003) Reference codes 19

    http://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00701.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00704.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/uj0e3.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00704.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00701.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00701.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00704.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00701.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc38.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00704.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00701.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00718.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00718.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00700.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc36.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00703.htm

  • v FI00719v FI00702

    B0036322

    Explanation: Abandon-call-retry; not all numbersdialed.

    Response:

    Failing Item:

    v UJC36v FI00703v FI00702v FI00719v FI00730

    B0036870

    Explanation: Automatic call unit power turned off.

    Response:

    Failing Item:

    v FI00703v FI00702v FI00719

    B0036890

    Explanation: Data-set-ready dropped on modeminterface.

    Response: No action is required if Operations Consoleis attached.

    Failing Item:

    v UJ0E3v FI00701v FI00704v FI00719

    B0036C05

    Explanation: I/O card Licensed Internal Code error.

    Failing Item:

    v FI00730v AJDG301

    B0036C0A

    Explanation: Hardware detected failure.

    Response:

    Failing Item:

    v FI00719v FI00718

    B0037200

    Explanation: Communications Configuration.

    Failing Item:

    v UJC35

    B0037210

    Explanation: Resource or storage not available.

    Failing Item:

    v UJC35v FI00730

    B0037212

    Explanation: Procedure error in vertical LicensedInternal Code.

    Failing Item:

    v AJDG301v FI00730

    B0037C00

    Explanation: Asynchronous server program endedabnormally.

    Failing Item:

    v FI00730

    B0037C02

    Explanation: Wrong command sent by verticalLicensed Internal Code.

    Failing Item:

    v FI00730

    B0037C03

    Explanation: Resource or storage not available.

    Failing Item:

    v UJB37v UJC35v FI00730

    B0037C04

    Explanation: Wrong internal routing information.

    Failing Item:

    v FI00730

    B0036322 • B0037C04

    20 System reference codes (Bxxx)

    http://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00702.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc36.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00703.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00702.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00703.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00702.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/uj0e3.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00701.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00704.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00719.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00718.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ajdg301.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujb37.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/ujc35.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/p7eb7/fi00730.htmhttp://publib.boulder.ibm.com