While I'm not convinced there is real need for member
generations/versions, I have to admit there is lack of support for this
feature. Even with this enhancement.
It's like long names in PDSE. I heard about it ~20 years ago. And I have
never seen it. And never seen any IBM tool (ISPF/PDF?) supporting such
names.
--
Radoslaw Skorupka
(looking for new job)
Lodz, Poland
W dniu 10.05.2021 o 19:47, Paul Gilmartin pisze:
On Mon, 10 May 2021 12:36:13 -0500, Lionel B. Dyck wrote:
...
OA60639: NEW FUNCTION (ibm.com)
<https://www.ibm.com/support/pages/apar/OA60639>
Which says:
...
GENS={ALL | NONE}
Indicates if the member generations of a Version 2 PDSE will
be copied or not. This keyword is valid only when copying from
a PDSE V2 with member generations to another
Does "only" mean not valid when unloading to a sequential PDSU?
Now the question is - will TSO TRANSMIT and RECEIVE be updated to support
this new capability?
I'm pretty sure that TRANSMIT does IEBCOPY unload under-the-covers. So:
o Does this depend on whether GENS is honored for unload to PDSU?
o Will this require new syntax for TRANSMIT?
THANK YOU IBM - THANK YOU
Lionel B. Dyck <><
Website: https://www.lbdsoftware.com
Github: https://github.com/lbdyck
-- 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
