Skip to Content

Default SUITE assignment rules

When Universal Information Exchange processes information about each individual active task, it checks all the SUITE commands that you have specified in the order that they are encountered in the command file.

If the particular task matches the SUITE definition rules, then the SUITE name is assigned to the task and then parsing of the command file stops.

Related topics

Getting-started

UIE-concepts

If the particular task does not match any SUITE command, then the SUITE name is assigned to the task by the following default rules:

  • Service Class name

  • If you have input subsystem data to the UIE batch job, UIE automatically separates each subsystem type into different SUITES, if the task is recognized by UIE as one of transaction processing subsystems. To review an example, see Example 5—Using the SUITE command.

    UIE can automatically recognize the following subsystems:

    • CICS, Db2, Db2 Standalone Utilities, IMS, IMS Utilities, IRLM, MQ, OMVS (Unix System Services) HTTP Server (WEB Server), CICS Utilities, and WebSphere Application Server (WAS).

By default, the SUITE name is assigned to the task as follows:

  • If the task is recognized by UIE as one of the subsystems listed earlier, it is assigned the following SUITE name:

    <ServiceClassName>_<SubsystemType>

  • If the task is not recognized as one of the subsystems, the SUITE name is assigned:

    <ServiceClassName>
Warning

Example

If you have Service Class, STCPROD, which contains some IMS regions, CICS regions, and some other started tasks (STCs), UIE creates by default the following SUITES:

STCPROD_IMS
STCPROD_CICS
STCPROD

The last SUITE contains all started tasks (STCs) that are not CICS and IMS regions.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

Universal Information Exchange 2.3