Re: Operational Descriptors

[Scott Klement <klemscot@xxxxxxxxxxxx>]

I've had that problem in every program that I've used OPDESC in.
Sometimes, the procedures have run (from the same place!) for over
a year without problems, but eventually it'll reach a point where
the program will crash with "missing operational descriptor".

I don't ever use OPDESC anymore.  It's much safer to pass a seperate
parameter with the length, or to use VARYING, instead of OPDESC.

I don't have much good to say about OPDESC.


On Sat, 11 Jan 2003, Bob Cozzi wrote:
>
> I'm using the OPDESC keyword on a procedure.
> The 3rd parameter of that procedure is defined as follows (well
> actually, here's the entire proc interface):
>
>      D GetNextEntry    PI            10I 0 OPDESC
>      D  szUserSpace                  20A   Const
>      D  nRefPos                      10I 0
>      D  szEntry                    4096A   OPTIONS(*VARSIZE)
>
> Upon entering the procedure, I call CEEDOD, or CEEGSI.
> I do that to extract the length of parameter 3.
>
> Upon calling either of these APIs, I get a "CEE0502 Missing operational
> descriptor" message.
>
> Now here's the strange part:
> If I call this procedure from within another procedure, I don't get the
> error and the APIs work fine. But if I call the exact same procedure
> from the mainline calcs in a program, I get the above mentioned error.
>
> Is this a bug, has anyone else come across this?