On Fri, 11 May 2018 11:47:08 -0400, Carmen Vitullo wrote: >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 ! > When I was very new to MVS I created several data sets with such names. Experimenting, self-training in the use of apostrophes in JCL. I left them allocated.
Within a few days, admins descended on me, irritated because their utility for scratching nonconforming data sets couldn't handle them. Too nonconforming, I guess. DFSMS should make the rules. Assembler and all higher layers should obey them and not invent additional restrictions. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
