IBM Support

PH28596: (1) OS/390 INDEXER MAY NOT PICK UP THE SECOND FIELD OF A TWO FIELD INDEX. (2) INPEXIT SUPPLIES INVALID DJDE.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • 1. When a FIELDnnn extends past the end of a line or is
    completely beyond the end of a physical record, the indexes
    generated are different than the 9.5 390 indexer.  This is
    noticeable when two fields are concatenated to form an index,
    and the first field extends past the physical record.
    
    2. When the INPEXIT supplies a DJDE for Global DJDE the DJDE
    is not stored correctly as a resource.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All Content Manager OnDemand for z/OS 10.1   *
    *                 and above using the 390 indexer.             *
    ****************************************************************
    * PROBLEM DESCRIPTION: 1.When a FIELDnnn extends past the end  *
    *                      of a line or is completely beyond the   *
    *                      end of a physical record, the indexes   *
    *                      generated are different than the 9.5    *
    *                      390 indexer.  This is noticeable when   *
    *                      two fields are concatenated to form an  *
    *                      index, and the first field extends past *
    *                       the physical record.                   *
    *                                                              *
    *                      2.When the INPEXIT supplies a DJDE for  *
    *                      Global DJDE the DJDE is not stored      *
    *                      correctly as a resource.  An arsadmin   *
    *                      retrieve of the resource has two bytes  *
    *                      of binary zeros for each DJDE           *
    ****************************************************************
    1.ARGL390L was using x'00' for characters that were not in the
    line.  The 9.5 390 indexer used blanks.  This causes issues when
    concatenating 2 fields of a multi-field index where an embedded
    x'00' terminates the string.
    
    2.ARGL390L was not setting a variable to indicate where a called
    routine was supposed to look for the record.  This caused the
    routine to not correctly locate the DJDE record from the exit.
    

Problem conclusion

  • 1.ARGL390L is changed to use blanks instead of x'00' for data
    that is not in the physical line.
    
    2.ARGL390 is changed to indicate to the called routine where the
    record is.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH28596

  • Reported component name

    CM OD Z/OS, OD/

  • Reported component ID

    5655H3900

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-08-18

  • Closed date

    2020-09-02

  • Last modified date

    2020-10-01

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

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

    UI71378 UI71379

Modules/Macros

  • ARGL390L
    

Fix information

  • Fixed component name

    CM OD Z/OS, OD/

  • Fixed component ID

    5655H3900

Applicable component levels

  • RA10 PSY UI71378

       UP20/09/03 P F009

  • RA50 PSY UI71379

       UP20/09/03 P F009

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.

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSQHWE","label":"Content Manager OnDemand for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"A10"}]

Document Information

Modified date:
02 October 2020