How can we exclude jobs or started tasks from CA Hyper-Buf control intercepts?
To keep CA Hyper-Buf from making performance changes for a the job via Constraint Table decision type of work you can add the following update to the Constraint Table and then refresh the Constraint Table dynamically. Using the Constraint update will still have Hyper-Buf interrogating the files at OPEN but deciding to exclude the job.
JOB=jobname to be excluded
add the following DD to the first step of application JCL:
//CAHBEXCL DD DUMMY
Using the DD will keep GVBDYNBF (the CA Hyper-Buf intercept) from being loaded and performing interrogations. No Constraint Table reviews will be made once the DD statement is discovered.
To exclude a started task:
In the Constraint Table use the following:
This specification forces CA Hyper-Buf to exclude Buffering for all Started tasks and TSO sessions, analyzing and applying Constraint Table parameter entries only to batch jobs.
Please review the CA Hyper-Buf® VSAM Buffer Optimizer User Guide for release 11.5; chapter 3 for in-depth information.