Does CA Hyper-Buf handle VSAM RLS(Record Lever Sharing)? If yes, how does it work?
CA Hyper-Buf and using RLS.
Record Level Sharing (RLS) is application based and managed at the application level. The application performs all the READ/WRITE functions.
What does CA Hyper-Buf actually do?
CA Hyper-Buf will intercept VSAM OPEN, interrogate the data at open and make decisions on BUFFER management to be used during the processing. You can look at this as a dynamic buffer adjustment for the files to be opened. The most efficient buffer and region sizes will be set based upon the Constraint Table settings provided by the user. The all control goes back to IDCAMS.
RLS processing to CA Hyper-Buf is nothing more than a VSAM OPEN. Once control is given back to IDCAMS CA Hyper-Buf is no longer involved. CA Hyper-Buf will NOT perform any data writes or reads.
During CA Hyper-Buf re-buffering on one System, a CICS region on another System could encounter an abend, if special algorithms for tuning CICS buffer space are not set. By coding one rule for any CICS partition, you can tune CICS to select optimum buffer space for online processing.
CA Hyper-Buf handles CICS processing but you should make some decisions when you setup the Constraint Table.
See the following in the User Guide chapter 3
CICS: Restricting Buffering for the CICS Environment
NSR: Restricting Conversion to Local Shared Resources
In recommending CA Hyperbuf usage CA stresses the proper use of NSR/LSR processing and setting up the Constraint Table for your files that will be managed by Hbuf.