BrightStor CA-1 Tape Management - SupportConnect

BrightStor® CA-1® Tape ManagementProduct Information PacketRelease 11AL0B00404P1

This documentation and related computer software program (hereinafter referred to as the "Documentation") isfor the end user's informational purposes only and is subject to change or withdrawal by Computer AssociatesInternational, Inc. ("CA") at any time.THIS DOCUMENTATION MAY NOT BE COPIED, TRANSFERRED, REPRODUCED, DISCLOSED, ORDUPLICATED, IN WHOLE OR IN PART, WITHOUT THE PRIOR WRITTEN CONSENT OF CA. THISDOCUMENTATION IS PROPRIETARY INFORMATION OF CA AND PROTECTED BY THE COPYRIGHTLAWS OF THE UNITED STATES AND INTERNATIONAL TREATIES.TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION "AS IS"WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIEDWARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, ORNONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO THE END USER OR ANY THIRD PARTYFOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION,INCLUDING WITHOUT LIMITATION, LOST PROFITS, BUSINESS INTERRUPTION, GOODWILL, ORLOST DATA, EVEN IF CA IS EXPRESSLY ADVISED OF SUCH LOSS OR DAMAGE.THE USE OF ANY PRODUCT REFERENCED IN THIS DOCUMENTATION AND THISDOCUMENTATION IS GOVERNED BY THE END USER'S APPLICABLE LICENSE AGREEMENT.The manufacturer of this documentation is Computer Associates International, Inc.Provided with "Restricted Rights" as set forth in 48 C.F.R. Section 12.212, 48 C.F.R. Sections 52.227-19(c)(1) and (2) or DFARS Section 252.227.7013(c)(1)(ii) or applicable successor provisions.Support InformationCall Computer Associates technical services for any information not covered in this or the relatedpublications. You can find the appropriate direct telephone number for Technical Support for each CAproduct under the Support button at http://www.ca.com/ on the Internet. Alternately, in North America, youmay call 1-800-645-3042 or 1-631-342-4683 and your call will be returned as soon as possible. OutsideNorth America, contact your local Computer Associates technical support center for assistance.Release 11, April 2004(c) 2004 Computer Associates International, Inc.,One Computer Associates Plaza, Islandia, NY 11749All rights reserved.All trademarks, trade names, service marks, and logos referenced herein belong to their respectivecompanies.

COMPUTER ASSOCIATES INTERNATIONAL, INC.5465 Legacy Drive Plano, TX 75024-3106Telephone (214) 473-1000 FAX (214) 473-1050To:From:BrightStor CA-1 Tape Management CustomersThe Computer Associates BrightStor CA-1 Product GroupDate: April xx, 2004Subject: BrightStor CA-1 Tape Management Release 11PML#: QI53828Dear Customers:Computer Associates International, Inc. is pleased to present you with Release 11 of BrightStor CA-1 TapeManagement, an integral component of the Storage solutions we provide for the z/OS operating system.This new version is being provided as maintenance to Release 5.2 as a convenience to you. That is, wehave not changed the SMP FMID so that you can simply receive and apply this new version as a servicepack for Release 5.2.Prerequisites:- Any supported release of the z/OS operating system- CA Common Services for z/OS and OS/390 Release 3.0 or higherGetting Started:1. Check the contents of this package against the enclosed packing list. Call your Technical Supportorganization for BrightStor CA-1 if you encounter any discrepancies.2. Refer to the installation and maintenance instructions found in the BrightStor CA-1 Getting Startedguide and Systems Programmer Guide.3. Review any enclosed Product Error Alerts or Product Documentation Changes to determine whether ornot they pertain to your environment.4. The VOLSER of the BrightStor CA-1 Release 11 tape is L00404. Please be sure to use this VOLSERin any JCL that will access this tape.BrightStor CA-1 Enhancements in Release 11:BrightStor CA-1 Release 11 contains a number of enhancements, including the following:

• Dynamically Extend the TMCThis feature allows the Tape Management Catalog (TMC) to be extended by dynamically creating aduplex “shadow” TMC while tape activity is ongoing, and providing a means to swap over to the new,expanded TMC. This feature simplifies the process of adding or removing volume ranges from theTMC and reduces the need to stop all tape processing to extend the TMC. Customers can specifytheir desired external volume serial number ranges in control statements used by the new TMC Extendutility, TMSXTEND. BrightStor CA-1 will dynamically build the necessary conversion routines fromthese statements and save the volume serial number ranges in the TMC, eliminating the requirementfor coding user exits TMSUX2E and TMSUX2U. Customers were previously required to code thesetwo user exits if they wanted to allow alphanumeric volume serial numbers to be used.Refer to the Product Documentation Change (PDC) for the TMC Extend feature provided in thispackage for further restrictions associated with this feature. Maintenance is required forBrightStor CA-Vantage Storage Resource Manager (SRM) and CAIGMI. Both products requiremaintenance to process an Extended Format TMC. For BrightStor CA-Vantage and CAIGMI Release6.2 PTF QO53276 is required to allow access to the new Extended Format TMC. PTF QO53275 isprovided for r11.1 of BrightStor CA-Vantage and CAIGMI. The appropriate PTF for your release levelmust be applied to all systems in a shared TMC environment where BrightStor CA-Vantage or CAIGMIare run.• CTSSYNC ImprovementsThe CTSSYNC utility is used to synchronize the tape management system with an OAM/SMSmanaged3494/3495 robotic device. Volume eject and scratch functions are also supported. This utilitywas enhanced to allow customers to specify a range of volsers to simplify robotics maintenance. Inaddition, the reporting of actions performed by the utility has been enhanced, and recent maintenancehas been incorporated.• Volume Utilization TrackingThis feature allows BrightStor CA-1 to record how fully utilized a tape cartridge is so that customerscan quickly and easily identify underutilized tape volumes. The increased capacities of new mediatypes make it even more important to obtain full utilization of newer, more expensive cartridges. Thisfeature adds logic to BrightStor CA-1 tape file CLOSE and END OF VOLUME processing to issuemedia-specific tape controller commands to obtain positioning information and the number of byteswritten to the media. This information is then processed to derive a “percent utilized” value that issaved in the TMC and can be displayed online and through Advantage CA-Earl reports.• Pattern Masking Performance ImprovementsThe CTS common pattern masking routines now process simple patterns more efficiently, resulting insignificant run time improvements in the daily batch utilities. Simple patterns are high-level qualifiercomparisons that do not include special masking characters. The Retention and Vault Managementsystems are expected to run significantly faster for customers with very large Retention data sets andVault Pattern data sets.• New ISPF Panels for the Retention and Vault Management SystemsThis feature provides new ISPF panels to define and manage the input control statements for theRetention System and the Vault Management System, making the maintenance of these rules filesmuch simpler. The formats of the Retention data set (RDS) and the Vault Pattern data set (VPD) arenot changed, so no conversion is necessary.• Blocked TMC SupportThe Tape Management Catalog (TMC) may now be blocked, significantly increasing the number ofvolumes and secondary data sets that may be tracked by BrightStor CA-1. Up to ten million combinedvolume and DSNB records may now be defined to the TMC.

• Data Erase UtilityA new Data Erase Utility is provided to allow you to perform a security erase on tape volumes that maybe sent to business partners. The Data Erase Utility permits you to perform security erase processingon residual data that follows one or more active files. Previously any tape that would be sent out ofhouse must be erased prior to writing data on it. This functionality is also important because newmedia types contain servo tracks which prevent the media from being physically degaussed.• ISPF Tape Inquiry (TI) CommandA new Tape Inquiry (TI) command is provided to allow quick lookup of important BrightStor CA-1information for cataloged tape files. The TI command is designed to be issued from the ISPF 3.4“DSLIST” display and will return a summary of important volume and file information in a convenientread-only display that is consistent with the displays of other ISPF commands. The TI commandpermits users to obtain volume information quickly without having to start the BrightStor CA-1 onlinesystem.• New, Modified, Removed OptionsBrightStor CA-1 PTFs introduce five new options, change four options, and remove two obsoleteoptions. Changes were made to the ISPF panels that display or allow updates to the TMOOPTxxmember, as well as to the parsing of the PPOPTION member during TMSINIT processing andreporting.• A new usermod has been added to CAI.PPOPTIONCL05245 can be installed to replace CL05228. This usermod incorporates additional calls to STK,Sutmyn robotic devices, BrightStor CA-Vtape as well as the existing call to the IBM 3494 and3494/VTS devices currently provided by CL05228. Please refer to the Getting Started guide for moredetails.Release 11 Tape Change Highlights:File 1 Contains three SAMPJCL members that can be used to unload files 9, 30 and 31.File 9 Contains several revised SAMPJCL members that will need to be downloaded before applyingmaintenance from this tape.File 15 Contains SMP/E HOLDDATA if any was available at the time the tape was created. The latestHOLDDATA can be obtained from SupportConnect.ca.com. To obtain this information logon toSupportConnect and select “Product News” from the choices at the left on the “Welcome toSupportConnect” page. Choose BrightStor CA-1 Tape Management from the drop down list of products.From the product page, click on the “Mainframe” link under “Detailed Service Pack Information”. The pagepresented will have a link to the latest HOLDDATA.File 30 Contains information about getting the latest product documentation.File 31 Contains members PTFS0404, PTFS0204, PTFS0104, PTFS0004, PTFS9910 and PTFS9901.These members can be used to review the changes made to BrightStor CA-1 since the Release 5.2 base.Installation Considerations:Customers installing BrightStor CA-1 R11 into an existing set of CA common libraries should examine thedata set information provided in the Getting Started guide to determine if library expansion is required

Note: When performing an upgrade of BrightStor CA-1 Release 5.2 to Release 11 by applyingmaintenance, the SMP/E REL files for the base functions will be left on disk. These files arenot used for the maintenance process and may be safely deleted.8. Please note that the CAI.PPOPTION member TMOOPT00 has changed. Four new optionshave been added and two removed. See Product Documentation Change (PDC) QI48357 formore information regarding these changes. If you would like to incorporate these changes,please add or remove them manually. You can use job L052JG from SAMPJCL to downloadthem to a new PPOPTION data set.Previous Maintenance LevelsThis section contains previous maintenance level high APARs and their accompanying ProductMaintenance Letter (PML) numbers.Maint Level High APAR PMLService Pack 4 (0204) QO18332 QI22149Service Pack 3 (0104) LO94801 LI98525Service Pack 2 (0004) LO72832 LI77196Service Pack 1 (9910) LO55742 LI68945Documentation:This tape contains the complete BrightStor CA-1 documentation set in both IBM BookManager and PDFformats. The job L052BKI may be used to download the new BookManager documentation files. Youshould delete any old BookManager files before you run this job.The job L052PDF may be used to receive the PDF documentation files.Additional instructions are provided in the JCL members. SAMPJCL member READDOC containsinformation on how to obtain the latest Adobe and IBM BookManager readers as well as generalinformation about using the documentation set.License Management:BrightStor CA-1 is maintained by the CA License Management Program (LMP). Information about LMP canbe found in the CA Common Services for z/OS and OS/390 Administrator Guide, Chapter 7 "ResourceInitialization Manager". This documentation is available for viewing and downloading atSupportConnect.ca.com.If you still have questions about LMP after referring to this documentation, please call the CA LicenseManagement Program hotline at 1-800-338-6720 in North America. Outside of North America, pleasecontact your local Computer Associates Technical Support organization.

Drop Support Date for Release 5.2:Computer Associates’ policy is to continue supporting a product release for a minimum of one (1) year aftera new release becomes available. We will provide support for BrightStor CA-1 Release 5.2 through July31, 2005. Support for Release 5.2 will be discontinued effective August 1, 2005.We are dedicated to ensuring that your use of BrightStor CA-1 is successful and we wish to thank you foryour continued support of Computer Associates. If you have any questions regarding this softwaresolution, please contact your Computer Associates technical support organization for BrightStor CA-1.

BrightStor CA-1 Product Documentation ChangePDC# QI30073DATE: November 5, 2002RELEASE: 5.2ENVIRONMENT: MVSHYPER: NoSUBJECT: 3495/3494 Tape Library Data Server Synchronization Utility EnhancementsDESCRIPTION/DISCUSSION:The enhancements provided by CTS APAR QO30013 allow CTSSYNC to process commands with VSNranges, provide reformatted reports, add an optional errors-only report, and standardize return codeprocessing. CTSSYNC now uses the CTS standard parsing routines to process input from SYSIN and the'EXEC PARM='. These routines allow commands to be free-form and include comments. A VSN range isspecified by including the low and high VSNs, separated by a dash. For example, ABC005-ABC024 meansthe command would be repeated for all VSNs from ABC005 through ABC024. The new report format printsa single line for each ATL command and provides the results from both the ATL and the tape managementsystem. An optional report of only the errors can be produced. CTSSYNC will now attempt to process allcommands even if errors occur. After all processing is attempted, CTSSYNC will terminate with themaximum return code set by any command. A new parm, ABDLMT=, can be used to ABEND CTSSYNC ata user-specified return code limit.The following documentation should be added to the appropriate sections of the BrightStor CA-1 Utilitiesand Reports Reference Guide.RESOLUTION:1.4 CTSSYNC - 3495/3494 Tape Library Data Server Synchronization UtilityCTSSYNC provides a high level interface to the IBM 3495/3494 LCS (Library Control System) andoptionally lists the results of client requested functions. This utility performs the following functions tosupport the 3495/3494 device:1. Synchronize the tape management catalog system and the 3495/3494 database. The scratch status ofa volume is obtained from the tape management database and that status is set in the 3495/3494 LCSdatabase.2. Eject cartridges needed for off-site storage from the 3495/3494. Tapes are ejected to the BULK orConvenience locations.3. Change the status of cartridges as they are scratched. The status is set in the 3495/3494 LCSdatabase according to the specified command without reference to the tape management database.4. IMPORT/EXPORT virtual tapes from the 3495/3494. Virtual tapes are extracted from or added tophysical "container" tapes, which can be moved into or out of the 3495/3494 robot.PDC# QI30073

This utility accepts input either via a PARM value and/or SYSIN control statements. The PARM value canbe either from a calling program or the EXEC JCL statement. Commands specified without VOLSERs are"global" commands that are used for subsequent VOLSERs that are specified without commands. Globalcommands are replaced by subsequent global commands but not specific commands which includea VOLSER. The default global command is SYNC. Each command is processed when the VOLSER orVOLSER range is specified without regard of any previous or subsequent commands.1.4.1 Job Control Statements//stepname EXEC PGM=CTSSYNC,PARM='parm'//STEPLIB DD DISP=SHR,DSN=CAI.CAILIB//SYSPRINT DD SYSOUT=* *NOTE 1//ERREPORT DD//EXPORT DDSYSOUT=*DSN=EXPORT.TAPE.LIST,*NOTE 2*NOTE 3 *NOTE 6UNIT=VTAPE,TRTCH=NOCOMP,DISP=(,CATLG)//IMPORT DD DSN=IMPORT.TAPE.LIST, *NOTE 4 *NOTE 6UNIT=VTAPE,TRTCH=NOCOMP,DISP=(,CATLG)//SYSIN DD * *NOTE 5(control statements here)/*Note 1: The SYSPRINT DD is optional. If coded, CTSSYNC writes the standard (or full) report to this file.The standard report produces a detail list of the requested commands for each volume and the resultsof those requests. When the command is for a range of volumes a line is listed for each volume. For SYNCcommands the results of the tape management query is also shown.Note 2: The ERREPORT DD is optional. If coded an "errors only" report is produced. This report is in sameformat as the standard report.Note 3: The EXPORT DD is required for use by the EXPORT command. CTSSYNC writes all the filesrequired by the 3494/VTS for an EXPORT operation to the virtual tape defined by this DD statement. If noexport commands are specified, then this DD is NOT used. DO NOT specify 'VOL=(,RETAIN)' on this DDstatement. See Note 6.Note 4: The IMPORT DD is required for use by the IMPORT command. CTSSYNC writes all the filesrequired by the 3494/VTS for an IMPORT operation to the virtual tape defined by this DD statement. If noimport commands are specified, then this DD is NOT used. DO NOT specify 'VOL=(,RETAIN)' on this DDstatement. See Note 6.Note 5: The SYSIN DD is optional. The commands can be entered by using the SYSIN control statements,or by coding them as parameters after the PARM= statement, or by passing a parameter list with the useofregister 1. Commands are free-form but the entire command line must be on a single line between columns1 and 71. Spaces and/or commas are delimiters. Comments must have the form /* comment text */. Theymay appear anywhere within a command or on a line by themselves.Note 6: DO NOT specify 'VOL=(,RETAIN)' on this DD statement. Specifying VOL=(,RETAIN) will cause theIMPORT/EXPORT list volume to remain on the tape drive. The robot does not consider the list volumeavailable if it is mounted, so the IMPORT/EXPORT invoked by CTSSYNC will fail.Note 7: CA-1 must be active or batch active to run CTSSYNC.Note 8: The CTSSYNC utility cannot be used with 3495/3494 BTLS devices.PDC# QI30073

