Software Product Description ___________________________________________________________________ PRODUCT NAME: Compaq OMNI MMS SPD 47.89.07 Version 3.1 DESCRIPTION Compaq OMNI MMS is a network communication product that provides a so- lution for the connection and management of manufacturing/utility con- trol devices and systems. Compaq OMNI MMS implements the Manufactur- ing Message Specification (MMS), ISO/IEC 9506-1 and ISO/IEC 9506-2. When combined with prerequisite hardware and software, Compaq OMNI MMS interoperates with other systems supporting the Manufacturing Message Specification ISO/IEC9506-1 and ISO/IEC 9506-2 specifications. Features Compaq OMNI MMS is an implementation of the Manufacturing Message Spec- ification (MMS), ISO/IEC 9506. It relies upon the Compaq OMNI API prod- uct that provides a high level applications programming interface (API) with a high degree of functionality built in. The interface is easy to use and requires very little support code. For more information, please refer to the Compaq OMNI API Software Product Description (SPD 47.88.xx). Alternatively, Compaq OMNI MMS can be integrated with the BASEstar Open Server product (SPD 47.87.xx) for connection to plant devices which use the MMS protocol. Compaq OMNI MMS provides, as a minimal set, the Client Conformance re- quirements for the services specified in MAP Implementation Class MAP3. The product is able to connect to those devices that have implemented to ISO/IEC 9506 (MMS). COMPAQ April 2000 CONFORMANCE TO STANDARDS The conformance of Compaq OMNI MMS software to OSI standards is spec- ified in Appendix A of this SPD. INSTALLATION Only experienced customers should install Compaq OMNI MMS software. Compaq recommends that all other customers purchase Compaq Installa- tion Services. These services provide for installation of the soft- ware product by an experienced Compaq software specialist. Installation steps for Compaq OMNI MMS consists of the following: o Verification that all components of Compaq OMNI MMS have been re- ceived o Verification that the necessary versions of the prerequisite soft- ware and documentation are available o Verification of the appropriate system parameters o Verification that the system meets the minimum hardware and soft- ware requirements as specified in this SPD o Installation of the Compaq OMNI MMS software by creating the nec- essary directories and by copying the software from the distribu- tion media o Verification that Compaq OMNI MMS has been installed correctly by using the IVP Compaq OMNI MMS Installation Verification Procedure (IVP) The Compaq OMNI MMS IVP performs a series of tests to verify proper installation. 2 HARDWARE REQUIREMENTS Alpha Processors Supported All Alpha processors supported by the Compaq OMNI API and BASEstar Open Server products. Disk Space Requirements (Block Cluster Size = 1): For_OpenVMS_Systems________________________________________________ During Instal- lation_____________Permanent_Use___________________________________ 20,000_blocks______10,000_blocks___________________________________ For_Tru64_Unix_Systems_____________________________________________ Component_____Installation__Permanent_Use__________________________ File 340 Kbytes 340 Kbytes System Root /usr/opt 7 Mbytes 6 Mbytes /usr/var 5 Mbytes 2 Kbytes /opt Total_________13_Mbytes_____9_Mbytes_______________________________ SUPPORTED PRODUCTS This SPD defines the following Compaq OMNI MMS products: o Compaq OMNI MMS for Tru64 Unix Version 3.1 o Compaq OMNI MMS for OpenVMS Alpha Version 3.1 3 SOFTWARE REQUIREMENTS YEAR 2000 READY YEAR 2000 READY This product is Year 2000 Ready. Year 2000 Ready is defined: "Year 2000 Ready" products are defined by Compaq as products capable of accurately processing, providing, and/or receiving date data from, into and between the twentieth and the twenty-first centuries, and the years 1999 and 2000, including leap year calculations, when used in accordance with the associated product documentation and pro- vided that all hardware, firmware and software used in combination with such products properly exchange accurate date data with the products. For OpenVMS Systems: o Either: - OpenVMS Alpha Operating System V6.1, V6.2, V7.0, V7.1,V7.2 or - OpenVMS VAX Operating System V6.1, V6.2, V7.0, V7.1, V7.2 o Compaq DECnet/OSI for OpenVMS V6.3 to V7.1, V7.2 o Compaq OMNI API for OpenVMS Version 3.1 For Tru64 Unix Systems: o Tru64 Unix Operating System V3.2 or V4.0 o Compaq DECnet/OSI for Tru64 Unix V3.2 or V4.0 o Compaq OMNI API for Tru64 Unix Version 3.1 4 GROWTH CONSIDERATIONS The minimum hardware/software requirements for any future version of this product may be different from the requirements for the current version. DISTRIBUTION MEDIA This product is distributed with the Compaq CD-ROM software libraries for OpenVMS Alpha and for Tru64 Unix. ORDERING INFORMATION For OpenVMS Alpha systems: Software Licenses: QL-2QD**-** Documentation Kit: QA-2QDAA-GZ Software Product Services: QT-2QD**-** For OpenVMS VAX systems: Software Licenses: QL-4VAA*-** Documentation Kit: QA-2QDAA-GZ Software Product Services: QT-4VA**-** For Tru64 Unix systems: Software Licenses: QL-2YU**-** Documentation Kit: QA-2YUAA-GZ Software Product Services: QT-2YU**-** * Denotes variant fields. For additional information on available li- censes, services, and media, refer to the appropriate price book. The above information is valid at time of release. Please contact your local Compaq office for the most up-to-date information. 5 SOFTWARE LICENSING The Compaq OMNI MMS license gives the user the right to use the soft- ware on a single CPU and includes the delivery of a license product Authorization Key (PAK) to enable Compaq OMNI MMS software. This soft- ware is furnished under the licensing provisions of Compaq Equipment Corporation's Standard Terms and Conditions for software licenses. For more information about Compaq licensing terms and policies, contact your local Compaq office. License Management Facility Support This layered product supports the OpenVMS and Tru64 Unix License Man- agement Facility. For more information on the License Management Fa- cility, refer to the appropriate operating system SPD or documenta- tion. SOFTWARE PRODUCT SERVICES A variety of service options are available from Compaq. For more in- formation, contact your local Compaq office. SOFTWARE WARRANTY This software is provided by Compaq with a 90 day conformance warranty in accordance with the Compaq warranty terms applicable to the license purchase. Warranty Limitations Compaq has produced this product according to Protocol Specifications produced by the International Organization for Standardization (ISO) defined in Appendix A of this SPD. Compaq warrants this product to conform to these Protocol specifica- tions, as described by these International Standards. 6 Compaq cannot assume responsibility for problems caused by: o Other vendors' nonconformance to the International Standards that Compaq OMNI API implements o Ambiguities in the International Standards implemented by Compaq OMNI MMS o Flaws in the protocol design appearing in the International Stan- dards implemented by Compaq OMNI MMS Assistance requested of Compaq for problems resulting from any of the errors listed above will result in all associated service calls be- ing billed at the prevailing per call rates. To minimize the risk of problems, Compaq has tested this product against selected other ISO /IEC 9506-1 and ISO/IEC 9506-2 implementations. APPENDIX A: Conformance to Standards This appendix defines the conformance of Compaq OMNI MMS Compaq OMNI MMS product to International Organization for Standardization (ISO) international specifications for protocol standards as specified in ISO/IEC 9506-2 clause 18. ___________________________________________________________________ Table_1:_PICS_Part_1:_Implementation_Information___________________ Attribute______________________________Value_______________________ Implementation's Vendor Name Compaq Implementation's Model Name Compaq OMNI MMS Implementation's Revision Identi- V3.0 fier Machine Name(s) and Version Num- - ber(s) Operating System(s) OpenVMS, Tru64 Unix MMS Abstract Syntax [1 0 9506 2 1] 7 ___________________________________________________________________ Attribute______________________________Value_______________________ MMS Version Number Supported 1 MMS Companion Standard Abstract None Syntaxes MMS Companion Standard Version N/A Number Supported Calling MMS-user (indicate "Yes" or Yes "No") Called MMS-user (indicate "Yes" or Yes "No") List_of_Standardized_Names_____________None________________________ ___________________________________________________________________ Table_2:_PICS_Part_2:_Service_CBBs_________________________________ S(erver), C(lient), or Service_Conformance_Building_Blocks____B(oth)______________________ Initiate B Conclude B Cancel - UnsolicitedStatus B Status B GetNameList B Identify B Rename - GetCapabilityList B Read B Write B InformationReport B GetVariableAccessAttributes B DefineNamedVariable - DefineScatteredAccess - 8 ___________________________________________________________________ S(erver), C(lient), or Service_Conformance_Building_Blocks____B(oth)______________________ GetScatteredAccessAttributes - DeleteVariableAccess - DefineNamedVariableList B GetNamedVariableListAttributes B DeleteNamedVariableList B DefineNamedType - GetNamedTypeAttributes - DeleteNamedType - Input - Output - TakeControl - RelinquishControl - DefineSemaphore - DeleteSemaphore - ReportSemaphoreStatus - ReportPoolSemaphoreStatus - ReportSemaphoreEntryStatus - AttachToSemaphore - InitiateDownloadSequence C DownloadSegment S TerminateDownloadSequence S InitiateUploadSequence C UploadSegment C TerminateUploadSequence C RequestDomainDownload S RequestDomainUpload S LoadDomainContent B StoreDomainContent B DeleteDomain B GetDomainAttributes B CreateProgramInvocation B DeleteProgramInvocation B 9 ___________________________________________________________________ S(erver), C(lient), or Service_Conformance_Building_Blocks____B(oth)______________________ Start B Stop B Resume B Reset B Kill B GetProgramInvocationAttributes B ObtainFile B DefineEventCondition - DeleteEventCondition - GetEventConditionAttributes - ReportEventConditionStatus - AlterEventConditionMonitoring - TriggerEvent - DefineEventAction - DeleteEventAction - GetEventActionAttributes - ReportEventActionStatus - DefineEventEnrollment B (See Note 9) DeleteEventEnrollment B (See Note 9) AlterEventEnrollment - ReportEventEnrollmentStatus - GetEventEnrollmentAttributes B (See Note 9) AcknowledgeEventNotification - AttachToEventCondition - EventNotification B GetAlarmSummary - GetAlarmEnrollmentSummary - ReadJournal - WriteJournal - InitializeJournal - CreateJournal - DeleteJournal - 10 ___________________________________________________________________ S(erver), C(lient), or Service_Conformance_Building_Blocks____B(oth)______________________ ReportJournalStatus____________________-___________________________ ___________________________________________________________________ Table_3:_PICS_Part_3:_Parameter_CBB________________________________ Parameter Conformance Building Blocks_________________________________Supported_(Value)___________ STR1 Y STR2 Y NEST ( >=0 . Give integer value.) 10 VNAM Y VADR Y VALT Y VSCA N TPY N VLIS NY REAL N CEI____________________________________N___________________________ ___________________________________________________________________ Table_4:_Supplemental_PICS_Table___________________________________ S(erver), C(lient), or Service_Conformance_Building_Blocks____B(oth)______________________ FileOpen B FileRead B FileClose B FileRename B 11 ___________________________________________________________________ S(erver), C(lient), or Service_Conformance_Building_Blocks____B(oth)______________________ FileDelete B FileDirectory__________________________C___________________________ ___________________________________________________________________ Table_5:_PICS_Part_4:_Local_Implementation_Values__________________ Attribute______________________________Value_______________________ Range of values for floating point See Note 1 numbers Supported values of the floating See Note 1 point exponent width Supported values of the floating See Note 1 point format width Range of values for signed integer 12**32-1 Range of values for unsigned inte- 2**32 ger The following semantics are defined for the use of the local detail calling/called fields. As a result, a limit is set for a maximum MMS PDU size which limits specific functions. Maximum length for BIT STRING in See Note 2 bits Maximum length for OCTET STRING in See Note 2 octets Address formats for VADR Parameter N/A CBB Maximum Input Time Out in seconds N/A Level of support for time See Note 3 Granularity of time in milliseconds N/A 12 ___________________________________________________________________ Attribute______________________________Value_______________________ Uninterruptible access to variable See Note 4 Priority processing for semaphores N/A Capabilities of VMD N/A Local Detail N/A File Name Syntax See Note 5 Range of Maximum Services Outstand- See Note 6 ing Calling Range of Maximum Services Outstand- See Note 6 ing Called Execution Argument N/A Additional Code in Error Type See Note 7 Additional Detail in Error Type See Note 7 Method for Extended Derivation of N/A Status Information Local Detail Calling/Called See Note 8 Load Data Format N/A Maximum Number of Upload State N/A Machines___________________________________________________________ Note 1: VAX F floating point is supported. The range is 1.17545*10**-38 through 1.17545*10**38. An exponent width of 8 bits is supported. A format width of 32 bits is supported. Note 2: The effective length for strings is limited by the maximum PDU size. See Note 8. Note 3: Date and Time are supported. Support for Time Sequence Identifier is N/A. 13 Note 4: Read and Write indications are delivered to user written code and thus uninterruptible access is application dependent. Note 5: The syntax and semantics for file name are specified by the OpenVMS operating system. This is documented in the OpenVMS documentation un- der "Full File Specification". Wildcard specifiers are not permitted. The file name must be specified in the first graphic string of the File- Name production. Any information in additional graphic strings will be ignored. Note 6: The range is 1-infinity. Acceptance of indications is under program- ming control. The actual number of outstanding requests allowable is dependent upon process memory limits which is set by either the pro- grammer or system manager. Note 7: This implementation does not specify additional code nor additional detail in error type. Note 8: The following semantics are defined for the use of the local detail calling/called fields. As a result, a limit is set for a maximum MMS PDU size, which limits specific functions. The semantics of this field are contained in the implementation agree- ments of the NIST (National Institute for Standards and Technology - OSE Implementor's Workshop) Special Publication 500-214 titled Sta- ble Implementation Agreements for Open Systems Interconnection Pro- tocols, Version 7, Edition 1, December 1993, Part 20 (MMS) Sections 8.2.0.3 and 8.2.0.4. Note 9: 14 The optional parameter of Event Actions on an Event Enrollment is not supported. © 2000 Compaq Computer Corporation. ® Motif is a registered trademark of Open Software Foundation, Inc. [TM] The Compaq Logo, AXP CI, Compaq DECnet, Compaq OMNI, Com- paq OSAP, DECwindows, Compaq, MicroVAX, Rdb, OpenVMS, TK, VAX, VAXcluster, VAXft, VAXserver, VAXstation, and VMS are trademarks of Compaq Equipment Corporation. All other trademarks and registered trademarks are the property of their respective holders. Compaq shall not be liable for technical or editorial errors or omissions contained herein. The information in this document is subject to change without notice. 15