PCSTLNET013 on TN3270 Connection to OS/390 Host

[Shelby Beach]

Hi...

I periodically receive an error PCSTLNET013 attempting to connect to an
OS/390 system. The help for this error says:

An unknown error occurred during DEVICE-TYPE negotiation. Make sure the
Telnet3270 parameters are correct. This connection cannot be established.

Explanation: TN3270E protocol only. An unknown error occurred during
DEVICE-TYPE negotiation.

User Response: Make sure the correct LU name is specified in the Telnet3270
advanced customization window.

Well I have never changed any of the configuration information, and this
error will eventually go away without my changing anything (or at least it
always has before). I'm guessing that some limit on the number of TN3270
sessions on the host has been reached. Does anyone have any experience with
this error condition ?

Thanks.
Shelby

[B Thompson]

It may mean that you have an LU hard coded on your client side. In TN3270E
device type negotiations the client (your PC) can ask for a specific LU. If
that LU is in use by another session the device type negotiations will fail.
Once the other session logs off the lu would be returned to the "available
to use" pool and your negotiations would then be successful. A packet trace
of the session setup attempt would show you if your client is asking for a
specific lu. Running out of LUs is also a possibility. If you are
connecting via a MSG10 screen, turning on MSG07 support on the server would
display a panel that will indicate the reason for the failure.
Good Luck :)

"Shelby Beach" <shelby...@prodigy.net> wrote in message
news:96hb2q$fo2$1...@news.software.ibm.com...

[Shelby Beach]

Thank you. I'm pretty sure we've ehausted the pool of LUs, at least that's
what my systems programmer is telling me.

Thanks again.
Shelby

"B Thompson" <beli...@us.ibm.com> wrote in message
news:96hl78$v96$1...@news.software.ibm.com...

[John S. Giltner, Jr.]

If you are trully running of of LU's in the pool, LU's can be added
dynamically.

[Shelby Beach]

Yes, that's what the systems programmer finally did and that fixed the
problem. Thanks to everyone.

Shelby

"John S. Giltner, Jr." <gil...@mnsinc.com> wrote in message
news:3A8CA280...@mnsinc.com...