Special characters in DSN names not supported #2132
Replies: 1 comment 2 replies
-
|
Hey @Felix-Braun, Once this is done, we will make sure to update this discussion alongside our codebase to integrate with the fixes. |
Beta Was this translation helpful? Give feedback.
-
|
@zFernand0 I believe we have adopted this, can we close the discussion? |
Beta Was this translation helpful? Give feedback.
-
|
yes, we have added support for special characters in dataset names. Maybe we close this discussion once it's merged. |
Beta Was this translation helpful? Give feedback.
-
Describe the issue
We are trying to get a PDS member that has a special character in the DSN name through the ZOWE Explorer in VS Code. In our case the '#' (hash tag character). The connection is made through the APIML using the authentication service. But we are getting the following error:
Retrieving response from zowe.List Error: z/OSMF REST API Error: Rest API failure with HTTP(S) status 400 <!doctype html><html lang="en"><head><title>HTTP Status 400 – Bad Request</title><style type="text/css">body {font-family:Tahoma,Arial,sans-serif;} h1, h2, h3, b {color:white;background-color:#525D76;} h1 {font-size:22px;} h2 {font-size:16px;} h3 {font-size:14px;} p {font-size:12px;} a {color:black;} .line {height:1px;background-color:#525D76;border:none;}</style></head><body><h1>HTTP Status 400 – Bad Request</h1></body></html>We already asked the question in the zowe/api-layer [zowe/api-layer/issues/2728] and were told, that this issue had to be analysed here because if the request is created in a different way when APIML is involved.
If we can assist you in any way, please let us know.
To Reproduce
Environment:
Beta Was this translation helpful? Give feedback.
All reactions