List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Binyamin Dissen
Sent: 07 March 2018 01:41
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Managing JESYSMSG size
As this is your code, it may be worth it to use BPAM rather than do a
separate allocation for each member. Will also save lots of CPU
eful to know!
:>
:>Thanks
:>Robin
:>
:>-Original Message-
:>From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Greg Price
:>Sent: 03 March 2018 10:10
:>To: IBM-MAIN@LISTSERV.UA.EDU
:>Subject: Re: Managing JESYSMSG size
:>
:
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Greg Price
Sent: 05 March 2018 19:39
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Managing JESYSMSG size
On 2018-03-05 5:50 PM, Robin Atwood wrote:
> Greg-
> The SVC 99s are under my c
On 2018-03-05 5:50 PM, Robin Atwood wrote:
Greg-
The SVC 99s are under my control and that is very useful to know!
Thanks
Robin
Robin,
Great!
:)
But I was slightly inaccurate.
:(
It is not in a text unit, it is in the RB proper - bit S99MSGL0 in byte
S99FLG11.
In a batch program
Greg-
The SVC 99s are under my control and that is very useful to know!
Thanks
Robin
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Greg Price
Sent: 03 March 2018 10:10
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Managing JESYSMSG
On 2018-03-02 9:53 PM, Robin Atwood wrote:
Is there anyway via
JES2 or SMS to suppress these messages? Preferably on a per-job basis rather
than globally
Would MSGLEVEL=(n,0) do the trick?
If the DYNALLOCs are under your control, you can request this in the
relevant SVC 99 text unit.
Robin Atwood wrote:
>Elardus-
>Dan has the solution, use the JESLOG parameter.
Yes and thanks to Dan. I simply could not remember that word "JESLOG", but I am
pretty sure there is a way to suppress messages. Thanks to Dan for refreshing
my memory.
>I don't think management would respond well
Sent: 02 March 2018 18:20
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Managing JESYSMSG size
Robin Atwood wrote:
>We have a customer using our file server to synchronise 200,000 odd members
>with a PC-based source manager. Each download requires a data set allocation
>which generate
Robin Atwood wrote:
>We have a customer using our file server to synchronise 200,000 odd members
>with a PC-based source manager. Each download requires a data set allocation
>which generates IGD10xI messages in the server's JESYSMSG file, about five
>lines per member.
That is a PITA. I can't
Wouldn't JESLOG=SUPPRESS on the job card do the trick?
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
We have a customer using our file server to synchronise 200,000 odd members
with a PC-based source manager. Each download
requires a data set allocation which generates IGD10xI messages in the
server's JESYSMSG file, about five lines per member.
So they are getting millions of messages filling
11 matches
Mail list logo