SCOUG-HELP Mailing List Archives
Return to [ 27 |
March |
2004 ]
<< Previous Message <<
>> Next Message >>
Date: | Sat, 27 Mar 2004 15:49:32 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,
Timing is the issue, I think. You should test it out by writing a little test Rexx script and having it write the PID information to an ASCII file, a different one, as follows:
1. Just before you start the first *.cmd program; that's your baseline PID's.
2. After you start your first *.cmd file and whenever the number of PID's increases by one
Start only one *.cmd file and see if it causes an increase by 1, only.
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:
>
> Here's what [Peter should do]:
> [Create] a single Rexx script to start each *.cmd
> program, one program at a time. . . . continually
> loop on the DOSPIDLIST function . . .
Okay, I understand now, thanks very much.
The Quercus Rexx library is $50. For $50 I'd rather run PSTAT /C and
parse the output to get the PID. I can still use your looping concept.
Legally it would be $100 because I'd need the Quercus library on two
different machines.
I'm a little worried about finding "the wrong PID" since these CMDs will
run at startup along with a bunch of other things. I would have to make
sure that none of the CMDs started any other CMDs; if they did, any PID
which I get might be the wrong one.
Thanks again, Harry.
- 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,
Timing is the issue, I think. You should test it out by writing a little test Rexx script and having it write the PID information to an ASCII file, a different one, as follows:
1. Just before you start the first *.cmd program; that's your baseline PID's.
2. After you start your first *.cmd file and whenever the number of PID's increases by one
Start only one *.cmd file and see if it causes an increase by 1, only.
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: > > Here's what [Peter should do]: > [Create] a single Rexx script to start each *.cmd > program, one program at a time. . . . continually > loop on the DOSPIDLIST function . . .
Okay, I understand now, thanks very much.
The Quercus Rexx library is $50. For $50 I'd rather run PSTAT /C and parse the output to get the PID. I can still use your looping concept. Legally it would be $100 because I'd need the Quercus library on two different machines.
I'm a little worried about finding "the wrong PID" since these CMDs will run at
startup along with a bunch of other things. I would have to make sure that none of the CMDs started any other CMDs; if they did, any PID which I get might be the wrong one.
Thanks again, Harry.
- 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 [ 27 |
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.
|