Frequently Asked Questions

1. What files can I purge with ARCTOOLS?

ARCTOOLS can purge any externally described file - including physical files, logical files, even multi-format logical files - as easily as writing a query definition. It will create non-keyed physical files in the archive library (if none exists already).

2. Do I need any source code for the files to be archived?

No. No source code is required for the production files. ARCTOOLS uses a proprietary command, RTVPFSRC, which will analyze the existing physical file and create a non-keyed file in the archive library.

3. How does ARCTOOLS work?

   ARCTOOLS has three main functions (and many other smaller functions….):

   	Purge without programming
   	Archive without programming
   	Add the archiving feature to existing purge programs without programming.

   The first two functions utilize a proprietary approach to create a custom ILE RPG program to either delete records or archive and delete records meeting the user specified criteria. The third function utilizes the journaling features of the AS/400 to ‘undelete’ records deleted by your existing purge programs.

4. My packaged software uses the CPYF approach to purging data. Should I be worried?

Perhaps. This can be a crude, quick and dirty, brute force approach to purging. Some implementations of this approach to ‘purging’ copies your data from the original file to a temporary file, then clears the original file, then copies the data back, excluding the data to be purged. This is usually prohibitively long running and obviously requires exclusive file allocation. If the purge (or the hardware) were to fail mid-stream, results could be devastating. Purging and archiving would be much safer by using ARCTOOLS instead of these types of purges.

5. Are there any types of purge-only routines that the ARCDATA feature of ARCTOOLS can’t archive data from?

ARCTOOLS can archive data from any existing purge routine that can support journaling. Typically, any RPG or other similar language purge program will work with ARCTOOLS. Some purge routines use a ‘copy file’ (CPYF) approach to ‘purging’ where a copy file using a record selection test is used to perform purging. Since the file is usually cleared during this purge design, journaling will not work properly.

6. My software doesn’t really ‘delete’ records when it purges, it sets a flag on the records that ‘inactivate’ the records. Can ARCTOOLS help me?

Definitely. If those records are really not needed, they are wasting space and slowing down your machine. Check with your application software vendor first, but simply archiving those records to a different library can speed up your production system considerably. If your files include an ‘inactive record’ indicator, your use of ARCTOOLS will be even easier.

7. Does ARCTOOLS purge data from multiple files simultaneously?

YES!!!. As of version 5, ARCTOOLS can purge data from physical files, logical files, even multi-format logical files.  The multi-format logical file support allows purges of order header/order detail files quick and easy.  Using a multi-format logical, choose purge criteria based on fields on the header record.  ARCTOOLS will then purge the header file and all the subordinate records.

8. Can ARCTOOLS do referential integrity checking when purging?

YES!!!. As of version 5, purges can be set up that pull together multiple files. So, very complex scenarios can be set up quickly and easily, without programming.  An example of such a scenario would be:  purge the sales order if the order is closed, the close date is less than 1/1/97, the invoice is paid, the check has cleared, and the customer status is set to inactive.

9. What validations are performed by ARCTOOLS?

ARCTOOLS performs extensive validations on the purge request (field types, data ‘reasonableness’ tests, etc). It also performs extensive file compatibility testing to ensure that the target archive file is compatible with the production file being purged. If any compatibility problems are found, the purge or archive job is stopped and the user is notified.

10. Is source code included for ARCTOOLS?

No.

11. Are customized versions of ARCTOOLS available?

Custom modifications to the ARCTOOLS product can be arranged separately.

12. Is ARCTOOLS Year 2000 compliant?

ARCTOOLS performs no date processing outside of checking the status of your license term. It’s code is Year 2000 compliant. Y2K compliance is guaranteed on v3r1 or higher.  For more information see our Y2K compliance information.  Click here.

13. How does ARCTOOLS help me keep track of my archived data?

For every purge and/or archive job run by ARCTOOLS, extensive audit trails are maintained. These audit trails include such things as the original file and library, the archive library, the number of records purged and/or archived, and the original request parameters (record selection tests, etc). Reports are included with ARCTOOLS to detail this audit trail data.

14. If I archive my data and move it to tape, how will ARCTOOLS help me find it?

ARCTOOLS includes a utility to copy (or move) your archived data off to tape. Audit trail data is created regarding the copy or move to tape. Archive data can be copied to multiple tapes.  The audit trail reports detail the tape backup information.

15. Can ARCTOOLS help me keep my data current with respect to my packaged application software upgrades?

Quite possibly. If you archive your data consistently, then you could possibly restore all your archived data prior to a software version upgrade. If your software package includes conversion utilities, it may be possible for you to convert all your data (including your archived data), then re-purge the data after converting to the new version of the application software. Check with your application software vendor for advice on this approach.

16. Can ARCTOOLS delete data that I want to keep?

ARCTOOLS does exactly what it’s told. Just like an RPG program, if you tell it to do something, it will do it. It is up to the user to be careful when submitting ARCTOOLS commands to ensure that the request is accurate.

17. Can I use ARCTOOLS commands in a CL program that I write?

Some of the feature can be. You can automate the use of ARCTOOLS by building your own routine for submitting purge and archive commands.  The PurgeWizard command can be built directly into a CL program.  The RulesWizard and JoinWizard can be called from CL programs if the 'rules' (the file selections, record selection tests, etc) are set up ahead of time.

18. Do I need to use journaling to use ARCTOOLS?

Journaling is required for the ‘add archiving to existing purge programs’ feature (ARCDATA) of ARCTOOLS. The ‘purge without programming’ and ‘purge and archive without programming’ features of ARCTOOLS do not require journaling.

The ReorgWizard uses commitment control to ensure data integrity.  This requires journaling.  If your files is already journaled, great.  If not, ReorgWizard will start journaling for the file at the start of the reorg and turn it off when it's finished.

19. Will I need to run journaling all the time?

No. Journaling is only required if you are using the ARCDATA command.  It is only required while your existing purge programs are being run. Utilities are included with ARCTOOLS to start and stop journaling.

ReorgWizard will manage it's own utilization of journaling, if required.

Copyright © 1996 - 2008 by DCSoftware, Inc.
Last modified: November 05, 2008  

ARCTOOLS, ARCTOOLS/400, ReorgWizard, PurgeWizard, JoinWizard, RulesWizard and ARCDATA are trademarks of DCSoftware, Inc.

All materials (c)1996 - 2003 by DCSoftware, Inc.  All rights reserved.