On two of our systems we are/were running with ESQA at 112% and hence ECSA
converted. Last weekend one of those systems was finally migrated to 1.8 and I
was finally able to convince the powers that be that ESQA should be increased
so that we're not converting ECSA anymore (which isn't all
On Fri, 28 Sep 2007 11:15:20 +0200, Barbara Nitz [EMAIL PROTECTED] wrote:
You can override the severity of the check, IIRC. But for this
one-time-expected change I should not be required to override a lot of checks.
In a perfect world, perhaps.
You don't *have to* override anything. It's
Barbara's complaint is noted, but does not apply across every shop, of
course.
When we went to z/OS 1.7 last year, we increased ECSA. No problem on our
test systems, where 1.7 lived for months of testing before migrating. All
was well, until we got to Prod. Suddenly a problem surfaced that
PROTECTED]
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of
Barbara Nitz
Sent: 28 September 2007 07:52
To: IBM-MAIN@BAMA.UA.EDU
Subject: Health CHECK(IBMVSM,VSM_PVT_LIMIT)/VSM_SQA_THRESHOLD
On two of our systems we are/were running with ESQA
Rob,
When I was a sysprog, this check would have been invaluable on many occasions
- (production ASIDs falling over on Monday at 11am because someone changed
the LPA list at the weekend and squeezed PVT).
I am NOT saying that this check is bad. As long as all else is equal! It can
well be a
5 matches
Mail list logo
