× 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.



The LPEX editor, if I understand correctly, does not
seem tailored to iSeries source types - yet(?). To get
that you need to use CODE. It also uses LPEX but has
much more done to make it usable.
> Hi,
>
> I just installed WDSc 4.0, and I'm trying to use the WSSDa part of it (since
> that is the strategic direction, isn't it, I'm avoiding the CODE/400 part of 
>it
> at any cost - whether or not that is currently a good decission).
>
> Anyway, I do have some issues in using the Remote Systems Explorer and LPEX
> editor;
>
> 1. When trying to compile in batch, he's failing and mentions something about
> QDEVTOOLS/QRSEEXEC which I'm missing).  In addition, somewhere in the help, I
> found a reference to STRRSESRV which I'm missing as well ?  Where do these 
>'RSE'
> commands come from, and how do I get them (box should be up-to-date with 
>V5R1).
>
> 2. The LPEX editor requires a CTRL-Enter to insert a new line... a normal 
>Enter
> in Insert mode (as mentioned in the help) does NOT create a new line (which is
> very annoying), but just positions itself on the next line.
>
> 3. The LPEX editor doesn't seem to do syntax checking ?  Shouldn't this 
>happen ?
> What is wrong, where do I enable this ?
>
> This WSSDa looks promising, but it looks like IBM already created such a
> confusion that nobody knows the difference (WDSc, WSSDa, WDT, WSAD, ...) and
> strategic direction anymore.
>
> Kind regards,
> Paul
>


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.