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



I'm opening it with the CCSID specified, that part has
always worked.  We're trying 950 as the CCSID.

I also thought about the job CCSID and default CCSID as
these are used to create the PF that is used, read in, and
converted to an IFS file.

The user has 65535 as the job CCSID and 37 as the default
CCSID.

I though because his job CCSID was not 937 (or even the
CHRID system value), this created the file used with a
CCSID of his job, then trying to convert that CCSID to 937
could be the issue.

Maybe?

On Wed, 3 May 2006 08:57:35 -0500
 Bruce Vining <bvining@xxxxxxxxxx> wrote:
> What is your open statement?  What release are you on
> (prior to V5R1 would 
> be a problem)?  What is your job CCSIDand job default
> CCSID (in case you 
> don't have O_CCSID specified with an explicit value)?
> 
>  
> 
> 
> 
> "Brad Stone" <brad@xxxxxxxxxxxx> 
> Sent by: midrange-l-bounces@xxxxxxxxxxxx
> 05/03/2006 08:50 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
> 
> 
> 
> 
> 
> 
> Sorry, that should have read "opening the stream file",
> not
> spooled file.. :)
> 
> On Wed, 03 May 2006 08:08:53 -0500
>  "Brad Stone" <brad@xxxxxxxxxxxx> wrote:
> > 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
> > -- 
> > 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.
> 
> 
> -- 
> 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

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.