On Wed, Jan 6, 2010 at 07:01, Shmuel Metz (Seymour J.) < shmuel+ibm-m...@patriot.net <shmuel%2bibm-m...@patriot.net>> wrote:
> In <d9d0c4681001051505w592508dfh92c302da9e77f...@mail.gmail.com>, on > 01/05/2010 > at 03:05 PM, Donald Russell <russell....@gmail.com> said: > > >Is USS the same thing as "OMVS"? > > Officially USS is Unformatted System Services, but many people > unofficially misuse the acronym to refer to Unix System Services. There's > also a distinction between using Unix System Services and logging on to > the Unix System Services shell. > > The acronym OMVS is a bit confusing because it refers both to Unix System > Services and to a specific address space. > > >I'm told USS is not available on the others. > > These days a lot of MVS software depends on Unix System Services, so I > suspect that what they mean is that you can't telnet to a Unix System > Services shell on those systems. However, they might mean that the > security data base doesn't have OMVS segments for normal users except on > one system. > > >What I'd like to do is invoke sftp from a rexx clist > > Rexx and CLIST are completely different animals. > The idea I was trying to convey is I wanted to invoke an sftp file transfer from a program invoked as if it were a TSO command. I figured everybody is familiar with "clist" as a concept, rather than a specific language, and I specified REXX because I don't write clist language code any more. Which is the correct noun to refer to a program, read from SYSEXEC in a TSO address space? In TSO land I generally refer to them as "clists" though they're written in REXX. In VM/CMS land I call them "EXECs" even though they are written in REXX, or EXEC 2 or EXEC. On zLinux I call them "scripts" or "shell scripts" even though they may be written in REXX, php, bash shell, korn shell, etc... > > > In <d9d0c4681001051612v6e7df7ebye08eb562cdf4e...@mail.gmail.com>, on > 01/05/2010 > at 04:12 PM, Donald Russell <russell....@gmail.com> said: > > >It's not that OMVS isn't there, it's just we don't grant access to it > >regularly except on one of our MVS systems. I wonder why that is.... > >I'm guessing it's money. :-) > > There's no charge for enabling access to Unix System Services; my guess is > that they're not configured to share Unix file systems and don't want to > allocate separate home directories for each system. > > I suspect that's the reason... I have a TSO ID on each of these different MVS systems, no sharing of files between them, so I manually copy my rexx tools from one system to the others with TSO TRANSMIT/RECEIVE... *I* wouldn't mind if I could access Unix System Services even if the home directories were not shared... that's not much different than what we do now with TSO access. (And if it really mattered I could probably do something with rsync or similar) I'll poke around and see what the response is like... ---------------------------------------------------------------------- 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
