RE: OVRDBF - Record lock -- MIDRANGE-L

So even though the RPG program ran/completed and the OVRDBF is deleted and recreated, the next instance of the RPG program is still going to use the previous OVRDBF?

Shane Reeves
Sr. Programmer
Summit Polymers- Technical Center

o. 269.324.9320 x50444
m. 269.217.4874

NOTICE: This e-mail message and any attachments are confidential and intended solely for use of the intended recipient. If you have received this e-mail in error, please delete this message. For purposes of engaging in binding contracts related to non-production goods and services with Summit Polymers, please refer to Contracts for Non-Production Goods and Services.

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Niels Liisberg
Sent: Thursday, February 20, 2025 4:32 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: OVRDBF - Record lock

CAUTION: This email originated from outside your organization. Exercise caution when opening attachments or clicking links, especially from unknown senders.

You have to close til file in your VND04R either by user controlled - open / close or old style exit the program with *INLR

otherwise the file stays open from the first iteration.

On Wed, Feb 19, 2025 at 11:50 PM Javier Sanchez < javiersanchezbarquero@xxxxxxxxx> wrote:

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://linkprotect.cudasvc.com/url?a=https%3a%2f%2flists.midrange.c
om%2fmailman%2flistinfo%2fmidrange-l&c=E,1,Uh3dwKut3C7ddR1pwF-NdMbBT
W7S3J_KfMyHbFVKEHz9NCkq_Yi0BXpMhOMonRB0PD0BYMowNcsuBfUMWB-lmZEH78SUa
VLqQqfIEJIJfBaDjI4UbtJk&typo=1 or email:
MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://linkprotect.cudasvc.com/url?a=https%3a%2f%2farchive.midrange.com%2fmidrange-l&c=E,1,iDWkFBFW8OxAHr7nMgt-2GUiu4CHrbMLf-N9IYNifPbbt2lU3WOSIEodh8hinX0Ly4jGvKf4obgCp3PUyXCYiMKAWrDV_SbYCLVSDFRvUaY,&typo=1.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
related questions.

--
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://linkprotect.cudasvc.com/url?a=https%3a%2f%2flists.midrange.com
%2fmailman%2flistinfo%2fmidrange-l&c=E,1,Q5fz42WEW5LYALkzBe8tBpo4seR0L
1xecoXDkjv5H8bXEz7dLxomaqUkWGwcqQ6g5wd5beK422USWeNng3JSdXj-EqDwVb55WFD
1i-PM0yn9KOMnjmy2hN08EA,,&typo=1 or email:
MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://linkprotect.cudasvc.com/url?a=https%3a%2f%2farchive.midrange.com%2fmidrange-l&c=E,1,h35XafDQ5gFbsjOIp7ScRAh7DBN2_kBTXojaEydqfSXx0ZIhlEVNHjnb8v-LRwAJr2MOuhdWuMKvEXNTXbC8hmlJNM_sycY9FTSKbxvMtYcO4HVbZQ1d0XQC&typo=1.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
related questions.

--
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://linkprotect.cudasvc.com/url?a=https%3a%2f%2flists.midrange.com%2fmailman%2flistinfo%2fmidrange-l&c=E,1,acKNhLzTp00zHTDXpqT_sNvfVt9VFhJwcqTYQuzMf-5IN-jwkz6uZxZhfLVUOtmz3yofurQoL8StFt5cUBmpk3EzQVU9BQ2HVp7FeE-UgIRBwN71lJc,&typo=1
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://linkprotect.cudasvc.com/url?a=https%3a%2f%2farchive.midrange.com%2fmidrange-l&c=E,1,l0sehkF5yQJxdwsn66aF4H5a0I-OKrPPaQMqdIUu_kc9oQjkdYMnrEd5Xu9jKdw30nCdz-5LN7yAI52zEqAX0bR-UmIp6T9QJGS-HI7zAY61M_rCuiJ2qcBJ&typo=1.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.