Using Software Delivery › Using the Software Package Library › Package Consistency Check

Package Consistency Check

Package consistency checking provides protection of packages against becoming corrupted. In effect, this means that if files are added, removed, or replaced with files of a different size in a package, and consistency checking is enabled on the package, then the software delivery functions refuse to distribute it and an error message is returned.

You can enable or disable package consistency check through the DSM Explorer, opening the Properties page of the software package in question. By default, the package consistency check feature is enabled when importing and creating new packages.

A checksum refers to the number of files, their names and size, but it does not involve the actual contents of the files.

The checksum is updated, when the following applies:

• An update is made to the package (like adding files)
• Registering new software packages
• Restoring software packages
• Auto-registering software
• Sealing a software package

The checksum is verified against the previously calculated checksum in the following cases:

• When enabling consistency checking
• When setting up new delivery environments
• Prior to execution of a nonexternal procedure on the agent

Notes on Checksum Calculation:

• Checksum control is also enabled by default when registering products through the command line.
• If a job has been set up for many targets, and a checksum error is detected during job distribution, all jobs that are not yet successfully completed will end with error. For example, the job for the first target computer executes OK, but when the job is to be delivered to the next computer, the software delivery manager detects a checksum error. Then the jobs for the next, and all subsequent target computers, will fail unless the checksum error is corrected.
• No checksum calculation is made on an software delivery agent unless it executes a job.