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?
Debug the CICS program with out increasing the cost.
- Robert Sample
- Global Moderator
- Posts: 1903
- Joined: Fri Jun 28, 2013 1:22 am
- Location: Dubuque Iowa
Re: Debug the CICS program with out increasing the cost.
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.
Create an account or sign in to join the discussion
You need to be a member in order to post a reply
Create an account
Not a member? register to join our community
Members can start their own topics & subscribe to topics
It’s free and only takes a minute