Well as a message code... actually if you look through that manual, there are a few uses that seem a bit 'footloose and fancy free.' But still nothing directly indicating USS = Unix Systems Services. May as well take the leap and equate the two.
Example 1: Export USS /u/user* or MVS A.B in export file. Maestro GUI: Note: Check the z/OS USS BPXPRMxx parmlib member for INADDRANYPORT and INADDRANYCOUNT. Their range cannot include the z/OS NFS server port ranges for the server to initialize. See z/OS Communications Server: IP Configuration Guide for more details. Using NFS v4 protocol (NFSv4) name mapping, a user can map owner and group names on a single DNS domain (INET environment) or on multiple DNS domains (CINET environment) to z/OS USS uid and gid numeric values. nfsv4domain(NFSv4_default_domain) specifies the "pseudo" NFSv4 domain for the -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Paul Gilmartin Sent: Tuesday, March 19, 2019 4:49 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: OpenSSH / Ported Tools / Co:Z On Tue, 19 Mar 2019 20:49:14 +0000, Seymour J Metz wrote: >> Unix System Services is not in an IBM manual > >WTF? >https://www-01.ibm.com/servers/resourcelink/svc00100.nsf/pages/zOSV2R3UnixSystemServicesPublications?OpenDocument > lists a bunch of manuals with Unix System Services in the title: > > z/OS UNIX System Services Command Reference, SA23-2280-30 z/OS UNIX > System Services File System Interface Reference, SA23-2285-30 z/OS > UNIX System Services Messages and Codes, SA23-2284-30 z/OS UNIX > System Services Planning, GA32-0884-30 z/OS UNIX System Services > Programming Tools, SA23-2282-30 z/OS UNIX System Services > Programming: Assembler Callable Services Reference, SA23-2281-30 z/OS > UNIX System Services User's Guide, SA23-2279-30 z/OS Using REXX and > z/OS UNIX System Services, SA23-2283-30 > I believe Mark misstated his intent and Shmuel (characteristically) took him literally. I suspect the intent was, "USS does not represent Unix System Services in any IBM manual." And that's false. The first of many such uses returned by the enormously useful "zOS_V2R3_Documentation.pdx" index in the 2017 zipped collection is: z/OSIBM Network File System Guide and Reference Version 2 Release 3 SC23-6883-30 containing: USS JRcccc reason codes (0000-0FFF) A yyyy value in the range 0000 to 0FFF indicates that the reason code matches one of the USS JRcccc reason codes described in z/OS UNIX System Services Messages and Codes. These reason codes can potentially appear for any NFS Client or NFS Server module. >________________________________________ >From: Schuffenhauer, Mark >Sent: Tuesday, March 19, 2019 4:29 PM > >United States Ship? > > I had never thought USS was not Unix System Services. I did VTAM work for > many years, so I was familiar with USS as Unformatted System Services, (which > you can find in an IBM manual). > >Unix System Services is not in an IBM manual, which I disbelieved and had to >do some bulk searching to determine. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN DISCLAIMER: This email and any attachments may contain confidential information that is intended solely for use by the intended recipient(s). If you are not the intended recipient, you are strictly prohibited from disclosing, copying, distributing or using any of the information contained in the communication. If you received this email in error, please contact the sender by reply email and immediately delete the communication. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
