Issues for COBOL Revision Task Force

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 5640: anomaly in that unsigned integers are mapped to signed integers
Issue 5857: COBOL Language Mapping Section: 1.2.1.2

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

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

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

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

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?

"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.