IBM Db2 for z/OS Developer Extension

IBM® Db2® for z/OS® Developer Extension (Db2 Developer Extension) is an extension for Visual Studio Code that provides language support for developing Db2 for z/OS SQL applications. Complete documentation is contained in our documentation repository.

Licenses

Before downloading this extension, review the Db2 Developer Extension License Agreement, Third Party Notices, and the license for Separately Licensed Code.

Overview

This extension provides language support for the Structured Query Language (SQL) syntax that is used to define, manipulate, and control data in IBM Db2 for z/OS databases. It includes basic productivity features that make it easier to write SQL, such as:

• SQL formatting
• Syntax checking and highlighting
• Code completion and signature help
• Customizable code snippets

It includes a robust set of capabilities for running SQL that include the ability to:

• Display consolidated results from running multiple SQL statements
• Run SQL that includes parameters and variables from within a native stored procedure (.spsql file)
• Sort query history by the timestamp of the execution
• Select multiple SQL elements on different lines and run those elements as a complete statement
• Restrict the number of rows in SQL result sets
• Quickly identify and display failing SQL statements
• Use null values and retain input values
• Validate XML for host variable parameters input
• Run selected SQL statements from any type of file
• Run SQL with or without parameter markers and host variables and to save SQL execution results
• Commit or rollback the results of SQL executions based on customizable success/failure settings

It also includes support for working with native stored procedures by providing the ability to:

• Deploy, run, and debug native stored procedures
• Set conditional breakpoints when debugging stored procedures

And it enables you to analyze and tune the performance of SQL queries by providing the ability to:

• Run Visual Explain - New
• Generate advice for collecting statistics for the data objects involved in a SQL statement and update statistics profiles by using the Statistics Advisor - New
• Generate and download all the artifacts that are needed to re-create access path issues, such as DDL and statistics, by using the Capture Query Environment feature - New
• Create, migrate, and drop EXPLAIN tables - New
• Configure tuning options - New
• Save a history of your tuning activities - New

Note: These SQL tuning capabilities require the Database Services Expansion Pack component of Db2 Accessories Suite 4.2 and APAR PH42944.

See the Key features section for more details and examples.

Table of contents

• Privacy notice for feedback
• Prerequisites for installing Db2 Developer Extension
• Configuring Java
• Specifying port numbers
• Key features
• Additional information
• Limitations for this release

Privacy notice for feedback

Db2 Developer Extension is provided free of charge, but we ask you to provide us feedback via the various means available, such as submitting an issue in our GitHub repository, submitting review comments in the VS Code Marketplace, and keeping the built-in telemetry and crash reports enabled.

This extension uses Microsoft VS Code's Telemetry solution, which collects telemetry data that is used to help understand how to improve the product. While we appreciate the insights this data provides, we also know that not everyone wants to send usage data. You can disable telemetry as described in Disable Telemetry Reporting. You can also read IBM's General Privacy Statement to learn more about our policies.

This current release of Db2 Developer Extension will collect anonymous data for the following events:

• Activation of this VS Code extension
• Opening supported file types (See the Feature Contributions tab for a list of supported file types.)
• Syntax parsing
• Connecting to Db2
• SQL execution
• Deploying, running, or debugging native stored procedures
• Performing tuning actions
• Deactivation of this VS Code extension

Each of these events is logged with the following information:

• Event time
• Operating system and version
• Country or region
• Anonymous user and session ID
• Version numbers of Microsoft VS Code and Db2 Developer Extension

Prerequisites for installing Db2 Developer Extension

Installing Db2 Developer Extension requires the following software:

