× 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.



Rob,

Are you working with TSM on the 400?  Do you have the Admin Command Line
application on your PC?


Fritz Hayes 

| -----Original Message-----
| From: midrange-l-bounces@midrange.com [mailto:midrange-l-
| bounces@midrange.com] On Behalf Of rob@dekko.com
| Sent: Wednesday, January 08, 2003 1:45 PM
| To: Midrange Systems Technical Discussion
| Subject: Re: Determining a 'process id'
| 
| ENDJOB *CNTRLD didn't do it
| ENDJOB *IMMED didn't do it
| ENDJOBABN didn't do it.
| Nope, need to kill that process.  Thus breaking out to a system command to
| kill the job isn't going to cut it.
| 
| Care to look in on a little Sametime chat?
| 
| Laura Watson/D...       In the meantime, can you run the kill command with
| the information I gave you above:   772928/WATSON/QP2FORK?
| Rob Berendt/D...        Wouldn't that just be ENDJOB?
| Laura Watson/...        Well it would if that actually ended the job.  I
| have 3 that I'm trying to kill and I've been working with IBM to try and
| get the process IDs.  I'm waiting for a call back.  In the meantime, I
| noticed these jobs still running after signing off and I know they need to
| die.  I told them to end *immed and they are mocking me.
| Rob Berendt/D...        > help kill
|   kill: kill [-s signame] job ...
|   kill [-n signum] job ...
|   kill [-sig] job ...
|   kill -l [signal ...]
|   $
| > kill job 772928/WATSON/QP2FORK
|   kill: 001-0032 Number job is not valid.
|   kill: 001-0032 Number 772928/WATSON/QP2FORK is not valid.
|   $
| > kill 772928/WATSON/QP2FORK
|   kill: 001-0032 Number 772928/WATSON/QP2FORK is not valid.
| Rob Berendt/D...        I'm no expert on PASE.  To get to the shell I
| entered STRQSH for STaRt QSHell
| Laura Watson/...        If you do "ps -ef" once you are in the shell, does
| it show you a list of processes?
| Rob Berendt/D...        > help ps
|   help: 001-0014 Command ps not found.
|   $
| > ps -ef
|   USER            PID     PPID               STIME DEVICE       TIME
| FUNCTION
|   qsys              2        1 11-16-2002 01:27:08 -          000:02 -
|   qsys              1        1 11-16-2002 01:26:24 -          000:00 -
|   qsys              1        1 11-16-2002 01:26:53 -          000:00 -
|   qsys              1        1 11-16-2002 01:26:53 -          000:00 -
| Rob Berendt/D...        ...
| Rob Berendt/D...        qtcp              1        1 01-01-2003 22:59:27 -
|          000:00 -
| helen             1        1 01-08-2003 08:30:34 gdsp52s4   000:00
| cmd-wrknetf
| psobjowns         1        1 01-06-2003 21:26:05 -          000:00 -
| qtcp              1        1 12-29-2002 22:15:42 -          000:00 -
| qnotes        24514        1 01-08-2003 04:54:37 -          000:00
| pgm-qnninsts
| qsys              1        1 01-08-2003 00:38:40 -          000:00 -
| rob           24733    24726 01-08-2003 14:02:47 -          000:00 pgm-ps
| 
| qsnads            1        1 01-08-2003 00:38:47 -          000:00 -
| qsys              1        1 01-07-2003 23:49:42 -          000:00 -
| asset             1        1 01-07-2003 23:49:46 -          000:00
| pgm-ca0001c
| asset             1        1 01-07-2003 23:49:46 -          000:00
| pgm-ca0001c
| asset             1        1 01-07-2003 23:49:46 -          000:00
| pgm-ca0001c
| Rob Berendt/D...        ...
| Rob Berendt/D...        Oops, let me try this on GDIHQ and not GDISYS.
| Rob Berendt/D...        ps -ef
| USER            PID     PPID               STIME DEVICE       TIME
| FUNCTION
| ...
| watson       105420        1 01-08-2003 09:15:10 -          000:00
| pgm-qp2fork
| ...
| watson       106712        1 01-08-2003 13:24:28 watsons6   000:00
| pgm-qp2term
| watson       106638        1 01-08-2003 13:16:35 -          000:00
| pgm-qp2fork
| watson       106655        1 01-08-2003 13:22:56 -          000:00
| pgm-qp2fork
| watson       106713   106712 01-08-2003 13:45:30 -          000:00
| pgm-qp2shell2
| watson       106726   106713 01-08-2003 13:49:00 -          000:00
| pgm-qp2fork
| watson            1        1 01-08-2003 13:49:15 watsons5   000:00
| cmd-wrkactjob
| 
| Maybe I'd kill 106638, 106655 and 106726?
| Laura Watson/D...       I'll give that a try.  thanks!
| Laura Watson/...        I tried and they would not die.
| Laura Watson/...        Sorry it took me so long.  I got interrupted by
| Don Allen for 45 minutes.
| Laura Watson/...        Can you try and kill 106638, 106655, and 106726
| just in case it is an authority issue?
| Rob Berendt/D...        It won't be an authority issue.  There is another
| command... ENDJOBABN.  Can sometimes make strange things happen during
| your next ipl.  Built for just such a situation.
| Laura Watson/...        Another handy command they told me about is "ps
| -ef | grep watson"   The "|" is the bar above the \ key.  This lets you
| pare down the list.
| Laura Watson/...        That didn't work earlier, but I think it is just
| becuase my QP2TERM sessions were getting locked up.
| Laura Watson/D...       I also found documentation that shows the
| following command to help you trace from the process id to the AS400 job:
| 
| Laura Watson/D...       system qsh "cmd('getjobid 106638')"
| Laura Watson/D...       It returns:
| Laura Watson/...         Process identifier 106638 is
| 772928/WATSON/WATSONS5
| Laura Watson/...        When you get off the phone, can you help me kill
| these nasty jobs?  Thanks!
| Rob Berendt
| --
| "They that can give up essential liberty to obtain a little temporary
| safety deserve neither liberty nor safety."
| Benjamin Franklin
| 
| 
| 
| 
| bdietz@3x.com
| Sent by: midrange-l-bounces@midrange.com
| 01/08/2003 03:41 PM
| Please respond to Midrange Systems Technical Discussion
| 
|         To:     Midrange Systems Technical Discussion
| <midrange-l@midrange.com>
|         cc:
|         Fax to:
|         Subject:        Re: Determining a 'process id'
| 
| 
| you can use the "system" command(?) that allows you to run a CL command,
| such as ENDJOB
| 
| 
| -------------------------
|  Bryan Dietz
| 3X Corporation
| 614-410-9205
| 
| 
| 
| 
| 
| 
| rob@dekko.com
| Sent by: midrange-l-bounces@midrange.com
| 01/08/2003 01:40 PM
| Please respond to
| Midrange Systems Technical Discussion <midrange-l@midrange.com>
| 
| 
| To
| midrange-l@midrange.com
| cc
| 
| Subject
| Determining a 'process id'
| 
| 
| 
| 
| 
| 
| I had a coworker here working on an iSeries PASE based Tivoli solution.
| She asked me a question.  She has to issue a 'kill' command to stop a
| 'process id'.  She knows that it is a particular job, like
| number/user/jobname, however ENDJOB is not the appropriate command.  Is
| there a way to determine the process id?
| 
| Rob Berendt
| 
| 
| 
| 
| _______________________________________________
| This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
| list
| To post a message email: MIDRANGE-L@midrange.com
| To subscribe, unsubscribe, or change list options,
| visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l
| or email: MIDRANGE-L-request@midrange.com
| Before posting, please take a moment to review the archives
| at http://archive.midrange.com/midrange-l.
| 
| 
| _______________________________________________
| This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
| list
| To post a message email: MIDRANGE-L@midrange.com
| To subscribe, unsubscribe, or change list options,
| visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l
| or email: MIDRANGE-L-request@midrange.com
| Before posting, please take a moment to review the archives
| at http://archive.midrange.com/midrange-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.