If you are running a lot of CICS regions, you might want to look at
reducing the mastask values, my understanding is that WLM create's PB for
every possible active task in CICS and they get scanned every 250 ms too.
On Mon, Mar 4, 2024 at 10:15 PM Jim Mulder wrote:
> The most important thing i
%DS2CSV (DATA=bat, RUNMODE=B, CSVFREF=CSV,
var=date job jesjobno termcode jobmxhps jobmxhrs
jobmxhss jobmxwss jobmx64b jobmx64s
mips );
On Wed, Aug 2, 2023 at 11:58 AM Mark Regan wrote:
> Jim,
>
> Do you have an example of using it in a batch job?
>
> Regards,
>
> Mark Rega
eracionais Mainframes
> Tel: +55 11 3684-9602 R: 49602 3-1404
> Fax: +55 11 3684-4427
>
>
>
> -Mensagem original-
> De: IBM Mainframe Discussion List Em nome de
> Anthony Hirst
> Enviada em: domingo, 27 de janeiro de 2019 22:12
> Para: IBM-MAIN@LISTSERV.UA.E
One difference that I haven't seen be mentioned is that SYSAFF controls all
stages of JES2 processing, while the SCHED only controls execution phase,
we've run into issues where subsystems aren't active on some LPARs and a
job with a SCHED setting gets interpreted on that system you get a JCL
error
What setting controls WLM managed initiator reuse?
On Tue, May 2, 2017 at 12:16 PM, Salva Carrasco
wrote:
> If you have millions of it from WLM initiator, may be you aren't reusing
> the WLM initiator address space. Check your settings.
>
> ---
+1
On Thu, Feb 9, 2017 at 10:52 AM, John Mattson
wrote:
> Why not admit that management it just not flexible, innovative, smart
> enough to determine whether their employees are working effectively. I
> totally view this as an admission of management's failure to keep up with
> changing technol
Large shop, 750M. I don't see what # of address spaces matter, it's more
product mix. IMS DBCTL is by far our biggest user, followed by VTAM/TCPIP
followed by DB2. Any ECSA usage would be too much in my opinion, move
above the bar and be free! We have an every other weekend IPL schedule,
and the
I've rolled it out into 2 of our test LPARs and have been using the HIS 113
records to try and measure the improvement. Specifically looking at the
percentage of TLB miss processor cycles. I haven't seen an improvement
using that metric, going into production this month so stay tuned.
On Thu, M
