I cannot see Sync Check deatiled report

iCluster 9.1.0 in IBM i 7.4 with mostly latest PTF groups. 

I first ran DMSTRSC *FULL with OUTPUT(*NONE) at DC system. There were more than 3,000 objects that were reported to be out of sync and I activated them all to DR system.

Then 2 days later, I ran DMSTRSC *CHECKSUM with OUTPUT(*ALL) and saw there were about 250 out-of-sync objects that were activated to DR as well.  But this time, I wanted to see the Sync Check report and I ran DMSCRPT  with DETAILS(*YES) at DR node. The command took about 1 minutes to produce this 1-page report WITHOUT any details at all : 

Then I ran DSPJOBLOG for my 5250 session and saw this error :

What should I do to see the deatiled report of DMSCRPT with DETAILS(*YES)? 

I did a Google search and found a few IBM Technotes mentioning that TCP3701 error happens a lot with the use of remote output queue and it needs port 515 to be opened by the Firewall for remote OUTQ to work.   I will ask this from my network admin to see if it will solve the issue or not.

iCluster 9.1.0 in IBM i 7.4 with mostly latest PTF groups. 

I first ran DMSTRSC *FULL with OUTPUT(*NONE) at DC system. There were more than 3,000 objects that were reported to be out of sync and I activated them all to DR system.

Then 2 days later, I ran DMSTRSC *CHECKSUM with OUTPUT(*ALL) and saw there were about 250 out-of-sync objects that were activated to DR as well.  But this time, I wanted to see the Sync Check report and I ran DMSCRPT  with DETAILS(*YES) at DR node. The command took about 1 minutes to produce this 1-page report WITHOUT any details at all : 

Then I ran DSPJOBLOG for my 5250 session and saw this error :

What should I do to see the deatiled report of DMSCRPT with DETAILS(*YES)? 

Hi Satid,

The OOS record will not exist in metadata anymore after it is activated. This works as design.

Regarding Metadata, please refer to DMSCRUN in ICLUSTER library. Details please refer to DMSCBSFOBJ for BSF object, DMSCNTVOBJ for native object.

Because the DMSCRPT report is generated with the latest metadata, so in the screenshot # failed is 0 for both *FULL and *CHECKSUM sync check and there are no records in Out of Sync or Unavailable Object List part. 

If the spooled file(DMSCRPT) is generated before the OOS records are activated, the mismatch records will be included.

We can generate the sync check spooled file with DMSCRPT after sync check or use DMSTRSC OUTPUT(*ALL or *MISMATCH) to generate spooled file automatically.

Of course, you can get the list of sync check spooled file via WRKCSMON-> F9 or use DSPHASC command directly. 

For the message TCP3436 and TCP3701 I restrict the 515 port manually for both *TCP and *UDP but this error is not reproduced. I'm not sure if there is any other restriction.