Control Statements:The CTSSYNC utility processes the following commands:VERIFYNOVERIFYBULKNOBULKEJECT{,vvvvvv{-vvvvvv}}PROTECT{,vvvvvv{-vvvvvv}}SCRATCH{,vvvvvv{-vvvvvv}}PRIVATE{,vvvvvv{-vvvvvv}}SYNC{,vvvvvv{-vvvvvv}}EXPORT{,llllll{-llllll}} {,destination}IMPORT{,pppppp} {,llllll{-llllll}} {,ooooooooo}Where vvvvvv - volume serial number (real or virtual)llllll - volume serial number for a logical (virtual) tapepppppp - volume serial number for a physical (container) tapeooooooo - IMPORT option either 'SCRATCH' or 'PRIVATE'VERIFY|NOVERIFYThe VERIFY instructs the system to first verify if the volume serial number is defined in the 3495/3494 LCSdatabase prior to executing any further commands. If NOVERIFY is specified, the LCS commands areissued even if the cartridge does not reside in the 3495/3494 LCS database. VERIFY is the default.BULK|NOBULKThe BULK command instructs any following EJECT commands to be sent to the bulk location. TheNOBULK command instructs all following EJECT commands to be sent to the convenience location. Ifneither BULK nor NOBULK was specified prior to an EJECT command, the utility defaults to the bulklocation.EJECTInstructs the 3495/3494 robotic device to eject the specified VOLSER(s). Depending on whether a BULK orNOBULK command had been issued prior to the EJECT command, the cartridge would be ejected to eitherthe bulk or the convenience location.PROTECT|SCRATCH|PRIVATEThe PROTECT, SCRATCH, and PRIVATE commands all change the status of the specified VOLSER(s).The SCRATCH command changes the status to scratch, while the PROTECT and PRIVATE commandschange the status to private within the 3495/3494 LCS database. This affects which cartridge(s) areselected to satisfy SCRATCH requests and which cartridge(s) are added to any auto cartridge loaders(ACLs) located inside the 3495/3494 robotic device. There is no difference between PROTECT andPRIVATE.SYNCCauses the specified VOLSER(s) to be synchronized between the tape management database and the3495/3494 LCS database. If the status is different, the tape management database is assumed to becorrect. This is the default if no specific command is specified.EXPORTCauses the specified LOGICAL VOLSER(s) to be written to the export list volume (a logical volumeresiding in the same library as the volumes to be exported).PDC# QI30073

After all volumes have been written to the export list volume, the OAM LCS schedules the list to beexported.DESTINATION - This sub-parameter can only be included on the EXPORT control statement and isoptional. If included, all virtual volumes with the same "destination" will be stacked together on a singlephysical volume. If a list of 50 virtual volumes to be exported had been supplied; and 25 had one"destination" and the other 25 had a different "destination", then the first 25 would be stacked together onone set of physical volume(s) and the other 25 would be stacked on a different set of physical volume(s).However, this value is NOT sent to the CBRUXEJC exit during eject processing nor is it tracked in theTCDB or the tape management catalog.IMPORTCauses the specified LOGICAL VOLSER(s) to be written to the import list volume (a logical volumeresiding in the same library as the volumes to be imported).After all volumes have been written to the import list volume, the OAM LCS schedules the list to beimported.Note 9: Only 1 EXPORT or IMPORT can be scheduled at a time. Subsequent EXPORTs or IMPORTs willbe shown as errors by CTSSYNC.SCRATCH|PRIVATE - One of these two optional sub-parameters can be included on the IMPORT controlstatement IF the specific virtual volume(s) had been specified. PRIVATE (the default) indicates that thespecified virtual volume should be copied back into cache inside the 3494/VTS completely (the entirevirtual volume is copied). If SCRATCH is specified, then the specified virtual volume is assumed to be inscratch status and only the VOL1/HDR1/HDR2 records are copied back into cache. While this will reducethe time to complete the IMPORT process, those virtual volumes cannot be made "un-scratched" becausethe data on them no longer will reside inside the 3494/VTS.ABDLMT=Is a keyword parameter used to set a return code limit at which CTSSYNC will ABEND. After CTSSYNChas completed all other processing and is about to terminate, the numeric value of ABDLMT is comparedwith the highest return code from any command. If that return code is greater than or equal to theABDLMT, CTSSYNC with abend with a U0006 and a reason code equal the return code. The default isABDLMT=99.It can be in either the ABDLMT=nn or the ABDLMT(nn) form. It can be specified in the EXEC parm field orin a SYSIN statement. It can be specified on a statement alone or with any command. It may be specifiedmultiple times, but only the last value is used.Examples of Specifying Commands to CTSSYNCThere are three methods of getting the commands or VOLSERs to the CTSSYNC utility: PARM= on theEXEC statement, through SYSIN control statements, or passed in a parameter list through register 1. Theeasiest way to perform a single command is through use of the PARM statement on the EXEC command.//STEP1 EXEC PGM=CTSSYNC,PARM='EJECT,123456'This causes cartridge 123456 to be ejected from the 3495/3494 robotic device. Likewise, the same valuecould have been used as input from the SYSIN control statements.PDC# QI30073

SYSIN DD *EJECT,123456The command can also be passed in a parameter list pointed to by register 1. This would be used ifanother program (such as the security exit) wanted to call the synchronization program passing it thecommand. The format of the parameter list pointed to by register 1 is as follows:R1 ==> A(addr1) ==> CL8'EJECT'A(addr2) ==> CL8'123456'It is possible to use the SYSIN control statement in addition to either of the two parameter methods. Forexample;//STEP1 EXEC PGM=CTSSYNC,PARM='BULK'//SYSIN DD *EJECT,123456EJECT,100001EJECT,001234In this example, the BULK command applies to all subsequent commands. Therefore, the EJECT of tapes123456, 100001, and 001234 would be directed to the bulk location. If a volume command is issuedwithouta VOLSER, all subsequent VOLSERs would then be processed.//STEP1 EXEC PGM=CTSSYNC//SYSIN DD *SYNC100002102030100202In this example, the three listed volumes (100002, 102030, and 100202) would have their statusessynchronized between the tape management system and the 3495/3494 LCS database. This could just aseasily be a list of tapes to be ejected to the BULK location (as a postprocess to the vaulting system forexample).//STEP1 EXEC PGM=CTSSYNC//EXPORT DD DSN=EXPORT.TAPE.LIST,// UNIT=VTAPE,TRTCH=NOCOMP,DISP=(,CATLG)//SYSIN DD *EXPORT,LV1234,OFFSITE1 /* comments */EXPORT,LV2345,OFFSITE1In this example, the logical volumes LV1234 and LV2345 are to be removed. An export list volume iscreated and the 3495/3494 LCS schedules the list to be exported. When the export function is completed,logical volumes LV1234 and LV2345 are stacked on to a physical volume and the physical volume is put inexport hold status, waiting to be removed from the 3495/3494.//STEP1 EXEC PGM=CTSSYNC//IMPORT DD DSN=IMPORT.TAPE.LIST,// UNIT=VTAPE,TRTCH=NOCOMP,DISP=(,CATLG)//SYSIN DD *IMPORT,PV0001,LV1234IMPORT,PV0001,LV2345-LV2348 /* range of logical volumes */PDC# QI30073

In this example, logical volumes LV1234 and LV2345 thru LV2348 are imported from physical volumePV0001. An import list volume is created and the 3495/3494 LCS schedules the list to be imported.//STEP1 EXEC PGM=CTSSYNC//IMPORT DD DSN=IMPORT.TAPE.LIST,// UNIT=VTAPE,TRTCH=NOCOMP,DISP=(,CATLG)//SYSIN DD *IMPORT,PV0001In this example, all logical volumes on physical volume PV0001 will be imported. An import list volume iscreated and the 3495/3494 LCS schedules the list to be imported.Note 10: The CTE3495 member in CAISRC can be used to help generate a list of VOLSERs as input toCTSSYNC.//STEP1 EXEC PGM=CTSSYNC,PARM='SCRATCH,ABDLMT=12'//IMPORT DD DSN=IMPORT.TAPE.LIST,// UNIT=VTAPE,TRTCH=NOCOMP,DISP=(,CATLG)//SYSIN DD *012345 /* SINGLE TAPE WITH COMMENT */ABC017-ABC052 /* SCRATCH ALL TAPES IN THIS RANGE */SYNC XYZ100-XYZ299In this example, the EXEC PARM is used to set 'SCRATCH' as a global command and to ABENDCTSSYNC if the highest return code is greater than or equal to 12. The volser 012345 and the range ofvolsers ABC017 thru ABC052 will be scratched via the global command. The range of volsers XYZ100 thruXYZ299 will be synchronized with the tape management system.Completion CodesCTSSYNC can complete with the following condition codes.RC=0RC=4The requested commands were performed successfully.One or more ATL commands failed or could not be performed.RC=8 One or more ATL commands failed or could not be performed because of environmentalconditions (i.e. tape management or the ATL not active)RC=12 One or more commands failed because of JOB setup. (i.e. missing DD statements)A U0006 abend will be issued when CTSSYNC is finished processing all control statements AND is goingto terminate with a condition code greater than the value specified in the abend limit parm (ABDLMT=).Example: ABDLMT=8 will cause CTSSYNC to abend with a U0006-rc when the highest RC is greater thanor equal to 8.When the 3495/3494 LCS is unable to schedule an EXPORT or IMPORT, CTSSYNCwill abend with the following user abend codes:- U0100-00rs EXPORT could not be scheduled.- U0200-00rs IMPORT could not be scheduled.PDC# QI30073

s is the reason code from the 3495/3494 LCS services; it indicates why the EXPORT/IMPORT could notbe scheduled. The reason codes can be found in the LCS External Services Parameter List (LCSPL),mapped by IBM macro CBRLCSPL, which is used to pass parameters to the LCS external services, and topass return and reason codes and other information back to the caller. This macro may be found inSYS1.MACLIB. U0999 with a dump may be issued if internal logic errors occur.1.4.2 CTSSYNC ATL RESPONSE LOG Report SampleFUNCTION ATL ACTION STATUS IN TAPE DATABASE .........' ' '' ' '' ' '' ' '' ' '' ' '' ' '' ' 'CTSSYNC report headings and their definitions:FUNCTION - The function or command or parameter that was passed to CTSSYNC. A "SYNC" commandis broken down first into a "QUERY" type transaction (to find out if the cartridge is in the robot or not andwhat its status is if it is inside the robot) and then either a PROTECT command (to change its status fromscratch to private), a SCRATCH command (to change its status from private to scratch) or a SYNCcommand (meaning that it was already in the correct status).ATL ACTION - A description of what the ATL has been asked to do and what its response was.STATUS IN TAPE DATABASE - A description of the status of the cartridge in the tape managementdatabase. This is used only for a SYNC command.ATL ACTION messages and their meanings:VERIFY MODE INITIATED - The VERIFY command had been issued and processed.VERIFY MODE TERMINATED - The NOVERIFY command had been issued and processed.CONVENIENCE DOOR ACTIVE - The NOBULK command was issued and the convenience door will beused for any further EJECT commands.BULK-EJECT DOOR ACTIVE - The BULK command was issued and the bulk door will be used for anyfurther EJECT commands.NO DD STATEMENT FOR IMPORT - An IMPORT command was issued, but the JCL did not contain anIMPORT DD statement.NO DD STATEMENT FOR EXPORT - An EXPORT command was issued, but the JCL did not contain anEXPORT DD statement.WRITTEN TO EXPORT LIST VSN vvvvvv - An EXPORT command was issued and the volume to beexported was written to the export list created on virtual-volume vvvvvv.WRITTEN TO IMPORT LIST VSN vvvvvv - An IMPORT command was issued and the volume to beimported was written to the import list created on virtual-volume vvvvvv.PDC# QI30073

QUERY COMPLETE, VOLUME IN ROBOT - A SYNC command was issued and the volume to besynchronized did reside inside the robot.VOLUME WAS ALREADY IN THAT STATUS - A SYNC command has been issued, and the volume wasalready in the correct status.REQUESTED PROCESS COMPLETE - Either a PROTECT, SCRATCH, PRIVATE command had beenissued and the volume had its status successfully changed. The PROTECT or SCRATCH command mayalso have been issued because of a SYNC command when the initial QUERY found the tape was not inthe correct status.EXPORT FAILED, REASON CODE=nnn - The EXPORT command failed. The reason codes can be foundin the LCS External Services Parameter List (LCSPL), mapped by IBM macro CBRLCSPL. This macro canbe found in SYS1.MACLIB.IMPORT FAILED, REASON CODE=nnn - The IMPORT command failed. The reason codes can be foundin the LCS External Services Parameter List (LCSPL), mapped by IBM macro CBRLCSPL. This macro canbe found in SYS1.MACLIB.REQUEST FAILED RC=rc,RS=rsn,FB=nnnnnn - The request (SCRATCH, PRIVATE, PROTECT, SYNC)failed with a return code of rc; and reason code of rsn. The return code and reason code combinations canbe found in the LCS External Services Parameter List (LCSPL), mapped by IBM macro CBRLCSPL. Thismacro can be found in SYS1.MACLIB.SYNTAX ERROR DURING PARSE - There was a syntax error on the specified control statement.PARSING ERROR IN THE VSN RANGE - A range of volumes had been specified, but there was a syntaxerror in the format.BYPASSED MIXING IMPORT AND EXPORT - It is not allowed to perform both an IMPORT and anEXPORT on the same execution.NO COMMAND(S) FOUND - No command was found on the PARM or in the SYSIN.INVALID REQUEST FOR THIS ATL - A command was rejected as un-supported by the ATL software.ATL INACTIVE OR NOT AVAILABLE - The 3494/ATL was either not active or not available tocommunicate with CTSSYNC.ATL SYNCRONIZE BYPASSED - The SYNC command was bypassed for the specified reason.VOLUME NOT FOUND BY ATL - The volume specified on the command is not defined in the ATL TCDB.STATUS IN TAPE DATABASE messages and their meanings:TAPE FULL OR EDM CONTROLLED - The requested volume was either full (it is part of a multi-volumechain) or is controlled by an external data manager. In either case, it cannot be mod'ed onto.VOLUME NOT IN SCRATCH STATUS - The requested volume is active (not in scratch status), but couldhave additional data mod'ed onto it or have additional files stacked upon it.VOLUME IN LIBRARY AND SCRATCH - The requested volume is in scratch statusPDC# QI30073

VOLUME NOT DEFINED TO THE DATABASE - The volume is not defined to the tape managementsystem.TAPE MANAGEMENT IS NOT ACTIVE - The tape management system is not currently active.TAPE CREATED WITHIN THE LAST 5 MINUTES - A SYNC command was issued for a volume that wascreated within the last 5-minutes, this volume was bypassed.BAD TAPE OR OUT-OF-SERVICE - A SYNC command was issued for a tape that is either marked asBAD or as OUT-OF-SERVICE in the tape management database.Thank you for your continued support of Computer Associates and its products. If you have any questionsabout this Product Documentation Change or any other questions about CA-1, please contact your localComputer Associates Technical Support organization for CA-1.PDC# QI30073

BrightStor CA-1 Product Documentation ChangePDC# QI30130DATE: November 6, 2002RELEASE: 5.2ENVIRONMENT: MVSHYPER: NoSUBJECT: New TMC fields, reporting on tape usage statistics, enhancement of the Realtime CatalogInterface and support of 3590-H devicesDESCRIPTION/DISCUSSION:This Product Documentation Change provides information regarding the enhancements and product errorresolutions provided by CA-1 APARs QO30031, QO30032 and QO30033.RESOLUTION:All three APARs should be installed to enable the new features, but no problem arises when they are notapplied at the same time, or when a TMC is shared among multiple systems with different maintenancelevels.The APARs include the following enhancements and error resolutions:• Introduction of new TMC fields• Tracking of physical tape usage and IDRC compression rate• Tracking of multiple catalog and uncatalog operations of tape files• Support of 3590-H (384 track) devices• Incorporation of confirmed test fixesIntroduction of new TMC fieldsThe following new TMC fields have been defined by reusing previously reserved fields. They are all binarynumeric fields, one byte in length.Volume record fields:Keyword TMC volume record Common Tape record EARL / EZTRIEVELabel Offset Label Offset Label----------------------------------------------------------------------------------------------------------------------------------VOLPERC TMVOLP 236 (EC) DBVPERC 183 (B7) VOL_PERCENTAGEFILPERC TMFILEP 237 (ED) DBFPERC 184 (B8) FILE_PERCENTAGECOMPRES TMCMPRS 238 (EE) DBCOMPRS 185 (B9) COMPRESSIONCTLGCNT TMCATCNT 232 (E8) DBCATCNT 439(1B7) CATALOG_COUNTPDC# QI30130

