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



I don't know if this is your problem, but it could be worth checking. In
your Compile Command, if you specify &L for the object library instead of
&O it will compile it to the source library instead of the object library.

i.e., If you want to compile to the object library specified under the
command execution properties, your command should look something like
this:

CRTBNDRPG PGM(&O/&N) SRCFILE(&L/&F) SRCMBR(&N) OPTION(*EVENTF)
DBGVIEW(*SOURCE)

If you've specified something like:

CRTBNDRPG PGM(&L/&N) SRCFILE(&L/&F) SRCMBR(&N) OPTION(*EVENTF)
DBGVIEW(*SOURCE)

it will generate the program in the source library.

HTH,
Michael Quigley
Computer Services
The Way International
www.TheWay.org

wdsci-l-bounces@xxxxxxxxxxxx wrote on 08/23/2008 01:00:02 PM:

----- Message from "Forbes, Vincent" <Vincent.Forbes@xxxxxxxx> on
Fri, 22 Aug 2008 15:55:17 -0400 -----

To:

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

Subject:

[WDSCI-L] Compiles into wrong lib

In the preferences; Remote Systems/iSeries/Command Execution I have been
using the "Object library" to change the compile library.

When I change the "Object library" & run a compile, it uses the old
library. Any ideas.

I just recently updated the patches on WDSC.

I am on...
Version: 7.0.0
Build id: 20070202_0030

\Vincent

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.