×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Been a long time since using level-breaks but I believe the original
programmer was trying to condition his/her level-breaks on contingent
record-level criteria (where X is in position Y) but I am not seeing any
conditional indicators on the level-break fields themselves in this case.
Below link is an article about split control field definitions using record
level indicators but IBM's example does not overlay record positions with
more than one field name, as you have in your code. Since your level-break
field names are coming in from a /COPY file then I must also assume that
the GL2x fields are being referenced in several different programs using
only one of the field names in this set. It seems redundant that a
developer would have 5 field names referencing the same location but if you
look at all the programs that use the /COPY file it may shed more light.
Perhaps GL2x may be defined in more than one record format with different
attributes (data type and/or length) and, hence, defined with different
field names here?
Maybe this will help?
https://www.ibm.com/support/knowledgecenter/en/ssw_ibm_i_72/
rzasd/splitctlfld.htm
midrange.com
