File event in pending-raised status

[Former Member]

Hi,

I created a file event and when the file arrived in the directory, the event definition stayed in an ambigus status : pending raised.

All incoming files created an event in pending status.

How can an event have both pending and raised status ?

Clement.

[Former Member · Accepted solution]

Hi Clement,

This can be correct, that you see multiple events in the event monitor that are pending (to be) raised. This normally means that the event belonging to the same EventDefinition is still raised, it has to be cleared again before new (file) events are picked up.

You can automatically clear an event using the corresponding check box for this event on the WaitEvents tab of the JobDefinition/JobChain that waits for this particular event.

If you have that checked, then there may be no job submitted to pick up the event. Either you can use auto submit (also on the event on the WaitEvents tab) to have CPS submit jobs automatically as soon as events occur, or you need to submit the job with a submit frame or recurrence, so that it regularly starts waiting for files.

Finally, if you do have the automatic submit as well as the clear flag set, then there may be a reason that CPS cannot submit the job (for instance when it has a required parameter that has no default value). Then there should be operator messages indicating what the problem is.

Regards,

Anton.

[Former Member · Accepted solution]

Hi Anton,

I'm confused, there's no event belonging to the same EventDefinition in status raised.

My Job Chain has a default queue and use auto submit (and clear event when complete), but is not launched as the Event is automatically set to Pending when the file arrived (I got Pending raised in my previous tests).

I clear the pending event, post a new file but went directly to a pending status !

Clement.

[Former Member · Accepted solution]

Hi,

Then there should be operator messages indicating why the chain did not get submitted automatically.

Did you check that already ?

Anton.

[Former Member · Accepted solution]

There's no operator messages. Other files EventDefinition I created in the same way works correctly.

Maybe because this one check an xml file ?

Clement.

[Former Member · Accepted solution]

OK right, I found this operator message :

-

---

"Could not raise Event "ZPO_LHP906".

Details:

JCS-122035: Unable to persist: JCS-111004: Queue QB0_Queue has no ProcessServer with the required JobDefinitionType/Service/Resource for Job 138621 (submitted from Z_INT_MOVE_PO_KSH copy from 2009/09/16 14:51:28,562 Etc/GMT1)) (submitted from Job Definition Z_INT_MOVE_PO_KSH (Copy from 2009/09/16 14:51:28,562 Etc/GMT1)): Job Definition Type KSH/Service PlatformAgentService/null "

-

---

I add the PA on the queue QBO, put this as default queue for Z_INT_MOVE_PO_KSH (step launched within the job Chain waiting the Event), stop/start the PA and the queue but ... still not working : no raised Evnet but incoming file giving an immediate pending status !

Thx for your help

Clement.

[Former Member · Accepted solution]

Hi,

The error message indicates that your script is a script of type KSH, and there is no process server on the queue that offers this job definition type.

You need to look at the process server, with a platform agent service on the system where you want to run this KSH job. This process server should be connected to the queue and it should have KSH listed as one of the Job Definition types.

Anton.

[Former Member · Accepted solution]

Hi,

It works.

For any reason an input parameter (put as Expression in the step) was not passed to the KSH job (=> Mandatory parameter not set: Parameter P_PREF for job 175228 ), I put it in the parameter tab of the Job Chain and reference it in the step. It's ok now.

Notice that I also create another EventDefinition ; the old one still going directly in a Pending status but the monitor is not showing a Raised one. Maybe it is stored somewhere in memory ? Will see when we'll reboot CPS (any idea on that ?).

Thank for your help.

Clement

[Former Member · Accepted solution]

Hi,

That is a different error that probably appeared in the operator messages after you added the correct process server to the queue, right ?

This in fact is the most frequent case when a job cannot automatically be submitted by an event: a mandatory parameter is not filled.

What was the expression you used ? Is it possible that the expression returned NULL ?

You can remove the file event from the old event to stop creating new pending/raised events for that event, you probably do not have any job anymore now that reacts on the old event, so that will be raised now (once) and all subsequent events must wait because the old event is already raised. You can clear all pending events from the "Action" menu on the EventDefinition.

Regards,

Anton.

[Former Member · Accepted solution]

Yes, it appeared after I added the correct process server to the queue.

I disabled the old Event Definition (still going in Pending status).

I close this thread.

Thanks.

Clement.