Peter Hunkeler wrote: >And this very fact disqualifies an x22 recovery routine as the solution for >such an important task as writing data out to disk.
Indeed. Such a job is probably busy with a messy loop... (been there, seen that. Stop the thing and you lose goodies... grrrr) >Been there seen that: Operators issuing "C SOMEJOB" some 50 times within 10 >minutes or so (no joke, and that's not the whole story) against some hanging >address space which did not get cancelled. I doubt if today's command flooding things may stop that Operator, but you could perhaps setup your automation software to sit in a counter somewhere, wait for exceeding a set value and then alert some top-brass to kick that operator [ and his/her fingers ] out. John McKown wrote: >Evil thought. I am reminded of something that I saw back in college (1970s) >when I was an RJE operator. I could do the MVT equivalent of an "D A,L" >command. And I say one job in execution with the name like "NOT/ME" Yes, there >was a slash in the name! So how to stop somebody from doing a CANCEL operator >command on your job? I have RTFM now to review the P, C and FORCE commands. Still in 2015 today, you can't use A=<asid> only... How did they start it in the first place? [ Forget for now the RACF and its STARTED+JESSPOOL classes which were not available then... ] >Go key 0, ... Of course, it might be easier to simply flip on the >non-cancelable bit in whatever control block that keeps it (I don't know / >remember). I believe that field is hidden pretty good these OCO days. I could not find it in my books and macros, just a little note in SCHEDxx. >Even easier is to do what I have done for some specific STC names: use >CA-OPS/MVS command rules to "just say 'No!' ". We had to do this for range >commands because we had some dyslexic(?) operators who meant to vary off 1 >device and somehow varied off hundreds. Automation is a blessing in such cases. Some commands like start/stop printers or other devices can be intercepted. Other just check the parameters and if it falls in a 'correct' range, the command is passed on. Or use Automation to translate a [custom] word typed on console into a full syntax valid command+parameters and off you go. >But I'm going very far afield from what the OP was talking about, now. Hahaha. Define 'far'... ;-) Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
