Re: Using Windows ssh with z/OS
The .inputrc doesn't seem to work for me. I have this in my .inputrc: "\e[3~": delete-char but the delete key is still a destructive backspace key. Am I doing something wrong? On 5/6/2020 2:06 AM, David Crayford wrote: BTW, if you want to use the delete key in the bash command line you need to put the following line into your readline init file. echo "\"\e[3~\"": delete-char >> ~/.inputrc On 2020-05-05 8:11 PM, Michael Babcock wrote: After reading this thread I finally have my command line completion back! I have Rocket’s Bash installed, set my OMVS segment to the bash shell, used Bluezone and created a ssh terminal session with VT320, set “disable dimming colors” and “Use ANSI colors” and set my screen to 32x120. I then added export TERM=xterm to .profile and VIOLA! Tab command line completion! Thanks to all! On Sun, May 3, 2020 at 12:28 PM Michael Babcock wrote: The thing I REALY miss in OMVS is command line completion with TAB key. On Sun, May 3, 2020 at 12:25 PM Paul Gilmartin < 000433f07816-dmarc-requ...@listserv.ua.edu> wrote: On Sat, 2 May 2020 12:02:56 -0600, Jack J. Woehr wrote: But z/OS used to deny login when TERM was not in terminfo. Did it ever get better? If it denies login to that term setting, you try something else :) Yah, but I wished it had presumed something minimal such as TTY33 until I could EXPORT TERM and/or set TERMINFO. Catch-22: can't login without correct TERMINFO; can't set TERMINFO without logging in. And I once had an esoteric terminal for which the developer supplied a .terminfo source file. With octal escape sequences. I compiled it with /bin/tic. Guess why it didn't work. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Michael Babcock OneMain Financial z/OS Systems Programmer, Lead -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Using Windows ssh with z/OS
On Thu, 7 May 2020 01:02:55 +0800, David Crayford wrote: >> >> On 2020-05-06 11:32 PM, Kirk Wolf wrote: >>> Not so fast: cp and cat are both /bin/sh built-in commands ( documented >>> under "Built-in commands" in the command reference for sh). So the shell >>> does employ DDs;-) >> >> I didn't know that! I thought they were binaries in /bin! Thanks ;) > >TS8004:/u/ts8004/rtehome: >type cat >cat is /bin/cat >TS8004:/u/ts8004/rtehome: >sh >TS8004:/u/ts8004/rtehome: >type cat >cat is a built-in command > What's "sh": type sh; echo $0; echo $SHELL; etc. Per POSIX, if a search of directories in $PATH does not find "cat" first in /bin (i.e. elsewhere or not at all), it will not be recognized as a builtin. This is to allow users to override builtins by providing alternatives in private directories. And POSIX requires that many builtins be available via exec(). z/OS takes a deplorable shortcut by making those a multi-linked shell script which invokes sh to call the builtin. Try "ls -li /bin/echo /bin/cat" and "ls -li /bin/echo /bin/cat". The deviant side effect is that those little scripts invoke the caller's $ENV script with its side effects. Try "(cd /bin & type *) | grep built-in". -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Using Windows ssh with z/OS
On 2020-05-07 12:55 AM, David Crayford wrote: On 2020-05-06 11:32 PM, Kirk Wolf wrote: Not so fast: cp and cat are both /bin/sh built-in commands ( documented under "Built-in commands" in the command reference for sh). So the shell does employ DDs;-) I didn't know that! I thought they were binaries in /bin! Thanks ;) TS8004:/u/ts8004/rtehome: >type cat cat is /bin/cat TS8004:/u/ts8004/rtehome: >sh TS8004:/u/ts8004/rtehome: >type cat cat is a built-in command -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Using Windows ssh with z/OS
On 2020-05-06 11:32 PM, Kirk Wolf wrote: Not so fast: cp and cat are both /bin/sh built-in commands ( documented under "Built-in commands" in the command reference for sh).So the shell does employ DDs;-) I didn't know that! I thought they were binaries in /bin! Thanks ;) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Using Windows ssh with z/OS
On Wed, May 6, 2020 at 9:35 AM Paul Gilmartin < 000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > > >On 2020-05-06 8:31 PM, Kirk Wolf wrote: > >> cat DD: isn't documented as supported? :-) > >> > >> what about "cp //DD:xxx /dev/fd1" - is that the shell? > >> > I don't believe shell is closely involved. I'd expect similar > behavior if it were invoked from a program by exec(). > "DD:xxx" would be elaborated by the C RTL provided that > cp invokes fopen(), which is not guaranteed, and > /dev/fd/1 is a kernel facility. > > -- gil > Not so fast: cp and cat are both /bin/sh built-in commands ( documented under "Built-in commands" in the command reference for sh).So the shell does employ DDs ;-) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Using Windows ssh with z/OS
On Wed, 6 May 2020 20:40:20 +0800, David Crayford wrote: >We've had this conversation many times before. Utilities that use >fopen() support DD:xxx and are not likely to change. > >Gil is being pedantic. But maybe IBM should update the doc? > Pedantic, yes, but I'd be loath to use in code distributed to customers constructs not documented as supported. I submitted such an RCF years ago saying that many of my peers misuse DD:xxx in this fashion and suggesting a clarification that the Appendix should state clearly that it is not supported. IBM declined, saying (roughly paraphrased), "We document what we support; we don't document what we don't support." Of course; the latter is an enormous set, impractical to enumerate. And I admired the gyrations of a co-worker to avoid using FALSE or TRUE in JCL IF-THEN-ELSE as boolean primaries. They happen to work but are not documented. She was being fastidious. >On 2020-05-06 8:31 PM, Kirk Wolf wrote: >> cat DD: isn't documented as supported? :-) >> >> what about "cp //DD:xxx /dev/fd1" - is that the shell? >> I don't believe shell is closely involved. I'd expect similar behavior if it were invoked from a program by exec(). "DD:xxx" would be elaborated by the C RTL provided that cp invokes fopen(), which is not guaranteed, and /dev/fd/1 is a kernel facility. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Using Windows ssh with z/OS
David, - using bash interactively and /bin/sh otherwise seems like a reasonable approach. (this makes me consider whether the COZBATCH default - to run the user's login shell - is problematic if this were popular) - I agree that change bash to use spawn looks extremely hard. Also, since bash is GNU / GPL, I believe that everyone who can download the Rocket z/OS port also has access to the source. On Wed, May 6, 2020 at 2:02 AM David Crayford wrote: > Agreed. I've got access to she source repository and I don't think spawn > will ever be implemented. > > I use bash as a login shell and /bin/sh for scripting and batch. Best of > both worlds. > > > On 2020-05-05 9:56 PM, Kirk Wolf wrote: > > FWIW, I would love to use bash exclusively on z/OS, but without > > _BPX_SHAREAS support: > > > > - there are things that you just can't do, like use DDs > > - the overhead for forking new address spaces is significant for many > > tasks. > > > > > > > > On Tue, May 5, 2020 at 8:06 AM David Crayford > wrote: > > > >> To create terminfo colors check out Jerry Callens comment in this thread > >> > >> > https://forum.rocketsoftware.com/t/no-colors-running-over-ssh-in-cygwin/1009/7 > >> > >> On 2020-05-05 8:11 PM, Michael Babcock wrote: > >>> After reading this thread I finally have my command line completion > back! > >>> > >>> I have Rocket’s Bash installed, set my OMVS segment to the bash shell, > >> used > >>> Bluezone and created a ssh terminal session with VT320, set “disable > >>> dimming colors” and “Use ANSI colors” and set my screen to 32x120. I > >> then > >>> added export TERM=xterm to .profile and VIOLA! Tab command line > >>> completion! > >>> > >>> Thanks to all! > >>> > >>> On Sun, May 3, 2020 at 12:28 PM Michael Babcock > > >>> wrote: > >>> > The thing I REALY miss in OMVS is command line completion with TAB > key. > > On Sun, May 3, 2020 at 12:25 PM Paul Gilmartin < > 000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > > > On Sat, 2 May 2020 12:02:56 -0600, Jack J. Woehr wrote: > >>> But z/OS used to deny login when TERM was not in terminfo. > >>> Did it ever get better? > >> If it denies login to that term setting, you try something else :) > >> > > Yah, but I wished it had presumed something minimal such as TTY33 > > until I could EXPORT TERM and/or set TERMINFO. Catch-22: > > can't login without correct TERMINFO; can't set TERMINFO without > > logging in. > > > > And I once had an esoteric terminal for which the developer supplied > > a .terminfo source file. With octal escape sequences. I compiled it > > with /bin/tic. Guess why it didn't work. > > > > -- gil > > > > > -- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO > IBM-MAIN > > > -- > Michael Babcock > OneMain Financial > z/OS Systems Programmer, Lead > > >> -- > >> For IBM-MAIN subscribe / signoff / archive access instructions, > >> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > >> > > -- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Using Windows ssh with z/OS
We've had this conversation many times before. Utilities that use fopen() support DD:xxx and are not likely to change. Gil is being pedantic. But maybe IBM should update the doc? On 2020-05-06 8:31 PM, Kirk Wolf wrote: cat DD: isn't documented as supported? :-) what about "cp //DD:xxx /dev/fd1" - is that the shell? On Tue, May 5, 2020 at 3:50 PM Paul Gilmartin < 000433f07816-dmarc-requ...@listserv.ua.edu> wrote: On Tue, 5 May 2020 13:12:44 -0500, Kirk Wolf wrote: "deploy" ? "employ"? ISTR that this is your favorite example of using DD's in the shell :-) cat //DD:MYDD o FSVO "favorite". See Appendix K of the Command Ref. It's not supported; it may work by happenstance; if it breaks you get to keep both parts. o If it happens to work it's because of "cat" and not "sh". I'd expect it to behave alike under "bash". On Tue, May 5, 2020 at 9:17 AM Paul Gilmartin wrote: On Tue, 5 May 2020 08:56:59 -0500, Kirk Wolf wrote: FWIW, I would love to use bash exclusively on z/OS, but without _BPX_SHAREAS support: - there are things that you just can't do, like use DDs Where does a shell employ DDs? - the overhead for forking new address spaces is significant for many tasks. That seems to be an argument for retaining _BPX_SHAREAS support. And for a shell's using spawn() where possible rather than fork(). -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Using Windows ssh with z/OS
cat DD: isn't documented as supported? :-) what about "cp //DD:xxx /dev/fd1" - is that the shell? On Tue, May 5, 2020 at 3:50 PM Paul Gilmartin < 000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > On Tue, 5 May 2020 13:12:44 -0500, Kirk Wolf wrote: > > > >"deploy" ? > > > "employ"? > > >ISTR that this is your favorite example of using DD's in the shell :-) > > > >cat //DD:MYDD > > > o FSVO "favorite". See Appendix K of the Command Ref. It's not > supported; it may work by happenstance; if it breaks you get to > keep both parts. > > o If it happens to work it's because of "cat" and not "sh". I'd > expect it to behave alike under "bash". > > > >On Tue, May 5, 2020 at 9:17 AM Paul Gilmartin wrote: > > > >> On Tue, 5 May 2020 08:56:59 -0500, Kirk Wolf wrote: > >> > >> >FWIW, I would love to use bash exclusively on z/OS, but without > >> >_BPX_SHAREAS support: > >> > > >> >- there are things that you just can't do, like use DDs > >> > > >> Where does a shell employ DDs? > >> > >> >- the overhead for forking new address spaces is significant for many > >> >tasks. > >> > > >> That seems to be an argument for retaining _BPX_SHAREAS support. > >> And for a shell's using spawn() where possible rather than fork(). > > -- gil > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Using Windows ssh with z/OS
BTW, if you want to use the delete key in the bash command line you need to put the following line into your readline init file. echo "\"\e[3~\"": delete-char >> ~/.inputrc On 2020-05-05 8:11 PM, Michael Babcock wrote: After reading this thread I finally have my command line completion back! I have Rocket’s Bash installed, set my OMVS segment to the bash shell, used Bluezone and created a ssh terminal session with VT320, set “disable dimming colors” and “Use ANSI colors” and set my screen to 32x120. I then added export TERM=xterm to .profile and VIOLA! Tab command line completion! Thanks to all! On Sun, May 3, 2020 at 12:28 PM Michael Babcock wrote: The thing I REALY miss in OMVS is command line completion with TAB key. On Sun, May 3, 2020 at 12:25 PM Paul Gilmartin < 000433f07816-dmarc-requ...@listserv.ua.edu> wrote: On Sat, 2 May 2020 12:02:56 -0600, Jack J. Woehr wrote: But z/OS used to deny login when TERM was not in terminfo. Did it ever get better? If it denies login to that term setting, you try something else :) Yah, but I wished it had presumed something minimal such as TTY33 until I could EXPORT TERM and/or set TERMINFO. Catch-22: can't login without correct TERMINFO; can't set TERMINFO without logging in. And I once had an esoteric terminal for which the developer supplied a .terminfo source file. With octal escape sequences. I compiled it with /bin/tic. Guess why it didn't work. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Michael Babcock OneMain Financial z/OS Systems Programmer, Lead -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Using Windows ssh with z/OS
Agreed. I've got access to she source repository and I don't think spawn will ever be implemented. I use bash as a login shell and /bin/sh for scripting and batch. Best of both worlds. On 2020-05-05 9:56 PM, Kirk Wolf wrote: FWIW, I would love to use bash exclusively on z/OS, but without _BPX_SHAREAS support: - there are things that you just can't do, like use DDs - the overhead for forking new address spaces is significant for many tasks. On Tue, May 5, 2020 at 8:06 AM David Crayford wrote: To create terminfo colors check out Jerry Callens comment in this thread https://forum.rocketsoftware.com/t/no-colors-running-over-ssh-in-cygwin/1009/7 On 2020-05-05 8:11 PM, Michael Babcock wrote: After reading this thread I finally have my command line completion back! I have Rocket’s Bash installed, set my OMVS segment to the bash shell, used Bluezone and created a ssh terminal session with VT320, set “disable dimming colors” and “Use ANSI colors” and set my screen to 32x120. I then added export TERM=xterm to .profile and VIOLA! Tab command line completion! Thanks to all! On Sun, May 3, 2020 at 12:28 PM Michael Babcock wrote: The thing I REALY miss in OMVS is command line completion with TAB key. On Sun, May 3, 2020 at 12:25 PM Paul Gilmartin < 000433f07816-dmarc-requ...@listserv.ua.edu> wrote: On Sat, 2 May 2020 12:02:56 -0600, Jack J. Woehr wrote: But z/OS used to deny login when TERM was not in terminfo. Did it ever get better? If it denies login to that term setting, you try something else :) Yah, but I wished it had presumed something minimal such as TTY33 until I could EXPORT TERM and/or set TERMINFO. Catch-22: can't login without correct TERMINFO; can't set TERMINFO without logging in. And I once had an esoteric terminal for which the developer supplied a .terminfo source file. With octal escape sequences. I compiled it with /bin/tic. Guess why it didn't work. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Michael Babcock OneMain Financial z/OS Systems Programmer, Lead -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Using Windows ssh with z/OS
On Tue, 5 May 2020 13:12:44 -0500, Kirk Wolf wrote: > >"deploy" ? > "employ"? >ISTR that this is your favorite example of using DD's in the shell :-) > >cat //DD:MYDD > o FSVO "favorite". See Appendix K of the Command Ref. It's not supported; it may work by happenstance; if it breaks you get to keep both parts. o If it happens to work it's because of "cat" and not "sh". I'd expect it to behave alike under "bash". >On Tue, May 5, 2020 at 9:17 AM Paul Gilmartin wrote: > >> On Tue, 5 May 2020 08:56:59 -0500, Kirk Wolf wrote: >> >> >FWIW, I would love to use bash exclusively on z/OS, but without >> >_BPX_SHAREAS support: >> > >> >- there are things that you just can't do, like use DDs >> > >> Where does a shell employ DDs? >> >> >- the overhead for forking new address spaces is significant for many >> >tasks. >> > >> That seems to be an argument for retaining _BPX_SHAREAS support. >> And for a shell's using spawn() where possible rather than fork(). -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Using Windows ssh with z/OS
Gil, "deploy" ? ISTR that this is your favorite example of using DD's in the shell :-) cat //DD:MYDD On Tue, May 5, 2020 at 9:17 AM Paul Gilmartin < 000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > On Tue, 5 May 2020 08:56:59 -0500, Kirk Wolf wrote: > > >FWIW, I would love to use bash exclusively on z/OS, but without > >_BPX_SHAREAS support: > > > >- there are things that you just can't do, like use DDs > > > Where does a shell employ DDs? > > >- the overhead for forking new address spaces is significant for many > >tasks. > > > That seems to be an argument for retaining _BPX_SHAREAS support. > And for a shell's using spawn() where possible rather than fork(). > > -- gil > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Using Windows ssh with z/OS
On Tue, 5 May 2020 08:56:59 -0500, Kirk Wolf wrote: >FWIW, I would love to use bash exclusively on z/OS, but without >_BPX_SHAREAS support: > >- there are things that you just can't do, like use DDs > Where does a shell employ DDs? >- the overhead for forking new address spaces is significant for many >tasks. > That seems to be an argument for retaining _BPX_SHAREAS support. And for a shell's using spawn() where possible rather than fork(). -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Using Windows ssh with z/OS
FWIW, I would love to use bash exclusively on z/OS, but without _BPX_SHAREAS support: - there are things that you just can't do, like use DDs - the overhead for forking new address spaces is significant for many tasks. On Tue, May 5, 2020 at 8:06 AM David Crayford wrote: > To create terminfo colors check out Jerry Callens comment in this thread > > https://forum.rocketsoftware.com/t/no-colors-running-over-ssh-in-cygwin/1009/7 > > On 2020-05-05 8:11 PM, Michael Babcock wrote: > > After reading this thread I finally have my command line completion back! > > > > I have Rocket’s Bash installed, set my OMVS segment to the bash shell, > used > > Bluezone and created a ssh terminal session with VT320, set “disable > > dimming colors” and “Use ANSI colors” and set my screen to 32x120. I > then > > added export TERM=xterm to .profile and VIOLA! Tab command line > > completion! > > > > Thanks to all! > > > > On Sun, May 3, 2020 at 12:28 PM Michael Babcock > > wrote: > > > >> The thing I REALY miss in OMVS is command line completion with TAB key. > >> > >> On Sun, May 3, 2020 at 12:25 PM Paul Gilmartin < > >> 000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > >> > >>> On Sat, 2 May 2020 12:02:56 -0600, Jack J. Woehr wrote: > > But z/OS used to deny login when TERM was not in terminfo. > > Did it ever get better? > If it denies login to that term setting, you try something else :) > > >>> Yah, but I wished it had presumed something minimal such as TTY33 > >>> until I could EXPORT TERM and/or set TERMINFO. Catch-22: > >>> can't login without correct TERMINFO; can't set TERMINFO without > >>> logging in. > >>> > >>> And I once had an esoteric terminal for which the developer supplied > >>> a .terminfo source file. With octal escape sequences. I compiled it > >>> with /bin/tic. Guess why it didn't work. > >>> > >>> -- gil > >>> > >>> -- > >>> For IBM-MAIN subscribe / signoff / archive access instructions, > >>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > >>> > >> -- > >> Michael Babcock > >> OneMain Financial > >> z/OS Systems Programmer, Lead > >> > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Using Windows ssh with z/OS
To create terminfo colors check out Jerry Callens comment in this thread https://forum.rocketsoftware.com/t/no-colors-running-over-ssh-in-cygwin/1009/7 On 2020-05-05 8:11 PM, Michael Babcock wrote: After reading this thread I finally have my command line completion back! I have Rocket’s Bash installed, set my OMVS segment to the bash shell, used Bluezone and created a ssh terminal session with VT320, set “disable dimming colors” and “Use ANSI colors” and set my screen to 32x120. I then added export TERM=xterm to .profile and VIOLA! Tab command line completion! Thanks to all! On Sun, May 3, 2020 at 12:28 PM Michael Babcock wrote: The thing I REALY miss in OMVS is command line completion with TAB key. On Sun, May 3, 2020 at 12:25 PM Paul Gilmartin < 000433f07816-dmarc-requ...@listserv.ua.edu> wrote: On Sat, 2 May 2020 12:02:56 -0600, Jack J. Woehr wrote: But z/OS used to deny login when TERM was not in terminfo. Did it ever get better? If it denies login to that term setting, you try something else :) Yah, but I wished it had presumed something minimal such as TTY33 until I could EXPORT TERM and/or set TERMINFO. Catch-22: can't login without correct TERMINFO; can't set TERMINFO without logging in. And I once had an esoteric terminal for which the developer supplied a .terminfo source file. With octal escape sequences. I compiled it with /bin/tic. Guess why it didn't work. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Michael Babcock OneMain Financial z/OS Systems Programmer, Lead -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Using Windows ssh with z/OS
After reading this thread I finally have my command line completion back! I have Rocket’s Bash installed, set my OMVS segment to the bash shell, used Bluezone and created a ssh terminal session with VT320, set “disable dimming colors” and “Use ANSI colors” and set my screen to 32x120. I then added export TERM=xterm to .profile and VIOLA! Tab command line completion! Thanks to all! On Sun, May 3, 2020 at 12:28 PM Michael Babcock wrote: > The thing I REALY miss in OMVS is command line completion with TAB key. > > On Sun, May 3, 2020 at 12:25 PM Paul Gilmartin < > 000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > >> On Sat, 2 May 2020 12:02:56 -0600, Jack J. Woehr wrote: >> > >> >> But z/OS used to deny login when TERM was not in terminfo. >> >> Did it ever get better? >> > >> >If it denies login to that term setting, you try something else :) >> > >> Yah, but I wished it had presumed something minimal such as TTY33 >> until I could EXPORT TERM and/or set TERMINFO. Catch-22: >> can't login without correct TERMINFO; can't set TERMINFO without >> logging in. >> >> And I once had an esoteric terminal for which the developer supplied >> a .terminfo source file. With octal escape sequences. I compiled it >> with /bin/tic. Guess why it didn't work. >> >> -- gil >> >> -- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >> > -- > Michael Babcock > OneMain Financial > z/OS Systems Programmer, Lead > -- Michael Babcock OneMain Financial z/OS Systems Programmer, Lead -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Using Windows ssh with z/OS
In article <6673472942485742.wa.paulgboulderaim@listserv.ua.edu> you wrote:
> On Mon, 4 May 2020 17:39:39 -0500, Wendell Lovewell wrote:
> >
> >Installing Rocket's bash provided the cursor history scrolling I was looking
> >for.
> >
> >I don't perceive a difference between TERM=xterm+256color and TERM=xterm in
> >the command-line-only functions I use. (I don't see any coloring in the ls
> >or other output for either value.)
> >
> >I have "bash" as the last line in /etc/profile. This seems to work, but I
> >do have to enter "exit" twice to close the window. Is there a way to invoke
> >bash so that this is not necessary? I'm also not sure if this matters, but
> >"echo $SHELL" still shows "/bin/sh", not "/bin/bash".
> >
> SHELL=/bin/bash exec $SHELL
> -- gil
If you have permission (or know someone that has permission), do:
TSO ALTUSER userid OMVS(PROGRAM('/path/to/bin/bash'))
--
Don Poitras - SAS Development - SAS Institute Inc. - SAS Campus Drive
sas...@sas.com (919) 531-5637Cary, NC 27513
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Using Windows ssh with z/OS
On 5/3/20 11:25 AM, Paul Gilmartin wrote: Yah, but I wished it had presumed something minimal such as TTY33 until I could EXPORT TERM and/or set TERMINFO. Put it in your .profile or .bash_profile or whatever. -- Jack J. Woehr # Science is more than a body of knowledge. It's a way of www.well.com/~jax # thinking, a way of skeptically interrogating the universe www.softwoehr.com # with a fine understanding of human fallibility. - Carl Sagan -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Using Windows ssh with z/OS
The thing I REALY miss in OMVS is command line completion with TAB key. On Sun, May 3, 2020 at 12:25 PM Paul Gilmartin < 000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > On Sat, 2 May 2020 12:02:56 -0600, Jack J. Woehr wrote: > > > >> But z/OS used to deny login when TERM was not in terminfo. > >> Did it ever get better? > > > >If it denies login to that term setting, you try something else :) > > > Yah, but I wished it had presumed something minimal such as TTY33 > until I could EXPORT TERM and/or set TERMINFO. Catch-22: > can't login without correct TERMINFO; can't set TERMINFO without > logging in. > > And I once had an esoteric terminal for which the developer supplied > a .terminfo source file. With octal escape sequences. I compiled it > with /bin/tic. Guess why it didn't work. > > -- gil > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- Michael Babcock OneMain Financial z/OS Systems Programmer, Lead -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Using Windows ssh with z/OS
On Sat, 2 May 2020 12:02:56 -0600, Jack J. Woehr wrote: > >> But z/OS used to deny login when TERM was not in terminfo. >> Did it ever get better? > >If it denies login to that term setting, you try something else :) > Yah, but I wished it had presumed something minimal such as TTY33 until I could EXPORT TERM and/or set TERMINFO. Catch-22: can't login without correct TERMINFO; can't set TERMINFO without logging in. And I once had an esoteric terminal for which the developer supplied a .terminfo source file. With octal escape sequences. I compiled it with /bin/tic. Guess why it didn't work. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Using Windows ssh with z/OS
Jack, Not everyone learns that way , I have ADHD and the way you described is the way I must learn, because of the sometimes levels of my attention. Scott On Sun, May 3, 2020 at 12:50 PM scott Ford wrote: > Wendell, > > Contact me of listserv I can help you out, we been using x3270 with their > scripting to this sort of thing for awhile, including CI/CD type work. > > Scott > > On Sun, May 3, 2020 at 3:30 AM Jack J. Woehr wrote: > >> On 5/2/20 11:16 AM, Paul Gilmartin wrote: >> > Doesn't ssh supposed to set that up? But z/OS may not >> > be savvy to the OP's TERM. Is it in terminfo? >> >> I dunno, but it sure works better than xterm-color256 on IBM i so just >> guessing. >> >> > But z/OS used to deny login when TERM was not in terminfo. >> > Did it ever get better? >> >> >> If it denies login to that term setting, you try something else :) >> >> Honestly, if folks want to understand this stuff, have the reference >> platform handy so they can see how it's supposed to work if it worked >> correctly, i.e., set up a cheap Linux box and learn your way around. >> >> -- >> Jack J. Woehr # Science is more than a body of knowledge. It's a way >> of >> www.well.com/~jax # thinking, a way of skeptically interrogating the >> universe >> www.softwoehr.com # with a fine understanding of human fallibility. - >> Carl Sagan >> >> -- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >> > -- > Scott Ford > IDMWORKS > z/OS Development > -- Scott Ford IDMWORKS z/OS Development -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Using Windows ssh with z/OS
Wendell, Contact me of listserv I can help you out, we been using x3270 with their scripting to this sort of thing for awhile, including CI/CD type work. Scott On Sun, May 3, 2020 at 3:30 AM Jack J. Woehr wrote: > On 5/2/20 11:16 AM, Paul Gilmartin wrote: > > Doesn't ssh supposed to set that up? But z/OS may not > > be savvy to the OP's TERM. Is it in terminfo? > > I dunno, but it sure works better than xterm-color256 on IBM i so just > guessing. > > > But z/OS used to deny login when TERM was not in terminfo. > > Did it ever get better? > > > If it denies login to that term setting, you try something else :) > > Honestly, if folks want to understand this stuff, have the reference > platform handy so they can see how it's supposed to work if it worked > correctly, i.e., set up a cheap Linux box and learn your way around. > > -- > Jack J. Woehr # Science is more than a body of knowledge. It's a way of > www.well.com/~jax # thinking, a way of skeptically interrogating the > universe > www.softwoehr.com # with a fine understanding of human fallibility. - > Carl Sagan > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- Scott Ford IDMWORKS z/OS Development -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Using Windows ssh with z/OS
On 5/2/20 11:16 AM, Paul Gilmartin wrote: Doesn't ssh supposed to set that up? But z/OS may not be savvy to the OP's TERM. Is it in terminfo? I dunno, but it sure works better than xterm-color256 on IBM i so just guessing. But z/OS used to deny login when TERM was not in terminfo. Did it ever get better? If it denies login to that term setting, you try something else :) Honestly, if folks want to understand this stuff, have the reference platform handy so they can see how it's supposed to work if it worked correctly, i.e., set up a cheap Linux box and learn your way around. -- Jack J. Woehr # Science is more than a body of knowledge. It's a way of www.well.com/~jax # thinking, a way of skeptically interrogating the universe www.softwoehr.com # with a fine understanding of human fallibility. - Carl Sagan -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Using Windows ssh with z/OS
On Sat, 2 May 2020 10:51:01 -0600, Jack J. Woehr wrote: >On 5/2/20 9:53 AM, Wendell Lovewell wrote: >> When connecting to z/OS (USS) using ssh, I'd like the USS shell to handle >> keys the same way Ubuntu does. I have these settings: >> >> echo $TERM displays xterm-color256 >> echo $SHELL displays /bin/sh > >As Gil pointed out, run bash. It's often there somewhere. > >If not bash, use tcsh > Eek! https://www-uxsup.csx.cam.ac.uk/misc/csh.html >Also: >export TERM=xterm > Doesn't ssh supposed to set that up? But z/OS may not be savvy to the OP's TERM. Is it in terminfo? But z/OS used to deny login when TERM was not in terminfo. Did it ever get better? -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Using Windows ssh with z/OS
On 5/2/20 9:53 AM, Wendell Lovewell wrote: When connecting to z/OS (USS) using ssh, I'd like the USS shell to handle keys the same way Ubuntu does. I have these settings: echo $TERM displays xterm-color256 echo $SHELL displays /bin/sh As Gil pointed out, run bash. It's often there somewhere. If not bash, use tcsh Also: export TERM=xterm -- Jack J. Woehr # Science is more than a body of knowledge. It's a way of www.well.com/~jax # thinking, a way of skeptically interrogating the universe www.softwoehr.com # with a fine understanding of human fallibility. - Carl Sagan -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Using Windows ssh with z/OS
In article <6643888504611180.wa.paulgboulderaim@listserv.ua.edu> you wrote: > On Sat, 2 May 2020 18:26:48 +0200, Mike Beer wrote: > >Maybe using putty might help: > >https://www.putty.org/ > >https://www.ssh.com/ssh/putty/putty-manuals/0.68/Chapter4.html > > > >Best regards > >Mike > > > >-Urspr??ngliche Nachricht- > >Von: IBM Mainframe Discussion List Im Auftrag von > >Wendell Lovewell > >Gesendet: Saturday, May 02, 2020 17:54 > >An: IBM-MAIN@LISTSERV.UA.EDU > >Betreff: Using Windows ssh with z/OS > > > >When connecting to z/OS (USS) using ssh, I'd like the USS shell to handle > >keys the same way Ubuntu does. I have these settings: > > > >echo $TERM displays xterm-color256 > >echo $SHELL displays /bin/sh > > > >Specifically, I'd like: > > > >a) The cursor-up key to perform the "history-search-backward" function > >b) The cursor-down key to perform the "history-search-forward" function > >c) The cursor-left and cursor-right keys to move thru the command just > >retrieved > >d) To be able to change the command by moving the cursor and typing over the > >retrieved command > > > Those are bash-isms. They may be unavailable in /bin/sh. > EXC-k and ESC-j are alternatives. > -- gil bash is available from Rocket: https://www.rocketsoftware.com/product-categories/mainframe/bash-zos -- Don Poitras - SAS Development - SAS Institute Inc. - SAS Campus Drive sas...@sas.com (919) 531-5637Cary, NC 27513 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
