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 command. If the initiating interactive session and the target port for the phantom process have device files of the same format, then you will have a problem knowing what session you're currently dealing with. We use LOGON extensively for continuous printing processes and I'm able to get around this issue only because the processes are initiated from a telnet session. Our telnet session's @TTY format happens to differ from the termserver printer port @TTY. If you don't have this luxury, you might have to write out the LOGON target device file name somewhere and check for a match.
The second problem is that we can not find where the system is storing the [command] that is passed into the new session. We have displayed all of the @ variables that we can find in the basic manual and none of them contain the proper data.
@SENTENCE is where you normally find the arguments entered at TCL. However, I'm not sure if the program name would appear in @SENTENCE for the initiating process, @SENTENCE for the phantom process, or both. You could add "PRINT @SENTENCE" to your program and see where it appears.
-John -- John Hester System & Network Administrator Momentum Group Inc. (949) 833-8886 x623 http://memosamples.com ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
