|
Scott, the dif must be the use of a reference file in the dds, refrencing a file with a 37 CCSID, causing the new file to adopt the 37. the 65535 file is the problem child - I think someone messed around with the system value for QCCSID. that's the only explanation I can come up with. On 6/5/06, Scott Klement <midrange-l@xxxxxxxxxxxxxxxx> wrote:
> the CRTPF default for CCSID is *JOB for both - although, I do notice > that when I compile them, the one that shows up as 65535, has an extra > parameter on the command: > > User specified DBCS data . . . . IGCDTA *NO I can't imagine that this is having any effect. Indeed, I'm pretty sure that IGCDTA is ignored when you specify DDS for a file. Even if it weren't, IGCDTA(*NO) is the default. You say that both files were created with CCSID(*JOB)? Is it possible that one file was created by a job that has a CCSID of 37, and the other a job with a CCSID of 65535? -- 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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.