| 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 |
When using DECnet as the transport protocol for a Collector AM, what DECnet object is required on the MCC system receiving the data collecor events? I tried setting up the Collector AM on a customer's DECmcc system to collect events from the local VMS operating system on that system, and when I run a sample data collection script (CHECK-DISK.COM) I get an error message to the extent that the "remote network object is unknown". I specify the node name of the DECmcc system as the host name, DECnet as the transport, and give the mcc_send_event API the name of the collector defined within MCC, and then receive the above mentioned error. What should I be looking for on the "remote" system (aka DECmcc system) to insure that the collector application on a remote system works with the mcc collector AM on the targetted mcc system? Thanks. Merlin
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 5194.1 | bit by bit. inch by inch... | TOOK::MCPHERSON | Dead or Canadian? | Fri Jun 11 1993 17:24 | 58 |
FIRST, you must (successully) enable the sink on the MCC system.
MCC> enable mcc 0 collection sink decnet
If that's successful, you should see a new zero-based object named
"mcc_evc_sink" with a PID for the process that's actually running the
sink executable.
Example:
SHOW NODE4 0 OBJECT MCC_EVC_SINK ALL ATTR
!
!Node4 LOCAL_NS:.polyw2 Object mcc_evc_sink
!AT 11-JUN-1993 16:15:17 All Attributes
!
!No such entity: Node4 0 Object mcc_evc_sink
! Unknown Entity = Node4 0 Object mcc_evc_sink
!
ENABLE MCC 0 COLLECTION SINK DECNET
!
!MCC 0 COLLECTION_AM SINK DECnet
!AT 11-JUN-1993 16:15:30
!
!Enable completed successfully.
!
SHOW NODE4 0 OBJECT MCC_EVC_SINK ALL ATTR
!
!Node4 LOCAL_NS:.polyw2 Object mcc_evc_sink
!AT 11-JUN-1993 16:15:53 All Attributes
!
! Name = MCC_EVC_SINK
! Number = 0
! Process ID = %X0000017D
!No such entity: Node4 0 Object mcc_evc_sink
! Unknown Entity = Node4 0 Object mcc_evc_sink
!
EXIT
!
If you don't have enough *DEFAULT* privs, you won't get it up. The
sink process. that is. You will need (as recently discussed) the
following DEFAULT privs to start the sink process: SYSNAM, DETACH,
TMPMBX and NETMBX.
If you have UCX installed on the system, then you should use the UDPIP
sink. It operates faster than the DECnet sink, since UDP is a very
light-weight mechanism, perfect for events. To enable the UDPIP
collector thread, just type:
MCC> enable mcc 0 collection sink udpip
Note that you *may* have to modify some older data collector scripts
(i.e. from the V1.2 kit) to include the 7th argument for protocol
(either DECNET or UDPIP).
Have fun.
doug
| |||||
| 5194.2 | Bingo! | ANGLIN::CLAYTON | Merlin Clayton DTN 445-7217 | Fri Jun 11 1993 18:16 | 8 |
Thanks Doug. I forgot about enabling the event sink when I was setting this up by the seat of my pants. I guess the moral is RTFM! Later... Merlin | |||||