COBOL Program performance tuning tips

This is a Mainframe COBOL forum - you can post your queries on Mainframe COBOL, VS COBOL II, COBOL/370 , Enterprise COBOL

Moderators: dbzTHEdinosauer, Moderator Group

User avatar
Krishna
Site Admin
Posts: 1052
Joined: Fri Jan 27, 2006 7:50 am

COBOL Program performance tuning tips

Post by Krishna » Wed Nov 22, 2006 12:08 pm

Hi All,


This Thread is for COBOL Performance tuning tips discussion.
Requesting members to participate in this thread.


Regards,
Krishna
www.geocities.com/srcsinc
www.ibmmainframeguru.com
www.jacharya.com

User avatar
Madhusudana Reddy Mandli
Member
Posts: 3
Joined: Wed Nov 15, 2006 6:35 pm

COBOL Performance Tuning Tips

Post by Madhusudana Reddy Mandli » Wed Nov 22, 2006 12:18 pm

Hi ,

This below tips while doing sort in COBOL may be useful to the members.

COBOL Performance Tuning Tips -



If at all possible avoid doing a sort within a COBOL program. COBOL sorts are very inefficient. If you must do a sort in a COBOL program, specifying the FASTSRT compiler option may speed up the sorting process.



Rounding numbers takes longer than the calculation, so try to avoid rounding numeric values.


Thanks,
Madhu

justaprogrammer
Member
Posts: 6
Joined: Tue Jul 18, 2006 12:36 pm

Post by justaprogrammer » Wed Nov 22, 2006 5:31 pm

If at all possible avoid doing a sort within a COBOL program. COBOL sorts are very inefficient. If you must do a sort in a COBOL program, specifying the FASTSRT compiler option may speed up the sorting process.
I agree to what Madhu had adviced over here with a little variation.
if you are using INPUT/OUTPUT procedure then FASTSRT compiler option will not increase the performance.In such cases it is better to use the DFSORT control statements like INREC,OUTREC,SUM,SKIPREC,INCLUDE or OMIT ,STOPAFT etc and put them under the ddname SORTCNTL or IGZSRTCD.

Also you can go through this documnet to know more about performance tuning of your cobol programs.
http://publibz.boulder.ibm.com/cgi-bin/ ... 0617172746
Thanks
justaprogrammer

Captain Nero
Member
Posts: 10
Joined: Fri Jun 20, 2008 4:21 pm
Location: Kolkata, India

Post by Captain Nero » Mon Jun 30, 2008 11:47 am

Hi,

Thanks for your advice, can you please give a short example of how to use this DFSORT commands in COBOL, it will be of great help.

Regards,
Regards,
Captain N.

Som_TCS
Member
Posts: 9
Joined: Thu Jan 08, 2009 4:44 pm
Location: Chennai / Kolkata

Post by Som_TCS » Fri Jan 09, 2009 11:26 am

Captain Nero wrote:Hi,

Thanks for your advice, can you please give a short example of how to use this DFSORT commands in COBOL, it will be of great help.

Regards,
Here r some tips of performance tuning:

1. When performing arithmetic, always use signed numeric fields. COBOL performs faster with signed fields than unsigned fields

2.When writing to variable length blocked sequential files, use the APPLY WRITE-ONLY clause for the file or use the AWO compiler option. This can reduce the number of calls to Data Management Services to handle the I/Os.

3. If you use SEARCH in COBOL, it is better to use SEARCH ALL ( Binary Search)

4. Using indexes to address a table is more efficient than using subscripts since the index already contains the displacement from the start of the table and does not have to be calculated at run-time.
Performance considerations for indexes vs subscripts (PIC S9(8)):
using binary data items (COMP) to address a table is 56% slower than using indexes
using decimal data items (COMP-3) to address a table is 426% slower than using indexes
using DISPLAY data items to address a table is 680% slower than using indexes

5. For loop control variables use binary data items
Performance considerations for loop control variables (PIC S9(8)):
using a decimal (COMP-3) is 320% slower than using binary (COMP)
using a DISPLAY is 890% slower than using binary (COMP)

