[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [open-cobol-list] Bug Report
From: |
Bill Klein |
Subject: |
RE: [open-cobol-list] Bug Report |
Date: |
Mon Oct 10 21:42:06 2005 |
I am still confused about this (and doing some research). I do see,
however, the
following in the output you provided:
> END OF COMPILATION 1, PROGRAM FFWER100, HIGHEST SEVERITY 4.
>
> 0RETURN CODE 4
>
> A return code of 4 means only warnings, no errors.
but I don't see a W-level message in what you provided. (I also noticed
that this compile with with IBM COBOL for OS/390 V2 - while the other one
was with Enterprise COBOL V3. I assume you get the same results with both.
> -----Original Message-----
> From: address@hidden
> [mailto:address@hidden On
> Behalf Of Robert Sherry
> Sent: Monday, October 10, 2005 9:59 AM
> To: 'Bill Klein'; 'John R. Culleton';
> address@hidden
> Cc: 'Roger While'
> Subject: RE: [open-cobol-list] Bug Report
>
>
> Here is part of a compiler listing of a COBOL program that has
> DATE-MODIFIED in it:
>
>
> Compiler Options Used:
>
> NOADATA
>
> NOADV
>
> NOANALYZE
>
> APOST
>
> ARITH(COMPAT)
>
> AWO
>
> BUFSIZE(32760)
>
> NOCICS
>
> NOCMPR2
>
> NOCOMPILE(E)
>
> NOCURRENCY
>
> DATA(31)
>
> NODATEPROC
>
> NODBCS
>
> NODECK
>
> NODIAGTRUNC
>
> NODLL
>
> NODUMP
>
> ,LINE,00000168
>
> NODYNAM
>
> NOEXIT
>
> NOEXPORTALL
>
> FASTSRT
>
> FLAG(W,E)
>
> NOFLAGMIG
>
> NOFLAGSTD
>
> NOIDLGEN
>
> INTDATE(LILIAN)
>
> LANGUAGE(UE)
>
> LIB
>
> LINECOUNT(57)
>
> NOLIST
>
> MAP
>
> NONAME
>
> NONUMBER
>
> NUMPROC(NOPFD)
>
> OBJECT
>
> OFFSET
>
> OPTIMIZE(FULL)
>
> OUTDD(SYSOUT)
>
> PGMNAME(COMPAT)
>
> RENT
>
> RMODE(AUTO)
>
> SEQUENCE
>
> SIZE(MAX)
>
> SOURCE
>
> SPACE(1)
>
> NOSQL
>
> NOSSRANGE
>
> P 5648-A25 IBM COBOL FOR OS/390 & VM 2.2.2
>
> NOTERM
>
> NOTEST
>
> TRUNC(BIN)
>
> NOTYPECHK
>
> NOVBREF
>
> NOWORD
>
> XREF(FULL)
>
> OPTIMIZE(FULL)
>
> OUTDD(SYSOUT)
>
> PGMNAME(COMPAT)
>
> RENT
>
> RMODE(AUTO)
>
> SEQUENCE
>
> SIZE(MAX)
>
> SOURCE
>
> SPACE(1)
>
> NOSQL
>
> NOSSRANGE
>
> P 5648-A25 IBM COBOL FOR OS/390 & VM 2.2.2
>
> NOTERM
>
> NOTEST
>
> TRUNC(BIN)
>
> NOTYPECHK
>
> NOVBREF
>
> NOWORD
>
> XREF(FULL)
>
> ,LINE,00
>
> YEARWINDOW(1900)
>
> ZWB
>
> PP 5648-A25 IBM COBOL FOR OS/390 & VM 2.2.2
>
>
>
> ********* ELIPS BROWSE:
> CMCCOS.FIELD.UB0000.LISTSRCE(FFWER100) 03/04/30
> 00:00:0
>
> COMMAND ===>, ,SCROLL
> ===>,CSR ,
>
>
> ,LINE,00000209,COL,001
> 080,
>
> LINEID PL SL
> ----+-*A-1-B--+----2----+----3----+----4----+----5----+----6--
>
> 000001 IDENTIFICATION DIVISION.
>
> 000002 PROGRAM-ID. FFWER100.
>
> 000003 AUTHOR. MARK LIPS.
>
> 000004 DATE-WRITTEN. NOV 07, 2002.
>
> 000005 DATE-MODIFIED. NOV 21, 2002.
>
> 000006 DATE-COMPILED. 04/30/03.
>
> 000007
>
> 000008
> ********************************************************
>
> 000009 * MODULE: FFWER100 (INSERT TO
> FFDWA00P - ERROR
> DA
>
> 000010
> ********************************************************
>
> 000011 * MODIFICATION HISTORY
>
> 000012 * --------------------
>
> 000013 *
>
> 000014 *
>
> 000015
> ********************************************************
>
> 000016
>
> 000017 ENVIRONMENT DIVISION.
>
> 000018 CONFIGURATION SECTION.
>
> -* STATISTICS FOR COBOL PROGRAM FFWER100:
>
> * SOURCE RECORDS = 519
>
> * DATA DIVISION STATEMENTS = 129
>
> * PROCEDURE DIVISION STATEMENTS = 131
>
>
>
> Results of Compilation:
>
> 0
> END OF COMPILATION 1, PROGRAM FFWER100, HIGHEST SEVERITY 4.
>
> 0RETURN CODE 4
>
> A return code of 4 means only warnings, no errors.
>
> Bob Sherry
>
>
>
>
> -----Original Message-----
> From: address@hidden
> [mailto:address@hidden On
> Behalf Of Bill Klein
> Sent: Thursday, October 06, 2005 4:39 PM
> To: 'Robert Sherry'; 'John R. Culleton';
> address@hidden
> Cc: 'Roger While'
> Subject: RE: [open-cobol-list] Bug Report
>
> correction (maybe). I just checked the latest manual. At:
>
> http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/igy
> 3lr30/3.1.6
>
>
> it says that the continuation of a comment-entry must be in
> the B-margin.
>
> THEREFORE, I would like to see a "clean compile" with
> DATE-MODIFIED in the
> A-margin - before committing to whether this should or should NOT be
> allowed. (If coded in the B-margin, it certainly WOULD be allowed.)
>
> > -----Original Message-----
> > From: address@hidden
> > [mailto:address@hidden On
> > Behalf Of Bill Klein
> > Sent: Thursday, October 06, 2005 3:33 PM
> > To: 'Robert Sherry'; 'John R. Culleton';
> > address@hidden
> > Cc: 'Roger While'
> > Subject: RE: [open-cobol-list] Bug Report
> >
> > The answer to this one is actually pretty funny (and it
> > really IS a bug).
> >
> > DATE-MODIFIED is *not* a valid paragraph name for any IBM (or
> > other compiler
> > that I know of).
> >
> > HOWEVER, (and here comes the funny part). IBM (and several
> > other compilers)
> > allow for a "comment-entry" to be in either the A-margin or
> > B-Margin. (The
> > '85 Standard isn't clear to me as to whether this is an
> > extension or not.)
> >
> > Therefore, given the construct:
> >
> > AUTHOR. MRK S.
> > DATE-WRITTEN. NOV 07, 2002.
> > DATE-MODIFIED. NOV 21, 2002.
> >
> > the "DATE-MODIFIED. ..." text is (on IBM and several other
> compilers)
> > treated as a "comment-entry" portion of the (valid and conforming)
> > DATE-WRITTEN. paragraph. You could just as well have coded:
> >
> > AUTHOR. MRK S.
> > DATE-WRITTEN. NOV 07, 2002.
> > Now-is-the-time. For all good men to come to the aid
> > of their party>
> >
> > and it would compile. For documentation on continuation of
> > comment-entries,
> > see the '85 Standard, page VI-6, SR(1).
> >
> > P.S. A common use of this "feature" is IBM code like the following:
> >
> > AUTHOR. MRK S.
> > REMARKS. OS/VS COBOL allowed for a REMARKS paragraph but
> > VS COBOL II and later do not. However, this
> > works because
> > it is actually a part of the AUTHOR paragraph.
> >
> >
> > > -----Original Message-----
> > > From: address@hidden
> > > [mailto:address@hidden On
> > > Behalf Of Robert Sherry
> > > Sent: Thursday, October 06, 2005 2:16 PM
> > > To: 'John R. Culleton'; address@hidden
> > > Cc: 'Roger While'
> > > Subject: RE: [open-cobol-list] Bug Report
> > >
> > > John,
> > >
> > > You are right. I meant to say: DATE-MODIFIED. Sorry. In
> > > any event, I
> > > believe it should work in MVS compatible mode. Do you
> > > disagree with that?
> > >
> > > Bob Sherry
> > >
> > > -----Original Message-----
> > > From: address@hidden
> > > [mailto:address@hidden On
> > > Behalf Of John R.
> > > Culleton
> > > Sent: Thursday, October 06, 2005 2:46 PM
> > > To: address@hidden
> > > Cc: Robert Sherry; 'Roger While'
> > > Subject: Re: [open-cobol-list] Bug Report
> > >
> > > On Thursday 06 October 2005 06:34 pm, Robert Sherry wrote:
> > > > John,
> > > >
> > > > While DATE-WRITTEN is not part of standard COBOL it is
> > > part of IBM
> > > MVS
> > > > COBOL. Therefore it should work with std=mvs.conf. By the
> > > way, it use to
> > > > work in Open COBOL.
> > > >
> > > > Bob Sherry
> > >
> > > DATE-MODIFIED IS THE PROBLEM!
> > > --
> > > John Culleton
> > > Books with answers to marketing and publishing questions:
> > > http://wexfordpress.com/tex/shortlist.pdf
> > >
> > > Book coaches, consultants and packagers:
> > > http://wexfordpress.com/tex/packagers.pdf
> > >
> > >
> > >
> > > -------------------------------------------------------
> > > This SF.Net email is sponsored by:
> > > Power Architecture Resource Center: Free content, downloads,
> > > discussions,
> > > and more. http://solutions.newsforge.com/ibmarch.tmpl
> > > _______________________________________________
> > > open-cobol-list mailing list
> > > address@hidden
> > > https://lists.sourceforge.net/lists/listinfo/open-cobol-list
> > >
> > >
> > >
> > > -------------------------------------------------------
> > > This SF.Net email is sponsored by:
> > > Power Architecture Resource Center: Free content, downloads,
> > > discussions,
> > > and more. http://solutions.newsforge.com/ibmarch.tmpl
> > > _______________________________________________
> > > open-cobol-list mailing list
> > > address@hidden
> > > https://lists.sourceforge.net/lists/listinfo/open-cobol-list
> > >
> >
> >
> >
> >
> > -------------------------------------------------------
> > This SF.Net email is sponsored by:
> > Power Architecture Resource Center: Free content, downloads,
> > discussions,
> > and more. http://solutions.newsforge.com/ibmarch.tmpl
> > _______________________________________________
> > open-cobol-list mailing list
> > address@hidden
> > https://lists.sourceforge.net/lists/listinfo/open-cobol-list
> >
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Power Architecture Resource Center: Free content, downloads,
> discussions,
> and more. http://solutions.newsforge.com/ibmarch.tmpl
> _______________________________________________
> open-cobol-list mailing list
> address@hidden
> https://lists.sourceforge.net/lists/listinfo/open-cobol-list
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Power Architecture Resource Center: Free content, downloads,
> discussions,
> and more. http://solutions.newsforge.com/ibmarch.tmpl
> _______________________________________________
> open-cobol-list mailing list
> address@hidden
> https://lists.sourceforge.net/lists/listinfo/open-cobol-list
>
- Re: [open-cobol-list] Bug Report, (continued)
- Re: [open-cobol-list] Bug Report, John R. Culleton, 2005/10/06
- RE: [open-cobol-list] Bug Report, Robert Sherry, 2005/10/06
- Re: [open-cobol-list] Bug Report, John R. Culleton, 2005/10/06
- RE: [open-cobol-list] Bug Report, Robert Sherry, 2005/10/06
- Re: [open-cobol-list] Bug Report, John R. Culleton, 2005/10/06
- RE: [open-cobol-list] Bug Report, Bill Klein, 2005/10/06
- RE: [open-cobol-list] Bug Report, Bill Klein, 2005/10/06
- RE: [open-cobol-list] Bug Report, Robert Sherry, 2005/10/10
- RE: [open-cobol-list] Bug Report, Bill Klein, 2005/10/10
- RE: [open-cobol-list] Bug Report, Robert Sherry, 2005/10/10
- RE: [open-cobol-list] Bug Report,
Bill Klein <=
- RE: [open-cobol-list] Bug Report, Roger While, 2005/10/06
[open-cobol-list] Bug report, Takao Kouji, 2005/10/10
[open-cobol-list] Bug Report, Robert Sherry, 2005/10/26