BrightStor CA-1 Tape Management - SupportConnect

More documents

Recommendations

Info

Sharing an unblocked TMC between systems of different maintenance levels, which do not all have thisAPAR installed, does not cause any problems.Blocking the TMC:Once all systems sharing the TMC and Audit files have been IPL'ed with this enhancement active, CA-1 canbe started with a blocked TMC. Blocking the TMC may be a consideration to save disk space. Apart fromsome reporting tools which use QSAM access, it will not significantly improve access performance of theTMC for tape processing or CA-1 utilities.When the TMC is blocked, the block size may be any multiple of the record length, 340, except 680. Thesmallest valid block size is 1020. Also, when a very small TMC is created for test purposes, it must consistof at least 2 blocks. CA-1 cannot process the data set if all records are contained in one block. Arecommended block size value is BLKSIZE=8840.While utilities TMSFORMT, TMSREMOV and TMSCOPY have been enhanced to allow for a blocked formatwhen creating a new TMC, a format or restore operation is not necessary to block an existing TMC. Simplyuse IEBGENER to copy the data set and specify the desired BLKSIZE in the SYSUT2 DD statement.There are no known compatibility problems with this change and any MVS product accessing the TMC. AllCA or OEM products or user programs which use CA-1 macros to read or update the TMC will work fine witha blocked TMC and not require any changes. If your TMC is shared with a non-MVS system, please contacttechnical support of the respective product for further information.Installation checklist:The following procedure should be used to upgrade one system at a time. The upgrade includes a systemIPL. If the TMC data set is shared among multiple CPUs, it can continue to be accessed normally from allother systems during the upgrade.Perform the following tasks to correctly apply this APAR:1. Back up your current CA-1 target environment.2. Apply the APAR to your target CAILIB.Ensure that updated modules are not accidentally invoked through LLA refresh or CAS9 REINIT etc.while CA-1 is active.3. Stop tape processing on the target system.4. If necessary, copy your maintenance target library into the production target library.Ensure that the linklist and all affected procedures (CAS9, CTS, TMSINIT, CA-1 batch utilities)exclusively point to the updated library.5. IPL your system.6. Run CAS9 and start TMSINIT as usual.PDC#: QI12531
7. Run any IVP jobs to test tape processing and batch/online TMC inquiry. TMSCKLVL can be used toverify the maintenance level of the active SVC module TMS00SVC. All csects updated by theenhancement should show eyecatcher PFFC044, unless remodified by subsequent maintenance.TMSCKLVL also displays the level of the TMSTMVT module which was loaded by CAS9 after the lastIPL. LEVEL = TVT5200 indicates the old level, LEVEL = TVT5201 indicates the PFFC044 level ofTMSTMVT is active.8. If all results are OK, resume tape processing.If a backout of the maintenance should be required, restore the APAR from your target library andrepeat steps 3 through 7 accordingly.Once all systems sharing the TMC have been upgraded and are running at the new level withoutproblems, the TMC can be reblocked if desired.*** The following steps are required to reblock the TMC: ***9. Run TMSCKLVL on all systems to verify that the active TMSTMVT and TMS00SVC modules show thecorrect maintenance level.10. Stop tape processing on all systems sharing the TMC.11. If subtask DBS is active in the CTS address space, issue the following CTS command to unallocate theTMC:MSG DBS,'RELEASE TMC'12. Back up the TMC using TMSCOPY.13. Allocate a new TMC data set on a shared device which is accessible from all systems. SpecifyDSORG=PSU in the DCB parameter, unless the volume is SMS controlled. Provide the desired blocksize:DCB=(DSORG=PSU,RECFM=FB,LRECL=340,BLKSIZE=n*340)14. Execute IEBGENER to copy the production TMC into the blocked TMC.15. Rename the production TMC to an alternate name, and catalog the blocked TMC under the productionname on all CPUs.16. Run TMSINIT to restart CA-1 on all systems.17. Run any IVP jobs to test tape processing and batch/online TMC inquiry. Ensure all systems are pointingto the same TMC data set and can access it properly. If any problems occur, rename the blocked TMCto an alternate name, and catalog the original TMC under the production name on all systems. Go backto step 16 to re-activate the original, unblocked TMC.18. If all results are OK, resume tape processing.19. If the DBS subtask is active in the CTS address space, issue the following command to re-allocate theTMC:MSG DBS,'OBTAIN TMC'If you need to backout the change, perform the same steps 10 through 19 accordingly to unblock your TMC.PDC#: QI12531
Page 1 and 2: BrightStor CA-1® Tape ManagementPr
Page 3: This Product Information Packet con
Page 6 and 7: Blocked TMC SupportUpdated versions
Page 8 and 9: 3. Non CA-Activator ConsiderationsT
Page 11 and 12: BrightStor CA-1 Product Error Alert
Page 13: BrightStor CA-1 Product Error Alert
Page 16 and 17: IMPACT:Tapes may be re-labelled ina
Page 18 and 19: Samples:1. If an EDM uses program p
Page 21 and 22: BrightStor CA-1 Product Documentati
Page 23: User Response: This normally occurs
Page 28 and 29: Documentation updates related to th
Page 30 and 31: Add the following message instead:I
Page 33 and 34: BrightStor CA-1 Product Documentati
Page 35 and 36: CA-1 Product Documentation ChangeDA

BrightStor CA-1 Tape Management - SupportConnect

Create successful ePaper yourself

Delete template?

Save as template?