Our Technology: SYSB-II
SYSB-II features improve CICS data availability and extend mainframe life.
SYSB-II is mainframe computer software that allows you to run batch processing anytime during the business day without the need to take CICS down or close files to CICS. Applications remain fully available and users get current batch data on demand.
The SYSB-II software allows mainframe CICS applications to stay online and update VSAM files while batch also updates the same VSAM files. This means companies can ensure current service hours, extend business hours, or expand to more time zones.
SYSB-II provides these essential features:
Increase data and application availability
- Batch can run anytime during the day to minimize the batch file time delay.
- Batch runs without affecting terminal response time.
- CICS applications remain available during batch processing.
- Syncpointing minimizes the time that records are unavailable to other CICS applications.
- Users get current data on demand because batch can update VSAM files throughout the day.
- SYSB-II is a lean system tool that allows a batch job to run like a CICS transaction.
Extend the life of your mainframe
- Leverage your existing investment in mainframe software applications and hardware.
- Use current resources and implement rapidly.
- Employ an alternative to DB2 migration.
- Use existing staff skills without extensive retraining.
- Eliminate the need to make application source-code changes.
Easily implement and integrate
- Architecture takes advantage of long-established CICS concepts.
- SYSB-II can be implemented one job, one job step or one file at a time.
- SYSB-II uses existing data and security standards.
- SYSB-II can be installed in a few hours.
- SYSB-II integrates into existing processes: There is no migration to other file structures, and current support tools are used.
- Companies can realize their return on investment in as little as 3 to 60 days.
Keep your existing operating environment
- SYSB-II supports IBM z/OS, VSEn, and CICS Transaction Server.
- SYSB-II supports but doesn't require RLS, CICSPlex, Sysplex, coupling facilities, and TCP/IP and VTAM protocols.
Technical Specifications
- The most current release of the SYSB-II software for z/OS is release 6.9.
- The most current release of the SYSB-II software for VSEn is release 2.1.1.
Compatibility
SYSB-II for z/OS
Unless otherwise specified, the compatibility specifications listed below apply to all supported releases of SYSB-II.
SYSB-II for VSEn
Why We're Different
Since 1979, H&W has been a leading provider of software solutions to enterprise data centers.
By offering secure technology solutions, H&W delivers the peace of mind these enterprises need to enhance their operations and deliver on their objectives.
H&W also provides unparalleled customer service with 24/7 support by technically skilled professionals. H&W works with our customers to meet universal customer objectives, which include mitigating risks, reducing costs, and making maximum use of resources. H&W helps customers meet these goals by anticipating their needs and continuously innovating the product and technology.
Security & Trust
SYSB-II is safe. If you trust CICS file control with data integrity, recovery, and locking, then you can trust SYSB-II.
If you run SYSB-II transparently, it has built-in safeguards like global sync pointing, and with CICS, retained locks are not an issue. SYSB-II uses sync pointing both implicitly and explicitly.
CICS creates log entries for files defined as recoverable. Because SYSB-II makes batch appear like any other CICS transaction, SYSB-II can make use of these log entries to recover from a batch job-step failure. SYSB-II also has a backward recovery option that allows you to back out the updates that a batch job step just made. The backward recovery option uses special batch logs for easier batch restarts.
As you might know, you can do forward recovery for online updates using a product like CICS VSAM Recovery. You can also do forward recovery for batch updates using that type of product and SYSB-II because batch changes are now logged in CICS.
