If your organization is running your IBM i system using multiple Auxiliary Storage Pools (ASP), then placement of the journal and journal receivers for the database files you are tracking is important.
An auxiliary storage pool (ASP) is one or more physical disk units assigned to the same storage area. ASPs allow you to isolate certain types of objects on specified physical disk units. Every installation has a System ASP where the IBM i OS resides. For many shops, this is the only ASP on the system and it is known as ASP #1. The IBM i supports up to 32 permanent ASPs (ASP numbers 1-32) and up to 200 more Independent Auxiliary Storage Pools (IASP) which may or may not be currently attached and active on your system (think switchable disc banks).
When you create the journal receiver/journal pair, they must be located in the same ASP where your data is located. This is true for both ASP and IASP installations. If you aren’t sure, you can guarantee that your journal receiver and journal are located in the same ASP by just placing them in the same library where your data is stored.
Some users, however, may want to consolidate all of their journal information in a single library. If this is your objective, then a separate library in each ASP will be needed. In the file journal activation process using the IBM i command STRJRNPF, you will get the error code CPF709D if your journal storage location does not match up with where your data is stored.
Our iFileAudit is a data tracking and audit software solution that uses IBM i journaling technology. Customers who are using multiple ASPs need to pay attention to the configuration in iFileAudit.
If either of the *DFTL or *IFAL values are used, the registration will fail with an error message (CPF709D) if the library where the file resides is in a different ASP. Be sure to enter the specific library name here when using multiple ASPs.
