RE: CRTPF and job CCSID

Brad,

AFAIK, it has always been that way.  The difference is that with v5r3
IBM tightened up the rules in regards to CCSID.



Charles Wilt
--
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
  

> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx 
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Brad Stone
> Sent: Friday, May 26, 2006 10:59 AM
> To: Midrange Systems Technical Discussion
> Subject: Re: CRTPF and job CCSID
> 
> Has this always been?  
> 
> The thing is, I'm using CPYSPLF to copy data to a PF.  Then
> I'm reading it and writing it to a stream file and no
> matter what code page I use it doen'st work, or it gives me
> a conversion error message.  
> 
> Brad
> 
> On Fri, 26 May 2006 07:57:51 -0500
>  Bruce Vining <bvining@xxxxxxxxxx> wrote:
> > It does seem contradictory but the first paragraph is
> > talking about 
> > FILETYPEs in general, of which there are two -- *DATA and
> > *SRC.  The 
> > second paragraph then says *DATA can't be used which
> > leaves you with *SRC. 
> >  And if you play with CRTPF and FILETYPE(*SRC) you will
> > find that CCSID is 
> > used (and CPD7306. CPD7307 being sent in many other
> > cases).
> > 
> > The text could be improved on...
> > 
> > Bruce
> > 
> > 
> > 
> > 
> > rob@xxxxxxxxx 
> > Sent by: midrange-l-bounces@xxxxxxxxxxxx
> > 05/26/2006 07:14 AM
> > Please respond to
> > Midrange Systems Technical Discussion
> > <midrange-l@xxxxxxxxxxxx>
> > 
> > 
> > To
> > Midrange Systems Technical Discussion
> > <midrange-l@xxxxxxxxxxxx>
> > cc
> > 
> > Subject
> > Re: CRTPF and job CCSID
> > 
> > 
> > 
> > 
> > 
> > 
> > Is it just me, but does the second paragraph of the help
> > for ccsid seem to 
> > 
> > conflict with the first paragraph?
> > 
> > This parameter is applicable only if no value is
> > specified for the 
> > Source file (SRCFILE) parameter and if a value is
> > specified for the 
> > Record length (RCDLEN) parameter.  If you specify a value
> > other than
> > the default value (*JOB) on this parameter, the SRCFILE
> > parameter is
> > not used, and a value must be specified for the RCDLEN
> > parameter. 
> >  
> >     Note:  A file created with no DDS when
> > FILETYPE(*DATA) is 
> >     specified has a CCSID of 65535, regardless of the job
> > CCSID 
> >     value. 
> > 
> > Rob Berendt
> > -- 
> > Group Dekko Services, LLC
> > Dept 01.073
> > PO Box 2000
> > Dock 108
> > 6928N 400E
> > Kendallville, IN 46755
> > http://www.dekko.com
> > 
> > 
> > 
> > 
> > 
> > "Brad Stone" <brad@xxxxxxxxxxxx> 
> > Sent by: midrange-l-bounces@xxxxxxxxxxxx
> > 05/26/2006 12:35 AM
> > Please respond to
> > Midrange Systems Technical Discussion
> > <midrange-l@xxxxxxxxxxxx>
> > 
> > 
> > To
> > Midrange Systems Technical Discussion
> > <midrange-l@xxxxxxxxxxxx>
> > cc
> > 
> > Subject
> > CRTPF and job CCSID
> > 
> > 
> > 
> > 
> > 
> > 
> > I was under the impression that when you issue a CRTPF
> > (no
> > DDS, just specifying record length) that the CCSID of the
> > file would be the job CCSID.
> > 
> > I have a case where a user has job ccsid and default
> > ccsid
> > f 935 (trad chinese).  When they issue CRTPF it creates
> > the
> > PF with a ccsid of 65535.
> > 
> > Any ideas?  I have to be missing something here.  :)
> > 
> > Brad
> > -- 
> > 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.
> > 
> > 
> > -- 
> > 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.
> > 
> > 
> > -- 
> > 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.
> > 
> 
> Bradley V. Stone
> BVS.Tools
> www.bvstools.com
> -- 
> 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.
> 
>