Re: search & compile options

My compile properties are still at *SRCLIB.

I'm good with creating a user defined command - I really only have a few pgm object libraries

-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of MichaelQuigley@xxxxxxxxxx
Sent: Tuesday, October 27, 2015 8:21 AM
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] search & compile options

"WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx> wrote on 10/26/2015 01:00:03 PM:

----- Message from Buck Calabro <kc2hiz@xxxxxxxxx> on Mon, 26 Oct
2015 11:36:45 -0400 -----

To:

wdsci-l@xxxxxxxxxxxx

Subject:

Re: [WDSCI-L] search & compile options

On 10/26/2015 11:22 AM, Greg Wilburn wrote:

Thanks a bunch for the detailed instructions... I already had a

compile option setup for compiled RPGLE members into my object
library (my source and objects in separate libraries).

I try to respond in such a way that the archives will benefit.
Hopefully that's the case here!

The missing piece was using iSphere to Export to Member filter

(then open in table) and having a User Action.

One question... Once I had the objects listed in the table, one of

the options available (right-click) was "Compile". So I tried it.
I was very surprised to learn that it placed the compiled pgm object
in the "correct" library (as opposed to the library containing the
source). I'm not sure how or why this option placed the object in
the correct library??

Hm, don't know - my source and object are all in the same library. I'll
have to tinker with this one.

On the connection properties, select Subsystems, and then the Commands
tab. The first property is the Object Library. It may be grayed-out, but
you can click the small left-pointing arrow which will then point to the
right and then you can specify the Object Library. I believe it defaults
to *SRCLIB.

I am just a user, but if I had to guess at why it is this way, imagine
that I'd selected CLP, SQLRPGLE, RPGLE, and REXX source member types.
Which compile command ought to be used for this grouping?

The last compile command used for each member type is used. It's
equivalent to pressing Ctrl+Shift+C in LPEX.

Yes, it is possible to pre-check the list and if they aren't all the
same source member type to pop up a warning or even a prompt for a
compile command for each type. Maybe they had to get it out the door,
and didn't have time for the extra bling. Maybe this would make for a
good RFE?

If you want more options an RFE is the way to go--no guarantees IBM would
accept it and even if they do, there's no guarantee when they would
deliver the functionality. I've generally been able to compile most
everything with the available compile option. Occasionally, I have to omit
a member or two from the select so that I can compile a module instead of
a program or vice versa.

Anyway, the inability to submit one compile across multiple members is
why I wrote (and suggested) a user command for it. User commands work
fine across multiple members.

--
--buck