Re: ODBC Connection iSeries Access ODBC Driver V7R1. Vendor program not receiving success code

On Apr 28, 2016, at 7:29 AM, Rob Berendt <rob@xxxxxxxxx> wrote:

<snip>
new IBM i Access For Windows
</snip>

Is that like saying I got a new car when you really mean I bought a used
car but it's new to me?
There hasn't been a new version of IBM i Access for Windows for a few
years now.
IBM is pushing IBM i Access Client Solutions.


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Michael Schutte <mschutte369@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 04/27/2016 05:18 PM
Subject: Re: ODBC Connection iSeries Access ODBC Driver V7R1.
Vendor program not receiving success code
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Since my computer was returning a Rows Affected of 1. I decided to look
into the ODBC driver version for the IBM i (aka iSeries, AS/400). The
version on the Endicia PC was several versions behind mine and mine was
even old. So I updated my machine and had the network team update the
Endicia PC. They are now on the current version according to the IBM
website.



Retrieved the new version from

http://www-03.ibm.com/systems/power/software/i/access/windows_sp.html



After installing the new IBM i Access For Windows, the Endicia Machine
stopped re-uploading the previously posted orders and deleted them from
the
post back data. All is good, thank you for your time.

On Wed, Apr 27, 2016 at 9:14 AM, Michael Schutte <mschutte369@xxxxxxxxx>
wrote:

Never mind that was easy enough. Found the driver version.

On Wed, Apr 27, 2016 at 9:12 AM, Michael Schutte <mschutte369@xxxxxxxxx>
wrote:

I got to thinking that maybe my machine has an updated driver. I'll

have

to get into the Endicia machine to see what driver version is

installed.

Any clue on how to check. I'm obviously going to search to see if I

can

find out. Just wondering if someone else could save me time. HAHA.

On Wed, Apr 27, 2016 at 6:55 AM, Rob Berendt <rob@xxxxxxxxx> wrote:

<snip>
Just an FYI, I used Excel MQ Query, inserted the record. The message
returned was Rows Affected: 1. This is what I expect from the Endicia
Diagnostics Message.
</snip>

That was a great idea. I was wondering if there was a possibility of

an

exit point program, etc.

Or if there was a host server not started. ;-)


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Michael Schutte <mschutte369@xxxxxxxxx>
To: Midrange Systems Technical Discussion

<midrange-l@xxxxxxxxxxxx>

Date: 04/26/2016 04:48 PM
Subject: ODBC Connection iSeries Access ODBC Driver V7R1.

Vendor

program not receiving success code
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



I'm using Endicia Professional (shipping softward) and set it up to

use

an
ODBC connection to write records to a file on our iSeries V7R1 using
iSeries Access ODBC Driver.

The process is writing the record into the file. However, Endicia
continues
to post back all orders that are currently sitting in the post back

data.

I have configured the post back data option to post back immediately

and

delete posted records.

The records are not being deleted, I've been told that it's because

the

ODBC connection, more specifically, the driver isn't returning back
successful.

I changed Endicia to show diagnostic messages, after it does the

insert,

I
see a message saying Rows Affected: -1. I'm guessing that this is the
reason why it's not being marked as being posted.

I checked the ODBC connection and verified that the commit mode is

*NONE.

So the record should just write without needing a commit command.

Anybody have experience in this? While we attempt to resolve this

issue,

I'm just having them delete the post back data every once in awhile.

As

the post back data grows, the longer it takes to process one label

print.

This is cross posted with EndiciaCommunity.com I'm just hoping that
someone here may have come across this issue with the ODBC connection
with
either this product or any other windows program trying to connect

with

ODBC.

Just an FYI, I used Excel MQ Query, inserted the record. The message
returned was Rows Affected: 1. This is what I expect from the Endicia
Diagnostics Message.
--
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 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 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 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.