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

Question: How does zowe jobs submit uss-file handle encoding ? #1455

Open
zFernand0 opened this issue Jun 20, 2022 · 4 comments
Open

Question: How does zowe jobs submit uss-file handle encoding ? #1455

zFernand0 opened this issue Jun 20, 2022 · 4 comments
Labels
bug Something isn't working priority-low Legit issue but cosmetic or nice-to-have severity-medium Bug where workaround exists or that doesn't prevent the usage of Zowe. Just makes it more complex.

Comments

@zFernand0
Copy link
Member

Should it follow the same encoding practices as zowe files download uss-file ?

Originally asked during the Zowe System Demo on 06/20/2022)

@zFernand0 zFernand0 added the question Further information is requested label Jun 20, 2022
@FALLAI-Denis
Copy link

Hi,

Yes, it should, both for submitting a job and for downloading outputs.

In addition, it is logical: when zowe zos-files download a JCL from the remote z/OS system, it is converted according to the encoding declared on the Zowe CLI profile.
So when submitted, it must be converted back the other way by the zowe zos-jobs command, otherwise the result will be inconsistent, especially on sysins.

Note that this will introduce a change from using the 3270 terminal for those using a code page other than IBM-037.

For example, I use the IBM-1147 codepage in my 3270 terminal: I have to transcode certain characters such as the $ character which becomes the £ character in my terminal.

If zowe zos-jobs enforces the encoding rules, I could encode a $ character, which will remain a $ character when submitting, and also a $ character when retrieving outputs.

@FALLAI-Denis
Copy link

See also #1463

@zFernand0 zFernand0 added enhancement New feature or request priority-low Legit issue but cosmetic or nice-to-have and removed question Further information is requested labels Mar 9, 2023
@github-actions
Copy link

github-actions bot commented Mar 9, 2023

Thank you for raising this enhancement request.
The community has 90 days to vote on it.
If the enhancement receives at least 5 upvotes, it is added to our development backlog.
If it receives fewer votes, the issue is closed.

@zFernand0 zFernand0 added for-review To be reviewed in an Eng & Prod Mgmt meeting bug Something isn't working and removed enhancement New feature or request for-review To be reviewed in an Eng & Prod Mgmt meeting labels Mar 9, 2023
@github-actions
Copy link

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.

@zFernand0 zFernand0 added the severity-medium Bug where workaround exists or that doesn't prevent the usage of Zowe. Just makes it more complex. label Mar 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working priority-low Legit issue but cosmetic or nice-to-have severity-medium Bug where workaround exists or that doesn't prevent the usage of Zowe. Just makes it more complex.
Projects
Status: Low Priority
Development

No branches or pull requests

2 participants