I rarely use the TSO OMVS shell - I just keep a few ssh sessions open for using the z/OS Unix shell. Once you get used to a few basics, you won't want to use TSO OMVS, and as a bonus you will be more comfortable on any UNIX system.
It is well worth learning a tiny bit of vi so that you can use vi line editing mode. How tiny? A half-dozen commands are enough to be productive. Note: some prefer emacs mode, but those are usually the ones who already know emacs. To do this, first enable vi line editing mode in the shell: (can do this in your .profile) set -o vi If vi line editing mode is set, you edit any line that you are typing. When typing you will be in vi "insert" mode, so press escape to get into edit mode. Then here are the basic six vi commands you need to know: h to go left, l to go right, x to delete a char, ^ for the beginning of the line $ for the end of the line i or a to go back into insert mode To edit your command history, press esc-k. Press additional k keys to get older commands. After you have the command you want, you will be in vi edit mode. After editing, press enter to submit. Finally, in vi line editing mode, you can type the beginning of a file name and then esc-\ to complete it. esc-= will give you a list of matches. Kirk Wolf Dovetailed Technologies http://dovetail.com On Wed, Jun 3, 2015 at 2:17 PM, Rob Schramm <[email protected]> wrote: > Ugh.. I think it would just be easier to re-type the command! > > Rob Schramm > > On Tue, Jun 2, 2015 at 12:20 PM Paul Gilmartin < > [email protected]> wrote: > > > ("Re: AW: Re: AW: Re: AW:" trimmed.) > > > > On Tue, 2 Jun 2015 17:48:13 +0200, Peter Hunkeler wrote: > > > > >>>Well, as I wrote, the OMVS command processor > > > > > > >>There's more to OMVS than just the shell. The phrase "but OMVS has no > > >>access" clearly refers to more than the shell. > > > > > >Not sure what you're referring to, but I was talking about the OMVS *TSO > > command processor*, only. And no, that statement you cited does neither > > refer to a shell nor to anything more than what I wrote: The OMVS TSO > > Command processor has not been programmed to read/write/care for any > > command history file any UNIX shell program might use. > > > > > In 3270 TSO OMVS, I can use the escape character (default is "¢") to > enter > > control > > codes. So, with "set -o vi", I can do "¢[kkkkk<ENTER>" to execute the > > fifth previous > > command. Unfortunately, it executes the command immediately, rather than > > just > > fetching it to the input area for modification before execution. I'm > > calling this > > a bug; IBM probably thinks it's WAD. (PF10 (Refresh) doesn't help.) > > > > -- gil > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to [email protected] with the message: INFO IBM-MAIN > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
