On Fri, 2 Jan 2009, Edward Jaffe wrote: > George Dranes wrote: > > I thought I would try to clean up some of our naming conventions. We are > > running a monoplex. I've named our SYSNAME and SMF ID values the same. > > What would be most appropriate for our JES2 node name? Should I make all 3 > > the same name? I'm currently using the sysplex name for the JES2 node name. > > > > Interesting approach. I do exactly the opposite. I want to know what I'm > really looking at when I see a so-called "system name" value displayed. > > I use different prefix values for MVS system name, JES member names > (except for JES3 because it always uses the 8-byte MVS system names), > SMF system IDs, etc. The only thing they all have in common is the > embedded two-character &SYSCLONE value. > > I ensure JES node and XCF group names are both JESplex level names. > However, I make them different from each other. > > My goal is to avoid all confusion. > >
this would only confuse me. Let's see, I want to /*JOBPARM SYSAFF= to which name? OK, the JES2 name. Now, I want to select the SMF data from that same system. Oh, that's a different name? Hum, now let me route a command to that same system. What! A third name???? I must remember three names and which name goes with which facility I want? Oh, my aching head. -- Q: What do theoretical physicists drink beer from? A: Ein Stein. Maranatha! John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
