> VMUTIL DMSEXT072E Error in EXEC file IDLEUESR, line 0 - not found Hmmm. Could it be as simple as a typo for your problem? "line 0 - not found" usually means that the exec can't be found. "IDLEUESR" is an unusual spelling for what would seem to be "IDLEUSER".
Mike Walter Hewitt Associates The opinions expressed herein are mine alone, not my employer's. "Wakser, David" <[email protected]> Sent by: "The IBM z/VM Operating System" <[email protected]> 09/09/2009 04:42 PM Please respond to "The IBM z/VM Operating System" <[email protected]> To [email protected] cc Subject Re: Problem that is a blast from the past... Here is a screen copy of all the times it has happened recently. I was looking for a pattern. It's always the same time. CONSERVE Console Display IFOX z/VM 5.3 (ZVMESA5) VMUTIL DMSEXT072E Error in EXEC file IDLEUESR, line 0 - not found 7:00:00 ------------------------------------------------------------------------ ------- ***** End of 08/11/09 ***** Start of 08/18/09 ***** ------------------------------------------------------------------------ ------- VMUTIL DMSEXT072E Error in EXEC file IDLEUESR, line 0 - not found 7:00:01 ------------------------------------------------------------------------ ------- ***** End of 08/18/09 ***** Start of 08/25/09 ***** ------------------------------------------------------------------------ ------- VMUTIL DMSEXT072E Error in EXEC file IDLEUESR, line 0 - not found 7:00:00 ------------------------------------------------------------------------ ------- ***** End of 08/25/09 ***** Start of 09/01/09 ***** ------------------------------------------------------------------------ ------- VMUTIL DMSEXT072E Error in EXEC file IDLEUESR, line 0 - not found 7:00:00 ------------------------------------------------------------------------ ------- ***** End of 09/01/09 ***** Start of 09/08/09 ***** ------------------------------------------------------------------------ ------- VMUTIL DMSEXT072E Error in EXEC file IDLEUESR, line 0 - not found 7:00:01 >>Overlap<< 08/11/09 Redisplay ===> PF1=Help PF2=Track PF3=Quit PF6=? PF7=Bwd PF8=Fwd -----Original Message----- From: The IBM z/VM Operating System [mailto:[email protected]] On Behalf Of Wandschneider, Scott Sent: Wednesday, September 09, 2009 5:34 PM To: [email protected] Subject: Re: Problem that is a blast from the past... Where is HOBBIT TIMES located? If the file changes should that disk be re-accessed ? Thank you, Scott -----Original Message----- From: The IBM z/VM Operating System [mailto:[email protected]] On Behalf Of Martha McConaghy Sent: Wednesday, September 09, 2009 4:13 PM To: [email protected] Subject: Problem that is a blast from the past... Well, I got to pull out my old System/370 reference "green card" (really a yellow book) for the first time in quite a while. That was quite nostalgic. The reason for using it isn't quite as much fun, though. I'm trying to get the Xymon client for VM working, which uses WAKEUP. I haven't used that in a number of years and am running into a weird problem. It will work for hours without a problem and then just drop out of WAKEUP due to an "external interrupt". WAKEUP is being called as follows: WAKEUP +5 ( CONS EXT SMSG FILE(HOBBIT TIMES *) Sometimes, it will run through a sequence and then exit, sometimes it will run for several days before it happens. This is happening on different systems to, not just on one VM system. I suspect that some silly thing is not set correctly, but I have no idea what. I finally did a CP TRACE EXT on one of them and found that it is getting an external interrupt code 1004. According to my trusty old reference book, that is a "clock comparator" interrupt. That is what is causing WAKEUP to stop with RC=6. Any ideas on how I can get it to stop doing that? Martha 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. 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. The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
