IBM TIVOLI ADSTAR 5697-VM3 User Manual
  1. Manuals
  2. Brands
  3. IBM Manuals
  4. Software
  5. TIVOLI ADSTAR 5697-VM3
  6. User manual
IBM TIVOLI ADSTAR 5697-VM3 User Manual

IBM TIVOLI ADSTAR 5697-VM3 User Manual

Distributed storage manager for vm
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
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.0
Document Date: June 1999
GI10-0548-00

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the TIVOLI ADSTAR 5697-VM3 and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for IBM TIVOLI ADSTAR 5697-VM3

Summary of Contents for IBM TIVOLI ADSTAR 5697-VM3

  • Page 1 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.0 Document Date: June 1999 GI10-0548-00...
  • Page 2 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.

  • Page 3: Table Of Contents

    7.1 VMSES/E Service Process Overview  Copyright IBM Corp. 1992, 1999 ........
  • Page 4 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...

  • Page 5: Introduction

    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.

  • Page 6: Important Vm/Esa 2.4.0 Information

    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;...

  • Page 7: Program Materials

    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.

  • Page 8: Optional Machine-Readable Material

    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...

  • Page 9: Microfiche Support

    Tivoli ADSTAR Distributed Storage Manager: Reference Cards for the Backup-Archive Clients 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.
  • Page 10 Figure 5 (Page 2 of 2). Publications Useful During Installation / Service on VM/ESA Version 2.3.0 and higher Publication Title VM/ESA: VMSES/E Introduction and Reference VM/ESA: Service Guide VM/ESA: Planning and Administration VM/ESA: CMS Command Reference VM/ESA: CMS File Pool Planning, Administration, and Operation VM/ESA: System Messages and Codes Tivoli ADSM for VM Program Directory Form Number...

  • Page 11: Program Support

    565511901 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.

  • Page 12: Program And Service Level Information

    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).  Copyright IBM Corp. 1992, 1999...

  • Page 13: Installation Requirements And Considerations

    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.

  • Page 14: Program Installation/Service Considerations

    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.

  • Page 15: Dasd Storage Requirements For Target Minidisks

    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.
  • Page 16 Figure 8 (Page 2 of 2). DASD Storage Requirements for Target Minidisks Storage in Minidisk Cylinders owner Default (user ID) Address DASD 5654A09A 3390 3380 9345 5654A09A 3390 3380 9345 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.

  • Page 17: Installation Instructions

    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.

  • Page 18: Plan Your Installation For Tivoli Adsm For Vm

    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.
  • Page 19 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.
  • Page 20 2. If you do not have a set of manuals for Tivoli ADSM for VM 3.1.2, you should contact your IBM marketing representative and order Tivoli ADSM for VM as described in 2.0, “Program Materials” on page 3. Remember to check the area which indicates to suppress media shipment, which will order you a set of manuals for Tivoli ADSM for VM 3.1.2.
  • Page 21 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 Notes: a. If you change the PPF name, a default user ID, or other parameters via a b.
  • Page 22 Tivoli ADSM for VM Program Directory...
  • Page 23 Note Complete this step only if you received message required by Tivoli ADSM for VM: either IBM Language Environment (5688-198) or IBM C/370 Library (5688-188). This message indicates that the product or products listed is/are a pre-requisite product for Tivoli ADSM for VM but were not found in the current system inventory.

  • Page 24: Allocate Resources For Installing Tivoli Adsm For Vm

    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 Create the 5654A09A user directory for SFS install. 6.3.1 Installing Tivoli ADSM for VM on Minidisk Obtain the user directory from the 5654A09A PLANINFO file.
  • Page 25 Change the password for 5654A09A from accordance with your security guidelines. 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).

  • Page 26: Install Tivoli Adsm For Vm

    The ppfname used throughout these installation instructions is 5654A09A, which assumes you are using the PPF supplied by IBM for Tivoli ADSM for VM. If you have your own PPF override file for Tivoli ADSM for VM, you should use your file's ppfname instead of 5654A09A. The ppfname you selected should be used throughout the rest of this procedure.
  • Page 27 Execute the profile to access MAINT's minidisks. profile 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.
  • Page 28 Review the install message log ($VMFINS $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 install Tivoli ADSM for VM Program Directory...

  • Page 29: Update Build Status Table For Tivoli Adsm For Vm

    6.4.1 Update Build Status Table for Tivoli ADSM for VM Update the VM SYSBLDS software inventory file for Tivoli ADSM for VM. vmfins build ppf 5654A09A {ADSM | ADSMSFS} (serviced nolink Review the install message log ($VMFINS $MSGLOG). If necessary, correct any problems before going on.
  • Page 30 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. Tivoli ADSM for VM Program Directory...

  • Page 31: Service Instructions

    All local service (mods) must be entered into the software inventory to allow VMSES/E to track the changes and build them into the system. Refer to Chapter 7 in the VM/ESA Service Guide for this procedure.  Copyright IBM Corp. 1992, 1999...

  • Page 32: Servicing Tivoli Adsm For Vm

    The ppfname used throughout these servicing instructions is 5654A09A, which assumes you are using the PPF supplied by IBM for Tivoli ADSM for VM. If you have your own PPF override file for Tivoli ADSM for VM, you should use your file's ppfname instead of 5654A09A. The ppfname you selected should be used throughout the rest of this procedure, unless otherwise stated differently.
  • Page 33 Receive the documentation. vmfrec info Check the receive message log ($VMFREC $MSGLOG) for warning and error messages. vmfview receive Read the product memo (5654A09A MEMO) before going on. This memo was loaded to the A-disk. Setup the correct minidisk acess order. vmfsetup 5654A09A {ADSM | ADSMSFS} Merge previously applied service to ensure that you have a clean alternate APPLY disk for new service.

  • Page 34: Receive The Service

    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.2 Receive the Service Electronic Service If you are receiving service from ServiceLink (electronic service) see Appendix A, Receiving Service for VMSES Envelopes , section Receive the Service , in the VM/ESA Service Guide.

  • Page 35: Apply The Service

    7.2.3 Apply the Service Apply the new service. vmfapply ppf 5654A09A {ADSM | ADSMSFS} Review the apply message log ($VMFAPP $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 apply Note If you get the message VMFAPP2120W then re-apply any local modifications before building the...

  • Page 36: Update The Build Status Table

    7.2.4 Update the Build Status Table Update the Build Status Table with serviced parts. vmfbld ppf 5654A09A {ADSM | ADSMSFS} (status Tivoli ADSM for VM Program Directory Use ADSM for installing on minidisks or ADSMSFS for installing in Shared File System directories. This command updates the Build Status Table.
  • Page 37 Note If the $PPF files have been serviced you will get the following prompt: vmfppf 5654A09A * copyfile 5654A09A $PPF a = = d (olddate replace erase 5654A09A $PPF a vmfbld ppf 5654A09A {ADSM | ADSMSFS} (status Enter a 0 and complete the following steps before you continue.

  • Page 38: Build Serviced Objects

    Use VMFVIEW to review the build status messages, and see what objects need to be built. vmfview build 7.2.5 Build Serviced Objects Rebuild Tivoli ADSM for VM serviced parts. vmfbld ppf 5654A09A {ADSM | ADSMSFS} (serviced Review the build message log ($VMFBLD $MSGLOG). If necessary, correct any problems before going on.
  • Page 39 You have finished servicing Tivoli ADSM for VM. Service Instructions...

  • Page 40: Appendix A. Applying An Rsu Tape For Tivoli Adsm For Vm

    Tivoli ADSM for VM. Reapplying Local Modifications (if applicable) All local modifications must be entered into the software inventory to allow VMSES/E to track the changes and build them into the system.  Copyright IBM Corp. 1992, 1999...

  • Page 41: Apply Tivoli Adsm For Vm Rsu

    The ppfname used throughout these instructions is 5654A09A, which assumes you are using the PPF supplied by IBM for Tivoli ADSM for VM. If you have your own PPF override file for Tivoli ADSM for VM you should use your file's ppfname instead of 5654A09A. The ppfname you use should be used throughout the rest of this procedure.
  • Page 42 vmfins install info (nomemo vmfins install info (nomemo env rptfnum 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.

  • Page 43: Receive The Preapplied, Prebuilt Service

    A.1.2 Receive the Preapplied, Prebuilt Service Refresh the Tivoli ADSM for VM service disks by loading new service from the RSU Tape vmfins install ppf 5654A09A {ADSM | ADSMSFS} (nomemo nolink override no vmfins install ppf 5654A09A {ADSM | ADSMSFS} (nomemo nolink env rptfnum override no Use ADSM for installing on minidisks or ADSMSFS for installing in Shared File System directories.

  • Page 44: Process Additional Service

    Check the receive message log ($VMFREC $MSGLOG) for warning and error messages. If necessary, correct any problems before going on. For information about handling specific receive messages, see VM/ESA: System Messages and Codes, or use online HELP. vmfview install A.1.3 Process Additional Service Apply additional service The VMFAPPLY command is used to reapply service that was not contained on the refresh tape that was already installed for the component.

  • Page 45: Build The New Service Level And Place Into Production

    vmfapply ppf 5654A09A {ADSM | ADSMSFS} VMFAPP2122E The set of PTFs in the Apply Status Table (5654A09A SRVAPPS) on the 2A2 (F) disk is not a subset of the PTFs in the highest Level Apply Status Table on the 2A6 (E) disk. This is an inconsistent state. VMFAPP2109R VMFAPPLY will automatically correct the problem identified by message 2122E by including the missing PTFs in the current Apply List.

  • Page 46: Determine Rsu Service Level

    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 Tivoli ADSM for VM Program Directory following console log.

  • Page 47: Appendix B. Disabling Tivoli Adsm For Vm

    In order to retain the DISABLED state for Tivoli ADSM for VM, update the CP system configuration file with the information in the 5654A09A PRODSYS file.  Copyright IBM Corp. 1992, 1999 The 5E5 minidisk is where VMSES/E resides. The 51D minidisk is where the VMSES/E Software Inventory files and other product dependent files reside.
  • Page 48 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.

  • Page 49: Appendix C. Moving Tivoli Adsm For Vm To Sfs Directories And Creating Ppf Override

    VM/ESA Installation Guide) you need to return to the section that pointed you to this appendix and continue from there (if you were pointed to this appendix). C.1 Setup SFS File Pool and Directories  Copyright IBM Corp. 1992, 1999...
  • Page 50 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.

  • Page 51: Copy Minidisk (Or Sfs) Files To Sfs Directories

    set filepool userfilepool: create directory dirid If you intend to use an SFS directory as the work space for the 5654A09A used ID, include the following IPL control statement in the 5654A09A directory entry: This will cause CMS to automatically access the 5654A09A's top directory as file mode A.

  • Page 52: Create Product Parameter File (Ppf) Override

    C.3 Create Product Parameter File (PPF) Override This section provides information to help you create a product parameter file (PPF) override. The example used in this section is how to change the shared file system (SFS) file pool where Tivoli ADSM for VM files reside.
  • Page 53 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. This override will replace the :DCL. section of the adsmsfs override area of the 5654A09A $PPF file. If your $PPF override file was created at file mode A, copy it to file mode D—the Software Inventory minidisk (MAINT 51D).

  • Page 54: Appendix D. Adsm Installation Tape Contents

    Appendix D. ADSM Installation Tape Contents  Copyright IBM Corp. 1992, 1999...
  • Page 55 Appendix D. ADSM Installation Tape Contents...
  • Page 56 Tivoli ADSM for VM Program Directory...

  • Page 57: Appendix E. Notices

    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.
  • Page 58 Tivoli ADSM for VM Program Directory...

  • Page 59: Reader's Comments

    Or you may use this form to comment about this document, its organization, or subject matter. Please understand that your feedback is of importance to IBM, but IBM makes no promises to always provide a response to your feedback. For each of the topics below please indicate your satisfaction level by circling your choice from the rating scale. A rating of a 1 represents Very Satisfied, where a rating of a 5 represents Very Dissatisfied.
  • Page 60 Address Telephone Thank you for your participation. Please send the completed form to the following address, or give to your IBM representative who will forward it to the Tivoli ADSTAR Distributed Storage Manager Development group: International Business Machines Corporation Information Development Dept.
  • Page 62  Program Number: 5697-VM3 5802 6001 Printed in U.S.A.

This manual is also suitable for:

Tivoli adstar

Table of Contents