create your own config.local.json
adjacent to config.default.json
with something like:
{
"host": "my.mainframe.net",
"username": "ibmuser",
"password": "ibmpass",
"deployDirectory": "/u/users/ibmuser/zowe-native-proto"
}
cd tools/build && npm install && npx tsc
node tools/build/lib init
(once)
node tools/build/lib/main.js deploy-build
node tools/build/lib/main.js deploy-build c/zds.cpp
to deploy one file
On remote system, cd
to deploy dir and run test.sh
(or run zowex
)
Check that your username and password are correct.
For private keys, confirm that you can ssh into the LPAR/zVDT using it.
You should be able to find the startup.mk file in /samples
cp /samples/startup.mk /etc/startup.mk
source: https://www.ibm.com/support/pages/fsum9383-configuration-file-etcstartupmk-not-found
The only way we (DKelosky) knew how to fix this is via SYSVIEW commands.
linklist
linkdef zowex from current
linklist zowex
add CBC.SCCNCMP
linkact zowex
set asid 1
linkupd *
Note 1: You may need to run linkact zowex
after an IPL.
Note 2: You may need to replace *
with your mask character. For example, linkact zowex =