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.

Sign up for GitHub

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

Jump to bottom

Allocate Like - Volume is not the same #3332

Open
RichardSGFR opened this issue Nov 20, 2024 · 6 comments
Open

Allocate Like - Volume is not the same #3332

RichardSGFR opened this issue Nov 20, 2024 · 6 comments
Labels
enhancement New feature or request priority-medium Not functioning - next quarter if capacity permits Research Needed

Comments

@RichardSGFR
Copy link

Describe the bug

When using the allocate like function to create a new dataset, it does not takes the volume of the initial dataet. Instead it takes the default volume declared for allocation on MVS. Which is annoying in our case because the default volume is a temporary one.

To Reproduce

  1. Open Zowe Explorer, search for a dataset
  2. right click on a dataset which is on a different volume than the default mvs volume
  3. Use the "Allocate like" function
  4. Compare the properties of the two dataset => the volume are different

Expected behavior

The volume of the new dataset should be the same as the one of the initial dataset

Screenshots

image

Desktop (please complete the following information):

  • OS: Windows 11
  • VSCODE: 1.94.2
  • Zowe Explorer Version: v2.18.0
@RichardSGFR RichardSGFR added the bug Something isn't working label Nov 20, 2024
@github-actions GitHub Actions
Copy link

Thank you for creating a bug report.
We will investigate the bug and evaluate its impact on the product.
If you haven't already, please ensure you have provided steps to reproduce the bug and as much context as possible.

@zFernand0
Copy link
Member

Hey @RichardSGFR,
I may be off base here, but I do remember this being brought up before.
This may be related to how the storage management classes are defined on your system. Meaning if you were to allocate a dataset on the 3270 and even specify a desired volume, it's possible that the dataset is allocated on a different one based on the storage-class configuration.

@adam-wolfe
Copy link
Contributor

It would be nice to have the option to specify a different storage class when doing an allocate like.

@RichardSGFR
Copy link
Author

In my case the storage class from the initial dataset is not used for the targetted one. The created dataset use the default storage class which the system affect if none is specified.

@RichardSGFR
Copy link
Author

It would be nice to have the option to specify a different storage class when doing an allocate like.

It has already been asked in this issue : #1960

@JTonda JTonda added enhancement New feature or request priority-medium Not functioning - next quarter if capacity permits and removed bug Something isn't working labels Nov 26, 2024
@github-actions GitHub Actions
Copy link

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

@zowe-robot zowe-robot moved this from New Issues to Medium Priority in Zowe Explorer for VS Code Nov 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request priority-medium Not functioning - next quarter if capacity permits Research Needed
Projects
Zowe Explorer for VS Code
Status: Medium Priority
Milestone
No milestone
Development

No branches or pull requests
4 participants
@JTonda @zFernand0 @adam-wolfe @RichardSGFR