Re: JES2MAIL Log Output to Two SDSF Output Groups - How to Disable One

[George, William@FTB]

Seymour

When one does not know the correct vocabulary that maybe a longtime system folk 
might know, one does their best to describe a situation.
I did my best. And thanks to Randy Lists for the describing the situation and 
easy fix.  

All the best
Bill

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Shmuel Metz (Seymour J.)
Sent: Monday, November 02, 2015 5:12 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: JES2MAIL Log Output to Two SDSF Output Groups - How to Disable One

In <984dfc2f94c72c4c9e9acbfd71e4feee32d...@fg1014.ftb.ca.gov>, on
11/02/2015
   at 10:23 PM, "George, William@FTB"  said:

>We have several jobs that use JES2MAIL to email reports to various 
>users. The JES2 output (in SDSF) from the step creates two entries

Are you referring to the job log and the hardcopy log?

>1.  The main SYSOUT from the job that includes the JES2MAIL
>trace log

Please don't invent your own vocabulary. There is no "main SYSOUT".

>2.  And a second log that seems to contain all the "Non-ConMsg:"
>lines found in the main trace log

See above.

You control the characteristics of SYSOUT datasets with OUTPUT statments. In 
your case you need the JESDS keyword to identify the dataset of interest.

>To attempt to show what I mean,

To show what you mean you must identify the JCL and the SDSF commands that you 
used. In particular, what information did you specify to control JES2MAIL?

>The two entries were created below within SDSF.

No; SDSF is only the program that you used to view them.

-- 
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 ISO position; see <http://patriot.net/~shmuel/resume/brief.html>
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

__
CONFIDENTIALITY NOTICE: This email from the State of California is for the sole 
use of the intended recipient and may contain confidential and privileged 
information. Any unauthorized review or use, including disclosure or 
distribution, is prohibited. If you are not the intended recipient, please 
contact the sender and destroy all copies of this email.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: JES2MAIL Log Output to Two SDSF Output Groups - How to Disable One

[George, William@FTB]

Thank you Randy... just what I was looking for!

Bill

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Randy Lists
Sent: Tuesday, November 03, 2015 7:28 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: JES2MAIL Log Output to Two SDSF Output Groups - How to Disable One

Bill,

Apologies for not responding sooner but I did not notice this email to the IBM 
list until this morning.  The messages you are referring to are written through 
the SYSPRINT DD statement.  Generally there is a "//SYSPRINT DD SYSOUT=*" 
statement in the JES2Mail JCL.  You can either remove this statement or dummy 
it out and that should suppress these messages.  The SYSPRINT messages are 
intended to be a summary of the activity that is reported in more detail in the 
LOGFILE sysout.

If need any further information on this, or any other JES2Mail matter, you can 
email us directly at supp...@casisoft.com.

Regards,

Randy Benderman
CASI Software

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of George, William@FTB
Sent: Monday, November 02, 2015 2:23 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: JES2MAIL Log Output to Two SDSF Output Groups - How to Disable One

We have several jobs that use JES2MAIL to email reports to various users.
The JES2 output (in SDSF) from the step creates two entries and I'm hoping to 
find a means to disable one of them.
The two entries are: (example SDSF entries further below)

1.  The main SYSOUT from the job that includes the JES2MAIL trace log

2.  And a second log that seems to contain all the "Non-ConMsg:" lines
found in the main trace log
Is there a means to disable the 2nd entry JES entry?
Why I find this strange as there is not a DD associated to it coded in the JCL 
to control it.

To attempt to show what I mean, as a test for the below example I ran JCL with 
just the JES2MAIL step.
The two entries were created below within SDSF.  Note: the entries are 
truncated but only the TOTAL-REC and O-GRP-NM are different between the two.

NP   JOBNAME JOBID  CRDATEC DESTNAME TOTAL-REC  O-GRP-NM
 TQ6498ML J0485602 11/02/2015 X LOCAL  1431
 TQ6498ML J0485602 11/02/2015 X LOCAL4
