SCOUG-HELP Mailing List Archives
Return to [ 26 |
March |
2004 ]
<< Previous Message <<
>> Next Message >>
Date: | Fri, 26 Mar 2004 14:17:44 PST8PDT,4,1,0,3600,10,-1,0,7200,3600 |
From: | Harry Motin <hmotin@sbcglobal.net > |
Reply-To: | scoug-help@scoug.com |
To: | scoug-help@scoug.com |
Subject: | SCOUG-Help: killing one of several .cmd files |
5
=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================
Content Type: text/plain
Peter,
Your statement is not true. As I said, I have a Rexx script that looks for the presents of a particular program running. It has code to start the program. Then, it loops until it finds it find that program loaded and running. Then it continues.
The scenario that I described to you, using the output of the 4 compound variables returned by the DOSPIDLIST is exactly what you need to locate and identify, by process ID #, the program that you want to kill. To repeat, you find the program by pathname in the second compound variable. Then, you find it by process ID in the first compound variable. Whatever program you want killed, you KNOW its pathname. Find it in the second variable. Whatever position it occupies in that compound variable, its process ID occupies the same position in the first variable. Then, use The DOSKILLPROCESS function to kill it, placing the find ID in that function.
Peter, I have the Rexx Library user's manual sitting right here in front of me. I'm looking at it right now. Those functions are what I use in my script.
HCMotin
Peter Skye wrote:
=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================
Harry Motin wrote:
>
> This library has a function, DOSPIDLIST, for identifying
> all the processes that are running on your computer.
The problem is that you can't look at the PSTAT /C list and figure out
which program is which process, and the function you suggest doesn't
appear (from your description) to give any more info than PSTAT /C
supplies.
- Peter
=====================================================
To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".
For problems, contact the list owner at
"rollin@scoug.com".
=====================================================
Content Type: text/html
Peter,
Your statement is not true. As I said, I have a Rexx script that looks for the presents of a particular program running. It has code to start the program. Then, it loops until it finds it find that program loaded and running. Then it continues.
The scenario that I described to you, using the output of the 4 compound variables returned by the DOSPIDLIST is exactly what you need to locate and identify, by process ID #, the program that you want to kill. To repeat, you find the program by pathname in the second compound variable. Then, you find it by process ID in the first compound variable. Whatever program you want killed, you KNOW its pathname. Find it in the second variable. Whatever position it occupies in that compound variable, its process ID occupies the same position in the first variable. Then, use The DOSKILLPROCESS function to kill it, placing the find ID in that function.
Peter, I have the Rexx Library user's manual sitting right here in front of me. I'm looking at it right now. Those functions are what I use in my script.
HCMotin
Peter Skye <pskye@peterskye.com> wrote:
===================================================== If you are responding to someone asking for help who may not be a member of this list, be sure to use the REPLY TO ALL feature of your email program. =====================================================
Harry Motin wrote: > > This library has a function, DOSPIDLIST, for identifying > all the processes that are running on your computer.
The problem is that you can't look at the PSTAT /C list and figure out which program is which process, and the function you suggest doesn't appear (from your description) to give any more info than PSTAT /C supplies.
- Peter
=====================================================
To unsubscribe from this list, send an email message to "steward@scoug.com". In the body of the message, put the command "unsubscribe
scoug-help".
For problems, contact the list owner at "rollin@scoug.com".
=====================================================
<< Previous Message <<
>> Next Message >>
Return to [ 26 |
March |
2004 ]
The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA
Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS
RESERVED.
SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group.
OS/2, Workplace Shell, and IBM are registered trademarks of International
Business Machines Corporation.
All other trademarks remain the property of their respective owners.
|