Adabas is delivered with its own data conversion capability called universal encoding support (UES). Entire Net-Work detects when it is connected to a target database that converts data and passes the data through to Adabas without converting it.

To ensure UES processing is handled properly, perform the following steps.

1. The Adabas database must include the correct libraries and have appropriate zaps applied.

   A sample startup job for a UES-enabled nucleus is provided in member ADANUCU of the ADAvrs.JOBS data set. For more information, read JCL Required for UES Support (z/OS).

   In addition, read Universal Encoding Support (UES) as well as ADADEF Utility: Define a Database and ADACMP Utility: Compress-Decompress Data for more information.

2. Ensure that UES support has been activated in the Adabas link routines. Verify that the load modules for all Adabas 8 link routines have been linked with LNKUES and the default (or updated) translation tables and that the LGBLSET SVCNO parameter has been set. For Adabas 8, UES is enabled by default for all link routines. For information on altering UES enablement in the link routines read appropriate sections of Installing Adabas With TP Monitors, starting with the section UES-Enabled Link Routines.

   UES-enabled databases can be connected to machines with different architectures through Com-plete, Software AG internal product software (APS), Entire Net-Work (WCP), and optionally in a z/OS environment through a direct TCP/IP link to the Adabas nucleus from web-based applications or from PC-based applications such as Software AG's Jadabas. Connections through Com-plete or the Software AG internal product software (APS) use the Adabas Com-plete link routines; connections through Entire Net-Work use the Adabas batch link routines. Connections through a direct TCP/IP link are described in the remainder of this document.

   Note:
   Effective with Adabas Version 8.3, only APS version 3.3.1 fix pack 22 and above are supported.