I found the information in StrobeDB2 Manual, The Strobe SQL Agent must be active to collect SQL data.
•A user ID for the Strobe SQL Agent(i.e.STRSSA)will need to be defined to your security product(RACF,CA-Top Secret, CA-ACF2).
•The Strobe SQL Agent (i.e. STRSSA) will need to be granted MONITOR2 and TRACE user authorization for each subsystem on which you will be using Strobe. A new installation member, STRBGRNT, has been provided for your use.
•A new package will need to be bound for the Strobe SQL Agent (STRSSA) for each subsystem on which Strobe will be used. A new installation job, STRBPBND, has been added to perform this bind. This package is bound, along with the Strobe SQL Analysis packages, into collection STROBE41. The collection is then bound into the STRANANA plan after the Strobe SQL Analysis packages have been bound.
How to make the SQL Agent active in MVS Strobe and Is there any special settings for capturing these reports ?
IF (<--Notice both capital letters!) it worked before, then your system folks have done an upgrade and one of two things happened.
Either the vendor did not include all of the licensed features for your shop, or your shop has decided not to continue using the features.
We had this happen once with Abend-Aid. The upgrade tape showed up, got installed, and all of the IMS sections of the report stopped appearing. We tried to figure it out for about a month before someone thought to call the vendor and ask what they sent. A replacement tape fixed the problem.
The shared libraries of that vendor caused a ripple effect into our STROBE reports too.