BrightStor CA-1 Tape Management - SupportConnect

BrightStor CA-1® Tape ManagementProduct Information PacketRelease 5.2Service Pack 4AL052SP04P2

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 5.2, August 2003(c) 2003 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.

This Product Information Packet contains important information about BrightStor CA-1 Tape Management.Included you will find:* The Product Maintenance/Cover Letter* Any applicable Product Error Alerts* Any applicable Product Documentation Changes* Any applicable high-impact APARsYou should review these documents prior to installing or applying maintenance to BrightStor CA-1.The Product Maintenance/Cover Letter (PML) provides information regarding prerequisites and installationconsiderations. The Product Error Alerts (PEAs) provide information about potential error situations. TheProduct Documentation Changes (PDCs) provide additional product documentation that has not yet beenincorporated into the documentation set. PDCs can also provide information that is not considered part of aproduct's documentation set, such as a change in Level 1 support hours. The APARS describe solutionsdetermined since the product tape was produced. Generally, you should apply any APARS included, asthese represent solutions to problems judged to be critical to a majority of product users.If you have any questions concerning the enclosed material, please contact your Computer AssociatesTechnical Support organization for BrightStor CA-1. Refer to your Computer Associates Product SupportDirectory for the appropriate telephone number to call for direct support.Product Information Packet Contents:Product Maintenance/Cover LetterQI22149 - BrightStor CA-1 Tape Management Release 5.2 Service Pack 4Product Error AlertsLI77194 - Increase Space Allocation for cai.CTS.C$F12LLDQI21034 – Missing EOV input intercept after IBM PTF UW88884, UW88885, or UW88886QI42919 – Missing CA-1 Contact During Label ConflictProduct Documentation ChangesLI89532 - Changes to External Data Manager InterfaceQI08686 – New Data Erase UtilityQI12531 - CA-1 APAR QO12485QI15005 – ISPF 3.4 Tape Inquiry (TI) DisplayQI15007 - Enhancement - New SMP/E Usermods for OAM exitsAPARsNone.

COMPUTER ASSOCIATES INTERNATIONAL, INC.5465 Legacy Drive Plano, TX 75024-3106Telephone (214) 473-1000 FAX (214) 473-1050To:From:BrightStor CA-1 Tape Management ClientsThe Computer Associates BrightStor CA-1 Product GroupDate: August 5, 2002Subject: BrightStor CA-1 Tape Management Release 5.2 Service Pack 4PML#: QI22149Dear Clients:Computer Associates International, Inc. is pleased to present you with Service Pack 4 for BrightStor CA-1Tape Management Release 5.2, an integral component of the Storage solutions we provide for the z/OS andOS/390 operating systems.Prerequisites:- Any supported release of the z/OS or OS/390 operating system- Unicenter TNG Framework for OS/390 Release 2.2 Service Pack 1 or higher- CA-Activator at Release 2.2 Service Pack 1 or higher (if CA-Activator is used to install)Getting 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 Installation andMaintenance Guide, Systems Programmer Guide and (if used) CA-Activator 2.1 Supplement.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 5.2 Service Pack 4 tape is L00204. Please be sure to usethis VOLSER in any JCL that will access this tape.BrightStor CA-1 EnhancementsWith Service Pack 4 the following enhancements were incorporated in BrightStor CA-1 Release 5.2:CTSDEU - new Data Erase UtilityNew ISPF 3.4 Tape Inquiry Display

Blocked TMC SupportUpdated versions and SMP/E installation of CBRUXENT and CBRUXEJC; and new CBRUXVNL exitWith Service Pack 3 the following enhancements were incorporated in BrightStor CA-1 Release 5.2: Support for OS/390 2.10 External Data Manager (EDM) enhancements Updated verions of CBRUXENT and CBRUXEJC to enhance support of IBM 3494/VTSWith Service Pack 2 the following enhancements were incorporated in BrightStor CA-1 Release 5.2:Full support for CA-1 Agent (with CA-1 5.2 PTF LO72832 and CTS PTF LO72767).Enhanced support for the IBM 3590 extended length cartridges, including 128-track and 256-trackrecording techniques.Full support for IBM 3494/VTS Import and Export functions.With Service Pack 1 the following enhancements were incorporated in BrightStor CA-1 Release 5.2:Enhanced Sample Exits For IBM Robotic Tape LibrarySample CA-EARL Program to produce totals for individual tapesWith prior maintenance the following enhancement was incorporated in BrightStor CA-1 Release 5.2:Realtime Tape StackingInstallation ConsiderationsDue to the nature of the product changes, a system IPL is required for this service pack.If an SMP/E APPLY of this service pack is done into your production CAILIB, an immediate IPL is required.If an IEBCOPY is used to copy the SMP/E target libraries into the production libraries, an immediate IPL willbe required after the IEBCOPYs have finished. The recommended method would be to copy the SMP/Etarget libraries into the production libraries on an alternate volume, and then IPL to activate this service packmaintenance. Sharing the TMC between systems of various maintenance levels of Release 5.2 does notcause any problems.Please refer to the BrightStor CA-1 for OS/390 5.2 Installation and Maintenance Guide for specific UnicenterTNG Framework for OS/390 component requirements.The OS catalog intercept feature, introduced with the base level (9609) of release 5.2, requires that SMF beactive in order to function properly. However, SMF records need not be written.***************************** Note ***********************************This BrightStor CA-1 Service Pack is the last to support BrightStor CA-1 installation or application ofmaintenance using CA-Activator. If you are installing BrightStor CA-1 for the first time, or are re-installing theproduct to obtain the latest maintenance, we recommend that you use the standard SMP/E install instead ofusing CA-Activator.************************************************************************1. CA-Activator ConsiderationsIf you choose to install BrightStor CA-1 with CA-Activator, you will need to make sure that theCSI you are installing into is large enough. With just BrightStor CA-1 libraries, you will need at

least 66 tracks allocated to the SMPCSI.CSI.DATA and at least 10 tracks allocated to theSMPCSI.CSI.INDEX. These data sets get defined in the CA-Activator PY00BE job. If this jobhas already been run in your CA-Activator environment, then you will need to reallocate theSMP CSI and REPRO into the larger data sets.A new CA-Activator install of BrightStor CA-1 in a z/OS 1.3 environment does not allow theNUCID parm on the SMP initialization step. In the JCL created from PY00DE, remove theNUCID entry.Maintenance Considerations1. New Format for Product MaintenanceTo simplify future maintenance upgrades and support current SMP requirements, all future maintenancewill be packaged as a single cumulative PTF per SYSMOD. This differs from previous maintenance,which contained one PTF for each SMP element. While the format is different, the new maintenance willstill allow you to upgrade to the most current Genlevel/Service Pack from any previous genlevel.The new packaging is in response to changes introduced by IBM SMP/E PTFs UR52887, UR53295,and UR53296, which change the requirements for superseding SYSMODS.Before applying any service pack, it is critical that you review the instructions for every maintenancelevel that you will be applying, beginning with the earliest. To review the information for previousgenlevels, please refer to "Previous Maintenance Levels" in this Product Maintenance Letter.With this new maintenance procedure, there will no longer be any SMP/E elements placed in ++HOLDstatus. Any replaced elements that have previously been tailored, must be retailored after themaintenance has been applied. To preserve a copy of your current environment and ensure that nocustomization is lost, we recommend that you backup your target libraries prior to applying anymaintenance.2. CA-Activator ConsiderationsClients who used CA-Activator to do a base install of BrightStor CA-1 from the Service Pack 1 (L09910)tape must comment out, from CA-Activator tasks L052MC and L052MH, the following entries thatreference 9910:/* LB52926 /* CG81200 9910 *//* LA50115 /* C$F1200 9910 *//* LA51022 /* C$F1200 9910 *//* LA53823 /* C$F1200 9910 *//* LA54392 /* C$F1200 9910 *//* LA55004 /* C$F1200 9910 *//* LA57493 /* C$F1200 9910 *//* LA57738 /* C$F1200 9910 *//* LB57493 /* C$F1200 9910 *//* LC57493 /* C$F1200 9910 */To install this Service Pack, your SMPCSI will probably not be large enough. Reallocate theSMPCSI.CSI.DATA to at least 66 tracks and the SMPCSI.CSI.INDEX to at least 10 tracks. Next, reprothe old SMPCSI into the new one, using the IDCAMS utility.

3. Non CA-Activator ConsiderationsThe Receive/Apply/Accept of this Service Pack tape will point to a single cumulative PTF perSYSMOD. You no longer need to modify the SAMPJCL members these jobs point to.To install this Service Pack, your SMPCSI will probably not be large enough. Reallocate theSMPCSI.CSI.DATA to at least 66 tracks and the SMPCSI.CSI.INDEX to at least 10 tracks.Next, repro the old SMPCSI into the new one, using the IDCAMS utility.After you unload the L052MA job from the CAI.SAMPJCL library on the maintenance tape,please update the SELECT statements for the IEBCOPY steps, deleting the levels that havealready been applied.If you remove all of the SELECT member statements for a COPY, be sure to remove theassociated COPY control statement.Do not run the L052ML or $F12ML tasks during application of Service Pack 4. These are usedto update the PROCs for CA-1 and have not changed with this maintenance.Add the following DD statement to your BrightStor CA-1 SMP/E proc L052SMPE under the"Define CA-1 Target Libraries" section://CAICLIB DD DSN =CAI.CAICLIB,DISP=SHRPrevious Maintenance LevelsThis section contains previous maintenance level high APARs and their accompanying Productmaintenance Letter (PML) numbers, which are included in file CAI.PTFREF.Maint Level High APAR PMLService Pack 3 LO94801 LI98525(0104)Service Pack 2 LO72832 LI77196(0004)Service Pack 1 LO55742 LI68945(9910)DocumentationThis 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 providedin the JCL members.The Adobe PDF files will be downloaded with the following naming conventions:c0152oa7.pdfBrightStor CA-1 Tape Management Administrator and Operator Guide

c0152og7.pdfBrightStor CA-1 Tape Management General Information Guidec0152oi7.pdfBrightStor CA-1 Tape Management Installation and Maintenance Guidec0152om7.pdfBrightStor CA-1 Tape Management Message Guidec0152or7.pdfBrightStor CA-1 Tape Management Release Guidec0152os7.pdfBrightStor CA-1 Tape Management Systems Programmer Guidec0152ou7.pdfBrightStor CA-1 Tape Management Utilities and Reports Reference Guidec0152ox7.pdfBrightStor CA-1 Tape Management CA-ACTIVATOR 2.1 Supplement GuideLicense ManagementBrightStor CA-1 is maintained by the CA License Management Program (LMP). Information about LMP canbe found in the Unicenter TNG Framework for OS/390 Administrator Guide, Chapter 7 "ResourceInitialization Manager". Go tohttp://support.cai.com/tng390supp.htmlto access the Unicenter TNG Framework for OS/390 manuals.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.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 software solution,please contact your Computer Associates technical support organization for BrightStor CA-1.

BrightStor CA-1 Product Error AlertDATE: June 27, 2000RELEASE: 5.2GENLEVEL: AllENVIRONMENT: MVSHYPER: YesSUBJECT: Increase Space Allocation for cai.CTS.C$F12LLDDESCRIPTION/DISCUSSION: This Product Error Alert applies only to those CA-1 clients who have installedCA-1 Release 5.2 from a prior maintenance level.It is necessary to increase the number of directory blocks and the space allocation for the Common TapeSystem (CTS) distribution library, cai.CTS.C$F12LLD.RESOLUTION:Clients who have the CTS component already installed must perform the following procedure to avoidSMP/E ACCEPT problems.1. Rename your existing CTS distribution library to cai.CTS.C$F12LLD.OLD.2. Using the JCL below, allocate a new CTS distribution library.//L052PIB JOB (ACCOUNT),'CTS ALLOCATE'//**-------------------------------------------------------------------*//** *//**THIS JOB ALLOCATES THE CTS DISTRIBUTION LIBRARY. *//** *//**-------------------------------------------------------------------*//ALOCLIB EXEC PGM=IEFBR14//C$F12LLD DD DSN=cai.CTS.C$F12LLD,// DISP=(NEW,CATLG,DELETE),// UNIT=SYSDA,// SPACE=(6144,(300,50,35)),// DCB=(DSORG=PO,RECFM=U,BLKSIZE=6144),// VOL=SER=VOLSER3. Copy your renamed cai.CTS.C$F12LLD.OLD into your new cai.CTS.C$F12LLD using IEBCOPY.//COPY EXEC PGM=IEBCOPY//SYSPRINT DD SYSOUT=*//SYSUT1 DD DSN=cai.CTS.C$F12LLD.OLD,DISP=OLD//SYSUT2 DD DSN=cai.CTS.C$F12LLD,DISP=OLD//SYSUT3 DD DSN=&&WRK1,UNIT=SYSDA,SPACE=(TRK,(5,1))PEA#: LI77194

