On 13 April 2015 at 16:52, Gentry, Steve < [email protected]> wrote:
> Well, I thought I had this working with the STARMSG, etc. Used the gate > example. Worked fine on my userid, but I really need this to run on a > programmable operator. (did I forget to mention that detail? 8-) ) > When running on a programmable operator, I get the following: > > FPLSMG650E CP system service *MSG is in use by another program > FPLMSG004I ... Issued from stage 1 of pipeline 2 name "starmsg" > FPLMSG001I ... Running "starmsg CP QUERY LLICPDM" > Right. That's because PROP acquires all those connections and captures the traffic (you would not want your exec to intercept important messages that PROP was supposed to act on). If you want this in PROP, would issue the command and then route the response messages on their own, maybe with an action routine that inspects a GLOBALV that was set by the action that issued the query. Rob
