| Title: | *OLD* ALL-IN-1 (tm) Support Conference |
| Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
| Moderator: | IOSG::PYE |
| Created: | Thu Jan 30 1992 |
| Last Modified: | Tue Jan 23 1996 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4343 |
| Total number of notes: | 18308 |
***************************************************************
* *
* Company Confidential - For INTERNAL Distribution ONLY *
* *
***************************************************************
Support for Applications on VMS DECnet/OSI for VMS
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This message is issued by Digital Product Service Engineering and Service
Delivery (DPSE & SD) on behalf of the Product Management for the following
products available now in SSB:
MAILbus: Message Router V3.2
Message Router VMSmail Gateway V3.2
Message Router X.400 Gateway V2.2
Message Router /Profs Gateway V1.2
Message Router /SNADS Gateway V1.2
ALL-IN-1 (IOS) V3.0
DEC MAILworks V1.1
DEC/EDI V1.2
This statement is made to clarify the current support status of these products
on DECnet/OSI for VMS and does not prejudice any subsequent announcement.
Neither is the statement meant to signify the relevant status of any future
version of the above products or any other application other than those listed
above.
................................................................................
The above products have NOT been engineered to function on any DECnet/OSI
platform environment (DECnet/Wave 2 or later) - their expected behaviours are
undefined. Consequently, installing these products on platforms other than
specified in the current application SPDs is
*** UNSUPPORTED BY ENGINEERING ***
These products continue to be supported on DECnet VAX or DECnet VAX Extensions
for VMS for as long as Engineering support for these network platforms
continues.
Customers who install any of the above set of products on a DECnet/OSI
platform (Wave 2 or later) and then finding problems can expect:
* Remedial support from Engineering only to be available if they can
demonstrate the same problems on the current SPD supported platforms.
* Any remedial solutions to be given only in the context of the
supported platforms and NOT for DECnet/OSI (Wave 2 or later)
platforms.
If solutions provided by Engineering are found to work on other platforms, it
will be entirely fortuitous and they remain, in that context, unsupported by
product engineering.
If, in the local interests of customer satisfaction, a field support
group provides solutions delivering the above products on a DECnet/OSI
platform, that group OWNs the continued support of such a solution. A
response to calls for Engineering to provide any backup support will be at
Engineering's discretion.
If there should be any concern about the availability of functionality,
feasibility on DECnet/OSI platforms, please:
*** contact your CSC for advice ***
Issues arising from such enquiries are to be directed to the following Product
Managers for their consideration, advice and action:
DECnet/OSI Iain Smith @LKG, Judy Cross @LKG
ALL-IN-1 Bill Colquitt @ZKO
DEC/EDI Nad Nadesan @REO
DEC MAILworks Ian Gunn @ZKO
MAILbus Debra Murphy @ZKO, Audrey Augun @ZKO
Statements of intent and future commitment for these applications
obtainable from Product Management will be made available in due course.
Christopher Mackay (DPSE & SD) @REO [ November 20th 1992 ]
M.E. MAILbus and ALL-IN-1
John Beecher @REO
Frank Ciszek @MKO
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Technical Notes
~~~~~~~~~~~~~~~
In the context of DECnet/OSI, MAILbus Engineering (MIG) will release the
MAILbus X.400 MTA for VMS to deliver the equivalent functionality to Message
Router X.400 Gateway on DECnet VAX Extensions (Wave 1) first and then
eventually on a future DECnet/OSI platform for both OpenVMS and Alpha AXP.
The availability of the MAILbus 400 MTA for VMS will NOT automatically
enable the functioning of the other applications using X.400 services (e.g.
DEC/EDI, ALL-IN-1, etc.) on DECnet/OSI - the applications will still need
to be re-engineered to work fully in the DECnet/OSI context and take advantage
of DECnet Phase V features.
To remove dependence upon either MAILbus / Message Router, any product
requiring X.400 services will need to use the X.400 API interface. This
interface is not "plug-in" replacement for MRIF. All applications using MRIF
will need to be re-engineered.
Applications that make use of the DDS supplied as part of the base Message
Router product will also require to be rewritten / redesigned to use the X.500
Directory Service API if they are to remove that element of dependence.
Applications may have an DECnet Phase IV NCP dependence; in the context
of DECnet/OSI, this functionality can be supported by the use of the NCP
Emulator supplied with DECnet/OSI (Wave 2). To remove NCP dependence will
usually require the application to be reworked to use NCL.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ [ End ]
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1842.1 | MB PM Statement - Strategy for OSI | ROCKS::MAILBUS | SPE @REO | Wed Dec 02 1992 17:08 | 79 |
+---------------------------+tm
! ! ! ! ! ! ! !
! d ! i ! g ! i ! t ! a ! l ! I N T E R O F F I C E M E M O
! ! ! ! ! ! ! !
+---------------------------+
* * * Company Confidential Memo * * *
TO: Distribution DATE: December 2, 1992
FROM: Debra Murphy @ZKO
John Kell @REO
Audrey Augun @ZKO
Derek Bell @REO
DEPT: Messaging Program
Subject: Electronic Messaging Product Strategy for DECnet/OSI
The intention of this memo is to provide you with the overall strategy for
the Messaging Program's support of the DECnet/OSI networking environment.
Following this memo, we will continue to provide you more detailed plans and
information over the next 60 days to help you decide the best strategy for
your customer.
The component products being discussed in this memo include :
Message Router (UPI 732),
Message Router VMSmail Gateway (UPI 730),
Message Router X.400 Gateway (UPI VDM),
Message Router/PROFS Gateway (UPI VCG),
Message Router/SNADS Gateway (UPI VDU), and
MAILbus 400 Message Transfer Agent (UPI O4Q).
All of the above products are supported on DECnet-VAX and DECnet-VAX
Extensions, and will continue to be supported in this environment.
The Messaging Program will support Message Router, Message Router VMSmail
Gateway, and MAILbus 400 MTA on DECnet/OSI, Wave 3 within one quarter of
Wave 3 FCS. By supporting Message Router and Message Router VMSmail Gateway
on DECnet/OSI, we provide customers the ability to transition their network
to DECnet/OSI, while providing support for their legacy applications such as
ALL-IN-1 Integrated Office System. The MAILbus 400 MTA provides 1988 X.400
Messaging Services with higher throughput and greater reliability than the
Message Router X.400 Gateway. It is our intention to offer an incentive
tradein program for the Message Router X.400 Gateway to the MAILbus 400 MTA
for customers who need to transition to DECnet/OSI and who want to take
advantage of the superior capability of MAILbus 400. Other applications that
use Message Router, such as DEC MAILworks for VMS and Teamlinks, will also
benefit through this support, however, future versions of these products
will implement a direct connection to the MAILbus 400 MTA, providing better
connectivity to X.400 in the DECnet/OSI environment.
We will not provide support for the above products on DECnet/OSI, Wave 2.
The rationale for this decision is the following:
- Fewer disruptions to the customer environment, by minimizing the
number of times customers have to upgrade their network and network
applications;
- Decreased cost to engineering, by supporting the environment that
customers will want to achieve over time;
- Availability of the tools and documentation required to more easily
integrate the current environment and transition the customer base
to the new environment.
Message Router/PROFS and Message Router/SNADS will not be supported in the
DECnet/OSI environment, but will continue to be supported in the current
environment as stated above. Alternative strategies for connecting to IBM
environments will be detailed at a later date.
In the next couple of months, we will be providing you a PID, containing
more detailed information on deliverables, timeframes and marketing programs
for use with your customers.
To Distribution List:
<removed>
| |||||