TTA0 to Lat port settings..

[Nigel Wright_1]

We have a device TTA0:, which I think is a DZQ11 type device in a VAX. This used to direct talk to external device.

We now need to talk to a device - the same device - but in another room onsite. We have a DECServer located there and I have been atempting to set this up to the same task.

Here is the TTA0:

sho dev/full tta0:

Terminal TTA0:, device type unknown, is online, record-oriented device, carriage
control.

Error count 0 Operations completed 1154653563
Owner process "" Owner UIC [SYSTEM]
Owner process ID 00000000 Dev Prot S:RWPL,O:RWPL,G,W:RW
Reference count 0 Default buffer size 80



sho term/full tta0:
Terminal: _TTA0: Device_Type: Unknown Owner: No Owner

Input: 9600 LFfill: 0 Width: 80 Parity: Even
Output: 9600 CRfill: 0 Page: 24 Terminate on parity errors

Terminal Characteristics:
Interactive Echo Type_ahead No Escape
No Hostsync TTsync Lowercase No Tab
No Wrap Scope No Remote Eightbit
No Broadcast No Readsync No Form Fulldup
No Modem No Local_echo No Autobaud No Hangup
No Brdcstmbx No DMA No Altypeahd Set_speed
No Commsync Line Editing Overstrike editing No Fallback
No Dialup Secure server No Disconnect No 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

We have alloacted LTA888 to this, which is as below:-

sho dev/full lta888

Terminal LTA888:, device type unknown, is online, record-oriented device,
carriage control.

Error count 0 Operations completed 161
Owner process "" Owner UIC [SYSTEM]
Owner process ID 00000000 Dev Prot S:RWPL,O,G,W:RWPL
Reference count 0 Default buffer size 80

sho term/full lta888
Terminal: _LTA888: Device_Type: Unknown Owner: No Owner

Input: 9600 LFfill: 0 Width: 80 Parity: Even
Output: 9600 CRfill: 0 Page: 24 Terminate on parity errors

Terminal Characteristics:
Interactive Echo Type_ahead No Escape
No Hostsync TTsync Lowercase No Tab
No Wrap Scope No Remote Eightbit
No Broadcast No Readsync No Form Fulldup
No Modem No Local_echo No Autobaud No Hangup
No Brdcstmbx No DMA No Altypeahd Set_speed
No Commsync Line Editing Overstrike editing No Fallback
No Dialup Secure server No Disconnect No 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


We are getting data set hangup error.

Any ideas what is wrong and what the DECServer port details should be?

Many Thanks Nigel

[Volker Halle]

Nigel,

without first looking at all the different settings... Can you communicate with the port on the DECserver ?

$ COPY some_file LTA888:/LOG

If this fails, you can't even establish a LAT connection to the remote port. The port must be set to 'access remote' and the DECserver and port name must be set with LATCP> set port lta888:/node=xxx/port=yyy

Volker.

[Nigel Wright_1]

I tried:-

> copy/log login.com; lat888:
%COPY-E-OPENOUT, error opening LAT888:[SYSMGR].; as output
-RMS-F-DEV, error in device name or inappropriate device type for operation
> copy/log login.com; lta888:
%COPY-E-WRITEERR, error writing LTA888:[]LOGIN.COM;39
-RMS-F-WER, file write error
-SYSTEM-F-HANGUP, data set hang-up
%COPY-W-NOTCMPLT, SYS$COMMON:[SYSMGR]LOGIN.COM;39 not completely copied
>

I did a connect via ncp and instead of letting in by typing access and then your in - it just let me try 3 times and then chucked me out! - eg locked session I had to do a control d to get out.

[Steve-Thompson]

Hi Nigel

You havent mentioned the configuration of the port connected to remote device.
(Modem or whatever) ie. the DECserver.
What model of DECserver is it?

Connect to the DECserver and look at the port in question.
The DECserver will have to support DTR signalling for modem control or you will need to configure for XON.

If the port doesnt coincide with the remote device then it will give the problems you are seeing.

You will need obviouly the speed/stop-bits/parity to conicide.

Access = remote

If XON isnt enough
set privilege (you'll need the password)
Signal control = enable
signal select = cts-dtr (or RI-DCD)

Have a look at these issues
Regards
Steven

[Heinz W Genhart]

Hi Niggel

what kind of cable ar you using. Straight or crossover?

Regards

Geni

[Volker Halle]

Nigel,

you can't communicate via LAT with the desired port on the terminal server (SS$_HANGUP is telling you this).

You need to check MC LATCP SHOW PORT LTA888: and the terminal server (name ?) and port settings (access remote ?) first.

Then worry about modem settings etc.

Volker.

[Nigel Wright_1]

That many replies don't know where to start.

Its a lovely (old) DS200/MC

> MC LATCP SHOW PORT LTA888:

Local Port Name: _LTA888: Local Port Type: Application (Queued)
Local Port State: Inactive
Connected Link:

Target Port Name: PORT_2 Actual Port Name:
Target Node Name: Actual Node Name:
Target Service Name: Actual Service Name:

The real problem I have is not being able to do a mc ncp connect node DS2D9B

It's in the ncp database.

> mc ncp sho node DS2D9B


Node Volatile Summary as of 11-JUN-2007 12:45:09

Node State Active Delay Circuit Next node
Links

4.209 (DS2D9B) 1.103 (xxxx)
>

On the cable - just checking.

Many thanks for your help and support.

Nigel.

[Volker Halle]

Nigel,

there is Node name in the LATCP database for port LTA888: - no wonder you can't connect via LAT...

Volker.

[Steve-Thompson]

Hi Nigel

(and good morning Volke)

Try using the MAC address
MC NCP CONN VIA EWA-0 PHY ADDR 08-00-2B-2D-9A-9D

Substitue the NCP circuit name "ewa-0" to whatever you need.

Regards

[Nigel Wright_1]

On more thing that might be relevant.

The network guys tell me they allowed the LAT protocol through to this port - by that I mean the port the DECSever plugs into - The DS200 boots (MOP - Loads) but does that prove that LAT is enabled?

Also I can plug a VT in and connect to a LAT service = node, so I suppose it must be working ok.

Not sure.

Thanks Nigel.