CPYFRMIMPF and double delimiters -- 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: CPYFRMIMPF and double delimiters
From: "Goodbar, Loyd (ETS - Water Valley)" <LGoodbar@xxxxxxxxxxxxxx>
Date: Fri, 29 Apr 2005 14:58:59 -0500
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/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

We're having an issue with CPYFRMIMPF, on V5R2. When we receive character
data such as "1 1/2"" 90 DEG ELL PVC SCH 80", only "1 1/2" appears in the
database file. I thought there was a PTF to fix this. This is a vendor's
standard extract file that we can't touch (remote SQL server system we don't
have access to). Any ideas?

 

Thanks,

Loyd

 

Loyd Goodbar

Senior programmer/analyst

BorgWarner

E/TS Water Valley

662-473-5713

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: CPYFRMIMPF and double delimiters , rob

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.