${taskforce.name} Avatar
  1. OMG Task Force

COBOL RTF — All Issues

  • Key: COBOL
  • Issues Count: 6
Open Closed All
All Issues

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

COBOL Language Mapping Section: 1.2.1.2

  • Key: COBOL-2
  • Legacy Issue Number: 5857
  • Status: open  
  • Source: Anonymous
  • Summary:

    "4. If the identifier is greater than 30 characters, then truncate right to 30 characters."

    After this step there might be a hyphen at the end of the identifier. This should be truncated, too.

  • Reported: COBOL 1.0 — Wed, 12 Feb 2003 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

anomaly in that unsigned integers are mapped to signed integers

  • Key: COBOL-1
  • Legacy Issue Number: 5640
  • Status: open  
  • Source: Anonymous
  • Summary:

    While skimming the CORBA->COBOL mapping of IDL constructs, I noticed an
    anomaly in that unsigned integers are mapped to signed integers:

    > IDL Name
    > COBOL Representation Integer Range COBOL Typedef
    >
    > unsigned short
    > PIC S9(05) BINARY 0 to 2^16 CORBA-unsigned-short
    > unsigned long
    > PIC S9(10) BINARY 0 to 2^32 CORBA-unsigned-long
    > unsigned long long
    > PIC S9(18) BINARY 18 numerics CORBA-unsigned-longlong
    > enum
    > PIC S9(10) BINARY CORBA-enum
    >
    > 1.4.1 Basic Integer Types
    >
    > The mapping of long long,
    > and unsigned long long
    > was made to PIC S9(18)
    > and PIC 9(18).

    Presumably the statement of section 1.4.1 is the correct one?

  • Reported: COBOL 1.0 — Tue, 3 Sep 2002 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 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

Mapping of short and long

  • Key: COBOL-3
  • Legacy Issue Number: 19255
  • Status: open  
  • Source: Anonymous
  • Summary:

    The integer ranges given are wrong, correct would be -2^15 to 2^15 -1 and -2^31 to 2^31 -1.
    The COBOL Representation for short should be PIC S9(4) BINARY (which is 2 bytes) and for long PIC S9(10) BINARY (which is 4 bytes).

  • Reported: COBOL 1.0 — Fri, 21 Feb 2014 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT