>>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
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
>>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
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
