Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Explanation about Dynamic-Length Items and UTF-8 Data #215

Merged

Conversation

tanto259
Copy link
Member

Signed-off-by: Hartanto Ario Widjaya tanto259@users.noreply.github.com

This pull request adds two new feature of Enterprise COBOL v6.3 (#212) which are:

The part on UTF-8 data are minimized to prevent an overload of information to the readers, and links to the Knowledge Center is provided for those who like to seek more information.

Contents adapted from the Programming Guide and Language Reference.

These are partly added because the Lab system is using Enterprise COBOL v6.3 and that they can be quite useful to know and learn from. But they are placed on the Advanced Topic since I think they are quite unusual and new.

Signed-off-by: Hartanto Ario Widjaya <tanto259@users.noreply.github.com>
Signed-off-by: Hartanto Ario Widjaya <tanto259@users.noreply.github.com>
# Dynamic-Length Item
So far during this course, we have only explored data items that have a fixed length. In other words, you need to define the length you need for each data type. But in this section, we will explore a fairly new concept in Enterprise COBOL - dynamic-length items.

Enterprise COBOL v6.3 supports dynamic-length items, which are items whose logical length might change at runtime.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As you mentioned in the PR, much of this content is from the Enterprise COBOL for z/OS documentation - https://www.ibm.com/docs/en/cobol-zos/6.3?topic=relationships-dynamic-length-items. Let's credit this source up-front. Additionally, much of this content is identical to that source. We should either quote the source directly or construct this chapter in our own words from what we learned from the source (and still credit it).

Copy link
Member Author

@tanto259 tanto259 Apr 17, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure. Would something like the Professional Manuals section on Course 1 suffice? Since I recall someone said that Course 1 was adapted from the Programming Guide

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like the idea of including something like the Professional Manuals section of Course 1 in Course 2. I still believe that when we adapt content, we should use our own words or directly quote the source.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed. Will re-write the paragraphs on this PR sometimes this week. Additionally, I will also put the Professional Manuals section.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!!

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added to c81c78a. When Course 2 is finalized, might need to shift things around to tidy the placing and formatting of the Professional Manuals section.

Signed-off-by: Hartanto Ario Widjaya <tanto259@users.noreply.github.com>
Signed-off-by: Hartanto Ario Widjaya <tanto259@users.noreply.github.com>
@MikeBauerCA
Copy link
Contributor

@tanto259 thanks for reworking! 👍

@MikeBauerCA MikeBauerCA merged commit f3b14e7 into openmainframeproject:master May 3, 2021
@tanto259 tanto259 deleted the dynamic-with-utf-8 branch May 10, 2021 17:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants