peter@vd.volvo.se (Peter Hkansson) (01/13/90)
To
the
small
line
eater :
(mums
mums
mums)
I'm posting this for a college of mine, i will forward
any help YOU can give them.
==============================================================
PROBLEMS WITH MOVING
SNA-SERVICES BETWEEN DIFFERENT
RT-PC'S
During installation of AIX 2.2.1 and SNA-services on 3 RT-PC's, we had
the idea that we could save time by installing one machine, backing it
up and restore the tape on the to other machines.
All machines have a multi-protocol adapter and we are planning on
sending files between the different machines using APPC (LU6.2).
The restoration of tapes worked very well except problems with
SNA-services. SNA-services works on the one machine where we first
made the installation. On the second machine we can run the program
"snaconfig" without problems. The configuration validates fine. The
program /etc/srcmstr also runs without difficulties.
Problems start with running the command "start sna". The command
starts out OK, but when we check with "ps -ef", the process has become
inactive. We also tried "snacontrol". The program runs fine but when
we try to start sna from the menues the process at first returns to
"active". It appears at first as if sna is running fine, but when we
issue the command "UPDATE" from the menue it appears that the process
has become "inactive" ("UPDATE" checks the different processes and
shows the active/inactive-status - what's on the screen may not be true
otherwise). Since the process now is inactive we can't start
connections and attachments. We get a message that indicates that the
server program is not running which we already knew (sna inactive).
Next we asked IBM Sweden, about solutions. They say that a particular
installation of SNA-services is tied to the very machine it is
installed on. Apparently is some kind of cpu-serial number checked.
They mentioned a command "peu" that perhaps could help but they weren't
sure. We found "/usr/lib/peu" but not in the manuals. Not in command
ref, inst. and maint, custom. AIX or in SNA services guide and ref.
Since we couldn't find the program in the manuals, we wern't able to
make "peu" run right.
The last idea we have is reinstalling SNA-services. We would rather
not do that since that requires rebuilding the kernel, followed by a
restart. The particular machine is in production at an HERTZ-rental
office and we prefer having the machine running 24 hours a day.
Does anybody know a fix for the problem without having to restart the
machine in the middle of the night.
SINCERELY THORSTEN JAKOBSSON, AXIELL AB
STURE LINGDEN, VOLVO CAR CORP.
PETER HAKANSSON, VOLVO DATA CORP.
Thanks!peter@vd.volvo.se (Peter Hkansson) (01/22/90)
I',m posting this for a friend without net access. However i'm also
partly involved in this, and will forward all Your responses to my friend.
Lets see if you netters can do better then IBM sweden!
PROBLEMS WITH MOVING
SNA-SERVICES BETWEEN DIFFERENT
RT-PC'S
During installation of AIX 2.2.1 and SNA-services on 3 RT-PC's, we had
the idea that we could save time by installing one machine, backing it
up and restore the tape on the to other machines.
All machines have a multi-protocol adapter and we are planning on
sending files between the different machines using APPC (LU6.2).
The restoration of tapes worked very well except problems with
SNA-services. SNA-services works on the one machine where we first
made the installation. On the second machine we can run the program
"snaconfig" without problems. The configuration validates fine. The
program /etc/srcmstr also runs without difficulties.
Problems start with running the command "start sna". The command
starts out OK, but when we check with "ps -ef", the process has become
inactive. We also tried "snacontrol". The program runs fine but when
we try to start sna from the menues the process at first returns to
"active". It appears at first as if sna is running fine, but when we
issue the command "UPDATE" from the menue it appears that the process
has become "inactive" ("UPDATE" checks the different processes and
shows the active/inactive-status - what's on the screen may not be true
otherwise). Since the process now is inactive we can't start
connections and attachments. We get a message that indicates that the
server program is not running which we already knew (sna inactive).
Next we asked IBM Sweden, about solutions. They say that a particular
installation of SNA-services is tied to the very machine it is
installed on. Apparently is some kind of cpu-serial number checked.
They mentioned a command "peu" that perhaps could help but they weren't
sure. We found "/usr/lib/peu" but not in the manuals. Not in command
ref, inst. and maint, custom. AIX or in SNA services guide and ref.
Since we couldn't find the program in the manuals, we wern't able to
make "peu" run right.
The last idea we have is reinstalling SNA-services. We would rather
not do that since that requires rebuilding the kernel, followed by a
restart. The particular machine is in production at an HERTZ-rental
office and we prefer having the machine running 24 hours a day.
Does anybody know a fix for the problem without having to restart the
machine in the middle of the night.
SINCERELY THORSTEN JAKOBSSON, AXIELL AB
STURE LINGDEN, VOLVO CAR CORP.
PETER HAKANSSON, VOLVO DATA CORP.