Rechecksum Store Command

The Rechecksum Store command is used to create a checksum for each file in a store. Typically you would use this on migrated files.

This page discusses:

Syntax

rechecksum store STORE_NAME [continue] [commit N] ;

The checksum for a file is calculated only if it has not been previously calculated. If a checksum is calculated, it will be based on an up-to-date copy of the file at an arbitrary location. The checksum value will be propagated to all non-obsolete copies of the file.

You can trace the rechecksum event by using the trace type store command that logs the store’s events. For more information, see trace Command.

This method of creating checksums for files that were migrated and not individually checked in (and thus did not have a checksum created at checkin) assumes the files are not already corrupted. You might find it helpful to run the validate command first. For more information, see Validate Store.

The rechecksum store command applies only when checksum has been turned on at the store level. For more information, see Add Store Command.

Using the rechecksum command during migration could consume a lot of time. For large stores and locations, it might be impractical to do a rechecksum store command. In this case, you can either use rechecksum buslist to migrate only active objects, or do not userechecksum at all. If you do not use rechecksum at all, only files that are newly checked in (with the checksum option on) will have their checksums verified on checkout. For more information, see Rechecksum Business Object or Business Object List.

Continue Clause

Include the keyword continue if you do not want the command to stop if an error occurs. If the log file is enabled, failures are listed in the file. For more information, see trace Command. For example:

rechecksum store "Engineering-Dallas" continue;

If an error occurs when using the continue clause, the existing transaction is rolled back, so any database updates that it contained are not committed. The command starts again with the next business object. When using the continue clause you should also include the commit clause.

Commit N Clause

Include the commit N clause when creating checksums for large stores. The number N that follows specifies that the command should commit the database transaction after this many objects have had a checksum created for them. The default is 10. For example: 

rechecksum store "Engineering-Dallas" continue commit 20;