Page 1 of 1

Debug the CICS program with out increasing the cost.

Posted: Thu Apr 14, 2016 4:56 pm
by Shuku
Hi,

We usually Xped the CICS programs to debug it. It is said to us that, using Xpeditor takes too high CICS CPU time that causes high mainframe utilization and cost. 

Is there any other way to debug the CICS program or are there some good ways for better Xpeditor use in terms of cost reduction?

Re: Debug the CICS program with out increasing the cost.

Posted: Thu Apr 14, 2016 7:28 pm
by Robert Sample
This is a discussion to have with your site support group.  Not all sites use charge backs, so not all sites have your concerns about cost.  And since charge back schemes are HEAVILY dependent upon the site, any advice anyone gives you will be useless unless they work AT YOUR SITE.  Furthermore, your site support group knows the available tools and (probably) their associated CPU costs and can help you choose the best way to debug.

Re: Debug the CICS program with out increasing the cost.

Posted: Thu Apr 28, 2016 12:08 pm
by Shuku
ok. thanks Robert.