|
Somebody correct me if I am wrong.... Basically the SQL precompiler uses QTEMP to do it's portion of the program compile. If you have errors in your compile the event file will come back and notify WDSc of the errors that took place. Upon clicking an error in the listing it will tell you that it can't find the compile listing (or something like that). Well that is because it was in QTEMP, and QTEMP is specific to that job, and if a new job gets created for each compile and ends after the compile then that compile listing will also be gone. To rectify it just have the results of your compile go to a static library. I put it in my personal library named ALBARTELL. For example: TOSRCFILE(ALBARTELL/QSQLTEMP) HTH, and again if anybody knows that my statements are in error please elaborate. Aaron Bartell -----Original Message----- From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Scott Johnson Sent: Tuesday, May 03, 2005 2:25 PM To: Websphere Development Studio Client for iSeries Subject: Re: [WDSCI-L] Not getting sql listing. Aaron, Can you please provide some details on what you changed to get it to work. Thanks, Scott Aaron Bartell wrote: > Where are they sending the compile results? QTEMP? I had to change > my compile command to put it into a different library than QTEMP for > it to come back to WDSc correctly. > > Aaron Bartell -- This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/wdsci-l or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l.
As an Amazon Associate we earn from qualifying purchases.
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.