Below is the output of dspffd for that perticular field DT.
Does that field not have a CCSID assigned for it? This looks like the field's CCSID rather than your system's QCCSID:
CODED CHARACTER SET IDENTIFIER . . . . . : 65535
A CCSID of 65535 defines the field as binary data. CPYTOIMPF doesn't know what characters to use. Technically, data defined as 65535 cannot be represented as readable/printable characters because that CCSID has no alphabet, no language, no region. It's essentially the same as trying to open an image file with NOTEPAD in Windows.
Prior to V5R3, CPYTOIMPF wasn't correctly handling CCSIDs. At V5R3 (and in some V5R3 PTFs), CCSID handling was corrected which brought the need for changes in procedures that used CPYTOIMPF or CPYFRMIMPF on some systems. Systems that didn't have system value QCCSID set to the CCSID that fit the language and region that the system system handled, or that had files that had CCSIDs that weren't defined, needed attention.
The V5R3 Memo to Users discusses changes in the CPYFRMIMPF and CPYTOIMPF command changes topic on page 26.
Information APAR II13784 provides some additional information and some suggested fixes.
In your case, you might create a VIEW over your file and use the VIEW as input to CPYTOIMPF. SQL based on something like this might be used:
CREATE VIEW mylib/ADO150FV ( DT37 ) AS SELECT cast( DT as char (10) CCSID 37 ) FROM mylib/ADO150F
I only listed one field -- DT -- which was CAST as CCSID 37 and given the name DT37. You'd want to include all of the fields in the file, and you'd want to CAST each of them away from CCSID 65535 if that's what they had. Also, you would only use CCSID 37 if that's appropriate for your system.
You'd use names for the library and the view that meet your requirements.
I don't know what your system QCCSID value is yet, so I can't guess what you should use. You might use DSPJOB against your interactive job to see what the system guesses your job CCSID ought to be.
i observed this working fine v5r3
but i am using v5r4