× 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.



OK, I'm kind of at wits end here.

I've used operational descriptors before in procedures and never had a problem.

Now, however, it's giving me grief.

My prototype is this:

Dprocname PR opdesc
D pListId like(wd_ListId) const
D pData like(wd_DqPayload) const
D options(*varsize)

My procedure is defined like this:

Pprocname B export
D PI opdesc
D pListId like(wd_ListId) const
D pData like(wd_DqPayload) const
D options(*varsize)

I'm invoking CEEDOD like this:

ibmCEEDOD(2:DescType:DataType:DescInfo1:DescInfo2:InLen:*omit);

But when this call is made, I get a CEE0502 error and it references procedure CEEDOD in the message text.

When the call is made, I am passing in a data structure as the 2nd parm. I want to determine the total length of the structure so I can trim off any excess data in the pData field.

Any thoughts?

Thanks!

david


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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.