Sender: |
|
Date: |
Mon, 15 Feb 1999 16:27:46 +1000 |
Reply-To: |
|
Subject: |
|
MIME-Version: |
1.0 |
Content-transfer-encoding: |
7BIT |
Content-Type: |
text/plain; charset=US-ASCII |
Organization: |
UniSuper |
From: |
|
Parts/Attachments: |
|
|
Dear listers,
I'm changing user's capabilities in our production accounts to remove AM from
all users that don't really need it. I've come up against a bit of a snag with
spoolfile access: nearly all jobs log on as a different username to any sessions
(ie. JOB.xxx for jobs and USER.xxx for sessions). This means that without
AM, users cannot see spoolfiles from any jobs - this is especially a problem for
our normal senior programming staff who perform some spoolfile management
for the normal users.
The question is: Is there any way to allow users to see any spoolfile for the
logon account, with no (or minimal) change to the way jobs log on?
TIA.
----------------------------------------------------------
Greg Chaplin
UniSuper
Level 28, 367 Collins St,
Melbourne VIC 3000,
Australia.
Email: [log in to unmask]
Phone: +61 3 9648 4145
Fax: +61 3 9648 4141
|
|
|