I like your local mods. Can I get a copy of them?
[EMAIL PROTECTED] wrote:
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, (like
%), 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 second
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
--
Stephen Frazier
Information Technology Unit
Oklahoma Department of Corrections
3400 Martin Luther King
Oklahoma City, Ok, 73111-4298
Tel.: (405) 425-2549
Fax: (405) 425-2554
Pager: (405) 690-1828
email: stevef%doc.state.ok.us
