Ask ASG. Ask IBM. For what it is worth.. The TMONMVS JOB TERMINATION UTILITY did not use an SRB at least the last time I was working with it.
It defaults to CANCEL first for which it builds a standard MVS CANCEL command in the correct syntax and issues it using MGCR nee SVC 34. If a CANCEL is already outstanding or the user elects the KILL option to bypass the check for CANCEL it invokes the CALLRTM macro with TYPE=MEMTERM. I thought the OMEGAMON KILL command did the same thing but ask IBM. I thought the main difference between TMONMVS & OMEGAMON KILL commands and the z/OS FORCE command is that the FORCE command obtains an enqueue on the CSCB control block chain and does some other checking that the OEM KILL commands don't. Don't forget at the end of the day all of these depend on the z/OS RTM to remove the unit of work all anyone can do is ask it very emphatically to do so. Related comments most of which I won't repeat here http://www.bama.ua.edu/cgi-bin/wa?A2=ind0209&L=ibm-main&D=0&O=D&P=257049 The TMONMVS CDE DETAIL DISPLAY does provide a KILL option which can be used to terminate a TCB using CALLRTM TYPE=ABTERM this is pretty much identical to the IBM CALLRTM program. Item FGPDW (02/26/96) TSO users get hung and cannot be released by CANCEL followed by FORCE. USERS: TSO MVS PDSE PROBLEM SUMMARY: TSO users get hung and cannot be released by CANCEL followed by FORCE. SOLUTION: See details below for removing job from system. PROBLEM DETAILS: TYPE: Maint COMPID: 5695DF115 RELEASE: 1B0 PROBLEM SUMMARY: Abstract: CANCEL followed by FORCE (TSO ID still hung) This item is being promoted to give users access to a method of forcing a task out of the system even if CANCEL and FORCE don't remove it from the system. IBM UPDATE: ****************************************************************** * function: this program will do a callrtm type=abterm to abend * a specific task in a specific asid (default 1). * (eg. hung in memterm resource manager - ieavtmtr) * requirement: this program must be linked into an apf authorized * library. * note: the tcb address for the hung task * must be inserted for symbol - tcbaddr. * symbol asidnum, the asid for the address space, if not asid1, * must be modified to match the desired address space. ****************************************************************** stm 14,12,12(13) balr 12,0 using *,12 b start dc c'callrtm - 09/21/93' ds 0f start equ * st 13,save+4 la 14,save st 14,8(13) lr 13,14 modeset key=zero,mode=sup,related=(callrtm) la 13,save1 l 6,tcbaddr l 7,asidnum callrtm type=abterm,compcod=x'fff',tcb=(6),asid=(7),dump=no la 13,save l 13,save+4 lm 14,12,12(13) sr 15,15 br 14 ds 0f tcbaddr dc x'xxxxxxxx' *** modify this line with desired tcb@ asidnum dc x'00000001' *** modify if other than asid1 save ds 18f save1 ds 18f ds 0f cvt dsect=yes ihapsa end callrtm /* IBM UPDATE: The CALLRTM macro requires that when the macro is a TYPE=ABTERM with ASID then REG 13 must contain the address of a 72 byte work area. SAVE1 is that 72 Byte work area. It doesn't matter that it is not restored and yes you do need it. This is a last-resort program to remove a job from the system. Depending on the resources being held by the cancelled job the system may or may not be able to continue. This is an 'it's worth a shot' effort if you need to remove a job without an ipl. There are no guarantees that the program will work or that the system will continue to operate after the problem job is removed from the system. Best Regards, Sam Knutson, GEICO Performance and Availability Management mailto:[EMAIL PROTECTED] (office) 301.986.3574 "Think big, act bold, start simple, grow fast..." -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Mark H. Young Sent: Wednesday, December 20, 2006 10:40 AM To: [email protected] Subject: Re: Force ,arm vs. Cancel Re: AFAIK -- FORCE ARM seems to be safe. A plain old FORCE with no ARM involved seems to be the dangerous command. Dear Gary Diehl, When using the FORCE command (after CANCEL does not work), the ARM parm is used to Force a NON-CANCELLABLE task. The ARM parameter executes normal task termination routines without causing address space destruction. Would you know of where I might find some discussion (and/or doc) that talks about the OMEGAMON and or TMON KILL command, and how it actually operates? I seem to recall someone telling me (might have been Steve Samson of Candle Corp.) that KILL actually schedules an SRB off the TCB chain. Hope this helps the discussion. THANX, Mark H. Young IBM Mainframe SysProg (old timer) [EMAIL PROTECTED] ==================== This email/fax message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution of this email/fax is prohibited. If you are not the intended recipient, please destroy all paper and electronic copies of the original message. ---------------------------------------------------------------------- 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
