Re: DBCS and the IFS

["Brad Stone" <brad@xxxxxxxxxxxx>]

I'm getting a "conversion error" message when trying to
open the spooled file with 950 as the code page.  Would it
make a difference on V5R2?

Brad

On Tue, 02 May 2006 23:17:12 -0500
 "Brad Stone" <brad@xxxxxxxxxxxx> wrote:
> Thanks, Vengoal.
> 
> We will give this a shot!
> 
> Brad
> 
> On Wed, 03 May 2006 08:33:32 +0800
>  Vengoal Chang <vengoal@xxxxxxxxxxx> wrote:
> > Traditional Chinese DBCS iSeries CCSID: 937
> > mapping to client ASCII is 950. You need change IFS
> ccsid
> > by CHGATR 
> > change IFS STMF ccsid to 950.
> > 
> > 
> > When you use FTP to put  binary file to iSeries the
> > default iSeries 
> > CCSID is 819, but if you use quote type c 950, you will
> > get ccsid 950 STMF.
> > When you copy file from PC to iSeries under NetServer
> > share or using 
> > samba client copy pc shared file from iSeries, you will
> > get ccsid 1208 
> > or 1252. You also need manual changet to STMF 950.
> > 
> > 
> > Best regards,
> > 
> > Vengoal
> > 
> > -------- Original Message  --------
> > From: Bruce Vining <bvining@xxxxxxxxxx>
> > To: Midrange Systems Technical Discussion
> > <midrange-l@xxxxxxxxxxxx>
> > Subject: Re:DBCS and the IFS
> > Date: 2006/5/2 ?? 11:44
> > 
> > >Brad,
> > >
> > >If you have Chinese characters that you are attempting
> > to convert then 937 
> > >is the better way to go.  1175 is a proper subset of
> the
> > characters found 
> > >in CCSID 37 (CHRID 697 37) and contains no Traditional
> > Chinese characters. 
> > > 937 contains the 1175 character set plus the DBCS 935
> > character set.  You 
> > >will also want to convert to a CCSID other than 819 as
> > that's just ISO 
> > >Latin 1 (again no Traditional Chinese).
> > >
> > >Bruce
> > >
> > >
> > >
> > >
> > >"Brad Stone" <brad@xxxxxxxxxxxx> 
> > >Sent by: midrange-l-bounces@xxxxxxxxxxxx
> > >05/02/2006 09:40 AM
> > >Please respond to
> > >Midrange Systems Technical Discussion
> > <midrange-l@xxxxxxxxxxxx>
> > >
> > >
> > >To
> > >Midrange Systems Technical Discussion
> > <midrange-l@xxxxxxxxxxxx>
> > >cc
> > >
> > >Subject
> > >Re: DBCS and the IFS
> > >
> > >
> > >
> > >
> > >
> > >
> > >Thanks Bruce.
> > >
> > >It shows the CCSID to use for ASCII (if I'm reading it
> > >right) is 819, but there seems to be some traditional
> > >chinese characters that don't get converted properly
> > from
> > >EBCDIC to ASCII.
> > >
> > >Brad
> > >
> > >
> > >On Tue, 2 May 2006 08:53:12 -0500
> > > Bruce Vining <bvining@xxxxxxxxxx> wrote:
> > >  
> > >
> > >>Brad,
> > >>
> > >>If you go to the V5R4 Information Center and search
> on
> > >>1175 you will find 
> > >>that 1175 is the default CHRID for the English Upper
> > and
> > >>Lower Case DBCS 
> > >>NLV (2984) and the SBCS CHRID for CCSID  937
> > (Traditional
> > >>Chinese).
> > >>
> > >>Bruce Vining
> > >>
> > >>
> > >>
> > >>
> > >>"Brad Stone" <brad@xxxxxxxxxxxx> 
> > >>Sent by: midrange-l-bounces@xxxxxxxxxxxx
> > >>05/02/2006 08:11 AM
> > >>Please respond to
> > >>Midrange Systems Technical Discussion
> > >><midrange-l@xxxxxxxxxxxx>
> > >>
> > >>
> > >>To
> > >>Midrange Systems Technical Discussion
> > >><midrange-l@xxxxxxxxxxxx>
> > >>cc
> > >>
> > >>Subject
> > >>DBCS and the IFS
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>I am working with a customer who is running QCHRID
> 1175
> > >>and
> > >>having problems with DBCS conversion from EBCDIC to
> > ASCII
> > >>while writing to the IFS.
> > >>
> > >>I can normally find what CCSID to use in the
> conversion
> > >>in
> > >>the IBM documentation, but in this case I find little
> > >>mention of this CHRID in any tables.
> > >>
> > >>Anyone familiar?  I believe it's a traditional
> Chinese
> > >>character set.
> > >>
> > >>Thanks!
> > >>-- 
> > >>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.
> > >>
> > >>    
> > >>
> > >
> > >Bradley V. Stone
> > >BVS.Tools
> > >www.bvstools.com
> > >  
> > >
> > -- 
> > 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.
> > 
> 
> Bradley V. Stone
> BVS.Tools
> www.bvstools.com
> -- 
> 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.
> 

Bradley V. Stone
BVS.Tools
www.bvstools.com