APAR status

• Closed as canceled.

Error description

• This document outlines the steps you need to follow to install
  and configure support for Unicode Conversion Services (UCS)
  on z/OS V1R2 or a subsequent release.
  .
  Please follow the z/OS Program Directory for basic
  installation guidance. And also please refer to these z/OS
  books (or similar for other releases):
   - Title: z/OS V1R2.0 Planning for Installation
   Document Number: GA22-7504-03
   - Title: z/OS V1R4.0 and z/OS.e V1R4.0 Planning for
  Installation
   Document Number: GA22-7504-09
  .
  Then use steps 1 and 2 of this document to
  configure Support for Unicode for your DB2 subsystem.
  
  .
  1. The conversion services can only be used when the conversion
     environment is active. The infrastructure provides tools to
     create a conversion image. When the image is loaded into a
     common data space, the conversion environment is activated
     and the conversion services are ready to be used by DB2.
  .
     The jobs in hlq.SCUNJCL, for example CUNJIUTL, as shipped
     by IBM, have placeholders for values on the JOB card
     such as the following:
  .
     //$JOBPREF$$JOBNAME$ JOB ($ACCOUNT$),'$USER$',
     //     NOTIFY=$NOTIFY$,MSGCLASS=$MC$,MSGLEVEL=$ML$,
     //     TIME=$TI$,CLASS=$CL$,REGION=$REGION0M$
  .
     The REXX exec CUNRUCST in hlq.SCUNREXX lets you
     customize these values and when you run the REXX exec
     CUNRUALL, the values you specify will be supplied on all
     the JCL images.
  .
     You may also choose to customize your system by displaying
     Japanese messages or displaying English messages with
     modified date and time formats.  You set up the MVS
     Message Service to obtain this capability.
  .
     For more information on both of the above topics,
     refer to the chapter "Setting up the system" in
     OS/390 V2 support for Unicode: using Conversion Services
     (SC33-7050) or in z/OS Support for Unicode Using Conversion
     Services (SA22-7649)
  .
  2. Set up the conversion image.
     Following is the sample JCL member in hlq.SCUNJCL(CUNJIUTL).
  .
     //CUNMIUTL EXEC PGM=CUNMIUTL
     //SYSPRINT DD   SYSOUT=*
     //TABIN    DD   DISP=SHR,DSN=hlq.SCUNTBL
     //SYSIMG   DD   DSN=hlq.IMAGES(CUNIMG00),DISP=SHR
     //SYSIN    DD   *
       /********************************************
        * INPUT STATEMENTS FOR THE IMAGE GENERATOR *
        ********************************************/
          CASE NORMAL;          /* ENABLE TOUPPER AND TOLOWER */
          CONVERSION 1047,850;  /* EBCDIC -> ASCII */
          CONVERSION 850,1047;  /* ASCII -> EBCDIC */
     /*
  .
     The DDNAMEs that are passed to CUNMIUTL are described as
     follows:
  .
     SYSPRINT: A listing that shows the processed steps and error
               messages if applicable.
     TABIN:    Conversion tables for character conversion and
               case conversion. They are supplied by IBM, in this
               example in data set hlq.SCUNTBL. The image        .
               transforms the conversion tables into an internal
               format and stores them in the conversion image.
  .
     SYSIMG:   Output is a single image of the entire conversion
               environment. The conversion image is built accord-
               ing to the specification in the SYSIN DDNAME.  The
               conversion image resides in either a sequential
               data set or a member of a partitioned data set
               with a fixed block 80 format, in this example in
               partitioned data set member hlq.IMAGES(CUNIMG00).
  .
     SYSIN:    Two types of statements are recognized in this DD
               statement: case conversion, identified by the CASE
               control statement, and character conversion,
               identified by the CONVERSION control statement.
  .
               CASE Control Statement:
               Case conversion is defined as converting unicode
               characters (for instance, UCS-2) to their upper
               case equivalent or their lower case equivalent.
  .
               In the example above, "CASE NORMAL" is specified
               which means basic case conversion is provided,
               based solely on the file UnicodeData.txt provided
               by the Unicode consortium. It does not include
               special casing as described in the file
               SpecialCasing.txt provided by the Unicode
               consortium. An example for special casing is the
               German "hard S" which when written appears as a
               flat B; in special casing it uppercases to SS in
               German text.
  .
               Please see the closing text of DB2 for z/OS
               APAR PQ88759 for instructions on how to set up
               special casing.
  .
               CONVERSION Control Statement:
  .
               Character conversion is also referred to as con-
               version between specified CCSIDs. An application
               such as DB2 invokes the CUNLCNV function to con-
               vert characters between the specified code pages,
               but the application can do so, you need to identi-
               fy the conversions that are possible on the
               CONVERSION control statement.
  .
               In the example above, the two CONVERSION
               statements provide conversion between the EBCDIC
               code page 1047, the ASCII code page 850 and vice
               versa.
  .
               There is an extremely large list of code page con-
               versions that are possible. They are documented in
               the appendix "Summary of IBM-supplied conversion
               tables" in OS/390 V2 support for Unicode: using
               Conversion Services (SC33-7050) or in z/OS Support
               for Unicode Using Conversion Services (SA22-7649).
               For DB2 UDB for OS/390 and z/OS Version 7, you
               need only be concerned with conversions for the
               ASCII and EBCDIC codepages used by your DB2 (as
               specified by your installation-defined DSNHDECP
               module) and conversion from these code pages to
               and from code pages 1200, 1208, and 367 which are
               the code pages for UCS-2.
  .
               DB2 UDB for z/OS Version 8 requires additional
               conversions between CCSIDs 37, 500, and 1047 and
               the ASCII, EBCDIC, and Unicode CCSIDs used by your
               system.
  .
               There may be multiple conversion tables available
               for converting one CCSID to another. A technique-
               search-order can be used to specify which table
               should be used. It consists of up to 8 technique-
               characters. If you specify more than one technique
               character, the image generator tries to find a
               matching table for the leftmost technique charac-
               ter in the sequence of the technique-search-order.
               If not found, the search continues with the second
               one and so on. Especially for mixed conversion, it
               is advisable to use more than one technique-char-
               acter as one of the sub-conversions might exist
               only in round-trip mode and one only in enforced-
               subset.  In this case, a technique-search-order of
               'RE' or 'ER' would be required. technique-search-
               order is optional. If not specified, RECLM is used.
  .
               In the example above, technique-search-order is
               not specified on any of the CONVERSION statements.
               Therefore, they are logically equivalent to the
               following:
  
                 CONVERSION 1047,850,RECLM; /* EBCDIC -> ASCII */
                 CONVERSION 850,1047,RECLM; /* ASCII -> EBCDIC */
  .
               The important technique characters for you to take
               note of regarding DB2 are E (enforced subset)
               followed by R (round trip). Enforced Subset
               conversions map only those characters from one
               CCSID to another which have a corresponding char-
               acter in the second CCSID. All other characters
               are replaced by a substitution character.
               Roundtrip conversions between two CCSIDs assure
               that all characters making the 'roundtrip' arrive
               as they were originally.
  .
               Therefore, you must specify CONVERSION statements
               as follows for DB2:
  .
                 CONVERSION xxx,yyy,ER;
                 CONVERSION yyy,xxx,ER;
  .
               on each of the CONVERSION statements you specify.
  .
  Starting in z/OS 1.4 plus these APARs:
  1. OA08723(PE)
  2. OA10699(fix for PE)
  and in the base code starting in z/OS 1.6
  Unicode Conversion Services now can give the -E
  and/or -R conversions separately when -ER was requested.
  So, you may not see the -ER conversions in your D UNI,ALL
  output. In this case DB2 for z/OS will use the -E conversion
  if it is there or the -R if it is not.
  .
     This completes the set up of the conversion image. At this
     time, you should have an updated CUNJIUTL JCL member.
  .
  **** Please reference II13049 for further installing and
       customizing steps.
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• Informational apar for unicode install and support
  Abends019 may occur running COBOL program using
            National datatype without this maintenance applied.
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.

Product categories:

Software

Data Management

Data Servers (Database Management Systems)

DB2 for z/OS

Operating system(s):

MVS

Software version:

001

Reference #:

II13048

IBM Group:

IBM Server Group

Modified date:

2009-08-21