Hi Felix,

Can you confirm the exact user interface that you are using? For example, ZMF4ECL, ZDD, the ZMF Explorer, etc? Or are you experiencing problems with multiple user interfaces? 

Many thanks,

Steve

Hi Steven,

Yes, we are using the ZMF Explorer. In the Zowe profiles there is the "encoding" property, but on the zmf profile the option doesn't exist. So I wanted to ask if there is a way to enter the correct encoding, or if this will be implemented.

Thanks,
Felix

Hi Felix,

Many thanks for the confirmation. I will follow up and ask the relevant people to respond on this question.

Best regards,

Steve

Hi Felix,

Currently, at this time we do not have a way to specify encoding in the ZMF profile. We will add this to our backlog and consider for a future release. Appreciate the feedback!

Jimmy  

Hi Felix,

I started investigating this request and am not sure I understand the problem, please bear with me.

Component data is saved by ZMF using the CCSID specified in the start up parameters (in our case this is CCSID=01047). Can you confirm which CCSID you are using in your ZMF stc ?

The ZMF REST api calls which the relevant services use to extract data from, and supply data to, ZMF perform a conversion from the target ZMF CCSID to utf-8 at the desktop 'end'. So, there shouldn't be any problem with special characters ?   But I am probably misunderstanding the issue.

Would it be possible to provide examples of what a source component looks like both when viewed via ISPF in a ZMF staging library - and again when the same source is presented by the ZMF explorer vscode extension ?

On the ISPF side, could we see an example of one or more characters that are not being handled correctly viewed with 'hex on' please ?

Thanks

All the best - Steve 

------------------------------
Steve Downes
Mr
Rocket Internal - All Brands
------------------------------

Further to this (and to explain where we are coming from, hence the request for more information)...

The encoding parameter in base zowe commands allows the zowe code to perform the correct translation when downloading data from the mainframe. This may be needed because zowe itself knows nothing about the codepage used to store data on the mainframe.

On the other hand, ZMF knows exactly which codepage was used to store ZMF data (this is the CCSID start-up parameter which defaults to 1047). So we don't need any kind of encoding parameter to let the zowe zmf cli commands know which codepage was used to store the data by ZMF - we already know it.

All the best - Steve