To be honest I did.
In the past I used each id different, however naming convention allowed
easily guess remaining names.
Example
sysname = HRET, HREV, HREM, etc. multiple systems, not sysplexed
SMF ID = RET1, REV1, REM1, etc.
NJE node = NRET, NREV, NREM, etc.
sysplex = HRETPLEX or HRET - that was future. And for future sysplex
members HR2T, HR3T...
Standard LPAR for HRET was LHRET. XHRET for DRP machine.
(it is not full list)
It wasn't pretty, but it was well documented and only one letter was
important.
Why not use same name whenever possible? Well, the idea was to know for
sure which of the IDs is displayed. It was intuitive.
--
Radoslaw Skorupka
Lodz, Poland
W dniu 11.02.2023 o 21:00, Rob Schramm pisze:
oh.. on that I agree. I have always thought that it was silly to have a
sysname that didn't match or in some cases is related to in any way the
SMFID... but I see it alot.
I would love a reason from someone that kept sysname <> smfid.
Rob
On Sat, Feb 11, 2023 at 2:44 PM Radoslaw Skorupka <
00000471ebeac275-dmarc-requ...@listserv.ua.edu> wrote:
As far as I understand the question is "what is the difference between
SMF ID and SYSNAME".
Or rather "Why on Earth have two identifiers, while there is always 1:1
correlation".
I agree, I see no reason to have SMF ID and sysname independent.
Among meny identifiers I can explain the purpose of JES2 NODE name, MAS
member name, LPAR name, TCPIP hostname, sysplex name, etc.
However I would like to know the reason if it exist.
My €0.02
--
Radoslaw Skorupka
Lodz, Poland
W dniu 10.02.2023 o 17:15, Matt Hogstrom pisze:
I’m doing some research involving historical SMF data. It’s caused me
to wonder how engineers use the &SYSNAME, &LPARNAME and &SMFID symbols.
From what I can see is that in most instances they are the same. LPARNAME
appears to me to have little value in that if may or may not have an
affinity for a z/OS guest in terms of naming.
&SMFID and &SYSNAME seem to generally correlate. I’m curious if there
are use cases where these are different and what the purpose might be?
Appreciate any insight / best parties that people are using.
Matt Hogstrom
m...@hogstrom.org
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
