RSQIWKEX job not processing queues

[Former Member]

Dear all,

There is a background job running in both ECC and SCM to pickup any objects and resend them. The program name is RSQIWKEX. Currently the background job is scheduled to run every 10 minutes. The job is not picking up the objects and processing them. The run time of the background job displays a duration of 0 seconds. Yet we continue to receive email notifications of blocked queues.

Frequency of job is

RSQIWKEX Runs Every 10 mins

SAPAPO/RCIFINQUEUECHECK Runs Every 15 mins

Please let us know what is the exact way of configuring these jobs so that they pick up and process

failed queue objects and reprocess them.

Note : We have refered notes 813029 and 864333 , 369007

Regards,

RR

[MichalKrawczyk · Accepted solution]

hi,

1. you know what RSQIWKEX works only with inbound queues?

(those you see in SMQ2)

b) for entries with SMQ1 you need to use report RSQOWKEX

c) for entries with SM58 use RSARFCEX

Regards,

Michal Krawczyk

[Former Member · Accepted solution]

Thanks for quick answers.

Prateek,

We have SCM system and not PI / XI system , as per note 813029 we need to set

parameter QRFC_RESTART_ALLOWED only when have XI environment.

Correct me if i am wrong ,... do i need to set this parameter in SCM system for inbound blobked queue

collection and reprocessing. ... Please let me know.

Also appreciate if you could provide any note which explains setting of this parameter QRFC_RESTART_ALLOWED as necessary thing for RSQIWKEX to function properly ??

What does this setting do ? and why job RSQIWKEX cannot process queues correctly without maintaining QRFC_RESTART_ALLOWED .

Regards,

RR

[Former Member · Accepted solution]

Dear Experts,

Please let me know your opinion on my questions ?

Thanks in advance.

Regards,

RR

[Former Member · Accepted solution]

QRFC_RESTART_ALLOWED paramter is needed for restarting of messages blcoked

but if you are able to clear the blocked queue no need of this parameter as everything will be cleared automatically,IN case if you need explicit retransfer the above parameter is needed

Rajesh

[Former Member · Accepted solution]

Dear all,

Thanks. Please let me know whether i can maintain parameter

QRFC_RESTART_ALLOWED = 1 and as well as keep job RSQIWKEX scheduledstate on every 20 Mins. in my SCM system for inbound queues which are currently getting stucked ?

Can this be done. Would there be any adverse effects to be considered in advance.

Note:

Currently i can see 2 queues stucked in my SCM system in transaction SMQ1

with status SYSFAIL

Correct me if i am wrong ... do i need to execute some other job for outbound queues ?

also does parameter setting require in this case ?

Regards,

RR

Edited by: ganesh rr on May 7, 2009 11:30 AM

Edited by: ganesh rr on May 7, 2009 1:58 PM

[Former Member · Accepted solution]

Dear experts ,

I executed job RSQOWKEX in SCM system and found queue is getting into READY state ...

but again after few secomnds resulted into SYSFAIL status.

I also observe dump DYNPRO_SEND_IN_BACKGROUND in target ECC system.

Does job RSQOWKEX or RSQIWKEX support queues with status SYSFAIL. ????

Regards,

RR

[Former Member · Accepted solution]

Dear Experts ,

Appreciate if anybody could provide answers to my queries.

Thanks in advance.

Regards,

RR

Edited by: ganesh rr on May 11, 2009 12:27 PM

[Former Member · Accepted solution]

Hi Ganesh,

please check in the queues whether the problem can be solved by restarting the queue. Sometimes it says then "QRFC restart not allowed" or something similar. In that case you need to restart the message, not the queue. Program RSXMB_RESTART_MESSAGES does that job, but you could restart manually as well. You should have both jobs scheduled anyway.

Regards,

Jörg

[prateek]

Have you set the Monitoring parameter in sxmb_adm -> integration engine configuration -> QRFC_RESTART_ALLOWED value to 1?

Regards,

Prateek