Problems with spool files

["James H. H. Lampert" <jamesl@xxxxxxxxxxxxxxxxx>]

At this point, I don't know any more than what I'm saying here; I'm 
waiting for a customer to answer some questions.

But here is the gist of the situation:

I'm creating a spool file using QPRINT, from O-specs in an RPG program.

I'm then emailing that spool file using Gumbo SpoolMail.

I'm then deleting the spool file.

All of this is automated with a CL program.

At some point in this process (I don't know where yet), a CPF3309 is 
being thrown, and on at least one occasion, Gumbo Spoolmail is throwing 
an exception of its own (SM11014, "Unable to e-mail 
soandso@xxxxxxxxxxxxxxxxx . . . . see the messages in the job log for a 
more complete description of what caused the error . . . .").

None of this happened when the customer's database administrator tested 
the program, BUT I noticed that her user profile doesn't have the 
default printer set to an actual printer, while the shipping clerk's 
user profile does.

I've asked whether there is new hardcopy coming out where it wasn't 
coming out before. Could it be that the shipping clerk's printing 
defaults are grabbing my spool file and printing it before it can be 
emailed and deleted?

Do I need to change all this from printing to QPRINT, to printing to a 
print file that's guaranteed to never be connected to a real printer? 
And if so, how? (Around here, we only have one physical printer 
connected to an AS/400, and if we want something printed, we have to 
explicitly send it there from WRKSPLF, so I'm not exactly "up" on how to 
keep spool files from being printed.)

--
JHHL