|
Hi James,If you do have SQL statements running, then I suggest you run the database monitor and check. Yes, creation of a large index can cause this, I believe that 'create index over address space' is one instruction at the microcode level. Yes it would generally use a lot of CPU though. But if you have an 825, looking at the various models they mostly have several CPUs, and it would only tie up one so you might not notice it...
If you need any more help, let me know! cheers, Clare Clare Holtham Director, Small Blue Ltd - Archiving for BPCS Web: www.smallblue.co.uk IBM Certified iSeries Systems Professional Email: Clare.Holtham@xxxxxxxxxxxxxxx----- Original Message ----- From: "James Viney" <James.Viney@xxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx> Sent: Wednesday, January 11, 2006 11:06 AM Subject: RE: Screen freezing and Call Stack unavailable
Thank you all for your responses.However, I should have mentioned that CPU usage at the time all these locksoccur is absolutely fine. It also can't be a CFINT, Client Access orcommunications issue as all other systems are unaffected, just the users of one system - the one I'm responsible for! The users are a mixture of localand remote - both types being affected. Also, we are not using the CEEPAYS API. Sorry, yes, there are a very small number of SQL programs in the system which I will check - however wouldn't the creation of a large index on thefly, triggering this kind of response, cause the CPU to be very high? I'llstill make this my next investigation. Finally, we're on V5R2 and our model is 825. Thanks again for any help! James Viney Senior Analyst/Programmer Fortis Insurance Limited Fortis House Tollgate Eastleigh Hants SO53 3YA Tel: 02380 313324 Email: james.viney@xxxxxxxxxx Registered Address: Fortis House Tollgate Eastleigh Hampshire SO53 3YA Registered Number: 354568 England Authorised and regulated by the Financial Services Authority This e-mail together with any attachments are intended for the addressee only and may be private and confidential. If you are not the intended recipient, or the person responsible for delivering it to the intendedrecipient, you must not open any attachments, or copy, disclose, distribute, retain or use this e-mail, including any attachments, in any way whatsoever;please return it to us immediately using the reply facility on e-mail. -----Original Message----- From: midrange-l-bounces+james.viney=fortis.com@xxxxxxxxxxxx [mailto:midrange-l-bounces+james.viney=fortis.com@xxxxxxxxxxxx] On Behalf Of Clare Holtham Sent: 11 January 2006 09:39 To: Midrange Systems Technical Discussion Subject: Re: Screen freezing and Call Stack unavailable James, I should have asked you - what model do you have, and which version of OS/400? That might rule some things out... cheers, Clare Clare Holtham Director, Small Blue Ltd - Archiving for BPCS Web: www.smallblue.co.uk IBM Certified iSeries Systems Professional Email: Clare.Holtham@xxxxxxxxxxxxxxx----- Original Message ----- From: "James Viney" <James.Viney@xxxxxxxxxx>To: <midrange-l@xxxxxxxxxxxx> Sent: Tuesday, January 10, 2006 11:15 AM Subject: Screen freezing and Call Stack unavailableWe are having a problem where some users of our in-house system are freezingfor several minutes. The 'X' appears in the bottom left of the screen andremains there until the screens 'unfreeze' and can affect many users at any time. The users affected can all be accessing different parts of the system so trying to work out where the source of the problem lies is verydifficult, They never timeout and to make it even more difficult to tracethe problem, if I try to view the call stack of one of the frozen users, my screen then freezes for as long as the user's screen is! Eventually, my screen will either return with 'Call stack unavailable' or both screens will be unfrozen and the call stack is now available. Because we don't know if the problem is at file level, or which file(s) is/are causing the problem is difficult to put a trace on anything. Also it can be weeks before the next incident occurs. The system is written in RPG (v. old style to RPG ILE) and CL. Synon was also used extensively. Fingers are being pointed at programming levelbecause users of other systems implemented on the same iseries do not havethis problem. Can anyone advise why the Call Stack would be frozen and any action I can take to find the problem. Thanks, James James Viney Senior Analyst/Programmer Fortis Insurance Limited Fortis House Tollgate Eastleigh Hants SO53 3YA Tel: 02380 313324 Email: james.viney@xxxxxxxxxxRegistered Address: Fortis House Tollgate Eastleigh Hampshire SO53 3YARegistered Number: 354568 England Authorised and regulated by the Financial Services Authority This e-mail together with any attachments are intended for the addressee only and may be private and confidential. If you are not the intended recipient, or the person responsible for delivering it to the intended recipient, you must not open any attachments, or copy, disclose, distribute, retain or use this e-mail, including any attachments, in any way whatsoever; please return it to us immediately using the reply facility on e-mail. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.--This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing listTo post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. --This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing listTo post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.