SCOUG-HELP Mailing List Archives

<< Previous Message << >> Next Message >>

Date:	Mon, 29 Mar 2004 04:26:20 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

Peter Skye wrote:
>The possible failure scenario that keeps nagging at me is that some
>other process might start a .cmd at the same time.

Well, you're right. But I personally do not know how else to do it. If you are worried by that failure scenario, then I would start my *.cmd programs, via the Rexx script, at a time after system startup, when I know that nothing else is going to screw up the identification of your *.cmd programs. For example, under XWorkplace you can order the running of your various startup programs. You can even set a delay between your various startup programs. I would run the Rexx script last.
HCM

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:
>
> Timing is the issue, I think.

The possible failure scenario that keeps nagging at me is that some
other process might start a .cmd at the same time. This is unlikely
except at startup, but startup is when my logging and monitoring
routines will all start. Your idea of polling the PID list is a good
one and as long as there is only one new CMD shown then there isn't any
confusion; I will just have to check to make sure there aren't multiple
new CMDs.

Thanks, 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".

=====================================================

=====================================================
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:
>
> Timing is the issue, I think.

The possible failure scenario that keeps nagging at me is that some
other process might start a .cmd at the same time. This is unlikely
except at startup, but startup is when my logging and monitoring
routines will all start. Your idea of polling the PID list is a good
one and as long as there is only one new CMD shown then there isn't any
confusion; I will just have to check to make sure there aren't multiple
new CMDs.

Thanks, 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".

=====================================================

Return to [ 29 | March | 2004 ]

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.