This document describes the steps for installing International Components for Unicode for Software AG (ICS) on z/VSE 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.
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.LIBR
data set
supplied on the installation medium for
base Natural.
Be sure to read Installation Process and Major Natural Features before you start the installation procedure.
Phase ICSNTTAB
is required under SMARTS for
reentrancy reasons.
Make sure that the ICS library is available at runtime of a Natural session:
Specify the ICS library in the job control statement
LIBDEF PHASE
for SMARTS.
Define ICSNTTAB
as RESIDENTPAGE
to
make it available for execution under SMARTS.
Make sure that the ICS library is available at runtime of a Natural session:
Specify the ICS library in the job control statement
LIBDEF PHASE
for your Natural batch or SMARTS jobs, or for the TP
monitor jobs under which Natural runs.
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.
Instead of the ICS module SAGICU
, you can also
load the ICS module SAGICUA9
. In addition to SAGICU
,
this module supports IBM architecture level 9: see
alternative ICS
modules in the Unicode and Code Page Support
documentation.
If you want to load SAGICUA9
, use the following
parameter setting:
RCA=SAGICU RCALIAS=(SAGICU,SAGICUA9)
The Natural profile parameter
RCALIAS
is described in the Parameter Reference
documentation.
Make sure that the ICS library is available at runtime of a Natural session:
Specify the ICS library in the job control statement
LIBDEF PHASE
for your Natural batch or SMARTS jobs, or for the TP
monitor jobs under which Natural runs.
At the start of a Natural session, set the Natural profile
parameters RCA
and CFICU
for the
ICU data
library (ICSDT60E
) to be used:
RCA=ICSDT60E CFICU=(DATFILE=ICSDT60E)
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 library is available at runtime of a Natural session:
Specify the ICS library in the job control statement
LIBDEF PHASE
for your Natural batch or SMARTS jobs, or for the TP
monitor jobs under which Natural runs.
Depending on your TP environment and the setting of the
Natural CFICU
profile
parameter, perform one of the following options:
Under CICS, with
CFICU=(DATITEM=NONE)
set:
Add one PPT entry for each ICU data item.
See also the corresponding step in Installing Natural CICS Interface.
Under Com-plete and Natural Development
Server, with CFICU=(DATITEM=NONE)
set:
Add THREAD-ESQA-SIZE=15K
as a keyword
parameter to the startup options for your Com-plete or Natural Development
Server.
Add one RESIDENTPAGE
entry for each ICU
data item that represents a converter (refer to the ICSCCOMP
source member in the ICSvrs.LIBR
data set).
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.