Fernando Rijo Cedeno

Are there any updates on this issue? We've had unexpected behavior for quite some time now and we captured it here: https://github.com/zowe/vscode-extension-for-zowe/pull/296#issuecomment-552892394

Details: This type below seems to have been created so the keys of the [IRestClientResponse](https://github.com/zowe/zowe-cli/blob/master/packages/zosfiles/src/doc/IRestClientResponse.ts) _**interface**_ could be used as **_values_**. https://github.com/zowe/zowe-cli/blob/d1da9779288ba66c9f463c095d63679cff01e7d4/packages/zosfiles/src/doc/types/ZosmfRestClientProperties.ts#L19-L20 It might be good to refactor (and possibly...

Hey @kraabrsg, As mentioned [in slack](https://openmainframeproject.slack.com/archives/CC8AALGN6/p1655995337104849?thread_ts=1655979237.675259&cid=CC8AALGN6), I wasn't able to reproduce the same problem on Windows. Did you see any installation errors when updating to `@zowe/[email protected]` ?

Seems to be related to a PR Template 😉

This may be related to how `bash` expands the `/` Could you try the same command in bash but with a double `//` 😋 `$ zowe files list uss "//"`

Possible location: https://docs.zowe.org/stable/troubleshoot/cli/troubleshoot-cli

I do believe it probably makes more sense to have it in the known issues section for the CLI. And we can probably callout which terminals may have this problem...

I agree with you @ChrisBoehmCA. Espacially in the https://github.com/zowe/zowe-cli/blob/master/packages/zosmf/src/api/CheckStatus.ts JSDoc, given that People building applications (e.g. vscode extensions, webapps, ...) could communicate a wrong message to their users.

Since this is a pure job related utility, I can see why we may want to place this in there. However, implementing it there will cause more interdependencies across packages...

Let's close this issue for now. We can circle back to this if there are more places where we find ourselves needed such descriptor utility