Re: RGZPFM without lock *EXCL - warehouse reads

[Jim Franz <franz9000@xxxxxxxxx>]

cool...

On Fri, Jun 19, 2015 at 12:06 PM, Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>
wrote:

> Jim,
>
> We have a rgzpfm while active utility, loads a work file with any PF that
> has deleted records.
> Can be run without stopping any apps.
>
> STRJRNPF   FILE(&MBLIB/&MBFILE) JRN(QGPL/RGZPFM)
>
>  SNDPGMMSG  MSG('RGZPFM starting for ' *BCAT &MBLIB *BCAT +
>               '/' *BCAT &MBFILE *BCAT '.')
>
>  RGZPFM     FILE(&MBLIB/&MBFILE) MBR(&MBNAME) +
>               RBDACCPTH(*NO) ALWCANCEL(*YES) +
>               LOCK(*SHRUPD) /* rgzpfm while active */
>  MONMSG     MSGID(CPF2981 CPF3135 CPF9801 CPF9809 +
>               CPF9810 CPF9820 CPF2982) EXEC(GOTO +
>               CMDLBL(ERROR2))
>
>
>  ENDJRNPF   FILE(&MBLIB/&MBFILE) JRN(QGPL/RGZPFM)
>  MONMSG     MSGID(CPF9803) EXEC(GOTO CMDLBL(ERROR4))
>
> Paul
>
> -----Original Message-----
> From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
> Jim Franz
> Sent: Friday, June 19, 2015 11:25 AM
> To: Midrange Systems Technical Discussion
> Subject: 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
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
> unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
> moment to review the archives at http://archive.midrange.com/midrange-l.
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.