× 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.



Hi Brad,
The CCSID 935 is Simplified Chinese (extended range), 937 is Traditional Chinese (extended range).
http://publib.boulder.ibm.com/infocenter/iseries/v5r4/topic/nls/rbagsnlsreferenceinformation.htm

I had also same condition as yours long time ago, we all thought that file created with no DDS should have same CCSID as job ccsid. The really thing is not as we thought. IBM also no any answer to this, The OS design no DDS source PF CCSID always is 65535. So If you want specified ccsid for created PF, you still need to create a long field O type for the file for DBCS data, Then it will create same as job ccsid.
A R SPLREC
A SPLFLD 300O

If the PF used by FTP, you need use DDS. Others like command CPYTOSTMF, CPYFRRMSTMF use with parameter STMFCODPAG(*PCASCII), even no DDS still can use to conversion.

Best regards,

Vengoal

-------- Original Message --------
From: "Brad Stone" <brad@xxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: CRTPF and job CCSID
Date: 2006/5/26 下午 12:35

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

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.