Skip to Content

Defining message exits

This section discusses types of user message exits, how they work, and how the Energizer product helps you configure those exits.

For information about using exits to enable security, see Defining-security-exits or press F1 for online Help. For information about dynamically reloading exits, see Reloading-exits-and-options-dynamically.

Exits are assembler language routines that are used to add customized functionality to the IMS Connect base code. IMS Connect uses exits to load modules, build user tables, and process messages. Exit Services, a component of 

Energizer

, enhances the functionality of IMS Connect by allowing you to perform the following tasks:

  • Create and maintain exits without coding in assembler language (see Virtual exits section in Adding-exits).
  • Define your existing assembler routine exits to Energizer so you can use the advanced features of Energizer(see Customer exits section in Adding-exits).
  • Transfer security from the datastore to IMS Connect (see Defining-security-exits).
  • Reload exits and processing options dynamically without recycling IMS Connect (see Reloading-exits-and-options-dynamically).

Adding message exits with Energizer

You can define customer exits that were written in assembler language, or you can create virtual message exits by using Exit Services.

Types of exits in Energizer

The following exit types are available in Energizer:

  • Virtual exits

    Virtual exits can be created and maintained only by using Energizer. These exits can use all Energizerfeatures. With Exit Services, you can quickly create message exits to handle the following tasks:

    • Translate data between ASCII to EBCDIC format, using standard translation tables

    If you have specific data characteristics–such as encryption–you can specify your translation tables.

    • Perform basic message validation to ensure that the message contains the required information
    • Construct the required OTMA prefixes before sending the message to the datastore
    • Remove the OTMA prefixes from the message that is received from the datastore, so the message can be sent back to the client
    • Provide a unique client identifier when the client does not provide one
Warning

Important

If you create a virtual exit while IMS Connect is running, Energizer adds the new exit to the exit configuration member. You must reload the exit options or recycle IMS connect before the exit is available. Reloading-exits-and-options-dynamically. For information about defining a customer exit, see Adding-exits.

  • Customer exits

    Customer exits are message exits that were written using assembler language. When you have defined these exits to Exit Services (see Adding-exits), you can use the advanced features of Energizer-such as DataStore Routing and dynamically reloading exits.

    Warning

    Important

    Energizer supports Trusted User Support by recognizing the new APPLname added to the standard IRM header and the increased IRM header message length. Energizer also supports PassTickets. For more information, see IMS Connect Guide and Reference.

The following table lists the available Energizer features by exit type:

Energizer features/functions available

Customer exit

Virtual exit

Create message exits without using assembler language

No

Yes

Reload the exits that are defined to Energizer without recycling IMS Connect

Yes

NA

Dynamically update Energizer defined options within IMS Connect, except for message ID and exit names. Those cannot be dynamically updated

Yes

Yes

Add or transfer security to the IMS Connect address space

Yes

Yes

Enable DataStore Routing for messages exits

Yes

Yes

Use the WorkLoad Governor

Yes

Yes

View Statistics

Yes

Yes

Exit Services Configurations

The Exit Services configuration member name field is a 1- to 8-character unique member name that you assign to a set of customer and virtual message exit definitions.

Multiple IMS Connects can use the same Exit Services configuration member. An IMS Connect can specify only one Exit Services configuration member.

 

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

BMC AMI Energizer for IMS Connect 1.9