What is new and noteworthy

You can find what is new and noteworthy of different releases of IBM Dependency Based Build (DBB) v1.1.x.

Version 1.1.1

Important notices

Server migration

If you are upgrading to DBB V1.1.1 from a previous release, you must merge the configuration from the old server into the new server configuration, and migrate the database before starting the new server. For detailed instructions, see Migrating the DBB server.

New features

Red Hat® OpenShift® is an enterprise-ready Kubernetes container platform with full-stack automated operations to manage hybrid cloud and multicloud deployments. It is optimized to improve developer productivity and promote innovation. DBB v1.1.1 provides the DBB Web Application Server as a certified container package as well as a Container Application Software for Enterprises (CASE) bundle for deploying the DBB operator to an OpenShift Container Platform such as Red Hat OpenShift on IBM Cloud. The DBB operator uses a DBB Server Custom Resource Definition to define and deploy the DBB Web Application Server container in OCP. For more information, see Defining and deploying a DBB server container and Installing the DBB Operator (CASE) bundle.

IBM Dependency Based Build (DBB) provides APIs to create and generate a build report that contains summary information of the DBB z/OS commands executed during the build. Each z/OS command adds a build report record automatically to the build report when it is run. Beginning in DBB v1.1.1, you can turn on "report only" mode. This mode disables the actual execution of the z/OS command while allowing the automatic generation of the build report record to occur as if the command ran successfully. This allows for the creation of a build preview without having to run a real build. To turn on "report only" mode, add the DBB configuration property dbb.command.reportOnly and set the value to true. DBB z/OS commands that support "report only" mode are CreatePDS, CopyToHFS, CopyToPDS, MVSExec, ISPFExec, TSOExec, and JCLExec.

In addition to identifying build dependencies like COBOL COPYBOOKs and PL/I INCLUDE files in program source files, the default dependency scanner can also identify if a program contains EXEC CICS, EXEC SQL, or EXEC DLI statements. These statements are surfaced as flags (isCICS, isSQL, and isDLI) in the program logical file created by the scanner. This information is useful when determining whether additional compile options or DD statements are needed when building programs that contain these statements. Beginning in DBB v1.1.1, the scanner can also identify IBM MQ calls because like CICS, SQL and DLI programs, MQ programs also often require additional compile options, DD statements, or both. The new logical file flag is isMQ.

Version 1.1.0

Important notices

DBB Web Application and Toolkit communication SSL protocol upgrade

The Secure Socket Layer (SSL) protocol used by the DBB Toolkit to communicate with the DBB Web Application for releases DBB v1.0.0 - v1.0.9 used the basic version of Transport Layer Security (TLS). Beginning with DBB v1.1.0, the SSL protocol has been upgraded to use TLSv1.2. If both the DBB toolkit and the DBB Web Application are at the same release version, then no further actions are required. But if the DBB Toolkit is at v1.1.0 and the DBB Web Application Server is at v1.0.x, then they will not be able to communicate with each other unless the DBB v1.0.x Web Application Liberty server configuration is modified to accept TLSv1.2 protocol communication messages. To do so, in the Liberty server server.xml file, find the <ssl> element:

<ssl id="defaultSSLConfig"
     sslProtocol="TLS"
     keyStoreRef="defaultKeyStore"/>

Update it to sslProtocol="TLSv1.2" as follows:

<ssl id="defaultSSLConfig" 
     sslProtocol="TLSv1.2"
     keyStoreRef="defaultKeyStore"/>

This will enable a DBB v1.1.0 Toolkit to communicate with a DBB v1.0.x Web Application.

Dependency Scanner Transfer Control Statement capturing turned off

In DBB v1.0.5, the Dependency Source Code Scanner was enhanced to collect some Transfer Control Statements, mostly in the form of COBOL static link calls. This was done as part of an investigation to support of the automatic compilation and execution of a COBOL program's related IDz zUnit Test program. However, another mechanism for the automatic compilation and executing IDz zUnit Test programs has been implemented, details of which can be found in Integration with z/OS Automated Unit Testing Framework (zUnit) below, so capturing Transfer Control Statements has been turned off in DBB v1.1.0 since they are not used. Recognizing that you might have found an alternative use for the capturing of Transfer Control Statements, you can turn capturing back on by adding the following build property to any loaded DBB property file:

dbb.DependencyScanner.controlTransfers = true

New features