[z/OS 1.4 DB2 v7 -> v8] CCSID Conversion

Bala

[z/OS 1.4 DB2 v7 -> v8] CCSID Conversion
Hello List,

I have spent fair enough time going through several web pages and posts in
this list about doing the CCSID conversions that is required before moving
to DB2 v8. We have set up Unicode Conversion Services at z/OS and createe
conversions that are required as per Informational APARs.

Our shop has EBCDIC SBCS_CCSID 37 at DSNHDECP. I find few
databases/tablespaces with SBCS_CCSID = 0 or 500. I understand those with
sbcs_ccsid = 0 are ones probably created before DB2 v5. Now, I am not sure
how this ccsid 500 objects were created.

1) Should I convert objects that have ccsid=0 to ccsid=37 as well, along
with converting objects with sbcs_ccsid=500 ?
2) What preferred method to do the conversion ? Is it
Unload-Drop-Recreate-Load-Bind ?

Thanks,
BaLa.


______________________________________________________________________

* IDUG 2009 Rome, Italy * 5-9 October * http://IDUG.ORG/Events *
______________________________________________________________________



IDUG.org was recently updated requiring members to use a new password. You should have gotten an e-mail with the temporary password assigned to your account. Please log in and update your member profile. If you are not already an IDUG.org member, please register at http://www.idug.org/component/juser/register.html

Peter Vanroose

Re: [z/OS 1.4 DB2 v7 -> v8] CCSID Conversion
(in response to Bala)
> Our shop has EBCDIC SBCS_CCSID 37 at DSNHDECP. I find few
> databases/tablespaces with SBCS_CCSID = 0 or 500.
> 1) Should I convert objects that have ccsid=0 to ccsid=37 as well,
> along with converting objects with sbcs_ccsid=500 ?

CCSID 87 is "EBCDIC USA" and CCSID 500 is "EBCDIC International".
Both have the same set of characters (Latin-1); they only differ in 7 places:
hex EBCDIC-87 EBCDIC-500
x4A ¢ [
x4F | !
x5A ! ]
x5F ¬ ^
xB0 ^ ¢
xBA [ ¬
xBB ] |
I would suggest you verify (a sample of) the data in (the textual columns
of) those tables with CCSID=500, to see if that data is really 500 or
actually 87.
Since the difference will be in just the 7 characters mentioned, search for
those. (I.e., mainly seach for exclamation point and square brackets.)
Then decide whether it was really CP 500 (in which case you leave the data
and the CCSID), or 87 (in which case you leave the data but set the CCSID to
87).
Normally, your 3270 display will show the data in CP87; so, for CP500 data,
you should see a vertical bar (|) in places where you would expect an
exclamation mark (!) and a cents sign where you expected an opening square
bracket.
For the tablespaces with CCSID=0, it should be safe to set them to CP87.
But you could again verify whether it's really "87" or rather "500" by
looking at the data.

-- Peter Vanroose
ABIS Training & Consulting.

______________________________________________________________________

* IDUG 2009 Denver, CO, USA * May 11-15, 2009 * http://IDUG.ORG/Events *
______________________________________________________________________




IDUG.org was recently updated requiring members to use a new password. You should have gotten an e-mail with the temporary password assigned to your account. Please log in and update your member profile. If you are not already an IDUG.org member, please register at http://www.idug.org/component/juser/register.html

Mark McCormack

[z/OS 1.4 DB2 v7 -> v8] CCSID Conversion
(in response to Peter Vanroose)
BaLa,

I suggest you contact IBM on this. We had similar issues with ccsid 37
and ccsid 500. There was a group of IBMers at SVL who were set up to
provide options and detailed instructions. This was 2-3 years ago for
us, so I don't remember all the details. It would be best for you to
let IBM guide you.

Mark

______________________________________________________________________

* IDUG 2009 Denver, CO, USA * May 11-15, 2009 * http://IDUG.ORG/Events *
______________________________________________________________________




IDUG.org was recently updated requiring members to use a new password. You should have gotten an e-mail with the temporary password assigned to your account. Please log in and update your member profile. If you are not already an IDUG.org member, please register at http://www.idug.org/component/juser/register.html

Richard Humphris

Re: [z/OS 1.4 DB2 v7 -> v8] CCSID Conversion
(in response to Mark McCormack)
Hi BaLa,

We started looking into this with v7; but instead we are migrating to v8
first and planning on doing ccsid conversion after that.

As long as all your (ebcdic) tables are all the same ccsid or zero. And
all your (ascii) tables are the same ccsid or zero. I suspect you could
just delay your conversion until after migrating to v8.

And I believe there is only one additional step you'll need to do in the
conversion process in v8 (as opposed to v7). But it's a big project
either way, so one extra step is minor.

And yes, you must open a PMR with IBM to fix the problem (either v7 or
v8) as only level 2 support can provide you with a special ptf you'll
need as part of the ccsid conversion process.

