Joined: 03 Oct 2009 Posts: 1775 Location: Bloomington, IL
It will certainly result in savings; whether those savings will be significant is not something we can answer, as we do not know your environment. The gripping hand is that it should be done regardless.
Joined: 06 Jun 2008 Posts: 8152 Location: East Dubuque, Illinois, USA
I wanted to know will removing theses display will result in any cost saving or not ?
First, you need to find out if cost savings are even possible. Some sites charge back mainframe costs and some sites don't. If your site does not charge back mainframe costs, then there is no chance for cost savings.
If you are using the term "cost savings" in a generic sense, rather than specifically oriented to currency savings, you need to consider that a current z/Architecture machine will execute tens of millions to hundreds of millions of lines of COBOL per second of CPU time. If we assume 100 million lines of COBOL per second of CPU time, and we assume the program uses one second of CPU time (most use more), and we assume that your DISPLAY statements take an average amount of CPU time per statement, saving 20,000 lines of DISPLAY statements in your program will reduce the CPU usage (and hence cost) a grand total of 0.02% (2 ten-thousandths). Even assuming the DISPLAY statements use 5 times as much CPU time as the typical COBOL statement, you are still looking at a "cost savings" of one-tenth of one percent by removing all DISPLAY statements. And, if your program runs a total of 10 seconds of CPU time, the cost savings will go down by a factor of 10. Depending upon how you play with the assumptions, you can come up with a "cost savings" in the range of 2% to 0.002% of the total program cost -- and unless the charge back scheme is really unusual (or there are other reasons to pursue it), there's not going to be much reason to expect cost savings by removing the DISPLAY statements.
Cost savings, like performance improvement, for COBOL programs should be a function of need -- if AND ONLY IF there is a known issue should anyone look at how to improve performance / reduce cost.