I have been running for many years with two local mods to IDENTIFY. Mod 1 ignores the first two digits of the CPUID (isn't this what IBM told other vendors they should do when they do CPUID checking in their products?) This could also be done by allowing a wildcard character, (li ke %), to cause that position in the CPUID to be ignored. Mod 2 will use the System Node Name if the NODEID is coded as an "*" (asterisk). So my SYSTEM NETID file looks like this: *CPUID NODEID NETID 050539 * TSSWRSCS
The "05" in the CPUID is ignored. Here is what IDENTIFY returns on my production VM system: TSSWDRS AT SDCVM01 VIA TSSWRSCS 2006-02-27 19:49:55 EST MONDAY SDCVM01 is my System Node Name. Here is what IDENTIFY returns on my seco nd level VM test system using the same SYSTEM NETID file: TSSWDRS AT VMTEST VIA TSSWRSCS 2006-02-27 19:51:35 EST MONDAY VMTEST is the Sytem Node Name for my test system. Maybe something like this could be done to make the SYSTEM NETID file easier and more flexible to use. Dale R. Smith Technology Services Senior IBM Global Services [EMAIL PROTECTED] 1-614-481-1608
