Re: Delay job from RPGLE

Hi Chuck -

On Fri, 12 Jul 2013 10:30:32 -0700, CRPence <CRPbottle@xxxxxxxxx>
wrote:

Ah. Perhaps I recalled incorrectly, and it was that concern expressed
instead. But my additional\snipped comments still stand, that the
concern for the "Function" displayed by WRKACTJOB can be /resolved/ by
use of the Change Current Job (QWCCCJOB) API, to better identify why the
job is in DLYW and possibly even what specific type of delay is in
effect [as best can be accomplished in the 10-bytes provided].

I do use that API to change the function, but not for delay waits.

I use it where the processing passes through a security structure
which masks setting the function to the underlying command or program
being run. So I use the API to change the function to that of the
underlying command or program.

In another case I use the API to set the function to the program name
plus a dash plus the first parameter on the program call. The program
name is only six characters and the first parameter is only one
character so it's short enough to fit.

Ken
Opinions expressed are my own and do not necessarily represent the views
of my employer or anyone in their right mind.