| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2775.1 | What about licenses? | BASEX::EISENBRAUN | John Eisenbraun | Tue Feb 18 1997 12:15 | 6 |
| The obvious question then comes...
Under what terms will DIGITAL be able to obtain licenses for
DECmessageQ (and ObjectBroker)? I'm part of an engineering group that
offers DECmessageQ connectivity as an option. We aren't likely to
continue that support if we don't get the licenses for free internally.
|
| 2775.2 | Q&A | PAMSIC::STEPHENS | | Tue Feb 18 1997 17:01 | 157 |
|
BEA/Digital Partnership
External Partylines
February 18, 1997
1. What is being announced today?
We are announcing the formation of a major strategic technology and
distribution partnership between BEA Systems, Inc. and Digital Equipment
Corporation that provides the first industry-standard, universal middleware
infrastructure for developing and deploying heterogeneous distributed
production applications.
2. What are the terms of the agreement?
Under this agreement, Digital will acquire an equity position in BEA, and will
make a direct engineering development investment in ObjectBroker and
DECmessageQ on Digital Alpha platforms. BEA will acquire the ObjectBroker and
DECmessageQ products.
Both companies will collaborate not only on setting engineering direction, but
also on the marketing and sale of these products world wide. BEA will port BEA
TUXEDO to the OpenVMS platform in addition to the Digital UNIX and NT platforms
already supported, and Digital's Alpha platform will attain first-tier status
for all of BEA's products, which means Alpha will be among the first platforms
upon which these software products ship.
3. Why did Digital partner with BEA?
Digital, who has a long history with the TUXEDO product, has joined with BEA,
because both companies share the same vision for the future of middleware. BEA
TUXEDO is the leading TP environment for open systems. The winning portfolio of
BEA TUXEDO, ObjectBroker and DECmessageQ will continue to meet the long term
needs of Digital customers who require a software development infrastructure on
Alpha and and other platforms in order to develop and deploy production
business applications.
Furthermore, by working with BEA's world-wide marketing and sales organizations
around this leading portfolio of middleware products, these products will be
established as the industry-standard technologies in their respective areas.
4. Why did BEA partner with Digital?
BEA will enjoy an expanded middleware portfolio which rounds out the product
offering to their customers. As a result, BEA becomes the only full-service,
cross-platform provider of open middleware. It also better positions these
middleware products as the foundation for BEA to deliver on the vision shared
by both companies of a universal middleware architecture. Additionally, Digital
has committed to regard BEA as its premier heterogeneous middleware partner.
5. What is the value of this partnership to customers?
We see this partnership as an expansion of this product line, developed by two
leading companies, who share the goal of establishing these products as
industry standards.
This partnership forges a reinforced, joint commitment to furthering the
enhanced development of current products as individual offerings. It also
ensures their future evolution as an integrated portfolio delivering on the
strategic vision of an open, simplified, middleware architecture, based on
BEA TUXEDO, ObjectBroker, and DECmessageQ.
Developers will be able to create applications that span multiple platforms
with the freedom to mix and match technologies to fit the application
environment.
6. What is your strategic vision?
Digital and BEA's strategic vision is toward a universal middleware backbone
consisting of message-oriented, object request broker, and transaction
processing middleware that work together in an open, distributed environment.
This architecture will simplify the way customers develop and deploy
distributed, mission-critical enterprise and Internet business solutions in the
future, and is consistent with the middleware direction described by leading
industry analysts.
7. What is unique about the BEA/Digital strategy?
No other vendor is attempting to deliver a middleware vision across
heterogeneous platforms. BEA and Digital share a common vision for a universal
application development infrastructure that spans all platforms.
8. How does this agreement affect Digital's relationships with Microsoft and
Oracle?
This agreement strengthens these relationships. Oracle has publicly stated its
support for the BEA/Digital partnership as being complementary to its NCA
direction. Digital plans to focus on developing technology that strengthens
Microsoft solutions across the enterprise, including interoperability, with
this direction.
9. Will products still be offered individually as well as part of the
integrated infrastructure?
Yes. The companies will continue to provide these technologies as separate,
best-in-class products while also working toward creating an integrated
enterprise object middleware suite, one that customers are requesting.
10. Have other partners committed to this strategy?
Yes, indeed. BEA's and Digital's software partners and systems integration
partners have been briefed on the terms and significance of this agreement and
see it as a positive step forward for developing and deploying middleware
solutions to their customers based on these middleware technologies.
11. Who will sell the products?
BEA and Digital's direct sales forces and distributors will sell the products.
12. How will the product strategies of ObjectBroker, DECmessageQ, and BEA
TUXEDO change?
For the near term, the product strategies will not change. BEA will continue
the development of these products based on the existing engineering plans of
ObjectBroker and DECmessageQ. However, as is usually the case, the
engineering plans for these products will evolve over time through input from
our customers, the field, and as determined jointly by Digital and BEA.
13. Will Digital engineering for these products become part of BEA?
Partially. BEA is taking over the engineering of ObjectBroker and DECmessageQ,
while Digital will retain responsibility for the optimization of DECmessageQ
and ObjectBroker on Alpha platforms, for the development of Distributed COM for
Digital UNIX and OpenVMS, and for the DCE/ActiveX work presently underway with
The Open Group.
14. Will Digital marketing and product management for these products become
part of BEA?
No. Since Digital will aggressively sell, service, and support these products,
Digital will retain the product management and marketing organization for these
products as it continues to focus on differentiating them along with BEA
TUXEDO, for the Alpha platform, while working with BEA to bring the vision to
reality.
15. How many people are involved in the move?
There are about 70 engineering personnel involved in the move.
16. How large is the equity position that Digital has acquired?
Digital policy says we are not permitted to disclose that figure.
17. Is all of Digital's middleware part of the deal?
No, only ObjectBroker, the ObjectBroker Desktop Connection, DECmessageQ,
and the DECmessageQ SAP/R3 wrapper are part of this deal.
18. What does this mean for other Digital software products?
Other Digital software products such as ACMS, ACMSxp, RTR, our compilers and
our mail and messaging products will continue as Digital engineered products
providing solutions to Digital's installed base and other customers who need
them.
|
| 2775.3 | www.beasys.com Q&A | PAMSIC::STEPHENS | | Tue Feb 18 1997 17:08 | 177 |
| 2775.4 | the goal...BEA's EOM | PAMSIC::STEPHENS | | Tue Feb 18 1997 17:13 | 36 |
| 2775.5 | hmmm.... | WHOS01::ELKIND | Steve Elkind, Digital SI @WHO | Tue Feb 18 1997 22:56 | 9 |
| Hmmm, one or two phrases from the Q&A from BEA's webpage (.-2?) disturb me:
something like "we will occasionally sell them separately" and
something to the effect the "Tuxedo will remain the core technology".
I sure hope the DmQ (oops, BmQ?) will continue to see a separate and
fruitful life, available separately to those who wish it....
In any event, I wish the best of luck and happiness to the DmQ
engineering team in their new organization.
|
| 2775.6 | http://www.beasys.com/Company/press28.htm | PAMSIC::STEPHENS | | Wed Feb 19 1997 11:58 | 138 |
| BEA Acquires Key Object and Messaging Technology from Digital Equipment
Corporation
BEA Garners Industry Support; Becomes Only Complete, Cross-Platform Provider
of Open Middleware
SUNNYVALE, CA, February 19, 1997 - BEA Systems, Inc.'s strategic partnership
with Digital Equipment Corporation, under which BEA will acquire DIGITAL
ObjectBroker and DECmessageQ product lines, received support from industry
leaders today. These acquisitions complement BEA TUXEDO, the company's
market-leading transactional middleware product, making BEA the only
full-service, cross-platform provider of open middleware.
"BEA TUXEDO is a key technology for our middleware strategy," said Richard
C. Watts, vice president and general manager of the Computer Systems
Organization for Hewlett-Packard Company. "This strengthens the range of
open, robust middleware solutions which HP and BEA jointly provide to our
customers."
"The technology collaboration between BEA and DIGITAL will yield a portfolio
of mission-critical middleware that takes full advantage of Network
Computing Architecture (NCA)," said Mark Jarvis, vice president of Server
Marketing, Oracle Corporation. "DIGITAL and BEA are both long-time partners
of Oracle's, and we look forward to working with both companies as they
implement this strategy."
Under the terms of the agreement announced yesterday, BEA will obtain
exclusive worldwide rights and all associated patents, trademarks, and
intellectual property for three DIGITAL products: ObjectBroker, a
production-quality CORBA-compliant Object Request Broker (ORB); DECmessageQ,
one of the industry's fastest message-oriented middleware (MOM) products;
and ObjectBroker Desktop Connection, which connects ActiveX clients to
ObjectBroker. In addition, BEA will receive an unrestricted worldwide source
license for DIGITAL's SAP R/3 Wrapper. This transaction is pending approval
of the U.S. government.
As an additional part of this relationship, BEA will make offers of
employment to the DIGITAL middleware developers associated with these
products. BEA immediately assumes research and development, sales, and
support functions for these products.
As the leading independent middleware provider, BEA will make these products
available to the open marketplace. Digital will become a worldwide reseller
of BEA TUXEDO, ObjectBroker, DECmessageQ, and ObjectBroker Desktop
Connection. BEA will make these products available for resale by other BEA
partners.
"Today BEA reset the bar as the industry leader in providing open,
cross-platform middleware solutions," said G.W. Smith, vice president of the
Alliance Partners Group for Unisys Corporation. "This announcement clearly
defines the middleware market, and BEA has set the standard."
Complementing BEA TUXEDO with MOM and ORB Technologies
Today, BEA TUXEDO is the market-leading transaction middleware product and
the core of BEA's middleware platform for developing and deploying
mission-critical business applications. The addition of ObjectBroker and
DECmessageQ strengthens and complements BEA's position as the only company
providing a full-range of open middleware solutions. BEA TUXEDO remains a
foundation technology, providing the transaction integrity and scalability
required for robust distributed applications.
DECmessageQ provides guaranteed message delivery for mission-critical
applications and enables publish-and-subscribe, queuing, and asynchronous
communication between applications. The SAP R/3 Wrapper allows applications
linked through DECmessageQ to communicate with SAP applications. DECmessageQ
also includes interfaces to legacy applications.
ObjectBroker provides the basis for a CORBA-based distributed object
development and communications environment for mission-critical
applications. BEA is committed to the integration, evolution, and support of
these products into a coherent set of offerings that provide a complete
infrastructure for distributed applications.
"The acquisition of TUXEDO last year formed the core of the BEA
infrastructure and established BEA as a leading middleware provider. Today's
acquisition drives the evolution of BEA forward to become the only
full-service, cross-platform middleware provider on the market," said Bill
Coleman, BEA chairman and CEO. "This announcement marks the realization of
our vision for TUXEDO and positions BEA as both the middleware market and
technology leader."
Leading industry analyst firms believe that the combination of transaction
monitors, message queuing, and object technology is the next evolution of
middleware, especially important for applications using the Internet. With
this acquisition, BEA's enterprise middleware suite is positioned to be at
the forefront of this next-generation middleware.
BEA and ObjectBroker
With ObjectBroker, a CORBA-conforming, enterprise-class Object Request
Broker (ORB), BEA enters the growing distributed object systems market.
ObjectBroker is the industry's most production-quality ORB with an
impressive set of customers using it today for mission-critical
applications. BEA will combine the mission-critical, high-performance
deployment characteristics of BEA TUXEDO with ObjectBroker's CORBA
distributed object development capabilities, creating the first
industrial-strength enterprise object middleware. The combination of BEA
TUXEDO and ObjectBroker capabilities will allow customers to confidently
deploy mission-critical object-based applications. BEA TUXEDO will integrate
ObjectBroker to allow objects and BEA TUXEDO services to interoperate,
providing an evolutionary migration path to object technology.
BEA and DECmessageQ
DECmessageQ complements the BEA TUXEDO and ObjectBroker products.
DECmessageQ is optimized for integrating disparate distributed applications
across a broad range of hardware platforms and operating systems. The
product accomplishes this by providing a fast and reliable queuing and
publish-and-subscribe system for brokering messages. This allows customers
to communicate among existing applications through one standard enterprise
middleware infrastructure. During 1997, BEA will provide DECmessageQ as a
standalone product and integrated with both BEA TUXEDO and ObjectBroker to
ensure seamless access to both new and existing applications and systems.
Distribution
ObjectBroker, Desktop Object Broker, and DECmessageQ are available now
directly from BEA and will be resold by Digital and available to partners
for distribution. The SAP R/3 Wrapper is also available now from BEA and
Digital. BEA and Digital will participate in joint marketing and sales.
BEA Systems, Inc.
BEA Systems, Inc., is a leading provider of cross-platform middleware
solutions for enterprise applications. BEA's products enable
mission-critical, distributed applications that work seamlessly in
client/server, Internet, and legacy environments. BEA provides
transactional, messaging, and distributed object-based software for
developing and deploying these enterprise applications. In addition to its
product line, BEA provides complete solutions through its extensive partner
network and broad range of professional services. BEA is headquartered in
Sunnyvale, Calif., with offices around the globe.
BEA and Enterprise Middleware Solutions are trademarks of BEA Systems, Inc.
TUXEDO is a registered trademark in the United States and other countries.
All other company and product names may be trademarks of the company with
which they are associated.
U.S. Toll Free: (800) 817-4BEA
BEA Offices Worldwide
Questions or comments regarding the BEA Website? webmaster@beasys.com
|
| 2775.7 | other questions | WLW::KIER | My grandchildren are the NRA! | Wed Feb 19 1997 17:16 | 19 |
| Some questions from someone who is in the middle of an NSIS effort
that uses DMQ in a crucial role:
Q. Will DMQ runtime still be a part of the NAS packages?
Q. Will it still deliver on the layered products CD?
Q. Will support contracts and CSC access still be offered through
Digital or will support requests need to go directly to BEA?
Q. Future phases of the project will require DMQ development
and/or client licenses on other platforms (Likely WIN95 or
WIN/NT) - will those licenses and support contracts also remain
with Digital or go to BEA (we want to avoid multiple support
contracts - this is a state government contract and things are
difficult enough already)
Thanks,
Mike
|
| 2775.8 | | PAMSIC::STEPHENS | | Wed Feb 19 1997 18:18 | 8 |
| re:7
Hi Mike,
I know this sounds simple, but would you try (800) 817-4BEA
I'd be very intrested to hear how your questions are responded to.
Bruce.
|
| 2775.9 | No changes for now | XHOST::MARCUS | DmQ Escalation and Quality Assurance Manager (DTN 320-5003, 860- | Wed Feb 19 1997 18:53 | 22 |
|
DmQ in the NAS packages? For the immediate future, yes. As to further
in the future, presumably Digital has agreed to buy a certain amount of
DECmessageQ licenses each year from BEA. In order to hit their order
I assume Digital will continue to put DmQ in the NAS packages.
However, I believe that is a Digital (maybe Ellery SEND::WILLETT can
provide some ideas) not a BEA issue.
Same answer for the layered product CD.
Support for now will continue to go through the CSC and will continue
for some time for DECmessageQ. As sales of Be-a-q grow, I don't know
if BEA will do it own support, in parallel to Digital/CSC, or contract
that out. However, that question is still some time off.
As to licenses, for some time, Digital will continue to sell and
service DECmessageQ. BEA will sell the same product under its own
name. However, Digital customers should be able to continue to do
business with Digital just as they have for getting DmQ licenses and
support. The only difference will be that a different company does the
engineering and eventually gets the license revenue.
|
| 2775.10 | A rose by any other name.... | OZROCK::PERKINS | Some contractors, their sex-life destroyed and overwhelmed by project pressures, turn to snorting quack. | Thu Feb 20 1997 06:17 | 56 |
| First of all i would like to congratulate the DMQ engineering group and
wish them well with their new masters. As a long time advocate and supporter,
I trust you will finally have all the success that you richly deserve. I
envy you working for a company that values software!!!!
Now some questions:
Can anyone explain THIS meaning of the word "partnership"???? I can see nothing
in any of the announcements/q&a's/press releases that even REMOTELY resemble a
partnership ... well at least as it is defined in my dictionaries. Set up an
adversarial environment with one of the adversaries (BEA) holding us by the
genitals. yep win-win .... partnership???
We give BEA our excellent engineering teams and get to keep product
marketing ... that was identified in the much vaunted ovum report as being
incompetent and non-existent ... now there is a win-win
Most of the coverage is of BOBB ... does this mean BMQ will again be the poor
cousin ... having market share and revenue and starved for resource to
subside BOBB?
Why are the financials SOOOO secret???? we told everyone what we flogged rdb,
fbe, etc etc for??? we never made it a secret what our equity in MIPS etc
was???
I think we should all stand and thank the SBU for yet another f****p. As
someone who has had to deal the major accounts and major BMQ accounts in the
region for the LAST WEEK, i would like to thank the sbu for the timing release
of information to the field with the appropriate 'corporate line' ... a week
late really helps!!! NOT
and gee i wish i was an ACMS or DCE or RTR customer
where does this stand with Dcom/falcon/viper???? all of which don't run
digital platforms despite our other GREAT partnership
>>Partially. BEA is taking over the engineering of ObjectBroker and DECmessageQ,
>>while Digital will retain responsibility for the optimization of DECmessageQ
>>and ObjectBroker on Alpha platforms
so we have to make our ex-software work on our platforms ... hey i keep feeling
win-win
>>"DECmessageQ" SAP/R3 wrapper
mmmm .... now there is a beautiful piece of lying, deceit, obfuscation and
back-stabbing (caveat - this vitriol is in no way targeted at anyone in BMQ)
We currently have betas for this working with mq and falcon and are looking
at doing ports to tib, orbix and some other transports. if you have a
requirement or a customer who would like to act as a beta test site please
contact me.
Kevin (who is typing this standing after a two day meeting with one of
digital's (ex-?)major accounts)
|
| 2775.11 | the reality of the partnership | OZROCK::PERKINS | Some contractors, their sex-life destroyed and overwhelmed by project pressures, turn to snorting quack. | Fri Feb 21 1997 00:19 | 12 |
| It appears that the shape of our "partnership" with bea as started
to emerge ... on the day of the announcement bea approached the
major bmq accounts i am aware of in this region with a view of
bypassing digital ... this was without any consulation with account
teams.
where did bea get our customer list from????
not only do they hold our genitals but we (or someone) has told
where to apply the pressure to hurt us
heh ... but i'm STILL feeling win-win
|
| 2775.12 | our customer list ? they bought it. | XHOST::SJZ | Rocking the Messaging Desktop ! | Fri Feb 21 1997 03:16 | 8 |
|
in the united states we have things called "full disclosure" and
"due diligence". you don't spend millions of dollars on a tech-
nology without investigating its ability to produce revenue, and
while we here in engineering would like to think that revenue
starts with is, the truth is that it starts with customers.
_sjz.
|
| 2775.13 | no argument but... | OZROCK::PERKINS | Some contractors, their sex-life destroyed and overwhelmed by project pressures, turn to snorting quack. | Fri Feb 21 1997 05:25 | 28 |
|
>>our customer list ? they bought it.
did they???? if they bought anything i thought it was technology
and a partnership or so this thread tries to make us believe.
>>you don't spend millions of dollars on a technology
did they????
>>in the united states we have things called "full disclosure" and
>> "due diligence".
in australia public companies must comply with "full disclosure"
and inform their stockholders and the market of the details of
financial deals like this and equity positions
in australia we also have things called "ethics" and "morality". here
a partner doesn't turn around the day you enter the partnership
and try poach the other partner's customers. i would have thought
the idea was to grow the market and market penetration ... not end
very thing in a destructive war over the existing customer base.
i have not problem with the bea deal .... i believe it is the best
thing that could happen to bmq ... but don't delude ourselves it is
a partnership ... then lets sit down and see what makes sense ... how
we do business and how we compete
|
| 2775.14 | | SIOG::BATEMAN | We are all DECservers | Fri Feb 21 1997 06:52 | 6 |
|
Has there been any discussion regarding the future pricing structure
for DECmessageQ? Just wondering if BEA are going to hike the price up
(like Oracle did with Rdb).
Alan.
|
| 2775.15 | Along the lines of -.1 | BASEX::EISENBRAUN | John Eisenbraun | Fri Feb 21 1997 11:59 | 8 |
| From .1
> Under what terms will DIGITAL be able to obtain licenses for
> DECmessageQ (and ObjectBroker)? I'm part of an engineering group that
I would find it incredible if this hasn't been fully discussed with BEA
and terms decided on. So, noone wants tell us the answer or you really
don't know!?!?!
|
| 2775.16 | | PAMSIC::STEPHENS | | Fri Feb 21 1997 12:19 | 13 |
| re:15, speaking only for myself, as an excited BEA engineer, I learned more
from the press releases than I was told. So, yes...we/I really don't
know. I would like to know. I have asked also. Some folks do
seem to know more, John Parodi DTN 381-1640 may be a good contact,
otherwise...here is/was the DmQ food chain...
|--- ROBERT B PALMER Site: MSO02/02 DTN: 223-6600
|----- HAROLD D COPPERMAN Site: MRO01/03 DTN: 297-7560
|------- JESSE LIPCON Site: PKO03/01 DTN: 223-5898
|--------- DONALD Z HARBERT Site: PKO03/01 DTN: 223-1253
|----------- TIMOTHY B YEATON Site: ZKO02/03 DTN: 381-0539
|------------- CARLOS G BORGIALLI Site: ZKO02/02 DTN: 381-1684
|
| 2775.17 | (800) 817-4BEA | PAMSIC::STEPHENS | | Fri Feb 21 1997 13:46 | 3 |
| re:16,15 Having said that, call someone who is intrested in selling
the product...I have two kids that need to go thru college...
|
| 2775.18 | | XHOST::SJZ | Rocking the Messaging Desktop ! | Fri Feb 21 1997 14:01 | 7 |
|
>I have two kids that need to go thru college...
have you spoken to them about the finer points
of the military academies :-?
_sjz.
|
| 2775.19 | My understanding is... | KLOVIA::MICHELSEN | DECmessageQ Engineering | Fri Feb 21 1997 15:02 | 11 |
| re: .14
> Has there been any discussion regarding the future pricing structure
> for DECmessageQ? Just wondering if BEA are going to hike the price up
> (like Oracle did with Rdb).
...that BEA has been specifically prevented from doing this
unilaterally in the agreement (for at least 3 years).
Marty
|
| 2775.20 | | SIOG::BATEMAN | We are all DECservers | Mon Feb 24 1997 09:01 | 12 |
|
Capping the pricing is good news - my only fear about this deal was
that there would be an immediate price hike.
Have the logictics details been decided yet? Just curious if kits are
going to remain available via a Web site within Digital (I assume that
the engineers move to BEA locations). Will there be a news group
established to replace this notes conference? Just wondering because
the support available through this notes conference has been great over
the years.
Alan.
|
| 2775.21 | Not yet... | KLOVIA::MICHELSEN | DECmessageQ Engineering | Mon Feb 24 1997 10:31 | 20 |
| re: .20
> Have the logictics details been decided yet? Just curious if kits are
> going to remain available via a Web site within Digital (I assume that
> the engineers move to BEA locations). Will there be a news group
> established to replace this notes conference? Just wondering because
> the support available through this notes conference has been great over
> the years.
These points you mention are also important to me to maintain
in some form or another. Since we are working more global details
right now, I have not had a chance to work these issues.
BTW, we are not going just drop off the net once the transition
has occured. From my point of view I expect to still be on the ENET
until summer, this is because we cannot afford the disruption to
the release schedules.
Marty
|
| 2775.22 | Erik Mintz DTN 226-6704 tuxedo::mintz | PAMSIC::STEPHENS | | Tue Mar 11 1997 13:54 | 26 |
|
****************************************************************************
ANNOUNCEMENT FROM TIM YEATON AND CARLOS BORGIALLI
****************************************************************************
We are pleased to announce Erik Mintz as the BEA Systems Value-Added
Development Manager, in addition to his present responsibilities for
NetView.
The recent strategic partnership between BEA Systems and Digital regarding
ObjectBroker, DECmessageQ and Tuxedo allows for Digital to focus on
differentiation of these products on our platforms (e.g., 64-bit support,
clustering, performance, etc.)
Consequently, as a part of this, the NetView engineering team that Erik
manages will become part of Carlos Borgialli's organization.
Erik has managed the development and delivery of POLYCENTER Manager on
NetView since its arrival at Digital in 1993. In recent months, he has
been instrumental in redefining Digital's relationship with IBM/Tivoli,
and in managing the transition of NetView engineering for all platforms
back to IBM/Tivoli. Erik's organization retains a support and integration
function for Digital's enterprise management offerings, including TME 10
NetView.
Please join us in wishing Erik success in his expanded responsibilities.
|
| 2775.23 | Who works for BEA now? (or in near future) | BEAVER::MCKEATING | | Tue Mar 25 1997 14:09 | 4 |
| Is there a list of who transfered/is in the process of transfering?
thanks in advance,
Bob
|
| 2775.24 | No specifics here... | KLOVIA::MICHELSEN | BEA/DEC MessageQ Engineering | Tue Mar 25 1997 14:42 | 9 |
| ...but everyone in both OBB and DmQ from the Engineering manager (i.e. below
Carlos Borgialli) on down plus a release engineer that was actually part of
another group. The Product Mgrs, the DmQ Technical Director and all of CSC
support specialists didn't transfer. However, one person from DmQ Marketing did
transfer.
Marty
|