John

It is not as easy as just using "REUSASID=YES" on start commands and I would 
not advise randomly starting system software address spaces with that parameter 
to "see what happens".

The most likely reason (**) for IEF352I is that the offending address space 
established a PC-ss with a system linkage index (LX) and therefore has an 
implicit cross-memory bind to every address space in the system. When this 
address space terminates, the system must therefore mark the address space 
non-reusable to preserve system integrity.
The server code can request a reusable system-LX so that the IEF352I situation 
does not occur, however all clients invoking the PC routine must now specify a 
special sequence number (in the HH of R15) along with the PC number.

So the bottom line is that REUSASID=YES will only help if the code causing 
IEF352I has been updated to support reusable system LX. If ADABAS supports 
REUSASID=YES, then the vendor may have documented it in the manuals (or you 
might have to raise a support ticket to ask them).

The next thing that springs to mind is  - why do you stop/restart ADABAS every 
week? Surely modern versions of database software support continuous 
availability these days - maybe another question for the vendor.

Peter Relson has presented many times on the "ASN and LX Reus Facility" over 
the years - I am sure that there is something out there on the internet.

(*) Both DB2 and MQ do NOT currently support (AFAIK) client callers from 
REUSASID=YES address spaces.

(**) Note that there are other instances where there are servers with PC-ss 
with non-system LX and client address spaces have to explicitly "connect" to 
the server. When these server ASIDs terminate with IEF352I, the ASID can be 
reclaimed once every client address space terminates and there are no more 
outstanding cross-memory links. This technique is not as commonplace as 
system-LX PC-ss.

Rob Scott
Rocket Software

-----Original Message-----
From: IBM Mainframe Discussion List <[email protected]> On Behalf Of 
John Blythe Reid
Sent: 10 January 2022 11:12
To: [email protected]
Subject: Re: Available ASIDs low and dropping

EXTERNAL EMAIL





Thanks Rob, Robin,

It was the IEA_ASIDS healthcheck that triggered the alert.

In this case it's due to recycling ADABAS regions. They do it weekly and each 
region terminates with this message:

IEF352I ADDRESS SPACE UNAVAILABLE

MXI currently shows this, so you can see that there's not long to go:

 Address Space Definitions
 Maximum Defined                   500
 Reserved Non-Reusable        500
 Reserved Start Commands        5

 Address Space Type        Number  Percentage
 Available For Use             29           2
 Marked Not-Reusable       816          81
 Started Tasks Active         111          11
 Batch Jobs Active                7           0
 TSO Users Active                 2           0
 Initiators Active                   39           3

I notice this suggestion in the IBM documentation:

An address space that becomes nonreusable when it terminates (that is, message 
IEF352I ADDRESS SPACE UNAVAILABLE is issued when the address space terminates) 
should be considered for using a reusable ASIDs. Specify REUSASID=YES on the 
START command for the address spaces or specify ATTR=(REUSASID) on the ASCRE. 
Investigate and remediate any 0D3 abends that result from the use of a reusable 
ASID.

I don't like the look of those 0D3 abends though.

Any thoughts on this ?

Regards,
John.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
[email protected] with the message: INFO IBM-MAIN

================================
Rocket Software, Inc. and subsidiaries ■ 77 Fourth Avenue, Waltham MA 02451 ■ 
Main Office Toll Free Number: +1 855.577.4323
Contact Customer Support: 
https://my.rocketsoftware.com/RocketCommunity/RCEmailSupport
Unsubscribe from Marketing Messages/Manage Your Subscription Preferences - 
http://www.rocketsoftware.com/manage-your-email-preferences
Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy
================================

This communication and any attachments may contain confidential information of 
Rocket Software, Inc. All unauthorized use, disclosure or distribution is 
prohibited. If you are not the intended recipient, please notify Rocket 
Software immediately and destroy all copies of this communication. Thank you.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to