Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI SQL Assurance for Db2 13.1.

Symbolic variables

Symbolic variables are special user-defined variables in one of the following formats:

  • ${variable}
  • #variable#

You can use symbolic variables to dynamically provide input for Jenkins projects.

Types of symbolic variables

Type

Description

Parameter-based variables

These variables are in ${variable} format.

SQL Assurance replaces these variables with the default or user-defined value of the corresponding parameter.

Example

You create a string parameter, MF_USER_ID, with a default value, TESTID1. When you build the project, the value of the symbolic variable, ${MF_USER_ID}, is either TESTID1 (the default value of the MF_USER_ID parameter) or the value that you enter.

To use parameter-based variables, you must select the This project is parameterized check box in the General tab when configuring the project.

Field-based variables

These variables are in ${variable} format.

SQL Assurance replaces these variables with the value of the corresponding fields.

Example

The value of the symbolic variable, ${Job Card}, is the value of the field, Job Card.

Plug-in variables file-based variables

These variables are in #variable# format.

SQL Assurance replaces these variables with the value of the the corresponding variable in the plug-in variables file.

Example

The value of the symbolic variable, #acctno#, is the value of the variable, acctno, in the plug-in variables file.

Important

  • For symbolic variables in ${variable} format, parameter-based variables have priority over field-based variables of the same name.
  • SQL Assurance searches for symbolic variable values in #variable# format only in the plug-in variables file.
  • The symbolic variables provided in the sample projects are not keywords. You can use any variable name in the plug-in variables file and subsequently in the project.
  • If required, you can add more symbolic values to your project.
  • You can delete symbolic variables from the project and hard-code values. However, BMC does not recommend this because it prevents you from dynamically providing values for your project.

Related topic

Command-and-syntax-reference

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*