[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference clt::cobol

Title:VAX/DEC COBOL
Notice:Kit,doc,performance talk info-->DIR/KEY=KIT or DOC or PERF_TALK
Moderator:PACKED::BRAFFITT
Created:Mon Feb 03 1986
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:3250
Total number of notes:13077

3242.0. "COBOL V2.4 ... executables has increased by 20%" by SIOG::HANLEY () Tue May 13 1997 16:25

    
    
        This concerns a Cobol compile problem is the Alpha
        environment. An upgrade to V2.4 has been applied. However, 
        the size of executables has increased by 20% as a result. 
        
        Any ideas why this should be so.
    
        Regards,
        Patrick Hanley
      
T.RTitleUserPersonal
Name
DateLines
3242.1Our measurements of object size changes (V2.3, V2.4, /NOOPT)PACKED::BRAFFITTTue May 13 1997 19:0528
>        This concerns a Cobol compile problem is the Alpha
>        environment. An upgrade to V2.4 has been applied. However, 
>        the size of executables has increased by 20% as a result. 
>        
>        Any ideas why this should be so.
    
    We measure DEC COBOL object sizes from version to version by compiling
    the 433 ANSI-85 tests.  Between DEC COBOL V2.3 and DEC COBOL V2.4, we
    measured a small drop (less than 1%) in object sizes for these 433
    ANSI-85 tests with /OPT:LEVEL:4 (the default).  We also did one other
    measurement with these 433 tests.  /OPT:LEVEL:0 increased object sizes
    by approximately 15% as contrasted with /OPT:LEVEL:4 (both measurements
    using DEC COBOL V2.4).
    
    Of course, these types of measurements are highly application
    dependent.
    
    Which version of DEC COBOL is being using now?  V2.4-863 on
    OpenVMS Alpha?
    
    Which version of DEC COBOL was used previously?
    
    Which compile and link qualifiers are used?
    
    Which version of the operating system is being used?
    
    If you could post one of the source files, we could attempt to
    duplicate this difference on our systems.
3242.2SIOG::HANLEYMon May 19 1997 10:5654
        
    Some answers ...
    
    i.   Current DEC COBOL version..   V2.4-863
    
    ii.  Previous version...           V2.2
    
    iii. Examples of a link are located in ISTS$TARCH_COM: (logical
         only defined in ISTSDEV_SSG)
    
    $       link /'debug_stat' -
                 /map=sys$login:'p1'_form_a.map -
    
    /share=ists$'release'A:['project_dir'.EXE]'form_exe_name'.exe  -
                 /nosysshr -
                 ists$'release'A:['project_dir'.OBJ]'p1'_form.obj, -
    
    ists$'release'A:['project_dir'.OBJ]ists_'project'/lib, -
                 ists$'release'A:[CMN.OBJ]ists_cmn/lib,     -
                 wb$wbc:alpha_wb_gbl_opt/opt,  -
                 sys$library:alpha_dswlib/lib, -
                 wb$wbc:alpha_user_prof_opt/opt, -
                 wb$wbc:alpha_form_opt/opt
    
    
         Example of a compile;
    
    $SQLPRE ISTS$'release':['project_dir'.SRC.COB]'sco_name'-
                    /OPTIMIZE-
                    /GRANULARITY = BYTE -
                    /RESERVED_WORDS=NOXOPEN -
    /LIST=ISTS$'release'A:['project_dir'.SRC.COB]/COPY_LIST -
    /OBJ=ISTS$'release'A:['project_dir'.OBJ]'sco_name'
    
    
    iv.  Version of operating system   OpenVMS V6.2
    
    
    The only 'proof' of an increase in size is from forms exes that
    haven't been purged, the installation was done sometime in
    April.
    
    Directory DISK$ISTS_AXP_P2:[ISTS_DEV.ONLINE.EXE]
    
    ISTSOL03_CLM_MNT_FORM_R3_0.EXE;35
                            5819/5823     14-MAY-1997 10:13:11.59
    ISTSOL03_CLM_MNT_FORM_R3_0.EXE;34
                            4618/4626     10-FEB-1997 12:14:05.66
    
    I can request a program from the development group if it would help.
    
    
    Regards,
    Patrick
3242.3We could try one of the .COB filesPACKED::BRAFFITTFri May 23 1997 10:0814
>    I can request a program from the development group if it would help.
    
    If you provide one of the .COB files, we can use both the V2.2 compiler
    and the V2.4 compiler with the qualifiers you are specifying, so we
    could at least compare .OBJ size.  However, we won't be able to link
    your programs on our systems since we don't have the libraries you are
    using.
    
>    $       link /'debug_stat' -
>                 /map=sys$login:'p1'_form_a.map -
    
    Since you are producing a link map, these could provide you some
    insight into which parts of the application contributed more of the
    .EXE size during the link.