Although, I may have misspoken a bit. If you are calling stored
procedures on the System i that would depend on what kind of SP's you
are using. In our case with the SQL server we are actually making
'direct' sql calls to DB2.......
Manager, Computing Services
Saint-Gobain Containers, Inc.
1509 S. Macedonia Ave.
Muncie, IN 47302
No single raindrop believes it is to blame for the flood.
This email and its attachments may be confidential and are intended
solely for the use of the individual to whom it is addressed. Any views
or opinions expressed are solely those of the author and do not
necessarily represent those of Saint-Gobain. If it did, it would be
folded, mutilated, watered down, politically corrected, and would show
up a week later if at all. If you are not the intended recipient of
this email and its attachments, you must take no action based upon them,
nor must you copy or show them to anyone.
Please contact the sender if you believe you have received this email in
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mark Allen
Sent: Monday, October 08, 2007 3:55 PM
To: Midrange Systems Technical Discussion
Subject: SQL Server Pull From Systemi
One of the "pieces" we lost in last weeks SQL Server crash was a number
stored procedures that in essence were set as kron jobs that did the
Delete all records from FILEA on SQL Server
Import all records from FILEA on Systemi to FILEA on SQL Server
Our SQL guy is having problems getting the SQL server to even see the
Systemi or any files to begin doing the critical ones manually.
I know he needs to set up some kind of OLEDB or ODBC connection, but
than that I am clueless and he's been pounding the keyboard all day just
tryign different things, googling etc without much success. Can someone
point me in the right direction to point him.
I can last about an hr with him before we both get
This mailing list archive is Copyright 1997-2020 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