Re: Using opdesc ... getting CEE0502

Hi, David:

Why not just pass one more parameter to your "procname" procedure, with the size of that other parameter (in this case, a data structure)? The caller can use %size(yourDS) to fill in the value of that parameter. This approach seems far simpler, and less expensive (from a resource usage point of view, at runtime), than using the IBM compiler "opdesc" feature, and then having to use the CEEDOD API at runtime to interrogate the operational descriptors, etc.

There is some "overhead" when using operational descriptors ... Sure, it is easy to code "opdesc" on the PI or PR spec, but, consider what this actually means -- for every CALL to that procedure, the compiler generated code must build the operational descriptors in memory for each of the parameters, and pass a pointer to those "operational descriptors", along with the parameters themselves, to the called procedure. And, there is also overhead for calling CEEDOD to retrieve or interrogate those "operational descriptors" and retrieve the results from that API.
I can understand using CEEDOD with some APIs or "exit points" of some other vendor product, over which you have no control, and when the source code might not even be provided or available. But, to use it within your own code, or as a part of product(s) you are supporting and maintaining or enhancing, I am not sure this is really such a "good idea"... _unless_ you are creating "APIs" that your customers will be calling?

All the best,

Mark


> David Gibbs wrote:

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