I had skimmed the article.

I will look closer :-)

Thanks.

Regards,
Richard Schoen
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business Intelligence
Email: richard@xxxxxxxxxxxxxxx
Web Site: http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT

------------------------------

message: 6
date: Tue, 3 Apr 2012 17:43:05 -0700
from: "Craig Pelkie" <craig@xxxxxxxxxx>
subject: RE: .NET application iSeries Access requirement???

http://www.systeminetwork.com/article/application-development/assembly-redir
ection-for-the-ibm-net-provider-65189

Craig Pelkie

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Richard Schoen
Sent: Tuesday, April 03, 2012 6:57 AM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: .NET application iSeries Access requirement???

Can you provide an example of how you changed machine.config.

I would like to use that in my ASP.Net class at COMMON.

Regards,
Richard Schoen
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business
Intelligence
Email: richard@xxxxxxxxxxxxxxx
Web Site: http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT
------------------------------

message: 7
date: Tue, 3 Apr 2012 12:05:59 +0000
from: "Maassel, John R." <John_Maassel@xxxxxxxxxxxx>
subject: RE: .NET application iSeries Access requirement???

Sorry about the delay...vacation days.

Yes, we used a "binding redirect" in the machine.config file to tell the
system to use the new 12.0 drivers when it asks for the 10.0. We regard this
as a temporary situation until we can get certain dependencies to work with
the newer 12.0 drivers, but nobody on our team has time to mess around with
stuff like that at the moment. We haven't seen any issues resulting from
this yet (knock on wood).

John Maassel
Programmer/Analyst
Bob Evans Farms, Inc
john_maassel@xxxxxxxxxxxx
614-492-7413

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Richard Schoen
Sent: Thursday, March 29, 2012 5:00 PM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: .NET application iSeries Access requirement???

Can you explain that one more ?

Are you saying you used the 12.0 drivers, but told the system it was 1.0 ?

Regards,
Richard Schoen
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business
Intelligence
Email: richard@xxxxxxxxxxxxxxx
Web Site: http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT

----------------------------------------------------------------------

message: 1
date: Thu, 29 Mar 2012 20:46:52 +0000
from: "Maassel, John R." <John_Maassel@xxxxxxxxxxxx>
subject: RE: .NET application iSeries Access requirement???

A problem we've run into when we started our migration to Client Access 6.1
is that the version of the IBM.Data.DB2.iSeries assembly went from 10.0.0.0
(with V5R4) to 12.0.0.0 (with V6R1). We immediately started getting messages
complaining about not finding the right version of IBM.Data.DB2.iSeries.
After we tracked it down to the new version of Client Access, we found that
we'd either have to recompile all of the .NET objects that use the database
against the new version, or put in binding redirects in the machine.config
file. Since we are in a mixed environment, we just set up the binding
overrides to make everything pretend it's on 5.4's driver.

John Maassel
Programmer/Analyst
Bob Evans Farms, Inc


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

________________________________

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.


------------------------------

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) digest 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.



End of MIDRANGE-L Digest, Vol 11, Issue 502
*******************************************



This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.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 on our policy page. If you have questions about this, please contact [javascript protected email address].