HomeAbout Us A-Z IndexSearchInquiries RegisterLoginPress Shop
Conformance Statement

Product Standard: Software Administration

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. Software Administration

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 General Compliance Category

Question 1: Is the implementation a "Conforming POSIX.7.2 Implementation" or a "Limited Conformance POSIX.7.2 Implementation"?

Response

Rationale

Reference


1.2 Non-standard Extensions

Question 2: If the implementation provides non-standard extensions, do those extensions conform to Clause 2.10.2 of the POSIX.2 standard?

Response

Rationale

Reference


Question 3: If the implementation provides non-standard extensions, what general operating instructions are required to enable a "Strictly Conforming POSIX.7.2 Distribution" to be operated upon and yield the behaviour specified in IEEE Std. 1387.2:1995?

Response

Rationale

Reference


1.3 Reliance on Other than POSIX.1 or POSIX.2 Functionality

Question 4: If the implementation meets all the criteria of a Conforming POSIX.7.2 Implementation (or of a Limited Conformance POSIX.7.2 Implementation) except with respect to those features of the standard that depend on the existence of conforming implementations of either POSIX-1 or POSIX-2, what are the details of any differences in functional behaviour?

Response

Rationale

Reference


1.4 Media Types Supported

Question 5: What media types are supported for the transmission and receipt of software distributions?

Response

Rationale

Reference


1.5 Communication and Interoperability

Question 6: If the implementation is a "Conforming POSIX.7.2 Implementation", by what protocol stacks does it communicate with other systems as part of a distributed software administration system?

Response

Rationale

Reference


Question 7: If the implementation is a "Conforming POSIX.7.2 Implementation", with what systems (platforms and operating systems) has interoperability for the purposes of processing software distributions as defined in IEEE Std. 1387.2:1995 been tested?

Response

Rationale

Reference


1.6 Other Applicable Standards

Question 8: What software standards, and applicable characteristics of those standards, does the implementation use that are approved by ISO/IEC, by any ISO/IEC member body, or by government bodies?

Response

Rationale

Reference


1.7 Implementation-defined Features

Question 9: What are the details of the implementation's standard features that are provided in an implementation-defined manner?

Response

Rationale

Reference


1.8 Control Scripts

Question 10: When a command is run in preview mode, does the implementation run the control scripts associated with the selection and analysis phases of the command being previewed?

Response

Rationale

Reference


Question 11: Does the implementation ensure that each software_collection_spec contained in the value of the targets option is the same between invocations of commands?

Response

Rationale

Reference


1.9 Support for Serial-format Target Distributions

Question 12: Does the implementation support target distributions in the serial format for swverify, swremove and swmodify?

Response

Rationale

Reference


1.10 Version Identifiers

Question 13: What additional Version Identifiers are supported in software specifications?

Response

Rationale

Reference


1.11 Event Definitions for Access and Concurrency Control Errors

Question 14: What event definitions does the implementation support in the event of access and concurrency control errors?

Response

Rationale

Reference


1.12 Environment Variable - LC_TIME

Question 15: Do the implementation's utilities use the LC_TIME variable when displaying dates and times in stdout, stderr and logging?

Response

Rationale

Reference


1.13 Script Return Codes

Question 16: Does the implementation provide additional script return codes and, if so, what is the behaviour of those codes?

Response

Rationale

Reference


1.14 Failure Events

Question 17: Which of the optional failure events does the implementation generate?

Response

Rationale

Reference


1.15 Archive Formats Supported for Serial Distributions

Question 18: What archive formats are supported for serial distributions?

Response

Rationale

Reference


1.16 Cross-reference Table

Section 1.3.1.3 (Documentation) of IEEE Std. 1387.2:1995 requires this Conformance Statement to follow the same structure as the standard itself, with the information presented in the appropriately numbered sections. This requirement is satisfied by the following table which provides, in sequence, a list of the individual sections of IEEE Std. 1387.2:1995 that give rise to conformance questions and, against each, a cross reference to the actual conformance questions above.

SectionTitleQuestion
1.3.1.1Conforming POSIX.7.2 Implementation1, 2, 3, 4
1.3.1.2Limited Conformance POSIX.7.2 Implementation1
1.3.1.3Documentation4, 8
2.3.1Features Inherited From POSIX.14
2.3.2Features Inherited From POSIX.24
3Software Structures9
3.2Distribution10
3.5Vendor10
3.5.1Vendor Attribute10
3.7.1Product Attributes10
3.8.1Bundle Attributes10
3.9.1Fileset Attributes9
3.11.1Software_File Common Attribute9
4.1.3Options11
4.1.3.1Non-interactive Operation9
4.1.4.1Software Specification and Logic14
4.1.4.2Source and Target Specification and Logic9, 13
4.1.5.1Defaults and Options Files9
4.1.5.2Extended Options9
4.1.5.6Access and Concurrency Control15
4.1.5.7Environment Variables16
4.1.6.1Control Script Execution and Environment12
4.1.6.1.2Control Script Return Codes17
4.1.6.5Logging9
4.1.7.1Selection Phase9
4.1.7.1.1Starting a Session9, 18
4.1.7.1.2Specifying Targets9, 18
4.1.7.2Analysis Phase18
4.1.7.3Execution Phase18
4.1.7.3.1Fileset State Transitions9
4.1.9Consequences of Errors9
4.2.7.2Execution Phase (swask)9
4.3.7.3.2Executing configure Scripts (swconfig)9
4.4.4Operands (swcopy)9
4.4.7.2Analysis Phase (swcopy)9
4.4.7.3Execution Phase (swcopy)19
4.4.7.3.1File Loading (swcopy)9
4.5.7.1Selection Phase (swinstall)9
4.5.7.2Analysis Phase (swinstall)9
4.5.7.3Execution Phase (swinstall)9
4.5.7.3.2Preinstall Scripts (swinstall)9
4.5.7.3.3File Loading (swinstall)9
4.5.7.3.4Compression (swinstall)9
4.5.7.3.5Postinstall Scripts (swinstall)9
4.5.7.3.6Kernel Scripts (swinstall)9
4.5.7.3.7Rebooting the System (swinstall)9
4.5.7.3.8Recovery (swinstall)9
4.6.4Operands (swlist)9
4.7.4Operands (swmodify)13
4.8.4Operands (swpackage)9
4.8.7.3Execution Phase (swpackage)19
4.9.4Operands (swremove)13
4.9.7.1Selection Phase (swremove)9
4.9.7.2Analysis Phase (swremove)9
4.9.7.3.1Executing preremove Scripts (swremove)9
4.9.7.3.3Executing postremove Scripts (swremove)9
4.10.4Operands (swverify)13


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 ]