COBOL Language Mapping Avatar
  1. OMG Specification

COBOL Language Mapping — Closed Issues

  • Acronym: COBOL
  • Issues Count: 3
  • Description: Issues resolved by a task force and approved by Board
Open Closed All
Issues resolved by a task force and approved by Board

Issues Descriptions

Name scooping inappropriate within some mainframe environments

  • Key: COBOL-6
  • Legacy Issue Number: 602
  • Status: closed  
  • Source: Anonymous
  • 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

  • Reported: COBOL 1.0b1 — Fri, 11 Jul 1997 04:00 GMT
  • Disposition: Resolved — COBOL 1.0
  • Disposition Summary:

    issue resolved, closed

  • Updated: Wed, 11 Mar 2015 01:53 GMT

CORBA sequence IDL type in COBOL

  • Key: COBOL-5
  • Legacy Issue Number: 626
  • Status: closed  
  • Source: Anonymous
  • 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

  • Reported: COBOL 1.0b1 — Wed, 16 Jul 1997 04:00 GMT
  • Disposition: Resolved — COBOL 1.0
  • Disposition Summary:

    resolved, close issue

  • Updated: Fri, 6 Mar 2015 20:58 GMT

COBOL Typedefs NOT universally available

  • Key: COBOL-4
  • Legacy Issue Number: 603
  • Status: closed  
  • Source: Anonymous
  • 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

  • Reported: COBOL 1.0b1 — Fri, 11 Jul 1997 04:00 GMT
  • Disposition: Resolved — COBOL 1.0
  • Disposition Summary:

    resolved, close dissue

  • Updated: Fri, 6 Mar 2015 20:58 GMT