LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous messageNext messagePrevious in topicNext in topicPrevious by same authorNext by same authorPrevious page (November 2009)Back to main CICS-L pageJoin or leave CICS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Thu, 19 Nov 2009 09:17:57 -0600
Reply-To:     CICS List <CICS-L@LISTSERV.UGA.EDU>
Sender:       CICS List <CICS-L@LISTSERV.UGA.EDU>
From:         "Mullen, Patrick" <Patrick.Mullen@GWL.CA>
Subject:      Re: CPU Spike - CICS 3.2
In-Reply-To:  <200911191400.nAJBn3i3030148@malibu.cc.uga.edu>
Content-Type: text/plain; charset=us-ascii

My old CICS/TS v1.3 System Definition Guide lists LLACOPY as a SIT parameter way back then, why do you say it was new in v3.2?

-----Original Message----- From: CICS List [mailto:CICS-L@LISTSERV.UGA.EDU] On Behalf Of Judy Ellis Sent: Thursday, November 19, 2009 8:00 AM To: CICS-L@LISTSERV.UGA.EDU Subject: Re: CPU Spike - CICS 3.2

On Tue, 17 Nov 2009 16:46:12 -0500, Martin, Mike <Mike.Martin@NCSECU.ORG> wrote:

>All, > > > >We just upgraded to CICS TS 3.2 (z/OS). One of our production online >regions spikes the CPU for about 26 seconds. All the transactions >appear to stop during this time. I don't see a flood of transactions or >a single transaction contributor. After the 26 second spike, everything >goes back to normal. It doesn't seem to coincide with an activity >keypoint or statistics interval. It happened four times yesterday and a >few times today. Any theories/ideas are greatly appreciated! (we are >a VSAM shop w/o DB2) > > > >Mike Martin > ></PRE>This email may contain confidential and privileged material for the sole use of the intended recipient. If you are not the intended recipient, please contact the sender and delete all copies. Any review or distribution by others is strictly prohibited. Personal emails are restricted by policy of the State Employees' Credit Union (SECU). Therefore SECU specifically disclaims any responsibility or liability for any personal information or opinions of the author expressed in this email. > ></P> >

Mike,

Take a look in the Performance Guide v3.2.1(SC33-0659-01) In short v3.2 introduced a new SIT parameter LLACOPY=YES|NO|NEWCOPY YES being the default. This has been known to cause spikes. I coded LLACOPY=NO in my SIT parameters and have not noticed any spikes since I've installed v3.2 about a year ago. We are are a DB2/CICS vsam shop.

thanks,

Judy Ellis


Back to: Top of message | Previous page | Main CICS-L page