6.BLOCK CONTAINS 0 RECORDS on FD and BLKSIZE = 0 on DCB - if u r accessing the file sequentially..

There r some complier option which affects run time performance...Can anyone put some lights over that...I am not sure of those...

anyway guys...njoy... :D

prm
Member
Posts: 7
Joined: Wed Apr 22, 2009 8:35 pm

Post by prm » Thu Apr 23, 2009 9:42 pm

Compiler Options also play a significant role in "Performance Tuning" of cobol programmes.

Many compiler options do have a far reaching performance implications on the program during runtime, especially the ARITH, AWO, DYNAM, FASTSRT, NUMPROC, OPTIMIZE, RENT, SSRANGE, TEST, THREAD, and TRUNC options.

Below is the explanation for each of the compiler options mentioned above and how they impact the performance:-

ARITH - EXTEND or COMPAT :
The ARITH compiler option allows you to control the maximum number of digits allowed for numeric variables in your program.ARITH(EXTEND), the maximum number of digits is 31 - Slower. ARITH(COMPAT), the maximum number of digits is 18 - Faster

AWO or NOAWO :
APPLY WRITE-ONLY processing for physical sequential files with VB format.
APPLY WRITE-ONLY , the file buffer is written to the output device when there is notenough space in the buffer for the next record.Without APPLY WRITE-ONLY, the file buffer is written to the output device when there is not enough space in the buffer for the maximum size record.
If the application has a large variation in the size of the records to be written, using APPLY WRITE-ONLY can result in a performance savings since this will generally result in fewer I/O calls.
NOAWO is the default.

DATA(24) or DATA(31) :
Specifies whether reentrant program data areas reside above or below the 16-MB line. With DATA(24) reentrant programs must reside below the 16-MB line. With DATA(31) reentrant programs can reside above the 16-MB line.
DATA(31) is the default.

DYNAM or NODYNAM :
DYNAM ,Changes the behavior of CALL literal statements to load subprograms dynamically at run time. Call path length is longer - slower NODYNAM ,CALL literal statements cause subprograms to be statically link-edited in the load module. Call path length is - faster
NODYNAM is the default.

FASTSRT or NOFASTSRT :
FASTSRT ,Specifies fast sorting by the IBM DFSORT licensed program. - FasterNOFASTSRT ,Specifies that Enterprise COBOL will do SORT or MERGE input/output. - Slower
NOFASTSRT is the default

NUMPROC - NOPFD, MIG, or PFD :
Handles packed/zoned decimal signs as follows:
NUMPROC(NOPFD), sign fix-up processing is done for all references to these numeric data items. NUMPROC(MIG), sign fix-up processing is done only for receiving fields (and not for sendingfields) of arithmetic and MOVE statements. NUMPROC(PFD), the compiler assumes that the data has the correct sign and bypasses this sign fix-up processing.
For performance sensitive applications, NUMPROC(PFD) is recommended when possible.NUMPROC(NOPFD) is the default.

OPTIMIZE(STD), OPTIMIZE(FULL), or NOOPTIMIZE :
Optimizes the object program. OPTIMIZE has the suboptions of (STD/FULL). OPTIMIZE(FULL) provides improved runtime performance, over both the OS/VS COBOL and VS COBOL II OPTIMIZE option, because the compiler discards unused data items and does not generate code for any VALUE clauses for these data items.
NOOPTIMIZE is generally used while a program is being developed when frequent compiles arenecessary. NOOPTIMIZE also makes it easier to debug a program since code is not moved;
NOOPTIMIZE is the default.

RENT or NORENT :
Using the RENT compiler option causes the compiler to generate some additional code to ensure that the program is reentrant.
On the average, RENT was equivalent to NORENT.
RENT is the default.

RMODE - AUTO, 24, or ANY :
Allows NORENT programs to have RMODE(ANY).
When using NORENT, the RMODE option controls where the WORKING-STORAGE will reside.With RMODE(24), the WORKING-STORAGE will be below the 16 MB line. With RMODE(ANY), theWORKING-STORAGE can be above the 16 MB line.
RMODE(AUTO) is the default.

