Should I use SYSB-II with all of my jobs?
Each company's business objectives differ. You can use SYSB-II to reduce your batch window or eliminate it altogether. Your business objectives may be met by using SYSB-II with only a few applications, batch jobs, or both.
SYSB-II can be one part of the total equation for reducing batch window. Other tools you might consider include:
- Backup while open: In lieu of running the backup steps before and after each batch update step, use this technique to back up your VSAM files (see IBM for tools like Snapshot and Enterprise Storage Server Flash Copy).
- Batch LSR: For high-volume, long-running batch update steps, try using Batch LSR to shorten your batch cycle. This tool might take enough time off your window to meet your business needs. Other examples of Batch LSR include SmartBatch and HiperBatch, which are not supported by CICS. SYSB-II has features that also speed up batch processing.
- Sequential striping: If the batch job has several hundred thousand updates, each being independent of the other, you could split the update file by simply using your own program or perhaps DFSORT and feed smaller sets of updates to the same batch program in several different batch job streams. A DFSORT job could use the OUTFIL control statement to identify the different output files together with the INCLUDE and SAVE parameters to control how records are distributed between the output data sets. This is a very effective technique if you have a long running batch update step. Using SYSB-II with sequential striping accomplishes both your need to keep CICS VSAM files fully available and to shorten your batch processing cycle.