|
The CL doesn't have ALCOBJ *EXCL (I'm assuming that does an exclusive open). The program open the table I-O. -----Original Message----- From: cobol400-l-bounces@xxxxxxxxxxxx [mailto:cobol400-l-bounces@xxxxxxxxxxxx] On Behalf Of Scott Lindstrom Sent: Monday, May 22, 2006 11:54 AM To: COBOL Programming on the iSeries/AS400 Subject: Re: [COBOL400-L] Locking records on Cobol By any chance is there a CL program doing a ALCOBJ *EXCL beforehand? My COBOL is a bit rusty, but are you perhaps opening the table for output rather than I/O? Scott "Garcia, Luis" <lgarcia@panameri canlife.com> To Sent by: "'COBOL Programming on the cobol400-l-bounce iSeries/AS400'" s@xxxxxxxxxxxx <cobol400-l@xxxxxxxxxxxx> cc 05/22/2006 12:44 Subject PM Re: [COBOL400-L] Locking records on Cobol Please respond to COBOL Programming on the iSeries/AS400 <cobol400-l@midra nge.com> The main issue is that program appears to be locking the whole table no one can access another record while someone has a record. I'll with "NO LOCK" and seem how it goes. -----Original Message----- From: cobol400-l-bounces@xxxxxxxxxxxx [mailto:cobol400-l-bounces@xxxxxxxxxxxx] On Behalf Of Don Stafford Sent: Monday, May 22, 2006 11:31 AM To: COBOL Programming on the iSeries/AS400 Subject: Re: [COBOL400-L] Locking records on Cobol For us, we decide how to handle the lock, based on the program type the is reading and changing the record. If it is a "batch" program (one that does not require a user to touch the keyboard), then we do not include a LOCK statement.... the time the record is active should be only a couple milliseconds. If the program is "interactive", then maybe.... it depends on the field(s) being (or allowed to be) changed. Most of the time, we do not lock the record. So far (17 years), it has not been an issue. ----- Original Message ----- From: "Garcia, Luis" <lgarcia@xxxxxxxxxxxxxxxxxxx> To: "'COBOL Programming on the iSeries/AS400'" <cobol400-l@xxxxxxxxxxxx> Sent: Monday, May 22, 2006 1:04 PM Subject: Re: [COBOL400-L] Locking records on Cobol > Would it be wise to use the "NO LOCK" if I'm changing the record? > > -----Original Message----- > From: cobol400-l-bounces@xxxxxxxxxxxx > [mailto:cobol400-l-bounces@xxxxxxxxxxxx] On Behalf Of David Scott > Sent: Monday, May 22, 2006 9:30 AM > To: 'COBOL Programming on the iSeries/AS400' > Subject: Re: [COBOL400-L] Locking records on Cobol > > Try read with "NO LOCK" > > > David Scott > SmartWeb Technology, Inc. > dlscott@xxxxxxxxxxxxxx > (Voice) 407-671-2277 > (Cell) 407-310-8106 > (Fax) 407-264-6877 > > > -----Original Message----- > From: cobol400-l-bounces@xxxxxxxxxxxx > [mailto:cobol400-l-bounces@xxxxxxxxxxxx] On Behalf Of Garcia, Luis > Sent: Monday, May 22, 2006 11:00 AM > To: 'COBOL Programming on the iSeries/AS400' > Subject: [COBOL400-L] Locking records on Cobol > Importance: High > > Hi everyone, I'm having a rough time with a program. The program is used > for a lot a people and every time someone tries to change data, the > program > freezes anyone who tries to access another record. > > Can anybody tell me what steps I should take to correct this problem. > > Thanks very much for all the help > > Luis > -- > This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) mailing > list > To post a message email: COBOL400-L@xxxxxxxxxxxx To subscribe, > unsubscribe, > or change list options, > visit: http://lists.midrange.com/mailman/listinfo/cobol400-l > or email: COBOL400-L-request@xxxxxxxxxxxx Before posting, please take a > moment to review the archives at http://archive.midrange.com/cobol400-l. > > > > -- > This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) mailing > list > To post a message email: COBOL400-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/cobol400-l > or email: COBOL400-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/cobol400-l. > -- > This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) mailing > list > To post a message email: COBOL400-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/cobol400-l > or email: COBOL400-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/cobol400-l. -- This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) mailing list To post a message email: COBOL400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/cobol400-l or email: COBOL400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/cobol400-l. -- This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) mailing list To post a message email: COBOL400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/cobol400-l or email: COBOL400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/cobol400-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