SSRANGE or NOSSRANGE :
SSRANGE - At run time, checks validity of subscript, index, and reference modification references. Its slower than NOSSRANGE.
NOSSRANGE is the default.

TEST or NOTEST :
TEST - Produces object code usable by Debug Tool for the product. It is slower than NOTEST.
NOTEST is the default.

THREAD or NOTHREAD :
THREAD -Enables a COBOL program for execution in a run unit with multiple POSIX threads or PL/I tasks. It is slower than NOTHREAD.
NOTHREAD is the default.

TRUNC - BIN, STD, or OPT :
Truncates final intermediate results.
TRUNC(STD) Truncates numeric fields according to PICTURE specification of the binary receiving field TRUNC(OPT) Truncates numeric fields in the most optimal way TRUNC(BIN) Truncates binary fields based on the storage they occupy
On an average performance analysis -
TRUNC(OPT) > TRUNC(STD) > TRUNC(BIN)
TRUNC(STD) is the default.


Regards
PRM

User avatar
Natarajan
Moderator
Posts: 537
Joined: Fri Oct 10, 2008 12:57 pm
Location: chennai
Contact:

Post by Natarajan » Fri Apr 24, 2009 12:00 pm

Thanks PRM, It is helpful information.
Natarajan
Chennai

basujanm2310
Member
Posts: 2
Joined: Thu Feb 04, 2010 5:12 am

Post by basujanm2310 » Thu Feb 04, 2010 5:16 am

COBOL is for common business oriented language.........

If you use SEARCH in COBOL, it is better to use SEARCH ALL ( Binary Search)


Thanks a lot..........

sachininx
Member
Posts: 8
Joined: Thu Jan 28, 2010 4:55 pm
Location: CHENNAI

Thanks everybody for replying

Post by sachininx » Thu Feb 04, 2010 6:28 pm

Thanks everybody for replying :D
Sachin

chaat
Member
Posts: 19
Joined: Sun Apr 18, 2010 11:51 pm
Location: St. Cloud, Minnesota, USA

Post by chaat » Sun Apr 18, 2010 11:55 pm

I had a situation where we loaded a large VSAM file into memory to be searched by online CICS application. We encountered problems trying to emulate the VSAM START verb using COBOL SEARCH ALL verb when the key does not exist in the array. To get around this we had to write our own BINARY SEARCH in COBOL.

The array which we are searching contains about 240,000 entries.

We found that the hand coded BINARY SEARCH was significantly more efficient in terms of cpu usage than the COBOL "SEARCH ALL" verb.

The code was modeled after KNUTH's binary search, see this link

http://www.z390.org/contest/p21/P21DW1.TXT

the key to maximizing the performance of the code below was to use PIC S9(8) COMP for all the binary fields. This avoids the check for binary overflow in the generated code. Also we used the compiler option TRUNC(OPT) to avoid the code generated to check for truncation.

Note --> the IF statement after the PERFORM loop is to check for a "not found" condition. To emulate the VSAM START command we need to position the INDEX to the first row which is >= the search key.

Code: Select all

      * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
      *                                                               *
      *    NOTICE THAT BECAUSE WE DO SEARCHES FOR KEYS WHICH ARE      *
      *    NOT PRESENT IN THE CACHE, WE HAVE TO USE OUR OWN HAND      *
      *    CODED BINARY SEARCH. THE REASON FOR THIS IS THAT THE       *
      *    SEARCH ALL VERB DOES NOT SET THE INDEX AFTER A NOT         *
      *    FOUND CONDITION TO POINT TO THE LAST ROW IT CHECKED.       *
      *                                                               *
      * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

           MOVE +1                     TO BIN-LOW.
           MOVE BCNTR-TCA1-ENTRIES-USED
                                       TO BIN-HIGH.

           PERFORM WITH TEST AFTER
               UNTIL BIN-LOW > BIN-HIGH
               COMPUTE BIN-RANGE = BIN-HIGH - BIN-LOW
               COMPUTE BIN-MID = (BIN-RANGE / 2) + BIN-LOW
               SET TCA1-INDEX          TO BIN-MID
               EVALUATE TRUE
                   WHEN TCA1-KEY (TCA1-INDEX) = SRCH-TCA1-KEY
                       MOVE 1          TO BIN-RANGE
                       COMPUTE BIN-LOW = BIN-HIGH + 1
                   WHEN TCA1-KEY &#40;TCA1-INDEX&#41; < SRCH-TCA1-KEY
                       COMPUTE BIN-LOW  = BIN-MID + 1
                   WHEN OTHER
                       COMPUTE BIN-HIGH  = BIN-MID - 1
               END-EVALUATE
           END-PERFORM.


           IF TCA1-KEY &#40;TCA1-INDEX&#41; < SRCH-TCA1-KEY
               SET TCA1-INDEX          UP BY +1
           END-IF.
