AW: Re: OMVS command history

2015-05-25 Thread Peter Hunkeler
The shell (/bin/sh to be specific) writes all commands into its history file .sh_history. This is kept across sessions. Command line editing when in a ssh (telnet/rlogin) shell session will use this file, as well as the "fc" and "history" shell commands. When using TSO/OMVS (the 3270 interface)

AW: Re: OMVS command history

2015-06-04 Thread Peter Hunkeler
Thanks for this post. I was about to suggest to (mostly) forget about TSO OMVS and start logging in via ssh. You've taken the burden off me :-) >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

Re: AW: Re: OMVS command history

2015-05-31 Thread Shmuel Metz (Seymour J.)
In , on 05/25/2015 at 09:27 PM, Peter Hunkeler said: >but OMVS has no access to this file. What about the history command? -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see We don't care. We don't have to care, we're C

AW: Re: AW: Re: OMVS command history

2015-05-31 Thread Peter Hunkeler
>>but OMVS has no access to this file. >What about the history command? Well, as I wrote, the OMVS command processor has no access to the .sh_history file (because it has not been programmed that way). You can of course use the histroy shell command. But this is not related to what the OP aske

Re: AW: Re: AW: Re: OMVS command history

2015-06-02 Thread Shmuel Metz (Seymour J.)
In , on 06/01/2015 at 07:51 AM, Peter Hunkeler said: >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. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see

AW: Re: AW: Re: AW: Re: OMVS command history

2015-06-02 Thread Peter Hunkeler
>>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 c

Re: AW: Re: AW: Re: AW: Re: OMVS command history

2015-06-04 Thread Shmuel Metz (Seymour J.)
In , on 06/02/2015 at 05:48 PM, Peter Hunkeler said: >Not sure what you're referring to, Your claim "but OMVS has no access to this file." in , on 05/25/2015 >but I was talking about the OMVS *TSO command processor*, Given that there is a component called OMVS and also a TSO command called