How about creating a COMMON variable that the program can set before
executing the command with a CAPTURING clause?
David A. Green
(480) 813-1725
DAG Consulting
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Doug
From experimentation on unidata on linux, if you execute something with
capturing it creates an entry in _PH_ of Z_{pid} the pid is zero filled to
8 digits e.g. _PH_/Z_00022141
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org]
That's only partially correct.
The capture log file is put into _PH_ in the account that you originally logged
in to. If you change accounts with LOGTO you will need to use the @ACCOUNT
variable to find the original account path.
The capture file name (on my windows system) is Z_nnn where
UniData
Looks like there is no easy solution. Messages are shown in a generic
subroutine and I do not want to do a lot of IO or CPU time to determine
if CAPTURING is on. The subroutine is called thousands of times a day
for a user. For the few times this has happened over the years, I guess
I
You can fillet the fish in another manner.
If this is a *subroutine* being *called* then why do you also have an Execute
going on?
If the Execute...Capturing is the only Execute, then just use @LEVEL and for
the level in question (say 3) you do this and if it's less than that, you do
that.
