zowe › profiles › create › dbm-db2-options-profile🖨️

The DBM-Db2 options profile is a named set of DBM Data Service parameters that are implicitly used with the zowe dbm-db2 commands. The profile includes execution-dependent details.

Warning: This command has been deprecated.
Recommended replacement: The 'config init' command

Usage

zowe profiles create dbm-db2-options-profile <profileName> [options]

Positional Arguments

• profileName (string)

  • Specifies the name of the new dbm-db2-options profile. You can load this profile by using the name on commands that support the "--dbm-db2-options-profile" option.

Options

• --authid | -a (string)

  • Specifies the primary Db2 authorization ID that is used to establish a connection between Db2 and a process.

• --change-set | --cs (string)

  • Specifies the creator and name of an existing RC/Migrator global change set that changes Db2 objects during a command execution.

    Format:

    <change-set-creator.change-set-name>

    For more information about global change services, see the RC/Migrator documentation at https://techdocs.broadcom.com/db2rcmig

    Note: If change-set and change-set-file are both specified, specifications in change-set-file take precedence.

• --change-set-values | --csv (array)

  • Specifies the global change specifications that modify Db2 object attributes during a command execution.

    Format:

    <object-attribute> <from-value> <to-value>

    The <object-attribute> consists of four characters. The first two characters identify the object type. The last two characters identify the specific attribute. Wildcard characters are supported in the <from-value> and <to-value>. The first occurrence in multiple specifications for the same <object-attribute> has the highest precedence.

    For a list of global change set attributes, see the RC/Migrator documentation at https://techdocs.broadcom.com/db2rcmig

    Example:

    The following example demonstrates changes to the table schema (creator) and tablespace names:

    TBCR TEST% PROD%
    TBTS TESTTS% PRODTS%

    Note:
    - If change-set and change-set-file are both specified, specifications in change-set-file take precedence.
    - The changeSetValues options-profile option has the same behavior as the change-set-file command option.

• --delete-work-datasets | --dwd (boolean)

  • Specifies whether to delete work data sets on a mainframe after the request is fulfilled.

• --description | -d (string)

  • Specifies a 1- to 25-character description for the RC/Migrator compare strategy.

• --id (string)

  • Specifies the 1- to 8-character name of the RC/Migrator compare strategy that is created on the target Db2 subsystem during a command execution.

    Format: The name must begin with a non-numeric character and contain the following characters only: uppercase letters from A to Z, numbers from 0 to 9, and special characters $, #, and @.

• --job-cards | --jc (array)

  • Specifies a string array of z/OS JCL JOB statements.

• --match-set | --ms (string)

  • Specifies the creator and name of an existing RC/Migrator automapping mask set. Matching is used to pair objects in a DDL file to objects that are defined on a Db2 subsystem. Matching determines whether the 'change-set' or 'rule-set' options are applied.

    Format:

    <match-set-creator.match-set-name>

    For more information about mask services, see the RC/Migrator documentation at https://techdocs.broadcom.com/db2rcmig

    Note: If --match-set and --match-set-file are both specified, specifications in match-set-file take precedence.

