Why does ObjectStar / Object Service Broker sometimes terminate with the z/OS message: IEF352I ADDRESS SPACE UNAVAILABLE

Why does ObjectStar / Object Service Broker sometimes terminate with the z/OS message: IEF352I ADDRESS SPACE UNAVAILABLE

book

Article ID: KB0092358

calendar_today

Updated On:

Products Versions
TIBCO ObjectStar Integration Foundation -
Not Applicable -

Description

Resolution:
Description:

"IEF352I ADDRESS SPACE UNAVAILABLE"  is a normal message issued by z/OS when an address space that had been used to provide services to other address spaces through space-switching PC routines under z/OS Cross Memory Services, terminates. z/OS arbitrarily prevents reuse of the address space in order to ensure system integrity. By doing so, other address spaces cannot reuse links previously established to gain access to the terminating address space and its contents.

Although this is a normal situation, later releases of z/OS provide new techniques that can be used to prevent loss of address spaces while providing similar Cross Memory communications function. Such changes require modification to the affected application software.

Environment:
z/OS systems where Cross Memory Communications are being employed.

TIBCO Products Affected:
TIBCO ObjectStar Integration Foundation for z/OS 4.x
TIBCO Mainframe Integrator for z/OS 4.x
TIBCO Object Service Broker for z/OS 5.0.0


Operating System(s) impacted:
z/OS (all levels)


Symptoms:
When ObjectStar address spaces terminate, z/OS may issue the console message:
   IEF352I ADDRESS SPACE UNAVAILABLE
The address space then becomes unusable until an Initial Program Load (IPL) is performed. Customer may eventually notice a loss of available and active address spaces.


Resolution:
There is no resolution at present. Customers experiencing this issue should open a service request with TIBCO Support and request tracking of enhancement request CR 1-93P4SC. At present, ObjectStar cannot execute in address spaces started with "REUSASID=YES".   Use of the z/OS option "REUSASID=YES" is presently not supported and will not resolve this problem.

As a workaround, z/OS should be configured with sufficient address spaces to continue running until a regularly scheduled IPL can be performed.

Issue/Introduction

Why does ObjectStar / Object Service Broker sometimes terminate with the z/OS message: IEF352I ADDRESS SPACE UNAVAILABLE