- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: DECSCHEDULER
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
тАО07-16-2009 07:25 AM
тАО07-16-2009 07:25 AM
Re: DECSCHEDULER
A VSS.DAT of that size will probably cause you performance issues.
Purely Personal Opinion
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-06-2009 08:44 AM
тАО08-06-2009 08:44 AM
Re: DECSCHEDULER
Not solved by db_utility.
I had this problem before and I think it was resolved by a reboot but can't be sure.
VERMONT_CREAMERY.LOG may look dormant but it's not.
I would be happy if there was a way to delete history only for one job.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-07-2009 12:49 AM
тАО08-07-2009 12:49 AM
Re: DECSCHEDULER
Thanks for all the responses to my issue.
We have found the cause and a resolution.
On one of our test clusters , i have been able to reproduce the problem.
It appears that when the history record for the job show it has run 260,080 times , you get the error message during the sched show history command for the job in question.
You then get the error from then on ....
When you next issue the command to close the schedule log file with the /summ switch , the log file rolls over and all job history are retained in the new log file. With the exception of the job that has the issue. This job has it's count reset to 0. Thus the error then goes away.
In production we roll over the sched log file every 90 days , with the /summ switch.
Thus on at the end of august the error will go away.
They will live with it until then. It's easier than navigating the change and testing process to get the log file rolled over as an exception.
Thanks everyone for the input...
Kevin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-07-2009 10:04 AM
тАО08-07-2009 10:04 AM
Re: DECSCHEDULER
The solution is not working for me.
I already tried scheduler close log/summary and also scheduler close log (without the sum).
The log is not not rolled over and renamed to .old , despite the -I- message that log has been closed.
In the other log file (nsched$:nodename.log) there is an "error renaming log".
I see a possible solution by shutting down scheduler, rename the file manually then start the scheduler. Needs to be tested though.
If history is only needed for manual research , it should be still accessible by sched sho hist /file=vermon_creamery.old
Cheers.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-17-2009 11:35 AM
тАО09-17-2009 11:35 AM
Re: DECSCHEDULER
I don't know if it will help you but there is
a strange log file called : VERMONT_CREAMERY.LOG
When you do a report this file is involved.
Also, it is a good idea to recreate it when you can. Here each day we stop the scheduler and make a cold backup of VSS.DAT file and rename the VERMONT_CREAMERY.LOG ... to VERMONT_CREAMERY.OLD!
When the Cremery is to large, it has an impact on performance !... ;)
Also, each Weekend the VSS.dat Data Base is compressed with the DB_UTILITY.EXE utility after taking a backup of it.
Regards
YH
sys>dir/col=2 disk_ced:[nsched.data]*cream*
Directory DISK_CED:[NSCHED.DATA]
VERMONT_CREAMERY.LOG;1
VERMONT_CREAMERY.OLD;884
VERMONT_CREAMERY.OLD;883
VERMONT_CREAMERY.OLD;882
VERMONT_CREAMERY.OLD;881
VERMONT_CREAMERY.OLD;880
VERMONT_CREAMERY.OLD;879
VERMONT_CREAMERY.OLD;878
sys>dir nsched$data:vss.dat /dat
Directory DISK_CED:[NSCHED.DATA]
VSS.DAT;513 12-SEP-2009 06:46:58.06
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-13-2009 09:23 AM
тАО10-13-2009 09:23 AM
Re: DECSCHEDULER
After moving the log to [DATA] (using RENAME) the command $ sched close log/summary did not fail anymore, vermont_creamery.log was rolled-over normally and also got rid of the SYSTEM-F-HPARITH error in history reports.
Did'n't even need to stop scheduler for this.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-14-2009 01:27 AM
тАО10-14-2009 01:27 AM
Re: DECSCHEDULER
So for the next 2 years + x months we are error free again .....lol
Based on the fact we are moving to a Solaris/ Java / VCS based solution ...in the next 12 months , this is no longer an issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-07-2011 03:17 AM
тАО09-07-2011 03:17 AM
Re: DECSCHEDULER
Hi Everyone ,
Would anyone know how to change the location of where the VERMONT_CREAMERY.LOG files are created in. ?
So for example if I want to change the location they go from dsa100:{vermont] to dsa300:[vermont] , how do I change this , is there a parameter file ? (struggling for a few hours trying to solve this)
Thanks,
Dave
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-07-2011 06:59 AM
тАО09-07-2011 06:59 AM
Re: DECSCHEDULER
Google is your friend.
"Note: You can set the name of the log file by modifying a line in the startup file SYS$STARTUP:SCHEDULER$STARTUP.COM. If you do not modify this file, the default file name is NSCHED$:VERMONT_CREAMERY.LOG. This command file is placed in your SYS$STARTUP directory when you install DECscheduler."
Here's the Google sequence I used. "VERMONT_CREAMERY.LOG". First hit in what is returned an index from a DECscheduler manual. Search in the index page (via Cmd-F here, probably Ctrl-F in your browser to find the string), and locate the index entry "NSCHED$:VERMONT_CREAMERY.LOG", follow that index entry link, and find above text.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-07-2011 10:46 AM
тАО09-07-2011 10:46 AM
Re: DECSCHEDULER
Brilliant Hoff , I was googling but I didnt get that at all hmmm . Thats a great help I will follow it up myself and see how I go.
Many thanks indeed
- « Previous
-
- 1
- 2
- Next »