IBM Support

PK81851: warning message 'ambiguous reference to XXXX' when editing Cobol program

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Warning message 'ambiguous reference to XXXX' when editing a
    COBOL program.
    
    Customer opened a COBOL program in a z/OS project and receives
    the following warning message 'ambiguous reference to xxx'.
    
    Recreate Steps:
    
    - Have a COBOL program named c0.cbl.
    
      This program inludes two copybook members :
    
           WORKING-STORAGE SECTION.
    
           COPY c1.
    
           COPY c2.
    
    - Have the two copybook members named c1.cpy and c2.cpy.
    
      They contain two structures A and B with an identical
    definitions:
       01 A.                        01 B.
           02  Y    PICTURE X.          02  Y    PICTURE X.
           02  FILLER REDEFINES Y.      02  FILLER REDEFINES Y.
               03 Z    PICTURE X            03 Z    PICTURE X.
    - Without compiling, if you edit c0.cbl, there is a warning
      displayed on the COPY c1 and COPY c2 clauses :
    
      Copybook contains the following error Ambiguous reference
      to Y.
      This is the problem encountered by customer.
    
    - In fact, there is no error in the code. The program might be
      compiled without error and its execution is correct as soon
      as the fields are correctly referenced.
    
    Notes :
    
    - If for REDEFINES, another name is used instead of FILLER then
      no warning is issued.
    
    - If one of the copybook c1 or c2 is not included then, of
      course, no warning is issued even when name FILLER is used.
    

Local fix

Problem summary

  • Redefine statements were not correctly resolving the redefined
    data item if the redefining statement was unnamed or FILLER.
    Additionally unnamed redefining data groups were not being
    populated correctly in content assist.
    

Problem conclusion

  • Redefines statements which are unnamed or are FILLER are now
    correctly handled.  The problem listed in this APAR has been
    resolved with IBM Rational Developer for System z V7.5.1.1 Fix
    Pack which is available from the Recommended Fixes support
    download page:
    http://www-1.ibm.com/support/docview.wss?rs=2294&uid=swg27006335
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK81851

  • Reported component name

    RATL DEV FOR SY

  • Reported component ID

    5724T0700

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-03-04

  • Closed date

    2009-10-27

  • Last modified date

    2009-10-27

  • 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

    RATL DEV FOR SY

  • Fixed component ID

    5724T0700

Applicable component levels

  • R751 PSY

       UP

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSJK49","label":"IBM Developer for z Systems"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
27 October 2020