|
DataMuseum.dkPresents historical artifacts from the history of: Rational R1000/400 |
This is an automatic "excavation" of a thematic subset of
See our Wiki for more about Rational R1000/400 Excavated with: AutoArchaeologist - Free & Open Source Software. |
top - download
Length: 57444 (0xe064)
Types: TextFile
Notes: R1k Text-file segment
└─⟦8527c1e9b⟧ Bits:30000544 8mm tape, Rational 1000, Arrival backup of disks in PAM's R1000
└─ ⟦5a81ac88f⟧ »Space Info Vol 1«
└─⟦fab2b780d⟧
└─⟦this⟧
Remote Compilation Facility
Release Information
Release 1_2_2
\f
Copyright 1992 by Rational
Part Number: 508-003255-009
June 1992 (Software Release 1_2_2)
DEC, VAX, and VMS are trademarks of Digital Equipment
Corporation.
UNIX is a registered trademark of AT&T.
Rational and R1000 are registered trademarks and Rational
Environment and Rational Subsystems are trademarks
of Rational.
Rational
3320 Scott Boulevard
Santa Clara, California 95054-3197
\f
Release 1_2_2
1. Overview
This release note describes Release 1_2_2 of the Rational Remote
Compilation Facility (RCF), also referred to as the Customizable
RCF. The purpose of this release is to enhance Release 1_1_1 of
the Customizable RCF.
This release provides support for pragma Inline and pragma Main.
It also includes an enhanced programmatic interface and fixes to
Nonexistent Page Error problems and various compilation ordering
problems uncovered in Rev1_1_1. For a complete list of fixed
bugs, refer to Section 6, "Fixed Problems" of this document.
2. RCF Components
The following RCF components are installed as part of the
release:
!Targets.Implementation.Rcf_Release1_2_2
-- Main RCF release world
!Machine.Target_Builder.Rcf_Errors
-- Encoded Rcf Errors
!Targets.Implementation.Rcf_User_Interface
-- Rcf command interface
Rev1_2_Spec
Code1_2_2
!Targets.Implementation.Rcf_Programmatic_Interface
-- Rcf Programmatic Interface
Rev1_2_Spec -- Rev1_0_Spec is still valid (and
-- is included on the release tape)
!Targets.Implementation.Rcf_Customization_Interface
-- Customization Interface
Rev1_2_Spec
!Rcf.Reusable_Components.Rev1_2_0
-- Rational Reusable Components
For more information on installation of this product, refer to
the installation instructions delivered with this release. For
user information, refer to the RCF User's Manual.
3. Upgrade Impact
This release uses a revised mechanism for computing compilation
ordering. This makes Release 1_2_2 incompatible with any previous
RCF release. Upgrading to Release 1_2_2 builds program libraries
for all RCF target key views. Installing the new release
automatically does this upgrade.
RATIONAL June 1992 1\f
RCF Release Information
This release has no impact on existing RCF customizations. You
can modify your existing customization to take advantage of the
new functionality provided in the Rev1_2_2 Rcf_Programmatic-
.Interface. Section 5.3, "Programmatic Interface Enhancements",
describes the changes.
Note: Do not delete Rev1_0_Spec under the following conditions:
* If you do not plan to upgrade to make use of the new
programmatic interface.
* If you have installed or plan to install any
Rational-supported RCF Extension.
4. Prerequisites
Before you use the RCF, confirm the following prerequisite
conditions:
* The host R1000 and remote compilation server are on the same
network.
* An entry in !Machine.Transport_Name_Map identifies the remote
compilation server. For example, where tcp/ip is the
communications protocol, 89.64.128.9 is the internet address,
Tilden is the logical machine name, and Aix is the remote
compilation operating system, the entry appears as follows:
tcp/ip 89.64.128.9 Tilden Aix
* The network communication server is running. The RCF supports
two modes of file transfer and command execution: DTIA and
Telnet/FTP.
DTIA is not a prerequisite for customizations using the
Telnet/FTP transfer mode.
If you are using a customization with a DTIA transfer mode,
the DTIA server must be installed on the host R1000 and
running on the remote compilation platform.
To detect if the host server is running:
- Execute What.Users.
- Search for job name DTIA Remote_Operations Server in the
list.
To detect if the remote DTIA server is running, refer to the
DTIA installation instructions.
2 June 1992 RATIONAL\f
Release 1_2_2
5. New Features
This section describes the features added since Release 1_1_1 of
the Customizable RCF.
5.1. Pragma Main Support
The RCF supports the Rational-defined pragma Main. If you specify
pragma Main in the specification of a main program, the RCF
invokes the remote link operation automatically after coding the
unit. This produces an executable module without explicitly
invoking the Rcf.Link command. Since this eliminates the need to
explicitly link the main program, the RCF development model more
closely matches the Rational Environment native development
model. RCF support of this feature is particularly useful when
you do host-based testing and transition from CDF to RCF use.
To use pragma Main, place it immediately after the end of the
specification or body of a main procedure. You can use pragma
Main in any library-level Ada unit that can be linked on the
remote compilation platform.
Before a main program can be promoted to the coded state, all
compilation units in its closure must be in the coded state. If
all units in the closure are not coded, the RCF creates a message
of the following form:
ERROR Link failed for <Main_Unit>. Failure in Host_Linker
.Prelink.
Attempting to demote a unit in the closure of a coded main unit
can result in an error message.
RCF support for pragma Main does not include parameters, which
means that the RCF issues warning messages in code joined with
R1000 or CDF views where pragma Main can include various
parameters.
Refer to the Rational LRM, Appendix F for more information about
the R1000 semantics of pragma Main.
5.2. Pragma Inline Support
The RCF supports pragma Inline. It takes inlining dependencies
into account when computing coding order, during promotion, and
obsolescence requirements, during demotion. Units are compiled in
an order that allows the remote compiler to inline (macro expand)
calls to inlined routines. Inlined callers are obsolesced when
the body of an inlined routine is demoted.
Note that inlining is always in effect, regardless of how your
site-specific customization or Rational-supported Extension has
been implemented.
RATIONAL June 1992 3\f
RCF Release Information
5.3. Programmatic Interface Enhancements
Release 1_2_2 enhances the RCF programmatic interfaces in the
following ways:
* Deletes some interfaces from the compilation interface.
* Adds calls to handle secondaries; to create and delete
secondaries and to display and manipulate secondary state
information.
* Adds calls to access various fields from the customization
templates.
This release contains the following changes to packages in
!Targets.Implementation.Rcf_Programmatic_Interface.Rev1_2_Spec.
Units:
* Compilation_Interface: Deletes interfaces to Promote, Demote,
and Link.
* Import_Interface: Adds the function Get_Referencers which
returns a list of views that import a given view.
* Library_Interface: No changes.
* Remote_Command_Interface: Adds the following functions:
- Upload_Ada_Unit: Uploads remote Ada units.
- Upload_Text_File: Uploads a remote text file after
acquiring the necessary network connections.
- Update_Consistency: Updates the consistency between a host
and remote unit.
* Target_Dependent_Interface: Adds functions that return the
values for customized attributes of the RCF; for example,
Directory_Prefix, Extension_Separator, Max_Filename_Length,
Linker_Post_Options. You can derive these values using
Rcf_Customization_Interface functions, but the functions in
this package provide a simpler interface.
* Unit_Interface: Adds functions to create and manipulate
secondaries and secondary state information. Refer to the
package spec for detailed information on the new functions.
5.4. Compilation Ordering Mechanism
The RCF now uses a revised mechanism for computing compilation
ordering. This mechanism is more robust and more tightly
integrated with the Rational Environment. The new mechanism
eliminates most compilation ordering problems found in previous
releases.
4 June 1992 RATIONAL\f
Release 1_2_2
6. Fixed Problems
This section describes problems fixed since Release 1_1_1.
Fixes noted as Customizers Only apply to customization components
of the RCF. Customizers should check these fixes; general users
can ignore these sections.
The following table provides the PRS number of the problem, the
section number of the description in this release note, and the
PRS summary of the problem.
Summary of Fixed Problems
-------------------------------------------------------------
| | | |
| PRS Number | Sec | PRS Summary |
| | Num | |
-------------------------------------------------------------
| | | |
|none |6.8 |Incremental pragma inline disallowal |
-------------------------------------------------------------
| | | |
|none |5.4 |Subunits of a generic body not coded |
| |6.7 |before the instantiation |
-------------------------------------------------------------
| | | |
|none |6.5 |Telnet Connection Echo Option |
-------------------------------------------------------------
| | | |
|1548835-Blut- |6.1 |Missing Reusable Component subunits have|
|Smp | |been provided |
-------------------------------------------------------------
| | | |
|169982-Gato- |6.19 |Customizer Only |
|Mboy | |Invalid parameters for |
| | |Promote_Preprocess using secondaries |
-------------------------------------------------------------
| | | |
|2394595-Gato- |6.10 |RCI error during import |
|Mboy | | |
-------------------------------------------------------------
| | | |
|244898-Jazm- |6.14 |Rcf.Accept_Remote_Changes should check |
|Jak | |out units |
-------------------------------------------------------------
| | | |
|2523423-Gato- |5.4 |Invalid compilation order dreated during|
|Mboy |6.6 |multiple dependent views |
-------------------------------------------------------------
| | | |
|2760406-Blut- |6.3 |rcf compiler locks terminal_nnn lines if|
|Smp | |job.kill of a rcf command |
-------------------------------------------------------------
RATIONAL June 1992 5\f
RCF Release Information
-------------------------------------------------------------
| | | |
| PRS Number | Sec | PRS Summary |
| | Num | |
-------------------------------------------------------------
| | | |
|3617494-Gato- |6.13 |Link with Make_Uncoded_Units does not |
|Mboy | |work |
-------------------------------------------------------------
| | | |
|4514072-Gato- |6.2, |DTIA doesn't close down csh process |
|Mboy |7.4 |properly |
-------------------------------------------------------------
| | | |
|5379137-Gato- |6.4 |RCF holds on to telnet port when link |
|Mboy | |fails. |
-------------------------------------------------------------
| | | |
|5386182-Gato- |6.20 |Customizer Only |
|Mboy | |CSR6322: RCI promote gets error UNIT |
| | |<UNIT_NAME> unknown to the RCF |
-------------------------------------------------------------
| | | |
|6133452-Jazm- |6.17 |Privileges required for registering a |
|Jak | |target key |
-------------------------------------------------------------
| | | |
|6158281-Jazm- |6.18 |Customizer Only |
|Jak | |create_predefined_library should check |
| | |length of target key |
-------------------------------------------------------------
| | | |
|6164103-Blut- |6.15 |RCI Initialize 2 minute delay needs to |
|Smp | |be lengthened |
-------------------------------------------------------------
| | | |
|7274371-Gato- |6.12 |RCF_CMVC.REMOVE_IMPORTS not working |
|Mboy | |correctly. |
-------------------------------------------------------------
| | | |
|9123690-0172-4|6.16 |Better interpretation of VAX error codes|
| | |needed for RCI |
-------------------------------------------------------------
| | | |
|9348469-Jazm- |6.21 |Customizer Only |
|Jak | |status not always being checked for |
| | |preprocess |
-------------------------------------------------------------
| | | |
|9523197-Jazm- |6.11 |Problem resolving <cursor> in |
|Jak | |Rcf_Cmvc.Import |
-------------------------------------------------------------
6 June 1992 RATIONAL\f
Release 1_2_2
-------------------------------------------------------------
| | | |
| PRS Number | Sec | PRS Summary |
| | Num | |
-------------------------------------------------------------
| | | |
|9930958-Jazm- |6.9 |Nonexistent_Page_Error while promoting a|
|Jak | |unit |
-------------------------------------------------------------
6.1. Reusable Component Subunits
PRS Number => 1548835-Blut-Smp
The reusable components, Parameter_Parser and Time_Utilities,
were missing their subunits; they are provided in this release.
6.2. DTIA and UNIX Shells
PRS Number => 4514072-Gato-Mboy
When you use the RCF in conjunction with DTIA and UNIX, the UNIX
default login shell must be "ksh". If the default shell is "csh",
then the RCF job hangs on some commands. Killing the RCF leaves
certain processes running on the UNIX system.
Section 7.4, "Using DTIA and UNIX Shells", describes the steps to
correct this problem.
6.3. Locked Telnet Ports
PRS Number => 2760406-Blut-Smp
In RCF Release 1_1_1, if you terminated any RCF job doing remote
communications, the RCF locked a Telnet port in !Machine.Devices.
This caused the RCF to eventually run out of available Telnet
ports on the machine, if enough jobs were terminated to use all
ports.
The RCF no longer locks a Telnet port when you kill the job that
acquired it.
6.4. Locked Telnet Port When Rcf.Link Fails
PRS Number => 5379137-Gato-Mboy
In RCF Release 1_1_1, if Rcf.Link failed during a remote
operation, it locked the Telnet port after job completion.
RATIONAL June 1992 7\f
RCF Release Information
The RCF releases the Telnet port after completion/termination of
any RCF job.
6.5. Telnet Connection Echo Option
If the Telnet protocol Echo option is set ON for the local host,
the host R1000 echos data received from the remote machine back
to the remote machine. This can occasionally cause login problems
on some remote systems.
The RCF now establishes Telnet connections with the Telnet
protocol Echo option set OFF for the local host. This means that
the R1000 does not echo back data that it receives from the
remote system.
6.6. Compilation Ordering with Compilation.Make
PRS Nmber => 2538423-Gato-Mboy
Invalid compilation ordering could result under certain
conditions. For example, for views A, B, C, ... n, where A
depends on B, B depends on C, and so forth, using
Compilation.Make creates an invalid compilation order when it
codes a main unit in view A or codes a set of views, A through n.
The restructured mechanism for computing compilation order
eliminates this problem.
6.7. Compilation Ordering of Generics
Invalid compilation ordering created a condition in which
subunits of a generic body were not coded before the
instantiation.
The restructured mechanism for computing compilation order
eliminates this problem.
6.8. Incremental Pragma Inline Error
In previous releases, The RCF did not produce a message if you
incorrectly added pragma Inline incrementally to a unit.
The RCF produces a semantic error if you incrementally add pragma
Inline to units.
8 June 1992 RATIONAL\f
Release 1_2_2
6.9. Nonexistent Page Errors
PRS => 9930958-Jazm-Jak
Intermittent Nonexistent Page Errors were encountered on heavily
loaded machines. The typical message was of the form:
1: EXCEPTION_HANDLED Promotion failed with
!Lrm.System.Nonexistent_Page_Error,
from PC = #258D0D, #1D3
This error usually stopped occurring after repeated commands.
All known sources of these errors in Releases 1_1_1 and 1_2_0
have been corrected in this release.
6.10. State File Access For Importing Views
PRS Number => 2394595-Gato-Mboy
In previous releases, views created by users with limited ACLs
(RCOD) could not import other views with limited ACLs.
In this release these views can be imported. The RCF explicitly
sets the access controls for the the state files and their
enclosing directories to usable access permissions. The ACLs are
set to Network_Public => RWCOD.
6.11. Rcf_Cmvc.Import Parameter Resolution Errors
PRS Number => 9523197-Jazm-Jak
In RCF Release 1_1_1, if you used Rcf_Cmvc.Import with the
Into_View parameter set to "<CURSOR>" and Remake_Demoted_Units
parameter set to True, the command produced error messages when
trying to remake units. The import operation succeeded.
For example, the following command:
Rcf_Cmvc.Import(View_To_Import => "!Projects.Mss.System.
Rci_Evaluation.Common_Layer.System_Services.Rev1_Working",
Into_View => "<CURSOR>",
Only_Change_Imports => False,
Import_Closure => False,
Remake_Demoted_Units => True,
Goal => INSTALLED,
Comments => "",
Work_Order => "<DEFAULT>",
Response => "<PROFILE>")
RATIONAL June 1992 9\f
RCF Release Information
produced the following message:
++* Had trouble finding units to promote (C'(COMBINED_VIEW)
is not defined in <CURSOR>.
This error message does not occur in Release 1_2_2.
6.12. Removing Multiple Imports With Rcf_Cmvc.Remove_Imports
PRS Number => 7274371-Gato-Mboy
In previous releases, Rcf_Cmvc.Remove_Import does not execute
Remove_Import_Preprocess or Remove_Import_Postprocess for each
view when the View parameter contained a list (for example,
[subsystem_a;subsystem_b].rev1_working). Because of this, you
could not remove more than one import from a view with the
Remove_Import command.
The RCF calls these procedures for each view in the list. You can
now remove multiple imports with the command.
6.13. Rcf.Link Make_Uncoded_Units Parameter Failure
PRS Number => 3617494-Gato-Mboy
In Release 1_2_0, the Make_Uncoded_Units parameter of the
Rcf.Link command did not cause the RCF to promote uncoded units
before linking.
The RCF takes the correct action if you use the
Make_Uncoded_Units parameter of the Rcf.Link command.
6.14. Rcf.Accept_Remote_Changes and Check In
PRS Number => 244898-Jazm-Jak
In RCF Release 1_1_1, the RCF expected host units to be checked
out (with Rcf_Cmvc.Check_Out) while accepting remote changes
(with Rcf.Accept_Remote_Changes). This was inconsistent with the
way Cmvc.Accept_Changes works.
The RCF expects a host unit to be checked in (with
Rcf_Cmvc.Check_In) before accepting changes into it. The
Rcf.Accept_Remote_Changes command now checks out the unit,
updates the changes, and checks the unit in.
10 June 1992 RATIONAL\f
Release 1_2_2
6.15. Rcf_Initialize Timing
PRS Number => 6164103-Blut-Smp
In the previous release, Rcf_Initialize failed after two minutes.
This did not provide adequate time, in some cases, for the
process to complete.
Initialize_Rcf now waits ten minutes for Start_Rcf to elaborate
before failing.
6.16. VAX Error Codes
PRS Number => 9123690-0172-4
In Release 1_0_3, the RCF mapped any odd-valued VAX error code or
0 (zero) error code to success, and any even-valued VAX error
code to failure. This caused remote warnings to be reported as
success.
The RCF maps VMS return code 0 (zero) to Simple_Status.Warning
on the host.
6.17. Registering RCF Customizations and Extensions
PRS Number => 6133452-Jazm-Jak
In previous releases of the RCF, you needed operator privileges
to register a customization.
You no longer need operator privileges to register an RCF
customization or a Rational-supported RCF Extension.
6.18. Create_Predefined_Library Target Key Length Check
CUSTOMIZER ONLY
PRS Number => 6158281-Jazm-Jak
The Rcf_Customization.Create_Predefined_Library command did not
check the value of the Target_Key_Name parameter for a valid
length.
The command now requires that the value specified in the
Target_Key_Name parameter is not longer than 16 characters.
RATIONAL June 1992 11\f
RCF Release Information
6.19. Invalid Parameters For Promote_Preprocess Using
Secondaries
CUSTOMIZER ONLY
PRS Number => 169982-Gato-Mboy
In RCF Release 1_1_1, the RCF passed the compilation extension
Promote_Preprocesss a compilation command for its
Remote_Unit_Name parameter.
The RCF correctly passes the secondary Remote_Unit_Name to this
extension.
6.20. Promote Error With Set/Get_Remote_Unit_Name
CUSTOMIZER ONLY
PRS Number => 5386182-Gato-Mboy; CSR6322
If a customization called the Set/Get_Remote_Unit_Name function
from the Programmatic Interface, it generated the following error
message due to a state file locking problem:
Unit <UNIT_NAME> unknown to the RCF
This is fixed.
6.21. Extension Status Checking
CUSTOMIZER ONLY
PRS Number => 9348469-Jazm-Jak
In RCF Release 1_1_1, the RCF did not check the status returned
by some extensions, including Link_Preprocess and
Link_Postprocess. The RCF command proceeded even if the
extensions failed.
The RCF checks status returned by all extensions. If the
extension fails, the RCF command fails.
7. Limitations
This section describes limitations in Release 1_2_2 of the
Customizable RCF.
7.1. Compilation Order Involving Generics
Compilation ordering involving generics assumes macro expansion,
regardless of how your site-specific customization or
Rational-supported Extension has been implemented. The RCF always
assumes macro expansions and introduces additional coding
dependencies as a result.
12 June 1992 RATIONAL\f
Release 1_2_2
7.2. Coding Subunits and Parents
PRS Number => 9123690-0167-0
Coding a subunit requires that the parent be coded first. In the
RCF, if units are installed, it is assumed that they will code on
the remote compilation platform. The RCF does not provide special
case handling for an unusual error in the event that an Ada unit
fails to code on the remote compilation platform. The compilation
operation does not record whether it has tried and failed to code
the parent unit. The RCF tries to code the subunit even though
the parent has failed to code.
7.3. Promoting Stubs to the Coded State
You cannot promote a stub directly to the Coded state. You must
first promote the stub to the Installed state.
7.4. Using DTIA and UNIX Shells
PRS Number => 4514072-Gato-Mboy
When you use the RCF in conjunction with DTIA and UNIX, the UNIX
default login shell must be "ksh". If the default shell is "csh",
then the RCF job hangs on some commands and return a "Variable
Syntax" message. Killing the RCF leaves certain processes, csh
and in.dtia, running on the remote UNIX system.
Use the following steps to remove those jobs:
1. Log in to the remote UNIX system.
2. Use the UNIX kill -9 for that system to kill the remaining
associated jobs.
7.5. Telnet Logins
For customizations using the Telnet/FTP transfer mode, remote
user logins cannot request input. If they do, such logins hang.
7.6. Prompting For Passwords
The RCF no longer supports the Prompt For Password feature.
7.7. Archive.Copy/Archive.Restore Operations
Note the following conditions when you use Archive.Copy and
Archive.Restore with the Customizable RCF.
RATIONAL June 1992 13\f
RCF Release Information
7.7.1. Archiving and Restoring Views
Archive.Copy and Archive.Restore refresh all RCF state
information when copying/restoring a view, including the
following:
* Remote unit names
* Unit download timestamps
* Unit options
Compiler_Switches are copied from the source view. This leaves
the switches Ftp.Remote_Machine, Ftp.Remote_Directory,
Ftp.Username, and Ftp.Password unchanged.
You are encouraged to copy views using the Goal_State =>
Installed option.
After the archive operation has completed, use
Rcf.Build_Remote_Library to build a new remote library for the
host view.
7.7.2. Copying and Restoring Secondaries
Archive does not copy sub-objects such as secondary referencer
files. Before you copy a view containing secondaries to a new
location, run Rcf.Expand_Secondary_Referencers to put secondary
referencer files into a form that can be copied. Once your copy
operation has completed, run Rcf.Collapse_Secondary_Referencer to
restore the secondary referencer sub-objects.
7.8. Configuration_Only Releases
Configuration_Only releases currently do not maintain the
host-target connection information. If you specify the
Remote_Directory parameter with Rcf_Cmvc.Release, it builds the
remote library. But when you restore the configuration with
Rcf_Cmvc.Build, the host-remote relationship is lost.
The Goal parameter is always Compilation.Source on a
Rcf_Cmvc.Build command executed on a configuration release.
Before you install or code such a view, you must unfreeze it and
run Rcf.Refresh_View.
Any secondary_referencer files must be expanded and controlled
before you build a configuration-only release, and then collapsed
after you restore the configuration. In order to restore the RCF
state information after using Rcf_Cmvc.Build, execute
Rcf.Refresh_View:
14 June 1992 RATIONAL\f
Release 1_2_2
Rcf.Refresh_View (View => "<CURSOR>",
Retain_History => True,
Response => "<PROFILE>");
In its current form, a configuration release is useful for
minimal-space host releases. A future RCF release will provide
full support.
Refer any questions to your Rational Technical Representative.
7.9. Rcf_Cmvc.Build And The State File
PRS Number => 7905886-Gato-Mboy
You must specify the Goal parameter as Goal => Compilation.Source
when restoring from a configuration to avoid errors resulting
from a nonexistent state file. Refer to Section 7.8,
"Configuration-Only Releases", for more information.
7.10. Trace_Command_Output And Rcf.Execute_Remote_Command
Since Trace_Command_Output is a library switch, and
Execute_Remote_Command is a command that is not associated with
any library context, this switch is not recognized by this
command.
7.11. Rcf.Execute_Remote_Command
Rcf.Execute_Remote_Command cannot run commands that require
input.
7.12. COTS Specifications
Caution: Rational Technical Representatives must not upload third
party vendor specifications into the RCF predefined areas.
As the customer, you must contact your third party vendor for
information regarding license and restrictions or to obtain
written permission to upload or copy specifications yourself.
7.13. Associated Files Retrieval For Secondaries
When processing a secondary file, the RCF does not call the
Retrieve_Associated_Files Preprocess and Postprocess extensions.
RATIONAL June 1992 15\f
RCF Release Information
7.14. Overloading Attributes
The types of the attribute prefixes must be mutually exclusive
when you customize to overload vendor-specific attributes.
7.15. Attributes as Component Clauses of Rep Specs
The Environment parser does not allow attributes as component
clauses of record representation clauses. For example, the
following causes a syntax error:
declare
type Int_Array is array (Integer range <>) of Integer;
type R (D : Integer) is
record
A : Int_Array (1 .. D);
end record;
for R use
record
A'Array_Descriptor at 0 range 1 .. 32;
A at 1 range 1 .. 32;
end record;
When you semaniticize this example, the apostrophe (') between
"A" and "Array_Descriptor" is underlined. The error message is
"Saw ''', expected at".
This requires changes to the Rational Environment and will be
fixed in Release D3.0 of the Rational Environment.
8. Known Problems
Following is a list of problems known at the time of this
release.
8.1. Nonexistent Page Error Exception
Nonexistent Page Errors can occur when the RCF is not elaborated.
To determine if the RCF is elaborated:
1. Execute What.Users.
2. Search for the job name Rcf_Compiler Rev1_2_2.
If the RCF_Compiler is not running:
1. Run Start_Rcf_Main.
2. Use Custom_Key.Register to register your customization.
16 June 1992 RATIONAL\f
Release 1_2_2
8.2. Remote Access Control
The remote DTIA server creates all remote files with the access
permissions:
rw- r-- r--
This permission setting gives read and write permission to the
owner of the file, but read permission only to group and others.
This can prevent multiple host R1000 users with different remote
userids from operating on the same set of host views.
Note: This only affects customizations that use DTIA.
8.3. File Transfer Using FTP
File transfer can fail occasionally for customizations using the
Telnet/FTP transfer mode. In this case, the RCF attempts the
transfer three times before it stops trying to transfer. If none
of the attempts succeed, the host unit is not promoted to the
coded state.
8.4. RCF Compiler Switch Modification
Any changes to the Compiler_Switches file while the RCF is not
elaborated cause all RCF switches in that file to revert to their
default values when the RCF is next elaborated.
8.5. Null Remote_Directory Library Switch
PRS Number => 5185401-Gato-Mboy
If the Remote_Directory library switch is inadvertantly set to
null, when you promote units to coded, the RCF still tries to
download and compile the units on the remote compilation
platform. The RCF downloads to the default home directory on the
remote system. Compilation succeeds if there is an adalib in that
directory.
Refer to Section 8.4, "RCF Compiler Switch Modification", for
information about reverting to default switch settings.
8.6. Compilation Warnings
When you execute a Compilation.Make operation that includes
predefined units in its closure, it generates warning messages
stating that the predefined units have no bodies. Ignore these
warnings.
Workaround: Set the Rational Environment Semantics-
.Subsystem_Interface library switch to True. Setting this switch
RATIONAL June 1992 17\f
RCF Release Information
indicates that the world should be treated as a subsystem
interface, a spec view, and thus the units do not require bodies.
8.7. Rcf_Cmvc.Accept_Changes and Indirect Files
PRS Number => 9123690-0173-4
Rcf_Cmvc.Accept_Changes can produce errors when you use an
indirect file as the Source parameter.
8.8. Response Parameter With Compilation Operations
PRS Number => 903338-Gato-Mboy
Setting the Response parameter in Compilation.Make or
Compilation.Promote has no effect on RCF messages.
8.9. Rcf.Accept_Remote_Changes Temporary File
PRS Number => 7288788-Gato-Mboy
The Rcf.Accept_Remote_Changes command creates a temporary file,
Rcf_Temp_<Time_Stamp>, in the directory containing the host unit.
If the changes are not parsed successfully on the Rational
Environment, then the RCF leaves this file behind without
deleting it.
8.10. Rcf.Check_Consistency Temporary File
PRS Number => 7554142-Gato-Mboy
Rcf.Check_Consistency creates a temporary file, <Unit_Name>_Tmp,
in the directory containing the host unit. If you have already
created a file with the same name, then the operation fails. This
also causes the same error as Rcf.Accept_Remote_Changes.
8.11. Associated-file Retrieval On Warning
PRS Number => 9123690-0167-4
The presence of warning messages does not alter file retrieval
behavior in the remote compilation operation. If there are no
errors in the output log, then the RCF retrieves files specified
to be retrieved under "On_Normal" or "Always" conditions. The RCF
does not recognize warnings, so no files are retrieved under that
condition.
Do not specify that files should be retrieved "On_Warning".
18 June 1992 RATIONAL\f
Release 1_2_2
8.12. Destroy_View_Postprocess
PRS Number => 8509773-Gato-Mboy
The RCF does not call Destroy_View_Postprocess.
8.13. Limited Private Types In Predefined Units
PRS Number => 7059170-Gato-Mboy
If a customization names a limited private type from a predefined
package, it generates a name resolution error. A customization
names a type if the string representation of the type name
appears anywhere in the customization. For example, if you define
an attribute that returns a value of type System.Address, and
System.Address is a limited private type, the following error
occurs during registration:
Name resolution failure for type 'System.Address': AMBIGUOUS.
If you make the type private, the error message does not occur.
8.14. Private Type Equality Operator In Package System
PRS Number => 4348467-Gato-Mboy
An error occurs when you attempt to rename the equality operator
of a private type in package System. This works if the type is
not private.
9. Documentation
Rational Remote Compilation Facility: User's Manual, PN
4000-00500, provides additional information for RCF users.
10. Training
Rational Target Tools Training: Remote Compilation Facility
Fundamentals, PN 7000-00653, provides user training for the RCF.
RATIONAL June 1992 19\f
RCF Release Information
20 June 1992 RATIONAL\f
Release 1_2_2
Appendix A
Fixed Problems History
This appendix describes problems fixed in previous releases of
the product since RCF Release 1_0_3. Descriptions of these fixes
are in the RCF: Release Information Release 1_1_1 Note (PN
508-003255-007).
Fixes noted as Customizers Only apply to customization components
of the RCF. Customizers should check these fixes; general users
can ignore these sections.
The following table provides the PRS number of the problem, the
release in which the problem was fixed, and the PRS summary of
the problem.
History of Fixed Problems
-------------------------------------------------------------
| | | |
| PRS Number | Rel | PRS Summary |
| | Num | |
-------------------------------------------------------------
| | | |
|none |1_1_1|DTIA and Telnet/FTP connections have |
| | |broken and hung |
-------------------------------------------------------------
| | | |
|none |1_1_1|Customizer Only |
| | |Remote_Command_Interface error statuses |
-------------------------------------------------------------
| | | |
|none |1_1_1|Compilation from detached jobs |
-------------------------------------------------------------
| | | |
|2912557-Jazm- |1_1_1|Slow demotion in RCI views |
|Jak | | |
-------------------------------------------------------------
| | | |
|308411-Jazm- |1_1_1|Private type recognition problems |
|Jak | | |
-------------------------------------------------------------
| | | |
|3546124-Jazm- |1_1_1|Customizer Only |
|Jak | |Delete phase went away in customizations|
-------------------------------------------------------------
| | | |
|3907848-Jazm- |1_1_1|Ftp waits too long between retries |
|Jak | | |
-------------------------------------------------------------
| | | |
|4379654-Gato- |1_1_1|Implementation defined attributes do not|
|Mboy | |work for expanded names |
-------------------------------------------------------------
RATIONAL June 1992 21\f
RCF Release Information
-------------------------------------------------------------
| | | |
| PRS Number | Rel | PRS Summary |
| | Num | |
-------------------------------------------------------------
| | | |
|5772860-Gato- |1_1_1|Problem with remote import command |
|Mboy | | |
-------------------------------------------------------------
| | | |
|6663531-Jazm- |1_1_1|New Feature |
|Jak | |Initialization routine should match RDF |
| | |format |
-------------------------------------------------------------
| | | |
|6785680-Gato- |1_1_1|Customizer Only |
|Mboy | |RCI passes a null "views_to_import" |
| | |iterator into IMPORT_PREPROCESS |
-------------------------------------------------------------
| | | |
|680047-Gato- |1_1_1|Problem with "IS_PRE_OPTION" on Link |
|Mboy | | |
-------------------------------------------------------------
| | | |
|7185171-Gato- |1_1_1|Cannot have a single view which uses |
|Mboy | |both the RDF and RCI |
-------------------------------------------------------------
| | | |
|7443648-Gato- |1_1_1|Problem with built-in operators |
|Mboy | | |
-------------------------------------------------------------
| | | |
|8046554-Gato- |1_1_1|Customizer Only |
|Mboy | |Type definitions during customization |
| | |registrations are case sensitive |
-------------------------------------------------------------
| | | |
|8105473-Gato- |1_1_1|Version error occurs during demote and |
|Mboy | |during link using RCI |
-------------------------------------------------------------
| | | |
|8385064-Jazm- |1_1_1|Customizer Only |
|Jak | |Rcf_Cmvc.Release calls wrong library |
| | |extension routines |
-------------------------------------------------------------
| | | |
|9080824-Jazm- |1_1_1|Customizer Only |
|Jak | |Null option problem |
-------------------------------------------------------------
| | | |
|9123690-0166-7|1_1_1|Csr5674: Problem with associated file |
| | |name formation |
-------------------------------------------------------------
22 June 1992 RATIONAL\f
Release 1_2_2
-------------------------------------------------------------
| | | |
| PRS Number | Rel | PRS Summary |
| | Num | |
-------------------------------------------------------------
| | | |
|9123690-0166-8|1_1_1|Customizer Only |
| | |Csr5679: RCF_LINK doesn't retrieve all |
| | |associated files |
-------------------------------------------------------------
| | | |
|9123690-0166-9|1_1_1|Csr5680: RCI Binary File retrieval |
| | |doesn't work |
-------------------------------------------------------------
| | | |
|959311-Jazm- |1_1_1|Csr6036: Overloading of Attributes |
|Jak | | |
-------------------------------------------------------------
RATIONAL June 1992 23\f
Release 1_2_2
Contents
1. Overview 1
2. RCF Components 1
3. Upgrade Impact 1
4. Prerequisites 2
5. New Features 3
5.1. Pragma Main Support 3
5.2. Pragma Inline Support 3
5.3. Programmatic Interface Enhancements 4
5.4. Compilation Ordering Mechanism 4
6. Fixed Problems 5
6.1. Reusable Component Subunits 7
6.2. DTIA and UNIX Shells 7
6.3. Locked Telnet Ports 7
6.4. Locked Telnet Port When Rcf.Link Fails 7
6.5. Telnet Connection Echo Option 8
6.6. Compilation Ordering with Compilation.Make 8
6.7. Compilation Ordering of Generics 8
6.8. Incremental Pragma Inline Error 8
6.9. Nonexistent Page Errors 9
6.10. State File Access For Importing Views 9
6.11. Rcf_Cmvc.Import Parameter Resolution Errors 9
6.12. Removing Multiple Imports With
Rcf_Cmvc.Remove_Imports10
6.13. Rcf.Link Make_Uncoded_Units Parameter Failure 10
6.14. Rcf.Accept_Remote_Changes and Check In 10
6.15. Rcf_Initialize Timing 11
6.16. VAX Error Codes 11
6.17. Registering RCF Customizations and Extensions 11
6.18. Create_Predefined_Library Target Key Length Check 11
6.19. Invalid Parameters For Promote_Preprocess Using
Secondaries 12
6.20. Promote Error With Set/Get_Remote_Unit_Name 12
6.21. Extension Status Checking 12
7. Limitations 12
7.1. Compilation Order Involving Generics 12
7.2. Coding Subunits and Parents 13
7.3. Promoting Stubs to the Coded State 13
7.4. Using DTIA and UNIX Shells 13
7.5. Telnet Logins 13
7.6. Prompting For Passwords 13
7.7. Archive.Copy/Archive.Restore Operations 13
7.7.1. Archiving and Restoring Views 14
7.7.2. Copying and Restoring Secondaries 14
7.8. Configuration_Only Releases 14
7.9. Rcf_Cmvc.Build And The State File 15
7.10. Trace_Command_Output And Rcf.Execute_Remote_Command 15
7.11. Rcf.Execute_Remote_Command 15
7.12. COTS Specifications 15
7.13. Associated Files Retrieval For Secondaries 15
7.14. Overloading Attributes 16
7.15. Attributes as Component Clauses of Rep Specs 16
8. Known Problems 16
RATIONAL June 1992 iii\f
RCF Release Information
8.1. Nonexistent Page Error Exception 16
8.2. Remote Access Control 17
8.3. File Transfer Using FTP 17
8.4. RCF Compiler Switch Modification 17
8.5. Null Remote_Directory Library Switch 17
8.6. Compilation Warnings 17
8.7. Rcf_Cmvc.Accept_Changes and Indirect Files 18
8.8. Response Parameter With Compilation Operations 18
8.9. Rcf.Accept_Remote_Changes Temporary File 18
8.10. Rcf.Check_Consistency Temporary File 18
8.11. Associated-file Retrieval On Warning 18
8.12. Destroy_View_Postprocess 19
8.13. Limited Private Types In Predefined Units 19
8.14. Private Type Equality Operator In Package System 19
9. Documentation 19
10. Training 19
A Fixed Problems History 21
iv June 1992 RATIONAL