 |
» |
|
|
|
1. back up your system with ASAVE.
Make sure you have a memory-based ARSTR system that you can use to
restore the ASAVE of your system. Refer to Chapter 3 of the RTE-A
Backup and Disk Formatting Reference Manual, version 6.2, part number
92077-90249, for details on ASAVE and ARSTR.
2. copy the 6.2 version of the RTE-A and VC+ products from tape to /RTE_A
and /VCPLUS.
A. Begin by clearing some room on a CI volume and creating the
global directories /RTE_A and /VCPLUS. Create the subdirectory
/GEN/REV62 to hold the answer, system, and snap files. If /RTE_A
and /VCPLUS already exist, then purge everything in them
(including everything in subdirectories) before loading the 6.2
software onto the system.
Example:
CI> crdir /rte_a
CI> crdir /vcplus
CI> crdir /gen/rev62
/RTE_A will require about 48500 blocks, and /VCPLUS will require
about 16200 blocks.
If you are planning to install any subsystems from your
customized subsystem tape (for example, networking, FORTRAN,
DEBUG, and so forth) be sure to create or clear the appropriate
directories.
B. Use FST to copy the software off the update tape(s) to the newly
created or cleared directories. For additional details on FST,
consult the RTE-A Backup and Disk Formatting Utilities Reference
Manual, part number 92077-90249.
Copy the RTE-A Operating System files from the operating system
update tape:
CI> FST mt|re @|ve|go
For VC+ and other subsystems, restore the software from your
customized subsystem tape.
3. modify your answer file for all 6.0/6.1/6.2 changes.
Follow the instructions below to modify your answer
file for all 6.0/6.1/6.2 changes. These instructions
were excerpted directly from the respective Communicators
for those revisions.
5.27 changes
There are no generation changes required at the 5.27 update
Two programs for NS1000, however, are no longer used.
These are: TIMER and READR.
6.0 changes
A. New modules: /vcplus/%ENVRN
If the target system is to perform the EXEC(39) call, which
performs environment variable look-ups for various utilities
such as LI, then this module must be relocated in the "System
Generation" section of the answer file. This module is
partionable; to partition, use the "PA,ENVRN" command in your
answer file. See the RTE-A System Generation and Installation
manual for the number of words required in the tag area.
B. SCSI disks:
The 6.0 revision of DDQ30_GEN.REL has two new model names, and
wo model names have been changed. These are for the C1701A
Model 650/A Optical Disk
It is recommended that you use the new model names, below. Which
model name you use depends on which media you use. These new
model are used to configure the media as all one LU.
| model | description |
| M650A_1 | use to make 92279A media all one LU |
| M650A_3 | use to make 92280A media all one LU |
The 6.0 revision of DDQ30_GEN.REL changed two model names to be
consistent with the naming convention that ":A" is used for the
large LU and ":B" is used for the small LU. The changes are:
| old model | new model |
| M19MB_3:A | M19MB_3:B |
| M51MB_3:B | M51MB_3:A |
C. NS-ARPA/1000 and ARPA/1000 changes:
The 6.0 revisions of NS-ARPA/1000 or ARPA/1000 software MUST be
used in conjunction with the 6.0 RTE-A operating system.
The file /NS1000/REL/NSPEC.REL no longer exists, and it should
not be relocated. The library search command:
SE /NS1000/LIB/NSLIB.LIB DSGLO
is no longer needed and can be deleted. For ARPA/1000 systems, the
global directory for these modules is /ARPA1000.
Module NSABP is now partitionable. File /NS1000/REL/NSABP.REL
may be relocated into an OS partition.
D. X.25 changes:
The file /X25/REL/#X25A.REL no longer exists. The entry points it
contained are now in VCTR. Delete the command:
RE /X25/REL/#X25A.REL
from your answer file
E. Miscellaneous:
These changes are unlikely to affect the answer file for
most systems:
Module SAM is no longer optional. %SAM must be relocated; module
"SAM.." is no longer available in $SYSA. Very few systems are
currently generated without SAM.
Five words of XSAM (or SAM if no XSAM) will be consumed per ID
segment. If there is insufficient XSAM/SAM for this purpose, then
the system will not boot.
The real VEMA module must be relocated (from %VEMA, as opposed to
"VEM.." from $SYSA) if the system is to use the new Large or
Extended models of EMA/VMA. This will not affect any host that
currently runs D.RTR, since the real VEMA must already be used.
The required tag area size is slightly higher; see the RTE-A
System Generation and Installation Manual for the number of words
required for each partitioned module.
Various restrictions on the values of class buffer limits (formerly)
known as spool buffer limits) have been removed. See Chapter 4 for
more information.
6.1 changes
A. SCSI Disks.
The 6.1 revision of DDQ30_GEN.REL has one new model name as
indicated below:
| Model | Description |
| M1GB | use for large disk LU (1 gigabyte) |
B. LAN Driver (%ID*67).
Prior to 6.1, the LAN driver required one IFT and two DVTs for
each LAN card. For example, your pre-6.1 answer file entries
for the LAN driver may have looked like:
ift,/rte_a/%id*67,sc:37b
dvt,/rte_a/%gen67,M67:1:lu:90
dvt,/rte_a/%gen67,M67:0:lu:91
The 6.1 revision of the LAN driver only requires one IFT and one
DVT for each LAN card. In addition, the %GEN67 file is no longer
needed.
If you use LAN, modify your 6.1 answer file to reflect the changes
for 6.1. Example entries for the LAN driver for 6.1 are as follows:
ift,/rte_a/%id*67,sc:37b
dvt,,,lu:90,DT:67b,TO:200
Refer to Chapter 4 for more information on the LAN driver
modifications.
6.2 changes
(Refer to the "Generation Considerations" section in Chapter 4 of
the Communicator for more details.)
A. SCSI Disks.
The 6.2 revision of DDQ30_GEN.MAC has added information to help
you generate the new C2490A 2Gb SCSI disk drive into your system
Information for the HP C1716T Optical Disk Drive has also been
added. This drive can accommodate two different physical media,
the HP 92880T Optical Disk Cartridge which has 1024-byte sectors
and the HP 92279A Optical Disk Cartridge which has 512-byte
sectors.
Model information is as follows:
| Model | Description |
| M512MB:0 | C2490A 2 Gigabyte SCSI disk drive |
| M512MB:1 | |
| M512MB:2 | |
| M497MB:A | |
| M1.2GB_1 | C1716T optical disk drive with 92279T Optical Disk Cartridge (with 512-byte sectors) |
| M1.3GB_3 | C1716T optical disk drive with 92280T Optical Disk Cartridge (with 1024-byte sectors) |
IMPORTANT:
When generating MO drives into the system, bit 15 of driver
parameter 2 should be clear for the C1701A. For all other
MO drives, however, this bit should be set. Failure to do
so could cause catastrophic loss of data on other devices
attached to the same SCSI bus.
B. DS/1000-IV and NS-ARPA/1000 DS Compatible Services
Memory-based systems which use APLDR to load programs into memory
from remote FMGR files no longer need the operating system module
$MWB1. The file %$MWB1 has been deleted from the RTE-A (92077A)
product. The following command to relocate %$MWB1 should be
deleted from the generation answer file:
re /rte_a/%$mwb1,, APLDR inter-map data move
4. generate your new 6.2 system.
The 6.0 revisions of three programs must be used to upgrade to 6.2,
RTAGN, LINK, and LINDX. These programs will run on
your 5.27 system, and should be loaded using your existing
5.27 system libraries and snap file. The .RUN files should be
placed in a temporary directory, where they can be used for
installation purposes only -- don't put them in /PROGRAMS/, since
the programs are incompatible with the 5.27 system.
A. Use the upgrade60.cmd file to load these programs.
A command file, upgrade60.cmd, is supplied with RTE-A to ease
the loading of 6.0 versions of software needed for RTE-A 6.2
installation. This command file is to be run with your working
directory set to a temporary directory created for this purpose.
The directory may safely be /SCRATCH, if desired.
The .RUN files created by this command file are named RTAGN60.RUN
LINK60.RUN, LINDX60.RUN. Each is created in the temporary
directory. Once this command file completes, these programs,
RTAGN, LINK and LINDX should be RP'ed before generating new
system and before linking any programs for the new system.
crdir /tempdir LU
wd /tempdir
tr /rte_a/upgrade60 [rte_a_dir]
where:
| LU | = the LU for your temporary directory. |
| rte_a_dir | = the directory where the RTE-A 6.2 software resides. The default is /RTE_A. |
NOTE
MACRO will most likely fail with an undefined external. This
can be ignored as we will not be using MACRO.RUN at this time.
Also, BUILD is not required at this time.
Now that the .RUN files have been created, they can be RP'ed as
follows:
rp /tempdir/rtagn60 rtagn
rp /tempdir/link60 link
rp /tempdir/lindx60 lindx
Note: once the 6.2 software installation is complete, you will
want to remove these ID segments. For example:
of rtagn id
of link id
of lindx id
When the temporary 6.0 programs are no longer needed, the contents
of the temporary directory may be purged.
B. Generate your 6.2 system as follows:
CI> wd /gen/rev62
CI> rtagn answer.ans - - -
This will create 'answer.sys' 'answer.snp' and 'answer.lst'
Now we need to create the minimum 6.2 programs in order
to boot a 6.2 system.
Create 6.2 programs directory:
CI> crdir /progs62 lu
Create a new $BIGLB. This is needed to load the 6.2 programs
To save your existing libraries, rename the directory.
CI> rn /libraries /libs527
CI> crdir /libraries lu
CI> wd /rte_A
CI> merge -l biglb.mrg /libraries/$biglb.lib
Copy the new LINK catalog file to /catalogs:
CI> co /rte_a/link.c000 /catalogs/@
Load crucial 6.2 programs (IMPORTANT: Use 6.0 LINK Rp'ed)
| CI> link ddrtr.lod | /progs62/drtr | /gen/rev62/answer.snp |
| CI> link link.lod | /progs62/link | /gen/rev62/answer.snp |
| CI> link cinc.lod | /progs62/ci | /gen/rev62/answer.snp |
| CI> link #cix | /progs62/cix | /gen/rev62/answer.snp |
| CI> link #is | /progs62/is.run | /gen/rev62/answer.snp |
| CI> link dderr.lod | /progs62/derr | /gen/rev62/answer.snp |
| CI> link lindx.lod | /progs62/lindx | /gen/rev62/answer.snp |
| CI> link ktest.rel | /progs62/ktest | /gen/rev62/answer.snp |
| CI> link ask.rel | /progs62/ask | /gen/rev62/answer.snp |
| CI> link merge.lod | /progs62/merge | /gen/rev62/answer.snp |
| CI> link mpack.lod | /progs62/mpack | /gen/rev62/answer.snp |
Useful, but not required:
| CI> link dl.lod | /progs62/dl | /gen/rev62/answer.snp |
| CI> link li.lod | /progs62/li | /gen/rev62/answer.snp |
5. if running DATAPAIR/1000, then run PREPAIR on the 6.2 system.
As usual, systems running DATAPAIR must be processed by the
PREPAIR utility before booting.
6. vopy new system and snap files to the bootable LU.
For a bootable LU 16 as a FMGR cartridge, use the following:
CI> wd, /gen/rev62
CI> co answer.snp snp62::16
CI> co answer.sys sys62::16
If your bootable LU is a CI volume, or if you are booting from a CI
volume but your bootex is on a FMGR cartridge, then you will need to
copy the system and snap files to the /system directory.
7. prepare to boot the 6.2 minimum system.
A. Setup the BOOT.CMD file on your bootable LU that
references the 6.2 System and Snap files.
Do not execute the welcome file at this time
(use ST,1 in boot.cmd)
* Boot 6p2 from LU16
* Define system and snap files
ec
sy,sys62
sn,snp62
**************************************************
* Mount cartridges that contain needed directories
**************************************************
*
*
mc 51 ,,,, /programs and /system directory
*
***********************************
* Define initially RP'ed programs
***********************************
rp /programs/drtr d.rtr
rp,/programs/derr,d.err
*
rp /programs/ci cm
rp,/programs/cix
rp,/programs/ci
st,1 ! DO NOT EXECUTE WELCOME FILE
*
en
*
***********************
* Define swap file
***********************
sw,swap.swp::system:1:2048
*
*
end
B. Install the 6.2 BOOTEX on your bootable LU.
The 6.2 revision of BOOTEX is NOT backwards-compatible with your
5.2/5.27 system. If you still wish to boot your old system, you
will need a second copy of BOOTEX on your disk.
The 6.2 revision of /RTE_A/BOOTEX must be used as the "source"
file to the INSTL utility (INSTL may be Rev.5020 or Rev.5270)
If an earlier revision of BOOTEX is used, an error
similar to "All snap entry points not found: $SHSZ" is given
after the "SN" command in the BOOT.CMD file. The FPUT utility
may be run to put down your BOOTEX file. Refer to the RTE-A
Utilities Manual for more information on how and when to use
the INSTL and FPUT utilities.
The following is an example of how this could be done for a CI LU
16; your LU and file names may be different.
CI> instl,/gen/rev62/answer.snp,/gen/rev62/answer.sys,
/gen/rev62,
/gen/rev62/bootex,16,/rte_a/bootex
CI> fput,/gen/rev62/bootex,16
C. Setup the Programs directory
After doing this, you will no longer be able to boot your old
system. If you wish to have a way to boot the 5.2/5.27 system
again in case your 6.2 system does not boot correctly, you need
to make another boot.cmd file and another welcome file. You
should use your existing 5.2/5.27 boot.cmd and welcome files for
this step. In the boot.cmd file, you need to access all programs
in the /progs527 directory.
To set up the /programs directory for 6.2, do the following:
CI> wd /programs
CI> rn /programs /progs527
CI> rn /progs62 /programs
8. boot your 6.2 interim system.
Once the 6.2 interim system is booted successfully, the
next step is to go through a normal update, as if you
were updating a 6.1 system to 6.2. The following
steps are identical to the standard 6.2 Appendix A.
updating the interim 6.2 system to full 6.2
1. Create /TARGETPROGRAMS and use RTE_INSTALL.CMD to install RTE-A and
VC+:
Approximate size requirements for a 6.2 RTE-A system with VC+ without
subsystems are as follows:
| /TARGETPROGRAMS | 22500 blocks |
| /LIBRARIES | 14750 blocks |
| /HELP | 1700 blocks |
| /CATALOGS | 650 blocks |
The number of blocks required for the target programs and libraries
can vary depending on which FMP library is used. The values shown
here are for a system that uses the largest FMP library, $UFMP and
$UCDS.
A. Create the directory for the 6.2 programs.
CI> crdir /targetprograms
The variables used in the cookbook example will update the host's
global directories (with the exception of /PROGRAMS). We recommend
that all subsystems that will be updated be shut down on the host
system in this scenario.
NOTE:
Refer to "Installation Considerations" in the (92077A) RTE-A Operating
System section of Chapter 4 for more information on the variables and
defaults used by the RTE_INSTALL.CMD file.
B. Set the CI variables needed by the RTE_INSTALL.CMD file.
CI> set rte_progs = /targetprograms
CI> set rte_dir = /
RTE_INSTALL.CMD uses the default settings indicated below:
| Variable name | Default setting | Description |
| $rte_cds | T | Will target system use CDS utilities?
(T = True, F = False) |
| $rte_nfs | F | Will target system support the FSRV file server and/or type 12 files?
(T = True, F = False) |
| $rte_slink | T | Will target system support symbolic links?
(T = True, F = False) |
| $rte_return | C | Abort, Continue, or Suspend installation after link errors? Where,
A = Abort the installation if an error is encountered when linking a program.
C = Continue the installation and only report
link errors.
S = Suspend the installation process and allow the user to correct the problem before proceeding. |
If you wish to change any of the defaults, you can use the SET
command to set the variable to the desired state.
The setting of $RTE_NFS and $RTE_SLINK determine the type of FMP
libraries that are used to build $BIGLB.LIB and $BGCDS.LIB. If
$RTE_NFS is set to T, $UFMP and $UCDS are used to build the
libraries. These libraries offer support of symbolic links and the
type 12 byte stream file type required by the file server
functionality offered with the NS-ARPA/1000 or ARPA/1000 products.
Setting $RTE_NFS to T forces $RTE_CDS and $RTE_SLINK to also be set
to T.
$RTE_NFS controls whether the file server program FSRV will be
linked by the install process and whether a system will support
type 12 files. When building a system, $RTE_NFS needs to be set to
T if you are going to use the file server on the system or if you
intend to use DS Transparency from the system you are building to
read type 12 files on another RTE system.
C. Make modifications for SCSI MO devices. (SCSI MO users only)
- Modify D.RTR load files if your system contains a SCSI MO device
If your system contains a SCSI MO device, the load files for
D.RTR must be modified to relocate the DDSEND.REL module.
The load files to modify are /RTE_A/DDRTR.LOD and/or
/VCPLUS/DDRTR_CDS.LOD.
- Modify DDMAX.MAC file for SCSI MO device spin-up/down and eject
on dismount feature. (Optional)
If you have a SCSI MO device and want to use the CN40b and CN41b
spin-up/down and eject on dismount feature (defined in Driver
Parameter 8), you must modify the DDMAX.MAC file and recompile it
using Macro. This feature is available with the CDS version of
D.RTR and is disabled by default. You can enable this feature
at link time by modifying the /VCPLUS/DDMAX.MAC file and running
Macro to regenerate DDMAX.REL. For example,
CI> MACRO DDMAX.MAC - -
See further instructions inside the DDMAX.MAC file.
D.Use RTE_INSTALL to install RTE-A and VC+.
Set CI variables to the directories containing the revision 6200
relocatables for RTE-A and VC+.
CI> set rte_a = /rte_a
CI> set vcplus = /vcplus
You can also install most of the subsystems at this time using the
RTE_INSTALL.CMD file. The product installation is controlled by CI
variables that contain the directory path for the relocatables
product being installed. For more information about the
RTE_INSTALL.CMD file, see Chapter 4 of this document or consult the
6.2 version of the System Generation and Installation Manual, part
number 92077-90034.
WARNING: RTE_INSTALL.CMD can only install the 6.2 revision
of the subsystem products.
WARNING: Note that RTEA1.CMD, which is called by RTE_INSTALL,
can be used to build the target libraries in a
directory other than /LIBRARIES; but, you must make
sure that the default library search path specified
in your snap file matches the target library directory.
Otherwise, RTEA1.CMD will build the new libraries in
the specified target, but, LINK will use the old
existing libraries to build the target programs. If
you need to build and use different libraries refer
to instructions within the RTE_INSTALL.CMD file.
For example, to also install the LP spooler and NS/1000 subsystems,
set the product variables to the directories containing the
revision 6200 relocatables.
CI> set lp = /vcplus/lp
CI> set ns1000 = /ns1000
Now transfer to RTE_INSTALL to install the new revision.
CI> /rte_a/rte_install, /gen/rev62/rtea62.snp,
/rte_a, Q, I
NOTE: RTE_INSTALL.CMD manages the calling of RTEA1.CMD, RTEA2.CMD,
VC1.CMD, and VC2.CMD. When the installation parameters are
displayed, RTEA1.CMD will show "Transfer to RTEA2.CMD = NO",
and VC1.CMD will show "Transfer to VC2.CMD = NO". This is
because these files will complete under the direction of
RTE_INSTALL.CMD, not RTEA1.CMD and VC1.CMD.
2. BUILD your 6.2 memory-based system (if needed).
3. Prepare to boot the 6.2 system.
A. Set up the boot command file (usually BOOT.CMD) and Welcome file
(usually WELCOMEn.CMD where n is a number from 1-99). Copies of
your 6.1 boot command and welcome files can be used. Place these
files on your bootable LU and on /SYSTEM, respectively. Be sure
to specify your 6.2 system and snap files in the boot command
file.
It is recommended you comment out any references to subsystem and
application start-up at this time. After you have successfully
booted your RTE-A/VC+ system, you can remove the comments and
bring up your subsystems and applications.
B. Set up the /PROGRAMS directory.
To set up the /programs directory for 6.2, use the following:
CI> wd /programs
CI> rn /programs /old_progs
CI> rn /targetprograms /programs
4. Boot your 6.2 system.
If you placed your BOOTEX at sector 0, your bootstring will look
something like this:
VCP> %BDC27
Perform the following steps only if you are satisfied that your new 6.2 system is working.
NOTE: All program files will need to be relinked. No pre 6.0
program files will run on 6.2.
5. Load Security/1000.
There are two programs that must be loaded, SECTL and STGEN, for
Security/1000. If you used the VC+ transfer files VC1.CMD and
VC2.CMD, then these programs should already be loaded.
6. Initialize Security/1000.
To initialize and turn on the security each time the system is
booted, the following line MUST BE THE FIRST COMMAND in the Welcome
file:
ru,sectl,+in[:],+on
If the snap file name is not supplied, /system/snap.snp will be the
default name used. For more details please refer to the RTE-A
System Manager's Manual, part number 92077-90056.
7. Load other RTE subsystem software.
Load any subsystems needed for your RTE-A/VC+ system, such as
languages, networking, DEBUG/1000, Mail/1000, and so forth, if you
did not already do so in step 6C. Note that the CDS version of a
subsystem should be loaded if it is available and the subsystem will
support type 12 files.
For more information about using the new RTE_INSTALL.CMD file to
load subsystem software, see the 6.2 revision of the RTE-A System
Generation and Installation manual, part number 92077-90034, or
Chapter 4 of this document.
8. Relink your own application software.
(If updating from 5.2x, all programs will need to be relinked)
Due to the networking code improvements implemented at 6.2, any of
your applications that use the NS-ARPA/1000 product will need to be
relinked. Any applications that you wish to access type 12 byte
stream files will also need to be relinked.
9. Back up your new system.
A. Build a new memory-based ARSTR system. Using the 6.2 BUILD,
ARSTR, and the current 6.2 system and snap files, create the type
1 file holding the memory-based system. Use CI's 'CO' command to
copy that file to magnetic tape (or use CSYS to put it on Linus
tape) and then put this tape in a safe place to be used for
restoring the system if you have a disk crash. You should check
to see that you can boot the ARSTR system from the tape you just
made.
B. Before this new 6.2 system is complete, make an ASAVE of your
system that you can restore in the case of a disk crash.
See the RTE-A Backup and Disk Formatting Utilities Reference
Manual, part number 92077-90249, for details on the above
utilities.
This completes the update. The new system is now generated, installed, verified, and backed up.
|
