SQLMONITOR is the Tango/04 engine when retrieving data from the iSeries SQL logging system.
When SQLMONITOR starts the monitor launches the STRDBMON command in order to start the iSeries SQL logging system to write data to the database B_DETECTOR/SLDBM01X. The way to configure properly the SQL monitor for interactive sessions is explained in this link.
As the iSeries logger is running the data is being saved to the B_DETECTOR/SLDBM01X database. Records in SLDBM01X database have a data source indicator to be stored in SILOG01X or SLLOG01X database once processed.
As the SQLMONITOR is processing data the recollection pointed is updated in data area B_DETECTOR/SLMONHIST. This pointer is in fact a date the monitor will be retrieving data from that moment on.
Apart from the configuration of the jobs and job types we want to retrieve data from, the configuration for the interactive SQL monitor is internally made by the monitor KRNSUPERV (Kernel Supervisor).
KRNSUPERV monitor uses the B_DETECTOR/ADDDBMJOB command with the qualified job name as input parameter and the flag of the monitor source. In our case, it is *SQI. This command ADDDMBJOB is in charge of activating an SQL supervisor job for the specified job. This way, when a new interactive job starts in an iSeries system and its qualified job name matches the SQL configuration the KRNSUPERV executes the command ADDDBMJOB for this specific job. Therefore, there will be an SQL supervisor for all the jobs matching the configuration made by the user. This command ADDDMBJOB also uses either the SIJOB01P or SLJOB01P to add a new entry with the qualified job name.
Once the interactive job finishes then the Kernel Supervisor Monitor launches the command RMVDBMJOB to stop the SQL supervisor job for this specific job but it does not delete the record from either the SIJOB01P or SLJOB01P databases. These databases are cleared when either the SQLMONITOR or KRNSUPERV monitor starts.
Be careful with the amount of jobs you need to monitor because the performance of the system could increase considerably. Sometimes, if the amount of jobs is huge then the SQLMONITOR can suffer huge delays when processing data. Make sure you have optimized as much as possible the amount of jobs to be monitored. In order to know how many SQL supervisor jobs you have in your system use the iSeries Navigator provided by IBM, concretely the section of the database SQL performance data. Here you can stop and start them if you need to do a cleanup.
Still have questions? We can help. Submit a case to Technical Support.