Skip to main content


II13049: SUPPORT FOR UNICODE: STEPS FOR INSTALLING AND CUSTOMIZING (PART 2) REFER TO II13048 (PART 1)

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as canceled.

Error description

  • Part 2 - Installing and Customizing, unicode support
    In II13048 you completed the set up of the conversion
       image. Following is an example of what your CUJIUTL JCL
       member should look like.  Additional conversion definitions
       may be required as described further below.  Note that
       (your sccsid), (your asccsid), and so on refer to the
       settings of the SCCSID, ASCCSID, etc. parameters of your
       installation-defined DSNHDECP module (job DSNTIJUZ).
       Note further that you also need to add conversion definitions
       for client connections that use CCSIDs other than those
       you define for this instance of DB2 for z/OS.
    .
       //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 *
          ********************************************/
          CONVERSION (your sccsid),00367,ER;
          CONVERSION (your sccsid),01200,ER;
          CONVERSION (your sccsid),01208,ER;
          CONVERSION (your sccsid),(your asccsid),ER;
    .
          CONVERSION 00367,(your sccsid),ER;
          CONVERSION 00367,01200,ER;
          CONVERSION 00367,01208,ER;
          CONVERSION 00367,(your asccsid),ER;
    .
          CONVERSION 01200,(your sccsid),ER;
          CONVERSION 01200,00367,ER;
          CONVERSION 01200,01208,ER;
          CONVERSION 01200,(your asccsid),ER;
    .
          CONVERSION 01208,(your sccsid),ER;
          CONVERSION 01208,00367,ER;
          CONVERSION 01208,01200,ER;
          CONVERSION 01208,(your asccsid),ER;
    .
          CONVERSION (your asccsid),(your sccsid),ER;
          CONVERSION (your asccsid),00367,ER;
          CONVERSION (your asccsid),01200,ER;
          CONVERSION (your asccsid),01208,ER;
    .
       If your DB2 uses mixed-byte or double-byte CCSIDs for EBCDIC
       and ASCII then these further conversion definitions are re-
       quired:
          CONVERSION (your sccsid),(your mccsid),ER;
          CONVERSION (your sccsid),(your amccsid),ER;
    .
          CONVERSION (your mccsid),00367,ER;
          CONVERSION (your mccsid),01200,ER;
          CONVERSION (your mccsid),01208,ER;
          CONVERSION (your mccsid),(your sccsid),ER;
          CONVERSION (your mccsid),(your asccsid),ER;
          CONVERSION (your mccsid),(your amccsid),ER;
    .
          CONVERSION (your gccsid),00367,ER;
          CONVERSION (your gccsid),01200,ER;
          CONVERSION (your gccsid),01208,ER;
          CONVERSION (your gccsid),(your agccsid),ER;
    .
          CONVERSION (your asccsid),(your mccsid),ER;
          CONVERSION (your asccsid),(your amccsid),ER;
    .
          CONVERSION (your amccsid),(your mccsid),ER;
          CONVERSION (your amccsid),00367,ER;
          CONVERSION (your amccsid),01200,ER;
          CONVERSION (your amccsid),01208,ER;
          CONVERSION (your amccsid),(your asccsid),ER;
          CONVERSION (your amccsid),(your sccsid),ER;
    .
          CONVERSION (your agccsid),(your gccsid),ER;
          CONVERSION (your agccsid),00367,ER;
          CONVERSION (your agccsid),01200,ER;
          CONVERSION (your agccsid),01208,ER;
    .
          CONVERSION 00367,(your mccsid),ER;
          CONVERSION 00367,(your gccsid),ER;
          CONVERSION 00367,(your amccsid),ER;
          CONVERSION 00367,(your agccsid),ER;
    .
          CONVERSION 01200,(your mccsid),ER;
          CONVERSION 01200,(your gccsid),ER;
          CONVERSION 01200,(your amccsid),ER;
          CONVERSION 01200,(your agccsid),ER;
    .
          CONVERSION 01208,(your mccsid),ER;
          CONVERSION 01208,(your gccsid),ER;
          CONVERSION 01208,(your amccsid),ER;
          CONVERSION 01208,(your agccsid),ER;
    .
       For Version 8 only, these further conversion definitions are
       required if the DSNHDECP SCCSID is not 37:
          CONVERSION 00037,00367,ER;
          CONVERSION 00037,00500,ER;
          CONVERSION 00037,01047,ER;
          CONVERSION 00037,01200,ER;
          CONVERSION 00037,01208,ER;
          CONVERSION 00037,(your asccsid),ER;
          CONVERSION 00367,00037,ER;
          CONVERSION 01200,00037,ER;
          CONVERSION 01208,00037,ER;
          CONVERSION (your asccsid),00037,ER;
    .
       For Version 8 only, these further conversion definitions are
       required if the DSNHDECP SCCSID is not 500:
          CONVERSION 00500,00037,ER;
          CONVERSION 00500,00367,ER;
          CONVERSION 00500,01047,ER;
          CONVERSION 00500,01200,ER;
          CONVERSION 00500,01208,ER;
          CONVERSION 00500,(your asccsid),ER;
          CONVERSION 00367,00500,ER;
          CONVERSION 01200,00500,ER;
          CONVERSION 01208,00500,ER;
          CONVERSION (your asccsid),00500,ER;
    .
       For Version 8 only, these further conversion definitions are
       required if the DSNHDECP SCCSID is not 1047:
          CONVERSION 01047,00037,ER;
          CONVERSION 01047,00367,ER;
          CONVERSION 01047,00500,ER;
          CONVERSION 01047,01200,ER;
          CONVERSION 01047,01208,ER;
          CONVERSION 01047,(your asccsid),ER;
          CONVERSION 00367,01047,ER;
          CONVERSION 01200,01047,ER;
          CONVERSION 01208,01047,ER;
          CONVERSION (your asccsid),01047,ER;
    .
          For Version 8 only, you also need to define conversion
          definitions for each additional CCSID presented by clients
          that make remote connections to this DB2:
          CONVERSION (client ccsid),00367,ER;
          CONVERSION (client ccsid),01200,ER;
          CONVERSION (client ccsid),01208,ER;
          CONVERSION 00367,(client ccsid),ER;
          CONVERSION 01200,(client ccsid),ER;
          CONVERSION 01208,(client ccsid),ER;
    .
       Submit the batch job in the CUNJIUTL member. Upon completion,
       it writes its output to the SYSPRINT DD (that is, SYSOUT in
       in this example). Expect a return code of zero from the
       CUNMIUTL program. If you receive other than return code zero,
       refer to the error situations in chapter "Creating the
       conversion image" of OS/390 V2 support for Unicode: using
       Conversion Services (SC33-7050) or of z/OS Support for
       Unicode Using Conversion Services (SA22-7649). This topic
       helps you correct environmental, syntactical and semantical
       errors that may occur.
    .
       After generating the conversion image, copy it to
       SYS1.PARMLIB or any other data set in the logical parmlib
       concatenation. In this example, you copy hlq.IMAGES(CUNIMG00)
       to SYS1.PARMLIB(CUNIMG00).
    .
    9. Calculate the storage needed for a conversion image.
    .
       Once the conversion image is created on DASD, you need to
       determine the amount of virtual storage the image will
       occupy. You specify this number as the number of pages on the
       REALSTORAGE parameter in the CUNUNIxx parmlib member that you
       create in the next step. The REALSTORAGE parameter was
       introduced to protect the system against main storage
       shortage caused by loading a conversion image that exceeds
       the amount of available storage.
       The minimum value for the REALSTORAGE parameter depends on
       how the image is activated:
    .
       * During IPL: The storage needed is the size of the image
         plus 1 page.
    .
       * Using the SET UNI command (parmlib member with keyword
         IMAGE): The storage needed is the size of the currently
         active image plus the size of the new conversion image.
    .
       To determine the storage that the currently active image
       occupies, issue the "D UNI,STORAGE" system command. The
       system displays the number of active pages. If this is the
       first time you are setting up the conversion environment or
       you are activating a conversion environment during IPL, this
       step is unnecessary.
    .
       To determine the storage that the new conversion image
       occupies, find the CUN1017I message in the SYSPRINT log
       created above. For example:
    .
         CUN1017I GENERATED IMAGE SIZE 291 PAGES........
    .
       it indicates the number of pages that are required for the
       new conversion image.
    .
       Note: As an alternative, it is possible to specify a
       REALSTORAGE value of zero that indicates that unlimited
       storage is available. In this case, a value of 524287
       pages will be used.
    .
    10.Create the parmlib member CUNUNIxx (parmlib member for
       activating a conversion environment).
    .
       Normally the member is created in SYS1.PARMLIB, but you
       create it in another data set in the logical parmlib
       concatenation. In this example, we choose SYS1.PARMLIB.
    .
       The "xx" can be any two alphanumeric characters (A-Z, 0-9,
       @, #, and $). In this example, we choose 00.
    .
       Following is the sample parmlib member in
       SYS1.PARMLIB(CUNUNI00).
    .
         REALSTORAGE 292;
         IMAGE CUNIMG00;
    .
       The REALSTORAGE statement indicates that 292 pages of real
       storage are required. We calculated this number above given
       that CUNMIUTL requires 291 pages and 1 page is required
       during IPL.
    .
       The IMAGE parameter indicates that the system is look in
       SYS1.PARMLIB (or a data set in the logical concatenation)
       member CUNIMG00 for the conversion image.
    .
       Note: It is possible to also create a parmlib member to
       delete a current conversion environment. Refer to the chapter
       "Creating the conversion image" of OS/390 V2 support for
       Unicode: using Conversion Services (SC33-7050) or of z/OS
         Support for Unicode Using Conversion Services (SA22-7649)
       for more information.
    .
    11.Edit IEASYSxx.
    .
       a. Add parameter UNI to IEASYSxx
    .
          >>--UNI=--+-xx-----------+---------><
                    |              |
                    |   <--,---+   |
                    |          |   |
                    +-(----xx--+-)-+
    .
          This parameter specifies one or more CUNUNI xx parmlib
          members that contain the keywords which configure the
          conversion environment. Each suffix xx identifies one
          CUNUNIxx member in the parmlib concatenation. If several
          parmlib members are specified, they are concatenated in
          the specified sequence. The concatenated contents is
          handled internally as a single member. This means that
          the lines are numbered consecutively and error messages
          about syntax errors refer to the concatenated text.
          Restrictions for keywords apply for the entire
          concatenated text.
          Note:  OW44581 must be applied to have the UNI support
          added to the operating system (ie.  support for the UNI
          system parameter, support for DISPLAY UNI command, etc.).
    .
       b. Check parameter MAXCAD in IEASYSxx, it limits the amount
          common data spaces in a system. If MAXCAD is specified,
          consider that OS/390 support for Unicode creates up to
          two common data spaces. Further information can be found
          under topic "Message CUN2011E appears" in OS/390 V2
          support for Unicode: using Conversion Services
          (SC33-7050) or z/OS Support for Unicode Using Conversion
              Services (SA22-7649).
    .
    12.Initialize the conversion environment with an IPL.
    .
    13.Once the system is initialized, you can use the DISPLAY UNI
       system command to show the current OS/390 Unicode status or
       use the SET UNI system command to change the conversion
       environment. For more information, refer to the chapter
       "Changing the conversion environment" in OS/390 V2 support
       for Unicode: using Conversion Services (SC33-7050) or z/OS
         Support for Unicode Using Conversion Services (SA22-7649)
    .
    You are now ready to apply any PTFs that makes use of the
    conversion environment.
    

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

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

APAR Information

  • APAR number

    II13049

  • Reported component name

    PB LIB INFO ITE

  • Reported component ID

    INFOPBLIB

  • Reported release

    001

  • Status

    CLOSED CAN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2001-10-30

  • Closed date

    2001-12-10

  • Last modified date

    2005-07-08

  • 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

Copyright and trademark information

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.

Rate this page

Please take a moment to complete this form to help us better serve you.

This material provides me with the information I need.






This material is clear and easy to understand.






Did the information help you to achieve your goal?

What updates, improvements, or related information would you like to see in this document?

Your response will be used to improve our document content. Requests for assistance, if applicable, should be submitted through your normal support channel as we cannot respond from this site.


Input the verification number to submit feedback:



Document information

Product categories:

Software

Data Management

Data Servers (Database Management Systems)

DB2 for z/OS


Operating system(s):

MVS


Software version:

001


Reference #:

II13049


IBM Group:

IBM Server Group


Modified date:

2005-07-08

Translate my page