Hi Forum,

Universe & SB+

I have a process that will take a substantial time to run. I need to
write the results to a temporary file. Our system generates workfiles
on active sessions (i.e. user logins) in the form of FILENAME,@PORT but
there is no association with PORT numbers during background processes.

Has anyone any wonderful ideas how to associate a PORT number with a
phantom, so that I can continue to use this method?

We like the use of temporary files by association of port numbers for
there reusability & no cleanups required.

I don't want to login as a dummy user either.

Cheers
Steve

Are there enough phantoms doing this process to make it worth having each
phantom known individually, or can you just pick a number like FILENAME,-1
or FILENAME,99999? Can you put the port number of the process initiating
the phantom in a work record somewhere and then have the phantom use THAT
number as a port number?

Mark Brown

"oz" <ozhiggsbus (AT) hotmail (DOT) com> wrote

why don't you do your own handling of ports for background processes?
You know how many ports you have available on your system, add a number
on top of that and use them as phantoms associating each number with
the background process id ...

I don't know if that'll work but its worth a try.

cheers

The SB+ variable @PORT is the same as the Universe variable @USERNO.
Phantom processes use the PID number and put a minus sign in front of
it. You could identify the PID number by grepping 'ps -ef' for the
program name and the PID. For example, if your process is called
FILENAME-20, you can do
SH -c 'ps -ef | grep phantom FILENAME-20'

I would use a global temp filename map and have a large list of temp
filenames available for use. Each phantom can grab a filename from the map,
mark it in-use and then create that file on the fly. Once the phantom is
done, the temp file can be deleted and then the filename can be marked as
not in-use so another phantom can use it. You can log the application, temp
filename, date, and time into a phantom activity log for later review. If
you really want to cover your rear, you can write a temp file I/O toolset
that includes a write application that generates a data tracelog for all
activity done per phantom, as well as open+create and close+delete routines
for managing the files and the filename map.

Glen
http://mvdevcentral.com
http://picksource.com


"oz" <ozhiggsbus (AT) hotmail (DOT) com> wrote