Hi, I've been following the thread on LPARNAME, SYSNAME and SMFID with interest, namely because of a naming issue at my site that has been a minor irritation for me for years. We run a small shop, 2 production LPARs not in a sysplex. One of the LPARs is set up as SYSNAME=SMFID=ZOS1. Unfortunately the other LPAR has SYSNAME=ZOS1 but the SMFID=ZOS2. What kind of headaches will I encounter if I change the SYSNAME on LPAR 2 to ZOS2? I was told we will have issues with SMS and potentially SCRT?
TIA Rex -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Al Sherkow Sent: Monday, February 13, 2023 9:23 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: [EXTERNAL] 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://urldefense.com/v3/__https://www.sherkow.com/lcs/__;!!KjMRP1Ixj6eLE0Fj!p5fZvhB5gl1CUBT9gY7F8pyp2PgyTGioz8icTGsRFrEHXW9vTdymGr3OQwlK7eCVJYwyVaprkRwZ$ ) 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://urldefense.com/v3/__http://www.sherkow.com__;!!KjMRP1Ixj6eLE0Fj!p5fZvhB5gl1CUBT9gY7F8pyp2PgyTGioz8icTGsRFrEHXW9vTdymGr3OQwlK7eCVJYwyVWudOQnO$ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- The information contained in this message is confidential, protected from disclosure and may be legally privileged. If the reader of this message is not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any disclosure, distribution, copying, or any action taken or action omitted in reliance on it, is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
