Other build scripts have been using "-DNEW_CAA_LOCATIONS=1" but not configmgr.
I believe this should allow configmgr to work with heappools being on, without any drawbacks.
How to test:
Before:
_CEE_RUNOPTS="HEAPPOOLS(ON),HEAPPOOLS64(ON)" ./configmgr -h
CEE3204S The system detected a protection exception (System Completion Code=0C4).
From compile unit ZZOW08:/ZOWE/tmp/pax-packaging-configmgr-1723644907470/content/build/../c/logging.c at entry point logConfigureDestination at statement 436 at compile unit offset +000000003C6B6C56 at entry offset +00000000000001CE at address
000000003C6B6C56.
Segmentation fault
After:
_CEE_RUNOPTS="HEAPPOOLS(ON),HEAPPOOLS64(ON)" ./configmgr -h
*** unknown option *** '-h'
Usage:
configmgr [options] <command> <args>
options
-h : show help
-script <path> : quickjs-compatible javascript file to run with configmgr utilities
-t <level> : enable tracing with level from 1-3
-o <outStream> : OUT|ERR , ERR is default
-s <path:path...> : <topSchema>(:<referencedSchema)+
-w <path> : workspace directory
-c : compact output for jq and extract commands
-r : raw string output for jq and extract commands
-m <memberName> : member name to find the zowe config in each PARMLIBs specified
-p <configPath> : list of colon-separated configPathElements - see below
commands:
extract <jsonPath> : prints value to stdout
validate : just loads and validates merged configuration
env <outEnvPath> : prints merged configuration to a file as a list of environment vars
configPathElement:
PARMLIB(datasetName) - a library that can contain config data
FILE(filename) - the name of a file containing Yaml
PARMLIBS - all PARMLIBS that are defined to this running Program in ZOS, nothing if not on ZOS
Other build scripts have been using "-DNEW_CAA_LOCATIONS=1" but not configmgr. I believe this should allow configmgr to work with heappools being on, without any drawbacks.
How to test:
Before:
After: