Tuning technique for .NetCOBOL.
Tuning technique for .NetCOBOL.
We have an application running on .Net COBOL. Due to long running batch jobs - no application can run during the batch window. And thus the performance of the long running jobs affects the business. Can some please share some tuning techniques for .NetCOBOL applications and if possible can some please drect me to some case studies on similar lines.
-
- Global Moderator
- Posts: 490
- Joined: Sun Aug 25, 2013 7:24 pm
Re: Tuning technique for .NetCOBOL.
Identify the programs which are long-running. Look at the code. Fix the code.
- Robert Sample
- Global Moderator
- Posts: 1886
- Joined: Fri Jun 28, 2013 1:22 am
- Location: Dubuque Iowa
Re: Tuning technique for .NetCOBOL.
You have posted your request on a mainframe forum. Is your .NetCOBOL program running on a z/OS or z/VM or z/LINUX LPAR?
In general, COBOL tuning involves looking at where the code is taking the most time and identifying how to reduce the time used there. Programs are either CPU-bound or I/O-bound (that is, the code mostly waits for CPU time to continue or waits for I/O to complete to continue). With an I/O-bound program, you have to look at how to reduce I/O (such as building tables in memory instead of reading from a file). With a CPU-bound program, you have to look at how to reduce the program code being executed (which may require changing the algorithm, changing variable definitions, or making other efficiency changes). Whether the program is CPU-bound or I/O-bound, using a code profiler can assist in determining where the bottlenecks are in the code.
A Google search of .net cobol tuning returned 382,000 hits. Have you done your basic research by using Google and reading some of these pages?
In general, COBOL tuning involves looking at where the code is taking the most time and identifying how to reduce the time used there. Programs are either CPU-bound or I/O-bound (that is, the code mostly waits for CPU time to continue or waits for I/O to complete to continue). With an I/O-bound program, you have to look at how to reduce I/O (such as building tables in memory instead of reading from a file). With a CPU-bound program, you have to look at how to reduce the program code being executed (which may require changing the algorithm, changing variable definitions, or making other efficiency changes). Whether the program is CPU-bound or I/O-bound, using a code profiler can assist in determining where the bottlenecks are in the code.
A Google search of .net cobol tuning returned 382,000 hits. Have you done your basic research by using Google and reading some of these pages?
Re: Tuning technique for .NetCOBOL.
It's on z/Linux.
Can we use same profiler tool as we use for Enterprise COBOL todetermine the bottlenecks.
Can we use same profiler tool as we use for Enterprise COBOL todetermine the bottlenecks.
- Robert Sample
- Global Moderator
- Posts: 1886
- Joined: Fri Jun 28, 2013 1:22 am
- Location: Dubuque Iowa
Re: Tuning technique for .NetCOBOL.
I don't know your site so I cannot say. Contact your site support group and find out which tool(s) are available on z/Linux for COBOL performance analysis.
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