# Community version

**URL:** <https://techcommunity.softwareag.com/t/community-version/58079>\
**Category:** Forum\
**Tags:** Former-Crossvision-Products, Application-Composer\
**Created:** [February 6, 2007, 3:31am UTC](https://techcommunity.softwareag.com/t/community-version/58079 "2007-02-06T03:31:21Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ralph\_Zbrog](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/ralph_zbrog/32/78_2.png) [@Ralph\_Zbrog](https://techcommunity.softwareag.com/u/Ralph_Zbrog)\
**Post date:** [February 6, 2007, 3:31am UTC](https://techcommunity.softwareag.com/t/community-version/58079/1 "2007-02-06T03:31:21Z")

</div>

I recently discovered that there are no checkpoints/restarts in any of the batch process that update ADABAS files.  
What is the ‘industry standard’ in this regard? Is there an ADABAS utility to do this sort of process?  
I’m looking for a means of restoring ADABAS to an earlier time due to a batch job ‘failure’.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/techcommunity/original/3X/c/d/cd19967bb605d28a72d77eb83a1cae22f3df2eb8.svg) [@system](https://techcommunity.softwareag.com/u/system)\
**Post date:** [April 2, 2021, 2:39pm UTC](https://techcommunity.softwareag.com/t/community-version/58079/2 "2021-04-02T14:39:02Z")

</div>