The issue with checksums and explanations was clearly explained by
Edward King (thank you!).
Of course this is rather minor issue, because besides source file
editing there is possibility to add explanations to just submitted file.
However the problem of dummy LPAR causing explanation requirement is
more interesting. Besides technical details of "dummy" there is also
formal/legal one: A customer has right to shut down the system. To
simplify let's assume the system was not left active after Z EOD, but
VARY XCF,OFFLINE was issued and/or Reset from HMC. Is it proper method
to close the system *from SCRT reporting point of view*? I assume yes,
otherwise I would like to have other method documented.
However customer has right to close the system (including V XCF and/or
Reset) and he should not be forced to explain it as exceptional issue,
because it is not exception. It is normal usage.
Note there is nothing about lack of SMF data. The data simply do not
exist, because it was never generated. Customer provides 100% of
generated (and collected) SMF data to the SCRT tool.
--
Radoslaw Skorupka
Lodz, Poland
W dniu 27.02.2023 o 20:26, Martin Packer pisze:
Hi Al!
Re “ I don't recall how a CF LPAR using GCPs showed up.” It shows up with
logical processors in Pool 1 (GCP Pool). It’s discernable as a CF LPAR using
SMF 74-4 which contains Serial and LPAR Number, amongst other identifying
things.
It’s rare I see it but I DO see it.
Cheers, Martin
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of Al
Sherkow <a...@sherkow.com>
Date: Monday, 27 February 2023 at 17:35
To: IBM-MAIN@LISTSERV.UA.EDU <IBM-MAIN@LISTSERV.UA.EDU>
Subject: Re: [EXTERNAL] Re: SCRT and not operating LPAR
Interesting thread. I thought I would add a few points.
REGARDING the checksum: Of course we don't know exactly what the checksum is
checking, but it is reasonable to assume it is the billable MSUs, CPU
consumption that SCRT calculates. That would be:
E5 section in machine level MSU reports,
B5 section in Country Multiplex MSU reports,
B5 section in Tailored Fit Reports,
I expect there are other assorted things checked to be certain that sites only
change fields that sites should be changing. Sites are supposed to change
(required) to whatever the explanation is. These cells will not be in the
checksum. Sites can change these before or after using the LMS interface to
submit their reports.
REGARDING missing data.
SCRT V25 in 2017 replaced the 95% coverage calculation with the 1 hour gap reporting in
H4 and H6 sections. Generally these use the cross LPAR reporting to determine if an LPAR
is consuming CPU time. (Each LPAR in the SMF70 data has data on all the other LPARs on
the machine, including CPU time. This can be controlled for environments like service
bureaus where you don't want one customer seeing another customer's usage). This thread
is indicating that LPARs not IPL'd but still "active" are being marked for
(required) explanations. I haven't looked in detail recently but the SMF data also
includes SMF70SPN (LPAR CLUSTER, which for z/OS is the SYSPLEX) and the SMF70STN (8-char
SYSNAME of z/OS) of the other LPARs. I used these fields to determine if the LPAR was
running z/OS. VM images showed up differently; I don't recall how a CF LPAR using GCPs
showed up.
Al Sherkow
I.S. Management Strategies, LTD.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
