Hallo Dieter,
vielleicht hilft die das auf die Sprünge...

Each time a temporary object is created, it uses a unique temporary address. The system has a very large but finite number of addresses available. Percent of temporary addresses indicates the percentage of those addresses used. If that number reaches 100 percent, the system abnormally terminates and requires a scratch installation from backup tapes. Many systems typically have a low % of temp addresses used. However, rapid use of temporary addresses can occur and is typically a sign of application(s) creating temporary objects at an abnormally high rate . Programs that use heap space can use an address for each 16MB of heap in the same thread. Each thread or activation group uses a new address. Query can use temporary addresses for internal processing of joins and sorts. Some API calls can create temporary space that would use one or more temporary address. The best course of action to reduce the number of temporary addresses used is to change the application that is using them. Perhaps the application can be re-written to have one job or one set of jobs handle multiple requests rather than starting a new job for each request. Or, perhaps the application can re-use the same temporary space by clearing and loading it with new data rather than deleting and creating new ones. Message CPI0997 is issued when nearly all available machine addresses used. The text indicates the following: Message . . . : Nearly all available machine addresses used. Cause . . . . . : Nearly all available machine addresses have been used for reason &1. If the percentage of addresses used reaches 100 percent, the system will end abnormally. See reason &1 shown below: 1 - At least &2 percent of the maximum possible addresses for permanent objects have been used. 2 - At least &3 percent of the maximum possible addresses for temporary objects have been used. Recovery . . . : See reason &1 shown below: 1 - Contact your service representative. 2 - Schedule an IPL to allow the system to reset the temporary addresses. The reset of the temporary addresses will have minimal impact on the scheduled IPL. Note: Temporary and permanent storage each have 2** 38 addresses available (2 to the 38th power is 274,877,906,944). New in V5R3M0: In Version 5 Release 3 of the operating system, an IPL resets the temporary addresses if the percentage used is above 85 percent. As long as the system is IPLed before the percentage of temporary addresses reaches 100 percent, a scratch installation can be prevented. Performance Explorer may be needed to analyze temporary address growth and may require a consulting agreement accordingly.