|
Usually when this happens to me it is because I have complied from WDSC into the wrong library. I would compile the program two or three time and then finally check to see if I had multiple objects. That's when I would discover that my WDSC compile resides lower in the library list and isn't actually running when I think it is. Michael Tobey Applications Analyst Foremost Farms USA (Consumer Products) mike.tobey@xxxxxxxxxxxxxxxxx -----Original Message----- From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of sjones@xxxxxxxxxxxxxx Sent: Friday, February 17, 2006 9:14 AM To: wdsci-l@xxxxxxxxxxxx Subject: [WDSCI-L] Strange Compile I was having a problem yesterday with a program I was developing when I tried to run it a divide by zero error would occur, but it was pointing to a line that was not dividing. First thing I thought was somehow I was running an old version, so I logged-off/back-on, problem still kept occurring. I was compiling the program using RSE , received the message that it compiled w/no errors. I decided to compile it using PDM and after that I seemed to get the correct version of the program when I ran it. I compared the compile options on RSE vs. PDM and the only difference I see is *Eventf, Optimization *Full and replace program *yes in the RSE. Anyone have an idea what was causing the compile in RSE to not replace the program? Thanks Steve Jones -- 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.