Queues in READY status for no apparent reason

[Former Member]

Dear All,

This question has been posted many times but never saw a conclusive answer on this forum.

To repeat, I see queues being built in READY status in APO inbound for no apparent reason.

All settings of scheduler being fine (SMQS - Type R), there are large number of queues awaiting to be manually unlocked from READY status and they get cleared on unlock. There are no waiting queues but still entries in say an update of a stock queue are like 70+. I am able to clear them manually but that would be stupidity when I am talking of 30K queues build up thus.

Its not that not a single queue is moving. Some are getting processed (RUNNING) on their own but thats at snails speed as compared to the queues in READY.

I have scheduled the report /SAPAPO/RCIFRESTART that seems to have scheuled something in the background but I cant trace that job.

Please help.

Regards,

Loknath

[Former Member · Accepted solution]

Hi

You can execute the /SAPAPO/RCIFRESTART report this is mainly used re-activate interrupted CIF activities.

Amol

[Former Member · Accepted solution]

Thanks Amol,

As mentioned I already executed this report that seems to be released some job is the background that I couldnt trace. Notwithstanding what this did the program didnt do any thing to unlock the queues.

Regards,

Loknath

[Former Member · Accepted solution]

Loknath,

If you have 'many' queues 'RUNNING' for a long period of time, LUWs that are inline behind them will eventually stop trying. You can restart these queues with the /SAPAPO/RCIFRESTART program mentioned above.

There are lots of ways to tune queues to meet business requirements. Speak to your local CIF expert.

Some people use a job to run /SAPAPO/RCIFRESTART on a regular schedule. I have seen a system where this job is scheduled to run hourly.

30K queues is not really reasonable. If you always have this backlog, then there is a performance issue that needs to be addressed (SCM is not able to process the data as fast as ECC is sending). If this is a startup, then you just have to be patient. Initial loads can sometimes take days to fully clear all queues, especially if the SCM is sized a bit on the small side. Continue restarting until you have cleared all queues, then see if they begin to build again.

Best Regards,

DB49

[Former Member]

Hi

Please use the following reports

/SAPAPO/CIFSTOPQUEUES Lock the CIF outbound queues

/SAPAPO/CIFSTARTQUEUES Unlock the CIF outbound queues

RSTRFCI1 Lock the CIF inbound queues

RSTRFCI3 Unlock the CIF inbound queues

Thanks

Amol

[Former Member]

Thanks DB49 and Amol,

As I said I already ran RCIFRESTART but I dont quite note it doing anything. Same is the case with RSTRFCI3..

The situation was fine today and as you said this is a performance issue. We are looking into influencing HEUR job in APO that locks CIF queues by design. Which affects what is still being diagonsed

Regards,

Loknath

[Former Member]

Thanks DB49 and Amol,

As I said I already ran RCIFRESTART but I dont quite note it doing anything. Same is the case with RSTRFCI3..

The situation was fine today and as you said this is a performance issue. We are looking into influencing HEUR job in APO that locks CIF queues by design. Which affects what is still being diagonsed

Regards,

Loknath