Operating System and Languages:
COE Platform Government-Supplied Kernel Source
Copyright © 2003 The Open Group

Product Standard
Operating System and Languages:
COE Platform Government-Supplied Kernel Source
Document Number: X02CQ

©May 2003, The Open Group All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, without the prior permission of the copyright owners.

COE Platform Government-Supplied Kernel Source - Product Standard

Product Standard

NAME

COE Platform Government-Supplied Kernel Source

LABEL FOR LOGO

No label.

DESCRIPTION

The COE Platform Government-Supplied Kernel Source (GSKS) Product Standard describes a common set of functionality that includes:

The availability of COE Platform implementations providing this functionality assures that the Human-Computer Interfaces are functionally identical across multiple applications platforms. This reduces training costs and potential operator error.

CONFORMANCE REQUIREMENTS

Conformance includes the ability of the COE Platform implementation to build the GSKS code from source with no unauthorized modifications. The following requirements apply to authorized modifications:

A COE Platform implementation shall be in conformance with the following.

Human-Computer Interface

  1. User Interface

  2. Print Services

    A COE Platform implementation shall demonstrate the ability to print ASCII text and postscript graphics to both a locally attached printer and a printer attached directly to the network. The following functions are demonstrated:

  3. System Management Services

    A COE Platform implementation shall support the COE Platform System Management Services providing the following functions:

  4. Accounts and Profile Manager (APM)

    The COE Platform Accounts and Profile Manager shall be provided on COE Platform implementations both on the Client and on the Master side. This software will:

  5. Segment Installer

    The COE Platform Segment Installer shall be provided on a COE Platform implementation. This is designed to install all COE segments (applications). It installs segments from disk, CD, tape, or the network on both local and remote machines.

  6. Runtime Tools

    The system administrator uses the Runtime Tools support to install, configure, and de-install systems. The tools also provide the developers with a means to communicate with the operator during segment installation. The following runtime tools shall be supported on a COE Platform implementation:

    COE_add_segment_features

    Adds one or more features to a segment installed on the system.

    COEAskUser
    Displays a message to the user, and has the user click on a button (Yes/No, True/False, Accept/Cancel, and so on) in response to the message.

    COE_feature_enabled

    Determines whether a specified segment feature is currently enabled in the user's current login session.

    COEFindSeg
    Returns information about a requested segment. The tool sets status and writes the pathname, segment name, segment prefix, and segment type information to stdout.

    COEGetProcessGroup

    Returns the current setting of a process group.

    COE_get_features

    Returns the list of features assigned to a profile.

    COEInstaller
    Displays a list of variants or segments that may be installed from tape, disk, or other electronic media. It is normally executed by an operator who selects it from a System Administrator menu to install or de-install segments.

    COEInstError
    Displays an error message to the user from within a Pre-Install, Post-Install, or De-Install script signalling installation termination or de-installation of the segment.

    COEListSegments

    Displays a list of segments that are installed on the system.

    COEListSegs
    Reads and outputs information on installed segments from a computer.

    COEMsg
    Displays a message to the user and has the user click on the "OK" button to continue. The tool may be used by the Pre-Install, Post-Install, and De-Install scripts.

    COEPrompt
    Displays a message to the user and has the user enter a response to the message. The tool may be used by the Pre-Install, Post-Install, and De-Install scripts.

    COEPromptPasswd

    Prompts the user to enter a password. The tool may be used by the Pre-Install, Post-Install, and De-Install scripts.

    COERegisterInterfaceEngine

    Prompts the user to enter a password.

    COESetProcessGroup

    Changes the current setting of a process group.

    COESegInstall
    Allows users to install a segment that already exists on disk without asking the user for input during installation. The COESegInstall API is essentially a stand-alone binary that can be executed from the command line, from a shell script, or from within an executable program. The program was developed to allow users to install a segment that already exists on disk without asking the user for input during installation. The API call was implemented as a binary to allow programmers to use the function in any type of program (for example, shell script, binary executable, or stand-alone tool) rather than tying it specifically to a limited set of C or X Window System library calls.

    COEUpdateHome

    Updates the HOME environment variable within a script file to point to where a segment was actually installed.

  7. Developer Tools

    COE Developer Tools support application software development and delivery, but are not delivered to operational sites. All interfaces to these tools are at the command line; none of them have a GUI interface. The following developer tools shall be supported on a COE Platform implementation:

    CalcSpace
    Computes the space required for the segment specified and updates the hardware descriptor accordingly. The segment referred to must not be compressed and must not contain any files that do not belong with the segment (for example, source code) at runtime. The amount of space required is written to stdout in K bytes.

    CanInstall
    Tests a segment to see whether it can be installed, which means that all required segments must already be on the disk, and the disk cannot have any conflicting segments.

    ConvertSeg
    Examines segment descriptors and converts them to the latest format. The original segment descriptor directory is not modified. The output is in a directory created by the tool and called SegDescrip.NEW. This directory will be located directly underneath the segment's home directory at the same level as SegDescrip. ConvertSeg is not location-sensitive and may be moved to any directory desired for development.

    MakeAttribs
    Creates the descriptor file FileAttribs. It recursively traverses every subdirectory beneath the segment home directory and creates a file containing permits, owner, group, and filename information.

    MakeInstall
    Writes one or more segments to an installation medium, or packages the segments for distribution over the SIPRNET. MakeInstall checks to see whether VerifySeg has been run successfully on each of the segments, and aborts with an error if it has not.

    TestInstall
    Temporarily installs a segment that already resides on disk. There must be no other COE process running when TestInstall is run. The reason for this restriction is that the tool may modify COE files already in use with unpredictable results.

    TestRemove
    Removes a segment that was installed by TestInstall. There must be no other COE process running when TestRemove is run. The reason for this restriction is that the tool may modify COE files already in use with unpredictable results.

    TimeStamp
    Puts the current time and date into the VERSION descriptor.

    VerifySeg
    Validates that a segment conforms to the rules for defining a segment. It uses information in the SegDescrip subdirectory and must be run whenever the segment is modified.

  8. Audit Log File Manager

    The COE Audit Log File Manager shall be available on a COE Platform implementation. It exercises the following functions:

Portability Interface

  1. Application Program Interface

    A COE Platform implementation shall demonstrate conformance for the following APIs as described in the COE Programmer's Guide and Reference Manual (PGRM) for Kernel:1

  2. The system shall include the COE-provided standard Java runtime tools, class libraries, or jar files.

Programming Language Environment

Not applicable.

Interoperability

Not applicable.

OPERATIONAL ENVIRONMENT

Not applicable.

PORTABILITY ENVIRONMENT
Java Support

A conforming system provides a set of services that permit the execution of pre-compiled applications that use the Java Runtime Environment (JRE) 1.2 or later.

OVERRIDING STANDARDS

Not applicable.

INDICATORS OF COMPLIANCE

The following are the required Indicators of Compliance:

MIGRATION

Not applicable.

Footnotes

1.
COE Programmer's Guide and Reference Manual (PGRM) for Kernel, Version 4.2.0.0, 4 February 2000, CM 30593.

Boundaryless Information Flow is a trademark and UNIX and The Open Group are registered trademarks of The Open Group in the United States and other countries. All other trademarks are the property of their respective owners.

Any comments relating to the material contained in this document may be submitted to The Open Group at:

The Open Group
Apex Plaza
Forbury Road
Reading
Berkshire, RG1 1AX
United Kingdom
or by electronic mail to:
OGSpecs@opengroup.org