Unfortunately, after about 45 years of doing it "this way", the users have a lot of their own JCL, it would not be economical or feasible to train or expect thousands of them to change or even know how to change their JCL. Many of them (most) don't even know what they are editing, they just replace a VOLSER with the one from the listing they have and submit the job. In a nice little environment where you can control these things, you are probably correct, but that is not the case in this instance.
Brian On Tue, 22 Sep 2020 12:55:05 +0200, R.S. <[email protected]> wrote: >My €0.02: >This is typical problem when the goal is NOT defined. >Existing approach seems ridiculous, but it exists. It works. >So, since it works, why to change it? What is the reason? What goal is >to achieve? >More ridiculous are the terms. JCL cannot be changed. WHY??? >However JES2 exit6 which changes JCL "in the flight" is allowed. Why??? >Datasets are important, but the chances it will be ever read are small. >Uncataloged datasets are a problem, however there is no big problem with >duplicate names and volser which is known after the dataset is created. > >My opinion: >First, recognize the situation and define the problem, then define the goal. >Never use tapes, especially for small datasets. Including virtual tapes. >Small datasets can be written to DASD, zEDC can be used to compress it. >And DFSMS MC can be used to migrate it to tape. Yes, tapes are still >good for backup and ML2. >Large number of datasets is not a problem, that's what are user catalogs >for. >Good naming convention will help with ACS routines and ICF aliases. >It can be GDG or just HLQ.YEAR.SOME.NAME.Ddate, or so. I would not go to >PDSE members. Member are good candidate for really big number of really >small files. Note, the smallest chunk of DASD is one track. The smallest >chunk of PDSE is 4kB, and for PDS is just the size of file, it can be >one byte. However migrated dataset occupies zero tracks. >All the revolution require ...just simple changes in JCL and few changes >in DFSMS realm. I can do that for peanuts ;-) > >-- >Radoslaw Skorupka >Lodz, Poland > > > > > >====================================================================== > >Jeśli nie jesteś adresatem tej wiadomości: > >- powiadom nas o tym w mailu zwrotnym (dziękujemy!), >- usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub >zapisałeś na dysku). >Wiadomość ta może zawierać chronione prawem informacje, które może wykorzystać >tylko adresat.Przypominamy, że każdy, kto rozpowszechnia (kopiuje, >rozprowadza) tę wiadomość lub podejmuje podobne działania, narusza prawo i >może podlegać karze. > >mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 >Warszawa,www.mBank.pl, e-mail: [email protected]. Sąd Rejonowy dla m. st. >Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, KRS 0000025237, >NIP: 526-021-50-88. Kapitał zakładowy (opłacony w całości) według stanu na >01.01.2020 r. wynosi 169.401.468 złotych. > >If you are not the addressee of this message: > >- let us know by replying to this e-mail (thank you!), >- delete this message permanently (including all the copies which you have >printed out or saved). >This message may contain legally protected information, which may be used >exclusively by the addressee.Please be reminded that anyone who disseminates >(copies, distributes) this message or takes any similar action, violates the >law and may be penalised. > >mBank S.A. with its registered office in Warsaw, ul. Senatorska 18, 00-950 >Warszawa,www.mBank.pl, e-mail: [email protected]. District Court for the >Capital City of Warsaw, 12th Commercial Division of the National Court >Register, KRS 0000025237, NIP: 526-021-50-88. Fully paid-up share capital >amounting to PLN 169.401.468 as at 1 January 2020. > >---------------------------------------------------------------------- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
