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 &CECNAME 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 &SYSPLEX..&SYSNAME..&SMFID as a combination going forward so that I’ve preserved all three and gained the benefit of the use of a difference between &SYSNAME and &SMFID.
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 <rsc...@rocketsoftware.com> 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