SYSUT4 DD DSN=&&WRK2,UNIT=SYSDA,SPACE=(TRK,(5,1))//SYSUDUMP DD SYSOUT=*//SYSIN DD *COPY OUTDD=SYSUT2,INDD=((SYSUT1,R))Thank you for your continued support of Computer Associates and its products. If you have any questionsabout this Product Error Alert or any other questions about CA-1, please contact your local ComputerAssociates Technical Support organization for CA-1.PEA#: LI77194

BrightStor CA-1 Product Error AlertDATE: July 19, 2002RELEASE: 5.2GENLEVEL: Service Pack 4 (SP04)ENVIRONMENT: MVSHYPER: YesSUBJECT: Missing EOV input intercept after IBM PTF UW88884, UW88885 or UW88886DESCRIPTION/DISCUSSION: This Product Error Alert only applies to clients who have appliedmaintenance to DFSMS that included IBM PTF UW88884, UW88885, or UW88886 (associated with IBMAPAR OW54001).With IBM PTF UW88884 (DFSMS 1.5), UW88885 (DFSMS 1.6), or UW88886 (z/OS DFSMS 1.3) applied,the execution order of IFG0553F and IFG0553H has been reversed, which impacts CA-1's EOV processing.A multi-volume data set may become partially unchained. When a data set spans three or more volumesand the program reading the tape reads at least into the second volume but not to end-of-file, all volumesnot read will be unchained.In addition, CA-1 will not record the LAST USE information for multi-volume EOV INPUT requests.This error/condition is described in StarTrak.Product: 1 Problem: 1434IMPACT: Secondary volumes prematurely unchained will become available for scratch processing, whichmay result in data loss.CIRCUMVENTION/PROPER HANDLING: Clients can circumvent this situation by changing the CA-1option RECRE8 to KEEP in TMOOPT00 in the CA-1 PPOPTION library, and then restarting TMSINIT toactivate this option.To assist in identifying this situation, clients should execute CA-1 utility TMSOSCAT with a LISTCATNONVSAM ALL and review the output for any discrepancies with the errors identified as:******* NO CATALOG ENTRY FOUND ********* ERROR05.To correct volumes that have not been reused, clients should execute TMSUPDTE with the appropriate1STVOL/NEXTVOL/PREVVOL statements to re-chain those volumes that were unchained, or use the CA-1ISPF/TIQ facilities to accommodate this.RESOLUTION:A CA-1 test APAR is available upon request by contacting CA-1 Technical Support.Thank you for your continued support of Computer Associates and its products. If you have any questionsabout this Product Error Alert or any other questions about CA-1, please contact your local ComputerAssociates Technical Support organization for CA-1.PEA#: QI21034

CA-1 Product Error AlertDATE: March 20, 2003RELEASE: 5.2ENVIRONMENT: MVSHYPER: NoSUBJECT: Missing CA-1 Control During Label ConflictThis Product Error Alert applies to all clients who have installed CA-1 Service Pack 4 (level 0204) or any ofthe following APARs: QO02598, QO12696, QO13854, QO15202 or QO22829.With any of the above maintenance applied, a previous APAR, LO35709, was partially dropped by mistake.In rare situations, this may prevent CA-1 from controlling dynamic label destruction and/or recreation.The error is described in StarTrakProduct: 1 Problem: 1469The problem can only occur when multiple data sets are opened in parallel by a single SVC call, and one ofthem is a tape data set opened for output, which requires dynamic label, density or TRTCH change. Parallelopen processing is used by COBOL II programs in particular.If a tape data set going through parallel open encounters a label conflict and requires label destructionand/or recreation, CA-1 may not control the request and may not verify the status of the tape or theappropriate LCHG, DCHG and/or TCHG system options. Label change may be allowed even if the tape isnot in scratch status, or if the specific action is generally disallowed by the respective CA-1 option.If this rare situation occurs, CA-1 does not reply to any version of the IEC704A WTOR, likenn IEC704A REPLY 'VOLSER,OWNER INFORMATION','M' OR 'U',to approve the label change request or to supply additional volser or owner information. The reply needs tobe handled manually.Also, in the usual case of a CA-1 controlled label conflict, the IECTMSx messages issued by CA-1 mayerroneously show a suffix of 'E' (EOV) rather than 'O' (Open), even if the data set does not go throughend-of-volume.Affected messages are:IECTMS1E dddd,,ENTER VSNIECTMS2E dddd,vvvvvv,VERIFY TAPE FROM OUTSIDE LIBRARYIECTMS3E dddd,vvvvvv IS NOT SCRTCH(cde)IECTMS6E dddd.vvvvvv IS APPROVED FOR LABEL/DENSITY/TRTCH CHANGEThe wrong message suffixes do not have any impact on tape processing. If any of the messages are issued,CA-1 controls the label change and fully protects the tape being relabelled.PEA#: QI42919

