original-
De: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] Em nome
de Smith, Sean M
Enviada em: quarta-feira, 13 de setembro de 2006 15:21
Para: IBM-MAIN@BAMA.UA.EDU
Assunto: Re: CA7 Slowdown after 1.7 implementation
Chris,
Do you have any updates on this issue for us?
Sean Smith
There are a couple of issues that were actually going on.
In 1.7 the INTRDR processing is done in the Address Space allocating
the Reader. It is possible that an Address Space that is not optimally
qualified in the WLM Service Policy, may not get access to the Processor
as much as you'd like. The
Chris,
Do you have any updates on this issue for us?
Sean Smith
Bank of America
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the
Do you have any updates on this issue for us?
Sean Smith
Bank of America
Norm Hollander has been working directly with IBM and with the CA7
development team and I have been standing on the sidelines - actually I
have spent most of the last month and a half doing the planes, trains
and
Any updates from those who were impacted by this? IBM problem? CA
problem? Tuning opportunity? We have z/OS R7 on all but our largest
on-line systems and two CA7 test instances running fine but have not had
the chance to move the production CA7 to an R7 system. I hope to get
that done this
Casey,
My shop runs CA7 extensively, and we encountered an issue simlar to yours.
However, it was not related to the migration z/OS v1.7. We discovered this
in the later part of 2005, prior to my migration to v1.7. My Performance
Team recommends you look at your Dormancy and Hold values for
We do not have CA7 but run ASG Workload Scheduler. We are about to go live
with Z/OS 1.7 on the 12. Is anybody aware of a similar problem with
Workload Scheduler (aka Beta42) under 1.7?
Thanks,
Liliane
Has anyone had any issues with CA7 since moving to 1.7. We have 14
sysplex's and
Has anyone had any issues with CA7 since moving to 1.7. We have 14
sysplex's and only have this problem in one. The one having the problem is
the largest with the heaviest volume. We believe this is due to the JES
internal reader changes made in 1.7. We have increased the dispatch
priority of
Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Casey Rhodes
Sent: Thursday, August 03, 2006 8:59 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: CA7 Slowdown after 1.7 implementation
Has anyone had any issues with CA7 since moving to 1.7. We have 14
sysplex's and only have this problem in one. The one having
Well, I hopefully will be able to answer this sometime next week. Our
plan is a Monday morning z/OS 1.5 to 1.7 upgrade on our last
production (2 of them ) image where CA-7 just happens to be running.
Nothing in test but then again this is one of those that might be
hard to see in test.
At
Casey,
May I ask what release of CA7 you are on?
Ed Micucci
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at
IBM-MAIN@BAMA.UA.EDU
08/03/2006 08:58 AM
Please respond to
IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU
To
IBM-MAIN@BAMA.UA.EDU
cc
Subject
CA7 Slowdown after 1.7 implementation
Has anyone had any issues with CA7 since moving to 1.7. We have 14
sysplex's and only have this problem
Casey,
We are running CA7 v3.3, level 0412 (SP6). In fact, we moved to this
version for z/OS 1.7 compatibility. This Monday morning we'll be
upgrading the partition where CA7 runs from z/OS 1.5 to 1.7.
Will let you know how it looks.
In the meantime, what version and level of CA7 are you
In the Plex we are having issues we are stil 3.3. In our other
environments we are half 3.3 and half V11 with z/OS 1.7 in all
environments. I just want to point out to everyone the only place we have
seen this is in our heaviest processing environment at the time of peak
production.
14 matches
Mail list logo
