• July 1, 2022

iCluster Cross-Library Logicals Report – A Catch 22!

If you have iCluster 7.1 TR1 or earlier, you are governed by a restriction in iCluster that has existed since the product was first introduced. Physical files and their associated logical files must reside in the same replication group. If you have good developers who keep all of the logicals and physicals in the same library, this is not a problem. If you are not so well blessed, there is a report to help you out. The Cross-Library Logicals report will list all of your files that have logicals and physicals in different libraries, to assist in configuring iCluster.

So here is the “Catch 22”. To get the Cross-Library Logicals Report you need to be at iCluster 7.1 TR2, but at TR2 the requirement to have logicals and physicals in the same replication group has been eliminated! There is a small tip to help if you are not at TR2, DMXtras had a command called HPRTXLF which is in essence the same report. My advice would be to upgrade to TR2 to get the report and keep your groups the way they are currently.

Below is the command which can be accessed through GO DMREPORTS and Option 11 or by using the DMRPTXLF command:


The only two parameters are Library and Output. Output is identical to most of the other reports, the default is to write the results to a spool file OUTPUT(*PRINT) but if the command is run interactively you can specify OUTPUT(*) to show the report on the interactive session.

The Library parameter can be set to *ALL for all libraries, *ALLUSR for all user libraries, *LIBL or *USRLIBL to look at libraries in the library list or user libraries in the library list, or finally just for a specific library.

In this example, I am checking only library MIKEW_X. Here are the results:


You can see the first section of the report shows physicals in library MIKEW_X with logicals in a different library – and there is one physical file called HACUST which has 3 logicals called HACUSTL in three different libraries – QGPL, KAL and KALTEST.

The second section of the report shows logicals in library MIKEW_X with physicals in a different library:


Here you can see all of these are system constraints (files beginning with SYS) that will always have their physicals in QSYS. You will note that KAL and KALTEST library logicals that we saw in the first section of the report are not listed as I only told the command to look at files in MIKEW_X. To see the logicals in KAL and KALTEST pointing back to HACUST, I would have to rerun the command perhaps using *ALL or just KAL as a library.

While the need for this report has diminished in terms of iCluster at TR2, it still may be helpful for programmers or system administrators trying to figure out why a physical file can’t be deleted!

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.


Leave a Comment

Your email address will not be published.