Edward Jaffe wrote: >On 4/4/2012 11:32 AM, Mary Anne Matyaz wrote: >> I was actually trying to break a PDSE last week, so that I could get an >> example of the IEBPDSE utility run against a hosed PDSE, and I couldn't seem >> to break one. I have two sysplexes so I was randomly back and forth updating >> from outside the sysplex, and it had no trouble at all. Does anyone have a >> fool proof way to break a pdse, on 1.13?
>You must live right. Almost every time I've accidentally updated a PDSE from >outside the sysplex it has been immediately broken. I suggest you do >concurrent ISPF 3.3 copy members to the target PDSE and/or LKEDs while also >doing copy. Edward is right. I would humbly also suggest that your volumes are shared so no enqueue can take place at all. Or at least, ensure nothing is keeping these updates in a single row, but allow them to occur simultaneausly. You could try to submit all those jobs with TYPRUN=HOLD and then when ready, release ALL of them. If you can't still break 'em, you certainly must be in a paradise... ;-D Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
