Re: SQL-Commitment control issue generating enormout amount of jog logs

[Vern Hamberg <vhamberg@xxxxxxxxxxx>]

Åke

We need to know what the rest of the message text is - DSPMSGD doesn't 
give the details - too many substitution variables. What is reason 6? 
And what messages are in the job log ahead of the CPF8361, if any that 
relate to this issue?

I googled for CPF8361 - one spoke of getting errors after upgrading to 
6.1 - maybe due to SQL defaulting to COMMIT *YES - it suggests using the 
SQL SET OPTION statement.

I didn't look farther, but there are some APAR links in the google 
results. Might be worth a look.

HTH
Vern

On 12/29/2011 3:37 AM, Åke Olsson wrote:
> We have an overnight job where we from time to time see an enormous number of job logs. Last night over 91 thousand pages.
>
> Most of this is repeats of the same information and it all happens in the flow between calls to two programs:
>
> The starting point for the issues is a call to non-sql program.
>
> We get a "CPF8361 Cannot place resource under commitment control. Reason code 6"
> Followed by
> SQL0752  Connection cannot be changed
> SQL0900
>
>
> And this continues for another 90785 pages of joblog - same three messages in that sequence.
> The time used by this is just under 3 minutes.
>
> I have checked all SQL programs in the flow  to see if there could be any SQL statements with problems and found none. We do not user journaling or commitment control at all.
>
> Any ideas on where to look?
>
>
> Med vänlig hälsning / Best regards
>
> Åke H Olsson
> [cid:image001.png@01CA1FE6.387A03A0]
> Box 433   SE 551 16  Jönköping   Sweden   visit: Brunnsgatan 11
> phone: +46 (0)36 342976   mobile: +46 (0)705 482976 fax: +46 (0)36 34 29 29
> ake.olsson@xxxxxx<mailto:ake.olsson@xxxxxx>     www.pdb.se