"Cole, Wes" wrote:

> > Upon further research, the log files are setup as CREATOR only file
> > access.  In order to read the system log files from another account, I
> > would need to change the program to have SM capability.  Or some other
> > means to bypass the ACCESS=(r,w,x,a,s,l:CR) on the file.
> >
> At this time, I will have to let this job run from MANAGER.SYS and research
> the intrinsics that might allow me to bypass CR file access to allow me to
> run from the production account down the road.

not knowing a thing about how you run things at your site....  there's no
reason why you can't have the job stream -- that resides in your production
account -- log on as manager.sys.  just because the job card has a 'foreign'
user doesn't mean the file can't reside in this account.  also, manager.sys can
write anywhere on the system -- so have a follow-on job that does <whatever> to
the data extracted from the log files.

above, there's a mention of assigning 'sm' capability to the program.  it can't
be done since 'sm' is a user capability.  also, i wouldn't recommend changing
the access on the log files to something other than creator (or changing the
creator of the log files to someone else....).  it may just be my paranoia but
i don't think the world should have general access to your system log
files.            - d

--
Donna Garverick     Sr. System Programmer
925-210-6631        [log in to unmask]

"Unix _is_ user friendly.
It's just very selective about who its friends are.
And sometimes even best friends have fights."

>>>MY opinions, not Longs Drug Stores'<<<