Home · About · A-Z Index · Search · Contacts · Press · Register · Login

UNIX 95 Testing Checklist



Testing Links

Data Sheets
Embedded Systems
POSIX® Systems
Realtime Systems
UNIX® Systems
The Open Brand

You are here: Testing > Branding > Product Registration Checklists > UNIX 95

Checklist of requirements for registering a UNIX 95 product

This checklist comprises the following parts:

  • UNIX 95 Summary of the Registration Requirements (including specifics on the test results to be submitted).
  • Conformance Statement Questionnaires (CSQs) and CSQ system 
  • Brand requirements and the relevant test suites for UNIX 95

UNIX 95 Summary of Registration Requirements

A Trademark License Agreement (TMLA) needs to be in place or must accompany the submission together with a letter detailing the royalty agreement with The Open Group.

Product Standard Registration forms should be completed and signed.  A covering letter is required confirming the contents of the application/submission and any other relevant information such as purchase order number (if the purchase order is not enclosed).

The UNIX 95 Product Standard (the Profile) is made up of the following constituent Product Standards:-

  • Internationalized System Calls & Libraries Extended
  • Commands & Utilities V2
  • C Language
  • Transport Service (XTI)
  • Sockets
  • Internationalized Terminal Interfaces

The constituent Product Standards can be registered separately, in advance, or all may be registered at the same time as the Profile Product Standard (UNIX 95). They need to be presented together with their individual Conformance Statements and indicators of compliance (test results).  More information is provided below.

To keep the amount of paper and processing time to a minimum, we only require hardcopy submission of the legal forms :

- Product Standard Registration forms,  signed by an authorized signatory
- TMLA (if not already submitted), signed by an authorized signatory
- those pages from the Test Reports which require signing and/or dating

The rest of the submission is made electronically.

Your submission should include: 

In hardcopy form:

  • TMLA and royalty agreement letter (if the TMLA is not already in place)
  • Forms and letters, as follows:
  1. Cover Letter confirming which Product Standard(s) you are registering for, the content of your submission (signed Registrations forms, TMLA), and purchase order information including the PO number and address for invoice if the PO is not attached to the Cover Letter.
  2. Purchase order
  3. UNIX 95 Product Standard Registration form
  4. 'Other UNIX Constituent Product Standards' Registration form
  5. The first pages of the vrpt where signatures and dates are present from each test suite (VSX4, VSU5, VSC5, VST5)
  6. A NIST certificate for the ISO C part of C Language, unless the Plum Hall or Perennial test results are being submitted (see below).
Electronic files:
  • Test results are uploaded by ftp to your Incoming directory in your FTP on The Open Group server.
  • Conformance Statements are submitted online through the Conformance Statement system http://www.opengroup.org/csq/

Conformance Statements should be completed and submitted for:
  1. UNIX 95
  2. Internationalized System Calls & Libraries Extended
  3. C Language
  4. Commands & Utilities V2
  5. Transport Service (XTI)
  6. Sockets
  7. Internationalized Terminal Interfaces

Test Reports should be completed and uploaded as follows:
  1. Test results (vrpt output) from VSX4, VSU5, VST5, VSC5
  2. Journal files from VSX4, VSU5, VSC5, VST5
  3. Bldfillst output from VSC
  4. For each test suite, a list of any FAIL, UNRESOLVED, UNREPORTED or UNINITIATED results set out in table form with their associated granted interpretations (TSD, PIN, etc).  Plain-text format is acceptable.
  5. Test results for ISO-C (Plum Hall or Perennial) unless a NIST certificate is presented in hardcopy.


Following is additional information related to submission requirements of test results for the component/constituent product standards.  This information is in addition to the Test Report requirements above; only extra and specific files/outputs are inserted below under the constituent Product Standard.

Internationalized System Calls & Libraries Extended

  1. The VSX4 test results from a single run in UNIX 95 mode.
  2. The VSU5 test results from a single run in UNIX 95 mode.

C Language

A NIST certificate for the ISO C part of C Language, OR

For ISO-C:  The requested output files from a valid release of either the Perennial or Plum Hall test suites.

Perennial ACVS Test Suite

  1. Copy of the "Failures" report generated by RUN_ALL.
  2. Copy of the "testlist" file used for the test run.
  3. Copy of the "err.log" file that was generated by the ACVS Driver program. This file will be located in the Results directory. It contains all of the messages generated by the implementations that were sent to "stdout" and/or "stderr".
  4. Copy of the Pxxxxx.log, and Pxxxxx.ex files for any "P" tests that failed in execution.
  5. Copy of the completed questionnaire on implementation defined features. An online, plain text copy is located in the "DOC" directory. The file name is "impdef.txt".

Plum Hall Test Suite

  1. A copy of the controlling script used to harness the suite (could be a makefile or shell script, batchfile etc.), and the copy of envsuite used to 'source' the suite's environment.
  2. The header files defs.h, compil.h, machin.h, gotdiag.h, flags.h.
  3. Compiler logs (eg. *.clg) and output files (eg. *.out) from the CONFORM directory, any linker logs (eg. *.llg) needed to show a diagnostic for mandatory error tests, and any other files produced needed to demonstrate compliance.
  4. Overview of results produced by summary -f fulltest.exp
  5. Completed questionnaire on Implementation defined features.

Plain text files should be provided with the output reports stored as individual files and a document explaining how to extract the data and process the contents should also be supplied.

- For Perennial or Plum Hall please submit the test results by ftp.
- For UNIX conformance the ISO C compiler is required to be the c89 utility.

For X/Open C:  The C language tests from VSX4 are covered by the complete test report for Internationalized System Calls & Libraries above.

Commands & Utilities V2

  1. Test results from VSC5 in a single run in XPG4 mode.
  2. for VSC5, the output from the program, bldfillst.  Bldfillst must be run with appropriate privilege (as root) from the vsc directory (VSC5.0.1/vsc)
  3. A uuencoded copy o fthe "vrpt -L54 JournalFile" output and "vrpt -L54 -lsect JournalFile"
  4. A uuencoded tar archive containing all files in the ImpleSpec directory.

Transport Interface (XTI)

  1. Test results from a single run of VST5 in XPG4 mode.

Note:  If more than one tested protocol stack is supported, we need test reports from each protocol stack.


Sockets

  1. Test results from a single run of VSU5 in UNIX 95 mode.


Internationalized Terminal Interfaces

There are two options:

- For 'hard' conformance, the indicator of compliance is VSU5.
- For 'soft' conformance, there is no indicator of compliance and the CSQ should be completed accordingly.



Conformance Statement Questionnaires

The following Conformance Statements should be completed and submitted using the online system:

  1. UNIX 95
  2. Internationalized System Calls & Libraries Extended
  3. C Language
  4. Commands & Utilities V2
  5. Transport Service (XTI)
  6. Sockets
  7. Internationalized Terminal Interfaces

UNIX 95 Brand Requirements and Relevant Test Suites

PRODUCT STANDARD COMPONENT PRODUCT STANDARDS MAKING UP THE MAIN PRODUCT STANDARD TEST SUITE
UNIX 95 Internationalized System Calls and Libraries Extended VSX4VSU5,
Commands and Utilities V2 VSC5
C Language VSX4 and either Plum Hall or Perennial or a NIST FIPS 160 certificate.
Transport Service (XTI) VST5
Sockets VSU5
Internationalized Terminal Interfaces VSU5 for 'hard'conformance

 


Home · Contacts · Legal · Copyright · Members · News
© The Open Group 1995-2012  Updated on Wednesday, 31 October 2007