Re: SQL Stored Procedure ROW_COUNT

Set deleted rows = select NUMBER_DELETED_ROWS
from QSYS2.SYSTABLESTAT;

one of the columns is NUMBER_DELETED_ROWS.

Craft your WHERE clause to specify TABLE_SCHEMA and TABLE_NAME.

It should work just fine wherever you run it as it is just a read of a
dataset

Steve Needles


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
dlclark@xxxxxxxxxxxxxxxx
Sent: Tuesday, May 17, 2016 8:58 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: SQL Stored Procedure ROW_COUNT

"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 05/16/2016
10:42:54 PM:

if you were at COMMON, you could have gotten the answer during Ted
Holt's presentation today.

SQLERRD(3) For INSERT, MERGE, UPDATE, REFRESH, and DELETE, shows the
number of rows affected.

I'm already familiar with SQLERRD(3) for embedded SQL and, in
point of fact, I have used ROW_COUNT in embedded SQL and it works just
fine. What I'm looking for is not embedded SQL but the equivalent of TSQL
for the IBM i. Are you saying that you know how to get to SQLERRD(3) from
inside a "native" SQL stored procedure (a.k.a., TSQL in the MS Server
world)? Please instruct me, thanks.

Sincerely,

Dave Clark
int.ext: 91078
direct: (937) 531-6378
home: (937) 751-3300

Winsupply Group Services
3110 Kettering Boulevard
Dayton, Ohio 45439 USA
(937) 294-5331





*********************************************************************************************
This email message and any attachments is for use only by the named
addressee(s) and may contain confidential, privileged and/or proprietary
information. If you have received this message in error, please immediately
notify the sender and delete and destroy the message and all copies. All
unauthorized direct or indirect use or disclosure of this message is
strictly prohibited. No right to confidentiality or privilege is waived or
lost by any error in transmission.

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

Please contact support@xxxxxxxxxxxx for any subscription related
questions.
________________________________
This communication, including attachments, is confidential, may be subject
to legal privileges, and is intended for the sole use of the addressee. Any
use, duplication, disclosure or dissemination of this communication, other
than by the addressee, is prohibited. If you have received this
communication in error, please notify the sender immediately and delete or
destroy this communication and all copies.

TRVDiscDefault::1201
--
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.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.