2

LOG EXAMPLE
A portion of the Main SYSOUT trace log.
Note:  items 0017,  0018, 0002 & 0003 below will also be found in the 2nd log
:0015  Min: ZIPService available: None
:0016  Min: SYSIN Command: FILE=DD:MESSAGE
:0017  Min: Non-ConMsg: J2M018  JES2Mail: Message From:  
:0018  Min: Non-ConMsg: J2M015  JES2Mail: Message From:  
:  Min: Message ACCEPTED by Post office: 250 Mail Delivered
:0001  Min: Msg Accepted on Date: Mon, 2 Nov 2015 at 18: 52:52 -
:0002  Min: Non-ConMsg: J2M017  JES2Mail: Message From: 250 Mail Delivered
:0003  Min: Non-ConMsg: J2M007  JES2Mail: Message From: All 1 msgs sent ok
:0004  Min: SYSIN Command: END

The 2nd SDSF entry
J2M018  JES2Mail: Message From: 
J2M015  JES2Mail: Message From: 
J2M017  JES2Mail: Message From: 250 Mail Delivered
J2M007  JES2Mail: Message From: All 1 msgs sent ok

Any insights into a means to disable this or have be part of the main SYSOUT 
entry would be appreciated.

Thanks!
Bill George


__
CONFIDENTIALITY NOTICE: This email from the State of California is for the sole 
use of the intended recipient and may contain confidential and privileged 
information. Any unauthorized review or use, including disclosure or 
distribution, is prohibited. If you are not the intended recipient, please 
contact the sender and destroy all copies of this email.

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: JES2MAIL Log Output to Two SDSF Output Groups - How to Disable One

[Randy Lists]

Bill,

Apologies for not responding sooner but I did not notice this email to the
IBM list until this morning.  The messages you are referring to are written
through the SYSPRINT DD statement.  Generally there is a "//SYSPRINT DD
SYSOUT=*" statement in the JES2Mail JCL.  You can either remove this
statement or dummy it out and that should suppress these messages.  The
SYSPRINT messages are intended to be a summary of the activity that is
reported in more detail in the LOGFILE sysout.

If need any further information on this, or any other JES2Mail matter, you
can email us directly at supp...@casisoft.com.

Regards,

Randy Benderman
CASI Software

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of George, William@FTB
Sent: Monday, November 02, 2015 2:23 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: JES2MAIL Log Output to Two SDSF Output Groups - How to Disable One

We have several jobs that use JES2MAIL to email reports to various users.
The JES2 output (in SDSF) from the step creates two entries and I'm hoping
to find a means to disable one of them.
The two entries are: (example SDSF entries further below)

1.  The main SYSOUT from the job that includes the JES2MAIL trace log

2.  And a second log that seems to contain all the "Non-ConMsg:" lines
found in the main trace log
Is there a means to disable the 2nd entry JES entry?
Why I find this strange as there is not a DD associated to it coded in the
JCL to control it.

To attempt to show what I mean, as a test for the below example I ran JCL
with just the JES2MAIL step.
The two entries were created below within SDSF.  Note: the entries are
truncated but only the TOTAL-REC and O-GRP-NM are different between the two.

NP   JOBNAME JOBID  CRDATEC DESTNAME TOTAL-REC  O-GRP-NM
 TQ6498ML J0485602 11/02/2015 X LOCAL  1431
 TQ6498ML J0485602 11/02/2015 X LOCAL4
2

