[JOBS] Error in encoding management in "Submit as JCL" and "Get JCL" functions

[FALLAI-Denis]

Describe the bug

When a JCL contains specific characters, either at the comment level or at the instream data flow level (sysin), these characters are incorrectly converted at the time of job submission, "Submit as JCL" function, and are also incorrectly converted by the "Get JCL" function.

This issue is relatively minor on comments, but it is major on instream data flow (sysin).

The JCL stream expected by z/OSMF should probably be encoded in UTF-8, and z/OSMF will take care of the translation to the correct encoding.
The API provides a header to declare the encoding to be applied: X-IBM-Intrdr-File-Encoding, IBM-1047 by default.
Zowe SDK supports this header a priori, but Zowe Explorer may not use it.

• Submit a job

For retrieving spool files, the z/OSMF API provides a parameter fileEncoding=code-page, IBM-1047 by default.
Zowe SDK also supports this parameter a priori, does Zowe Explorer use it?

• Retrieve the contents of a job spool file

To Reproduce

Sample JCL before submit:

Expected behavior

Use the encoding specified in the Zowe profile to submit and retrieve information from z/OS after submission.

Screenshots

Submitted JCL on z/OS:

JESJCL view:

"Get JCL":

Desktop (please complete the following information):

• OS: Windows
• Zowe Explorer Version: 3.2.2
• (Optional) Zowe CLI Version: N/A
• (Optional) Do you have secure credentials enabled? default
• (Optional) Are you using a custom credential manager? no

Additional context

[github-actions]

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.

[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.

[t1m0thyj]

For retrieving spool files, the z/OSMF API provides a parameter fileEncoding=code-page, IBM-1047 by default.
Zowe SDK also supports this parameter a priori, does Zowe Explorer use it?

Yes, if the encoding property is defined in a z/OSMF profile, then Zowe Explorer will respect it when downloading spool files. You can also right-click on a spool file in the ZE Jobs tree and select the "Open with Encoding" option to choose a different codepage.

The API provides a header to declare the encoding to be applied: X-IBM-Intrdr-File-Encoding, IBM-1047 by default.
Zowe SDK supports this header a priori, but Zowe Explorer may not use it.

Zowe Explorer doesn't support this yet but we plan to add support for the jobEncoding property in profiles in ZE 3.4.