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.
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 Common Options
-
--job-cards
| --jc
(string)
-
Specifies a newline delimited string of z/OS JCL JOB statements.
Default value: //DB2DVOPS JOB (<nnn>),'DB2 PROVISIONING',NOTIFY=&SYSUID,\n// CLASS=A,MSGCLASS=X,MSGLEVEL=(1,1),\n// REGION=0M,TIME=NOLIMIT
-
--work-dataset-prefix
| --wdp
(string)
-
--authid
| -a
(string)
-
--sqlid
| -s
(string)
-
--termination-character
| --tc
(string)
-
Specifies the SQL termination character that you want to use to terminate object DDL for triggers, XML indexes, functions, and procedures that contain embedded semicolon-terminated SQL statements.
You cannot use a comma, an underscore, a single quote, double quotes, left parentheses, or right parentheses for this value.
-
--overwrite-output-files
| --oof
(boolean)
dbm-db2 Connection Options
-
--host
| -H
(string)
-
--port
| -P
(number)
-
--user
| -u
(string)
-
--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.
Default value: <password>
-
--reject-unauthorized
| --ru
(boolean)
-
--protocol
(string)
-
Specifies the communication protocol to use between the zowe dbm-db2 client and the DBM Data Service.
Default value: https
Allowed values: http, https
-
--environment-list
| --el
(string)
-
Specifies a string of one or more paired values consisting of a Db2 subsystem ID and a DBM Data Service environment pair. The paired entry identifies the DBM Data Service environment to use for a subsystem that is accessible through multiple DBM Data Service environments.
Format:
<ssid1>:<env1>, <ssid2>:<env2>, …
<ssid> is the subsystem ID. <env> is an entry that is configured in the DBM Data Service environments.yaml file. 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.
Example: ssid:prod@host1.net:7300,ssid2:test@host2.net:7300
Options
Examples
-
Create a dbm-db2 profile named profile_name1 and default values for all the dbm-db2-profile options:
zowe profiles create dbm-db2-profile profile_name1
-
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
-
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
-
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 --el “SUBA:prod@host1.com:322,SUBB:test@host2.net:522”