Remove unnecessary tree nodes

[AndrewTwydell]

If SMSS system is in use, there is an unneeded tree with the Region Applid.

If the system is an SMSS system, append the region applid to the profile node label and show programs, transactions and localfiles directly underneath.

[github-actions[bot]]

Thank you for raising this enhancement request. The community has 90 days to vote on it. If the enhancement receives at least 5 upvotes, it is added to our development backlog. If it receives fewer votes, the issue is closed.

[zFernand0]

Hey @Joe-Winchester, Thanks a lot for today's conversation with a few members of the team. I forgot to get to this issue during said call, my apologies for that.

In your own words,

1. Could you briefly explain what it means for a customer to be on a single server setup?
2. How can we detect (via CMCI) that this region is not managed by CICSPlex SM?

More details about CICS SMSS:

• https://www.ibm.com/docs/en/cics-ts/6.1?topic=topology-what-is-single-cics-region

[zFernand0]

Hey Joe, I believe that your comment on the other issue (https://github.com/zowe/cics-for-zowe-client/issues/70#issuecomment-2017840392) helped answer some of the questions.

There seems to be something in place that helps us to determine whether the session is configured to connect to a CICSPlex (other than just the cics-plex property in a cics profile).

That being said, I believe the request in this issue is to simply avoid showing the region name/dropdown whenever there is only one region that this session can communicate with.

[Joe-Winchester]

Hi @zFernand0 ,

Yes I think the original request was that if there is a single region then there is no need to show a node in the tree as it's implied by the connection.

        "cics_3b": {
            "type": "cics",
            "properties": {
                "host": "xxxxx.hursley.ibm.com",
                "port": 10887,
                "rejectUnauthorized": false,
                "protocol": "http",
                "regionName": "IY3BNCAF",
                "zosmfName": "3b"
            },
            "secure": [
               "user",
               "password",
             ]
        },

creates the tree:

The connection profile could instead be something like cics_3b: IY3BNCAF. to show it's a single region and then show the resource tree items directly beneath it.

[Joe-Winchester]

Note also that there can be times when there is a CMCI connection available to a plex where a user can have multiple connections, some directly to the whole plex, e.g.

and some to a specific scope, e.g.

        "cics_lc_plex": {
            "type": "cics",
            "properties": {
                "host": "esysmvs1.wsclab.washington.ibm.com",
                "port": 3041,
                "protocol": "http",
                "cicsPlex": "DEMOPLEX"
            },
            "secure": [
              "user",
              "password"
            ]
        },

is for an entire plex (which can have many regions) while:

        "cics_lc_aor1": {
            "type": "cics",
            "properties": {
                "host": "esysmvs1.XXX.washington.ibm.com",
                "port": 3041,
                "rejectUnauthorized": false,
                "protocol": "http",
                "cicsPlex": "DEMOPLEX",
                "regionName": "CICSAOR1"
            },
            "secure": [
              "user", 
              "password"
              ]
        },

specifies a scope in the field miscalled "regionName". This scope can actually have multiple regions. I think the way to know whether it's part of a plex might be to ask for the "CICSCICSManagingAddressSpace" region table. In the case where there isn't a plex it'll return a 404 for no table present, and when the connection is for a plex there will be some kind of valid response.