Binding to a database creates a package that enables VisualAge to use your database. There are two ways you can bind your database; in both cases you must bind the database before you attempt to access it.
The following are some common problems that can be solved by ensuring that you are properly bound to the database you need to access:
SQL0805N "<package name>" is not found.
SQL0552N "<user ID>" does not have the privilege to perform operation "CREATE IN".
Make sure first that the user ID has authorization to use the table. Then issue authority to the user ID to run the package that performed the bind on the database by issuing one of the following commands from a command prompt. In these examples, replace bindfile with the name of the bind file that is appropriate for your database manager and replace userid with the user ID under which the user wants to bind to the database.
GRANT RUN ON PACKAGE NULLID.bindfile TO userid GRANT RUN ON PACKAGE NULLID.bindfile TO PUBLIC
Note: | Binding a database to your image is a one-time requirement. After VisualAge is bound once, it doesn't have to be bound again. |