Recommendations

• Most IBM commands duplicated from a release prior to V5R2 will be logged as violations. These commands should be deleted and re-created using the CRTDUPOBJ (Create duplicate object) command each time a new release is loaded.
• Running an Object Integrity Scan requires *AUDIT special authority. Sign on as QSECOFR when changing the object integrity scanning schedule.
• The command may take a long time to run because of the scans and calculations it performs. You should run it at a tim e when your system is not busy.
• Most objects in user libraries are not signed. Using CHKSIG(*ALL) on user libraries will log an error for every object in the library – probably not what you want. All IBM objects are signed, so use CHKSIG(*ALL) on all IBM libraries, and CHKSIG(*SIGNED) on user libraries that are not signed.