IBM Support

PH69636: IVPS CONTAIN MOVE THAT INTRODUCES INVALID DATA

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The "MOVE CVIVNMBR OF PVICBLC TO VIVWORK." line of code in the
    IVP job CQIPGM1 initializes SEED, a PIC 9(9)V9(7) USAGE DISPLAY
    data item, to SPACES. This can cause an issue if a client
    compiles the IVP with NUMPROC(PFD) and a high-enough ARCH level
    to use vector instructions.
    

Local fix

  • Use
    
    INITIALIZE VIVWORK
    
    instead of
    
    MOVE CVIVNMBR OF PVICBLC TO VIVWORK
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of IBM Automatic Binary Optimizer      *
    *                 (ABO) for z/OS 2.3, and ABO for z/OS 2.3     *
    *                 Trial attempting to use the IVP programs to  *
    *                 validate their ABO installation who compile  *
    *                 the IVP programs with NUMPROC(PFD) and       *
    *                 ARCH(14) or higher.                          *
    ****************************************************************
    * PROBLEM DESCRIPTION: IVP program BOZSRC1 abends with a S0C7  *
    *                      abend.                                  *
    ****************************************************************
    * RECOMMENDATION: Apply the provided PTF                       *
    ****************************************************************
    The MOVE statement as written moves SPACES to all data items in
    VIVWORK, causing SEED, a PIC 9(9)V9(7) USAGE DISPLAY data item,
    to contain invalid data. An instruction generated at ARCH(14) or
    above when NUMPROC(PFD) is specified, abends when using this
    invalid data.
    

Problem conclusion

  • IVP program BOZSRC1 was changed, replacing "MOVE CVIVNMBR OF
    PVICBLC TO VIVWORK" with "INITIALIZE VIVWORK" to avoid creating
    an invalid data situation.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH69636

  • Reported component name

    AUTO BINARY OPT

  • Reported component ID

    5697AB200

  • Reported release

    230

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2026-01-12

  • Closed date

    2026-01-15

  • Last modified date

    2026-02-01

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

    PH69431

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

Modules/Macros

  • BOZACCEP BOZALLOC BOZAPPLY BOZAUPLE BOZBXITA BOZCIAPJ BOZCICPJ
    BOZCICPR BOZCICSJ BOZCICSR BOZDDDEF BOZEQCWI BOZEXE1  BOZGLUE
    BOZJCLE  BOZJIVP  BOZMCTPA BOZMSGE  BOZMSGK  BOZMSGT  BOZOBJ1
    BOZOBJ2  BOZOPT   BOZPA    BOZPAJ   BOZRECV  BOZRECV1 BOZRIDT
    BOZSETRT BOZSMF   BOZSMFJ  BOZSMFR  BOZSMPE  BOZSRC1  BOZSRC2
    BOZTRUE
    

Fix information

  • Fixed component name

    AUTO BINARY OPT

  • Fixed component ID

    5697AB200

Applicable component levels

  • R230 PSY UO06487

       UP26/01/30 P F601

  • R23J PSY UO06488

       UP26/01/30 P F601

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":"BU048","label":"IBM Software"},"Product":{"code":"SSERQD","label":"IBM Automatic Binary Optimizer for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"2.3.0","Line of Business":{"code":"LOB70","label":"Z TPS"}}]

Document Information

Modified date:
01 February 2026