| Title: | SNA GATEWAY NOTEFILE |
| Notice: | Note 1.* -> kits and doc, 288.* -> obtaining product support |
| Moderator: | EDSCLU::GARROD |
| Created: | Fri Feb 07 1986 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 7116 |
| Total number of notes: | 28576 |
Hi,
My customer is using the following products to communicate with
their mainframe:
Digital UNIX 3.2
Peer Server 2.1
Terminal/Printer Emulation 1.0
APPC/LU6.2 1.0
Once every month, the SNA backbone will be shutdown for monthly
maintenance. They claim that the LU6.2 applications cannot be
automatically connected back to the transaction in the mainframe
when the SNA network was back online. They need to manually stop/start
the LU6.2 software. They claimed that similiar applications in AIX can be
restarted without any problem. As they can use the Terminal/Printer
emulation when the SNA is back, the problem should not be in the Peer
Server.
I have following questions regarding the APPC/LU6.2 software:
1. Will the LU6.2 automatically connect back to the session when
the link is drop ? Is it an administrative issue or a programming
issue ?
2. If 1. is negative, then what is proper procedure to shutdown the
LU6.2 when the line is drop ?
I am trying to write some monitoring program to automate the stop/start
work. Answer to above questions will help me a lot to implement the
program.
Any comment are welcome
Best Regards
Colin Tong
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 7070.1 | Shut it all down and start it all over. | DELNI::BARBER_MINGO | Let me DANCE for you | Mon Jun 02 1997 12:12 | 26 |
Hello,
You state you have peer server 2.1. There is no peer server 2.1.
There is a 1.2, but it is VERY OLD and two revs behind the current
software.
In any case, 1.0 does NOT automatically restart sessions. The
safest way out is to stop all of the processes and start them all
OVER again.
Be aware, however, that the peer server itself does not notify
you of disconnects under certain circumstances. You must find out
what kind of shut down they do (making sure, if they have token ring,
that they aren't unplugging the ring ). You must then find out
what sessions they have killed. You would then re-initiate the
services modes, and then re-establish your sessions. I do NOT have
an example to give you to show you how. Every system's timing is
different, and hence has different requirements.
The alternative is to migrate EVERYTHING to the latest LU6.2 and
peer server software. LU6.2 3.1 is supported on Digital Unix 4.0, has
static configuration capability, and tries to re-establish sessions
for you on startup if you configure it to.
Luck,
Cindi
| |||||