PI98510: ABENDS0C4, ABENDU1017, IEA705I

APAR status

• Closed as duplicate of another APAR.

Error description

• (HPU5.1 only) An ABENDS0C4 occurs during a logical unload
  (OUTDDN opion) involving a conversion from a char constant to a
  char/varchar/graphic/vargraphic/binary/varbinary field too short
  to contain the whole data once converted to the output format.
  .
  This occurs only if the following conditions are fulfilled:
  - the unload is performed in native mode
  - the character loss notification feature is enabled, i.e. the
  value determined from the CHARACTER_LOSS option from the OPTIONS
  block if any and from VUU071/LOSSCHAR in parmlib otherwise is
  different from IGNORE.
  
  For example, the following unload fails:
  GLOBAL OPTIONS CHARACTER_LOSS WARNING ;
  UNLOAD  TABLESPACE
  SELECT '12345', ACCOUNT_ID, WITHDRAW
  INTO EXCERPT_ID CHAR(4)
  FROM me.mytable
  OUTDDN(SYSREC)
  
  Local fix: solve the trivial truncation situation or accept it
  by specifying CHARACTER_LOSS IGNORE or force the SQL mode by
  specifying DB2 FORCE.
  PB52778
  
  An ABENDS0C4 occurs during a logical unload (OUTDDN opion)
  involving a conversion from a char constant to a
  char/varchar/graphic/vargraphic/binary/varbinary field too short
  to contain the whole data once converted to the output format.
  
  This occurs only if the following conditions are fulfilled:
  - the unload is performed in native mode
  - the character loss notification feature is enabled, i.e. the
  value determined from the CHARACTER_LOSS option from the OPTIONS
  block if any and from VUU071/LOSSCHAR in parmlib otherwise is
  different from IGNORE.
  For example, the following unload fails:
  GLOBAL OPTIONS CHARACTER_LOSS WARNING ;
  UNLOAD  TABLESPACE
  SELECT '12345', ACCOUNT_ID, WITHDRAW
  INTO EXCERPT_ID CHAR(4)
  FROM me.mytable
  OUTDDN(SYSREC)
  Local fix: solve the trivial truncation situation or accept it
  by specifying CHARACTER_LOSS IGNORE or force the SQL mode by
  specifying DB2 FORCE.
  PB52833
  
  An ABENDS0C4 occurs during the unload of the LOB data from a
  subset of the partitions of a tablespace. This occurs if the
  following conditions are fullfilled :
  - the unload is run in SQL mode
  - LOB data is to be unloaded
  - the SPANNED YES options is specified
  - the SQLPART option specifies less partitions than the table
  space involved in the unload has
  PB52659
  
  HPU terminates in abend ABENDs0C4 with the following traceback :
  ohashLoad +00000022 506 INZUTILK
   _inzzpiltBuildTasksForPartitioned
   +0000061A 2392 INZUTILK
   _inzzpiltBuildTasksForParallelRead
   +00000314 2204 INZUTILK
   _inzzpiltUnload
   +00000136 3313 INZUTILK
   _inzzpiltUnloadThread
   +0000018A 1925 INZUTILK
   oenclaveBootXplink
  when the following conditions are fullfilled:
  - the unload is performed in native mode
  - a partition-by-range and a partition-by-growth are unloaded
  - the data from both tablespaces are to be unloaded into the
  same single (not a separate output dataset per partition)
  dataset
  - GBLPARAL YES and SUBTKSOF YES apply
  Local fix: specify GBLPARAL NO or SUBTKSOF NO.(HPU 5.1 only) HPU
  terminates in abend ABENDs0C4 with the following traceback :
  ohashLoad +00000022 506 INZUTILK
   _inzzpiltBuildTasksForPartitioned
   +0000061A 2392 INZUTILK
   _inzzpiltBuildTasksForParallelRead
   +00000314 2204 INZUTILK
   _inzzpiltUnload
   +00000136 3313 INZUTILK
   _inzzpiltUnloadThread
   +0000018A 1925 INZUTILK
   oenclaveBootXplink
  when the following conditions are fullfilled:
  - the unload is performed in native mode
  - a partition-by-range and a partition-by-growth are unloaded
  - the data from both tablespaces are to be unloaded into the
  same single (not a separate output dataset per partition)
  dataset
  - GBLPARAL YES and SUBTKSOF YES apply
  Local fix: specify GBLPARAL NO or SUBTKSOF NO.
  PB52665
  
  Intermittent ABENDS30A-24 occurs during any HPU job.
  PB52366
  An ABENDU1017 occurs when unloading LOB data in SQL mode when
  the following conditions are fulfilled:
  - the length of a LOB to be unloaded is greater than 65510 bytes
  - VUU041/ULOCSIZE > 65510
  Local fix: set VUU041/ULOCSIZE to a value less than 65510.
  
  An ABENDU1017 occurs when unloading LOB data in SQL mode when
  the following conditions are fulfilled:
  - the length of a LOB to be unloaded is greater than 65510 bytes
  - VUU041/ULOCSIZE > 65510
  
  Local fix: set VUU041/ULOCSIZE to a value less than 65510.
  
  (HPU 5.1 only) Various and unpredictable failure occur when
  unloading a formerly compressed table space that has been
  altered to remove compression and not reorganized since then.
  Some of the identified symptoms are:
  - incorrect data unloaded
  - 227 * EXPRESSION EVALUATION ERROR * ddname * column name
  - ABENDS0C4 with traceback as follows
    6     oenclaveWaitTerminatedThread
                      -1DAE2010              INZU
    CEE3841I A statement number is not available
    7     ozprocWaitForTerminated
                      +000000A2  867         INZU
    8     _inzzpiltWaitForOneTask
                      +0000012E  4978        INZU
    9     _inzzpiltWaitForAllTasks
                      +00000124  5126        INZU
    10    _inzzpiltUnload
                      +00000200  3353        INZU
    11    _inzzpiltUnloadThread
                      +0000018A  1929        INZU
  or as follows
    6     oenclaveWaitTerminatedThread
                      -1DAE2010              INZU
    CEE3841I A statement number is not available
    7     ozprocWaitForTerminated
                      +000000A2  867         INZU
    8     _inzzpiltWaitForOneTask
                      +0000012E  4978        INZU
    9     _inzzpiltWaitForAllTasks
                      +00000124  5126        INZU
    10    _inzzpiltUnload
                      +00000200  3353        INZU
    11    _inzzpiltUnloadThread
                      +0000018A  1929        INZU
  or with no traceback and a shymptom dump as follows:
  SYSTEM COMPLETION CODE=0C4  REASON CODE=00000011
     NO ACTIVE MODULE FOUND
     NAME=UNKNOWN
     DATA AT PSW  200EFB84 - D2FD4248  625ED2FD  4346635C
     AR/GR 0: 00000000/00000000_00000000   1:
  00000002/00000000_20089FBC
           2: 00000000/00000048_200EE4F0   3:
  00000000/00000000_1F41A950
           4: 00000000/00000000_203EE9C4   5:
  00000000/00000000_00000444
           6: 1FEE0E10/00000000_20AA5BED   7:
  E9D3D6C7/00000000_000001A9
           8: 00000000/00000000_200EFA88   9:
  00000000/00000000_20089FCC
           A: 00000000/00000000_20089FD0   B:
  00000000/00000048_21C4A110
           C: 00000000/00000048_1F462B5C   D:
  00000000/00000000_200EDD50
           E: 00000000/00000000_9F4192B0   F:
  00000000/00000000_1F462B5C
  
  Local fix: reorganize the tablespace to remove compressed data
  from the underlying LDSes.
  
  An ABENDS0C4 can occur when unloading XML or LOB data as LOB
  files into partitioned data sets. The issue was on encountered
  on a z/OS 1.11 system.
  
  PB52631
  PB52425
  

Local fix

• See above.
  

Problem summary

Problem conclusion

Temporary fix

Comments

•  Fix included in APAR PI98105/PTF UI56696
  

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