IMPACT:Tapes may be re-labelled inadvertently, which may result in data loss. Outstanding IEC704A WTORs maybe encountered. This can happen only in the rare case of multiple DCBs being opened in parallel with one ofthem causing a label conflict.CIRCUMVENTION/PROPER HANDLING:No circumvention is available to prevent CA-1 from losing control during label conflicts.Replies to outstanding IEC704A WTORs should be given with care, and in accordance with site specifictape processing standards. If valid scratch mounts cannot be guaranteed, or if label change is disallowed viaCA-1 option, replies should not be handled by an auto-operator product.PROBLEM RESOLUTION:CA-1 APAR QO39908 is available to resolve this situation.CA-1 APAR QO39908 also resolves the following problems:Possible swapout of a tape job with outstanding enqueue on the TMCVOL=SER=poolid not working with UNIT=AFF on same DD statementWrong subpool assigned at EOV after TMSUX2A bypassBlank volser used after invalid blank reply to IECTMS1Problem with re-use of checkpoint-restart tapes under SMS controlThank you for your continued support of Computer Associates and its products. If you have any questionsabout this Product Error Alert or any other questions about this product, please contact your localComputer Associates Technical Support organization.PEA#: QI42919

CA-1 Product Documentation ChangeDATE: March 7, 2001RELEASE: 5.2ENVIRONMENT: MVSHYPER: NoSUBJECT: Changes to External Data Manager InterfaceDESCRIPTION/DISCUSSION: CA-1 APAR LO87299, which will be included in Service Pack 3, introduceschanges to the External Data Manager (EDM) interface. After upgrade of CA-1 5.2 to Service Pack 3, thefollowing changes apply to the External Data Manager interface and may require a modification of existingEDM definitions.RESOLUTION: The functionality of the EDM interface was enhanced to prevent one EDM from expiringanother EDM's tapes in case the EDM databases are not synchronized correctly with the TMC. The EDMrules defined in PPOPTION member TMOEDMxx are now verified not only during tape creation, but alsowhen tapes are released from EDM control.Module TMSTMSTV, before expiring an EDM volume and turning the TMETMS flag on (FLAG2 bit x'01' -"deleted by CA-1, CA-11 or EDM"), now retrieves the EDM definitions to verify that the releasing EDMactually owns the volume being released.TMSTMSTV determines the EDMID of the releasing EDM using the following parameters:JOB - Job name of the executing job which releases the volumePGM - Program name of the executing programDD - Dummy ddname TMSEDMSCDSN - Data set name from the TMC volume record (no DSN is passed from the EDM)The obtained EDMID is compared to the one in the TMC record. Only if they are equal is the volume allowedto be expired. This means that job name and program name can be used to identify the releasing EDMand to prevent an EDM volume from being expired by a different EDM by mistake.Clients will need to ensure that their existing EDM definitions are still valid in this context and allow for acorrect, unique EDMID assignment. Changes will be required if:1. the JOB or PGM parameter is used and the creating job/program is different from the releasingjob/programor2. the DD parameter is usedPDC#: LI89532

Samples:1. If an EDM uses program prog1 to create tapes and prog2 to release them, the previous EDM rulemay have looked like:EDM=edmx,DSN=abc.-,PGM=prog1In future, the following two rules will be required to provide the same functionality:EDM=edmx,DSN=abc.-,PGM=prog1EDM=edmx,DSN=abc.-,PGM=prog22. If an EDM rule previously contained a DD parameter, specifying a creation ddname, likeEDM=edmy,DSN=def.-,DD=cddnameanother similar rule with the fix ddname TMSEDMSC will be required to allow volumes to bereleased properly:EDM=edmy,DSN=def.-,DD=cddnameEDM=edmy,DSN=def.-,DD=TMSEDMSCThe following new messages were introduced:TMSTMSTV-00 vvvvvv EXPIRE COMPLETE - EDMID=xxxxExplanation: Notification that a volume has been processed by CA-1 for expiration by the requestingExternal Data Manager shown in the message.User Response: None, informational.TMSTMSTV-1C vvvvvv EXPIRE IGNORED, EDM PMA ERRORExplanation: An EDM option did not pass a pattern masking acceptance check.User Response: Ensure that EDM control statements are coded according to the rules defined for theTMOEDMxx member.TMSTMSTV-20 vvvvvv EXPIRE IGNORED, EDM MISMATCHExplanation: An EDM has attempted to expire a volume that is owned by a different EDM, according tothe EDM definitions in member TMOEDMxx.User Response: 1) Ensure that the EDM control statements allow for assignment of a unique EDMIDduring tape creation and release. 2) Ensure that the databases of both EDMs are synchronized with thecorrect volume serial numbers.PDC#: LI89532

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#: LI89532

BrightStor CA-1 Product Documentation ChangeDATE: January 2, 2002RELEASE: 5.2ENVIRONMENT: MVSHYPER: YesSUBJECT: New Data Erase Utility***NOTE*** This PIB supersedes QI06958 which has been withdrawnDESCRIPTION/DISCUSSION:A new Data Erase Utility has been added to CA-1 via maintenance PTF QO06872 for the Common TapeSystem (CTS) component. Following is documentation related to this new feature.PROBLEM RESOLUTION:CTSDEU - Data Erase UtilityThe CTSDEU utility can be used to erase residual data left on a tape following one or more valid files. Thisis done to prevent unauthorized access to potentially sensitive data, which may be left on the end of a tapefrom previous use. Normally this is done before the tape leaves a secured area. When a multivolume dataset is being processed, the last volume of the set needs security erase processing. If all volumes of a dataset are to be processed, the parameter ALL can be used to request every volume in the multivolume dataset be processed. This parameter should be used if the program creating the tape issues a FORCE-END-OF-VOLUME before the tape is full.Job Control Statements//stepname EXEC PGM=CTSDEU,PARM='parm'//STEPLIB DD DSN=CAI.CAILIB,DISP=SHR//SYSPRINT DD SYSOUT=*//SYSUT1 DD UNIT=(TAPE,,DEFER),DISP=(OLD,KEEP),// LABEL=(,SL), see NOTE 1// VOL=SER=anyvol, see NOTE 2// DSN=any.tape.fileNOTE 1: LABEL=(,BLP) is needed to erase scratch tapes.NOTE 2: The JCL parameter VOL=SER= is required if the requested DSN is not in the MVS catalog.Parameter DefinitionMore than one parameter may be specified.The parameters specified are processed in the order shown, not in the order of their appearance in theEXEC statement.PDC QI08686

ERASEReads the tape header label and verifies that the tape is in the CA-1 Tape Management Catalog (TMC) isnot a virtual tape, and that the data set names match those records in the TMC. If the volume serial numberwas not supplied by VOLLABI (the VOLSER from the VOL1 record on SL or AL tapes) or the TMSXTPPRuser exit, the console operator is asked to supply the volume serial number.NOERASEReads the tape header label and verifies that the tape matches the TMC, but no residual data is erased.Because the erase is not performed console operator intervention is suppressed.Note: If the NOERASE parameter is used on a scratch tape the specified scratch tape is taken out of scratchstatus.The default is: ERASEALLIndicates that all volumes of the requested tape file should be secured. Normally when sets of tapes areproduced, they are filled completely, overlaying any old data, but if force end of volume (FEOV) macro isused to produce short tapes, data previously written may not be overlaid.LASTIndicates that only the last volume of the requested tape file will be secured. All volumes of the requested fileare read but only the last volume is secured.The default is: LASTLISTA detail list of the contents of the requested volumes is produced.NOLISTA detail list is not produced.The default is: NOLISTMessagesCA$F003EOPEN UNSUCCESSFUL ON FILE - xxxxxxxxExplanation: An OPEN was unsuccessful for the file listed in the message.User Response: If this message is accompanied by message CA$F004E, refer to that message foradditional information; otherwise, ensure that the file's DD statement is coded properly in the JCL and restartthe job that issued this message (CTS or CTSDEU).CA$F004ETAPEDB ERROR OCCURRED - FN=xxxx,RC=xxxx,RS=xxxx,FB=xxxxExplanation: An error occurred processing the TMC. The function code (FN), return code (RC), reason code(RS) and feedback (FB) are described in the message. See "I/O Module Codes" in topic 1.2.1.User Response: Correct and restart the job that issued this message (CTS or CTSDEU).IEBTMS2 TAPE EXCP CCW WAS REJECTEDExplanation: The CCW (CCW 97) to erase the tape was rejected.PDC#: QI08686

User Response: This normally occurs only when changes to the operating system have occurred. CTSDEUand TMSTPPRO use the CCW 97 for tape erasure processing.IEBTMS2 TAPE IS OUT OF RANGEExplanation: The volume serial number requested was not found to be part of the TMC's valid ranges.User Response: The volume is demounted. The volume serial number in question is not in the TMC or is ininactive (DELETE) status.IEBTMS2 TAPE MOUNTED IS NOT FIRST OF SETExplanation: The volume serial number mounted is not the first volume of a multivolume set.User Response: The volume is demountedIEBTMS2 TAPE DATABASE AND TAPE HDR DSN ARE NOT EQUALExplanation: This message is issued when the tape label data set name is compared to the last 17 positionsin the TMC data set name, and they are not equal. If the tape contains multiple data sets all tape label dataset names will be compared.User Response: Verify the correct volume was mounted.IEBTMS2 TAPE COULD NOT BE PROCESSEDExplanation: The tape read was not successful.User Response: Determine the cause of failure by dumping or direct examination of the tape. Possiblecauses are incorrect density, incorrect recording (7-track versus 9-track) or a damaged tape. Correct andresubmit the job.IEBTMS2 ddd,......,ENTER VSNExplanation: This message is issued with the ERASE option. The volume serial number is unknown andmust be supplied to CTSDEU or TMSTPPRO.User Response: Enter the required volume serial number.IEBTMS2 VOLUME IS A VIRTUAL TAPEExplanation: Virtual tapes cannot be erased by CTSDEU.User Response: The virtual volume will be demounted and CTSDEU will end.Thank you for your continued support of Computer Associates and its products. If you have any questionsabout this Product Information Bulletin or any other questions about this product, please contact your localComputer Associates Technical Support organization.PDC#: QI08686

BrightStor CA-1 Product Documentation ChangeDATE: February 26, 2002RELEASE: 5.2GENLEVEL: Service Pack 4ENVIRONMENT: MVSHYPER: NoSUBJECT: CA-1 APAR QO12485PROBLEM DESCRIPTION: BrightStor CA-1 Tape Management APAR QO12485This Product Documentation Change provides information regarding the enhancements and product errorresolutions provided by CA-1 APAR QO12485, including installation requirements and considerations.PROBLEM RESOLUTION:The APAR includes the following enhancements and error resolutions:- Support for blocking of the Tape Management Catalog- Consolidation of TMC and Audit I/O processing- Correction of DSNB left/right indicator in Audit exception records- Correction of various errors in utilities TMSGRW and TMSFORMTThe APAR includes and supersedes the following unpublished test fixes:- TE9C089 - Detect invalid DSNB DELETE request- TE9C119 - Prevent possible S0C4 in CTSPM when processing NSM rules- TFFC063 - Add support for 8 byte USERID field- TE4D110 - TMSGRW: Correct verification of DSNB flag bits- TFFC046 - TMSGRW: Correct print of ACTVOL field- TFFC047 - TMSGRW: Add new TRTCH values to translation table- TFFC109 - TMSGRW: Module replacement including all previous changes- TFFC096 - TMSFORMT: Improve control statement parsing- TFFC110 - TMSFORMT: Allow FORMAT/EXTEND of range 000000-000000Installation requirements:Due to the nature of the product changes, a system IPL is required for this upgrade, regardless of whetherthe TMC is actually blocked or not. SMP HOLD information was added to the APAR to point out the IPLrequirement. To apply the APAR, the following parameter must be added to the SMP APPLY statement:BYPASS(HOLDSYS(DOC))An SMP APPLY of this APAR into your production CAILIB requires an immediate IPL. While some of theupdated modules are fetched from steplib or linklist or loaded by the CAS9 procedure, module TMSTMVTcannot be refreshed dynamically. Therefore an IPL is mandatory. The TMC and Audit I/O routines will not beoperational when the APAR has been activated only partially.PDC#: QI12531