Good luck,
Rich Humphris


________________________________

From: DB2 Data Base Discussion List [mailto:[login to unmask email]
On Behalf Of McCormack, Mark A
Sent: Thursday, January 22, 2009 11:36 AM
To: [login to unmask email]
Subject: [DB2-L] [z/OS 1.4 DB2 v7 -> v8] CCSID Conversion



BaLa,

I suggest you contact IBM on this. We had similar issues with
ccsid 37 and ccsid 500. There was a group of IBMers at SVL who were set
up to provide options and detailed instructions. This was 2-3 years ago
for us, so I don't remember all the details. It would be best for you
to let IBM guide you.

Mark


________________________________

IDUG 2009 - Australasia * 18-20 March * Melbourne, Australia
< http://idug.org/lsAU >

IDUG.org < http://www.idug.org > was recently updated requiring
members to use a new password. You should have gotten an e-mail with the
temporary password assigned to your account. Please log in and update
your member profile. If you are not already an IDUG.org member, please
register here. < http://www.idug.org/component/juser/register.html >


E-MAIL CONFIDENTIALITY NOTICE: The contents of this e-mail message and any attachments are intended solely for the
addressee(s) and may contain confidential and/or legally privileged information. If you are not the
intended recipient of this message or if this message has been addressed to you in error, please
immediately alert the sender by reply e-mail and then delete this message and any attachments. If you
are not the intended recipient, you are notified that any use, dissemination, distribution, copying, or
storage of this message or any attachment is strictly prohibited.

______________________________________________________________________

* IDUG 2009 Melbourne, Australia * 18-20 March * http://IDUG.ORG/Events *
______________________________________________________________________




IDUG.org was recently updated requiring members to use a new password. You should have gotten an e-mail with the temporary password assigned to your account. Please log in and update your member profile. If you are not already an IDUG.org member, please register at http://www.idug.org/component/juser/register.html

Bala

Re: [z/OS 1.4 DB2 v7 -> v8] CCSID Conversion
(in response to Richard Humphris)
Thanks, Mark, Rick and Peter. I opened a PMR with IBM.

And, there is a doc listing out differences between EBCDIC code pages.
http://www-01.ibm.com/support/docview.wss?uid=swg21197185

At least , I would try to fix those code page 500's leaving code page 0's to
be fixed after v8 if that is an issue.

Thanks.

On Thu, Jan 22, 2009 at 4:03 PM, Peter Vanroose <[login to unmask email]> wrote:

> > Our shop has EBCDIC SBCS_CCSID 37 at DSNHDECP. I find few
> > databases/tablespaces with SBCS_CCSID = 0 or 500.
> > 1) Should I convert objects that have ccsid=0 to ccsid=37 as well,
> > along with converting objects with sbcs_ccsid=500 ?
>
> CCSID 87 is "EBCDIC USA" and CCSID 500 is "EBCDIC International".
> Both have the same set of characters (Latin-1); they only differ in 7
> places:
> hex EBCDIC-87 EBCDIC-500
> x4A ¢ [
> x4F | !
> x5A ! ]
> x5F ¬ ^
> xB0 ^ ¢
> xBA [ ¬
> xBB ] |
> I would suggest you verify (a sample of) the data in (the textual columns
> of) those tables with CCSID=500, to see if that data is really 500 or
> actually 87.
> Since the difference will be in just the 7 characters mentioned, search for
> those. (I.e., mainly seach for exclamation point and square brackets.)
> Then decide whether it was really CP 500 (in which case you leave the data
> and the CCSID), or 87 (in which case you leave the data but set the CCSID
> to
> 87).
> Normally, your 3270 display will show the data in CP87; so, for CP500 data,
> you should see a vertical bar (|) in places where you would expect an
> exclamation mark (!) and a cents sign where you expected an opening square
> bracket.
> For the tablespaces with CCSID=0, it should be safe to set them to CP87.
> But you could again verify whether it's really "87" or rather "500" by
> looking at the data.
>
> -- Peter Vanroose
> ABIS Training & Consulting.
>
> ______________________________________________________________________
>
> * IDUG 2009 Denver, CO, USA * May 11-15, 2009 * http://IDUG.ORG/Events < http://idug.org/Events > *
> ______________________________________________________________________
>
>
>
>
> IDUG.org was recently updated requiring members to use a new password. You
> should have gotten an e-mail with the temporary password assigned to your
> account. Please log in and update your member profile. If you are not
> already an IDUG.org member, please register at
> http://www.idug.org/component/juser/register.html
>

______________________________________________________________________

* IDUG 2009 Melbourne, Australia * 18-20 March * http://IDUG.ORG/Events *
______________________________________________________________________




IDUG.org was recently updated requiring members to use a new password. You should have gotten an e-mail with the temporary password assigned to your account. Please log in and update your member profile. If you are not already an IDUG.org member, please register at http://www.idug.org/component/juser/register.html