DSNB fields:Keyword TMC DSNB record Common Tape record EARL / EZTRIEVELabel Offset Label Offset Label------------------------------------------------------------------------FILPERC DSNBPERC 133 (85) DBFPERC 184 (B8) FILE_PERCENTAGECOMPRES DSNBCPRS 134 (86) DBCOMPRS 185 (B9) COMPRESSIONCTLGCNT DSNBCCNT 135 (87) DBCATCNT 439(1B7) CATALOG_COUNTTracking of physical tape usage and IDRC compression rateDuring CLOSE OUTPUT processing, CA-1 now tracks tape usage information for all cartridge device typesand stores the following values in the respective TMC record:VOLPERCindicates what percentage of the physical space on the tape volume is currently used.FILPERCindicates what percentage of the physical space is used by the specific data set. The volume record fieldrelates to the first file on the tape, the DSNB field relates to the first volume of the respective secondaryfile.COMPRESindicates what percentage of the space occupied by the file has been saved by IDRC compression. Thevolume record field relates to the first file on the tape, the DSNB field relates to the first volume of therespective secondary file.Sample: COMPRES = 0 indicates that the file is not compressed. COMPRES = 30 indicates that thecompressed file uses 70% of the space that would have been required without compression.These values can be used to report on the actual usage of tape space more accurately than by onlycalculating the logical data length from block size and block count. When the Realtime Tape Stackingfeature is used, threshold calculations are improved for 3590 devices.The following example shows how the file percentage fields are filled in a multifile/multivolume aggregate:Volume A holds files 1 and 2, volume B holds files 2 and 3.The FILPERC of volume A shows the percentage of volume A used by file 1.The FILPERC of the first DSNB, associated with file 2, shows the percentage of volume A used by file 2.Volume A is the F1STVSN of file 2. The FILPERC of volume B shows the percentage of volume B used byfile 2. The spanned file 2 is the first file on volume B.The FILPERC of the second DSNB, associated with file 3, shows the percentage of volume B used by file3.The file percentage is tracked individually for each part of a specific file residing on a specific volume. Thesame is true for the compression ratio. This logic is different from the way block counts are tracked. Whena secondary file spans over multiple volumes, its block count is accumulated in the DSNB field, while theblock count field of the secondary volume records remains zero.PDC# QI30130

Note that a meaningful compression ratio cannot be obtained for files of less than about 40 K of data. Forfiles which use less than 0.4 % of the tape space, the displayed percentage may be zero. Also, becauseof rounding, the sum of the FILPERC values for all files on a volume will quite often be much higher thanthe VOLPERC field itself. For example, if there are 200 small files on the volume, they may each have aFILPERC value of 1 (meaning each file takes up between 0-1.5% of the volume), while the VOLPERC maybe much less then 100 (meaning a 100% full volume).NOTE: For virtual volumes, useful percentage values can normally not be obtained.Tracking of multiple catalog and uncatalog operations of tape filesField CTLGCNT was introduced to track the number of times a data set is (un)cataloged. Previously, theOSC flag bit of the TMC record was turned on whenever the respective data set was cataloged, and turnedoff when it was uncataloged. This could cause the OSC bit to be cleared prematurely when a tape file wasdefined to multiple catalogs and not all catalog entries were deleted at the same time. The same couldhappen with IDCAMS REPRO MERGECAT. When catalogs are merged, data sets are first defined to thenew catalog and then deleted from the old one. As a result, the OSC bit was turned off in the TMC becausethe last operation had been an uncatalog.Now with the catalog count field available, multiple catalog operations for the same file cause the catalogcount to be increased accordingly and decreased as uncatalogs occur. Only when the number ofuncatalogsequals the number of catalogs will the count be zeroed and the OSC flag bit turned off. For a MERGECAToperation, this means that the CTLGCNT value of all files being recataloged will temporarily be increasedto 2 and then reset to 1. The OSC bit is never turned off during the catalog merge. It is therefore no longernecessary to resynchronize TMC and OS catalog using TMSOSCAT after a catalog merge.This change can prevent tape data sets under catalog control from being expired prematurely in thedescribed situations when option OCTLG=NO is used. This works safely even if the original, first catalogentry was established before the maintenance was applied.A performance improvement was also included. Previously, the Realtime Catalog Interface could causeperformance degradation in particular when very long multifile chains (hundreds or thousands of files ononetape) were (un)cataloged. The new logic prevents the catalog intercept from running the multifile chainunnecessarily and can significantly reduce the number of TMC I/Os.The above processing changes of the Realtime Catalog Interface were actually included in Service Pack 4(APARs QO03405 and QO09357). However, the new catalog count field is displayed and made availablefor inquiry and update only when these new APARs have been installed.Support of 3590-H (384 track) devicesNew TRTCH values were defined to represent 384 track tapes:x'EC' - 384T - 3590 384 tracks standard length cartridgex'ED' - 384X - 3590 384 tracks extended length cartridgeSupport of the new 3590 model was added to all product components. A new version of OAM userexitCBRUXENT is provided for customization.PDC# QI30130

Incorporation of confirmed test fixesThe APARs include and supersede all previously published maintenance to the affected modules, as wellas the following confirmed test fixes:T5XD937 - Prevent DSNB allocation during open if volume is not last in chainT246001 - Prevent TMDFAULT flag bit from being set in error during openTFFC097 - Correct 'keytape' checkin logicTFFC101 - Prevent unnecessary IECTMS2 WTOR before NS(08) rejectTF45109 - Allow volumes to be 'released' during checkpoint/restartTF45116 - Correct problem with TF45109T5XD226 - Correct expiration date on new volumes created after a checkpoint/restart with TF45109 andTF45116 appliedT5XD237 - Post block count for temporary data setsT5XD989 - Prevent TMNOSTAK flag bit from being set in error during closeTFFC136 - Prevent DSNBABND bit from being set during close/inputT137010 - TMSTPNIT: Prevent CAL0TN01 when 3490 re-initialized on 3480 deviceT5XD257 - TMSUDSNB: Prevent S0C4 at +806 with multiple subsequent DSNB cardsT5XD267 - TMSUDSNB: Prevent truncation of field values with PARM=AUDITDocumentation updates related to these APARs:Updates to the CA-1 Systems Programmer Guide:Appendix A.1 TMC Volume Record Definition with Keywords (TMMTMREC)At the end of the TRTCH definition, add the following values:--------------------------------------------------------------------------------------------------------------------------------------------TM384TRK EC HEX X'EC' 3590 CARTRIDGE - 384 TRACKS--------------------------------------------------------------------------------------------------------------------------------------------TM384T2 ED HEX X'ED' 3590 CARTRIDGE - 384 TRACKS(EXTENDED LENGTH)--------------------------------------------------------------------------------------------------------------------------------------------Replace line--------------------------------------------------------------------------------------------------------------------------------------------B1INT TMB1INT 232(E8) BIN 3 B1 SECURITYINTEGRITY LABEL--------------------------------------------------------------------------------------------------------------------------------------------with the following:--------------------------------------------------------------------------------------------------------------------------------------------CTLGCNT TMCATCNT 232(E8) BIN 1 CATALOG COUNT SMF--------------------------------------------------------------------------------------------------------------------------------------------233(E9) 2 RESERVED--------------------------------------------------------------------------------------------------------------------------------------------PDC# QI30130

Replace line--------------------------------------------------------------------------------------------------------------------------------------------B1DIS TMB1DIS 237(EC) BIN 3 B1 SECURITY DIS-CLOSURE LABEL--------------------------------------------------------------------------------------------------------------------------------------------with the following:--------------------------------------------------------------------------------------------------------------------------------------------VOLPERC TMVOLP 236(EC) BIN 1 TOTAL TAPE PER- unitCENTAGE IN USE--------------------------------------------------------------------------------------------------------------------------------------------FILPERC TMFILEP 237(ED) BIN 1 TAPE PERCENTAGE unitUSED BY FILE--------------------------------------------------------------------------------------------------------------------------------------------COMPRES TMCMPRS 238(EE) BIN 1 COMPRESSION RATIO unit--------------------------------------------------------------------------------------------------------------------------------------------Appendix A.2 TMC DSNB Record Definition with Keywords (TMMDSNB)Replace line--------------------------------------------------------------------------------------------------------------------------------------------DSNBUNOS 133(85) 13 RESERVED--------------------------------------------------------------------------------------------------------------------------------------------with the following:--------------------------------------------------------------------------------------------------------------------------------------------FILPERC DSNBPERC 133(85) BIN 1 TAPE PERCENTAGE unitUSED BY FILE--------------------------------------------------------------------------------------------------------------------------------------------COMPRES DSNBCPRS 134(86) BIN 1 COMPRESSION RATIO unit--------------------------------------------------------------------------------------------------------------------------------------------CTLGCNT DSNBCCNT 135(87) BIN 1 CATALOG COUNT SMF--------------------------------------------------------------------------------------------------------------------------------------------DSNBUNUS 136(88) 10 RESERVED--------------------------------------------------------------------------------------------------------------------------------------------Updates to the CA-1 Utilities and Reports Reference Guide:2.3.1 EARLDEFS Tape Record Field DefinitionsReplace line--------------------------------------------------------------------------------------------------------------------------------------------DEF COMMON_RSRVA 181-186 X--------------------------------------------------------------------------------------------------------------------------------------------PDC# QI30130

with the following:--------------------------------------------------------------------------------------------------------------------------------------------DEF STACKING_INUSE 181-181 X 'STK' 'USE' TMFLAG4 TMINUSE Y/N--------------------------------------------------------------------------------------------------------------------------------------------DEF STACKING_FULL 182-182 X 'STK' 'FUL' TMFLAG4 TMNOSTAK Y/N--------------------------------------------------------------------------------------------------------------------------------------------DEF STACKING_VOLUME 183-183 X 'STK' 'VOL' TMFLAG5 TMSTACK Y/N--------------------------------------------------------------------------------------------------------------------------------------------DEF VOL_PERCENTAGE 184-184 B 'VOL' 'USE' TMVOLP--------------------------------------------------------------------------------------------------------------------------------------------DEF FILE_PERCENTAGE 185-185 B 'FIL' 'USE' TMFILEP or DSNBPERC--------------------------------------------------------------------------------------------------------------------------------------------DEF COMPRESSION 186-186 B 'COMP' 'RATE' TMCMPRS or DSNBCPRS--------------------------------------------------------------------------------------------------------------------------------------------Replace line--------------------------------------------------------------------------------------------------------------------------------------------DEF UNUSED2 438-440 X--------------------------------------------------------------------------------------------------------------------------------------------with the following:--------------------------------------------------------------------------------------------------------------------------------------------DEF UNUSED2 438-439 X--------------------------------------------------------------------------------------------------------------------------------------------DEF CATALOG_COUNT 440-440 B 'CAT' 'CNT' TMCATCNT or DSNBCCNT--------------------------------------------------------------------------------------------------------------------------------------------Updates to the CA-1 Release Guide:1.8.1 Database Changes - TMMTMRECReplace definitions--------------------------------------------------------------------------------------------------------------------------------------------TMB1INT Bin 3 B1INT B1 security integritylabel (this field hasbeen shortened from 4bytes to 3)--------------------------------------------------------------------------------------------------------------------------------------------TMB1DIS Bin 3 B1DIS B1 security disclosurelabel (this field hasbeen shortened from 4bytes to 3)--------------------------------------------------------------------------------------------------------------------------------------------PDC# QI30130

with the following:--------------------------------------------------------------------------------------------------------------------------------------------TMVOLP Bin 1 VOLPERC Volume percentage usedby data--------------------------------------------------------------------------------------------------------------------------------------------TMFILEP Bin 1 FILPERC Volume percentage usedby first file--------------------------------------------------------------------------------------------------------------------------------------------TMCMPRS Bin 1 COMPRES IDRC compression ratio--------------------------------------------------------------------------------------------------------------------------------------------TMCATCNT Bin 1 CTLGCNT Catalog count--------------------------------------------------------------------------------------------------------------------------------------------1.8.2 Database Changes - TMMDSNBAdd the following to the table:--------------------------------------------------------------------------------------------------------------------------------------------DSNBPERC Bin 1 FILPERC Volume percentage usedby secondary file--------------------------------------------------------------------------------------------------------------------------------------------DSNBCPRS Bin 1 COMPRES IDRC compression ratio--------------------------------------------------------------------------------------------------------------------------------------------DSNBCCNT Bin 1 CTLGCNT Catalog count--------------------------------------------------------------------------------------------------------------------------------------------Changes to the CA-1 Message Guide:3.1.3 3xx-rc Invalid Multivolume or DSNB Pointers and Specification ErrorsAdd the following at the end of the section:--------------------------------------------------------------------------------------------------------------------------------------------40 An attempt has been made to Correct the JCL of the tapecreate a secondary data set on job to refer to the last volumea volume which is part of aof the chain for creation ofmultivolume chain, but is notfurther data sets.the last volume of the chain.--------------------------------------------------------------------------------------------------------------------------------------------Thank you for your continued support of Computer Associates and its products. If you have any questionsabout this Product Documentation Change or any other questions about CA-1, please contact your localComputer Associates Technical Support organization for CA-1.PDC# QI30130

BrightStor CA-1 Product Documentation ChangePDC# QI32727DATE: January 16, 2003RELEASE: 5.2ENVIRONMENT: MVSHYPER: NoSUBJECT: Performance Enhancements for Retention and Vaulting SystemsDESCRIPTION/DISCUSSION:This enhancement improves the performance of the TMSEXPDT Retention system daily utility and theTMSVMEDT Vault system daily utility through improvements to the pattern masking logic used by theseutilities.Clients with very large Retention Data Sets (RDS) and Vault Pattern Data Sets (VPD) should experiencesignificant performance improvements when CA-1 APAR QO32675 and CTS (Common Tape System)APAR QO32671 are applied. In addition, TMSEXPDT was changed to support a new style of comments onits RDS statements, and a new parameter, LISTRDS, was added. The LISTRDS parameter causesEXPDT to print all the RDS rules instead of just those with errors.Following are documentation changes and additions associated with these enhancements.RESOLUTION:1.28.4.2 Comment StatementCA-1 5.2 Utilities and ReportsYou may include comment statements by placing an asterisk (*) inposition 1. Text for a comment may appear anywhere between positions 2and 71 inclusive. As of CA-1 Release 5.2 Service Pack 4, comments mayalso appear anywhere in the statement when enclosed in '/*.....*/'.Both old and new style comments may appear after the RDS controlparameters. At least one blank must separate the parameters fromthe comments.example 1: DSN=W-,LABEL=EXPDT='CATALOG' OLD STYLE COMMENTSexample 2: DSN=W-,LABEL=EXPDT='CATALOG' /* NEW STYLE COMMENTS */example 3: * ENTIRE STATEMENT WITH OLD STYLE COMMENTSexample 4: /* ENTIRE STATEMENT WITH NEW STYLE COMMENTS */PDC# QI32727

1.28.3.1 Job Control Statements//stepname EXEC PGM=TMSEXPDT// (,PARM='(DATEFMT=(fmt))(,DSNBS)(,TEST)(,NODFLT)// (,DEBUG)(,TESTRDS)(,LISTRDS)')//STEPLIB DD DSN=CAI.CAILIB,DISP=SHR//TMSRPT DD SYSOUT=A//SYSPRINT DD SYSOUT=A//EARLOUT DD DSN=save.tmsexpdt.earlout,// DISP=(NEW,PASS,DELETE),// UNIT=SYSDA,// VOL=SER=VOLSER,// SPACE=(CYL,5),// DCB=(RECFM=FB,LRECL=376,BLKSIZE=15416)//SYSIN DD *(RDS control statements here)/*Parameter DefinitionsDATEFMT=(fmt) Specifies the date format to be printed on TMS Report 82. The date pattern indicated by(fmt) is limited to 10 bytes and must be enclosed in parentheses. This parameter is optional. For moreinformation on valid date formats, refer to Overriding the Preferred Date Pattern in topic 1.1.1.Note: If a date pattern is defined and then subsequently revised, it may be necessary to reflect the patternchange in the optional preferred date value for EXPDT. Read the caution text on 1.28.4.1 and then revisethe preferred date pattern, as necessary.DSNBS Indicates that DSNBs (secondary data sets) that are eligible for RDS override are to beprocessed. This option causes the volume expiration date to be reset to the new DSNB expiration date ifthe new RDS date is numerically higher than the volume expiration date. This parameter is optional.TEST Process normally, but do not update any TMC records. The EARLOUT data set contains recordsused for the Batch Expiration Update Listing, but the TMC is not updated. This parameter is optional.NODFLT Indicates that the EARLOUT data set will list records with an RDS match only. This parameter isoptional.DEBUG This parameter can be used to examine the internal entries created from the Retention Data Set(RDS). This parameter is optional.LISTRDS This parameter will cause all the RDS rules to be printed, not just those with error.TESTRDS Check the syntax of RDS rules only. The TMC is not examined. No records are written to theEARLOUT ddname. May only be specified with DEBUG or DATEFMT parameter.JCL ConsiderationsSYSIN Defines the Retention Data Set (RDS). It must be composed of fixed-length, 80-byte records. Itmay be included in the job stream in statement form, stored as a sequential data set, or exist as a memberof a partitioned data set. SYSIN DD DUMMY will generate an EARLOUT data set of all data sets whichhave the eligible for RDS override bit on in FLAG1.PDC# QI32727

