If you are into clean ups etc a good practice is. Main line code Do something set Bit0 Do somethingelse set bit1 ...
In the recovery code you do the opposite order (this is important) if bit1 then undo something else if bit0 then undo something. Where something could be a database call, set an option, get storage, set a flag in memory. Your recovery code could be comparable in size to the main line code! Colin On Thu, 3 Jul 2025 at 17:55, Jon Perryman <[email protected]> wrote: > On Thu, 3 Jul 2025 06:11:47 -0500, Thomas David Rivers <[email protected]> > wrote: > > > IBM provides a way to query the link-state state, but doesn't provide > > a way to restore it to a previous state (except through the recovery > > mechanism. > > As someone mentioned before, standard save areas will give you more > control. Don't forget about cleanup. Whether you use BAKR or saveareas, the > routine at a minimum will have obtained storage and potentially other > actions like closing files and transaction backout my need to be > considered. Instead of restoring to a point in time savearea, you might > want to consider implementing recovery/cleanup routine associated to each > savearea and run each savearea to completion. If none is provided, then > proceed to the next. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
