RE: SQL SERVER/ISERIES INTEGRATION

Rosalie,

Are you using DTS to do this? The problem is caused by the way that DTS
and the OLEDB driver work together to do the insert. The want (demand)
that you use transactions, hence the need for journaling. You'll get the
same problem trying to do a simple insert statement in Query Analyzer.

I've linked by iSeries to my pc and called the link SOL. The following
blows up:

insert into sol...c values('a', 'b')

Saying:

Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'IBMDA400' reported an error.  
[OLE/DB provider returned message: CPF4328: Member C not journaled to
journal *N.]
OLE DB error trace [OLE/DB Provider 'IBMDA400' IOpenRowset::OpenRowset
returned 0x80004005:   ]. 

However, you can make it work if you don't mind a strange looking SQL:

insert into openquery(sol,'select * from waldenl.c where 1=0')
values('a', 'b')

Read up on openquery() in books online.

Now, if you're using DTS why not use a custom DTS script and do the
inserts in code instead of relying on the DTS data pump.

-Walden


------------
Walden H Leverich III
President & CEO
Tech Software
(516) 627-3800 x11
WaldenL@xxxxxxxxxxxxxxx
http://www.TechSoftInc.com 

Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)
 
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rosalie Ducasse
Sent: Wednesday, 10 November, 2004 00:51
To: midrange-l@xxxxxxxxxxxx
Subject: Re: SQL SERVER/ISERIES INTEGRATION



Steve

I have no problem with initiating the job on the iSeries, however the
job
is being initiated on the SQL server.  When I import data from the
iSeries
to the SQL server - no problem, the issue arrises when I try to export
data
from the SQL server to the iSeries


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/



 

                      "Steve Landess"

                      <sjl_abc@hotmail.        To:      "Midrange
Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>             
                      com>                     cc:
<rosalie@xxxxxxxxxxx>

                                               Subject: Re: SQL
SERVER/ISERIES INTEGRATION                                            
                      09/11/2004 05:56

                      PM

 

 







> "Rosalie Ducasse" wrote:
> 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 :-
>
> 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 -
I'm a satisfied user is iS/ODBC - it allows you to copy data to/from a
SQL
Server database directly from the iSeries.

See:
WWW.iStudio400.com

Steve Landess
Austin, Texas
(512) 423-0935
















    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.


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