Chuck Haatvedt

email --> clastnameatcharterdotnet

(replace lastname, at, dot with appropriate
characters)

Anuj Dhawan
Moderator
Posts: 1625
Joined: Sat Aug 09, 2008 9:02 am
Location: Mumbai, India

Post by Anuj Dhawan » Mon Apr 19, 2010 5:54 pm

Thanks for sharing Chuck, that's nice. I gotta try it out...:)
Regards,
Anuj

User avatar
Natarajan
Moderator
Posts: 537
Joined: Fri Oct 10, 2008 12:57 pm
Location: chennai
Contact:

Post by Natarajan » Mon Apr 19, 2010 7:20 pm

Very good information shared. thanks Chuck.
Natarajan
Chennai

bharani
Member
Posts: 13
Joined: Fri Oct 09, 2009 2:47 am

Post by bharani » Fri Mar 25, 2011 2:53 pm

Hi all,

I have one doubt.

I can see lot of dead codes in one of the program. (Dead codes, am refering here is commented as well as unused paragraphs)

Will that affect the performance? by removing these codes is it possible to increase the performance or is it possible to save anything by doing so?

Please advice.

Thanks,
Barani

User avatar
dbzTHEdinosauer
Moderator
Posts: 981
Joined: Mon Oct 02, 2006 8:31 pm

Post by dbzTHEdinosauer » Fri Mar 25, 2011 11:26 pm

performance viewed as the module: does not have any effect. (think you need to read and think alittle).

as for as the machine and other tasks,
if you have the optimizer set to 'not generate code that can never logically execute
then the module size is larger,
and that affects the performance of the machine in general
- more work to load a large program than a small program.

now if you are trying to use performance as a topic to have modules 'reasonably clean',
forget it.

If your shop has a good repository,
which would allow for versioning,
thus allowing one to go back a few versions and pick-up a routine or so
then there should be no argument to remove the garbage and make it easier for a programmer to deal with it.

and that is the only benifit.

(and having smaller source files for the compiler to deal with,
but that is nothing, with the speeds of todays computers)
Dick Brenholtz
JCL, SQL and code in programs have an irritating habit of doing what you say,
not what you meant.

newwaysys
Member
Posts: 38
Joined: Tue Apr 14, 2015 3:19 pm
Location: dfd
Contact:

Post by newwaysys » Tue Apr 14, 2015 3:22 pm

I agree to what Madhu had adviced over here with a little variation.
if you are using INPUT/OUTPUT procedure then FASTSRT compiler option will not increase the performance.In such cases it is better to use the DFSORT control statements like
http://mobilenumbertrackr.com/Mobile-Number-Tracer.aspx
INREC,OUTREC,SUM,SKIPREC,INCLUDE or OMIT ,STOPAFT etc and put them under the ddname SORTCNTL or IGZSRTCD.

Post Reply

FREE TUTORIALS

Tutorials
Free tutorials from mainframegurukul
  • JCL Tutorial
    Covers all important JCL concepts.
  • Cobol Tutorial
    This tutorials covers all Cobol Topics from STRING to COMP-3.
  • DB2 Tutorial
    DB2 Tutorial focuses on DB2 COBOL Programming.
  • SORT Tutorial
    This Tutorial covers all important aspects of DFSORT with examples
  • CICS Tutorial
    This CICS tutorial covers CICS concepts and CICS Basics, CICS COBOL Programming.
Interview
Mainframe Interview questions



Other References
Mainframe Tools and others