|
<FONT face="Default Sans Serif, Verdana, Arial, Helvetica, sans-serif" size=2><DIV>How about a CRTPF with a CCSID of 37? That's what I've done in the past.<BR><DIV><BR><BR><BR>Paul Nelson<BR>Arbor Solutions, Inc.<BR>708-670-6978 Cell<BR>pnelson@xxxxxxxxxx<BR><BR><DIV><BR></DIV><FONT color=#990099>-----midrange-l-bounces@xxxxxxxxxxxx wrote: -----<BR><BR></FONT>To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx><BR>From: rick baird <rick.baird@xxxxxxxxx><BR>Sent by: midrange-l-bounces@xxxxxxxxxxxx<BR>Date: 02/08/2005 02:23PM<BR>Subject: Re: code page/CCSID for CPY***IMPF and STMF<BR><BR>Rob,<BR><BR>On Tue, 8 Feb 2005 14:51:00 -0500, rob@xxxxxxxxx <rob@xxxxxxxxx> wrote:<BR><BR>> That ain't going to work.<BR>> <BR>> We did a CHGSYSVAL QCCSID to 37.<BR><BR>ooh.<BR> <BR>> Try a CHGJOB CCSID(37) then your steps (including deleting the file and<BR>> the CRTPF) again to test. If successful, then figure out a time to do the<BR>> CHGSYSVAL QCCSID and make the leap. Really didn't cause any issues. He!!<BR><BR>You don't sound all that confident. ;)<BR><BR>This is interesting: I did a CRTPF CCSID(37) without changing my job,<BR>and it told me that "CCSID 37 not allowed with file type *DATA". Why<BR>would it care?<BR><BR>I then changed my job to CCSID(37) and did the same thing, same<BR>message. not specifying the CCSID let me create the file, but the<BR>resulting object had a CCSID of 65535. Is this expected behaviour?<BR><BR>> I think I did it midday.<BR>><BR>> This is the long term solution. You will hear of all sorts of workarounds<BR>> and temporary fixes like the data area (which will be removed in a future<BR>> release). However IBM is giving a hard push to getting off of 65535 and<BR>> picking a different CCSID.<BR><BR>I agree, but I hate flying blind here.<BR><BR>Where can I learn a little more about code pages and CCSID? I didn't<BR>find infocenter very helpful.<BR><BR>thanks,<BR><BR>Rick<BR><BR>> Rob Berendt<BR>> --<BR>> Group Dekko Services, LLC<BR>> Dept 01.073<BR>> PO Box 2000<BR>> Dock 108<BR>> 6928N 400E<BR>> Kendallville, IN 46755<BR>> <a href="http://www.dekko.com"; target=blank>http://www.dekko.com</a><BR>> <BR>> rick baird <rick.baird@xxxxxxxxx><BR>> Sent by: midrange-l-bounces@xxxxxxxxxxxx<BR>> 02/08/2005 02:09 PM<BR>> Please respond to<BR>> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx><BR>> <BR>> To<BR>> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx><BR>> cc<BR>> <BR>> Subject<BR>> Re: code page/CCSID for CPY***IMPF and STMF<BR>> <BR>> <BR>> Rob,<BR>> <BR>> >>When you try to copy the file back to the IFS, what are you copying<BR>> from?<BR>> <BR>> flat physical file - CRTPF RCDLEN(80) CCSID(*JOB)<BR>> user CCSID is *sysval<BR>> sysval for CCSID is 65535<BR>> <BR>> >>What is the CCSID and/or code page of that file?<BR>> <BR>> 65535<BR>> <BR>> The original file received from the bank is a stream file - CCSID 37.<BR>> I get the file via FTP.<BR>> <BR>> Thanks,<BR>> <BR>> Rick<BR>> <BR>> ><BR>> > Rob Berendt<BR>> > --<BR>> > Group Dekko Services, LLC<BR>> > Dept 01.073<BR>> > PO Box 2000<BR>> > Dock 108<BR>> > 6928N 400E<BR>> > Kendallville, IN 46755<BR>> > <a href="http://www.dekko.com"; target=blank>http://www.dekko.com</a><BR>> ><BR>> > rick baird <rick.baird@xxxxxxxxx><BR>> > Sent by: midrange-l-bounces@xxxxxxxxxxxx<BR>> > 02/08/2005 01:30 PM<BR>> > Please respond to<BR>> > Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx><BR>> ><BR>> > To<BR>> > Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx><BR>> > cc<BR>> ><BR>> > Subject<BR>> > code page/CCSID for CPY***IMPF and STMF<BR>> ><BR>> ><BR>> > Can someone point me to a clear and concise document that explains<BR>> > code page - CCSID topics and how to effectively use them when<BR>> > transfering files of various CCSIDs from physicals to stream files<BR>> > using the CPY***IMPF or STMF commands?<BR>> ><BR>> > Ever since upgrading to V5R3, a ton of my CPYFRMIMPF and CPYTOIMPF<BR>> > commands have broken. I know about the PTFs, and the data area to go<BR>> > back to V5R2 versions of the commands, but some things are still are<BR>> > just not working right anymore, and I'm ticked off about.<BR>> ><BR>> > in one case, i have a flat file from the bank, and it has a leading<BR>> blank.<BR>> ><BR>> > I do a cpyfrmimpf to a flat PF, using RMVBLANK(*NONE) but it still<BR>> > trims the first blank of the first record before stopping the trim.<BR>> ><BR>> > When I recieve the file from the bank, it's indeciferable when opened<BR>> > in notepad, but copies up to the iseries just fine (except for the<BR>> > blank described above). But I can't copy the same file back to the<BR>> > IFS. I used to be able to do a CPYTOIMPF STMFCODPAG(*PCASCII) and I<BR>> > could get an ascii readable stream file no matter the code page of the<BR>> > source file - not any more.<BR>> ><BR>> > I've done a work around for the trim, but if they fix it in a<BR>> > subsequent PTF, it'll break again.<BR>> ><BR>> > Thanks in advance,<BR>> > --<BR>> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing<BR>> > list<BR>> > To post a message email: MIDRANGE-L@xxxxxxxxxxxx<BR>> > To subscribe, unsubscribe, or change list options,<BR>> > visit: <a href="http://lists.midrange.com/mailman/listinfo/midrange-l"; target=blank>http://lists.midrange.com/mailman/listinfo/midrange-l</a><BR>> > or email: MIDRANGE-L-request@xxxxxxxxxxxx<BR>> > Before posting, please take a moment to review the archives<BR>> > at <a href="http://archive.midrange.com/midrange-l"; target=blank>http://archive.midrange.com/midrange-l</a>.<BR>> ><BR>> > --<BR>> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing<BR>> list<BR>> > To post a message email: MIDRANGE-L@xxxxxxxxxxxx<BR>> > To subscribe, unsubscribe, or change list options,<BR>> > visit: <a href="http://lists.midrange.com/mailman/listinfo/midrange-l"; target=blank>http://lists.midrange.com/mailman/listinfo/midrange-l</a><BR>> > or email: MIDRANGE-L-request@xxxxxxxxxxxx<BR>> > Before posting, please take a moment to review the archives<BR>> > at <a href="http://archive.midrange.com/midrange-l"; target=blank>http://archive.midrange.com/midrange-l</a>.<BR>> ><BR>> ><BR>> --<BR>> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing<BR>> list<BR>> To post a message email: MIDRANGE-L@xxxxxxxxxxxx<BR>> To subscribe, unsubscribe, or change list options,<BR>> visit: <a href="http://lists.midrange.com/mailman/listinfo/midrange-l"; target=blank>http://lists.midrange.com/mailman/listinfo/midrange-l</a><BR>> or email: MIDRANGE-L-request@xxxxxxxxxxxx<BR>> Before posting, please take a moment to review the archives<BR>> at <a href="http://archive.midrange.com/midrange-l"; target=blank>http://archive.midrange.com/midrange-l</a>.<BR>> <BR>> --<BR>> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list<BR>> To post a message email: MIDRANGE-L@xxxxxxxxxxxx<BR>> To subscribe, unsubscribe, or change list options,<BR>> visit: <a href="http://lists.midrange.com/mailman/listinfo/midrange-l"; target=blank>http://lists.midrange.com/mailman/listinfo/midrange-l</a><BR>> or email: MIDRANGE-L-request@xxxxxxxxxxxx<BR>> Before posting, please take a moment to review the archives<BR>> at <a href="http://archive.midrange.com/midrange-l"; target=blank>http://archive.midrange.com/midrange-l</a>.<BR>> <BR>><BR>-- <BR>This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list<BR>To post a message email: MIDRANGE-L@xxxxxxxxxxxx<BR>To subscribe, unsubscribe, or change list options,<BR>visit: <a href="http://lists.midrange.com/mailman/listinfo/midrange-l"; target=blank>http://lists.midrange.com/mailman/listinfo/midrange-l</a><BR>or email: MIDRANGE-L-request@xxxxxxxxxxxx<BR>Before posting, please take a moment to review the archives<BR>at <a href="http://archive.midrange.com/midrange-l"; target=blank>http://archive.midrange.com/midrange-l</a>.<BR><BR></DIV></DIV></FONT>
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.
midrange.com
