Runtime Configuration

The runtime configuration consist in the creation of all those executable files that require to be recompiled and/or linked on the target system: during this task some XFRAME components are rebuilt to get access to third party softwares (i.e. compilers, databases, etc.).

The runtime configuration is almost automated and it is divided in two phases:

During the first phase, the XFRAME configuration tool asks you for all the information it needs to rebuild the XFRAME components (i.e. which components must be linked, where to find some libraries, etc.). During the link phase the XFRAME rebuild tool analyzes the information collected in the first phase and recompiles and links whatever component must be rebuilt.

The runtime configuration may run automatically or manually.

Automatic runtime configuration

To execute it automatically, simply install (or re-install) XFRAME according to the installation instructions: during the setup procedure, the configuration tool is started and, when all the information have been collected, the link phase is automatically performed.

If any problem arises during this operation, the setup procedure stops and shows where to find the log of the procedure that caused the problem.

Manual runtime configuration

If you want to manually configure the runtime you may follow this procedure:

perl etc/xframeConfig

ksh etc/xframeLink

If no error occurs during this phase, XFRAME is correctly rebuilt, otherwise check the xframeLink.log file to discover the cause of the failure.

Third party software

As described before, the runtime configuration is useful to add to the base XFRAME runtime all those components required to access the resources of third party softwares.

This components includes:

Depending on the component you are linking, the XFRAME configuration tools asks for the information it needs. The following paragraphs describe the information requested and the relative options.

COBOL runtime

XFRAME requires a COBOL runtime. This setting configures the type of COBOL runtime to be linked:

Liant Open/PLI runtime

The runtime must be linked with PL/I runtime if the user application contains programs written in PL/I.

If this option is set to "yes", the runtime is linked with the Liant Open/PLI runtime libraries. The environment variable LPI_PRODUCT_DIR must be correctly set.

LU62/APPC

If the user applications require to communicate over a SNA network, the runtime must be linked with a valid APPC APIs library. This setting configures the type of SNA communication product to be linked:

If you specify a valid communication product, the tool will ask for the product installation base and for the product's include files path.

I.e.

using LU62 (none|snapix|snaplus|ibmcs|tpssna) [snapix] : snapix
SNAP/IX(TM) installation path [/opt/sna] : /opt/sna
SNAP/IX(TM) include path [/usr/include/sna] : /usr/include/sna

IBM MQ/Series interface

If the user applications require to communicate with an MQ/Series (AKA WebSphere/MQ) system, the runtime must be linked with the MQ APIs libraries. This setting configures if and how the MQ libraries must be linked:

When the MQ/Series server runs on the same system where XFRAME runs, both "server" and "client" configuration may be used.

When MQ/Series server runs on a remote system only "client" configuration may be used: in this case the MQ/Series client component must be installed and configured on the system where XFRAME runs.

The environment variable MQSERIES_HOME must be correctly set up.

RDBMS interface

If the user applications require to communicate with a database system, the runtime must be linked with the database client libraries. This setting configures if database libraries must be linked. If you reply "yes", the configuration tools asks for the type of database to use:

When the DB types has been chosen, you have to configure the interface type:

At the end a suitable database connection string is requested to compile the DB dependant objects. The string must be entered in the format user/password@database.

LDAP Interface

If you want to enable the inter-operation between XCICS/TS and an LDAP server, an LDAPv3 client must be installed on the system, to allow the XCICS LDAP interface compiling and to be linked to the XFRAME runtime.

If you choose to link with LDAP, you have to provide the full path to the directory where the LDAP include file(s) may be found (ldap.h) and all the libraries (or ld linker options) required to link the LDAP client.

These are some samples:

Linking with OpenLDAP client:

LDAP authentication interface (yes|no) [no] : yes
LDAP include files path [] : /usr/local/include
LDAP libraries [] : /usr/local/lib/hpux32/libldap.so

Linking with Mozilla LDAP client:

LDAP authentication interface (yes|no) [no] : yes
LDAP include files path [] : /opt/mozilla-ldap/mozilla/dist/public/ldap
LDAP libraries [] : /opt/mozilla-ldap/mozilla/dist/lib/libldap50.so

Linking with Oracle LDAP client:

LDAP authentication interface (yes|no) [no] : yes
LDAP include files path [] : /opt/oracle/product/9.2.0/ldap/public
LDAP libraries [] : /opt/oracle/product/9.2.0/lib/libldapclnt9.a

All the client libraries in the samples above make use of only one library for linking. If your client libraries requires more than one library, you may configure it adding more than one library with space as separator:

LDAP libraries [] : /my/ldap/lib/libldap1.so /my/ldap/lib/libldap2.so

or use "ld" options

LDAP libraries [] : -L /my/ldap/lib -lldap1 -lldap2

Note: The Oracle LDAP API implementation provides only limited diagnostic functions, therefore they inhibit a detailed error diagnostic for XCICS/TS user signon functions, such as SIGNON, CHANGE PASSWORD and VERIFY PASSWORD. If you need a detailed error management for these CICS commands, you should use another LDAP API implementation.