System-managed access-path protection

System-managed access-path protection (SMAPP) allows you to use some of the advantages of journaling without explicitly setting up journaling. Use SMAPP to decrease the time it takes to restart your system after an abnormal end.

SMAPP is a way to reduce the time for an iSeries™ server or independent disk pool to restart after an abnormal end. An access path describes the order in which records in a database file are processed. A file can have multiple access paths, if different programs need to see the records in different sequences.

When the system or an independent disk pool ends abnormally, the system must rebuild the access paths the next time you restart the system, or vary on an independent disk pool. When the system must rebuild access paths, the next restart or vary on operation takes longer to complete than if the system ended normally.

When you use SMAPP, the system protects the access paths so the system does not need to rebuild the access paths after an abnormal end. This topic introduces SMAPP, describes SMAPP concepts, and provides setup and management tasks.

SMAPP concepts
Use this information to find out why you might want to use SMAPP, how it works, and how it affects your system.
  • Benefits of SMAPP
  • How SMAPP works
  • How the system chooses access paths to protect
  • Effects of SMAPP on performance and storage
  • How SMAPP handles changes in disk pool configuration
  • SMAPP and access path journaling
  • SMAPP and independent disk pools
Start or change SMAPP and display SMAPP status
Use this information to start or change SMAPP and to display the status of SMAPP on your server.
  • Start SMAPP or change SMAPP values
  • Display SMAPP status
Related concepts
Reasons to journal access paths
Reasons to journal before-images
Functions that increase the journal receiver size