Merge branch 'master' into certificate-config-minor-changes

.github/dco.yml

@@ -0,0 +1,3 @@
+allowRemediationCommits:
+  individual: true
+  thirdParty: true

dco_signoffs/Lobhas-Paradkar-docs-site.txt

@@ -0,0 +1,3 @@
+I, Lobhas Paradkar, hereby sign-off-by all of my past commits to this repo subject to the Developer Certificate of Origin (DCO), Version 1.1. 
+In the past I have used email: [email protected]
+41febb79fe07ae4670a746301b7215740e65a3c7 updated release notes 2.12 (#3203)

dco_signoffs/Sergei-Kurnevich-docs-site.txt

@@ -0,0 +1,3 @@
+I, Sergei Kurnevich, hereby sign-off-by all of my past commits to this repo subject to the Developer Certificate of Origin (DCO), Version 1.1. In the past I have used emails: [email protected]
+
+3b9ecfb727b8b0081cea8a3a395d278c1c26de42 ZIS load module typo fix (#3258)

docs/troubleshoot/launcher/launcher-error-codes.md

@@ -115,4 +115,27 @@ The following error message codes may appear on Zowe Launcher SYSPRINT. Use the
 
   **Action:**
 
-  Validate the format of Zowe configuration file. It should be a valid YAML file following specifications defined in https://yaml.org/.
+  Validate the format of Zowe configuration file. It should be a valid YAML file following specifications defined in https://yaml.org/.
+
+### ZWEL0073E
+
+  Launcher Could not load schemas, status=5
+
+  **Reason:**
+
+  The Zowe Launcher was able to locate the runtime directory, but unable to find the /schemas directory.  
+
+  **Action:**
+
+  Locate the runtimeDirectory from the `zowe.yaml` variable `runtimeDirectory: "<PATH_TO_RUNTIME>"`.
+
+  Check that there is a `<PATH_TO_RUNTIME>/schemas` directory. This should contain four `.json` files shown below. 
+
+  ```
+  manifest-schema.json
+  server-common-json
+  trivial-component-schema.json
+  zowe-yaml-schema.json
+  ```
+
+  On ocassion the error occurs because the `runtimeDirectory` is pointing to a valid directory, but one which doesn't contain a valid Zowe runtime environment is one of the first failures during a Zowe launch.