Re: What happens when the ASP threshold value in System Service Tools is exceeded?

On 02-Feb-2015 12:48 -0600, rob@xxxxxxxxx wrote:

First, I am not talking about the values shown in WRKSYSVAL QSTGLOW*.
I am talking about:
STRSST
3. Work with disk units
2. Work with disk configuration
3. Work with ASP threshold

Second, I am talking about a single ASP shop.

Now, I seem to remember back when we were still running SNADS that
some items would shut down if this was exceeded. Is there some place
where this is documented? All I read now is that some system message
is sent. Perhaps they considered SNADS shutting itself down was
independent. That SNADS was doing it's own checking for that system
message and shutting itself down.

So, I repeat, is there someplace where it is documented what the
ramifications of exceeding this value are?

Other than the SNA/DS, I am unaware of anything in the OS or IBM LPP that is coded to self-inhibit according to solely\directly that threshold. I am unaware of and was unable to find any [TechNote or other] document that attempts to describe what effects and various implementations that exist [in the OS and\or LPPs], as dependencies on that ASP threshold setting.

Each feature [of the OS or an LPP] should document, both if there are any dependencies on the ASP Storage Threshold and what means they provide to configure any customizable options\effects. A poorly documented feature might depend solely on their messaging that diagnoses whatever is the effect on that particular feature, when\since that threshold has been exceeded, and possibly also any automatic recovery after\since that threshold is no longer exceeded; any feature poorly documented in that way, hopefully would be subject of a reader-comment asking the documentation be updated to provide the necessary details so as not to have to find out after-the-fact.

Searching the KnowledgeCenter I found that Disk Watcher, SNA/DS, and possibly Virtual Tape [though seems its threshold is endemically defined with no ties to the value defined in SST] may have dependencies, but each with a unique implementation. The Add Disk Watcher Definition (ADDDWDFN) and the Add Job Watcher Definition (ADDJWDFN) commands, for example, have the System ASP Threshold (SYSASPTHLD) [and each has another parameter similarly] for which the special value of *SYSTEM can ask to refer to the established ASP Threshold instead of an explicitly specified numeric\integer percentage.

FWiW: That any particular feature [OS, LPP, or 3rd party] might [eventually decide to] impose any restrictions and might also have any custom means to avoid or configure the impact of those restrictions, impedes documenting the possible effects from the perspective of the Threshold setting.