Re: diff between cobol1 & cobol3

On Sat, 8 Dec 2007 07:14:23 -0800 (PST), Alistair <alistair@xxxxxxxxxxxxxxxxxxxxx> wrote:

Be advised that Cobol for MVS does stupid things like changing the
date formats (which might be over-ridable with compiler directives but
wasn't where I worked for the year 2000 project).

Except intrinsic functions and ACCEPT .. FROM DATE, Cobol did not have a date format until
IBM introduced the DATE FORMAT clause in the late '90s. IBM did not change intrinsic
functions nor ACCEPT except to add an 02-style YYYYMMDD option.

What are you referring to?
.

Relevant Pages

  • Re: gfortran and initialization expressions
    ... A format is a default-char-expr, label, or asterick. ... I had also gone through many intrinsic functions that gfortran ... some Fortran 2003 and 2008 extensions and of course bugs. ... function he tried and failed to report to the proper support ...
    (comp.lang.fortran)
  • Re: C vs. fortran
    ... >whole lot more in terms of string handling and formatted I/O ... The intrinsic functions of C, for a long time, ... and exp have been available in both single double precision in Fortran ... because you can build a format string and don't need to use the format ...
    (sci.crypt)
  • Re: diff between cobol1 & cobol3
    ... Except intrinsic functions and ACCEPT .. ... IBM introduced the DATE FORMAT clause in the late '90s. ... to WMK. ...
    (comp.lang.cobol)
  • Re: diff between cobol1 & cobol3
    ... Except intrinsic functions and ACCEPT .. ... IBM introduced the DATE FORMAT clause in the late '90s. ... Unfortunately I can not recall which format the date came in in. ...
    (comp.lang.cobol)
  • Re: Recordset based on a SQL string gives Too few parameters error -- Access97
    ... I used the following date format: ... >> Dim rs As DAO.Recordset ... >> This seems to be referring to the three fields specified in the WHERE ... >> Leonard Priestley ...
    (microsoft.public.access.formscoding)