| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 7009.1 | Should work automatically | EDSCLU::PORCARO | | Fri Feb 14 1997 11:14 | 7 |
| Customer should not have to start the session. If he attempts
a conversation, the session will start for him at that time.
This assumes he negotiated session limits for the modename prior
to the LU going inactive.
Bill
|
| 7009.2 | They are activated as needed... | EDSCLU::BELANGER | DEBUGGING. The art of creating better bugs! | Fri Feb 14 1997 11:17 | 10 |
|
LU6.2 only proactively activates sessions after CNOS negotiation when
the conwinner auto-activate limit is not zero. Otherwise, it will
activate a session as an additional session is required and there is
sufficient session limit for the additional session. stopping/starting
the LU6.2 Server process is not necessary. Use the activate session
option of the /usr/lib/sna/lu62_config utility to activate sessions if
one is needed/desired before a conversation requests one.
~Jon.
|
| 7009.3 | | FREE::CAMBRIA | We're just one PTF from never talking to VTAM again | Fri Feb 14 1997 11:39 | 19 |
| > <<< Note 7009.0 by IB004::CODINA >>>
> -< LU6.2 server and LU deactivation >-
[deleted]
> And now the question: what happen with the session started by LU6.2
> server? Customer says that he has to stop/start the server to restore
> the session. Is there any possibility for automatic recovery of
> the session?
The peer server does _not_ tell the LU62 Server that an inop'ed line is now
contacted again <g>. Therefore, even if the min contention winner session
limit is non-zero, the LU62 Server will not know to automatically activate
that number of sessions.
As others have suggested, you need to manually activate a session (the
CNOS session I would guess, since peer-server cannot have one LU use more
than one link at a time, this session would also be lost on link discontact.)
MikeC
|
| 7009.4 | Nope- but if I had a dime for every time I was asked. | DELNI::BARBER_MINGO | Let me DANCE for you | Tue Feb 18 1997 18:01 | 13 |
| Hi,
People have written endless programs to address the issue.
They write programs that continue activating sessions into perpetuity.
In this way, they are re-connected if they need to stay connected.
There is no automatic detect.
If you happen to have a token ring...
You CAN parse the system log, it tells you when you've lost
and recovered the ring. Based on THAT, you know you have to restart
your sessions,and re-negotiate your limits.
Ugly, but true.
Cindi
|