Re: Question on use of LPARNAME, SYSNAME and SMFID

: [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

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

Re: Question on use of LPARNAME, SYSNAME and SMFID

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 nam

Re: Question on use of LPARNAME, SYSNAME and SMFID

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

Re: Question on use of LPARNAME, SYSNAME and SMFID

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

Re: Question on use of LPARNAME, SYSNAME and SMFID

d 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 SYSNA

Re: Question on use of LPARNAME, SYSNAME and SMFID

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 hand

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 wit

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 p

Re: Question on use of LPARNAME, SYSNAME and SMFID

: 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 betwe

Re: Question on use of LPARNAME, SYSNAME and SMFID

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 &SYSNAME. That would fall under "is related to". Pe

Re: Question on use of LPARNAME, SYSNAME and SMFID

@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

Re: Question on use of LPARNAME, SYSNAME and SMFID

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 w

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 <

Re: Question on use of LPARNAME, SYSNAME and SMFID

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 J

Re: Question on use of LPARNAME, SYSNAME and SMFID

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

Re: Question on use of LPARNAME, SYSNAME and SMFID

> the &SYSNAME, &LPARNAME and &SMFID 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 Techn

Re: Question on use of LPARNAME, SYSNAME and SMFID

In almost all instances I’ve seen the word ‘PLEX’ is in the &SYSPLEX. variable in some form or another. PRODPLEX, PLEXA1, … Matt Hogstrom m...@hogstrom.org +1-919-656-0564 PGP Key: 0x90ECB270 Facebook LinkedIn Twitter

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 a

Re: Question on use of LPARNAME, SYSNAME and SMFID

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 man

Re: Question on use of LPARNAME, SYSNAME and SMFID

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 resear

Re: Question on use of LPARNAME, SYSNAME and SMFID

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 &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 valu

Re: Question on use of LPARNAME, SYSNAME and SMFID

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 &SYSNAME, &LPARNAME and &SMFID symbols. From what

Question on use of LPARNAME, SYSNAME and SMFID

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