I haven't had an Outline for this particular source member since RDp 8.5 (or earlier).
Refreshing the cache worked in this case. I haven't done a Verify since moving from WinXP. On Win7, Verify always took several minutes, so I stopped using it. In RDi 9.1, it seems actually usable again.
-----Original Message-----
From: Gary Thompson [mailto:gthompson@xxxxxxxxxxx]
Sent: Thursday, September 04, 2014 4:43 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Subject: Re: [WDSCI-L] Outline not working for some SQLRPGLE source
+1
When things go twilight zone in RDi - my first stop is:
Source - Verify(Prompt) - Cache - check Refresh cache then fix errors
-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Kurt Anderson
Sent: Thursday, September 04, 2014 3:33 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Subject: Re: [WDSCI-L] Outline not working for some SQLRPGLE source
When I've had this happen it's been due to a syntactical issue in the program. I don't recall which types of coding screw-ups cause the outline to disappear, but some things clearly are messing up the parser. Interesting, though, that on pre-9.01 versions I don't recall this happening.
Kurt Anderson
Sr. Programmer/Analyst - Application Development, Service Delivery Platform
-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Bob Schuch
Sent: Thursday, September 04, 2014 3:33 PM
To: WDSCI-L@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] Outline not working for some SQLRPGLE source
Jon Paris wrote:
I encountered the same problem yesterday Justin - haven't had time to dig into it and since it turned out I had opened the wrong source ...
I have also encountered this and was told it is because the parser has trouble parsing something in the source, usually where a reserved word is used as a variable.
To find the error, there is a thin bar along the right side of the source which will have a little yellow marker in it. This will indicate where the parser fails.
I was able to remedy it on one source by changing the name of that variable to something that was not a reserved word.
Hope this helps.
--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/wdsci-l.
--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/wdsci-l.
midrange.com
