Supporting concatenatation of unlike libraries would give users more freedom with creating private libraries. However, I'm assuming that will never be supported and simply explaining why BPXWDYN doesn't address the issue.
Yes, allowing a directory in a concatenation would make life easier. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 עַם יִשְׂרָאֵל חַי נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר ________________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Paul Gilmartin <[email protected]> Sent: Friday, December 29, 2023 6:38 PM To: [email protected] Subject: Re: Checking status of multiple datasets in CLIST and REXX On Fri, 29 Dec 2023 22:15:31 +0000, Seymour J Metz wrote: >BPXWDYN may support concatenating FB and VB, but ISPF and TSO don't. > I don't see that would be very useful. It might be more useful to concatenate a mixture of DISPs. But not concatenating DSN with PATH is a sore lack. (Again, PATHOPTS, PATHOODE and PATHDISP can't have a mixture of values.) >________________________________________ >From: Paul Gilmartin >Sent: Friday, December 29, 2023 5:10 PM >> >TSO can CALL BPXWDYN, subject to an onerous 100-byte PARM limit. > >In one case, for a mixed concatenation, I used a sequence of ALLOCATE >followed by a single CALL BPXWDYN 'CONCAT ...' > >CONCAT requires at least two operands; fails with just one. -- 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
