microsoft / microsoft/vscode-remote-release
Support ssh to IBM z/OS (USS)
Open
Nobody has claimed this yet.
feature-request
ssh
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 470
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
Hello ...
I would greatly appreciate it if it were possible to start an SSH remote session on a z/OS (USS) system.
Currently I get the SSH connection established, but it fails with things like grep or the code page.
[17:28:39.177] Log Level: 2
[17:28:39.178] remote-ssh@0.78.0
[17:28:39.178] win32 x64
[17:28:39.190] SSH Resolver called for "ssh-remote+1.2.3.4", attempt 1
[17:28:39.191] "remote.SSH.useLocalServer": false
[17:28:39.191] "remote.SSH.showLoginTerminal": false
[17:28:39.191] "remote.SSH.remotePlatform": {}
[17:28:39.191] "remote.SSH.path": undefined
[17:28:39.191] "remote.SSH.configFile": undefined
[17:28:39.191] "remote.SSH.useFlock": true
[17:28:39.191] "remote.SSH.lockfilesInTmp": false
[17:28:39.191] "remote.SSH.localServerDownload": auto
[17:28:39.191] "remote.SSH.remoteServerListenOnSocket": false
[17:28:39.192] "remote.SSH.showLoginTerminal": false
[17:28:39.192] "remote.SSH.defaultExtensions": []
[17:28:39.192] "remote.SSH.loglevel": 2
[17:28:39.192] "remote.SSH.enableDynamicForwarding": true
[17:28:39.192] "remote.SSH.enableRemoteCommand": false
[17:28:39.192] "remote.SSH.serverPickPortsFromRange": {}
[17:28:39.192] "remote.SSH.serverInstallPath": {}
[17:28:39.205] SSH Resolver called for host: 1.2.3.4
[17:28:39.205] Setting up SSH remote "1.2.3.4"
[17:28:39.209] Using commit id "57fd6d0195bb9b9d1b49f6da5db789060795de47" and quality "stable" for server
[17:28:39.212] Install and start server if needed
[17:28:40.910] Checking ssh with "ssh -V"
[17:28:40.960] > OpenSSH_for_Windows_8.1p1, LibreSSL 3.0.2
[17:28:40.963] Running script with connection command: ssh -T -D 65207 "1.2.3.4" bash
[17:28:40.965] Terminal shell path: C:\Windows\System32\cmd.exe
[17:28:41.264] > ]0;C:\Windows\System32\cmd.exe
[17:28:41.264] Got some output, clearing connection timeout
[17:28:42.464] > 95763210cc11: running
[17:28:42.683] > FSUMA930 grep: Unknown option -a
> Usage: grep [-E|-F] [-BNbcilnqsvx] [-A|-P|-C num] [-S string] [-W option[,option
> ]...] [-e pattern] ... [-f patternfile] ... [pattern] [file ...]
[17:28:42.808] > FSUMA930 grep: Unknown option -a
> Usage: grep [-E|-F] [-BNbcilnqsvx] [-A|-P|-C num] [-S string] [-W option[,option
> ]...] [-e pattern] ... [-f patternfile] ... [pattern] [file ...]
[17:28:42.982] > Unsupported platform: ��a���
> 95763210cc11: start
> exitCode==35==
[17:28:43.001] > listeningOn====
> osReleaseId==��a���==
> arch====
> tmpDir==/tmp==
> platform====
> unpackResult====
> didLocalDownload==0==
> downloadTime====
> installTime====
> extInstallTime====
> serverStartTime====
> 95763210cc11: end
[17:28:43.002] Received install output:
exitCode==35==
listeningOn====
osReleaseId==��a���==
arch====
tmpDir==/tmp==
platform====
unpackResult====
didLocalDownload==0==
downloadTime====
installTime====
extInstallTime====
serverStartTime====
[17:28:43.003] Failed to parse remote port from server output
[17:28:43.003] Resolver error: Error:
at Function.Create (c:\Users\migo\.vscode\extensions\ms-vscode-remote.remote-ssh-0.78.0\out\extension.js:1:586041)
at Object.t.handleInstallOutput (c:\Users\migo\.vscode\extensions\ms-vscode-remote.remote-ssh-0.78.0\out\extension.js:1:584693)
at Object.t.tryInstall (c:\Users\migo\.vscode\extensions\ms-vscode-remote.remote-ssh-0.78.0\out\extension.js:1:681924)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async c:\Users\migo\.vscode\extensions\ms-vscode-remote.remote-ssh-0.78.0\out\extension.js:1:644564
at async Object.t.withShowDetailsEvent (c:\Users\migo\.vscode\extensions\ms-vscode-remote.remote-ssh-0.78.0\out\extension.js:1:647909)
at async Object.t.resolve (c:\Users\migo\.vscode\extensions\ms-vscode-remote.remote-ssh-0.78.0\out\extension.js:1:645643)
at async c:\Users\migo\.vscode\extensions\ms-vscode-remote.remote-ssh-0.78.0\out\extension.js:1:722950
[17:28:43.006] ------
[17:28:44.308] "install" terminal command done
[17:28:44.308] Install terminal quit with output:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Remote-SSH connection and server-install flow shown in the log, especially the bash invocation and install-output parsing. Reproduce the failure against IBM z/OS (USS); done means the remote server starts successfully, its port is parsed, and the grep and code-page errors no longer prevent connection.
Written by the indexing model from the issue text.
Assessment
- Domain
- devtools, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100