Support the message transmission/reception API for TSO.

[Joe-Winchester]

Is your feature or enhancement request related to a problem or limitation? Please describe

The zowe tso command group allows sending commands to a TSO session (either a persistent one that can be started/stopped and addressed by key, or one that is created and torn down with each command).

For scenarios where the customer is running a TSO application within and address space, there is no way to send messages to the application and receive the messages back. The REST API support this with https://www.ibm.com/docs/en/zos/2.5.0?topic=services-send-messages-application and https://www.ibm.com/docs/en/zos/2.5.0?topic=services-receive-messages-from-application

Describe your enhancement idea

Support the APIs to receive and send messages. Perhaps a syntax 'zowe tso issue commandcould be extended to have--app. This would then issue PUT /zosmf/tsoApp/app//, where without -appit could still issue the currentPUT /zosmf/tsoApp/tso/. However with the appKey` I'm not sure if this can be done, so maybe a new command is needed. More design needs to occur.

As well as send, receive is also needed to support the API GET /zosmf/tsoApp/app/<servletKey>/<appKey>

[github-actions]

Thank you for raising this issue.
The community has 90 days to upvote 👍 the issue.
If it receives 5 upvotes, we will move it to our backlog. If not, we will close it.

[gejohnston]

Added the for-review tag due to the number of up-votes.

[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.