Re: Stalled job

[John McKee <jmmckee@xxxxxxxxxxxxxx>]

It was a case of hurry-up programming to try to satisfy a demanding
consultant coupled with bad data entry.  A very bad combination.  What
I saw gave the appearance of a stalled job.  But, it was in a tight
loop.  Too many things were backed up this morning to give me the
luxury of looking at the program to see >why< it had appeared to have
"stalled".  The obvious of job being put on hold was not the case.
Dumb, stupid program error.  Which has been fixed.

I panicked.  Doesn't bode well for a day to start off like that.

We now return control to more appropriate subjects.

John McKee

On Tue, May 15, 2012 at 10:38 AM, Darryl Freinkel
<dfreinkel@xxxxxxxxxxxxxxxxx> wrote:
> What size machine/LPAR is this occurring on?
>
>
>
> I have had experiences on the smaller systems or LPARS that are set up with
> a minimum of everything. The jobs do stall. This has been confirmed by IBM
> support.
>
>
>
> SQL is a particular culprit experiencing this problem.
>
>
>
> It seems that ILE programs need a certain minimum resource, but it's not
> published anywhere.
>
>
>
>
>
> Darryl Freinkel | Assignment 400 Group, Inc.
>
> Tel: 770.321.8562 ext 111
>
>
>
> --
> 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.