Please refer to:
http://www.ibm.com/developerworks/linux/linux390/whatsnew.html
for the 2006-03-28 change summary:
April 2004 stream:
- Updated manual: Device Drivers, Features, and Commands
- Updated Technical details
- Updated Restrictions
October 2005 stream:
- kernel 2.6.16
On Wednesday, 03/29/2006 at 09:31 ZE2, Grega Bremec [EMAIL PROTECTED]
wrote:
We've just upgraded from z/VM 4.4 to z/VM 5.2 and I am wondering if it
was safe to use QIOASSIST with OSA and HiperSocket devices with 5.2
already. We had some nasty issues with JDBC connection pools from WAS to
DB2 -
Tim,
Does anyone have a log, or other documentation, on the sequence of
events I'm supposed to see in an install of SLES9 via FTP?
It's documented in the Virtualization Cookbook for an NFS install. The
only difference with the FTP install will be early in the process on the
3270 session after
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Alan Altmark wrote:
| On Wednesday, 03/29/2006 at 09:31 ZE2, Grega Bremec [EMAIL PROTECTED]
| wrote:
|
| We've just upgraded from z/VM 4.4 to z/VM 5.2 and I am wondering if
| it was safe to use QIOASSIST with OSA and HiperSocket devices with
|
Here is the rest.
Ryan
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
Inst2.doc
And the rest.
Ryan
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
Inst3.doc
On Wednesday, 03/29/2006 at 07:58 ZE2, Grega Bremec [EMAIL PROTECTED]
wrote:
I don't know if this APAR [VM63685] was closed prior to release of z/VM
5.2, and
last time I heard about it, it was still open. So I'm asking if anyone
can either verify it was actually fixed in z/VM 5.2, if there is a
This year WAVV is a little early. I find that it is not as easy to get away at
this time as it was when it was later. Personal not work related reasons. I was
going to bring this up at WAVV but I realized that the people who have the same
problems may not be there. David's comment on VSE-L about
I haven't gotten to the software selection menu. I get, in the ssh Yast
panel...
A message under Partitioning No automatic proposal possible. Specify
mount points manually in the 'Partitioning' dialog
A message under Software cannot read package data from installation
media. Media error? ERROR:
Tim,
I haven't gotten to the software selection menu. I get, in the ssh Yast
panel...
A message under Partitioning No automatic proposal possible. Specify
mount points manually in the 'Partitioning' dialog
So you are able to FTP into your FTP server because you get past the
networking
Jim...I'm sending this back out on the listserv as others have also been
asking...
We may be on simular but different tangents.
From my understanding, DB2 Connect is only for the ascii side to
connect to mainframe servers.
DB2/UDB on zLinux is not a mainframe server (still the ascii side).
So,
We have a Hipersocket defined between two guests. It has stopped
working on one of the guests. I have deleted the configuration and
recreated it and ran mkinitrd. We have also rebooted the guest. Below
is the config file for the failing interface:
BOOTPROTO='static'
BROADCAST='10.14.1.255'
What are the addresses of the hipersockets in the failing machine?
Being QDIO I believe that the hipersocket low order address needs to be
even. It should be a triplet of
even (read) even+1(write) available address(date transfer)
David
Kenneth Libutti wrote:
We have a Hipersocket defined
Also you describe hipersockets between two guests. Are these guests on
the same LPAR? Is the hipersocket being used by different LPARs?
David
Kenneth Libutti wrote:
We have a Hipersocket defined between two guests. It has stopped
working on one of the guests. I have deleted the configuration
I've been meaning to get back to this for some time. I looked at the
SLES9 kernel source. There's nothing in the smbfs code that would
generate that kind of message. I'm guessing that SUSE/Novell hacked the
modutils code to put out that message and set the kernel tainting on.
Just exactly
I run into that as well when I build one from scratch (so to speak). I
can't remember what the screen looks like, but go the Expert
Partitioner route.
Select your device (i.e., /dev/dasda1, etc.), format it, choose your
file system, choose your mount point, etc. You should then be able to
I must be missing something here. I performed the steps you suggested
and tried again. Got the same result. Checked modprobe list and found
that there are two files and one is old:
-rw-r--r-- 1 root root 20319 Mar 27 15:16
/lib/modules/2.6.5-7.97-s390/kernel/drivers/s390/char/cpint_mod.ko
The guests are on the same LPAR but we do have the Hipersocket connected
to a third vse machine in another LPAR and that connection is
functioning. The addresses for the failing hipersocket are F509 F50A
F50B.
Ken Libutti CNE, CNI, SCSA, RHCT
Asst. Director of Systems Services
Broward Community
Just out of curiosity, what is the MTU size?
Thanks,
tom
- - - - - - - - - - - -
Toto, I have a feeling we're not in the mainframe world any more.
_/) Tom Shilson
~Unix Team / IT Server Services
Aloha Tel: 651-733-7591 tshilson at mmm dot
We copied all the 6 SLES9 CDs into a server and pointed Yast to the
server when trying to install python.
Yast does not recognise the FTP directories. It does not walk down from
the base directory to look for the packages. We have
/SUSE/S390/Server9/Install/disk1 ... disk2 and so on.
The
ifconfig -a from non-working interface:
hsi0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
inet addr:10.14.1.4 Bcast:10.14.1.255 Mask:255.255.255.0
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING NOARP MULTICAST MTU:57344 Metric:1
In SLES8 you could copy all the CDs into one directory and it would work.
In SLES9 they fixed that. The CDs need to be in a particular structure
with some links and the server has to be running a YaST server program.
tom
- - - - - - - - - - - -
Toto, I have a feeling we're not in the mainframe
Are there any messages on syslog when you load the driver? What does ls -l
/dev/cpcmd show now?
-Original Message-
I must be missing something here. I performed the steps you suggested
and tried again. Got the same result. Checked modprobe list and found
that there are two files and one
OK. I got it working. I performed a make install again, did a
modprobe -r cpint_mod and then modprobe cpint_mod
zlt1:/home/tssrxn1/cpint-2.5.3 # make install
install -c -m 750 mongen /usr/sbin
install -c -m 750 monstat /usr/sbin
install -c -m 750 hcp /usr/sbin
cp cpint_mod.ko
Post, Mark K wrote:
I've been meaning to get back to this for some time. I looked at the
SLES9 kernel source. There's nothing in the smbfs code that would
generate that kind of message. I'm guessing that SUSE/Novell hacked the
modutils code to put out that message and set the kernel
Ok, a clarification. I was referring to but post-installation install
of software. Is there any documentation on how to set up an FTP server
for software upgrade? Is this same as YOU server?
Tom Shilson wrote:
In SLES8 you could copy all the CDs into one directory and it would work.
In SLES9
26 matches
Mail list logo
