Topic
  • 3 replies
  • Latest Post - ‏2012-08-24T13:13:23Z by SystemAdmin
gb12345
gb12345
38 Posts

Pinned topic $-sign in cobol copybook name deactivates content assist in lpex

‏2012-08-24T10:04:39Z |
Hi,
I have the following statement in a cobol program:

EXEC SQL
INCLUDE MY$STDB2
END-EXEC.

The lpex editor shows the following warning for this statement:
Unexpected character "$" ignored.
"ERROR_TOKEN" unexpected tokens ignored.

The problem is, that with this statement the content assist of the lpex editor is not working.

The cobol compiler at z/OS does accept the statement.
Regards
Georg
Updated on 2012-08-24T13:13:23Z at 2012-08-24T13:13:23Z by SystemAdmin
  • gb12345
    gb12345
    38 Posts

    Re: $-sign in cobol copybook name deactivates content assist in lpex

    ‏2012-08-24T10:47:36Z  
    Additional info: We use RDz 8.5 and especially the tooltips in lpex are not working.

    Georg
  • SystemAdmin
    SystemAdmin
    1086 Posts

    Re: $-sign in cobol copybook name deactivates content assist in lpex

    ‏2012-08-24T13:02:52Z  
    The editor is enforcing the rules listed for COPY statements from the Enterprise COBOL for z/OS Language Reference, which include:

    v Can contain the following characters: Latin uppercase letters A-Z, Latin
    lowercase letters a-z, digits 0-9, and hyphen
    Bill Halterman
    IBM Rational Software
  • SystemAdmin
    SystemAdmin
    1086 Posts

    Re: $-sign in cobol copybook name deactivates content assist in lpex

    ‏2012-08-24T13:13:23Z  
    The editor is enforcing the rules listed for COPY statements from the Enterprise COBOL for z/OS Language Reference, which include:

    v Can contain the following characters: Latin uppercase letters A-Z, Latin
    lowercase letters a-z, digits 0-9, and hyphen
    Bill Halterman
    IBM Rational Software
    sorry, I posted accidentally before I finished typing...

    The alternate syntax for COPY statements in COBOL (other than the character set I mentioned from the Language Reference) uses a literal, which is also accepted by the editor for EXEC SQL INCLUDE:

    EXEC SQL
    INCLUDE 'MY$STDB2'
    END-EXEC.

    Editor tools such as Open Declaration, Open Copybook, etc.. will work with that syntax, and by using a syntax accepted by the editor, the other tools like content assist should work again. See if that will work in your environment.

    Bill Halterman
    IBM Rational Software