IBM Support

PH67565: ANALYSIS FAILS FOR PROGRAM WHOSE NAME DOESN'T MATCH THE MODULE NAME GIVING MSGCQI5029W: ADATA FOR CSECT XXXX DOESN'T MATCH CSECT

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Analysis fails for programs whose name doesn't match the module
    name. The analysis engine gives messages MSGCQI5029W: ADATA for
    CSECT XXXXX doesn't match the CSECT. Analyzing performance
    without ADATA. and MSGCQI5040W: Matching data item names from
    ADATA to module without using a listing is not supported for
    programs compiled with Enterprise COBOL 6.4. Programs in CSECT
    XXXXX will not use listing information during analysis.
    

Local fix

  • Use the CONFIG parameter to specify a config file. Provided all
    programs are in the same module and all listing and ADATA files
    are in one dataset each with member names matching the program
    name, the config file can consist of a single entry for programs
    named "*", specifying the listing and ADATA datasets without any
    members.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of Z Code Optimization Advice          *
    *                 analyzing programs that contain two or more  *
    *                 programs that are statically linked          *
    *                 together in a single module and that use     *
    *                 the ADATA and LISTING parameters instead of  *
    *                 the CONFIG parameter in the launcher JCL.    *
    ****************************************************************
    * PROBLEM DESCRIPTION: Analysis fails for programs whose name  *
    *                      doesn't match the module name. The      *
    *                      analysis engine gives messages          *
    *                      MSGCQI5029W: ADATA for CSECT XXXXX      *
    *                      doesn't match the CSECT. Analyzing      *
    *                      performance without ADATA. and          *
    *                      MSGCQI5040W: Matching data item names   *
    *                      from ADATA to module without using a    *
    *                      listing is not supported for programs   *
    *                      compiled with Enterprise COBOL 6.4.     *
    *                      Programs in CSECT XXXXX will not use    *
    *                      listing information during analysis.    *
    ****************************************************************
    * RECOMMENDATION: Apply the provided PTF                       *
    ****************************************************************
    Z Code Optimization Advice had several requirements in order to
    successfully use the ADATA and LISTING parameters instead of
    setting up a config file, specified with the CONFIG parameter.
    One is that each ADATA file and each listing file reside in a
    dataset where the member name matches the program name. The
    other is that each module and each source file contain only one
    main program (nested programs are allowed). For clients who
    bind multiple programs statically, even if they meet the
    requirement for their ADATA and listing datasets and have only
    one main program per source file, they still have multiple
    programs in the module. The module name was used to find the
    correct ADATA and listing files for a program, so if multiple
    programs are in the same module, Z Code Optimization Advice
    would find the ADATA and listing files that matched the module
    name and try to use them for all programs. Since those ADATA
    and listing files would only match at most one of the programs,
    Z Code Optimization Advice detected a mismatch error when
    trying to use one program's ADATA or listing files to analyze
    other programs.
    

Problem conclusion

  • When using the ADATA and LISTING parameters, Z Code
    Optimization Advice now attempts to use the program's name as
    the member name when looking for ADATA and listing files first,
    falling back to the module name if no ADATA or listing file
    member matching the program name was found. This allows for the
    correct ADATA and listing files to be used even when clients
    have multiple programs with distinct ADATA and listing files
    statically linked into one module.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH67565

  • Reported component name

    CODE OPT ADVICE

  • Reported component ID

    5900B4M04

  • Reported release

    210

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2025-07-30

  • Closed date

    2025-08-06

  • Last modified date

    2025-08-31

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

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

Modules/Macros

  • CQIALC   CQIBE    CQIBXITA CQICONFG CQIINI1  CQIINI2  CQIINI3
    CQIINIJ1 CQIINIJ2 CQIINIJ3 CQIINIT  CQIINITJ CQIIVPE  CQIIVPJ
    CQIIVPS1 CQIIVPS2 CQIMSGE  CQIMSGK  CQIMSGT  CQIRIDT
    

Fix information

  • Fixed component name

    CODE OPT ADVICE

  • Fixed component ID

    5900B4M04

Applicable component levels

  • R210 PSY UO04425

       UP25/08/26 P F508

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":"BU048","label":"IBM Software"},"Product":{"code":"SSK5UBS","label":"IBM watsonx Code Assistant for Z"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"210","Line of Business":{"code":"LOB70","label":"Z TPS"}}]

Document Information

Modified date:
02 October 2025