Instruction/ maintenance manual of the product 5697-VM3 IBM
Go to page of 62
IBM Program Directory for Tivoli ADSTAR Distributed Storage Manager for VM Version 3 Release 1.2 Program Number 5697-VM3 for Use with VM/ESA Version 2 Release 2.
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.
Contents 1.0 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1.1 Program Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1.
7.2 Servicing Tivoli ADSM for VM ........................................ 28 7.2.1 Prepare to Receive Service ....................................... 28 7.2.2 Receive the Service ........................................... 30 7.2.3 Apply the Service .
1.0 Introduction 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.
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.
2.0 Program 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.
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.
One copy of the VM/ESA Softcopy displayable CD-ROM collection kit, IBM Online Library Omnibus Edition: 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.
Figure 5 (Page 2 of 2). Publications Useful During Installation / Service on VM/ESA Version 2.3.0 and higher Publication Title Form Number VM/ESA: VMSES/E Introduction and Reference GC24-5837 VM/ESA: .
3.0 Program 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.
4.0 Program 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.
5.0 Installation Requirements and Considerations The following sections identify the system requirements for installing the Tivoli ADSM for VM program product.
(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.
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 2 of 2). DASD Storage Requirements for Target Minidisks Minidisk owner (user ID) Default Address Storage in Cylinders FB-512 Blocks SFS 4K Blocks Usage DASD CYLS Default SFS Directory N.
6.0 Installation 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.
For a complete description of all VMSES/E installation options refer to VMSES/E Introduction and Reference . 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.
continue with these procedures until a R/W link is established to the 51D minidisk. 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.
is what needs to be updated. You will need to replace the current DISABLED entry for PRODID 5654A09A (Tivoli ADSM for VM) with the entry from the 5654A09A PRODSYS file (created by VMFINS in the previous step). If necessary, refer to the VM/ESA Planning and Administration manual for more information about the CP system configuration file.
VMFINS276I VMFINS processing started VMFINS199I VMFINS PRODLIST created on your A-disk VMFINS276I VMFINS processing completed successfully Ready; 8 Obtain resource planning information for Tivoli ADSM for VM. Note: The product will not be loaded by the VMFINS command at this time.
VMFINS2767I Reading VMFINS DEFAULTS B for additional options VMFINS276I VMFINS processing started VMFINS261R Do you want to create an override for :PPF 5654A9A ADSM :PRODID 5654A9A.
Note Complete this step only if you received message VMFREQ286W for any of the products that are required by Tivoli ADSM for VM: either IBM Language Environment (5688-198) or IBM C/370 Library (5688-188).
6.3 Allocate Resources for Installing Tivoli ADSM for VM Use the planning information in the 5654A09A PLANINFO file, created in the PLAN step, to: Create the 5654A09A user directory for minidisk install OR Create the 5654A09A user directory for SFS install.
2 Change the password for 5654A09A from xxxxxxxx to a valid password, in accordance with your security guidelines. 3 If you intend to use an SFS directory in place of the 191 minidisk for the 5654A09A.
Note: This must be done from a user ID that is an administrator for VMSYS: filepool. c Determine if there are enough blocks available in the filepool to install Tivoli ADSM for VM. This information can be obtained with the QUERY FILEPOOL STATUS command.
3 Execute the profile to access MAINT's minidisks. profile 4 If the Software Inventory disk (51D) was accessed R/O (read only) then establish write access to the Software Inventory disk. Note: If the MAINT 51D minidisk was accessed R/O, you will need to have the user who has it linked R/W link it as R/O.
VMFINS2767I Reading VMFINS DEFAULTS B for additional options VMFINS276I VMFINS processing started VMFINS261R Do you want to create an override for :PPF 5654A9A ADSM :PRODID 5654A9A.
6.4.1 Update Build Status Table for Tivoli ADSM for VM 1 Update the VM SYSBLDS software inventory file for Tivoli ADSM for VM. vmfins build ppf 5654A09A {ADSM | ADSMSFS} (serviced nolink Use ADSM for installing on minidisks or ADSMSFS for installing in Shared File System directories.
Admin Client on your system. The book also contains instructions for migrating a Version 2 ADSM system to Version 3. Tivoli ADSM for VM is now installed and built on your system.
7.0 Service Instructions RSU Warning If applying a Tivoli ADSM for VM RSU (Recommended Service Upgrade) go to the instructions in Appendix A, “ Applying an RSU Tape for Tivoli ADSM for VM ” on page 36. You will return to a step in this chapter as specified in that appendix.
Build New Levels The build task generates the serviced level of an object and places the new object on a test BUILD disk. Place the New Service into Production Once the service is satisfactorily tested it is ready to put into production by copying the new service to the production disk.
5654A09A is the PPF that was shipped with the product. If you have your own PPF override you should substitute your PPF name for 5654A09A. Use ADSM for installing on minidisks or ADSMSFS for installing in Shared File System directories. 5 Receive the documentation.
Use ADSM for installing on minidisks or ADSMSFS for installing in Shared File System directories. This command clears the alternate APPLY disk. 10 Review the merge message log ($VMFMRD $MSGLOG).
7.2.3 Apply the Service 1 Apply the new service. vmfapply ppf 5654A09A {ADSM | ADSMSFS} Use ADSM for installing on minidisks or ADSMSFS for installing in Shared File System directories.
7.2.4 Update the Build Status Table 1 Update the Build Status Table with serviced parts. vmfbld ppf 5654A09A {ADSM | ADSMSFS} (status Use ADSM for installing on minidisks or ADSMSFS for installing in Shared File System directories. This command updates the Build Status Table.
Note If the $PPF files have been serviced you will get the following prompt: VMFBLD2185R The following source product parameter files have been serviced: VMFBLD2185R 5654A9A $PPF VMFBLD2185R When source product parameter files are serviced, all product parameter files built from them must be recompiled using VMFPPF before VMFBLD can be run.
2 Use VMFVIEW to review the build status messages, and see what objects need to be built. vmfview build 7.2.5 Build Serviced Objects 1 Rebuild Tivoli ADSM for VM serviced parts. vmfbld ppf 5654A09A {ADSM | ADSMSFS} (serviced Use ADSM for installing on minidisks or ADSMSFS for installing in Shared File System directories.
You have finished servicing Tivoli ADSM for VM. Service Instructions 35.
Appendix A. Applying an RSU Tape for Tivoli ADSM for VM Note You should first read through the RSU hard copy memo contained with the tape before continuing with these instructions. The RSU Tape is structured to install all PTFs included on the tape plus the tape files containing the preapplied service and prebuilt objects.
Building New Levels The build tasks generates the serviced level of an object and places the new object on a BUILD disk. Placing the New Service into Production Once the service is satisfactorily tested it should be put into production by copying the new service to the production disk.
a If receiving the RSU from tape vmfins install info (nomemo b If receiving the RSU from an envelope file vmfins install info (nomemo env rptf num 5 Determine DASD sizes for disks to receive service In order to receive the service from the RSU Tape, you need to have adequate space available on the alternate APPLY and DELTA disks.
Use ADSM for installing on minidisks or ADSMSFS for installing in Shared File System directories. This command produces an output file that contains information about the service on the RSU compared against the service and local modifications on your system.
VMFINS2767I Reading VMFINS DEFAULTS B for additional options VMFINS276I VMFINS processing started VMFINS263I Processing product :PPF 5654A9A ADSM :PRODID 5654A9A%ADSM VMFREQ285I.
vmfapply ppf 5654A09A {ADSM | ADSMSFS} . Use ADSM for installing on minidisks or ADSMSFS for installing in Shared File System directories. Messages VMFAPP2122E and VMFAPP2109R will be displayed only if you have reach-ahead service that needs to be reapplied.
A.1.5 Determine RSU Service Level The service contained on each RSU constitutes a new service level. Use this service level when ordering corrective service. The service level is updated in the system inventory when the RSU is installed. The following command is used to query the current service level of the system.
Appendix B. Disabling Tivoli ADSM for VM If you are running VM/ESA Version 2 Release 4.0 and had previously licensed and enabled Tivoli ADSM for VM 3.1.2 for use, and no longer are licensed for Tivoli ADSM for VM, you need to explicitly disable Tivoli ADSM for VM.
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 DISABLED state. If you are not authorized to update the CP system configuration file then contact your CP System Administrator.
Appendix C. Moving Tivoli ADSM for VM to SFS Directories and Creating PPF Override This appendix describes how to move Tivoli ADSM for VM into shared file (SFS) if it was not installed into SFS at initial install time. It also gives sample instructions on creating a PPF (Product Parameter File) override.
Notes: 1. The steps that follow help you determine the Tivoli ADSM for VM file pool space requirements, file pool enrollment, and SFS directory definitions. If not all of these steps are required - for example, you are changing only SFS directory or subdirectory names - adapt these instructions as needed for your environment.
set filepool userfilepool : create directory dirid dirid is the name of the SFS directory you're creating, such as the default names: create directory userfilepool :5654A9A.adsm create directory userfilepool :5654A9A.adsm.OBJECT create directory userfilepool :5654A9A.
Where vdev is the minidisk you are copying files from. If you are copying from SFS then substitute in the SFS directory name in place of vdev . dirid is the name of the (target) SFS directory that you are copying files to.
2 Create (or modify as required) the Variable Declarations ( :DCL. ) section for the ADSMSFS override area so that it resembles the :DCL. section as shown below. :OVERLST. ADSMSFS ========================================================= :ADSMSFS.
Appendix D. ADSM Installation Tape Contents File 1: INS 99 Tape descriptor file $$TAPE$$ VMSES Standard header file for SES format tapes 5654A9A PRODPART Product Parts file 5654A9A $PPF Ba.
ANRSVM5 MODULE SVM module DSMSERV PROFILE Sample PROFILE EXEC for DSMSERV virtual machine DSMEXIT PROFILE Sample PROFILE EXEC for tape mount virtual machine DSMSERV SAMPDIR Sample DSMSERV virtual mach.
ANRVM CNTRL Control file containing the Version Vector Table level SCRIPTS SAMPLE Server sample SCRIPTs ANRBAROC SAMPLE ANRUSRXA SAMPLE ANRUSRXC SAMPLE ANRUSRXH SAMPLE DSMSERV IDL Server IDL file ASHG.
Appendix E. Notices References in this document to IBM products, programs, or services do not imply that IBM intends to make these available in all countries in which IBM operates. Any reference to an IBM product, program, or service is not intended to state or imply that only IBM's product, program, or service may be used.
54 Tivoli ADSM for VM Program Directory.
Reader's Comments Tivoli ADSTAR Distributed Storage Manager Version 3 Release 1.2 Your feedback is important in helping to provide the most accurate and high-quality information. If you have comments or suggestions for improving this publication, you can send us comments electronically by using these addresses: - Internet: starpubs@us.
Is this the first time your organization has installed this product? Yes No Were the people who did the installation experienced with the installation of VM products using VMSES/E? .
.
IBM Program Number: 5697-VM3 5802 6001 Printed in U.S.A. GI1-548-.
An important point after buying a device IBM 5697-VM3 (or even before the purchase) is to read its user manual. We should do this for several simple reasons:
If you have not bought IBM 5697-VM3 yet, this is a good time to familiarize yourself with the basic data on the product. First of all view first pages of the manual, you can find above. You should find there the most important technical data IBM 5697-VM3 - thus you can check whether the hardware meets your expectations. When delving into next pages of the user manual, IBM 5697-VM3 you will learn all the available features of the product, as well as information on its operation. The information that you get IBM 5697-VM3 will certainly help you make a decision on the purchase.
If you already are a holder of IBM 5697-VM3, but have not read the manual yet, you should do it for the reasons described above. You will learn then if you properly used the available features, and whether you have not made any mistakes, which can shorten the lifetime IBM 5697-VM3.
However, one of the most important roles played by the user manual is to help in solving problems with IBM 5697-VM3. Almost always you will find there Troubleshooting, which are the most frequently occurring failures and malfunctions of the device IBM 5697-VM3 along with tips on how to solve them. Even if you fail to solve the problem, the manual will show you a further procedure – contact to the customer service center or the nearest service center
