Re: Data structure changes in QSYSINC?

Sorry if I wasn't clear.

The name changes didn't change the API.  Any code that has already been compiled using the old names still works even though the names are different, because the data is in the same place.  So any existing compiled code should continue to work: object code compatibility.

Now, if you are trying to COMPILE source using the names from the old copy book, but including the new copy book, the you compile will fail: source code incompatibility.

Object incompatibility would have caused a great uproar.  Source incompatibility affects a much smaller market.  That's why as programmers we appreciate it so much, because IBM typically adheres to it even though it's not strictly necessary.



On 4/24/2018 6:00 PM, Vernon Hamberg wrote:

Not sure I'm getting you here, Joe - in this case, the 7.1 version and the 7.2+ versions are different in several subfield names - this would break code that included this copy member - and example is QSQPO08 at 7.1 is QSQPRO at 7.2 - same position, same definition, different names.

I think the name change is the main thing - the data is in the same location for what it is, like Privileges Option, CCSID Option, etc., The name changes will result in "not defined" errors, right?

Bruce would never have done this, maybe someone rewrote his utility that takes the C++ code and converts it to RPGLE.

Elsewhere in this member, B data types are changed to I - but the names stay the same.

Cheers
Vern