Help with After condition and looking for the most recent Fiserv DNA Queue

[Kellie Brown]

I'm looking for help with this scenario because it is not picking up the most recent report queue from history.  

Report A runs 3 times / day.  9a, noon and 3p

When I run this sql (set up as a sub var) it shows the exact queue I am expecting at 9a, noon and 3p at 9a noon and 3p.

select max(so_ref1) from so_job_history where so_module in ( 'AH_PENDING_5137') and (so_job_finished) >= sysdate -(12/24)

If I add an After Condition to extract data from the report, using the same sql as above to locate the queue of the job, it resolves the queue from the previous run report not the most recent.  example - run job at noon, the After condition locates the 9a queue number not the noon queue number.  

With that, I created a dummy job to run the After condition, and let it run 100 sec after AH_PENDNG and it still finds the 9a queue not the noon queue.  

Is there something I am missing or could change?  Thanks in advance.  

[Phearith Mao]

What are the possible values that is returned as you are doing a "max(so_ref1)"?

I assume if so_ref1 is return numbers, you would get the highest number, but there is mention of Queue so I am a bit confused.

Also if you enable RmiServer debug, while the condition is being resolved during a Job run, the RmiServer<timestamp>.log will show the full sql and the sql results as well. Just search the log for part of the sql string and you should be able to find it. Results will be somewhere below in another line depending on how busy the system was at condition evaluation time.

You can also take the same sql and run it via sqlplus and see what you get back as it should be the same value as when AM is resolving it.

[Phearith Mao]

Taking a look at another post, it looks like you may have resolved the issue already so please ignore my post =)

[Kellie Brown]

Hi Phearith,

Thank you for looking at this.  Believe it or not it still doesn't work even with the change I made a while back (but I never had the time to invest looking further).  I just looked at the log from the 2 runs of the same job, 2 hours apart, and the sql pulls the correct queue number but the log at the time the 2nd run ran, shows the 1st queue number not the 2nd.  I changed the sql from using the History queue to using SELECT TO_CHAR (MAX(QUENBR)) FROM QUE WHERE QUEDESC = ' job name'.  I really think something is not right with the Extract Value Condition.  If I get the time this week or next, I'll dive back into this.  We are testing 9.5.3 so maybe it changed with that version.  I'll test it and send an update.  Thank you -