The usual trick is to recycle the ASID restarting the non-reusable ASIDs, IIRC.
-----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of John Blythe Reid Sent: 10 January 2022 18:12 To: [email protected] Subject: Re: Available ASIDs low and dropping 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 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
