×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On 12/8/2015 5:20 PM, Justin Dearing wrote:
I wrote a cursor in SqlWorkbench/J. Generated some PASE commands with sql
string concatenation so I could loop through with a cursor and execute. It
failed terribly and the job won't die. WRKUSRJOB only shows my greenscreen
job as active and a bunch of OUTQ status jobs. So how do I find the job
created by the JDBC connection so I can kill it?
Wrkactjob will bring up a list of all active jobs on the system.
Press F11 a few times until the display shows Current User. It'll be
one of the columns on the leftish side.
Move the cursor into that column and press F16 (Shift F4) and the
display will sort by that column. Now you can page down until you see
your user ID. It'll probably be on a job named QZDASOINIT.
Use option 5 to wotk with the job, then 10 to see the job log. If that
looks like your job, F3 to get back to the WRKACTJOB display and take
option 4 to kill it.
What's happening under the covers is the system creates prestart jobs
(that's the actual term) which are pre-established, waiting for work to
arrive to spring into action. It's a performance enhancement. When
that job starts, say Monday at 0001, it runs with a profile called QUSER
- a generic profile. When your JDBC work arrives, the system attaches
it to one of these prestart jobs and does a profile swap to your
profile. So the profile attached to the job is QUSER, but the CURRENT
PROFILE is JUSTIN.
Hope that helped.
midrange.com
