• July 1, 2022

The iCluster replication coverage report

In our last post we covered the Group Status Report, which is option 3 from the Reports Menu. In this post we skip over option 4 the sync check report, as this is just the regular DMSCRPT (Generate Sync Check Report) command which generates a report based on what is in the sync check metadata files.

Option 5 is a new report called the Replication Coverage report, which is used to generate a report which lists the user libraries, IFS, directories and DLO folders on the current machine and their replication coverage by the iCluster product. This command can be run on any node in the cluster and the objects listed are the objects that exist on the node on which the command is being run.

Below is the command DMRPLCVRPT.


There are not a lot of parameters for this command. The last parameter OUTPUT is identical to the previous reports and specifies whether you would like to optionally see the report on your display OUTPUT(*) in addition to the spool file which is always created. Note that the data for the report is stored in the DMRPLCVG metadata file, which is cleared before each run. This means the data is NOT cumulative and only contains data for the current command run.

The first parameter is coverage type CVGTYPE and determines whether both libraries (native objects) and IFS/DLO objects are listed CVGTYPE(*ALL), just native objects CVGTYPE(*LIBRARY) or just IFS/DLO objects CVGTYPE(*PATH). If *ALL is specified, which is the default, the report consists of 2 parts, the first section is for library replication coverage and the second section is for IFS/DLO. Depending on your environment CVGTYPE(*ALL) may be a very long running option and the command should be submitted in batch!

NOTE: Directory pathnames longer than 50 characters cannot be listed directly in the report. For these directories, the report will list a truncated version of the pathname, along with a numerical identifier for the full pathname. The full pathnames of truncated directory pathnames are listed at the end of the report in a mapping table.

The second parameter is Order and here is where the real power of the command comes into play! The default value is ORDER(*ALPHA) which lists all objects in alphabetical order. ORDER(*NOTREPL) lists the user libraries and/or user IFS directories that are not being replicated first, followed by the user libraries and/or user IFS directories and DLO folders that are being replicated by iCluster. ORDER(*REPL) is the opposite of the previous value, listing objects being replicated by iCluster first. The final value ORDER(*ELIGIBLE) lists the user libraries and/or user IFS directories that are eligible for replication by iCluster first, followed by the user libraries and/or user IFS directories and DLO folders that are not eligible for replication.

A set of reason codes for lack of eligibility as specified next to each object in the report under the RC column includes:

  1. The object is owned by the DMCLUSTER user profile
  2. The object is owned by one of the Rocket Aldon LM(i) user profiles and is not eligible for Aldon LM(i) high availability with iCluster using CFGHAXAPP.
  3. The object is a licensed program product library or directory
  4. The object is in an iCluster work library
  5. The object is in an iCluster staging store library or directory
  6. The object is an iCluster target library or directory for a replication group that has the current node as it’s backup node
  7. The library contains only journals and journal receivers
  8. The directory is a file system that is not supported for replication.

Below is a sample report run with some non-eligibility reason codes.

Sample Replication Report

The only caveat for this report is that your IBM i user profile must be enrolled in the system directory in order to use the DMRPLCVRPT command for DLO folders, and it is recommended that your user profile has *ALLOBJ authority in order to have access to all libraries and directories on the system.

If you like this report, reply back to this post to let me know!

iCluster Tech Tuesday 0 Posts

iCluster TechTuesday is a set of posts covering technical tips and techniques to help get the most out of your Rocket iCluster installation.


  • Q Reply

    March 26, 2015 at 8:05 am

    What would be the result on the reports if there are objects in the library excluded from replication ?

    • iCluster Tech Tuesday Reply

      March 26, 2015 at 9:19 am

      Hello Q.

      Thanks for your question. The report works at the library level not the object level, so as long as the library is defined as an object specifier in a group it will be listed in the report. Note that currently if the library is owned by QSYS or by a user profile owned by QSYS it will NOT be listed in the report, so if you don’t see your library, check it’s owner.

Leave a Comment

Your email address will not be published.