RE: RGZPFM with ALWCANCEL(*YES)

Why end the job at all?
You can use shared update and allow the file to be used during its reorg.

RGZPFM LOCK(*SHRUPD) ALWCANCEL(*YES)

--
Chris Hiebert
Lead Software Developer
Disclaimer: Any views or opinions presented are solely those of the author and do not necessarily represent those of the company.

From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Dan Bale via MIDRANGE-L
Sent: Friday, October 17, 2025 4:27 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Cc: Dan Bale <dan.bale@xxxxxxxxxxxxxxxxxxxxx>
Subject: RGZPFM with ALWCANCEL(*YES)


If RGZPFM with ALWCANCEL(*YES) is used on a file for which there are a lot of logical access paths/indexes, are the access paths/indexes updated on the fly, or are they ignored until the physical file reorg is completed? The reason for asking is that if we need to cancel the reorg submitted with ALWCANCEL(*YES), will the job still need to spend time updating the access paths/indexes? So, if we're given until 9:000am when the file must absolutely be available, can we cancel the job at 8:59am with the expectation that the file and its indexes will be ready and available to use?



- Dan Bale