The enhancement includes support for the RECOVER function for HPR and the CHACCUM function for the Change Accumulation component and can be installed through LU00468 and LU00469.
Original Message:
Sent: 01-25-2021 05:04 AM
From: Rabah Beggar
Subject: Secondary index Builder vs 8Gb Databases
Hello @JEAN CLAUDE LEMONNIER and @Lesley Rowe
The CA IMS Tools team is happy to announce that SIB support for 8 GB OSAM HALDBs has been completed (PTF SO14973) and that as of last week CA Database Copier™ for IMS for z/OS has been enhanced to support 8 GB OSAM data sets in HALDBs as well through SO16207, SO16208, for the following functions:
Regards,
Rabah
Product Owner,
rabah.beggar@broadcom.com
------------------------------
Broadcom
Original Message:
Sent: 07-27-2020 01:53 AM
From: Jakub Hofman
Subject: Secondary index Builder vs 8Gb Databases
Hi Lesley,
thank you for taking time to contribute this thread. Currently, our tools support the 8 GB OSAM HALDB in Database Analyzer -https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-mainframe-software/database-management/ca-database-management-solutions-for-ims-for-z-os/20/release-notes/enhancements.html for:
ANALYZE and ANALYZEALL (allows you to check database integrity and related indexes);
DISPLAY and ZAP (allows you to display and update blocks in the Database Surgeon component).
Support in DBO is in development now and SIB is in the development backlog.
May I suggest to get in touch, my email is jakub.hofman@broadcom.com
Regards,
Jakub Hofman
Original Message:
Sent: 07-24-2020 12:49 PM
From: Lesley Rowe
Subject: Secondary index Builder vs 8Gb Databases
RE: IMS HALDB Utilities vs 8GB Databases
We, at DXC Technology / United Airlines account have had this need for CA IMS DB Utilities to support the HALDB OSAM 8GB
for several years. Our largest HALDB database, now at 128 partitions, keeps growing. Instead of growing at the 97 parts we once had,
we have to keep splitting the current parts in order to grow within the HALDB OSAM 4GB limit as the CA IMS utilites ( Copier, Organizer, SIU )
do not support the 8GB OSAM dataset IMS HALDB has had available.
We have had to keep going thru the split process, introducing some minor risk by adding the next part# to DBRC as well as adding to the IMS objects and job schedules/parms.
We very much champion that Broadcom IMS related tools should be updated to support HALDB OSAM 8GB !!
All the best,
Lesley Rowe
Sr. Database Administrator
DXC Technology
lesley.rowe@dxc.com
------------------------------
DBA-IMS and DB2
DXC Technology
Original Message:
Sent: 07-10-2020 11:25 AM
From: JEAN CLAUDE LEMONNIER
Subject: Secondary index Builder vs 8Gb Databases
Secondary index Builder : 8GB HALDB OSAM support.
We do need this urgently for the following reasons :
We have huge IMS databases used in after sales activity (The most beneficial one in automotive industry) which must be extended to 8 Gb.
If SIU do no support this option, we'll have the choice between 2 equally inacceptable solutions :
- Keep the size as it is (4 Gb) and reorganize the databases every 2 weeks), which generates service outages and is utterly inacceptable for the business.
- Extend their size to 8 Gb and do not reorganize them any more because SIU won't be able to handle such databases.
For the time being we have chosen the first option, but our business won't accept this situation much longer, especially when the corresponding IBM product supports this facility.
We have other IMS databases which are growing significantly, which means we'll need this facility on a larger scale. The big data also exists on mainframe, in DB2 and IMS databases.
One last thing : This 8 Gb support existed since IMS V14. The current IMS version is 15.2. All the Broadcom IMS-related tools should have been updated accordingly several years ago.
Best regards
------------------------------
JC.LEMONNIER
RENAULT SAS
FRANCE
------------------------------