Or maybe a haiku? FORCE or LOGOFF pends What options have I today? Next summer too far
Peter -----Original Message----- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Alan Altmark Sent: September 23, 2009 14:49 To: IBMVM@LISTSERV.UARK.EDU Subject: Re: HCPCQU361E LOGOFF/FORCE pending for user OPERATR4 On Wednesday, 09/23/2009 at 02:05 EDT, Suleiman Shahin <s_s_sha...@hotmail.com> wrote: > That's exactly what I want to avoid. besides, this user can stay hung all it > wants. > > So, wait is the best option. In the meantime, I might open a ticket with the > support center. Follow Marcy's advice. Get a SNAPDUMP and open a PMR. We should simply change the text of the message to say "LOGOFF/FORCE pending. If it doesn't complete in the next 15 minutes (or highest MITIME), get a SNAPDUMP and open a PMR." [Go away. What? Oh, alright, I'll tell him.] He Who Must Not Be Named just handed me this. He says to "just chant the magic spell" when you call. I have a problem, if I may; It's one that's never ending. I have a guest who's here to stay, With a FORCE or LOGOFF pending. I have a dump for you to see And save me from this hell. Is it something I can fix? Or must I IPL? Tell me not "Just use STORE HOST!" For that command I fear -- One mistake, and Doom will fall! I think I'll have a beer. -- Chuckie Alan Altmark z/VM Development IBM Endicott The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review retransmission dissemination or other use of or taking any action in reliance upon this information by persons or entities other than the intended recipient or delegate is strictly prohibited. If you received this in error please contact the sender and delete the material from any computer. The integrity and security of this message cannot be guaranteed on the Internet. The sender accepts no liability for the content of this e-mail or for the consequences of any actions taken on the basis of information provided. The recipient should check this e-mail and any attachments for the presence of viruses. The sender accepts no liability for any damage caused by any virus transmitted by this e-mail. This disclaimer is property of the TTC and must not be altered or circumvented in any manner.
