|
IBM did something regarding 65535 on release 5.2 or 5.3. Before, 65535 was the default. After 65535 was not acceptable...and for USA/English you needed to use 37. Caused a BIG PITB when it happened. Incidentally, we had an interesting problem with MIMIX, when I began logging the command usage of MIMIXOWN. We got 8+ logs PER SECOND of the CCSID changing from 65535 to 37 back to 65535 back to 37, etc., etc., etc. 65535 was hard coded in the user profile. I change it to *SYSVAL. Haven't had the guts to try logging it again, but will eventually... Dave -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of fbocch2595@xxxxxxx Sent: Thursday, August 17, 2006 2:56 PM To: midrange-l@xxxxxxxxxxxx Subject: Re: Ascii file conversion Sysval on my system is set to 65535 and I'm gettig cpda082 when I CPYFRMSTMF FROMSTMF('/lockbox/In/lbx.txt') TOMBR('/qsys.l ib/TEST.lib/mytestfile.file/test.mbr') MBROPT(*REPLACE) STMFCODPAG(*PCASCII) The file called mytestfile was compiled w/dds and has a ccsid of 37 and I get cpda082 when the ccsid on the file is 37. If the ccsid is 65535 then the cpyfrmstmf runs ok. Rob, I think you're saying that if I change ccsid to 37 I won't have an issue completing the command. We do many transmissions, in and out, what type of issues might I have if I change to 37?
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.
midrange.com
