Re: SQL SERVER/ISERIES INTEGRATION

[rob@xxxxxxxxx]

Rosalie,

Your attachment was blasted.  The list doesn't like them.  You'll have to 
manually retype the message.  Sometimes I just hate error windows that do 
not allow you to copy just the text.

On a straight iSeries application we get something that sounds similar 
when we compile a program in SQLRPGLE and do not use 
     C/EXEC SQL
     C+ Set Option
     C+     Commit    = *None
     C/END-EXEC
So, is there some way to turn off commitment control?  Perhaps that is 
your issue.  If we create a library using CREATE COLLECTION, and it is 
thus journaled, then we too do not need the Commit = *none.

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





"Rosalie Ducasse" <rosalie@xxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
11/09/2004 08:24 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
midrange-l@xxxxxxxxxxxx
cc

Fax to

Subject
SQL SERVER/ISERIES INTEGRATION






I am trying to export data from a table on a sql server database using a
linked server to our iSeries.  The table gets created however it does not
populate the data and I get the following message :-

(Embedded image moved to file: pic12859.pcx)

None of the files or libraries that we need to populate on the iSeries are
journaled and we cannot journal them as they are part of an ERP package.
When I create a library through a SQL statement using "create collection
testlib" and try to populate the table it then works, however when trying
to update an existing table in an existing library it does not.  I notice
that the library "testlib" is created with journals.
Can anyone help please?

Rosalie Ducasse
Omnia iTs - Fertilizer CONTACT DETAILS:
Tel:    + 2711 709 8816
Fax:    + 2711 463 6045
Cell:    + 2783 679 1415
E-mail:    rosalie@xxxxxxxxxxx
Website:    http://www.omnia.co.za/








DISCLAIMER:   This message contains information intended solely for the
addressee.  If you are not the intended recipient, you may not peruse, 
use,
disseminate, distribute or copy this message or any file attached to this
message.  If you have received this message in error, please notify the
sender immediately by e-mail, facsimile or telephone and thereafter delete
the original message from your machine.  Furthermore, the information
contained in this message, and any attachments thereto, is for information
purposes only and may contain the  personal views and opinions of the
author, which are not necessarily the views and opinions of the Omnia
Group. Therefore the Omnia Group  does not accept liability for any 
claims,
loss or damages of whatsoever nature, arising as a result of the reliance
on such information by anyone.    Whilst all reasonable steps are taken to
ensure the accuracy and integrity of information transmitted
electronically, the Omnia Group accepts  no liability or responsibility
whatsoever if information or data is, for whatsoever reason, incorrect,
corrupted or does not reach its intended destination.

The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited. If you received
this in error, please contact the sender and delete the material from any
computer.
--
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.