IBM Support

PH67465: API requester response data is printed incorrectly in the Host API trace.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as unreproducible in next release.

Error description

  • When using OpenAPI 3 API requester Host API trace, the response
    data in the Host API trace is not correctly formatted. For
    example, the Host API trace might show the following at the
    start of the response data:
    
    <Date_Timestamp> (webtBodyStreamExit) -- Response Data:
     C2C1D8C8C1D7C9E2  F0F0F0F10000000C  |  .....P..........
     E2E3C1D9E3C4C140  C2C1D8C2C1E2C540  |  ................
    
    but it should look like this:
    <Date_Timestamp> (webtBodyStreamExit) -- Response Data:
     C2C1D8C8C1D7C9E2  F0F0F0F10000000C  |  BAQHAPIS0001....
     E2E3C1D9E3C4C140  C2C1D8C2C1E2C540  |  STARTDA BAQBASE
    
    Additional search words: BAQVERBOSE
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of z/OS Connect 3.0 feature        *
    *                 oasRequester-1.0 for OpenAPI 3 API           *
    *                 requesters.                                  *
    ****************************************************************
    * PROBLEM DESCRIPTION: API requester response data is printed  *
    *                      incorrectly in the Host API trace.      *
    ****************************************************************
    Static data was used to format and translate the hexadecimal
    response data into EBCDIC data in the HOST API trace. In the
    interactions between the HOST API and the z/OS Web
    Client Enablement Toolkit, the addressability to the static data
    was lost. This resulted in the data in the HOST API trace was
    not formatted correctly.
    

Problem conclusion

Temporary fix

Comments

  • z/OS Connect has been changed to use a different formatting
    mechanism for the OpenAPI 3 Host API trace.
    
    The fix for this APAR is expected to be delivered by the PTF
    for z/OS Connect V3.0.98.0 (PH68103).
    

APAR Information

  • APAR number

    PH67465

  • Reported component name

    Z/OS CONNECT EE

  • Reported component ID

    5655CE300

  • Reported release

    000

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2025-07-23

  • Closed date

    2025-11-03

  • Last modified date

    2025-11-03

  • 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

    Z/OS CONNECT EE

  • Fixed component ID

    5655CE300

Applicable component levels

[{"Business Unit":{"code":"BU029","label":"Software"},"Product":{"code":"SSVVFY","label":"z\/OS Connect Enterprise Edition"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"000"}]

Document Information

Modified date:
03 November 2025