Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Dataset/files access via ZOWE Explorer don't honor codepage settings.

See original GitHub issue

Since the update of all profiles to v2 structure the codepage property has no more effect on the dataset representation in VScode. The conversion of datasets/members seems to be done with IBM-1047. This behaviour prevents us to use Zowe Explorer v2 because all datasets in our site were encoded with IBM-1141. This was no problem with ZOWE Explorer V1.*.

my zowe.config.json looks like:

{
    "$schema": "./zowe.schema.json",
    "profiles": {
        "zosmf": {
            "type": "zosmf",
            "properties": {
                "port": 443,
                "codePage": "1141",
            },
            "secure": []
        },
        "tso": {
            "type": "tso",
            "properties": {
                "account": "",
                "codePage": "1141",
                "logonProcedure": "IZUFPROC"
            },
            "secure": []
        },
        "ssh": {
            "type": "ssh",
            "properties": {
                "port": 22
            },
            "secure": []
        },
        "base": {
            "type": "base",
            "properties": {
                "host": "zosmf.enterprise.de",
                "codePage": "1141",
                "rejectUnauthorized": true
            },
            "secure": [
                "user",
                "password"
            ]
        }
    },
    "defaults": {
        "zosmf": "zosmf",
        "tso": "tso",
        "ssh": "ssh",
        "base": "base"
    },
    "autoStore": true
}

OS: Windows 10
Zowe Explorer Version: 2.0.1
Zowe CLI Version: 7.0.2

Kind regards, Björn