Re: Starting TCP -- 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.

IP does NOT need to be running for the LAN console to function. It uses a short IP stack that is part of the LIC. This is why you can use the console while in dedicated system mode! Additional this interface is what's used for network based virtual optical drives so they too are available when in dedicated system.

- Larry "DrFranken" Bolhuis

www.frankeni.com
www.iDevCloud.com
www.iInTheCloud.com

On 4/17/2013 12:03 PM, John McKee wrote:

I'm confused. There is a startup job on the controlling subsystem.
Essentially the first thing it does is call QSTRUP. Then, it does STRTCP.
I retrieved the source of QSTRUP. Nothing about starting TCP in it.

This startup job, not from IBM, has a MONMSG CPF9999 following the STRTCP
command.

I thought that TCP would have to be up before the LAN console would be
available. This STRTCP was added locally to the vendor code back in 1998.

Two questions:

1) When/how is TCP started?
2) Is this STRTCP doing anything or just a relic from a long time ago?

I believe this modification dates back to when we were on a CISC box and
just starting on networking.

Currently at v5r4m0.

I can explain why I was looking, but it started with a request from the
boss.

John McKee

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.