Re: Filled up the DASD! Now can't run a specific query...

On 11-Sep-2015 16:55 -0600, Bob Cagle wrote:

On 10-Sep-2015 17:16 -0600, CRPence wrote:

On 10-Sep-2015 13:13 -0600, Bob Cagle wrote:

<<SNIP>>
But now after the DASD issue, the job runs, but isn't doing
anything I can see. It shows as active on WRKACTJOB, but no
activity in the file I/O, call stack, or job log - it just sits
there with no movement.
<<SNIP>>

<<SNIP>>
And the stack is? I would expect likely a CQE query; seemed an
all-too-typical symptom [an apparent hang]. A LIC process dump
will include the LIC stack; a second dump taken some time
later, might expose changes [similar to F5=Refresh might, in
Work With Job (WRKJOB) for the Program Stack (*PGMSTK)].

The Program Stack includes QSQROUTE, QSQRUN2, and QDBGETMQO.

That shows the query is running SQE.

Not sure if that really answers your question or not? The WRKJOB
*PGMSTK is not moving at all that I can see.

The LIC process dump is either via the Start System Service Tools (STRSST), or after Start Service Job (STRSRVJOB) by using Dump Job Internal (DMPJOBINT) and then Print Internal Data (PRTINTDTA) to spool the Dump Identifier (*DMPID) produced by the prior DMPJOBINT request. In that output the full stack, beyond what is visible via the *PGMSTK, is presented.