example-zowe.yaml in SZWESAMP

[Martin-Zeithaml]

Idea: provide the same content of example-zowe.yaml as SZWESAMP member, which means to fit into 80 chars per line (record).

Ideally to have automation and making new updates only to example-zowe.yaml or some template, which can be used for generating "long" and 80 chars lines.

As seen, some customers are used to do the most of their work in 3270 terminal/ISPF. And with the support of different parmlib names, all configuration members could be stored in one parmlib dataset, which is convenience for editing.

At this point, it is not possible to copy example-zowe.yaml to dataset (RECL=80) due to the record length.

[1000TurquoisePogs]

Although people can just copy unix files into datasets and use datasets and terminals that are wider than 80 characters, it's also not too much to ask to duplicate this file as a dataset, and refactor the comments to be less than 80 characters. Having a github workflow that just checks that new PRs dont go beyond the 80 character limit could be enough to keep it working over time.

There currently are no code lines in the yaml that are over 80 characters, but upon people trying to use a yaml in a dataset they may find they quickly run out of space for paths.