Fix for REXX properties

[M-DLB]

Fixing issue #548
The PR adds some checks and use defaults values if these properties are not set. They are set by default in the REXX.properties file of application-conf folder.

[dennis-behm]

Hi @M-DLB,

these updates feel odd to me.

zAppBuild has the following capabilities:

• Enforce the presence of build properties via the rexx_requiredBuildProperties list in build-conf. Looks like that these properties are missing there.
• and the capability to set defaults - probably via the central applicationDefaultPropFiles setting in build.properties if the customer is looking for centrally controlling it.

Any specific reasoning to hard-code the defaults in the script itself?

[M-DLB]

You're right it's odd. It is just a workaround for people who are trying to use zAppBuild to build REXX programs, without having taken REXX.properties from samples/application-conf/ and put that in the application's application-conf.
I'm happy to kill this PR, as long as we accept that we have the same problem with all our other scripts. For instance Cobol.properties in build-conf doesn't require cobol_compileMaxRC, cobol_linkEditMaxRC and cobol_linkEdit which are set in Cobol.properties of application-conf, and Cobol.groovy is using them.
What do you think?

[dennis-behm]

@M-DLB

You're right it's odd. It is just a workaround for people who are trying to use zAppBuild to build REXX programs, without having taken REXX.properties from samples/application-conf/ and put that in the application's application-conf.

Let's see this as a broader initiative to reconcile how properties are set. It is time to make use of applicationDefaultPropFiles and reduce the settings in application-conf, and review the required build properties