quote who=Tom Dodds
We are migrating a company from an UltPlus system to UniVerse. We are
running UniVerse 10.1.11 on AIX 5.3.3. The UniVerse is running Pick
flavor.
The legacy application relays heavily on the use of LOGON port [command]
processes. So if you say LOGON 92 EOD.REPORT.25,
And you checked that the 'main' and/or current account doesn't have a
proc stored in the MD called EOD.REPORT.25?
Have you tried something like PHANTOM EOD.REPORT.25? And any chance
that the printer settings are also in the proc, so you don't have to
worry about the @tty settings?
Or if
Tom Dodds wrote:
One of the problems is that the LOGON does not populate the @tty variable
with PHANTOM or LOGON or anything else that we can find.
When using LOGON, the value of @TTY will be the actual unix level device
file name defined in the DEVICE record that is the target of the LOGON
Tom,
Maybe this is what you are looking for. @TTY will equal a lower case
'phantom' for phantom jobs. We use this to keep phantoms from going
through our login program. All of the output from the commands in a
phantom can be found in the PH file with the program name with date
and time as the key.
