| 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 just been asked a question from a customer about DECmcc V1.2
Ultrix V4.3..
Is MCC's signal handling any different from the signal handling
performed by sockets in unix..
Unfortunately most of this is alien to me so I tried to take down
bullet points. He mentioned that the sockets signal handling was
CIGURG CIGIO CIGPIPE so I guess the question is does MCC use the
same for its signal handling or has anyone used this in MCC and are
there any gotcha's to look out for..
Any help welcome, even further questions to feedback to the customer.
Gary Lowe NUK CSC comms
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 4305.1 | TOOK::SWIST | Jim Swist LKG2-2/T2 DTN 226-7102 | Tue Dec 22 1992 12:41 | 8 | |
It would help if you could post what problem the customer is trying to solve. And is this as an end user, or is he/she trying to program a new MCC module or invoke MCC services from another application. MCC use DCE threads which provides for asynchronous I/O on the sockets used for interprocess and network communications. The technique is based on asynch read/write with select. The I/O system signals you mention are not used. | |||||
| 4305.2 | Cheers... | PLUNDR::LOWEG | Blimey thats good !! | Wed Dec 23 1992 05:53 | 7 |
Jim thankyou for your quick response the customer was more than happy
with the information as his main concern was if MCC used the CIG
signals he would have to make some changes to his system to cater for
them..
Gary Lowe NUK CSC...
| |||||