Re: Changing job description for compiling

Thanks everyone for the responses. I've made a note and hope to try this out soon.

Oh Vern, I just had to respond and say that I know that the CRT* commands don't have the job description as a parameter on the i. ;) However, the response I was given said it was a parameter, and I thought that maybe the interface for the command in WDSCi might include additional parameters for an under-the-covers submit.
Thanks again,
Kurt

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Joe Pluta
Sent: Monday, March 22, 2010 9:23 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Subject: Re: [WDSCI-L] Changing job description for compiling

This is my preferred method as well. I've got a command SEL (Set Environment Libraries) and it does the same thing. I have a value CURPROJ that is defaults to whatever is my current project, and if I need to switch I execute the command, usually from the Commands Log view (although right-clicking on the Objects subsystem in RSE and selecting Run Command works as well).

Joe

I have a signon program or whatever it's called hooked onto my user profile.
That program manages my configurations, library lists and stuff (organized
on the sense of a "project" with a notion of "current project"). I have
this program registered in RDi/RDPi as the startup program (for the
connection? Must be because it only does it on this one system). When the
connection starts, the program runs and my "current project" config is
loaded into the server job that serves RDi/RDPi. THis stuff is used for
compiling as far as I've seen. Whether I submit compiles to batch OR run
them inline, they always work with this job setup. When I want to change
it, on the command line on RDi/RDPi, I issue "setproj PAYROLL" for example
and it switches all the job settings. From then on the new settings are
used.

Works well for me, better than managing lots of connections for me.

Stu




On Mon, Mar 22, 2010 at 14:39, Buck <kc2hiz@xxxxxxxxx> wrote:

On 3/22/2010 2:45 PM, Tyler, Matt wrote:

The only way I know of (in WDSC 7.0) is to create a new connection for
each job description. Might seem over kill but then you get to code the
job description into the connection properties. You could even name the
connection like the job description name.

That's about how I do it. I have a bunch of connections; one for every
project and global ones for 'test' and 'production.'
--buck
--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & 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.