I used to perform the following sequence:

The first night job in the sequence raised the outfence to 13.

The last job was in MPEX and "SPSAVED" all spool files and "RELEASED"
everything in @.OUT.HPSPOOL, then it lowered the outfence.

"Releasing" all spool files periodically may solve your problem.  It
depends how secure you want your system to be.  In our case they're just
spool files, and like Jay Leno and potato chips, "we'll make more".

----------
From:   John Pearce[SMTP:[log in to unmask]]

...

Everything works very well as long as the spoolfile is created by the user.
 The trouble arises with the spoolfile output from certain batch jobs.  The
jobs are initiated by the user however they run with the MANAGER logon.
When the user tries to access the spoolfile, MPE security kicks in and a
security error is reported.

Can anyone think of a good solution to this problem?  I'm not interested in
providing OP capability to the remote user.  The system in question is a
package and there is no way to run the batch jobs with the user's logon.

John