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

Add API functionality for specifying the enqueue type of a data set member when renaming it #573

Closed
CForrest97 opened this issue Nov 5, 2019 · 1 comment
Labels
enhancement New feature or request priority-low Legit issue but cosmetic or nice-to-have
Milestone

Comments

@CForrest97
Copy link
Contributor

User Story

As a CLI extender,
I want to be able to specify the enqueue type of a data set member when renaming it
so that I can change the enqueue type of the renamed member.

Acceptance Criteria

Scenario 1: Rename data set member
Given A patitioned data set USER.DATA.SET with a member named mem1
When I call the rename API with USER.DATA.SET, mem1, mem2 and enqueue: SHRW
Then the data set member in data set USER.DATA.SET will be renamed to mem2 and have enqueue type SHRW

Blocked by: #572

See: https://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.izua700/IZUHPINFO_API_PutDataSetMemberUtilities.htm

@CForrest97 CForrest97 added the enhancement New feature or request label Nov 5, 2019
@MikeBauerCA MikeBauerCA added this to the Backlog milestone Aug 26, 2021
@gejohnston gejohnston added the priority-low Legit issue but cosmetic or nice-to-have label Oct 12, 2022
@gejohnston
Copy link
Member

This enhancement has had no activity for 12 months. The issue also has less than 5 up-votes by the community. No action on this enhancement is targeted for the next 2 calendar quarters. Therefore, this enhancement is being closed. If you feel that this enhancement should continue to be available for community up-votes, you may reopen this issue.

@gejohnston gejohnston closed this as not planned Won't fix, can't repro, duplicate, stale Oct 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request priority-low Legit issue but cosmetic or nice-to-have
Projects
None yet
Development

No branches or pull requests

3 participants