|
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 - metrics - download
Length: 24263 (0x5ec7)
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«
└─⟦74cc4c704⟧
└─⟦this⟧
Remote Compilation Facility
Release Information
Release 1_0_3
\f
Copyright 1991 by Rational
Part Number: 508-003255-005
October 1991 (Software Release 1_0_3)
AIX and RISC System/6000 are trademarks and IBM is a registered
trademark of International Business Machines Corporation.
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_0_3
1. Overview
This release note describes the production release, Release
1_0_3, of the Rational Remote Compilation Facility, also referred
to as the Customizable RCF.
You can customize the Customizable RCF for a variety of Ada
compilers and operating systems. This release is not delivered
with packaged customizations. If you have existing customizations
from the beta phase, you can update those customizations for the
production release. Contact your Rational Technical
Representative for assistance.
Beta versions of the Customizable RCF have had revision numbers
as high as Rev3_3_8. For the purpose of production, the
Customizable RCF revision number is based at Release 1_0_3.
2. RCF Components
The following RCF components are installed as part of the
release:
!Targets.Implementation.Rcf_Release1_0_3
-- Main RCF release world
!Machine.Target_Builder.Rcf_Errors
-- Encoded Rcf Errors
!Machine.Initialize_Rcf
-- Initializes the RCF at machine boot
!Targets.Implementation.Rcf_User_Interface
-- Rcf command interface
Rev1_0_Spec
Code1_0_3
!Targets.Implementation.Rcf_Programmatic_Interface
Rev1_0_Spec -- Rcf Programmatic Interface
!Targets.Implementation.Rcf_Customization_Interface
Rev1_0_Spec -- Customization Interface
!Rcf.Reusable_Components.Rev1_0_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 Guide.
RATIONAL October 1991 1\f
RCF Release Information
3. Upgrade Impact
This section summarizes the upgrade impact of transitioning from
the beta to the production version of Customizable RCF.
Complete the following steps to upgrade your beta environment.
* Convert all existing customizations built on top of the beta
Customizable RCF to the new customization format. Contact a
Rational Technical Representative for assistance.
* Run the Release 1_0_3 implementation of Rcf.Refresh_View on
all existing RCF views before you proceed with development
using the production RCF.
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 October 1991 RATIONAL\f
Release 1_0_3
5. New Features
The following features have been added since the beta release of
the Customizable RCF.
5.1. Rebuilding Remote Libraries
Rcf.Rebuild_Remote_Library rebuilds remote libraries that may be
corrupt. Refer to the Rcf package specification or the RCF User's
Guide for details.
5.2. Unit Compiler Options
You can maintain remote compiler options on a unit-by-unit basis.
Previously, you could maintain compiler options on a view-by-view
basis in the Compiler_Switches file. Setting options on a unit
basis overrides values set for these options in the
Compiler_Switches file. Refer to the Rcf package specification or
the RCF User's Guide for details.
5.3. Customizable Communications
The customizer can modify the RCF to communicate with most
operating systems supporting Telnet and FTP.
5.4. Executing Remote Commands
Using Rcf.Execute_Remote_Command, you can initiate commands to
run on the remote compilation server from an R1000 Environment
command window. Refer to the Rcf package specification or the RCF
User's Guide for details.
5.5. Reusable Components
The Rational Reusable Components have been released in source
form in an R1000 view (!Rcf.Reusable_Components.Rev1_0_0). Copy
these components to an RCF combined view in a subsystem of your
choice. These components are provided for use at your own risk;
they are not supported with the RCF product.
6. Changed Features
The following features have changed since the Beta release of the
Customizable RCF.
RATIONAL October 1991 3\f
RCF Release Information
6.1. Packages Rcf and Rcf_Cmvc
All RCF user interface commands are separated into two packages,
package Rcf and package Rcf_Cmvc. Package Rcf contains
RCF-specific operations such as handling secondaries, managing
remote libraries, and setting unit options. Package Rcf_Cmvc
contains RCF extensions to existing Rational Environment CMVC
commands. For more information on the contents of these packages,
refer to the RCF User's Guide.
6.2. RCF Compiler Job Name
The name of the RCF Compiler, which acts as a server for all RCF
operations, is Rcf Compiler Rev1_0_3.
6.3. Secondaries
The scheme for managing and processing non-Ada files through
secondary files has been redesigned. Refer to the Rcf package
specification or the RCF User's Guide for details.
6.4. Consistency Checking
The Compare_Objects parameter has been added to both
Rcf.Check_Consistency and Rcf.Accept_Remote_Changes. This
parameter allows you to select between a timestamp consistency
check and a full textual comparison.
6.5. Refreshing Views
Rcf.Refresh_View refreshes, that is, updates or rebuilds, state
information that is thought to be corrupt in a host view.
The command works in one of two modes, determined by the
Retain_History parameter. If Retain_History is True, it preserves
existing remote names, timestamps and unit options. If
Retain_History is False, it reinitializes this information. Refer
to the Rcf package specification or the RCF User's Guide for
details.
6.6. Uploading Units
Rcf.Upload_Unit has been modified to allow you to upload units
into a sub-directory.
Rcf.Upload_Units, added to package Rcf, allows you to upload from
a list of units. You can specify the list of units in an indirect
file.
4 October 1991 RATIONAL\f
Release 1_0_3
Refer to the Rcf package specification or the RCF User's Guide
for details.
6.7. Removed Functionality
The following operations have been removed from the Customizable
RCF.
* Rcf.Initialize
Rcf.Refresh_View replaces this command.
* Rcf.Show_Imports
The RCF no longer separately maintains imports. Use
Rcf_Cmvc.Information to display import information.
* Rcf.Make_Imports_Consistent
The RCF no longer separately maintains imports.
* Rcf.Set_Remote_Machine
Use Switches.Set to change Ftp.Remote_Machine.
* Rcf.Set_Remote_Directory
Use Switches.Set to change Ftp.Remote_Directory.
7. Limitations
This section describes limitations in Release 1_0_3 of the
Customizable RCF.
7.1. Archive.Copy/Archive.Restore Operations
Note the following conditions when you use Archive.Copy and
Archive.Restore with the Customizable RCF.
7.1.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
RATIONAL October 1991 5\f
RCF Release Information
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.1.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 expand
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.2. Configuration-Only Releases
Configuration-only releases currently do not maintain the
host-target connection information. A configuration is created on
the host, although it produces an error message of the form:
++* Can't resolve "<Release_Name>" (<Release_Name> is not defined
... in <Subsystem>)
*** An error occurred during a call to Cmvc.Release.
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 and secondary_state files must be
expanded and controlled before you build a configuration-only
release, and then collapsed after you restore the configuration.
Refer any questions to your Rational Technical Representative.
In its current form, a configuration release is useful for
minimal-space host releases. A future RCF release will provide
full support.
6 October 1991 RATIONAL\f
Release 1_0_3
7.3. Prompting For Passwords
The RCF no longer supports the Prompt For Password feature.
7.4. Detached Operations
You cannot compile from a detached job when the originating
session has been terminated. The compilation operation attempts
to retrieve the remote password from the remote passwords file.
7.5. COTS Specifications
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
permission to upload or copy specifications yourself.
7.6. Rcf.Execute_Remote_Command
Rcf.Execute_Remote_Command cannot run commands that require
input.
7.7. Telnet Logins
For customizations using the Telnet/Ftp transfer mode, remote
user logins cannot request input. If they do, such logins hang.
7.8. Registering Customizations
You need operator privileges to register an RCF customization.
7.9. 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;
RATIONAL October 1991 7\f
RCF Release Information
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".
7.10. Pragma Inline
Units are not necessarily compiled in an order that allows the
remote compiler to inline (macro expand) calls to inlined
routines. However, Host Environment Release D2.2 uses a new
coding algorithm that attempts to compile all library level
procedure and package bodies immediately after the compilation of
their specs. The net effect is that the remote compiler obeys
pragma inline a higher percentage of the time.
Pragma Inline is not ignored during demotion. This ensures that
inline callers are obsolesced when the body of an inlined routine
is demoted.
7.11. 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.
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 for the following reasons:
* 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_0_3.
8 October 1991 RATIONAL\f
Release 1_0_3
If the RCF_Compiler is not running:
1. Run Start_Rcf_Main.
2. Use Custom_Key.Register to register your customization.
* When a state file has become corrupt.
This is usually indicated by one of the following messages:
*** Aborting from Refresh_Suppliers because
!Lrm.Nonexistent_Page_Error was raised Unexpectedly
-or-
*** Aborting from Register because
!Lrm.Nonexistent_Page_Error was raised Unexpectedly
To fix the corrupt state file, use the Rcf.Refresh_View
command:
Rcf.Refresh_View (View => "<CURSOR>",
Retain_History => True,
Response => "<PROFILE>");
Fill in the View parameter with a naming expression
identifying all views in the closure of the application being
operated on.
If errors persist, contact your Rational Technical
Representative.
* For unknown reasons.
Intermittent Nonexistent Page Errors have been encountered on
heavily loaded machines. The typical message is of the form:
1: EXCEPTION_HANDLED Promotion failed with
!Lrm.System.Nonexistent_Page_Error,
from PC = #258D0D, #1D3
This error usually stops occurring after repeated commands.
This problem is being investigated.
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.
RATIONAL October 1991 9\f
RCF Release Information
This can prevent multiple host R1000 users with different remote
userids from operating on the same set of host views.
8.3. 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.4. 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.
8.5. Reverting to Simpler Method...
The following message may be generated during compilation:
!!! Reverting to simpler method of computing coding order in
... Compilation.Promote due to unexpected exception:
... !Lrm.System.Assertion_Error, from ... PC ...
This means that compilation will proceed with a more simplistic,
but correct, compilation ordering. Ignore this message.
8.6. 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.7. Library_Extensions and Host_Only Views
Many remote library operations fail on operations in Host_Only
views. The RCF should not attempt to do remote library operations
in Host_Only views. This problem will be fixed in a maintenance
release.
9. Documentation
Rational Remote Compilation Facility: User's Manual, PN
4000-00500, provides additional information for RCF users.
10 October 1991 RATIONAL\f
Release 1_0_3
10. Training
Rational Target Tools Training: Remote Compilation Facility
Fundamentals, PN 7000-00653, provides user training for the RCF.
RATIONAL October 1991 11\f
Release 1_0_3
Contents
1. Overview 1
2. RCF Components 1
3. Upgrade Impact 2
4. Prerequisites 2
5. New Features 3
5.1. Rebuilding Remote Libraries 3
5.2. Unit Compiler Options 3
5.3. Customizable Communications 3
5.4. Executing Remote Commands 3
5.5. Reusable Components 3
6. Changed Features 3
6.1. Packages Rcf and Rcf_Cmvc 4
6.2. RCF Compiler Job Name 4
6.3. Secondaries 4
6.4. Consistency Checking 4
6.5. Refreshing Views 4
6.6. Uploading Units 4
6.7. Removed Functionality 5
7. Limitations 5
7.1. Archive.Copy/Archive.Restore Operations 5
7.1.1. Archiving and Restoring Views 5
7.1.2. Copying and Restoring Secondaries 6
7.2. Configuration-Only Releases 6
7.3. Prompting For Passwords 7
7.4. Detached Operations 7
7.5. COTS Specifications 7
7.6. Rcf.Execute_Remote_Command 7
7.7. Telnet Logins 7
7.8. Registering Customizations 7
7.9. Attributes as Component Clauses of Rep Specs 7
7.10. Pragma Inline 8
7.11. Promoting Stubs to the Coded State 8
8. Known Problems 8
8.1. Nonexistent Page Error Exception 8
8.2. Remote Access Control 9
8.3. RCF Compiler Switch Modification 10
8.4. Compilation Warnings 10
8.5. Reverting to Simpler Method... 10
8.6. File Transfer Using FTP 10
8.7. Library_Extensions and Host_Only Views 10
9. Documentation 10
10. Training 11
RATIONAL October 1991 iii\f
RCF Release Information
iv October 1991 RATIONAL