Add Inherit Rules to IFS journalling

Today when you set up journalling for the IFS the STRJRN command allows you to filter the objects that are to be journalled, however this is a one off request and the inherit rules are not able to be set to allow future filtering of the objects journalled.

When you start journalling against a library you can set the inherit rules, so you can filter what new objects are journalled when they are created in the library, this would be a very good option at the directory level.

Some application have issues when objects reside on the system which should not be there when a start of the application is requested? This means certain IFS objects if replicated via a HA tool can cause the application to fail.

Filtering of the objects on the target before being applied is an option, but it adds significant overhead in terms of LAN, CPU, Disk and memory managing the filters. Every single journal entry has to be mapped against the filter even if it is to be applied or not.

Many applications generate a lot of temporary IFS files which are not required, being able to filter and not journal will save a lot of overhead, things like .log files are common and can grow to a significant size, asking the developers not to place these in a directory with other files that are required to be journalled and replicated is a non starter.