In this case, it was a SEND CP userid LOGOFF. IBM has fixed many of these over the years. Now, they are not nearly so frequent as in the past.
Regards, Richard Schuh ________________________________ From: The IBM z/VM Operating System [mailto:[email protected]] On Behalf Of Wandschneider, Scott Sent: Wednesday, September 30, 2009 3:23 PM To: [email protected] Subject: Re: LOGOFF/FORCE PENDING Richard, Please keep the list posted with any updates to this subject. I, for one, am *very* interested in your PMR. As I recall this has been a nagging problem since the VM/370 days. As I update our VM systems I am taking the FORCE command away by changing its privilege class, but in the process have upset operations and others as their procedures actually call for forcing users off, instead of logging on, then logging them off. Thank you, Scott From: The IBM z/VM Operating System [mailto:[email protected]] On Behalf Of Schuh, Richard Sent: Wednesday, September 30, 2009 4:38 PM To: [email protected] Subject: LOGOFF/FORCE PENDING We have a user in the subject state. Track shows an interesting thing. In the VMDBK display, the storage is shown to be -107373M. That's right, a whopping small negative number. Most of the rest of the VMDBK is zeros with no devices and no I/O pending. Is this a normal value for that field in these conditions? It looks like the system owes the user more storage that there is configured in the LPAR. I will have the OPERATOR take a SNAPDUMP and open an incident. Regards, Richard Schuh Confidentiality Note: This e-mail, including any attachment to it, may contain material that is confidential, proprietary, privileged and/or "Protected Health Information," within the meaning of the regulations under the Health Insurance Portability & Accountability Act as amended. If it is not clear that you are the intended recipient, you are hereby notified that you have received this transmittal in error, and any review, dissemination, distribution or copying of this e-mail, including any attachment to it, is strictly prohibited. If you have received this e-mail in error, please immediately return it to the sender and delete it from your system. Thank you.
