Issues for COBOL Revision Task Force

To comment on any of these issues, send email to cobol-rtf@omg.org. (Please include the issue number in the Subject: header, thusly: [Issue ###].) To submit a new issue, send email to issues@omg.org.

List of issues (green=resolved, yellow=pending Board vote, red=unresolved)

List options: All ; Open Issues only; or Closed Issues only

Issue 602: Name scooping inappropriate within some mainframe environments
Issue 603: COBOL Typedefs NOT universally available
Issue 626: CORBA sequence IDL type in COBOL

Issue 602: Name scooping inappropriate within some mainframe environments (cobol-rtf)

Click here for this issue's archive.
Nature: Uncategorized
Severity:
Summary:

Summary: Within some mainframe environments, only the first 8 bytes of a name within a CALL statement are significant. This restriction means that current mapping is not usable within such environments

Resolution: issue resolved, closed
Revised Text:
Actions taken:
July 11, 1997: received issue
February 25, 1999: closed issue

Discussion:

Issue 603: COBOL Typedefs NOT universally available (cobol-rtf)

Click here for this issue's archive.
Nature: Uncategorized
Severity:
Summary:

Summary: COBOL typedefs have not been standardized or are universally available. An easy-to-use alternative to proposed alternative of using COBOL COPY books needs to be found

Resolution: resolved, close dissue
Revised Text:
Actions taken:
July 11, 1997: received issue
February 25, 1999: closed issue

Discussion:

Issue 626: CORBA sequence IDL type in COBOL (cobol-rtf)

Click here for this issue's archive.
Nature: Uncategorized
Severity:
Summary:

Summary: Under the current standard, the sequence accessor functions have no way of knowing how big each element in a sequence is.Add another element to the sequence type describing length of elements

Resolution: resolved, close issue
Revised Text:
Actions taken:
July 16, 1997: received issue
February 25, 1999: closed issue

Discussion: