RE: SQLCOD 12

Thanks, lessons learned:
1. check for SQLCOD < 0
2. Using Correlation Identifiers for the files/fields results =
SQLCOD 0 SQLSTATE 0000
no matter where the process is initiated.

Thanks for all the help!!

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Billy Waters
Sent: Saturday, March 29, 2014 9:27 AM
To: midrange-l@xxxxxxxxxxxx
Subject: SQLCOD 12

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..

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.