| Title: | TeamLinks for Windows |
| Notice: | Kit and ECO locations: See replies to note 8. o note 8. |
| Moderator: | ORION::chayna.zko.dec.com::tamara::eppes AN |
| Created: | Mon Aug 28 1995 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 2238 |
| Total number of notes: | 9650 |
Windows 3.11
TeamLinks 2.5-4
Customer has changed from their own modem bank (which they could
successfully use 8 bit no parity) to a Compuserve service provider
and they have to use 7bit even. The TeamLinks Remote script appears to
work, gets connected, but when the connection is being established from
the Information Manager to the file cabinet, they receive the error that
"The file cabinet server is not running or there is a network
connection error".
The logical...
$define tlnk$remote_noeight "Y"
....was added to a tlnk$remote.com and the script was
modified to call this command procedure. It made no difference.
Same error.
I asked what happens if they use the 7bit to their own
modem bank - same problem.
Asked the customer to capture a trace and debug log from the
server...
$DEFINE TLNK$REMOTE_DEBUG_ENABLED "Y"
$DEFINE TLNK$REMOTE_TRACE_ENABLED "1"
Edit WIN.INI
In [XTI Transports] add...
MTraceOptions=PTRACE
and to send via internet mail the log files so that I can
look at them. We tried and it did not capture the EVL log.
He says the terminal server is set to 7bit flow control XON.
The TTY devices by default are 8 bit but a command procedure
upon vms login sets them to noeight even parity.
The terminal server is a Digital 90L terminal server that
is set to 7bit.
We added trace to the office.ini
CFCLOGOPTIONS=NEWLOG LOG TRACE
I am not including entire log file but if anyone wants it I
can send it. The brunt of the information is...
CFCIOS DLL version: TeamLinks Client IOS ECO 4
XTIMOBL: Received: TIMEOUT
XTIMOBL: No response to ZRQINIT
XTIMOBL: Cannot exchange INIT with server
OafcOpenCabinetW Oafc Status: 55804042 Oafc Status2: 11
ERROR 566: Cannot connect to server node
Resource Open Cancelled
The above string is repeated several times
Checked the tty-typahdsz and the bytlm - 1500 and 60,000.
If they change to 8bit via their own modem bank they are
fine.
HELP!
DEBBIE
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2167.1 | Refer customer to 90L SPD | AIMTEC::ZANIEWSKI_D | Add Jean to the list of deserters! | Thu May 01 1997 09:32 | 5 |
Your customer is SOL. The DECserver 90L does not support modems,
only terminals and printers. He'll have to upgrade to at least a
90TL.
Dave Zaniewski
| |||||
| 2167.2 | but why? | AIMTEC::GIANNETTI_D | Thu May 01 1997 11:33 | 6 | |
Dave,
Why would it work if they are using 8bit no parity to the same
terminal server?
Debbie
| |||||
| 2167.3 | AIMTEC::ZANIEWSKI_D | Add Jean to the list of deserters! | Thu May 01 1997 15:14 | 6 | |
Just dumb luck. 8-bit/no parity is the basic "terminal" setting.
Something the 90L knows a lot about. They are probably generating
little or no traffic that require modem control to handle at this
config. 7-bit on the other hand, requires lots of help.
Dave Zaniewski
| |||||
| 2167.4 | changed terminal servers - no luck | ALFSS2::GIANNETTI_D | Tue May 06 1997 15:28 | 7 | |
Okay,
Customer tried a 90M (decserver) and a 300 - same problem.
Help!
Debbie Giannetti
| |||||
| 2167.5 | Debugging 7-bit tlremote problems | MANANA::FLANAGAN | Thu May 08 1997 10:43 | 36 | |
Debbie,
Can you establish a normal terminal session (outside of TeamLinks)
with the host? I.e. can you enter commands and use an editor for
example without a problem? This would indicate that the host is
receiving characters without a problem.
The tlnk$remote_evl.log would be very useful. If you're not getting
one I wonder if there could be a problem with those logicals getting
set. You can generate a very short log by logging on to the system
and typing:
$ run sys$system:tlnk$remote.exe
It should type something like the following back at you:
$ run sys$system:tlnk$remote.exe
TLNK$REMOTE Version V1.1-2 Started at Thu May 8 09:36:51 1997
TeamLinks Remote -- waiting for client to start...
You will then have to type six control-X's to get back to the command
prompt. You should get a very short log file with the current
time/date stamp.
While you're there, would you please do a
$ show logical tlnk$*
and a
$ show logical TT
to see if the logicals got set and the terminal is reading from the
input port?
/ Peter
| |||||
| 2167.6 | May need to set terminal parity too | MANANA::FLANAGAN | Thu May 08 1997 10:49 | 11 | |
Debbie,
You may also have to set the parity for the OpenVMS session using
$ set terminal/parity=even
But if you can communicate ok at the command prompt this may already
have been done via a login.com file.
/ Peter
| |||||
| 2167.7 | Dropping the 7bit tlremote project | AIMTEC::GIANNETTI_D | Mon May 12 1997 12:05 | 11 | |
Well guys,
I really really appreciate all your help but I called the customer
this morning for an update (after sending them requests from the
previous notes) and they stated they are dropping the project at
this point. May pick it up later but wanted me to close the call.
Hopefully the information in this topic will help someone else
down the road but no resolution on this one.
Debbie Giannetti
| |||||