AFTER RECREATING THE LOGGER FILE SYSVIEW STOPPED WRITING DATA IN IT
Article ID: 117208
Updated On:
Products
SYSVIEW Performance Management
NXBRIDGE - SYSVIEW/ENDEVOR
Issue/Introduction
Cust were collecting MQ data in SYSVIEW logger MQSDATA--but decided to
recreate it in order to change the logger LS/STG size and retention. After
recreating the logger file SYSVIEW stopped writing data in it--and
cust could not find the reason. MQSDATA logger file is empty.
Cust could not find an error message and the logger looked like working well.
It started the MQSDATA started task--the only thing cust noticed is that is
does not occur the message of the MQ connection.
recreate it in order to change the logger LS/STG size and retention. After
recreating the logger file SYSVIEW stopped writing data in it--and
cust could not find the reason. MQSDATA logger file is empty.
Cust could not find an error message and the logger looked like working well.
It started the MQSDATA started task--the only thing cust noticed is that is
does not occur the message of the MQ connection.
Environment
OS: z/OS.
Resolution
The problem was solved changing the parm MONITOR-MQS-REQUESTS from No
to Yes in PARMLIB MQSDATA member.
Probably it was set dynamically to Yes and when cust executed re-start with Cold it
got the parm from PARMLIB--that was set to No.
to Yes in PARMLIB MQSDATA member.
Probably it was set dynamically to Yes and when cust executed re-start with Cold it
got the parm from PARMLIB--that was set to No.
Feedback
Yes
No
Powered by