Sharing an unblocked TMC between systems of different maintenance levels, which do not all have thisAPAR installed, does not cause any problems.Blocking the TMC:Once all systems sharing the TMC and Audit files have been IPL'ed with this enhancement active, CA-1 canbe started with a blocked TMC. Blocking the TMC may be a consideration to save disk space. Apart fromsome reporting tools which use QSAM access, it will not significantly improve access performance of theTMC for tape processing or CA-1 utilities.When the TMC is blocked, the block size may be any multiple of the record length, 340, except 680. Thesmallest valid block size is 1020. Also, when a very small TMC is created for test purposes, it must consistof at least 2 blocks. CA-1 cannot process the data set if all records are contained in one block. Arecommended block size value is BLKSIZE=8840.While utilities TMSFORMT, TMSREMOV and TMSCOPY have been enhanced to allow for a blocked formatwhen creating a new TMC, a format or restore operation is not necessary to block an existing TMC. Simplyuse IEBGENER to copy the data set and specify the desired BLKSIZE in the SYSUT2 DD statement.There are no known compatibility problems with this change and any MVS product accessing the TMC. AllCA or OEM products or user programs which use CA-1 macros to read or update the TMC will work fine witha blocked TMC and not require any changes. If your TMC is shared with a non-MVS system, please contacttechnical support of the respective product for further information.Installation checklist:The following procedure should be used to upgrade one system at a time. The upgrade includes a systemIPL. If the TMC data set is shared among multiple CPUs, it can continue to be accessed normally from allother systems during the upgrade.Perform the following tasks to correctly apply this APAR:1. Back up your current CA-1 target environment.2. Apply the APAR to your target CAILIB.Ensure that updated modules are not accidentally invoked through LLA refresh or CAS9 REINIT etc.while CA-1 is active.3. Stop tape processing on the target system.4. If necessary, copy your maintenance target library into the production target library.Ensure that the linklist and all affected procedures (CAS9, CTS, TMSINIT, CA-1 batch utilities)exclusively point to the updated library.5. IPL your system.6. Run CAS9 and start TMSINIT as usual.PDC#: QI12531

7. Run any IVP jobs to test tape processing and batch/online TMC inquiry. TMSCKLVL can be used toverify the maintenance level of the active SVC module TMS00SVC. All csects updated by theenhancement should show eyecatcher PFFC044, unless remodified by subsequent maintenance.TMSCKLVL also displays the level of the TMSTMVT module which was loaded by CAS9 after the lastIPL. LEVEL = TVT5200 indicates the old level, LEVEL = TVT5201 indicates the PFFC044 level ofTMSTMVT is active.8. If all results are OK, resume tape processing.If a backout of the maintenance should be required, restore the APAR from your target library andrepeat steps 3 through 7 accordingly.Once all systems sharing the TMC have been upgraded and are running at the new level withoutproblems, the TMC can be reblocked if desired.*** The following steps are required to reblock the TMC: ***9. Run TMSCKLVL on all systems to verify that the active TMSTMVT and TMS00SVC modules show thecorrect maintenance level.10. Stop tape processing on all systems sharing the TMC.11. If subtask DBS is active in the CTS address space, issue the following CTS command to unallocate theTMC:MSG DBS,'RELEASE TMC'12. Back up the TMC using TMSCOPY.13. Allocate a new TMC data set on a shared device which is accessible from all systems. SpecifyDSORG=PSU in the DCB parameter, unless the volume is SMS controlled. Provide the desired blocksize:DCB=(DSORG=PSU,RECFM=FB,LRECL=340,BLKSIZE=n*340)14. Execute IEBGENER to copy the production TMC into the blocked TMC.15. Rename the production TMC to an alternate name, and catalog the blocked TMC under the productionname on all CPUs.16. Run TMSINIT to restart CA-1 on all systems.17. Run any IVP jobs to test tape processing and batch/online TMC inquiry. Ensure all systems are pointingto the same TMC data set and can access it properly. If any problems occur, rename the blocked TMCto an alternate name, and catalog the original TMC under the production name on all systems. Go backto step 16 to re-activate the original, unblocked TMC.18. If all results are OK, resume tape processing.19. If the DBS subtask is active in the CTS address space, issue the following command to re-allocate theTMC:MSG DBS,'OBTAIN TMC'If you need to backout the change, perform the same steps 10 through 19 accordingly to unblock your TMC.PDC#: QI12531

Documentation updates related to this APAR:Updates to the CA-1 5.2 Systems Programmer Guide:1.4.1 Tape Management CatalogIn the case titled 'Organization:', replaceDCB=(DSORG=PSU,RECFM=FB,LRECL=340,BLKSIZE=340)with:DCB=(DSORG=PSU,RECFM=FB,LRECL=340,BLKSIZE=n*340)Note: The BLKSIZE may be any multiple of the LRECL, 340,but not 680. When blocking the TMC, the smallest validblock size is 1020.Also, when formatting a small blocked test TMC, ensurethat it consists of at least 2 blocks.A recommended value is BLKSIZE=8840.3.4.3 Moving the TMCIn step 5, remove the sentenceDO NOT REBLOCK THE TMC.Updates to the CA-1 5.2 Utilities and Reports Reference Guide:1.29.2.1 TMSFORMT Job Control StatementsIn the JCL box, replace statement//TMC DD DSN=CAI.CA1.TMC,DISP=OLD,DCB=(BUFNO=60)with://TMC DD DSN=CAI.CA1.TMC,DISP=OLD,DCB=(BUFNO=60,BLKSIZE=n*340) *NOTEBelow the box, add:Note: The BLKSIZE may be any multiple of the LRECL, 340,but not 680. When blocking the TMC, the smallest validblock size is 1020.Also, when formatting a small blocked test TMC, ensurethat it consists of at least 2 blocks.A recommended value is BLKSIZE=8840.1.29.7 TMSFORMT - Extending the TMCIn step 4, replaceDCB=(RECFM=FB,LRECL=340,BLKSIZE=340,DSORG=PSU,BUFNO=60)PDC#: QI12531

