Re: CPYTOIMPF isn't writing the correct ccsid

Thank you for the suggestion.

I found the problem and fixed it.

In Operations Navigator, File Systems, File Shares, Tmp, Properties, Text Conversion
the check mark was missing in "Allow file text conversion". After adding two
extensions
.txt
.xml
It started working fine again.

The reason I didn't go there to begin with is the file was being viewed just fine on the
PC I was testing with XP Pro with a OS CCSID of 1252.
The PC that required the production job is running Win7 with a OS CCSID of 437.
I don't understand why It was working for months on the Win7 machine and now all of
a sudden it stopped. I guess that XP is still smart enough to convert to ASCII
without that setting in File Servers.

Thanks,

Gary


On 2 Nov 2010 at 13:48, Ken (Ken Sims <midrange-l@xxxxxxxxxxxx>) commented about
Re: CPYTOIMPF isn't writing the correct ccsid:

Hi Gary -

On Tue, 02 Nov 2010 12:50:38 -0700, "Gary Kuznitz "
<docfxit@xxxxxxxxxxxx> wrote:

The input file (ENVELOPE) is externally described so I can't use CPYTOSTMF.

Could you create a program-described file in QTEMP, CPYF ENVELOPE with
*NOCHK to that file, then use CPYTOSTMF? That's the method I use when
I need a flat file in the IFS from an externally-described file.

Ken
Opinions expressed are my own and do not necessarily represent the views
of my employer or anyone in their right mind.
--
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.