OnDemand User Group

Support Forums => z/OS Server => Topic started by: dagerrity on March 05, 2020, 12:57:52 PM

Title: Large sysout handling
Post by: dagerrity on March 05, 2020, 12:57:52 PM

We are new users of CMOD looking for some direction/tips on usage.   We have address spaces (such as CICS regions) that stay up for weeks at a time generating multiple sysouts.  Under CMOD, these sysouts (JESLOG for example) are broken down into many CMOD segments that all look the same from the search screens.  This makes debugging/troubleshooting very cumbersome and problematic.  How can we differentiate the segments?
For example, we have problem occurring in a CICS regions at a specific date and time, how can the segment containing that date/time be located without searching through each of the sysout segments?
TIA

Title: Re: Large sysout handling
Post by: Greg Ira on March 06, 2020, 05:59:58 AM

Most CICS logs have date and time stamps on them.  If you add a GROUPRANGE index for the timestamps you can get the beginning and ending timestamp for the segment.

Title: Re: Large sysout handling
Post by: dagerrity on March 09, 2020, 04:41:49 AM

Thanx very much.  We'll give that a try.

Title: Re: Large sysout handling
Post by: Justin Derrick on March 09, 2020, 01:54:25 PM

I just bumped this over from the "Other" forum, since this seemed very z/OS specific.  Greg's answer is great, but hopefully this post will get a little more attention from being in the right place.  :)

-JD.