with:DCB=(RECFM=FB,LRECL=340,BLKSIZE=n*340,DSORG=PSU,BUFNO=60)Note: The BLKSIZE may be any multiple of the LRECL, 340,but not 680. When blocking the TMC, the smallest validblock size is 1020.Also, when formatting a small blocked test TMC, ensurethat it consists of at least 2 blocks.A recommended value is BLKSIZE=8840.1.29.9.1 TMSFORMT Report Field DefinitionsBehindNUMBER OF TMC RECORDS WRITTEN.Number of volume records writtenadd the following:NUMBER OF TMC RECORDS PER BLOCK.Number of TMC records in a block1.39.2 TMSREMOV ProcedureIn step 3, changeto:DCB=(RECFM=FB,LRECL=340,BLKSIZE=340,DSORG=PSU)DCB=(RECFM=FB,LRECL=340,BLKSIZE=n*340,DSORG=PSU)Note: The BLKSIZE may be any multiple of the LRECL, 340,but not 680. When blocking the TMC, the smallest validblock size is 1020.Also, when formatting a small blocked test TMC, ensurethat it consists of at least 2 blocks.A recommended value is BLKSIZE=8840.Updates to the CA-1 5.2 Message Guide:2.23 TMSFORMT MessagesRemove the following message including Explanation andUser Response:VERSION 3 RESTORE RECORD NOT IN A VALID RANGE.PDC# QI12531

Add the following message instead:INVALID BLKSIZE DEFINED FOR TMC DATA SET.Explanation: The TMC to be formatted is allocated withBLKSIZE=680, which is not allowed.When blocking the TMC, the smallest valid block size is 1020.User Response: Allocate the TMC with correct DCB attributesand resubmit the job.3.2.11 Eyy-rc I/O ERROR ON TMCFor all four codes, 104, 108, 116 and 120, modify the Reason and Action portions as follows:Reason:Remove the 2nd sentence:The physical record read was not 340 bytes in length.Action:Replace the phraseDCB=(RECFM=FB,LRECL=340,BLKSIZE=340,DSORG=PSU)with the following:DCB=(RECFM=FB,LRECL=340,BLKSIZE=n*340,DSORG=PSU)Add the following new code at the end of the section:124 The TMC was allocated If the TMC data set iswith BLKSIZE=680, which blocked, the smallest validis invalid. block size is 1020.Updates to the CA-1 5.2 Installation and Maintenance Guide and to the CA-1 5.2 ActivatorSupplement GuideIn the Installation and Maintenance Guide,4.17 Step 16 Allocate TMC and Audit Data Sets (L052IU),as well as in the CA-Activator 2.1 Supplement Guide,4.15 Task L052IU: Allocate TMC and Audit Data Sets,perform the following changes:Change the paragraph after the caution boxThe BLKSIZE for the Tape Management Catalog (TMC) must be 340.The BLKSIZE for the Audit data set must a multiple of 370.If a block size is not specified for the Audit data set, TMSFORMTwill use a block size of 8880.For information on space requirements for the TMC and Audit datasets, refer to the CA-1 Systems Programmer Guide.PDC#: QI12531

as follows:The BLKSIZE for the Tape Management Catalog (TMC) must be 340 or a multiple of 340 greater or equal1020. 680 is not a valid BLKSIZE. The BLKSIZE for the Audit data set must a multiple of 370.Recommended values are BLKSIZE=8840 for the TMC and BLKSIZE=8880 for the Audit.For information on space requirements for the TMC and Audit datasets, refer to the CA-1 Systems Programmer Guide.In the following TMC storage formulaFormula: TMC storage = (3 + V + (D / 2)) / RCNote: When you round the value, be sure to round up.V equals number of Volume recordsD equals number of DSNB recordsRC equals records per cylinder for device typechange the RC definition toRC equals records per cylinder for device type and blocking factorIn the note at the bottom, change sentenceThis means that the total number of volume records plus half of thetotal number of DSNB records (there are two DSNB records on eachphysical record) must be equal to or less than 3,735,492.as follows:This means that the total number of volume records plus half of thetotal number of DSNB records (there are two DSNB records on eachphysical record) of an unblocked TMC must be equal to or less than3,735,492.Thank you for your continued support of Computer Associates and its products. If you have anyquestions about this Product Information Bulletin or any other questions about this product, pleasecontact your local Computer Associates Technical Support organization.PDC#: QI12531

BrightStor CA-1 Product Documentation ChangeDATE: April 2, 2002RELEASE: 5.2ENVIRONMENT: MVSHYPER: NoSUBJECT: ISPF 3.4 Tape Inquiry (TI) DisplayDESCRIPTION/DISCUSSION:This Product Documentation Change (PDC) describes a new feature of CA-1: the ISPF 3.4 Tape Inquiry (TI)display. Two APARs are required to use this feature: Common Tape System (CTS) APAR QO14967 andCA-1 APAR QO14969.PROBLEM RESOLUTION:CA-1 currently offers a full ISPF application for accessing tape information in the CA-1 Tape ManagementCatalog (TMC), however many clients use the ISPF 3.4 "DSLIST" display extensively. This feature providesyou the ability to quickly access CA-1 TMC information from the DSLIST panel. This can be done for anycataloged tape files by issuing the "TI" (Tape Inquiry) command in the detail line command field. A new,easy to read display will return essential information from the CA-1 TMC organized into groups of relatedinformation.In addition, a new field called Media Type has been added that combines the TRTCH and DEN fields to tellwhat type of media the data set is cataloged on, or VIRTUAL if in a VTS.For the data set requested, the display provides the starting volume serial number and up to six secondaryvolumes. If more than six secondary volumes are used, five secondary volumes and the text (more) will bedisplayed. Note that a new field "percent utilized" is provided in the display. This field will remain blank untila future APAR provides additional logic to capture the information necessary to calculate this value.New display field (user data) has been added. This is a user controlled area. Only character format isdisplayable. If user data contains decimal or packed data, or hex, user data line will appear but non-printablecharacters will appear as blank.An example of the TI display follows:PDC#: QI15005