LOG EXAMPLE
A portion of the Main SYSOUT trace log.
Note:  items 0017,  0018, 0002 & 0003 below will also be found in the 2nd
log
:0015  Min: ZIPService available: None
:0016  Min: SYSIN Command: FILE=DD:MESSAGE
:0017  Min: Non-ConMsg: J2M018  JES2Mail: Message From:  
:0018  Min: Non-ConMsg: J2M015  JES2Mail: Message From:  
:  Min: Message ACCEPTED by Post office: 250 Mail Delivered
:0001  Min: Msg Accepted on Date: Mon, 2 Nov 2015 at 18: 52:52 -
:0002  Min: Non-ConMsg: J2M017  JES2Mail: Message From: 250 Mail Delivered
:0003  Min: Non-ConMsg: J2M007  JES2Mail: Message From: All 1 msgs sent ok
:0004  Min: SYSIN Command: END

The 2nd SDSF entry
J2M018  JES2Mail: Message From: 
J2M015  JES2Mail: Message From: 
J2M017  JES2Mail: Message From: 250 Mail Delivered
J2M007  JES2Mail: Message From: All 1 msgs sent ok

Any insights into a means to disable this or have be part of the main SYSOUT
entry would be appreciated.

Thanks!
Bill George


__
CONFIDENTIALITY NOTICE: This email from the State of California is for the
sole use of the intended recipient and may contain confidential and
privileged information. Any unauthorized review or use, including disclosure
or distribution, is prohibited. If you are not the intended recipient,
please contact the sender and destroy all copies of this email.

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email
to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: JES2MAIL Log Output to Two SDSF Output Groups - How to Disable One

[Shmuel Metz (Seymour J.)]

In <984dfc2f94c72c4c9e9acbfd71e4feee32d...@fg1014.ftb.ca.gov>, on
11/02/2015
   at 10:23 PM, "George, William@FTB"  said:

>We have several jobs that use JES2MAIL to email reports to various
>users. The JES2 output (in SDSF) from the step creates two entries 

Are you referring to the job log and the hardcopy log?

>1.  The main SYSOUT from the job that includes the JES2MAIL
>trace log

Please don't invent your own vocabulary. There is no "main SYSOUT".

>2.  And a second log that seems to contain all the "Non-ConMsg:"
>lines found in the main trace log

See above.

You control the characteristics of SYSOUT datasets with OUTPUT
statments. In your case you need the JESDS keyword to identify the
dataset of interest.

>To attempt to show what I mean,

To show what you mean you must identify the JCL and the SDSF commands
that you used. In particular, what information did you specify to
control JES2MAIL?

>The two entries were created below within SDSF.

No; SDSF is only the program that you used to view them.

-- 
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 ISO position; see  
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: JES2MAIL Log Output to Two SDSF Output Groups - How to Disable One

[Lizette Koehler]

I am not familiar with this product.  
Have you checked with the Vendor?

Lizette


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of George, William@FTB
> Sent: Monday, November 02, 2015 3:23 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: JES2MAIL Log Output to Two SDSF Output Groups - How to Disable One
> 
> We have several jobs that use JES2MAIL to email reports to various users.
> The JES2 output (in SDSF) from the step creates two entries and I'm hoping to
find a
> means to disable one of them.
> The two entries are: (example SDSF entries further below)
> 
> 1.  The main SYSOUT from the job that includes the JES2MAIL trace log
> 
> 2.  And a second log that seems to contain all the "Non-ConMsg:" lines
found in
> the main trace log
> Is there a means to disable the 2nd entry JES entry?
> Why I find this strange as there is not a DD associated to it coded in the JCL
to
> control it.
> 
> To attempt to show what I mean, as a test for the below example I ran JCL with
just
> the JES2MAIL step.
> The two entries were created below within SDSF.  Note: the entries are
truncated
> but only the TOTAL-REC and O-GRP-NM are different between the two.
> 
> NP   JOBNAME JOBID  CRDATEC DESTNAME TOTAL-REC  O-GRP-NM
>  TQ6498ML J0485602 11/02/2015 X LOCAL  1431
>  TQ6498ML J0485602 11/02/2015 X LOCAL4  2
> 
> LOG EXAMPLE
> A portion of the Main SYSOUT trace log.
> Note:  items 0017,  0018, 0002 & 0003 below will also be found in the 2nd log
> :0015  Min: ZIPService available: None
> :0016  Min: SYSIN Command: FILE=DD:MESSAGE
> :0017  Min: Non-ConMsg: J2M018  JES2Mail: Message From:  
> :0018  Min: Non-ConMsg: J2M015  JES2Mail: Message From:  
> :  Min: Message ACCEPTED by Post office: 250 Mail Delivered
> :0001  Min: Msg Accepted on Date: Mon, 2 Nov 2015 at 18: 52:52 -
> :0002  Min: Non-ConMsg: J2M017  JES2Mail: Message From: 250 Mail Delivered
> :0003  Min: Non-ConMsg: J2M007  JES2Mail: Message From: All 1 msgs sent ok
> :0004  Min: SYSIN Command: END
> 
> The 2nd SDSF entry
> J2M018  JES2Mail: Message From: 
> J2M015  JES2Mail: Message From: 
> J2M017  JES2Mail: Message From: 250 Mail Delivered
> J2M007  JES2Mail: Message From: All 1 msgs sent ok
> 
> Any insights into a means to disable this or have be part of the main SYSOUT
entry
> would be appreciated.
> 
> Thanks!
> Bill George
> 
> 

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

