- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: DCL to detect runaway processes
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
тАО09-17-2007 09:10 PM
тАО09-17-2007 09:10 PM
Thank you.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-17-2007 09:25 PM
тАО09-17-2007 09:25 PM
Re: DCL to detect runaway processes
you can use the attached command procedure as a starter template.
It optionally kills/reports the CPU hogs. You should customise it for your own environment!
Regards,
Duncan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-17-2007 09:32 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-18-2007 06:13 AM
тАО09-18-2007 06:13 AM
Re: DCL to detect runaway processes
I think you're missing a procedure:
MONITOR_CPU_CHECK_CAPTURE.COM
-Jeff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-18-2007 08:30 AM
тАО09-18-2007 08:30 AM
Re: DCL to detect runaway processes
Are you interested in all processes in COM state, or just ones that are running and competing with interactive users (i.e. ones that are getting CPU time)? The point being that a process being in COM state doesn't necessarily mean it is consuming a lot of resources, in fact, if it is being starved of CPU, that's the state it will be in most of the time.
You may also be more interested in interactive jobs than batch jobs.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-18-2007 02:48 PM
тАО09-18-2007 02:48 PM
Re: DCL to detect runaway processes
I created a similar command file some time ago, but I found that defining a runaway was the most important thing. For example, you want to detect COM states - but on a multiprocessor you might also be looking for CUR states, or even COMO. Also, you might want your target process to be using over a certain threshold of CPU - but what if there are multiple runaways? Probably , your target process will not be clocking any IOs (otherwise it won't be COM/COMO/CUR all the time). So from memory I think my DCL was doing a MONITOR PROC/TOPCPU to an output file for a few seconds, reading the output file to get the top 2 or 3 processes, then looking at each process using f$getjpi to get the state and direct and buffered IOs, then storing those values, hibernating for a while then comparing the figures again. So my definition of a runaway was a process that, after x minutes, was a top 2 or 3 cpu user, was in com, como or cur state , and hadn't clocked any IOs in the intervening period.
Have fun!
PJ
Peejay
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If it can't be done with a VT220, who needs it?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-19-2007 12:43 AM
тАО09-19-2007 12:43 AM
Re: DCL to detect runaway processes
here is the missing routine as an attachment.
Regards,
Duncan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-19-2007 02:28 AM
тАО09-19-2007 02:28 AM
Re: DCL to detect runaway processes
Steve
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-19-2007 03:45 AM
тАО09-19-2007 03:45 AM
Re: DCL to detect runaway processes
I have tested both procedures and they're exactly what I'm looking for.
Duncan's procedure is the more sophisticated, but Steve's is equally effective.
Nice work !
Niall