IBM Support

PH64718: NATURAL ERROR: "ERROR [999] : SYNTAX ERROR: 'PARSE ERROR, EXPECTING `SYM_INT' WHEN ENCOUNTERING TOKEN: I OR: I'"

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • When executing the Application Discovery build in a Natural
    project, a "Error [999] : Syntax error: 'parse error, expecting
    `SYM_INT' when encountering token: I or: I'" is displayed
    
    [12/17/2024 6:36 AM] (29) : Error [999] : Syntax error: 'parse
    error, expecting `SYM_INT' when encountering token: I or: I'
    [12/17/2024 6:36 AM] (1) : Error [999] : Syntax error: 'Fatal
    parsing error has occured.'
    

Local fix

  • n/a
    

Problem summary

  • Several specific parsing errors encountered while natural
    programs building:
                        Error [999] : Syntax error: 'parse error,
    expecting `SYM_RT_PAR' or `SYM_SLASH' or `SYM_PERIOD' when
    encountering token: , or: ,'
                        Error [999] : Syntax error: 'parse error,
    expecting `SYM_INT' when encountering token: I or: I'
                        Error [999] : Syntax error: 'parse error,
    expecting `RETURN' or `END_SUBROUTINE' when encountering token:
    , or: ,'
                        Error [999] : Syntax error: 'parse error,
    expecting `$' when encountering token: * or: *'
                        Error [999] : Syntax error: 'parse error
    when encountering token: DO or: DO'
                        Error [999] : Syntax error: 'parse error,
    expecting `DOEND' when encountering token: ( or: ('
    

Problem conclusion

  • 1. A compiler requirement to be done by the client: each natural
    program must be put in the appropriate subfolder ('Report' or
    'Structured') taking into account their assigned programming
    mode  (Reporting or Structured mode). One way to detect the
    programming mode is: only in the structured mode there is a
    "DEFINE DATA" section (outside of any defined procedure).
    2. There were the next syntax issues: (I) and *OI for the
    'INPUT' and 'DISPLAY' programming statements, as in the samples
    below:
                               1300 INPUT [...] 'SOME TEXT' (I)
    [...] #STRUCT-FIELDNAME (I)
                               1310 INPUT [...] 'SOME TEXT' '-' *OI
    [...] #STRUCT-FIELDNAME '-' *OI
                               1320 DISPLAY [...] 'SOME TEXT' (I)
    [...] #STRUCT-FIELDNAME (I)
                               1330 DISPLAY [...] 'SOME TEXT' '-'
    *OI  [...] #STRUCT-FIELDNAME '-' *OI
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH64718

  • Reported component name

    APPL DISCOVERY

  • Reported component ID

    5737B1600

  • Reported release

    613

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2025-01-07

  • Closed date

    2025-02-13

  • Last modified date

    2025-02-13

  • 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

    APPL DISCOVERY

  • Fixed component ID

    5737B1600

Applicable component levels

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSRR9Q","label":"IBM Application Discovery"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"613","Line of Business":{"code":"LOB70","label":"Z TPS"}}]

Document Information

Modified date:
13 February 2025