step:

The step: element defines a DBB command or common build action that should be executed for each build file in the language sublist. The step element represents the most basic building block for language build configuration.

Syntax

For step syntax, visit the steps: element reference page. Use the links below to access syntax specific to each step type:

Generated step variables

The language task makes the following variables available for reference during step execution. They are updated dynamically for each build file:

Step Variable Type Description
${FILE} String Current file being processed
${MEMBER} String Dataset member name of current file being processed
${STEP} String Name of the current step being executed
${RC} Integer The return code of the last step to execute
${<step-name>} Integer The return code of the named step
${IS_CICS} Boolean Flag that indicates whether the program contains CICS calls
${IS_DLI} Boolean Flag that indicates whether the program contains DLI calls
${IS_MQ} Boolean Flag that indicates whether the program contains MQ calls
${IS_SQL} Boolean Flag that indicates whether the program contains SQL calls

Note: Occasionally the DBB Dependency Scanner fails to identify a file’s subsystems correctly. As an alternative to using the IS_* variable definitions from the scanner, you can provide subsystem file associated variables in the language configuration that will be used when setting the generated subsystem variables. These variables should be given a default value and added to the appropriate conditions:

variables:
  - name: isSQL
    value: false
  - name: isSQL
    value: true
    forFiles:
      - cobol/epsmlist.cbl

...
condition: ${IS_SQL} || ${isSQL}
...