well, of course a type, CA-TLMS sorry CA :(
Carmen Vitullo ----- Original Message ----- From: "Carmen Vitullo" <cvitu...@hughes.net> To: IBM-MAIN@LISTSERV.UA.EDU Sent: Friday, May 11, 2018 10:47:08 AM Subject: Re: CONTROVERSY! z/OS UNIX: is it an enhancement or a tool of the Devil? Talking about strange dsn allocations, I worked as a contractor Y2K for state Govmt, after updating TLSM to support OS/390 2.5 one of our agency's support folks told me I broke TLMS because the dataset(s) they use to write to take for DOL is, for example DSN='Sears Roebuck and Co', DISP=(,KEEP),UNIT=CART well I said, you can't do that ! that's not a valid datasets name, but we've been creating them for many years, I found out I was very wrong, CA knew better and provided a PTF fix for the issue, embarrassed, ah yup , I was ! Carmen Vitullo ----- Original Message ----- From: "John McKown" <john.archie.mck...@gmail.com> To: IBM-MAIN@LISTSERV.UA.EDU Sent: Friday, May 11, 2018 10:39:55 AM Subject: Re: CONTROVERSY! z/OS UNIX: is it an enhancement or a tool of the Devil? On Fri, May 11, 2018 at 9:06 AM, Charles Mills <charl...@mcn.org> wrote: > Oh for gosh sakes! Every operating system is different. There is no > eleventh commandment "filenames shall be 44 uppercase characters" that UNIX > violated. Tell him a foolish consistency is the hobgoblin of little minds. > Or that the inability to learn new things is a sign of old age. > > Or point out that z/OS is case-dependent. Don't think so? Try referencing > 'sys1.maclib'. > Or, if you want to break someone's mind use //SYSUT2 DD DSN='&SYSUID.x.DATA' On my system (likely because my ID is very powerful), a data set is actually created on a volume. So DADSM will accept the DSN. I had to use STORCLAS=NONSMS to force non-SMS allocation. If I didn't, SMS would fail the allocation (yah!). However, I couldn't get it catalogued. And when using JCL to allocate it, I get: 3 IEF648I INVALID DISP FIELD- KEEP SUBSTITUTED 3 IGD01008I NULL STORCLAS ASSIGNED I now have a DSN on a non-SMS volume which is not catalogued (which is valid). But, although it is displayed by ISPF 3.4, it cannot be used in any way that I have found. I get the weird message "Invalid change". I guess ISPF is uppercasing the DSN and then whining that the values are different. Now that I think about it, I remember many years ago, at my first job, they were converting from DOS to VS1. The DOS system actually had a DSN on a volume named 'WATER MONSTER FILE' (aka Water Master File -- city water dept.). And I could "use it" on VS1. But not really, because it was a DOS ISAM dataset. I appreciate the response so far. I'm really getting the idea that people are more "resigned" to UNIX as part of z/OS, rather than "enthusiastic" about it. > > Charles > > -- We all have skeletons in our closet. Mine are so old, they have osteoporosis. Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
