> On May 28, 2018, at 12:38 AM, Paul Gilmartin > <0000000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > > No, no! The suggestion was that it should automagically add one record, > *then*delete*it*. > (Others have said this suffices.) Or, in a shortcut initialize the data set > in such a state. > Once the record is gone, it doesn't matter what the key was. There's nothing > for any record > subsequently inserted to be a duplicate key of. IBM doesn’t want to touch your dataset, You created it and its up to you to prime it. But this is counter intuitive to IBM automatically encrypting all datasets. > > (But does that create a CA/CI for a range that the customer would never use > and > leave it dangling?) > > What happens when the programmer REPROs an empty KSDS which formerly contained > records in order to reorganize it and prune otiose CA/CIs?
---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
