I apologize if you already know what follows, but thought someone should spell
it out.
When you connect, what you are actually doing is starting a job on the i. This
job starts up using the relevant attributes of your user profile such as job
description, output queue, etc. It does NOT run your initial program.
If you open the properties for the connection, go to the Subsystems menu item,
and then the Commands tab, you can specify overrides to the library list your
connection job uses, and a command to do anything else that you want. This
command can be a call to an 'initial program' of sorts that does anything you
set it up to do, like changing output queues and so forth.
If you choose to run your compiles in batch (I don't), you can also override
some attributes, such as job description, for the compile jobs on the Objects
tab. This is somewhat analogous to parts of the PDM Change Defaults screen that
you can access using F18.
With a little basic understanding of work management on the i and some thought,
it's pretty easy to set it up to do whatever you need it to do with your library
lists, output queues, and so forth.
Dave Shaw
Mohawk Industries
----- Original Message ----
From: dale janus <dalejanus@xxxxxxxxxxxxxxxxx>
To: wdsci-l@xxxxxxxxxxxx
Sent: Mon, October 31, 2011 10:27:23 AM
Subject: Re: [WDSCI-L] Find not working, gives error message
Changing user profile won't work for me. I use 5 client access
sessions. Two are for programming and have the outq set to send
compiles, (actually, all printing) to an outq with no printer. This is
what I use for testing and compiles so I don't have to worry about
printing hundreds of pages when stuff goes wrong. Or any compiles.
Now that you are making me think about it, those two sessions are really
job descriptions called PROGRAMMER.
I would like some way to set RDI to use that job description and then I
think things would work the way I prefer. I will play around with the
connection properties and see what I can find.
---Dale
I can change the user library in the connection from QSYS to QGPL so that
my searches work and I avoid the error message. But it does not remember
my change so when I start RDI up, it reverts to QSYS.
The simplest way is to set both current library and output queue in your
user profile:
CHGUSRPRF CURLIB(<library-name>) OUTQ(<library-name>/<output-queue-name>)
These user profile attributes should be use for the job attributes of your
RDi connections.
PS
Multiple RDi users should not use the same library as current library. Bad
things can happen, like one RDi user receiving an other's output. You
should consider creating a 'personal' library for each RDi user.
midrange.com
