Good morning Robert, we found a command that will probably solve the questioning, but we have not yet issued the command, as we are waiting for the management's authorization to perform.
Below is the command that we will test:
/ F SYSVIEW, MODIFY CICSLOGR, START
As soon as we test, I'll report the result.
But answering your question ...
Three more CICS are in production and are being monitored by SYSVIEW, but their LOGRECS are not active for storing the logs in the .SYSD, .TRAN, .TSUM, .XLOG files. On the LGLOGS screen, it appears as follows:
SYSVIEW 14.0 BNB1 ------------ LGLOGS, Data Logs ---------- 2018/03/19 09:50:36
Command ====> Scroll * ===> CSR
----------------------------------------------- Lvl 3 Row 22-57 / 57 Col 1-79 / 151
Cmd Name Status Bgn-Date Bgn-Time End-Date End-Time TimeSpan
___ CICSPP02.SYSD EMPTY
___ CICSPP02.TRAN EMPTY
___ CICSPP02.TSUM EMPTY
___ CICSPP02.XLOG EMPTY
___ CICSPP03.SYSD EMPTY
___ CICSPP03.TRAN EMPTY
___ CICSPP03.TSUM EMPTY
___ CICSPP03.XLOG EMPTY
___ CICSPP04.SYSD EMPTY
___ CICSPP04.TRAN EMPTY
___ CICSPP04.TSUM EMPTY
___ CICSPP04.XLOG EMPTY
___ CICSPSC1.SYSD ACTIVE 2018/01/15 17:46:40 2018/03/19 09:45:05 62.7DAYS
___ CICSPSC1.TRAN ACTIVE 2018/03/09 09:41:02 2018/03/19 09:50:27 10DAYS
The CICS I am referring to are the CICSPP02, CICSPP03 and CICSPP0
Thanks for listening.