Re: DECServer 700 help
- From: "John E. Malmberg" <wb8tyw@xxxxxxxxxxx>
- Date: Sat, 08 Sep 2007 06:05:55 GMT
bakermo wrote:
OK - it's been a while since I worked with a DECServer 700 so I wonder
if anyone can please give me some advice and/or help?
I am trying to configure a reverse LAT port from an Alpha GS140 to a
DECServer 700. I have a 4800 baud clock signal that will go into the
DECServer on port 7 and have VMS get the signal on LTA7.
The clock is ansi characters in the format:
203:00:00:02B
I presume you mean ASCII.
ANSI in this context usually applies to escape sequences used to control terminal functions, usually display features.
I have looked at this signal on a VT320 on a crash cart and it is OK.
(4800 baud, XON, 1 stop bit, noparity). The cable is connected via a
null modem into port 7 of the DS700.
Here's how the server port is configured:
Port 7: (Remote) Server: RAQ1TS
Character Size: 8 Input Speed: 4800
Flow Control: XON Output Speed: 4800
Parity: None Signal Control: Disabled
Stop Bits: Dynamic Signal Select: CTS-DSR-RTS-DTR
Should be 1 stop bit for anything other than 110 baud.
Access: Remote Local Switch: None
Backwards Switch: None Name: PORT_7
Break: Local Session Limit: 4
Forwards Switch: None Type: Ansi
Default Protocol: LAT Default Menu: None
Autolink Timer One:10 Two:10 Dialer Script: None
Preferred Service: None
Authorized Groups: 0-255
(Current) Groups: 0-255
Enabled Characteristics:
==========================================================
Here's the VMS LAT port:
Local Port Name: _LTA7: Local Port Type: Application
(Queued)
Local Port State: Active
Connected Link: TSLINK
Target Port Name: PORT_7 Actual Port Name: PORT_7
Target Node Name: RAQ1TS Actual Node Name: RAQ1TS
Target Service Name: Actual Service Name:
=========================================================
Here's the VMS LTA7 terminal:
Terminal: _LTA7: Device_Type: Unknown Owner: NAME
Username: USER
Input: 4800 LFfill: 0 Width: 132 Parity: None
Output: 4800 CRfill: 0 Page: 64
Terminal Characteristics:
Passall No Echo No Typeahead No Escape
No Hostsync No TTsync Uppercase No Tab
No Wrap Hardcopy No Remote Eightbit
No Broadcast No Readsync No Form Fulldup
No Modem No Local_echo No Autobaud No Hangup
No Brdcstmbx No DMA Altypeahd Set_speed
No Commsync No Line Editing Overstrike editing No
Fallback
No Dialup No Secure server No Disconnect Pasthru
No Syspassword No SIXEL Graphics No Soft Characters No Printer
Port
Numeric Keypad No ANSI_CRT No Regis No
Block_mode
No Advanced_video No Edit_mode No DEC_CRT No
DEC_CRT2
No DEC_CRT3 No DEC_CRT4 No DEC_CRT5 No
Ansi_Color
VMS Style Input
========================================================
A set host/dte LTA7 will show either nothing or sometime a buch of
characters that seem to be a baud rate mismatch.
Are you doing:
$allocate lta7
$set term lta7:/type
$set host/dte lta7:
......
$deallocate lta7:
Here's what the program is getting for the input:
Fmterr :OEOO¢
Fmterr :OEOOª
Fmterr :OEOO²
Fmterr :OEOOº
Fmterr :OEOOA
Fmterr :OEOOE
Fmterr :OEOO
Fmterr :OEOO
Fmterr :EOO
Fmterr :EOO
Fmterr :EOO¢
========================================================================
Here's what it should look like:
date= 7-SEP-2007 00:00:02.91 ,len= 23
date= 7-SEP-2007 03:59:36.00 ,len= 23
date= 7-SEP-2007 18:13:53.00 ,len= 23
========================================================================
The example from a running program is from another server that is
working except it is via a DS900. No - I don't have access to anything
but the DS700 and the other server is across the country in another
datacenter.
I copied its port and terminal characteristics with three exceptions.
1. The working system has NOAltypeahd on its terminal and I have no
idea how to set that on mine.
Altypeahd is a larger type ahead buffer. Having it on should improve things in most cases like this. Usually though I have needed to make it larger via AUTOGEN. But for a clock, it is probably not an issue.
2. The DS900 has no Signal Select: CTS-DSR-RTS-DTR setting
Watch how your cable is wired. If the DS900 does not support a signal pair, it should be jumpered at the end of the cable.
CTS should be jumpered to RTS, and DTR should be jumpered to DSR if the cable is not supporting them. Some devices will not send data if the CTS signal is not asserted. If the hardware supports it, it is preferable to use CTS/RTS for handshaking instead of XON/XOFF.
Normally though, your device should be asserting DTR when it is on, and that signal will be wired to the DECserver DSR line, which the application can monitor as a sanity check.
The DECServer should assert DTR when ever is allocated by an application, the crossover cable should connect this to the device DSR line. Devices may decide not to send data if they do not see a DSR signal. The lack of a DSR signal indicates to them that there is nothing on the other end of the wire.
Printers tend to use DTR/DSR for flow control instead of RTS/CTS for some reason. This is preferred as some terminals servers forget the state of the XON/XOFF when they are not allocated to a process on a host.
3. The DS900 has no Autolink Timer One:10 Two:10 setting
I am not remembering what this does, and not sure that it means anything in this application.
I have three systems that are all configured the same (all with
DS700's) and none work. I would think that eliminates a hardware
error.
It makes it unlikely that there is a malfunction in the DS700, but does not eliminate other errors.
Any thoughts?
The type of noise that you are seeing looks like either a baud rate mis-match or of a wiring error.
Verify that you have the baud rate right. Some devices will autobaud, which works when they are connected to a real terminal and someone hits enter, but does not work when they are connected to a computer type device.
The application should be setting the port to /typeahead after it assigns a channel to the ltann: device. Failure to do that may cause problems.
If modtap or modular connectors are involved, be aware that there are two signal commons on the cable. Both must be connected to the single signal common(ground) on the typical D connector. If you only run one, because of the twist in a NULL modem configuration, you actually end up with no signal commons being connected. Surprisingly I have seen this type of mis-configuration work most of the time, but it tends to fail with the phase of the moon. In one case it was found that the safety ground pin in the powerlines was handling the signal return because the modular to D connectors were miswired by having only one signal common connected at each end.
-John
wb8tyw@xxxxxxxxxxx
Personal Opinion Only
.
- References:
- DECServer 700 help
- From: bakermo
- DECServer 700 help
- Prev by Date: Re: Here's one for Bob (hope it makes your head spin)
- Next by Date: Re: VMS License Plates
- Previous by thread: Re: DECServer 700 help
- Next by thread: Re: DECServer 700 help
- Index(es):
Relevant Pages
|
