×
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.
"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 07/11/2018
12:38:49 PM:
The vendor may want a configuration change of some sort. So, I
will wait to recycle it until I know for sure. Since there are no
connections to this particular Telnet server instance it will be easy to
recycle.
OK, I found the problem. The way the mainframe is set up, there
is another communications server that sits between the Telnet server and
the CICS application server. This communications server is called VTAM.
There must be associated session definitions active in VTAM for the Telnet
sessions to be able to log on to the CICS application server. In this
case I had the associated VTAM definitions created but they weren't
active. After activating them and recycling the Telnet server, I can now
TELNET from our IBM i to our mainframe.
I found that both of the following command specifications worked
exactly the same in my case.
TELNET RMTSYS(...) PORT(...) PAGEUP(*F7) PAGEDOWN(*F8)
TELNET RMTSYS(...) PORT(...) PAGEUP(*F7) PAGEDOWN(*F8) RMTVRTDSP(NULL)
Thanks, all.
Sincerely,
Dave Clark
As an Amazon Associate we earn from qualifying purchases.