Please follow this link to read the full interview:
http://www.itindepth.com/PSI_Ron_Interview.htm
8 ---
Quick, the oxygen!!
Multi-platform server consolidation: The PSI server is unique in that
it can be simultaneously used as a consolidation target for
On 3/8/06, John Summerfield [EMAIL PROTECTED] wrote:
Quick, the oxygen!!
Multi-platform server consolidation: The PSI server is unique in that
it can be simultaneously used as a consolidation target for traditional
mainframe systems such as z/OS and open systems such as Windows.
Everyone
I have just installed SuSE SLES 9 on zVM 5.1. It is Service Pack 0 but
fully patched. It is not finding the vdisks that I allocated for swap.
Googling around seems to indicate that it won't work on 64-bit, although
there is a private patch that does make it work. Does someone have the
latest
Please refer to:
http://www.ibm.com/developerworks/linux/linux390/whatsnew.html
for the 2006-03-08 change summary:
June 2003 stream:
- kernel 2.4.21 (patch 32) recommended kernel bug fixes
* end of message
Mit freundlichem Gruß /
Tom Shilson [EMAIL PROTECTED] wrote on 08.03.2006 17:27:21:
I have just installed SuSE SLES 9 on zVM 5.1. It is Service Pack 0 but
fully patched. It is not finding the vdisks that I allocated for swap.
Googling around seems to indicate that it won't work on 64-bit, although
there is a
That is not what I wanted to hear, but it has the ring of truth. Gr-r-r-r!
Thanks for the response!
Linux on 390 Port LINUX-390@VM.MARIST.EDU wrote on 03/08/2006 11:08:12
AM:
I don't know about that 'private patch', but:
z/VM 5.2:
Block I/O (Diagnose X'250'): Extended to allow a virtual
On z/VM5.2 I have an EDEVICE defined with multiple FCP paths to its scsi
device.
Does anyone know if VM does I/O load balancing across the EDEVICE's FCP
paths?
Or does VM use the extra paths just for fail-over when one of the FCP
paths is lost?
Tom,
To use vdisks for Linux swap, you need to add the following to SYSTEM
CONFIG :
Vdisk,
Syslim infinite ,
Userlim infinite
See Mike MacIssac's Virtual-Cookbook.
Bernie Wu
[EMAIL PROTECTED]
Tom Shilson
[EMAIL PROTECTED]
Our new VM guy, who did all sorts of interesting things back in the day was
wondering if there was a VMCF or VSECMD type of thing for z/VM to talk to,
get results back from and otherwise interact with a z/Linux guest.
I'm totally unfamiliar with 'VSECMD' as I think I was 20 the last time I
You can use the secondary console input facility (SCIF) to control the virtual
console of another machine. You can turn it on with SET SECUSER and/or the
CONSOLE directory statement.
If you set USERA to be the secuser of USERB usera can issue commands and view
the responses. This can be
Tom,
I forgot to add :
In your PROFILE EXEC
'SWAPGEN 101 524288' /* create a 256M VDISK swap space */
Once again, its in Mike MacIsaac's Virtual-Cookbook.
Bernie Wu
[EMAIL PROTECTED]
Tom Shilson
[EMAIL PROTECTED]
We talked about that - just concerned about what happens when an unhandled
exception leaves the console in a VMREAD state - doesn't that potentially
hang the guest?
David Kreuter [EMAIL PROTECTED]
Sent by: Linux on 390 Port
LINUX-390@VM.MARIST.EDU
Probably SET SECUSER is as close as you'll get. That allows you to manipulate
the console, and that can be automated with PROP.
There's been some discussion about Linux VMCF support, but since VMCF is
officially deprecated (in favor of IUCV) not a lot of effort has been put in
that direction.
well I don't really know your architecture or your needs but you can always
poll the console state and if needed issue a SEND CP USERB BEGIN to coax
userb back to a good state. Most of the time.
David
-Original Message-
From: Linux on 390 Port on behalf of James Melin
Sent: Wed 3/8/2006
If you are a secure system, you can use REXEC as we do.
Crispin Hugo
Systems Programmer, Macro 4
http://www.macro4.com/
Macro 4 plc, The Orangery, Turners Hill Road, Worth, Crawley, RH10 4SS
Direct Line: +44 (0)1293 872121 Switchboard: +44 (0) 1293 872000
Fax: +44 (0) 1293 872001
This message
VSECMD is CMS program that passes a command line to a VSE system and returns the
output of the command to CMS. It is useful as a CMS command the output comes
back to your screen. It is even more useful in a REXX procedure where the output
can be analyzed by the procedure.
I don't know of any
I don't think CP is involved in this; this should be the function of the
channel subsystem. CP starts a subchannel and subsystem picks an available path.
-- Original message --
From: Romanowski, John (OFT) [EMAIL PROTECTED]
On z/VM5.2 I have an EDEVICE defined
And from asking that question here I received a reply stating that its
done so using a round robin type algorithm.
Kurt Acker
Michael A. Short [EMAIL PROTECTED]
Sent by: Linux on 390 Port LINUX-390@VM.MARIST.EDU
03/08/2006 02:45 PM
Please respond to
Linux on 390 Port LINUX-390@VM.MARIST.EDU
My understanding of it is FCP channels aren't part of the traditional
CCW-based channel subsystem and don't necessarily have their features,
such as the channel subsystem picking a path.
I suspect CP's FBA emulator or CP's scsi driver stack has to do the I/O
load balancing. But I don't know
Quoting Tom Shilson [EMAIL PROTECTED]:
I have just installed SuSE SLES 9 on zVM 5.1. It is Service Pack 0 but
fully patched. It is not finding the vdisks that I allocated for swap.
Googling around seems to indicate that it won't work on 64-bit, although
there is a private patch that does
[Cross-posted to VMESA-L and LINUX-390]
Hi, Everyone. The VM Development team needs your help once again.
Back in July of last year, IBM published a Statement of Direction for
encrypting tape drives (Announcement 105-241). We would like to know:
- If you currently backup or archive z/VM data,
Quoting Leland Lucius [EMAIL PROTECTED]:
Quoting Tom Shilson [EMAIL PROTECTED]:
Unless, of course, you don't mind using that patch you found. It's been
working
for a couple of years now where I used to work. Even so...no guarantees.
:-)
Sorry...different patch. But, mine HAS been
It is the SCSI driver stack's responsibility to perform the path
selection, which in most cases uses a straightforward round-robin
approach. I think the main difference worth highlighting is that of the
DS6000 path selection, which tries to respect the PREFerred/NOTPREFerred
settings in the
We're about to move our DASD to new Shark. Linux/390 is currently on
addresses 0FAA and 0FAB. The new device addresses on the Shark will be
7949 and 794A.
Will Linus/390 automagically recognize these new devices? Or am I in
deep trouble?
Thanks,
Craig
are you in LPAR mode or under z/VM
Kittendorf, Craig
[EMAIL PROTECTED]
Sent by: Linux on 390 Port
To
LINUX-390@VM.MARIST.EDU
If you are running in lpar, then yes, you're in trouble.
No - not really. But you do have to change the addresses that the dasd
driver will bring online before you shutdown the old and IPL from the new
DASD. How to do this depends on what distro youre running. If you tell the
list, I'm sure
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On
Behalf Of Kittendorf, Craig
Sent: Wednesday, March 08, 2006 4:04 PM
To: LINUX-390@VM.MARIST.EDU
Subject: New DASD
We're about to move our DASD to new Shark. Linux/390 is currently on
addresses 0FAA and
LPAR mode.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
James Melin
Sent: Wednesday, March 08, 2006 5:10 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: New DASD
are you in LPAR mode or under z/VM
Kittendorf, Craig
[EMAIL
LPAR mode running SuSE Linux SLES S/390 Version 7.2.0-0 (Kernel 2.4.7)
Thanks
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Robert J Brenneman
Sent: Wednesday, March 08, 2006 5:13 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: New DASD
If you are running
We're running SuSE Linux SLES S/390 Version 7.2.0-0 (Kernel 2.4.7) in
LPAR mode.
I doubt we have anyone here (nice or otherwise) that knows hows to
map the old device addresses to the new ones. FDRPAS is being used to
move the volumes.
Thanks,
-Original Message-
From: Linux on 390 Port
Once again: LPAR mode running SuSE Linux 7.2 (S390) - Kernel 2.4.7-SMP
and moving to new dasd.
What about changing the current dasd addresses in the following:
/boot/parmfile
/proc/dasd/devices
/etc/zipl.conf
to the new dasd addresses.
Run zipl?
Anything else?
Thanks,
Craig
On Mar 8, 2006, at 6:42 PM, Kittendorf, Craig wrote:
Once again: LPAR mode running SuSE Linux 7.2 (S390) - Kernel 2.4.7-SMP
and moving to new dasd.
What about changing the current dasd addresses in the following:
/boot/parmfile
/proc/dasd/devices
/etc/zipl.conf
to the new dasd addresses.
Is there a reasonable place to ask an Linux/Intel question? I'm spoiled
by this forum!
My question, in case anybody is interested, relates to recovering a
dead mouse. I have four desktops connected to a single
keyboard/video/mouse via a KVM switch. If I lose power to the KVM
switch, the mouse on
Yes, the network devices remain the same. I fought that crisis a few
weeks ago.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Adam Thornton
Sent: Wednesday, March 08, 2006 8:01 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: New DASD
On Mar 8, 2006, at
34 matches
Mail list logo
