Compile Printing

Bill Barnes wrote:

Thanks to all for the suggestions. I didn't make myself clear. I
don't care if the compile goes to an OUTQ. I would like to know how
to redirect it so that anyone compiling in RSE would go to a
non-printer attached OUTQ. I don't want to have to redirect each time

or to remember to prompt and change the printer OUTQ. My compiles in
batch go to my own OUTQ and I can redirect to a printer if I desire.
(Rare)

Hi Bill,

WDSC uses native System i user profile and spooling functionality. Each
RSE user would have her compile listings go to the OUTQ specified in her
user profile. If you want to set up RSE to override that behaviour you
might look at the connection properties, subsystems tab.

In RSE, right click on your machine name (connection)
Properties
Subsystems (left side)
iSeries Commands (right side)

There is a place you can put an initial command. You can write a
command that will call a CL program to test the user profile and CHGJOB
OUTQ() accordingly. This would be a good plan if you feel there are
several things about the System i environment you want to set. Another
thought is to put in OVRPRTF *PRTF OUTQ(nnn) or HOLD(*YES).

Another thought is to call the user's initial program, which might be an
issue if it wants to bring up a menu. You can overcome that problem by
making a tiny change to the initial program. Test (RTVJOBA TYPE()) if
the initial program is running in batch or interactively. If
interactively, do everything. If batch, skip the menu.

--buck

I am missing something here. Each programmer has an OUTQ and compiling
in Batch or interactive causes the compiles to go to their specific
OUTQ. In RSE I have checked to see if it says *USRPRF and it does. Yet
the compiles running in the RSE subsystem go to an active printer. At
first it wasn't too bad because there was a forms change message and the
printout could be deleted but, somebody decided to answer the message
and now the compiles just whiz right through. I have switched back to
compile in batch which is OK most of the time except when someone is
running a job in QPGMR and the compile gets held up and I don't realize
it and can't figure out why my changes didn't work.

Is there a good reason why so many things in RSE are so difficult to
figure out?
Bill