IBM Support

PI91174: MOVE STATEMENT BETWEEN 1 BYTE DATA ITEMS NOT EXECUTED

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • MOVE statement between 1 byte data items not executed
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of the IBM Automatic Binary        *
    *                 Optimizer (ABO) for z/OS                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: In rare cases a MOVE statement between  *
    *                      1 byte data items of the same display,  *
    *                      internal decimal or alphanumeric type   *
    *                      may not be executed in the specific     *
    *                      set of conditions below.                *
    *                                                              *
    *                      For example, a statement such as MOVE   *
    *                      X TO Y may not be executed when:        *
    *                                                              *
    *                      - the data items X and Y are each 1     *
    *                      byte and declared to be the same        *
    *                      display, internal decimal or            *
    *                      alphanumeric type                       *
    *                      - the data items X and Y are declared   *
    *                      to be directly adjacent in storage      *
    *                      - the MOVE X TO Y statement directly    *
    *                      follows a conditionally executed block  *
    *                      of code                                 *
    *                      - the conditionally executed block of   *
    *                      code contains a single MOVE statement   *
    *                      of a literal to data item X             *
    *                                                              *
    *                      Example source for one case is below:   *
    *                                                              *
    *                             DATA DIVISION.                   *
    *                             WORKING-STORAGE SECTION.         *
    *                             01  WS-GROUP.                    *
    *                                 05 X   PIC 9(1).             *
    *                                 05 Y   PIC 9(1).             *
    *                             PROCEDURE DIVISION.              *
    *                                 IF some-condition            *
    *                                    MOVE 1 TO X.              *
    *                                 MOVE X TO Y.                 *
    *                                                              *
    *                      When some-condition is false the        *
    *                      conditional block is not executed, and  *
    *                      due to the problem described in this    *
    *                      APAR, the MOVE X to Y statement is      *
    *                      also not executed.                      *
    *                                                              *
    *                      When some-condition is true the         *
    *                      conditional block is executed and the   *
    *                      MOVE X to Y statement will be executed  *
    *                      so the problem described in this APAR   *
    *                      does not happen.                        *
    *                                                              *
    *                      The correct behavior is that the MOVE   *
    *                      X to Y statement should be executed     *
    *                      regardless of the value of              *
    *                      some-condition.                         *
    ****************************************************************
    * RECOMMENDATION: Apply provided service                       *
    ****************************************************************
    ABO was modified to correctly optimize these modules
    

Problem conclusion

  • The ABO optimized module now behaves correctly for these MOVE
    statements
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI91174

  • Reported component name

    AUTO BINARY OPT

  • Reported component ID

    5697AB100

  • Reported release

    130

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-12-06

  • Closed date

    2017-12-06

  • Last modified date

    2018-01-03

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

    PI89894

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

    UI52466 UI52467

Modules/Macros

  • BOZBXITA BOZEXE1  BOZJIVP  BOZMSGE  BOZMSGK  BOZMSGT  BOZOBJ1
    BOZOPT   BOZRIDT  BOZSRC1
    

Fix information

  • Fixed component name

    AUTO BINARY OPT

  • Fixed component ID

    5697AB100

Applicable component levels

  • R130 PSY UI52466

       UP17/12/08 P F712

  • R13J PSY UI52467

       UP17/12/08 P F712

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":"SSERQD","label":"IBM Automatic Binary Optimizer for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"130","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"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":"130","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
03 January 2018