Very much looking forward to these enhancements. Rock on, RBTI
Dennis McGrath Software Developer QMI Security Solutions 1661 Glenlake Ave Itasca IL 60143 630-980-8461 [email protected] -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Ken Shapiro Sent: Monday, December 30, 2013 5:27 PM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: Tip of the Day: AUTOMUMbering in a Multi-UserEnvironment "The upcoming update of R:BASE eXtreme 9.5 (32/64), Update 4 in 2014, includes more enhancements related to the resource not available and I/O -ERROR- in a multi-user, multi-session environment that loops adding rows with Autonumbered columns." That would be a welcome enhancement. I'm struggling with this very issue. Although I have already set wait to 60 and interval to .9, the resource unavailable is still displayed; sometimes after about 20 seconds. Although in my case I think it is an "SATTACH TEMP...." that is causing the lock on the database. Can't wait to see what is in store for next R:year. Happy New Year! Ken -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of A. Razzak Memon Sent: Monday, December 30, 2013 1:44 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Tip of the Day: AUTOMUMbering in a Multi-User Environment Monday, December 30, 2013 Tip of the Day: AUTOMUMbering in a Multi-User Environment Product.: R:BASE eXtreme 9.5 (32/64) Build...: 9.5.3.21205 or higher www.rupdates.com Keywords: Commands, Settings In a typical multi-user, multi-session environment, you may notice the resource conflict or I/O -ERROR- when resources are not available, mainly from trying to get a lock on the SYS_DEFAULTS table to update the AUTONUM values. Did you know that by increasing the setting for WAIT and INTERVAL in a multi-user, multi-session environment can reduce the instances of resource conflicts? You can still get a resource not available message, but the chances of getting it can be reduced by increasing the value for WAIT from 4 (default) to something larger. SET WAIT sets the minimum number of seconds to retry the last requested resource (a table or database) before halting execution. Rather than aborting execution, SET WAIT allows you to set a length of time for R:BASE to keep trying to access a resource. A message is displayed showing the approximate percentage of wait time remaining. If you do not run a SET WAIT command, R:BASE automatically retries the locked resource for approximately four seconds before issuing a retry message. You can also adjust the INTERVAL in which R:BASE tries the command during the SET WAIT period. The SET INTERVAL command specifies the time to elapse before R:BASE retries the command that caused a conflict within the waiting period. The upcoming update of R:BASE eXtreme 9.5 (32/64), Update 4 in 2014, includes more enhancements related to the resource not available and I/O -ERROR- in a multi-user, multi-session environment that loops adding rows with Autonumbered columns. Alternatively, in a multi-user, multi-session, and/or on-line R:BASE applications using a common database, you may also take advantage of (NEXT(tblname,autonumcol)) function. A sample application is available to demonstrate the use of such feature in R:BASE eXtreme 9.5. Sample Applications: http://www.razzak.com/sampleapplications/ Application Title: Understanding R:BASE (NEXT(tblname,autonumcol)) Function Date Posted: 06/27/2013 Have Fun! Very Best R:egards, Razzak. www.rbase.com www.facebook.com/rbase www.RazzakMemon.com
