Broken As Designed (BAD). It actually takes less code to do it right than to do it wrong with the current level of DFSMSdfp, although the broken code already exists.
RFE? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Paul Gilmartin <[email protected]> Sent: Monday, September 28, 2020 9:39 PM To: [email protected] Subject: Re: [External] LMINIT cannot handle concatenation with more than 16 data sets? On Mon, 28 Sep 2020 20:15:43 +0000, Pommier, Rex wrote: >Robert, > >IDK if this specifically LMMINIT, but when I enter ISRDDN and try to browse a >library concatenation with greater than 16 libraries in it, I get this: > >Only the first sixteen data sets are shown in this list. ISRDDN uses ISPF >services to process DD names and these services are limited to >concatenations of sixteen or fewer data sets. > >Whichleeads me to believe the 16 limit is still there. z/OS 2.4. > Perhaps worse, it does not report members in UNIX files in directories among the 16 supported catenands. So if I have member WOMBAT in a zFS in a SYSLIB concatenation, it may show me a WOMBAT in a later PDS(E) whereas HLASM will use the one in the zFS. Treacherous indeed. I suspect that ISPF uses the antique technique of allocating each catenand with DSORG=PS and parsing directory blocks. Would DESERV do better? I went to SR on this: Record 55733,033,000 Created: 04/11/22 ... got an elaborate WAD. -- gil ---------------------------------------------------------------------- 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
