|
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: 50699 (0xc60b)
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«
└─⟦203fa24b2⟧
└─⟦this⟧
Rational Environment Release Information
D_10_20_2 Release
\f
Copyright 1990 by Rational
February 1990 (Software Release D_10_20_2)
EXABYTE is a registered trademark of EXABYTE Corporation.
Rational and R1000 are registered trademarks and Rational
Environment is a trademark of Rational.
Sony is a registered trademark of Sony Corporation of America.
Sun Workstation is a registered trademark of Sun Microsystems,
Inc.
\f
Rational
3320 Scott Boulevard
Santa Clara, California 95054-3197
\f
D_10_20_2 Release
1. Overview
The purpose of the D_10_20_2 release of the Rational Environment
is to support a variety of new system configurations and
upgrades. Specifically, D_10_20_2 supports the following
configurations of the R1000:
* The Series 200 (Models 10, 20, and 40)
* The Series 300 System (300S)
* The Series 300 Coprocessor (300C) served by the Sun
Workstation
Note that D_10_20_2 does not support (and will not be installed
on) the Series 100 configuration.
D_10_20_2 supports two kinds of tape drive:
* The 9-track tape drive, which is standard on the Series 200
and an optional upgrade to the Series 300S.
* The 8-mm cartridge tape drive, which is standard on the Series
300S and 300C and an optional upgrade to the Series 200.
The 8-mm cartridge tape drive makes unattended system backups
possible by enabling a full system backup to be put onto a single
tape. Consequently, the operator is free to leave after
initiating the backup request and mounting the tape cartridge.
(In contrast, backups taken on a 9-track tape drive require the
operator's presence for the duration to mount additional tapes.)
No change has been made to the way backups are initiated-the
command interface remains the same and minimal changes appear in
the tape-mount request. Note that D_10_20_2 supports systems that
have either one or both kinds of tape drive.
D_10_20_2 also supports the optional expansion of memory from 32
megabytes to 64 megabytes to improve system performance. This
upgrade applies to Series 200, 300S, and 300C systems.
2. Configurations
The various possible combinations of configurations and upgrades
supported by D_10_20_2 are shown in Table 1 (the unsupported
Series 100 is included for comparison):
Table 1 Configurations and Upgrades Supported by D_10_20_2
R 2/16/90 1\f
Rational Environment Release Information
--------------------------------------
| | | | | |
| | 8-mm |9-Track|32-Mb | 64-Mb|
| | Tape | Tape |Memory| Memory|
| | Drive | Drive | | |
--------------------------------------
| | | | | |
|Series |N/A |Standar|Standa| N/A |
|100 | |d | rd | |
--------------------------------------
| | | | | |
|Series |Upgrade|Standar|Standa| Upgrad|
|200 | |d | rd | |
--------------------------------------
| | | | | |
|Series |Standar|Upgrade|Standa| Upgrad|
|300S |d | | rd | |
--------------------------------------
| | | | | |
|Series |Standar|N/A |Standa| Upgrad|
|300C |d | | rd | |
--------------------------------------
3. Compatibility
D_10_20_2 is compatible with all production versions of Rational
layered software products. Any software that can run on the
D_10_20_0 version of the Environment will run unmodified on
D_10_20_2. No upgrades of other layered products are included in
the D_10_20_2 release.
3.1. Compatible Layered Products
Design Facility: 2167 6_0_7
Design Facility: 2167A 6_2_4
Documentation Tools 10_2_9
Design Tools 10_2_9
CDF: 1750A 3_0_1 or later
CDF: 68K OS2000 4_1_3 or later
CDF: 68K Bare 3_0_1 or later
Mail 10_0_0 or later
Target Builder 9_4_4 or later
RXI 10_2 or later
2 2/16/90 R\f
D_10_20_2 Release
4. Upgrade Impact
The D_10_20_2 release can upgrade existing Series 200 and Series
300S machines. With the following exceptions, the D_10_20_2
release removes no functionality and has no impact on
user-written applications:
* D_10_20_2 installs a new implementation of
!Commands.Abbreviations.Do_Backup, which overwrites the
existing Do_Backup'Body. Because the existing Do_Backup'Body
may contain user customizations, its contents are saved as a
text file whose name is of the form
!Commands.Abbreviations.Do_Backup_Vnn, where nn is the unit's
default version number. The customizations then can be
transferred to the new implementation. See Sections 6.1 and
7.1 for more information about the new Do_Backup'Body.
* D_10_20_2 also installs a new implementation of
!Machine.Initialize, which overwrites the existing
Initialize'Body. Because the existing Initialize'Body may
contain user customizations, its contents are saved as a text
file whose name is of the form !Machine.Initialize_Vnn, where
nn is the unit's default version number. The customizations
then can be transferred to the new implementation. The new
implementation contains changes that facilitate the
installation of new releases.
* On R1000s running the D_11_1_3 release before upgrade, the
D_10_20_2 release removes the features (such as CMVC access
control) that were introduced as part of D_11_1_3.
R 2/16/90 3\f
Rational Environment Release Information
5. Known Problems
5.1. Lost Tape-Drive Allocation
In D_10_20_0, the tape drive remains allocated to a given session
until it is reallocated to another session. This behavior allows
you to perform consecutive tape operations without having to
respond to intervening tape-mount requests. In D_10_20_2, this
behavior remains the same for systems that have only one tape
drive; however, on systems with more than one tape drive, a mount
request is issued every time you open a tape, even if the desired
drive was already allocated to your session. This is because the
tape-mount operation doesn't know whether to reopen the allocated
drive or to allocate and open the other drive.
The additional mount requests will be most noticeable with
commands like Tape.Rewind and Tape.Unload (for example, when you
rewind or unload a tape after reading it). Furthermore, because
each mount request causes the tape to be rewound, consecutive
uses of the Tape.Display_Tape command must always assume that the
current tape position is at the beginning of the tape. The next
Environment release will allow tape-drive allocations to be
retained even on machines with multiple tape drives.
5.2. Unexpected Exception During Backup
Some Series 300C machines use disks that have very large
formatted capacities. On these machines, backups may fail to
complete because of a variety of unexpected exceptions. This
problem occurs on Series 300C machines for which one or more
disks has a formatted capacity greater than 655,776 disk blocks.
This problem is caused by an insufficient job page limit and can
be corrected by setting the job page limit to 16000 or higher.
The following steps provide a workaround to backup failures that
occurred because the default job page limit was insufficient:
1. Use the Operator.Disk_Space command to verify that the Series
300C has at least one disk with capacity greater than 655,776
disk blocks. (If no disk is larger than this, exceptions
raised by backup have a different cause. In this case, call
the Rational Customer Support Response Center.)
2. Modify !Commands.Abbreviations.Do_Backup'Body by inserting the
following statement immediately preceding the call to Backup
(the instantiated generic):
System_Utilities.Set_Page_Limit (16000);
4 2/16/90 R\f
D_10_20_2 Release
6. New Features
Several new features have been added in D_10_20_2. A generic
procedure has been added to package System_Backup. The purpose of
this generic procedure is to support the enhancements made to
procedure !Commands.Abbreviations.Do_Backup, which are described
in Section 7. Because the Do_Backup command provides a standard
instantiation for the generic procedure, customers do not have to
instantiate it themselves. However, if desired, customers can
change the standard instantiation to tailor certain aspects of
backup operation.
R 2/16/90 5\f
Rational Environment Release Information
Other new features include commands for managing the
authorization of Rational products that are now purchased on a
per-session basis. Under per-session pricing, a customer
purchases a specific number of concurrent usages that are
authorized for a given Rational product. For example, by
purchasing the Rational Environment under per-session pricing, a
customer obtains a total number of concurrent logins that are
authorized on their R1000s.
Two new procedures, Give_Up_Tokens and Accept_Tokens, enable such
a customer to distribute authorized usages of various products
among multiple R1000s. These usages may be distributed only
among the R1000s that reside within a given site, where the
notion of a site is defined in the Rational Price Guide. It is
important to note that, by definition, the R1000s in a given site
must be on the same support contract. Thus, if a customer has
three R1000s at a single site, and has purchased a total of 15
concurrent logins for the Environment, then that customer can use
the new procedures to distribute the logins on those three
machines (for example, to authorize 7 logins on one R1000 and 4
logins each on the others). However, if the same customer
purchases an additional R1000 and places it on a separate support
contract (thereby defining a different site for that R1000), none
of the original 15 logins will be transferable to the new
machine.
6.1. Generic Procedure System_Backup.Backup_Generic
generic
with procedure Backup_Starting (Is_Full : Boolean);
with procedure Backup_Finishing (Was_Successful :
Boolean);
procedure Backup_Generic (Variety : Kind;
Wait_Until : String);
Provides a more complete form of the System_Backup.Backup
procedure. The Backup_Generic procedure itself is not used
interactively; rather, it is instantiated and called with the
!Commands.Abbreviations.Do_Backup procedure.
The !Commands.Abbreviations.Do_Backup procedure passes parameters
to the Backup_Generic procedure to specify the kind of backup
to be performed (full, primary, or secondary), as well as the
time at which the backup is to begin. The backup tape can be
mounted at any time after the !Commands.Abbreviations.Do_Backup
procedure is entered and before the backup is scheduled to begin.
The Backup_Generic procedure provides formal procedures
(Backup_Starting and Backup_Finishing) through which various
system characteristics are set for the duration of the backup and
then restored afterward. Backup_Starting executes just before the
actual backup is scheduled to begin and Backup_Finishing executes
immediately after the backup finishes. As instantiated in the
6 2/16/90 R\f
D_10_20_2 Release
standard !Commands.Abbreviations.Do_Backup procedure, the
Backup_Starting formal procedure broadcasts a message to all
users informing them that a backup is beginning, saves the
current memory scheduler and snapshot settings, and then turns
off memory scheduling and snapshot warnings. The Backup_Finishing
formal procedure restores memory scheduling and snapshot warnings
according to the saved settings.
The system manager can edit the body of
!Commands.Abbreviations.Do_Backup to change the effect of these
two formal procedures. One possibility is to use Backup_Finishing
to send mail when the backup has completed. Another possibility
is to use Backup_Starting and Backup_Finishing to turn off the
disk collection daemon for the duration of the backup. Doing so
will prevent disk collection from interfering with the backup.
However, turning off disk collection is recommended only for
backups made on the 8-mm cartridge tape drive because such
backups require significantly less time than those made on
9-track tape drives. In any case, turning off disk collection is
not recommended if the disks are very full.
6.2. !Commands.System_Maintenance.Revn.Accept_Tokens
procedure Accept_Tokens
(Donations : Positive;
Resulting_Count : Positive;
Code : String := ">>Give_Up_Tokens
Result<<";
Product : String := "Logins";
Response : String := "<PROFILE>");
Completes the transfer of authorized usages for the specified
product from one R1000 to another.
When a customer purchases a Rational product on a per-session
basis, the customer obtains a specific number of authorized
usages for that product. Each authorized usage is represented
internally as a token. These tokens represent the rights of
individual users to use a particular product; the number of
tokens on a given R1000 determines the number of users that can
use that product concurrently. The Give_Up_Tokens and
Accept_Tokens procedures allow the customer to distribute tokens
(product usages) among multiple R1000s within the same site. By
default, the Give_Up_Tokens and Accept_Tokens procedures transfer
tokens that represent authorized logins to the Rational
Environment.
The transfer of tokens between machines is initiated by the
Give_Up_Tokens procedure on the donating machine. Among other
things, the Give_Up_Tokens procedure displays a call to the
Accept_Tokens procedure in which specific parameter values are
filled in:
R 2/16/90 7\f
Rational Environment Release Information
* The values of the Donations and Resulting_Count parameters
reflect the input that was given to the Give_Up_Tokens
procedure. (These parameter values specify the number of
transferred tokens and the total number of tokens on the
receiving machine, respectively.)
* The value of the Code parameter is a unique authorization code
valid only for the current day. Without this code, the
transfer cannot be completed.
The displayed call to Accept_Tokens must then be copied to the
receiving R1000 and executed there. (Alternatively, the call can
be executed remotely using the Remote.Run procedure.) As a
result, the new number of authorized tokens is recorded in the
receiving machine's error log, and the new tokens are made
available immediately.
Restrictions:
* The Accept_Tokens procedure must be run on the same day as the
Give_Up_Tokens procedure.
* The donating and receiving machines must reside within a
single site.
8 2/16/90 R\f
D_10_20_2 Release
6.3. !Commands.System_Maintenance.Revn.Give_Up_Tokens
procedure Give_Up_Tokens
(Donations : Positive;
Remote_Machine_Id : Long_Integer;
Resulting_Remote_Count : Positive;
Product : String := "Logins";
Response : String :=
"<PROFILE>");
Initiates a transfer of authorized usages for the specified
product from one R1000 to another.
When a customer purchases a Rational product on a per-session
basis, the customer obtains a specific number of authorized
usages for that product. Each authorized usage is represented
internally as a token. These tokens represent the rights of
individual users to use a particular product; the number of
tokens on a given R1000 determines the number of users that can
use that product concurrently. The Give_Up_Tokens and
Accept_Tokens procedures allow the customer to distribute tokens
(product usages) among multiple R1000s within the same site. By
default, the Give_Up_Tokens and Accept_Tokens procedures transfer
tokens that represent authorized logins to the Rational
Environment.
The Donations parameter specifies the number of authorized tokens
to be transferred from the current machine. The Remote_Machine_Id
parameter specifies the R1000 that is to receive the transferred
tokens. For verification, the Resulting_Remote_Count parameter
must specify the number of authorized tokens that will exist on
the receiving R1000 as a result of the transfer.
The Give_Up_Tokens command displays a call to the Accept_Tokens
procedure with the appropriate parameter values filled in. The
transfer is completed when the Accept_Tokens call is copied to
the receiving R1000 and executed there.
In addition to displaying the required call to the Accept_Tokens
procedure, the Give_Up_Tokens procedure records the initiated
transfer in the donating R1000's error log.
Restrictions:
* This command requires operator capability.
* The Give_Up_Tokens procedure fails if the transfer would leave
the donating machine with fewer authorized tokens than are
currently in use.
* The same machine may not both give up and accept tokens in the
same day.
* The donating and receiving machines must reside within a
single site.
R 2/16/90 9\f
Rational Environment Release Information
Example
Assume that you have two R1000s at your site and a total of 10
authorized logins that are currently distributed so that each
R1000 has 5. Assume further that you want to transfer 3 logins
from one machine to the other, resulting in 8 logins on the other
machine. The Give_Up_Tokens procedure initiates the transfer:
Give_Up_Tokens (Donations => 3,
Remote_Machine_Id => destination_machine_id,
Resulting_Remote_Count => 8);
10 2/16/90 R\f
D_10_20_2 Release
As a result, this procedure displays the Accept_Tokens procedure
with specific parameter values in the current output window. This
display includes the authorization code to complete the transfer:
Accept_Tokens (Donations => 3,
Resulting_Count => 8,
Code => "a_unique_authorization_code");
To complete the transfer, you now need to copy the displayed
Accept_Tokens procedure into a file, archive it to the
destination machine, and enter it in a Command window there.
(Alternatively, the call to Accept_Tokens can be executed
remotely using the Remote.Run procedure.)
7. Changes from D_10_20_0
7.1. System Backup Changes
A number of Environment commands are available for initiating
backups. Most users use one of the standard backup procedures in
!Commands.Abbreviations: Do_Backup, Full_Backup, Primary_Backup,
or Secondary_Backup. The Do_Backup procedure initiates the kind
of backup specified by the Variety parameter and delays the
backup until the time specified by the Starting_At parameter. In
addition, Do_Backup adjusts certain system settings for the
duration of the backup. The other three backup procedures are
specialized forms of Do_Backup, each initiating a specific kind
of backup (full, primary, or secondary).
The specifications for all backup commands remain as they are in
D_10_20_0, so operators will continue to initiate backups the
same way. However, the implementation of backup operations has
been enhanced in the present release. Note that the changes
described below for the Do_Backup procedure apply to the
specialized backup commands as well, because each of these
commands calls Do_Backup.
7.1.1. Improved Do_Backup Implementation
The procedure !Commands.Abbreviations.Do_Backup has been enhanced
to take advantage of the new generic procedure
!Commands.System_Backup.Backup_Generic. In particular,
Do_Backup'Body has been rewritten to instantiate the formal
procedures associated with the generic as follows:
* The Backup_Starting formal procedure, which executes as the
backup begins, broadcasts a message announcing the backup to
all users, saves the current memory scheduler and snapshot
settings, and turns off memory scheduling and snapshot
warnings.
R 2/16/90 11\f
Rational Environment Release Information
* The Backup_Finishing formal procedure, which executes as the
backup ends, restores memory scheduling and snapshots using
the saved settings.
The system manager can edit Do_Backup'Body to further customize
system settings for the duration of backups.
12 2/16/90 R\f
D_10_20_2 Release
7.1.2. Support for 8-Millimeter Cartridge Tape Drive
All backup operations (including those in package System_Backup)
have been enhanced to take backups on the 8-mm cartridge tape
drive as well as on the 9-track tape drive. Each backup taken on
the 8-mm cartridge tape drive requires only a single tape
cartridge, in contrast to the multiple tape reels required for
backups taken on a 9-track tape drive. Consequently, the 8-mm
cartridge tape drive permits unattended backups because the
operator can leave after entering the Do_Backup command and
mounting the tape. Unattended backups also take significantly
less time because the time spent changing tapes is eliminated.
For example, a backup that takes 8 hours to complete on a 9-track
tape drive may take as little as 4 hours on an 8-mm cartridge
tape drive.
When the 8-mm cartridge tape drive is used, slight differences
appear in the backup tape-mount request. In particular, the
tape-mount request no longer prompts for a separate "blue tape";
instead, a backup index is appended to the data on the single
8-mm tape. (However, during a backup restoration, the tape-mount
request still prompts for a "blue tape" to indicate when the sole
backup tape cartridge is to be mounted.) Progress messages are
displayed in the current output window; these messages appear as
the backup starts and finishes each disk volume.
7.1.3. Guidelines for Choosing Tape Size
To ensure unattended backups when using the 8-mm cartridge tape
drive, it is recommended that you choose a single tape large
enough to hold the entire backup. Guidelines for choosing the
appropriate tape size are given in Table 2. To use this table,
you need to know the total number of disk blocks that are used on
your machine. You can obtain this information using the
Operator.Disk_Space command. Note that a tape larger than the
minimum can always be used.
Tape sizes are given in several ways, depending on the brand of
tape. EXABYTE tapes are identified by their length in meters.
Sony tapes are identified by their cartridge type, which
correlates to minutes of playing time (for example, P6-15MP and
P5-15MP indicate 15-minute tapes). P6 mode tapes, which are used
in the United States, have a smaller capacity in megabytes than
P5 mode tapes, which are used (at least) in Europe. Both P5 and
P6 tapes are listed in the table.
R 2/16/90 13\f
Rational Environment Release Information
Table 2 Minimum 8-mm Cartridge Tape Size for Full Backups
----------------------------------------
| | |
|Total Number| |
|of |Recommended Minimum Tape |
|Disk Blocks |Size |
|Used | |
----------------------------------------
| | |
| 0-235,500|Sony P6-15MP Video 8 |
| |Sony P5-15MP Video 8 |
| |EXABYTE 8MM Data Cartridge |
| |15 m |
----------------------------------------
| | |
|235,501-471,|Sony P6-30MP Video 8 |
| 500|Sony P5-30MP Video 8 |
| |EXABYTE 8MM Data Cartridge |
| |54 m |
----------------------------------------
| | |
|471,501-943,|Sony P6-60MP Video 8 |
| 500|Sony P5-60MP Video 8 |
| |EXABYTE 8MM Data Cartridge |
| |54 m |
----------------------------------------
| | |
| 943,501-1,|Sony P6-90MP Video 8 |
| 415,000|Sony P5-60MP Video 8 |
| |EXABYTE 8MM Data Cartridge |
| |112 m |
----------------------------------------
| | |
|1,415,001-1,|Sony P6-120MP Video 8 |
| 887,000|Sony P5-90MP Video 8 |
| |EXABYTE 8MM Data Cartridge |
| |112 m |
----------------------------------------
| | |
|1,887,001 or|May require multiple |
| greater|cartridges for backup |
----------------------------------------
As the table indicates, machines with greater than 1,887,001 used
disk blocks may require multiple tapes for backups. However,
because the estimates in the table are conservative, it may in
fact be possible to put an entire backup for such a machine on a
single 120-minute (or 112-meter) tape.
As an example, assume that Operator.Disk_Space produces the
following display:
14 2/16/90 R\f
D_10_20_2 Release
Volume Capacity Available Used % Free
====== ======== ========= ======= ======
1 625482 257433 368049 41
2 655776 255030 400746 38
3 655776 247569 408207 37
4 655776 220230 435546 33
Total 2592810 980262 1612548 37
This machine has a total of 1,612,548 used disk blocks.
Therefore, this machine requires a tape such as a Sony P6-120MP
tape for a single-tape backup.
R 2/16/90 15\f
Rational Environment Release Information
7.1.4. Backups on Systems with Two Tape Drives
Series 200 and Series 300S machines can optionally have both a
9-track tape drive and an 8-mm cartridge tape drive. When two
kinds of tape drive are available, the system manager must decide
which tape drive to use for system backups. It is important to
make this decision early for two reasons:
* It is recommended that the tape drive used for backups should
be made the default tape drive (drive number 0). Doing so
simplifies the operator's response to the backup tape-mount
request, so that only a carriage return is needed for the On
which drive? prompt. (See Section 7.2.1.)
* Incremental backups (primary and secondary) must be made on
the same kind of tape drive as the full backup on which they
are based. Full and incremental backups made on different
kinds of tape drive are incompatible and cannot be restored
together. Thus, if you make a full backup on an 8-mm cartridge
tape drive, you must make all subsequent primary backups on
that tape drive. If you want to switch to the 9-track tape
drive, you must wait until the next scheduled full backup.
7.1.5. Restoring Backups
Backups taken on 9-track tape drives span multiple tapes,
including one or more tapes containing the data and one tape
(often called the "blue tape") containing the backup index.
During restoration of such a backup, the tape-mount request
prompts you for the blue tape first so that the backup index can
be read first. The tape-mount request then prompts you for the
remaining tapes in order.
Backups taken on 8-mm cartridge tape drives usually require only
one tape, in which case the backup index is written after the
data on a single tape. When, during restoration, you are prompted
for a blue tape, you need to mount the sole tape cartridge. The
restoration operation skips through this tape until the backup
index is found. After reading the backup index, the restoration
operation automatically returns to the beginning of the tape to
read the data.
On very large systems, a backup taken on an 8-mm cartridge tape
drive may require multiple tapes. The backup operation writes to
these tapes as if they were logically a single tape-that is, the
backup index is written immediately following the data.
Consequently, restoration of multitape backups is a two-pass
process. The tape-mount request first prompts you to mount each
tape in sequence so that the tapes can be skipped through until
the backup index is found. Then the tape-mount request prompts
you to mount the sequence again so that the tapes can be read and
the data restored.
16 2/16/90 R\f
D_10_20_2 Release
During restoration on an 8-mm cartridge tape drive, progress
messages appear on the operator's console. These messages report
when the backup index has been located and when it is being
processed; subsequent messages report when the backup data has
been located and when it is being processed.
R 2/16/90 17\f
Rational Environment Release Information
7.1.6. Bug Fixes Pertaining to Backup
The new implementation of Do_Backup corrects several bugs from
D_10_20_0. In particular, the time specified by the Starting_At
parameter is now absolute rather than relative to the time at
which the tape is mounted. Consequently, the actual backup now
begins at the Starting_At time no matter when the tape is mounted
(as long as it is mounted before the backup is scheduled to
start). Furthermore, because of the new Backup_Starting formal
procedure, the message announcing the backup is now displayed
when the actual backup begins rather than at the time the
Do_Backup command is executed.
Another important bug fix is that secondary backups now work
correctly. Secondary backups are based on primary (or other
secondary) backups, just as primary backups are based on full
backups. In previous releases, secondary backups didn't work.
7.2. General Tape-Related Changes
Environment tape interfaces now accommodate the 8-mm cartridge
tape drive in addition to the 9-track tape drive.
7.2.1. Default Tape Drive
Many prompts and commands require that you specify a tape drive
using its logical tape-drive number. The default value for these
prompts and commands is always drive number 0. Therefore, by
convention, the tape drive whose number is 0 is the default
drive.
When a machine has both an 8-mm cartridge tape drive and a
9-track tape drive, the system manager must decide which drive is
to serve as the default. The default drive is then assigned drive
number 0, and the remaining drive can be assigned a drive number
from 1 through 3. The default drive should be the tape drive that
will be used for system backups.
Logical tape-drive numbers are assigned using the IOP ENVIROMENT
menu during the boot process. The initial assignments are usually
set by Rational technical representatives, although system
managers can change the assignments during subsequent system boot
processes. System managers who want to do this should contact
their Rational technical representatives for assistance.
7.2.2. Package Tape
Many commands in package Tape have a Drive parameter through
which the user may specify the tape-drive number for the desired
drive. On machines with only one tape drive, these parameters
accept only the value 0; on machines with multiple drives, this
parameter accepts any number that has been assigned to a drive.
18 2/16/90 R\f
D_10_20_2 Release
7.2.3. Tape-Mount Requests
Commands that require tape operations initiate a tape-mount
request on the operations console. Such commands include
Tape.Read, Tape.Write, Archive.Save, and Archive.Restore. When
these commands are entered on R1000s that have two tape drives,
the resulting tape-mount request contains certain prompts and
fields that don't appear on machines with only one tape drive. In
particular, the tape-mount request on a two-drive machine
displays:
R 2/16/90 19\f
Rational Environment Release Information
* The On which drive? prompt asking you to specify the logical
number of the tape drive on which the tape operation is to
take place. (Note that in previous releases, this prompt
appeared on machines with one tape drive, as well.)
* A Kind of Drive field along with the label information that is
displayed about the mounted tape. The kind of drive is given
as 8mm for 8-mm cartridge tape drives and 9_TRACK for 9-track
tape drives.
For example, assume that a Series 200 has been upgraded so that
it has an 8-mm cartridge tape drive as well as a 9-track tape
drive, and that the 8-mm cartridge tape drive is tape drive 0
(the default) while the 9-track tape drive is tape drive 3. The
following is an excerpt from a tape-mount request in which the
default tape drive is specified:
Please Load Tape
(Kind of Tape => CHAINED_ANSI,
Direction => WRITING,
Volume Set Name => BACKUP, 07-NOV-89 16:47:23 3)
Is Tape mounted and ready to read labels? yes
On which drive? [ 0]
Info on mounted tape is
(Kind of Drive => 8MM,
Kind of Tape => UNLABELED_TAPE,
Writeable => TRUE)
OK to overwrite volume? [YES]
What should the volume id handling mode be? [AUTO_GENERATE]
Volume id of tape is now: 007100
In contrast, the following excerpt is from a tape-mount request
in which the nondefault drive 3 is specified:
Please Load Tape
(Kind of Tape => CHAINED_ANSI,
Direction => WRITING,
Volume Set Name => BACKUP, 07-NOV-89 16:47:23 3)
Is Tape mounted and ready to read labels? yes
On which drive? [ 0] 3
Info on mounted tape is
(Kind of Drive => 9_TRACK,
Kind of Tape => UNLABELED_TAPE,
Writeable => TRUE)
OK to overwrite volume? [YES]
What should the volume id handling mode be? [AUTO_GENERATE]
Volume id of tape is now: 007100
.
20 2/16/90 R\f
D_10_20_2 Release
7.2.4. Package Archive
The Archive.Save and Archive.Restore commands can write the Data
and Index files to either of two types of devices-namely, a tape
or an Environment library. The Device parameter determines which
type of device is to be used. The default value for this
parameter ("MACHINE.DEVICES.TAPE_0") is a special value that
causes a tape-mount request to appear on the operations console.
Any other string is interpreted as the name of an Environment
library.
Note that in the present release, you cannot use the Device
parameter to specify a particular tape drive. Instead, the choice
of tape drive must be made as part of the tape-mount request (see
Section 7.2.3, above). Thus, the special value
"MACHINE.DEVICES.TAPE_0" is appropriate for any tape operation,
even when a tape drive with a number other than 0 is to be used.
If you specify a string such as "Machine.Devices.Tape_3", a
library named Machine.Devices.Tape_3 is created in the current
context and used as the device. It is anticipated that in a
future release the Device parameter will accept naming
expressions that reference specific tape drives.
7.2.5. User-Written Applications
User-written applications written against Device_Independent_Io
must be instructed to open specific devices for reading or
writing. When such applications are to perform tape operations,
they must be passed naming expressions that reference a
particular tape drive by its logical number. For example, the
name "!Machine.Devices.Tape_0" references the default tape drive;
the name "!Machine.Devices.Tape_3" references tape drive number
3. (These names are not to be confused with the special value
used in the Archive commands; see Section 7.2.4, above.) The
drive that is specified to the application must also be specified
during the subsequent tape-mount request. Note that applications
written against Tape_Tools do not require names that reference
specific tape drives; instead, the drive to be used is specified
during the tape-mount request.
When writing tape-related applications, bear in mind that tape
marks written on 8-mm cartridge tapes occupy much more space than
tape marks written on 9-track tapes. In particular, each tape
mark written on an 8-mm cartridge tape occupies 2 megabytes of
space. Thus, when an application writes tape marks between files,
writing a large number of small files can easily exhaust the
space on a single tape.
7.2.6. Tape-Related Messages in the Error Log
In !Machine.Error_Logs.Log@, log entries pertaining to tape
operations now reflect the type of drive. When the type of drive
is 9 track, the entry also reports the density. Following are
R 2/16/90 21\f
Rational Environment Release Information
examples of messages reporting each kind of tape drive and
density:
13:34:33 --- Tape_Handling Tape_Mounted Volume_Id=TEST1 ,
Type_Of_Drive=9Track, Density=PE_1600CPI
13:34:33 --- Tape_Handling Tape_Mounted Volume_Id=TEST2 ,
Type_Of_Drive=9Track, Density=GCR_6250CPI
12:37:05 --- Tape_Handling Tape_Mounted Volume_Id=012601,
Type_Of_Drive=8mm
22 2/16/90 R\f
D_10_20_2 Release
7.2.7. DFS Backup
Backups of the Diagnostic File System (DFS) can be made on the
8-mm cartridge tape drive. If the DFS backup is to be made on a
tape drive other than the default drive 0, the nondefault drive
number must be specified. For example, to specify drive number 3,
append /unit=3 to the backup command:
CLI> backup/unit=3
Omitting the drive number causes the DFS backup to be taken on
drive 0:
CLI> backup
7.3. Changes Pertaining to Login Limits
The number of permitted concurrent logins (sessions) for each
Series 300S and 300C is set at the factory. If a user attempts to
log in after the maximum number has been reached, the following
message will appear:
Login denied - resource restriction
An existing session will have to be logged out before that user
can log in.
7.4. Changes Pertaining to EEDB
The special character "$" can now be used as an argument to EEDB
commands to reference the currently running release.
8. Documentation
No new documentation is issued with the D_10_20_2 release.
The existing online and hard-copy documentation for package
System_Backup has no reference entry for the generic procedure
Backup_Generic. (The existing documentation is found in Rev. 3.0
of the System Management Utilities (SMU) book of the Rational
Environment Reference Manual.) Until the SMU book is updated,
this release note serves as documentation for
System_Backup.Backup_Generic.
9. Training
No new training is issued with the D_10_20_2 release.
R 2/16/90 23\f
D_10_20_2 Release
Contents
1. Overview 1
2. Configurations 1
3. Compatibility 2
3.1. Compatible Layered Products 2
4. Upgrade Impact 3
5. Known Problems 4
5.1. Lost Tape-Drive Allocation 4
5.2. Unexpected Exception During Backup 4
6. New Features 5
6.1. Generic Procedure System_Backup.Backup_Generic 6
6.2. !Commands.System_Maintenance.Revn.Accept_Tokens 7
6.3. !Commands.System_Maintenance.Revn.Give_Up_Tokens 9
7. Changes from D_10_20_0 11
7.1. System Backup Changes 11
7.1.1. Improved Do_Backup Implementation 11
7.1.2. Support for 8-Millimeter Cartridge Tape Drive 13
7.1.3. Guidelines for Choosing Tape Size 13
7.1.4. Backups on Systems with Two Tape Drives 16
7.1.5. Restoring Backups 16
7.1.6. Bug Fixes Pertaining to Backup 18
7.2. General Tape-Related Changes 18
7.2.1. Default Tape Drive 18
7.2.2. Package Tape 18
7.2.3. Tape-Mount Requests 19
7.2.4. Package Archive 21
7.2.5. User-Written Applications 21
7.2.6. Tape-Related Messages in the Error Log 21
7.2.7. DFS Backup 23
7.3. Changes Pertaining to Login Limits 23
7.4. Changes Pertaining to EEDB 23
8. Documentation 23
9. Training 23
R 2/16/90 iii\f
Rational Environment Release Information
iv 2/16/90 R