Skip to content
New issue

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

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

Already on GitHub? # to your account

V3 - Must reload window after recalling data set in order to view it #3294

Closed
adam-wolfe opened this issue Nov 4, 2024 · 3 comments · Fixed by #3335
Closed

V3 - Must reload window after recalling data set in order to view it #3294

adam-wolfe opened this issue Nov 4, 2024 · 3 comments · Fixed by #3335
Assignees
Labels
bug Something isn't working priority-high Production outage - this quarter or at least next quarter severity-medium Bug where workaround exists or that doesn't prevent the usage of Zowe. Just makes it more complex.

Comments

@adam-wolfe
Copy link
Contributor

Describe the bug

After recalling a migrated data set, the icon for the data set is updated correctly, however clicking on the data set or selecting "Pull from Mainframe" does not open the data set. After reloading VS Code, the data set can be edited normally.

To Reproduce

  1. Find a migrated data set
  2. Right-click on the data set and select "Recall Data Set"
  3. The recall operation is successful
  4. Click on the data set - nothing happens
  5. Reload the window and search for the data set, click on it - the data set is opened in an editor tab

Expected behavior

After recalling the data set, I should be able to click on it and open it in an editor.

Screenshots

Desktop (please complete the following information):

  • OS:
  • Zowe Explorer Version: 3.0.2
  • (Optional) Zowe CLI Version:
  • (Optional) Are you using Secure Credential Store?

Additional context

Copy link

github-actions bot commented Nov 4, 2024

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.

@traeok
Copy link
Member

traeok commented Nov 4, 2024

Although the previous bug report for this issue was marked as priority-medium, we might want to consider making this one high priority, as the regression was fixed in v2 and is now broken again in v3.

@JTonda JTonda added priority-medium Not functioning - next quarter if capacity permits severity-medium Bug where workaround exists or that doesn't prevent the usage of Zowe. Just makes it more complex. labels Nov 5, 2024
@zowe-robot zowe-robot moved this from New Issues to Medium Priority in Zowe Explorer for VS Code Nov 5, 2024
@t1m0thyj t1m0thyj added priority-high Production outage - this quarter or at least next quarter and removed priority-medium Not functioning - next quarter if capacity permits labels Nov 15, 2024
@t1m0thyj t1m0thyj self-assigned this Nov 15, 2024
@zowe-robot zowe-robot moved this from Medium Priority to High Priority in Zowe Explorer for VS Code Nov 15, 2024
@t1m0thyj
Copy link
Member

This is an issue in ZE 2.18 as well. It may be specific to PDS/library data sets because their context value is not updated correctly when recalled.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
bug Something isn't working priority-high Production outage - this quarter or at least next quarter severity-medium Bug where workaround exists or that doesn't prevent the usage of Zowe. Just makes it more complex.
Projects
Status: Closed
Development

Successfully merging a pull request may close this issue.

4 participants