![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Copy Views Options in the File > Copy Object Dialog Box (Apex/Summit)Copying Views Radio Button
You can use the File > Copy Object (Apex/Summit) command to create a set of working views or a set of release views. There must be no checked-out files in any of the source views, and the source views in the Copy Object field cannot name two views from the same subsystem. The File > Copy Object (Apex/Summit) command updates the imports of the new views to reflect the imports of the source view.
The Copy Object dialog box displays view options when the Copy Views radio button is selected. These options are accessed through the following tabs:
- Control Tab
- View Tab
- Filter Tab
- Other Tab
- RCI Tab (Ada only)
- Shadow Tab
Command Line Interface > copy_view
Copying Multiple Views
When you copy more than one view at a time, the Destination Name field is interpreted to be relative to the source views. For example if you have
![]()
and are copying the following views in the following subsystems:
![]()
The result is that each rel1.wrk view is copied in its own subsystem and is named new.wrk:
![]()
Note that cabin_ops.ss/new.wrk is a copy of cabin_ops.ss/rel1.wrk and so on.
Imports of all copied views are updated so that any references to source views are changed to reference the new views.
Control Tab
The following options are displayed when the Control tab is selected
If source object is checked out: Radio Buttons
- Fail (Default)
If the source view is checked out, fail the copy operation.
- Fail Unless Check-out is Private
If the source view is checked out, fail the copy operation unless the checkout is private
- Check in Before Copy
If the source view is checked out, check in the view before copying.
- Abandon Check-out
If the source view is checked out, abandon the check out.
- Abandon Check-out and Save
If the source view is checked out, abandon the check out and save the view.
- Copy Latest Checked in version
If the file to be copied is checked out, or the view being copied contains a checked-out file, the latest checked in version of the object is copied.
- Copy Version History If Controlled
If a file being copied is controlled, copy the version history of the file (this is the default). Otherwise, an uncontrolled copy is created.
- New History Field
Specifies that the history of each controlled file will be set to the value supplied. If it is not possible to set the history for a particular file then that file will be left uncontrolled.
- Create New History if it does not exist
Specifies that the history family named by the New History field should be created if it does not exist. This option does not apply when copying an entire subsystem.
View Tab
The following options are displayed when the View tab is selected
View Copy Options Check Boxes and Radio Buttons
- Destination name is subsystem-relative view name.
Indicates that the Destination field is a subsystem-relative view name. For example, "new.wrk" is a subsystem relative view name. This allows you to copy more than one view at a time, when the destination views are in same subsystems as the corresponding source views and have the same view name.
- Destination name is level number for auto-name generation.
Generates a view name for you. The Destination field specifies the "release level" to use in automatic name generation. The default is 1.
- New View Kind: Pull Down Menu
The New View Kind pull down menu allows you to specify the kind of view to create or change the kind of view specified. View kinds are described in the Concepts Guide. The Preserve option indicates that each destination view is to be same kind as the corresponding source view.
- New Model Field
The newly created views will be based on this model. In particular, the compiler key from the model view is copied into the new views, and the imports of the model are used to update the imports of the new views. If no new model is provided (the default) then each new view has the same model as the corresponding source view.
- Replace all switches with those from the New Model's switch file
Active only if an entry is made in the New Model field. When selected, all switches in the view are replaced with those of the model specified in the above field.
- New Imports Field
Specifies that the imports of the new view should include the view or views listed here. Existing imports of a subsystem will be updated to reflect the newly specified view. No new subsystem will be imported.
- Recompile to State: Pull Down Menu
If preserve, copy objects and their compilation object files as they are.
If archived, do not copy any compilation files.
If source, copy only minimal source information that exists, and create it for any files that lack it.
If installed, copy semantic information for any files that have it, and create it for any files that lack it.
If coded, copy semantic information and object files if they exist, then run compilation to create object files for any units that need compilation.
If linked, save as coded, but then link any units that have pragma main in them.
- Place storage in parent subsystem
Storage for the new views is allocated within the containing subsystems.
- Place storage in Field
Specifies that the storage for new views is to be allocated within the designated parent directory.
Filter Tab
The filter options limit the objects to be copied using filename patterns. Different filters may be specified for working views and release views, and for inclusions and exclusions in each case. The default filters are displayed initially. The following options are displayed when the Filter tab is selected.
- Use the default [Working | Release] View Copy [Inclusions | Exclusions]
These radio buttons are selected to use the default filters.
- Set [Working | Release] [Inclusions | Exclusions]
These radio buttons are selected to specify filters. A filter is space-separated list of filename patterns. A file in a Working or Release view is included only if it matches one of the patterns specified in corresponding Inclusions filter but matches no pattern in the corresponding Exclusions filter.
Controlling the Contents of New Views describes the options and switches used in this area.
Other Tab
The following options are displayed when the Other tab is selected.
- Access Category
Specifies the permissions for this object.
- Associated Group
Specifies the group access to this object.
- Create configuration file named: Field
Specifies the name of the configuration file to create that references the newly created views.
- Create Interface-Only View
Creates an interface view. Interface views contain only interface files, such as specifications and generic instances.
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 view.
Note: Do not assign two views 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 host view are marked as requiring recoding on the target.
When you create a target library for a view that is imported by others, the importing views' imports are made obsolete.
Before you compile units in one of the importing views, 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 views. For example, a host-only view with or without a target library, or a host-target view with a target library.
Enable RCI Options Check Box
Indicates whether RCI options for new views 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 host view.
This field will be used to set the value of the RCI_COMPILATION_PLATFORM context switch for the host view.
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 view if this button is selected. Such a view can still have an associated target library which allows RCI views 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 view.
This pathname will be used to set the value of the RCI_TARGET_DIRECTORY context switch for the host view.
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 host view's 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/<view:t:r>.rci<view:e> (i.e. a subdirectory within a targets directory with the same base name as the host view, and extension .rciwrk or .rcirel, depending on the kind of the host view).
View has no target library Button
Views 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. |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |