50 EFS Systems on a Linux Base: Getting Started
$ rm /s390/S2DIS1
$ rm /s390/S2DIS2
7. Repeat the process with more volumes from the CDs, if necessary.
8. After all the additional volumes are on the second hard disk, use an ls -al /s391
command to verify that they are owned by userid flexes.
Another way to stage volumes would be to copy zipped files from CD onto the first hard disk.
You could then unzip them onto the second hard disk.
5.2 Dump/restore distribution
We installed the Customized Offering Driver system (IBM product 5665-343, release 1.17).
This is often known as the
COD system and it replaces what was formerly known as the
Starter System. It is a working z/OS system on two 3390-3 volumes. Only limited functions are
available. The COD system is a sufficient base for installing a z/OS ServerPac. That is, if you
have no other z/OS (or OS/390) system installed, you could first install the COD (using a
stand-alone restore) and then use the COD to customize and install a ServerPac. This
process is independent of any AD systems and is one of the startup processes that might be
followed by new z/OS customers who are not using AD CD-ROM packages.
For this installation we used a PC that had a SCSI-attached 3480/90 tape drive.
Although this section describes the installation of the COD system, the same general steps
apply to installing backup tapes of any system. In essence, the COD package is simply a
small z/OS system that has been backed up to tape (plus an additional tape containing two
stand-alone utility programs).
Our copy of the COD included:
Four tapes containing 3390-3 volume D9ESY1
Five tapes containing 3390-3 volume D9ECAT
One tape with stand-alone utilities
We first studied the COD documentation (IBM order number GI10-0615-04, or later) to
determine what device addresses we could use.
We found the following should work:
3390 disk drives at addresses 320, 321 (up through 33F, if needed)
3490 tape drive at address 390
3270 console for NIP and z/OS at address 0A1
3270 terminals for TSO at addresses 0F00-0F03
The COD has a large number of devices and addresses (“device numbers”) in its IODF and
our choices were somewhat arbitrary. Based on our choices, we created appropriate
FLEX-ES definitions and a startup shell script, shown in “Customized Offerings Driver
definitions” on page 96.
Included with the COD system is a tape with two stand-alone utilities. A stand-alone utility is
one that can be IPLed directly--without any operating system involved. The first utility on the
tape is Device Support Facilities (DSF) that is used to initialize a disk volume. The second
utility on the tape is DFSMSdss™, which is used to restore a volume from tape to disk.
If you are restoring some other system (other than the COD), you must determine the device numbers used by that
system. That is, you must know the devices (and device numbers) included in the IODF that will be used when you
IPL the new system. You must find this information from external sources; there is no easy way to determine it by
examining the tapes.