Re: Question on use of LPARNAME, SYSNAME and SMFID

[Martin Packer]

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: [EXTERNAL] Re: Question on use of LPARNAME, SYSNAME and SMFID
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 through 
DeveloperWorks, or perhaps through ISV relations. That was turned down. I 
understand it is kind of an "edge case" that doesn't impact many customers.

Certainly it occurs for many sites during DR exercises. Clearly ASYS could move 
from one machine to another. That will cause an SMF90 subtype 7 if the site 
using "Z EOD" command on the original machine and SMF0 for the IPL on the new 
machine. The reverse occurs when ASYS moves back to the original, non-DR 
hardware.

With Country Multiplex Pricing, depending on how the site does their DR 
Exercises, all these moves need to be understood. So lots of merging of 
SMFID/SYSPLEX/SYSNAME with timestamps to track these events on the proper 
hardware.

Al

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Unless otherwise stated above:

IBM United Kingdom Limited
Registered in England and Wales with number 741598
Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Question on use of LPARNAME, SYSNAME and SMFID

[Al Sherkow]

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 through 
DeveloperWorks, or perhaps through ISV relations. That was turned down. I 
understand it is kind of an "edge case" that doesn't impact many customers. 

Certainly it occurs for many sites during DR exercises. Clearly ASYS could move 
from one machine to another. That will cause an SMF90 subtype 7 if the site 
using "Z EOD" command on the original machine and SMF0 for the IPL on the new 
machine. The reverse occurs when ASYS moves back to the original, non-DR 
hardware. 

With Country Multiplex Pricing, depending on how the site does their DR 
Exercises, all these moves need to be understood. So lots of merging of 
SMFID/SYSPLEX/SYSNAME with timestamps to track these events on the proper 
hardware. 

Al

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Question on use of LPARNAME, SYSNAME and SMFID

[Seymour J Metz]

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 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Question on use of LPARNAME, SYSNAME and SMFID

>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 predate even that.

It remains the case that, of the three items in the subject, only  is 
defined as a system symbol by z/OS.

Peter Relson
z/OS Core Technology Design


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Question on use of LPARNAME, SYSNAME and SMFID

[Seymour J Metz]

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 14, 2023 4:19 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Question on use of LPARNAME, SYSNAME and SMFID

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 MVS/SP until
1982ish.

Lennie

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of
Peter Relson
Sent: 14 February 2023 01:34
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Question on use of LPARNAME, SYSNAME and SMFID

>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 predate even that.

It remains the case that, of the three items in the subject, only 
is defined as a system symbol by z/OS.

Peter Relson
z/OS Core Technology Design


--
For IBM-MAIN subscribe / signoff / archive access instructions, send email
to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Question on use of LPARNAME, SYSNAME and SMFID

[Burgess, Otto A. (CTR)]

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 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 with PRSM. I think the OS was ESA/390 on 3090 hardware.

For some expert witness work I did in the early 90s I began identifying MVS 
images with the 4-char SMFID from offset 14, the CPUTYPE (SMF70MOD) and the 
serial number (SMF70SER). 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 handled that condition. 

This worked well, and I implemented the same image tracking when I wrote LCS 
(https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.sherkow.com%2Flcs%2F=05%7C01%7COtto.Burgess%40opm.gov%7Cddb2470d86ff454f69f108db0e3ad95a%7C844ef9977b6348f0882a7dc8162e363b%7C0%7C0%7C638119418160619162%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=wRs69%2FjBQ%2FUjJ3ZSxFLuwiYoNVog8wy6tbekD5nEli0%3D=0)
 to help sites audit SCRT in 2002. One customer eventually showed me that more 
