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



Other than using the compile option from the menu bar I think this is what most 
RSE/LPEX users do when editing source.

The original question I believe was about using the verify option.  I am 
currently using 5.1.2.3 and the verify works well.  The only issue I have is 
that it doesn't like the %KDS BIF.  It tells me that the number of key fields 
aren't correct.  The compile works fine.  There have been other issues with 
older versions but since the 5.1 version it has been very good in my opinion.

The only time I go to the job log is if I have a binding issue.  I haven't 
found a way to identify those through WDSc yet.

We even have some really old RPT code I have to maintain periodically and I 
still prefer to use WDSc over PDM for maintaining it.

Rick

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx
[mailto:wdsci-l-bounces@xxxxxxxxxxxx]On Behalf Of
jstevens@xxxxxxxxxxxxxx
Sent: Wednesday, January 05, 2005 2:06 PM
To: Websphere Development Studio Client for iSeries
Subject: RE: [WDSCI-L] for experienced Healthcare users


I learned WDSC on my own, so there are probably others on this list that
are much better than I.  However, when I edit a source member (I use
filters).  I setup one filter for each library, and limit it to files that
start with Q* - that way I get QCLSRC, QRPGSRC, QDDSSRC, QSRC, etc. -
stuff like that.  Then I expand the source file and then double click on
the source member I want to edit. When I'm done editing, I click on the
save icon, then I right click on the member name and select "compile", If
it's an RPG II/III member, it just comes up with CRTRPGPGM, if it's a RPG
IV member, it comes up with CRTRGPMOD and CRTPGM.  You might need to
experiment with "work with compile commands".  Anyway I select CRTxxxPGM,
etc, I select iSeries Error List in the tabs at the bottom and - it will
show my errors there.  From there I can double click on the error and it
will place my cursor in the member on the line with the error.  Very nice.

Suggestions from others?

Jeff Stevens
Mize, Houser & Co. P.A.
913 451 1882
JStevens@xxxxxxxxxxxxxx





"Kurt Anderson" <kjanderson@xxxxxxxxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
01/05/2005 01:49 PM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
"Websphere Development Studio Client for iSeries" <wdsci-l@xxxxxxxxxxxx>
cc

Subject
RE: [WDSCI-L] for experienced Healthcare users







>I've written some new programs dealing with EDI data, so that's in RPG
IV/ILE.  I use WDSC for all of my
>iSeries work.  I can't remember the last time I was in SEU.

Do you compile on the iSeries and then bring up the joblog in your 5250
session and update the code in WDSC?  Or do you use the verify function?
If you use the verifier, and it doesn't seem buggy to you, what version
are you on?

Thanks,
Kurt


Privileged and Confidential.  This e-mail, and any attachments there to, is 
intended only for use by the addressee(s) named herein and may contain legally 
privileged or confidential information.  If you have received this e-mail in 
error, please notify me immediately by a return e-mail and delete this e-mail.  
You are hereby notified that any dissemination, distribution or copying of this 
e-mail and/or any attachments thereto, is strictly prohibited.


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.