[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

3229.0. "NUMLONG error with COBOL/CDD on AXP using huge init. values" by MUNICH::SBECKER (Every minute - every hour, I feel the power) Thu Apr 17 1997 06:08

    
    
    
    
    
    
    
    
    
    
    
    
    Hi, I got a strange customer problem with Cobol and CDD.
    
    Because first I thaught that it is a problem with CDD and asked Oracle
    to have a look at the problem. But they think it is a problem with CDD.
    
    See the extraction of the CDD notes entry for a description.
    
    I tried to reproduce the problem, but I was NOT able to get the error.
    I don't know why.
    
    Has anyone seen this problem before or can anyone reproduce it ?
    
    Thank you a lot advance 
    
    	Sigi Becker, DSC Munich
    
    
    
    
          <<< NOMAHS::DISK$NOMAHS1:[NOTES$LIBRARY]REPOSITORY.NOTE;1 >>>
                           -< Oracle CDD/Repository >-
================================================================================
Note 1081.0         cobol-e-numlong with large initial value             1 reply
5150::KLEIN                                          49 lines  16-APR-1997 11:25
--------------------------------------------------------------------------------
VMS V6.2 AXP
CDD V6.1-03 and V7.0
COBOL V2.4-863

Customer is getting COBOL-E-NUMLONG when including a record from dictionary 
with a field containing a large initial value (> 999999999).
According to the customer (I don't have the versions running here anymore)
he could compile his program successfully with CDD V5.3 and DEC COBOL V2.3-793.

    02  BIGFIELD_Q          PIC S9(11)V9(2) COMP VALUE IS 91540398400843284.49.
..........................................................^
%COBOL-E-NUMLONG, More than 18 digits in numeric literal
at line number 13 in file USER1:[KLEIN.TEST]TEST_REC.;
%COBOL-E-ENDDIAGS, USER1:[KLEIN.TEST]TEST.COB;2 completed with 1 diagnostic

Thanks a lot in advance for any help. Regards,

Ingrid

Script to reproduce the error:

$ create TEST.CDO 
set ver 
delete record/desce test_rec.
define field bigfield_q
    datatype is signed quadword 13 digits scale -2 
    initial_value 1000000000000. 
define record test_rec.
    bigfield_q.
end record.
set nover 
$!
$ DICT OPER @TEST.CDO 
$! 
$ create TEST.COB 
 
*------------------------------------------------------- 
IDENTIFICATION DIVISION. 
PROGRAM-ID. TESTPROG INITIAL. 
DATA DIVISION. 
WORKING-STORAGE SECTION. 
 
COPY 'test_rec'     FROM DICTIONARY. 
 
END PROGRAM TESTPROG. 
*------------------------------------------------------- 
$!
$ COBOL/RESERVED=NOXOPEN/LIST/COPY_LIST/NOOBJ TEST.COB 
$exit 
================================================================================
Note 1081.1         cobol-e-numlong with large initial value              1 of 1
NOVA::SMITHI "Don't understate or underestimate Rdb!" 5 lines  16-APR-1997 12:17
--------------------------------------------------------------------------------
As they upgraded COBOL too, why don't they ask DEC if there is a problem with
COBOL.  It looks like the value is being converted from binary to text
incorrectly.

Ian
    
T.RTitleUserPersonal
Name
DateLines
3229.1list filesMUNICH::SBECKEREvery minute - every hour, I feel the powerThu Apr 17 1997 06:3661
    Here are 2 list files ....
    
    OpenVMS V7.1 on AXP
    Cobol V2.4-863
    CDD 6.1/003
    
    TEST-CDD-53-61                  Source Listing                 
    15-APR-1997 11:11:33  D`
    0                               Source Listing                 
    14-APR-1997 09:32:48  D`
    
                  1 IDENTIFICATION DIVISION.
                  2 PROGRAM-ID. TEST_CDD_53_61 INITIAL.
                  3 DATA DIVISION.
                  4 WORKING-STORAGE SECTION.
                  5 
                  6 COPY 'cdd$top.bigfield_q'     FROM DICTIONARY.
    L             7 *
    L             8 * _CDD$TOP.BIGFIELD_Q
    L             9 *
    L            10 * Copy from BATV tap_fld.tap_max_betr_qk 
    L            11 * For Testing CDD 5.3 and CDD 6.1 
    L            12 * 10 Vorkomma und 2 Nachkommastellen 
    L            13 01  BIGFIELD_Q              PIC S9(11)V9(2) COMP VALUE
    IS 42949672.97.
                 14 
                 15 END PROGRAM TEST_CDD_53_61.
                 16 
    c
    TEST-CDD-53-61                  Source Listing                 
    15-APR-1997 11:11:33  D`
    0                               Program Section Summary        
    .....
    
    
    
    and according to the customer
    Alpha AXP OPEN VMS V6.2 with CDD V6.1-003 and DEC COBOL V2.3-795 
    Alpha AXP OPEN VMS V6.2 with CDD V6.1-003 and DEC COBOL  V2.4    
    
    
    $ COBOL/RESERVED=NOXOPEN/LIST/COPY_LIST/NOOBJ TEST_CDD_53_61.COB
    
    01  BIGFIELD_Q              PIC S9(11)V9(2) COMP VALUE IS
    91521750683636203.53.
    ..........................................................^
    %COBOL-E-NUMLONG, More than 18 digits in numeric literal
    at line number 15 in file
    SYS$SYSDEVICE:[BATV.JQ_BATV]CDD$TOP.BIGFIELD_Q;
    %COBOL-E-ENDDIAGS, SYS$SYSDEVICE:[BATV.JQ_BATV]TEST_CDD_53_61.COB;2 
                       completed with 1 diagnostic
    
    
    but please see that in the first list file the initial value is also
    wrong, but less that 18 characters !!!!!!
    
    
    Sigi
    
    
    
3229.2Could not reproduce with DEC COBOL V2.4 and CDD V5.3PACKED::BRAFFITTThu Apr 17 1997 07:0821
>VMS V6.2 AXP
>CDD V6.1-03 and V7.0
>COBOL V2.4-863

>he could compile his program successfully with CDD V5.3 and DEC COBOL V2.3-793.
>
>    02  BIGFIELD_Q          PIC S9(11)V9(2) COMP VALUE IS 91540398400843284.49.
    
    I could not reproduce this problem with DEC COBOL V2.4 and CDD V5.3.
    
    I successfully ran your script with
    
    	DEC COBOL V2.3-795	CDD V5.3	A/VMS V6.1
    	DEC COBOL V2.4-863	CDD V5.3	A/VMS V6.1
    	VAX COBOL V5.4		CDD V5.3	V/VMS V5.5-2
    
    I left off the /RES=NOXOPEN for VAX COBOL.
    
    There is a known problem with CDD V5.3 and handling of quadwords, and
    CDD made a change in this area with CDD V6.1.  Some details are in
    CLT::DEC_COBOL_IFT note 364.
3229.3may i please see your 2.4 .lis fileMUNICH::SBECKEREvery minute - every hour, I feel the powerThu Apr 17 1997 09:098
    thank you very much for the quick answer !!!!
    
    
    may i please see your 2.4 .lis file with the line where the field is
    included from the cdd ?
    
    
    sigi
3229.4User's CDO definition is inconsistent, I thinkWIBBIN::NOYCEPulling weeds, pickin&#039; stonesThu Apr 17 1997 10:0016
>    datatype is signed quadword 13 digits scale -2 
>    initial_value 1000000000000. 

"13 digits scale -2" is the same as PIC S9(11)V9(2).  The initial value
you're providing is too large for that field -- it needs at least
S9(13)Vwhatever.

If you want 13 digits left of the decimal, and 2 to the right, write
	"signed quadword 15 digits scale -2".

If you want 11 digits left of the decimal, and 2 to the right, you need
a smaller initial value, perhaps "10000000000".

If you want 13 digits left of the decimal, with the two low digits not stored
(same as S9(11)P(2), I think), write "11 digits scale +2".

3229.5TEST.LIS with DEC COBOL V2.4PACKED::BRAFFITTThu Apr 17 1997 10:1668
                                Source Listing                  17-APR-1997 09:15:21  DEC COBOL V2.4-863                Page 1      
                                Source Listing                  17-APR-1997 09:15:19  COB$USER2:[BRAFFITT.WORK]TEST.COB;1  

	      1  
	      2 *------------------------------------------------------- 
	      3 IDENTIFICATION DIVISION. 
	      4 PROGRAM-ID. TESTPROG INITIAL. 
	      5 DATA DIVISION. 
	      6 WORKING-STORAGE SECTION. 
	      7  
	      8 COPY 'test_rec'     FROM DICTIONARY. 
L	      9 *
L	     10 * _CDD$TOP.TEST_REC
L	     11 *
L	     12 01  TEST_REC.
L	     13     02  BIGFIELD_Q          PIC S9(11)V9(2) COMP VALUE IS 10000000000.
	     14  
	     15 END PROGRAM TESTPROG. 
	     16 *------------------------------------------------------- 

TESTPROG                        Source Listing                  17-APR-1997 09:15:21  DEC COBOL V2.4-863                Page 2      
0                               Program Section Summary         17-APR-1997 09:15:19  COB$USER2:[BRAFFITT.WORK]TEST.COB;1  




DIAGNOSTICS SUMMARY

       Informationals       4 (suppressed)
       ----------------------
       Total                4

TESTPROG                        Source Listing                  17-APR-1997 09:15:21  DEC COBOL V2.4-863                Page 3      
0                               Compilation Summary             17-APR-1997 09:15:19  COB$USER2:[BRAFFITT.WORK]TEST.COB;1  



COMMAND QUALIFIERS

   COBOL 

      /NOALIGNMENT                                                   /GRANULARITY = QUAD                                         
      /NOANALYSIS_DATA                                               /LIST                                                       
      /NOANSI_FORMAT                                                 /NOMACHINE_CODE                                             
      /NOAUDIT                                                       /NOMAP                                                      
      /CHECK = (NOPERFORM, NOBOUNDS, NODECIMAL, NODUPLICATE_KEYS)    /NATIONALITY = US                                           
      /NOCONDITIONALS                                                /NOOBJECT                                                   
      /NOCONVERT = LEADING_BLANKS                                    /OPTIMIZE = LEVEL=4                                         
      /COPY_LIST                                                     /RESERVED_WORDS = (NOXOPEN, NOFOREIGN_EXTENSIONS)           
      /NOCROSS_REFERENCE                                             /NOSEPARATE_COMPILATION                                     
      /DEBUG = (NOSYMBOLS, TRACEBACK)                                /NOSEQUENCE_CHECK                                           
      /NODEPENDENCY_DATA                                             /STANDARD = (NOXOPEN, NOSYNTAX, NOV3, 85, NOMIA)            
      /NODIAGNOSTICS                                                 /NOTIE                                                      
      /NOFIPS                                                        /NOTRUNCATE                                                 
      /NOFLAGGER                                                     /VFC                                                        
      /FLOAT = D_FLOAT                                               /WARNINGS = (NOINFORMATION, OTHER)                          
         


COMPILATION STATISTICS

  CPU time:          0.66 seconds
  Elapsed time:      5.49 seconds
  Pagefaults:         827
  I/O Count:          228
  Source lines:        16

  1454 lines per CPU minute.
3229.6no differenceMUNICH::SBECKEREvery minute - every hour, I feel the powerThu Apr 17 1997 11:0652
    
    
    hi again ...
    
    
    I tried this
    
    CDO> show field cdd$top.bigfield_q
    Definition of field BIGFIELD_Q
    |   Description              /* Copy from BATV tap_fld.tap_max_betr_qk 
    */
    |                            /* For Testing CDD 5.3 and CDD 6.1  */
    |                            /* 10 Vorkomma und 2 Nachkommastellen  */
    |   Datatype                 signed quadword 15 digits scale -2
    |   Initial_value            1.000000000000000E+012
                             
    CDO> 
    IDENTIFICATION DIVISION.
    PROGRAM-ID. TEST_CDD_53_61 INITIAL.
    DATA DIVISION.
    WORKING-STORAGE SECTION.
    
    COPY 'cdd$top.bigfield_q'     FROM DICTIONARY.
    
    END PROGRAM TEST_CDD_53_61.
    
    and got this ....
    
    SEE THE INIT VALUE OF BIGFIELD_Q !!!
    
    
    TEST-CDD-53-61                  Source Listing                 
    17-APR-1997 15:`
    0                               Source Listing                 
    14-APR-1997 09:`
    
                  1 IDENTIFICATION DIVISION.
                  2 PROGRAM-ID. TEST_CDD_53_61 INITIAL.
                  3 DATA DIVISION.
                  4 WORKING-STORAGE SECTION.
                  5 
                  6 COPY 'cdd$top.bigfield_q'     FROM DICTIONARY.
    L             7 *
    L             8 * _CDD$TOP.BIGFIELD_Q
    L             9 *
    L            10 * Copy from BATV tap_fld.tap_max_betr_qk 
    L            11 * For Testing CDD 5.3 and CDD 6.1 
    L            12 * 10 Vorkomma und 2 Nachkommastellen 
    L            13 01  BIGFIELD_Q              PIC S9(13)V9(2) COMP VALUE IS 42949672.97.
                 14 
                 15 END PROGRAM TEST_CDD_53_61.
    
3229.7MUNICH::SBECKEREvery minute - every hour, I feel the powerThu Apr 17 1997 11:0913
    > .5 
    
    did you really use a value of 1.000000000000000E+012 in your CDD def ??
    
    CDO> show field cdd$top.bigfield_q
    Definition of field BIGFIELD_Q
    |   Description              /* Copy from BATV tap_fld.tap_max_betr_qk 
    */
    |                            /* For Testing CDD 5.3 and CDD 6.1  */
    |                            /* 10 Vorkomma und 2 Nachkommastellen  */
    |   Datatype                 signed quadword 15 digits scale -2
    |   Initial_value            1.000000000000000E+012
    
3229.8I used the script from .0PACKED::BRAFFITTThu Apr 17 1997 12:093
>    did you really use a value of 1.000000000000000E+012 in your CDD def ??
    
    I ran the script in .0.
3229.9(maybe truncation problem ?MUNICH::SBECKEREvery minute - every hour, I feel the powerThu Apr 17 1997 12:3918
    
    
    >.8 sorry for the stupid question, I asked it, because
    the cdo def is initial_value 1000000000000.
    
    but your lis file says
    13     02  BIGFIELD_Q          PIC S9(11) V9(2) COMP VALUE IS 10000000000.
    
    (maybe there was a truncation when extracting the script from notes,
    may you please check your cdd def again ?)
     
    I always did get back chunk as  COMP VALUE IS, as you can see
    in my lis files.
    
    
    Thank you a lot
    
    Sigi
3229.10Are you getting a failure with CDD V5.3?PACKED::BRAFFITTThu Apr 17 1997 12:506
>    I always did get back chunk as  COMP VALUE IS, as you can see
>    in my lis files.
    
    Are you using DEC COBOL V2.4 with CDD V5.3?  I thought you said this
    worked OK.  I am using CDD V5.3.  My understanding of what you have
    posted is that the problem shows up with CDD V6.1.
3229.11yes CDD V6.1-003MUNICH::SBECKEREvery minute - every hour, I feel the powerThu Apr 17 1997 13:019
    
        Yes, I'm using CDD V6.1-003, that's the only version I have, but I think
        is does not a matter of the CDD version
    
        Greetings
    
    
        Sigi
           
3229.12I think the version of CDD may make a differencePACKED::BRAFFITTThu Apr 17 1997 14:5415
>        Yes, I'm using CDD V6.1-003, that's the only version I have, but I think
>        is does not a matter of the CDD version
    
    I think the CDD version may make a difference.
    
    If you are able to duplicate the problem with CDD V5.3 with any version
    of DEC COBOL, we can take a look at it further to try to isolate what
    may be causing the problem you are seeing.  If things work fine for you
    with CDD V5.3 and fail only with CDD V6.1, you'll have to go to Oracle
    for the next step in isolating the cause of the difference.  The
    DEC/VAX COBOL team is set up to isolate problems with many different
    versions of DEC/VAX COBOL, but our range of CDD configurations is very
    limited.  My guess is that Oracle has a very limited number of versions
    of DEC/VAX COBOL that they can test with, but they may be able to test
    with both versions of CDD the customer has been trying recently.
3229.13Did the suggestions Bill made in .4 help?PACKED::BRAFFITTThu Apr 17 1997 18:182
    Were you able to get the source to compile with CDD V6.x when you
    tried Bill's suggestions from .4?
3229.14the problem is the wrong valueMUNICH::SBECKEREvery minute - every hour, I feel the powerFri Apr 18 1997 04:1924
    
    
    I'm sorry, but I think we have a confusion now.
    
    I (with OVMS V7.1 for AXP, COBOL V2.4 and CDD V6.1) ALSO HAVE a problem
    with the initial value. As you can see in the lis file the copy does
    not copy the correct value into the program.
    Instead of the CDD defined value of 1.000000000000000E+012 I get in MY 
    Cobol lis file the value of 42949672.97.
    
    The only difference between the Oracle and my lis file is that they get
    a "longer value" (more than 18 characters) and so they can see the
    COBOL NUMLONG error message.
    
    But I think the real problem is that we don't get copied the value of 
    1.000000000000000E+012 into the  COBOL program.
    
    I have to say thank you all for the great support so long.
    
    Can anybody reproduce the problem, please ?
    
    
    
    Sigi 
3229.15WIBBIN::NOYCEPulling weeds, pickin&#039; stonesFri Apr 18 1997 09:287
>    I (with OVMS V7.1 for AXP, COBOL V2.4 and CDD V6.1) ALSO HAVE a problem
>    with the initial value.

And Don Braffitt thinks the problem occurs only with CDD V6.1.  Is there any
evidence that it's not caused by the version of CDD?  It seems to work properly
with CDD V5.3 -- does anyone have a case where CDD V5.3 gets an error or the
wrong initial value?
3229.16No reports yet of this problem with CDD V5.3PACKED::BRAFFITTThu May 01 1997 09:2724
          <<< NOMAHS::DISK$NOMAHS1:[NOTES$LIBRARY]REPOSITORY.NOTE;1 >>>
                           -< Oracle CDD/Repository >-
================================================================================
Note 1081.5         cobol-e-numlong with large initial value              5 of 5
ORAREP::PACKED::BRAFFITT                             17 lines   1-MAY-1997 08:23
             -< Problem shows up with CDD V6.1-03 (not CDD V5.3) >-
--------------------------------------------------------------------------------
    RE: .1
    
>As they upgraded COBOL too, why don't they ask DEC if there is a problem with
>COBOL.

    The problem appears to be unrelated to DEC COBOL version.  It seems to
    show up with CDD V6.1-03 (I don't know about higher versions).  We've
    had no reports of this problem with CDD V5.3 used with any version of
    DEC COBOL.
    
>Note 1081.0         cobol-e-numlong with large initial value           4 replies
>VMS V6.2 AXP
>CDD V6.1-03 and V7.0
>COBOL V2.4-863
    
>Note 1081.2         cobol-e-numlong with large initial value              2 of 4
>    CDD 6.1-03 and COBOL 2.2-674.
3229.17Update sent on casePACKED::BRAFFITTTue May 06 1997 14:00152
From:	PACKED::BRAFFITT "06-May-1997 1251"  6-MAY-1997 12:55:39.71
To:	FIXCLD::SDT_ACE,MUNICH::SBECKER
CC:	BRAFFITT
Subj:	UPDATE MGO102795

>>To Engineering please :
>>Thank you very much for your time spending to reproduce the proble
>>m.
>>I have to deal with the Oracle people and need some infos please.
>>- Did you use an Alpha ?

Yes.

>>- Which version of OpenVMS was installed ?
>>- Which versions of Cobol did you try ?

           <<< CLT::DISK$CLT_LIBRARY3:[NOTES$LIBRARY]COBOL.NOTE;1 >>>
                               -< VAX/DEC COBOL >-
================================================================================
Note 3229.2*  NUMLONG error with COBOL/CDD on AXP using huge init. valu  2 of 16
PACKED::BRAFFITT                                     21 lines  17-APR-1997 06:08
           -< Could not reproduce with DEC COBOL V2.4 and CDD V5.3 >-
--------------------------------------------------------------------------------
>VMS V6.2 AXP
>CDD V6.1-03 and V7.0
>COBOL V2.4-863

>he could compile his program successfully with CDD V5.3 and DEC COBOL V2.3-793.
>
>    02  BIGFIELD_Q          PIC S9(11)V9(2) COMP VALUE IS 91540398400843284.49.
    
    I could not reproduce this problem with DEC COBOL V2.4 and CDD V5.3.
    
    I successfully ran your script with
    
    	DEC COBOL V2.3-795	CDD V5.3	A/VMS V6.1
    	DEC COBOL V2.4-863	CDD V5.3	A/VMS V6.1
    	VAX COBOL V5.4		CDD V5.3	V/VMS V5.5-2
    
    I left off the /RES=NOXOPEN for VAX COBOL.
    
    There is a known problem with CDD V5.3 and handling of quadwords, and
    CDD made a change in this area with CDD V6.1.  Some details are in
    CLT::DEC_COBOL_IFT note 364.

           <<< CLT::DISK$CLT_LIBRARY3:[NOTES$LIBRARY]COBOL.NOTE;1 >>>
                               -< VAX/DEC COBOL >-
================================================================================
Note 3229.16  NUMLONG error with COBOL/CDD on AXP using huge init. val  16 of 16
PACKED::BRAFFITT                                     24 lines   1-MAY-1997 08:27
               -< No reports yet of this problem with CDD V5.3 >-
--------------------------------------------------------------------------------
          <<< NOMAHS::DISK$NOMAHS1:[NOTES$LIBRARY]REPOSITORY.NOTE;1 >>>
                           -< Oracle CDD/Repository >-
================================================================================
Note 1081.5         cobol-e-numlong with large initial value              5 of 5
ORAREP::PACKED::BRAFFITT                             17 lines   1-MAY-1997 08:23
             -< Problem shows up with CDD V6.1-03 (not CDD V5.3) >-
--------------------------------------------------------------------------------
    RE: .1
    
>As they upgraded COBOL too, why don't they ask DEC if there is a problem with
>COBOL.

    The problem appears to be unrelated to DEC COBOL version.  It seems to
    show up with CDD V6.1-03 (I don't know about higher versions).  We've
    had no reports of this problem with CDD V5.3 used with any version of
    DEC COBOL.
    
>Note 1081.0         cobol-e-numlong with large initial value           4 replies
>VMS V6.2 AXP
>CDD V6.1-03 and V7.0
>COBOL V2.4-863
    
>Note 1081.2         cobol-e-numlong with large initial value              2 of 4
>    CDD 6.1-03 and COBOL 2.2-674.

>>- May I please have the *.LIS file  (MUNICH::SBECKER)
>>Thank you a lot for  answering my questions !
>>Sigi Becker, DSC Munich

           <<< CLT::DISK$CLT_LIBRARY3:[NOTES$LIBRARY]COBOL.NOTE;1 >>>
                               -< VAX/DEC COBOL >-
================================================================================
Note 3229.5  NUMLONG error with COBOL/CDD on AXP using huge init. value  5 of 16
PACKED::BRAFFITT                                     68 lines  17-APR-1997 09:16
                       -< TEST.LIS with DEC COBOL V2.4 >-
--------------------------------------------------------------------------------
                                Source Listing                  17-APR-1997 09:15:21  DEC COBOL V2.4-863                Page 1      
                                Source Listing                  17-APR-1997 09:15:19  COB$USER2:[BRAFFITT.WORK]TEST.COB;1  

	      1  
	      2 *------------------------------------------------------- 
	      3 IDENTIFICATION DIVISION. 
	      4 PROGRAM-ID. TESTPROG INITIAL. 
	      5 DATA DIVISION. 
	      6 WORKING-STORAGE SECTION. 
	      7  
	      8 COPY 'test_rec'     FROM DICTIONARY. 
L	      9 *
L	     10 * _CDD$TOP.TEST_REC
L	     11 *
L	     12 01  TEST_REC.
L	     13     02  BIGFIELD_Q          PIC S9(11)V9(2) COMP VALUE IS 10000000000.
	     14  
	     15 END PROGRAM TESTPROG. 
	     16 *------------------------------------------------------- 

TESTPROG                        Source Listing                  17-APR-1997 09:15:21  DEC COBOL V2.4-863                Page 2      
0                               Program Section Summary         17-APR-1997 09:15:19  COB$USER2:[BRAFFITT.WORK]TEST.COB;1  

DIAGNOSTICS SUMMARY

       Informationals       4 (suppressed)
       ----------------------
       Total                4

TESTPROG                        Source Listing                  17-APR-1997 09:15:21  DEC COBOL V2.4-863                Page 3      
0                               Compilation Summary             17-APR-1997 09:15:19  COB$USER2:[BRAFFITT.WORK]TEST.COB;1  

COMMAND QUALIFIERS

   COBOL 

      /NOALIGNMENT                                                   /GRANULARITY = QUAD                                         
      /NOANALYSIS_DATA                                               /LIST                                                       
      /NOANSI_FORMAT                                                 /NOMACHINE_CODE                                             
      /NOAUDIT                                                       /NOMAP                                                      
      /CHECK = (NOPERFORM, NOBOUNDS, NODECIMAL, NODUPLICATE_KEYS)    /NATIONALITY = US                                           
      /NOCONDITIONALS                                                /NOOBJECT                                                   
      /NOCONVERT = LEADING_BLANKS                                    /OPTIMIZE = LEVEL=4                                         
      /COPY_LIST                                                     /RESERVED_WORDS = (NOXOPEN, NOFOREIGN_EXTENSIONS)           
      /NOCROSS_REFERENCE                                             /NOSEPARATE_COMPILATION                                     
      /DEBUG = (NOSYMBOLS, TRACEBACK)                                /NOSEQUENCE_CHECK                                           
      /NODEPENDENCY_DATA                                             /STANDARD = (NOXOPEN, NOSYNTAX, NOV3, 85, NOMIA)            
      /NODIAGNOSTICS                                                 /NOTIE                                                      
      /NOFIPS                                                        /NOTRUNCATE                                                 
      /NOFLAGGER                                                     /VFC                                                        
      /FLOAT = D_FLOAT                                               /WARNINGS = (NOINFORMATION, OTHER)                          

COMPILATION STATISTICS

  CPU time:          0.66 seconds
  Elapsed time:      5.49 seconds
  Pagefaults:         827
  I/O Count:          228
  Source lines:        16

  1454 lines per CPU minute.

- Don Braffitt
  DEC/VAX COBOL project leader