IBM Support

PH19624: NATURAL MEMBERS CANNOT BE VIEWED WHEN ANALYSIS CLIENT IN IDZ

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • If the AD Analysis Client is installed in iDZ, and a source
    member has been downloaded from the mainframe via the Mainframe
    Agents, then a request to view source automatically attempts to
    retrieve the source from the mainframe location. This works fine
     for PDS members, or Endevor members (via use of Carma). However
     it does not work for Natural, as Natural members are stored
    within Adabas databases and manipulated within the Natural IDE.
    They are not stored in directly accessible libraries, and iDZ
    has no method to access them (Application Discovery downloads
    them from Natural via use of the Natural Batch Utility).
    Attempts to retrieve Natural members for View/Edit result in an
    error message 'Invalid entry for source <Connection Name>
    (<member name>)'.
    
    If AD Analysis Client is installed into Native Eclipse, then the
    Natural source can be viewed correctly, as the member is
    retrieved from the shared mainframe sources folder, into which
    the Natural Members are extracted and downloaded via the
    Mainframe Agents.
    

Local fix

  • n/a
    

Problem summary

  • Attempts to retrieve Natural members from IDZ for View/Edit
    result
    in an error message 'Invalid entry for source <Connection Name>
    (<member name>)'    as Natural members are stored within Adabas
    databases and manipulated within the Natural IDE. They are not
    stored in directly accessible libraries, and iDZ has no method
    to access them (Application Discovery downloads them from
    Natural via use of the Natural Batch Utility).
    
    
    Fix:-
    
    
    Because IDZ has no method to download Natural members from
    Adabas databases, we have modified AD to open the Natural
    members from retrieve members folder and this will be
    implemented in AD 5.1.0.5
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PH19624

  • Reported component name

    APPL DISCOVERY

  • Reported component ID

    5737B1600

  • Reported release

    510

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-11-26

  • Closed date

    2019-12-18

  • Last modified date

    2019-12-18

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

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

Fix information

Applicable component levels

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSRR9Q","label":"IBM Application Discovery for IBM Z"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"510","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
18 December 2019