Installation instructions for IBM tape analysis tools 2012Nov12 Updated: APF library is added 2018Feb13 Updated: The pharase "Use WordPad to view on PC" is removed 2018Feb28 as useless Updated: the content has been actualized 2018Apr16 Updated: the content of item 22 has been actualized 2021Feb04 The IBM Tape Analysis Tools are licensed, not sold. The license agreement can be found at http://public.dhe.ibm.com/storage/tapetool/ as: $$_License_Areeement_for_IBM_Tape_Tools.doc There are no guarantees that the programs will run in every customer environment or with different sets of data, but we provide best effort support for all of the distributed tools. Program enhancements will be made to handle data format changes when they occur. If you try to run new data with old program versions, results may be unpredictable. To avoid this situation, you need to be informed of these enhancements. To be informed of major changes to any of the tools distributed via this ftp site, send an email message to: TAPETOOL@US.IBM.COM In the subject, specify NOTIFY. Nothing else is required in the body of the note. This will add you to our change distribution list. Fixes and enhancements are logged in UPDATES.TXT on the ftp sites and you should review this file at least quarterly. There are four files on the FTP site that make up the IBM Tape Tools package. IBMJCL.XMI - Execution JCL for current tape analysis tools. IBMCNTL.XMI - Parameters needed for job execution, but do NOT need to be modified by the user. IBMLOAD.XMI - Load library for executable load modules. Currently Batch Magic and VTSA analyses plus the JCL tailoring job are the only tools that use load modules. IBMPAT.XMI - Data pattern library only needed if you will be running the QSAMDRVR utility. JCL library contains $READxx members that describe each process in more detail. If you already have the IBMTOOLS.JCL library, you can run member FTPTOOLS or follow the step by step proceedure below. Installation at the customer site. Refer to the instructions for installing directly from TSO if you want to bypass the PC. 1. Copy the individual .XMI files to the hard drive of a PC that is network attached to an MVS Operating System so you can upload to MVS. *** Before doing file transfer to host, you may need to create a new transfer template. Look in Transfer "pull-down-menu" for "setup" or "create template". Create a template for BIN80 if it doesn't already exist. Use the standard BINARY template to start, but use RECFM=F, LRECL=80, and BLKSIZE=3120 for the new template. Do not use ACSII or CRLF. Use a space request for CYLS,(8,2). *** If you are using an FTP program that doesn't give you the option of setting RECFM or LRECL, you will have to pre-allocate the data sets on the mainframe under your TSO id first. With ISPF 3.2, use RECFM=FB,LRECL=80, BLKSIZE=3120, with NO directory blocks for all four files to allocate physical sequential files. When you then to use RECEIVE INDSN(xxx.XMI), it will create partitioned data sets. Be sure allocate enough space to hold 600 blocks of data (at 3120). *** Also, you may have to issue the file transfer commands from the TSO READY prompt instead of ISPF 6. Systems using PCOMM should be fine using ISPF 6. 2. From ISPF 6, use PC-to-host-transfer to copy each file from your PC disk to your MVS system. *** Use BIN80 *** 3. From ISPF 6, enter the TSO command: RECEIVE INDSN(IBMJCL.XMI) 4. Reply DSN(IBMTOOLS.JCL) when asked for restore options. (default) Reply "R" to replace members if library already exists. 5. Repeat steps 4 and 5 for each file. 6. You can now delete IBMLOAD.XMI, IBMJCL.XMI, IBMCNTL.XMI, and IBMPAT.XMI. ** IMPORTANT ** Read item 9. ** IMPORTANT ** 7. Copy, edit and submit userid.IBMTOOLS.JCL($$CPYLIB) to create a new JCL library that has a unique second node (&SITE symbolic). This will create a private JCL library for you that you can submit jobs from while leaving the original asis. The CNTL and LOAD can then be shared by multiple users running jobs from the same system. 8. EDIT and submit userid.SITENAME.IBMTOOLS.JCL($$TAILOR) to tailor the JCL. 9. Submit tools jobstreams from userid.SITENAME.IBMTOOLS.JCL. To use FTP directly from TSO, follow these steps. 1. Allocate the following physical sequential files in zOS with RECFM=FB, LRECL=80 a. userid.IBMLOAD.XMI b. userid.IBMCNTL.XMI c. userid.IBMJCL.XMI d. userid.IBMPAT.XMI (only needed if planning on using QSAMDRVR) Then from option 6 of ISPF, 1. Enter FTP public.dhe.ibm.com At FTP prompts: 2. When prompted for user ID, enter: anonymous 3. When prompted for password, enter your e-mail address 4. cd /storage/tapetool/ 5. bin 6. get ibmload.xmi ibmload.xmi (replace 7. get ibmcntl.xmi ibmcntl.xmi (replace 8. get ibmjcl.xmi ibmjcl.xmi (replace 9. get ibmpat.xmi ibmpat.xmi (replace 10. quit At ISPF Option 6 prompt: 11. receive indsn('userid.ibmload.xmi') 12. Respond with DSN('userid.IBMTOOLS.LOAD') 13. receive indsn('userid.ibmcntl.xmi') 14. Respond with DSN('userid.IBMTOOLS.CNTL') 15. receive indsn('userid.ibmjcl.xmi') 16. Respond with DSN('userid.IBMTOOLS.JCL') 17. receive indsn('userid.ibmpat.xmi') 18. Respond with DSN('userid.IBMTOOLS.PATTERNS') ** IMPORTANT ** Read item 19. ** IMPORTANT ** 19. Copy, edit and submit userid.IBMTOOLS.JCL($$CPYLIB) to create a new JCL library that has a unique second node (&SITE symbolic). This will create a private JCL library for you that you can submit jobs from while leaving the original asis. The CNTL and LOAD can then be shared by multiple users running jobs from the same system. 20. EDIT and submit userid.SITENAME.IBMTOOLS.JCL($$TAILOR) to tailor the JCL. 21. Submit tools jobstreams from userid.SITENAME.IBMTOOLS.JCL. ** IMPORTANT ** Read item 22. ** IMPORTANT ** 22. Before to run the jobs: BVIRHSTS, CHKCOPY, COPYRFSH, IFASMFDP, ISSUECMD, LIBEJECT MOUNTMON, PRESTAGE, RCVRPVOL, SLEEPCHK, TCDBMCH, TCDB2BVR, please copy the following load modules to an APF (Authorized Program Facility) library and change STEPLIB to point to that library before running: BVIRPRPT, CBRSPLCS, CHKCOPY, COPYRFSH, CPYHIST, ISSUECMD, MOUNTMON, RCVRPVOL, RESETSG, SLEEPCHK, STAGEVOL, TCDBMCH, TCDB2BVR BVIRPRPT - if using RECLAIMGB for copy-export volumes, module BVIRPRPT must be in an APF library. CBRSPLCS - used in the job LIBEJECT RCVRPVOL - RCVRPVOL must be in an APF library if it is going to be used used to issue the LIB REQ commands. STAGEVOL - is used for PRESTAGE job. After changes done on January 25 the following load modules must be copy to the same APF library as well: COMPARSE, INTERVAL, SMFILTER (for job IFASMFDP only) because they are called dynamically from the load modules from the previous list.