Re: A z/OS Redbook Corrected - just about!
In 4f96b993.2020...@phoenixsoftware.com, on 04/24/2012 at 07:32 AM, Jim Phoenix jimphoe...@phoenixsoftware.com said: Shmuel Metz (Seymour J.) wrote: IBM maintains a list of official acronyms and Unix system Services is not in that list. OpenEdition MVS See UNIX System Services. http://www-01.ibm.com/software/globalization/terminology/u.html#x2182787 There's no USS listed there: UNIX System Services An element of z/OS that creates a UNIX environment that conforms to XPG4 UNIX 1995 specifications and that provides two open-system interfaces on the z/OS operating system: an application programming interface (API) and an interactive shell interface. Wouldn't it make more sense to look under USS, where I see only: USS See unformatted system service. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html 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...@bama.ua.edu with the message: INFO IBM-MAIN
Re: A z/OS Redbook Corrected - just about!
In 481781196635.wa.elardus.engelbrechtsita.co...@bama.ua.edu, on 04/24/2012 at 12:06 PM, Elardus Engelbrecht elardus.engelbre...@sita.co.za said: Aw cr*p, hehehe ( :-D ) , there are at least two ( 2 ) definitions of USS shown there. FSVO two twice as large as the standard value. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html 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...@bama.ua.edu with the message: INFO IBM-MAIN
Re: A z/OS Redbook Corrected - just about!
In 4f97116c.2060...@bremultibank.com.pl, on 04/24/2012 at 10:47 PM, R.S. r.skoru...@bremultibank.com.pl said: They don't care. Don't be a hypocrite. You obviously care enough to jump in when anyone posts a correction. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html 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...@bama.ua.edu with the message: INFO IBM-MAIN
Re: A z/OS Redbook Corrected - just about!
In CAPD5F5rbXvyQC9-Zh1MX18uL4ipr8GS8a9EDncmVMd_=cxSF=w...@mail.gmail.com, on 04/22/2012 at 07:58 AM, John Gilmore johnwgilmore0...@gmail.com said: Almost all acronyms are overloaded. Yes. However, in this case it is an IBM acronym, IBM maintains a list of official acronyms and Unix system Services is not in that list. Can we now perhaps move on to other topics? Please do. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html 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...@bama.ua.edu with the message: INFO IBM-MAIN
Re: A z/OS Redbook Corrected - just about!
Shmuel Metz (Seymour J.) wrote: IBM maintains a list of official acronyms and Unix system Services is not in that list. OpenEdition MVS See UNIX System Services. http://www-01.ibm.com/software/globalization/terminology/u.html#x2182787 -- | Jim Phoenix | Voice: (310) 338-0400 x316 | | Senior Software Developer| Fax: (310) 338-0801| | Phoenix Software International || | 831 Parkview Drive North | jimphoe...@phoenixsoftware.com | | El Segundo, CA 90245 | http://www.phoenixsoftware.com | Opinions expressed by this individual are not necessarily those of the Company. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: A z/OS Redbook Corrected - just about!
No, Shmuel's point is that, while no one gainsays that UNIX Systems Services is IBM terminology, IBM has not associated the acronym USS with it in its 'official listing'. The URL you supply indeed supports his view. In begin extract UNIX System Services An element of z/OS that creates a UNIX environment that conforms to XPG4 UNIX 1995 specifications and that provides two open-system interfaces on the z/OS operating system: an application programming interface (API) and an interactive shell interface. UNIX-to-UNIX Copy Program (UUCP) The command (uucp) that starts file copying from one or more sources to a single destination. A group of commands, programs, and files that allows the user to communicate with another UNIX system over a dedicated line or a telephone line. /end extract the entry for UNIX Systems Services is not followed by an acronym, while that for UNIX-to-UNIX Copy Program is followed by one, (UCFP). This pother has nevertheless gone on long enough, indeed too long, as Schmuel apparently also agrees. John Gilmore, Ashland, MA 01721 - USA -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: A z/OS Redbook Corrected - just about!
In my previous post the text (UCFP) should of course be (UUCP) instead. My apologies. John Gilmore, Ashland, MA 01721 - USA -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: A z/OS Redbook Corrected - just about!
Jim Phoenix wrote: http://www-01.ibm.com/software/globalization/terminology/u.html#x2182787 Aw cr*p, hehehe ( :-D ) , there are at least two ( 2 ) definitions of USS shown there. Let us go the route of John G and Shmuel M - move on ( ... and you can just define the real USS when you post something involving USS.) Usually, I just enjoy reading the lot of really amusing yap-yap-yap about overloaded 'USS', but I now have to jump in here... ;-D Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: A z/OS Redbook Corrected - just about!
On Tue, 24 Apr 2012 12:06:24 -0500, Elardus Engelbrecht elardus.engelbre...@sita.co.za wrote: Jim Phoenix wrote: http://www-01.ibm.com/software/globalization/terminology/u.html#x2182787 Aw cr*p, hehehe ( :-D ) , there are at least two ( 2 ) definitions of USS shown there. There are? I see only one: quote USS See unformatted system service. /quote -- Walt -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: A z/OS Redbook Corrected - just about!
There are? I see only one: quote USS See unformatted system service. /quote And this very recent APAR describes a problem with a zFS loop in renaming processing after a BPX1REN ( rename, rename() ) syscall from Unformatted System Service. No wonder it caused a loop! g,d, r APAR Identifier .. OA38688 Last Changed 12/04/13 ZFS LOOP IN RENAME PROCESSING Symptom .. LP LOOP Status ... CLOSED PER Severity ... 2 Date Closed . 12/04/13 Component .. 5696EFS00 Duplicate of Reported Release . 3B0 Fixed Release 999 Component Name ZFS ZSERIES FIL Special Notice HIPER Current Target Date ..12/06/29 Flags SCP ... FUNCTIONLOSS Platform Status Detail: APARCLOSURE - APAR is being closed. PE PTF List: PTF List: Release 3B0 : PTF not available yet Release 3B0 : Relief is available in the form of: AA38688 Release 3D0 : PTF not available yet Release 3D0 : Relief is available in the form of: BA38688 Parent APAR: Child APAR list: ERROR DESCRIPTION: A loop in zFS rename processing ( ZFSRENAM ) occurred after a BPX1REN ( rename, rename() ) syscall from USS. The token structure on the rename consists of the source directory vnode and the source vnode and the new token structure of the target directory vnode and the target vnode. The trace has shown the source directory vnode being the same as the target vnode which is incorrect and drove the loop. LOCAL FIX: None PROBLEM SUMMARY: * USERS AFFECTED: zFS Release 11 and zFS Release 13* * zFS FMID:HZFS3B0 and FMID:HZFS3D0* * PROBLEM DESCRIPTION: A loop in zFS rename processing * * ZFSRENAM occurred after a * * BPX1REN syscall from USS was made. * * RECOMMENDATION: APPLY PTF* The vnodes for the operation are passed as input to zFS by the USS. The sdevp should not be the same as tdevp. PROBLEM CONCLUSION: A validity check of the input vnodes was added. In addition, code was added to ctkc_Lock4Vnodes to exit the loop if we are in recovery. TEMPORARY FIX: * * HIPER * * -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: A z/OS Redbook Corrected - just about!
It's boring. Another example for USS meaning Unix system services, not Unformatted system services. Yes, IBMer do use USS for Unix SS, regardless it is official or not official. And yes we can discuss what the acronym is and what is IBM authority to authorize the acronyms since it part of the English language. AFAIK English language is not a product of IBM, so I can freely use USS for USS Pampanito (I visited it in San Francisco) without IBM approvement. And yes there are two or three IBM-MAIN members (I call them fundamentalists) who fight for the only usage of USS acronym. The rest, about 4,500 f*ck the idea of the only meaning of saint USS_Acronym. They don't care. They udnerstand that many acronyms are overloaded and the meaning of the acronym should be explained explicitly or should be obvious from the context. So, my idea is to consequently ignore emails from USS fundamentalists and not to discuss about USS meaning. It is nonsense to discuss with 1 (up to three) persons about USS acronym meaning. This is NOT the purpose of the group. Let's back to discussion about mainframes, z/OS, USS (UNIX System Services), USS (Unformatted System Services), VTAM, SNA, TCPIP, SMS, RACF, CSI, CSI (guess why I used it TWICE), HCD, etc. etc. This is not forum about one persons idee fixe or fobia. -- Radoslaw Skorupka Lodz, Poland W dniu 2012-04-24 21:17, Mark Zelden pisze: There are? I see only one: quote USS See unformatted system service. /quote And this very recent APAR describes a problem with a zFS loop in renaming processing after a BPX1REN ( rename, rename() ) syscall from Unformatted System Service. No wonder it caused a loop!g,d, r APAR Identifier .. OA38688 Last Changed 12/04/13 ZFS LOOP IN RENAME PROCESSING Symptom .. LP LOOP Status ... CLOSED PER Severity ... 2 Date Closed . 12/04/13 Component .. 5696EFS00 Duplicate of Reported Release . 3B0 Fixed Release 999 Component Name ZFS ZSERIES FIL Special Notice HIPER Current Target Date ..12/06/29 Flags SCP ... FUNCTIONLOSS Platform Status Detail: APARCLOSURE - APAR is being closed. PE PTF List: PTF List: Release 3B0 : PTF not available yet Release 3B0 : Relief is available in the form of: AA38688 Release 3D0 : PTF not available yet Release 3D0 : Relief is available in the form of: BA38688 Parent APAR: Child APAR list: ERROR DESCRIPTION: A loop in zFS rename processing ( ZFSRENAM ) occurred after a BPX1REN ( rename, rename() ) syscall from USS. The token structure on the rename consists of the source directory vnode and the source vnode and the new token structure of the target directory vnode and the target vnode. The trace has shown the source directory vnode being the same as the target vnode which is incorrect and drove the loop. LOCAL FIX: None PROBLEM SUMMARY: * USERS AFFECTED: zFS Release 11 and zFS Release 13* * zFS FMID:HZFS3B0 and FMID:HZFS3D0* * PROBLEM DESCRIPTION: A loop in zFS rename processing * * ZFSRENAM occurred after a * * BPX1REN syscall from USS was made. * * RECOMMENDATION: APPLY PTF* The vnodes for the operation are passed as input to zFS by the USS. The sdevp should not be the same as tdevp. PROBLEM CONCLUSION: A validity check of the input vnodes was added. In addition, code was added to ctkc_Lock4Vnodes to exit the loop if we are in recovery. TEMPORARY FIX: * * HIPER * * -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- Tre tej wiadomoci moe zawiera informacje prawnie chronione Banku przeznaczone wycznie do uytku subowego adresata. Odbiorc moe by jedynie jej adresat z wyczeniem dostpu osób trzecich. Jeeli nie jeste adresatem niniejszej wiadomoci lub pracownikiem upowanionym do jej przekazania adresatowi, informujemy, e jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne dziaanie o podobnym charakterze jest prawnie zabronione i moe by karalne. Jeeli otrzymae t wiadomo omykowo, prosimy niezwocznie zawiadomi nadawc wysyajc odpowied oraz trwale usun t wiadomo wczajc w to wszelkie jej kopie wydrukowane lub zapisane na dysku.
Re: A z/OS Redbook Corrected - just about!
On 24 Apr 2012 13:53:26 -0700, in bit.listserv.ibm-main you wrote: It's boring. Another example for USS meaning Unix system services, not Unformatted system services. Yes, IBMer do use USS for Unix SS, regardless it is official or not official. And yes we can discuss what the acronym is and what is IBM authority to authorize the acronyms since it part of the English language. AFAIK English language is not a product of IBM, so I can freely use USS for USS Pampanito (I visited it in San Francisco) without IBM approvement. And yes there are two or three IBM-MAIN members (I call them fundamentalists) who fight for the only usage of USS acronym. The rest, about 4,500 f*ck the idea of the only meaning of saint USS_Acronym. They don't care. They udnerstand that many acronyms are overloaded and the meaning of the acronym should be explained explicitly or should be obvious from the context. So, my idea is to consequently ignore emails from USS fundamentalists and not to discuss about USS meaning. It is nonsense to discuss with 1 (up to three) persons about USS acronym meaning. This is NOT the purpose of the group. Let's back to discussion about mainframes, z/OS, USS (UNIX System Services), USS (Unformatted System Services), VTAM, SNA, TCPIP, SMS, RACF, CSI, CSI (guess why I used it TWICE), HCD, etc. etc. This is not forum about one persons idee fixe or fobia. Crime Scene Investigator checking out bad use of Catalog Search Interface? G.D. and R. Clark Morris -- Radoslaw Skorupka Lodz, Poland W dniu 2012-04-24 21:17, Mark Zelden pisze: There are? I see only one: quote USS See unformatted system service. /quote And this very recent APAR describes a problem with a zFS loop in renaming processing after a BPX1REN ( rename, rename() ) syscall from Unformatted System Service. No wonder it caused a loop!g,d, r APAR Identifier .. OA38688 Last Changed 12/04/13 ZFS LOOP IN RENAME PROCESSING Symptom .. LP LOOP Status ... CLOSED PER Severity ... 2 Date Closed . 12/04/13 Component .. 5696EFS00 Duplicate of Reported Release . 3B0 Fixed Release 999 Component Name ZFS ZSERIES FIL Special Notice HIPER Current Target Date ..12/06/29 Flags SCP ... FUNCTIONLOSS Platform Status Detail: APARCLOSURE - APAR is being closed. PE PTF List: PTF List: Release 3B0 : PTF not available yet Release 3B0 : Relief is available in the form of: AA38688 Release 3D0 : PTF not available yet Release 3D0 : Relief is available in the form of: BA38688 Parent APAR: Child APAR list: ERROR DESCRIPTION: A loop in zFS rename processing ( ZFSRENAM ) occurred after a BPX1REN ( rename, rename() ) syscall from USS. The token structure on the rename consists of the source directory vnode and the source vnode and the new token structure of the target directory vnode and the target vnode. The trace has shown the source directory vnode being the same as the target vnode which is incorrect and drove the loop. LOCAL FIX: None PROBLEM SUMMARY: * USERS AFFECTED: zFS Release 11 and zFS Release 13* * zFS FMID:HZFS3B0 and FMID:HZFS3D0* * PROBLEM DESCRIPTION: A loop in zFS rename processing * * ZFSRENAM occurred after a * * BPX1REN syscall from USS was made. * * RECOMMENDATION: APPLY PTF* The vnodes for the operation are passed as input to zFS by the USS. The sdevp should not be the same as tdevp. PROBLEM CONCLUSION: A validity check of the input vnodes was added. In addition, code was added to ctkc_Lock4Vnodes to exit the loop if we are in recovery. TEMPORARY FIX: * * HIPER * * -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: A z/OS Redbook Corrected - just about!
Almost all acronyms are overloaded. In some contexts this overloading can be ambiguous, even misleading; in others it is not. All of the arguments about this issue have been set out, chewed over, and regurgitated repeatedly. No consensus has emerged, and none is likely. Can we now perhaps move on to other topics? John Gilmore, Ashland, MA 01721 - USA -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: A z/OS Redbook Corrected - just about!
Well, shouldn't that be USST? But yes cobber, it could be a contraction of Unix System Services Table. It could even be Universal Studios Singapore Table. Geez, why is it that VTAM should have a mortgage over these three letters. I'm going to write to the United States Senate (USS) about this. If one has difficulty understanding the context it's their problem, not mine. You know when someone is talking about a ship, shell scripts or a modify table which USS they are referring to, so get smart and adapt. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Dick Bond Sent: Thursday, April 12, 2012 2:47 PM To: IBM-MAIN@bama.ua.edu Subject: Re: [IBM-MAIN] A z/OS Redbook Corrected - just about! Oh, so USSTAB means Unix Systems Services table. Wonder what that's used for, mate? On Fri, Apr 6, 2012 at 10:20 PM, Ron Hawkins ronjhawk...@sbcglobal.netwrote: Chris, I took your advice and read this post, but then I took it to a higher authority for validation. Yes, I googled acronym USS.' Mate, I'm sure I don't have to tell you that the internet holds the keys that unlock all mysteries, and for this one I was horrified to find that for all your hard work, the first hit in Google just simply did not support your position. There was the site with all the answers staring me in the face, waiting for the USS conundrum to be unraveled at a hit labeled USS - Definition by AcronymFinder. I mean, this has to be place to find the correct meaning of an acronym - forget all these red books and stuff. And so I curtailed my googling activities, sallied forth, clicked my mouse button, and infiltrated this place of purveyance to negotiate the reading of some contracted comestibles. And there it was, on the fifth line of the list: Unix System Services (IBM). I'm afraid there was no mention of that other meaning you are always talking about. I mean, based on this unassailable reference it is hard to believe that Unformatted System Services was ever abbreviated to USS, and probably should not have been because all the math's majors working in mainframes back then would have immediately been misled into thinking one was talking about the Uncorrected Sum of Squares (did you know that SAS has a USS function - you should write to them and get them to change it). So I'm afraid we have Internet 1, Chris nil, and we should all start using USS the way God and Google intended us to. Ron -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Chris Mason Sent: Wednesday, March 21, 2012 5:35 AM To: IBM-MAIN@bama.ua.edu Subject: [IBM-MAIN] A z/OS Redbook Corrected - just about! Back in early February, I sent off this comment to the redbooks site: comment To whom it may concern, - This feedback concerns redbook z/OS Version 1 Release 13 Implementation, SG24-7946-00, which is described still to be in Draft status. - Recently I wanted to check on what z/OSMF was all about. Expecting to be more quickly enlightened by finding a suitable redbook, I tried z/OSMF as a search word on the redbooks site. There were 3 hits, the first, gratifyingly, was entitled z/OS Management Facility. The other two were z/OS Version 1 Release xx Implementation, where xx was 12 and 13. I happened to notice the following at the beginning of the z/OS UNIX System Services chapter in the release 13 redbook: quote z/OS UNIX System Services, is an element of z/OS, is a UNIX operating environment, and is implemented within the z/OS operating system. It is also known as z/OS UNIX. In addition, there is a short abbreviation called USS. /quote How very curious, I thought. How did this mistake creep in? I then checked the beginning of the z/OS UNIX System Services chapter in the release 12 redbook and found that the curious addition had been slipped in only in the later V1R13 edition: quote The UNIX System Services element of z/OS is a UNIX operating environment, implemented within the z/OS operating system. It is also known as z/OS UNIX. /quote Since the V1R13 redbook is still in draft status, the inappropriate text can be removed. - First, in order to confirm that the abbreviation sanctioned by the authors of the manuals when UNIX System Services was introduced, we can pick any of the front-line manuals, the OS/390 MVS Initialization and Tuning Reference being one: quote CHANGES Summary of Changes ... As part of the name change of OS/390 OpenEdition to OS/390 UNIX System Services, occurrences of OS/390 OpenEdition have been changed to OS/390 UNIX System Services or its abbreviated name, OS/390 UNIX. ... /quote http
Re: A z/OS Redbook Corrected - just about!
Ron, There are all the Navy ships to USS ..United States Ship Scott Ford Senior Systems Engineer www.identityforge.com On Apr 21, 2012, at 4:39 PM, Ron Hawkins ronjhawk...@sbcglobal.net wrote: Well, shouldn't that be USST? But yes cobber, it could be a contraction of Unix System Services Table. It could even be Universal Studios Singapore Table. Geez, why is it that VTAM should have a mortgage over these three letters. I'm going to write to the United States Senate (USS) about this. If one has difficulty understanding the context it's their problem, not mine. You know when someone is talking about a ship, shell scripts or a modify table which USS they are referring to, so get smart and adapt. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Dick Bond Sent: Thursday, April 12, 2012 2:47 PM To: IBM-MAIN@bama.ua.edu Subject: Re: [IBM-MAIN] A z/OS Redbook Corrected - just about! Oh, so USSTAB means Unix Systems Services table. Wonder what that's used for, mate? On Fri, Apr 6, 2012 at 10:20 PM, Ron Hawkins ronjhawk...@sbcglobal.netwrote: Chris, I took your advice and read this post, but then I took it to a higher authority for validation. Yes, I googled acronym USS.' Mate, I'm sure I don't have to tell you that the internet holds the keys that unlock all mysteries, and for this one I was horrified to find that for all your hard work, the first hit in Google just simply did not support your position. There was the site with all the answers staring me in the face, waiting for the USS conundrum to be unraveled at a hit labeled USS - Definition by AcronymFinder. I mean, this has to be place to find the correct meaning of an acronym - forget all these red books and stuff. And so I curtailed my googling activities, sallied forth, clicked my mouse button, and infiltrated this place of purveyance to negotiate the reading of some contracted comestibles. And there it was, on the fifth line of the list: Unix System Services (IBM). I'm afraid there was no mention of that other meaning you are always talking about. I mean, based on this unassailable reference it is hard to believe that Unformatted System Services was ever abbreviated to USS, and probably should not have been because all the math's majors working in mainframes back then would have immediately been misled into thinking one was talking about the Uncorrected Sum of Squares (did you know that SAS has a USS function - you should write to them and get them to change it). So I'm afraid we have Internet 1, Chris nil, and we should all start using USS the way God and Google intended us to. Ron -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Chris Mason Sent: Wednesday, March 21, 2012 5:35 AM To: IBM-MAIN@bama.ua.edu Subject: [IBM-MAIN] A z/OS Redbook Corrected - just about! Back in early February, I sent off this comment to the redbooks site: comment To whom it may concern, - This feedback concerns redbook z/OS Version 1 Release 13 Implementation, SG24-7946-00, which is described still to be in Draft status. - Recently I wanted to check on what z/OSMF was all about. Expecting to be more quickly enlightened by finding a suitable redbook, I tried z/OSMF as a search word on the redbooks site. There were 3 hits, the first, gratifyingly, was entitled z/OS Management Facility. The other two were z/OS Version 1 Release xx Implementation, where xx was 12 and 13. I happened to notice the following at the beginning of the z/OS UNIX System Services chapter in the release 13 redbook: quote z/OS UNIX System Services, is an element of z/OS, is a UNIX operating environment, and is implemented within the z/OS operating system. It is also known as z/OS UNIX. In addition, there is a short abbreviation called USS. /quote How very curious, I thought. How did this mistake creep in? I then checked the beginning of the z/OS UNIX System Services chapter in the release 12 redbook and found that the curious addition had been slipped in only in the later V1R13 edition: quote The UNIX System Services element of z/OS is a UNIX operating environment, implemented within the z/OS operating system. It is also known as z/OS UNIX. /quote Since the V1R13 redbook is still in draft status, the inappropriate text can be removed. - First, in order to confirm that the abbreviation sanctioned by the authors of the manuals when UNIX System Services was introduced, we can pick any of the front-line manuals, the OS/390 MVS Initialization and Tuning Reference being one: quote CHANGES Summary of Changes ... As part of the name change of OS/390 OpenEdition to OS/390 UNIX System Services, occurrences of OS/390 OpenEdition have been changed to OS/390 UNIX System Services or its abbreviated name, OS/390 UNIX
Re: A z/OS Redbook Corrected - just about!
At the last conference I attended, the Unix Systems Services table was used for serving Guinness, and was one of the busiest tables. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Dick Bond Sent: April 12, 2012 4:47 PM To: IBM-MAIN@bama.ua.edu Subject: Re: A z/OS Redbook Corrected - just about! Oh, so USSTAB means Unix Systems Services table. Wonder what that's used for, mate? On Fri, Apr 6, 2012 at 10:20 PM, Ron Hawkins ronjhawk...@sbcglobal.netwrote: Chris, I took your advice and read this post, but then I took it to a higher authority for validation. Yes, I googled acronym USS.' Mate, I'm sure I don't have to tell you that the internet holds the keys that unlock all mysteries, and for this one I was horrified to find that for all your hard work, the first hit in Google just simply did not support your position. There was the site with all the answers staring me in the face, waiting for the USS conundrum to be unraveled at a hit labeled USS - Definition by AcronymFinder. I mean, this has to be place to find the correct meaning of an acronym - forget all these red books and stuff. And so I curtailed my googling activities, sallied forth, clicked my mouse button, and infiltrated this place of purveyance to negotiate the reading of some contracted comestibles. And there it was, on the fifth line of the list: Unix System Services (IBM). I'm afraid there was no mention of that other meaning you are always talking about. I mean, based on this unassailable reference it is hard to believe that Unformatted System Services was ever abbreviated to USS, and probably should not have been because all the math's majors working in mainframes back then would have immediately been misled into thinking one was talking about the Uncorrected Sum of Squares (did you know that SAS has a USS function - you should write to them and get them to change it). So I'm afraid we have Internet 1, Chris nil, and we should all start using USS the way God and Google intended us to. Ron -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Chris Mason Sent: Wednesday, March 21, 2012 5:35 AM To: IBM-MAIN@bama.ua.edu Subject: [IBM-MAIN] A z/OS Redbook Corrected - just about! Back in early February, I sent off this comment to the redbooks site: comment To whom it may concern, - This feedback concerns redbook z/OS Version 1 Release 13 Implementation, SG24-7946-00, which is described still to be in Draft status. - Recently I wanted to check on what z/OSMF was all about. Expecting to be more quickly enlightened by finding a suitable redbook, I tried z/OSMF as a search word on the redbooks site. There were 3 hits, the first, gratifyingly, was entitled z/OS Management Facility. The other two were z/OS Version 1 Release xx Implementation, where xx was 12 and 13. I happened to notice the following at the beginning of the z/OS UNIX System Services chapter in the release 13 redbook: quote z/OS UNIX System Services, is an element of z/OS, is a UNIX operating environment, and is implemented within the z/OS operating system. It is also known as z/OS UNIX. In addition, there is a short abbreviation called USS. /quote How very curious, I thought. How did this mistake creep in? I then checked the beginning of the z/OS UNIX System Services chapter in the release 12 redbook and found that the curious addition had been slipped in only in the later V1R13 edition: quote The UNIX System Services element of z/OS is a UNIX operating environment, implemented within the z/OS operating system. It is also known as z/OS UNIX. /quote Since the V1R13 redbook is still in draft status, the inappropriate text can be removed. - First, in order to confirm that the abbreviation sanctioned by the authors of the manuals when UNIX System Services was introduced, we can pick any of the front-line manuals, the OS/390 MVS Initialization and Tuning Reference being one: quote CHANGES Summary of Changes ... As part of the name change of OS/390 OpenEdition to OS/390 UNIX System Services, occurrences of OS/390 OpenEdition have been changed to OS/390 UNIX System Services or its abbreviated name, OS/390 UNIX. ... /quote http://publibz.boulder.ibm.com/cgi- bin/bookmgr_OS390/BOOKS/IEA1E211/CHANGES Thus we have it confirmed that OS/390 UNIX is the supported abbreviation, clearly to be transformed to z/OS UNIX when z/OS was introduced and that there is nary a mention of any other abbreviation. After all, one abbreviation should be sufficient, shouldn't it? In case there is any doubt over the ancestry of this other abbreviation, we have the following web page in order to remind us what, within IBM, is the correct attribution: http://www- 01.ibm.com
Re: A z/OS Redbook Corrected - just about!
Oh, so USSTAB means Unix Systems Services table. Wonder what that's used for, mate? On Fri, Apr 6, 2012 at 10:20 PM, Ron Hawkins ronjhawk...@sbcglobal.netwrote: Chris, I took your advice and read this post, but then I took it to a higher authority for validation. Yes, I googled acronym USS.' Mate, I'm sure I don't have to tell you that the internet holds the keys that unlock all mysteries, and for this one I was horrified to find that for all your hard work, the first hit in Google just simply did not support your position. There was the site with all the answers staring me in the face, waiting for the USS conundrum to be unraveled at a hit labeled USS - Definition by AcronymFinder. I mean, this has to be place to find the correct meaning of an acronym - forget all these red books and stuff. And so I curtailed my googling activities, sallied forth, clicked my mouse button, and infiltrated this place of purveyance to negotiate the reading of some contracted comestibles. And there it was, on the fifth line of the list: Unix System Services (IBM). I'm afraid there was no mention of that other meaning you are always talking about. I mean, based on this unassailable reference it is hard to believe that Unformatted System Services was ever abbreviated to USS, and probably should not have been because all the math's majors working in mainframes back then would have immediately been misled into thinking one was talking about the Uncorrected Sum of Squares (did you know that SAS has a USS function - you should write to them and get them to change it). So I'm afraid we have Internet 1, Chris nil, and we should all start using USS the way God and Google intended us to. Ron -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Chris Mason Sent: Wednesday, March 21, 2012 5:35 AM To: IBM-MAIN@bama.ua.edu Subject: [IBM-MAIN] A z/OS Redbook Corrected - just about! Back in early February, I sent off this comment to the redbooks site: comment To whom it may concern, - This feedback concerns redbook z/OS Version 1 Release 13 Implementation, SG24-7946-00, which is described still to be in Draft status. - Recently I wanted to check on what z/OSMF was all about. Expecting to be more quickly enlightened by finding a suitable redbook, I tried z/OSMF as a search word on the redbooks site. There were 3 hits, the first, gratifyingly, was entitled z/OS Management Facility. The other two were z/OS Version 1 Release xx Implementation, where xx was 12 and 13. I happened to notice the following at the beginning of the z/OS UNIX System Services chapter in the release 13 redbook: quote z/OS UNIX System Services, is an element of z/OS, is a UNIX operating environment, and is implemented within the z/OS operating system. It is also known as z/OS UNIX. In addition, there is a short abbreviation called USS. /quote How very curious, I thought. How did this mistake creep in? I then checked the beginning of the z/OS UNIX System Services chapter in the release 12 redbook and found that the curious addition had been slipped in only in the later V1R13 edition: quote The UNIX System Services element of z/OS is a UNIX operating environment, implemented within the z/OS operating system. It is also known as z/OS UNIX. /quote Since the V1R13 redbook is still in draft status, the inappropriate text can be removed. - First, in order to confirm that the abbreviation sanctioned by the authors of the manuals when UNIX System Services was introduced, we can pick any of the front-line manuals, the OS/390 MVS Initialization and Tuning Reference being one: quote CHANGES Summary of Changes ... As part of the name change of OS/390 OpenEdition to OS/390 UNIX System Services, occurrences of OS/390 OpenEdition have been changed to OS/390 UNIX System Services or its abbreviated name, OS/390 UNIX. ... /quote http://publibz.boulder.ibm.com/cgi- bin/bookmgr_OS390/BOOKS/IEA1E211/CHANGES Thus we have it confirmed that OS/390 UNIX is the supported abbreviation, clearly to be transformed to z/OS UNIX when z/OS was introduced and that there is nary a mention of any other abbreviation. After all, one abbreviation should be sufficient, shouldn't it? In case there is any doubt over the ancestry of this other abbreviation, we have the following web page in order to remind us what, within IBM, is the correct attribution: http://www- 01.ibm.com/software/globalization/terminology/u.html#x2042481 quote IBM Terminology ... This site contains terms and definitions from many IBM software and hardware products as well as general computing terms. ... unformatted system service (USS) A communications function that translates a character-coded command, such as a LOGON or LOGOFF
Re: A z/OS Redbook Corrected - just about!
Hi Ron, Such language! Contracted comestibles. So what does that mean? I looked up comestibles, and it means edible. I have no idea what contracted edibles means. You get an A for humor though. Eric Bielefeld Sr. Systems Programmer IBM Global Services Division Dubuque, Iowa 414-477-7259 - Original Message - From: Ron Hawkins ronjhawk...@sbcglobal.net Subject: Re: A z/OS Redbook Corrected - just about! And so I curtailed my googling activities, sallied forth, clicked my mouse button, and infiltrated this place of purveyance to negotiate the reading of some contracted comestibles. Ron -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: A z/OS Redbook Corrected - just about!
Eric, Look up cheese shop sketch. It was a twist on one of my favorite John Cleese lines, substituting cheesy with contracted which is a synonym for abbreviate. An example of an abbreviation that springs to mind is USS for Unix System Services. Ron -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Eric Bielefeld Sent: Saturday, April 07, 2012 11:54 AM To: IBM-MAIN@bama.ua.edu Subject: Re: [IBM-MAIN] A z/OS Redbook Corrected - just about! Hi Ron, Such language! Contracted comestibles. So what does that mean? I looked up comestibles, and it means edible. I have no idea what contracted edibles means. You get an A for humor though. Eric Bielefeld Sr. Systems Programmer IBM Global Services Division Dubuque, Iowa 414-477-7259 - Original Message - From: Ron Hawkins ronjhawk...@sbcglobal.net Subject: Re: A z/OS Redbook Corrected - just about! And so I curtailed my googling activities, sallied forth, clicked my mouse button, and infiltrated this place of purveyance to negotiate the reading of some contracted comestibles. Ron -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: A z/OS Redbook Corrected - just about!
In order not to disturb those delicate souls who can't take too much of this topic, I have consolidated my responses. --- From Sebastian Welton Wed, 21 Mar 2012 10:48:13 -0500 ... then maybe IBM will have to change ***all*** their manuals. Obviously untrue! Of the 400 plus manuals in the z/OS elements and features bookshelves[1], about 40 are contaminated. Thus I'll allow an order of magnitude of 10 percent as a general estimate overall. It is not an infeasible objective to have essentially corrected with a bit of effort. Where the incorrect use appears, it, in effect, corresponds to John Eells's stray cats and they tend to appear in ones and twos in most manuals. In other words, it is never systematic. Looking back over some releases I have noticed some new text with a stray cat get herded back after an edition or two. I'll admit it doesn't happen every time and there a bit of work to be done. Thank you for the reminder that not all the contagion is to be found on the z/OS elements and features bookshelves and that contagion is more likely when the origin of the manual is the untrammelled domain of previously vendor products. Confusion could abound for the novice ... Indeed it could but, more likely, inevitably will. That is the major concern I try to emphasise but the noisy ones ignore. ... but I'm pretty sure that if someone sees: ... they are going to know what the book is discussing. That's as may be. But when someone saw quote Someone got the uss screen, was able to get into the production CICS, /quote he demonstrated he completely misunderstood what the post was discussing. Or let me take an invented example: But when someone sees invented quote Use an USS command to access the application. If you made a mistake, you will be able to see from the USS message returned what your mistake was. /invented quote and the reader has had no prior contact with this correct usage - for which the manual author may justifiably have felt no need whatsoever for a so-called clarification - they are *not* going to know what the book is discussing and they are going to be all at sea! Your confused novice may well have his or her eyes opened eventually with a bit of a shock when, because of downsizing, the old SNA/VTAM specialist is retired to the golf course and this novice is expected to take over. I've seen it happen. Fortunately I know there was a manager who could admit to dealing with it if necessary - his userid was on the ancient source files! - [1] http://www-03.ibm.com/systems/z/os/zos/bkserv/zshelves13.html --- From Kirk Wolf Wed, 21 Mar 2012 10:57:58 -0500 Thank goodness IBM is spending time correcting USS atrocities rather than improving z/OS Unix. Compensating for the sarcasm, I imagine the correction took about half an hour if my opposite experience over *re*introducing the correct abbreviation into the IBM z/OS V1Rxx Communications Server TCP/IP Implementation set of manuals a while ago is anything to go by. These computer thingamajigs are pretty good at this sort of thing! Incidentally ITSO is not in the business of actually improving products - that's development. ITSO have the responsibility to advise on how to use products, typically in combination, and provide background, tutorials and the like. --- From Rob Schramm Wed, 21 Mar 2012 12:07:00 -0400 I know that only a very short list of people will ever be truly confused by USS (unformatted system services) and USS (unix system services) references How can you possibly know anything of the sort! Even among IBM-MAIN subscribers we generally hear only from the spittle-flecked brigade on this topic - although I'm encouraged by some who have put their heads above the parapet and risked the slings and arrows of the outraged in order to express agreement. Try - hard this time - to understand the response above to Sebastian Walton. --- From Dick Bond Mon, 26 Mar 2012 10:16:32 -0700 I agree with Chris Mason. Thank you! IBM should have never started called it USS ... In principle - as John Eells explained to Eric Bielefeld who made the same assertion - IBM never did. It was careless IBM employees - starting - if the manuals I have tracked are anything to go by - with one author in one manual of three in the German development lab prior even to the name change from OpenEdition to UNIX System Services. IBM adores putting a z in front of everything (for some clueless reason) ... There's no accounting for the ideas suits get into their heads! Actually in a way, there is: if a suit pays for some marketing advice, it is likely to be introduced - because it was paid for, no matter how ridiculous. In MBA courses, this tendency is discouraged, but I guess the message doesn't always get through. --- From Mark Zelden Mon, 26 Mar 2012 13:21:56 -0500 but USS started long before z was ever around. Approximately a quarter of a century, from 1977 to 2001[1]. BTW, I still see
Re: A z/OS Redbook Corrected - just about!
Chris, I took your advice and read this post, but then I took it to a higher authority for validation. Yes, I googled acronym USS.' Mate, I'm sure I don't have to tell you that the internet holds the keys that unlock all mysteries, and for this one I was horrified to find that for all your hard work, the first hit in Google just simply did not support your position. There was the site with all the answers staring me in the face, waiting for the USS conundrum to be unraveled at a hit labeled USS - Definition by AcronymFinder. I mean, this has to be place to find the correct meaning of an acronym - forget all these red books and stuff. And so I curtailed my googling activities, sallied forth, clicked my mouse button, and infiltrated this place of purveyance to negotiate the reading of some contracted comestibles. And there it was, on the fifth line of the list: Unix System Services (IBM). I'm afraid there was no mention of that other meaning you are always talking about. I mean, based on this unassailable reference it is hard to believe that Unformatted System Services was ever abbreviated to USS, and probably should not have been because all the math's majors working in mainframes back then would have immediately been misled into thinking one was talking about the Uncorrected Sum of Squares (did you know that SAS has a USS function - you should write to them and get them to change it). So I'm afraid we have Internet 1, Chris nil, and we should all start using USS the way God and Google intended us to. Ron -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Chris Mason Sent: Wednesday, March 21, 2012 5:35 AM To: IBM-MAIN@bama.ua.edu Subject: [IBM-MAIN] A z/OS Redbook Corrected - just about! Back in early February, I sent off this comment to the redbooks site: comment To whom it may concern, - This feedback concerns redbook z/OS Version 1 Release 13 Implementation, SG24-7946-00, which is described still to be in Draft status. - Recently I wanted to check on what z/OSMF was all about. Expecting to be more quickly enlightened by finding a suitable redbook, I tried z/OSMF as a search word on the redbooks site. There were 3 hits, the first, gratifyingly, was entitled z/OS Management Facility. The other two were z/OS Version 1 Release xx Implementation, where xx was 12 and 13. I happened to notice the following at the beginning of the z/OS UNIX System Services chapter in the release 13 redbook: quote z/OS UNIX System Services, is an element of z/OS, is a UNIX operating environment, and is implemented within the z/OS operating system. It is also known as z/OS UNIX. In addition, there is a short abbreviation called USS. /quote How very curious, I thought. How did this mistake creep in? I then checked the beginning of the z/OS UNIX System Services chapter in the release 12 redbook and found that the curious addition had been slipped in only in the later V1R13 edition: quote The UNIX System Services element of z/OS is a UNIX operating environment, implemented within the z/OS operating system. It is also known as z/OS UNIX. /quote Since the V1R13 redbook is still in draft status, the inappropriate text can be removed. - First, in order to confirm that the abbreviation sanctioned by the authors of the manuals when UNIX System Services was introduced, we can pick any of the front-line manuals, the OS/390 MVS Initialization and Tuning Reference being one: quote CHANGES Summary of Changes ... As part of the name change of OS/390 OpenEdition to OS/390 UNIX System Services, occurrences of OS/390 OpenEdition have been changed to OS/390 UNIX System Services or its abbreviated name, OS/390 UNIX. ... /quote http://publibz.boulder.ibm.com/cgi- bin/bookmgr_OS390/BOOKS/IEA1E211/CHANGES Thus we have it confirmed that OS/390 UNIX is the supported abbreviation, clearly to be transformed to z/OS UNIX when z/OS was introduced and that there is nary a mention of any other abbreviation. After all, one abbreviation should be sufficient, shouldn't it? In case there is any doubt over the ancestry of this other abbreviation, we have the following web page in order to remind us what, within IBM, is the correct attribution: http://www- 01.ibm.com/software/globalization/terminology/u.html#x2042481 quote IBM Terminology ... This site contains terms and definitions from many IBM software and hardware products as well as general computing terms. ... unformatted system service (USS) A communications function that translates a character-coded command, such as a LOGON or LOGOFF command, into a field-formatted command for processing by formatted system services. See also formatted system service. ... USS See unformatted system service. ... /quote Now there are some - particularly to be found in the IBM-MAIN list - who will swear
Re: A z/OS Redbook Corrected - just about!
Since they have AIX on Power, how about zIX or MIX. One concern I have is an operating system name without z/OS implies a completely independent operating system, not a subsystem of z/OS. On Mon, Mar 26, 2012 at 9:34 PM, J R jayare...@hotmail.com wrote: I agree, why not zUnix? Or z/Unix? However, since Lynn Wheeler has reminded us that z/OS Unix is (to some degree) POSIX compliant/compatible, why not adopt a catchy contraction of POSIX? I'd like to suggest z/POX, which also connotes the blight it has become on z/OS. ;-) ... Date: Mon, 26 Mar 2012 10:16:32 -0700 From: dickbond...@gmail.com Subject: Re: A z/OS Redbook Corrected - just about! To: IBM-MAIN@bama.ua.edu I agree with Chris Mason. IBM should have never started called it USS - how about a simple definitive abbreviation, like zUnix. IBM adores putting a z in front of everything (for some clueless reason) so why should their version of Unix be any different? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: A z/OS Redbook Corrected - just about!
Many, especially around here, would go with a different expansion of the first three characters. And it's not Point Of Sale. They don't like the POSIX / UNIX (since it is X/Open branded) portion of z/OS at all. -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of J R Sent: Monday, March 26, 2012 9:34 PM To: IBM-MAIN@bama.ua.edu Subject: Re: A z/OS Redbook Corrected - just about! I agree, why not zUnix? Or z/Unix? However, since Lynn Wheeler has reminded us that z/OS Unix is (to some degree) POSIX compliant/compatible, why not adopt a catchy contraction of POSIX? I'd like to suggest z/POX, which also connotes the blight it has become on z/OS. ;-) ... Date: Mon, 26 Mar 2012 10:16:32 -0700 From: dickbond...@gmail.com Subject: Re: A z/OS Redbook Corrected - just about! To: IBM-MAIN@bama.ua.edu I agree with Chris Mason. IBM should have never started called it USS - how about a simple definitive abbreviation, like zUnix. IBM adores putting a z in front of everything (for some clueless reason) so why should their version of Unix be any different? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: A z/OS Redbook Corrected - just about!
After seeing this thread it's very apparent to me, IMHO, that someone at IBM missed the boat on the acronyms. Maybe an accident ? zUSS would have been better IMHO than calling Unix System Services , USS ...fwiw Sent from my iPad Scott Ford Senior Systems Engineer www.identityforge.com On Mar 27, 2012, at 8:21 AM, McKown, John john.mck...@healthmarkets.com wrote: Many, especially around here, would go with a different expansion of the first three characters. And it's not Point Of Sale. They don't like the POSIX / UNIX (since it is X/Open branded) portion of z/OS at all. -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of J R Sent: Monday, March 26, 2012 9:34 PM To: IBM-MAIN@bama.ua.edu Subject: Re: A z/OS Redbook Corrected - just about! I agree, why not zUnix? Or z/Unix? However, since Lynn Wheeler has reminded us that z/OS Unix is (to some degree) POSIX compliant/compatible, why not adopt a catchy contraction of POSIX? I'd like to suggest z/POX, which also connotes the blight it has become on z/OS. ;-) ... Date: Mon, 26 Mar 2012 10:16:32 -0700 From: dickbond...@gmail.com Subject: Re: A z/OS Redbook Corrected - just about! To: IBM-MAIN@bama.ua.edu I agree with Chris Mason. IBM should have never started called it USS - how about a simple definitive abbreviation, like zUnix. IBM adores putting a z in front of everything (for some clueless reason) so why should their version of Unix be any different? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: A z/OS Redbook Corrected - just about!
This could go another route and ask why every IBM product that is old, new or purchased via OEM, seems to be given the Tivoli brand name? ;-) On Tue, Mar 27, 2012 at 6:09 AM, Scott Ford scott_j_f...@yahoo.com wrote: After seeing this thread it's very apparent to me, IMHO, that someone at IBM missed the boat on the acronyms. Maybe an accident ? zUSS would have been better IMHO than calling Unix System Services , USS ...fwiw Sent from my iPad Scott Ford Senior Systems Engineer www.identityforge.com On Mar 27, 2012, at 8:21 AM, McKown, John john.mck...@healthmarkets.com wrote: Many, especially around here, would go with a different expansion of the first three characters. And it's not Point Of Sale. They don't like the POSIX / UNIX (since it is X/Open branded) portion of z/OS at all. -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of J R Sent: Monday, March 26, 2012 9:34 PM To: IBM-MAIN@bama.ua.edu Subject: Re: A z/OS Redbook Corrected - just about! I agree, why not zUnix? Or z/Unix? However, since Lynn Wheeler has reminded us that z/OS Unix is (to some degree) POSIX compliant/compatible, why not adopt a catchy contraction of POSIX? I'd like to suggest z/POX, which also connotes the blight it has become on z/OS. ;-) ... Date: Mon, 26 Mar 2012 10:16:32 -0700 From: dickbond...@gmail.com Subject: Re: A z/OS Redbook Corrected - just about! To: IBM-MAIN@bama.ua.edu I agree with Chris Mason. IBM should have never started called it USS - how about a simple definitive abbreviation, like zUnix. IBM adores putting a z in front of everything (for some clueless reason) so why should their version of Unix be any different? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: A z/OS Redbook Corrected - just about!
mike.a.sch...@gmail.com (Mike Schwab) writes: Since they have AIX on Power, how about zIX or MIX. One concern I have is an operating system name without z/OS implies a completely independent operating system, not a subsystem of z/OS. re: http://www.garlic.com/~lynn/2012e.html#13 A z/OS Redbook Corrected - just about! besides the OSF and POSIX support on MVS folklore recent tale of origin of AIX http://www.garlic.com/~lynn/2012e.html#2 was done for IBM by the company that had done port of ATT unix to ibm/pc as PC/IX ... i.e. ROMP was originally going to be the followon to the Displaywriter ... but when that was canceled, it was redirected to the unix workstation market (as PC/RT with AIX). RS/6000 and Power were then followon to PC/RT. the above also mentioned that the people that had done the initial development for what becomes SUN workstation, had come to IBM about producing the product. There was meeting in Palo Alto that included several organizations around the company ... afterwards several organizations all claimed that they were doing something better .. and IBM declined to come out with SUN workstation. Palo Alto had been working on port of Berkeley's unix work-alike (BSD) to mainframe ... but later get redirected to port it to the PC/RT ... coming out as AOS (as an alternative to AIX). I had done internal advanced technology conference spring of 1982 ... one of the first since the mid-70s ... when there was lots of corporate retrenching after the failure of Future System effort .. some past posts http://www.garlic.com/~lynn/submain.html#futuresys Presentations included BSD implementation on vm/370, TSS/370 UNIX PRPQ for ATT, and CMS running under MVS ... old post regarding the adtech conference http://www.garlic.com/~lynn/96.html#4a Palo Alto was also working with UCLA and its unix work-alike (Locus) ... and ported it to both mainframe and ps2 ... which was released as AIX/370 and AIX/386. Another unix work-alike was MACH done at CMU ... a derivative can still be found as the Apple operating system. recent tale of mainframe C language http://www.garlic.com/~lynn/2012d.html#64 Layer 8: NASA unplugs last mainframe There joint project between IBM and ATT for unix on the mainframe ... purely for ATT internal use ... it involved doing a stripped down TSS/370 (residual limited availability follow-on to TSS/360) kernel with unix higher levels layered on top. Part of the TSS/370 strategy was to provide an alternative to Amdahl's UTS (unix) Amdahl processors for large number of ATT installations. As an aside, person responsible for UTS (code named GOLD during development for Au or Amdahl Unix) had done port of unix to ibm mainframe at school. When he was graduating, some of us attempted unsuccesfully to get IBM to make him an offer. -- virtualization experience starting Jan1968, online at home since Mar1970 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: A z/OS Redbook Corrected - just about!
They ran out of W's so couldn't use Websphere anymore? -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Dick Bond Sent: Tuesday, March 27, 2012 11:04 AM To: IBM-MAIN@bama.ua.edu Subject: Re: A z/OS Redbook Corrected - just about! This could go another route and ask why every IBM product that is old, new or purchased via OEM, seems to be given the Tivoli brand name? ;-) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: A z/OS Redbook Corrected - just about!
Well, I know a corporation where everyone use Tivoli to name one of Tivoli-branded product. To be more funny, they use much more Tivoli products. I also met a guy who used 'Websphere' to call MQ. Ooops, I'm sorry: Websphere MQ. While I can live with IBM Tivoli Optim products, but I'm still forgetting new names for PPRC, XRC, etc. And 3494 successor (3584, more commonly known as TS3500). -- Radoslaw Skorupka Lodz, Poland W dniu 2012-03-27 23:00, Hylton Tom P pisze: They ran out of W's so couldn't use Websphere anymore? -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Dick Bond Sent: Tuesday, March 27, 2012 11:04 AM To: IBM-MAIN@bama.ua.edu Subject: Re: A z/OS Redbook Corrected - just about! This could go another route and ask why every IBM product that is old, new or purchased via OEM, seems to be given the Tivoli brand name? ;-) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- Tre tej wiadomoci moe zawiera informacje prawnie chronione Banku przeznaczone wycznie do uytku subowego adresata. Odbiorc moe by jedynie jej adresat z wyczeniem dostpu osób trzecich. Jeeli nie jeste adresatem niniejszej wiadomoci lub pracownikiem upowanionym do jej przekazania adresatowi, informujemy, e jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne dziaanie o podobnym charakterze jest prawnie zabronione i moe by karalne. Jeeli otrzymae t wiadomo omykowo, prosimy niezwocznie zawiadomi nadawc wysyajc odpowied oraz trwale usun t wiadomo wczajc w to wszelkie jej kopie wydrukowane lub zapisane na dysku. This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e-mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorised to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete permanently this e-mail including any copies of it either printed or saved to hard drive. BRE Bank SA, 00-950 Warszawa, ul. Senatorska 18, tel. +48 (22) 829 00 00, fax +48 (22) 829 00 33, www.brebank.pl, e-mail: i...@brebank.pl Sd Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego Rejestru Sdowego, nr rejestru przedsibiorców KRS 025237, NIP: 526-021-50-88. Wedug stanu na dzie 01.01.2012 r. kapita zakadowy BRE Banku SA (w caoci wpacony) wynosi 168.410.984 zotych. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: A z/OS Redbook Corrected - just about!
On Mon, 26 Mar 2012 22:34:01 -0400, J R jayare...@hotmail.com wrote: I agree, why not zUnix? Or z/Unix? While I enjoy the USS Naming Wars immensely (NOT), this particular question gets old, and I thought the answer would be obvious: You cannot take other peoples' trademarks and alter them or use them without permission. UNIX is a registered trademark of the Open Group. While it is convenient to call something UNIX System Services, it doesn't really stand by itself. The OS in question is not UNIX, but it is the UNIX-branded part of z/OS. It SHOULD have the word z/OS in it. I mean, perhaps the listener thinks you mean LINUX! Someone else mentioned POSIX, a registered trademark of the IEEE. They, working with the Open Group, will grant permission to use the POSIX mark to certify that [...] computer operating systems comply with standards of interoperability and portability based upon the UNIX operating system. Back in 2002, IBM cancelled its OpenEdition trademark (I vaguely remember reading in the media about some dispute with some other company.) In z/VM, it is called Open Extensions. Sure, some the names IBM comes up with are strange, to say the least, but they are not just random strings of characters. That is, there's a method to the madness, to be certain, but it's our particular *brand* of madness! :-) Alan Altmark IBM -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: A z/OS Redbook Corrected - just about!
I agree with Chris Mason. IBM should have never started called it USS - how about a simple definitive abbreviation, like zUnix. IBM adores putting a z in front of everything (for some clueless reason) so why should their version of Unix be any different? On Wed, Mar 21, 2012 at 11:31 AM, Scott Ford scott_j_f...@yahoo.com wrote: Amen, heaven forbid the improve unix systems services, btw I have worked Vtam and unix, so amen brothers and sisters I ave seen the Chris light, teasing Chris . Sent from my iPad Scott Ford Senior Systems Engineer www.identityforge.com On Mar 21, 2012, at 11:57 AM, Kirk Wolf k...@dovetail.com wrote: Thank goodness IBM is spending time correcting USS atrocities rather than improving z/OS Unix. Kirk Wolf Dovetailed Technologies http://dovetail.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: A z/OS Redbook Corrected - just about!
On Mon, 26 Mar 2012 10:16:32 -0700, Dick Bond wrote: I agree with Chris Mason. IBM should have never started called it USS - how about a simple definitive abbreviation, like zUnix. IBM adores putting a z in front of everything (for some clueless reason) so why should their version of Unix be any different? Sigh. That would be at hazard for branding changes, complicating archive searches, etc. Is it free of trademark encumbrances? Would it be reasonably unambiguous in WWW searches (unlike zFS vis-à-vis ZFS)? (What do people use nowadays as a keyword for that product?) -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: A z/OS Redbook Corrected - just about!
dickbond...@gmail.com (Dick Bond) writes: I agree with Chris Mason. IBM should have never started called it USS - how about a simple definitive abbreviation, like zUnix. IBM adores putting a z in front of everything (for some clueless reason) so why should their version of Unix be any different? back when MVS posix support started ... was in the unix wars period http://en.wikipedia.org/wiki/Unix_wars which also resulted in the formation of OSF http://en.wikipedia.org/wiki/Open_Software_Foundation to produce a posix, copyright-free implementation while we were doing HA/CMP product http://www.garlic.com/~lynn/subtopic.html#hacmp we also did some consulting to the executive that was behind doing the MVS posix implementation ... it was one of the many efforts to try and get around the strangle-hold that the communication group had on the datacenter ... attempting to reverse lots of stuff that was fleeing the mainframe to more distributed computing friendly platforms. -- virtualization experience starting Jan1968, online at home since Mar1970 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: A z/OS Redbook Corrected - just about!
On Mon, 26 Mar 2012 10:16:32 -0700, Dick Bond dickbond...@gmail.com wrote: I agree with Chris Mason. IBM should have never started called it USS - how about a simple definitive abbreviation, like zUnix. IBM adores putting a z in front of everything (for some clueless reason) so why should their version of Unix be any different? I'm not getting in the middle of this (again!), but USS started long before z was ever around. And before it was USS - Unix System Services under OS/390, it was OMVS - Open Edition or Open Edition MVS. BTW, I still see OMVS used a lot as well. USS is one less key stroke. :-) The problem with this discussion (that never seems to end) is that you can't go back and rewrite history.Even if MVS was not a component of z/OS, or IBM renamed the MVS component to something else, everyone would still call it MVS. Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:m...@mzelden.com Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: A z/OS Redbook Corrected - just about!
Dick Bond wrote: I agree with Chris Mason. IBM should have never started called it USS - how about a simple definitive abbreviation, like zUnix. IBM adores putting a z in front of everything (for some clueless reason) so why should their version of Unix be any different? That'd be branding. Not clueless; indicates that it's the System z version of something. Seems pretty clear and simple to me. And it'd be z/Unix if it were done that way, because it's software. Hardware: no slash (z900, z990, z9, zEnterprise); software: slash (z/OS, z/VM, z/VSE, z/Architecture - yes, the architecture is software, go figure). But yeah, it's confusing. IBM should have a TLA Czar, and an ETLA Czar (obviously different people for no apparent reason!) who must rule on all such acronyms. Yes, I'm kidding about the last... -- ...phsiii Phil Smith III p...@voltage.commailto:p...@voltage.com Voltage Security, Inc. www.voltage.comhttp://www.voltage.com (703) 476-4511 (home office) (703) 568-6662 (cell) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: A z/OS Redbook Corrected - just about!
On Wed, Mar 21, 2012 at 8:34 AM, Chris Mason chrisma...@belgacom.netwrote: Back in early February, I sent off this comment to the redbooks site: gargantuan snip Definition of TL;DR. -- zMan -- I've got a mainframe and I'm not afraid to use it -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: A z/OS Redbook Corrected - just about!
Looking a Acronym finder for USS: I see Unix System Service (IBM) as number 6 And Unix System Services as number 14 I think it is time to except it. Regards, Herman Stocker It is impossible to make anything foolproof, because fools are so ingenious. -- Robert Heinlein -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Phil Smith Sent: Monday, March 26, 2012 2:36 PM To: IBM-MAIN@bama.ua.edu Subject: Re: A z/OS Redbook Corrected - just about! Dick Bond wrote: I agree with Chris Mason. IBM should have never started called it USS - how about a simple definitive abbreviation, like zUnix. IBM adores putting a z in front of everything (for some clueless reason) so why should their version of Unix be any different? That'd be branding. Not clueless; indicates that it's the System z version of something. Seems pretty clear and simple to me. And it'd be z/Unix if it were done that way, because it's software. Hardware: no slash (z900, z990, z9, zEnterprise); software: slash (z/OS, z/VM, z/VSE, z/Architecture - yes, the architecture is software, go figure). But yeah, it's confusing. IBM should have a TLA Czar, and an ETLA Czar (obviously different people for no apparent reason!) who must rule on all such acronyms. Yes, I'm kidding about the last... -- ...phsiii Phil Smith III p...@voltage.commailto:p...@voltage.com Voltage Security, Inc. www.voltage.comhttp://www.voltage.com (703) 476-4511 (home office) (703) 568-6662 (cell) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN --- The sender believes that this E-mail and any attachments were free of any virus, worm, Trojan horse, and/or malicious code when sent. This message and its attachments could have been infected during transmission. By reading the message and opening any attachments, the recipient accepts full responsibility for taking protective and remedial action about viruses and other defects. The sender's employer is not liable for any loss or damage arising in any way from this message or its attachments. --- -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: A z/OS Redbook Corrected - just about!
I suppose that this conversation will continue in some form until USS becomes rebranded as something other than unix system services. But until then... avast ye land lubbers and have at thee!! Damn the torpedoes and full USS ahead!! VBG And for when I am having a unformatted system services conversation... all both times... I'll be sure to be specific. Arrrgh!! (goes the rebel USS user) Rob Schramm Senior Systems Consultant Imperium Group On Mon, Mar 26, 2012 at 2:52 PM, Stocker, Herman herman.stoc...@avisbudget.com wrote: Looking a Acronym finder for USS: I see Unix System Service (IBM) as number 6 And Unix System Services as number 14 I think it is time to except it. Regards, Herman Stocker It is impossible to make anything foolproof, because fools are so ingenious. -- Robert Heinlein -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Phil Smith Sent: Monday, March 26, 2012 2:36 PM To: IBM-MAIN@bama.ua.edu Subject: Re: A z/OS Redbook Corrected - just about! Dick Bond wrote: I agree with Chris Mason. IBM should have never started called it USS - how about a simple definitive abbreviation, like zUnix. IBM adores putting a z in front of everything (for some clueless reason) so why should their version of Unix be any different? That'd be branding. Not clueless; indicates that it's the System z version of something. Seems pretty clear and simple to me. And it'd be z/Unix if it were done that way, because it's software. Hardware: no slash (z900, z990, z9, zEnterprise); software: slash (z/OS, z/VM, z/VSE, z/Architecture - yes, the architecture is software, go figure). But yeah, it's confusing. IBM should have a TLA Czar, and an ETLA Czar (obviously different people for no apparent reason!) who must rule on all such acronyms. Yes, I'm kidding about the last... -- ...phsiii Phil Smith III p...@voltage.commailto:p...@voltage.com Voltage Security, Inc. www.voltage.comhttp://www.voltage.com (703) 476-4511 (home office) (703) 568-6662 (cell) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN --- The sender believes that this E-mail and any attachments were free of any virus, worm, Trojan horse, and/or malicious code when sent. This message and its attachments could have been infected during transmission. By reading the message and opening any attachments, the recipient accepts full responsibility for taking protective and remedial action about viruses and other defects. The sender's employer is not liable for any loss or damage arising in any way from this message or its attachments. --- -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: A z/OS Redbook Corrected - just about!
It's not immediately clear to me what your intent was here. Accept and except are homophonic opposites. Sadly, I sense that you may have meant accept. ... Date: Mon, 26 Mar 2012 14:52:40 -0400 From: herman.stoc...@avisbudget.com Subject: Re: A z/OS Redbook Corrected - just about! To: IBM-MAIN@bama.ua.edu Looking a Acronym finder for USS: I see Unix System Service (IBM) as number 6 And Unix System Services as number 14 I think it is time to except it. Regards, Herman Stocker It is impossible to make anything foolproof, because fools are so ingenious. -- Robert Heinlein -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: A z/OS Redbook Corrected - just about!
When pronounced distinctly (forcing oneself to speak more slowly than normally) and correctly, the two words are not homophonic. Bill Fairchild -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of J R Sent: Monday, March 26, 2012 3:10 PM To: IBM-MAIN@bama.ua.edu Subject: Re: A z/OS Redbook Corrected - just about! It's not immediately clear to me what your intent was here. Accept and except are homophonic opposites. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: A z/OS Redbook Corrected - just about!
I don't know if I'm correct, but accept I pronounce like ack sept. And except is ecks sept. But I will accept an exception. John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Bill Fairchild Sent: Monday, March 26, 2012 3:43 PM To: IBM-MAIN@bama.ua.edu Subject: Re: A z/OS Redbook Corrected - just about! When pronounced distinctly (forcing oneself to speak more slowly than normally) and correctly, the two words are not homophonic. Bill Fairchild -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of J R Sent: Monday, March 26, 2012 3:10 PM To: IBM-MAIN@bama.ua.edu Subject: Re: A z/OS Redbook Corrected - just about! It's not immediately clear to me what your intent was here. Accept and except are homophonic opposites. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: A z/OS Redbook Corrected - just about!
You have the core-wrecked pronunciation. Bill Fairchild -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of McKown, John Sent: Monday, March 26, 2012 3:50 PM To: IBM-MAIN@bama.ua.edu Subject: Re: A z/OS Redbook Corrected - just about! I don't know if I'm correct, but accept I pronounce like ack sept. And except is ecks sept. But I will accept an exception. John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Bill Fairchild Sent: Monday, March 26, 2012 3:43 PM To: IBM-MAIN@bama.ua.edu Subject: Re: A z/OS Redbook Corrected - just about! When pronounced distinctly (forcing oneself to speak more slowly than normally) and correctly, the two words are not homophonic. Bill Fairchild -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of J R Sent: Monday, March 26, 2012 3:10 PM To: IBM-MAIN@bama.ua.edu Subject: Re: A z/OS Redbook Corrected - just about! It's not immediately clear to me what your intent was here. Accept and except are homophonic opposites. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: A z/OS Redbook Corrected - just about!
Yes, your pronunciation appears to be an acceptable one---'correct' is too normative a word for most linguists---for an educated-circa-2012-somewhere-in-Texas speaker. Still, I don't suppose that I will be expected to forego my usual plea for the use of the IPA instead of such expedients in these situations; and I will not. John Gilmore, Ashland, MA 01721 - USA -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: A z/OS Redbook Corrected - just about!
��z{S���}�ĝ� �xjǺ�*'���O*^��m��Z�w!j�
Re: A z/OS Redbook Corrected - just about!
��z{S���}�ĝ� �xjǺ�*'���O*^��m��Z�w!j�
Re: A z/OS Redbook Corrected - just about!
Just about everyone is tired of the USS crap. IMO, there are three root causes for all of this waste of time: 1) IBM has now had three names: Open Edition MVS, Unix System Services, and now z/OS Unix (System Services). The first two had usable (and widely used) acronyms, where as z/OS Unix really doesn't. 2) Some folks are of the strong opinion that acronyms *MUST* be unique, whereas I don't care so long as they are clear in context. Sure, USS is not an IBM sanctioned acronym - so what? 3) IBM-MAIN thrives on pedantic posts (like this one :-) Given this situation, I suggest that the polite etiquette in this matter is to: a) don't use USS since it is not an official IBM acronym for z/OS Unix b) don't correct someone who does. Kirk Wolf Dovetailed Technologies http://dovetail.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: A z/OS Redbook Corrected - just about!
Hi Kirk, Ah, the voice of reason. Off with his Head!!! :-) BobL -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Kirk Wolf Sent: Monday, March 26, 2012 3:29 PM To: IBM-MAIN@bama.ua.edu Subject: Re: A z/OS Redbook Corrected - just about! /snip Given this situation, I suggest that the polite etiquette in this matter is to: a) don't use USS since it is not an official IBM acronym for z/OS Unix b) don't correct someone who does. Kirk Wolf Dovetailed Technologies http://dovetail.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN mailgate3.oppenheimerfunds.com made the following annotations - This e-mail transmission may contain information that is proprietary, privileged and/or confidential and is intended exclusively for the person(s) to whom it is addressed. Any use, copying, retention or disclosure by any person other than the intended recipient or the intended recipient's designees is strictly prohibited. If you are not the intended recipient or their designee, please notify the sender immediately by return e-mail and delete all copies. OppenheimerFunds may, at its sole discretion, monitor, review, retain and/or disclose the content of all email communications. - -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: A z/OS Redbook Corrected - just about!
Well . . . my original post said almost homophonic, but a quick trip to m-w.com gave accept \ik-ˈsept, ak- also ek-\ except \ik-ˈsept\ So, since Webster gave the same primary pronunciation for both, I thought that I was maybe splitting hairs and removed the word almost. Suffice to say, probably because of the (almost) homophonic nature of the two words and the potential for confusion, we rarely see except used as a simple verb. We are more likely to see the verbal phrase make an exception of. Anyway, my final sentence stands: Sadly, I sense that you (the poster) may have meant accept. Why sadly? Because, while not the popular position, I'm with Chris Mason on this. . . . On Monday, 26 March 2012 16:47:11 UTC-4, Bill Fairchild wrote: When pronounced distinctly (forcing oneself to speak more slowly than normally) and correctly, the two words are not homophonic. Bill Fairchild -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of J R Sent: Monday, March 26, 2012 3:10 PM To: IBM-MAIN@bama.ua.edu Subject: Re: A z/OS Redbook Corrected - just about! It's not immediately clear to me what your intent was here. Accept and except are homophonic opposites. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: A z/OS Redbook Corrected - just about!
On 03/26/2012 04:20 PM, John Gilmore wrote: Yes, your pronunciation appears to be an acceptable one---'correct' is too normative a word for most linguists---for an educated-circa-2012-somewhere-in-Texas speaker. Still, I don't suppose that I will be expected to forego my usual plea for the use of the IPA instead of such expedients in these situations; and I will not. John Gilmore, Ashland, MA 01721 - USA No doubt a subtle form of humor for this group to use another overloaded acronym, IPA. I made the mistake of getting IPA by accident once when intending beer/ale. Have never forgotten what India Pale Ale is like (yuk) and won't make that mistake again; but I'm sure in sufficient quantities it would put an end to any argument over acceptable or correct pronunciation - hence, I submit, this could be a plausible interpretation of IPA in this context -- though knowing John's posts, I'm sure the interpretation of one of the later Google links was intended. :) -- Joel C. Ewing,Bentonville, AR jcew...@acm.org -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: A z/OS Redbook Corrected - just about!
In cahm_n2k9pybdezjqo_l19jt3rgot0k5a-ldkngzz6r8f22z...@mail.gmail.com, on 03/26/2012 at 04:29 PM, Kirk Wolf k...@dovetail.com said: Just about everyone is tired of the USS crap. IMO, there are three root causes for all of this waste of time: 4.) IBM has a list of official acronyms and Unix system Services is not in it. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html 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...@bama.ua.edu with the message: INFO IBM-MAIN
Re: A z/OS Redbook Corrected - just about!
On Mon, 26 Mar 2012 16:29:18 -0500, Kirk Wolf wrote: a) don't use USS since it is not an official IBM acronym for z/OS Unix b) don't correct someone who does. You forgot: c) don't boast about your forays into (a) and (b). -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: A z/OS Redbook Corrected - just about!
I agree, why not zUnix? Or z/Unix? However, since Lynn Wheeler has reminded us that z/OS Unix is (to some degree) POSIX compliant/compatible, why not adopt a catchy contraction of POSIX? I'd like to suggest z/POX, which also connotes the blight it has become on z/OS. ;-) ... Date: Mon, 26 Mar 2012 10:16:32 -0700 From: dickbond...@gmail.com Subject: Re: A z/OS Redbook Corrected - just about! To: IBM-MAIN@bama.ua.edu I agree with Chris Mason. IBM should have never started called it USS - how about a simple definitive abbreviation, like zUnix. IBM adores putting a z in front of everything (for some clueless reason) so why should their version of Unix be any different? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
A z/OS Redbook Corrected - just about!
Back in early February, I sent off this comment to the redbooks site: comment To whom it may concern, - This feedback concerns redbook z/OS Version 1 Release 13 Implementation, SG24-7946-00, which is described still to be in Draft status. - Recently I wanted to check on what z/OSMF was all about. Expecting to be more quickly enlightened by finding a suitable redbook, I tried z/OSMF as a search word on the redbooks site. There were 3 hits, the first, gratifyingly, was entitled z/OS Management Facility. The other two were z/OS Version 1 Release xx Implementation, where xx was 12 and 13. I happened to notice the following at the beginning of the z/OS UNIX System Services chapter in the release 13 redbook: quote z/OS UNIX System Services, is an element of z/OS, is a UNIX operating environment, and is implemented within the z/OS operating system. It is also known as z/OS UNIX. In addition, there is a short abbreviation called USS. /quote How very curious, I thought. How did this mistake creep in? I then checked the beginning of the z/OS UNIX System Services chapter in the release 12 redbook and found that the curious addition had been slipped in only in the later V1R13 edition: quote The UNIX System Services element of z/OS is a UNIX operating environment, implemented within the z/OS operating system. It is also known as z/OS UNIX. /quote Since the V1R13 redbook is still in draft status, the inappropriate text can be removed. - First, in order to confirm that the abbreviation sanctioned by the authors of the manuals when UNIX System Services was introduced, we can pick any of the front-line manuals, the OS/390 MVS Initialization and Tuning Reference being one: quote CHANGES Summary of Changes ... As part of the name change of OS/390 OpenEdition to OS/390 UNIX System Services, occurrences of OS/390 OpenEdition have been changed to OS/390 UNIX System Services or its abbreviated name, OS/390 UNIX. ... /quote http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IEA1E211/CHANGES Thus we have it confirmed that OS/390 UNIX is the supported abbreviation, clearly to be transformed to z/OS UNIX when z/OS was introduced and that there is nary a mention of any other abbreviation. After all, one abbreviation should be sufficient, shouldn't it? In case there is any doubt over the ancestry of this other abbreviation, we have the following web page in order to remind us what, within IBM, is the correct attribution: http://www-01.ibm.com/software/globalization/terminology/u.html#x2042481 quote IBM Terminology ... This site contains terms and definitions from many IBM software and hardware products as well as general computing terms. ... unformatted system service (USS) A communications function that translates a character-coded command, such as a LOGON or LOGOFF command, into a field-formatted command for processing by formatted system services. See also formatted system service. ... USS See unformatted system service. ... /quote Now there are some - particularly to be found in the IBM-MAIN list - who will swear that this is now out-of-date and so the abbreviation is vacant. Well, it's evident they haven't been paying attention to a function which may well have been assisting them to access TSO through an SNA-oriented TELNET server as recently as today! Nor perhaps a function which may be assisting them to logon to TSO (or other applications supporting 3270s) using an OSA feature configured as an ICC. But then there are none so blind as those who will not see! While locating the above reference, I found the following: Glossary of z/OS terms and abbreviations http://publib.boulder.ibm.com/infocenter/zos/basics/index.jsp?topic=/com.ibm.zglossary.doc/zglossary.html Note that this does *not* include the second abbreviation you propose but does, of course, include the first: quote z/OS UNIX System Services (z/OS UNIX). z/OS services that support a UNIX-like environment. ... /quote Another point I noticed was the inherent confusion likely to be caused by anyone searching the IBM site for this abbreviation. The 10th hit can be guaranteed to confuse anyone familiar only with the persistent misuse of this abbreviation: USS messages sent to terminal users http://publib.boulder.ibm.com/infocenter/zos/v1r11/index.jsp?topic=/com.ibm.zos.r11.istmnc0/f1a1c69005.htm Yes, you are right, it's about time this misuse was addressed thoroughly by IBMers. If there are still any lingering hesitation, there is always this seminal post from John Eells which makes the position clear: quote Re: USS misuse Tue, 28 Jul 2009 09:55:04 -0700 Eric Bielefeld wrote: I still think that IBM should have chosen another acronym for Unix than USS. I believe VTAM USS table is still valid, and still used, so it is confusing to me that IBM should use the same acronym for something that is still in use. snip We did not chose USS as an acronym for z/OS UNIX System
Re: A z/OS Redbook Corrected - just about!
I won't get into a lather about USS vs. UNIX but then maybe IBM will have to change all their manuals. For example, SC27-2353-01 - OMEGAMON XE on z/OS Users Guide (and nearly anything to do with monitoring) refers to USS in regards to Unix System Services although in this manual it does make a clarification: --- The Dynamic XE to 3270 (Classic) linking feature requires the VTAM® Unformatted System Services (USS) screen to accept a LOGON APPLID() DATA() command. If the default Telnet USS screen does not accept this command, the name of a Logical Unit (LU) group that does accept it must be provided. --- Confusion could abound for the novice but I'm pretty sure that if someone sees: 'The USS Address Spaces attributes provide information about all z/OS address spaces (so-called dubbed address spaces) that have issued a call to the UNIX System Services application programming interface (API).' they are going to know what the book is discussing. Sebastian. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: A z/OS Redbook Corrected - just about!
Thank goodness IBM is spending time correcting USS atrocities rather than improving z/OS Unix. Kirk Wolf Dovetailed Technologies http://dovetail.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: A z/OS Redbook Corrected - just about!
LOL - I know that only a very short list of people will ever be truly confused by USS (unformatted system services) and USS (unix system services) references... the cat hearding reference is awesome and very appropriate... since the cat is out of the bag. Rob Schramm Senior Systems Consultant Imperium Group On Wed, Mar 21, 2012 at 11:57 AM, Kirk Wolf k...@dovetail.com wrote: Thank goodness IBM is spending time correcting USS atrocities rather than improving z/OS Unix. Kirk Wolf Dovetailed Technologies http://dovetail.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: A z/OS Redbook Corrected - just about!
Amen, heaven forbid the improve unix systems services, btw I have worked Vtam and unix, so amen brothers and sisters I ave seen the Chris light, teasing Chris . Sent from my iPad Scott Ford Senior Systems Engineer www.identityforge.com On Mar 21, 2012, at 11:57 AM, Kirk Wolf k...@dovetail.com wrote: Thank goodness IBM is spending time correcting USS atrocities rather than improving z/OS Unix. Kirk Wolf Dovetailed Technologies http://dovetail.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
