Frosty the Coder
Legendary Poster
List,
Issue:
Continuing the XE to 9.0 upgrade.
In XE a UBE had 11 p/opts. In 9.0, it only has six.
Options 2, 4, 5, 6 and 9 were eliminated.
We have an APPL, that calls an NER to get the values of that UBE's p/opts.
In XE, that NER had a "dow counter < 12" loop.
W/in that loop, UBE name, version ID, and counter are passed to B9090001, "Get processing option data", returning the value.
In 9.0, the APPL failed, throwing an "PO Option ID in version is invalid".
I thought this was caused by the "dow counter < 12" loop, and changed it to "dow counter < 7".
I still get the error.
Thoughts:
I know that data structures and bsvws sequence their columns.
This is why you shouldn't delete or insert columns.
I'm assuming that p/opts work in the same fashion. Is this correct?
If so, would I use a "dow counter < 12" loop but not call B9090001 for those p/opts that were eliminated?
If not, what am I missing, overlooking, and/or not understanding about how this should work?
Please AND Thanks
Issue:
Continuing the XE to 9.0 upgrade.
In XE a UBE had 11 p/opts. In 9.0, it only has six.
Options 2, 4, 5, 6 and 9 were eliminated.
We have an APPL, that calls an NER to get the values of that UBE's p/opts.
In XE, that NER had a "dow counter < 12" loop.
W/in that loop, UBE name, version ID, and counter are passed to B9090001, "Get processing option data", returning the value.
In 9.0, the APPL failed, throwing an "PO Option ID in version is invalid".
I thought this was caused by the "dow counter < 12" loop, and changed it to "dow counter < 7".
I still get the error.
Thoughts:
I know that data structures and bsvws sequence their columns.
This is why you shouldn't delete or insert columns.
I'm assuming that p/opts work in the same fashion. Is this correct?
If so, would I use a "dow counter < 12" loop but not call B9090001 for those p/opts that were eliminated?
If not, what am I missing, overlooking, and/or not understanding about how this should work?
Please AND Thanks