Requesting additional dynamic routing support

This section contains Product-sensitive Programming Interface Information.

Note

If you are running CICS® Transaction Server for OS/390® Version 1 Release 3 and later, it is recommended that you use the CICSPlex® SM-supplied program EYU9XLOP for all your dynamic routing requirements. You need the information in this section only if you wish to continue to use this function during migration to CICS Transaction Server for OS/390 Version 1 Release 3.

If your routing regions are CICS Transaction Server for OS/390 Version 1 Release 3 and later, or if you are using CICS BTS or enterprise beans, you do not need the information in this section. You should use the distributed routing facilities described inDynamic routing with CICSPlex SM.

This section describes how to access the CICSPlex SM workload management facilities directly from an application program. To write such a program, you should be familiar with:

The primary method of invoking CICSPlex SM workload management is by defining module EYU9XLOP to CICS as the dynamic routing program. This causes EYU9XLOP to be invoked by the CICS relay program, allowing CICSPlex SM workload management to make a routing decision about each work request that can be sent to another CICS system.

If necessary, CICSPlex SM workload management can be invoked directly from an application program, without going through the CICS relay program. You can use this interface, from CICS releases before CICS Transaction Server for OS/390 Version 1 Release 3, to workload management to determine the best target region for a dynamic program load (DPL) from a requesting region. The application program you write must follow certain guidelines:

Note:
Accessing workload management through a program that issues an EXEC CICS START command is not recommended with an asynchronous transaction start. Furthermore, EXEC CICS START commands that are not related with either a terminal or a user should not be used for transactions that have affinity relationships, as those relationships cannot be correctly resolved using this interface.

Accessing workload management from a program using a dynamic program load is not supported. CICSPlex SM workload management uses the CICS application programming interface to gather information about the current environment in which it is running. Due to DPL restrictions some of that information will not be available, and unpredictable results may occur.

In order to make a routing decision, CICSPlex SM workload management needs certain information that is normally supplied by the CICS relay program. (The CICS relay program derives the information from data available to CICS for the instance of the transaction being relayed.) When you invoke CICSPlex SM workload management directly, you need to provide this information, including terminal-oriented data and the equivalent of a transaction name to identify the work to be routed.

Related concepts
Dynamic routing with CICSPlex SM
Workload management and dynamic routing
Workload requirements
Related tasks
How to invoke CICSPlex SM workload management
Modifying dynamic routing
Creating a user-replacement module for EYU9WRAM
Related reference
Processing considerations
Sample calling sequence
[[ Contents Previous Page | Next Page Index ]]