What to do about message PKMR012E "PACKAGE INTEGRITY ERROR" when processing package shipment destinations?

Document ID : KB000014212
Last Modified Date : 14/02/2018
Show Technical Document Details
Question:

What to do about message PKMR012E "PACKAGE INTEGRITY ERROR" when processing package  shipment destinations?

Environment:
Sites upgrading to a current release from a release older than 15.1 (that is, 4.0, 7.0, 12.0, 14.0 or 15.0) may experience this message when accessing destination definitions if they run both releases using the same package file.This may happen for destination definitions that have been created or updated under the new release and are later accessed by the old release.In batch runs, the symptom is an error message:C1BMX23S ERROR IN FILE QUERY FOR DESTINATION "xxxx" - RC=000C REASON=000E
Answer:

As of release 15.1, the destination definition records stored in the package dataset changed their length in order to support Z/OS Unix datasets.

Each record in the package file contains a checksum which is used to ensure that the record is only updated through endevor.

The change in the record length causes the checksum to change when release 15.1 or later updates the record. Then, when the older release tries to access that same record, the integrity error arises

If the old release is 12.0 or earlier, it is NO LONGER possible to access the updated records with it. They need to be deleted and recreated with the old release, or the package file needs to be reloaded from a backup

If the old release is 15.0 or 14.0, it needs the following compatibility fixes in order to be able to access these records

  • RO46425 is for release 15.0
  • RO46424 is for release 14.0