| Ivan,
The MtraceOptions=PTRACE (note: upper case) in the [XTI Transports]
section of win.ini along with setting the cfclogoptions=newlog log in
the [TeamLinks] section of office.ini should get you a log on the pc.
It sounds like the broker is not seeing anything since otherwise you
would at least get error messages. Would you please post the resulting
cfcdebug.log since it should show an error if it could not establish a
connection with the broker. The tlnk$remote_evl.log might be pretty
long if you don't override the timeout (e.g.
$ define tlnk$remote_timeout 60
sets the timeout to one hour. The default is one week. But if you
can post the nonrepetitive portions of the one associated with the
*same* cfcdebug.log it would help.
As a test that the PC can communicate with the OpenVMS system, can
you use a terminal emulator to log into the pc and verify you can
send/receive characters ok. e.g. write sys$output "abcdeFGHIJKL"
You should also be able to start the broker by doing a
$ run sys$system:tlnk$remote.exe
Note that you can only terminate this broker this way by typing six
Control-X's at it.
/ Peter
|
|
Thanks, I have asked hime to try your suggestions.
The interactive run of sys$system:tlnk$remote.exe. worked without
error. Though the PTRACE option produced the following CFCDEBUG.LOG
TLCOMMON: Transparent mode: Device = N, App = Y
XTIMOBL: zshhdr" 4 ZRQINIT 0
XTIMOBL: Received: TIMEOUT
XTIMOBL: No response to ZRQINIT
XTIMOBL: Cannot exchange INIT with server
ERROR 458: File cabinet service is not available.
XTIMOBL: zshhdr" 4 ZRQINIT 0
XTIMOBL: Received: TIMEOUT
XTIMOBL: No response to ZRQINIT
XTIMOBL: Cannot exchange INIT with server
ERROR 458: File cabinet service is not available
Resource open cancelled.
This is it. Sounds like it is a server problem again. But they say the
script connects OK, and they see the $ prompt at some point.
The Server log, they say, has no useful info in, but I am going to
ask for them to retry this.
Hope this helps
Many Thanks
Ivan.
|