Re: TELNET from IBM i / OS/400 to IBM mainframe? -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Jack, Dave ...

Wow.

Reading those links below, it describes the "NULL" client identifier.

So, I decided to try this:

TELNET RMTSYS(xxx.yyyyyy.zzz) PORT(nnnn) RMTVRTDSP(NULL)

and, it worked! :-)

Thanks, everyone ... :-D

All the best,

Mark S. Waterbury

> On 7/11/2018 11:03 AM, Jack Woehr wrote:

Pretty sure your admin should deal with it:

*The simplest way to assign LUs is to create a default LU group that Telnet
can use for all terminal connections. DEFAULTLUS is a combination statement
that defines the LUs in a default group and maps the group to the NULL
Client Identifier. If the client's Client Identifiers do not match any LU
mapping statements, the client is identified by the NULL Client Identifier
and will be assigned LUs from the default group.*

<https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.halz002/telnet_defaultlus_stmt.htm>
DEFAULTLUS Statement
<https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.halz002/telnet_defaultlus_stmt.htm>

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.