-
2
- #1
There are two (working) documents on the J4 (COBOL) web site that I think those interested in "enhancements" to COBOL might be interested in - whether or not their "vendor of choice" appears to be implementing the 2002 ISO COBOL Standard - much less thinking about the (hoped for) 2008 COBOL Standard.
These both represent enhancements to the COBOL language that I can *imagine* that vendors will implement whether or not they are implementing other new (or proposed) features from the '02 (or theoretical '08) ISO Standards. Therefore, I think those interested in COBOL may want to read about them now - and send comments (if any) to J4 sooner than later. If interested, communicate to the J4
chair at:
Don.Schricker <at> microfocus.com
See:
"04-0198- Any-length elementary items"
at:
Summary:
""D.2.7 Any-length elementary items
A truly any-length elementary item of unlimited size can be defined by coding the following picture format:
05 notes PIC X ANY LENGTH.
If the item has a maximum length
, ANY LENGTH LIMIT n is written or, if there is no theoretical maximum length, ANY LENGTH is sufficient.
Any-length items may be national items, or bit items:
05 city-name PIC 1 ANY LENGTH.
05 customer-name PIC N ANY LENGTH.
When a new value is stored in an any-length elementary item, the item's length is automatically adjusted, subject to any maximum length. For example,
MOVE "This product is no longer available" TO notes
..."
****
See:
"04-0197- Dynamic-capacity Tables"
at:
Summary:
"D.2.6 Dynamic-capacity tables
A dynamic-capacity table (or "dynamic table") is a table whose physical size, known as its "capacity", grows dynamically as you add more entries to it. Its maximum capacity is limited only by the resources your implement ation can make available. Its capacity can also be reduced. To improve the description and the planning of memory resources, you can optionally indicate a minimum capacity and an expected capacity. If the expected capacity is reached, you receive a warning in the form of a non-fatal exception but, unless you terminate the process, further entries will continue to be added."
****
Personally, I suggest you start reading the documents from the "Concepts" section and review the (already) resolved issues before communicating any (new) concerns/issues to J4.
Bill Klein
These both represent enhancements to the COBOL language that I can *imagine* that vendors will implement whether or not they are implementing other new (or proposed) features from the '02 (or theoretical '08) ISO Standards. Therefore, I think those interested in COBOL may want to read about them now - and send comments (if any) to J4 sooner than later. If interested, communicate to the J4
chair at:
Don.Schricker <at> microfocus.com
See:
"04-0198- Any-length elementary items"
at:
Summary:
""D.2.7 Any-length elementary items
A truly any-length elementary item of unlimited size can be defined by coding the following picture format:
05 notes PIC X ANY LENGTH.
If the item has a maximum length
, ANY LENGTH LIMIT n is written or, if there is no theoretical maximum length, ANY LENGTH is sufficient.Any-length items may be national items, or bit items:
05 city-name PIC 1 ANY LENGTH.
05 customer-name PIC N ANY LENGTH.
When a new value is stored in an any-length elementary item, the item's length is automatically adjusted, subject to any maximum length. For example,
MOVE "This product is no longer available" TO notes
..."
****
See:
"04-0197- Dynamic-capacity Tables"
at:
Summary:
"D.2.6 Dynamic-capacity tables
A dynamic-capacity table (or "dynamic table") is a table whose physical size, known as its "capacity", grows dynamically as you add more entries to it. Its maximum capacity is limited only by the resources your implement ation can make available. Its capacity can also be reduced. To improve the description and the planning of memory resources, you can optionally indicate a minimum capacity and an expected capacity. If the expected capacity is reached, you receive a warning in the form of a non-fatal exception but, unless you terminate the process, further entries will continue to be added."
****
Personally, I suggest you start reading the documents from the "Concepts" section and review the (already) resolved issues before communicating any (new) concerns/issues to J4.
Bill Klein