Having a LOGGER task abend when a job allocating a SYSVIEW logstream was cancelled.
A quick look at the operlog showed this:
PLOS 20304 08:17:43.68 INTERNAL 00000290 CANCEL TTSYUS01,A=028F
PLOS 20304 08:17:43.68 INTERNAL 00000094 IEE301I TTSYUS01 CANCEL COMMAND ACCEPTED
4040100 PLOS 20304 08:17:43.70 JOB37450 40000010 IXG063I LOGGER ABENDED AND REQUESTED AN SVC DUMP WHILE PROCESSING 941
941 40000010 LOGSTREAM: CASYVW.XXXXXX.TRAN
941 40000010 STRUCTURE: **UNKNOWN**
941 40000010 GROUP: PRODUCTION
941 40000010 MODULE=IXGF2BRW,ABEND=S09C6,REASON=002601FF
4020000 PLOS 20304 08:17:43.70 JOB37450 00000084 GSVX482I (API.XXXXXX) API task abnormal termination in progress
4020000 PLOS 20304 08:17:43.70 JOB37450 00000084 GSVX484I (API.XXXXXX) Abend occurred in an ancestor task
4000000 PLOS 20304 08:17:43.70 00000094 IEA045I AN SVC DUMP HAS STARTED AT TIME=08.17.43 DATE=10/30/2020 944
944 00000094 FOR ASIDS(0007,001B,028F)
944 00000094 ERROR ID = SEQ05755 CPU03 ASID028F TIME08.17.43.6
944 00000094 QUIESCE = NO
SYSVIEW 15.0 & 16.0 - z/OS supported releases -
The reason for ABEND=S09C6,REASON=002601FF is that when the logger took ABEND 47B, the return code was 0.
That was fixed by IBM APAR OA58301 to return a non-zero return code, which would lead SYSVIEW, via fix SO10629, to not make another call to the logger. Thus, avoiding an abend condition such as the one been seen.
IBM confirms that this issue is resolved by IBM's OA58301.