⟦91a1ca766⟧

TextFile

CEDIT

The CEDIT program is used to edit R1000 configurations.  These
configurations specify a group of microcode and software subsystems
which may be loaded into the R1000 processor.  In addition a
configuration also specifies certain attributes of the systems
hardware.  Usually configurations are distributed with system
software releases and should not be edited.  The CEDIT program is
intended for use by Rational Support Personnel when debugging or
working around certain problems with new releases.  Changing the
contents of a configuration may make it difficult or impossible for
Rational to determine which versions of software comprise the running
system.

The Rational Environment is made up of several dozen subsystems.  Most of
these subsystems reside within the Environment's virtual memory system.
Ten of the subsystems are loaded from the DFS during system boot and
comprise the portions of the Environment which are required for the
virtual memory system to function and for the remainder of the sub-
systems to be located and elaborated.  These subsystems are:

        ADA_BASE
        MACHINE_INTERFACE
        KERNEL_DEBUGGER_IO
        KERNEL_DEBUGGER
        KERNEL
        ENVIRONMENT_DEBUGGER
        ABSTRACT_TYPES
        MISCELLANEOUS
        OS_UTILITIES
        ELABORATOR_DATABASE

For each of these subsystems a configuration file contains information
about where the subsystem is within the DFS.  A subsystem may be located
in one of three ways:

    o    User should be queried at load time for the subsystem.  This
    method is only used internally for Environment development.

    o    The subsystem is explicitly named within this configuration.
    This is the normal method of locating subsystems.

    o    The subsystem is explicitly named in the STANDARD configuration
    and its location should be determined from the STANDARD.  This
    method is useful for defining deltas from the STANDARD.

To invoke the configuration editor type:

    CLI> x cedit

The program will first begin to edit the systems hardware configuration
as follows:

    Change hardware configuration [N] ?
\f


If you want to modify the hardware configuration enter "Y" otherwise
enter the default.  If you have chosen the default the editor will
proceed to the software configuration.  If you request to modify
the hardware configuration it will proceed as follows:

    If the system is a Series 100 you will be asked:

    Is this a multi-processor ?

    This attribute is only used on Rationals internal Series 100
    processors which have been modified for multi-processing.

    Does this processor have 8 MB memory boards ?

    All Rational systems currently use eight mega-byte memory
    modules.  This question should be answered "Y".

    For each of the four possible memory modules you will be
    asked:

    Does memory board <n> exist ?

    All Rational systems currently use all four possible memory
    modules.  All of these four questions should be answered "Y".


Editing the hardware configuration is now done

Editing the software configuration is really done in two parts.  First
some information about how the booting process should work is needed
followed by information about each of the ten subsystems.  Before that
the name of the configuration you are creating or modifiying is needed.
The CEDIT program will ask:

    Enter name of configuration to edit [STANDARD] :

Enter the name of the configuration on which you want to base your
changes.  This is not neccessarily the configuration you will be
changing.  You will then be asked:

    Enter name of configuration to save [<name-of-configuration-to-edit>] :

By default the editor will save you changes in the configuration you
are basing them on.  You may specify a different name if you wish.  If
you specify a different configuration the original will not be changed.

Now the editor will inquire about some booting options.  These are:

    Allow operator to enter CLI immediately ?

    If this question is answered "Y" the operator will be asked if he/she
    wishes to fork the CLI at the beginning of the booting process.
\f


    Allow editing of configuration ?

    If this question is answered "Y" the operator will be asked if he/she
    wishes to edit the configuration being used to boot the processor
    during the booting process.
    
    Allow operator to enter CLI prior to starting the cluster ?

    If this question is answered "Y" the operator will be asked if he/she
    wishes to fork the CLI between the time that microcode is loaded and
    macro-code is loaded.  At this point the R1000 processor will not yet
    have been started.

    Load kernel layer subsystems only ?

    If this question is answered "Y" only the first five subsystems will
    be loaded before the R1000 processor is started.  This feature is
    used to run certain R1000 diagnostics and exercisers.

Now the editor will ask some questions about the microcode and subsystems
to be used to boot the processor.  These questions will be asked eleven
times, once for each of the following:

        MICROCODE
        ADA_BASE
        MACHINE_INTERFACE
        KERNEL_DEBUGGER_IO
        KERNEL_DEBUGGER
        KERNEL
        ENVIRONMENT_DEBUGGER
        ABSTRACT_TYPES
        MISCELLANEOUS
        OS_UTILITIES
        ELABORATOR_DATABASE

The questions are:

    Take <subsystem-name> from STANDARD ?

    This question will not be asked if you are editing the STANDARD
    configuration.  If you answer "Y" to this question you will not
    be asked any more questions about this subsystem.

    Should this configuration query for <subsystem-name> ?

    If you answer this question "Y" then at boot time the macro-state
    loader will query about where the subsystem is located.

    Enter name for <subsystem-name> ?

    The answer to this question tells the macro-state loader where to
    get code for this subsystem.  It is the name of an MLOAD file. If
    you answered "Y" to the query question the name you enter here will
    be the default answer when the operator is queried at boot time.
\f


The configuration editor will now save the configurations modified during
the editing process.  If this succeeds it will display the message:

    Configuration saved!

In any case the CEDIT program will terminate.«nul»
DataMuseum.dk

Rational R1000/400 DFS Tapes

⟦91a1ca766⟧ HLP, TextFile

Derivation

TextFile
