search

zowe / cics-for-zowe-client

Monorepo for all CICS related APIs and Apps built by Zowe Clients
https://www.zowe.org/
Eclipse Public License 2.0
1 stars 3 forks source link

VSCode - cannot connect to CICS #35

Open EdwardMcCarthy opened 1 year ago

EdwardMcCarthy commented 1 year ago

Have set up the CICS plugin in VScode, defined connection to a CICS WUI server, but it is not able to connect, I get an icon like red "no entry" sign

I can connect to the CICS WUI all ok from CICS SM Explorer in zOS Explorer on the same PC, so I know I have the correct settings to use to connect

Target CICS is V6.1 on zOS 2.5

VSCode is latest download as I set this up all new in last few days

Not using SSL/TLS to connect

No msgs in CICS or zOS syslog

Any advice on how to find out why cannot connect from VSCode ?

github-actions[bot] commented 4 months 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.

zFernand0 commented 4 months ago

Hello @EdwardMcCarthy, I wasn't able to reproduce the problem with or without TLS 😢

A lot has changed in the CICS VSCE, could you please try testing with the latest version of the CICS VSCE?

Joe-Winchester commented 3 months ago

Hi @EdwardMcCarthy , are you able to connect with the Zowe CICS CLI ? A good first command I use it zowe cics get resource CICSTask | wc -l which does a count of the CICS tasks in the region, e.g.

image

If this fails to connect then something is awry with the connection and/or the Zowe classes that do the underlying connection. Hopefully this will be shown in the error that comes back so it'd be great to have that info. If the CLI connects and the Zowe Explorer doesn't then this is a defect. We did have an issue a while back where we couldn't work with http connections that had no authentication defined, and if yours has no authentication defined on the TCP/IP service it's possible you ran into that issue. Can you re-try please as we did release a fix for that which possibly means it no longer occurs for you, and if it does occur can you check whether auth is actually turned on the region. The easiest way to test this would be to put an invalid user ID in your CLI connection profile and see if you're still able to connect with the CLI and unable to connect in VS Code. Cheers !