BrightStor CA-1 Tape Management - SupportConnect

BrightStor CA-1 Tape Management - SupportConnect BrightStor CA-1 Tape Management - SupportConnect

supportconnectw.ca.com
from supportconnectw.ca.com More from this publisher
11.07.2015 Views

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.

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 <strong>CA</strong>-Activator PY00BE job. If this jobhas already been run in your <strong>CA</strong>-Activator environment, then you will need to reallocate theSMP CSI and REPRO into the larger data sets.A new <strong>CA</strong>-Activator install of <strong>BrightStor</strong> <strong>CA</strong>-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. <strong>CA</strong>-Activator ConsiderationsClients who used <strong>CA</strong>-Activator to do a base install of <strong>BrightStor</strong> <strong>CA</strong>-1 from the Service Pack 1 (L09910)tape must comment out, from <strong>CA</strong>-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 ID<strong>CA</strong>MS utility.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!