Access your multi-member files, let your users dynamically select the member they want to query at run time, and create a report that uses the latest and greatest database engine technology.

Written by Gene Cobb

Over the last several years, I have written several articles about DB2 for i and DB2 Web Query, some of which emphasized the importance of employing techniques to ensure that your queries are using the SQL Query Engine (SQE), the strategic database engine for DB2 for i. One of the requirements for SQE processing is that the database access method must be SQL. However, one of the very few drawbacks with SQL access on our beloved system is that it does not natively support the concept of physical file members.

Use this simple method to manage the display size of your reports.

Written by Robert Andrews

When you create a dashboard in DB2 Web Query, it often contains a combination of graphs, reports, and, optionally, selection criteria. Because of changing criteria or business loads, the size required to display these reports changes. By default, Web Query uses fixed locations, which means that you need to plan for the largest size to avoid overlap. However, when you have smaller reports, this leads to large sections of undesired white space. In this TechTip, I will explain how to avoid this problem by using floating reports.

Simplify database administration tasks by using graphical administration tools for PostgreSQL and MySQL databases.

Written by Max Hetrick

I'm not a database guru, so for me, getting into and working with the guts of databases isn't always easy. For the limited amount of time I have to work with databases, I like using GUI tools to help me complete my tasks. Also, when you use administration tools, there's often no need to worry about the various SQL command-line differences between databases—or at least not as much. Although diehard SQL administrators and DBAs will probably disagree with me, graphical database tools can and will make your experience with databases a little less complex and cumbersome.

Empower users so that they can get the data they want to see.

Written by Floyd Del Muro

How do you deliver the information your users need to do their jobs? Can they answer business questions quickly and correctly? Are they empowered with the tools and the knowledge they need to find and access the data spread out across your enterprise?

Sadly, for many, the answers are "we don't," "not really," and "no."

i5/OS Query is outdated, and Enterprise BI tools require more licenses, consulting, and money.

Written by Floyd Del Muro

Are users begging you for a modern look and feel when it comes to System i data? Are they telling you that green-screen reports are unacceptable? Is your backlog of text-based reports getting you down? Is your DB2 data warehouse project over budget, past due, and not satisfying user requests? Are you confused about what tools to use for accessing business data, how many tools you need, and what skill sets are required?

Check out the lab tests on the new OVRDBF feature that lets you override the REUSEDLT(*YES) attribute of a physical file or table and effectively use the behavior of REUSEDLT(*NO).

Written by Fernando Echeveste

In a previous TechTip, I introduced a new Override with Database File (OVRDBF) command option that allows an application that requires high velocity inserts to temporarily override the REUSEDLT(*YES) attribute of a physical file or table and effectively use the behavior of REUSEDLT(*NO). In this second part, I will explain the results of lab-testing this new feature and some of the performance considerations when inserting rows into a table. I will also explain how you can obtain this new feature and start benefiting from it in your shop.

With a new OVRDBF feature, you can override the REUSEDLT(*YES) attribute of a physical file or table and effectively use the behavior of REUSEDLT(*NO).

Written by Fernando Echeveste

If your application inserts a large volume of rows into DB2 for i tables, the following features found on IBM i can influence the performance of your application:

Are you in a quandary because DB2 Web Query can't use *libl to find your stored procedure's synonym? Yes, it can!

Written by Anita Corcoran

In a previous Tech Tip, "Use a Stored Procedure as Your Data Source in DB2 Web Query for i," I discussed using a stored procedure as the data source in DB2 Web Query for i. Using a stored procedure as your data source offers many benefits to you as a developer: