Thank you, gentlemen. I had read the INTRDR init statement
documentation. It does not mention SYSAFF. However, I issued the JES2
operator command to set SYSAFF on our test system and tested it. Thanks
again.
--
For IBM-MAIN
We have 3 LPARs in our sysplex all in the same MAS. All running z/OS
1.7. We have an anomaly we can't explain.
When a job is submitted on System A, it is converted on system B. Due
to the scheduling environment, the job
executes and ABENDs on System A. Designating SYSAFF=A resolved the
On Mon, 14 Sep 2009 13:21:24 -0700, Mark Yuhas mark.yu...@paccar.com wrote:
We have 3 LPARs in our sysplex all in the same MAS. All running z/OS
1.7. We have an anomaly we can't explain.
When a job is submitted on System A, it is converted on system B. Due
to the scheduling environment, the
On Mon, 14 Sep 2009 13:21:24 -0700, Mark Yuhas wrote:
Even though both systems have the same PROC name. The PROCs our
different on each system. ...
Is there a way, besides an exit, to force a job without a SYSAFF
designation to be converted on the same system
that it was submitted on?
I didn't think you could put it on the INTRDR statement, but I've been using
$T INTRDR,SYSAFF=* in the init deck for decades, no need for a system symbol
;-)
Mark Zelden mark.zel...@zurichna.com 9/14/2009 4:36 PM
On Mon, 14 Sep 2009 13:21:24 -0700, Mark Yuhas mark.yu...@paccar.com wrote:
You
5 matches
Mail list logo
