Re: OVRDBF - Record lock

When testing and in general, as a safety precaution, I always put a DLTOVR
at the start with its corresponding MONMSG if the override does not exist.
This is because when you test, or repeat the try on another turn, you may
find the record already locked because it was not updated and thus not
unlocked. You may not fix this at that moment but probably could be able
to use the next library's instance of the file and get a successful lock on
the next one.

I guess this may be what you mean.

HTH
JS



El mié, 19 feb 2025 a las 16:35, Shane Reeves (<SReeves@xxxxxxxxxxxxxxxxxx>)
escribió:

I'm not understanding something with OVRDBF.
My desire is to loop through a number of libraries all with same file, and
update them.
The below CL program sets the current library as it loops through a file
listing the libraries. *(I would think this isn't needed with the OVRDBF
but added as an extra precaution).
The rpg program that the below CL calls (VND040R) will check the record
lock before updating the record.
What I have discovered is that if the file has a record lock in the first
library, the log file is coming back showing the record is locked in every
library. Which makes me think that the OVRDBF isn't redirecting to the
library.
What am I doing (or assuming) wrong about the OVRDBF?


/****************************************/
/* Loop Through All Global Libraries */
/****************************************/
DOUNTIL COND(&EOF)
RCVF RCDFMT(SPPLNTGV) OPNID(GLIB)
MONMSG MSGID(CPF0864) EXEC(LEAVE)

/************************/
/* Add Global Library */
/************************/
ADDLIBLE LIB(&GLIB_SPGLIB) POSITION(*FIRST)
MONMSG MSGID(CPF2103)
CHGCURLIB CURLIB(&GLIB_SPGLIB)


OVRDBF FILE(MYFILE) TOFILE(&GLIB_SPGLIB/MYFILE) +
RCDFMTLCK((VENDR *SHRRD)) WAITRCD(5) SHARE(*YES)

/* CALL - Update Vendor */
CALL PGM(VND040R) PARM(&PVEND &PTERM &PUSER +
&GLIB_SPGLIB)

DLTOVR FILE(MYFILE)

/************************/
/* Remove Global Library*/
/************************/
RMVLIBLE LIB(&GLIB_SPGLIB)
MONMSG MSGID(CPF2103)


ENDDO

Thanks
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.