Support extensibility

[JeffinSiby]

The Zowe Explorer for IBM CICS extension should support other plugins to access useful properties of CICS resources and extend its capabilities.

It should provide an API for other VS Code extension to contribute such implementations.

[davsc01]

Thanks @JeffinSiby for starting the conversation. Ideally, it would be beneficial for each of the entities that the ZE for IBM CICS extension adds to the tree could be extended through a right click option in a structured manner.

[jellypuno]

Tips:

• What are the functionalities and use cases that extenders need?
• Reference the ZE APIs

[Joe-Winchester]

@davsc01 , we're working on an item #60 whose goal is to exclude all internal/system resources from the UI to just allow a user to see only application resources.
Our plan to do this is to use DEFINESOURCE and exclude values of SYSTEM and DEH*, which will pick up all CICS resources. For Broadcom we imagine you have your own DEFINESOURCE that isn't DFH*, for example if a debug tool or profiler or other vendor tool needed to get transactions, programs, ... running inside CICS do you use DEFINESOURCE as a way to identify them, and/or do you use a particular name (the way CICS uses C* or DFH*). Jeffin and I don't have access to any regions with Broadcom products so we can't see how your CICS resources get installed into regions, but it'd be great to know and/or if this doesn't make sense maybe we could jump on a webex and see a region with some Broadcom tools in for us to see how the internal vendor resources are being installed.

[github-actions]

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.