A user ASP overflow should require an IPL to reset the status no matter what. Clearing space and moving data shouldn’t reset the status.
For example, you could delete objects from the ASP to make sufficient space available, save the object (or objects) that caused the overflow, delete the overflowing object, then restore the object. The newly restored version should fit within the user ASP, but ASP status shouldn’t change. (It might be worth a try on recent releases, though.)
However, you <i>might</i> be able to avoid overflows in the future <b>if</b> you can take advantage of the CHGASPA CPRRCYPCY() parameter for the user ASP.
The attribute must be set before overflow occurs.