MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » March 2014

Re: SQLCOD 12



fixed

Billy

You should have a message in your job log that corresponds to SQLCOD 12 - SQL0012. If it's not in the log, you can do this -

dspmsgd sql0012 qsqlmsg

Now positive SQLCOD is not necessarily an error - negative almost definitely is.

If this is positive, here is the message -

Correlation without qualification occurred for column &1 to table &2.

This won't stop the processing - I bet if you check the log of the job the the stored procedure uses, you will see the same message.

Your SQLCOD test should be for SQLCOD < 0, not <> 0, seems to me.

Positive SQLCOD is very often a warning - you might get the value of SQLWRN - I think that's the variable. Look into the docs for more info.

HTH
Vern

On 3/29/2014 8:27 AM, Billy Waters wrote:
RPG Code
Exec SQL
update LIb/file1 set var =
(select var1 from lib/file2
where field1 = field2)
where exists(select * Lib/file2 where field1=field2);

RSTNG = 'UPDATE STATUS: ' + SQLSTATE;
Write R001;
If SQLCOD <> 0;
*INU1 = *on;
EndIf;

Take necessary actions in CL if INU1 is off or on.

If I call from command line:
UPDATE STATUS: 00000 (SQLSTAT)
Zero Records: 0
Off (State of INU1) check doe SQLCOD <> 0

If I start from MSSQL stored procedure
UPDATE STATUS: 01545
Zero Records: 0
on
update is successful

Different user ids when calling from command line vs from MSSQL.
Please help..







Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact