       %                                COMPAQ   	  Software   Product  Description  D  ___________________________________________________________________  D  Product Name:  MAILbus 400 Application Program Interface        SPD6  42.80.07                for OpenVMS VAX, Version 2.0C    PRODUCT DESCRIPTION  D  MAILbus 400[TM] Application Program Interface (API) for OpenVMS[TM]E  VAX[TM] is a layered software product that resides on an OpenVMS VAX G  system. It provides a programming interface that gives application de- G  velopment programmers access to the messaging services provided by the $  MAILbus 400 Message Transfer Agent.  I  MAILbus 400 API for OpenVMS provides a C language interface to the MAIL- G  bus 400 MTA's messaging services. An ANSI C conformant compiler is re- #  quired to use the 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 VAX 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-PVRRH-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- D  culations, when used in accordance with the associated COMPAQ Prod-E  uct documentation and provided that all hardware, firmware and soft- E  ware used in combination with such COMPAQ Products properly exchange $  date data with the COMPAQ Products.    HARDWARE REQUIREMENTS    Processors Supported   +  Any OpenVMS VAX configuration supported by D  DECnet[TM]-Plus for OpenVMS VAX, with the exception of those listedE  below. See the DECnet-Plus for OpenVMS VAX Software Product Descrip- E  tion (25.03.*) for further information on supported hardware config- 
  urations.    Processors Not Supported   E  MicroVAX[TM] I, VAXstation[TM] I, VAX-11/725, VAX-11/782, VAXstation   8000   #                                   2        2  Disk Space Requirements (Block Cluster Size = 1):  '  Disk space required for    3500 blocks   installation:  '  Disk space required for    3100 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 VAX Operating System V6.2 ,     DECnet/OSI[R] for OpenVMS V6.3 with ECO8  %  o  OpenVMS VAX 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 VAX 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[TM] C for OpenVMS V4.0 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   D  For more information on OpenVMS classes and tailoring, refer to theJ  OpenVMS VAX Operating System Software Product Description (SPD 25.01.xx).    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   D  MAILbus 400 MTA is also available as part of the DIGITAL[TM] CD-ROMI  Software Library for OpenVMS VAX Layered Products, part number QA-VWJ8A-   H8.    ORDERING INFORMATION     Software Licenses: QL-04RA*-** )  Software Documentation: QA-04RAA-GZ.2.0C '  Software Product Services: QT-04RA*-**   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.              #                                   5          =  [TM] The COMPAQ Logo, CI, DEC, DECnet, DIGITAL, MAILbus 400, C      MicroVAX, OpenVMS, VAX, VMScluster, and VAXstation, are trade- *      marks of Compaq Computer Corporation.  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 1993,1998,1999. All rights reserved.                                                 #                                   6 