>>> On 1/3/2011 at 08:25 PM, Stephen Frazier wrote:
> DIAG works with CDL format. As DIAG was added to Linux after CDL format
> was in wide use, I don't know if support for LDL was added to DIAG. (It
> probably was.)
Sorry, but that is not correct. The DIAG driver requires the disk to be in
ei
LDL format was the first format used by Linux. It was quickly replaced
by CDL format. The main difference is that a disk in CDL format is seen
as being full by all other operating systems (VM, VSE OS/390). However,
they see a LDL fromat disk as being empty. Thus if you are going to run
anything ot
Second time I am sending this. Weird interaction with Droid GMail applet
since Samir's post appeared (to GMail) to be spam (but Mark's did not, duh).
Anyway, LDL is kind of a misnomer. It simply means that the disk is all
blocked consistently at 4K, which is more good than bad. The only downsid
LDL is kind of a misnomer. It only means that the disk is all blocked
consistently (at 4K), which is more good than bad.
Last I recall, you could still boot from LDL just fine. (It is the original
layout for Linux/390 CKD.)
Last time I measured, I was disappointed to not find significant performa
>>> On 1/3/2011 at 10:59 AM, Samir Reddahi wrote:
> a couple of questions:
>
> 1) Are there any disadvantages of formatting disks as ldl instead of cdl?
With LDL, you only get one (automagically created) partition. With z/VM that's
not such a huge problem, since disks can be made any arbitrar
Last year I questioned WebSphere's propensity to eat memory and/or CPU over
time (thank you to Marcy and Rob for help). Now that we have 20 servers
running Medicare insurance claims, it is no longer a "hypothetical" scenario.
Each server runs several WAS instances, hence several Java processes
>> During IPL, TCPIP tries to attach device 0600, fails and stop working.
This is a problem from IPWIZARD.
You put the NICDEF command into Directory, correctly, so no need to get
the device via DTCPARMS. But, any inconsistency with DTCPARMS and TCPIP
dies.
Comment or delete the :ATTACH. line and
Thank you, David.
I removed "attach"and all works fine!
WBR, Sergey
David Kreuter
Sent by: Linux on 390 Port
03.01.2011 19:23
Please respond to Linux on 390 Port
To: LINUX-390@VM.MARIST.EDU
cc:
Subject:Re: VSWITCH for z/vm tcpip
Hi - remove or
The ATTACH is attaching real device 600-602. However you already have 600
defined as NIC.
Remove the ATTACH
-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Sergey
Korzhevsky
Sent: Monday, January 03, 2011 12:18 PM
To: LINUX-390@VM.MARIST.EDU
Hi, Sergey.
The entry in the SYSTEM DTCPARMS file is incorrect. It should read:
:nick.TCPIP:type.server
:class.stack
:VNIC.600 TO SYSTEM VSW1
Use VNIC instead of ATTACH.
DJ
On 01/03/2011 11:18 AM, Sergey Korzhevsky wrote:
> Hi All,
>
> Could you, please, hel
Hi - remove or comment out the ATTACH tag in your SYSTEM DTCPARMS. The
nicdef statement in the tcpip directory entry is taking care of business
by defining a vnic at addresses 600-602 and coupling it to vswitch vsw1.
Take this opportunity to remove class B privileges from TCPIP too.
David
-
Hi All,
Could you, please, help me define vswitch for linuxes AND z/VM TCPIP.
At first, i created all tcp/ip configuration with 'ipwizard' and real OSA
addresses and it worked fine. Now, i would like to move to VSWITCH.
The OSA is 010, i made the following changes in system config:
DEFINE VSWI
We have currently a couple of DB2 machines with logical volumes on MOD-9
ECKD disks. On our DB2 production server we have mdcache enabled for the
logical volumes that contains the DB2 data. The other servers have mdcache
disabled.
We already use the DIAG driver for the swap disks and the VDISKs. N
13 matches
Mail list logo
