RE: [WDSCI-L] Re: Compile commands

[<Rick.Chevalier@xxxxxxxxxxxxxxx>]

Sarah,

This is probably caused because at this time the precompiler generates a 
separate source member to compile from.  There wouldn't be a link from the 
generated error back to the original source member.  Some errors may even be 
caused as a result of code inserted by the precompiler.

Like Charles said, this is limitation of how the precompiler is implemented.  I 
understand it's being improved but I don't have any details.

Rick

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx
[mailto:wdsci-l-bounces@xxxxxxxxxxxx]On Behalf Of Wilt, Charles
Sent: Friday, January 07, 2005 12:26 PM
To: Websphere Development Studio Client for iSeries
Subject: RE: [WDSCI-L] Re: Compile commands


Sarah,

Not that I know of.

Charles Wilt
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121


> -----Original Message-----
> From: wdsci-l-bounces+cwilt=meaa.mea.com@xxxxxxxxxxxx
> [mailto:wdsci-l-bounces+cwilt=meaa.mea.com@xxxxxxxxxxxx]On Behalf Of
> SPoger@xxxxxxxxxxxxxxxxxx
> Sent: Friday, January 07, 2005 11:40 AM
> To: wdsci-l@xxxxxxxxxxxx
> Subject: RE: [WDSCI-L] Re: Compile commands
>
>
> Do you know if there is an existing APAR for this issue? If not, I'll
> call IBM support.
>
> > -----Original Message-----
> > From: Wilt, Charles [mailto:CWilt@xxxxxxxxxxxx]
> > Sent: Thursday, January 06, 2005 12:10 PM
> > To: Websphere Development Studio Client for iSeries
> > Subject: RE: [WDSCI-L] Re: Compile commands
> >
> >
> > Sarah,
> >
> > I believe its considered a "limitation" as opposed to a "bug".
> >
> > I'm pretty sure IBM is working on supporting this properly.
> >
> > Charles Wilt
> > iSeries Systems Administrator / Developer
> > Mitsubishi Electric Automotive America
> > ph: 513-573-4343
> > fax: 513-398-1121
> > 
> >
> > > -----Original Message-----
> > > From: wdsci-l-bounces@xxxxxxxxxxxx
> > > [mailto:wdsci-l-bounces@xxxxxxxxxxxx]On Behalf Of
> > > SPoger@xxxxxxxxxxxxxxxxxx
> > > Sent: Thursday, January 06, 2005 12:48 PM
> > > To: wdsci-l@xxxxxxxxxxxx
> > > Subject: RE: [WDSCI-L] Re: Compile commands
> > >
> > >
> > > I am able to use a custom compile command or the IBM command
> > > CRTSQLRPGI to successfully compile my SQL RPGLE source from
> > > WDSC. In either case I am able to get the compile error list
> > > back in WDSC.  But... what is not workinking is the link from
> > > the error list back to the source code. When I double-click a
> > > specific error, the source member that opens is the output of
> > > the SQL precompiler. NOT the original SQL RPGLE source.  I
> > > can manually open the original source from the Remote Systems
> > > Window. But its a nuisense that double-clicking the error
> > > does not open the correct source automatically.
> > >
> > > Is this considered a bug in WDSC? To reproduce this issue,
> > > simply compile from WDSC using the IBM command CRTSQLRPGI,
> > > then double click a line in the iSeries error list.
> > >
> > > Thanks,
> > > Sarah
> > >
> > > -----Original Message-----
> > > From: David Gibbs [mailto:david@xxxxxxxxxxxx]
> > > Sent: Wednesday, January 05, 2005 11:27 AM
> > > To: wdsci-l@xxxxxxxxxxxx
> > > Subject: [WDSCI-L] Re: Compile commands
> > >
> > >
> > > Alan Campin wrote:
> > > > Anyway, in order to get it to work, I issue the command COMPILE
> > > > though WDSC but like you, I did not get anything back. I
> > > notice below
> > > > that David says OPTION(*SRCDBG). I think he meant to say
> > > > OPTION(*EVENTF) but that still did not work. You always
> > have to use
> > > > OPTION(*EVENTF) and I could see the Event file being
> > built but not
> > > > being returned to me.
> > >
> > > Actually, I did mean OPTION(*SRCDBG) :)
> > >
> > > What I did, for our compile commands (part of the Implementer SCM
> > > product) is put a dummy parameter on the compile command
> > > where I put the
> > > 'SRCMBR(&N) OPTION(*SRCDBG)'.  Neither parameter is
> > actually used by
> > > anything, but WDSC notices them and is able to return the compile
> > > information.
> > >
> > > The actual compile command needs to have either the
> > > OPTION(*EVENTF) or
> > > OPTION(*SRCDBG) parameter.
> > >
> > > > Finally found that the only way I could get it
> > > > to work was to compile interactively and that would work.
> > I, also,
> > > > got the free plug-in from Softlanding to retrieve
> > messages from the
> > > > message queue to show me the result messages.
> > >
> > > Make sure the compile is not submitted within the batch
> > > compile.  WDSC
> > > submits the compile, and keeps track of the submitted job.
> > >
> > > Also, make sure you don't compile the object into QTEMP ...
> > > if you do,
> > > the event file will be written to QTEMP and WDSC won't be able to
> > > retrieve it.
> > >
> > > david
> > >
> > > --
> > > David Gibbs
> > > david@xxxxxxxxxxxx
> > >
> > > Receipt of this message does not grant you permission to send me
> > > Unsolicited Commercial Email

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.