Data Set Name . . . : TEST.TESTMOD.PDS1General DataCreation InformationVolume Serial. . . : 202583 Date . . . . . . : 2001/10/03Alternate Volume . : A202583 Time . . . . . . : 01:00:00Media type . . . : 3480-18TK Jobname . . . . : IEBDGRecord Format. . . : F Program . . . . : CTSTAPERRecord Length. . . : 24 Last Used InformationBlock Size . . . : 24 Date . . . . . . : 2001/10/04Number of blocks . : 4 Time . . . . . . : 00:03:00Per Cent utilized. :Jobname . . . . : CATMGBatch ID/Hook ID . : Expiration InformationStatus . . . . . : ACTIVE Expire Date. . . : 2004/01/01File / Volume SetVault Management InformationBase Volume. . . . : 102583 Outcode. . . . . : XA11Sequence Number. . : 1 Slot . . . . . : 0012345Total Files in Set : 1 Outdate. . . . . : 2001/10/05Secondary volumes: 102584 102585 102586 102587 102588 (MORE)User Data: 8439190 -4444 TEST BOXINSTALLATIONThis feature is the first CA-1 feature to install elements into a new CLIST library. The standard CLIST libraryfor used CA products is CAI.CAICLIB. Prior to APPLY'ing the APARs for this functionality you must updateyour SMP/E procedure to include a DD statement for CAICLIB as below://CAICLIB DD DSN=CAI.CAICLIB,DISP=SHRThe name of the SMP/E procedure to update is L052SMPE. Replace 'CAI.' high level identifier with thespecific user high level qualifier used at your installation. If you do not have a CAI.CAICLIB data setallocated, you should allocate this data set as a Partitioned Data Set (PDS) with an LRECL of 80 andBLOCKSIZE of 3120 (or some multiple of 80.) Some customization of the TI CLIST may be necessary.After installing APARs QO14967 and QO14969 with SMP/E, the executable load module, ISPF panels,messages and the CLIST member 'TI' will be installed into the CA-1 target libraries. Check to make sure thetarget libraries are accessible on the systems you want to have access to this command.If you fail to update the SMP/E procedure L052SMPE, the following error messages will result for SYSMODQO14969:GIM54502E ** ALLOCATION FAILED FOR CAICLIB BECAUSE THERE IS NO DD STATEMENT IN THEJCL AND NO DDDEF ENTRY IN TARGET ZONE CAITGT.GIM28307E ** ALLOCATION FAILED FOR CAICLIB, WHICH IS REQUIRED IN ORDER TO PROCESSELEMENT TI IN SYSMOD QO14969.Thank you for your continued support of Computer Associates and its products. If you have any questionsabout this Product Information Bulletin or any other questions about this product, please contact your localComputer Associates Technical Support organization.PDC#: QI15005

CA-1 Product Documentation ChangeDATE: April 2, 2002RELEASE: 5.2ENVIRONMENT: MVSHYPER: NoSUBJECT: Enhancement - New SMP/E Usermods for OAM exitsDESCRIPTION/DISCUSSION: With CTS PTF QO14941, some new usermods have been created toassemble and link the three OAM exits; CBRUXENT (entry), CBRUXEJC (eject), and CBRUXVNL (volumenot in library). Also, these three exits have been moved to the SMP maintained CAISRC library. In CAISRC,they are called CTSUXENT, CTSUXEJC, and CTSUXVNL. One new usermod (CL05244) will be used toapply any customization you may wantto apply to the supplied samples. Once CL05244 is applied and theCTSUXnnn exits have been reassembled and linked into CAILIB, you may then apply the second usermod(SMPEOAM) in your DFSMS SMP/E zone. This will then relink and rename them from CTSUXnnn toCBRUXnnn in SYS1.LINKLIB.If you have made modifications to the sample CBRUXnnn exits that were previously supplied in theSAMPJCL library; you will have to reapply those modifications to the new CL05244 usermod. Thosemodifications will be in IEBUPDTE form and applied by CL05244. This way, your modifications will not belost even if changes are made to the sample provided.If you have copies of the CBRUXnnn exits already assembled and linked into the CAILIB, they can bedeleted after these usermods have been applied. Since these usermods will relink the exits intoSYS1.LINKLIB, you will not have to delete the IBM supplied default versions.Following is documentation related to this new usermod.PROBLEM RESOLUTION:New CL05244 UsermodA new usermod called CL05244 has been added to the PPOPTION library. This new usermod will apply anyclient-specific modifications to the sample exits supplied with CA-1. It is strongly recommended that theATLTABLE in the CTSUXENT exit be modified to include the library name(s) of your SMS-managedlibraries. Also, if the IMPORT/EXPORT feature is used it is strongly recommended that the 3 commentedoutlines in CTSUXEJC be un-commented out and a pseudo data set name be placed in the WCDSN field.Once any changes to the CTSUXnnn exits have been made in the CL05244 usermod, you should receiveand apply it using the standard receive and apply members L052JEE (receive) and L052JFE (apply) foundin the SAMPJCL library.New SMPEOAM UsermodA new usermod called SMPEOAM has been added to the SAMPJCL library. This new usermod will relinkand rename the three exits from the CAILIB library into SYS1.LINKLIB. This will replace any versions of theexits that may already exist in SYS1.LINKLIB that interface to other tape management systems. Thisusermod should be applied in your DFSMS SMP/E zone, so that if any IBM maintenance causes theirdefault versions to be re-installed; you will simply restore and then reapply the SMPEOAM usermod after theIBM maintenance has been applied.PDC#: QI15007

New CBRUXVNLAlso new with this usermod is CBRUXVNL, the volume not-in-library exit. This exit will get control for EVERYtape mount not satisfied inside an SMS-managed robotic device, and for any non-tape (dasd) device that isnot currently online. The version that is supplied will do no processing by default. If you want to haveWTORs issued (asking the operator to re-insert a cartridge into the 3494 for example for non-vaulted 3590cartridges); then you will need to modify the CL05244 usermod (un-comment out some compares andbranches and comment-out some others). Once the CL05244 usermod to the CTSUXnnn exits have beenapplied, simply re-apply the SMPEOAM usermod to install the new version in SYS1.LINKLIB and refresh theexit to OAM.Thank you for your continued support of Computer Associates and its products. If you have any questionsabout this Product Information Bulletin or any other questions about this product, please contact your localComputer Associates Technical Support organization.PDC#: QI15007