You don't seem to be able to put any values on the phantom line (and if you do, they seem to be ignored). I never tried Commons for this.
Another method I use is I create a VOC entry based on UserNO and something static like: (ex. 101phantom) <1>PA <2>RUN LIB PROGRAMNAME PASSVAR1 PASSVAR2 PASSVAR3 PASSVA4 Then EXECUTE "PHANTOM 101phantom" Inside PROGRAMNAME: [EMAIL PROTECTED] PASSVAR1=FIELD(CMDLINE," ",4) PASSVAR2=FIELD(CMDLINE," ",5) ETC... Include the VOC ID as one of the PASSVAR, and have the program DELETE the VOC ENTRY. George >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] >Sent: Monday, March 29, 2004 2:26 PM >To: [EMAIL PROTECTED] >Subject: Re: COMMON Variable. > > >In a message dated 3/29/2004 1:11:11 PM Eastern Standard Time, >[EMAIL PROTECTED] writes: > >> > Is there a way to pass some common variable to a Phantom >> program - which >> > will be called using EXECUTE 'PHANTOM XXXX'. >> > >> > I've even tried named COMMON and it lost its value. > >Yes Carolina. There are a few ways >1) EXECUTE "PHANTOM XXXX some other stuff interpreted as variables" >2) MYSTUFF = "here are some more arguments" >WRITE MYSTUFF TO FILE, ITEM >EXECUTE "PHANTOM XXXX" (which starts by reading MYSTUFF) >3) disconnected processes >process A writes stuff and moves on >process B at some other disconnected time EXECUTE "PHANTON >XXXX" which reads the stuff writen by process A five minutes >or five days ago >4) process A, B, C, D, E, etc write various stuff at various times >process P starts the PHANTOM at boot time and it runs forever. > The phantom periodically wakes up and looks for something to >do, does it, then goes to sleep for a minute or so. > >Will "Phantom" Johnson >-- >u2-users mailing list >[EMAIL PROTECTED] >http://www.oliver.com/mailman/listinfo/u2-users > -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
