Bruce > ...there is a very simple MVS command that ALL products should be able to accept (intercept) .. that is STOP (P).
The rub[1] is in the "should". Indeed, it is just about the simplest MVS command it is possible to devise. However there is still a need to support it within the program itself and, while not difficult, it is *not* trivial - although I guess both of those are relative. Incidentally, I checked the MVS System Commands manual to be sure of my ground and my memory of my QEDITEX program which I used to explore this matter of the MODIFY and STOP commands long ago. Indeed, I remembered correctly that, there is no opportunity to add parameters to a STOP command while there is for a MODIFY command - of course. Thus, should you want to have different flavours of "stop", you may actually be *obliged* to use the MODIFY command for that purpose - sorry! Chris Mason [1] Hamlet's sense. On Thu, 30 Sep 2010 03:59:53 -0500, Bruce Hewson <[email protected]> wrote: >PLEASE PLEASE - do not suggest MODIFY or WTOR to request shutdown of >your task....there is a very simple MVS command that ALL products should be >able to accept (intercept) .. that is STOP (P). > >Use MODIFY to change your task environment....not to shutdown your task. > >Use STOP to request shutdown...... >Then if that dont work ... use CANCEL.... >Then if that dont work ... use FORCE..... but be propared to IPL the whole >system. > >In this day or age there is simply NO excuse not to support the STOP >command. > >extra: Separation of security access rules for STOP and CANCEL away from >MODIFY is highly advised. The functionality of these commands is distinctly >different. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
