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

The DBM-Db2 profile is a named set of DBM Data Service parameters that are implicitly used with the zowe dbm-db2 commands. The profile includes server connection, z/OS execution, and user-dependent details.

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

Usage

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

Positional Arguments

• profileName (string)

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

DBM-Db2 Options

• --host | -H (string)

  • Specifies the DBM Data Service REST API server host name or TCP/IP address to use.

• --port | -P (number)

  • Specifies the DBM Data Service REST API server TCP/IP port number.

    Default value: 7300

• --user | -u (string)

  • Specifies the mainframe user name that you want to use to connect to the mainframe systems during execution of the Zowe CLI commands. This user name can be the same as your TSO login ID.

• --password | --pass | --pw (string)

  • Specifies the mainframe password for the user name that is used to connect to the mainframe systems during execution of the CLI commands. This password can be the same as your TSO password.

• --protocol (string)

  • Specifies the communication protocol between zowe dbm-db2 client and DBM Data Service.

    Default value: https
    Allowed values: http, https

• --reject-unauthorized | --ru (boolean)

  • Determines whether the dbm-db2 command is accepted or rejected when a self-signed certificate is returned by the DBM Data Service.

    Default value: true

• --environment-list | --el (string)

  • Specifies a string of one or more entries consisting of a Db2 subsystem ID and a DBM Data Service REST API server host name or TCP/IP address. Use a comma to separate entries. The same Db2 subsystem can be used in multiple DBM Data Service environments. For more information about configuring the DBM Data Service, see the Database Management Solutions for Db2 for z/OS documentation at https://techdocs.broadcom.com/db2mgmt

    Default value: [object Object]

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

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

    Default value: //DB2DVOPS JOB CLASS=A,,// MSGCLASS=X

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

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

    Default value: ${user}.dbmdb2

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

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

    Default value: true

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

  • Specifies whether to overwrite output files if they exist.

    Default value: false

• --authid | -a (string)

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

    Default value: ${user}

• --sqlid | -s (string)

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

    Default value: ${user}

• --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.

    Default value: ;

Options

• --overwrite | --ow (boolean)

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

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

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

Examples

• Create a DBM-Db2 profile named profile_name1 and default values for all the options:

  • zowe profiles create dbm-db2-profile profile_name1 Copy

• Create a DBM-Db2 profile named dbm123 that connects to the DBM Data Service at host dbm123 and port 1443 as user db2user and password myp4ss:

  • zowe profiles create dbm-db2-profile dbm123 --host dbm123 --port 1443 --user db2user --password myp4ss Copy

• Create a DBM-Db2 profile named dbm124 that connects to the DBM Data Service at host dbm124 and the default port as user db2user and password myp4ss, and allow self-signed certificates:

  • zowe profiles create dbm-db2-profile dbm124 --host dbm124 --user db2user --password myp4ss --reject-unauthorized false Copy

• Create a DBM-Db2 profile named dbm125 that connects to the DBM Data Service at host dbm125 and port 1443 and requires a user and password to be specified on every dbm-db2 command. DBM Data Service access to Db2 subsystems SUBA and SUBB uses prod@host1.com:322 and test@host2.com:522, respectively:

  • zowe profiles create dbm-db2-profile dbm125 --host dbm125 --port 1443 --environment-list "SUBA:prod@host1.com:322,SUBB:test@host2.net:522" Copy

• Create a DBM-Db2 profile named dbm126 that uses specified job cards for every mainframe job:

  • zowe profiles create dbm-db2-profile dbm126 --job-cards "//DB2DVOPS JOB (123456789),'DB2 PROVISIONING',NOTIFY=&SYSUID," "// CLASS=A,MSGCLASS=X,MSGLEVEL=(1,1)," "// REGION=0M,TIME=NOLIMIT" Copy