Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support the message transmission/reception API for TSO. #1566

Closed
Tracked by #1671
Joe-Winchester opened this issue Nov 14, 2022 · 3 comments · Fixed by #2280
Closed
Tracked by #1671

Support the message transmission/reception API for TSO. #1566

Joe-Winchester opened this issue Nov 14, 2022 · 3 comments · Fixed by #2280
Assignees
Labels
community-upvoted enhancement New feature or request priority-medium Not functioning - next quarter if capacity permits
Milestone

Comments

@Joe-Winchester
Copy link
Member

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>

@Joe-Winchester Joe-Winchester added enhancement New feature or request new The issue wasn't triaged yet labels Nov 14, 2022
@github-actions
Copy link

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 gejohnston added for-review To be reviewed in an Eng & Prod Mgmt meeting priority-medium Not functioning - next quarter if capacity permits labels Jan 10, 2023
@gejohnston
Copy link
Member

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

@JTonda JTonda removed for-review To be reviewed in an Eng & Prod Mgmt meeting new The issue wasn't triaged yet labels Jan 11, 2023
@zFernand0 zFernand0 added enhancement New feature or request and removed enhancement New feature or request labels Mar 8, 2023
@github-actions
Copy link

github-actions bot commented Mar 8, 2023

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 zFernand0 mentioned this issue Mar 29, 2023
28 tasks
@adam-wolfe adam-wolfe mentioned this issue May 31, 2023
19 tasks
@adam-wolfe adam-wolfe mentioned this issue Jan 4, 2024
26 tasks
@adam-wolfe adam-wolfe mentioned this issue Feb 26, 2024
23 tasks
@jace-roell jace-roell self-assigned this Sep 25, 2024
@jace-roell jace-roell linked a pull request Sep 30, 2024 that will close this issue
4 tasks
@adam-wolfe adam-wolfe added this to the V3.1.0 milestone Oct 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community-upvoted enhancement New feature or request priority-medium Not functioning - next quarter if capacity permits
Projects
Status: Closed
Development

Successfully merging a pull request may close this issue.

6 participants