When you need 'em, you need 'em. We likewise had to implement initially a
while back because of some DB2 maintenance. Took quite a while and IBM help
to figure out was wrong.

There are basically two ways to implement: throw in *every* possible
conversion table (easy), or track down just the ones you need and implement
only those (harder). The main reason for not taking the easy shotgun
approach is that UCS tables live in page-fixed storage, which effectively
means real storage. I'm probably overly sensitive to this requirement; in a
well-heeled LPAR you probably wouldn't notice the impact. Nonetheless, I
still think it's worth being a little choosy in order to minimize the real
storage cost. It's a business issue more than a technical one.

.
.
.
JO.Skip Robinson
Southern California Edison Company
SHARE MVS Program Co-Manager
626-302-7535 Office
323-715-0595 Mobile
[EMAIL PROTECTED]

IBM Mainframe Discussion List <[email protected]> wrote on 06/19/2005
08:39:34:

> From my experience, only products that use UCS know it is there.  We had
> to implement a year or two ago because of some DB2 PTFs.
>
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
> Behalf Of Cwi Jeret
> Sent: Sunday, June 19, 2005 6:04 AM
> To: [email protected]
> Subject: Aplications running on z/OS1.4 after implementation of Unicode
> Conversion services (UCS)
>
>
> Hello,
>
> Due to some problems after installation of "EVENT PUBLISHER"
> we got the request from IBM to implement "Unicode Conversion Services"
> on
> our Production Site.
>
> We want to be sure that this will not affect running Production
> Applications !
>
> Does anyone have experience with implementation of "Unicode Conversion
> Services"
> and the impact on working applications ?

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to