CA-1 5.2 Message Guide2.24 TMSEXPDT MessagesDelete the following error messages:*** DATE IS EXPIRED*** DUPLICATE RETENTION FOUND - xxxxxxxx*** DUPLICATE xxxxxxxx FOUND yyyyyyyy*** INVALID KEYWORD, NEAR COLUMN xx*** INVALID VALUE xxxxxxxx yyyyyyyy*** MISSING LAST DELIMITER*** MISSING xxxxxxxx QUALIFIER*** OUT OF MEMORY FOR RDS ENTRY*** RETENTION xxxx EXCEEDS 9999*** TESTRDS INVALID WITH xxxxxxxx PARM*** VALUE SPECIFIED FOR xxxxxxxx EXCEEDS MAXAdd the following error messages:*** DUPLICATE RETENTION FOUNDExplanation : This retention statement is a duplicate of a previous statement.User Reponse: Correct the retention statement(s) and resubmit the job.*** BAD VALUE FOR ABEND=EXPDT=Explanation : An invalid value was specified for this keyword.User Reponse: Correct the retention statement(s) and resubmit the job.*** BAD VALUE FOR ABEND=RETPD= OR ABEND=WRETPD=Explanation : An invalid value was specified for this keyword.User Reponse: Correct the retention statement(s) and resubmit the job.*** PATTERN MASKING ERROR:Explanation : DSN= or JOB= does not contain a valid pattern mask.User Reponse: Correct the retention statement(s) and resubmit the job.*** BAD VALUE FOR LABEL=EXPDT=Explanation : An invalid value was specified for this keyword.User Reponse: Correct the retention statement(s) and resubmit the job.*** BAD VALUE FOR LABEL=RETPD= OR LABEL=WRETPD=Explanation : An invalid value was specified for this keyword.User Reponse: Correct the retention statement(s) and resubmit the job.*** ABEND DATE IS EXPIREDExplanation : An expiration date value specified is in the past.User Reponse: Correct the retention statement(s) and resubmit the job.*** LABEL DATE IS EXPIREDExplanation : An expiration date value specified is in the past.User Reponse: Correct the retention statement(s) and resubmit the job.PDC# QI32727

*** TESTRDS NOT VALID WITH DSNBS, TEST AND NODEFLTExplanation : TESTRDS parmameter is not valid with these parms.User Reponse: Correct the JCL and resubmit the job.*** SELECT AND JOB ARE MUTUALLY EXCLUSIVEExplanation : The SELECT and JOB keywords can not be specified in the same retention statement.User Reponse: Correct the retention statement(s) and resubmit the job.*** PARSE ERRORExplanation : This statement has invalid syntax or missing/extra keywords.User Reponse: Correct the retention statement(s) and resubmit the job.*** PARSE ERROR IN ABEND KEYWORDExplanation : This statement has invalid syntax or missing/extra keywords.User Reponse: Correct the retention statement(s) and resubmit the job.*** PARSE ERROR IN LABEL KEYWORDExplanation : This statement has invalid syntax or missing/extra keywords.User Reponse: Correct the retention statement(s) and resubmit the job.*** MGMTCLAS=, M= DSN=, AND D= ARE MUTUALLY EXCLUSIVEExplanation : This statement contains keywords or forms of keywords which cannot be specifiedtogetheron an RDS statement.User Reponse: Correct the retention statement(s) and resubmit the job.*** JOBNAME=, JOB= and J= ARE MUTUALLY EXCLUSIVEExplanation : This statement contains multiple forms of the same keyword.User Reponse: Correct the retention statement(s) and resubmit the job.*** PROGRAM ABORTED FOR FATAL PARSE ERRORExplanation : The program encountered error(s) while parsing a RDS statement that were so severe thatthe program could not identify the error or continue processing.User Reponse: Correct the retention statement(s) and resubmit the job.PDC# QI32727

BrightStor CA-1 Product Documentation ChangePDC# QI35237DATE: March 5, 2003RELEASE: 5.2ENVIRONMENT: MVSHYPER: NoSUBJECT: Enhancement of Pointer Verification Utility TMSPTRSDESCRIPTION/DISCUSSION:This Product Documentation Change (PDC) describes the changes to TMSPTRS introduced by BrightStorCA-1 APAR QO35140:• Support of a blocked SYSUT3 data set• Elimination of all device dependent code• Support of SYSUT3 synchronization from the Audit data set (without• PARM=ENQ specified) with unlike device types• Handling of Sort errors• Modification of the ERR85 message text• Elimination of unneeded report trailerThese enhancements have been published as APAR QO35140 and will also be included in Service Pack 5of Brightstor CA-1 Release 5.2.TMSPTRS uses a work data set specified as SYSUT3 DD. It holds a copy of the TMC catalog and is usedfor the actual validation of multivolume and multi-data set chains. This SYSUT3 data set can now beblocked to save disk space. The BLKSIZE may be any multiple of the LRECL, 340, and does not dependon the block size of the active TMC.Performance can also be improved by allocating the SYSUT3 data set in VIO storage. Any DASD or VIOdevice may be used without limitation.It is now possible to allocate SYSUT3 on a device which differs from the device type of the TMC, evenwithout specifying PARM=ENQ. This allows TMSPTRS to copy the TMC and to synchronize the copy fromthe Audit data set without issuing a RESERVE against the TMC. A U0999-04 abend is no longer issued ifunlike device types are found.If the internal sort of the DSNB records is not successful, TMSPTRS now displays the sort return code andterminates with CC=16:"RETURN CODE xxx FROM SORT - PROCESSING TERMINATED".The message text of ERR85, "VOLUME xxxxxx HAS A CONFLICT BETWEEN FLAG4 (TMACVOLI) ANDACTVOL" was expanded to read: "VOLUME xxxxxx HAS A CONFLICT BETWEEN FLAG4 (TMACVOLI)OR FLAG5 (TMVTEXP) AND ACTVOL". Since the ACTVOL field can also be used to save the volser ofthe physical container volume of an exported virtual tape, ERR85 may also indicate a conflict betweenACTVOL and bit TMVTEXP of FLAG5, the "virtual volume exported" indicator. The ACTVOL field shouldPDC# QI35237

show a volser if either the TMACVOLI or the TMVTEXP flag bit is set, and should be hexzero otherwise.Any mismatch causes the ERR85 error to be issued.The misleading report lines "TMC LOW EXTENT IN HEX", "FIRST DSNB IN HEX" and "TMC DEVICECODE", which were printed at the end of the report and which referred to the allocation of the SYSUT3data set, have been removed.RESOLUTION:Documentation changes related to this enhancement:CA-1 5.2 Utilities and Reports Reference Guide1.38 TMSPTRS - Maintaining Multivolume/Multi-Data Set ChainsReplace the two paragraphs behind the caution box -TMSPTRS can be run without issuing a RESERVE against the TMC. This default option is valid only if thesame device type is used for SYSUT3 as is currently being used by the active TMC. A copy of the TMC ismade and then updated by applying all changes from the Audit data set that have occurred since the copyoperation began. Because it is necessary to apply the Audit records, TMSPTRS should not be run whileother CA-1 batch utilities, such as TMSCLEAN and TMSEXPDT, are running.If the device type specified in SYSUT3 is different than the device type of the active TMC, the ENQparameter must be specified. If the ENQ parameter is included, the active TMC is RESERVEd for theduration of the copy operation.with the following:TMSPTRS can be run without issuing a RESERVE against the TMC. A copy of the TMC is made and thenupdated by applying all changes from the Audit data set that have occurred since the copy operationbegan. Because it is necessary to apply the Audit records, TMSPTRS should not be run while other CA-1batch utilities, such as TMSCLEAN and TMSEXPDT, are running. If the ENQ parameter is specified, theactive TMC is RESERVEd for the duration of the copy operation.After the sentence -In the event TMSPTRS terminates with U0999 abend, R15 will indicate the cause:remove the entry for value 04:04 - SYSUT3 was referencing a device type unlike the one the TMC is on.1.38.1.1 Job Control StatementsIn the JCL box, change -//SYSUT3 DD UNIT=SYSDA,SPACE=(same as TMC)to://SYSUT3 DD UNIT=SYSDA,SPACE=(same as TMC) *NOTE 2PDC# QI35237

Note 2: The SYSUT3 data set holds a copy of the TMC. It may be blocked, regardless of whether the TMCitself is blocked or not. The BLKSIZE may be any multiple of the LRECL, which is 340.In the parameter definitions,ENQ Reserves the TMC for the length of the copy operation. This parameter is required if the device typespecified in SYSUT3 is not the same as the device type of the active TMC.remove the following sentence:This parameter is required if the device type specified in SYSUT3 is not the same as the device type of theactive TMC.1.38.6 TMS Report 29 - Invalid PointersAt the end of the displayed report, remove the following lines:TMC LOW EXTENT IN HEX CCHHR=02C1/0000/01FIRST DSNB IN HEXCCHHR=02CF/0000/22TMC DEVICE CODE =0E1.38.6.1 TMSPTRS Report Field DefinitionsRemove this section entirely:Message Error messageTMC LOW EXTENT IN HEXCylinder/head/track address of TMC copyFIRST DSNB IN HEXCylinder/head/track address of first DSNB record in TMC copyTMC DEVICE CODE Unit type device code of TMC copyUnit type device code of TMC copy2.32 TMSPTRS MessagesChange the description of ERR85 as follows:CA-1 5.2 Message GuideERR85 VOLUME xxxxxx HAS A CONFLICT BETWEEN FLAG4 (TMACVOLI) OR FLAG5(TMVTEXP) AND ACTVOLExplanation: Either the TMACVOLI bit of FLAG4 or the TMVTEXP bit of FLAG5 was on and ACTVOL wasblank, or ACTVOL was nonblank and both flag bits were off.PDC# QI35237

User response: If this is an AIVS volume, turn the TMACVOLI flag bit on and update ACTVOL with theactual internal volser. If this is an exported virtual volume, set the TMVTEXP flag bit and update ACTVOLwith the volser of the physical container volume that was used for the export. Otherwise, turn both flag bitsoff and set ACTVOL to HEXZEROS.Thank you for your continued support of Computer Associates and its products. If you have any questionsabout this Product Documentation Change or any other questions about BrightStor CA-1, please contactyour local Computer Associates Technical Support organization for BrightStor CA-1.PDC# QI35237

BrightStor CA-1 Product Documentation ChangePDC# QI37358DATE: April 14, 2003RELEASE: 5.2ENVIRONMENT: MVSHYPER: NoSUBJECT: New Retention and Vault System ISPF PanelsDESCRIPTION/DISCUSSION:A new set of panels to update the CA-1 Retention data set (RDS) Rules and the Vault Pattern data set(VPD) Rules have been added to CA-1 via maintenance PTF QO37342. Following is documentationrelated to this new feature.RESOLUTION:New RDS and VPD panelsTo inquire on or update the VPD and RDS rules, go to the CA-1 ISPF Primary Option Menu, type 3 (forMAINTENANCE) and press ENTER. The CA-1 ISPF Configuration Tables Maintenance Panel is displayedwith new options for RDS and VPD maintenance.CA-1 CONFIGURATION TABLES MAINTENANCE Panel---------------- CA-1 CONFIGURATION TABLES MAINTENANCE ---------------OPTION ===>1 - CA-1 SECURITY Table2 - CA-1 SYSTEM Options3 - CA-1 SCRATCH Pool Definitions4 - CA-1 NSM (Non-Specific Mount) Rules5 - CA-1 RDS Rules Edit6 - CA-1 VPD Rules EditRequired fields if requesting OPTION 2, 3, or 4:Do you wish to use the resident module ? ===> YES(Yes or No)The following information must be supplied if NO was entered above:Parmlib DSN ===>Member suffix ===>Allocate new ===> NO(2 digits)(YES or NO)Choose option 5 to edit the Retention data set Rules.Choose option 6 to edit the Vault Pattern Description Rules.PDC# QI37358

CA-1 Retention data set Rules (Option 5)------------------- Retention data set Rules -----------------Command ===> ______________________________ DATE: 02/01/0702.007RDS Dataset Name = ____________________________________________Confirm a rule delete: YESConfirm save of rules: YESThe name of the fully qualified data set that contains the RDS rules being edited will need to be provided.CA-1 Vault Pattern Rules (Option 6)----------------------- Vault Pattern Rules ---------------------Command ===> ___________________________________ DATE: 02/01/0702.0071 Maintain Vault Definitions (VAULT=)2 List Vault Patterns (DSN=, VOL= or CDSN=)Vault Patterns: ____________________________________________Vault Definitions : ____________________________________________Confirm a rule delete: YESConfirm save of rules: YESThe Vault Patterns field is the fully qualified name of the data set that contains the Vault Pattern rules(DSN=, CDSN= and VOL=) being edited. The Vault Definitions field is the fully qualified name of the dataset that contains the VAULTS statements (VAULTS=) being edited. The Vault Definitions field may be leftblank if your Vault Definitions are included in the Vault Patterns data set.VPD and RDS panels are formatted to fit on a 24-line by 80-character display. PF keys operate accordingto the definitions you specify or the defaults assigned at your site. Help panels are provided for every paneland may be accessed by pressing the HELP PF key (default is PF1), or by entering HELP on thecommand line and pressing ENTER.Using the panels to edit the VPD and RDS rules does not change the format of the rules. Also note that thepanels are not required to edit the rules; you may continue to edit the rules data sets with your favoriteeditor. When the panels are used to edit the rules, they are checked for errors when they are saved. Thepanels do not allow for new comments to be added but existing comments are preserved.InstallationAfter installing APAR QO37342 with SMP/E, the ISPF panels, messages and the CLIST members will beinstalled into the CA-1 target libraries. Check to make sure the target libraries are accessible to TSO onthe systems you want to have access to the new commands, or copy the CLIST members to a library thatis already accessible to TSO.PDC# QI37358

BrightStor CA-1 Product Documentation ChangePDC# QI44641DATE: September 25, 2003RELEASE: 5.2ENVIRONMENT: MVSHYPER: NoSUBJECT: Enhancement of TMSCYCLE to support ABARS GDGsDESCRIPTION/DISCUSSION:This Product Documentation Change (PDC) describes a change to utility TMSCYCLE introduced by APARQO44640. The APAR enables Cycle Control retention for ABARS pseudo GDG data set names ending in".CnnVnnnn".When ABARS GDGs get an EXPDT of CYCLE/ccc assigned, and the CA-1 system option ADGDG is set toYES, TMSCYCLE now handles the ABARS files like regular GDG data sets and disregards the versionspecificsuffix when building cycles. All generations of one ABARS GDG are now treated as cycles of onedata set, rather than as individual data sets.Following are documentation changes associated with this enhancement.RESOLUTION:CA-1 5.2 Utilities and Reports Reference Guide1.25 TMSCYCLE - Removing Tapes from Cycle ControlTMSCYCLE selects all TMC records with an EXPDT subject to Cycle Control (CYCLE/ccc in controlstatements and online interfaces, or LABEL=EXPDT=99ccc in JCL), to determine if any volumesassociated with the data set should be removed from Cycle Control. TMSCYCLE retention is determinedby the File 1 EXPDT only.To remove volumes from Cycle Control, TMSCYCLE updates the expiration date in the TMC to the currentdate or to the current date plus the number of days defined in the TMOOPTxx member of CAI.PPOPTION(RC parameter). TMSCYCLE does not consider the generation/version number for GDG data sets.Therefore, GDGs under Cycle Control may expire prior to meeting the GDG limit. If Cycle Control is usedfor ABARS pseudo GDG data sets (ending in ".CnnVnnnn"), system option ADGDG should be set to YES.This allows the pseudo GDGs to be treated the same way as regular GDG data sets.CA-1 5.2 Systems Programmer Guide1.6.3.8 ABARS Pseudo GDGs (Options Checklist #31)The ADGDG parameter allows pseudo GDGs created by the ABARS product to be handled the same wayas true GDGs during the vaulting process and during calculation of Cycle Control retention.PDC# QI44641

Specification:If set to YES, the CnnVnnnn pseudo GDG files created by ABARS are treated the same way as true GDGsin the vaulting process and in TMSCYCLE.Default: The default value for ADGDG is NO.Thank you for your continued support of Computer Associates and its products. If you have any questionsabout this Product Documentation Change or any other questions about BrightStor CA-1, please contactyour local Computer Associates Technical Support organization for BrightStor CA-1.PDC# QI44641

BrightStor CA-1 Product Documentation ChangePDC# QI47060DATE: November 18, 2003RELEASE: 5.2ENVIRONMENT: MVSHYPER: NoSUBJECT: Changes to the 3495/3494 Tape Library Data Server Synchronization Utility CTSSYNCDESCRIPTION/DISCUSSION:CTS APAR QO46925 was created to standardize return code setting of utility CTSSYNC. The programlogic was changed to set appropriate completion codes in case of missing input parameters or LCScommandfailures due to volumes not being found in the LCS database.The following documentation changes are provided to clarify return code setting.RESOLUTION:BrightStor CA-1 Utilities and Reports Reference Guide1.4 CTSSYNC - 3495/3494 Tape Library Data Server Synchronization UtilityCompletion CodesCTSSYNC can complete with the following condition codes.RC=0 Successful completionThe requested commands were performed successfully.Or commands were not processed because no volser was provided.RC=4 Successful completion with redundant commandsIn VERIFY mode, one or more ATL commands failed or could not be performed because the volser wasnot defined in the 3495/3494 LCS database.Or for the SYNC command, synchronization of one or more volumes was bypassed, due to their status inthe tape management database.Or a PRIVATE, PROTECT or SCRATCH command was issued for a volume which already was in therequested status in the LCS database.RC=8 Processing errorsOne or more ATL commands failed or could not be performed because the volser was not defined in the3495/3494 LCS database, and NOVERIFY was specified.Or one or more ATL commands failed for other reasons.PDC# QI47060

