IBM Support

PH28090: DELETE_BEFORE_INSERT not applied when no rows in EXTRACT

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Customer is performing INSERT processing in BATCH and specified
    the DELETE_BEFORE_INSERT YES keyword.
    Optim is ignoring the DELETE request when the used EXTRACT file
    contains no rows.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Optim users performing INSERT processing     *
    *                 with DELETE_BEFORE_INSERT request.           *
    ****************************************************************
    * PROBLEM DESCRIPTION: Optim does not honor the "Delete before *
    *                      INSERT" request when the EXTRACT file   *
    *                      has no rows.                            *
    ****************************************************************
    The decision to ignore the DELETE_BEFORE_INSERT request,
    when the EXTRACT file contains 0 rows for all tables was a
    deliberate one.
    

Problem conclusion

  • Optim processing will be changed to perform an INSERT request
    when the EXTRACT file contains 0 rows.
    This means that a DELETE_BEFORE_INSERT request will be honored
    at all times.
    Note that this a change in the existing product behavior and
    users may need to adjust their processing based on the new
    behavior.
    The following Optim publications will be updated to document the
    new behavior:
    o Utilities Guide,
    o Common Elements.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH28090

  • Reported component name

    OPTIM MOVE FOR

  • Reported component ID

    5655V0700

  • Reported release

    B70

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-07-31

  • Closed date

    2020-08-20

  • Last modified date

    2020-09-01

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

    PH28085

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

Modules/Macros

  • FOP9APIM FOPCFPMN FOPHSTM  FOPMAIN  FOPMAMAI FOPMDPRC FOPMDXTR
    FOPMMCMR FOPMMJBS FOPMMUTL FOPOMN   FOPRS9   FOPZFMMN
    

Fix information

  • Fixed component name

    OPTIM MOVE FOR

  • Fixed component ID

    5655V0700

Applicable component levels

  • RB70 PSY UI71165

       UP20/08/25 P F008

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"},"Platform":[{"code":"PF054","label":"z Systems"}],"Version":"B70"}]

Document Information

Modified date:
02 September 2020