opening of cics profile gives an axios error

[kraabrsg]

Describe the bug

Hi,

when installing zowe explorer and zowe explorer for cics we copy the zowe files from our own extension to the workspace folder (where the multiroot workspace file is located)

zowe.config.user.json and zowe.schema.json

we use the zowe sdk for file operations with our own extesnsion (tso and zosmf) and we also installed the zowe explorer to give the user the opportunity to browse files and jobs etc.

Now we want todo the same with cics.

zowe.config.user.json

{
    "$schema": "./zowe.schema.json",
    "profiles": {
        "entw-zosmf": {
            "type": "zosmf",
            "properties": {
                "port": 443,
                "host": "zosmf-myaddi.at",
                "encoding": "1141",
                "user": "${MYUSER}",
                "password": "${MYPASS}"
            },
            "secure": []
        },
        "entw-tso": {
            "type": "tso",
            "properties": {
                "account": "ACCC",
                "characterSet": "695",
                "codePage": "1141",
                "logonProcedure": "LOGONPROC"
            },
            "secure": []
        },
        "ssh": {
            "type": "ssh",
            "properties": {
                "port": 22
            },
            "secure": []
        },
        "base": {
            "type": "base",
            "properties": {
                "host": "zosmf-myaddi.at",
                "rejectUnauthorized": false
            },
            "secure": []
        },
        "cics": {
		    "type": "cics",
            "properties": { 
				"host": "1.1.1.1",
				"port":  58104,
                "user": "${MYUSER}",
                "password": "${MYPASS}",
				"regionName": "XXXX",
				"cicsPlex": "YYYY",
				"rejectUnauthorized": false
			},
            "secure": []
		}
    },
    "defaults": {
        "zosmf": "entw-zosmf",
        "tso": "entw-tso",
        "ssh": "ssh",
        "base": "base",
        "cics": "cics"
    },
    "autoStore": true
}

zowe.schema.json

zowe log at startup

Zowe Explorer 3.0.3
This log file can be found at c:\mypath\vscode\data\extensions\zowe.vscode-extension-for-zowe-3.0.3
Zowe Explorer log level: DEBUG
[2024/11/21 13:16:16] [DEBUG] Reading imperative.json Credential Manager.
 {
  "overrides": {
    "CredentialManager": false
  }
}

[2024/11/21 13:16:16] [DEBUG] Updating imperative.json Credential Manager to @zowe/cli.
{
  "overrides": {
    "CredentialManager": false
  }
}
[2024/11/21 13:16:16] [INFO] Zowe explorer profiles are being set as unsecured.
[2024/11/21 13:16:16] [INFO] Zowe home directory is located at C:\Users\myuser\.zowe
[2024/11/21 13:16:16] [INFO] No custom credential managers found, using the default instead.
[2024/11/21 13:16:16] [INFO] Zowe explorer profiles are being set as unsecured.
[2024/11/21 13:16:16] [INFO] Zowe Explorer is using the team configuration file "zowe.config.json"
[2024/11/21 13:16:16] [DEBUG] Summary of team configuration files considered for Zowe Explorer: ["Path: C:\\mypath2\\zowe.config.user.json: Found, with the following defaults:{\"zosmf\":\"entw-zosmf\",\"tso\":\"entw-tso\",\"ssh\":\"ssh\",\"base\":\"base\",\"cics\":\"cics\"} ","Path: C:\\mypath3\\zowe.config.json: Not available ","Path: C:\\Users\\myuser\\.zowe\\zowe.config.user.json: Not available ","Path: C:\\Users\\myuser\\.zowe\\zowe.config.json: Not available "]
[2024/11/21 13:16:16] [INFO] Zowe Profiles initialized successfully.
[2024/11/21 13:16:16] [INFO] No custom credential managers found, using the default instead.
[2024/11/21 13:16:16] [INFO] Zowe explorer profiles are being set as unsecured.
[2024/11/21 13:16:17] [DEBUG] Initializing profiles with data set favorites.
[2024/11/21 13:16:17] [DEBUG] No data set favorites found.
[2024/11/21 13:16:17] [DEBUG] Initializing profiles with USS favorites.
[2024/11/21 13:16:17] [DEBUG] No USS favorites found.
[2024/11/21 13:16:17] [DEBUG] Initializing profiles with jobs favorites.
[2024/11/21 13:16:17] [DEBUG] No jobs favorites found.
[2024/11/21 13:16:20] [INFO] No custom credential managers found, using the default instead.
[2024/11/21 13:16:20] [INFO] Zowe explorer profiles are being set as unsecured.
[2024/11/21 13:17:12] [INFO] No custom credential managers found, using the default instead.
[2024/11/21 13:17:12] [INFO] Zowe explorer profiles are being set as unsecured.
[2024/11/21 13:17:12] [INFO] Zowe Explorer has activated successfully.
[2024/11/21 13:17:13] [INFO] No custom credential managers found, using the default instead.
[2024/11/21 13:17:13] [INFO] Zowe explorer profiles are being set as unsecured.

Expected and actual results

Failure when trying to open the cics profile and also the creation (after filing the connection detials no profile is showing up) / delete update(changing cics details does not reflect in the json file) does not work

Describe your environment

node: 20.11.1
npm: 10.2.4
win 10

no zowe cli plugins installed

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.

[AndrewTwydell]

Hi @kraabrsg, there's a protocol option not specified in your profile that may allow you to connect. In your Axios error, it says Protocol Undefined and it's not in your config file, so you could try adding that in ("http" or "https").

"cics": {
    "type": "cics",
    "properties": {
        "protocol": "http"     <-- Something like this
        "host": "1.1.1.1",
        "port":  58104,
        "user": "${MYUSER}",
        "password": "${MYPASS}",
        "regionName": "XXXX",
        "cicsPlex": "YYYY",
        "rejectUnauthorized": false
    },
    "secure": []
}

I would like the protocol to default to HTTPS if not specified so I'll look into that behaviour in the meantime.

[kraabrsg]

Hi @AndrewTwydell thanks for spotting this, when doing it with "protocol": "http" it seems to work, why everything is 0 is another topic (wrong settings etc.). It seems that https is not supported at our site because it throws an
Error: write EPROTO HOST:PORT

[AndrewTwydell]

Great I'm glad you're able to solve the problem! 🙂

Out of interest, if others see this issue, are you able to provide info about which version of TLS your test system uses? It's possible you're using a version of NodeJS that only supports TLS 1.3 but your test system is lower? It's a possibility, but would help us diagnose and error-handle these issues in a clearer way 🙂