• --match-set-values | --msv (array)

  • Specifies the mapping mask specifications. Matching is used to pair objects in a DDL file to objects that are defined on a Db2 subsystem. For example, a mask specification can account for different schema naming patterns across environments. Matching determines whether the 'change-set' or 'rule-set' options are applied.

    Format:

    <object-type> <source-name-mask> <target-name-mask>;

    STOGROUP <name> <name>
    DATABASE <name> <name>
    TABLESPACE <database.name> <database.name>
    TABLE <schema.name> <schema.name>
    INDEX <schema.name> <schema.name>
    VIEW <schema.name> <schema.name>
    SYNONYM <schema.name> <schema.name>
    ALIAS <schema.name> <schema.name>
    TRIGGER <schema.name> <schema.name>
    SEQUENCE <schema.name> <schema.name>
    FUNCTION <schema.name[.version]> <schema.name[.version]>
    PROCEDURE <schema.name[.version]> <schema.name[.version]>

    Note:
    - <name> must be between 1 and 128 characters. For DATABASE and TABLESPACE, <name> must be between 1 and 8 characters.
    - <schema> must be between 1 and 128 characters.
    - <version> must be between 1 and 64 characters.

    A mask specification can include the following wildcard characters:

    Percent sign (%) indicates that zero or more characters can occupy that position and all remaining positions to the end of the name, or to the next character. The percent sign can be used anywhere in the name. However, the source and target characters must match exactly.

    Hyphen or dash (-) indicates that any character can occupy that position, but a character must exist at that position, and the source and target character must match exactly. The hyphen can be repeated in several places in the name.

    Asterisk (*) indicates matching values. An asterisk cannot be used with other characters.

    Use a semicolon to separate mask specifications. Multiple mask specifications for the same object type are supported.

    Example:

    The following example demonstrates different ways of matching the table MYNAME.MYTABLE to the table YOURNAME.YOURTABLE:

    TABLE MY%.%TABLE YOUR%.%TABLE;
    TABLE MYN-M-.MYT% YOURN-M-.YOURT%;
    TABLE MYNAME.MYTABLE YOURNAME.YOURTABLE;
    TABLE *.MYTABLE *.YOURTABLE;

    For a list of mask specifications, see the RC/Migrator documentation at https://techdocs.broadcom.com/db2rcmig

    Note:
    - If --match-set and --match-set-file are both specified, specifications in match-set-file take precedence.
    - The matchSetValues options-profile option has the same behavior as the match-set-file command option.

• --modification | -m (string)

  • Specifies a named set of server-managed default parameter values that control the execution behavior of the zowe dbm-db2 commands. For example, you can use a modification to identify a set of default values that differ from the current set of default values.

    For more information about using the modification option, see the DBM Data Service documentation at https://techdocs.broadcom.com/db2mgmt

• --overwrite-output-files | --oof (boolean)

  • Specifies whether to overwrite output files if they exist.

• --rule-set | --rs (string)

  • Specifies the creator and name of an existing RC/Migrator rule set that overrides Db2 object attributes in the target Db2 subsystem with the corresponding values from the input DDL file. The changes only apply to existing objects, as determined by match-set processing.

    Format:

    <rule-set-creator.rule-set-name>

    For more information about rule database services, see the RC/Migrator documentation at https://techdocs.broadcom.com/db2rcmig

• --sqlid | -s (string)

  • Specifies the authorization ID that is used in generated SET CURRENT SQLID statements.

• --source-db2 | --sd (string)

  • Specifies the source Db2 subsystem or data sharing group where the objects that you want to use in a command are located.

    Note: If you specify the data sharing group, the first active Db2 subsystem in the group is used.

• --target-db2 | --td (string)

  • Specifies the target Db2 subsystem or data sharing group where you want to use a command.

    Note: If you specify the data sharing group, the first active Db2 subsystem in the group is used.

• --termination-character | --tc (string)

  • Specifies the SQL termination character to use in DDL generation when the default termination character conflicts with the SQL statements that are used in triggers, XML indexes, and routines (external SQL functions and native SQL stored procedures). The default termination character is a semi-colon (;). You cannot specify a comma, double quote, single quote, left or right parentheses, or an underscore.

• --type | -t (string)

  • Specifies the type of DDL statements that you want to generate. You can generate CREATE or DROP statements.

    Allowed values: drop, create

• --verify | -v (string)

  • Specifies whether to verify that the objects to be created do not exist on the Db2 subsystem and that the related objects that are required for successful creation of the objects exist on the Db2 subsystem or in the input DDL.

    Default value: no

    Allowed values: yes, no

• --work-dataset-prefix | --wdp (string)

  • Specifies the prefix (high-level qualifier) in z/OS work data set names.

• --overwrite | --ow (boolean)

  • Overwrite the dbm-db2-options profile when a profile of the same name exists.

• --disable-defaults | --dd (boolean)

  • Disable populating profile values of undefined properties with default values.