× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi Craig,

We are aware of this problem.  Please see APAR SE21356
Fix is slated for 6.0.0.2

thanks,

Violaine Batthish
WebSphere Development Studio Client, IBM Toronto Lab

You know you've achieved perfection in design, not when you have nothing
more to add, but when you have nothing more to take away. - Antoine de
Saint-Exupéry



wdsci-l-bounces@xxxxxxxxxxxx wrote on 09.09.2005 09:59:52:

>
> Often I have been getting the stack overflow error when changing an
> expression in a prompted CL command in the Lpex Editor in WDSC 6.0 with
the
> latest updates.  For example, IF COND(&AUTIND = ' ' *OR &MSGID > ' ')
> THEN(DO).  I prompt with F4 and place my cursor on the character before
the
> &MSGID and hit backspace a couple times.  When it gets to where it looks
> like (&AUTIND = ' &MSGID > ' ') it errors out.  Then I hit backspace
again
> so it looks like (&AUTIND = '&MSGID > ' ') and it errors out again.  Then
I
> can hit backspace until I make it look like (&MSGID > ' ').  If instead I
> just delete everything and type (&MSGID > ' ') then it doesn't error out.
> I tried to exit WDSC and then get back in and when I try deleting
> characters in the first example above, I error out again.
> "Internal Error" it states,
> "A stack overflow error has occurred.
> You are recommended to exit the workbench.
> Subsequent errors may happen and may terminate the workbench without
> warning.
> See the .log file for more details.
> Do you want to exit the workbench? <Yes> <No>
>
> Default is no and I decided not to exit but did it again and got the same
> error.
>
> I see a bunch of the following error in the .log file.  I'm not sure if
> this is related:
> at
com.ibm.etools.iseries.core.util.clprompter.ClExpression.<init>(Unknown
> Source)
>
> This is getting really frustrating as I used to exclusively use CODE for
CL
> but I like how the Lpex Editor handles indenting and the prompts are
nice.
> IBM, please fix if you aren't already.  Thanks!
>
> Craig Strong



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.