Re: Question on SDSF/JES2



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
.



Relevant Pages

  • Re: Printing from Solaris
    ... >> Try issuing 100 lp commands for that printer very quickly, ... >> in a script. ... You'll find that a few of the jobs become stuck on ... There are some software packages that let print jobs build up ...
    (comp.unix.solaris)
  • Re: IEE345I command authority error from batch
    ... jobs set up to issue MVS Modify commands to CICS. ... It could be that your JES parms no longer allow commands from batch jobs, or that the OPERPARM segment for the user has the wrong authority level specified. ...
    (bit.listserv.ibm-main)
  • Re: zfs: Fatal trap 12: page fault while in kernel mode
    ... jobs is hanging, cannot be killed, even not with -9. ... zfs commands are hanging and cannot be killed, ... I will leave the machine running in this ...
    (freebsd-current)
  • Re: zfs: Fatal trap 12: page fault while in kernel mode
    ... jobs is hanging, cannot be killed, even not with -9. ... zfs commands are hanging and cannot be killed, ...
    (freebsd-current)