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.
Anmerkung:
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.
When used in this document, the notation
vrs
or
vr
represents the relevant product
version (see also Version in the
Glossary).
See General Prerequisites and System Support in the section Overview of the Installation Process.
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.
Be sure to read Installation Process and Major Natural Features before you start the installation procedure.
Add the following INCLUDE
statement to the link
instructions for the environment-independent
nucleus:
INCLUDE-MODULES LIB=ICSvrs.MOD,ELEMENT=(SAGICU),TYPE=(R,L)
Anmerkung:
The ICU data library ICSDT54J
is contained
in the ICS module SAGICU
and loaded by default.
Anmerkung:
The
ICU data
library ICSDT54J
is contained in the ICS module
SAGICU
and available by default.
Link the ICS module to the environment-independent nucleus as described in Link the Nucleus in Installing Natural.
This step is only required if you want to use another data library in
addition to ICSDT54J
.
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)
Link the ICU data library to the environment-independent nucleus as described in Link the Nucleus in Installing Natural.
Anmerkung:
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.
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.
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.
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.
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.
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.
After the last step of the installation procedure has been completed, proceed as follows:
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).
After successful activation, you can execute the example programs described in the Unicode and Code Page Support documentation.