SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, 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.

The Southern California OS/2 User Group
USA

SCOUG-Programming Mailing List Archives

Return to [ 26 | October | 1999 ]

>> Next Message >>


Date: Tue, 26 Oct 1999 08:39:12 PDT
From: Peter Skye <pskye@peterskye.com >
Reply-To: scoug-programming@scoug.com
To: scoug-programming@scoug.com
Subject: SCOUG-Programming: REXX file lock/unlock, program instances

Content Type: text/plain

Aaron Lawrence wrote:
>
> > -- How do I lock a file,
>
> In rexx, all files are opened non-share, so
> are automatically locked (AFAIK) and no other
> program can access them

Hi Aaron,

I wrote some test programs just now (Warp 4 FixPak 10), and they allow
me to open a file in one program and, while the file remains open, open
and read the file in another program. Thus, the files aren't locked
while open. This may be specific to OS/2 and other platforms may lock
the files while open.

> > -- How can an executing REXX .cmd file
> > find out if it is already running?
>
> Some sort of nasty external flag e.g. create
> a file at startup. ... Unfortunately ... you
> can't use OS/2 semaphores which are better,

Mutexes were added in one of the FixPaks (I have them in FixPak 10 and
they seem to work fine). I was hoping there would be some one-line
solution. (The documentation is only in \OS2\BOOK\OREXX.INF under
Rexx Utilities (RexxUtil) but the mutex semaphores are in both Object
Rexx and Classic Rexx. Don't know why the Classic Rexx documentation
wasn't updated.)

> Basically Rexx is best not used for situations where
> multiprocessing matters (or any "serious" task) IMHO

I very much agree. I'm trying to move a set of old DOS programs over to
OS/2 and I'm hoping I can glue everything together with some Rexx.

Thanks. :)

- 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-programming".

For problems, contact the list owner at
"rollin@scoug.com".

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


>> Next Message >>

Return to [ 26 | October | 1999 ]



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.