Sync TPF File System tables in loosely coupled systems

We cleaned up the tpf file system in one of our sabre systems and noticed other processors didn't reflect the update with a ZFILE df -aic entry. I submitted a case (TS003005946) with the following response:

The numbers for these values sync up over time but can get out of sync. This is by design for performance reasons.
In the TFS, we use #IZERO record ordinals to track the free inodes. This is where we obtain the "inodes available"
information for our memory structures that are out of sync. In order to bring the numbers back into sync we need
to use (find) each of the #IZERO record ordinals. For a system with 1,000,001 #INODE ordinals you would have
1,000 #IZERO ordinals in use. As you create and delete files and directories in the TFS, the #IZERO records are
accessed regularly (once for each file creation or deletion). The #INODE ordinals are returned to the #IZERO where they
originated and are dispensed in a round robin fashion (typically). As we access the #IZEROs as part of allocating or
releasing an #INODE, we also update our processor specific memory tables with the latest available count
from the #IZERO. So a large number of allocates or releases on one processor will cause a skew in this number on the other
processor until that other processor has read in each of the #IZERO ordinals itself (or until you IPL).
If you wanted us to sync the tables that would be an enhancement .
We could either read all of the #IZERO record ordinals when the the zfile DF command is issued OR implement some sort
of sipcc sync up to other processors when a large number of changes are detected within a short amount of time.
Please open an RFE if you want this.