add zowe auxiliary address space content

Signed-off-by: Andrew Jandacek <[email protected]>
zowe · Oct 19, 2023 · 5b37fd1 · 5b37fd1
1 parent 886766c
commit 5b37fd1
Show file tree

Hide file tree

Showing 3 changed files with 16 additions and 5 deletions.
diff --git a/docs/user-guide/configure-xmem-server.md b/docs/user-guide/configure-xmem-server.md
@@ -22,7 +22,8 @@ To install and configure the cross memory server, it is necessary to define APF-
 - [Zowe auxiliary service](#zowe-auxiliary-service)
     - [When to configure the auxiliary service](#when-to-configure-the-auxiliary-service)
     - [Installing the auxiliary service](#installing-the-auxiliary-service)
-
+      - [Zowe Auxiliary Address space](#zowe-auxiliary-address-space)
+
 ## PDS sample library and PDSE load library
 
 The cross memory server runtime artifacts, the JCL for the started tasks, the parmlib, and members containing sample configuration commands are found in the `SZWESAMP` PDS sample library.  
@@ -195,6 +196,18 @@ To install the auxiliary service to allow it to run, you take similar steps to i
 - The PDSE load library `SZWEAUTH`is APF-authorized, or load module `ZWESAUX` is copied to an existing APF Auth LoadLib.
 - The load module `ZWESAUX` must run in key 4 and be non-swappable by adding a PPT entry to the SCHEDxx member of the system PARMLIB `PPT PGMNAME(ZWESAUX) KEY(4) NOSWAP`.
 
-**Important!**
+#### Zowe Auxiliary Address space
+
+The cross memory server runs as a started task `ZWESISTC` that uses the load module `ZWESIS01`.
+
+In some use cases, the Zowe cross memory server has to spawn child address spaces, which are known as auxiliary (AUX) address spaces.  The auxiliary address spaces run as the started task `ZWESASTC` using the load module `ZWESAUX` and are started, controlled, and stopped by the cross memory server.  
+
+An example of when an auxiliary address space is used is for a system service that requires supervisor state but cannot run in cross-memory mode. The service can be run in an AUX address space which is invoked by the Cross Memory Server acting as a proxy for unauthorized users of the service. 
+
+Do not install the Zowe auxiliary address space unless a Zowe extension product's installation guide explicitly asks for it to be done.  This will occur if the extension product requires services of Zowe that cannot be performed by the cross memory server and an auxiliary address space needs to be started.  
+
+A default installation of Zowe does not require auxiliary address spaces to be configured.
 
+:::important
 The cross memory `ZWESISTC` task starts and stops the `ZWESASTC` task as needed. **Do not start the `ZWESASTC` task manually.**
+:::
diff --git a/docs/user-guide/configuring-security.md b/docs/user-guide/configuring-security.md
@@ -7,8 +7,7 @@ During the initial installation of Zowe server-side components, it is necessary
 
 ## Validate and re-run `zwe init` commands
 
-:::note
-During installation, the system programmer customizes values in the zowe.yaml file. However, due to insufficient permissions of the system programmer, the `zwe init security` command is likely to fail. Consult with your security administrator to review your `ZWESECUR` job content so that your security adminstrator can re-submit this command.
+:::note During installation, the system programmer customizes values in the zowe.yaml file. However, due to insufficient permissions of the system programmer, the `zwe init security` command is likely to fail. Consult with your security administrator to review your `ZWESECUR` job content so that your security adminstrator can re-submit this command.
 :::
 
 ## Initialize Zowe security configurations

diff --git a/sidebars.js b/sidebars.js
@@ -93,7 +93,6 @@ module.exports = {
           label: "Installing convenience, SMP/E, and PSWI builds",
           items: [
             "user-guide/zos-components-installation-checklist",
-            "user-guide/zos-components-installation-checklist-dev",
             {
               type: "category",
               label: "Planning",