JES2MAIL Log Output to Two SDSF Output Groups - How to Disable One

[George, William@FTB]

We have several jobs that use JES2MAIL to email reports to various users.
The JES2 output (in SDSF) from the step creates two entries and I'm hoping to 
find a means to disable one of them.
The two entries are: (example SDSF entries further below)

1.  The main SYSOUT from the job that includes the JES2MAIL trace log

2.  And a second log that seems to contain all the "Non-ConMsg:" lines 
found in the main trace log
Is there a means to disable the 2nd entry JES entry?
Why I find this strange as there is not a DD associated to it coded in the JCL 
to control it.

To attempt to show what I mean, as a test for the below example I ran JCL with 
just the JES2MAIL step.
The two entries were created below within SDSF.  Note: the entries are truncated
but only the TOTAL-REC and O-GRP-NM are different between the two.

NP   JOBNAME JOBID  CRDATEC DESTNAME TOTAL-REC  O-GRP-NM
 TQ6498ML J0485602 11/02/2015 X LOCAL  1431
 TQ6498ML J0485602 11/02/2015 X LOCAL4  2

LOG EXAMPLE
A portion of the Main SYSOUT trace log.
Note:  items 0017,  0018, 0002 & 0003 below will also be found in the 2nd log
:0015  Min: ZIPService available: None
:0016  Min: SYSIN Command: FILE=DD:MESSAGE
:0017  Min: Non-ConMsg: J2M018  JES2Mail: Message From:  
:0018  Min: Non-ConMsg: J2M015  JES2Mail: Message From:  
:  Min: Message ACCEPTED by Post office: 250 Mail Delivered
:0001  Min: Msg Accepted on Date: Mon, 2 Nov 2015 at 18: 52:52 -
:0002  Min: Non-ConMsg: J2M017  JES2Mail: Message From: 250 Mail Delivered
:0003  Min: Non-ConMsg: J2M007  JES2Mail: Message From: All 1 msgs sent ok
:0004  Min: SYSIN Command: END

The 2nd SDSF entry
J2M018  JES2Mail: Message From: 
J2M015  JES2Mail: Message From: 
J2M017  JES2Mail: Message From: 250 Mail Delivered
J2M007  JES2Mail: Message From: All 1 msgs sent ok

Any insights into a means to disable this or have be part of the main SYSOUT 
entry would be appreciated.

Thanks!
Bill George


__
CONFIDENTIALITY NOTICE: This email from the State of California is for the sole 
use of the intended recipient and may contain confidential and privileged 
information. Any unauthorized review or use, including disclosure or 
distribution, is prohibited. If you are not the intended recipient, please 
contact the sender and destroy all copies of this email.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN