for Use with
VM/ESA Version 2 Release 2.0
VM/ESA Version 2 Release 3.0
VM/ESA Version 2 Release 4.0
Document Date: June 1999
GI10-0548-00
Note
Before using this information and the product it supports, be sure to read the general information under Appendix E, “Notices”
on page 53.
This program directory, dated June 1999, applies to Tivoli ADSTAR Distributed Storage Manager Version 3 Release 1.2 (Tivoli
ADSM for VM), Program Number 5697-VM3.
A form for reader's comments appears at the back of this publication. When you send information to IBM, you grant IBM a
nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you.
Copyright International Business Machines Corporation 1992, 1999. All rights reserved.
Note to U.S. Government Users — Documentation related to restricted rights — Use, duplication or disclosure is subject to
restrictions set forth in GSA ADP Schedule Contract with IBM Corp.
8.DASD Storage Requirements for Target Minidisks........................... 11
ivTivoli ADSM for VM Program Directory
1.0Introduction
This program directory is intended for the system programmer responsible for program installation and
maintenance. It contains information concerning the material and procedures associated with the
installation and service of Tivoli ADSM for VM. You should read all of this program directory before
installing the program and then keep it for future reference.
The program directory contains the following sections:
2.0, “Program Materials” on page 3 identifies the basic and optional program materials and
documentation for Tivoli ADSM for VM.
3.0, “Program Support” on page 7 describes the IBM support available for Tivoli ADSM for VM.
4.0, “Program and Service Level Information” on page 8 lists the APARs (program level) and PTFs
(service level) incorporated into Tivoli ADSM for VM.
5.0, “Installation Requirements and Considerations” on page 9 identifies the resources and
considerations for installing and using Tivoli ADSM for VM.
6.0, “Installation Instructions” on page 13 provides detailed installation instructions for Tivoli ADSM for
VM.
7.0, “Service Instructions” on page 27 provides detailed servicing instructions for Tivoli ADSM for VM.
Appendix A, “Applying an RSU Tape for Tivoli ADSM for VM” on page 36 provides detailed
Recommended Service Upgrade instructions for Tivoli ADSM for VM.
Appendix B, “Disabling Tivoli ADSM for VM” on page 43 describes how to disable Tivoli ADSM for
VM 3.1.2, if on VM/ESA Version 2 Release 4.0.
Appendix C, “Moving Tivoli ADSM for VM to SFS Directories and Creating PPF Override” on page 45
describes how to move Tivoli ADSM for VM into SFS, if originally installed using minidisks, and how to
create a Product Parameter File (PPF) override.
Appendix D, “ADSM Installation Tape Contents” on page 50 lists the names of the files contained in
the installation tape.
Before installing Tivoli ADSM for VM, read 3.1, “Preventive Service Planning” on page 7. This section tells
you how to find any updates to the information and procedures in this program directory.
1.1 Program Description
Tivoli ADSTAR Distributed Storage Manager (ADSM) is a client/server program that provides storage
management to customers in a multivendor computer environment.
ADSM provides an administrator-controlled, highly automated, centrally scheduled, network-based backup
and archive functions for a wide variety of workstations and LAN file servers.
Copyright IBM Corp. 1992, 1999 1
1.2 Important VM/ESA 2.4.0 Information
Beginning with VM/ESA 2.4.0, Tivoli ADSM for VM 3.1.2 is a pre-installed, optionally installable product on
the VM/ESA System DDR in a disabled state. Most of the install steps have already been completed.
This includes installing the ADSM base tape and RSU tape. You will still need to complete some new
planning steps and the place into production steps; as documented in chapter 6.0, “Installation
Instructions” on page 13.
2Tivoli ADSM for VM Program Directory
2.0Program Materials
An IBM program is identified by a program number. The program number for Tivoli ADSTAR Distributed
Storage Manager Version 3 is 5697-VM3.
The program announcement material describes the features supported by Tivoli ADSM for VM. Ask your
IBM marketing representative for this information if you have not already received a copy.
The following sections identify:
basic and optional program materials available with this program
publications useful during installation.
Ordering Tivoli ADSM for VM 3.1.2 on VM/ESA 2.4.0
If you plan on licensing Tivoli ADSM for VM 3.1.2 on VM/ESA 2.4.0 the following describes how to
order the product, and obtain a set of manuals, depending on your current Tivoli ADSM for VM Version
3 Release 1.2 license:
Installations who have not previously ordered Tivoli ADSM for VM 3.1.2:
Order one of the feature codes listed in Figure 1, below, and indicate that you want to suppress
media shipment. This will license you for Tivoli ADSM for VM 3.1.2 and provide you with a set of
manuals. Media shipment is not necessary since the product has already been pre-installed on
the VM/ESA System DDRs for you.
Installations currently using Tivoli ADSM for VM 3.1.2:
There is nothing additional you need to order.
2.1 Basic Machine-Readable Material
The distribution medium for this program is 3480 or 4mm tape cartridge. The cartridge contains all the
programs and data needed for installation. See section 6.0, “Installation Instructions” on page 13 for more
information about how to install the program. Figure 1 describes the cartridge. Figure 2 on page 4
describes the file content of the program cartridge.
Figure 1 (Page 1 of 2). Basic Material: Program Tape
Feature
NumberMedium
58023480
cart.
Physical
VolumeTape ContentExternal Tape Label
1Tivoli ADSM for VM 3.1.2ADSM VM Server
Copyright IBM Corp. 1992, 1999 3
Figure 1 (Page 2 of 2). Basic Material: Program Tape
Feature
NumberMedium
60014mm
tape
cart.
Figure 2. Program Tape: File Content
Tape
FileContent
1Tape Header
2Tape Header
3Product Header
4Product Memo
5Service Apply Lists
6PTFPARTs
7Tivoli ADSM for VM Service
8Tivoli ADSM for VM Service
9Tivoli ADSM for VM Base Code
10Tivoli ADSM for VM Executable Code
Physical
VolumeTape ContentExternal Tape Label
1Tivoli ADSM for VM 3.1.2ADSM VM Server
2.2 Optional Machine-Readable Material
There are no optional machine-readable materials for Tivoli ADSM for VM.
2.3 Program Publications
The following sections identify the basic and optional publications for Tivoli ADSM for VM.
2.3.1 Basic Program Publications
One copy of the following publications are included when you order the basic materials for Tivoli ADSM for
VM. For additional copies, contact your IBM representative.
Figure 3 (Page 1 of 2). Basic Material: Unlicensed Publications
Publication TitleForm Number
Tivoli ADSTAR Distributed Storage Manager for VM: Licensed Programming SpecificationsGC35-0350
Tivoli ADSTAR Distributed Storage Manager for VM: Quick StartGC35-0351
4Tivoli ADSM for VM Program Directory
Figure 3 (Page 2 of 2). Basic Material: Unlicensed Publications
Publication TitleForm Number
Tivoli ADSTAR Distributed Storage Manager: Installing the ClientsSH26-4080
Tivoli ADSTAR Distributed Storage Manager: Reference Cards for the Backup-Archive ClientsSX26-6019
One copy of the VM/ESA Softcopy displayable CD-ROM collection kit, IBM Online Library OmnibusEdition: VM Collection number SK2T-2067, will be included in your order. Note that this collection kit will
not be available until July 23, 1999. It contains all of the Tivoli ADSM for VM publications. This includes
the Administrator's Guide, Administrator's Reference and Messages. Until the VM/ESA softcopy CD is
available these ADSM manuals will be shipped with your ADSM order. For additional copies, contact your
IBM representative.
Additionally, English language versions of all of the ADSM publications are offered in BookManager,
PDF and HTML softcopy displayable format off of the Tivoli ADSM Web site at url:
http://www.tivoli.com/adsm
2.4 Microfiche Support
There is no microfiche for Tivoli ADSM for VM.
2.5 Publications Useful During Installation
The publications listed in Figure 4 or Figure 5, depending on your VM/ESA release, may be useful during
the installation of Tivoli ADSM for VM. To order copies, contact your IBM representative.
Figure 4. Publications Useful During Installation / Service on VM/ESA Version 2.2.0
Publication TitleForm Number
Tivoli ADSTAR Distributed Storage Manager for VM: Quick StartGC35-0351
VM/ESA: VMSES/E Introduction and ReferenceSC24-5747
VM/ESA: Service GuideSC24-5749
VM/ESA: Planning and AdministrationSC24-5750
VM/ESA: CMS Command ReferenceSC24-5776
VM/ESA: CMS File Pool Planning, Administration, and OperationSC24-5751
VM/ESA: System Messages and CodesSC24-5784
Figure 5 (Page 1 of 2). Publications Useful During Installation / Service on VM/ESA Version 2.3.0 and higher
Publication TitleForm Number
Tivoli ADSTAR Distributed Storage Manager for VM: Quick StartGC35-0351
Program Materials5
Figure 5 (Page 2 of 2). Publications Useful During Installation / Service on VM/ESA Version 2.3.0 and higher
Publication TitleForm Number
VM/ESA: VMSES/E Introduction and ReferenceGC24-5837
VM/ESA: Service GuideGC24-5838
VM/ESA: Planning and AdministrationSC24-5750
VM/ESA: CMS Command ReferenceSC24-5776
VM/ESA: CMS File Pool Planning, Administration, and OperationSC24-5751
VM/ESA: System Messages and CodesGC24-5841
6Tivoli ADSM for VM Program Directory
3.0Program Support
This section describes the IBM support available for Tivoli ADSM for VM.
3.1 Preventive Service Planning
Before installing Tivoli ADSM for VM, check with your IBM Support Center or use IBMLink (ServiceLink)
to see whether there is additional Preventive Service Planning (PSP) information. To obtain this
information, specify the following UPGRADE and SUBSET values:
Figure 6. PSP Upgrade and Subset ID
Retain
UpgradeSubsetCOMPIDRelease
565511901A31ADSM312ADSMVM/SES
565511901A31ADSM312yynnRSU
565511901A31ADSM312RSU-BY-LVL
565511901A31ADSM312RSU-BY-APAR
565511901A31ADSM312RSU-BY-PTF
3.2 Statement of Support Procedures
Report any difficulties you have using this program to your IBM Support Center. If an APAR is required,
the Support Center will provide the address to which any needed documentation can be sent.
Figure 7 identifies the component ID (COMPID), Retain Release and Field Engineering Service Number
(FESN) for Tivoli ADSM for VM.
Figure 7. Component IDs
Retain
Component NameFESNCOMPIDRelease
565511901A31Tivoli ADSM for VM 3.1.20402385
Copyright IBM Corp. 1992, 1999 7
4.0Program and Service Level Information
This section identifies the program and any relevant service levels of Tivoli ADSM for VM. The program
level refers to the APAR fixes incorporated into the program. The service level refers to the PTFs shipped
with this product. Information about the cumulative service tape is also provided.
4.1 Program Level Information
All ADSM Version 2 APARs closed before April 1,1999 were incorporated into this version.
4.2 Service Level Information
Check the ADSM312 PSP bucket for any additional PTFs that should be installed or any additional install
information.
4.3 Cumulative Service Tape
Cumulative service for Tivoli ADSM for VM Version 3 Release 1.2 is available through a periodic
Recommended Service Upgrade (RSU) tape. See PSP bucket upgrade ADSM312, subset yynnRSU
(where yynn is the RSU service level) for the latest RSU tape available. For the list of PTFs included on
the RSU tape, see the service memo from the tape or the PSP subsets sorted by PTF, APAR or RSU
level (LVL).
The RSU can be ordered using the PTF number UQ99312 (APAR PQ25527).
8 Copyright IBM Corp. 1992, 1999
5.0Installation Requirements and Considerations
The following sections identify the system requirements for installing the Tivoli ADSM for VM program
product.
5.1 Migration Requirements
If you are a current user of ADSM Version 2 and will be migrating to Tivoli ADSM for VM Version 3, then
you must preserve the ADSM Version 2 program product because you will need it to back-up your existing
ADSM database. And, if necessary, the ADSM Version 2 program product will be needed for recovery
purposes. The manual Tivoli ADSTAR Distributed Storage Manager for VM: Quick Start has more
information on the back-up requirement.
5.2 Hardware Requirements
There are no special hardware requirements for Tivoli ADSM for VM.
5.3 Program Considerations
The following sections list the programming considerations for installing Tivoli ADSM for VM and activating
its functions.
5.3.1 Operating System Requirements
Tivoli ADSM for VM supports the following VM operating systems:
VM/ESA Version 2 Release 4.0
VM/ESA Version 2 Release 3.0
VM/ESA Version 2 Release 2.0
5.3.2 Other Program Product Requirements
The Tivoli ADSM for VM Server program has the following requisites:
One of the following:
– IBM Language Environment for MVS & VM Version 1 Release 5 (5688-198) and later
– IBM C/370 Library Version 2 (5688-188) and later
(Optional) Transmission Control Program/Internet Protocol (TCP/IP) Version 2 Release 3 for VM
(5735-FAL) or later is required to establish TCP/IP communications between an ADSM client and the
server.
Copyright IBM Corp. 1992, 1999 9
(Optional) IBM ACF/VTAM Version 3 Release 4 (5684-095) or later is required for SNA
communications (3270 and APPC) between an ADSM client and the server.
5.3.3 Program Installation/Service Considerations
This section describes items that should be considered before you install or service Tivoli ADSM for VM.
VMSES/E is required to install and service this product.
If multiple users install and maintain licensed products on your system, there may be a problem
getting the necessary access to MAINT's 51D disk. If you find that there is contention for write access
to the 51D disk, you can eliminate it by converting the Software Inventory from minidisk to Shared File
System (SFS). See the VMSES/E Introduction and Reference manual, section "Changing the
Software Inventory to an SFS Directory", for
information on how to make this change.
Customers will no longer install and service Tivoli ADSM for VM strictly using the MAINT user ID, but
will use a new user ID named 5654A09A. This is the IBM suggested user ID name. You are free to
change this to any user ID name you wish, however, a PPF override must be created.
Note: It may be easier to make the above change during the installation procedure 6.2, “Plan Your
Installation For Tivoli ADSM for VM” step 8 on page 17, than after you have installed this product.
If you decide to move Tivoli ADSM for VM from minidisk to Shared File System (SFS) after you have
initially installed the product, or if you want to change from the default SFS file pool or directories, then
you will need to follow the steps in Appendix C, “Moving Tivoli ADSM for VM to SFS Directories and
Creating PPF Override” on page 45. These steps will have you create the SFS directories, move the
files to the SFS directories and create a PPF override. You can also refer to the VMSES/EIntroduction and Reference manual for more information on creating a PPF override.
RSU tapes will be supplied as necessary. Service between RSU tapes can be obtained through
CORrective service.
5.4 DASD Storage and User ID Requirements
Figure 8 on page 11 lists the user ID and minidisks that are used to install and service the Tivoli ADSM
for VM program product. The figure does not include DASD storage requirements needed for the Tivoli
ADSM for VM database or server machine. These requirements are discussed in Tivoli ADSTARDistributed Storage Manager for VM: Quick Start.
Important Installation Notes:
User ID(s) and minidisks will be defined in 6.2, “Plan Your Installation For Tivoli ADSM for VM” on
page 14 and are listed here so that you can get an idea of the resources that you will need prior
to allocating them.
5654A09A is a default user ID and can be changed. If you choose to change the name of the
installation user ID you need to create a Product Parameter Override (PPF) to reflect this change.
This can be done in 6.2, “Plan Your Installation For Tivoli ADSM for VM” step 8 on page 17.
10Tivoli ADSM for VM Program Directory
If you choose to install Tivoli ADSM for VM on a common user ID the default minidisk addresses
for Tivoli ADSM for VM may already be defined. If any of the default minidisks required by Tivoli
ADSM for VM are already in use you will have to create an override to change the default
minidisks for Tivoli ADSM for VM so they are unique.
Figure 8 (Page 1 of 2). DASD Storage Requirements for Target Minidisks
Minidisk
owner
(user ID)
5654A09A2B23390
5654A09A2D23390
5654A09A2A63390
5654A09A2A23390
5654A09A4913390
Notes:
1. An SFS directory SHOULD NOT be used for the production disk or the test build disk to avoid suspension of
the ADSM server. The message repository, which is read as needed by the server, will reside on these disks.
By placing the message repository in an SFS directory the ADSM Server can be suspended while the SFS
Server satisfies a read request when a message text is needed.
2. Cylinder values defined in this table are based on a 4K block size. FB-512 block and SFS values are derived
from the 3380 cylinder values in this table. The FBA blocks are listed as 1/2K but should be CMS formatted
at 1K size. 37,650 4K blocks are needed for SFS install.
3. The list of DASD in this figure does not show all devices supported by VM/ESA and you are not limited to only
these devices when installing the Tivoli ADSM for VM program product. To determine the amount of space
needed on a device not listed but supported by VM/ESA, start with the value in the "SFS 4K Blocks" column.
Default
Address
Storage in
Cylinders
DASDCYLSDefault SFS Directory Name
25
3380
9345
3380
9345
3380
9345
3380
9345
3380
9345
30
30
90
108
108
2
2
2
2
2
2
45
54
54
FB-512
Blocks
360004500Contains all the base code shipped with
12960016200Contains serviced files
2400300Contains AUX files and software
2400300Contains AUX files and software
648008100This is the production disk. All the files
SFS 4K
Blocks
Tivoli ADSM for VM
VMSYS:5654A09A.ADSM.OBJECT
VMSYS:5654A09A.ADSM.DELTA
inventory tables that represent the
test service level of Tivoli ADSM for VM
VMSYS:5654A09A.ADSM.APPLYALT
inventory tables that represent the
service level of Tivoli ADSM for VM
that is currently in production.
VMSYS:5654A09A.ADSM.APPLYPROD
needed by the ADSM Server and the CMS
Admin client will exist in this disk.
SFS directory not recommended.
Usage
(1*)
Installation Requirements and Considerations11
Figure 8 (Page 2 of 2). DASD Storage Requirements for Target Minidisks
Minidisk
owner
(user ID)
5654A09A4E23390
5654A09A1913390
Notes:
1. An SFS directory SHOULD NOT be used for the production disk or the test build disk to avoid suspension of
the ADSM server. The message repository, which is read as needed by the server, will reside on these disks.
By placing the message repository in an SFS directory the ADSM Server can be suspended while the SFS
Server satisfies a read request when a message text is needed.
2. Cylinder values defined in this table are based on a 4K block size. FB-512 block and SFS values are derived
from the 3380 cylinder values in this table. The FBA blocks are listed as 1/2K but should be CMS formatted
at 1K size. 37,650 4K blocks are needed for SFS install.
3. The list of DASD in this figure does not show all devices supported by VM/ESA and you are not limited to only
these devices when installing the Tivoli ADSM for VM program product. To determine the amount of space
needed on a device not listed but supported by VM/ESA, start with the value in the "SFS 4K Blocks" column.
Default
Address
Storage in
Cylinders
DASDCYLSDefault SFS Directory Name
45
3380
9345
3380
9345
54
54
1
1
1
FB-512
Blocks
648008100This is the test build disk which will
12001505654A09A user ID's 191 minidisk
SFS 4K
Blocks
contain the production files after the
service process completes. Once
testing is complete, files must be copied
to the production disk.
SFS directory not recommended.
VMSYS:5654A09A.
Usage
(1*)
12Tivoli ADSM for VM Program Directory
6.0Installation Instructions
This chapter describes the installation methods and the step-by-step procedures to install the Tivoli ADSM
for VM program product.
The step-by-step procedures are in two column format. The steps to be performed are in bold large
numbers. Commands for these steps are on the left hand side of the page in bold print. Additional
information for a command may exist to the right of the command. For more information about the two
column format see "Understanding the Dialog with the System" in the VM/ESA Installation Guide.
Each step of the installation instructions must be followed. Do not skip any step unless directed to do so.
Throughout these instructions, the use of IBM-supplied default minidisk addresses and user IDs is
assumed. If you use different user IDs, minidisk addresses, or SFS directories to install Tivoli ADSM for
VM, adapt these instructions as needed for your environment.
Note
The sample console output presented throughout these instructions was produced on a VM/ESA
Version 2 Release 3 system. If you're installing Tivoli ADSM for VM on a different VM/ESA system,
the results obtained for some commands may differ from those depicted here.
6.1 VMSES/E Installation Process Overview
The following is a brief description of the main steps in installing Tivoli ADSM for VM using VMSES/E.
Plan Your Installation
Use the VMFINS command to load several VMSES/E files from the product tape and to obtain Tivoli
ADSM for VM resource requirements.
Allocate Resources
The information obtained from the previous step is used to allocate the appropriate minidisks (or SFS
directories) and the user ID needed to install the Tivoli ADSM for VM program product.
Install the Tivoli ADSM for VM Product
Use the VMFINS command to load the Tivoli ADSM for VM product files from tape to the test BUILD
and BASE minidisks/directories. VMFINS is then used to update the VM SYSBLDS file used by
VMSES/E for software inventory management.
Place Tivoli ADSM for VM Files into Production
Once the product files have been tested and the operation of Tivoli ADSM for VM is satisfactory, they
must be copied from the test BUILD disk to the production BUILD disk.
Copyright IBM Corp. 1992, 1999 13
For a complete description of all VMSES/E installation options refer to VMSES/E Introduction andReference.
6.2 Plan Your Installation For Tivoli ADSM for VM
Note
This planning section should be followed no matter what release of VM/ESA you are installing on.
Follow the instructions that pertain to your VM/ESA release.
The VMFINS command will be used to plan the installation. This section has steps that will:
load the first tape file, containing installation files
generate a 'PLANINFO' file listing
– the install user ID and minidisk requirements
– required products
To obtain planning information for your environment:
link MAINT 5e5 5e5 rr
access 5e5 b
link MAINT 51d 51d mr
access 51d d
1 Logon to a user ID where the installation planning tasks can be performed.
This user ID can be any ID that has the following:
read access to MAINT's 5E5 minidisk
write access to MAINT's 51D minidisk
Privilege class E authority required for VM/ESA 2.4.0 installations.
2 Establish read access to the VMSES/E code.
The 5E5 disk contains the VMSES/E code.
3 Establish write access to the Software Inventory disk.
The MAINT 51D disk is where the VMSES/E
system-level Software Inventory and other
dependent files reside.
Note: If another user already has the MAINT 51D minidisk linked in write
mode (R/W), you will only obtain read access (R/O) to this minidisk. If this
occurs, you will need to have that user re-link the 51D in read-only mode
(RR), and then re-issue the above LINK and ACCESS commands. Do not
14Tivoli ADSM for VM Program Directory
continue with these procedures until a R/W link is established to the 51D
What's Next?
Beginning with VM/ESA Version 2 Release 4.0, Tivoli ADSM for VM 3.1.2 is pre-installed, using
VMSES/E, in a DISABLED state, on the VM/ESA System DDRs. If, and only if, you have a
license for Tivoli ADSM for VM 3.1.2, you can enable it for use. If you are
running on VM/ESA Version 2 Release 4.0
optionally installed Tivoli ADSM for VM from the VM/ESA System DDRs, and
are licensed for Tivoli ADSM for VM
then continue with step 4.
Otherwise, continue with step 6 on page 16.
VM/ESA Version 2 Release 4.0 Licensed Users of Tivoli ADSM for VM only!
minidisk.
4 Set Tivoli ADSM for VM to the enabled state.
vmfins enable ppf 5654A09A {ADSM | ADSMSFS}Use ADSM if installing using minidisk or
ADSMSFS if installing using Shared File System
directories.
This command will perform the following:
Set Tivoli ADSM for VM as ENABLED in
VMSES/E and within CP.
Create a 5654A09A PRODSYS file on the
A-disk that contains the CP system
configuration PRODUCT statement with a state
of ENABLED
5 In order to retain the ENABLED state for Tivoli ADSM for VM, update the
CP system configuration file with the information in the 5654A09A
PRODSYS file.
The 5654A09A PRODSYS file was created by VMFINS in the previous step.
You need to update the CP system config file so that the next time you IPL
your system Tivoli ADSM for VM will be in the ENABLED state. If you are
not authorized to update the CP system configuration file then contact your
CP System Administrator.
The CP system configuration file default name is SYSTEM CONFIG and it
resides on the CP parm disk (MAINT's CF1 and CF2 minidisks). The section,
PRODUCT ENABLE/DISABLE INFORMATION, in the SYSTEM CONFIG file,
Installation Instructions15
Loading...
+ 43 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.