HomeAbout Us A-Z IndexSearch  Inquiries RegisterLoginPress Shop
Conformance Statement

Product Standard: Message Access

This form contains a series of questions that need to be answered. As you go about answering the questions, please keep the following things in mind:

Enter the name of the Organization that produced the implementation and the name of the author of the Conformance Statement.

Organization
Author


1. Message Access

Product Information

Enter the product name, version/release number, and product supplier for each product required to meet the conformance requirements.

Product IdentificationVersion/Release NumberProduct Supplier
 
 
 
 
 

Environment Specification

Product registration applies to software products operating in a specific hardware or hardware/software environment.

A product may be registered in all members of a binary-compatible family of products on the basis of a single test report.

Answer the questions for each binary-compatible family. Alternately, provide the answers in the Appendix at the end of this document.

Testing Environment Binary-compatible Family Portability Environment Indicator of Compliance Compliance Details
None. None.
None. None.
None. None.
None. None.
None. None.

Temporary Waivers

Enter the waiver number and expiry date for each temporary waiver granted by The Open Group.

Waiver NumberExpiry Date


1.1 X.400 Message Access Interface Options

1.1.1 X.400 Message Access Interface Roles

Question 1: Which of the following roles are supported?

Response

Rationale

Reference


1.1.2 Message Access Interface Optional Functional Units

Question 2: If the MA interface is supported in the service role which of the following optional Functional Units (FU) are supported?

Response

Rationale

Reference


Question 3: If the Delivery functional unit is supported, is Multiple-Delivery supported?

Response


Question 4: What is the maximum number of MA sessions that can exist simultaneously?

Response

Rationale

Reference


Question 5: How many sessions does the Wait() function notify of an object's arrival when several sessions provide access to the queue?

Response


Question 6: What is the criteria for the session(s) to be selected to receive the signal from the Wait() function?

Response


Question 7: What is the criteria for an object to be selected for delivery when there is more than one object available in the queue?

Response


Question 8: What is the maximum number of users that can be associated with a Client Name?

Response

Rationale

Reference


1.1.3 Default Features Supplied by Open()

Question 9: Which of the features associated with the MA interface are supplied as default by a call to ma_open()?

Response

Rationale

Reference


1.1.4 MA Protocol Realisations

Question 10: If the MA interface is supported in the service role which of the following alternate realisations is used?

Response

Reference


1.2 Message Handling Packages

1.2.1 MH Package Implementation

Question 11: If the MA interface is supported in the service role which of the following packages are implemented?

Response

Rationale

Reference


1.2.2 MH88 Classes

Question 12: If the MH88 package is supported then which, if any, of the following classes are supported?

Response

Rationale

Reference


1.2.3 Encode Option

Question 13: If the MH84 package is supported then for which classes is Encode() provided (in addition to OR Address)?

Response

Rationale

Reference


Question 14: If the MH88 package is supported then for which classes is Encode() provided (in addition to OR Address and OR Name)?

Response

Rationale

Reference


1.3 Interpersonal Messaging Packages

1.3.1 IM Package Implementation

Question 15: If the MA interface is supported in the service role how are the following packages implemented?

Response

Rationale

Reference


1.3.2 IM Classes

Question 16: If the IM84 or IM88 Package is supported then which, if any, of the following immediate subclasses of Body Part class are implemented?

Response

Rationale

Reference


1.3.3 Encode Option

Question 17: If the IM84 package is supported then for which classes is Encode() provided?

Response

Rationale

Reference


Question 18: If the IM88 package is supported then for which classes is Encode() provided?

Response

Rationale

Reference


1.4 Other Packages

1.4.1 Package Implementations

Question 19: Is the SM88 package supported?

Response

Rationale

Reference


2. OSI-Abstract-Data Manipulation (XOM)

2.1 Character Sets

Question 1: Is the service performing conversion to a local character set?

Response


Question 2: Does the conversion of information to and from the local character set result in the loss of information?

Response

Rationale

Reference


Question 3: What is the local character set representation, and what are the precise mappings between it and the various string syntaxes?

Response


Question 4: What are the precise definitions in C of the intermediate data types?

Response


Question 5: What is the length of the longest string that the Get() function will return?

Response


Question 6: Does the service report an exception if an object supplied to it as an argument is not minimally consistent?

Response

Rationale

Reference


2.2 Intermediate Data Types

Question 7: What are the precise C definitions for the following intermediate data types?

Response

Rationale

Reference


2.3 XOM Options

2.3.1 Maximum String Attribute Length

Question 8: What is the maximum string length for an attribute value before the elements of the string are omitted by the Get() function?

Response

Rationale

Reference


2.3.2 Error if Object not Minimally Consistent

Question 9: In operational versions of the XDS library, if an object supplied to the service is not minimally consistent is an error reported?

Response

Rationale

Reference


Question 10: In debug versions of the XDS library, if an object supplied to the service is not minimally consistent is an error reported?

Response

Rationale

Reference


3. Appendix

This appendix contains additional, explanatory material that was provided by the vendor.


Copyright © 
All rights reserved.


4. Change History

DateNameComment
New

 Copyright © 1998-2002 The Open Group. All Rights Reserved.

 OSF/1, Motif, UNIX, and the "X" device are registered trademarks in the U.S. and other countries, and IT DialTone and The Open Group are trademarks of The Open Group.


[ Home ] [ Testing Home ] [ Conformance Statement Library Home ] [ Search Conformance Statements ] [ Send Feedback ]