Mike, Our company uses SYSB almost exactly as John McKown described how it is used at his company. We have one production CICS region and we see its CPU utilization percentage rise when multiple jobs using SYSB are running.
As Systems Programmers, we have to be mindful of how our Applications Programmers have coded their procs when they use SYSB. There are parameters available so that SYSB will not lock records in CICS if they haven't been updated, or can perform the VSAM reads in the batch job and only send the VSAM updates to CICS. We work with the programmers to incorporate these parms when they seem beneficial. H&W has been good about reviewing output from batch jobs and suggesting ways to improve utilization, which has helped us immensely. Regards, Greg Shirey Ben E. Keith Company -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Ward, Mike S Sent: Thursday, February 06, 2014 2:53 PM To: [email protected] I know this is loading a gun :), but do any of you have any opinion on the SYSB-II product? Is detrimental to CICS? Is it a memory hog? Is it a CPU hog? And for those of you who use it. How does it perform in a zSystem environment? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
