Compile Print Suppression

["Bill Barnes" <bbarnes@xxxxxxxxxxxxx>]

message: 2
date: Wed, 8 Aug 2007 08:00:29 -0500
from: "Cheri Duchrow" <cduchrow@xxxxxxxxxxxxxx>
subject: Re: [WDSCI-L] Suppressing Compile prints

Bill

Buck had a good suggestion and here is another one.
If you go to Windows/Preferences/Remote Systems/iSeries and select
Command 
Execution.
There is a section for compiles that allows you to
select a job description to use when compiling with WDSc.  The default
is 
for *usrprf but you could set up one for the developers and they would
need 
to change this setting to the job description you setup that would send 
output to a que that wasn't attached to a printer.

Here we have a job description for developers and it is attached to our
user 
profile so we can keep it at *usrprf.  I know that is not always
possible.

All the developers have their own OUTQ with no printer.  If we compile
from RSE in batch the compiles run in QPGMR and the listings go to our
own OUTQs if we compile from PDM the same thing happens.  It only gets
messed up when we switch to Compile in Batch unchecked and then the
compiles go to our main Laser printer.

Now when I change back to compile n batch I get nothing and the compile
is off in lala land somewhere and I have to go back and compie in the
RSE subsystem and catch the print before it prints.  

We are all on V6