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.0 VM/ESA Version 2 Release 3.0 VM/ESA Version 2 Release 4.
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.
Contents 1.0 Introduction . . . . . . . . . . . . . . 1.1 Program Description . . . . . . . . . . 1.2 Important VM/ESA 2.4.0 Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.0 Program Materials . . . . . . . . . . 2.1 Basic Machine-Readable Material . . 2.2 Optional Machine-Readable Material 2.3 Program Publications . . . . . . . . . 2.3.1 Basic Program Publications . . . 2.4 Microfiche Support . . . . . . . . . . . 2.5 Publications Useful During Installation . . .
7.2 Servicing Tivoli ADSM for VM . . . . . . . . . . . . . . . . . . . . 7.2.1 Prepare to Receive Service . . . . . . . . . . . . . . . . . . . 7.2.2 Receive the Service . . . . . . . . . . . . . . . . . . . . . . . 7.2.3 Apply the Service . . . . . . . . . . . . . . . . . . . . . . . . . 7.2.4 Update the Build Status Table . . . . . . . . . . . . . . . . . 7.2.5 Build Serviced Objects . . . . . . . . . . . . . . . . . . . . . . 7.2.6 Place the New Tivoli ADSM for VM Service into Production Appendix A.
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. 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.
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.
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. The following sections identify: basic and optional program materials available with this program publications useful during installation.
Figure 1 (Page 2 of 2). Basic Material: Program Tape Feature Number 6001 Medium 4mm tape cart. Physical Volume Tape Content External Tape Label 1 Tivoli ADSM for VM 3.1.2 ADSM VM Server Figure 2. Program Tape: File Content Tape File Content 1 Tape Header 2 Tape Header 3 Product Header 4 Product Memo 5 Service Apply Lists 6 PTFPARTs 7 Tivoli ADSM for VM Service 8 Tivoli ADSM for VM Service 9 Tivoli ADSM for VM Base Code 10 Tivoli ADSM for VM Executable Code 2.
Figure 3 (Page 2 of 2). Basic Material: Unlicensed Publications Publication Title Form Number Tivoli ADSTAR Distributed Storage Manager: Installing the Clients SH26-4080 Tivoli ADSTAR Distributed Storage Manager: Reference Cards for the Backup-Archive Clients SX26-6019 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.
Figure 5 (Page 2 of 2). Publications Useful During Installation / Service on VM/ESA Version 2.3.
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. To obtain this information, specify the following UPGRADE and SUBSET values: Figure 6.
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. 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.
5.0 Installation 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.
(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 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).
Figure 8 (Page 2 of 2). DASD Storage Requirements for Target Minidisks Storage in Cylinders Minidisk owner (user ID) Default Address 5654A09A 4E2 3390 3380 9345 5654A09A 191 3390 3380 9345 DASD Usage FB-512 Blocks SFS 4K Blocks 45 54 54 64800 8100 This is the test build disk which will 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.
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. 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 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. Follow the instructions that pertain to your VM/ESA release. The VMFINS command will be used to plan the installation.
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. 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.
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. What's Next? All remaining installation steps have already been completed for you. Continue with 6.4.2, “Place Tivoli ADSM for VM into Production” on page 25. Notes: 1.
VMFINS276 I VMFINS processing started VMFINS19 9I VMFINS PRODLIST created on your A-disk VMFINS276 I VMFINS processing completed successfully Ready; 4 5 8 Obtain resource planning information for Tivoli ADSM for VM. Note: The product will not be loaded by the VMFINS command at this time. vmfins install ppf 5654A09A {ADSM | ADSMSFS} (plan nomemo Use ADSM for installing on minidisks or ADSMSFS for installing in Shared File System directories.
VMFINS2767I Reading VMFINS DEFAULTS B for additional options VMFINS276 I VMFINS processing started VMFINS26 1R Do you want to create an override for :PPF 5654A 9A ADSM :PRODID 5654A 9A%ADSM? Enter (No), 1 (Yes) or 2 (Exit) VMFINS26 3I Processing product :PPF 5654A 9A ADSM :PRODID 5654A 9A%ADSM VMFINS19 9I 5654A 9A PLANINFO created on your A-disk VMFREQ28 5I Product :PPF 5654A 9A ADSM :PRODID 5654A 9A%ADSM has passed requisite checking VMFINT26 3I Planning for the installation of product :PPF 5654A 9A A
Note Complete this step only if you received message VMFREQ28 6W 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. 6.3.1 Installing Tivoli ADSM for VM on Minidisk 1 Obtain the user directory from the 5654A09A PLANINFO file.
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 user ID, the IPL statement must include the values "PARM FILEPOOL poolid:" (poolid is the name of the SFS Filepool where 5654A09A is enrolled). For example: IPL CMS PARM FILEPOOL NEWPOOL: This will cause CMS to automatically access 5654A09A's top directory as file mode A.
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. Near the end of the output from this command is a list of minidisks in the filepool and the number of blocks free.
3 Execute the profile to access MAINT's minidisks. 4 If the Software Inventory disk (51D) was accessed R/O (read only) then establish write access to the Software Inventory disk. profile 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. You then can issue the following commands to obtain R/W access to it.
VMFINS2767I Reading VMFINS DEFAULTS B for additional options VMFINS276 I VMFINS processing started VMFINS26 1R Do you want to create an override for :PPF 5654A 9A ADSM :PRODID 5654A 9A%ADSM? Enter (No), 1 (Yes) or 2 (Exit) VMFINS26 3I Processing product :PPF 5654A 9A ADSM :PRODID 5654A 9A%ADSM VMFREQ28 5I Product :PPF 5654A 9A ADSM :PRODID 5654A 9A%ADSM has passed requisite checking VMFINT26 3I Installing product :PPF 5654A 9A ADSM :PRODID 5654A 9A%ADSM VMFSET276 I VMFSETUP processing started for 5654A
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. The SERVICED option will build any parts that were not built on the installation tape (if any) and update the Software Inventory build status table showing that the product 5654A09A has been built.
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. This section of the Program Directory contains the procedure to install CORrective service to Tivoli ADSM for VM. VMSES/E is used to install service for Tivoli ADSM for VM.
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. 7.2 Servicing Tivoli ADSM for VM RSU Warning If applying a Tivoli ADSM for VM RSU go to the instructions in Appendix A, “Applying an RSU Tape for Tivoli ADSM for VM” on page 36.
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. Electronic Service If you are receiving service from ServiceLink (electronic service) see Appendix A, "Receiving Service for VMSES Envelopes" section 'Receive Service Documentation', in the VM/ESA Service Guide.
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). If necessary, correct any problems before going on. For information about handling specific error messages, see VM/ESA: System Messages and Codes, or use on-line HELP. vmfview mrd 7.2.
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. This command applies the service that you just received. The version vector table (VVT) is updated with all serviced parts and all necessary AUX files are generated on the alternate APPLY disk.
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 5654A 9A $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. Note: If your software inventory disk (51D) is not owned by the MAINT user ID then make sure the VMSESE PROFILE reflects the correct owning user ID.
You have finished servicing Tivoli ADSM for VM.
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. All PTF-related files are loaded to the DELTA disk. The tape file containing the preapplied service, i.e.
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.1 Apply Tivoli ADSM for VM RSU A.1.1 Prepare Your System for Service Refresh The ppfname used throughout these instructions is 5654A09A, which assumes you are using the PPF supplied by IBM for Tivoli ADSM for VM.
a If receiving the RSU from tape b If receiving the RSU from an envelope file vmfins install info (nomemo vmfins install info (nomemo env rptfnum 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. The required sizes are identified in the Tivoli ADSM for VM documentation (5654A09A MEMO D) received in the previous step.
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. The file name is appid PSUPLAN, where appid is specified in the PPF file. A.1.
VMFINS2767I Reading VMFINS DEFAULTS B for additional options VMFINS276 I VMFINS processing started VMFINS26 3I Processing product :PPF 5654A 9A ADSM :PRODID 5654A 9A%ADSM VMFREQ28 5I Product :PPF 5654A 9A ADSM :PRODID 5654A 9A%ADSM has passed requisite checking VMFINT26 3I Installing product :PPF 5654A 9A ADSM :PRODID 5654A 9A%ADSM VMFSET276 I VMFSETUP processing started for 5654A 9A ADSM VMFUTL22 5I Minidisk|Directory Assignments: String Mode Stat Vdev Label/Directory VMFUTL22 5I APPLY E R/W 2A6 DSM2A6
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. If you receive these messages, enter 1 in reply to VMFAPP2109R to reapply the reach-ahead service (as shown in the example below).
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. vmfsim query vm sysrecs tdata :ppf ppfname :stat The output from this command is similar to the following console log.
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. Perform the following steps to disable Tivoli ADSM for VM. 1 Logon to a user ID that has privilege class E authority and has access to the VMSES/E code disk (default MAINT 5E5) and VMSES/E Software Inventory disk (default MAINT 51D).
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. The CP system configuration file default name is SYSTEM CONFIG and it resides on the CP parm disk (MAINT's CF1 and CF2 minidisks).
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. By default, Tivoli ADSM for VM is installed to minidisks, as part of the VM/ESA Version 2 Release 4.0 System DDR; unless you choose to move Tivoli ADSM for VM to SFS during the initial VM/ESA 2.4.0 install.
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. 2. The following steps assume that a user-defined SFS file pool name is being used.
set filepool userfilepool: create directory dirid dirid is the name of the SFS directory you're creating, such as the default names: create create create create create directory directory directory directory directory userfilepool:5654A userfilepool:5654A userfilepool:5654A userfilepool:5654A userfilepool:5654A 9A.adsm 9A.adsm.OBJECT 9A.adsm.DELTA 9A.adsm.ALTAPPLY 9A.adsm.PRODAPPLY If necessary, see VM/ESA CMS Command Reference for more information about the CREATE DIRECTORY command.
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. 5654A09A%ADSM is the PRODID defined within the 5654A09A PPF file for the Tivoli ADSM for VM minidisk and SFS components. The VMFCOPY command will update the VMSES PARTCAT file on the target directory. C.
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 P P=========================================================P :ADSMSFS. ADSM 5654A 9A P=========================================================P :DCL. UPDATE &PROD191 DIR MYPOOL:5654A 9A. P 5654A 9A Userid A-disk &BASE DIR MYPOOL:5654A 9A.ADSM.OBJECT P Initial Product code &APPLY1 DIR MYPOOL:5654A 9A.ADSM.
Appendix D.
ANRSVM5 DSMSERV DSMEXIT DSMSERV DSMEXIT1 DSMSERV DSM ANRUME MODULE PROFILE PROFILE SAMPDIR SAMPDIR SAMPOPTS SAMPOPTS TEXT DSMAMENG TXT DSCAMENG TXT File 1 : ANRVM CNTRL SCRIPTS ANRBAROC ANRUSRXA ANRUSRXC ANRUSRXH DSMSERV ASHG 998 CMMNDLN DSMCNSL README SAMPLE SAMPLE SAMPLE SAMPLE SAMPLE IDL CLASS CLASS CLASS TXT DSMINST EXEC DSMMDISK EXEC DSMOP DSMMOUNT DSMDELET DSMAMENG DSMSERV DSMADMC ANRSVM5 DSMSERV DSMEXIT DSMSERV DSMEXIT1 DSMSERV DSM ANRUME EXEC EXEC EXEC HLP MODULE MODULE MODULE PROFILE PROFI
52 ANRVM CNTRL SCRIPTS ANRBAROC ANRUSRXA ANRUSRXC ANRUSRXH DSMSERV ASHG 998 CMMNDLN DSMCNSL P P README SAMPLE SAMPLE SAMPLE SAMPLE SAMPLE IDL CLASS CLASS CLASS HTML GIF TXT Tivoli ADSM for VM Program Directory Control file containing the Version Vector Table level Server sample SCRIPTs Server Server Server Server Server Server Server IDL Web Web Web Web Web and file client panel client panel client panel client panels client panels CMD Admin client latest info
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. Any functionally equivalent product, program, or service that does not infringe on any of IBM's intellectual property rights may be used instead of the IBM product, program, or service.
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.ibm.com - Fax from U.S.
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? Yes How many years of experience do they have? __________ No How long did it take to install this product? ____________________ If you have any comments to make about your ratings above, or any other aspect of the product installation, please list them below: Please provide the following contact information: Name
IBM Program Number: 5697-VM3 Printed in U.S.A.
