Program GVBISIT detects CA Hyper-Buf if it is active on your system. You can use GVBISIT to verify that CA Hyper-Buf is active for jobs that require CA Hyper-Buf, and that it is inactive for any jobs that you want to run when CA Hyper-Buf is down.
GVBISIT does not require any input or output files. The only output is the return code passed back to OS/390 in R15. If CA Hyper-Buf is inactive when GVBISIT runs, the return code in R15 is set to zero. If CA Hyper-Buf is active, R15 is set to eight.
For example, you may decide to remove all of the old release CA Hyper-Buf modules before you install a new version. This is only safe to do if CA Hyper-Buf is not active, since OPEN processing when CA Hyper-Buf is active LOADs some of these modules, and removing them while CA Hyper-Buf is active can cause your SYS1.DUMP data sets to fill up (your jobs still run, but each OPEN triggers another dump).
In this case, you can insert GVBISIT at the beginning of the clean-up job and use the return code to 'skip' the delete step if CA Hyper-Buf is active.
If you have a job that runs too long without CA Hyper-Buf active, you can use the same return code to skip the step if CA Hyper-Buf is not active and issue the appropriate messages. This way, you can make sure that the job runs only if CA Hyper-Buf is active.
Sample JCL member GVBISIT is provided in the CBS3JCL library.
|
Copyright © 2011 CA.
All rights reserved.
|
|