       %                                COMPAQ   	  Software   Product  Description  D  ___________________________________________________________________  D  Product Name:  MAILbus 400 Application Program Interface        SPD8  54.69.04                for OpenVMS Alpha, Version 2.0C    PRODUCT DESCRIPTION  G  MAILbus 400[TM] Application Program Interface (API) is a layered soft- F  ware product that resides on an OpenVMS[TM] Alpha system. It providesD  a programming interface that gives application development program-G  mers access to the messaging services provided by the MAILbus 400 Mes-   sage Transfer Agent.   I  MAILbus 400 API provides a C language interface to the MAILbus 400 MTA's E  messaging services. An ANSI C conformant compiler is required to use   MAILbus 400 API.   D  A MAILbus 400 Application Program Interface license is required forE  application development only. An application built using MAILbus 400 E  Application Program Interface can be operated without the need for a 3  MAILbus 400 Application Program Interface license.   E  MAILbus 400 API can operate either colocated with MAILbus 400 MTA or #  on a remote OpenVMS Alpha machine.     CONFORMANCE TO STANDARDS   D  MAILbus 400 API is an implementation of the X/Open[TM] CAE Specifi-E  cation - OSI-Abstract-Data-Manipulation (November 1991 edition), and E  the X/Open CAE Specification - API to Electronic Mail (November 1991 D  edition). These specifications define a vendor-independent program-I  ming interface to X.400 messaging services. However, applications linked   D                                                           April 1999  D                                                          AE-QEFZE-TE       F  with the MAILbus 400 API can only communicate directly with the MAIL-E  bus 400 MTA. MAILbus 400 API provides both the Application and Gate- 9  way interfaces defined by the X/Open CAE Specifications.   F  MAILbus 400 API does not support the Retrieval Functional Unit of the3  X/Open CAE Specification - API to Electronic Mail.     YEAR 2000 READY (Y2K)  G  MAILbus 400 Application Program Interface also becomes Year 2000 Ready E  with Version 2.0B release. Any two digit dates received by the MAIL- (  bus 400 API are interpreted as follows:  :  -  Years "70" to "99" (inclusive) as "1970" to "1999" and  7  -  Years "00" to "69" (inclusive) as "2000" to "2069".   E  MAILbus 400 API V2.0B will correctly process, calculate, compare and H  sequence date data from, into and between the twentieth and the twenty-G  first centuries, and the years 1999 and 2000, including leap year cal- E  culations, when used in accordance with the associated DIGITAL Prod- E  uct documentation and provided that all hardware, firmware and soft- F  ware used in combination with such DIGITAL Products properly exchange%  date data with the DIGITAL Products.     HARDWARE REQUIREMENTS    Processors Supported   E  Any Alpha AXP[TM] processor supported by DECnet[TM]-Plus for OpenVMS G  Alpha. See the DECnet-Plus for OpenVMS Alpha Software Product Descrip- E  tion (50.45.*) for further information on supported hardware config- 
  urations.  2  Disk Space Requirements (Block Cluster Size = 1):  '  Disk space required for    5300 blocks   installation:    #                                   2          '  Disk space required for    4600 blocks   use (permanent):   F  These counts refer to the disk space required on the system disk. TheE  sizes are approximate. Actual sizes may vary depending on the user's 9  system environment, configuration, and software options.     CLUSTER ENVIRONMENT  D  This layered product may be installed on each node in any valid andE  licensed VMScluster[TM] configuration. Each node of a VMScluster can F  run one instance of MAILbus 400 API. Each API is independent and doesF  not share workspace and operates as it would on an individual system.  F  VMScluster configurations are fully described in the VMScluster Soft-F  ware Product Description (29.78.xx) and include CI[TM], Ethernet, and#  Mixed Interconnect configurations.     SOFTWARE REQUIREMENTS  .  One of the following software configurations:  '  o  OpenVMS Alpha Operating System V6.2 -     DECnet/OSI[R] for OpenVMS V6.3 with ECO8.   '  o  OpenVMS Alpha Operating System V7.1 H     DECnet-Plus for OpenVMS V7.1 with ECO2, or later, including the DEC-F     net Application Interface component (formerly known as the OSI Ap-"     plications Kernel or OSAK[TM])  '  o  OpenVMS Alpha Operating System V7.2 F     DECnet-Plus for OpenVMS V7.2, including the DECnet Application In-D     terface component (formerly known as the OSI Applications Kernel     or OSAK[TM], V3.0-003O          #                                   3          OPTIONAL SOFTWARE  *  o  DEC C for OpenVMS Alpha, V4.1 or later  G  OpenVMS Tailoring: The following OpenVMS classes are required for full '  functionality of this layered product:     o  OpenVMS Required Saveset    o  Network Support     o  Programming Support     GROWTH CONSIDERATIONS  E  The minimum hardware/software requirements for any future version of D  this product may be different from the requirements for the current	  version.     DISTRIBUTION MEDIA   E  MAILbus 400 API is available as part of the DIGITAL[TM] CD-ROM Soft- G  ware Library for OpenVMS Alpha Layered Products, part number QA-03XAA-   H8.    ORDERING INFORMATION     Software Licenses: QL-3L4A*-** )  Software Documentation: QA-3L4AA-GZ.2.0C '  Software Product Services: QT-3L4A*-**   G  *  Denotes variant fields. For additional information on available li- E     censes, services, and media, refer to the appropriate price book.               #                                   4          SOFTWARE LICENSING   D  This software is furnished under the licensing provisions of CompaqF  Computer Corporation's Standard Terms and Conditions. For more infor-E  mation about COMPAQ's licensing terms and policies, contact your lo-   cal COMPAQ office.   $  License Management Facility Support  D  This layered product supports the OpenVMS License Management Facil-  ity.   D  License units for this product are allocated on an Unlimited System  Use basis.   F  For more information on the License Management Facility, refer to the7  OpenVMS Operating System Software Product Description.     SOFTWARE PRODUCT SERVICES  E  A variety of service options are available from COMPAQ. For more in- -  formation, contact your local COMPAQ office.     SOFTWARE WARRANTY  G  Warranty for this software product is provided by COMPAQ with the pur- G  chase of a license for the product as defined in the Software Warranty   Addendum of this SPD.  9  [R] OSI is a registered trademark of CA Management, Inc.   6  [TM] X/Open is a trademark of the X/Open Company Ltd.  =  [TM] The COMPAQ Logo, AXP, CI, DECnet, DIGITAL, MAILbus 400, C      OpenVMS, OSAK and VMScluster are trademarks of COMPAQ Computer       Corporation.         #                                   5        E  Compaq Computer Corporation makes no representations that the use of F  its products in the manner described in this publication will not in-D  fringe on existing or future patent rights, nor do the descriptionsF  contained in this publication imply the granting of licenses to make,G  use, or sell equipment or software in accordance with the description.   E  Possession, use, or copying of the software described in this publi- H  cation is authorized only pursuant to a valid written license from COM-"  PAQ or an authorized sublicensor.  C   Compaq Computer Corporation 1995,1998,1999. All rights reserved.                                                           #                                   6 