- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- errlog.sys & operator.log
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
Forums
Discussions
Discussions
Discussions
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
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
03-23-2004 10:30 PM
03-23-2004 10:30 PM
errlog.sys & operator.log
we are using VMS 7.3 on GS80 server.
can someone tell me that why there is only one errlog.sys & operator.log on the system. why the system deletes the previous files from disk.
Regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-23-2004 10:41 PM
03-23-2004 10:41 PM
Re: errlog.sys & operator.log
I am not sure if I understood your question fully, anyway...
errlog.sys files contains the error log entries of the system. It is not created with the system reboot, i.e. the system uses the same errlog.sys files .
Operator.log files contain OPCOM events. This file is created whenever system reboots, or with the command reply/log .However the older versions of operator.log are not deleted by system. There must be some command or command procedure , which might be running during system boot which purges old operator.log. You have to check this on your system startup files.
HTH,
Best regards,
Lokesh Jain
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-24-2004 12:54 AM
03-24-2004 12:54 AM
Re: errlog.sys & operator.log
Look at the creation date of ERRLOG.SYS, and at the size.
If it is 'old', (say , > 0.5 years) or 'big'
( say, > 5000 blacks), then simply rename it.
To us, a convenient name is to rename the ".SYS" part to .
(And also rename it if you do a VMS upgrade. Sometimes the structure is changed a little, and then only the old part or the new part is accessible, or nothing at all)
OPERATOR.LOG is another beast. Like Martin wrote, maybe it is purged by your Startup sequence (although the PURGE suggested in the template woukd keep 3 versions).
Another cause -might- by if the file (or its directory) has a Version Limit.
Do a dir/full of the file (and of the .DIR file that holds it) and look for "version limit"
If eighther is set to 1 (one), then do a SET FILE /VERSION=
hth.
Jan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-24-2004 12:55 AM
03-24-2004 12:55 AM
Re: errlog.sys & operator.log
mixed up 2 streams.
Not like MARTIN wrote, but like LOKESH wrote.
sorry to both....
Jan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-24-2004 02:43 AM
03-24-2004 02:43 AM
Re: errlog.sys & operator.log
since I was quoted already I might chip in as well. I too suspect version limits might be the problem. Here is an example of a file with version limit and how to check if it is set:
$ set file verlim.txt/version_limit=1
$ dir/full verlim.txt
Directory DISK$USER:[ZINSER]
VERLIM.TXT;1 File ID: (8822,83,0)
Size: 0/0 Owner: [ZINSER]
Created: 24-MAR-2004 09:39:07.46
Revised: 24-MAR-2004 09:39:17.80 (2)
Expires:
Backup:
Effective:
Recording:
File organization: Sequential
Shelved state: Online
Caching attribute: Writethrough
File attributes: Allocation: 0, Extend: 0, Global buffer count: 0
-------------> Version limit: 1 <------
Record format: Variable length, maximum 0 bytes, longest 0 bytes
Record attributes: Carriage return carriage control
RMS attributes: None
Journaling enabled: None
File protection: System:RWED, Owner:RWED, Group:RE, World:
Access Cntrl List: None
Client attributes: None
Total of 1 file, 0/0 blocks.
Greetings, Martin