Re: different CCSID on a PF

more strangeness.

this is the only dds in this source file that compiles at 65535.  all
the rest compile at 37.

I'm really starting to freak out here, there seems to be no rhyme or
reason for it to compile at 65535, but it just does.

why would one file compile at 37, and another compile at 65535, in the
same session, not submitted, one right after another?

On 6/6/06, rick baird <rick.baird@xxxxxxxxx> wrote:

Ok, I got the-powers-that-be to change the system value for QCCSID to 37.

I signed off, signed back on, checked my current job and my job ccsid
is set to 37.

I deleted my file and recompiled.   It's still set at CCSID 65535, and
I can't do a CPYTOIMPF *PCASCII to it.

I can do a CHGPF to make it 37, but why should I have to?

I'm lost.   help me please.

On 6/6/06, rick baird <rick.baird@xxxxxxxxx> wrote:
> 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.
> >
> >
>