Re: Question on SDSF/JES2
- From: edjaffe@xxxxxxxxxxxxxxxxxxx (Edward Jaffe)
- Date: 15 Feb 2009 22:41:33 -0800
Edward Jaffe wrote:
I suggest you give your programmers OPERCMDS authority to issue the STOP command...
MVS CANCEL and STOP can be controlled by jobname:
MVS.CANCEL.JOB.jobname
MVS.STOP.JOB.jobname
That works if the names of the jobs can be known in advance. If you have no job naming conventions, or if the code in question can run in any job, then I agree it's not an ideal solution.
I've been pondering this and I'm not sure why SDSF prevents MVS commands from being issued against jobs assigned the PROTECTED attribute by JES2. There's no way it could prohibit such commands for jobs shown on DA that are running in a different MAS. Therefore, its behavior in this regard is inconsistent and, in your case at least, quite undesirable and perhaps arguably wrong.
In general, it seems to me that MVS commands should not be allowed or disallowed based on any JES-assigned attribute. Only JES commands should be sensitive to such things.
--
Edward E Jaffe
Phoenix Software International, Inc
5200 W Century Blvd, Suite 800
Los Angeles, CA 90045
310-338-0400 x318
edjaffe@xxxxxxxxxxxxxxxxxxx
http://www.phoenixsoftware.com/
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to listserv@xxxxxxxxxxx with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
.
- References:
- Re: Question on SDSF/JES2
- From: Thompson, Steve
- Re: Question on SDSF/JES2
- From: Edward Jaffe
- Re: Question on SDSF/JES2
- Prev by Date: Re: JES2 exits and ACF2
- Next by Date: VTS - Stacked Volume Ejects without a Warning Message
- Previous by thread: Re: Question on SDSF/JES2
- Next by thread: Re: Question on SDSF/JES2
- Index(es):
Relevant Pages
|