IBM Support

II09065: ABEND0C4 IN IEFAB482 AFTER D/T3495 D/T3494 CONTROL UNIT ADDITION SMS TAPE MSGCBR3710I MSGIEA437I MSGIEA438I MSGCBR3006I

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as canceled.

Error description

  • .
    See, also OW31830, OW33304, and OW33620.
         also OW35146, OW35488, OW35489 and OW43252.
    The best support is now OW56456 for CB built support.
    .
         For a new ATL see Section B.  For ATL modifications see
    Section A.
    .
    Section A:
     - You must have APAR OW24184 prior to the deletion of devices
       to successfully avoid an IPL.
     - When an ATL model change is done you must follow the steps
       below.
     - When new control units are added to a D/T3495 or D/T3494
       that will cause the address of the any string's devices
       to change
    you must:
      1. Activate an IODF deleting all devices from the library.
      2. Activate an IODF that defines all of the devices.
      3. MVS Vary online the devices in the library. This will
         create some control blocks.
         You expect to see the message:
         msgIEA437I TAPE LIBRARY DEVICE(DDD), ACTIVATE IODF=XX,
               IS REQUIRED
       4.Then do a final activate.
    
    OR
    
    1. Use APAR OA07505 to delete the library's dynamic CB's
       DS QL,nnnnn,DELETE where nnnnn is the LIBID
    
    IF you have IODEF with LIBID and LIBPORT
    2. Use QLIB LIST to display that the INACTIVE
       control blocks have been deleted.
    3. Use ACTIVATE IODF to redefine the devices.
    4. Use QLIB LIST to display that the ACTIVE control
       blocks are properly defined.
    
    IF LIBID and LIBPORT are not coded.
    
    2. MVS Vary online the devices in the library. This will
       create some control blocks.
       You expect to see the message:
       msgIEA437I TAPE LIBRARY DEVICE(DDD), ACTIVATE IODF=XX,
            IS REQUIRED
    3. Use ACTIVATE IODF to redefine the devices.
    4. Use QLIB LIST to display that the ACTIVE control
       blocks are properly defined.
    
    ********* OR ************
    
    Perform an OAM RESTART or vary OFF then ON of composite library.
    
    F OAM,RESTART
    
    V SMS,LIB(composite_lib_name),OFFLINE|ONLINE
    
    ********* OR ************
         IPL the system
    .
    Section B:
    When Installing an ATL you must follow the steps below.
     1. Activate an IODF that defines all of the devices.
     2. MVS Vary online the devices in the library.  This will
        This will create some control blocks.
        You expect to see the message:
         msgIEA437I TAPE LIBRARY DEVICE(DDD), ACTIVATE IODF=XX,
               IS REQUIRED
     3. Then do a final activate.
        This activate is required to build the EDT ( Eligible Device
        for MVS Allocation
    ********* OR ************
         IPL the system
    .
    Additional Data:
         If the above procedure is not followed, an abend0C4 can
    occur at IEFAB482 +x'CF0' (at UW09015) trying to get to a UCB,
    because the Allocation Algorith table UCB address (GRPUCBP)
    will have been overlaid with a group id (CVRGRPID).  This
    overlay is caused by device pools which contain duplicate
    devices.
         Due to the way Allocation calculates the Algorithm Table
    sizes, the duplicates are NOT counted to build the group list
    (because the count is based on a bitstring) but they ARE counted
    when filling in the groupID's.  This scheme should, normally,
    work, since device pools should never have overlapping devices.
    .
    Additional Symptoms:
    After migrating from version3 to version5 of HCD the following
    occurred on one system in the complex.
    When they issue the command LI SETCL,391,NONE, they receive the
    message:
    CBR3710I LIBSERV FAILURE OCCURRED FOR LIBRARY 10053 RC=C,
    RSN=C06
    This is an AOM return code which says:
        DFP - LSSDP NOT FOUND FOR UCB
              OR DRIVE NUMBER.
    .
    At IPL time on the failing system they received messages:
    IEA437I TAPE LIBRARY DEVICE (10053) DUPLICATE LIBRARY ID
    IEA438I THE FOLLOWING TAPE LIBRARY DEVICE ARE UNAVAILABLE:
    *
    We were unable to determine what had occurred but the
    corrective action was to follow the procedure outlined
    in this APAR to remove the devices and add them back.
    .
         Another symptom was abend0C4 in IEFAB4F2+x'EC' (at
    HBB5520).
           - a LISTEDT SHOWUNIT in the dump showed in the device
             pool for tape library each device number (700, 701,
             704, 705, 708, 709, 70C, and 70D.
           - a LI DISPDRV,IBM3494R showed 700, 701, 704, and 705
             listed twice eac.
           - a LI DISPDRV,700,12 showed each listed just once.
    The dump showed two distinct device pools with the same entries.
    .
    Additional Keywords:
    MSGCBR3710I MSGIEA437I MSGIEA438I
    CBR3710i IEA347i IEA438i
    D/T3590 3590 D/T3490 3490 D/T3480 3480
    msgCBR3006I CBR3006I
    MOVE ATL
    D/T3495 3495 D/T3494 3494
    5695DF113 110 1B0 1C0            howto
    ISSUER=IEFAB4ED,ERRCSECT=IEFBB404,ABEND0C4
    IEFAB4ED IEFBB404 IEFAB424 ABEND0C4 Secondary files
    
     Additional Diagnostic Data:
    The dump showed two distinct device pools with the same entries.
        Enter IPCS to display the library control blocks as follows:
         1. Use OPTION=0 to set SOURCE ==> ACTIVE, in order to
            display active system storage.
        2. Use OPTION=6 to enter the command:
           VERBX AOMIPCS 'CBDUMP'
           LSSCB   Each library is represented by an LSSCB.
           LSSDP   Each string in a library is represented by
                   an LSSDP.
           DPDEV   Contains the device number of each device in
                   a library string.
    The set of library control blocks prior to AOMDATA17 are the
    static set and are in use by the system now. The set after the
    AOMDATA17 are the dynamic set and will be in use after the next
    activate.
    To ensure that the activate will not render the library
    unavailable ensure there are no duplications of devices in the
    DPDEV under any LSSDP.
    An example of danger waiting to happen:
    LSSCB: 02AB0008
       +0000  BEYN..... LSSCB     BEYV..... 0101      BLEN..... 0000
       +000C  BLID..... 11928     BSER..... 011928    BNXT..... 02B3
       +0018  BDPA..... 02B38270  BNUM..... 00000007  BFLG..... 0400
       +0024  BSIZ..... 00000000  BMSC..... 00000000  00000000
              BEND.....
    
    LSSDP: 02B38270
       +0000  PEYN..... LSSDP     PEYV..... 0101      PLEN..... 0000
       +000C  PID...... 1192806*  PNXT..... 02AB0C48  PDAD..... 02B3
       +001C  PNUM..... 00000004  PORT..... 06
    
    DPDEV: 02B382B0
       +0000  PDEV..... 16240000  PUCB..... 00F04DD0  RSV......
       +0008  PDEV..... 16250000  PUCB..... 00F04E98  RSV......
       +0010  PDEV..... 16340000  PUCB..... 00F05A50  RSV......
       +0018  PDEV..... 16350000  PUCB..... 00F05B18
    
    LSSDP: 0D0E12C0
       +0000  PEYN..... LSSDP     PEYV..... 0101      PLEN..... 0000
       +000C  PID...... 1192801*  PNXT..... 0D0E1320  PDAD..... 0D0E
       +001C  PNUM..... 00000004  PORT..... 01
    
    DPDEV: 0D0E1300
       +0000  PDEV..... 16380000  PUCB..... 00F05D70  RSV......
       +0008  PDEV..... 16390000  PUCB..... 00F05E38  RSV......
       +0010  PDEV..... 16200000  PUCB..... 00F04AB0  RSV......
       +0018  PDEV..... 16210000  PUCB..... 00F04B78
    
    LSSDP: 0D0E1320
       +0000  PEYN..... LSSDP     PEYV..... 0101      PLEN..... 0000
       +000C  PID...... 1192807*  PNXT..... 00000000  PDAD..... 0D0E
       +001C  PNUM..... 00000004  PORT..... 07
    
    DPDEV: 0D0E1360
       +0000  PDEV..... 16200000  PUCB..... 00F04AB0  RSV......
       +0008  PDEV..... 16210000  PUCB..... 00F04B78  RSV......
       +0010  PDEV..... 16380000  PUCB..... 00F05D70  RSV......
       +0018  PDEV..... 16390000  PUCB..... 00F05E38
    Ports 1 and 7 have duplicates and will cause the library to be
    unusable on the next activate. The only way out is IPL.
       Note: if VERBX AOMIPCS 'CBDUMP' does not  work try
             VERBX AOMDATA 'CBDUMP'
    
    In the following case where Port 6 (the real one) with devices
    1638 and 1639 was not available at Activate time and was added
    to the System after a CE repair action. Since the incorrect
    devices are first found in Port 6 and they are physically now
    on Port 7 we were able to correct the control blocks with 5
    Activates and avoid an IPL (see below for details).
    LSSDP: 02B38270
       +0000  PEYN..... LSSDP     PEYV..... 0101      PLEN..... 0000
       +000C  PID...... 1192806*  PNXT..... 02AB0C48  PDAD..... 02B3
       +001C  PNUM..... 00000004  PORT..... 06
    
    DPDEV: 02B382B0
       +0000  PDEV..... 16340000  PUCB..... 00F04DD0  RSV......
       +0008  PDEV..... 16350000  PUCB..... 00F04E98  RSV......
       +0010  PDEV..... 16380000  PUCB..... 00F05A50  RSV......
       +0018  PDEV..... 16390000  PUCB..... 00F05B18
    LSSDP: 0D0E1320
       +0000  PEYN..... LSSDP     PEYV..... 0101      PLEN..... 0000
       +000C  PID...... 1192807*  PNXT..... 00000000  PDAD..... 0D0E
       +001C  PNUM..... 00000004  PORT..... 07
    
    DPDEV: 0D0E1360
       +0000  PDEV..... 16340000  PUCB..... 00F04DD0  RSV......
       +0008  PDEV..... 16350000  PUCB..... 00F04E98  RSV......
    
    The plan to avoid an IPL:
    
     1) Create an IODF (IODFxx) that is the same as the current one
        and delete devices 1634 and 1635.
    
     2) Activate the new IODF (IODFxx)
         Use IPCS with a source of ACTIVE. Command VERBX AOMIPCS
      'CBDUMP' ensure that 1634 and 1635 are removed from
      PORT 06
    
     3) Activate the original IODF (IODFdd for desired)
         This will generate UCB's for 1634 and 1635, but the DPDEV
      will show the old UCB.
    
     4) Activate the new IODF (IODFxx)
          This will remove 1634 and 1635 from PORT 07
          Use IPCS to verify.
    
     5) Activate the original IODF (IODFdd for desired)
         Use IPCS to verify 1634 and 1635 have been added to PORT
      07 and note the UCB address. IPCS Command LISTU 1634 and
      verify the address to be the same as the AOM CB's show.
    
     6) One more Activate to get the EDT built since LIBID and
        PORTID are not used.
    
    You should use IPCS Command VERBX AOMIPCS 'CBDUMP' to verify
    the expected results of each step.
    
    If all goes as expected you should be able to use the library
    at this point.
    
    To obtain the LIBID and PORTID :
    DS QT,210,RDC
     IEE459I 18.00.32 DEVSERV QTAPE 251
     UNIT DTYPE  DSTATUS CUTYPE  DEVTYPE  CU-SERIAL  DEV-SERIAL ACL
     0210 3490L  ON-NRD  3490C2A 3490C2A  0177-C4057 0177-C4057 I
       READ DEVICE CHARACTERISTIC
     3490543490540000 1FF8808000000000 0000000000000000 000000000000
     0115070200000000 4281000000000000 0000000000000000 000000000000
     **SN**Port number
     in this example the lib id is 011507 and the port is 02
    .
    activate empty configuration 5695df110 5695df113
    

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

  • this is a dummy apar
    

APAR Information

  • APAR number

    II09065

  • Reported component name

    V2 LIB INFO ITE

  • Reported component ID

    INFOV2LIB

  • Reported release

    001

  • Status

    CLOSED CAN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    1995-11-21

  • Closed date

    1995-11-21

  • Last modified date

    2013-04-17

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19N","label":"APARs - OS\/390 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSSN3L","label":"z\/OS Communications Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
17 April 2013