Hi Al! (et al)
I’ve also asked for eg 02-12345 to be added – quite a while ago. I also was
turned down. But then I’m not a customer…
Cheers, Martin
From: IBM Mainframe Discussion List on behalf of Al
Sherkow
Date: Tuesday, 14 February 2023 at 16:39
To: IBM-MAIN@LISTSERV.UA.EDU
Subject:
I had problems to solve to combine old SMF records (0/IPL, 90(5A)/System
Status) when 4-char SMFID/SYSPLEX/SYSNAME are duplicated on different machines
as the CPUTYPE and serial number are not in most of the SMF records. I did ask
IBM to add those to the SMF header some time ago. I think
The SMF id goes back to the SMF option of OS/360.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Peter Relson [rel...@us.ibm.com]
Sent: Monday, February 13, 2023 8:34
It goes back to OS/360.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Lennie Dymoke-Bradshaw [032fff1be9b4-dmarc-requ...@listserv.ua.edu]
Sent: Tuesday, February
That was educational
Thanks Al!
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Al
Sherkow
Sent: Monday, February 13, 2023 10:23 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Question on use of LPARNAME, SYSNAME and SMFID
The 4-char SMFID has been around a very long
Interesting.
I remember the SMFid being around on MVS 3.7 and 3.8. The Sysname (CVTSNAME)
became more important with the advent of Sysplex so I probably remember
using it from then. Wikipedia has MVS/SP dated as 1980. It was preceded by
MVS/SE and before that by MVS 3.8. I don't think I used
On 2/13/2023 7:23 PM, Al Sherkow wrote:
I don’t think this happens anymore, but also long ago a machine could be
significantly changed and keep the same serial number to make software
licensing simpler. (For example, replacing a 3033 with a 3090). Keeping the
CPUTYPE and the serial number
The 4-char SMFID has been around a very long time. This field is in the header
of SMF records at offset=14 (SMF70SID), SMF0SID, etc.).
SYSNAME and SYSPLEX were added to many SMF records with MVS/ESA 5.1.0 (as
documented in MXG with change 12.034 on Feb 14, 1994). LPARNAME was added in
1988
>I think the SMFID is older than SYSNAME. I think SYSNAME dates from the late
>80s or 90s, whereas SMFID was in the early versions of MVS.
System symbols are only 30 years old, but system name (via CVTSNAME) has
existed since at least MVS/SP1.3 (no later than 1977).
SMF ID (SMCASID) appears to
I think that they are not different for that very reason in most shops. Fear of
making a mistake on the HMC or elsewhere.
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Scott Chapman
Sent: Saturday, February 11, 2023 7:46 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject:
While SYSNAME is often not the same as SMFID (such as when customers find a
productive use of the extra 4 characters available for system name), many
create their SMFID using some part of the sysname, such as by using a substring
expression of That would fall under "is related to".
Peter
I think the SMFID is older than SYSNAME. I think SYSNAME dates from the late
80s or 90s, whereas SMFID was in the early versions of MVS.
Lennie Dymoke-Bradshaw
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Rob
Schramm
Sent: 11 February 2023 20:01
To:
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
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 <
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
Some of this used to be more helpful for the suplex data sets that were
tied to the hardware like the coupling facility stuff. And it comes into
play when you restoring on hardware that you want to switch to a different
data set and have it automatically come up. Brain cell too may have been
> the , and symbols.
FWIW, the latter two are not symbols that z/OS provides. Obviously a customer
could create them.
The LPARNAME can be used as a filter in processing of the IEASYMxx parmlib
member (and others), as can HWNAME and VMUSERID
Peter Relson
z/OS Core Technology Design
In almost all instances I’ve seen the word ‘PLEX’ is in the variable
in some form or another. PRODPLEX, PLEXA1, …
Matt Hogstrom
m...@hogstrom.org
+1-919-656-0564
PGP Key: 0x90ECB270
Facebook LinkedIn
Twitter
Having looked at data from a whole lot of customer systems, I can say that
SMFID and SYSNAME are often (but not always) the same. LPARNAME is very often
different, although I appreciate it when there's at least some sort of visual
link between it and SMFID/SYSNAME. E.G. SYSA and C1SYSA vs SYSA
Thanks to all that responded so far. I expected that there is a lot of history
behind the decisions and that makes the decisions persistent and difficult to
change. Although, as Ed pointed out, being able to be confident because of
different values is useful, it’s probably not an option to
Hi,
We use different lpar names for our base systems and recovery system. And
we use that variable to choose the IPL sequence for each situation. As for
smfid and sysname, yes, they usually tend to be the same.
Regards
Jack
On Fri, Feb 10, 2023, 16:16 Matt Hogstrom wrote:
> I’m doing some
On 2/10/2023 8:15 AM, Matt Hogstrom wrote:
I’m doing some research involving historical SMF data. It’s caused me to wonder how
engineers use the , and 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
Matt
Of course the big difference is that SMFID is 4 characters and SYSNAME is 8
I know that software vendors often run QA on systems where all three (incl
LPARNAME) are deliberately different to catch any assumptions made in code or
product sample JCL.
I have seen customers using different
I’m doing some research involving historical SMF data. It’s caused me to
wonder how engineers use the , and 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
24 matches
Mail list logo
