Re: different CCSID on a PF

["rick baird" <rick.baird@xxxxxxxxx>]

Thanks Mel, I will.

On 6/6/06, Mel Rothman <mel@xxxxxxxxxxxxxx> wrote:
> Rick,
>
> Regarding RCDDLM(*LFCR), I keyed it in quickly after the default of 
> RCDDLM(*EOR) failed.
>
> It also works with RCDDLM(*CRLF).
>
> I'm also running on V5R3M0 with 5722SS1 cum level TC06142.
>
> Searching the V5R3M0 PTF cover letters,
>
>    http://www-912.ibm.com/a_dir/as4ptf.nsf/$$search?openform ,
>
> for CPYTOIMPF, finds a lot of PTFs, none of which appears to be the same 
> problem, but one
> never knows.
>
> You might check your system's PTF levels.
>
> Mel Rothman
>
> rick baird wrote:
>
> > Mel and Scott,
> >
> > On 6/6/06, Mel Rothman <mel@xxxxxxxxxxxxxx> wrote:
> >> Rick,
> >>
> >> CPYTOIMPF with *PCASCII with a 65535 file containing only numerics (your 
> first file, named
> >> BAIRD) worked OK
> >
> > you're way ahead of me.
> >
> >> Here is the command I used:
> >>
> >> CPYTOIMPF FROMFILE(BAIRD) TOSTMF('/home/rothman/test.txt')  MBROPT(*REPLACE)
> >> STMFCODPAG(*PCASCII) RCDDLM(*LFCR)
> >
> > *LFCR?  I always use *CRLF  other than the obvious characters, is
> > there a difference?
> >
> > still didn't work though
> >
> > On 6/6/06, Scott Klement <midrange-l@xxxxxxxxxxxxxxxx> wrote:
> >> I think *PCASCII is calculated based on the from CCSID.  Try specifying an
> >> actual numeric codepage on the STMFCODPAG parm.  For example:
> >>
> >>     CPYTOSTMF FROMMBR(/whatever) TOSTMF(/whatever) STMFCODPAG(819)
> >
> > I tried both 819 and 1252 and still no luck.
> >
> > btw, i'm on V5R3
> >
> > I think i'm just going to bale and add an alpha field to the file and move on.
> >
> > thanks to all,
> >
> > Rick
>
> --
> 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.