On Thu, Oct 29, 2009 at 08:33, Rob van der Heij <[email protected]> wrote:
>> Rob was completely correct - CPCONIO IUCV grabbed the midnight message. The >> other thing that I could do to stop the midnight message locking up the >> terminal was to do TERM HOLD OFF. > Those nasty unspoken requirements :-) IIRC You were asking how to > suppress it, not how prevent it putting the terminal in HOLD (which > every msg or wng would do). Well, not really a requirement. More a question of different ways to achieve the same result. > So I guess you're now doing a very cheap scrolling operator console? I can see how you have reached your assumption about what I am doing but 2 + 2 does not always make 5 and I do work on more than 1 thing at a time ;-) In this case it was an existing server, that already trapped msg & wng, that I was monitoring. I (inadvertently) left it logged on overnight and, of course, at midnight it hung up when the midnight message came out. As I am now getting quite old and forgetful, I wanted to protect against making the same mistake again ;-) It really did not matter if the midnight message was trapped by IUCV (my original question) or if just avoided putting the terminal in hold but the IUCV trap is the better solution. > Surely Kris must have uploaded a tool that will issue SEND CP to you > around 23:59 to issue a TERM HOLD OFF for 2 minutes ;-) I am sure I could make it more complicated than that if I think about it hard enough ;-) > :rant. > I very much dislike things that mess with my TERM settings for me. > Like the the z/VM installation process to set TERM MORE 0 0 (and issue > VMFCLEAR frequently) that prevent me from reading the error messages. > If I don't have to see it, then don't display it. When I am supposed > to read it, give me time for that. VM Systems Programmers also are a > shared resource. Sometimes we do get interrupted for high priority > work and get back to the original work later. I do not think I feel as strongly about this as you but I do agree that I do not like processes messing with MY settings in MY userid. However, I think this is a completely different thing to a defined server/userid with a defined process setting defined values (CP SET or CP TERM or whatever) in a way that it allows it process to work in the way it is designed. Of course, it should be friendly and restore the settings when leaving the process and returning to the command line (typically after a terminal break-in). Colin Allinson Amadeus Data Processing GmbH IMPORTANT - CONFIDENTIALITY NOTICE - This e-mail is intended only for the use of the individual or entity shown above as addressees. It may contain information which is privileged, confidential or otherwise protected from disclosure under applicable laws. If the reader of this transmission is not the intended recipient, you are hereby notified that any dissemination, printing, distribution, copying, disclosure or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this transmission in error, please immediately notify us by reply e-mail or using the address below and delete the message and any attachments from your system. Amadeus Data Processing GmbH Geschäftsführer: Eberhard Haag Sitz der Gesellschaft: Erding HR München 48 199 Berghamer Strasse 6 85435 Erding Germany
