IBM Support

PI89818: VARIOUS ISSUES WHEN CREATING A FIXED EXTERNAL OR DELIMITED LOADFILE AFTER MODIFYING MODEPARM FILE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The Fixed External and Delimited LOADFILEs are created from the
    formatted data. The ISPF front end correctly sets a flag so
    that formatting will not be skipped. However, when the MODEPARM
    file is updated the product was not processing the SKIP
    FORMATTING option properly. When the SKIP FORMATTING is set and
    the LOADFILEs need the data formatted, various issues can be
    encountered such as U=50 ABEND, U=88 ABEND, message ALAA041E,
    RC=2, and possibly other issues as well.
    

Local fix

  • Set the parameter "SKIP FORMATTING (WHEN POSSIBLE)....." to 'N'
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of ALA 350                             *
    ****************************************************************
    * PROBLEM DESCRIPTION: ***********PI89818********************* *
    *                      The Fixed External and Delimited        *
    *                      LOADFILEs are created from the          *
    *                      formatted data. The ISPF front end      *
    *                      correctly sets a flag so                *
    *                      that formatting will not be skipped.    *
    *                      However, when the MODEPARM              *
    *                      file is updated the product was not     *
    *                      processing the SKIP                     *
    *                      FORMATTING option properly. When the    *
    *                      SKIP FORMATTING is set and              *
    *                      the LOADFILEs need the data formatted,  *
    *                      various issues can be                   *
    *                      encountered such as U=50 ABEND,         *
    *                      U=88 ABEND,                             *
    *                      message ALAA041E,                       *
    *                      RC=2, and possibly other issues as well *
    *                                                              *
    *                                                              *
    *                                                              *
    ****************************************************************
    * RECOMMENDATION: Apply the PTF                                *
    ****************************************************************
    

Problem conclusion

  • Apply the PTF
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI89818

  • 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-11-03

  • Closed date

    2017-11-16

  • Last modified date

    2017-12-02

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

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

Modules/Macros

  • ALALB2
    

Fix information

  • Fixed component name

    DB2 LOG ANALYSI

  • Fixed component ID

    5655E6601

Applicable component levels

  • R350 PSY UI51958

       UP17/11/29 P F711

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:
02 December 2017