Re: User Action commands different from command line?

Hey Gene,

There should be no difference between running a user action or directly
from the command log.
I imagine that since your program is writing to the file member, a lock is
being automatically placed.  I would venture to guess that if the program
doesn't "close" the file member (using C/java terminology) for some
abnormal reason then that the file/member lock remains.

thanks,

Violaine Batthish
WebSphere Development Studio Client, IBM Toronto Lab



wdsci-l-bounces@xxxxxxxxxxxx wrote on 09/15/2006 11:27:08 AM:

Nevermind.  The last two times I ran this from the command line it
worked the first time and locked the second time.  When I run this
command from the green screen it hasn't locked the member (so far).
Only  when running through WDSC has the member been locked, and not
every time.  Confusing.

Gene

Gene Burns wrote:

I set up a User Action to run a command to update blocks of RPG source
with mod marks and also to comment out blocks of source.  When I use
the User Action the source is locked and I have to restart WDSC to
free the lock.  When I run this command through the command line, the
source is not locked.  Anyone know why this is different as a User
Action?

Gene