Use Zowe encoding for DSN data#10
Merged
Merged
Conversation
Tannex
marked this pull request as ready for review
July 15, 2026 20:33
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
encodingproperty through base, nested profile, team/user layer, andZOWE_OPT_ENCODINGprecedence--data-dsndecoding when-codepageis not explicitly supplied-codepage, thecp037fallback, and lazy Zowe loading for local inputsBranch relationship
This branch is synchronized with
mainat merge commit33ec3ab, which contains PR #9. Merge commit31281b7resolves the former stacked-branch conflicts, so this PR now shows only the encoding-specific changes.Validation
Rerun on head
31281b7:go test ./...go test -race ./...go vet ./...