Re: J4 (INCITS aka ANSI COBOL) Committee update

Actually, unlike some, I am ENCOURAGED by this. It seems to me (and I *know*
others will disagree - and some agree) that the current J4 process has totally
lost contact with what can/should be done with COBOL. Work on the '08 Standard
continues (see Chuck's separate note) with (as far as I can tell) ZERO attention
to the fact that there are no implementations of the '02 Standard. Furthermore,
the "quick and tentative" TR process has bogged down (just as the previous
amendment process did) and J4 seems to be spending more time (and resources) on
the XML TR than on the '08 Standard OR interpretations of the '02 Standard.

****

Once upon a time (and long ago) there were two groups:
CCC (CODASYL COBOL Committee) - that created a "futuristic" (not implemented)
JOD
and
X3J4 a "technical committee" that worked with real implementable standards and
its interpretation

When the 2 merged (under the X3J4 - soon after J4) title, the INTENT was to
bring these two closer together - with the thought this would be closer to what
was actually wanted and in use - and to provide "timely" enhancements.

What ended up was an "ivory tower" delayed specification that must be useful for
someone or some organization - but certainly doesn't (to me) seem to have any
relationship to current (or future) COBOL usage.

When (if) INCITS "closes down" J4, it would be my hope (not necessarily
expectation) that COBOL vendors (those remaining) will separately or together
support a programming language meeting the needs of their customers (current and
future).

--
Bill Klein
wmklein <at> ix.netcom.com
"Frank Swarbrick" <Frank.Swarbrick@xxxxxxxxxxxxxx> wrote in message
news:4cbs69F14rcseU2@xxxxxxxxxxxxxxxxx
William M. Klein<wmklein@xxxxxxxxxxxxxxxxx> 05/08/06 8:03 PM >>>
From a recent J4 email distribution:

"The following documents have been posted:
...
06-0030 - Status of Officer Position - Chairman for INCITS/J4, Programming

Language COBOL - Two Calls for Volunteers Closed Without Response (Garner)

Note in 06-0030 that the actions that the INCITS SDB will be forced to
consider
in July if no one volunteers to serve as chairman of J4 before than will
most
likely result in the disbandment of J4."

For those interested in reading 06-0030, see:

http://www.cobolportal.com/j4/files/06-0030.doc

Wow, that certainly is discouraging, though not all that surprising. I'm
guessing you aren't going to volunteer?

Frank


---
Frank Swarbrick
Senior Developer/Analyst - Mainframe Applications
FirstBank Data Corporation - Lakewood, CO USA


.

Relevant Pages

  • Re: Method to force keeping of source
    ... It appears to me that your wish is that the COBOL standard should prevent ... environment for the compiler or in the execution environment. ... > implementor defined is one of the problems as I look at the situation as ...
    (comp.lang.cobol)
  • Re: Program templates as Object Classes
    ... Here's the problem with OO COBOL - it is still very incomplete.. ... realized that OO was incomplete without support ... It's about two years ago a former, retired M/F Manager, (not Bill Klein ... Micro Focus above - but he was referring to the fact that Standard ...
    (comp.lang.cobol)
  • Re: Program templates as Object Classes
    ... There are users of OO COBOL; they are just far fewer than either the vendors ... whether from the same vendor or not. ... disagreed with you that XML should be supported *first* by the OO features ... > being spent by J4 to provide these facilities through a standard that will ...
    (comp.lang.cobol)
  • Re: Program templates as Object Classes
    ... some aspects of OO COBOL have grown and evolved since then. ... Classes from ANY vendor on ANY platform can be "wrapped" (provided the ... 2002 standard implemented. ... I really don't care what J4 or WG4 or SG-1 ...
    (comp.lang.cobol)
  • Re: Program templates as Object Classes
    ... on the ISO Date/Time formats proposal. ... provided *precisely* so that a *single standard* numeric format including ... personal focus is on "core COBOL" and extending what's already there. ... In addition, at the WG4 meeting in October, with the support of J4, I ...
    (comp.lang.cobol)