RE: CPYFRMSTMF problem

Oliver,

Its all to do with the CCSID defaults, not change of systems.

Testing your problem, I couldn't use the QDLS dir for some reason, but got
the same results from one of my own directories:

CPYTOSTMF seems to use the default CCSID of the dir you are copying to.
My  dir has CCSID of 37, so the file I copied ended up as CCSID 37 in the
IFS dir
When you look at that in windows, its garbage. When its moved around by
Explorer, and then copied back to the IFS, the CCSID changes to 1252 (on my
machine).
Then CPYFRMSTMF puts it back as garbage into the PF.
(I note that the CCSID of Qdls is zero)

To make it work, I changed the default CCSID on the CPYTOSTMF to 819 (param
STMFCODPAG) & it all worked OK.

I don't know if this will work with QDLS, but try it in a dir of your own in
the IFS


Regards

Ian Patterson



-----Original Message-----
From: midrange-l-bounces+ian=grange-systems.co.uk@xxxxxxxxxxxx
[mailto:midrange-l-bounces+ian=grange-systems.co.uk@xxxxxxxxxxxx]On
Behalf Of oliver.wenzel@xxxxxxxxxxxxxxxxxxxxxxx
Sent: 30 March 2004 14:42
To: midrange-l@xxxxxxxxxxxx
Subject: CPYFRMSTMF problem


Hello,

I have a physical file of fixed length 256 that I want to send as a text
file and import it to another AS400.

If I do a CPYTOSTMF "QGPL/EDI256" to \QDLS\EDI256.txt  and then the
opposite CPYFRMSTMF on the same AS400, the physical file is
identical.

If I copy the text file through Windows explorer into the QDLS of the
other AS400, and then do the CPYFRMSTMF, the physical file on the 400
is garbage.

I use the standard parameters on both systems and both are at V5R2, same
language and CCSID.

Any ideas?


_______________________________________________
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.