;Behalf Of Mark Zelden
>Sent: Wednesday, December 6, 2017 12:15 PM
>To: IBM-MAIN@LISTSERV.UA.EDU
>Subject: Re: Strange Things in JES2
>
>Is this held output? What if you use the ST command and "INPUT ON" while
>looking
>at the DDs with a "?"? Does that
of Syncsort.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Mark Zelden
Sent: Wednesday, December 6, 2017 12:15 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Strange Things in JES2
Is this held output? What if you use the ST command
t;From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
>Behalf Of Allan Staller
>Sent: Monday, December 4, 2017 11:27 AM
>To: IBM-MAIN@LISTSERV.UA.EDU
>Subject: Re: Strange Things in JES2
>
>DSID 105 seems to be missing from the JESLOG.
>GDE message are n
DSID starting with 102? Does it start with 101 or even 100? Is there
an autodelete MSGCLASS (Z)?
On Mon, Dec 4, 2017 at 10:26 AM, Allan Staller wrote:
> DSID 105 seems to be missing from the JESLOG.
> GDE message are not IBM JES2, I have no idea what is producing them.
>
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Strange Things in JES2
I have spoken to the author and he is baffled also.
The file you pointed out was allocated in JCL, but never opened, thus the
allocated but unused DSID.
I reran the job without the data set and still had extra messages reported
Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Allan Staller
Sent: Monday, December 4, 2017 11:27 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Strange Things in JES2
DSID 105 seems to be missing from the JESLOG.
GDE message are not IBM JES2, I have no idea what is producing them
DSID 105 seems to be missing from the JESLOG.
GDE message are not IBM JES2, I have no idea what is producing them.
I suggest checking w/the vendor that issues the GDE messages.
Possible causes?
Dynamic allocation of sysout?
Under another OUTGRP?
Different non-print (or dummy) SYSOUT Class?