What is the CoB job that fails?

Is it a report job that has gone wrong somehow, generating
ridiculously large transactions?

Is it localdev or core?

If it is a report, should it run in CoB or can it be set to run on an
"A"dhoc basis instead?

On Feb 4, 4:16 pm, Jim Idle <[email protected]> wrote:
> Pawel (privately) wrote:
> > Hi,
>
> > I know that it sounds unbeliveable for most of you, but I would like to
> > share with problems that we started to face on our test servers about
> > 2-3 days ago.
>
> > We started to run out of memory errors on our test servers, eg.:
> > jsh t24fe ~ -->jdiag
> >  ** Warning [ PERFORM_ERROR ] **
> > Unix error number 0 while attempting PERFORM , Line   111 , Source jsh.b
> > Trap from an error message, error message name = PERFORM_ERROR
> > Line 111 , Source jsh.b
> > jBASE debugger->q
> > Are you sure ?y
> > .
>
> I meant to add that if valgrind can be compiled on your system, then you
> could run it against a jBASE program that exited normally. You will see
> that some allocations are left to the system to reclaim, but nothing
> from the application. However valgrind does have a useful heap
> examination tool that can identify where memory is being held out on the
> stack. I have only ever used it in Linux however.
>
> There are other tools for AIX, but I think that most of them would
> require source code. What does Temenos help desk say by the way? They
> are only going to have to ask the jBASE guys, but we have been through
> this sort of thing lots of times.
>
> Jim- Hide quoted text -
>
> - Show quoted text -

--~--~---------~--~----~------------~-------~--~----~
Please read the posting guidelines at: 
http://groups.google.com/group/jBASE/web/Posting%20Guidelines

IMPORTANT: Type T24: at the start of the subject line for questions specific to 
Globus/T24

To post, send email to [email protected]
To unsubscribe, send email to [email protected]
For more options, visit this group at http://groups.google.com/group/jBASE?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to