If the JCL specifies AMP=(?BUFND=??, BUFNI=???) how will CA Hyper-Buf product behave in case the constraints table has AMPOVR=FORCE?

Document ID : KB000046223
Last Modified Date : 14/02/2018
Show Technical Document Details


If the JCL specifies AMP=(‘BUFND=??, BUFNI=??’) how will CA Hyper-Buf perform the buffering in case the constraints table has AMPOVR=FORCE? 


Any application that uses AMP= in their JCL should be reviewed closely and tested to be sure Hyper-Buf will not alter the buffers to a size that the application cannot utilize. This could cause abends.

With AMPOVR=FORCE then Hyper-Buf will decide what happens regardless of the JCL values. 

With AMPOVR=GREATER then CA Hyper-Buf will review the AMP= statement and then based on that information, the Constraint Table information, and buffering recommendations internal to CA Hyper-Buf, the "greater" buffer the value will be used.

With AMPOVR=NO CA Hyper-Buf will do nothing and follow the AMP= values with no changes.


AMPOVR=NO if you have a lot of JCL with AMP= statements 
AMPOVR=GREATER if you do not have much in the way of AMP= specified in JCL. These applications may require special attention or exclusion from Hyper-Buf.