Re: Using opdesc ... getting CEE0502

I seem to recall I had a similar problem the other day with CEEUTCO.

Originally I had it defined:
D CEEUTCO PR opdesc
D Hours 10I 0
D Minutes 10I 0
D Seconds 8F

and used it like:
CEEUTCO( hours: mins: secs);

I changed it to:

D CEEUTCO PR opdesc
D Hours 10I 0
D Minutes 10I 0
D Seconds 8F
D fc 12A options(*omit)

and used it like:
CEEUTCO( hours: mins: secs : *omit);


Adding the "fc" and then *omit seemed to be the winning combination.

Bryan


On Wed, Mar 24, 2010 at 11:13 AM, David Gibbs <david@xxxxxxxxxxxx> 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

--
IBM i on Power Systems - For when you can't afford to be out of business
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.