I seem to recall seeing this too and I believe that we need an PTF to fix the issue. I would start there to make sure you PTFs are up to date.
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Bryce Martin
Sent: Thursday, July 14, 2011 4:03 PM
To: RPG programming on the IBM i / System i
Subject: MCH3601 being thrown during sql update. SQLCOD gives -901.
I have an SQL statement that has been intermittently throwing a MCH3601.
Sometimes it will throw it, and sometimes it won't even for the same
inputs. There are 2 statements that throw it, 1 more than the other. Its
the strangest thing I've ever seen. All the user sees is a spool file
QSQLSRV which is a User Trace Dump for the interactive job. But sometimes
they get a series of QPSRVDMP spool files with a QPDSPJOB spool file after
them. The QPDSPJOB spool shows the job dump, which is how I tracked it
down to the service program procedure that was causing this.
The table is a global temporary table, if that makes a difference. We
just loaded the latest CUM on 6/26 and the users first reported this to us
on wednesday. We looked back and its been happening since at least last
Friday, could be longer but we don't keep spool files for more than 5 days
or so I think. Here are the two statements...
Exec Sql
Update qtemp/MatDetail
Set Date_Avail = :wrkRequestDate, Qty_Short = :ShortQty
Where Parent_Number = :ChildItem and Child_Number = ''
and Line_Number = :OrderLine;
Exec SQL
Update qtemp/MatDetail
Set Qty_Short = :detQuantity_Short,
Date_Avail = :tmpRdateNum
Where Date_Avail = 0;
I am at V5R5M5. The host variables are populated with values when the
error happens (I put some logging code after the statements and check for
SQLCOD <> 0).
There are other statements that update this table that never have a
problem. In fact... the first statement comes from a program where there
are two statements in a row that both update this table. The first one
will sometimes fall over, but the second one is always ok. Here is that
statement... you can see that the only difference is in the where clause
in that one comparison is a string literal as opposed to a host variable.
Exec SQL
Update qtemp/MatDetail
Set Date_Avail = :wrkRequestDate, Qty_Short = :ShortQty
Where Parent_Number = :ItemNumber and
Child_Number = :ChildItem
and Line_Number = :OrderLine;
I'm at a loss, there doesn't seem to be a rhyme or reason at this point,
and logging the job at *SECLVL gets me nothing more. Anyone have any
ideas?
Thanks
Bryce Martin
Programmer/Analyst I
570-546-4777
--- This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed and may contain information that is non-public, proprietary, privileged, confidential, and exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us and destroy this message immediately. ---
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/rpg400-l.
________________________________
Notice from Bob Evans Farms, Inc: This e-mail message, including any attachments, may contain confidential information that is intended only for the person or entity to which it is addressed. Any unauthorized review, use, disclosure or distribution is strictly prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message and any attachments.
midrange.com
