|
I did an EDTF and changed it from ....+....1....+....2....+....3....+....4.... ************Beginning of data************** "1 1/2" of stuff ",1 ************End of Data******************** to ....+....1....+....2....+....3....+....4.... ************Beginning of data************** "1 1/2"" of stuff ",1 ************End of Data******************** Then the CPYFRMIMPF worked, sort of select * from rob/borg ....+....1....+....2....+....3....+....4....+ MYTEXT MYNBR 1 1/2"" of stuff 1 ******** End of data ******** Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com rob@xxxxxxxxx Sent by: midrange-l-bounces@xxxxxxxxxxxx 04/29/2005 04:19 PM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> cc Subject Re: CPYFRMIMPF and double delimiters Yeah, so much has changed with CPY...IMPF with V5R3 it's frightening. If I do this in reverse: INSERT INTO ROB/BORG VALUES('1 1/2" of stuff', 1) select * from rob/borg ....+....1....+....2....+....3....+....4....+. MYTEXT MYNBR 1 1/2" of stuff 1 ******** End of data ******** CPYTOIMPF FROMFILE(ROB/BORG) TOSTMF('/rob/borg.txt') STMFCODPAG(*PCASCII) RCDDLM(*CRLF) dspf '/rob/borg.txt' ....+....1....+....2....+....3....+....4.... ************Beginning of data************** "1 1/2" of stuff ",1 ************End of Data******************** Now I'll take it back up. clrpfm rob/borg CPYFRMIMPF FROMSTMF('/rob/borg.txt') TOFILE(ROB/BORG) RCDDLM(*CRLF) 0 records copied to member BORG. Zero? CPYFRMIMPF FROMSTMF('/rob/borg.txt') TOFILE(ROB/BORG) RCDDLM(*CRLF) Ownership of object QCPIMTEMPS in QTEMP type *USRSPC changed. Ownership of object QACPTEMP01 in QTEMP type *USRSPC changed. Ownership of object QCFT689284 in QTEMP type *USRSPC changed. Ownership of object QF689284BR in QTEMP type *FILE changed. 0 records copied to member BORG. cpc2659 Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com daparnin@xxxxxxxxxxxxxx Sent by: midrange-l-bounces@xxxxxxxxxxxx 04/29/2005 03:55 PM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To midrange-l@xxxxxxxxxxxx cc Subject Re: CPYFRMIMPF and double delimiters Interesting... I tried this, first on our V5R1 system and got this: ....+....1....+....2....+....3....+....4....+. MYTEXT MYNBR 1 1/2 1 ******** End of data ******** Next, I tried it on our V5R3 system and got this: ....+....1....+....2....+....3....+....4....+. MYTEXT MYNBR 1 1/2"" of stuff 1 ******** End of data ******** I copied and pasted the commands from one screen to another. Both systems got the latest PTF's in January so they shouldn't be too far off. Dave Parnin Nishikawa Standard Company Topeka, IN 46571 daparnin@xxxxxxxxxxxxxx rob@xxxxxxxxx Sent by: To: Midrange Systems Technical Discussion midrange-l-bounces@m <midrange-l@xxxxxxxxxxxx> idrange.com cc: Subject: Re: CPYFRMIMPF and double delimiters 04/29/2005 03:15 PM Please respond to Midrange Systems Technical Discussion V5R3 dspf rob/borg.txt ....+....1....+....2....+....3 ************Beginning of data "1 1/2"" of stuff",1 ************End of Data****** CREATE TABLE ROB/BORG (MYTEXT CHAR (30 ) NOT NULL WITH DEFAULT, MYNBR INT NOT NULL WITH DEFAULT) CPYFRMIMPF FROMSTMF('/rob/borg.txt') TOFILE(ROB/BORG) RCDDLM(*CRLF) select * from rob/borg ....+....1....+....2....+....3....+....4....+. MYTEXT MYNBR 1 1/2"" of stuff 1 ******** End of data ******** Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com "Goodbar, Loyd (ETS - Water Valley)" <LGoodbar@xxxxxxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 04/29/2005 02:58 PM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> cc Subject CPYFRMIMPF and double delimiters 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 -- 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. -- 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. -- 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. -- 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.
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
