- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: $REPLY/URGENT messaging
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
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
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
08-06-2012 07:19 AM
08-06-2012 07:19 AM
Over this past weekend we had an issue with a DCL procedure which ran amok. Within the procedure
is this line: $repl/bell/urgent/user "blah blah blah".
Due to an unforseen issue this repl message was broadcast 60,000+ times!
The message is coming from the sys$batch of a 4 node OpenVMS cluster.
Two nodes have a one system disk and the other two nodes have their own system disk.
The repl messaging finished on the broadcasting nodes quite some time ago but the
messaging continues on the remaining two nodes of the cluster.
Which is causing the user community some consternation/confusion.
A temporary workaround was to add $set broadcast=nourgent to sylogin.com
What I would like to do is find the buffer (network?) where the remaining messages are coming from.
Is this possible and, if so, where would I look?
Thanks in advance.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-06-2012 02:26 PM
08-06-2012 02:26 PM
SolutionI don't think there's a supported way to clear pending OPCOM messages.
Presumably the noise has died down by now, but if you have a repeat, I'd guess you can clear the buffer by stopping and restarting OPCOM. The process should be killable with STOP/ID. You can then restart it by executing SYS$STARTUP:VMS$CONFIG-050_OPCOM from SYSTEM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-07-2012 07:00 AM
08-07-2012 07:00 AM
Re: $REPLY/URGENT messaging
thanks John. The messages have cleared so no need to kill OPCOM. (Duh. Why didn't I think of that?!!!)
What is odd, though, is that none of the messaging is going to operator.log I would have thought any
$repl/to= would go there but these 60,000 spurious messages are not.
Regardless, the messages have finally given up the ghost.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-08-2012 12:25 AM
08-08-2012 12:25 AM
Re: $REPLY/URGENT messaging
This REPLY command issues a BRAODCAST using the $BRKTHRU system service. OPCOM is NOT involved in this operation.
A cluster-wide broadcast is being handled by the CLUSTER_SERVER process on the other nodes in the cluster.
So stopping OPCOM would not have achieved anthing.
Volker.