RGZPFM without lock *EXCL - warehouse reads

Trying to inch towards 24x7 but have some old processes.
We have an existing process to reorg some files weekly, and during that
time we don't allow our warehouse, web clients or any other process to read
data - lock is *EXCL.

REUSEDLT to reuse deleted records is not our standard (unfortunate).

We would like to go to RGZPFM *SHRUPD - and asking if any issues from those
who tried it.
Files are mostly not journalled.
The possible updates during this time would be C# web clients adding,
changing, deleting records (some under commitment control, but not all).
At V7R1, and not latest cume.

Help text from RGZPFM

*SHRUPD
A shared update lock is acquired. Concurrent update, delete, and
insert access to the physical file member is allowed from
another job.

If *SHRUPD is chosen, the resulting order of the rows may not
exactly match what was requested on the KEYFILE keyword. The
rows will be reorganized to closely match the specified order,
but concurrent update, delete, and insert operations will cause
some rows to not be reorganized. If the rows must exactly match
the arrival sequence (*NONE) or a keyed file sequence, do not
use *SHRUPD.

If *SHRUPD is specified, ALWCANCEL(*YES) must also be specified.

Jim Franz