• One of the following IBM Data Server Driver for JDBC and SQLJ license files. Db2 Developer Extension requires an appropriately licensed JDBC driver. Using a JDBC driver from another tool or product not listed below is not permitted.

  • The Db2 Connect Unlimited Edition for System z® server license V11.1 M4 FP4 iFix or later

  This license must be activated on the Db2 for z/OS subsystems that you want to connect to. For more information, see the following topic: https://www.ibm.com/support/knowledgecenter/SSEPGG_11.5.0/com.ibm.db2.luw.licensing.doc/doc/t0057375.html

  • The IBM Data Server Driver for JDBC and SQLJ client license file 4.25.1301 or later

  For information about locating and and enabling the client license file, see the following topic: https://www.ibm.com/support/pages/db2-jdbc-driver-not-licensed-connectivity-file-db2jcclicensecisuzjar-errorcode-4472-sqlstate42968

  When you specify the location of the db2jcc_license_cisuz.jar license file in your VS Code settings (db2forzosdeveloperextension.db2sqlservice.dependencies), you must provide the full path.

• One of the following 64-bit Java SDKs:

  • Oracle Java SDK 8 or the LTS version 11 of Oracle Java
  • Version 8 or 11 of the OpenJDK

  Alternatively, if you are not developing Java applications, you can install a supported JRE.

  See Configuring Java for information about setting the various options that control how Db2 Developer Extension uses Java.

• libsecret on Linux

  If you are running Db2 Developer Extension for VS Code on Linux, install libsecret by running the appropriate command for your distribution:

  • Debian/Ubuntu: sudo apt-get install libsecret-1-0
  • Red Hat-based: sudo yum install libsecret-devel
  • Arch Linux: sudo pacman -S libsecret

• The SQL tuning capabilities that were introduced in 1.3 of this extension require the Database Services Expansion Pack component of Db2 Accessories Suite 4.2 and APAR PH42944. See the following resources for more information:

  • Db2 Accessories Suite 4.2 overview
  • Database Services Expansion Pack program directory
  • SQL Tuning Services installation and configuration documentation
  • APAR PH42944

Configuring Java

Because part of the SQL language server in IBM Db2 for z/OS Developer Extension is implemented using Java, a Java runtime must be defined in the program path to start Db2 Developer Extension in VS Code. You can specify the specific Java runtime that you want to use and you can set additional Java configuration parameters, such as how much memory the extension can use, in the VS Code User or Workspace Settings. You can also specify a Java runtime and set configuration parameters by editing the settings.json file directly.

Specifying the Java runtime for the Db2 Developer Extension language server

The language server client that is running in the Db2 Dev Extension checks the following places to find a matching Java runtime:

1. First, it checks your current VS Code User Settings or Workspace Settings. These settings take precedence over all other locations, which allows you to specify a different Java runtime for Db2 Developer Extension than you do for other programs on your computer.
2. If a Java runtime was not specified in your VS Code User Settings or Workspace Settings, it checks your JAVA_HOME environment variable.
3. If a Java runtime was not specified in your JAVA_HOME environment variable, it checks your PATH environment variable.

If a Java runtime is not found in any of these locations, an error message is issued. To resolve the problem, specify a Java runtime in one of these locations.

Tip: Alternatively, you can specify a path to a Java SDK on the JAVA_HOME environment variable; for example:

• On Mac:

  "db2forzosdeveloperextension.java.home": "/Library/Java/JavaVirtualMachines/jdk1.8.0_181.jdk/Contents/Home"
  

• On Windows:

  "db2forzosdeveloperextension.java.home": "C:\Program Files\Java\jdk1.8.0_181"
  

Specifying port numbers

You need to specify port number settings for the Db2 SQL Service and the Debugger Session Manager. You can specify a single port number, multiple port numbers, or a range of port numbers.

Db2 SQL Service

The Db2 SQL Service (DSS) provides support for parsing Db2 SQL syntax and for communicating with Db2. Complete the following steps to specify the port number or numbers that the DSS server will run on.

1. Open VS Code settings and search for the db2forzosdeveloperextension.db2sqlservice.port setting.
2. Specify the port number or numbers that you want to assign to the DSS server.
3. Restart VS Code.

Debugger Session Manager

The Debugger Session Manager (DSM) provides support for debugging native stored procedures. Complete the following steps to specify the port number or numbers that the DSM will run on.

