IBM came back with an answer. I will be monitoring the CA Dispatch STC.
Should we see this again, we will look at raising its Region size.
Here is their response:
The HASP473 message with RC=0 is primarily informational. The cell
pool get for B32K is from the SAPI SSI which is called by a SAPI
application (CADISPATCH). When the B32K subpool is no longer
expandable, the request is satisfied by doing Getmains for smaller
amounts of storage. This action was implemented as a result of FIN
apar OA06734.
In the case of the B32K subpool, there is no initialization statement
to modify, and the current activity is associated only with the SAPI
application that is making that request.
We have seen this before with SAPI applications using multiple SAPI
threads that are all making requests for the B32K cellpools. Also
occasional $HASP473 RC00 messages may be also be tied to a low region
size so you might want to verify the region size for the SAPI
application is sufficient.
Lizette
>
>Unfortunately, this situation is not that unusual for CA utilities. As we
>discover them, we add something (an additional job step, an MPF exit, etc) to
>force a non-scrollable message to the operator console (or in some cases to
>suppress a non-scrollable message which has no significance).
>
>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
