![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
File > New > New SubsystemTo create a new subsystem or Rational subsystem in a directory, select File > New > New Subsystem. This displays the New Subsystem dialog box.
New Subsystem Dialog Box Fields:
Subsystem Full Name
Enter a fully qualified pathname in the Name field. This is the permanent name for the subsystem and is subject to the context exclusion list specified by the session switch APEX_SS_CONTEXT_EXCLUSIONS.
For Apex/ClearCase, a Rational Subsystem (RSS) is created. These are described in detail in Getting Started.
Caution: For Apex/Summit, subsystems cannot be created within an existing subsystem.
Model Selection (Apex/ClearCase)
There are often many models to choose from when creating a new RSS. The Model Selection section of this dialog is designed to assist you in narrowing down the number of models you have to choose from.
- Language Pull Down Menu
The Language pull down menu provides the following options:
The Language Type is defaulted based on the setting of APEX_DEFAULT_MODEL.
- Host Architecture Pull Down Menu
The Host Architecture pull down menu provides options corresponding to the architectures supported by Apex (for example, sun4_solaris2, hppa_hpux, etc.).
The host architecture is defaulted based on the setting of $APEX_ARCH.
Once you have set the above pull don menus to your desired values, click the Alternatives button to view the list of models that meet your criteria. If the settings of the pull down menus matches exactly one model, that model is automatically entered in the Model Field.
Model Field (Apex/ClearCase)
In the Model field, enter the name on which to base the new RSS. Subdirectories, switches, compiler options, and imports of the new RSS are copied from the model . The current model appears in the Model field by default. To view additional models available for your configuration, use the Alternatives popup. A list of alternative models is displayed which is based on the values of language and host architecture. In addition, the list includes the models listed in your Active Projects. Active projects are discussed under File > Setup.
More information on models is provided in the Programmer's Guide.
Imports Field (Apex/ClearCase)
Use the Import field to specify the imports of the new RSS. The RSS, Summit/CM subsystem or configuration to be imported is added to any already specified by the model. You can name only one entity.
Storage Radio Buttons (Apex/Summit)
- Place storage in subsystem's enclosing directory
Places the physical storage in the subsystem's enclosing directory.
- Place storage in directory
Use the storage text field to specify a location for physical storage that is different from the logical name. When you use this field, symbolic links are created from the logical location to the physical location.
Visit Check Box
- Visit the new subsystem
To display the subsystem in a Directory Viewer window, check the Visit the new subsystem option. This is the default.
Make it an element Check Box (Apex/ClearCase)
- Make it an element
To make the Rational Subsystem a ClearCase element, click this box. When you do this, a Note field appears. Enter any text you wish associated with the RSS>
Command Line Interface: create_subsystem
RCI Tab (Ada only)
The following options are displayed when the RCI tab is selected.
These options are used to specify a target Ada library (Target Directory) that corresponds to the specified host view. (Depending on your RCI customization, the elements of the Ada library required by your target compiler will be built, including the Ada program library and import information.)
If the Target Directory does not already exist on the target, it will be created and associated it with the selected host view. If the RCI Target Directory does exist on the target but is not an Ada library, it will be converted it into an Ada library before associating it with the host view. If the RCI Target Directory exists on the target and is already an Ada library, it will just be associated it with the selected subsystem.
Note: Do not assign two subsystems from the same subsystem to the same target library, unless your customization specifically requires this structure.
Once the target library has been created, all units in the subsystem are marked as requiring recoding on the target.
When you create a target library for a subsystem that is imported by others, the importing subsystem imports are made obsolete.
Before you compile units in one of the subsystems, you must refresh its imports (use Control > Maintenance > Refresh (Apex/Summit)).
Some buttons work in pairs, and in addition, button combinations are only allowed that create correctly formed RCI subsystems. For example, a host-only subsystem with or without a target library, or a host-target subsystem with a target library.
Enable RCI Options Check Box
Indicates whether RCI options for new subsystems are provided below.
Machine Button and Text Field
Use this field to specify which machine, if different from the host on which Apex is running, will perform target operations (such as library operations, compilation and linking) for this subsystem.
This field will be used to set the value of the RCI_COMPILATION_PLATFORM context switch for the host subsystem.
Selecting the Machine button will cause the Compile on Host Only button to be deselected.
Compile on Host Only Button
No target compilations will occur for this subsystem if this button is selected. Such a subsystem can still have an associated target library which allows RCI subsystems to be associated with precompiled target libraries.
Selecting the Compile on Host Only Button will cause the Machine Button to be deselected.
Target Directory specification fields:
These fields are used to specify a context, and a library name within this context, which will be combined (in a RCI customization specific way) to form the pathname for the target library to create and associate to the host subsystem.
This pathname will be used to set the value of the RCI_TARGET_DIRECTORY context switch for the host subsystem.
Context for target libraries Button and Text Field
The path to the directory context for the target library.
Selecting the Context for target libraries Button will cause the Target library context is default context Button to be deselected.
Target library context is default context Button
Sets target library context to a default value.
Selecting the Target library context is default context Button will cause the Context for target libraries Button to be deselected.
The value for the default context is RCI customization dependent. Generally, if the host filesystem is visible from the target machine, this default context will be the enclosing subsystem.
Target library name Button and Text Field
The name of the target library within the context.
Selecting the Target library name Button will cause the Target library name is automatically generated Button to be deselected.
Target library name is automatically generated Button
Sets target library name within the context to a default, automatically generated, value.
Selecting the Target library name is automatically generated Button to be deselected will cause the Target library name Button to be deselected.
The value for the default name is RCI customization dependent. Generally, if the host filesystem is visible from the target machine, this default name will be targets/<subsystem:t:r>.rci<subsystem:e> (i.e. a subdirectory within a targets directory with the same base name as the host subsystem, and extension .rciwrk or .rcirel, depending on the kind of the host subsystem).
Subsystem has no target library Button
Subsystems without target libraries must also be Host Only, although the reverse is not true as mentioned above.
Selecting this button will cause the Compile on Host Only Button to be selected, and the context and target library name Fields to become inactive.
Note: The creation of target libraries may or may not be implemented from one RCI customization to another. Also, your customizer can modify the way it operates (in particular the rules used to analyze and combine the provided target library context and name, and to generate default values for these).
For additional information, check the documentation for your RCI customization.
For additional detailed information on Apex shadowing, see the Client/Server Concepts Guide
Additional Topics
Rational Software Corporation http://www.rational.com support@rational.com techpubs@rational.com Copyright © 1993-2001, Rational Software Corporation. All rights reserved. |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |