| Title: | NAS Message Queuing Bus |
| Notice: | KITS/DOC, see 4.*; Entering QARs, see 9.1; Register in 10 |
| Moderator: | PAMSRC::MARCUS EN |
| Created: | Wed Feb 27 1991 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 2898 |
| Total number of notes: | 12363 |
Since the transition of MessageQ Engineering from Digital to BEA, we have been trying to set up an arrangement to allow MessageQ Engineering to continue to participate in the DECmessageQ notesfile. Doing so has not been easy, since it would involve, in some way, giving non-Digital employees (the BEA MessageQ engineers) access to the Digital systems hosting the notesfile. We believed there was an existing model for doing this and thought that, while it might involve a lot of administrative work, we could set up such access. Now it appears that this will not be true. There is still one possible avenue left, but, so far, Digital has refused to allow any such access. As things stand now, when MessageQ Engineering comes off the Digital network, about June 1, MessageQ Engineering will no longer post or respond to notes in this notes conference. As such, active support for DECmessageQ through these informal but important channels will stop and all support will have to go through normal (CSC) contacts (this will mean all callers will have to have a CSC access number or there will be no DECmessageQ support, either formal or informal). Obviously, non remedial support (e.g., consulting, general information, etc.) questions, which the CSC does not normally handle, will have no channel for input into MessageQ Engineering. The problem appears to be the Digital security bureaucracy being unwilling to tolerate a setup which, while having some potential (low level) risk also allows Digital to support its customers in the way they have become accustom. Clearly the Digital DECmessageQ community can continue to benefit from the shared information this notesfile contains. The only change will be the lack of comments, answers, and pointers provided by MessageQ Engineering. We will keep you informed of the status of this situation as the last chance being explored plays out. However, since the potential disconnection is about two weeks ago, we suggest you prepare for that eventuality by ensuring that proper support agreements are in place so you and your customers are not totally cut off.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2876.1 | What is BEA doing??? | OZROCK::PERKINS | Some contractors, their sex-life destroyed and overwhelmed by project pressures, turn to snorting quack. | Wed May 14 1997 22:27 | 28 |
I think it would be sad (for a lot of reasons) to lose the interaction with engineering this conference supplies.... You could establish a Web Forum/news group or whatever to allow a similar dialogue with your partners (of which digital is one) and maybe one for customers. If not... can you outline what BEA is doing to support (not just in a bug-fix mode) its partners. How where and when will we supplied with the type of information a partner requires??? What will be supplied??? How do we get support questions like those asked in this conference answered??? Who in which geographies are assigned to look after the partnership??? What type of support and knowledge transfer will they be part of their role??? Peter i know you and the team are working hard on this type issue to ensure smooth migration for the customers (even if there is no love of digital :-) but the arrangements have little or no visibility to the field ... now i don't know who's responibility it is but right now 1 june is appearing as a great big black hole. Can you either post here and email me any information that is available and who is responsible for what?? Greatly appreciated Regards Kevin | |||||
| 2876.2 | Continuing support | XHOST::MARCUS | BEA/DEC MessageQ Engineering Services Manager (DTN 320-5003, 860-258-5003) | Thu May 15 1997 10:22 | 24 |
I do not know what arrangements BEA has to support its partners in a way that is different than it supports it customers. BEA does have a support service, similar to the CSC arrangement Digital has, but, obviously, smaller. BEA is ramping up that support operation to be able to service the customers who purchase support from BEA. Digital will continue to service the DECmessageQ customers and, from the engineering point of view, these will be parallel operations that we will support equally. Right now, obviously, all support is done by Digital. Over time, we expect this will shift and, in some period of time (1 year, 2 years?) the bulk of support will probably come through the BEA support channel. If and when Digital decides to stop providing direct support on its own is unknown; that is clearly based on business realities (like how soon customers stop paying Digital to provide support). As to other "partner" support, such as the consulting design, potential futures, and other such discussions that go on in this notesfile, I have no idea how BEA will do that. The person who would normally drive that, I would assume, will be the BEA MessageQ Product Manager; there is no one in that position at this point. I know that Digital is maintaining a DECmessageQ (and ObjectBroker) focus through the group that Eric Mintz is managing; I do not know what their actual charter and deliverables are. If the existing notesfile models cannot be maintained, I do not know what we will set up. However, we will almost certainly parallel whatever BEA has already set up for its other products, rather than develop a new mechanism/model or establish one specially for Digital. We strongly believe that the best way to support Digital is to maintain the active notesfiles with Digital and BEA MessageQ Engineering participation. If that is something Digital does not wish to continue, Digital will have to get in the boat with all other BEA partners (HP already, more coming) and use whatever support arrangements are/will be set up that way. | |||||
| 2876.3 | for the > 80 column challenged | XHOST::SJZ | Kick Butt In Your Face Messaging ! | Thu May 15 1997 10:36 | 33 |
I do not know what arrangements BEA has to support its partners in a way
that is different than it supports it customers. BEA does have a support
service, similar to the CSC arrangement Digital has, but, obviously,
smaller. BEA is ramping up that support operation to be able to service
the customers who purchase support from BEA. Digital will continue to
service the DECmessageQ customers and, from the engineering point of view,
these will be parallel operations that we will support equally. Right
now, obviously, all support is done by Digital. Over time, we expect
this will shift and, in some period of time (1 year, 2 years?) the bulk
of support will probably come through the BEA support channel. If and
when Digital decides to stop providing direct support on its own is
unknown; that is clearly based on business realities (like how soon
customers stop paying Digital to provide support).
As to other "partner" support, such as the consulting design, potential
futures, and other such discussions that go on in this notesfile, I
have no idea how BEA will do that. The person who would normally drive
that, I would assume, will be the BEA MessageQ Product Manager; there
is no one in that position at this point. I know that Digital is
maintaining a DECmessageQ (and ObjectBroker) focus through the group
that Eric Mintz is managing; I do not know what their actual charter and
deliverables are.
If the existing notesfile models cannot be maintained, I do not know what
we will set up. However, we will almost certainly parallel whatever BEA
has already set up for its other products, rather than develop a new
mechanism/model or establish one specially for Digital. We strongly
believe that the best way to support Digital is to maintain the active
notesfiles with Digital and BEA MessageQ Engineering participation. If
that is something Digital does not wish to continue, Digital will have
to get in the boat with all other BEA partners (HP already, more
coming) and use whatever support arrangements are/will be set up that way.
| |||||