Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix webui and misc docs for v3 #3918

Merged
merged 8 commits into from
Oct 8, 2024
197 changes: 0 additions & 197 deletions docs/extend/extend-desktop/mvd-conda.md

This file was deleted.

2 changes: 1 addition & 1 deletion docs/extend/extend-desktop/mvd-server-config.md
Original file line number Diff line number Diff line change
Expand Up @@ -62,7 +62,7 @@ ZWED_logLevels_org____zowe____terminal____tn3270_x2e_x2a:5
* strings can have quotes, but otherwise everything that isnt an array, boolean, or number is a string
* objects are never values. They are the keys.

# Parameter details
## Parameter details
Below is some more detail on certain parameters than can be covered within the json-schema.

### Configuration directories
Expand Down
2 changes: 1 addition & 1 deletion docs/getting-started/user-roadmap-zowe-explorer.md
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ For a better understanding of Zowe Explorer, review the various reference materi

- Check out the [**Zowe Explorer GitHub repository**](https://github.com/zowe/vscode-extension-for-zowe#readme) to view the source code for Zowe Explorer and other Zowe Explorer-related extensions.

- Watch the following videos to learn how to get started with Zowe Explorer, and work with data sets:
- Watch the following videos to learn how to get started with Zowe Explorer, and work with data sets:

<iframe class="embed-responsive-item" id="youtubeplayer" title="Getting Started with Zowe" type="text/html" width="100%" height="365" src="https://www.youtube.com/embed/G_WCsFZIWt4" frameborder="0" webkitallowfullscreen="true" mozallowfullscreen="true" allowfullscreen="true"> </iframe>

Expand Down
32 changes: 16 additions & 16 deletions docs/user-guide/initialize-zos-system.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,40 +7,40 @@ Once you complete the installation of the Zowe runtime, begin configuration by i

## About the `zwe init` command

The `zwe init` command is a combination of the following subcommands. Each subcommand defines a configuration.
The `zwe init` command is a combination of the following subcommands. Each subcommand defines a configuration.

- **mvs**
- **mvs**
Copies the data sets provided with Zowe to custom data sets.
- **security**
- **security**
Creates the user IDs and security manager settings.
- **apfauth**
APF authorizes the LOADLIB containing the modules that need to perform z/OS privileged security calls.
- **certificate**
- **apfauth**
APF authorizes the LOADLIB containing the modules that need to perform z/OS privileged security calls.
- **certificate**
Configures Zowe to use TLS certificates.
- **stc**
- **stc**
Configures the system to launch the Zowe started task.
- (Deprecated) **vsam**
- (Deprecated) **vsam**
Configures the VSAM files needed if the Caching service is set to VSAM mode. This is not required nor the default, and exists for compatibility.

:::info Recommendation:
We recommend you to run these sub commands one by one to clearly see the output of each step. To successfully run `zwe init security`, `zwe init apfauth`, and `zwe init certificate`, it is likely that your organization requires elevated permissions. We recommend you consult with your security administrator to run these commands. For more information about tasks for the security administrator, see the section [Configuring security](./configuring-security.md) in this configuration documentation.
:::
:::

:::tip
Enter `zwe init --help` to learn more about the command or see the [`zwe init` command reference](../appendix/zwe_server_command_reference/zwe/init/zwe-init-vsam.md) for detailed explanation, examples, and parameters.
Enter `zwe init --help` to learn more about the command or see the [`zwe init` command reference](../appendix/zwe_server_command_reference/zwe/init/zwe-init-vsam.md) for detailed explanation, examples, and parameters.
:::

## zwe init arguments

The following `zwe init` arguments can assist you with the initization process:

- **--update-config**
- **--update-config**
This argument allows the init process to update your configuration file based on automatic detection and your `zowe.setup` settings. For example, if `java.home` and `node.home` are not defined, they can be updated based on the information that is collected on the system. `zowe.certificate` section can also be updated automatically based on your `zowe.setup.certificate` settings.
- **--allow-overwrite**
- **--allow-overwrite**
This argument allows you to rerun the `zwe init` command repeatedly regardless of whether some data sets are already created.
- **-v** or **--verbose**
- **-v** or **--verbose**
This argument provides execution details of the `zwe` command. You can use it for troubleshooting purposes if the error message is not clear enough.
- **-vv** or **--trace**
- **-vv** or **--trace**
This argument provides you more execution details than the `--verbose` mode for troubleshooting purposes.

## Zowe initilization command
Expand All @@ -56,10 +56,10 @@ For more information about the individual `zwe init` subcommands, see [zwe init
:::

:::caution Validate successful initialization
Output from the execution of this command indicates the command ran successfully. However, to determine if each of the subcommands ran successfully, check the full output log. Failed execution of some subcommands may be the result of insufficient user permissions. Consult with your security administrator to find out if elevated permissions are required to successfully execute some of the `zwe init` subcommands.
Output from the execution of this command indicates the command ran successfully. However, to determine if each of the subcommands ran successfully, check the full output log. Failed execution of some subcommands may be the result of insufficient user permissions. Consult with your security administrator to find out if elevated permissions are required to successfully execute some of the `zwe init` subcommands.

For more information about security administrator tasks, see:
* [Addressing security requirements](./address-security-requirements.md)
* [Addressing security requirements](./address-security-requirements.md)
* [Configuring security](./configuring-security.md)
* [Configuring certificates](./configure-certificates.md)
:::
Expand Down
Loading
Loading