BrightStor CA-1 Tape Management - SupportConnect

More documents

Recommendations

Info

• TMSBLDVRThis section documents the TMC Build Volume Range program, TMSBLDVR, a subprogram ofTMSXTEND. TMSBLDVR can be executed in standalone mode to analyze your existing TMC andvalidate any planned volume range additions or deletions.• TMSAUDEXThis section documents the TMC Audit Extract utility, TMSAUDEX. When run in standalone mode,TMSAUDEX will inspect a BrightStor CA-1 Audit file to determine which CPUs are sharing the TMCand if they are at the proper maintenance level to support an extend function.• TMSRINITThis section documents the TMC Extend Monitor program, TMSRINIT, which is used to monitor theswitch to the new TMC. TMSRINIT is recommended to be manually executed to trigger the switch-overon systems with BrightStor CA-1 active, but having moderate or no tape activity. It will then handle thenecessary switch of the TMC and issue the TMSMR04I message when complete.TMSXTEND - Dynamic TMC Extend Process Control ProgramThe TMSXTEND utility enables you to dynamically build a new TMC while tape processing is allowed tocontinue across the shared TMC environment. Volume ranges may be added or removed by specifyingthe desired ranges as SYSIN parameters. The TMSXTEND utility saves the volume ranges internally in anew TMC record type, the Volume Definition Record. Refer to Appendix C for more detailed information onthese new Volume Definition Records.TMSXTEND may be run in TEST mode to verify the shared TMC environment before a switch is attemptedand also provides a RECOVER function to return the TMC to its previous state in the event of a failedextend attempt. Note that the utility is designed to check as many environmental details as possible beforeproceeding with a TMC switch, greatly reducing the likelihood of a problem.TMSFORMT was previously used to define a new TMC or Audit file and to extend an existing TMC. Withthe introduction of TMSXTEND, these functions are now performed by TMSXTEND, except for theformatting of a new Audit file. In addition, those customers with nonstandard volume serial numbers (asdiscussed below) should continue to use TMSFORMT to extend the TMC or define a new TMC.RESTRICTIONS:• Nonstandard Volume Serial Numbers:A small number of BrightStor CA-1 customers have nonstandard volume serial numbers defined in theirTMC that cannot be processed by TMSXTEND. A nonstandard volser is defined as any volser with alphacharacters in the rightmost positions of the volser or with blanks to the left of a 4 or 5 character volser.Examples of nonstandard volsers are 0920XT, 00010A, or ' 12345'. These customers must continue to runthe special versions of BrightStor CA-1 user exits TMSUX2U and TMSUX2E that they have coded tosupport these volsers. Users with these volsers should plan to eliminate their use over time to enable themto take advantage of the convenience of the TMSXTEND utility.Short 3, 4, or 5 character volsers with the blank on the right are valid. Volsers with alpha characters on theleft or even middle are also valid. Examples of VALID volsers would be '12345 ', 9XT456, and ABC123. Forall these types of volsers, there will be no need to maintain the CA-1 TMSUX2U and TMSUX2E exits.• IPL Requirement:An IPL is required before the first execution of TMSXTEND. It is possible to install the PTFs and continuerunning CA-1; however, you must IPL prior to running TMSXTEND to fully install the required components.Note that this IPL can be done weeks, months, or even years before the TMSXTEND utility is actuallyPDC# QI53827
used. The IPL is not required immediately after the CA-1 linklist library has been refreshed. It is possible tocopy over the new CA-1 library days or weeks before an IPL is performed.• Reverse Conversion:The output of the TMSXTEND utility is a new format TMC with volume ranges defined internally in a newtype of record, the Volume Definition record. A TMC created in this format is described as an ExtendedFormat TMC. Once a TMC has been converted to this format, the only way to convert back to the previousTMC format is by running TMSSPLIT to SPLIT off (export) all TMC and DSNB entries to a sequential file,followed by a MERGE process to import them into a TMC defined with TMSFORMT. This can be a verytime-consuming process in larger installations. User exits TMSUX2U and TMSUX2E would also have tobe re-activated with an IPL. For this reason it is critical that you plan your conversion to the ExtendedFormat TMC well and do not convert back.If you want to test the complete conversion (always a good idea), it is recommended that you make a copyof your TMC before the conversion. Then, after the conversion has completed and you have finished anytesting, simply restore the TMC with no Audit records and re-IPL to re-establish exits TMSUX2E andTMSUX2U. You will have lost all updates done to the TMC after the conversion, so any volumes used foroutput should have their DSN17 fields set to hex-zeros to prevent NS28 dismounts.• User Written Programs:Customers who have written their own programs to read and/or update the TMC must check to insure thatthey can process the new Extended Format TMC. In general, programs that do not process DSNBs shouldwork without modification. Contact your local BrightStor CA-1 Support organization if you need help indetermining if your user-written programs will need modification.• BrightStor CA-Vantage SRM and CAIGMI:BrightStor CA-Vantage and the CAIGMI graphical interface that is built from a subset of BrightStor CA-Vantage both require maintenance to process an Extended Format TMC. For BrightStor CA-Vantage andCAIGMI Release 6.2, PTF QO53276 is required to allow both products to access the new ExtendedFormat TMC. PTF QO53275 is provided for R11.1 of BrightStor CA-Vantage and CAIGMI. Theappropriate PTF for your release level must be applied to all systems in a shared TMC environment whereBrightStor CA-Vantage or CAIGMI are run. Note that you may upgrade to BrightStor CA-1 Release 11 andcontinue to run BrightStor CA-Vantage or CAIGMI if you do not run TMSXTEND to create an ExtendedFormat TMC; however, all systems must be upgraded when TMSXTEND is run.• BrightStor VM:Tape:Customers running BrightStor VM:Tape must apply maintenance to that product if it is configured to sharea TMC with BrightStor CA-1. If you are running BrightStor VM:Tape and sharing a TMC, contact your localBrightStor VM:Tape Technical Support organization to obtain the necessary maintenance. TheTMSAUDEX utility can be executed to determine if a BrightStor VM:Tape system sharing the TMC is backlevel. Refer to the description of TMSAUDEX for further information.• Changes to existing utilities:There are a few minor changes to existing utilities that should also be noted.1. TMSREMOV should NOT be used to remove volume ranges already in DELETE status on anExtended Format TMC. Instead, the REMVOL control statement of TMSXTEND should be used toremove those volumes.2. TMSFORMT should NOT be used when the input is an Extended Format TMC. If you need to addmore volumes to a TMC that is already in the new format, simply run TMSXTEND again.3. TMSBINQ reports will report zero (0) as the number of ranges for a new format TMC. Since thereis no longer a limit to the number of volume ranges, there is no reason to maintain a count field ofthem in the control records.PDC# QI53827
Page 1 and 2: BrightStor® CA-1® Tape Management
Page 5 and 6: COMPUTER ASSOCIATES INTERNATIONAL,
Page 7: • Data Erase UtilityA new Data Er
Page 10 and 11: Drop Support Date for Release 5.2:C
Page 12 and 13: This utility accepts input either v
Page 14 and 15: After all volumes have been written
Page 16 and 17: In this example, logical volumes LV
Page 18 and 19: QUERY COMPLETE, VOLUME IN ROBOT - A
Page 21 and 22: BrightStor CA-1 Product Documentati
Page 23 and 24: Note that a meaningful compression
Page 25 and 26: Replace line-----------------------
Page 27: with the following:----------------
Page 30 and 31: 1.28.3.1 Job Control Statements//st
Page 32 and 33: *** TESTRDS NOT VALID WITH DSNBS, T
Page 34 and 35: show a volser if either the TMACVOL
Page 36 and 37: User response: If this is an AIVS v
Page 38 and 39: CA-1 Retention data set Rules (Opti
Page 40 and 41: Specification:If set to YES, the Cn
Page 42 and 43: Or no valid input command was found
Page 44 and 45: Thank you for your continued suppor
Page 46 and 47: For example, if volume 123456 is de
Page 48 and 49: CONCLUSION:In addition to these opt
Page 52 and 53: 4. TMSBINQ, the online TMSTIQ displ
Page 54 and 55: FOLLOW UP PROCEDURES AFTER INITIAL
Page 56 and 57: Appendix A., TMC Volume Definition
Page 58 and 59: User Response: None. Information on
Page 60 and 61: TMSXT05I ATTACH TMSBLDVR TO COPY/EX
Page 62 and 63: User Response: None. Information on
Page 64 and 65: TMSXT80E COULD NOT OBTAIN TMSVOLU T
Page 66 and 67: 52 82 EXTEND ALREADY ACTIVESee msg
Page 68 and 69: TMS REPORT-80 Report Field Definiti
Page 70 and 71: TMS REPORT-81 Report Field Definiti
Page 72 and 73: Eyy-112 I/O ERROR ON TMCExplanation
Page 74: (29 CPU entries in same format not

BrightStor CA-1 Tape Management - SupportConnect

Create successful ePaper yourself

Delete template?

Save as template?