On Tue, 19 Dec 2023 23:13:46 GMT, [email protected] <[email protected]> wrote:
.
>I have been following the thread on ARR and CSVQUERY, and started
>thinking about a retry routine.
The discussion is about a CBT file that has been referred to as "generic
recovery". I took a 2 minute look at it. It does not do any type of recovery
and I spotted multiple bugs. It only displays some diagnostic data which is not
the hard part.
If you are doing this for a specific project, then you should ask questions and
describe what you want to accomplish. There are many approaches to solving
recovery problems.
>When I hear the words "retry", I interpret that as: re-execute the
>failing instruction.
Completely false interpretation. RETRY is a word that IBM chose because there
was not a better word that describes the true functionality.
Retry is the address where you want to continue. Consider IBM's use of abend
recovery. For example, S0C4 abend is used to verify the existence of an
address.
In my case with a product, I close the current unit of work and then dispatch
the next unit of work.
>Whether it's an ARR or ESTAE, it is my understanding that a Recovery
>Routine may be capable of retrying a failed instruction.
You can choose to retry the failed instruction but remember the definition of
insanity is trying the same thing over and over again while expecting different
results.
>Dose anyone have any experience in developing a ESTAEX or ARR
>where they actually retry the failing instruction ?
Simply retrying the failed instruction serves no useful purpose.
> How should a recovery routine determine which register or data area is
> invalid ?
You design your code to specifically handle this situation. In IBM's S0C4 case,
they know the failing register or they look at the failing instruction.
>How many times should a recovery routine try to re-execute the same
>failing instruction ?
Your design dictates how many times you should retry.
>I guess I'm looking for a strategy for correcting the failing instruction.
>
It's very rare that you need to retry a failed instruction. Why don't you use a
strategy that doesn't need to retry the failing instruction?
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