Or no valid input command was found.Or the tape management system was not active.RC=12 Incorrect job setupA required DD statement was missing.RC=16 Invalid requestA schedule of both IMPORT and EXPORT operations was attempted.Thank you for your continued support of Computer Associates and its products. If you have any questionsabout this Product Documentation Change or any other questions about BrightStor CA-1, please contactyour local Computer Associates Technical Support organization for BrightStor CA-1.PDC# QI47060

DATE: November 18, 2003RELEASE: 5.2ENVIRONMENT: MVSHYPER: NoBrightStor CA-1 Product Documentation ChangeQI47064SUBJECT: Support for 3592 and 9840C Tape DevicesDESCRIPTION/DISCUSSION:Support for the new IBM 3592 and STK 9840C device types has been provided by CA-1 APARs QO46928and QO46929 and by CTS APAR QO46930.New density and tape recording technique bit values are available to record the new cartridges in the TMC.During tape creation, CA-1 determines the device type and updates the TMC accordingly. For 3592volumes, CA-1 also documents whether the tape capacity has been reduced by performance scaling.Following are documentation changes associated with this enhancement.RESOLUTION:BrightStor CA-1 Systems Programmer GuideAppendix A.1 TMC Volume Record Definition with Keywords (TMMTMREC)Add the following values to the definition of the TRTCH field:----------------------------------------------------------------------------------------------------------------------------------------------TM9844 E2 HEX X'E2' STORAGE TEK 9840-C CARTRIDGE(9844)----------------------------------------------------------------------------------------------------------------------------------------------TMEF1 EE HEX X'EE' 3592 CARTRIDGE - EXTENDEDFORMAT 1----------------------------------------------------------------------------------------------------------------------------------------------TMEF1S EF HEX X'EF' 3592 CARTRIDGE - EXTENDEDFORMAT 1, PERFORMANCE SCALEDAdd the following value to the definition of the DEN field:TM3592 E9 HEX X'E9' 3592 (CARTRIDGE TAPE)PDC# QI47064

Thank you for your continued support of Computer Associates and its products. If you have any questionsabout this Product Documentation Change or any other questions about BrightStor CA-1, please contactyour local Computer Associates Technical Support organization for BrightStor CA-1.PDC# QI47064

BrightStor CA-1 Product Documentation ChangePDC# QI48357DATE: December 9, 2003RELEASE: 5.2ENVIRONMENT: MVSHYPER: NoSUBJECT: Enhancements - New, Modified, and Obsolete OptionsDESCRIPTION/DISCUSSION:CA-1 APARs QO48315, QO48317, and QO48318 introduce five new options, change four options, andremove two obsolete options. Changes were made to the ISPF panels that display or allow updates to theTMOOPTxx member, as well as to the parsing of the PPOPTION member during TMSINIT processing andreporting. The following documentation provides information about these changes and enhancements.RESOLUTION:OBSOLETE OPTIONSThe two obsolete options are TRUXPD and KEYDD. These options were added as support for Y2K toallow the option of treating keyword expiration dates as a true date or keyword dates. Since 1998/DDD and1999/DDD are no longer in conflict with true expiration dates, these options are no longer needed. If thesetwo options are present, you will receive an IEFTMS12 message when TMSINIT is run. However, in thiscase this is an informational only message. TMSINIT will still run successfully and process all otherparameters.MODIFIED OPTIONSThe four options that have been changed to accept additional values are LCHG, YSVC, FUNC, and ABE.LCHG, YSVC and FUNC have been changed to accept two new values of E or EXT (for EXTended).These options will still accept values of Y or YES and N or NO which will work exactly as they didpreviously.• The LCHG optionThe new LCHG value of E or EXT allows you to control label changes through an external securityrule. If LCHG is set to EXTended, a security call is done to determine if the label change will beallowed or not. This new security call is very similar to the security calls previously done by the FUNCoption. Within the class or key of CATAPE, CAT, or CA@APE (depending on your external securitysystem), a check is done on a resource of x2yRES.Vvvvvvv.UCBnnnn orx2yNORES.Vvvvvvv.UCBnnnn.- 'x' and 'y' are either 'S' for SL, 'A' for AL, or 'N' for NL- 'RES' or 'NORES' indicates if the volume is resident (defined to the TMC) or not- 'vvvvvv' is the volser of the volume whose label type is being changed- 'nnnn' is the UCB address where the label change is taking placePDC# QI48357

For example, if volume 123456 is defined in the TMC in a scratch state, and is being changed from SLto NL on device 1AE4, a security check will be done (read level access)against a resource called'S2NRES.V123456.UCB1AE4'. Generic rules can be set to support S2NRES.V*, S2NNORES.V*,A2NRES.V*,A2NNORES.V*, etc. Once these 12 generic rules are defined, you may also define rulesfor specific volumes or masks to indicate ranges of volumes for special treatment. Also, setting up arule such as'S2NRES.V*.UCB1E0*' would control SL to NL label changes for all volumes on devices1E00-1E0F. In order for the EXT option of LCHG to work, there is a requirement that FUNC must beset to either YES or EXT. If FUNC is set to NO, then even if LCHG is set to EXT no external securitycall will be made.• The YSVC optionThe new YSVC value of E or EXT means that even if the caller of the YSVC service has UPDATE levelaccess (unconditional update) to the YSVCUNCD resource if the data set name is being changed,security will be checked as if the caller had YSVCCOND access (conditional update access).Thismeans that someone with UPDATE level access to the YSVCUNCD resource cannot change the dataset name unless they also have access to both the original and new data set names. They can changeany other field without any additional security checks, but not the data set name. This is therecommended value for the YSVC option, since there is no reason during normal tape librarianfunctions to change the data set name on a CA-1-controlled volume. However, the default for YSVChas been left as NO for those sites that have never activated external security control over CA-1.• The FUNC optionThe new FUNC value of E or EXT means that instead of simply checking to see if access is permittedto a resource, such as BLPNORES or NLRES, the resource that will be checked is in a new "extended"format. The new resource name starts with the same 5-8 characters that were previously checked,however there are two more qualifiers included. The format is 'xxxRES.Vvvvvvv.UCBnnnn' or'xxxNORES.Vvvvvvv.UCBnnnn'. The xxx is either BLP, NL, NSL, or FOR (for foreign tape processing).The RES or NORES indicates if the volume is resident to CA-1 (defined in the TMC) or not. The vvvvvvis the volser of the volume being accessed, and nnnn is the UCB address the access is beingattempted upon. If you want to prevent anyone from using EXPDT=98000 to bypass CA-1 for tapesinside a robotic device whose UCB addresses are 01E0-01EF, you would code a rule in your externalsecurity system for the following resource: 'FOR*.V*.UCB01E*'. This will control both FORRES andFORNORES processing (using EXPDT=98000 for both in-house tapes and foreign tapes), for allvolumes, where the UCB address is between 01E0 and 01EF.• The ABE optionThe ABE option still accepts a value of 0-999, meaning the ddd portion of LDATE/ddd will be assignedto any tape files closed by abend processing. You can now also use a value of CATALOG orDAYS000-DAYS999. CATALOG indicates that the default abend expiration date is CATALOG. A valueof DAYSnnn indicates that the abend expiration date is simply the specified number of days sincecreation.NEW OPTIONSThe five new options are CATSEC, NLWTOR, MIXGDG, UX0AUPD, and PMASK.- The CATSEC optionCATSEC indicates that CA-1 should perform an external security call whenever a tape file is beingPDC# QI48357

CATALOGed or UNCATALOGed from the OS Catalog. This security check is similar to the one doneby your external security system, but will be done even if the external security system is not active fortape data sets. If you want to rely strictly on CA-1 to "drive" the external security calls, use CATSEC tocause CA-1 to issue security calls similar to those of an external security system. The difference (muchlike the difference with the CA-1OCEOV option and standard external security checks) is in theprocessing of foreign volumes and non-existent tape files. If CATSEC is set to Y or YES (default is Nor NO), then an external security call will be done whenever a tape file is being cataloged. Likewise, asecurity call will be made when a tape file is being uncataloged. However, if the CATSEC option is setto B or BYP, then the security call will be bypassed if the volume it is currently cataloged to is notdefined in the TMC or ifthe volume is in scratch status. This way, a value of B or BYP will allow oldcatalog entries to be removed without having to give the person special access to the user catalogs ordefine rules for data sets that no longer exist.- The NLWTOR optionThe NLWTOR option NLWTOR is a replacement for the optional usermod T5XD917. If NLWTOR is setto N or NO (default is Y or YES), it prevents the IECTMS1 WTOR from being issued when a tape iscalled for by specific volser and no labels are present. It is "assumed" that the requested volume will bemounted correctly. Many sites with robotic systems that still use NL or BLP use this optional usermodto prevent this WTOR. If a request is made to read an NL volume 123456(VOL=SER=123456,LABEL=NL), then in a robotic environment it may be assumed that the requestedvolume will always be correctly mounted. A value of Y or YES will indicate that the IECTMS1 WTORwill still be issued as it was previously.- The MIXGDG optionThe MIXGDG option MIXGDG is a replacement for optional usermod TF45060.If MIXGDG is set to Yor YES (default is N or NO), then the catalog indicator will correctly be turned off when a (+1)generation is created on DASD that results in a tape generation being "bumped off". Previously,without this option and without TF45060, if a (+1) was created on DASD and the oldest generation"bumped off" resided on tape, the catalog indicator was not turned off in the TMC.- The UX0AUPD optionThe UX0AUPD option UX0AUPD is a replacement for the optional usermodT5Q4137. With this optionset to Y or YES (default is N or NO), then a new call is made to exit-A (TMSUX2A).This new call ismade just prior to the update of the TMC (while the TMC is enqueued) and allows for changes to theTMC record itself. This has been used by some customers that want to change the expiration datefrom what was specified in the JCL without using retention rules in TMSEXPDT. It has also been usedto store the CPU ID on which the file was created, in the user field (instead of doing the same thingwith an SMF exit). If this option is changed to Y or YES, make sure the version of exit-A (TMSUX2A),already active on the system, can support this new call. The AXOPCODE in the parameter list for thisnew call is x'14'.- The PMASK optionThe new PMASK option allows the six pattern masking characters to be changed. Note: Use of thebackslash character cannot be changed. Instead of using #@!?*- as the six pattern maskingcharacters, you can specify any non-alpha or non-numeric characters you want. The only additionalrestriction is that no character can be used more than once (and of course the back-slash charactercannot be used either). If this option is used, and the characters are changed (which is NOTRECOMMENDED), then you must make sure that all rules in the TMONSMxx member, as well as allRetention and Vaulting rules, are also changed at the same time. If the PMASK option is used, and thepattern masking characters are changed without changing the rules, then the results of TMSEXPDT orthe Vaulting System may not be what is expected.PDC# QI48357

CONCLUSION:In addition to these option updates, CA-1 now checks to see if any option (new or existing) is specifiedmore than once. If it is, the last value will be used and a new informational version of message IEFTMS12will be issued, indicating that an option has been specified twice. Use of the last specified value means thatTMSINIT will function as it previously did, but the new informational message will be issued to allowcleanup of the TMOOPTxx member. No change to the TMOOPTxx member of PPOPTION is necessaryunless you choose to exploit any of the new features. However, it is recommended that the obsoleteoptions be removed as soon as possible. Processing will remain the same for the existing options until youchange the values. Likewise, if you do not add any of the new options to TMOOPTxx, CA-1 will continue toprocess as it previously did. If you want to take advantage of and exploit these new options you need toupdate TMOOPTxx.NEW MESSAGESIECTMS3E dddd,vvvvvv IS NOT SCRTCH(38)IECTMS3O dddd,vvvvvv IS NOT SCRTCH(38)Reason: An attempt has been made to change the label-type of volume vvvvvv which has been rejectedbased on external security rules.Action: Mount a tape already labeled with the requested label-type to avoid a label-change operation.IEFTMS12 - ERROR BUILDING OPTIONS TABLE, OPTION XXXXXXXX IS A DUPLICATEExplanation: The option xxxxxxxxx was found duplicated in the TMOOPTxx member of PPOPTION. Thelast option found will actually be the one used. CA-1 initialization continues.User Response: It is recommended that duplicate options be removed from the TMOOPTxx member. Thiswill prevent problems when it is thought that a specific option is specified one way, when a duplicate entryactually causes the option to work in a different way.PDC# QI48357

BrightStor CA-1 Product Documentation ChangePDC# QI53827DATE: April 26, 2004RELEASE: 5.2GENLEVEL: AllENVIRONMENT: MVSHYPER: NoSUBJECT: New Dynamic TMC Extend featureDESCRIPTION/DISCUSSION:This PDC (Product Documentation Change) documents a major new feature of BrightStor CA-1 that allowsyou to add and remove volume ranges from the BrightStor CA-1 Tape Management Catalog (TMC) withoutstopping tape processing. The feature is delivered in PTFs QO52668, QO52477 and QO51169 andconsists of a new batch utility, TMSXTEND, and subprograms, some of which may also be executed asstandalone utilities to report on the volume ranges defined to BrightStor CA-1 and the z/OS systemssharing the TMC. The restriction on number of ranges defined to the TMC (currently restricted to 52ranges) has also been eliminated with this enhancement.In addition, the TMSXTEND utility has been designed to automatically convert alphanumeric volume serialnumbers to their BrightStor CA-1 internal format. Except for a small number of customers usingnonstandard volume serial number formats identified below, this new functionality will allow you to retirethe TMSUX2U and TMSUX2E user exits that have been previously necessary for alphanumeric volsersupport. They are not required to be removed, but will not be used by BrightStor CA-1 after TMSXTENDhas been successfully executed.TMSXTEND has been designed for multi-system environments where the TMC is shared by a number ofz/OS images. A new TMC is dynamically built by copying the existing TMC, and adding or removingvolume ranges and DSNBs. TMC updates for active tape processing are monitored through the BrightStorCA-1 Audit file and any updates to the TMC made during the extend function are also made to the newTMC. TMSXTEND identifies the systems sharing the TMC by analyzing the Audit file, confirms that theyare at the correct level and, when the new TMC is complete and current, triggers the switch from the oldTMC to the new TMC on all systems. Even though the TMSXTEND job may complete successfully, untilthat final switch has occurred (either by TMSRINIT or by any tape O/C/EOV event occurring) on ALLsystems, the extend process should not be considered complete.TMSXTEND will change CTL#4 so it will appear that the Audit file is past the warning threshold level. Assoon as TMSXTEND is finished, IEFTMS9 messages will start occurring for every update to the TMC untilTMSCOPY is run.RESOLUTION:This PDC is organized into sections describing the TMC Extend utility and its subprograms that may beexecuted separately to aid in planning a TMC extend. The documentation provided in this PDC should beretained and added to your copy of the BrightStor CA-1 Utilities and Reports Reference Guide.• TMSXTENDThis section documents the TMC Extend utility and restrictions concerning its use, as well as thenecessary JCL, control statements and messages.PDC# QI53827

• 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

4. TMSBINQ, the online TMSTIQ display of the volume ranges, and the CA-1 ISPF online display ofthe volume ranges are different on an Extended Format TMC. The display will now show thestarting and ending volser in each range and the starting and ending relative record number foreach of those volsers.REPORT DESCRIPTIONSubprograms of TMSXTEND, TMSBLDVR and TMSAUDEX create two reports - TMS REPORT-80 andTMS REPORT-81 respectively.PLANNINGPROCEDURES FOR EXECUTING THE TMSXTEND UTILITYPlanning is an important part of running the TMSXTEND utility, especially the first time. The TMSXTENDutility will create new Volume Definition records in the TMC. Every system sharing the TMC must be at thecorrect maintenance level to perform an extend. The required PTFs are QO52668, QO52477 andQO51169. TMSXTEND will check the maintenance level of every system it finds having written records tothe BrightStor CA-1 Audit file; however, you must make sure that this accurately reflects your shared TMCenvironment. If a system has not been up, with CA-1 tape activity being recorded to the Audit, that systemwill not be known. If CA-1 is later started on that system without the necessary maintenance applied, it willfail to initialize. You should first run the TMSBLDVR utility in standalone mode to evaluate your TMCvolume ranges.If you have coded CA-1 user exits TMSUX2E and TMSUX2U to support volume serial numbers withalpha characters in the rightmost position in the volser, you will not be able to use TMSXTEND.1. Apply PTFs QO52668, QO52477 and QO51169 to all systems in the shared TMC environment.You may install these PTFs and continue to run without an IPL. However, you must IPL every CPUbefore your first run of TMSXTEND. A new type-5 Audit record that TMSXTEND and TMSAUDEXlook for will be cut AFTER an IPL with this maintenance active.2. Run TMSAUDEX to verify that you have identified all of the systems updating the TMC asrecorded in your active Audit file. Any systems found by analyzing an old Audit that are not alsofound in the active Audit should be explicitly included with an INCLUDE control statement. If thesystem is not a production system, it can be excluded with an EXCLUDE statement; however, itmust be upgraded later if it is to ever share the new TMC.3. Run the TMSBLDVR utility in standalone mode, specifying the ranges you want to add or remove.TMSBLDVR will analyze the existing and new volume ranges and report any possible errors. It willalso report on the amount of space that the new TMC will require to support the existing rangesplus any new ranges being added.4. Fix the errors coming out of TMSBLDVR. If any volumes with alpha characters in the right-mostposition are found, you will not be able to use the TMSXTEND utility.5. Verify that program TMSRINIT can be run on all systems in the shared TMC environment. Thisshould be done by specifying PARM=STATUS in the JCL.6. If you are removing volume ranges from the TMC and you use the scratch subpooling feature ofBrightStor CA-1, make certain that any volume ranges being removed are not defined in a rangestatement in the TMOSCRnn member of PPOPTION (used to define scratch subpools).7. You should review your catalog environment to determine if the TMC is cataloged in any nonsharedcatalogs. Any recatalog actions performed by the TMSXTEND utility will be performedfrom the catalog environment on the system where TMSXTEND is run. See the notes below in theFOLLOW UP PROCEDURES.PDC# QI53827

RUNNING TMSXTENDAfter performing the planning steps outlined above to verify that all systems sharing the TMC are at theproper maintenance level and that the desired range and DSNB additions or deletions are valid, you arenow ready to execute TMSXTEND.1. Pre-allocate the new BrightStor CA-1 TMC on the desired volume using the following namingconvention - use the current TMC name and add a suffix of '.N'. Refer to the report from TMSBLDVRfor the space requirements of the new TMC. An example of the naming requirement is:Existing TMC name - SYS3.CA1.TMCNew TMC name - SYS3.CA1.TMC.NNote: The new TMC name MUST be cataloged on every system sharing the TMC.You may change the blocking factor for the TMC by allocating the new TMC with the desired blocksize.Refer to the BrightStor CA-1 Systems Programmer Guide for additional guidelines on blocking theTMC.2. Run TMSPTRS to insure that any critical chaining errors in the DSNB free chain are corrected. Minorerrors in DSNB or volume records will not cause any problems for TMSXTEND (such as incorrectDSN17 fields, or a bad 1STVSN field), but errors in the DSNB free chain may cause TMSXTEND toabend.3. No BrightStor CA-1 batch utilities should be running when you execute TMSXTEND. You should planto run TMSXTEND before or after the BrightStor CA-1 daily maintenance or any other BrightStor CA-1batch job. Also, the DBS subtask of CTS must be shutdown (if active) prior to the execution ofTMSXTEND (refer to section 10.4 of the BrightStor CA-1 Administrator and Operator Guide). TheBrightStor CA-Vantage script for BrightStor CA-1 must be disabled. While the ISPF interface and theold TSOTIQ interface will both work correctly for individual volume and/or DSNB inquiries or updates,the range-display in the ISPF interface will NOT work while TMSXTEND is in progress.4. Run the TMSXTEND utility first with PARM=TEST to verify that all systems are in the proper status andthat the volume/DSNB control statements are valid. This will also validate that the new TMC is largeenough to hold all records requested.5. Backup the TMC by running TMSCOPY. This must be performed within three hours of runningTMSXTEND.6. Submit the TMSXTEND utility and monitor its execution. It will provide numerous messages indicatingthe status of the extend and the switch to the new TMC.7. Review messages produced by TMSXTEND to insure no errors were encountered. If abends wereencountered that TMSXTEND could not automatically recover from, run TMSXTEND withPARM=RECOVER. Refer to the messages issued from TMSXTEND to see if the automatic recoveryhad already taken place.8. Verify that all systems switched to the new TMC by checking the job log of the TMSXTEND utility andby inspecting the system consoles for the non-deleteable message, TMSMR04I, confirming the switch.If any CPUs involved do not have tape activity, it is recommended that either TMSRINIT or TMSINITbe run on that CPU to finalize the switch to the new TMC.9. Create a post-conversion backup of the TMC by running the TMSCOPY utility again.PDC# QI53827

FOLLOW UP PROCEDURES AFTER INITIAL RUN OF TMSXTEND1. After you have converted to an Extended Format TMC, exits TMSUX2U and TMSUX2E must beretired. Remove them from your LINKLIST library.2. Users in a non-shared MVS/catalog environment should check to insure that the TMC is cataloged onthe correct volume on all systems. For systems that are not part of a shared catalog structure, youmust uncatalog the old TMC and catalog it on the new volume (where you had allocated "TMC.N".)Job Control Statements//stepname EXEC PGM=TMSXTEND,REGION=0M,// PARM='parm1,parm2 '//TMSRPT80 DD SYSOUT=* /* TMSBLDVR RPT *///TMSRPT81 DD SYSOUT=* /* TMSAUDEX RPT *///SYSPRINT DD SYSOUT=* /* IDCAMS OUTPUT *///CAISNP DD SYSOUT=*//SYSUDUMP DD SYSOUT=*//*//SYSIN DD *ADDVOL 001800-001899 ROBTY=02 VENDOR=BASFADDVOL VM5000-VM5099 /* adding a second range */REMVOL VT0100-VT0199 /* sample of removing a volume range*/ADDDSNB 1000/*//CPULIST DD *EXCLUDE CPU9 /* this is a test system we are removing */INCLUDE CPU6 /* PROD system with no tape activity *//*Parameter DefinitionsThe DIAG parameter can be specified alone or with the TEST or RECOVER parameter. Parameters maybe specified in any order and separated by commas or blanks. If the RECOVER parameter is omitted theprogram will execute in extend mode.• DIAGThis parameter causes TMSXTEND to write diagnostic snap dumps to the CAISNP output. Snapdumps are created to display internal volume tables, key data areas and changes to control records.• RECOVERThis parameter causes TMSXTEND to run in recovery mode. In recovery mode TMSXTEND willdetermine the status of a failed extend. If the signal to switch to the new TMC has NOT yet been givento all CPUs sharing the TMC, it will rename and return the old TMC to its original status, updating anycontrol records necessary. If the signal to switch to the new TMC HAS been given to all CPUs sharingthe TMC, it will finish updating any control records necessary.• TESTThis parameter causes TMSXTEND to run in test mode. In test mode, TMSXTEND will perform all ofthe checks and most of the functions of the actual extend mode. The new TMC is created andsynchronized but the TMCs are not renamed and the CPUs do not switch to the new TMC.This mode allows you to preview or test the extend process. In test mode, if errors are detected theywill be reported but the process does not fail as it does with an actual extend.PDC# QI53827

JCL ConsiderationsNote that the JCL provided in this document assumes that the BrightStor CA-1 load library is defined as aLINKLIST data set.• TMSRPT80 - Defines the report output data set for the TMS REPORT-80. This DD statement isrequired.• TMSRPT81 - Defines the report output data set for the TMS REPORT-81. This DD statement isoptional.• SYSPRINT - Defines the report output data set used by IDCAMS, which is invoked to perform the TMCrenames. This DD statement is required.• CAISNP - TMSXTEND writes snap dumps to this DD statement when requested by PARM=DIAG.This DD statement is required only if PARM=DIAG is specified.• SYSIN - Defines the input data set for volume range and DSNB control statements. This DDstatement is optional. If you do not specify a SYSIN DD statement, all volume ranges and DSNBs inthe existing TMC will be copied to the new TMC. This approach may be used to copy a TMC to a new,blocked TMC without adding or removing any volume ranges.• CPULIST - Defines the input data set for CPU include or exclude control statements. This DDstatement is optional and if not specified, all CPUs sharing the TMC must be found in the current Auditfile.Completion CodesThe following completion codes are issued by TMSXTEND:• 0 - Successful completion.• 8 - TMC extend failed. Refer to the TMS REPORT-80 or 81 reports and the job log to determine causeof failure.• U0006 - Invalid control statement error. Check TMS REPORT-80 or 81 to determine cause of failure.• U0996 - The current TMC could not be allocated. Check to insure that the TMC is cataloged on thesystem where you are running TMSXTEND.• U0997 - The new TMC could not be allocated or opened. Refer to messages TMSVR03E orTMSVR05E for further information.• U1022 - TMSXTEND has abended for one of many reasons. Refer to the complete list of reason codeson page 18.Control Statement SpecificationsControl statements for the SYSIN DD statement• ADDDSNB nnnnnnnRequests that nnnnnnn additional DSNB records be added to the new TMC.• ADDVOL lowvol-highvol DEN=nn ROBTY=nn TRTCH=nn VENDOR=cccccccc DELETESpecifies that the volume range lowvol-highvol be added to the new TMC. Optional parameters areprovided to initialize the volume records with a density (DEN), robot type (ROBTY) recording technique(TRTCH) and vendor (VENDOR). For the DEN, ROBTY and TRTCH parameters, nn should bereplaced with hexadecimal values as defined in the BrightStor CA-1 Systems Programmer Guide,PDC# QI53827

Appendix A., TMC Volume Definition Keywords. The DELETE parameter simply indicates thevolume(s) are added in DELETE status in the new TMC. VENDOR is a 1-8 character string that is usedto identify the media manufacturer. In addition to a range, a single volser may also be specified on theADDVOL statement.Note 1 - The dash ("-") is required between lowvol and highvol.Note 2 - Volsers shorter than 6 characters are supported - they will be left justified and padded withblanks.• REMDSNB nnnnnnnRequests that nnnnnnn free DSNB records be removed from the new TMC. Only DSNBs from the endof the free chain that have never been used can be removed.• REMVOL lowvol-highvolSpecifies that all volumes in the range lowvol-highvol be removed from the TMC. All volumes in thisrange must be in DELETE status, otherwise the entire range is not removed. A single volser may alsobe specified on a REMVOL control statement.Control statements for the CPULIST DD statementWhen all systems sharing the TMC have tape processing performed on them at least once a day, there isno need for any CPUs to be included in the CPULIST control statements. However, if there are someCPUs that have NO tape processing performed on them, or where the tape processing is very sporadic(and can go for days at a time without any tape processing), then it would be recommended to use theINCLUDE type of CPULIST control statement.The EXCLUDE control statement should only be used when:there is a CPU that shares the TMC *** AND *** that CPU will not be active when TMSXTEND is running*** AND *** that CPU is 100% guaranteed to be at the correct maintenance level with QO52668, QO52477and QO51169 applied. If that CPU will be active, but there will not be any tape jobs running on it, it shouldNOT be excluded using the EXCLUDE control statement.Also, you cannot exclude the CPU that TMSXTEND is running on itself. If the SMF ID of the CPU thatTMSXTEND is running on is listed on the EXCLUDE statement, it will be automatically included and shownas "forced" on Report-81.• INCLUDE smf idThis control statement defines the SMF ID of a system running BrightStor CA-1 that should be includedin the list of systems to process when performing an extend function. INCLUDE must begin in column1 followed by a blank and then the SMF ID. Only one SMF ID may be specified per control statement.• EXCLUDE smf idThis control statement defines the SMF ID of systems running BrightStor CA-1 that should be excludedfrom processing by TMSXTEND. EXCLUDE must begin in column 1, followed by a blank and then theSMF ID. Only one SMF ID may be specified per control statement. Note that failure to find a systemspecified on an EXCLUDE statement is not considered an error.Comments (identified by an asterisk in column 1) may be specified in both CPULIST and SYSIN DDs;however, they are not listed in any report.TMSXTEND Report Field DefinitionsThe report field definitions for the TMS REPORT-80 and 81 are documented in the sections on theTMSBLDVR and TMSAUDEX utilities later in this PDC.PDC# QI53827

TMSXTEND Recovery ProceduresAs has been previously mentioned, if an abend situation occurs in TMSXTEND, it will probably recover byitself (look for messages TMSXT41I and TMSXT49I). However, if the machine that TMSXTEND is runningon goes down, there will be some manual recovery necessary.The first scenario is when the TMC being extended is shared by more than one CPU. This is the easiestsituation to recover from. Simply run TMSXTEND with PARM=RECOVER on any other CPU that sharesthe same TMC and Audit.The second scenario is when the TMC being extended is only accessed from one CPU, and that CPUgoes down. After it has been re-IPL'd and CAS9 has run, but BEFORE the TMSINIT job has been run, youmay be required to perform some manual intervention. If the TMSXT30I message had been issued, butNOT the TMSXT31I message OR TMSXT21I messages, then you must manually rename TMC.O to TMCbefore running TMSINIT. In this situation, after TMSINIT has been run you should also run TMSXTENDwith a PARM=RECOVER to finish the cleanup of CTL#4.In the same scenario, if the TMSXT30I message had not yet been issued by TMSXTEND, then there is norecovery necessary and you may simply run TMSINIT.Also in this same scenario, if the TMSXT31I AND TMSXT21I messages had both already been issued,there is also no recovery necessary and you may simply run TMSINIT.NEW MESSAGESThe following new messages may be issued by the new TMC Extend Utility, TMSXTEND, and itssubprograms. These messages will be added to the BrightStor CA-1 Messages Guide.TMSMR01I NEW TMC INITIALIZATION STARTED FOR CA-1.Explanation: TMSMRINT has begun the process of allocating and testing the new TMC.User Response: None. Information only.TMSMR02I NEW TMC INITIALIZATION COMPLETE FOR CA-1.Explanation: TMSMRINT has allocated and tested a new TMC. The control blocks for the new TMC areanchored in the TMVT in field TVRINIT.User Response: None. Information only.TMSMR03I CA-1 SWITCHING TO NEW TMC.Explanation: TMSMRINT has begun the process of switching to the new TMC.User Response: None. Information only.TMSMR04I CA-1 SWITCHED TO NEW TMC.Explanation: TMSMRINT has completed the switch to the new TMC. The anchor field, TVRINIT, in theTMVT has been cleared. The new TMC is now the active TMC for this CPU.User Response: None. Information only.TMSMR09I CLEARED EXTEND STATUS FOR ALL CPUS.Explanation: TMSMRINT has recognized that all CPUs have been switched to the new TMC and allrenames completed. It then clears all the signaling information from CTL#4.PDC# QI53827

User Response: None. Information only.TMSMR99E CA-1 EXTEND PROCESS ABORTED. REASON=XXXExplanation: TMSMRINT was unable to complete and has aborted the current process. XXX is the uniquereason for the abort. Diagnostic data may also appear on the console and job log.User Response: Call BrightStor CA-1 Support. Have the REASON=XXX and diagnostic data available.TMSRI00I CPU(cccc) - TMC EXTEND MONITOR ACTIVATED.Explanation: TMSRINIT has been started to support the TMC extend process on a system which is notresponding to TMSXTEND.User Response: None. Information only.TMSRI01I CPU(cccc) - DETECTED TMC EXTENDING.Explanation: TMSRINIT has recognized the TMC extend process and is monitoring CTL#4 record for validextend functions.User Response: None. Information only.TMSRI02I CPU(cccc) - CALL TMSMRINT TO ACCESS NEW TMC.Explanation: Program TMSMRINT has been called to access the new TMC. Message TMSMR02I will beissued when this CPU has successfully accessed the TMC.User Response: None. Information only.TMSRI03I CPU(cccc) - CALL TMSMRINT TO SWITCH TMCS.Explanation: Program TMSMRINT has been called to switch to the new TMC. Message TMSMR04I willbe issued when the switch has been successfully completed for this CPU.User Response: None. Information only.TMSRI04I CPU(cccc) - CLEARED EXTEND STATUS FOR ALL CPUS.Explanation: TMSRINIT recognized that all CPUs have been switched to the new TMC and all renamescompleted. It then clears all the signaling information from CTL#4.User Response: None. Information only.TMSRI05I CPUInn=cccc AUDFLG=aa CPUFnn=ccExplanation: TMSRINIT is displaying the status of the signal flags in CTL#4. Where cccc is the SMF ID forthe CPU, aa is the hex value of the Audit flag, and cc is the hex value of the CPU flag.User Response: None. Information only.TMSVR02E INVALID RANGE. ABENDS WITH U0006.Explanation: Invalid range statement processed.User Response: Correct the range statement.TMSVR03E CAN NOT OPEN CURRENT TMCExplanation: The TMC cannot be opened.User Response: Verify that the active TMC on the system where TMSBLDVR is running is a valid TMC.PDC# QI53827

