|
Maybe you should delete the stream files before you copy to them? The error message indicates that the code page of the existing stream file is not the same as what *PCASCII would calculate. >From the help text for the *PCASCII option: If the stream file exists, this option is valid only if the code page associated with the stream file is the same as the specified value. Otherwise, the operation will fail. If the stream file does not exist, a code page in the Microsoft Windows encoding scheme (x4105) is computed. (Microsoft, Windows, Windows NT, and the Windows 95 logo are registered trademarks of Microsoft Corporation). This code page is associated with the target stream file and is used for data conversion if it is requested. This option allows the resulting data to be used by Microsoft Windows applications. Code page 1252 is the default code page used by Microsoft Windows here in the US, and probably also in other areas where they use the same character set, so it's logical that this is what *PCASCII would select. If you are somehow changing the file to 850, it would cause the error that you've indicated. The fix, as I mentioned, is to delete the file first. Since there's no file there, you don't have to worry about whether the code page matches. Another idea would be to use *PCASCII only if the file does not already exist. If it does exist, use *STMF instead. On Tue, 29 Jul 2003, Tim Kredlo wrote: > > At first failure, both 'destination' files had already existed, as they > had been created by the previous run. > The first copy (Tim) worked fine. > Somehow the 'code page' of the 2nd destination file is now determined to > be 1252 instead of 850. > > What does this mean, how did it happen, and how do I prevent it in the > future? >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.