zowe/zowe-explorer-vscode

Rework wording of error message when saving ds that is over LRECL

Open

#4,076 opened on Feb 21, 2026

 (1 comment) (0 reactions) (0 assignees)TypeScript (119 forks)auto 404
buggood first issuepriority-lowseverity-medium

Repository metrics

Stars
 (189 stars)
PR merge metrics
 (PR metrics pending)

Description

Describe the bug

I've had a wave of reports from developers finding that the new "This upload operation may result in data loss" error message when trying to save a member that is over the data sets LRECL is not clear enough of what the actual problem is.

I'm aware this is mostly the issue that they are not reading the error message or clicking "Troubleshoot", but as one developer explained to me, they see the "This upload operation may result in data loss" error, think it's some entirely unrelated problem (such as their connection to the server being broken) and then get fed up that they can't save their program and go back to editing it on the greenscreen.

Also, when I showed them they can click on the "Troubleshoot" button, they thought there was nothing there, as it is not clear in the webview that you can click on the "Full error summary" dropdown (I mean I thought it looks clear enough but I am clearly biased).

To Reproduce

Save file that has a line over LRECL of data set.

Expected behavior

I agree that the error message is quite vague though, and since it's hardcoded only in that one LRECL check on the save, we should change it to something clearer, such as "Line(s) in the file exceed the logical record length of this data set. Please review the following lines: {line nums}. Click "Troubleshoot", then "Full error summary" for more detailed information."

Screenshots

Desktop (please complete the following information):

  • OS: Win11
  • Zowe Explorer Version: 3.4.1

Additional context

On the bright side, this has at least saved several of them from complete data loss as we were saying before, so very glad this feature exists now, thanks fernando!! But does also go to show how common it is that people are going over LRECL length in file, it really surprises me actually.

Contributor guide