In <[EMAIL PROTECTED]>,
on 02/14/2007
at 04:30 PM, "Pommier, Rex R." <[EMAIL PROTECTED]> said:
>This is probably a case of not seeing the forest due to the trees,
>but here goes.
1. SDSF has always had different views of SYSOUT depending on
the panel you used.
2. In JES2 a SYSOUT data s
AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: JES confusion on a specific job
Rex,
What Control-M is doing here is altering the sysout class for the
joblog, jcl image, and allocation messages to a held class that can be
picked up by the control-m monitor. That is how the monitor is checking
for JCL err
Rex,
What Control-M is doing here is altering the sysout class for the
joblog, jcl image, and allocation messages to a held class that can be
picked up by the control-m monitor. That is how the monitor is checking
for JCL errors, space errors, and other issues. In your schedule
definitions you w
ontractor.
Rex
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Tom Schmidt
Sent: Thursday, February 15, 2007 10:26 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: JES confusion on a specific job
On Thu, 15 Feb 2007 09:03:34 -0600, Pommier, Rex R. w
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Alan Scott
Sent: Thursday, February 15, 2007 10:21 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: JES confusion on a specific job
Can you provide the output from the JES command "$DOJ,o
On Thu, 15 Feb 2007 09:03:34 -0600, Pommier, Rex R. wrote:
>I can't categorically say that it is something Control-M is doing to me,
>but it sure is suspicious that we started having this problem about the
>same time we implemented the scheduler.
Rex, I do believe that it is Control-M that is do
Can you provide the output from the JES command "$DOJ,outgrp=*" ?
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at ht
On Thu, 15 Feb 2007 09:03:34 -0600, Pommier, Rex R.
<[EMAIL PROTECTED]> wrote:
>
>I can't categorically say that it is something Control-M is doing to me,
>but it sure is suspicious that we started having this problem about the
>same time we implemented the scheduler.
>
>Rex
>
We don't use Contr
List [mailto:[EMAIL PROTECTED] On
Behalf Of John S. Giltner, Jr.
Sent: Wednesday, February 14, 2007 6:11 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: JES confusion on a specific job
Do you have any OUTPUT cards in the jobs?
One of the things we used to do is have print go to two classes. One
that automat
Do you have any OUTPUT cards in the jobs?
One of the things we used to do is have print go to two classes. One
that automaticaly went to $AVER and one that stayed on the SPOOL for 48
hours. So each print had "two" output classes. We have stopped this
pratice and we did not have SDSF at tha
Hi list.
This is probably a case of not seeing the forest due to the trees, but
here goes.
We are z/OS 1.4, JES2, and running control-m for a job scheduler. I
have certain jobs that show up differently under SDSF depending on how I
look at them. Because of this apparent disparity, job output
11 matches
Mail list logo