information was required. They had two 4-char SMFIDs 'ASYS' on the same machine 
in different LPARs simultaneously! That totally broke my software. I called Bob 
Rogers at IBM to ask what was happening and what didn't I understand. He said 
"they must have different 8-char SYSNAMEs, as that is how Parallel Sysplex 
keeps those two 'ASYS' separate." Eye opening for me... I had to add SYSPLEX 
and SYSNAME to completely identify images. I was auditing SCRT, so I determined 
I needed to add LPARNAME also. A particular 4-char SMFID, SYSNAME, SYSPLEX 
could be in two different LPARs on a machine during the month (not 
simultaneously) and I needed to keep them separate. (Later recognized they 
needed LPARNAME to properly merge SMF70 and SMF89 and in 2007 APAR OA20314 
added the LPARNAME to the SMF89 record.)

Most of my licensees have 4-char SMFID=SYSNAME.  I have a few customers where 
they are different. As others have written some sites have found interesting 
uses for the extra four characters in SYSNAME. 

Al Sherkow, I/S Management Strategies, Ltd.
+1 414 332-3062
https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.sherkow.com%2F=05%7C01%7COtto.Burgess%40opm.gov%7Cddb2470d86ff454f69f108db0e3ad95a%7C844ef9977b6348f0882a7dc8162e363b%7C0%7C0%7C638119418160619162%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=gc679rVXx5DOSWAZKuuWI4HY5eXuEfP8kctp1ge8fnw%3D=0

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Question on use of LPARNAME, SYSNAME and SMFID

[Lennie Dymoke-Bradshaw]

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 MVS/SP until
1982ish. 

Lennie

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of
Peter Relson
Sent: 14 February 2023 01:34
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Question on use of LPARNAME, SYSNAME and SMFID

>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 predate even that.

It remains the case that, of the three items in the subject, only 
is defined as a system symbol by z/OS.

Peter Relson
z/OS Core Technology Design


--
For IBM-MAIN subscribe / signoff / archive access instructions, send email
to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Question on use of LPARNAME, SYSNAME and SMFID

[Ed Jaffe]

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 handled that condition.


If you order an MES upgrade on a supported path, you can keep your 
serial number when going from one CPC type to another.


You cannot keep the CPC type. That is an inherent attribute of both the 
new machine and the older one you're replacing...



--
Phoenix Software International
Edward E. Jaffe
831 Parkview Drive North
El Segundo, CA 90245
https://www.phoenixsoftware.com/



This e-mail message, including any attachments, appended messages and the
information contained therein, is for the sole use of the intended
recipient(s). If you are not an intended recipient or have otherwise
received this email message in error, any use, dissemination, distribution,
review, storage or copying of this e-mail message and the information
contained therein is strictly prohibited. If you are not an intended
recipient, please contact the sender by reply e-mail and destroy all copies
of this email message and do not otherwise utilize or retain this email
message or any or all of the information contained therein. Although this
email message and any attachments or appended messages are believed to be
free of any virus or other defect that might affect any computer system into
which it is received and opened, it is the responsibility of the recipient
to ensure that it is virus free and no responsibility is accepted by the
sender for any loss or damage arising in any way from its opening or use.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Question on use of LPARNAME, SYSNAME and SMFID

[Al Sherkow]

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 with PRSM. I think the OS was ESA/390 on 3090 hardware.

For some expert witness work I did in the early 90s I began identifying MVS 
images with the 4-char SMFID from offset 14, the CPUTYPE (SMF70MOD) and the 
serial number (SMF70SER). 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 handled that condition. 

