waiting recovery

We put together a process flow that reads the queue for anything needing recovery / invalid parameters and emails the admin as well as the job submitter. Runs every 15 minutes.

Thanks Randy. I will save this so when we do get process flow.

There are several other options.. cygwin on windows, or if you are unix....
https://www.lawsonguru.co...eId/500/default.aspx

H bernfc10 - We built a unix script that calls "jqstatus -hr" every 30 minutes and sends email to a distribution list if it finds any "new" jobs that are in Needs Recovery. It's not pretty, but it gets the job done.

Kelly

We monitor our queue every 15 minutes as well...

However, although we have IPA (Process Flow), we do this through a scheduled windows batch job that calls a SQL query. When a stalled or failed job is found, we only send an email to the sys admins. Other than that, depending on the type of job needing recovery, we may also send another to certain department heads, but we don't send it directly to the submitter of the job(s).

Our organization does not have global email so, unless there is a way (in IPA) to evaluate whether or not the submitter actually has email, it makes notification to the actual submitter a little tricky. I'd be interested in the specifics of notifying the actual submitter, but am not sure if we'd be able to evaluate GroupWise to ensure they actually have an email account. Does anyone have any info on whether or not this evaluation could be accomplished using IPA?

Thanks in advance.