Carsten Otte wrote:
> Anyway, you can use the parameter (diag) in your parmfile/kernel
parameter
> list to choose diag for a specific device
> or range. Works like this:
> "dasd=1234,1235(diag,ro),1236-1240,1241-1250(diag)"
Yup, that worked.
Thanks to all who replied.
"Mike MacIsaac" <[EMAIL PR
>> *** Reply to note of Fri, 19 Nov 2004 14:38:43 -0500 (EST/CDT)
>> *** by [EMAIL PROTECTED]
>>
>> And it works only on 31-bit systems.
>>
>Leland Lucius did a kernel patch which fixes this, as long as you have
>less than 2G of main storage.
It seems questionable to me that a patch that makes the
On Nov 19, 2004, at 2:09 PM, Sal Torres/SBC Inc. wrote:
*** Reply to note of Fri, 19 Nov 2004 14:38:43 -0500 (EST/CDT)
*** by [EMAIL PROTECTED]
And it works only on 31-bit systems.
Leland Lucius did a kernel patch which fixes this, as long as you have
less than 2G of main storage.
Adam
which driver picks up the DIAG disks.
>
>
>Mark Post
>
>-Original Message-
>From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
>Michael MacIsaac
>Sent: Friday, November 19, 2004 1:14 PM
>To: [EMAIL PROTECTED]
>Subject: VDISK swap on SLES9 and the F
: [EMAIL PROTECTED]
Subject: VDISK swap on SLES9 and the FBA vs. DIAG driver
Has anyone gotten VDISK swap spaces to use the DIAG driver on SLES-9? I
can't seem to.
I do this:
1) Create a VDISK in my PROFILE EXEC with 'SWAPGEN 101 524288 (DIAG'
2) Install SLES9 and specify "
Has anyone gotten VDISK swap spaces to use the DIAG driver on SLES-9? I
can't seem to.
I do this:
1) Create a VDISK in my PROFILE EXEC with 'SWAPGEN 101 524288 (DIAG'
2) Install SLES9 and specify "Set DIAG ON" in the DASD Disk Management
YaST panel
3) Add dasd_diag_mod to /etc/sysctrl/kernel, run
