Deploying Changes to DB2 on z/OS using SQL Scripts

Step 1: Create an SQL Folder

In the Liquibase project folder that you created, create a folder named sql_files to store SQL scripts that Liquibase will track, version, and deploy.

The directory structure should look like this:


Step 2: Setup the changelog

This is a one-time step to configure a change log to point to the SQL folder that will contain SQL scripts. Create and save a file in the Liquibase project directory you created ($LB_HOME/db2_zos). The file should be named db2zosChangeLog.xml.

The contents of db2zosChangeLog.xml should be as follows:

<?xml version="1.0" encoding="UTF-8"?>
<includeAll path="sql_files"/>

Step 3: Add an SQL Script to the SQL Folder

With a Liquibase properties file, like from the tutorial setup and the newly created db2zosChangeLog.xml, we are now ready to start adding SQL scripts to the sql_files folder. Liquibase orders the scripts in the folder alphanumerically.

Create a file named 001_create_person_table.sql with the following and save it in the sql_files folder:

create table PERSON (
ID int not null,
FNAME varchar(100) not null

We are now ready to deploy the script! Open the command line and navigate to $LB_HOME/db2_zos. Run $LB_HOME/liquibase update if on a UNIX system or $LB_HOME\liquibase.bat update if on Windows.

You will see that your database now contains a table called PERSON.

Step 4: Check your Database

From a database UI tool, ensure that your database contains the table you added along with the DATABASECHANGELOG table and DATABASECHANGELOGLOCK table.

Common Command Line Arguments

Use can use command line arguments to override the default options at runtime. The following are common command line arguments:

Command line argument Action
--changelog-file=<path and filename> Specify the XML changelog
--url=<value> Specify a database URL
--defaultsFile=<path to> Specify the properties file. Default is ./