- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: .jou file -- insufficient privilege
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-24-2008 11:18 AM
тАО06-24-2008 11:18 AM
.jou file -- insufficient privilege
This seems pretty common and is getting frustrating. Is there any way around this? I'm not an administrator.
Thanks, Joe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-24-2008 11:40 AM
тАО06-24-2008 11:40 AM
Re: .jou file -- insufficient privilege
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-24-2008 12:24 PM
тАО06-24-2008 12:24 PM
Re: .jou file -- insufficient privilege
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-24-2008 12:29 PM
тАО06-24-2008 12:29 PM
Re: .jou file -- insufficient privilege
The JOU file is created in the current default directory. If you do not have permission to write in that directory, there will be problems creating the journal file.
Do you have write access to that directory? Write access to the directory is not the same as write access to the file.
If needed, you can redirect the JOU file to a different location (e.g., your login directory) or suppress it altogether. Do HELP EDIT /EDT /JOURNAL for details.
- Bob Gezelter, http://www.rlgsc.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-24-2008 12:32 PM
тАО06-24-2008 12:32 PM
Re: .jou file -- insufficient privilege
How bad is the problem? Are new .JOU files left lying around daily? Weekly? Find the bad guys who are creating them and make them delete them.
Work for your system manager:
1. Delete all of the .JOU files.
2. Consider granting an identifier to all who are authorized to edit these files. Create an ACL granting (ACCESS=READ+WRITE+EXECUTE+DELETE) to holders of this identifier. Apply this ACL to all affected files and directories.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-24-2008 12:38 PM
тАО06-24-2008 12:38 PM
Re: .jou file -- insufficient privilege
I also did edit/nojournal (same result) but I'm wondering is there a /notemp or something?
Thanks, Joe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-24-2008 12:42 PM
тАО06-24-2008 12:42 PM
Re: .jou file -- insufficient privilege
I had one guy delete his .jou's and showed him how to do it correctly. The other guy is on another shift (for the ones I'm trying now). I guess I'll have to wait unless there's another idea. I'll try some more of you suggestions shortly.
Thanks alot, Joe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-24-2008 01:03 PM
тАО06-24-2008 01:03 PM
Re: .jou file -- insufficient privilege
It is also clear that there are some significant issues here with the system security configuration, and quite possibly some security exposures. I'd get the security reviewed, lest you either expose sensitive information (such as via the journal files in the shared area, as described above) or lest somebody cross between the users and UICs identified here that are sharing directories.
There is a reasonable chance that parallel edits might be (or are?) getting lost. Colliding journal files can mean colliding filenames. Which means this sequence could mean that edits are lost. That turns into a discussion of code management systems and/or of local (usually DCL) hacks that lock out parallel accesses to shared files.
Stephen Hoffman
HoffmanLabs LLC
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-25-2008 07:30 AM
тАО06-25-2008 07:30 AM
Re: .jou file -- insufficient privilege
I can get around the file.jou issue with eve or edt/nojournal. But some of the files also have an associated file.tmp that won't allow me to save my changes due to insufficient privileges. Some files just have the file.jou and I can save fine.
Any ideas to get around the file.tmp?
I'll send him an e'mail to delete them but I'd like to update these scripts while I have the momentum. They are all several years old...probably when he first started.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-25-2008 07:21 PM
тАО06-25-2008 07:21 PM
Re: .jou file -- insufficient privilege
In any event, these allow-access approaches can also open up cross-user access and can thus be considered insecure; folks can potentially read each others' files.
The whole area of these environment appears broken.
You could also set up a per-user SYS$SCRATCH area.