IBM Support

PH20135: FIND COMMAND RETURNS NO ITEMS IN ACCESS

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If an Optim user enters a 'find' command within the display of
    tables returned for browsing or editing in an Access session
    Optim may incorrectly display the message 'END OF DATA REACHED'
    meaning the value was not found.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Optim Access users displaying a list of      *
    *                 tables to potentially be browsed or edited.  *
    ****************************************************************
    * PROBLEM DESCRIPTION: If an Optim Access user generates a     *
    *                      list of tables from which one will be   *
    *                      browsed or edited it is possible that   *
    *                      the result of a FIND command searching  *
    *                      for a table in the list may incorrectly *
    *                      be that the end of the list was reached *
    *                      without finding it.                     *
    ****************************************************************
    * RECOMMENDATION: Apply the fix provided.                      *
    ****************************************************************
    When the list of tables matching the search criteria is built
    Optim was assigning an incorrect offset of the field names
    within the list structure.  Consequently, the target of the
    FIND command was not found.
    

Problem conclusion

  • If the list of creator IDs and tables contained at least one
    long object name Optim assigned offsets for each table entry
    using length values of long objects.  This caused the code that
    displays the list to search beyond the list entries that it
    uses which does not support long object names.
    The code that generates the list has been amended to be more
    sensitive of the field offsets and the code that performs the
    search within the list has been modified to recognize and handle
    long object names.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH20135

  • 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

    2019-12-10

  • Closed date

    2020-02-05

  • Last modified date

    2020-03-02

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

    PH20133

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

Modules/Macros

  • FOP9APIM FOPCFPMN FOPCRDB  FOPCXLIB FOPHSTM  FOPI0000 FOPI0005
    FOPI0017 FOPI0018 FOPI4700 FOPI4706 FOPIBDPK FOPIDMDR FOPIDMTB
    FOPINS0  FOPITABL FOPITSPC FOPK04   FOPMADDE FOPMAIN  FOPMCBMN
    FOPMCMMN FOPMCOLA FOPMCOLP FOPMECMN FOPMMUNU FOPMMUTL FOPMTMDB
    FOPOMN   FOPRS6   FOPT40G  FOPT4702 FOPT4704 FOPT4706 FOPT48H
    FOPTBIPK FOPTDCCL FOPTFBND FOPTIBND FOPTISM1 FOPTISM2 FOPTISMP
    FOPTTSPC
    

Fix information

  • Fixed component name

    OPTIM MOVE FOR

  • Fixed component ID

    5655V0700

Applicable component levels

  • RB70 PSY UI67718

       UP20/02/08 P F002

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":"B70","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
27 March 2020