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

UNIX 98 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 98

A checklist of what is needed to register a UNIX 98 product

This checklist comprises the following parts:

  • UNIX 98 : a summary and further notes on the details with regard to the test results submitted;
  • Where to find the CSQs;
  • Brand requirements versus test suite tables for UNIX 98

UNIX 98 Summary of Registration Requirements

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

Product Standard registration application forms need to be completed and signed. A covering letter bringing together the contents of the application and any other relevant information such as purchase order number (if the purchase order is not enclosed) is also requested.

The UNIX 98 Product Standard is made up of the following constituent Product Standards:-

  • Internationalised System Calls & Libraries Extended V2
  • Commands & Utilities V3
  • C Language
  • Transport Service (XTI) V2
  • Sockets V2
  • Internationalised Terminal Interfaces
  • Software Administration (optional)

The constituent Product Standards need to be either registered in advance or all registered at the same time as the main Product Standard. They need to be presented with their individual Conformance Statements and indicator of compliance where necessary, please see details below.

In order to keep the amount of paper and processing time to a minimum we are only asking for the legal forms and those pages from the test reports which need signing and/or dating in hard copy.

A summary of what we need is:- (any essential extra detail is provided below under specific Product Standards)

  • In hard copy
    • TMLA + royalty agreement letter (if not already in place)
    • Forms and letters
      1. Covering letter
      2. Purchase order (or PO reference number with address for invoice)
      3. Application forms for the UNIX 98 Product Standard and for its constituent Product Standards.
      4. For each test suite VSX4, VSX5, VSU5, VSC5, VSTH5 (optionally VSRT5) and VST5 we need the first pages of vrpt [or creport for VSU5.0.4 or earlier] where signatures and dates are present.
        Note that VSX4, VSX5, VSU5, VSTH and (optionally) VSRT may be used together as a merged test suite under VSXgen, the first pages of vrpt output from the merged test suite are also acceptable as an alternative to the individual requirements for VSX4, VSX5, VSU5, VSTH5 and VSRT5.
      5. A NIST certificate for the ISO C part of C Language unless the Plum Hall or Perennial results are being submitted (see below)
  • Electronic files uploaded by ftp to your incoming directory in your ftp account or in the case of the Conformance Statements to the online WWW CSQ system.
    • CSQs (these are required to be entered online in the WWW CSQ system at http://www.opengroup.org/public/csq/)

      Completed Conformance Statements for:-

      1. UNIX 98
      2. XSH Extended V2
      3. C Language
      4. C&U V3
      5. XTI V2
      6. Sockets V2
      7. Internationalised Terminal Interfaces
      8. Software Administration (optional)
    • Test Reports
      1. Test results (vrpt output) from VSX4, VSX5, VSU5 [creport output if VSU5.0.4 or earlier], VST5, VSC5, VSTH5 and optionally VSRT5.
        Note that a single vrpt file for the merged suite (under VSXgen) comprising VSX4, VSX5, VSU5, VSTH5 and optionally VSRT5 is an acceptable alternative to separate files for each test suite.
      2. Journal files from VSU5, VSC5, VSTH5, VSX4, VSX5 , VST5 and optionally VSRT5
        Note that a single journal file for the merged suite (under VSXgen) comprising VSX4, VSX5, VSU5, VSTH5 and optionally VSRT5 is an acceptable alternative to separate files for each test suite.
      3. Bldfillst output from VSC and VSU [only for VSU5.0.4 and earlier]
      4. For each test suite, we need 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 is fine.
      5. Test results for ISO-C (Perennial or Plum Hall) unless a NIST certificate is presented in hard copy

Further detailed notes on the above set out by Component:-

(For test results, please refer to general requirements for uploading electronic files above, only extra specific files/outputs are inserted below under the particular Product Standard)

Internationalised System Calls & Libraries Extended V2

  • Either:

    The VSX4 test results from a single run in UNIX 98 mode.

    The VSX5 test results from a single run in UNIX 98 mode

    The VSTH5 test results from a single run in UNIX 98 mode.

    (OPTIONALLY) The VSRT5 test results from a single run in UNIX 98 mode.

    The VSU5 test results from a single run in UNIX 98 mode
    For VSU5.0.4 [or earlier], the specific details of what we need are:-

            vsurpt -f JournalFile
            vsurptx -o organization -s system -f JournalFile
    

    Also, the output from the program, bldfillst. Bldfillst must be run with appropriate privelege (as root) from the CAPI directory.

  • OR:

    The test results from a single run in UNIX 98 mode of the merged test suite (under VSXgen) comprising valid releases of VSX4, VSX5, VSU5, VSTH5, and optionally VSRT5.

C Language

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

  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.

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.

OR a NIST certificate. For Perennial & Plum Hall please submit the results by ftp or email the files to the Conformance Administrator. For UNIX conformance the ISO C compiler is required to be the c89 utility.

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

Commands & Utilities V3

A completed Conformance Statement Questionnaire for Commands and Utilities Version 3.

Test results from VSC5 in a single run in UNIX 98 mode.

For VSC5, the output from the program, bldfillst. Bldfillst must be run with appropriate privelege (as root) from the vsc directory (ie VSC5.0.1/vsc).

A uuencoded copy of the "vrpt -L54 JournalFile" output. and "vrpt -L54 -lsect JournalFile"

A uuencoded tar archive containing all files in the ImplSpec directory.

Transport Interface (XTI) V2

Test results from a single run of VST5 in UNIX 98 mode.

Please note if more than one tested protocol stack is supported then we need test reports from each protocol stack.

Sockets V2

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

Please note that test results from a single run in UNIX 98 mode of the merged test suite (under VSXgen) comprising valid releases of VSX4, VSX5, VSU5, VSTH5, and optionally VSRT5 is also valid.

Internationalised Terminal Interfaces

A completed Conformance Statement Questionnaire for Internationalised 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

Conformance Statements should be completed using the online system


UNIX 98 Brand Requirements versus Test Suites

PRODUCT STANDARD COMPONENTS MAKING UP THE MAIN PRODUCT STANDARD TEST SUITE
UNIX 98 Internationalised System Calls and Libraries Extended V2
(Including optional Real Time section)
VSX4, VSX5, VSU5, VSTH
(VSRT)
Commands and Utilities V3 VSC5
C Language VSX4 and either Plum Hall or Perennial or a NIST FIPS 160 certificate.
Transport Service (XTI) V2 VST5
Sockets V2 VSU5
Internationalised Terminal Interfaces VSU5 for 'hard'conformance
Software Systems Administration (Optional) None

 


Home · Contacts · Legal · Copyright · Members · News
© The Open Group 1995-2015