Remove parts of Zowe that aren't there anymore (#3925)

* Remove parts of Zowe that aren't there anymore

Signed-off-by: Jakub Balhar <[email protected]>

* Replace calendar links

Signed-off-by: Jakub Balhar <[email protected]>

* Fix broken links

Signed-off-by: Jakub Balhar <[email protected]>

* Fix broken links

Signed-off-by: Jakub Balhar <[email protected]>

* Add ZAAS to the HA Scheme

Signed-off-by: Jakub Balhar <[email protected]>

* Fix another broken link

Signed-off-by: Jakub Balhar <[email protected]>

* Fix another broken link

Signed-off-by: Jakub Balhar <[email protected]>

---------

Signed-off-by: Jakub Balhar <[email protected]>

docs/appendix/zowe-yaml-configuration.md

@@ -421,7 +421,7 @@ These configurations can be used under the `components.gateway` section:
   Specifies the global feature toggle. Set the value to `true` to enable OIDC authentication functionality.
 
 - **`apiml.security.oidc.registry`**  
-  Specifies the SAF registry used to group the identities recognized as having an OIDC identity mapping. The registry name is the string used during the creation of the mapping between the distributed and mainframe user identities. For more information, see the [ESM configuration](#esm-configuration).
+  Specifies the SAF registry used to group the identities recognized as having an OIDC identity mapping. The registry name is the string used during the creation of the mapping between the distributed and mainframe user identities. For more information, see the [ESM configuration](../extend/extend-apiml/api-mediation-oidc-authentication.md#esm-configuration-prerequisites).
 
 - **`apiml.security.oidc.jwks.uri`**  
   Specifies the URI obtained from the authorization server's metadata where the Gateway will query for the JWK used to sign and verify the access tokens.
@@ -440,7 +440,7 @@ User authorization is required to use the `IRR.RUSERMAP` resource within the `FA
 
 - **`apiml.security.oidc.identityMapperUrl`**  
   Defines the URL where the Gateway can query the mapping of the distributed user ID to the mainframe user ID. 
-  This property informs the Gateway about the location of this API. ZSS is the default API provider in Zowe, but if you are using Zowe release 2.14 or a later version, we recommend you use the [API ML internal mapper](../../user-guide/authenticating-with-client-certificates.md#enabling-the-internal-api-ml-mapper). You can provide your own API to perform the mapping. In this case, it is necessary to customize this value.
+  This property informs the Gateway about the location of this API. ZSS is the default API provider in Zowe, but if you are using Zowe release 2.14 or a later version, we recommend you use the [API ML internal mapper](../user-guide/api-mediation/configuration-client-certificates.md#configure-internal-api-ml-mapper). You can provide your own API to perform the mapping. In this case, it is necessary to customize this value.
 
   The following URL is the default value for Zowe and ZSS:
 

docs/extend/extend-apiml/api-mediation-versioning.md

@@ -24,7 +24,6 @@
  Resource Identifier (URIs). The services are accessed via APIML gateway. Example of a URI:
  `https://host:10010/endevormfno/api/v1/ENWSQA01/packages/PACKAGETST
  (https://{gatewayHost}:{port}/{serviceName}/api/v{majorVersion}/{resource}`)
- See [Components of URL](../extend-apiml/api-mediation-components-of-URL.md) for more information about the URL components of REST APIs.
 
  ## Data Model
 

docs/extend/extend-apiml/onboard-plain-java-enabler.md

@@ -40,7 +40,7 @@ The following steps outline the overall process to onboard a service with the AP
     * [Maven build automation system](#maven-build-automation-system)
 
 3. [Configuring your service](#configuring-your-service)
-    * [Service identification](#rest-service-identification)
+    * [Service identification](#service-identification)
     * [Administrative endpoints](#administrative-endpoints)
     * [API info](#api-info)
     * [API routing information](#api-routing-information)
@@ -312,7 +312,7 @@ customMetadata:
 ```
 The onboarding configuration parameters are broken down into the following groups:
 
-- [Service identification](#rest-service-identification)
+- [Service identification](#service-identification)
 - [Administrative endpoints](#administrative-endpoints)
 - [API info](#api-info)
 - [API routing information](#api-routing-information)

docs/extend/extend-desktop/mvd-server-config.md

@@ -3,11 +3,11 @@
 The Zowe's App Server and ZSS rely on many required or optional parameters to run, which includes setting up networking, deployment directories, plugin locations, and more. 
 These parameters can be specified in two ways: configuration files, or environment variables.
 
-Every configuration option and requirement is documented within the application framework [json-schema file](https://github.com/zowe/zlux/blob/v3.x/staging/schemas/zlux-config-schema.json)
+Every configuration option and requirement is documented within the application framework [json-schema file](https://github.com/zowe/zlux-app-server/blob/v3.x/staging/schemas/app-server-config.json)
 
 ## Configuration file
 
-In Zowe's server configuration file, app-server parameters can be specified within `components.app-server` as shown in the component [json-schema file](https://github.com/zowe/zlux/blob/v3.x/staging/schemas/zowe-schema.json), or `components.zss` for ZSS.
+In Zowe's server configuration file, app-server parameters can be specified within `components.app-server` as shown in the component [json-schema file](https://github.com/zowe/zlux-app-server/blob/v3.x/staging/schemas/zowe-schema.json), or `components.zss` for ZSS.
 
 ## Environment variables
 

docs/extend/extend-sdks.md

@@ -14,6 +14,6 @@ For detailed contribution guidelines, see the following documents:
 ## Community resources 
 
 - Join the [#zowe-cli Slack channel](https://openmainframeproject.slack.com/) to ask questions about Zowe CLI and Zowe SDKs, propose new ideas, and interact with the Zowe community.
-- You can join one of the [Zowe CLI squad meetings](https://lists.openmainframeproject.org/g/zowe-dev/calendar) to discuss Zowe SDKs issues and contibute to Zowe SDKs.
+- You can join one of the [Zowe CLI squad meetings](https://zoom-lfx.platform.linuxfoundation.org/meetings/zowe) to discuss Zowe SDKs issues and contibute to Zowe SDKs.
 - Read a series of [blogs about Zowe](https://medium.com/zowe) on Medium to explore use cases, best practices, and more. 
 - Look for discussion on Zowe topics on the [Open Mainframe Project Community Forums](https://community.openmainframeproject.org/c/zowe).

docs/getting-started/install-zowe-sdks.md

@@ -125,16 +125,16 @@ Download and install the packages:
 
 2. Unzip the SDK folder, which contains the packages for each set of functionality (such as z/OS Jobs). Copy each file that you want to install and paste them into your project directory.
 
-3. Install required dependencies, which are included in the bundle. See [Software requirements and dependencies](#software-requirements-and-dependencies) for more information.
+3. Install required dependencies, which are included in the bundle. See [Software requirements and dependencies](#sdk-software-requirements-and-dependencies) for more information.
 
-3. In a command-line window, navigate to your project directory. Issue *one* of the following commands.
+4. In a command-line window, navigate to your project directory. Issue *one* of the following commands.
 
    - To install a Node.js package: `npm install <packageName>.tgz`
    - To install a Python package: `pip install <packageName>.whl`
 
       -`<packageName>`
       The name of the package that you want to install, such as `zos-files-for-zowe-sdk`.
 
-4. Repeat the command for each package that you need.
+5. Repeat the command for each package that you need.
 
     Packages are now installed.

docs/troubleshoot/cli/troubleshoot-cli-credentials.md

@@ -14,7 +14,7 @@ Zowe CLI accepts various methods, or mechanisms, of authentication when communic
 
 However, some services can accept multiple methods of authentication. When multiple methods are provided (in a configuration profile or command) for a service, the CLI follows an *order of precedence* to determine which method to apply.
 
-To find the authentication methods used for different services and their order of precedence, see the table in [Authentication mechanisms](../../extend/extend-cli/cli-devTutorials.md#authentication-mechanisms).
+To find the authentication methods used for different services and their order of precedence, see the table in [Authentication mechanisms](../../extend/extend-cli/cli-authentication-mechanisms.md).
 
 ### PEM certificate files
 

docs/user-guide/_install-cli-via-proxy.md

@@ -64,7 +64,7 @@ You can install Zowe CLI from an online registry via proxy on Windows, macOS, or
 
    - [my-plugin]: The syntax for the plug-in. For example, `@zowe/cics@zowe-v2-lts`.
 ​
-6. **(Optional)** Test the connection to z/OSMF. See [Testing connections to z/OSMF](../user-guide/cli-using-test-zosmf-connection) 
+6. **(Optional)** Test the connection to z/OSMF. See [Testing connections to z/OSMF](../user-guide/_cli-using-test-zosmf-connection) 
 
 7. **(Optional)** Access the Zowe CLI Help (`zowe --help`) or the Zowe CLI Web Help for a complete reference of Zowe CLI.
 ​

docs/user-guide/api-mediation/api-mediation-caching-service.md

@@ -16,7 +16,7 @@ The Caching Service is available only for internal Zowe applications, and is not
 - [Architecture](#architecture)
 - [Storage methods](#storage-methods)
   - [Infinispan](#infinispan-recommended)
-  - [VSAM](#vsam)
+  - [VSAM](#vsam-deprecated)
   - [Redis](#redis)
   - [InMemory](#inmemory)
 - [How to start the service](#how-to-start-the-service)

docs/user-guide/cli-installcli copy.md

@@ -19,12 +19,12 @@ To install Zowe CLI on **z/Linux**, **z/OS UNIX System Services (USS)**, or on a
 
 -  To install Zowe CLI on a z/Linux operating system and you **require** the Secure Credential Store:
    1. Follow the steps in [Configure Secure Credential Store on headless Linux operating systems](./cli-configure-scs-on-headless-linux-os.md).
-   2. Follow the steps in [Install Zowe CLI from npm](#install-zowe-cli-from-npm) or [Install Zowe CLI from a download](#install-zowe-cli-from-a-download).
+   2. Follow the steps in [Install Zowe CLI from npm](#install-zowe-cli-from-npm) or [Install Zowe CLI from a download](#install-zowe-cli-from-a-local-package).
 -  To install Zowe CLI on a z/Linux operating system and you **do not require** the Secure Credential Store:
-   1. Follow the steps in [Install Zowe CLI from npm](#install-zowe-cli-from-npm) or [Install Zowe CLI from a download](#install-zowe-cli-from-a-download).
+   1. Follow the steps in [Install Zowe CLI from npm](#install-zowe-cli-from-npm) or [Install Zowe CLI from a download](#install-zowe-cli-from-a-local-package).
    2. Follow the steps in [Configure Zowe CLI on operating systems where the Secure Credential Store is not available](./cli-configure-cli-on-os-where-scs-unavailable.md).
 -  To install Zowe CLI on a USS system or on an operating system where you **cannot install** the Secure Credential Store:
-   1. Follow the steps in [Install Zowe CLI from npm](#install-zowe-cli-from-npm) or [Install Zowe CLI from a download](#install-zowe-cli-from-a-download).
+   1. Follow the steps in [Install Zowe CLI from npm](#install-zowe-cli-from-npm) or [Install Zowe CLI from a download](#install-zowe-cli-from-a-local-package).
    2. Follow the steps in [Configure Zowe CLI on operating systems where the Secure Credential Store is not available](./cli-configure-cli-on-os-where-scs-unavailable.md).
 
 ### Installation notes
@@ -38,8 +38,6 @@ To install Zowe CLI on **z/Linux**, **z/OS UNIX System Services (USS)**, or on a
 
 ### Prerequisite notes
 
-- If you are installing Zowe CLI on a computer that is running Node.js 16 on a Windows operating system, see [Installing Zowe CLI with Node.js 16 on Windows](../user-guide/cli-install-cli-nodejs-windows.md).
-
 - If you are running NPM version 7 (`npm@7`) or NPM version 8 (`npm@8`) on a Windows operating system, ensure that your computer is connected to the Internet.
 
    Issue the following command ***before*** you install Zowe CLI:

docs/user-guide/cli-using-understanding-core-command-groups.md

@@ -258,7 +258,7 @@ The `zosmf` command group lets you work with Zowe CLI profiles and get general i
 
 With the `zosmf` command group, you can perform the following tasks:
 
-* Verify that your profiles are set up correctly to communicate with z/OSMF on your system. For more information, see [Testing connections to z/OSMF](../user-guide/cli-using-test-zosmf-connection).
+* Verify that your profiles are set up correctly to communicate with z/OSMF on your system. For more information, see [Testing connections to z/OSMF](../user-guide/_cli-using-test-zosmf-connection.md).
 * Get information about the current z/OSMF version, host, port, and plug-ins installed on your system.
 
 :::note

docs/user-guide/cli-using-usingcli.md

@@ -5,11 +5,11 @@ In this section, learn how to use Zowe CLI, including how to connect to the main
 You can use the CLI interactively from a command window on any computer on which it is installed, or run it in a container or automation environment.
 
 :::tip
-Text colors could be difficult to read in some terminals. If this is the case, we suggest either adjusting the terminal settings, or setting the `FORCE_COLOR` [environment variable](../user-guide/cli-configuringcli-ev.md#setting-other-environment-variables) to `0`. For other accessibility options, check the accessibility settings for your operating system or terminal.
+Text colors could be difficult to read in some terminals. If this is the case, we suggest either adjusting the terminal settings, or setting the `FORCE_COLOR` environment variable to `0`. For other accessibility options, check the accessibility settings for your operating system or terminal.
 :::
 
 
-Text colors could be difficult to read in some terminals. If this is the case, we suggest either adjusting the terminal settings, or setting the `FORCE_COLOR` [environment variable](../user-guide/cli-configuringcli-ev.md#setting-other-environment-variables) to `0`. For other accessibility options, check the accessibility settings for your operating system or terminal.
+Text colors could be difficult to read in some terminals. If this is the case, we suggest either adjusting the terminal settings, or setting the `FORCE_COLOR` environment variable to `0`. For other accessibility options, check the accessibility settings for your operating system or terminal.
 
 :::
 

docs/user-guide/configmgr-using.md

@@ -152,15 +152,13 @@ Here are some examples of templates that you can use to simplify your configurat
 
 ### Template functions
 
-
-
 ## Configuration Manager Unix executable
 
 `configmgr` is a file located within `<zowe.runtimeDirectory>/bin/utils` in the Zowe server component runtime for z/OS. If you run it with no arguments, it prints a help command that details what you can do with it. `configmgr` commands focus on providing input files and schemas, and then providing output such as validation success or printing the configuration.
 
 The `configmgr` executable needs the following as input:
 
-- A list of configuration locations. Each location can be a different type such as a Unix file or parmlib from a dataset, but each must be YAML format. Every configuration object in the list must only contain data from the same schema because the list will be merged together into a single configuration object during processing. The rules and syntax are the same as seen in the `config` property of the [Using `zwe` with Configuration Manager section](#using-zwe-with-configuration-manager).
+- A list of configuration locations. Each location can be a different type such as a Unix file or parmlib from a dataset, but each must be YAML format. Every configuration object in the list must only contain data from the same schema because the list will be merged together into a single configuration object during processing. 
 - A list of json-schema Unix files separated by a colon `:`, with the top-level schema being the left-most in the list. The unified configuration will be validated against this top-level schema and any references in the other schema files in the list.
 
 The `configmgr` executable can do the following with the input:

docs/user-guide/obtaining-information-about-api-services.md

@@ -20,8 +20,6 @@ This article provides further detail about each of these use cases.
 
 The _API ID_ uniquely identifies the API in the API ML. The API ID can be used to locate the same APIs that are provided by different service instances. The API developer defines this ID.
 
-For more information about _baseUrl_ or _basePath_, see [Components of a URL](../extend/extend-apiml/api-mediation-components-of-URL).
-
 ## Protecting Service Information
 
 Information about API services is considered sensitive as it contains partial information about the internal topology of the mainframe system. As such, this information should be made accessible only by authorized users and services.

docs/user-guide/systemrequirements-zos.md

@@ -19,7 +19,7 @@ Be sure your z/OS system meets the following prerequisites:
 - z/OS version is in active support, such as Version 2.5, and 3.1
 
   :::note Notes:
-  * z/OS V2.4 reached end of support on 30 September, 2024. For more information, see the [z/OS v2.4 lifecycle details](https://www.ibm.com/support/pages/zos24x-withdrawal-notification).
+  * z/OS V2.4 reached end of support on 30 September, 2024. 
   * z/OS V2.3 reached end of support on 30 September, 2022. For more information, see the [z/OS v2.3 lifecycle details](https://www.ibm.com/support/pages/zos23x-withdrawal-notification).
   :::
 

docs/user-guide/user-roadmap-zowe-cli copy.md

@@ -111,7 +111,7 @@ Zowe CLI extenders can build plug-ins that provide new commands.
 
    If you want to start working with the code immediately, check out this code repository. 
 
-- [**Tutorials**](../extend/extend-cli/cli-devTutorials.md#tutorials)
+- [**Tutorials**](../extend/extend-cli/cli-tutorials.md)
 
    Follow these tutorials to get started working with a sample plug-in.
 
@@ -147,7 +147,7 @@ Zowe CLI extenders can build plug-ins that provide new commands.
 
    Join the #zowe-cli Slack channel to ask questions about Zowe CLI, propose new ideas, and interact with the Zowe community. 
 
-- [**Zowe CLI squad meetings**](https://lists.openmainframeproject.org/g/zowe-dev/calendar)
+- [**Zowe CLI squad meetings**](https://zoom-lfx.platform.linuxfoundation.org/meetings/zowe)
 
    Join Zowe CLI squad meetings to get involved.
 

docs/user-guide/ze-install-verify-your-installation.md

@@ -15,4 +15,4 @@ Verify that Zowe Explorer has been installed successfully by searching data sets
 
     If Zowe Explorer is able to connect with z/OSMF and the user credentials are valid, the filtered data sets display in the **DATA SETS** tree view.
 
-    If there is a problem with the z/OSMF connection and/or user credentials, an error displays. See [Troubleshooting Zowe Explorer](https://docs.zowe.org/stable/troubleshoot/ze/troubleshoot-ze.md) for possible next steps.
+    If there is a problem with the z/OSMF connection and/or user credentials, an error displays. See [Troubleshooting Zowe Explorer](../troubleshoot/ze/troubleshoot-ze.md) for possible next steps.

docs/user-guide/ze-install.md

@@ -27,7 +27,7 @@ Zowe Explorer is a subcomponent of [Zowe](https://zowe.org/home/). The extension
 
 To install Zowe Explorer:
 
-1. Address [the system requirements](#system-requirements).
+1. Address [the system requirements](../getting-started/ZE-system-reqs.md).
 2. Open VS Code, and navigate to the **Extensions** tab on the **Activity Bar**.
 3. Type `Zowe Explorer` in the **Search** field.
 

docs/user-guide/ze-profiles.md

@@ -130,7 +130,7 @@ As a Zowe user, you can leverage the base profile functionality to access multip
 
 If you want to access services through multiple API ML gateways, the same following steps apply. However, you must first edit your configuration file to follow a specific structure.
 
-Review [Accessing services for multiple API ML instances](../user-guide/cli-using-creating-profiles.md#accessing-services-for-multiple-api-ml-instances) to see how profiles are structured in the configuration file.
+Review [Accessing services for multiple API ML instances](../user-guide/cli-using-creating-profiles.md#accessing-services-through-multiple-api-ml-gateways) to see how profiles are structured in the configuration file.
 
 :::
 

docs/whats-new/release-notes/v2_0_0.md

@@ -202,7 +202,6 @@ Zowe CLI contains the following enhancements and changes:
    ```
    zowe config convert-profiles
    ```
-   **Note:** For more information, see [Team configurations](../../user-guide/cli-using-using-team-profiles.md#important-information-about-team-profiles).
 
 #### Zowe CLI Plug-ins
 
@@ -238,7 +237,7 @@ The Nodejs SDK packages were updated to make use of key Zowe V2 features, includ
 Zowe Explorer makes use of Team Configuration and is secure by default. For information about enhancements and bug fixes, see the following changelogs:
 
 - [Zowe Explorer](https://github.com/zowe/zowe-explorer-vscode/blob/next/packages/zowe-explorer/CHANGELOG.md)
-- [Zowe Explorer CICS Extension](https://github.com/zowe/cics-for-zowe-client/blob/next/packages/vsce/CHANGELOG.md)
+- [Zowe Explorer CICS Extension](https://github.com/zowe/cics-for-zowe-client/blob/main/packages/vsce/CHANGELOG.md)
 - [Zowe Explorer FTP Extension](https://github.com/zowe/zowe-explorer-vscode/blob/next/packages/zowe-explorer-ftp-extension/CHANGELOG.md)
 
 ## Bug fixes