Re: Authority to spool file... resolved

Finucci, Alan, John and Buck,

Thanks for the help.  As it turns out, the server job DID switch 'current'
user profiles mid-job.  Why does it do that?  I'm sure, to IBM, it sounded
like a good idea at the time... ;)

anyway, the spool file owner was QTMHHTTP, but the 'current user' was
QTMHHTP1 (or visa versa - don't remember anymore :) - thus, the user had no
authority to the spool file.

anyway, to solve the problem, without giving undue authority to the
QTMHHTTP and QTMHHTP1 users, was to create a new outq with DSPDTA(*YES),
strictly for cgi use, and grant those users *use authority to the outq - I
overrided the printer file to the outq and away we went.

I suppose I could have made this outq the default for the http users, and
may yet still.

That seemed to me to be the best way of fixing the problem.  If anyone has
a better way, I'm listening.

anyway, thanks again for pointing the way.....

Rick