Download all-members replaces special characters

[Morora69]

Describe the bug

Hi,

I am using Zowe cli to download all members from multiple PDS one by one via Z/OS MF.
All of the PDS names are hardcoded in a script.
Some of the members of these PDS contain special characters (such as 'é' and '°').

The issue is that I download the members every night in a folder that is created before the download happens (and therefore clean).
Randomly, on some 1 or 2 lines in very few files (3 out of 1500), the special characters are downloaded as unknown characters and the next day they'll be downloaded fine.

The files impacted are not always the same but some come more frequently than others.
We've cheked that the files are correct on the mainframe and it is the case, no difference with these characters than the others on the rest of the file.
I tried to open the files on different text editors to try and change the charset to see if it would make a difference and it is not the case.

Expected and actual results

Details about the behavior:

1. Command issued: zowe zos-files download all-members $SourcePDS -d $DestinationFolder --extenstion $Extension (where extension is .cbl or .bms) --encoding IBM-1147 (Yes, it's the right one on our config) --host $ZOSMFHost --port $ZOSMFPort --user $user --pass $pwd
2. Expected results: The file as it is on the mainframe with all special characters fine for example :
   "PROCESSING TABLE N° 168"
3. Actual results:
   "PROCESSING TABLE N?? 168" where the '?' are the unrecognized char symbol.

Describe your environment

• Zowe CLI version installed (run command zowe --version): 7.20.1
• Installed plug-ins and their version numbers (run command zowe plugins list --short): No plugins
• Node.js and NPM versions installed (run node --version, npm --version): v20.11.1
• Operating system and version: Windows Server 2019
• Shell/terminal (bash, cmd, powershell, etc...): Powershell
• For more information, see Gathering information to troubleshoot Zowe CLI

I'd be happy to give more details if needed or help in any way.
Thanks !

[github-actions]

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.