RE: RE: compiling sqlrpgle

Rick, 
Adding the   keyword OPTION(*SRCSTMT)did not help,the line #'s don't match 
up.  Also, I noticed today, when I double click the error, it opens the 
"/copy" program and displays the dialog box that it can't find the 
indicated line #.  So why double clicking the error would open my 
procedure program and not the program that I'm compiling??   It is 
definitely an aggravation but not enough to give up WDSC - can't work 
without it.  If I have to, I'll compile on the 5250 and code in WDSC. 
Thanks for your suggestion. 

Diane 



<Rick.Chevalier@xxxxxxxxxxxxxxx> 
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
12/21/05 04:31 PM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
<wdsci-l@xxxxxxxxxxxx>
cc

Subject
RE: [WDSCI-L] RE: compiling sqlrpgle







Diane,

I hate to see you dump WDSc for this. 

I haven't compiled an SQLRPGLE program in a while but I'm pretty sure you 
can use the line numbers in the error view to locate the correct source 
statements.  I don't double click on the errors because it imbeds all of 
the errors and IMHO clutters up the source to the point of being 
unreadable.

Try adding the keyword OPTION(*SRCSTMT) to your H-spec and see if the line 
numbers don't match up.

Rick

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx
[mailto:wdsci-l-bounces@xxxxxxxxxxxx]On Behalf Of infosys5@xxxxxxx
Sent: Wednesday, December 21, 2005 3:13 PM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] RE: compiling sqlrpgle


Bruce,
I feel certain prior to my 6.0.1 install, I never had this issue.  As it
stands now, it's useless for me to compile my sqlrpgle program in
WDSC/Rational (or whatever I should be calling it) - since I can't see my
errors.  I have to jump over to the 5250 session, compile it there, and
then get my errors.
With version 5.xxx, my errors were visible.

Thanks for your reply, maybe an IBMer will jump in on this and set me
straight.
Diane


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