IBM Support

PH04071: DURING ENDEVOR EXTRACTION STC CRASHES IN U3009 AND CONTINUES UNTL HANGS IN 2 MINUTES. STOPPING AND RELAUNCH REFURBISHES ST

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • Customer had an incident during ENDEVOR extraction, STC crashes
    in U3009; the issues repeats itself continuously and then hangs
    after 2 minutes. Stopping and relaunching has refurbished the
    STC.
    

Local fix

  • Stephen will create a fix fixing hte cause of hte mempory leak
    in AD mainframe agents.
    

Problem summary

  • This is a known problem when using the Endevor API - ENAPI001.
    Under heavy use, the address space where this API is being
    called will sometimes experience storage shortages or failures
    to the point that the API issues an internal abend or LE issues
    a U3009.  After this point, the AD agent subtask becomes
    unusable and the only solution is to cycle the AD agent address
    space.  CA has recommended limiting the number of requests sent
    to the API - so to implement this suggested workaround, there is
     now an option to move the Endevor API work into an
    automatically submitted batch job, which performs the work and
    returns the results to the agent.  When the job ends, all
    storage is freed and we avoid the cumulative loss of storage
    leading to the reported abends.
    

Problem conclusion

  • This is a known problem when using the Endevor API - ENAPI001.
    Under heavy use, the address space where this API is being
    called will sometimes experience storage shortages or failures
    to the point that the API issues an internal abend or LE issues
    a U3009.  After this point, the AD agent subtask becomes
    unusable and the only solution is to cycle the AD agent address
    space.  CA has recommended limiting the number of requests sent
    to the API - so to implement this suggested workaround, there is
     now an option to move the Endevor API work into an
    automatically submitted batch job, which performs the work and
    returns the results to the agent.  When the job ends, all
    storage is freed and we avoid the cumulative loss of storage
    leading to the reported abends.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH04071

  • Reported component name

    APPL DISCOVERY

  • Reported component ID

    5737B1600

  • Reported release

    505

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-10-15

  • Closed date

    2019-05-15

  • Last modified date

    2019-05-15

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

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

Fix information

  • Fixed component name

    APPL DISCOVERY

  • Fixed component ID

    5737B1600

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

Document Information

Modified date:
15 May 2019