Migrate build tool from package to standalone script

.github/workflows/zos-build.yml

@@ -22,7 +22,7 @@ jobs:
 
       - name: Set up Credentials
         run: |
-          cat << EOF > tools/build/config.local.json
+          cat << EOF > config.local.json
           {
             "host": "${{ secrets.SSH_MARIST_RACF_HOST }}",
             "port": 65522,
@@ -33,11 +33,11 @@ jobs:
           }
           EOF
 
-      - name: Build (Local)
-        run: npm ci && npm run build:tools
+      - name: Install Dependencies
+        run: npm ci --workspaces=false
 
-      - name: Build (z/OS)
-        run: npm run tools:all && npm run tools:artifacts
+      - name: Build on z/OS
+        run: npm run z:all
 
       - uses: actions/upload-artifact@v4
         with:

.gitignore

@@ -8,9 +8,11 @@ listings
 node_modules
 out
 typedoc
+zowe-native-proto-package
 
 # Files
 .DS_Store
+config.*.json
 tsconfig.tsbuildinfo
 zowe.config.json
 zowe.schema.json

README.md

@@ -4,7 +4,7 @@
 
 Run `npm install` to install project dependencies.
 
-In the `tools/build` folder, create your own `config.local.json` adjacent to `config.default.jsonc` with something like:
+Create your own `config.local.json` adjacent to `config.default.jsonc` with something like:
 
 ```json
 {
@@ -21,17 +21,16 @@ In the `tools/build` folder, create your own `config.local.json` adjacent to `co
 
 ### z/OS
 
-- `npm run tools:build` - build local tool to manage z/OS builds (only needed once)
-- `npm run tools:init` - create project folder structure on z/OS (only needed once)
-- `npm run tools:deploy` - deploy source files to z/OS
-  - **Tip:** You can deploy just one file or directory like this: `npm run tools:deploy c/zowex.cpp`
-- `npm run tools:build` - build native binaries on z/OS
-  - **Tip:** You can deploy and build at the same time with `npm run tools:deploy:build`
+- `npm run z:init` - create project folder structure on z/OS (only needed once)
+- `npm run z:deploy` - deploy source files to z/OS
+  - **Tip:** You can deploy just one file or directory like this: `npm run z:deploy c/zowex.cpp`
+- `npm run z:build` - build native binaries on z/OS
+  - **Tip:** You can deploy and build at the same time with `npm run z:deploy:build`
 - `npm run watch:native` - detect and upload changes to native code
 
 ## Client
 
-- `npm run tools:artifacts` - download binaries to package with clients
+- `npm run z:artifacts` - download binaries to package with clients
 - `npm run build` - build all projects in the `packages` folder
   - **Tip:** You can run incremental builds with `npm run watch:client` for client code only, or `npm run watch` at the root to watch all code
 - `npm run package` - create CLI and VSCE artifacts in `dist` folder

native/README.md

@@ -5,7 +5,7 @@
 To create a C header from an HLASM DSECT:
 
 - create a `.s` file in `asmchdr` folder, e.g. `asasymbp.s`
-- upload, e.g. `npm run tools:deploy asmchdr/asasymbp.s`
+- upload, e.g. `npm run z:deploy asmchdr/asasymbp.s`
 - allocate output adata data set if none exists, e.g. `zowex data-set create-adata <hlq>.adata`
 - allocate output chdr data set if none exists, e.g. `zowex data-set create-vb <hlq>.chdr`
 - build `.s` file, e.g. `as -madata --gadata="//'<hlq>.USER(ASASYMBP)'" asasymbp.s`
@@ -24,4 +24,4 @@ To create a C header from an HLASM DSECT:
 ## Runtime options (recovery)
 
 - `_CEE_RUNOPTS` https://www.ibm.com/docs/en/zos/3.1.0?topic=options-how-specify-runtime
-- `TRAP(ON,NOSPIE)` https://www.ibm.com/docs/en/zos/3.1.0?topic=ulero-trap
+- `TRAP(ON,NOSPIE)` https://www.ibm.com/docs/en/zos/3.1.0?topic=ulero-trap