TMSVR05E CAN NOT ALLOCATE NEW TMCExplanation: A new TMC could not be allocated. The format of the TMC is the old TMC name followed byan '.N'.User Response: Allocate a new TMC on the desired target volume with the required TMC name.TMSVR06E CAN NOT ALLOCATE CURRENT TMCExplanation: The current TMC could not be allocated.User Response: Determine why the TMC could not be located. Check that the TMC is cataloged on thesystem where TMSBLDVR is running.TMSVR07I CREATE NEW VSN CONTROL RECORDS.Explanation: TMSXTEND subprogram TMSBLDVR is creating the new volume range records andupdating the TMC control records to point to the new volume range records.User Response: None. Information only.TMSVR11I COPY/CREATE/REMOVE VOLUME RECORDS.Explanation: TMSXTEND subprogram TMSBLDVR has initiated the process of building the volumerecords in the new TMC from the records defined in the old TMC and applying any volume additions orremovals as requested in control statements.User Response: None. Information only.TMSVR13I CREATE VOLUME DEFINITION RECORDS.Explanation: TMSXTEND subprogram TMSBLDVR has started the process of adding the VolumeDefinition records to the TMC.User Response: None. Information only.TMSVR15I COPY/CREATE/REMOVE DSNB RECORDS.Explanation: TMSXTEND subprogram TMSBLDVR has initiated the process of building the DSNB recordsin the new TMC from the DSNB records in the old TMC and applying any DSNB record additions orremovals as requested in control statements.User Response: None. Information only.TMSXT01I TMC EXTEND STARTING.Explanation: TMSXTEND has started.User Response: None. Information only.TMSXT03I ATTACH TMSAUDEX FOR STATUS OF CPUS.Explanation: TMSAUDEX has been started to find all the CPUs which have written to the Audit file.User Response: None. Information only.TMSXT04I CPU STATUS TABLE OBTAINED.Explanation: TMSAUDEX has returned a table of all CPUs found in the Audit file plus those specified viathe CPULIST DD statement.User Response: None. Information only.PDC# QI53827

TMSXT05I ATTACH TMSBLDVR TO COPY/EXTEND TMC.Explanation: TMSBLDVR has been started to create a new TMC using the current TMC and the controlstatements from the SYSIN DD.User Response: None. Information only.TMSXT06I TMC DEFINITON TABLE OBTAINED.Explanation: TMSBLDVR has returned a table which maps all the VOLSER ranges in the new TMC.User Response: None. Information only.TMSXT07I WAIT FOR SUBTASKS.Explanation: TMSXTEND is waiting for TMSAUDEX and TMSBLDVR to complete processing.User Response: None. Information only.TMSXT09I SIGNAL ALL CPUS TO ACCESS NEW TMC.Explanation: TMSXTEND has signaled all CPUs in the shared TMC environment that they should attemptto access the control records of the new TMC and respond to TMSXTEND.User Response: None. Information only.TMSXT11I ENQUEUE TO LOCKOUT TMC ACTIVITY.Explanation: TMSXTEND has locked the TMC for updating.User Response: None. Information only.TMSXT12I DEQUEUE TO UNLOCK TMC ACTIVITY.Explanation: TMSXTEND has released the TMC so others can access it.User Response: None. Information only.TMSXT14E SOME CPU(S) DID NOT ACCESS NEW TMC.Explanation: Before using the Audit file data to synchronize the new TMC, a check was made that allCPUs had responded after accessing the new TMC. One or more CPUs have not responded.User Response: See either message TMSXT50I or TMSXT59E for details on which CPU failed to respondto the initial request.TMSXT15I CHECK FOR TMC UPDATES NEEDED.Explanation: The Audit file is checked for records added after TMSXTEND started or last checked. Thischeck is to determine if additional updates are required.User Response: None. Information only.TMSXT16I VERIFY ALL CPUS CAN ACCESS NEW TMC.Explanation: TMSXTEND is starting a check for non-responding CPUs.User Response: None. Information only.TMSXT17I BEGIN UPDATES TO SYNCHRONIZE TMCS.Explanation: TMSXTEND is starting the TMC synchronization process.User Response: None. Information only.PDC# QI53827

TMSXT18I NO MORE TMC UPDATES REQUIRED.Explanation: There were no additional Audit records to process for TMC synchronization.User Response: None. Information only.TMSXT19I END UPDATES TO SYNCHRONIZE TMCS.Explanation: The TMC synchronization is complete.User Response: None. Information only.TMSXT20I MAKE UPDATES TO SYNCHRONIZE TMCS.Explanation: TMSXTEND will start updating the new TMC with AUDIT records.User Response: None. Information only.TMSXT21I SIGNAL CPUS TO SWITCH TMCS.Explanation: TMSXTEND is updating the Audit file to signal all CPUs in the shared TMC environment toswitch to the new TMC.User Response: None. Information only.TMSXT23I PREPARE TO SWITCH ACTIVE TMCS.Explanation: TMSXTEND starting the routine to switch to new TMC. This involves several critical steps andprogress messages are written to the console.User Response: None. Information only.TMSXT25I OPEN/CLOSE TMC FOR OUTPUT TO PREVENT BATCH PROCESSING.Explanation: TMSXTEND will open the current TMC for OUTPUT. This will stop TMSXTEND if a batch jobhas the TMC open.User Response: None. Information only.TMSXT26I FINAL CHECK FOR UPDATES TO TMC.Explanation: TMSXTEND has the TMC locked. It will make a final check for updates made since thesynchronization routine completed. There should only be a few updates at most.User Response: None. Information only.TMSXT27I DISABLE OLD TMC FOR ADDITIONAL DATA.Explanation: TMSXTEND will modify CNTL#1 and CNTL#2 in the old TMC to prevent programs from usingit instead of the new TMC.User Response: None. Information only.TMSXT30I RENAMING TMCDSN TO TMCDSN.OExplanation: TMSXTEND will invoke CTSIDC to rename the current TMC to the old TMC. Thiswill prevent future access.User Response: None. Information only.TMSXT31I RENAMING TMCDSN.N TO TMCDSNExplanation: TMSXTEND will invoke CTSIDC to rename the new TMC to the original TMC name. It willthen be available to batch programs.PDC# QI53827

User Response: None. Information only.TMSXT33I ------ TEST MODE IS ACTIVE -----Explanation: TMSXTEND was started with PARM=TEST and has entered the TEST MODE. In TESTMODE TMSXTEND will simulate a TMC extend as closely as possible without renaming the current TMCor signaling all CPUs in the shared tape environment to switch TMCs. It will create a new TMC and signalall CPUs sharing the TMC to access the new TMC. It will attempt to continue, after most errors, instead ofterminating. The TEST MODE is designed to allow you to preview the TMC extend process.User Response: None. Information only.TMSXT40I RECOVER FUNCTION STARTING.Explanation: TMSXTEND is starting with PARM=RECOVER.User Response: None. Information only.TMSXT41I AUTO-RECOVER FUNCTION STARTING.Explanation: TMSXTEND is about to terminate in error and has started a recovery process to return theenvironment to a functional state.User Response: None. Information only.TMSXT43I RENAMING TMCDSN.O TO TMCDSNExplanation: TMSXTEND will invoke CTSIDC to rename the old TMC back to the current TMC name.User Response: None. Information only.TMSXT49I RECOVER FUNCTION COMPLETE.Explanation: TMSXTEND has completed a recovery process.User Response: None. Information only.TMSXT50I CPU(cccc) HAS NOT ACCESSED NEW TMC. RUN TMSRINIT ON THAT CPUExplanation: CPU(cccc) has not responded to TMSXTEND. It must respond before synchronization canbegin. TMSXTEND will wait approximately twenty minutes before terminating.User Response: Run TMSRINIT or a tape job on CPU(cccc).TMSXT51I TMSRINIT MUST BE RUN ON CPU(cccc) WITHIN XX MINUTES.Explanation: This is part of a ten minute count down for TMSRINIT to be started on CPU(cccc). IfCPU(cccc) does not respond before the end of the count down TMSXTEND will terminate.User Response: Run TMSRINT on CPU(cccc).TMSXT55I CPU(cccc) NEVER RESPONDED TO THE SIGNAL TO ACCESS NEW TMC.Explanation: This is a confirmation that EXCLUDEd CPU cccc did not respond to the signal to access thenew TMC.User Response: None. Information only.TMSXT56E CPU(cccc) BECAME ACTIVE DURING TMC SYNCRONIZATION.Explanation: This CPU was not in the CPU table returned by TMSAUDEX and can not be signaled toswitch TMCs.PDC# QI53827

