| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
I have a customer running 5.5 VSM and DECmcc 1.1. I have already
installed to Alarms Patch to get the Icons to fire, but I'm having
another problem that I wonder if its related to the queuing issues
in 5.5.
I've been trying to get alarms to enable in batch and can't seem to
get it to work.
I've tried just one alarm, which tests to see if Circuit SVA-0 counters
have been zeroed. This works fine when I enable it within the Iconic
Map. It also will work if I have a separate MCC command line session
going and issue the command:
Enable MCC 0 Alarms Rule SVA-0_Counters_Zeroed, in DOMAIN
WL_NS:.ENGINEEGING
While I'm still in MCC command line, this works.
But when I put it in a batch job after adding the line:
SHOW MCC 0 ALARMS RULE * ALL CHARACTERISTICS, IN DOMAIN ENGINEERING,-
AT START=(+3-00:00:00)
Nothing happens.
I checked the Batch job log and it shows the rule being activated with
no errors. SHOW/QUEUE/ALL tells me the job is still Executing.
I'm at a loss. I checked the rest of the notes but didn't see anything
like this. Could it possibly still be a 5.5 queuing problem? This
customer is really going to be upset if I can't auto-enable alarms from
batch.
Thanks for any help you can provide.
Rick
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2999.1 | is que on the event 'sink node'??? | ICS::WOODCOCK | Fri May 15 1992 09:44 | 10 | |
Hi Rick, The only experience I can offer is that if this is an "OCCURS" rule (which it appears to be) then the batch queue *must* be on the same system the events are sinked to. A generic cluster batch will not work for you here. Specify the /que= to a specific queue on the system you know works from fcl. best regards, brad... | |||||
| 2999.2 | Importance of being backward compatible on VMS | TOOK::BURGESS | Fri May 15 1992 10:08 | 6 | |
For VMS 5.5 the queueing subsystem underwent substantial changes including some changes to the sys$sbjw system service used by the ALARMS module. I believe that the developer created a patch for VMS 5.5 systems. I'll forward your request to the DRI. \Pete | |||||
| 2999.3 | CLuster Queue is Culprit! | ODIXIE::PEACOCKR | Fri May 15 1992 13:08 | 14 | |
Thanks for the input - I've solved the mystery. The VAXstation 4000
that DECmcc is set up on is part of a cluster. I was using the
generice batch queue - COMM_BATCH. I found out that I had to specify a
specific queue ( which did not show up with SHOW/QUEUE)
COMM_BATCH_MYNODE.
Then everything worked as advertised.
I have a feeling that there may be other issues with using this in a
clustered environment as well. I'll search the notes for this but if
anyone knows some real problems maybe they could point me in the right
directions.
Rick
| |||||