HomeAbout Us A-Z IndexSearchInquiries RegisterLoginPress Shop
Conformance Statement

Product Standard: ISAM

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. ISAM

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
Test Suite:
Test Report:
Test Suite:
Test Report:
Test Suite:
Test Report:
Test Suite:
Test Report:
Test Suite:
Test Report:

Temporary Waivers

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

Waiver NumberExpiry Date


1.1 Implementation Limits

Question 1: What limits does the implementation impose for the following aspects?

Response

Rationale

Reference


1.2 Variable-length Records

Question 2: Does the implementation support files having records of variable length?

Response

Rationale

Reference


Question 3: Does a variable-length record retain the same number after it is rewritten with a different length?

Response

Rationale

Reference


Question 4: If the implementation does not support files with variable-length records does the setting of the ISVARLEN flag for isbuild(\|) and isopen(\|) generate an error?

Response

Rationale

Reference


1.3 Locking

Question 5: Does an unsuccessful ISAM function call release a lock established by automatic record locking?

Response

Rationale

Reference


Question 6: Do the file locking operations islock(\|) and isunlock(\|) have effect when the file is opened in automatic locking mode?

Response

Rationale

Reference


Question 7: Do record locks conflict when obtained by different processes using the same file descriptor?

Response

Rationale

Reference


Question 8: Do record locks conflict when obtained by the same process through different file descriptors?

Response

Rationale

Reference


1.4 Threading

Question 9: Is your ISAM implementation thread safe?

Response

Rationale

Reference


2. Appendix

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


Copyright © 
All rights reserved.


3. 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 ]