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

[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 OMVS, the obvious reading was that "OMVS" meant the component
and "OMVS TSO command processor" the TSO command.
 
-- 
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 ISO position; see  
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

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

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


--
Peter Hunkeler



--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN