What would it even mean to release the space for a member? Note: RLSE is a positional sub-parameter of SPACE on a DD statement; the leading commas are mandatory.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List [[email protected]] on behalf of Thomas David Rivers [[email protected]] Sent: Tuesday, October 27, 2020 6:46 AM To: [email protected] Subject: SVC 99 RLSE text unit on DISP=SHR allocation with a PDS/PDSE member name I have a DYNALLOC set up with a default of adding the RLSE text unit (to release the space after a CLOSE.) This is to retrieve a system-provided DD name for an eventual OPEN OUTPUT operation, for opening a DSN(MEM) PDS/PDSE member. The PDS in question already exists (happens to be a PDSE.) That is, this is not a NEW allocation. So, basically it would be something like: //<sysname> DD DSN=MY.PDSE(MEM),SPACE=(RLSE),DISP=SHR (no other space parms are provided in the DYNALLOC text-units, it's invalid JCL but seems to be OK for DYNALLOC.) It seems that if the RLSE text-unit is provided, _all_ of the remaining space in the PDS/PDSE is released, not just "space" for the member; that is, the entire PDS/PDSE allocation is truncated on the CLOSE. I would expect RLSE to apply to the member - which doesn't make sense, since the eventual directory update is going to set the member's size to just the blocks in the PDS/PDSE it's using... but it seems to be applying to the entire PDS/PDSE... which is equally surprising. Am I rightly surprised, or does it not apply to the entire PDS/PDSE and there is something else in my processes that is perhaps releasing the allocated space. That is, what does the RLSE text-unit mean when the allocation has a DSN and a MEMBER for an existing PDS/PDSE? Just hoping someone has been down-this-road before... - Thanks! - - Dave Rivers - -- [email protected] Work: (919) 676-0847 Get your mainframe programming tools at http://secure-web.cisco.com/1h5aNYUGd5NpBejG2gs7KW09FOAbvsUAk1ssOOp9CSOJx4Tk9hqapEmQaa_GKSrKZzMKFCfVjYoFdfrJMa6VFrXtwGBczg7OjBW5y_6_Dex6wZaLqSVA5_I94uQa9QSGjhXIQzX3cF8fTKrCeC9a9wcljb9lgFLcY52g3Jz4LlEdPQn9QkazotNabIkfeno-Gq_2BgaCK_HvJvUZxoxiqvQyiopxPOGBNkZ254vtan0YFnI4m4A4GtRzEt2hxSaAXO4s0kmbIDP6JgFpZFP_Un6MQ6JpFrVJgPoBxYZ23cS5s8TnoVZRDgOp8oJ1flpjJ-Ni24oI7CXEe0iU6ls4s6Iga3O_ZplhuvyTRjrbnDQvF10iQHPDbXQraNyOI_MyVy0Na70CZq71MroLibgtlZahpn37RQIdXCGLb9h0bp07VPILpZe-GBllKNT2jvRek/http%3A%2F%2Fwww.dignus.com ---------------------------------------------------------------------- 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
