A fix is available
Closed as program error.
A COBOL program has the following DB2 definition: 01 my-xml USAGE IS SQL TYPE IS CLOB(2M). This generates 2 additional data areas that are not visible in the source or listing: 49 my-xml-LENGTH PIC S9(9) COMP-5. 49 my-xml-DATA PIC X(2097152) DISPLAY. These data definitions are referenced within the program. The program is accessed in an RDz view with both the COBOL and LPEX editors. In both cases my-xml-LENGTH and my-xml-DATA are flagged and the hover error message is 'Unable to resolve reference.' If the same program is compiled with Enterprise COBOL on the zOS Host system, these references are not flagged as errors. These definitions are not visibly expanded, but know to the batch Host compiler. NOTE: This situation was discovered in RDz 8.5.1.
Resolution warnings were being generated for references to fields generated by the DB2 precompiler for BLOB, CLOB, and DBCLOB usages in COBOL.
Implicit variables for elements generated by the DB2 precompiler for SQL Usages of the following kinds in COBOL programs are now resolved by the real time syntax parser: BLOB CLOB DBCLOB BLOB FILE CLOB FILE DBCLOB FILE XML AS BLOB XML AS CLOB XML AS DBCLOB XML AS BLOB FILE XML AS CLOB FILE XML AS DBCLOB FILE The problem listed in this APAR has been resolved with IBM Rational Developer for System z V220.127.116.11 Fix Pack which is available from the Recommended Fixes support download page: http://www-1.ibm.com/support/docview.wss?rs=2294&uid=swg27006335
Reported component name
RATL DEV FOR SY
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
RATL DEV FOR SY
Fixed component ID
Applicable component levels