topic Re: LAT protocol, Print queues, and dec servers in Operating System - OpenVMS

LAT protocol, Print queues, and dec servers

Clayton_12 — Thu, 10 Nov 2005 13:16:21 GMT

I’m having trouble connecting to decserver and ethernet devices to access legacy printers.

Queues currently sit on a OPEN VMS 6.2 box and are queued to a LTA port which is defined as a DEC server address and port #.

The Lat protocol appears to be running. I can see other nodes in the network.
However No matter what I try I cannot seem to connect a queue to these ports from openvms alpha 8.2?

Any suggestions on how to check and trouble shoot the LAT port connection from 8,2???

Re: LAT protocol, Print queues, and dec servers

Uwe Zessin — Thu, 10 Nov 2005 13:29:07 GMT

Did you compare the port's characteristics with those of a working one?

I once had a _very_ strange problem: one job got printed, the second failed :-(
turned out that I had two DECservers with the same name - outch!!

Re: LAT protocol, Print queues, and dec servers

Clayton_12 — Thu, 10 Nov 2005 13:38:22 GMT

I don't think it is a problem. Set up is print straight to LTANNN
NODe = LAT_MACaddress , port = port #

Yet queues always stall or pause when I try to print.

How can I tell it if my LTANNN device connection is live,

How can I tell if I can talk to node LAt_mac address on LAt ?

Re: LAT protocol, Print queues, and dec servers

Allan Bowman — Thu, 10 Nov 2005 14:02:08 GMT

You should be able to connect to the DECserver from the Alpha and vice versa. What method did you use to configure the DECserver? When you connect to the DECserver, you can monitor the port you are using while you try to print - see if it changes from the idle state.

Allan in Atlanta

Re: LAT protocol, Print queues, and dec servers

Jan van den Ende — Thu, 10 Nov 2005 14:07:17 GMT

Clayton,

dumbest question first, it has been known to help:
Are your DECservers and 8.2 systems on the same, or two bridged Ethernet segment(s)?
They have to be - LAT is a non-routable protocol!

Second: What is the state of the LTA port?

$ MCR LATCP SHO PORT LTAxxx /FULL

Post the answer, we will take it from there.

Proost.

Have one on me.

jpe

Re: LAT protocol, Print queues, and dec servers

Clayton_12 — Thu, 10 Nov 2005 14:23:14 GMT

Thx :
I'm out of my element here , I'm not quite sure how to connect to the dec_servers.

The only thing I see now are the LTA devices connected on the 6.2 system. Everything still works from there?

On the 8.2 system I can see other VMS and unix nodes , they say reachable.

How do I connect to the Dec server ??

Another printer is a DEC laser 3500 with a printserver? card in it. Currently configured has Lat printer. I can't this one working from 8.2 alpha either...

It has an outdated IP address on it, how could I connect to this printer to configure the printserver ethernet card???

Thx
Clayton

Re: LAT protocol, Print queues, and dec servers

Clayton_12 — Thu, 10 Nov 2005 14:50:34 GMT

Thx Jan
Yes it is the same network, no routing going on. HOwever there are vlans involved via cisco switches (2950's). I can see the 6.2 Alpha from the 8.2 Alpha on LAT. The 6.2 printing queues are fine, but 8.2 queues just don't want to go.

DECSERVER
$ MCR LATCP SHO PORT LTA1/FULL

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

Target Port Name: port_6 Actual Port Name:
Target Node Name: LAT_08002B02114C Actual Node Name:
Target Service Name: Actual Service Name:

DEC PRINT SERVER (3500 laser)
ocal Port Name: _LTA123: Local Port Type: Application (Queued)
Local Port State: Inactive
Connected Link:

Target Port Name: PORT_1 Actual Port Name:
Target Node Name: LAT_0040AF206EE0 Actual Node Name:
Target Service Name: Actual Service Name:

Thx
Clayton

Re: LAT protocol, Print queues, and dec servers

Jan van den Ende — Thu, 10 Nov 2005 15:19:20 GMT

Oops,
my mistake...

Those LTA ports, that would be as seen from the Alpha system?

In that case, the port HAS been created, ie, there IS communication between Host and Server.
The trouble is the State: INactive.

Are the printers also being accessed by the Vax system?
In that case, maybe the port as seen from the server is not queued?

hth

Proost.

Have one on me.

jpe

Re: LAT protocol, Print queues, and dec servers

Bojan Nemec — Thu, 10 Nov 2005 15:22:30 GMT

Clayton,

This means that the printer queues are active on yours 6.2 system? If this is true, which symbiont is used on this system?
You should use LATSYM (INIT or START /QUEUE/PROCESSOR=LATSYM) and not the default PRTSYM (/NOPROCESSOR). The difference between the symbionts is that LATSYM disconnects the port after each job and PRTSYM (the default) disconnects only when you stop the symbiont (STOP/QUE/NEXT).
If you have the PRTSYM on the queues you can print only when the queues are stopped (with STOP/QUE/NEXT) on the other system. If you have the LATSYM (on both systems) you can print from both systems and the simple queue on the server port will be in effect.

Bojan

Re: LAT protocol, Print queues, and dec servers

Vladimir Fabecic — Fri, 11 Nov 2005 01:25:18 GMT

Hello
Like Jan said, first check that your server with OpenVMS 8.2 and terminal server are on same ethernet segment or in the same VLAN (if you use Cisco or simular switches).
Can you connect to terminal server using MOP:
$ MC NCP CONN VIA EWA-0 PHYS ADDR
If not, talk to your network administration people to see how is your LAN configured.

Re: LAT protocol, Print queues, and dec servers

Steven Schweda — Fri, 11 Nov 2005 01:51:40 GMT

> Can you connect to terminal server using MOP:

With DECnet Plus (OSI, phase V), you'll get
something like:

ALP $ NCP CONNECT VIA EWA-0
%NCP-W-SYSMGT, System-specific management function not supported

Use SET HOST/MOP instead of NCP CONNECT.

If so, do that. Do we know which DECnet is
in use?

On my old junk (DECserver 200/MC), if you do
get connected, there's a "#" prompt (default
password: "access"). After that, it's either
obvious or else there's HELP. SHOW PORT is
popular. SET PRIVILEGE may be needed to
change anything (default password: "system"),
but with any luck, the problem is back on
the host.

Re: LAT protocol, Print queues, and dec servers

Jan van den Ende — Fri, 11 Nov 2005 03:30:57 GMT

Clayton,

try Bojans suggestion first!
I have vague memories of something similar, so I am guessing he has got the tiger by the tail!

Proost.

Have one on me.

jpe

Re: LAT protocol, Print queues, and dec servers

Anton van Ruitenbeek — Fri, 11 Nov 2005 04:30:49 GMT

Clayton,

Is the 6.2 system the only one using this printer (over LAT) ?
If so, possible is that you aren't using LATSYM as protocol with the queue. If there is only one system connecting you don't see a difference. Only LATSYM will disconnect the printer when ready and de default doesn't.
You also mentioned 'I can see the Unix machines', this is over IP (or not ?). IP is another protocol and is routable.
If you are using a decserver that is capable of IP, try to switch over to IP for this printer. If I'm right you can use LAT and IP mixed to the same port of the terminalserver (716).

AvR

Re: LAT protocol, Print queues, and dec servers

Michael Yu_3 — Fri, 11 Nov 2005 08:19:09 GMT

Hi Clayton,

Have you enabled outgoing connections?

LATCP> set node/connection=both

Thanks and regards.

Michael

Re: LAT protocol, Print queues, and dec servers

Clayton_12 — Tue, 15 Nov 2005 14:50:28 GMT

Micheals suggestion
LATCP> set node/connection=both

worked.

I actually thought I was okay here. And was embroiled in trying to set up queues and devices. Has someone said. Simplest is often best.

I tested ports by simple copy file.txt LTANNN:

Until I set connection to both I would get
RMS-F-WER, file write error
-SYSTEM-F-HANGUP, data set hang-up

Now it works fine.

Once again this community has provided me a wealth of knowledge all comments and suggestions greatly increase my wisdom in the OPenvms fiefdom.

Thanks All for the input and support.

Re: LAT protocol, Print queues, and dec servers

Clayton_12 — Tue, 15 Nov 2005 14:55:38 GMT

Thks All for feedback.
Great sugestions throughoput the thread

solutrion was
LATCP> set node/connection=both
as posted by Michaeal Yu

All the comments and feedback help me learn and I appreciate the contributions