Managing signed objects

 

Use this information to learn about i5/OS^® system commands and system values that you can use to work with signed objects and how signed objects affect backup and recovery processes.

Beginning in V5R1, IBM^® started signing i5/OS. licensed programs, and PTFs as a way of officially marking the operating system as originating from IBM and as a means of detecting when unauthorized changes occur to system objects. Also, business partners and other vendors may be signing the applications that you purchase. Consequently, even if you do not sign objects yourself, you need to understand how to work with signed objects and how these signed objects affect routine system administrative tasks.

Signed objects primarily affect backup and recovery tasks, specifically how you save objects and restore objects onto your system.

• System values and commands that affect signed objects
  This topic provides information about i5/OS system values and commands that you can use to manage signed objects or that have an affect on signed objects when you run them.

• Save and restore considerations for signed objects
  This topic provides information about how signed objects affect how you perform save and restore tasks for your system running the i5/OS operating system.

• Code checker commands to ensure signature integrity
  Learn about using i5/OS commands to verify object signatures to determine object integrity.

• Verifying code checker function integrity
  Learn how to verify the integrity of the code checker function that you use to verify i5/OS system integrity.

 

Parent topic:

Object signing and signature verification