|
Hi Vernon, Just to ask the obvious -- does the command point to a CPP in a particular library? Is the ALCOBJ locking the program in a particular library? Is your library list the same when calling from a command line vs the command (assuming the command specifies *LIBL for the CPP's library)? It just sounds like you're locking one program, but another is getting called. Peter Dow Dow Software Services, Inc. 909 425-0194 voice 909 425-0196 fax ----- Original Message ----- From: "Vernon Hamberg" <vhamberg@mn.mediaone.net> To: <midrange-l@midrange.com> Sent: Wednesday, February 13, 2002 11:23 AM Subject: Re: Lock on command processing program ignored > Yeah, that's a typical way to do things, and we do something like that. > > Question still is--why is lock ignored when program called through the > command? > > Mark Phippard wrote: > > > > If it is your own command, then you should change the CPP to ALCOBJ *EXCL > > on some *DTAARA object and release the lock when it is finished. > > > > Then you can have the validity checking program check for locks on that > > same *DTAARA objects and issue an error if it is locked. Of course I would > > also do the same in CPP in case the validity checker is removed. > > > > Hope this helps. > > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.