Re: RDi vs SEU

On 3 April 2015 at 15:54, Kurt Anderson <Kurt.Anderson@xxxxxxxxxxxx> wrote:

As mentioned, a connection per client works.

This is how I do it. I have a connection for each environment.
Test, Dev, QA, Production. Each one has a different *LIBL and a
different user profile I connect with. o my compiled bjects have the
correct authorities for the given environment...

You can also modify the library list on the fly from within a Library List Filter. It affects verify, but not compile. Setting up a specific userID per connection can give you the correct jobD per connection so compiles work as well. (There may be another way to associate a jobD with a connection, but if so I don't know it).

If needed, one can issue an ADD/RMVLIBLE from the Command Log view.
Or, if you have a command all set up to set the environment, you can
issue a SETENV *TEST from there. Or, if you have a command or program
that you'd like to associate with a particular connection, you can
specify that in the initial command. That's handy if you have a
complex setup program that sets library lists, PATH, CLASSPATH, and so
on.

Sign up for the WDSC list here on midrange.com to interact with people
who use RDi. We'd love more participation! Well, I would...
--buck