× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: Record Lock message
  • From: Joe Giusto <JGiusto@xxxxxxxxxxxx>
  • Date: Wed, 30 Jun 1999 08:19:41 -0400

If you OVRDBF filename WAITRCD(sec)  where sec is number of seconds to wait
for a lock.
Code an error indicator on your read or chain.  U can use a INFDS and check
the status code for (I forget the number off the top of my head.  Think it
is 1217 but don't quote me on that), or you can just assume that the error
is a record lock and present a screen to the user indicating such)  as for
who is looking the record, it is located in the low level messages.  You
could use a CL to receive the program messages until you get to the one that
contains the record lock message and pull the message data out of it.  Sorry
I don't know the CPF message # off hand.


Joe Giusto II
Patuxent Publishing Company
 <mailto:jgiusto@patuxent.com> mailto:JGiusto@patuxent.com
http://www.lifegoeson.com <http://lifegoeson.com> 


-----Original Message-----
From:   Joel Fritz [SMTP:JFritz@sharperimage.com]
Sent:   Monday, June 28, 1999 2:25 PM
To:     'RPG400-L@midrange.com'
Subject:        RE: Record Lock message

The simplest(?) method is to use the error indicator on the file opcode and
pipe the output from wrkobjlck or dsprcdlck to a spooled file that you
display in a little callable module.  Getting the immediate response can be
a problem since there is a system value that controls how long a program
will wait for resolution of a record lock.  My experience is that users on
PCs will often reboot before the delay period has passed.  I bet there's a
more elegant way to do it with APIs. 

-----Original Message-----
From: Rajeev Asthana [mailto:Rajeev_Asthana@paramount.com]
Sent: Monday, June 28, 1999 10:31 AM
To: rpg400-l@midrange.com
Subject: Record Lock message


Hi All,

In my application, if someone is using a record and someone else is trying
to
use it, a message should be displayed immediatly stating the same together
with
the user's name who is holding the record.
What can be the better way to do this?

Any help appreciated.

Thanks in advance.

Rajeev.


* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the RPG/400 Discussion Mailing List!  To submit a new         *
* message, send your mail to "RPG400-L@midrange.com".  To unsubscribe   *
* from this list send email to MAJORDOMO@midrange.com and specify       *
* 'unsubscribe RPG400-L' in the body of your message.  Questions should *
* be directed to the list owner / operator: david@midrange.com          *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the RPG/400 Discussion Mailing List!  To submit a new         *
* message, send your mail to "RPG400-L@midrange.com".  To unsubscribe   *
* from this list send email to MAJORDOMO@midrange.com and specify       *
* 'unsubscribe RPG400-L' in the body of your message.  Questions should *
* be directed to the list owner / operator: david@midrange.com          *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the RPG/400 Discussion Mailing List!  To submit a new         *
* message, send your mail to "RPG400-L@midrange.com".  To unsubscribe   *
* from this list send email to MAJORDOMO@midrange.com and specify       *
* 'unsubscribe RPG400-L' in the body of your message.  Questions should *
* be directed to the list owner / operator: david@midrange.com          *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.