PK80957: BATCHCRD: 1) GETMAIN ERRORS ABENDS0C4 RUNNING HIGH VOLUME OF SQL 2) ENDLESS COLLECTION IF ELAPSED TIME NOT SPECIFIED

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• BatchCRD running large amounts of SQL with many subsystems gets
  FPEV0003S  DB1P GETMAIN 72 FAILED
  FPEV9999I LVLS/OMEGAMON XE PE/PM
  FPEV9999I VALU/PCHK
  FPEV9999I AB/S/0C4
  FPEV9999I AB/U/000
  FPEV9999I RIDS/FPEZCRD#l
  .
  Code will be added to prevent the large amount of storage and
  stop the job before it abends.
  This job is requesting too much data. Job needs to be broken
  into smaller requests to get the needed data.
  

Local fix

• Break up job to request smaller amounts of data.
  Apply ptf to prevent the abend0c4 and job will end much sooner
  and large amounts of storage will be prevented before the job
  ends.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
  *                 users of component:                          *
  *                 -   Batch CRD                                *
  *                 -   Performance Warehouse users              *
  ****************************************************************
  * PROBLEM DESCRIPTION: If the IFCID that are collected are     *
  *                      generating a high workload in DB2 (CPU  *
  *                      and memory), it may happen that an      *
  *                      Out of Memory exception occurs. In this *
  *                      case a S0C4 happens.                    *
  ****************************************************************
  * RECOMMENDATION: Apply this PTF                               *
  ****************************************************************
  PROBLEM SUMMARY:
  A freemem was called in case the getmem was not successful.
  Now the freemem is only called if the getmem returns with 0.
  In the case the getmem (Out Of Memory) was not successful,
  the BatchCRD is stopped.
  The elapsed time is only relevant if the GDG dataset is not
  used. If GDG is used, the elapsed time is the time when the
  job is switching to the next GDG member.
  
  PROBLEM CONCLUSION:
  The allocated memory is only freed if the memory could be
  allocated correctly. The elapsed time is only relevant in case
  the OUTPUT dataset is specifed. If GDG is used, the elapsed time
  time when the job is switching to the next GDG member.
  In case an out of memory is happening, the batch job will end.
  

Problem conclusion

• The allocated memory is only freed if the memory could be
  allocated correctly. The elapsed time is only relevant in case
  the OUTPUT dataset is specifed. If GDG is used, the elapsed time
  time when the job is switching to the next GDG member.
  In case an out of memory is happening, the batch job will end.
  
  KEYWORDS :
  BATCHCRD FPEZCRD 0C4 PWH TASK RUNNING OUT OF MEMORY
  

Temporary fix

Comments

APAR Information

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

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

  UK45783

Modules/Macros

• FPEZCRD
  

Fix information

• Fixed component name

  OM XE DB2PE/PM

• Fixed component ID

  5655OPE00

Applicable component levels

• R410 PSY UK45783

     UP09/04/23 P F904

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.