From:	CRDGW2::CRDGW2::MRGATE::"SMTP::CRVAX.SRI.COM::RELAY-INFO-VAX" 29-JUN-1989 01:26
To:	MRGATE::"ARISIA::EVERHART"
Subj:	Re: EMULEX... Trouble... Trouble... Trouble... Trouble...

Received: From KL.SRI.COM by CRVAX.SRI.COM with TCP; Wed, 28 JUN 89 21:05:10 PDT
Received: from ucbvax.Berkeley.EDU by KL.SRI.COM with TCP; Wed, 28 Jun 89 21:06:43 PDT
Received: by ucbvax.Berkeley.EDU (5.61/1.37)
	id AA15851; Wed, 28 Jun 89 21:00:46 -0700
Received: from USENET by ucbvax.Berkeley.EDU with netnews
	for info-vax@kl.sri.com (info-vax@kl.sri.com)
	(contact usenet@ucbvax.Berkeley.EDU if you have questions)
Date: 28 Jun 89 17:19:54 GMT
From: ecsvax!tpmsph@mcnc.org  (Thomas P. Morris)
Organization: UNC Educational Computing Service
Subject: Re: EMULEX... Trouble... Trouble... Trouble... Trouble...
Message-Id: <7263@ecsvax.UUCP>
References: <459@acad.cut.oz>
Sender: info-vax-request@kl.sri.com
To: info-vax@kl.sri.com

In article <459@acad.cut.oz>, CSJR@acad.cut.oz (Steve Rollinson) writes:
 ...describes problems setting up terminal server (emulex) for lat
 queue usages, resulting in messages like...
	>    %PSM-E-WRITEERR,  error writing !AS
	>    -LAT-F-NOMSG, Message number 01769F7C
 ... and ...
	> %DIRECT-F-WRITEERR, Error writing LTA etc......
	> -RMS-F-WER, file write error

I've got a _bunch_ of queues on both DECservers and Emulex P4000's, and
I've run into this problem on both flavors of beasts. The problem you are
encountering is probably caused by one of four  things, with the last two
listed below as the most likely cause:

	1) Improper definition of the LTAxx: port definition
	   via LATCP/LTLOAD, or
	2) Device protections, or
	3) Most likely, the emulex server doesn't know its own
	   name, and has configured itself internally as some 
	    LAT_00000000000000 name (where those 0's are replaced
	   by the ether hardware address of the server.
	4) The port doesn't have the name you specified in your 
	   LATCP SET PORT command.

(Actually, (1) and (4) are sort of the same problem.)

What to check:
	Use TSM or NCP CONNECT and do a SHOW SERVER NET command (for
EMULEX) or SHO SERVER (for DEC), and see what the "Name:" is. If it is 
one of those LAT_000000000000 names, then SET and DEF SERVER NAME to
change it in the volatile and perm settings.

	Also use TSM or NCP CONNECT to SHO PORT, and see the port "Name:".
Now check to make sure these match what was set in the LATCP SET PORT
/APPLICATION/NOLOG/NODE=server-name/PORT=port-name  command used to create
and configure the server port.

-----------------------------------------------------------------------------
Tom Morris                                 BITNET: TOM@UNCSPHVX
UNC School of Public Health                UUCP  : ...!mcnc!ecsvax!tpmsph
-----------------------------------------------------------------------------

-- 
-----------------------------------------------------------------------------
Tom Morris                                 BITNET: TOM@UNCSPHVX
UNC School of Public Health                UUCP  : ...!mcnc!ecsvax!tpmsph
-----------------------------------------------------------------------------