× 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.


  1.  Home
  2. RPG400-L
  3. June 2006

RE: Condition handler and lock waits - Retry! Retry!

Larry,
        I noticed on our system a record lock sent to the *EXT message
queue is actually RNQ1218 not RNX1218.  Did you mean RNQ verses RNX?
The RNQ message gives you the retry option. 

<snip>
Hmmm... The thing that gets me is the fact that the system happily
allows
the failing command to be "rerun". If I ignore the RNX1218 *ESCAPE
message
and resume at the next processing instruction (action code 10), it gets
"handled" and a RNX1218 *INQ message is issued - this has a (R)etry
option.
If the uses replies with R then the system attempts to allocate the
record
again. So the code is in there, it is a case of forcing it to run
without
displaying that screen to the user.
</snip>

Thanks, Matt

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.