Make `Pull from mainframe` behavior more intuitive

[adam-wolfe]

Is your feature request related to a problem? Please describe.

When the user right-clicks on a data set, member, USS file, or spool file, and selects Pull from mainframe, it can be unclear what is happening; particularly if there are no changes to pull in from the mainframe.

Users might also expect this action to download a member/file/etc. to their hard drive (and are confused when nothing seems to happen after clicking it).

Describe the solution you'd like

There are a few options:

• Changing the name of the context menu item:
  • The text "Pull from mainframe" may be confusing, but I am struggling to think of a concise alternative.
• Removing the context menu item:
  • If this action is only useful when I have a file open in an editor tab, does it make sense to have it in the tree view context menu, or is it possible that I could click on a member/file and see old/cached data (in which case the context menu item is still useful)?
  • Would it make more sense for this to be a command palette action, or could we add a refresh button to the editor tab?
• Adding a clearer notification to indicate what this action is doing. Currently, we show a brief message in the status bar. Could we show a clearer status message that persists for a longer amount of time?

Describe alternatives you've considered

Additional context

[github-actions]

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.

[JWaters02]

The text "Pull from mainframe" may be confusing, but I am struggling to think of a concise alternative.

How about "Check for updates"?

If this action is only useful when I have a file open in an editor tab, does it make sense to have it in the tree view context menu, or is it possible that I could click on a member/file and see old/cached data (in which case the context menu item is still useful)?

Yep

Would it make more sense for this to be a command palette action, or could we add a refresh button to the editor tab?

Maybe not a command palette action as this command is useful some cases and command palette is too hidden away but refresh button might be interesting.

Adding a clearer notification to indicate what this action is doing. Currently, we show a brief message in the status bar. Could we show a clearer status message that persists for a longer amount of time?

Maybe an information message to say if there was a new content or the contents remain unchanged (string check between current and mainframe versions).

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.