When running on CICS®, the behavior of the storage tuning user exit could be as follows:

• At the region initialization call, the storage tuning user exit allocates and initializes a table that has storage tuning information for the load modules it wants to tune.

  The storage tuning user exit would need to know which load modules it wants to tune and it would need to find the storage values it wants to use for each load module. These values could be in the storage tuning user exit itself as constants, or could be in a file.

• At the new load module call, the storage tuning user exit would do a lookup in the table to see if the load module has storage tuning information. If it does, the load module is enabled for storage tuning and the storage tuning information is provided back to Language Environment.
• At the enclave initialization call, the storage tuning user exit would do a lookup in the table for the storage tuning information and the storage tuning information is provided back to Language Environment.
• At the region termination call, the storage tuning user exit frees any resources it acquired.