User Response: Run TMSXTEND with PARM=RECOVER. Add an INCLUDE statement for this CPU andrerun TMSXTEND.TMSXT59E CPU(cccc) NEW TMC ACCESS FAILEDExplanation: This CPU was not able to access the new TMC.User Response: This CPU was unable to access the new TMC as requested by TMSXTEND. Verify thatthe new TMC is cataloged on this CPU and is a PSU format data set.TMSXT60E DATA SET NAME OF TMC LONGER THAN 42 CHARS.Explanation: Because TMSXTEND adds '.O' for the old TMC name and '.N' for the new TMC name, thecurrent TMC name can not be longer than 42 characters.User Response: You must change the current TMC name before a dynamic TMC extend can be run. Innon-shared catalog environments, the rename may be required on multiple systems. Check to insure thataccess to the new shorter TMC name is possible from all systems sharing the TMC.TMSXT61E VOL ERROR - vvvvvv rrrrrrExplanation: Error occurred during synchronization. TMSXTEND cannot update the new TMC for volservvvvvv at relative record number rrrrrr.User Response: Verify that the volser is defined in the new TMC and that TMSXTEND has updateaccess to the new TMC.TMSXT62E DSNB ERROR - nnnnnnExplanation: Error occurred during synchronization. TMSXTEND cannot update the new TMC for DSNBnumber nnnnnn.User Response: Verify that the DSNB number is defined in the new TMC and that TMSXTEND has updateaccess to the new TMC.TMSXT63E RECOVER AND TEST ARE MUTUALLY EXCLUSIVE.Explanation: RECOVER and TEST cannot be specified together.User Response: Change the PARM= to specify either RECOVER or TEST.TMSXT64E CPU(cccc) FROM AUDIT IS INVALID.Explanation: An Audit record was found for a CPU which was not specified in the CPUtable returned by TMSAUDEX. This CPU may not be aware of the new TMC.User Response: Add an INCLUDE statement for this CPU in the CPULIST.TMSXT65E INVALID BATCHID DURING SYNC.Explanation: While synchronizing the new TMC, TMSXTEND found an update in the AUDIT filewhich is not allowed while extending. This would indicate other maintenance was occurring.User Response: Run TMSXTEND with PARM=RECOVER, then wait until all batch and maintenance jobsare complete before running TMSXTEND.TMSXT66E TMC BACKUP IS NOT CURRENT(

TMSXT80E COULD NOT OBTAIN TMSVOLU TABLE.Explanation: TMSBLDVR did not return the TMSVOLU table to TMSXTEND. This table is required for TMCsynchronization.User Response: See messages and return codes from TMSBLDVR.TMSXT81E COULD NOT OBTAIN TABLE OF CPUS.Explanation: TMSAUDEX did not return the CPU table to TMSXTEND. This table is required to identify allCPUs sharing the TMC.User Response: See messages and return codes from TMSAUDEX.TMSXT82E TMC EXTEND ALREADY IN PROGRESS.Explanation: Status fields in the Audit file indicate that an extend job is currently running or has failed whileextending the TMC.User Response: If TMSXTEND is not currently running, run TMSXTEND with PARM=RECOVER. IfTMSXTEND is running, you must wait until the current extend job completes before running another one.TMSXT84E AUDIT DOES NOT CONTAIN EXTEND STATUS.Explanation: TMSXTEND was started with PARM=RECOVER but the Audit file does not indicate that anextend was started or failed. The TMC extend process may have failed either before or after a point wherea RECOVER is required. If changes to the TMC and Audit file have not been made or all changes arecomplete a recovery is not needed.User Response: Determine if the extend is complete or not started. If TMSXTEND failed before anychanges were made, see error messages and reason codes from the extend job. If TMSXTEND failed afterall changes were made, no further action is required.TMSXT96E ERROR(S) IN EXEC PARM=Explanation: Incorrect values specified for PARM=. Only DIAG and RECOVER or TEST are valid.RECOVER and TEST are mutually exclusive. If more than one parameter is specified, they should beenclosed in single quotes and separated by one or more spaces.User Response: Correct the PARM= values and re-run.TMSXT97E TMSXTEND TERMINATED WITH ERRORS.Explanation: TMSXTEND has terminated because of errors.User Response: See the Reason Codes documented under Abend U1022 and any preceding messages.TMSXT99I TMSXTEND COMPLETED SUCCESSFULLY.Explanation: TMSXTEND has completed. Note that it is possible for this message to be issued while someof the systems have still not switched over to use the new TMC. Messages TMSMR09I and TMSRI04I areissued when all systems have switched over to using the new TMC.User Response: Check for messages TMSMR09I and TMSRI04I to indicate a successful completion ofTMSXTEND.U1022Explanation: This abend is uniquely associated with TMSXTEND. The exact reason for the failure isdocumented in the reason code in register 15.PDC# QI53827

Hex dec. description01 1 TMC OPEN FAILEDTMSXTEND was unable to open the TMC for SVC access.05 5 SIGNAL ECB NOT ZEROTMSBLDVR did not post the signal ECB with a zero.This would indicate a problem and TMSXTEND is NOTto signal other CPUs to access the new TMC.06 6 TMSAUDEX NON-ZERO COMPLETIONSubtask did not end normally. See output from TMSAUDEX.07 7 TMSBLDVR NON-ZERO COMPLETIONSubtask did not end normally. See output from TMSBLDVR.1E 30 TMC ----> TMC.OThe rename failed. See msg TMSXT30I.1F 31 TMC.N ----> TMCThe rename failed. See msg TMSXT31I.2B 43 TMC.O ----> TMCThe rename failed. See msg TMSXT43I.33 51 CTSDIO ERROR ON NEW TMCSee msg TMSXT51I.38 56 BAD ACTIVITY FROM NON-RESP CPUSee msg TMSXT56E.3B 59 CPU(S) CAN NOT ACCESS NEW TMCSee messages TMSXT59E and/or TMSXT14E.3C 60 TMC DSN IS TOO LONGSee msg TMSXT60E.3D 61 VOLSER UPDATE ERRORSee msg TMSXT61E.3E 62 DSNB UPDATE ERRORSee msg TMSXT62E.3F 63 MUTUALLY EXCLUSIVE PARMS.See msg TMSXT63E.40 64 INVALID CPU DURING SYNCSee msg TMSXT64E.41 65 UPDATE WITH BAD BATCH-IDSee msg TMSXT65E.42 66 TMC BACKUP > 3HRS OLDSee msg TMSXT66E.PDC# QI53827

52 82 EXTEND ALREADY ACTIVESee msg TMSXT82E.54 84 NO EXTEND STATUS RECOVER NOT REQSee msg TMSXT84E.55 85 TMEXTEND FLAG RESET WHILE EXTEND PROCESSINGThe extend flag in the AUDIT file was set to zeroafter TMSXTEND started processing.TMSBLDVR - TMC Build Volume RangesThe TMSBLDVR program is invoked by TMSXTEND to read the TMC and create a volume range tablebased on the ranges it finds, then adding or deleting any volume ranges or DSNBs as requested based onthe control statements specified in the SYSIN DD. When executed in standalone mode, TMSBLDVR canbe used to identify the volume ranges in an existing TMC, validate volume range or DSNB controlstatements, and determine the size requirement of the new TMC.TMSBLDVR can also be used to define a new, empty TMC. TMSBLDVR is superior to TMSFORMT fordefining a new TMC because of its ability to format alphanumeric volume serial number ranges without theuse of the TMSUX2E and TMSUX2U user exits. Also, the only time the TMCNEW DD statement is used iswhen executed in standalone mode with the PARM=NEW parameter.Report DescriptionTMSBLDVR creates TMS REPORT-80 which displays the volume ranges found in the existing TMC andlists the volume ranges that will be built as a result of any add or remove range statements. Statistics arealso produced for the number of total and free DSNBs. In addition, if run in standalone mode without aPARM=NEW parameter, the report will include the size requirements for the new TMC based on ablocksize of either 340 or 8840. This will help insure that the new TMC is correctly preallocated.Job Control Statements//STEP01 EXEC PGM=TMSBLDVR,REGION=0M {,PARM=NEW}//TMSRPT80 DD SYSOUT=*//TMCNEW DD DSN=new.tmc.name,DISP=OLD,DCB=(BUFNO=60,BLKSIZE=n*340) * NOTE//SYSUDUMP DD SYSOUT=*//*//SYSIN DD *ADDVOL 500000-502999ADDVOL VT0000-VT2999 ROBTY=88,VENDOR=CA-VTAPEADDVOL 5000 -5099 /* adding a third range of 4-character volser */REMVOL TN0100-TN0599/*//*NOTE: This is an OPTIONAL DD statement; see PARM=NEW for details.Note: The BLKSIZE may be equal to the LRECL or any multiple of the LRECL. However, whenblocking the TMC the smallest valid block size is 1020. Also, when formatting a small blocked test TMC,ensure that it consists of at least2 blocks.PDC# QI53827

Parameter Definitions• NEWWhen this parameter is specified, a new TMC is formatted without copying volume ranges or DSNBrecords from an input TMC. The new TMC must be preallocated and cataloged. BrightStor CA-1 doesnot have to be active or batch active to run with PARM=NEW.JCL Considerations• SYSINThis DD defines the control statement input data set. When run in standalone mode, TMSBLDVR willvalidate that the function requested is proper for the requested range.• TMSRPT80This is the report output DD for TMS REPORT-80. This DD statement is required.• TMCNEWThis DD statement is required if PARM=NEW is specified. A newly allocated, empty TMC should bespecified. The TMC DCB attributes follow:DCB=(RECFM=FB,LRECL=340,BLKSIZE=n*340,DSORG=PSU,BUFNO=60)Completion Codes• RC=0 - Program completed successfully.• RC=4 - Program completed with minor errors. Review the TMSRPT80 report for details on errors.• RC=12 - Program failed due to an invalid control statement. Review the TMSRPT80 report for detailson control statement errors.Control Statement Specification• ADDDSNB nnnnnnnRequests that nnnnnnn additional free DSNB records be added to the new TMC.• ADDVOL lowvol-highvol DEN=nn ROBTY=nn TRTCH=nn VENDOR=cccccccc DELETESpecifies that the volume range lowvol-highvol be added to the new TMC. Optional parameters areprovided to initialize the volume records with a density (DEN), robot type (ROBTY) recording technique(TRTCH) and vendor (VENDOR). For the DEN, ROBTY and TRTCH parameters, nn should bereplaced with hexadecimal values as defined in the BrightStor CA-1 Systems Programmer Guide,Appendix A., TMC Volume Definition Keywords. The DELETE parameter simply indicates thevolume(s) are added in DELETE status in the new TMC. VENDOR is a 1-8 character string that is usedto identify the media manufacturer. In addition to a range, a single volser may also be specified on theADDVOL statement.• REMDSNB nnnnnnnRequests that nnnnnnn free DSNB records be removed from the new TMC.Note: REMDSNB is not valid with PARM=NEW and is mutually exclusive with the ADDDSNB controlstatement.• REMVOL lowvol-highvolSpecifies that all volumes in the range lowvol-highvol be removed from the TMC. All volumes in thisrange must be in DELETE status, otherwise the entire range is not removed.Note: REMVOL is not valid with PARM=NEW.PDC# QI53827

TMS REPORT-80 Report Field Definitions• External Volser RangeThis field shows the low and high volser numbers for a range found in the TMC.• TMC Rec NumberThis field shows the low and high relative record number of the volume serial numbers for each rangein the TMC.In addition, TMS REPORT-80 lists the TMC name being evaluated, the input control statements specifiedand the ranges that would be created for the new TMC. It also gives the number of DSNBs currentlyallocated, how many are currently unused, and how many can be removed. And finally, it givesthe space requirements of the TMC based on an unblocked TMC or a TMC allocated with a blocksize of8840 (this is only reported if TMSBLDVR is run in standalone mode).MessagesMessages produced by TMSBLDVR are in the format TMSVRnnI (for informational messages) andTMSVRnnE (for error messages) and are documented under the TMSXTEND utility.TMSAUDEX - TMC Audit ExtractorTMSAUDEX is a subprogram of the TMSXTEND utility that is called to build a table of systems sharing theTMC. The table is constructed by extracting records from the BrightStor CA-1 Audit data set and is thenused by TMSXTEND to manage the switch to a newly constructed TMC with new volume ranges orDSNBs. TMSAUDEX also checks to insure that all systems sharing the TMC are at the proper levelnecessary to permit a TMC extend function.TMSAUDEX is also being documented separately because it can be executed as a standalone utility toexamine the active Audit data set or prior generations of Audit data sets. The utility prints out the numberof audit records for each system sharing the TMC, and the start and end date/time of the audit records inthe file.Report DescriptionTMSAUDEX creates TMS REPORT-81, which displays all z/OS systems sharing the TMC as recorded inthe Audit file. The first and last dates of the audit records for each system are also displayed and anindicator showing that BrightStor CA-1 is at the necessary level to perform an extend function.Job Control Statements//STEP01 EXEC PGM=TMSAUDEX,REGION=0M{//AUDIT DD DISP=SHR,DSN=CAI.AUDIT.BACKUP}

JCL Considerations• AUDITDefines the BrightStor CA-1 Audit data set to be processed. You may also specify previous versions ofthe Audit data set on either disk or tape. If this DD statement is omitted, the active Audit data set willbe processed.Completion CodesTMSAUDEX adheres to the standard BrightStor CA-1 conventions for batch utilities, issuing user abendsfor problems common to most BrightStor CA-1 utilities.• RC=0 - TMSAUDEX completed successfully.• RC=8 - One or more systems sharing the TMC is not at the maintenance level required by theTMSXTEND utility.• U0001 - BrightStor CA-1 is not active or the Audit DD statement does not point to an Audit data set.• U0006 - Invalid data. This can be issued for invalid or incomplete control statements specified in theCPULIST DD as well as for invalid data found in the Audit file. In environments where the TMC isshared with BrightStor VM:Tape, a U0006 is generated if BrightStor VM:Tape does not have therequired level of maintenance applied. A blank CPU ID in the TMS REPORT-81 is indicative ofBrightStor VM:Tape being back level. With the required maintenance applied, BrightStor VM:Tape willdisplay a user-customizable CPU ID defined by BrightStor VM:Tape.Control StatementsThe control statements for TMSAUDEX are designed for use when the program is run as part of aTMSXTEND function. When run in standalone mode, TMSAUDEX will always attempt to report on allsystems found in the Audit file. If specified, the INCLUDE and EXCLUDE control statements are onlyverified for proper syntax.For a complete discussion on using the INCLUDE and EXCLUDE statements, refer to the ControlStatements section of this document associated with running the TMSXTEND utility.• EXCLUDE smf IDThis control statement defines the 4-byte SMF ID of systems running BrightStor CA-1 that should beexcluded from processing by TMSXTEND. EXCLUDE must begin in column 1 followed by a blank andthen the SMFID. Only one SMF ID may be specified per control statement. Note that failure to find asystem specified on an EXCLUDE statement is not considered an error. TMSAUDEX will continue toprocess and complete with a RC=0.• INCLUDE smf IDThis control statement defines the 4-byte SMF ID of a system running BrightStor CA-1 that should beincluded in the list of systems to process when performing an extend function. INCLUDE must begin incolumn 1 followed by a blank and then the SMF ID. Only one SMF ID may be specified per controlstatement.Note that this utility supports comment statements that begin with an asterisk (*) in column 1; however,they are not listed in any report. Comments may also be placed on the INCLUDE and EXCLUDEstatements after column 12.PDC# QI53827

TMS REPORT-81 Report Field Definitions• CPUThe SMF ID of the z/OS system creating audit records. SMF IDs for systems specified on an INCLUDEor EXCLUDE statement are also listed even if no audit records were found for the requested system.Users running BrightStor VM:Tape and sharing the TMC with that product may see a report line with ablank SMF ID. This is an indication of the BrightStor VM:Tape system not being at the necessarymaintenance level for sharing the TMC and is considered an error.• RECORD COUNTTotal number of audit records found for the system.• LO--DATE / TIMELowest date and time of any audit record found for the system.• HI--DATE / TIMEHighest date and time of any audit record found for the system.• FLGFlag indicating if the system is at the required level to run the TMC extend utility, TMSXTEND. Notethat all systems listed must be at the required level in order to run TMSXTEND. 'Y' or 'N' will be listedin this column, indicating whether or not the system is at the right maintenance level.• CTL STMTThis column will show INCLUDE or EXCLUDE if a control statement was specified for this system.• ERRORSThis column provides a description of any errors encountered in processing the Audit file.MessagesTMSAUDEX does not issue any console messages.TMSRINIT - TMC EXTEND MONITORThe BrightStor CA-1 SVC has been enhanced for the TMC Extend feature to detect when an extendfunction has been requested and to invoke the routines that will complete the switch to the new TMC.However, this is only done during the creation of secondary files. This is not done for a simple first-fileoutput request, or for any input tape request. So depending on the tape activity, it is very possible thatBrightStor CA-1 would not automatically detect the initial validation request from TMSXTEND. In thesecases, the TMSXTEND utility will issue a message requesting that program TMSRINIT be run on thatsystem(s). TMSRINIT provides functionality similar to the SVC, detecting that a switch has been requestedand it then invokes the routines to complete the switch.TMSRINIT may also be run with PARM='STATUS' to provide diagnostic information about the TMC Extendcontrol blocks.Report DescriptionTMSRINIT does not create any reports.PDC# QI53827

Job Control Statements//TMSRINIT EXEC PGM=TMSRINIT,REGION=0M,TIME=1440,// PARM=''//* PARM='STATUS '//* PARM='WAIT=00001500'//CAISNP DD SYSOUT=*//SYSUDUMP DD SYSOUT=*//Parameter Definition• PARM=''This is the default monitor mode. The BrightStor CA-1 Audit control record #4 is examined at 1 minuteintervals to determine if a TMC switch is in progress.• PARM='WAIT=HHMMSSTH'This parameter overrides the wait time between checks of the Audit control record to the valuespecified.• PARM='STATUS'Requests that the control blocks created by the TMSXTEND task be dumped in SNAP dumps.JCL Considerations• CAISNPDefines the output DD for snap dumps requested when PARM='STATUS' is specified.Completion Codes• RC=0 - Normal completion.Control StatementsThis program does not use any control statements.Report Field DefinitionsTMSRINIT does not produce any reports.MessagesMessages created by TMSRINIT are in the format TMSRInnI (Informational messages) and aredocumented under the TMSXTEND utility.IEFTMS72 ENHANCED TMC FORMATOTHER MESSAGES OR ABENDSExplanation: During TMSINIT processing, it was determined that the TMC is in the new Extended Format.User Response: None, this is informational only.PDC# QI53827

Eyy-112 I/O ERROR ON TMCExplanation: During a TMSXTEND operation, an attempt to perform an I/O operation to the new TMC atthe time the system was switching to the new TMC failed.User Response: Insure that the TMC is valid and all new ranges and/or DSNB records can be accessed.This can be done by simply using the ISPF interface or running a TMSBINQ report.ABEND=S000 U1001 REASON=00000020Explanation: After a TMSXTEND operation has completed, but BEFORE any tape activity has run or theTMSRINIT utility has finished, a BrightStor CA-1 batch utility has attempted to allocate the TMC.User Response: Simply allow TMSRINIT to finish, or run TMSINIT, or wait for some tape activity to occur.Any of these will cause the TMVT control blocks to be correctly updated.6yy-138 CTL#2 Not FoundExplanation: During TMSINIT processing, the second file in the TMC was not found to be TMSCTL#2.User Response: Insure that the TMC is valid and the job building it had been run successfully.6yy-140 TMDVOLDF Is Not Correct in TMSCTL#2Explanation: During TMSINIT processing, the TMDVOLDF field in the TMSCTL#2 control record did notpoint to a volume-definition record. The record found was a volume record.User Response: Insure that the TMC is valid and the job building it had been run successfully.6yy-142 TMDVOLDF or TMDVOLRC Are Not Correct in TMSCTL#2Explanation: During TMSINIT processing, the TMDVOLDF field in the TMSCTL#2 control record did notpoint to a volume-definition record. The record found was a DSNB record. Either the TMDVOLDF orTMDVOLRC fields are not correct.User Response: Insure that the TMC is valid and the job building it had been run successfully.BRIGHTSTOR CA-1 SYSTEMS PROGRAMMER GUIDE APPENDIX A. UPDATESThe BrightStor CA-1 Systems Programmer Guide Appendix A. should be updated to include new layouts ofthe TMC Control Records 2 and 4.UPDATED LAYOUT OF TMC CONTROL RECORD 2 (CTL#2)KEYWORD DATA LABEL OFFSET TYPE LENGTH DESCRIPTIONRECID TMSCTL#2 0(0) CHAR 8 Header #2 IDALLOCAT TMDSNB01 8(8) BIN 4 Number of DSNBs formattedUSED TMDSNB02 12(C) BIN 4 Number of DSNBs used totrack filesBASE TMDSNB03 16(10) HEX 4 Relative address 1st DSNBNXAVAIL TMDSNB04 20(14) HEX 4 Relative address next freeDSBNn/a TMDSNB05 24(18) 4 RESERVED1STVDEF TMDVOLDF 28(1C) HEX 4 Relative address 1st VolumeDefinition recordNUMVDEF TMDVOLRC 32(20) BIN 4 Number of Volume DefinitionRecordsPDC# QI53827

n/a 36(24) 304 RESERVEDTOTAL RECORD LENGTH: 340(154)TMMAUREC - A new Type 5 record (subtype 003) is now createdIn a TMSAUDIT report, the same report as documented in section 1.16.9 of the BrightStor CA-1 Utilitiesand Reports manual will now include the following extra list:TMS0YIN TVT TMS0XEP TF45130 12/10/03 17.50TMS0YEP TF45130 12/19/03 13.46UPDATED LAYOUT OF AUDIT CONTROL RECORD 4 (CTL#4)KEYWORD DATA LABEL OFFSET TYPE LENGTH DESCRIPTIONRECID TMSCTL#4 0(0) CHAR 8 Header #4 IDGENERAT TMAUDIT1 8(8) BIN 4 Number of Audit recordsgeneratedn/a 12(C) 4 RESERVEDNXAVAIL TMAUDIT3 16(10) HEX 4 Next available recordBACKUP TMBACKUP 20(14) HEX 20 Copy of TMDSNB01-TMDSNB05BKDATE TMBKDATE 40(28) PACK 4 Date of last TMC backupn/a 44(2C) 1 RESERVEDBKTIME TMBKTIME 45(2D) PACK 4 Time of last TMC backupBKVOL TMBKVOL 48(30) CHAR 6 Volser or backup tapeBKDSN TMBKDSN 54(36) CHAR 44 DSN of last backup tapeBACIND TMBINDC 98(62) HEX 1 Backup indicator!TMBKUP HEX x'80' Backup in progress orpreviously abendedAUDFLG TMAUDFLG 99(63) HEX 1 TMSXTEND Audit FlagTMEXTEND HEX 1 x'80' TMSXTEND processingactiveTMNEWNAM HEX x'40' TMC.N renamed to TMCTMOLDNAM HEX x'20' TMC renamed to TMC.O1STAUDI TMAUDIT4 100(64) BIN 4 1st Audit record since last backupNXLABEL TMAUDIT5 104(68) BIN 4 Next label to print (used byTMSLBLPR)NXSEND TMAUDIT6 108(6C) BIN 4 CA-1 Communication taskCA-Dynam/T pointerTMCPUS 112(70) HEX 0 Start of Entries for 32 CPUsCPUI01 TMCPUI01 112(70) CHAR 4 SMF ID for CPU1CPUF01 TMCPUF01 116(74) HEX 1 Status flag for CPU1TMCPU_HELLO!x'80' Initial helloTMCPU_RESPx'40' Initial response receivedTMCPU_SWTCH!x'20' Switch to new TMCcommandTMCPU_DONETMCPU_FAILx'10' Switch has completedx'08' Switch to, or initial testof the new TMC failed.Note - the above flags are usedforall CPU status flags belowCPUI02 TMCPUI02 117(75) CHAR 4 SMF ID for CPU2CPUF02 TMCPUF02 121(79) HEX 1 Status flag for CPU2PDC# QI53827

(29 CPU entries in same format not displayed)CPUI32 TMCPUI32 267(10B) CHAR 4 SMF ID for CPU32CPUF32 TMCPUF32 271(10F) HEX 1 Status flag for CPU32CATVSN TMCATVSN 332(14C) CHAR 6 Disk volser of new TMCTOTAL RECORD LENGTH: 370(172)Note - Fields AUDFLG, CPUInn, CPUFnn and CATVSN are only non-zero during an actual execution ofTMSXTEND.BRIGHTSTOR CA-1 SYSTEMS PROGRAMMER GUIDE APPENDIX C. UPDATESThe BrightStor CA-1 Systems Programmer Guide Appendix C documents the structure of the TMC andAudit file. The TMSXTEND utility will create a new record type in the TMC, the Volume Definition record.Appendix C will be updated to reflect the following changes to the TMC.1. Two TMC formats will be supported by BrightStor CA-1, a new Extended Format TMC, which has beencreated by TMSXTEND, and the original TMC format.2. A TMC that has been processed by the TMSXTEND utility will include a Volume Definition Record(s)before the DSNB records. The Volume Definition Record is created from an unused subtype of DSNBrecords, identified by a X'FF20' in the first and second bytes of the record. Active DSNB records areidentified by X'FF80' in the first and second bytes of a record (170 bytes long.) The Volume Definitionrecord is 340 bytes long but is designed to include a X'FF20' ID 170 bytes into the record, which allowsprograms reading through the DSNB ranges expecting 170 byte records to process the VolumeDefinition records without modification. Note that a user-written program processing DSNBs mustcheck the second byte of the record for a X'80' for active DSNBs or x'00' for inactive DSNBs, otherwiseit will incorrectly process Volume Definition Records as DSNBs.3. The volume ranges previously defined in Control Record 1 and Control Record 3 have been moved tothe new Volume Definition records if the TMSXTEND utility was used and are cleared in ControlRecord 1 and Control Record 3.4. The requirement that customers must install user exits TMSUX2U and TMSUX2E for alphanumericvolsers is removed for customers running with the Extended Format TMC.5. Control Record 2 is updated to include an offset to the first Volume Definition record. Control Record 2also includes a count of the Volume Definition records.6. The structure of the Audit file and its relationship to the TMC is unchanged.Thank you for your continued support of Computer Associates and its products. If you have any questionsabout this Product Documentation Change or any other questions about BrightStor CA-1, please contactyour local Computer Associates Technical Support organization for BrightStor CA-1.PDC# QI53827