HP3000-L Archives

January 2001, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Cole, Wes" <[log in to unmask]>
Reply To:
Cole, Wes
Date:
Tue, 2 Jan 2001 10:03:51 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (28 lines)
> 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.

> Thanks,
>
> Wes C.
> [log in to unmask]
>
> Date:    Mon, 1 Jan 2001 12:46:04 -0600
> From:    Dennis Heidner <[log in to unmask]>
> Subject: Re: Reading system log files?
>
> You can't access the currently opened system log file.  You must issue a
> switchlog first.  As for the other log files, you should be able to see
> them from almost any account.  They are in PUB.SYS and thus are setup as
> READ:ANY.
>
> Also make sure that your program is correctly qualifying the group and
> account name.  I.E.   Log####.PUB.SYS.
>
>

ATOM RSS1 RSS2