Re: Erratic behavior in trigger program, since unscheduled shutdown lastnight.

I notice that your prototype (and calling) of CEEUTCO is incorrect. You're missing the omissible fc parameter. I would suggest calling the API with all of the parameters that is requires. Just use *omit for fc as you do for the other CEE calls.

Whether this fixes up your problem or not, I have no idea. But the code is wrong as provided.

Bruce
----- Original Message ----- From: "James H. H. Lampert" <jamesl@xxxxxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Thursday, March 19, 2009 2:02 PM
Subject: Erratic behavior in trigger program, since unscheduled shutdown lastnight.

See the thread, "Weird problem with times" on the RPG list, but to
summarize, our power evidently blinked last night, shutting down our
V4R4 development box. Ever since I brought it back up, a trigger program
has been exhibiting erratic behavior: after calling the published RPG
"MailDate" procedure (which calls CEEUTCO, CEELOCT, and CEEDATM), the
very next TIME statement (with a Z-Timestamp field as its result) throws
a CPF1850 exception, and the joblog messages produced appear to have no
connection to where the exception actually happens if I single-step in
the debugger.

--
JHHL
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.