On Fri, 04 Mar 2005 18:40:55 -0500, you wrote:
>Allen wrote: "Nope. Blank Common and Named Common are specific to each user
>process. So, if I run a program which initializes common, any other program
>run by me during that session has that data available, but that data is NOT
>available to a
Allen wrote: "Nope. Blank Common and Named Common are specific to each user
process. So, if I run a program which initializes common, any other program
run by me during that session has that data available, but that data is NOT
available to any other process."
Allen it is my understanding tha
On Fri, 4 Mar 2005 16:51:02 -0500, you wrote:
>Question on COMMON. Is there a way to use COMMON so that any subroutine
>can use the COMMON variables for that account. I'm thinking I could
>write a program that will set some COMMON variables and run as a phantom
>job. I would then have other pr
That would mean passing common across sessions. Something that I wish
was possible but unfortunately is not as far as I know.
Any routines that your phantom calls can see the common. But if you
telnet in or start another phantom that can't see it.
-Original Message-
From: [EMAIL PROTECTE
But named common only persists for the life of that session. If you want
some variables set to be used by several sessions then your only recourse
is to have your phantom write the variables to some kind of constant file.
Your other subroutines/programs would then read the constant item from
I do not believe this is possible. Named common is about as close as
you'll come, and that's session dependent. Can you write the
information to a file somewhere, load it up into named common, and
then be good for the rest of the phantom session?
-Original Message-
From: [EMAIL PROTECTE
A labeled/named common might work. As long as your phantom doesn't
stop, you might be able to.
BobW
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:owner-u2-
> [EMAIL PROTECTED] On Behalf Of Nick Cipollina
> Sent: Friday, March 04, 2005 1:51 PM
> To: u2-users@listserver.u2ug.or
