## zowe › profiles › create › ops-profile

The OPS Web Services session profile schema, where you specify your session information and credentials

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

#### Usage

zowe profiles create ops-profile <profileName> [options]

#### Positional Arguments

- `profileName` (string)

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

#### OPS WEB SERVICES CONNECTION OPTIONS

- `--host` (string)

  - The hostname of the server where OPS Web Services is running.

- `--port` | `-p` (number)

  - The port number for OPS Web Services.

- `--user` (string)

  - Your z/OS user name used to authenticate to OPS Web Services

- `--password` | `--pass` (string)

  - Your z/OS password used to authenticate to OPS Web Services

- `--protocol` | `--prot` (string)

  - The protocol used for connecting to OPS Web Services

    Default value: https
    Allowed values: http, https

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

  - If set to true, the server certificate is verified against the list of supplied CAs. If set to false, certificate verification is not performed.

    Default value: true

- `--subsystem` | `--subs` (string)

  - Specifies the subsystem id of the OPS/MVS instance to which commands will be directed.

#### Options

- `--overwrite` | `--ow` (boolean)

  - Overwrite the ops 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 an OPS profile called 'myLPAR' to connect to OPS Web Services at host lpar123 and port 8080, using http protocol, allowing self-signed certificates:

  - `zowe profiles create ops-profile myLPAR --host lpar123 --port 8080 --user ibmuser --password !@#$^ --prot http --reject-unauthorized false`