Re: way to reactivate (IP) ifc automatically?

>> I just upgraded my 510 from V3R7 to V4R2, and yes,
>> one of my inactive interfaces was re-activated
>> after the upgrade.  Caused me some problems
>> before I figured it out.

Gary,

Well, the QTCPIP doesn't "re-activate" an interface per se. Possibly what you
saw was due to the automatic reovery of the line. But it also could be a change
that's a result of changes made to
the QTCPIP job as part of what I fondly (??) refer to as the "APAR from hell",
aka SA59434 (et alia).

In a nutshell, if the QTCPIP job is instructed to start an interface it'll now
keep trying to start it until either (1) it gets a clear cut "this ain't ever
gonna work" failure indication or (2) 45' elapses. This change was introduced
because the server IOP's can take 2-3 minutes (or longer to vary on. The QTCPIP
job was previously not able to detect when a *NWSD was varying on after an IPL
as a result of ONLINE(*YES) being specified for the *NWSD. If it was, then the
interfaces wouldn't get started.

The workaround for this in the past was to require specifying ONLINE(*NO) for
the *NWSD. With the support that has been PTF'd back to V3R2, V4R1, and V4R2
(V3R7 will follow soon) the QTCPIP job now tests the status of the *NWSD,
*LIND, *CTLD, *DEVD objects and waits and retries the interface activation
later if any of these objects are "busy".

Is it possible that this retry logic is what actually caused the interface to
come active? If it was, it should be obvious enough from the messages in job
QTCPIP's joblog.

-john martz
IBM AS/400 TCP/IP PPP development (and stuff)
Internet e-mail:                     jmartz@us.ibm.com
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---