Application uses CALLX to run a routine that does some processing. This
routine is FLASH-COMPILED with option 'O'.

When using the EXECUTE and/or OCONV statements, in this CALLX routine, it
starts a phantom user that doesn't terminate.

Is this a known fault and is there a fix for it or is this already fixed in
another version as were using 7.4.4 D3 NT server, else is there another way
of finding out what the account name is so that we can decide whether to
continue callx processing or not. We also have problems with opening for
instance pibs file with port number system 22 variable as we are not able to
open another file within a callx routine.

I'm assuming this is a "new" routine, or something that has changed?
What is the statuis of the port/pib/process that is running the routine
(WHERE) ... I'm guiessing it is in the debugger .... can you find out
more by tandeming to the routine?

7.4 release went to 7.4.7, now @ 7.5.1 - LOTS of fixes, and if people
are on maintenance, probably worthwhile .... for a start 7.4.7 should
give good backups !?!

ChrisM wrote: