BrightStor CA-1 Tape Management - SupportConnect
BrightStor CA-1 Tape Management - SupportConnect
BrightStor CA-1 Tape Management - SupportConnect
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
used. The IPL is not required immediately after the <strong>CA</strong>-1 linklist library has been refreshed. It is possible tocopy over the new <strong>CA</strong>-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 <strong>BrightStor</strong> <strong>CA</strong>-1 Support organization if you need help indetermining if your user-written programs will need modification.• <strong>BrightStor</strong> <strong>CA</strong>-Vantage SRM and <strong>CA</strong>IGMI:<strong>BrightStor</strong> <strong>CA</strong>-Vantage and the <strong>CA</strong>IGMI graphical interface that is built from a subset of <strong>BrightStor</strong> <strong>CA</strong>-Vantage both require maintenance to process an Extended Format TMC. For <strong>BrightStor</strong> <strong>CA</strong>-Vantage and<strong>CA</strong>IGMI 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 <strong>BrightStor</strong> <strong>CA</strong>-Vantage and <strong>CA</strong>IGMI. Theappropriate PTF for your release level must be applied to all systems in a shared TMC environment where<strong>BrightStor</strong> <strong>CA</strong>-Vantage or <strong>CA</strong>IGMI are run. Note that you may upgrade to <strong>BrightStor</strong> <strong>CA</strong>-1 Release 11 andcontinue to run <strong>BrightStor</strong> <strong>CA</strong>-Vantage or <strong>CA</strong>IGMI if you do not run TMSXTEND to create an ExtendedFormat TMC; however, all systems must be upgraded when TMSXTEND is run.• <strong>BrightStor</strong> VM:<strong>Tape</strong>:Customers running <strong>BrightStor</strong> VM:<strong>Tape</strong> must apply maintenance to that product if it is configured to sharea TMC with <strong>BrightStor</strong> <strong>CA</strong>-1. If you are running <strong>BrightStor</strong> VM:<strong>Tape</strong> and sharing a TMC, contact your local<strong>BrightStor</strong> VM:<strong>Tape</strong> Technical Support organization to obtain the necessary maintenance. TheTMSAUDEX utility can be executed to determine if a <strong>BrightStor</strong> VM:<strong>Tape</strong> 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