Add ability to download/view/upload Datasets/Members/USS files in non-standard codepage

[awharn]

Is your feature request related to a problem? Please describe.

Sometimes, I have datasets, members, and untagged USS files that are not in my default 1047 codepage, and I am frustrated when I need to change my configuration to specify the encoding, then immediately remove it once I download my respective file.

Describe the solution you'd like

The ability to right click a dataset or USS file and download/open in a different codepage, and upload with the same codepage.

Describe alternatives you've considered

• Modify the configuration file, reload VSCode, download the dataset/member/USS file, remove the configuration file modification, reload VSCode again, and resume work
• Create a second profile targeting the same system with a different codepage

Additional context

[github-actions]

Thank you for raising this enhancement request.
The community has 90 days to vote on it.
If the enhancement receives at least 10 upvotes, it is added to our development backlog.
If it receives fewer votes, the issue is closed.

[FALLAI-Denis]

Hi @awharn

See also:

• Not all mvs data sets necessarily use the same ccsid #1589
• zos-files - Apply rules defined by .zosattributes to all dataset and uss file transfers zowe-cli#1463
• Failure to respect USS file tagging zowe-cli#1431

For USS files, Zowe Explorer should/must use the tagging declared on the file:

• no tag: IBM-1047 encoding apply
• presence of a tag: encoding declared by the tag apply, (to see if the auto-convert option must also be taken into consideration)

For datasets, Zowe Explorer should/must allow the user to specify the encoding when downloading and uploadling the dataset.
If the data set has been previously downloaded the uploading should be done with the same encoding as the downloading, but to see if it is necessary to authorize a change of encoding between downloading and uploading.

Zowe Explorer should also take into account the presence of a .zosattributes file or a .gitattributes file if the workspace is a cloned git repository.

[t1m0thyj]

Related to Editing a USS file that has an existing encoding overwrites it with a binary tag rather than keep the existing encoding #2576

[AnthonyGiorgio]

This behavior prevents me from editing files that are in ASCII format via zowe. The z/OS Open Tools team has their git repo setup to clone in ASCII format, meaning that I can't use zowe to work on that code directly.