Re: SQL stored procedure takes longer to run in batch than interactively.

[Bobby Adams <bobby_adams@xxxxxxx>]

We discovered the 'Max Active' setting for QBATCH was too low. We tried 
a few settings before settling on one.  Now the batch job runs much 
quicker.  We understand that when it comes to performance no individual 
setting change exists in a vacuum so we will continue to review the 
different settings and evaluate as we go.

Thank you for all your responses.

Regards,

Bobby

On 5/13/2025 11:45, Bobby Adams wrote:
> Hi All,
>
> We have an SQL stored procedure that deletes records from a table and 
> then inserts records into the table using a view.  The view uses an 
> SQL function that calls an RPG procedure in a service program.  If I 
> run the the stored procedure from a 5250 session interactively, it 
> runs in about 35 minutes.  It should insert just over 7 million 
> records, but after 4 hours of running in batch it had only inserted 
> 3,300 records.  What would account for such a difference in behavior 
> between batch and interactive?
>
> I am using "CALL PGM(DP/UPDCSTCACH)" to run it interactively or submit 
> it to batch.  We are baffled.
>
> Thanks for your help.
>
> Regards,
>
> Bobby Adams