- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Monitoring bugchecks
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
тАО01-21-2008 05:35 AM
тАО01-21-2008 05:35 AM
Wim
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-21-2008 10:31 AM
тАО01-21-2008 10:31 AM
Re: Monitoring bugchecks
See example belows.
hth,
Hein.
$ show sys/noproc
OpenVMS V8.3 on node ... 21-JAN-2008 ...
$create cmexec_crash.mar
.psect code,exe,nowrt
.entry start, ^M<>
pushl #0
pushal sub
calls #2, sys$cmexec
ret
.entry sub, ^M<>
clrl 0
ret
.end start
$ macro cmexec_crash
$ link cmexec_crash
$ set proc/priv=(noall,cmexec,tmpmbx)
$ spawn/priv=current run cmexec_crash
%DCL-S-SPAWNED, process HEIN_52036 spawned
%DCL-S-ATTACHED, terminal now attached to process HEIN_52036
%DCL-S-RETURNED, control returned to process HEIN
%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=000000000000000C, PC=000000000000000C, PS=7FF9DEBA
$
$ set proc/priv=(noall,read)
$ ANALYZE/ERROR_LOG/ELV TRANSLATE/INCL=BUG
Output file SYS$OUTPUT: created at 21-JAN-2008...
Output for SYS$SYSROOT:[SYSERR]ERRLOG.SYS;1
EVENT EVENT_TYPE__ TIMESTAMP_ NODE_ EVENT_CLASS
4 System Bugcheck 21-JAN-2008....... ...... BUGCHECKS
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-21-2008 11:19 PM
тАО01-21-2008 11:19 PM
Re: Monitoring bugchecks
I would like to aboid doing the anal/error or diag or ca. Is there a way to find the last bugcheck date very quickly ? Or is there somewhere a counter that increases (e.g. in ana/sys) ?
Wim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-21-2008 11:44 PM
тАО01-21-2008 11:44 PM
Re: Monitoring bugchecks
Jur.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-21-2008 11:57 PM
тАО01-21-2008 11:57 PM
Solutionyou could use the unsupported and undocumented $DERLMB (Declare Errlog Mailbox) system service and thus receive errlog entries in a program in realtime.
You would need to decode the received errlog entry and react appropriately, if it's a non-fatal bugcheck.
Volker.