1. Open VS Code settings and search for the db2forzosdeveloperextension.db2sqlservice.debugger.sessionManagerPort setting.
2. Specify the port number or numbers that you want to assign to the DSM.
3. Restart VS Code.

Key features

Working with stored procedures

Db2 Developer Extension provides end-to-end support for working with Db2 for z/OS native stored procedures, from creating them through deploying, running, and debugging them.

Deploying a native stored procedure

To deploy a native stored procedure, open a .spsql file that contains a CREATE PROCEDURE statement, then right-click the file and select Deploy Stored Procedure. You can specify deployment options and routine options before deploying the native stored procedure. For this release, only the first native stored procedure in the file will be deployed.

Debugging a native stored procedure

To debug a native stored procedure, open a .spsql file that contains a CREATE PROCEDURE statement, then right-click the file and select Debug Stored Procedure. You will need to specify input values before debugging the native stored procedure. For this release, only the first native stored procedure in the file will be run.

Db2 Developer Extension supports conditional hit-count breakpoints, which means that when the breakpoint is reached, instead of pausing, execution continues until the hit count that you specified is reached. This feature is useful for debugging stored procedures that contain loops.

SQL execution

You can run individual SQL statements that are embedded in any type of source code file by highlighting those statements, right-clicking, and selecting Run Selected SQL. This feature eliminates the need for copying and pasting the statements into a .sql file or modifying your SQL (for example, removing host variables or INTO clauses) before you run it.

Within a SQL file, you can run individual statements and even SQL elements that are on different lines by using the Run Selected SQL option, or you can run the entire file by right-clicking and selecting Run All. If your SQL contains host variables, you'll be prompted to provide a value and data type, or you can specify a null value. When the SQL finishes running, you can export the results in a .csv file.

Db2 Developer Extension supports XML host variables and will validate the syntax if you specify an XML host variable. When you run multiple SQL statements, the results are displayed in in the Execution Summary page. From this page, you can drill down into individual statements, quickly identify, display, and cycle through failing SQL statements, and sort results by their timestamp.

Complete instructions for using the Db2 Developer Extension features for running SQL are in the WORKING WITH SQL category in our documentation repository.

SQL formatting

Db2 Developer Extension takes advantage of VS Code’s Format Document and Format Selection capabilities by allowing you to format SQL within all SQL file types, including .ddl, .spsql, .sql, .javaspsql, and .udfsql files.

The ability to format your SQL makes it much easier to parse large blocks of code and to understand the relationship between different blocks of SQL elements and clauses.

The formatting actions are available from the editor context menu, as keyboard shortcuts, and from the Command Palette.

Tuning SQL statements

You can set up and run Visual Explain, Statistics Advisor, and Capture Query Environment directly from Db2 Developer Extension. As mentioned in the Prerequisites section, these features require the Database Services Expansion Pack feature of Db2 Accessories Suite 4.2.

Setting up a tuning environment

You can register a SQL Tuning Services server into the extension by adding the related information, create a tuning connection profile and EXPLAIN tables if they don't already exist, and then associate the tuning connection profile with the corresponding Db2 connection profile that you defined in the extension.

Running the tuning features

After you've set up your tuning environment, you can configure SQL tuning options and then run any of the available tuning features. The results from Visual Explain are displayed in a browser. Statistics Advisor and Capture Query Environment results are displayed in the Tuning Results window. Results from all three tuning features are accessible from the TUNING HISTORY view.

Additional information

You can find additional information in the Db2 for z/OS Developer Extension documentation repository, including instructions for:

• Getting started, which contains information about the syntax checking and highlighting, code completion and signature help, and code snippets features.
• Creating a database connection
• Committing and rolling back changes

Also, see our blog site to keep up with latest developments.

Limitations for this release

• When you run a CALL statement that includes OUT or INOUT parameters, it will fail.

• Debugging a native stored procedure that contains input parameters as array types is not supported.