Validate System Datasets #471
Conversation
Signed-off-by: Dennis Behm <dennis.behm@de.ibm.com>
Signed-off-by: Dennis Behm <dennis.behm@de.ibm.com>
build.groovy
Outdated
| @@ -268,14 +269,15 @@ options: | |||
| cli.r(longOpt:'reset', 'Deletes the dependency collections and build result group from the MetadataStore') | |||
| cli.v(longOpt:'verbose', 'Flag to turn on script trace') | |||
| cli.pv(longOpt:'preview', 'Supplemental flag indicating to run build in preview mode without processing the execute commands') | |||
| cli.cds(longOpt:'checkSystemDatasets', 'Optional flag to validate the presense of the defined system datasets. ') | |||
There was a problem hiding this comment.
Shouldn't it be -csd as the first letters of "Check System Datasets"?
There was a problem hiding this comment.
@M-DLB - CSD is already a known term from CICS. Should we rename the long option to checkDatasets instead ?
I added the system datasets, because it is really just the system datasets that can be validated in advance and not the additional build datasets that are created during build time.
There was a problem hiding this comment.
Let's call it checkDatasets then, so -cd should be fine :)
There was a problem hiding this comment.
Hi,
Or -ivp (Installation Verification Procedure)?
Not limited to check system data sets but validate anything need to be checked.
Could be enhenced / extended by site customisation.
Signed-off-by: Dennis Behm <dennis.behm@de.ibm.com>
This is a new feature helping during the setup phase of zAppBuild to validate that the defined system datasets in
datasets.propertiesare correctly configured and present on the system where the build is performed.