RE: Record Lock message

["Rajeev Asthana" <Rajeev_Asthana@xxxxxxxxxxxxx>]

Chris,

Though I'm able to pull Message Desciption- "record 8989 already locked by job"
, I'm unable to get Message ID value CPF5027. Is there anything special I need
to do?

Thanks,
Rajeev.





Chris Bipes <ChrisB@cross-check.com> on 06/28/99 11:51:41 AM

Please respond to RPG400-L@midrange.com












Subject:  RE: Record Lock message




OVRDBF FILE(YOUR FILE) WAITRCD(*IMMED) This will cause the program to error
immediate.  In your CHAIN/READx statement put an indicator in the error
position.  When this error is on, test for message CPF5027, CPF5032 &
CPF9853.  The program status data structure hold the Job that has the lock
on the record.  See the message file QCPFMSG for detail on the format of
these messages.  I do not remember exactly which one is presented.  Check
your job logs for the message you get when a record is locked.  Position
40-46 holds the cpf message id and 91-170 hold the message data.  Another
trick to skip the locked record and advanced to the next record is to SETGT
on the key of the locked record and then do your reade.  This is great for
having multiple users working on the first available record in a group. i.e.
telemarketing.

Christopher K. Bipes          mailto:ChrisB@Cross-Check.com
Sr. Programmer/Analyst        mailto:Chris_Bipes@Yahoo.com
CrossCheck, Inc.              http://www.cross-check.com
6119 State Farm Drive         Phone: 707 586-0551 x 1102
Rohnert Park  CA  94928       Fax: 707 586-1884



-----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          *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *