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

link fix #3600

Merged
merged 3 commits into from
Apr 9, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/user-guide/configure-zowe-runtime.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ After your installation of Zowe runtime, you can run the `zwe init` command to p
* Configure VSAM files to run the Zowe caching service used for high availability (HA)
* Configure the system to launch the Zowe started task

For more information about this z/OS runtime initialization method, see [Initializing the z/OS system with zwe init](./initialize-zos-system)
For more information about this z/OS runtime initialization method, see [Configuring Zowe with zwe init](./initialize-zos-system.md)

## Configure Zowe with z/OSMF workflows

Expand Down
2 changes: 1 addition & 1 deletion docs/user-guide/configure-zowe-zosmf-workflow.md
Original file line number Diff line number Diff line change
Expand Up @@ -184,4 +184,4 @@ After you execute each step, the step is marked as Complete. The workflow is exe

## Next step

After you successfully execute the workflow, you are ready to [configure the z/OS system for Zowe](./configure-zos-system.md).
After you successfully execute the workflow, you are ready to configure the z/OS system for Zowe. For more information, see [Addressing z/OS requirements for Zowe](./configure-zos-system.md).
2 changes: 1 addition & 1 deletion docs/user-guide/configuring-overview.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ Successful completion of steps 2, 3, and 4 may require elevated security permiss
To cofigure Zowe runtime, choose from the following options:

* **Option 1: Configure Zowe manually using the `zwe init` command group**
To run the `zwe init` command, it is necessary to create a Zowe configuration file. For more information about this file, see the [Runtime directory](./installandconfig.md#zowe-configuration-file) which details all of the started tasks in the article _Preparing for installation_.
To run the `zwe init` command, it is necessary to create a Zowe configuration file. For more information about this file, see the [Runtime directory](./installandconfig.md#runtime-directory) which details all of the started tasks in the article _Preparing for installation_.

Once your configuration file is prepared, see [Configuring Zowe with zwe init](./initialize-zos-system.md), for more information about using the `zwe init` command group.

Expand Down
8 changes: 4 additions & 4 deletions docs/user-guide/initialize-zos-system.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,11 +23,11 @@ Configures the VSAM files needed to run the Zowe caching service used for high a
Configures the system to launch the Zowe started task.

:::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) in this configuration documentation.
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) 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
Expand Down Expand Up @@ -55,10 +55,10 @@ zwe init --config /path/to/zowe.yaml
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 `zwe init` subcommands, see [zwe init subcommand overview](./zwe-init-subcommand-overview).
For more information about `zwe init` subcommands, see [zwe init subcommand overview](./zwe-init-subcommand-overview.md).

## Next step

After all `zwe init` subcommands are successfully executed, the next step is to [configure the z/OS system for Zowe](./configure-zos-system).
After all `zwe init` subcommands are successfully executed, the next step is to configure the z/OS system for Zowe. For more information, see [Addressing z/OS requirements for Zowe](./configure-zos-system.md).

For detailed information about individual `zwe init` subcommands, see [zwe init subcommand overview](./zwe-init-subcommand-overview.md).
Loading