This worked well, and I implemented the same image tracking when I wrote LCS 
(https://www.sherkow.com/lcs/) to help sites audit SCRT in 2002. One customer 
eventually showed me that more information was required. They had two 4-char 
SMFIDs ‘ASYS’ on the same machine in different LPARs simultaneously! That 
totally broke my software. I called Bob Rogers at IBM to ask what was happening 
and what didn’t I understand. He said “they must have different 8-char 
SYSNAMEs, as that is how Parallel Sysplex keeps those two ‘ASYS’ separate.” Eye 
opening for me… I had to add SYSPLEX and SYSNAME to completely identify images. 
I was auditing SCRT, so I determined I needed to add LPARNAME also. A 
particular 4-char SMFID, SYSNAME, SYSPLEX could be in two different LPARs on a 
machine during the month (not simultaneously) and I needed to keep them 
separate. (Later recognized they needed LPARNAME to properly merge SMF70 and 
SMF89 and in 2007 APAR OA20314 added the LPARNAME to the SMF89 record.)

Most of my licensees have 4-char SMFID=SYSNAME.  I have a few customers where 
they are different. As others have written some sites have found interesting 
uses for the extra four characters in SYSNAME. 

Al Sherkow, I/S Management Strategies, Ltd.
+1 414 332-3062
www.sherkow.com

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Question on use of LPARNAME, SYSNAME and SMFID

[Peter Relson]

>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 predate even that.

It remains the case that, of the three items in the subject, only  is 
defined as a system symbol by z/OS.

Peter Relson
z/OS Core Technology Design


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Question on use of LPARNAME, SYSNAME and SMFID

[Burgess, Otto A. (CTR)]

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: Re: Question on use of LPARNAME, SYSNAME and SMFID

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 and C1LP4. Most 
sites do tend to have that sort of link between them, but some don't. It seems 
like that would make it easier to make a mistake while working on the HMC. 

There's a whole lot of PRODPLEX and SYSA and similar out there. But there's 
also a fair number of more creative names too. 

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Question on use of LPARNAME, SYSNAME and SMFID

[Peter Relson]

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 Relson
z/OS Core Technology Design


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Question on use of LPARNAME, SYSNAME and SMFID

[Lennie Dymoke-Bradshaw]

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: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Question on use of LPARNAME, SYSNAME and SMFID

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 < 
0471ebeac275-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 ,  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 terms of naming.
> >
> >  and  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
> >
> > A generalist knows less and less about more and more till he knows
> nothing about everything
> > A specialist knows more and more about less and less till he knows
> everything about nothing
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send 
> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Question on use of LPARNAME, SYSNAME and SMFID

[Radoslaw Skorupka]

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 <
0471ebeac275-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 ,  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 terms of naming.

 and  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

Re: Question on use of LPARNAME, SYSNAME and SMFID

[Rob Schramm]

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 <
0471ebeac275-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 ,  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 terms of naming.
> >
> >  and  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
> >
> > A generalist knows less and less about more and more till he knows
> nothing about everything
> > A specialist knows more and more about less and less till he knows
> everything about nothing
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Question on use of LPARNAME, SYSNAME and SMFID

[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 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 ,  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 terms of naming.

 and  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

A generalist knows less and less about more and more till he knows nothing 
about everything
A specialist knows more and more about less and less till he knows everything 
about nothing


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Question on use of LPARNAME, SYSNAME and SMFID

[Rob Schramm]

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
lost in in the years but it was done because the Dr hardware was different
than the production hardware.  So we used the LPARNAME to help resolve the
sysplex data sets by use of the CEC.  At least that's how I think it used
to work.

Me personally I never try to discount a symbol until I get stuck with
having to use it. VBG

Rob

On Sat, Feb 11, 2023, 08:26 Matt Hogstrom  wrote:

> 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 <
> https://linkedin/in/mhogstrom>  Twitter 
>
> “It may be cognitive, but, it ain’t intuitive."
> — Hogstrom
>
>
>
> > On Feb 11, 2023, at 1:46 PM, Scott Chapman <
> 03fffd029d68-dmarc-requ...@listserv.ua.edu> wrote:
> >
> > There's a whole lot of PRODPLEX and SYSA and similar out there. But
> there's also a fair number of more creative names too.
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Question on use of LPARNAME, SYSNAME and SMFID

[Peter Relson]

> 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


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Question on use of LPARNAME, SYSNAME and SMFID

[Matt Hogstrom]

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 

“It may be cognitive, but, it ain’t intuitive."
— Hogstrom



> On Feb 11, 2023, at 1:46 PM, Scott Chapman 
> <03fffd029d68-dmarc-requ...@listserv.ua.edu> wrote:
> 
> There's a whole lot of PRODPLEX and SYSA and similar out there. But there's 
> also a fair number of more creative names too. 


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Question on use of LPARNAME, SYSNAME and SMFID

[Scott Chapman]

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 and C1LP4. Most 
sites do tend to have that sort of link between them, but some don't. It seems 
like that would make it easier to make a mistake while working on the HMC. 

There's a whole lot of PRODPLEX and SYSA and similar out there. But there's 
also a fair number of more creative names too. 

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Question on use of LPARNAME, SYSNAME and SMFID

[Matt Hogstrom]

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 many.  Broadcom also 
makes an  available with is interesting for historical purposes but 
hardly a value that has merit apart from historical investigation.  My current 
thinking is to simply take the  as a combination 
going forward so that I’ve preserved all three and gained the benefit of the 
use of a difference between  and   

If anyone has other thoughts I’m all ears. 

Thanks!

Matt Hogstrom
m...@hogstrom.org




> On Feb 10, 2023, at 5:42 PM, Rob Scott  wrote:
> 
> 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 values for SMFID and when queried I am 
> normally told that it relates to historical chargeback and accounting (and 
> very possible that the reasons for it are forgotten/lost).
> 
> Rob Scott
> Rocket Software


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Question on use of LPARNAME, SYSNAME and SMFID

[Jack Zukt]

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 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 terms of naming.
>
>  and  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
>
> A generalist knows less and less about more and more till he knows nothing
> about everything
> A specialist knows more and more about less and less till he knows
> everything about nothing
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Question on use of LPARNAME, SYSNAME and SMFID

[Ed Jaffe]

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 may not have an affinity for a z/OS guest in terms of naming.


We ensure all three names are different to minimize confusion about 
which one you are seeing displayed to you.


That applies to JES member names as well...


--
Phoenix Software International
Edward E. Jaffe
831 Parkview Drive North
El Segundo, CA 90245
https://www.phoenixsoftware.com/



This e-mail message, including any attachments, appended messages and the
information contained therein, is for the sole use of the intended
recipient(s). If you are not an intended recipient or have otherwise
received this email message in error, any use, dissemination, distribution,
review, storage or copying of this e-mail message and the information
contained therein is strictly prohibited. If you are not an intended
recipient, please contact the sender by reply e-mail and destroy all copies
of this email message and do not otherwise utilize or retain this email
message or any or all of the information contained therein. Although this
email message and any attachments or appended messages are believed to be
free of any virus or other defect that might affect any computer system into
which it is received and opened, it is the responsibility of the recipient
to ensure that it is virus free and no responsibility is accepted by the
sender for any loss or damage arising in any way from its opening or use.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Question on use of LPARNAME, SYSNAME and SMFID

[Rob Scott]

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 values for SMFID and when queried I am 
normally told that it relates to historical chargeback and accounting (and very 
possible that the reasons for it are forgotten/lost).

Rob Scott
Rocket Software

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Matt Hogstrom
Sent: 10 February 2023 16:16
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Question on use of LPARNAME, SYSNAME and SMFID

EXTERNAL EMAIL





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 terms of naming.

 and  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

A generalist knows less and less about more and more till he knows nothing 
about everything A specialist knows more and more about less and less till he 
knows everything about nothing


--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Rocket Software, Inc. and subsidiaries ■ 77 Fourth Avenue, Waltham MA 02451 ■ 
Main Office Toll Free Number: +1 855.577.4323
Contact Customer Support: 
https://my.rocketsoftware.com/RocketCommunity/RCEmailSupport
Unsubscribe from Marketing Messages/Manage Your Subscription Preferences - 
http://www.rocketsoftware.com/manage-your-email-preferences
Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy


This communication and any attachments may contain confidential information of 
Rocket Software, Inc. All unauthorized use, disclosure or distribution is 
prohibited. If you are not the intended recipient, please notify Rocket 
Software immediately and destroy all copies of this communication. Thank you.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Question on use of LPARNAME, SYSNAME and SMFID

[Matt Hogstrom]

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 terms of naming.

 and  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

A generalist knows less and less about more and more till he knows nothing 
about everything
A specialist knows more and more about less and less till he knows everything 
about nothing


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN