|
one problem maybe explained - the 37 CCSID file used a reference file that is a PF38, which is a 37 too. but I have a new problem - the file without the reference file, but the one that was created with clean new dds, got created with CCSID 65535? I think I ran into this problem before, and I think it was because the system value for QCCSID was set to 65535, and I thought I changed it a few years ago. Well, it's sitting at 65535 again, and I didn't change it. Is there anyway to tell when the last time that system value was changed? I compiled a file last friday, and that file is CCSID 37. gosh, i'm so confused.... On 6/5/06, rick baird <rick.baird@xxxxxxxxx> wrote:
Hey all, what would cause one PF to be created (DDS) with a CCSID of 37 and another with 65535? nothing special in the DDS, one uses a reference file, but other than that it's just plain old DDS. 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 what's up with that? Thanks, Rick
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.