CPUID Anomaly
Hi, This past weekend after an IPL of our z10 to apply RSU 5409 and a VTAM ptf I discovered that the reported CPUID in zVM had changed: CPUID prior to this weedend was : FF01C82620988000 CPUID after IPL was : FF00C82620988000 The difference in the above id¹s is 1C8262 to 0C8262. Also, made a change to MODE from s/390 to ZVM. No IOCDS changes were made. After I discovered the changed CPUID I backed everything out and there was no change in the CPUID. I did finally put everything back and just dealt with the new CPUID. Also found out that MCL¹s had been applied to the HMC but not to the SE¹s. Has anybody seen this behavior? Thanks in advance Jim Poirier Senior zVM/zVSE Systems Programmer, Mainframe Technical Support Group Department of Information Technology State of New Hampshire 27 Hazen Drive Concord, NH 03301 603-271-1535Fax 603.271.1516 Statement of Confidentiality: The contents of this message are confidential. Any unauthorized disclosure, reproduction, use or dissemination (either whole or in part) is prohibited. If you are not the intended recipient of this message, please notify the sender immediately and delete the message from your system.
Re: CPUID Anomaly
Off the top of my head isn't that the LPAR identifier? - 00 vs 01 - On Tue, Jul 12, 2011 at 7:51 AM, James Poirier james.poir...@doit.nh.govwrote: Hi, This past weekend after an IPL of our z10 to apply RSU 5409 and a VTAM ptf I discovered that the reported CPUID in zVM had changed: CPUID prior to this weedend was : FF01C82620988000 CPUID after IPL was : FF00C82620988000 The difference in the above id’s is 1C8262 to 0C8262. Also, made a change to MODE from s/390 to ZVM. No IOCDS changes were made. After I discovered the changed CPUID I backed everything out and there was no change in the CPUID. I did finally put everything back and just dealt with the new CPUID. Also found out that MCL’s had been applied to the HMC but not to the SE’s. Has anybody seen this behavior? Thanks in advance Jim Poirier Senior zVM/zVSE Systems Programmer, Mainframe Technical Support Group Department of Information Technology State of New Hampshire 27 Hazen Drive Concord, NH 03301 603-271-1535Fax 603.271.1516 Statement of Confidentiality: The contents of this message are confidential. Any unauthorized disclosure, reproduction, use or dissemination (either whole or in part) is prohibited. If you are not the intended recipient of this message, please notify the sender immediately and delete the message from your system.
Re: CPUID Anomaly
It appears that it probably is but we made no changes to affect the LPAR id, also the HMC reports that the CPUID is 1C8262 and that is what we used to get before this last IPL. On 7/12/11 11:02 AM, Tom Huegel tehue...@gmail.com wrote: Off the top of my head isn't that the LPAR identifier? - 00 vs 01 - On Tue, Jul 12, 2011 at 7:51 AM, James Poirier james.poir...@doit.nh.gov wrote: Hi, This past weekend after an IPL of our z10 to apply RSU 5409 and a VTAM ptf I discovered that the reported CPUID in zVM had changed: CPUID prior to this weedend was : FF01C82620988000 CPUID after IPL was : FF00C82620988000 The difference in the above id¹s is 1C8262 to 0C8262. Also, made a change to MODE from s/390 to ZVM. No IOCDS changes were made. After I discovered the changed CPUID I backed everything out and there was no change in the CPUID. I did finally put everything back and just dealt with the new CPUID. Also found out that MCL¹s had been applied to the HMC but not to the SE¹s. Has anybody seen this behavior? Thanks in advance Jim Poirier Senior zVM/zVSE Systems Programmer, Mainframe Technical Support Group Department of Information Technology State of New Hampshire 27 Hazen Drive Concord, NH 03301 603-271-1535 tel:603-271-1535 Fax 603.271.1516 tel:603.271.1516 Statement of Confidentiality: The contents of this message are confidential. Any unauthorized disclosure, reproduction, use or dissemination (either whole or in part) is prohibited. If you are not the intended recipient of this message, please notify the sender immediately and delete the message from your system. Jim Poirier Senior zVM/zVSE Systems Programmer, Mainframe Technical Support Group Department of Information Technology State of New Hampshire 27 Hazen Drive Concord, NH 03301 603-271-1535Fax 603.271.1516 Statement of Confidentiality: The contents of this message are confidential. Any unauthorized disclosure, reproduction, use or dissemination (either whole or in part) is prohibited. If you are not the intended recipient of this message, please notify the sender immediately and delete the message from your system.
Re: CPUID Anomaly
On Tuesday, 07/12/2011 at 10:56 EDT, James Poirier james.poir...@doit.nh.gov wrote: This past weekend after an IPL of our z10 to apply RSU 5409 and a VTAM ptf I discovered that the reported CPUID in zVM had changed: CPUID prior to this weedend was : FF01C82620988000 CPUID after IPL was : FF00C82620988000 The difference in the above id?s is 1C8262 to 0C8262. Also, made a change to MODE from s/390 to ZVM. No IOCDS changes were made. After I discovered the changed CPUID I backed everything out and there was no change in the CPUID. I did finally put everything back and just dealt with the new CPUID. Also found out that MCL?s had been applied to the HMC but not to the SE?s. Has anybody seen this behavior? Looks like you changed LPARs. When the Format bit (48) is 1 (as yours is), word 0 of the virtual CPU ID is of the form FFpp, where pp is the UPID (user partition id #), and n is a digit derived from the CPU id. See the STORE CPU ID instruction in the z/Architecture book. Alan Altmark Senior Managing z/VM and Linux Consultant IBM System Lab Services and Training ibm.com/systems/services/labservices office: 607.429.3323 mobile; 607.321.7556 alan_altm...@us.ibm.com IBM Endicott
Re: CPUID Anomaly
On Tuesday, 07/12/2011 at 11:10 EDT, James Poirier james.poir...@doit.nh.gov wrote: It appears that it probably is but we made no changes to affect the LPAR id, also the HMC reports that the CPUID is 1C8262 and that is what we used to get before this last IPL. Then you need to contact the Support Center. CP issues a STIDP as each processor starts. When you log on, a copy of the stored CPU id is copied into your VMDBK, with the HOB set to FF. This is your default CPU ID. It is overridden by the CPU statement in your directory entry or the SET CPUID command. If the HMC reports the LPAR UPID as 01, but the STIDP instruction stored 00, that's not good. Make sure you are looking at the image profile (General), not the CPC Details. (There are more digits in the CPU serial # than are contained in the CPU ID.) Perhaps changing the LPAR mode caused a change in the UPID? Though I don't know why it would Alan Altmark Senior Managing z/VM and Linux Consultant IBM System Lab Services and Training ibm.com/systems/services/labservices office: 607.429.3323 mobile; 607.321.7556 alan_altm...@us.ibm.com IBM Endicott
Re: CPUID Anomaly
James, FF01C82620988000 the 01 tells me that your LPAR configuration has this as LPAR 1 FF00C82620988000 the 00 tells me that after you changed the LPAR MODE it was not provided a number q cpu CPUID = FF00B0AF20948000 Munson at zVM2a; T=0.01/0.01 11:08:04 q cpu CPUID = FF06B0AF20948000 Munson at zVM2; T=0.01/0.01 11:13:32 when we carved out zVM2A we did not number it Bill Munson Sr. z/VM Systems Programmer Brown Brothers Harriman CO. 525 Washington Blvd. Jersey City, NJ 07310 201-418-7588 VM Workshop http://www.VMWorkshop.org/ President - MVMUA http://www2.marist.edu/~mvmua/ LVM Program Officer - SHARE http://www.linkedin.com/in/BillMunson From: James Poirier james.poir...@doit.nh.gov To: IBMVM@LISTSERV.UARK.EDU Date: 07/12/2011 10:56 AM Subject:CPUID Anomaly Sent by:The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU Hi, This past weekend after an IPL of our z10 to apply RSU 5409 and a VTAM ptf I discovered that the reported CPUID in zVM had changed: CPUID prior to this weedend was : FF01C82620988000 CPUID after IPL was : FF00C82620988000 The difference in the above id?s is 1C8262 to 0C8262. Also, made a change to MODE from s/390 to ZVM. No IOCDS changes were made. After I discovered the changed CPUID I backed everything out and there was no change in the CPUID. I did finally put everything back and just dealt with the new CPUID. Also found out that MCL?s had been applied to the HMC but not to the SE?s. Has anybody seen this behavior? Thanks in advance Jim Poirier Senior zVM/zVSE Systems Programmer, Mainframe Technical Support Group Department of Information Technology State of New Hampshire 27 Hazen Drive Concord, NH 03301 603-271-1535Fax 603.271.1516 Statement of Confidentiality: The contents of this message are confidential. Any unauthorized disclosure, reproduction, use or dissemination (either whole or in part) is prohibited. If you are not the intended recipient of this message, please notify the sender immediately and delete the message from your system. *** IMPORTANT NOTE*-- The opinions expressed in this message and/or any attachments are those of the author and not necessarily those of Brown Brothers Harriman Co., its subsidiaries and affiliates (BBH). There is no guarantee that this message is either private or confidential, and it may have been altered by unauthorized sources without your or our knowledge. Nothing in the message is capable or intended to create any legally binding obligations on either party and it is not intended to provide legal advice. BBH accepts no responsibility for loss or damage from its use, including damage from virus.
