The
CCSID for the file is 280. The CCSID for the field that has this problem is
65535. I've got a document from IBM stating that the 65535 CCSID for a give
field gets not converted at all from V5R3, unless specified in the CPYTOIMPF
command. To have it automatically converted it's required to chenge that CCSID
to one differnet from 65535 (neutral) ...for istance 280. The default CCSID
comes from the job. I'm ruuning some test in order to validate what's stated
from IBM.
I'm
going to run the file/field generation (using Qry/SQL) after changing the job
(CHGJOB) to use a 280 CCSID during the file/field creation.
I'll
let you know the results as soon as I'll have a better clear pitcture of
it.
Thanks
Corrado
From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Antoon van Os
Sent: Tuesday, 17 January, 2006 18:35
To: [email protected]
Subject: RE: [Easy400Group] Problem with RUNEXCEL on V5R3
Corrado,
When
you say "browsing" is that in green screen using EDTF or a PC editor on Windows
?
Could
you tell us what the CCSID of the file and its fields are ?
Somewhere in the back of my mind there is something about IBM doing
something about
how
OS/400 deals with CCSIDs as of V5R3, I will investigate
further.
regards
Antoon
-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED]On Behalf Of Corrado Vallino
Sent: maandag 16 januari 2006 9:05
To: [email protected]
Subject: RE: [Easy400Group] Problem with RUNEXCEL on V5R3This is the job log of the cmd after the run:4500 - CPYTOIMPF FROMFILE(VITPQ/ICIISSER *FIRST)
TOSTMF('/qdls/mydir/ICIISSER.csv') MBROPT(*ADD) STMFCODPAG(*PCASCII)
RCDDLM(*LF) FLDDLM(';') DECPNT('*PERIOD') DATFMT(*EUR) TIMFMT(*EUR)The cmd ends normally, without any error. Browsing the file I'm getting the following data in that date field:"ñöKññKòððõ";Corrado
From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Antoon van Os
Sent: Sunday, 15 January, 2006 11:37
To: [email protected]
Subject: RE: [Easy400Group] Problem with RUNEXCEL on V5R3Corrado,The RUNEXCEL command uses IBM's CPYTOSTMF in this way :CPYTOIMPF FROMFILE(*LIBL/TCILA *FIRST)
TOSTMF('/home/output/yourfile.csv') MBROPT(*ADD) STMFCODPAG(*PCASCII)
RCDDLM(*LF) FLDDLM(';') DECPNT('*PERIOD')Could you verify this in your joblog; then check the file in the IFSHth,Antoon-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED]On Behalf Of Corrado Vallino
Sent: zaterdag 14 januari 2006 18:42
To: [email protected]
Subject: [Easy400Group] Problem with RUNEXCEL on V5R3I've completed the migration for my 820 to V5R3 but now the RUNEXCEL command on a query generated date filed (dd/mm/yy format) gives me strange results.Here an example: On the iSeries the DB file looks like this:Mfg Order Status Ord Qty Received Qty Scrap Qty Close Dt Component Part Req Qty Issued Qty
BF22443 Z 100 96 4 16/11/05 6431026800 3 2As you can see the "Close Dt" filed is correct.In the stream file I've:
Mfg Order Status Ord Qty Received Qty Scrap Qty Close Dt Component Part Req Qty Issued Qty BF22443 Z 100 96 4 ñöKññKòððõ 6.43E+09 3 2 As you can see the Close Dt filed is not correctly converted.Any help will be appreciated, since this command is widely used in production to generate several stream file conversion.ThanksCorrado
YAHOO! GROUPS LINKS
- Visit your group "Easy400Group" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
