Re: Do NOT do ENDSBS without shutting down TCP first! -- 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.

It may have been more of a MAC address issue. The line description on both
the old and the new had the same mac addresses. Remember to vary those
lines off...

On Sat, Mar 4, 2023 at 7:10 PM Rob Berendt <robertowenberendt@xxxxxxxxx>
wrote:

Do NOT do ENDSBS without shutting down TCP first!

I've ran into issues in the past. One time was so drastic that it took a
lot of work to get 5250 to work again.

However, this time it was on an old lpar that I wanted to leave up, but in
restricted state in case I needed to compare stuff.
I actually brought it out of restricted state before firing up the new one
so I could print off the brms recovery report.
I probably skipped the ENDTCP stuff and jumped straight to ENDSBS *ALL.
Figuring if it damages stuff, what do I care? I burn the boats when
migrating.

Result was dueling IP addresses from the old/new system. Even though
WRKSBS, F11 showed QCTL as "RSTD". And you cannot see the interface status
or do ENDTCPIFC when the system was brought into restricted state like this.
Varying the lines off did it.

This is not OS400. Do not treat it as such. Treat it like IBM i. IBM
cautions you greatly about running ENDSBS without ending tcp first.

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.