Problems with CEE date APIs

[bmorris@xxxxxxxxxx]

>Date: Tue, 4 Jul 2000 14:42:07 +0100
>From: "Alan Moulsdale" <alan.moulsdale@virgin.net>
> ...
> My problem is that the CEEDAYS API will only work if I place a DSPLY
>directly after it! This is obviously not desirable.
> ...

Alan, you need the third (fc) parameter for CEEDWK.  The call to CEEDAYS
is working fine, but when you leave off the third parameter to CEEDWK,
CEEDWK still looks for the third parameter.  What it finds is the pointer
to LilDate, which was passed as the third parameter to CEEDAYS.  It must
be updating the feedback parameter before it does the calculation, so
it messes up your LilDate variable.

Doing a DSPLY between the calls changes the program stack.  If CEEDWK finds
a null pointer, all will be fine.  If it finds one of the pointers used to
do DSPLY, something, who knows what, will get corrupted.

The documentation for CEEDWK says the third parameter is omissible.  That
means you can pass *OMIT for it, but you still have to pass something.  All
the CEE APIs require you to pass all the parameters.

Barbara Morris


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---