Good discussion.   As OP, I was hoping for some consensus that "Under
z/OS Unix" or "Under USS" are not very useful terms since most people
don't recognize them as meaning "any dubbed z/OS Unix process".
"Under a z/OS Unix shell" or "program in a zFS filesystem" are closer
to what most people see to think of.    But I don't care to discuss
"proper" terminology - there is enough of that around here.   More
interesting to me is to better understand how z/OS Unix works and what
needs improvement.

Kirk Wolf
Dovetailed Technologies
http://dovetail.com

On Wed, May 4, 2011 at 1:44 PM, Mike Schwab <mike.a.sch...@gmail.com> wrote:
> On Wed, May 4, 2011 at 1:33 PM, Mark Zelden <m...@mzelden.com> wrote:
>> On Wed, 4 May 2011 12:48:14 -0400, Shmuel Metz (Seymour J.)
>> <shmuel+ibm-m...@patriot.net> wrote:
>>
>>>In <listserv%201105031010589557.0...@bama.ua.edu>, on 05/03/2011
>>>   at 10:10 AM, Mark Zelden <m...@mzelden.com> said:
>>>
>>>>But I think your last part I quoted is probably closer.   People
>>>>don't say "under USS" when they use FTP or Telnet for example,
>>>
>>>Which people? I certainly consider FTP and telnet in z/OS to be Unix
>>>services.
>>>
>>
>> The part I was addressing wasn't "what is z/OS Unix", rather it was
>> what people meant when they write or say "I was doing blah blah
>> under USS".   I've never heard anyone say "I was FTPing under USS" for
>> example unless they were executing FTP interactively from a shell of
>> some sort.
>>
>> Mark
>> --
>> Mark Zelden
> When I FTP a tersed dump or log to IBM, I use a batchjob with no step
> lib and control cards that reference z/OS PS files.  Yes, I did have
> to get a OMVS RACF segment in order to run, but the appearance of the
> control cards just look like a login FTP logoff sequence.
>

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to