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 locks
occur is absolutely fine.  It also can't be a CFINT, Client Access or
communications 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 local
and 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 the
fly, triggering this kind of response, cause the CPU to be very high?  I'll
still 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 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.

 -----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 unavailable


> We are having a problem where some users of our in-house system are 
> freezing
> for several minutes.  The 'X' appears in the bottom left of the screen and
> remains 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 very
> difficult,  They never timeout and to make it even more difficult to trace
> the 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 level
> because users of other systems implemented on the same iseries do not have
> this 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@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 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.
>
>