Hi, Gerhard, Limited use is exactly what is under discussion, based on the original point of LPA not allowing PDSE data sets All the PARMLIB member needs to do is provide a list of PDSE datasets to be loaded into LPA.
If you want to do more than that, sure, an exit is ideal. This is more like an extension to LPALSTxx, and I'm confident you wouldn't advocate an exit to replace that PARMLIB member, would you? Cheers,,,Steve Steven F. Conway, CISSP LA Systems z/OS Systems Support Phone: 703.295.1926 [email protected] From: Gerhard Postpischil <[email protected]> To: [email protected] Date: 09/16/2013 01:18 PM Subject: Re: PDS/E, Shared Dasd, and COBOL V5 Sent by: IBM Mainframe Discussion List <[email protected]> On 9/16/2013 10:11 AM, Steve Conway wrote: > While Gerhard's suggestion of an exit has the merit of being (probably) > easier to get IBM to implement, I much prefer Ed's suggestion of a PARMLIB > member. That is much easier to review, implement and maintain down here > in the trenches. Unless the PARMLIB member provides for an exit name, it would be of limited use. I see PARMLIB as the equivalent of reading a book - it may be interesting, but the capabilities are limited to what the author provides. An exit is closer to writing your own book, where (almost) anything goes. Gerhard Postpischil Bradford, Vermont ---------------------------------------------------------------------- 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
