Open johnpdscott opened 1 month ago
Thank you for creating a bug report. We will investigate the bug and evaluate its impact on the product. If you haven't already, please ensure you have provided steps to reproduce the bug and as much context as possible.
Hello, I have a similar issue with Zowe Explorer v2.18.0. I use code page 1147. On mainframe my member is named ".MELGN4E" for example, but on VSCODE on the tree explorer I see "ÚMELGN4E"
This issue is due to a discrepancy in the z/OSMF REST APIs where the encoding is respected for data set contents, but not when listing data sets.
We have filed an issue on IBM Ideas to support a custom encoding when listing data sets and data set members: https://ideas.ibm.com/ideas/ZOS-I-4279
It is marked for future consideration, but please feel free to "thumbs up" the idea to express your interest. Note that you will need to sign up or log in with an IBMid to access this page.
I found I need to specify "encoding": 285 so that £ characters are not changed when edited using zowe explorer. However, a £ character used in a DATA SET name or member name is being presented as $ when using zowe explorer or when returned from a TSO command issued by zowe explorer
Steps to reproduce the behavior: In 3270 create a dataset or member that contains the character £ e.g. MY.DATASET£ or MEMBER£
Connect using VSCODE ZOWE EXPLORER My profile contains "encoding": 285
List the dataset or member under DATA SETS or via command issued from VSCODE Right click on the zosmf profile and issue TSO command listc or issue zowe command in terminal zowe zos-tso issue command "listc"
Expected behavior Expect the character to be displayed the same as it is on mainframe using ISPF or TSO
Screenshots
Desktop (please complete the following information):