1. Home
  2. Relational Databases
  3. Db2 Reviews
  4. User Review of Db2
Love Having and Working on Db2 for z/OS
February 13, 2024

Love Having and Working on Db2 for z/OS

Anonymous | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User

Software Version

Db2 on-premise

Overall Satisfaction with Db2

We use Db2 as the Application Databases that we have and the processes that utilize them at SSE/OVO Energy. A Db2 Sub-system can itself be part of a Db2 Data Sharing Group. Db2 Data Sharing allows us to spread the workload and resources of Db2 over more than one LPAR. The assigned Application databases are accessible through the Db2 sub-systems of the group. At SSE, we have several Data Sharing Groups. Each one has two sub-systems, these sub-systems running on separate LPARs. Each Data Sharing Group has its own unique name, there are several ways to connect to Db2 when wishing to access the databases. The Application that we use here is called the Customer System (also known as the CS Database). CS comprises 17 databases totaling over 1100 tables.
  • It reduced the amount of time we spend managing data
  • A high degree of availability
  • Data Protection and data integrity
  • Exceptional scalability with a high volume of transactions
  • Partition by growth tablespaces
  • Data refresh
  • Integration with cloud
  • Fast response time by processing optimization and cost reduction by reduced CPU utilization. Nowadays, good performance is a necessary condition for the survival of a company and its sustained growth
  • SQL enhancements are targeted to improve performance, simplify current and new applications, and reduce the development cycle time to market.
  • A CPU reduction at peak times can immediately reduce our TCO by reducing software costs related to CPU utilization.
  • Impressive reductions in memory requirements, which used to limit the concurrent database activity
  • Out-of-the-box savings without changing the database or application
Impressive reductions in memory requirements, which are used to limit the concurrent database activity. Db2 logging and the internal Db2 serialization mechanisms (latches) have been improved, giving an overall increased throughput per Db2 where they might have been the limiting factor in previous versions. These changes open new consolidation opportunities where reducing the required number of Db2 subsystems for the same workload with the potential of obtaining further performance improvements and TCO savings.
High availability changes rapidly from simply being available to being available and having excellent response time. With many applications providing a Web interface, and thus having more online users, the SSE/OVO achieved a near-instantaneous response time expectation. A modern application is constantly available and provides fast and consistent response time. Excellent response times are achieved by optimizing the in-house IT infrastructure, applications, and middleware and providing fast response times to online users. Nowadays, many applications query large amounts of historical data, and SSE/OVO delivers a good response time.

Do you think Db2 delivers good value for the price?

Yes

Are you happy with Db2's feature set?

Yes

Did Db2 live up to sales and marketing promises?

Yes

Did implementation of Db2 go as expected?

I wasn't involved with the implementation phase

Would you buy Db2 again?

Yes

IBM CICS, IBM MQ, BMC Automated Mainframe Intelligence (AMI)
Unloading all tables on the Invoice Database and Transfer, and then transferring the data off the mainframe is much faster. It was at some point a bit less appropriate for Windows support while we executed a series of jobs to read the Db2 Unload files. For each partition, the file is reformatted and processed by a Cobol program. A DFILE type file is produced. This file is then read by another Cobol program, this program produces an SQL update file. Execute File Transfers to Windows Server.