|
midrange.com
Bruce,
Message ID . . . . . . : CPF2845
Message . . . . : The copy did not complete for reason code 1.
Cause . . . . . : The Copy From Import File (CPYFRMIMPF) command, or Copy To
Import File (CPYTOIMPF) command could not be completed for reason 1. The
reason codes are:
1 - The CCSID or code page value is not valid.
Recovery .
1 - The FROMCCSID or TOCCSID must be set to a valid CCSID value if the
file CCSID is 65535. If the file does not have a CCSID of 65535, use the
CCSID(*FILE) value. Or, the FROMCCSID, TOCCSID, or STMFCODPAG specified is
not supported.
Thanks,
On 6/6/06, Bruce Vining <bvining@xxxxxxxxxx> wrote:
Numerics have no CCSID associated with them, so 65535 is probably being
chosen as a compromise as there are no alphanumeric fields requiring a
CCSID tag. When I create a file with just numerics and use CPYTOIMPF I'm
not getting any error and the data shows up in my *STMF. What error are
you getting? I tried V5R2 and V5R4.
Bruce Vining
"rick baird" <rick.baird@xxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
06/06/2006 12:23 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
To
"Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
cc
Subject
Re: different CCSID on a PF
Certainly!
Thanks,
CCSID 65535:
A R PPSFLCR
A FCCOMP 3S 0 COLHDG('COMP')
A FCACCT 3S 0 COLHDG('Acct')
A FCLOC 4S 0 COLHDG('Store')
A FCYEAR 4S 0 COLHDG('Fisc' 'Year')
A FCPER 2S 0 COLHDG('Fisc' 'Per')
A FCAMT 17S 2 COLHDG('Theoretical')
CCSID 37:
A R PPSUSTR
A SHFRLC 3S 0 COLHDG('From' 'Loc')
A SHTOLC 3S 0 COLHDG('To' 'Loc')
A SHITCL 2S 0 COLHDG('Item' 'Class')
A SHPROD 6S 0 COLHDG('Prod' 'Code')
A SHPRDS 30A COLHDG('Prod' 'Description')
A SHPRQT 8S 2 COLHDG('Ship' 'Quantity')
A SHTYPE 3A COLHDG('Ship' 'Type')
A SHSLUM 2A COLHDG('Sale' 'U/M')
A SHINUM 2A COLHDG('Inv' 'U/M')
A SHDSUM 2A COLHDG('Div' 'U/M')
A SHSTCS 7S 3 COLHDG('Std' 'Cost')
A SHPRST 1A COLHDG('Product' 'Status')
A SHMKTC 2A COLHDG('Market' 'Code')
A SHSTRT 25A COLHDG('To Loc' 'Street Address')
A SHCITY 24A COLHDG('To Loc' 'City/State')
A SHZIP 5A COLHDG('To Loc' 'Zip' 'Code')
A SHXPC1 6S 6 COLHDG('To Loc' 'Tax' 'Rate 1')
A SHXTP1 1A COLHDG('To Loc' 'Tax' 'Type 1')
A SHXAU1 4A COLHDG('To Loc' 'Tax' 'Auth 1')
A SHXPC2 6S 6 COLHDG('To Loc' 'Tax' 'Rate 2')
A SHXTP2 1A COLHDG('To Loc' 'Tax' 'Type 2')
A SHXAU2 4A COLHDG('To Loc' 'Tax' 'Auth 2')
A SHXPC3 6S 6 COLHDG('To Loc' 'Tax' 'Rate 3')
A SHXTP3 1A COLHDG('To Loc' 'Tax' 'Type 3')
A SHXAU3 4A COLHDG('To Loc' 'Tax' 'Auth 3')
A SHXPC4 6S 6 COLHDG('To Loc' 'Tax' 'Rate 4')
A SHXTP4 1A COLHDG('To Loc' 'Tax' 'Type 4')
A SHXAU4 4A COLHDG('To Loc' 'Tax' 'Auth 4')
A SHXPC5 6S 6 COLHDG('To Loc' 'Tax' 'Rate 5')
A SHXTP5 1A COLHDG('To Loc' 'Tax' 'Type 5')
A SHXAU5 4A COLHDG('To Loc' 'Tax' 'Auth 5')
A SHLCTP 1A COLHDG('To Loc' 'Type')
A SHUSTX 6S 6 COLHDG('To Loc' 'Use Tax' 'Rate')
A SHDIV 3A COLHDG('To Loc' 'Div')
A SHST 2A COLHDG('To Loc' 'State' 'Abbr')
A SHSTNM 15A COLHDG('To Loc' 'State' 'Name')
A SHCOMP 3S COLHDG('Comp' 'Code')
A SHPPSC 3S COLHDG('PplS' 'Tax' 'Acct')
A SHYEAR 4S COLHDG('Fisc' 'Year')
A SHPER 2S COLHDG('Fisc' 'Per')
On 6/6/06, Bruce Vining <bvining@xxxxxxxxxx> wrote:
> Can you provide a bit of the relevant DDS for the file? You generally
> should not be getting 65535 but there are ways to cause this with DDS
(for
> instance using datatype H for hexadecimal).
>
> Bruce Vining
>
>
>
>
> "rick baird" <rick.baird@xxxxxxxxx>
> Sent by: midrange-l-bounces@xxxxxxxxxxxx
> 06/06/2006 10:19 AM
> Please respond to
> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
>
>
> To
> "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
> cc
>
> Subject
> Re: different CCSID on a PF
>
>
>
>
>
>
> 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.
> > >
> > >
> >
> --
> 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.
--
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.
