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

Changes are not saved to USS file opened from z/OS Resources Table #458

Open
1 of 5 tasks
adam-wolfe opened this issue Nov 18, 2024 · 1 comment
Open
1 of 5 tasks
Assignees
Labels
bug Something isn't working

Comments

@adam-wolfe
Copy link

Development environment used

  • Z Open Editor version: 5.0.0
  • Editor Platform
    • Visual Studio Code
    • Red Hat CodeReady Workspaces
    • Eclipse Che
    • Standalone Theia
  • Editor Platform Version: 1.95.3
  • Operating System (on which VS Code runs such as Windows 10 2004, otherwise name and version of platform such as OpenShift v4.3): Windows 10
  • Java Version (when using VS Code or Theia, execute java -version and paste the details here):
  • Related to RSE API?
    • RSE API Plugin version:
    • Zowe CLI version:
    • Node.js version:
  • Logs attached (see here how to get them): no

Problem Description

Detailed steps for reproducing the problem:

  1. Find a file using the z/OS Resources Table, and click on it to open it in an editor tab.
  2. Make some changes.
  3. Save the file.
  4. Check the file on the mainframe (using "Pull from mainframe" or ssh), and notice that the file does not include your changes.

Observed behavior

  • If I open a file (with write permission), make changes, then hit ctrl+s to save. The file appears to be saved (the dot in the editor tab goes away), but changes are not made to the file on the mainframe.
  • However, if I open the same file from the USS tree, make changes, and save the file, the changes are made to the file on the mainframe

Expected behavior

  • If I save changes in an editor tab, the changes should be sent back to the mainframe regardless of how I opened the file using Zowe Explorer.
@benjamin-t-santos
Copy link
Collaborator

Hi @adam-wolfe,
Thanks for filing this bug, I was able to recreate it. Starting with the next release of Z Open Editor, the z/OS Resources Table will use the same virtual filesystem as Zowe Explorer for opened MVS and USS files. This should fix the issue you are experiencing as well as provide better synchronization between the two views.
If you encounter other bugs or have any enhancement requests for the z/OS resources table, do not hesitate to file them here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants