IBM Support

PM59733: RDz COBOL syntax check of EXEC SQL INCLUDE .. END-EXEC terminating period rules inconsistent.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • If a COBOL program containing EXEC SQL INCLUDE .. END-EXEC
    statements is compiled with the Enterprise COBOL compiler using
    the DB2 CoProcessor, a terminating period is required after the
    END-EXEC phrase.
    However, if the DB2 Preprocessor is run before the COBOL
    compiler, the the terminating period is optional.
    
    COBOL programs using the RDz editor real-time syntax checking
    through version 8.0.2 had missing periods flagged.  This warned
    users to make any necessary changes if they moved to the
    COBOL/DB2 CoProcesssor, but while using the Preprocessor, the
    RDz editor tooling was disabled because of the flagged
    condition.
    However, in RDz 8.0.3 the missing periods are no longer flagged,
    offering no help correcting this error for CoProcessor users.
    
    Since different users have different needs, there should be a
    way to accommodate both situations.
    

Local fix

Problem summary

  • The DB2 CoProcessor and the DB2 Preprocessor have different
    rules regarding the period in a COBOL program following EXEC SQL
    INCLUDE .. END-EXEC.    Flagging the missing period with a
    parser error disabled tooling for customers continuing to use
    the Preprocessor, and removing the error annotation didn't
    indicate the problem for customers using the Coprocessor, so
    their compile failed later, which is what the editor tooling is
    supposed to prevent.   A middle-ground is needed.
    

Problem conclusion

  • A post-parsing check for this condition was added, and so the
    condition is always flagged with the annotation, but as it is
    checked after the parse stage completes, the error now does not
    disable the RDz editor tooling.   The warning can simply be
    ignored by Preprocessor customers.
    
    The problem listed in this APAR has been resolved with
    IBM Rational Developer for System z V8.0.3.2 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

    PM59733

  • Reported component name

    RATL DEV FOR SY

  • Reported component ID

    5724T0700

  • Reported release

    803

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-03-05

  • Closed date

    2012-03-29

  • Last modified date

    2012-03-29

  • 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

  • R803 PSY

       UP



Document information

More support for: Rational Developer for System z

Software version: 8.0.3

Reference #: PM59733

Modified date: 29 March 2012