IBM Support

PH64358: Message BAQH2001S is reported when the BAQZ-TRACE-VERBOSE parameter is specified.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as unreproducible in next release.

Error description

  • When the BAQZ-TRACE-VERBOSE parameter is specified in an API
    requester program and the field containing the trace level value
    is padded,the following error is reported:
    
    BAQ-ZCON-COMPLETION-CODE=00012
    BAQ-ZCON-REASON-CODE=02001
    BAQ-ZCON-RETURN-MESSAGE=BAQH2001S: The call to BAQINIT for the
    initialization of the Host API failed unexpectedly. Service ID=0
    Service Code=0
    
    Additional search words: msgBAQH2001S msgBAQH2001 BAQH2001S
    BAQH2001
    

Local fix

  • Workaround: C-style null termination -> BAQINIT terminates
    successfully.
    
           move all x'00' to W-VERBOSE(4: 1)
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of the z/OS Connect                *
    *                 zosconnect:oasRequester-1.0 feature for      *
    *                 OpenAPI 3 z/OS application API requesters    *
    *                 when overriding the trace level in the z/OS  *
    *                 application.                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: Message BAQH2001S is reported when the  *
    *                      BAQZ-TRACE-VERBOSE parameter is         *
    *                      specified.                              *
    ****************************************************************
    When a string value, padded with 0x40 characters, was specified
    in BAQZ-TRACE-VERBOSE, the length specified in
    BAQ-ZCON-PARM-LENGTH was not used. The expected end of the
    string was not found and the attempt to match the input string
    against the list of valid verbosity levels failed. This caused
    the failure of the BAQINIT call.
    

Problem conclusion

Temporary fix

Comments

  • z/OS Connect has been changed to correctly use the specified
    BAQ-ZCON-PARM-LENGTH, preventing the reported issue when
    enabling trace in z/OS applications by using Host API
    parameters.
    
    The fix for this APAR is expected to be delivered by the PTFs
    for z/OS Connect V3.0.93.0 (PH66161).
    

APAR Information

  • APAR number

    PH64358

  • 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

    2024-11-29

  • Closed date

    2025-04-23

  • Last modified date

    2025-04-23

  • 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:
23 April 2025