flood of console with I/O error messages when Db2 is always tring to allocate/open LOGCOPY1 first for each LOG-READ request

Customer would like to avoid a flood of console with I/O error messages.

The test environment and scenario is as follows.
environment:
- DB2 V11 DATA sharing (We have three MEMBER DB1A, DB2A, DB3A)
- Q-Capture(IIDR for DB2 V10.2.1) server is running on DB2A subsystem which is reading the LOGCOPY datasets for three subsystems (DB1A,DB2A,DB3A) by Q-Capture IFI LOG read request.

scenario and expectation/result:
When DB2A subsytem was reading a LOG from DB1A's LOGCOPY1 dataset, we did 'OFFLINE,FORCE' for the LOGCOPY1 volume in the LPAR2(DB2A running) to simulate a I/O error.
We expected
- Once DB2A subsystem detected the I/O error for LOGCOPY1 dataset, DB2A continue to read the next log from the LOGCOPY2 dataset first.
- our expectation is that minimum I/O error messages are appeared.
But, the result is
- It looks the log manger is always trying to allocate/open LOGCOPY1 frist for each LOG-READ request.
so, too many I/O error messages are appeared. This is a design issue.

13:47:38.45 V 4E21,OFFLINE,FORCE
13:47:38.45 *374 IEE800D CONFIRM VARY FORCE FOR 4E21 - REPLY NO OR YES
13:47:46.13 R 374,YES
13:47:46.13 IEE600I REPLY TO 374 IS;YES
13:47:46.13 IOS102I DEVICE 4E21 BOXED, OPERATOR REQUEST
13:47:46.13 IEE793I 4E21 PENDING OFFLINE AND BOXED
13:47:46.14 IEF524I 4E21, VOLUME SMP016 PENDING OFFLINE
13:47:46.41 IOS000I 4E21,**,SIM,**,**06,,,SMP016,CATALOG
13:47:46.41 IEC331I 050-026(0000000C,SMP016),DB2AMSTR,DB2AMSTR,VALO,
IGG0CLE5
13:47:46.41 IEC161I 229(050,026,IGG0CLE5)-232,DB2AMSTR,DB2AMSTR,
SYS00019,,,
IEC161I DSNDB0A.DB1A.LOGCOPY1.DS02
13:47:46.42 IEA045I AN SVC DUMP HAS STARTED AT TIME=13.47.46 DATE=03/3
FOR ASIDS(0169,0155,0168,016A)
QUIESCE = NO
13:47:47.79 IEA992I SLIP TRAP ID=J104 MATCHED. JOBNAME=DB2AMSTR, ASID
13:47:47.79 IEA411I SLIP TRAP ID=J104 DISABLED FOR MATCHLIM
13:47:46.41 DSNJ104I -DB2A RECEIVED ERROR STATUS 82E5E800 FROM
FOR DSNAME=DSNDB0A.DB1A.LOGCOPY1.DS02
13:47:47.80 DSNJ700I -DB2A DSNJPB01 ERROR ATTEMPTING TO ACCESS
BSDS FOR PEER MEMBER ID= 0, MEMBER NAME= DB1A,
REASON-CODE= 00D10908.
13:47:47.83 IEA794I SVC DUMP HAS CAPTURED:
DUMPID=005 REQUESTED BY JOB (DB2AMSTR)
DUMP TITLE=SLIP DUMP ID=J104
13:47:48.33 IOS000I 4E21,**,SIM,**,**06,,,SMP016,CATALOG
13:47:48.33 IEC331I 050-026(0000000C,SMP016),DB2AMSTR,DB2AMSTR,VALO,
IGG0CLE5
13:47:48.33 IEC161I 229(050,026,IGG0CLE5)-232,DB2AMSTR,DB2AMSTR,
SYS00019,,,
IEC161I DSNDB0A.DB1A.LOGCOPY1.DS02
13:47:48.33 DSNJ104I -DB2A RECEIVED ERROR STATUS 82E5E800 FROM
FOR DSNAME=DSNDB0A.DB1A.LOGCOPY1.DS02
13:47:48.33 DSNJ700I -DB2A DSNJPB01 ERROR ATTEMPTING TO ACCESS
BSDS FOR PEER MEMBER ID= 0, MEMBER NAME= DB1A,
REASON-CODE= 00D10908.
13:47:48.84 IOS000I 4E21,**,SIM,**,**06,,,SMP016,CATALOG
13:47:48.84 IEC331I 050-026(0000000C,SMP016),DB2AMSTR,DB2AMSTR,VALO,
IGG0CLE5
13:47:48.85 IEC161I 229(050,026,IGG0CLE5)-232,DB2AMSTR,DB2AMSTR,
SYS00019,,,
IEC161I DSNDB0A.DB1A.LOGCOPY1.DS02
13:47:48.85 DSNJ104I -DB2A RECEIVED ERROR STATUS 82E5E800 FROM
FOR DSNAME=DSNDB0A.DB1A.LOGCOPY1.DS02
13:47:48.85 DSNJ700I -DB2A DSNJPB01 ERROR ATTEMPTING TO ACCESS
BSDS FOR PEER MEMBER ID= 0, MEMBER NAME= DB1A,
REASON-CODE= 00D10908.
.....
..... Same messages continue endlessly until the volume is brought back to online
-----------------------------------------------------------------
Please refer to the PMR 10662,69G,760.