DBUnifier FAQ's

1. What is DBUnifier?

A programmer’s utility which allows developers to dynamically create list programs one time and call them from any number of programs. F4 List programs create pop up windows for validation or selection (i.e. if you press F4 when cursor is position on STATE on our screen, you get a listing of all possible values)

Note: No source code is generated. No compiler is needed.

DBUnifier was developed to assist programmers and power users with the ability to create interactive applications from DB2/400 database information. You are able to create Selection Lists (F4-Lists Processes), Work with Subfile Processes, Inquiry Applications and File Maintenance Applications with Field level validations.

Instantly increase productivity and standardize programs. It's the ultimate in the 'code-less' creation of your applications!
 

2. How much is it?

$1995 per license LPAR or non-LPAR. $295 yearly maintenance after 90 days. No Tier Pricing.
 

3. What are the iSeries systems requirements to utilize DBUnifier?

OS/400 V4R2 & above.
 

4. What is the trial time?

30 days, plus extension code available for another 30 days.
 

5. How do you load DBUnifier from the cd-rom provided?

Place the cd-rom in AS/400 Drive & execute the command LODRUN *opt.
 

6. How do you execute DBUnifier?

• ADDLIBLE dbunifier
• Execute the command ‘WRKDBUAPP’
• The interface is similar to WRKQRY on the iSeries and walks you thru the file, field and window size selections for your DBUnifier application.

Once completed, the application can be saved and integrated with your current systems.

All DBUnifier applications can be called from any high level language.
 

7. Where is the source code for a DBUnifier application?

There is no source code produced when building a DBUnifier application. You can think of DBUnifier application like you would a Query Definition. The applications definition is stored in a user space which can be distributed to other systems.
 

8. How do you integrate DBUnifier application into your existing systems?

There are sample applications that show you how to integrate DBUnifier applications into your existing system. These examples can be found in the source file DBFSOURCE in the library DBUNIFIER.
 

9. Are DBU Apps and DBUnifier Application the same thing?

Application built within DBU are not the same type of objects that DBUnifier Applications are. Although, with the latest version of DBU you can access and build DBUnifier Applications.
 

10. Can the same DBUnifier Application be used for both Updating of data and Inquiry Only?

Yes. You can launch a DBUnifier Application in any one of the following modes.

• *INQUIRY – Allows only inquiry
• *UPDATE – Allows Inquiry and Update. No Record Deletes or Record Inserts.
• *FULL – Allows Inquiry, Update, Inserting and Deleting of Records.
• *NODELTE – Allows Inquiry, Update, and Inserting of Records.

11. How do you only process a subset of data from a DB2/400 file?

By using the QRYSLT parameter, when launching a DBUnifier Application, you can limit the data in a DB2/400 file that is processed. The QRYSLT parameter is modeled after the OPNQRYF Query Select statement. We determined it would be easier for programmers to construct a Query Select within high level language, than trying to build an SQL Select statement. (QRYSLT utilizes double quotes to define an alpha value, and SQL Select utilizes single quotes).
 

back to top