ZWEGEN00 split CONFIG entry over multiple lines #3873
Conversation
Signed-off-by: 1000TurquoisePogs <[email protected]>
|
build 5491 SUCCEEDED. |
zowe-robot
had a problem deploying
to
marist-zzow07
GitHub Actions
Failure
|
Test workflow 4833 is started. |
Signed-off-by: Martin Zeithaml <[email protected]>
|
build 5495 SUCCEEDED. |
Signed-off-by: Martin Zeithaml <[email protected]>
|
build 5496 SUCCEEDED. |
|
Test workflow 4839 is started. |
|
Test workflow 4840 is started. |
Signed-off-by: 1000TurquoisePogs <[email protected]>
Signed-off-by: 1000TurquoisePogs <[email protected]>
|
Merge back into main branch |
|
build 5497 SUCCEEDED. |
|
build 5498 SUCCEEDED. |
* WIP to have ZWEGEN00 split CONFIG entry over multiple lines. Signed-off-by: 1000TurquoisePogs <[email protected]> * Update CONFIG= for launcher Signed-off-by: Martin Zeithaml <[email protected]> * Simplify macro Signed-off-by: Martin Zeithaml <[email protected]> * Update SMPMCS.txt Signed-off-by: 1000TurquoisePogs <[email protected]> * Update SMPMCS.txt Signed-off-by: 1000TurquoisePogs <[email protected]> --------- Signed-off-by: 1000TurquoisePogs <[email protected]> Signed-off-by: Martin Zeithaml <[email protected]> Co-authored-by: Martin Zeithaml <[email protected]>
Current JCL branch can leave CONFIG entry of ZWESLSTC without template resolution if the configuration length exceeds jcl line length.
This PR attempts to correct it by using some rexx to process ZWESLSTC deliberately for splitting the config the way we want.
CONFIG= works like this
one entry:
CONFIG=FILE(/foo)
multiple entries:
CONFIG=FILE(/foo):
FILE(/foo2):
FILE(/foo3)
Additionally, I saw the opportunity to force "defaults.yaml" into the config reading.
It should not end up in the CONFIG= output, but should be considered during the template resolution.
To add it, I detect runtimeDirectory via finding that in the first line of the schema entries, since they must be in the runtime directory.