II13822: ABEND0C4 IN IEFAB482

APAR status

• Closed as canceled.

Error description

• Abend0C4 in IEFAB482 at UA07911 offset x'21D0'.
  An SVC99 was issued with the following text units:
   DALDDNAM  DDNAME = RESIN1
   DALSTATS  DATA SET STATUS = 08 - SHR
   DALDSSEQ  DATA SET SEQUENCE NUMBER = 0001
   DALVLCNT  VOLUME COUNT = 01
   DALLABEL  LABEL TYPE = 02
             -THE VOLUME HAS AN IBM STANDARD LABEL (SL)
   DALPRIVT  PRIVATE VOLUME
   DALNDISP  DATA SET NORMAL DISPOSITION = 08 - KEEP
   DALCDISP  DATA SET CONDITIONAL DISPOSITION = 08 - KEEP
   DALDEFER  DEFER SPECIFICATION
  The EDL for the above SIOT shows that there were 4 device pools
      3333302*
      3333304*
      3333303*
      3333301* and this is the device which was mixed device
               types in a device pool as follows:
  UNITNAME = 3333301*
  NAME TYPE = DEVICE POOL
  VIO = NO
  AFFINITY INDEX = 0480
  ASSOCIATED GENERIC = 3590-1
  ALLOCATION DEVICE TYPE = 78048083
  GROUP 0006 = 0562
  ASSOCIATED GENERIC = 3490
  ALLOCATION DEVICE TYPE = 78048081
  GROUP 0022 = 6600
  GROUP 0023 = 6601
  GROUP 0024 = 6602
  GROUP 0025 = 6603
  GROUP 0026 = 6604
  GROUP 0027 = 6605
  GROUP 0028 = 6606
  GROUP 0029 = 6607
  GROUP 002A = 6608
  GROUP 002B = 6609
  GROUP 002C = 660A
  GROUP 002D = 660B
  GROUP 002E = 660C
  GROUP 002F = 660D
  GROUP 0030 = 660E
  GROUP 0031 = 660F
  .
  In this case the units 6600 - 660F are VTS drives and device
  0562 is a D/T 3590. This should never happen.
  Found in Syslog from IPL was
  IEE476I UNIT 0562     INFORMATION 430
  IEE763I NAME= IOSCCMSG CODE= 0000000800000021
  IOS291I  CONFIGURATION DATA COULD NOT BE READ ON PATH(0562,A3)
           RC=21
  IEE763I NAME= IECTDSR2 CODE= 0000000800000000
  IEA437I TAPE LIBRARY DEVICE 0562 (33333-01) IS A DUPLICATE OF
          DEVICE 0562 (11630-02) AND IS BEING MARKED FOR DELETION
  IEE764I END OF IEE476I    RELATED MESSAGES
  .
  Notice the IOS291I message RC=21 for path A3,
  Explanation: IOS was unsuccessful in its attempt to
               read the configuration data for the specified
               device on the channel path identifier xx.
  21 - CDR could not be added to CDT because
       token NED of CDR does not match token NED
       of subsystem
  .
  From the IEA437I we see device 0562 being deleted from Library
  11630 where it belongs and added to VTS library 33333, this was
  caused by obtaining RDC data on path A3. Turns out that path
  A3 was incorrectly cabled into the VTS 33333 instead of ATL
  D/T3590 control unit 0560.
  Note that the incorrect devices seen in the AOM control blocks
  using IPCS command VERBX AOMIPCS 'CBDUMP' varied from IPL to
  IPL depending on which device had its RDC obtained on the
  path that was incorrectly cabled.
  .
  This could have been avoided by coding LIBID / PORTID in HCD for
  all devices in the ATL and VTS.
  
  Additional Symptoms:
       msgIGD330I -  ERROR OCCURRED DURING CBRXLCS PROCESSING.
                     NO DEVICE POOLS TO FULFILL REQUEST FOR THE
                     SPECIFIED RECORDING
       msgIGD306I UNEXPECTED ERROR DURING ?CBRXLCS PROCESSING
                  RETURN CODE 12 REASON CODE 66 (rc12 rsn66)
  
  Additional Keywords:
       msgIOS291I rc21, msgIEA437I
  

Local fix

• Correct the cabling error and IPL.
  

Problem summary

Problem conclusion

Temporary fix

Comments

• Closing to make available to view.
  

APAR Information

• 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