WDSc, which I'm using, and RDI both work through a servicing job on the iSeries. You probably need to tweak this job.

Right click your connection, then click Properties.
Highlight Subsystems.
Click the iSeries Commands tab.

You can put in your library list here.

Alternatively, and this is what I do, use the Initial Command box. In the green screen world I have a short CL programs that sets my environment the way I like it, library list, outq, etc. I run that same program in the Initial Command box, e.g. CALL mylib/mypgm. So when I open the connection this program runs once and everything is set.

This works in my environment because I don't do a lot of swapping of library list. YMMV. If you do a lot of swapping you can change your environment from iSeries Command Log, where you can also enter commands. Others, I think, may have multiple connections to the same machine, each connection customized as needed.

You don't need to see the compiler listing in WDSc or RDI. The tool downloads the errors for you and you can insert them (temporarily) into the source while you correct them.

Sam

On 12/10/2010 11:08 AM, dale janus wrote:
I am still finding my way through RDI.

One problem is all my compiles now print.

With PDM, I had changed my device configuration to default to an outq
that had no printer attached. I did this for 2 of my client access
sessions and used them for compiles, or any testing I did not want
printed. Compiles went there and I could view them if needed and delete
after I was finished with them.


RDI uses the default printer for my user id and always prints. How can I
either stop printing or send the compiles to the outq I have been using
with no printer attached? I went to Window > Preferences > Remote
Systems > IBM i > Command Execution and changed the command execution to
use my job description of PROGRAMMER, but that is only for batch
compiles. And I have discovered that batch compiles do not create an
object module.

Remember I am used to the PDM method, where I need a spool file printout
to see my errors.
I just compiled a CL program and the command log says "Cause . . . . . :
See the compiler printout for a list of any messages. Recovery . . . :
If necessary, correct the errors."

Where do I see the compiler listing?

---Dale

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.