Adam,

Thanks for that suggestion - it certainly works, but I failed to mention one added complication when I posted my original message. As developers, we should only have read access to the spoolfiles, but the SET command gives us the possibility of purging spoolfiles.

Can you think of any other way we can do this?

Thanks again.

Michael.

>>> Adam Dorritie <[log in to unmask]> 06 March 2001 15:44:58 >>>
Mike asks:

> Developers such as myself on our system currently do not have
> either SM or OP capability (quite reasonably), but we would like
> to have access to any spoolfiles on the system (particularly
> those generated by live batch jobs).
>
> - OUT.HPSPOOL does not have any group or account level security -
> read/write, etc is set to ANY.
> - We use Security/3000 and generally manage out spoolfiles with NBSpool.
> - We are running MPE version 6.0
>

Mike,

Check out the NBSpool SET command.  An SM user can issue the command SET
USERCAP=OP;USER=USER.ACCOUNT which will allow anyone logged on as
USER.ACCOUNT to act as though he/she has OP capability when issuing NBSpool
commands (this does not apply to MPE commands issued from within NBSpool).
This setting is permanent (until manually undone).

Regards,

Adam Dorritie
Easy Does It Technologies LLC
http://www.editcorp.com 
(702) 270-6402