IBM Support

PI86542: ALAA470E DURING LOAD ON 32K PAGESIZES

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When an object has a record length that approaches the maximum
    allowed by DB2, the process to generate a LOADFILE could fail
    with an ALAA470E due to headers whether requested or forced for
    object identification.
    .
    This APAR will allow the LOADFILE / LOADCARD to still be
    generated as long as the last column is a VARCHAR and the actual
    length of the VARCHAR data along with the length of the rest of
    the data in the record being created does not exceed 32752.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of ALA350                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: *****PI86542*****                       *
    *                      When an object has a record length      *
    *                      that approaches the maximum             *
    *                      allowed by DB2, the process to          *
    *                      generate a LOADFILE could fail          *
    *                      with an ALAA470E due to headers         *
    *                      whether requested or forced for         *
    *                      object identification.                  *
    *                      .                                       *
    *                      This APAR will allow the                *
    *                      LOADFILE / LOADCARD to still be         *
    *                      generated as long as the last column    *
    *                      is a VARCHAR and the actual             *
    *                      length of the VARCHAR data along with   *
    *                       the length of the rest of              *
    *                      the data in the record being created    *
    *                      does not exceed 32752.                  *
    *                                                              *
    *                                                              *
    *                                                              *
    ****************************************************************
    * RECOMMENDATION: Apply the PTF                                *
    ****************************************************************
    

Problem conclusion

  • Apply the PTF
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI86542

  • Reported component name

    DB2 LOG ANALYSI

  • Reported component ID

    5655E6601

  • Reported release

    350

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-08-29

  • Closed date

    2017-10-19

  • Last modified date

    2017-11-01

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

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

    UI51274

Modules/Macros

  • ALAA72   ALACTAU  ALAETV   ALAGLOAD ALALFP
    ALALF1   ALAMSP   ALASBDB  ALASQ1CB ALATCZD  ALAZH030
    

Fix information

  • Fixed component name

    DB2 LOG ANALYSI

  • Fixed component ID

    5655E6601

Applicable component levels

  • R350 PSY UI51274

       UP17/10/25 P F710

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.

[{"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":"3.5.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
01 November 2017