-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Corrects zos_data_set default record format FB breaking VSAM #647
Corrects zos_data_set default record format FB breaking VSAM #647
Conversation
Signed-off-by: ddimatos <[email protected]>
… not Signed-off-by: ddimatos <[email protected]>
Signed-off-by: ddimatos <[email protected]>
Signed-off-by: ddimatos <[email protected]>
Signed-off-by: ddimatos <[email protected]>
Passed locally:
result: |
Signed-off-by: ddimatos <[email protected]>
Although this solution does work , longer term enhancing our better arg parsers mutual exclusive capabilities such that it can be instructed when what is seeing is a result of a default value and know when it's permitted and when it's not, eg an exemption list also be provided. Such work needs appropriate planning because all modules use the parser |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
SUMMARY
This addresses issues #638 and #646 such that when the default value for record format FB was set it was was also set for VSAM and this would break VSAM data set creation. It did not make sense to not have a default so it was added back after going through the changes enforced by ansible 2.14. This code adds the correcting behavior.
ISSUE TYPE
COMPONENT NAME
See git issue #646 for more detals
ADDITIONAL INFORMATION