Now we’ll access Scriptcase from Scriptcase from the browser and create a connection with the DB2 database.
Step 1: Access your Scriptcase, for example, http://localhost:8081/scriptcase/ on
go to the marked icon in the image below, referring to “New Connection”.
Step 2: After clicking “New Connection”, the page for creating connections will appear, click on the
DB2 database image.
Step 3: On the following image, place the required information:
Connection Name - Define the name of your new connection.
DBMS Driver - Allows you to define the driver that’ll be used, by default it’s DB2 Native ODBC.
Test Connection - Validates the connection and informs if it was successful or not.
Server/Host (Name or IP) - Inform the location of the DB2 database.
Database Name - Inform the name of your DB2database.
User - Inform the user of your DB2 database.
Password - Inform the password of your DB2 database.
Schema - You can tell the Schema (Optional), if you wish to use only the tables belonging to
For more details on configuring the connection of the database click on Advanced
autocommit - Enable or disable autocommit feature.
i5_lib - A character value that indicates the default library that will be used for resolving
unqualified file references. This is not valid if the connection is using system naming mode.
i5_naming - Enables or disables the appointment so DB2 UDB CLI iSeries system. Files are
qualified using the slash (/) delimiter. Unqualified files are resolved using the library list for the job.
i5_commit - Select desired option for treating IBM DB2 data reading.
Decimal Separator - Select the type of separator, between coma and period.
Persistent Connection - Persistent connections are connections that don’t close after running
Use the schema before the table name - Allows the use of schemas before the table names.
Filter - Clicking on this tab, the following page will appear:
Show - Allows to show Tables, Views, System Tables and Procedures.
Searches - Allows to define which tables and owners will be shown.
Step 4: Always test your connection before saving, if the message “Connection Success” appears, then
save the connection. If it fails to connect, revise the fields that were informed, especially Username, Password,
Database and Server/Host.