Re: 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.

So I guess (at least in this instance) I don't need the user action??

Here is the other thing... Once I have my source members listed in the object table, all of my compile options are available if I select only ONE of them. The moment I select more than one, those options disappear. Why wouldn't the same options be available?? Doesn't make sense.

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?

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?

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.