Installing International Components for Unicode for Software AG on BS2000/OSD

This document describes the steps for installing International Components for Unicode for Software AG (ICS) on BS2000/OSD which allows Natural to convert code pages and support Unicode.

International Components for Unicode for Software AG (ICS) requires the use of an ICS module and an ICU data library. In addition, you can use ICU data items to load ICU components that are not contained in the ICU data library. The ICS module does not have to be linked to the Natural nucleus if neither code page conversion nor Unicode support are required.

The use of ICU functionality increases the required Natural thread size.

Note:
For increased flexibility, it is also possible to load the ICS module during initialization of the Natural session. A dynamically loaded ICS module overrides the statically linked ICS module. You can also load an ICU data library during initialization of the Natural session. A dynamically loaded ICU data library overrides any statically linked ICU data library.

The ICS module, the ICU data libraries and the ICU data items are explained in Enabling Unicode and Code Page Support in the Unicode and Code Page Support documentation.

Notation vrs or vr:

When used in this document, the notation vrs or vr represents the relevant product version (see also Version in the Glossary).

Prerequisites

See General Prerequisites and System Support in the section Overview of the Installation Process.

Installation Medium

The ICS module, the ICU data libraries and the ICU data items are contained on the ICSvrs.MOD file supplied on the installation medium for base Natural.

Installation Procedure

Be sure to read Installation Process and Major Natural Features before you start the installation procedure.

Step 1: Link the ICS Module

  1. Add the following INCLUDE statement to the link instructions for the environment-independent nucleus: 

     INCLUDE-MODULES LIB=ICSvrs.MOD,ELEMENT=(SAGICU),TYPE=(R,L)

    Note:
    The ICU data library ICSDT54J is contained in the ICS module SAGICU and loaded by default.

    Note:
    The ICU data library ICSDT54J is contained in the ICS module SAGICU and available by default.

  2. Link the ICS module to the environment-independent nucleus as described in Link the Nucleus in Installing Natural.

Step 2: Link an ICU Data Library

This step is only required if you want to use another data library in addition to ICSDT54J.

  1. Add one of the following INCLUDE statements to the BINDER instructions for the environment-independent nucleus depending on the ICU data library to be used: 

     INCLUDE-MODULES LIB=ICSvrs.MOD,ELEMENT=(ICSDT54E),TYPE=(R,L)

    Or:

     INCLUDE-MODULES LIB=ICSvrs.MOD,ELEMENT=(ICSDT54X),TYPE=(R,L)

  2. Link the ICU data library to the environment-independent nucleus as described in Link the Nucleus in Installing Natural.

    Note:
    Since the size of the resulting module will exceed 16 MB, the environment-independent nucleus has to be linked with the linkage editor BINDER if ICU data libraries are to be included.

Step 3: Load the ICS Module at Session Start

  1. Make sure that the ICS load library from the ICSvrs.MOD file is available to the execution JCL of your Natural or TP monitor interface. Depending on your environment, perform one of the following options:

    • Add ICSvrs.MOD with the link name BLSLIBnn as an alternative user library to your execution JCL.

  2. At the start of a Natural session, set the Natural profile parameter RCA as follows: 

    RCA=SAGICU

    RCA is described in the Parameter Reference documentation.

    The ICS module SAGICU is described in the Unicode and Code Page Support documentation.

Step 4: Load an ICU Data Library at Session Start

  1. Make sure that the ICS load library from the ICSvrs.MOD file is available to the execution JCL of your Natural or TP monitor interface. Depending on your environment, perform one of the following options:

    • Add ICSvrs.MOD with the link name BLSLIBnn as an alternative user library to your execution JCL.

  2. At the start of a Natural session, set the Natural profile parameters RCA and CFICU for the ICU data library to be used:

    For ICSDT54E: 

    RCA=ICSDT54E  CFICU=(DATFILE=ICSDT54E)

    For ICSDT54X: 

    RCA=ICSDT54X  CFICU=(DATFILE=ICSDT54X)

    RCA and CFICU are described in the Parameter Reference documentation.

Step 5: Load ICU Data Items on Request in a Session

This step is optional and only required if you want to dynamically load an ICU data item on request during a Natural session instead of an entire ICU data library. For more information, see the Unicode and Code Page Support documentation.

  • Make sure that the ICS load library from the ICSvrs.MOD file is available to the execution JCL of your Natural or TP monitor interface. Depending on your environment, perform one of the following options:

    • Add ICSvrs.MOD with the link name BLSLIBnn as an alternative user library to your execution JCL.

Installation Verification

After the last step of the installation procedure has been completed, proceed as follows:

  1. Configure and activate your Unicode and code page environment by following the instructions in Configuration and Administration of the Unicode/Code Page Environment and Profile Parameters and Macros in the Unicode and Code Page Support documentation.

    For information on the code pages and ICU data files available in your current Natural environment, you can use the SYSCP utility (described in the Utilities documentation).

  2. After successful activation, you can execute the example programs described in the Unicode and Code Page Support documentation.