Writing from ms SQL to IBM i database -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Writing from ms SQL to IBM i database
From: "Voris, John" <john.voris@xxxxxxxxxxxxx>
Date: Tue, 11 Aug 2015 15:08:02 +0000
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

The brackets are the standard in many documentation manuals as indicating Optional Parameters . . .

Also, if you have embedded blanks in your schema name etc, you may have to play with quotes to enclose them, or the whole string to the filename.

- John V.

The script is basically rejecting the 4 part file name, that is,
[linked server name].[catalog name].[library name].[file name]

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Writing from ms SQL to IBM i database , Justin Dearing

This mailing list archive is Copyright 1997-2024 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].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.