I've had this problem before. The simple way to get around it is to create a
MODULE EXEC, and in it, do an "Address Command" commandline. This removes
the normal selection of execs before modules, and executes the module given
in commandline. The whole exec would look like:
/* module exec */
Parse arg commandline
Address Command commandline
Exit rc
--
.~. Robert P. Nix Mayo Foundation
/V\ RO-OE-5-55 200 First Street SW
/( )\ 507-284-0844 Rochester, MN 55905
^^-^^ -----
"In theory, theory and practice are the same, but
in practice, theory and practice are different."
On 12/20/07 9:53 AM, "Gentry, Stephen" <[EMAIL PROTECTED]>
wrote:
> It's my understanding that when an EXEC and a MODULE are named the same,
> the EXEC will run first. I have a situation where the EXEC and MODULE
> are named the same and are on the same mdisk. Is there a way, from the
> command line, that I can invoke the module and not the EXEC?
> Yes, I can move the MODULE to a different mdisk, RELease the the
> connection to the EXEC mdisk and invoke the module, but what about a
> situation where this cannot be done?
> Thanks,
> Steve G.
