Given that the program that's crashing doesn't actually use the MULTDS
it is passed, but merely passes it, if available, to a customized
UNDEL2, and given that everything in an OPM program call is passed by
reference, I tried this:
I changed the optional parameter to a simple 1-character field.
Now, if the MULTDS is received (in the 1-character field), it is passed
on to the custom UNDEL2. If it isn't, it isn't. And it looks like the
custom UNDEL2 is getting the whole MULTDS.
*************
*BUT I'M WORRIED.* This MULTDS can potentially have 9999 occurrences of
186 bytes each. Could there be side effects of passing a reference as if
it were only one byte?
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
