I want to HMIGRATE a data set to consolidate extents. The data set is routinely browsed by several users. HMIG fails.
I'm quite willing to get in line and wait my turn. Something like IKJEFT01; DISP=OLD; HMIGRATE DSN. But will HMIG collide with my own ENQ? Is there a better way to defragment? Reallocate; copy; delete; rename? I wish z/OS had a preemptive and atomic RENAME. With LUW isolation. And it's a PDSE routinely browsed from several systems; we can't sysplex all of them. Updates routinely fail. One user has suggested using UNIX files instead of Classic. (See! I'm not the only one!) I briefly considered using generated opaue DSNs and manifest ALIASes. But that's ugly because of the lurking deferred ABENDs. Is there any way to force an ENQ on the RELATED DSN at job initiation? (Would JES3 do that?) -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
