In a message dated 7/9/98 7:29:33 PM GMT,  [log in to unmask] writes:

<< Is there an easy way for users to access spoolfiles that are in the same
 account but different groups without giving the user 'OP' capability??
 In our development environment we have users logon to their own 'home'
 groups in which they can access their own $stdlists but they also run
 jobs in other groups which simulate the production environment.  They
 cannot access the $stdlists or spoolfiles from these other groups
 because the file access is restricted to the creator of the file.  Even
 though they may have created the job that is run, they cannot view the
 $stdlist from it. >>

Try setting the OUTCLASS for the job, which will set the $STDLIST a PSEUDO
printer, then allow the user to ASSOCIATE to that printer, this will give them
access to the spoolfiles on the printer, regardless of the user/group/account
the job or the user are logged into. The only problem with this, is that only
one user can associate to the printer at the same time.

Hope this is helpful.

Andy Popay
ARC Central.