× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



<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&nbsp;Nelson<BR>Arbor&nbsp;Solutions,&nbsp;Inc.<BR>708-670-6978&nbsp;&nbsp;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 
&lt;midrange-l@xxxxxxxxxxxx&gt;<BR>From: rick baird 
&lt;rick.baird@xxxxxxxxx&gt;<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 &lt;rob@xxxxxxxxx&gt; wrote:<BR><BR>&gt; That 
ain't going to work.<BR>&gt; <BR>&gt; We did a CHGSYSVAL QCCSID to 
37.<BR><BR>ooh.<BR> <BR>&gt; Try a CHGJOB CCSID(37) then your steps (including 
deleting the file and<BR>&gt; the CRTPF) again to test.  If successful, then 
figure out a time to do the<BR>&gt; 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>&gt; I think I did it midday.<BR>&gt;<BR>&gt; This is the 
long term solution.  You will hear of all sorts of workarounds<BR>&gt; and 
temporary fixes like the data area (which will be removed in a future<BR>&gt; 
release).  However IBM is giving a hard push to getting off of 65535 
and<BR>&gt; 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>&gt; 
Rob Berendt<BR>&gt; --<BR>&gt; Group Dekko Services, LLC<BR>&gt; Dept 
01.073<BR>&gt; PO Box 2000<BR>&gt; Dock 108<BR>&gt; 6928N 400E<BR>&gt; 
Kendallville, IN 46755<BR>&gt; <a href="http://www.dekko.com"; 
target=blank>http://www.dekko.com</a><BR>&gt; <BR>&gt; rick baird 
&lt;rick.baird@xxxxxxxxx&gt;<BR>&gt; Sent by: 
midrange-l-bounces@xxxxxxxxxxxx<BR>&gt; 02/08/2005 02:09 PM<BR>&gt; Please 
respond to<BR>&gt; Midrange Systems Technical Discussion 
&lt;midrange-l@xxxxxxxxxxxx&gt;<BR>&gt; <BR>&gt; To<BR>&gt; Midrange Systems 
Technical Discussion &lt;midrange-l@xxxxxxxxxxxx&gt;<BR>&gt; cc<BR>&gt; 
<BR>&gt; Subject<BR>&gt; Re: code page/CCSID for CPY***IMPF and STMF<BR>&gt; 
<BR>&gt; <BR>&gt; Rob,<BR>&gt; <BR>&gt; &gt;&gt;When you try to copy the file 
back to the IFS, what are you copying<BR>&gt; from?<BR>&gt; <BR>&gt; flat 
physical file - CRTPF RCDLEN(80) CCSID(*JOB)<BR>&gt; user CCSID is 
*sysval<BR>&gt; sysval for CCSID is 65535<BR>&gt; <BR>&gt; &gt;&gt;What is the 
CCSID and/or code page of that file?<BR>&gt; <BR>&gt; 65535<BR>&gt; <BR>&gt; 
The original file received from the bank is a stream file - CCSID 37.<BR>&gt; I 
get the file via FTP.<BR>&gt; <BR>&gt; Thanks,<BR>&gt; <BR>&gt; Rick<BR>&gt; 
<BR>&gt; &gt;<BR>&gt; &gt; Rob Berendt<BR>&gt; &gt; --<BR>&gt; &gt; Group Dekko 
Services, LLC<BR>&gt; &gt; Dept 01.073<BR>&gt; &gt; PO Box 2000<BR>&gt; &gt; 
Dock 108<BR>&gt; &gt; 6928N 400E<BR>&gt; &gt; Kendallville, IN 46755<BR>&gt; 
&gt; <a href="http://www.dekko.com"; 
target=blank>http://www.dekko.com</a><BR>&gt; &gt;<BR>&gt; &gt; rick baird 
&lt;rick.baird@xxxxxxxxx&gt;<BR>&gt; &gt; Sent by: 
midrange-l-bounces@xxxxxxxxxxxx<BR>&gt; &gt; 02/08/2005 01:30 PM<BR>&gt; &gt; 
Please respond to<BR>&gt; &gt; Midrange Systems Technical Discussion 
&lt;midrange-l@xxxxxxxxxxxx&gt;<BR>&gt; &gt;<BR>&gt; &gt; To<BR>&gt; &gt; 
Midrange Systems Technical Discussion &lt;midrange-l@xxxxxxxxxxxx&gt;<BR>&gt; 
&gt; cc<BR>&gt; &gt;<BR>&gt; &gt; Subject<BR>&gt; &gt; code page/CCSID for 
CPY***IMPF and STMF<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; &gt; Can someone point me 
to a clear and concise document that explains<BR>&gt; &gt; code page - CCSID 
topics and how to effectively use them when<BR>&gt; &gt; transfering files of 
various CCSIDs from physicals to stream files<BR>&gt; &gt; using the CPY***IMPF 
or STMF commands?<BR>&gt; &gt;<BR>&gt; &gt; Ever since upgrading to V5R3, a ton 
of my CPYFRMIMPF and CPYTOIMPF<BR>&gt; &gt; commands have broken.   I know 
about the PTFs, and the data area to go<BR>&gt; &gt; back to V5R2 versions of 
the commands, but some things are still are<BR>&gt; &gt; just not working right 
anymore, and I'm ticked off about.<BR>&gt; &gt;<BR>&gt; &gt; in one case, i 
have a flat file from the bank, and it has a leading<BR>&gt; blank.<BR>&gt; 
&gt;<BR>&gt; &gt; I do a cpyfrmimpf to a flat PF, using RMVBLANK(*NONE) but it 
still<BR>&gt; &gt; trims the first blank of the first record before stopping 
the trim.<BR>&gt; &gt;<BR>&gt; &gt; When I recieve the file from the bank, it's 
indeciferable when opened<BR>&gt; &gt; in notepad, but copies up to the iseries 
just fine (except for the<BR>&gt; &gt; blank described above).  But I can't 
copy the same file back to the<BR>&gt; &gt; IFS.   I used to be able to do a 
CPYTOIMPF STMFCODPAG(*PCASCII) and I<BR>&gt; &gt; could get an ascii readable 
stream file no matter the code page of the<BR>&gt; &gt; source file - not any 
more.<BR>&gt; &gt;<BR>&gt; &gt; I've done a work around for the trim, but if 
they fix it in a<BR>&gt; &gt; subsequent PTF, it'll break again.<BR>&gt; 
&gt;<BR>&gt; &gt; Thanks in advance,<BR>&gt; &gt; --<BR>&gt; &gt; This is the 
Midrange Systems Technical Discussion (MIDRANGE-L) mailing<BR>&gt; &gt; 
list<BR>&gt; &gt; To post a message email: MIDRANGE-L@xxxxxxxxxxxx<BR>&gt; &gt; 
To subscribe, unsubscribe, or change list options,<BR>&gt; &gt; visit: <a 
href="http://lists.midrange.com/mailman/listinfo/midrange-l"; 
target=blank>http://lists.midrange.com/mailman/listinfo/midrange-l</a><BR>&gt; 
&gt; or email: MIDRANGE-L-request@xxxxxxxxxxxx<BR>&gt; &gt; Before posting, 
please take a moment to review the archives<BR>&gt; &gt; at <a 
href="http://archive.midrange.com/midrange-l"; 
target=blank>http://archive.midrange.com/midrange-l</a>.<BR>&gt; &gt;<BR>&gt; 
&gt; --<BR>&gt; &gt; This is the Midrange Systems Technical Discussion 
(MIDRANGE-L) mailing<BR>&gt; list<BR>&gt; &gt; To post a message email: 
MIDRANGE-L@xxxxxxxxxxxx<BR>&gt; &gt; To subscribe, unsubscribe, or change list 
options,<BR>&gt; &gt; visit: <a 
href="http://lists.midrange.com/mailman/listinfo/midrange-l"; 
target=blank>http://lists.midrange.com/mailman/listinfo/midrange-l</a><BR>&gt; 
&gt; or email: MIDRANGE-L-request@xxxxxxxxxxxx<BR>&gt; &gt; Before posting, 
please take a moment to review the archives<BR>&gt; &gt; at <a 
href="http://archive.midrange.com/midrange-l"; 
target=blank>http://archive.midrange.com/midrange-l</a>.<BR>&gt; &gt;<BR>&gt; 
&gt;<BR>&gt; --<BR>&gt; This is the Midrange Systems Technical Discussion 
(MIDRANGE-L) mailing<BR>&gt; list<BR>&gt; To post a message email: 
MIDRANGE-L@xxxxxxxxxxxx<BR>&gt; To subscribe, unsubscribe, or change list 
options,<BR>&gt; visit: <a 
href="http://lists.midrange.com/mailman/listinfo/midrange-l"; 
target=blank>http://lists.midrange.com/mailman/listinfo/midrange-l</a><BR>&gt; 
or email: MIDRANGE-L-request@xxxxxxxxxxxx<BR>&gt; Before posting, please take a 
moment to review the archives<BR>&gt; at <a 
href="http://archive.midrange.com/midrange-l"; 
target=blank>http://archive.midrange.com/midrange-l</a>.<BR>&gt; <BR>&gt; 
--<BR>&gt; This is the Midrange Systems Technical Discussion (MIDRANGE-L) 
mailing list<BR>&gt; To post a message email: MIDRANGE-L@xxxxxxxxxxxx<BR>&gt; 
To subscribe, unsubscribe, or change list options,<BR>&gt; visit: <a 
href="http://lists.midrange.com/mailman/listinfo/midrange-l"; 
target=blank>http://lists.midrange.com/mailman/listinfo/midrange-l</a><BR>&gt; 
or email: MIDRANGE-L-request@xxxxxxxxxxxx<BR>&gt; Before posting, please take a 
moment to review the archives<BR>&gt; at <a 
href="http://archive.midrange.com/midrange-l"; 
target=blank>http://archive.midrange.com/midrange-l</a>.<BR>&gt; <BR>&gt;<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 thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.